Release 8
`
`49
`
`3C-EPP TS 36.300 VB.4.0 (2008-03}
`
`NOTE:
`
`the total number ofbits is 5 for TDD Frame Structure Type ll.
`
`2) Random Access Response generated by MAC on DL-SCH:
`
`-
`
`Semi-synchronous {within a flexible window ofwhich the size is one or more TTI) with message 1;
`
`- No HARQ;
`
`- Addressed to RA-RNTI on I.lr‘L2 control channel;
`
`- Conveys at least RA-preamble identifier, Timing Alignment information, initial UL grant and assignment of‘
`Temporary C-RNTI (which may or may not be made permanent upon RRC Contention Resolution);
`
`-
`
`Intended for a variable number of UEs in one DL-SCH message.
`
`3) First scheduled UL transmission on UL-SCH:
`
`- Uses HARQ;
`
`-
`
`-
`
`Size ofthe transport blocks depends on the UL grant conveyed in step 2 and is at least 80 bits.
`
`For initial access:
`
`- Conveys the RRC Connection Request generated by the RRC layer and transmitted via CCCH;
`
`- Conveys at least NAS UE identifier but no NAS message;
`
`- RLC TM: no segmentation;
`
`- After radio link failure:
`
`- Conveys the RRC Connection Re-establishment Request generated by the RRC layer and transmitted via
`CCCH;
`
`- RLC TM: no segmentation;
`
`- Does not contain any NAS message.
`
`- After handover, in the target cell:
`
`- Conveys the ciphered and integrity protected RRC Handover Confinn generated by the RRC layer and
`transmitted via DCCH:
`
`- Conveys the C-RNTI ofthe UE (which was allocated via the Handover Command);
`
`-
`
`Includes an uplink Buffer Status Report when possible.
`
`-
`
`For other events:
`
`- Conveys at least the C-RNTI ofthe UE.
`
`4) Contention Resolution on DL-SCH:
`
`- Early contention resolution shall be used i.e. eNB does not wait for NAS reply before resolving contention
`
`- Not synchronised with message 3;
`
`- HARQ is supported;
`
`- Addressed to:
`
`- The Temporary C-RNTI on LHL2 control channel for initial access and after radio link failure;
`
`- The C-RNTI for UE in RRC_CONNECTED;
`
`- HARQ feedback is transmitted only by the UE which detects its own UE identity, as provided in message 3,
`echoed in the RRC Contention Resolution message;
`
`-
`
`For initial access and after radio link failure. no segmentation is used (RLC-TM}.
`
`3GPP
`
`ZTE/HTC
`
`Exhibit 1017-0101
`
`ZTE/HTC
`Exhibit 1017-0101
`
`

`
`Release 8
`
`50
`
`3GPP TS 36.300 V8.4.0 [2008-03}
`
`The Temporary C-RNTI is promoted to C-RNTI for a UE which detects RA success and does not already have a C-
`RNTI; it is dropped by others. A UE which detects RA success and already has a C-RNTI, resumes using its C-RNTI.
`
`10.1.5.2
`
`Non-contention based random access procedure
`
`The non-contention based random access procedure is outlined on Figure l0. l .5.2—l below:
`
`
`
`UE
`
`eNB
`
`6*)
`
`(9
`
`RA Preamble assignment
`
`Random Access Preamble-er ®
`
`Random ACCESS RES pone
`
`
`
`Figure 10.1.5.2-1: Non-contention based Random Access Procedure
`
`The three steps ofthe non-contention based random access procedures are:
`
`0) Random Access Preamble assignment via dedicated signalling in DL:
`
`eNB assigns to UE a non-contention Random Access Preamble (a Random Access Preamble not within the
`set broadcasted on BCH).
`
`Signalled via:
`
`HO command generated by target eNB and sent via source eNB for handover;
`
`MAC signalling {LUL2 control channel or MAC control PDU is FFS) in case of DL data arrival.
`
`I} Random Access Preamble on RACH in uplink:
`
`UE transmits the assigned non-contention Random Access Preamble.
`
`2)
`
`Random Access Response on DL-SCH:
`
`Semi-synchronous (within a flexible window ofwhich the size is one or more TTl) with message 1;
`
`No HARQ;
`
`Addressed to RA-RNTI on LUL2 control channel;
`
`Conveys at least:
`
`Timing Alignment information and initial UL grant for handover;
`
`Timing Alignment information for DL data an'ival;
`
`RA-preamble identifier.
`
`intended for one or multipie UEs in one DL-SCH message.
`
`10.1.5.3
`
`Interaction model between L1 and L2z'3 for Random Access Procedure
`
`Random access procedure described above is modelled in Figure 10.1.5.3-I below from LI and L213 interaction point
`ofview. L2fL3 receives indication from LI whether ACK is received or DTX is detected after indication of Random
`
`3GPP
`
`ZTE/HTC
`
`Exhibit 1017-0102
`
`ZTE/HTC
`Exhibit 1017-0102
`
`

`
`Release 8
`
`51
`
`3GPP TS 36.300 VB.4.0 (2008-03)
`
`Access Preamble transmission to L1. L28 indicates L1 to transmit first scheduled UL transmission (RRC Connection
`Request in case of initial access) if necessary or Random Access Preamble based on the indication from L].
`
`_
`_,
`_
`_
`L1 lzransrnrts Flmdorn
`Access Preamble“
`
`Response” reoefl-ion)‘
`
`ACK C‘Random
`Access Response’
`reception)
`
`DTX reception (No
`"Random Assess
`
`Figure 10.1.5.3-1: Interaction model between L1 and L213 for Random Access Procedure
`
`10.1.6 Radio Link Failure
`
`Two phases governs the behaviour associated to radio link failure as shown on Figure 10.1.6-1:
`
`-
`
`First phase:
`
`-
`
`-
`
`-
`
`-
`
`started upon radio problem detection;
`
`leads to radio link failure detection;
`
`no UE—based mobility;
`
`based on timer or other (e.g. counting) criteria (Ti).
`
`-
`
`Second Phase:
`
`—
`
`-
`
`started upon radio link failure detection or handover failure;
`
`leads to RRC_|DLE;
`
`- UE-based mobility;
`
`- Timer based (T3).
`
`First Phase
`
`
`
`RRC_CONN ECTED
`RRC_|DLE
`
`
`no recovery during T1
`
`F
`
`.
`
`
`
`radio link failure
`
`Figure 1D.1.6—1: Radio Link Failure
`
`Table I0. I .6-I below describes how mobility is handled with respect to radio link failure:
`
`3GPP
`
`ZTE/HTC
`Exhibit 1017-0103
`
`

`
`Release 8
`
`52
`
`3C-SPF TS 36.300 VB.4.0 (2008-03}
`
`Table 10.1.6-1: llllobiiity and Radio Link Failure
`
`Second Phase
`First Phase
`Cases
`UE returns to the same cell Continue as if no radio Activity is resumed by means
`problems occurred
`of explicit signalling between
`UE and eNB
`
`T2 expired
`Go via RRC_lDLE
`
`Go via RRC_|DLE
`
`Go via RRC_lDLE
`
`Activity is resumed by means
`of explicit signalling between
`UE and eNB
`
`Activity is resumed by means
`of explicit signalling between
`UE and eNB
`
`a prepared eNB is an eNB which has admitted the UE during an earlier executed HO preparation phase.
`
`UE selects a different cell
`from the same eNB
`
`UE selects a cell of a
`prepared eNB (NOTE)
`
`UE selects a cell of a
`different eNB that is not
`
`prepared (NOTE)
`NOTE:
`
`Go via RRC_lDLE (FFS)
`
`Go via RRC_IDLE
`
`in the Second Phase, in order to resume activity and avoid going via RRC_lDLE when the UE returns to the same cell
`or when the UE selects a different cell from the same eNB, or when the UE selects a cell from a different eN B, the
`following procedure applies:
`
`— The UE stays in RRC_CONNECTED;
`
`- The UE accesses the cell through the random access procedure;
`
`-
`
`The UE identifier used in the random access procedure for contention resolution (i.e. C-RNTI ofthe UE in the
`cell where the RLF occurred + physical layer identity ofthat cell + MAC based on the keys ofthat cell) is used
`by the selected eNB to authenticate the UE and check whether it has a context stored for that UE:
`
`-
`
`-
`
`Ifthe eNB finds a context that matches the identity ofthe UE, it indicates to the UE that its connection can be
`resumed;
`
`lfthe context is not found, RRC connection is released and UE initiates procedure to establish new RRC
`connection. In this case UE may be required to go via RRC_lDLE (FFS).
`
`10.1.7 Radio Access Network Sharing
`
`E-UTRAN shall support radio access network sharing based on support for multi-to-muiti relationship between E-
`UTRAN nodes and EPC nodes (S1-flex).
`
`ifthe E-UTRAN is shared by multiple operators, the system information broadcasted in each shared cell contains the
`PLMN-id ofeach operator {up to 6) and a single tracking area code {TAG} valid within all the PLMNS sharing the radio
`access network resources.
`
`The UE shall be able to read up to 6 PLMN-ids, to select one ofthe PLMN-ids at initial attachment and to indicate this
`PLMN-id to the E-UTRAN in subsequent instances ofthe Random Access procedures (e.g. as defined in subclause
`I01 .5). The E-UTRAN shall select an appropriate MME for the PLMN indicated by the UE. Once attached to an
`MM E, the UE shall be able to indicate the allocated MME in subsequent instances ofthe Random Access procedures.
`Whether the indication ofthe selected PLMN or the allocated MME is contained in the temporary UE identity or
`signailed separately is FFS.
`
`Handiing ofarea restrictions for UE in ECM-CONNECTED shall follow the principles specified in sub-clause 10.4.
`
`10.1.8 Handling of Roaming and Area Restrictions for UEs in ECM—
`CONNECTED
`
`Handling ofroainingfarea restrictions and handling of subscription specific preferences in ECM-CONNECTED is
`performed in the eNB based on information provided by the EPC over the SI interface.
`
`3GPP
`
`ZTE/HTC
`
`Exhibit 1017-0104
`
`ZTE/HTC
`Exhibit 1017-0104
`
`

`
`Release 8
`
`53
`
`3C-SPF TS 36.300 VB.4.0 (2008-03}
`
`10.2
`
`Inter RAT
`
`Service-based redirection between GERAN I UTRAN and E-UTRAN is supported in both directions. This should not
`require inter-RAT reporting in RRC CONNECTION REQUEST.
`
`10.2.1
`
`Cell reselection
`
`A UE in RRC_IDLE performs cell reselection. The principles ofthis procedure are as follows:
`
`- The UE makes measurements of attributes ofthe serving and neighbour cells to enable the reselection process:
`
`-
`
`-
`
`For a UE to search and measure neighbouring GERAN cells. the ARFCNs ofthe BCCH carriers need to be
`indicated in the sewing cell system information (i.e., an NCL). The NCL does not contain BSlCs or cell
`specific offsets and Qrxlevmin is given per frequency band.
`
`For a UE to search and measure neighbouring UTRAN cells, the serving cell can indicate an NCL containing
`a list ofcarrier frequencies and scrambling codes.
`
`- Measurements may be omitted ifthe serving cell attribute fulfils particular search or measurement criteria.
`
`- Cell reselection identifies the cell that the UE should camp on. [t is based on cell reselection criteria which
`involves measurements ofthe serving and neighbour cells:
`
`-
`
`Inter-RAT reselection is based on absolute priorities where UE tries to camp on highest priority RAT
`available. Absolute priorities for inter-RAT reselection are provided only by the RPLMN and valid only
`within the RPLMN; priorities are given by the system information and valid for all UEs in a cell, specific
`priorities per UE can be signalled in the RRC‘ Connection Release message. A validity time can be associated
`with UE specific priorities.
`
`-
`
`It should be possible to prevent the UE from reselecting to specific detected neighbouring cells;
`
`- The UE is allowed to "leave" the source E-UTRAN cell to read the target GERAN cell broadcast, in order to
`determine its "suitability". prior to completing the cell reselection;
`
`- Cell reselection can be speed dependent [speed detection based on UTRAN solution};
`
`Cell access restrictions apply as for UTRAN. which consist of access class (AC) barring and cell reservation (e.g. for
`cells "reserved for operator use"] applicable for mobiles in RRC_lDLE mode.
`
`When performing cell reselection while the UE is camped on another RAT. the principles ofthis procedure are as
`follows:
`
`- The UE measures attributes ofthe E-UTRA neighbouring cells:
`
`- Only the carrier frequencies need to be indicated to enable the UE to search and measure E-UTRA
`neighbouring cells;
`
`- Cell reselection identifies the cell that the UE should camp on. It is based on cell reselection criteria which
`involves measurements ofthe serving and neighbour cells:
`
`-
`
`For E-UTRA neighbouring cells, there is no need to indicate cell-specific cell reselection parameters i.e.
`these parameters are common to all neighbouring cells on an E-UTRA frequency;
`
`- Cell reselection parameters are applicable to all UEs in a cell, but it is possible to configure specific reselection
`parameters per UE group or per UE.
`
`-
`
`It should be possible to prevent the UE from reselecting to specific detected neighbouring cells.
`
`10.2.2 Handover
`
`inter RAT H0 is designed so that changes to GERAN and UTRAN are minimised. This can be done by following the
`principles specified for GERAN toffrom UTRAN intersystem H0. in particular the following principles are applied to
`E-UTRAN Inter RAT HO design:
`
`3GPP
`
`ZTE/HTC
`
`Exhibit 1017-0105
`
`ZTE/HTC
`Exhibit 1017-0105
`
`

`
`Release 8
`
`54
`
`3C-SPF TS 36.300 VB.4.0 (2008-03)
`
`1.
`
`Inter RAT H0 is network controlled through source access system. The source access system decides about
`starting the preparation and provides the necessary information to the target system in the format required by the
`target system. That is, the source system adapts to the target system. The actual handover execution is decided in
`the source system.
`
`2.
`
`Inter RAT H0 is backwards handover, i.e. radio resources are prepared in the target 3GPP access system before
`the UE is commanded by the source 3G PP access system to change to the target 3GPP access system.
`
`3. To enable backwards handover, and while RAN level interfaces are not available, a control interface exists in
`CN level. In Inter RAT H0 involving E-UTRAN access, this interface is between 2Gf3G SGSN and
`corresponding MMEE Serving Gateway.
`
`4. The target access system will be responsible for giving exact guidance for the UE on how to make the radio
`access there (this includes radio resource configuration, target cell system information etc.}. This information is
`given during the handover preparation and should be transported completely transparently through the source
`access system to the UE.
`
`5. Mechanisms for avoiding or mitigating the loss of user data {i.e. forwarding} can be used until the 3GPP Anchor
`determines that it can send DL U-plane data directly to the target system.
`
`6. The handover procedure shouid not require any UE to CN signalling in order for data to start to flow in the target
`system. This requires that the security context. UE capability context and QoS context is transferred (or
`translated) within the network between source and target system.
`
`7'. Similar handover procedure should apply for handovers of both real time and non-real time services.
`
`8. Similar handover procedure should apply for both Inter RAT Handover and intra-LTE Handover with EPC node
`change.
`
`9. Network controlled mobility is supported even if no prior UE measurements have been perfonned on the target
`cell andfor frequency i.e. “blind H0" is supported.
`
`10.2.23 Inter-RAT cell change order to GERAN with NACC
`
`For interworking towards GERAN. inter-RAT cell change order with NACC is supported even if no prior UE
`measurements have been perfonned on the system i.e. “blind NACC“ is supported.
`
`10.2.3 Measurements
`
`10.2.3.1
`
`Inter-RAT handovers from E-UTRAN
`
`Measurements to be performed by a UE for inter-RAT mobility can be controlled by E-UTRAN, using broadcast or
`dedicated control. In RRC'_CONNECTED state. a UE shall follow the measurement parameters specified by RRC or
`MAC commands {FFS) directed from the E—UTRAN (e.g. as in UTRAN MEASUREMENT_CONTROL).
`
`UE perfonns inter-RAT neighbour cell measurements during DLIUL idle periods that are provided by the network
`through suitable DRXIDTX period or packet scheduling ifnecessary.
`
`10.2.3.2
`
`Inter-RAT handovers to E-UTRAN
`
`From UTRAN, UE performs E-UTRAN measurements by using idle periods created by compressed mode
`(CELL_DCH), FACH measurement occasions (CELL_FACH - FFS}, or DRX (other states).
`
`From GERAN, E-UTRAN measurements are perfonrred in the same way as WC DMA measurements for handover to
`UTRAN: E-UTRAN measurements are performed in GSM idle frames in a time multiplexed manner. However. it
`should be discussed with GERAN how to ensure that inter-RAT measurements do not take too much measurement time.
`while the requested 3GPP inter-RAT measurements can be performed well enough.
`
`Design constraints of 3GPP inter-RAT measurements should be considered when Ll details of E-UTRAN concept are
`defined.
`
`3GPP
`
`ZTE/HTC
`
`Exhibit 1017-0106
`
`ZTE/HTC
`Exhibit 1017-0106
`
`

`
`Release 8
`
`55
`
`3C-SPF TS 36.300 VB.4.0 (2008-03}
`
`10.2.3.3
`
`Inter-RAT cell reselection from E-UTRAN
`
`In RRC_IDLE state, a UE shall follow the measurement parameters specified by the E-UTRAN broadcast [as in
`UTRAN SIB). The use ofdedicated measurement control is FPS.
`
`10.2.3.4
`
`Limiting measurement load at UE
`
`Introduction of E-UTRA implies co-existence of various UE capabilities. Each UE may support different combinations
`ofRATs. e.g., E-UTRA, UTRA, GSM, and non-3GPP RATS, and different combinations offrequency bands, e.g., 800
`MHz, 1.? (EH2, 2 GHZ. etc. Moreover, some UEs may support the full E-UTRA spectrum bandwidth of 20 MHz,
`whereas some UEs may support only a part of 20 MHZ. Despite such heterogeneous environment, the measurement
`load at UE should be minimised. To limit the measurement load and the associated control load:
`
`-
`
`E-UTRAN can configure the RATS to be measured by UE;
`
`- The number ofmeasurement criteria {event and periodic reporting criteria) should be limited {as in TS 25.133
`subclause 8.3.2 [7]);
`
`- E-UTRAN should be aware ofthe UE capabilities for efficient measurement control, to prevent unnecessary
`waking up of the measurement entity;
`
`- The UE capabilities should be categorised to prevent diversion ofcapabilities and conformance test scenarios.
`FFS;
`
`-
`
`Support for blind HO (i.e.. H0 without measurement reports from UE} is FFS.
`
`10.2.4 Network Aspects
`
`Inter-frequencyfinter-RAT UE based mobility relies on a “priority based scheme", where the network configures a list
`of RATs!frequencies to be taken as basis for UE’s inter-frequency/inter-RAT cell reselection decisions in priority order.
`E-UTRAN cells can enable inter-frequencyfinter-RAT cell reselection by broadcasting a common priority valid for all
`UEs in a given cell in addition to other inter-frequencyfinter-RAT infonnation.
`
`NOTE: The same principles apply in UTRAN.
`
`These common priorities can be overwritten by E-UTRAN through dedicated signalling to individual UEs at
`RRC_CONNECTED to RRC_lDLE transition.
`
`NOTE:
`
`In order to have consistent inter-RAT operation, the same principles apply to inter-RAT reselection to E-
`UTRAN. For UTRAN this includes also the transitions within RRC_CONNECTED state from
`CELL_DCH to CELL_PCH and URA_PCH.
`
`Setting dedicated priorities by E-UTRAN can be based on subscription related infonrlation provided by the MME.
`
`NOTE:
`
`The same principle have been taken as a working assumption in UTRAN (awaiting for SA2 decision on
`feasibility ofproviding subscription related information by the CN}.
`
`10.3
`
`Mobility between E-UTRAN and Non-3GPP radio
`technologies
`
`10.3.1
`
`UE Capability Configuration
`
`A UE shall be able to communicate with the E-UTRAN about its radio access capability, such as the system (including
`the release and frequency band) it supports and it's receive and transmit capabilities isingleidual radio. dual receiver}.
`UE shall transfer its capability about other radio technologies over E-UTRAN using the same procedure used to carry
`its E-UTRAN radio capability.
`
`10.3.2 Mobility between E—UTRAN and cdma2000 network
`
`This section describes the E-UTRAN mechanisms to support idle and active mode mobility between E-UTRAN and
`cdma2000 HRPD or lxRTT. The overall system is described in [17].
`
`3GPP
`
`ZTE/HTC
`
`Exhibit 1017-0107
`
`ZTE/HTC
`Exhibit 1017-0107
`
`

`
`Release 8
`
`10.3.2.1
`
`56
`
`3C-SPF TS 36.300 VB.4.0 (2008-03}
`
`Tunnelling of cdma2000 Messages over E-UTRAN between UE and
`cdma2000 Access Nodes
`
`In order to efficiently support handover procedures when on E-UTRAN with a cdma2000 target system, cdma2000
`messages are sent transparently to the target system over the E-UTRAN, with the eNB and MME acting as relay points.
`
`To support the MME in its selection ofthe correct target system node to which it should route an Uplink tunnelled
`message and to provide the target system with infonnation that is needed to resolve technology-specific measurement
`information (RouteUpdate and pilot strength measurements) that are delivered to the cdrna2000 system each eNB cell is
`associated with a cdma2000 HRPD Sector[D andfor with a cdma2000 lxRTT SectorlD [generically referred to as
`cdma2000 reference cellid). This cdma2000 reference cellid is provided by the eNB to the MME using the cdma200D
`message transfer capability over S I-AP and forwarded to the target system via the S101 interface and corresponding
`interface to the cdma2000 lxRTT system.
`
`Tunnelling is achieved over the E-UTRAN radio interface by encapsulating tunnelled cdma2000 messages in the UL
`Information Transfer and DL Information Transfer RRC messages {e.g., similar to UMTS UplinkfDownlink Direct
`Transfer). A specific IE in these RRC messages is used to identify the type of information contained in the message
`(c.g.. NAS. TunneledMsg). Additionally ifthe message is carrying a tunnelled message, an additional IE is included to
`carry RRC Tunnelling Procedure lnfonnation.
`
`RRC Tunnelling Procedure Information in the UL direction will include:
`
`- RAT type { IXRTT encapsulated, HRPD encapsulated];
`
`-
`
`cdma2000 message type (e.g. pre-registration or handover initiation).
`
`RRC Tunnelling Procedure Information in the DL direction will include:
`
`- RAT type { 1xRTT encapsulated. HRPD encapsulated].
`
`AS level security will be applied for these U L Information Transfer and DL Information Transfer RRC messages as
`normal but there is no NAS level security for these tunnelled cdma200(} messages.
`
`UE
`
`eNB
`
`MME
`
`DL infonnation Transfer
`(lnfo ‘rype_
`RRC DLTunne|ing Proc Info,
`cdma2000 Message)
`
`DL 31 Information Transfer
`—(S1 DL Tunneling Proc |nfo.—
`Cdmazooo M95939?)
`
`Figure 10.3.2.1-1: Downiink Direct Transfer
`
`UE
`
`eNB
`
`UL information Transfer
`( Info Type,
`RRC U|_Tun,-,e|ing p,-0° |nfo’
`cdmagggg Message)
`
`c.dma2D00 Message)
`
`_
`UL 81 Information Transfer
`(81 UL Tunneling Free Info,
`
`Figure 10.3.2.1-2: Uplink Direct Transfer
`
`Tunnelling to the MME is achieved over the S1-MME interface by encapsulating the tunnelled cdma2000 message in a
`new S1-MME S1 lnfomiation Transfer message. These SI-MME messages carry S1 Tunnelling Procedure Information
`as well as the tunnelled message.
`
`SI Tunnelling Procedure lnformation in the UL direction will include:
`
`-
`
`cdma2000 Reference Cell ld;
`
`3GPP
`
`ZTE/HTC
`
`Exhibit 1017-0108
`
`ZTE/HTC
`Exhibit 1017-0108
`
`

`
`Release 8
`
`57
`
`3C-SPF TS 36.300 VB.4.0 (2008-03}
`
`- RAT type { IXRTT encapsulated, HRPD encapsulated];
`
`-
`
`cdma200{) message type (e.g. pre-registration or handover initiation).
`
`S1 Tunnelling Procedure information in the DL direction will include:
`
`- RAT type { lxRTT encapsulated. HRPD encapsulated):
`
`-
`
`cdma2000 message type (eg. pre-registration or handover completion];
`
`- Data forwarding information ifrequired.
`
`10.3.2.2
`
`Mobility between E—UTRAN and HRPD
`
`‘l0.3.2.2.1
`
`Mobility from E-UTRAN to HRPD
`
`10.3.2.2.1.1
`
`HRPD System Information Transmission in E-UTRAN
`
`The HRPD system information block (SIB) shall be sent on the E-UTRAN BCCH. The UE shall monitor the E-
`UTRAN BCCH during the RRC_lDLE and RRC_CONNECTED modes to retrieve the HRPD system infomtation for
`the preparation ofcell reselection or handover from the E-UTRAN to HRPD system. HRPD system information may
`also be provided to the UE by means ofdedicated signalling. The following HRPD system infonnation is transmitted on
`E-UTRAN BCCH:
`
`- HRPD pre-registration allowed;
`
`- HRPD Pre-registration Zone;
`
`- HRPD Neighbour Bandclass;
`
`- HRPD Neighbour Frequency;
`
`- HRPD Searching Window Size;
`
`- HRPD Neighbour PN Sequence Offset;
`
`- HRPD Pilot PN sequence offset index increment;
`
`- HRPD Timing Reference;
`
`- Number of HRPD Neighbour Bandclass;
`
`- Number of HRPD Neighbour Frequency;
`
`- Number of HRPD Neighbour PN Sequence Offset;
`
`- HRPD Start Measuring E-UTRAN Signal Quality Threshold;
`
`- HRPD Start Measuring E-UTRAN Rx Power Strength Threshold.
`
`10.3.2.2.1.2
`
`Measuring HRPD from E-UTRAN
`
`Measurement events and parameters for HRPD measurements are to be aligned with those defined in section 10.2.3.
`
`10.3.2.2.1.2.1
`
`Idle Mode Measurement Control
`
`UE shall be able to make measurements on the HRPD cells in RRC_[DLE mode to perform cell re-selection.
`The intra-3GPP inter-RAT idle mode measurement control is re-used to control the idle mode measurements on HRPD.
`
`The UE performs measurement on HRPD when the signal quality from E-UTRAN serving cell falls below a given
`threshold.
`
`3GPP
`
`ZTE/HTC
`
`Exhibit 1017-0109
`
`ZTE/HTC
`Exhibit 1017-0109
`
`

`
`Release 8
`
`58
`
`3C-SPF TS 36.300 VB.4.0 (2008-03}
`
`10.3.2.2.1.2.2
`
`Active Mode Measurement Control
`
`In RRC_CONNECTED mode, the UE shall perform radio measurements on the HRPD network when directed by the
`E-UTRAN network. The network provides the required HRPD neighbour cell list information and measurement
`controls to the UE through dedicated RRC‘ signalling. When needed the eNB is responsible for configuring and
`activating the HRPD measurements on the UE via the dedicated RRC signalling message. Periodic and event-triggered
`measurements are supported.
`
`For single-radio terminals, measurement gaps are needed to allow the UE to switch into the HRPD network and do
`radio measurements. These measurement gaps are network-controlled. The eNB is responsible for configuring the gap
`pattern and providing it to the UE through RRC dedicated signalling. Terminals with a dual receiver perform
`measurements on HRPD neighbour cells without tuning away from the E-UTRAN network. No DL gap patterns will be
`required for UEs which are capable ofsimultaneous reception on the involved frequency bands. No UL gap patterns
`will be required for UEs which are capable simultaneous transmission in one access and measuring on another access.
`
`10.3.2.2.1.2.3
`
`Active Mode Measurement
`
`ln RRC_CONNECTED mode, the UE measures the strengths ofeach ofthe HRPD neighbour cells and reports them in
`an RRC message.
`
`10.3.2.2.1.3
`
`Pre—registration to HRPD Procedure
`
`Pre-registration allows a UE to establish a presence with an HRPD system in advance ofa cell re-selection or handover.
`E-UTRAN network instructs the UE whether the pre-registration is needed over broadcast channel and in a dedicated
`RRC message.
`
`E-UTRAN does not need to know whether a specific UE is pre-registered or not. The procedure is transparent to E-
`UTRAN network. In the pre-registration to HRPD, messages shall be tunnelled inside RRC and S1-AP messages
`between the UE and MME and in a generic "transfer" message between source MME and target RNC.
`
`The UE is responsible for maintaining the HRPD context e.g. by performing periodic re-registrations if needed. The UE
`will use "HRPD Pre-registration Zone" to decide whether a re-registration shall be performed. A dual-receiver UE can
`ignore the parameter. E-UTRAN will provide the "HRPD Pre-registration Zone" parameter on the E-UTRAN system
`information broadcast channel or dedicated RRC signalling (unless it is determined that the UE will read the E-UTRAN
`system information broadcast channel in RRC,CONNECTED). Re-registrations are only allowed in areas where pre-
`registration is requested.
`
`10.3.2.2.1.4
`
`E-UTRAN to HRPD Cell Re-selection
`
`The pre-condition for cell re-selection from E-UTRAN to HRPD is that the UE has previously established a presence in
`the target HRPD network, either through the pre-registration procedure or previous HRPD attachment. The UE
`perfonns Cell re-selection to HRPD while in RRC_|DLE.
`
`Cell reselection from E-UTRAN to HRPD should be aligned with 3CrPP inter RAT cell reselection mechanism. .
`
`.
`
`10.3.2.2.‘l.5
`
`E-UTRAN to HRPD Handover
`
`The pre-condition for the E-UTRAN to HRPD Handover procedure is that the UE is attached in the E-UTRAN network
`in E-UTRAN_ACTlVE state and has pre-registered with the HRPD network. Based on measurement reports received
`from the UE the eNB initiates a handover by sending an RRC message to the UE to indicate to the UE that it should
`begin the handover procedure. This message shall include the specified target type and any cdma2000 specific HRPD
`parameters needed by the UE to create the appropriate HRPD messages needed to request a connection. These HRPD
`parameters are transparent to E-UTRAN. The set of the required HRPD parameters are out of scope of this
`specification.
`The UE can continue to send and receive data on the E-UTRAN radio until it receives the “handover command”. After
`
`the "handover command" is received by the UE, the UE shall leave the E-UTRAN radio and start acquiring the HRPD
`traffic channel. The HRPD handover signaliing is tunnelled between the UE and HRPD network. The HRPD network
`sends the high level progress of the ongoing HRPD signalling (e.g. Handover Success, Handover Failure) to E-UTRAN.
`
`10.32.22
`
`Mobility from HRPD to E—UTRAN
`
`Mobility from HRPD to E-UTRAN has no impact on the E-UTRAN.
`
`3GPP
`
`ZTE/HTC
`
`Exhibit 1017-0110
`
`ZTE/HTC
`Exhibit 1017-0110
`
`

`
`Release 8
`
`59
`
`3C-SPF TS 36.300 VB.4.0 (2008-03}
`
`10.3.2.3
`
`Mobility between E-UTRAN and cdma2000 ‘IXRTT
`
`10.3.2.3.1
`
`Mobility from E-UTRAN to cdma2000 TXRTT
`
`10.3.2.3.1.1
`
`cdma2000 1xRTT System Information Transmission in E-UTRAN
`
`The cdma2000 txRTT system information biock (SIB) shall be sent on E-UTRAN BCCH. The UE shall monitor the
`E-UTRAN BCCH during the LTE_lDLE and RRC_CONNECTED modes to retrieve the l!(RTT system information
`for the preparation of handover from the E-UTRAN to cdma 2000 lxRTT system.
`lXRTT system infonnation may also
`be provided to the UE by means ofdedicated signalling. The following cdma2000 lxRTT system information shall be
`carried on E-UTRAN BCCH:
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`cdma2000 IX Neighbour Bandclass;
`
`cdma2000 IX Neighbour Frequency;
`
`cdma2U00 IX Neighbour PN Sequence Offset;
`
`cdma2000 IX Pilot PN sequence offset index increment;
`
`cdma2000 IX Timing Reference:
`
`cdma2000 Ix Searching Window Size;
`
`- Number ofcdma2D00 IX Neighbour Bandclass;
`
`- Number ofcdma2000 IX Neighbour Frequency;
`
`- Number ofcdma2000 IX Neighbour PN Sequence Offset;
`
`-
`
`-
`
`cdrna2000 IX Start Measuring E-UTRAN Signal Quality Threshold;
`
`cdma2000 lX Start Measuring E-UTRAN Rx Power Strength Threshold.
`
`10.3.2.3.1.2
`
`Measuring cdma200G ‘EXRTT from E—UTRAN
`
`Measurement events and parameters for ]xRTT measurements are to be aligned with those defined in section 10.2.3.
`
`10.3.2.3.1.2.1
`
`Idle Mode Measurement Control
`
`UE shall be able to make measurements on the lxRTT system cells in LTE_lDLE mode to perform cell re-selection.
`UE shall perfomt cdn1a2000 IxRTT neighbour cell measurements during DRX periods, between paging occasions.
`The intra-3G PP inter-RAT idle mode measurement control is re-used to control the idle mode measurements on
`
`cdma2D00 lxRTT. The UE performs measurement on cdma2000 lxRTT when the signal quality from E-UTRAN
`Serving cell falls below a given threshold.
`
`10.3.2.3.1.2.2 Active Mode Measurement Control
`
`In the E-UTRAN network, in RRC_CONNECTED mode, the UE shall perform radio measurements on the cdma2000
`lxRTT network when directed by the E-UTRAN network. The network provides the required cdma2000 lXRTT
`neighbour cell list information and measurement controls to the UE through dedicated RRC signalling. When needed
`the eNB is responsible for configuring and activating the cdma2000 lxRTT measurements on the UE via the dedicated
`RRC signalling message. As for intra-3GPP inter-RAT measurement reporting, periodic and event-triggered
`measurements are supported.
`
`For single-radio terminals, measurement gaps are needed to allow the UE to switch into the cdma2000 lXRTT network
`and do radio measurements. These Measurement gaps are network-controlled. The eNB is responsible for configuring
`the gap pattern and providing it to the UE through RRC dedicated signalling. Terminals with a dual receiver perform
`measurements on edma2000 lxRTT neighbour cells without tuning away from the E-UTRAN network. No DL gap
`patterns will be required for UEs which are capable ofsimultaneous reception on the involved frequency bands. No UL
`gap patterns will be required for UEs which are capable simultaneous transmission in one access and measuring on
`another access.
`
`3GPP
`
`ZTE/HTC
`
`Exhibit 1017-0111
`
`ZTE/HTC
`Exhibit 1017-0111
`
`

`
`Release 8
`
`B0
`
`3C-SPF TS 36.300 VB.4.0 (2008-03}
`
`10.3.2.3.1.2.3 Active Mode Measurement
`
`In RRC_CONNECTED mode, the UE measures the strengths of each ofthe cdma2(}00 lxRTT neighbour cells and
`reports them in an RRC Message.
`
`10.3.2.3.1.3
`
`E-UTRAN to cdma2000 1xRTT Cell Re-selection
`
`UE performs Cell re-selection to cdma2000 lxRTT while in RRC_[DLE.
`
`Cell reselection from E-UTRAN to lxRTT should be aligned with 3GPP inter RAT cell reselection mechanism.
`
`10.3.2.3.1.4
`
`E-UTRAN to cdma2000 1><RTT Handover
`
`In the high level procedure for handover from E-UTRAN to cdma2D00 lxRTT, registration and handover is performed
`directly afier the handover decision has been Inade. Based on measurement reports received from the UE the eNB
`initiates a handover by sending a RRC message to the UE to indicate to the UE that it should begin the handover
`procedure. This message shall include the specified target type and any cdma2000 specific lxRTT access parameters
`neede