hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.8 QoS Considerations | The removal of one GPRS specific node from the data path by the One Tunnel Approach improves the packet bearer QoS by reducing the packet transfer delay.
If two tunnels are established then the SGSN has to perform the following functions:
- IP/UDP termination
- GTP termination,
- look up for the corresponding PDP conte... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.9 Security | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.10 O&M | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.11 RAN Considerations (e.g. GERAN) | The One Tunnel Approach is applicable for any RAN with separated transport and control at the interface to the core network, i.e. for UTRAN and the Iu enabled part of the GERAN. The One Tunnel Approach has no impact on the RAN. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.12 Abnormal Cases | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.13 Compatibility | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.14 Benefits and Drawbacks | The benefits and drawbacks are compared to the R’99 architecture, unless otherwise specified.
Benefits:
- Removes the SGSN from the user data path when this is possible (NB, it is expected to apply for most of the cases). The delay that the packets experience in the UMTS network is then decreased by bypassing the SGSN ... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.15 Open Issues | - The actual reduction in delay by bypassing the SGSN in the transport plane is strongly dependent on implementation and can therefore not be exactly estimated here. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8 Summary | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.1 Selection Criteria | This subsection contains an unordered list of selection criteria which will be used as a guideline when the feasibility study makes its recommendation.
The selection criterion is divided into two parts. The first refers to specific aims of the Feasibility Study and is included to give a clear indication of the advantag... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.1.1 Aims | - Available in a timely manner (e.g., R4/R5). However, the interactions with a split of call control and user planes, also in UTRAN, need to be taken into consideration to allow comprehensive operator reasoning behind the viability of the split functionality
- The chosen approach should make efficient use of the networ... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.1.2 Compatibility criteria | - Can be introduced into an existing network in a phased manner, i.e. can co-exist and inter-operate with non-split elements of the same type.
- Applicable for both pre-pay and subscription subscribers
- Applicable for both roaming and non-roaming subscribers
- Should not preclude the use of Mobile IP, both v4 and v6, ... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.2 Assignment of Functions to the Logical Architecture | The following table provides an overview of the functions performed by the different nodes of each alternative. SGSN and GGSN refer to R99 nodes and also to the case where it is not possible to establish one tunnel in alternative 2.
NOTE 1: For alternative 2, the SGSN and cSGSN functions on one hand, and the GGSN and x... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.2.1 High-Level Functions Description | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.2.1.1 Network Control Functions | Authentication and Authorisation Function: This function performs the identification and authentication of the service requester, and the validation of the service request type to ensure that the user is authorised to use the particular network services. The authentication function is performed in association with the ... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.2.1.2 Packet Routeing and Transfer Functions | Relay Function: The relay function is the means by which a node forwards data received from one node to the next node in the route.
Routeing Function: The routeing function determines the network node to which a message should be forwarded and the underlying service(s) used to reach that GPRS Support Node (GSN), using ... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.2.1.3 Mobility Management Functions | The mobility management functions are used to keep track of the current location of an MS within the PLMN or within another PLMN. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.3 Comparison of the Overall Functionality | The table below addresses the cases where the respective evolved architectures are applicable.
NOTE 1: The split SGSN approach is not applicable when 2G radio is used.
NOTE 2: The one tunnel approach is not applicable when 2G radio is used, at inter PLMN scenarios, and when R97-R99 SGSN and/or GGSN is used.
Table 3: Co... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 9 Work Plan | SA2#13
May 22-26, 2000
Proposal for a new Work Item.
CN/SA2 workshop
June 14-15, 2000
Discussion of Work Item responsibilities.
SA#8
June 26-28, 2000
Work Item and distribution of responsibilities approved.
Drafting session
August 22-24
Discussion and selection of alternative architectures to be studied. Start work on ... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 1 Scope | The purpose of the present document is to help the TSG RAN WGs to understand the proposed method and to specify the impacts to existing specifications, which is needed for the introduction of the “Enhancement on the DSCH hard split mode” for Release 5.
“Enhancement on the DSCH hard split mode” is proposed to specify th... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
For a specific reference, subsequent revisions do not apply.
For a no... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 3 Definitions, symbols and abbreviations | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply. |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 3.2 Symbols | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply:
TFCI Transport Format Combination Indicator
DSCH Downlink Shared Channel |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4 TFCI coding in DSCH hard split mode | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4.1 Introduction | In the current Rel99 & Rel’4 specification, as identified by RAN WG’s (WG1, WG2 and WG3), when DSCH scheduling be done in DRNC, logical split cannot be supported over Iur during the DSCH soft handover. Furthermore, hard split has advantage over logical split in the sense that it can be supported over Iur. However, it w... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4.3.4 Operation of TFCI in Hard Split Mode | If one of the DCH is associated with a DSCH, the TFCI code word may be split in such a way that the code word relevant for TFCI activity indication is not transmitted from every cell. The use of such a functionality shall be indicated by higher layer signalling.
The TFCI is encoded by using punctured code of (32,10) su... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4.4.3.1 Study Areas | 4.4.3.1.1 Impact on NBAP messages
Currently, on Iub interface, it is assumed that the TFCI bit for DCH and DSCH in hard split mode have 5 bit/5 bit length. TFCI signalling mode that contains TFCI split information is included in following NBAP messages for DSCH split mode setting.
• RADIO LINK SETUP REQUEST
• RADIO LI... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 9.2.2.50 TFCI signalling mode | This parameter indicates if the normal or split mode is used for the TFCI. In the event that the split mode is to be used then the IE indicates whether the split is 'Hard' or 'Logical', and in the event that the split is 'Logical' the IE indicates the number of bits in TFCI (field 2).
IE/Group Name
Presence
Range
IE ty... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 9.2.2.46 TFCI Signalling Mode | This parameter indicates if the normal or split mode is used for the TFCI.
IE/Group Name
Presence
Range
IE type and reference
Semantics description
TFCI Signalling Mode
ENUMERATED (Normal, Split)
===========================================================================
In the above message, if the TFCI Signalling Mod... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4.4.3.2 Agreements and associated contributions | 4.4.3.2.1 Impact on TS 25.423
4.4.3.2.1.1 RADIO LINK SETUP REQUEST
FDD Message
IE/Group Name
Presence
Range
IE type and reference
Semantics description
Criticality
Assigned Criticality
Message Type
M
9.2.1.40
YES
reject
Transaction ID
M
9.2.1.59
–
SRNC-Id
M
RNC-Id
9.2.1.50
YES
reject
S-RNTI
M
9.2.1.53
YES
reject
D-RNT... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4.4.3.2.1.3 UPLINK SIGNALLING TRANSFER INDICATION | FDD Message
IE/Group Name
Presence
Range
IE type and reference
Semantics description
Criticality
Assigned Criticality
Message Type
M
9.2.1.40
YES
ignore
Transaction ID
M
9.2.1.59
–
UC-Id
M
9.2.1.71
YES
ignore
SAI
M
9.2.1.52
YES
ignore
Cell GAI
O
9.2.1.5A
YES
ignore
C-RNTI
M
9.2.1.14
YES
ignore
S-RNTI
M
9.2.1.54
YES
ign... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4.4.3.2.1.5.2 Flexible Hard Split Support Indicator | The Flexible Hard Split Support Indicator indicates whether the particular cell is capable to support Flexible Hard Split or not.
IE/Group Name
Presence
Range
IE type and reference
Semantics description
Flexible Hard Split Support Indicator
ENUMERATED (Flexible Hard Split Supported,).
4.4.3.2.2 Impact on TS 25.433
Fo... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4.4.3.3 Specification Impact and associated Change Request | Table 1: Place where Change request is given in order to refer the new procedure
3G TS
CR
Title
Remarks
25.433
583
NBAP signalling support for DSCH hard split mode
25.423
543
RNSAP signalling support for DSCH hard split mode |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4.4.3.4 Backward Compatibility | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5 TFCI power control in DSCH hard split mode | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.1 Introduction | According to Release99 and Rel’4 specification, there is split mode of operation where TFCI2 (TFCI for DSCH) is not necessarily transmitted from every cell in the active set when UE is in soft handover region. Thus, the combined TFCI power in UE may not be enough to detect it reliably. As well, the power offset for TFC... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.3 Proposed TFCI power control scheme | In this section, some details on the proposed TFCI power control scheme are described, in which new parameters such as TFCI PO or TFCI PO_primary are introduced in Frame Protocol specification and how to allocate flexible power offset for TFCI is explained. As well, simulation results are shown to indicate the required... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.4 Specification Impact and associated Change Request | The expected specification impacts are small.
25.214: Time-varying TFCI power by method 1 or method 2 should be explained.
• For method 1, no impact is expected.
• For method 2, SSDT uplink signalling usage for TFCI power control is to be described.
25.427: The changed power offset should be signalled via Iur/Iub signa... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.2.1 DPCCH/DPDCH | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.2.1.1 General | The downlink transmit power control procedure controls simultaneously the power of a DPCCH and its corresponding DPDCHs. The power control loop adjusts the power of the DPCCH and DPDCHs with the same amount, i.e. the relative power difference between the DPCCH and DPDCHs is not changed.
The relative transmit power offs... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.2.1.4 Site selection diversity transmit power control | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.2.1.4.1 General | Site selection diversity transmit power control (SSDT) is another macro diversity method in soft handover mode. This method is optional in UTRAN.
Operation is summarised as follows. The UE selects one of the cells from its active set to be ‘primary’, all other cells are classed as ‘non primary’. The main objective is t... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.4.2 Agreements and associated contributions | It is agreed that the Method2 described in the study area is accepted as the Enhanced TFCI Power Control procedure and this solution will be adopted and specified in RAN3 TSs.
1. It is agreed to use the User plane to signal TFCI power offsets.
2. It is agreed that TFCI PO and TFCI PO_primary parameters are introduced i... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.4.3 Specification Impact and associated Change Request | 5.4.3.1 Impacts on RNSAP (TS 25.423)
=========================== TS 25.423 ============================== |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 8.3.1 Radio Link Setup | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 8.3.1.1 General | This procedure is used for establishing the necessary resources in the DRNS for one or more radio links.
The connection-oriented service of the signalling bearer shall be established in conjunction with this procedure. |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 8.3.1.2 Successful Operation | Figure 5: Radio Link Setup procedure: Successful Operation
When the SRNC makes an algorithmic decision to add the first cell or set of cells from a DRNS to the active set of a specific UE-UTRAN connection, the RADIO LINK SETUP REQUEST message is sent to the corresponding DRNC to request establishment of the radio link(... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 8.3.1.3 Unsuccessful Operation | Figure 6: Radio Link Setup procedure: Unsuccessful Operation
In unsuccessful case (i.e. one or more RLs can not be established) the RADIO LINK SETUP FAILURE message shall be sent to the SRNC, indicating the reason for failure. If some radio links were established successfully, the DRNC shall indicate this in the RADIO... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 8.3.2 Radio Link Addition | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 8.3.2.1 General | The Synchronised Radio Link Reconfiguration Preparation procedure is used to prepare a new configuration of Radio Link(s) related to one UE-UTRAN connection within a Node B.
The Synchronised Radio Link Reconfiguration Preparation procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subcl... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 8.3.2.2 Successful Operation | Figure 30: Synchronised Radio Link Reconfiguration Preparation procedure, Successful Operation
The Synchronised Radio Link Reconfiguration Preparation procedure is initiated by the CRNC by sending the message RADIO LINK RECONFIGURATION PREPARE to the Node B. The message shall use the Communication Control Port assigned... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 8.3.2.3 Unsuccessful Operation | Figure 8: Radio Link Addition procedure: Unsuccessful Operation
If the establishment of at least one RL is unsuccessful, the DRNC shall send a RADIO LINK ADDITION FAILURE as response.
If some RL(s) were established successfully, the DRNC shall indicate this in the RADIO LINK ADDITION FAILURE message in the same way as ... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 9.1.4 RADIO LINK SETUP RESPONSE | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 9.1.4.1 FDD Message | IE/Group Name
Presence
Range
IE type and reference
Semantics description
Criticality
Assigned Criticality
Message Type
M
9.2.1.40
YES
reject
Transaction ID
M
9.2.1.59
–
D-RNTI
O
9.2.1.24
YES
ignore
CN PS Domain Identifier
O
9.2.1.12
YES
ignore
CN CS Domain Identifier
O
9.2.1.11
YES
ignore
RL Information Response
1..<ma... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 9.1.5 RADIO LINK SETUP FAILURE | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 9.1.5.1 FDD Message | IE/Group Name
Presence
Range
IE type and reference
Semantics description
Criticality
Assigned Criticality
Message Type
M
9.2.1.40
YES
reject
Transaction ID
M
9.2.1.59
–
D-RNTI
O
9.2.1.24
YES
ignore
CN PS Domain Identifier
O
9.2.1.12
YES
ignore
CN CS Domain Identifier
O
9.2.1.11
YES
ignore
CHOICE Cause Level
M
YES
ignor... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 9.1.7 RADIO LINK ADDITION RESPONSE | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 9.1.7.1 FDD Message | IE/Group Name
Presence
Range
IE type and reference
Semantics description
Criticality
Assigned Criticality
Message Type
M
9.2.1.40
YES
reject
Transaction ID
M
9.2.1.59
–
RL Information Response
1..<maxnoofRLs-1>
EACH
ignore
>RL ID
M
9.2.1.49
–
>RL Set ID
M
9.2.2.35
–
>URA Information
O
9.2.1.70B
–
>SAI
M
9.2.1.52
–
>Cel... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 9.1.8 RADIO LINK ADDITION FAILURE | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 9.1.8.1 FDD Message | IE/Group Name
Presence
Range
IE type and reference
Semantics description
Criticality
Assigned Criticality
Message Type
M
9.2.1.40
YES
reject
Transaction ID
M
9.2.1.59
–
CHOICE Cause Level
M
YES
ignore
>General
–
>>Cause
M
9.2.1.5
–
>RL Specific
–
>>Unsuccessful RL Information Response
1..<maxnoofRLs-1>
EACH
ignore
>>>R... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 8.2.17 Radio Link Setup | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 8.2.17.1 General | This procedure is used for establishing the necessary resources for a new Node B Communication Context in the Node B.
[FDD – The RL Setup procedure is used to establish one or more radio links. The procedure establishes one or more DCHs on all radio links, and in addition, it can include the establishment of one or mor... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 8.2.17.2 Successful Operation | Figure 24: Radio Link Setup procedure, Successful Operation
The procedure is initiated with a RADIO LINK SETUP REQUEST message sent from the CRNC to Node B.
Upon reception of RADIO LINK SETUP REQUEST message, the Node B shall reserve necessary resources and configure the new Radio Link(s) according to the parameters gi... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 8.3.2 Synchronised Radio Link Reconfiguration Preparation | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.8 Radio Interface Parameter Update [FDD] | This procedure is used to update radio interface parameters which are applicable to all RL's for the concerning UE. Both synchronised and unsynchronised parameter updates are supported.
The procedure consists of a RADIO INTERFACE PARAMETER UPDATE control frame sent by the SRNC to the Node B.
Figure 9: Radio Interface P... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 6.3.3.9 RADIO INTERFACE PARAMETER UPDATE [FDD] | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 6.3.3.9.1 Payload structure | The figure 22 shows the structure of the payload when the control frame is used for signalling radio interface parameter updates.
Figure 22: Structure of the payload for the RADIO INTERFACE PARAMETER UPDATE control frame |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 6.3.3.9.2 Radio Interface Parameter Update flags | Description: Contains flags indicating which information is valid in this control frame.
Value range:
Bit 0: Indicates if the 3rd byte of the control frame payload contains a valid CFN (1) or not (0);
Bit 1: Indicates if the 4th byte (bits 0-4) of the control frame payload contains a valid TPC PO (1) or not (0);
Bit 2:... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 6.3.3.9.3 TPC Power Offset (TPC PO) | Description: Power offset to be applied in the DL between the DPDCH information and the TPC bits on the DPCCH as specified in the clause 5.2 of [12].
Value range: {0-7.75 dB}.
Granularity: 0.25 dB.
Field length: 5 bits. |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 6.3.3.9.4 Spare Extension | The Spare Extension IE is described in subclause 6.3.3.1.4.
6.3.3.9.4A CFN
Description: The CFN value indicates when the presented parameters shall be applied.
Value range: As defined in subclause 6.2.4.3.
Field length: 8 bits. |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 6.3.3.9.5 DPC Mode | Description: DPC mode to be applied in the UL.
Value range: {0,1}.
The DPC mode shall be applied as specified in [12].
Field length: 1 bit.
6.3.3.9.x TFCI Power Offset (TFCI PO)
Description: Power offset to be applied in the DL between the DPDCH information and the TFCI bits on the DPCCH.
Value range: {0-31.75 dB}.
Gra... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.4.4 Backward Compatibility | Rel’ 5-Node Bs and Release 99 (or Rel’ 4)-Node Bs in the same active set:
• Rel’ 5- and Release 99 (or Rel’ 4)-Node Bs may be configured in the same active set. In this case, while flexible TFCI power offset would be set in the Rel’ 5-Node Bs, fixed power offset would be set in the Release 99 (or Rel’ 4)-Node Bs. This ... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.5 Backward Compatibility | 5.5.1 DSCH power offset
In the current specification, the DSCH power offset is described as information element in the Iub specification (Frame Protocol) [3].
The indicated value is the offset relative to the power of the TFCI bits of the downlink DPCCH directed to the same UE as the DSCH.
From the above description, t... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 7 History | Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
08/03/02
RAN_15
RP-020127
Approved at TSG RAN #15 and placed under Change Control
-
5.0.0 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 1 Scope | This technical Report identifies the RF Radio Transmission/Reception and Radio Resource Management requirements for the 1.28 Mcps UTRA TDD option, including the commonalties and differences. Furthermore, the impact on the RF system Scenarios and BS conformance testing is also identified. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• Fo... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 3 Abbreviations | (void) |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4 RF Parameters in Support of Radio Resource Management | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.1 Idle Mode | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.1.1 Cell Selection | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.1.1.1 Introduction | After a UE has switch on and a PLMN has been selected, the cell selection process takes place. This process allows the UE to select a suitable cell where to camp on in order to access available services. In this process the UE can use stored information (stored information cell selection) or not (initial cell selection... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.1.2 Cell Re-Selection | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.1.2.1 Introduction | The cell re-selection procedure allows the UE to select a more suitable cell and camp on it.
When the UE is in Normally Camped state it shall attempt to detect, synchronise and monitor cells indicated in the measurement control system information of the serving cell. If the occasions/triggers occur, as specified in 25.... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.1.2.2 Requirements | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.1.2.2.1 Measurement and evaluation of cell selection criteria S of serving cell | The UE shall measure the PCCPCH RSCP level of the serving cell and evaluate the cell selection criterion S defined in TS 25.304 [8] for the serving cell once per DRX cycle. The UE shall filter the PCCPCH RSCP level of the serving cell using at least 2 measurements, which are taken so that the time difference between th... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.1.2.2.2 Measurement of intra-frequency cells | The UE shall measure PCCPCH RSCP at least every TmeasureNTDD (see table 4.1) for intra-frequency cells that are detected and measured according to the measurement rules. TmeasureNTDD is defined in Table 4.1. The UE shall filter PCCPCH RSCP measurements of each measured intra-frequency cell using at least 2 measurement... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.1.2.2.3 Measurement of 1.28 Mcps TDD inter-frequency cells | The UE shall measure PCCPCH RSCP at least every (Ncarrier-1) * TmeasureNTDD (see table 4.1) for inter-frequency cells that are detected and measured according to the measurement rules. The parameter Ncarrier is the number of carriers used for NTDD cells. The maximum number of carriers is [3] including the carrier the U... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.1.2.3 High Chip Rate TDD re-selection | This requirement only applies to UEs supporting this mode.
The ranking of the low and high chip rate TDD cells shall be made according to the cell reselection criteria specified in TS 25.304 [8]. The use of mapping functions is indicated in the broadcast.
The UE shall measure PCCPCH RSCP at least every NTDDcarrier * Tm... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.1.2.4 FDD Cell re-selection | This requirement only applies to UEs supporting this mode.
The UE shall measure the signal level CPICH RSCP of each FDD neighbour cell indicated in the measurement control system information of the serving cell, according to the measurement rules defined in TS 25.304 [8], at least every TmeasureFDD (see table 4.1). The... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.1.3 Measurement of inter-RAT GSM cells | These requirements only apply to UEs supporting GSM.
The UE shall measure the signal level of each GSM neighbour cell indicated in the measurement control system information of the serving cell, according to the measurement rules defined in TS 25.304 [8], at least every TmeasureGSM (see table 4.1). The UE shall mainta... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.1.4 Evaluation of cell reselection criteria | The UE shall evaluate the cell re-selection criteria defined in TS 25.304 [8]for the cells, which have new measurement results available, at least every DRX cycle.
Cell reselection shall take place immediately after the UE has found a better suitable cell unless the UE has made cell reselection within the last 1 second... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.1.5 Maximum interruption time in paging reception | UE shall perform the cell re-selection with minimum interruption in monitoring downlink channels for paging reception.
At intra-frequency cell re-selection, the UE shall monitor the downlink of current serving cell for paging reception until the UE is capable to start monitoring downlink channels of the target intra-fr... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.1.6 Numbers of cells in neighbouring cell list | The UE shall be capable of monitoring [32] intra-frequency NTDD cells (including serving cell),
- [32] inter-frequency cells including low and high chip rate TDD Mode cells and FDD Mode cells if FDD and/or high chip rate TDD is supported by the UE
- the NTDD inter-frequency cells can be located on [x] additional freque... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2 Connected Mode | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.1 TDD/TDD Handover | The requirements apply for 1.28 Mcps and 3.84 Mcps handover. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.1.1 Introduction | The purpose of TDD/TDD handover is to change the cell of the connection between UE and UTRAN. The handover procedure is initiated from UTRAN with a RRC message that implies a handover. The handover procedure may cause the UE to change its frequency.
The handover process should be implemented in both the UE and UTRAN. T... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.1.2 Requirements | Requirements for 3.84 Mcps are only applicable if high chip rate TDD is supported by the UE. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.1.2.1 Handover delay | Procedure delay for all procedures, that can command a hard handover, are specified in TS 25.331 [9].
When the UE receives a RRC message that implies a handover, with the activation time "now" or earlier than Dhandover seconds from the end of the last TTI containing the RRC command,,the UE shall start transmission with... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.