hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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
ignore
>General
–
>>Cause
M
9.2.1.5
–
>RL Specific
–
>>Unsuccessful RL Information Response
1...<maxnoofRLs>
EACH
ignore
>>>RL ID
M
9.2.1.49
–
>>>Cause
M
9.2.1.5
–
>>Successful RL Information Response
0..<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
–
>>>Cell GAI
O
9.2.1.5A
–
>>>UTRAN Access Point Position
O
9.2.1.70A
–
>>>Received Total Wide Band Power
M
9.2.2.35A
–
>>>Secondary CCPCH Info
O
9.2.2.37B
–
>>>DL Code Information
M
FDD DL Code Information
9.2.2.14A
–
>>>Diversity Indication
M
9.2.1.21
–
>>>CHOICE Diversity Indication
M
–
>>>>Combining
–
>>>>>RL ID
M
9.2.1.49
Reference RL ID for the combining
–
>>>>>DCH Information Response
O
9.2.1.16A
YES
ignore
>>>>Non Combining or First RL
–
>>>>>DCH Information Response
M
9.2.1.16A
–
>>>SSDT Support Indicator
M
9.2.2.43
–
>>>Maximum Uplink SIR
M
Uplink SIR
9.2.1.69
–
>>>Minimum Uplink SIR
M
Uplink SIR
9.2.1.69
–
>>>Closed Loop Timing Adjustment Mode
O
9.2.2.3A
–
>>>Maximum Allowed UL Tx Power
M
9.2.1.35
–
>>>Maximum DL TX Power
M
DL Power
9.2.1.21A
–
>>>Minimum DL TX Power
M
DL Power
9.2.1.21A
–
>>>Primary CPICH Power
M
9.2.1.44
–
>>>Primary Scrambling Code
O
9.2.1.45
–
>>>UL UARFCN
O
UARFCN
9.2.1.66
Corresponds to Nu in ref. [6]
–
>>>DL UARFCN
O
UARFCN
9.2.1.66
Corresponds to Nd in ref. [6]
–
>>>DSCH Information Response
O
DSCH FDD Information Response
9.2.2.13B
YES
ignore
>>>Neighbouring UMTS Cell Information
O
9.2.1.41A
–
>>>Neighbouring GSM Cell Information
O
9.2.1.41C
-
>>>PC Preamble
M
9.2.2.27a
-
>>>SRB Delay
M
9.2.2.39A
-
>>>Cell GA Additional Shapes
O
9.2.1.5B
YES
ignore
>>>TFCI PC Support Indicator
O
9.2.2.x
YES
ignore
Uplink SIR Target
O
Uplink SIR
9.2.1.69
YES
ignore
Criticality Diagnostics
O
9.2.1.13
YES
ignore
Range bound
Explanation
MaxnoofRLs
Maximum number of RLs for one UE.
Unaffected parts are omitted |
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
–
>Cell GAI
O
9.2.1.5A
–
>UTRAN Access Point Position
O
9.2.1.70A
–
>Received Total Wide Band Power
M
9.2.2.35A
–
>Secondary CCPCH Info
O
9.2.2.37B
–
>DL Code Information
M
FDD DL Code Information
9.2.2.14A
YES
ignore
>Diversity Indication
M
9.2.1.21
–
>CHOICE Diversity Indication
M
–
>>Combining
–
>>>RL ID
M
9.2.1.49
Reference RL ID
–
>>>DCH Information Response
O
9.2.1.16A
YES
ignore
>>Non Combining
–
>>>DCH Information Response
M
9.2.1.16A
–
>SSDT Support Indicator
M
9.2.2.43
–
>Minimum Uplink SIR
M
Uplink SIR
9.2.1.69
–
>Maximum Uplink SIR
M
Uplink SIR
9.2.1.69
–
>Closed Loop Timing Adjustment Mode
O
9.2.2.3A
–
>Maximum Allowed UL Tx Power
M
9.2.1.35
–
>Maximum DL TX Power
M
DL Power
9.2.1.21A
–
>Minimum DL TX Power
M
DL Power
9.2.1.21A
–
>Neighbouring UMTS Cell Information
O
9.2.1.41A
–
>Neighbouring GSM Cell Information
O
9.2.1.41C
–
>PC Preamble
M
9.2.2.27a
–
>SRB Delay
M
9.2.2.39A
–
>Primary CPICH Power
M
9.2.1.44
–
>Cell GA Additional Shapes
O
9.2.1.5B
YES
ignore
>TFCI PC Support Indicator
O
9.2.2.x
YES
ignore
Criticality Diagnostics
O
9.2.1.13
YES
ignore
Range bound
Explanation
MaxnoofRLs
Maximum number of radio links for one UE.
Unaffected parts are omitted |
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
>>>RL ID
M
9.2.1.49
–
>>>Cause
M
9.2.1.5
–
>>Successful RL Information Response
0..<maxnoofRLs-2>
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
–
>>>Cell GAI
O
9.2.1.5A
–
>>>UTRAN Access Point Position
O
9.2.1.70A
–
>>>Received Total Wide Band Power
M
9.2.2.35A
–
>>>Secondary CCPCH Info
O
9.2.2.37B
–
>>>DL Code Information
M
FDD DL Code Information
9.2.2.14A
YES
ignore
>>>Diversity Indication
M
9.2.1.21
–
>>>CHOICE Diversity Indication
M
–
>>>>Combining
–
>>>>>RL ID
M
9.2.1.49
Reference RL ID
–
>>>>>DCH Information Response
O
9.2.1.16A
YES
ignore
>>>>Non Combining
–
>>>>>DCH Information Response
M
9.2.1.16A
–
>>>SSDT Support Indicator
M
9.2.2.43
–
>>>Minimum Uplink SIR
M
Uplink SIR
9.2.1.69
–
>>>Maximum Uplink SIR
M
Uplink SIR
9.2.1.69
–
>>>Closed Loop Timing Adjustment Mode
O
9.2.2.3A
–
>>>Maximum Allowed UL Tx Power
M
9.2.1.35
–
>>>Maximum DL TX Power
M
DL Power
9.2.1.21A
–
>>>Minimum DL TX Power
M
DL Power
9.2.1.21A
–
>>>Neighbouring UMTS Cell Information
O
9.2.1.41A
–
>>>Neighbouring GSM Cell Information
O
9.2.1.41C
–
>>>Primary CPICH Power
M
9.2.1.44
–
>>>PC Preamble
M
9.2.2.27a
-
>>>SRB Delay
M
9.2.2.39A
-
>>>Cell GA Additional Shapes
O
9.2.1.5B
YES
ignore
>>>TFCI PC Support Indicator
O
9.2.2.x
YES
ignore
Criticality Diagnostics
O
9.2.1.13
YES
ignore
Range bound
Explanation
MaxnoofRLs
Maximum number of radio links for one UE.
Unaffected parts are omitted
9.2.2.x TFCI PC Support Indicator
The TFCI PC Support Indicator indicates whether the TFCI power control in the DSCH hard split mode can be applied to DL DPCH in the cell or not. TFCI PC Mode 1 means that the only one power offset(TFCI PO[4]) is applied in TFCI power control. TFCI PC Mode 2 means that the cell also supports enhanced DSCH power control and two power offset(TFCI PO and TFCI PO_primary[4]) are applied in TFCI power control.
IE/Group Name
Presence
Range
IE type and reference
Semantics description
TFCI PC Support Indicator
ENUMERATED (TFCI PC Mode 1 Supported, TFCI PC Mode 2 Supported)
Unaffected parts are omitted
====================================================================
5.4.3.2 Impacts on NBAP (TS 25.433)
=========================== TS 25.433 ============================== |
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 more DSCHs on one radio link.]
[TDD – The RL Setup procedure is used for establish one radio link including one or more transport channels. The transport channels can be a mixture of DCHs, DSCHs, and USCHs, including also combinations where one or more transport channel types are not present.] |
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 given in the message.
The Node B shall prioritise resource allocation for the RL(s) to be established according to Annex A.
Transport Channels Handling:
DCH(s):
[TDD – If the DCH Information IE is present, the Node B shall configure the new DCH(s) according to the parameters given in the message.]
If the RADIO LINK SETUP REQUEST message includes a DCH Information IE with multiple DCH Specific Info IEs then, the Node B shall treat the DCHs in the DCH Information IE as a set of co-ordinated DCHs. The Node B shall include these DCHs in the new configuration only if it can include all of them in the new configuration.
[FDD – For DCHs which do not belong to a set of co-ordinated DCHs with the QE-Selector IE set to "selected", the Transport channel BER from that DCH shall be the base for the QE in the UL data frames. If no Transport channel BER is available for the selected DCH the Physical channel BER shall be used for the QE, ref. [16]. If the QE-Selector is set to "non-selected", the Physical channel BER shall be used for the QE in the UL data frames, ref. [16].]
For a set of co-ordinated DCHs the Transport channel BER from the DCH with the QE-Selector IE set to “selected” shall be used for the QE in the UL data frames, ref. [16]. [FDD - If no Transport channel BER is available for the selected DCH the Physical channel BER shall be used for the QE, ref. [16]. If all DCHs have QE-Selector IE set to "non-selected" the Physical channel BER shall be used for the QE, ref. [16]].
The Node B shall use the included UL FP Mode IE for a DCH or a set of co-ordinated DCHs to be added as the FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the configuration.
The Node B shall use the included ToAWS IE for a DCH or a set of co-ordinated DCHs to be added as the Time of Arrival Window Start Point in the user plane for the DCH or the set of co-ordinated DCHs in the configuration.
The Node B shall use the included ToAWE IE for a DCH or a set of co-ordinated DCHs to be added as the Time of Arrival Window End Point in the user plane for the DCH or the set of co-ordinated DCHs in the configuration.
The received Frame Handling Priority IE specified for each Transport Channel should be used when prioritising between different frames in the downlink on the radio interface in congestion situations within the Node B once the new RL(s) has been activated.
[FDD – The Diversity Control Field IE indicates for each RL (except the first RL in the message) whether the Node B shall combine the concerned RL or not. If the Diversity Control Field IE is set to"May", then Node B shall decide for either of the alternatives. If the Diversity Control Field IE is set to "Must", the Node B shall combine the RL with one of the other RL. Diversity combining is applied to Dedicated Transport Channels (DCH), i.e. it is not applied to the DSCHs. When a new RL is to be combined, the Node B shall choose which RL(s) to combine it with. If the Diversity Control Field IE is set to “Must not” , the Node B shall not combine the RL with any other existing RL.]
[FDD – In the RADIO LINK SETUP RESPONSE message the Node B shall indicate with the Diversity Indication IE whether the RL is combined or not. In case of combining, only the Reference RL ID IE shall be included to indicate one of the existing RLs that the concerned RL is combined with. In case of not combining the Node B shall include in the RL SETUP RESPONSE the Binding ID IE and Transport Layer Address IE for the transport bearer to be established for each DCH of this RL.]
[TDD – The Node B shall include in the RADIO LINK SETUP RESPONSE the Binding ID IE and Transport Layer Address IE for the transport bearer to be established for each DCH of this RL.]
In case of coordinated DCH, the Binding ID IE and the Transport Layer Address IE shall be specified for only one of the coordinated DCHs.
DSCH(s):
If the DSCH Information IE is present, the Node B shall configure the new DSCH(s) according to the parameters given in the message.
[FDD – If the RADIO LINK SETUP REQUEST message includes the TFCI2 Bearer Information IE then the Node B shall support the establishment of a transport bearer on which the DSCH TFCI Signaling control frames shall be received. The Node B shall manage the time of arrival of these frames according to the values of ToAWS and ToAWE specified in the IE’s. The Binding ID IE and Transport Layer Address IE for the new bearer to be set up for this purpose shall be returned in the RADIO LINK SETUP RESPONSE message.]
The Node B shall include in the RADIO LINK SETUP RESPONSE the Binding ID IE and Transport Layer Address IE for the transport bearer to be established for each DSCH of this RL.
[TDD – USCH(s)]:
[TDD – If the USCH Information IE is present, the Node B shall configure the new USCH(s) according to the parameters given in the message.]
[TDD – In case the USCH Information IE is present, the Node B shall include in the RADIO LINK SETUP RESPONSE the Binding ID IE and Transport Layer Address IE for the transport bearer to be established for each USCH of this RL.]
Physical Channels Handling:
[FDD – Compressed Mode]:
[FDD – If the RADIO LINK SETUP REQUEST message includes the Transmission Gap Pattern Sequence Information IE, the Node B shall store the information about the Transmission Gap Pattern Sequences to be used in the Compressed Mode Configuration. This Compressed Mode Configuration shall be valid in the Node B until the next Compressed Mode Configuration is configured in the Node B or Node B Communication Context is deleted.]
[FDD – If the Downlink compressed mode method IE in one or more Transmission Gap Pattern Sequence is set to 'SF/2' in the RADIO LINK SETUP REQUEST message, the Node B shall use or not the alternate scrambling code as indicated for each DL Channelisation Code in the Transmission Gap Pattern Sequence Code Information IE.]
[FDD – If the RADIO LINK SETUP REQUEST message includes the Transmission Gap Pattern Sequence Information IE and the Active Pattern Sequence Information IE, the Node B shall use the information to activate the indicated Transmission Gap Pattern Sequence(s) in the new RL.The received CM Configuration Change CFN refers to the latest passed CFN with that value The Node B shall treat the received TGCFN IEs as follows:]
- [FDD - If any received TGCFN IE has the same value as the received CM Configuration Change CFN IE, the Node B shall consider the concerning Transmission Gap Pattern Sequence as activated at that CFN.]
- [FDD - If any received TGCFN IE does not have the same value as the received CM Configuration Change CFN IE but the first CFN after the CM Configuration Change CFN with a value equal to the TGCFN IE has already passed, the Node B shall consider the concerning Transmission Gap Pattern Sequence as activated at that CFN.]
- [FDD - For all other Transmission Gap Pattern Sequences included in the Active Pattern Sequence Information IE, the Node B shall activate each Transmission Gap Pattern Sequence at the first CFN after the CM Configuration Change CFN with a value equal to the TGCFN IE for the Transmission Gap Pattern Sequence.]
[FDD – DL Code Information]:
[FDD – When more than one DL DPDCH are assigned per RL, the segmented physical channel shall be mapped on to DL DPDCHs according to [8]. When p number of DL DPDCHs are assigned to each RL, the first pair of DL Scrambling Code and FDD DL Channelisation Code Number corresponds to "PhCH number 1", the second to “PhCH number 2”, and so on until the pth to "PhCH number p".]
General:
[FDD – If the Propagation Delay IE is included, the Node B may use this information to speed up the detection of L1 synchronisation.]
[FDD – The UL SIR Target IE included in the message shall be used by the Node B as initial UL SIR target for the UL inner loop power control.]
[1.28Mcps TDD – The UL SIR Target IE included in the message shall be used by the Node B as initial UL SIR target for the UL inner loop power control according [19] and [21].]
[FDD – If the received Limited Power Increase IE is set to 'Used', the Node B shall, if supported, use Limited Power Increase according to ref. [10] subclause 5.2.1 for the inner loop DL power control.]
[FDD – If the TFCI Signalling Mode IE within the RADIO LINK SETUP message indicates that there shall be a hard split on the TFCI field but the TFCI2 Bearer Information IE is not included in the message then the Node B shall transmit the TFCI2 field with zero power.]
[FDD - If the TFCI Signalling Mode IE within the RADIO LINK SETUP message indicates that there shall be a hard split on the TFCI and the TFCI2 Bearer Information IE is included in the message then the Node B shall transmit the TFCI2 field with zero power until Synchronization is achieved on the TFCI2 transport bearer and the first valid DSCH TFCI Signalling control frame is received on this bearer (see ref.[24]).]
Radio Link Handling:
[FDD – Transmit Diversity]:
[FDD – When Diversity Mode IE is "STTD", "Closedloop mode1", or "Closedloop mode2", the Node B shall activate/deactivate the Transmit Diversity to each Radio Link in accordance with Transmit Diversity Indication IE]
DL Power Control:
[FDD – The Node B shall start the DL transmission using the initial DL power specified in the message on each DL DPCH of the RL until either UL synchronisation on the Uu is achieved for the RLS or Power Balancing is activated. No inner loop power control or balancing shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref.[10], subclause 5.2.1.2) and the power control procedure (see subclause 8.3.7), but shall always be kept within the maximum and minimum limit specified in the RADIO LINK SETUP REQUEST message. During compressed mode, the PSIR(k) , as described in ref.[10] subclause 5.2.1.3, shall be added to the maximum DL power in slot k.]
[FDD - If the DPC Mode IE is present in the RADIO LINK SETUP REQUEST message, the Node B shall apply the DPC mode indicated in the message, and be prepared that the DPC mode may be changed during the life time of the RL. If the DPC Mode IE is not present in the RADIO LINK SETUP REQUEST message, DPC mode 0 shall be applied (see ref. [10]).]]
[TDD – The Node B shall start the DL transmission using the initial DL power specified in the message on each DL DPCH and on each Time Slot of the RL until the UL synchronisation on the Uu is achieved for the RL. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref.[22], subclause 4.2.3.3), but shall always be kept within the maximum and minimum limit specified in the RL SETUP REQUEST message.]
[TDD – If the [3.84Mcps TDD - DL Time Slot ISCPInfo IE] or [1.28Mcps TDD - DL Timeslot ISCP LCR IE] is present, the Node B shall use the indicated value when deciding the initial DL TX Power for each timeslot as specified in [21], i.e. it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged].
[FDD – If the received Inner Loop DL PC Status IE is set to "Active", the Node B shall activate the inner loop DL power control for all RLs. If Inner Loop DL PC Status IE is set to "Inactive", the Node B shall deactivate the inner loop DL power control for all RLs according to ref. [10]]
General:
[FDD – If the RADIO LINK SETUP REQUEST message includes the SSDT Cell Identity IE and the S-Field Length E, the Node B shall activate SSDT, if supported, using the SSDT Cell Identity IE and SSDT Cell Identity Length IE.]
[FDD – Irrespective of SSDT activation, the Node B shall include in the RADIO LINK SETUP RESPONSE message an indication concerning the capability to support SSDT on this RL. Only if the RADIO LINK SETUP REQUEST message requested SSDT activation and the RADIO LINK SETUP RESPONSE message indicates that the SSDT capability is supported for this RL, SSDT is activated in the Node B.]
[FDD - If the RADIO LINK SETUP REQUEST message includes the SSDT Cell Identity for EDSCHPC IE, the Node B shall activate enhanced DSCH power control, if supported, using the SSDT Cell Identity for EDSCHPC IE and SSDT Cell Identity Length IE as well as Enhanced DSCH PC IE in accordance with ref. [10] subclause 5.2.2. If the RADIO LINK SETUP REQUEST message includes both SSDT Cell Identity IE and SSDT Cell Identity for EDSCHPC IE, then the Node B shall ignore the value in SSDT Cell Identity for EDSCHPC IE. If the enhanced DSCH power control is activated and the TFCI power control in DSCH hard split mode is supported, the primary/secondary status determination in the enhanced DSCH power control is also applied to the TFCI power control in DSCH hard split mode.]
[FDD – Radio Link Set Handling]:
[FDD – The First RLS Indicator IE indicates if the concerning RL shall be considered part of the first RLS established towards this UE. The First RLS Indicator IE shall be used by the Node B together with the value of the DL TPC pattern 01 count IE which the Node B has received in the Cell Setup procedure, to determine the initial TPC pattern in the DL of the concerning RL and all RLs which are part of the same RLS, as described in [10], section 5.1.2.2.1.2.]
[FDD – For each RL not having a common generation of the TPC commands in the DL with another RL, the Node B shall assign the RL Set ID IE included in the RADIO LINK SETUP RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication context.]
[FDD – For all RLs having a common generation of the TPC commands in the DL with another RL, the Node B shall assign the RL Set ID IE included in the RADIO LINK SETUP RESPONSE message the same value. This value shall uniquely identify the RL Set within the Node B Communication context.]
[FDD – The UL out-of-sync algorithm defined in [10] shall for each of the established RL Set(s) use the maximum value of the parameters N_OUTSYNC_IND and T_RLFAILURE, and the minimum value of the parameters N_INSYNC_IND, that are configured in the cells supporting the radio links of the RL Set]
Response Message:
If the RLs are successfully established, the Node B shall start reception on the new RL(s) and respond with a RADIO LINK SETUP RESPONSE message.
After sending of the RADIO LINK SETUP RESPONSE message the Node B shall continuously attempt to obtain UL synchronisation on the Uu and start reception on the new RL. [FDD – The Node B shall start transmission on the new RL after synchronisation is achieved in the DL user plane as specified in [16].] [TDD – The Node B shall start transmission on the new RL immediately as specified in [16].]
Unaffected parts are omitted |
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 Parameter Update procedure
If the RADIO INTERFACE PARAMETER UPDATE control frame contains a valid TPC power offset value, the Node B shall apply the newly provided TPC PO in DL. If the frame contains a valid DPC mode value, the Node B shall apply the newly provided value in DL power control. If the frame contains valid TFCI PO_primary parameter and cell is decided to be primary, the Node B shall apply the newly provided value in DL TFCI power control. If the frame contains valid TFCI PO parameter, the Node B shall apply the newly provided value in DL TFCI power control. The new values shall be applied as soon as possible in case no valid CFN is included or from the indicated CFN.
Unaffected parts are omitted |
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: Indicates if the 4th byte (bit 5) of the control frame payload contains a valid DPC mode (1) or not (0);
Bit 3: Indicates if the 5th byte (bit 0-7) of the control frame payload contains a valid TFCI PO (1) or not (0);
Bit 4: Indicates if the 6th byte (bit 0-7) of the control frame payload contains a valid TFCI PO_primary (1) or not (0);
Bit 35-15: Set to (0): reserved in this user plane revision. Any indicated flags shall be ignored by the receiver.
Field length: 16 bits. |
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}.
Granularity: 0.25 dB.
Field length: 7 bits.
6.3.3.9.x TFCI Power Offset for primary cell (TFCI PO_primary)
Description: Power offset to be applied in the DL between the DPDCH information and the TFCI bits on the DPCCH when cell is decided to be primary. The primary status shall be determined as specified in [4].
Value range: {0-31.75 dB}.
Granularity: 0.25 dB.
Field length: 7 bits.
====================================================================
Table 1: Place where Change request is given in order to refer the new procedure
3G TS
CR
Title
Remarks
25.423
CR582
RNSAP changes for TFCI power control in DSCH hard split mode
25.427
CR082
DCH FP changes for TFCI power control in DSCH hard split mode
25.433
CR626
NBAP changes for TFCI power control in DSCH hard split mode |
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 does not cause any problem to network operation. By using TFCI PC Support Indicator IE in the RADIO LINK SETUP RESPONSE, RADIO LINK SETUP FAILURE, RADIO LINK ADDITION RESPONSE and RADIO LINK ADDITION FAILURE messages, SRNC knows which cell in the active set is using flexible TFCI power offset.
Consequently, the TFCI power control procedure in the DSCH hard split mode is backward compatible with Release 99 and REL-4.
===================== End of the WG 3 part ============================= |
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, the power level of the DSCH is based on the PO1, which is the time-invariant TFCI power offset relative to the DPDCH power in Release 99 and Rel’4. Since the TFCI power offset may vary in time with the proposed scheme, clarification as regard to the DSCH power offset is required. If the power level of the DSCH is based on the flexible TFCI power, the flexible DSCH power offset should be used for the DSCH power control as in Release 99 and Rel’4. Thus, there is no backward compatibility problem regarding DSCH power offset.
5.5.2 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 does not cause any problem to network operation.
5.5.3 Backward compatibility issues in UE
It is clear that Release 99 (or Rel’ 4)- UEs operate in Rel’ 5 Node Bs and Rel’ 5-UEs operate with Release 99 (or Rel’ 4)-Node Bs where the proposed schemes are not available. Therefore, there is no backward compatibility problem.
Appendix (Informative)
• IFHT Algorithm for supporting the flexible length
When the number of information bits is less than 6 ( k < 6 ), there are some alternatives to decode the received data efficiently. In fact, it doesn’t matter if we do not use the following structure for decoding. The following structure only provides an example of efficient decoding scheme.
When the number of information bits < 6, only the first IFHT is performed. But, this structure is so loose in terms of the number of operation because the first IFHT with 32x32 size is always fully performed for each k < 6 case. Actually, it is desirable to use IFHT with size 2kx2k for each k. That is, it is desirable to use IFHT with the flexible size. Therefore, the flexible IFHT can be used as shown in Fig A1.
Fig A1. Flexible IFHT Structure
Fig. A1 describes the overall structure of the flexible IFHT. Generally, 2kx2k IFHT performance consists of k stages. For example, 32x32 IFHT consists of 5 stages. Hence, by using this property, the size of IFHT can be varied adaptively. That is, if 2 stages out of 5 stages are performed, then 4x4 IFHT is effectively calculated, and if 3 stages out of 5 stages are performed, then 8x8 IFHT is effectively calculated, and so on. This is called “Nested Property”. Fig A.1 is a well-designed structure based on this “Nested Property”. But this structure requires some new circuits in each stage, instead of the well-known “Butterfly Logic”, because “Butterfly Logic” is not suited for “Nested Property”. The new circuit suited for “Nested Property” is as shown in Fig A.2.
Fig A2. Circuit of Stage
• Implementation of mapping rule
In this section, we describe the method to implement the mapping rule. Actually, instead of the formula, it may be very useful to use a mask for presenting the transmission position that is calculated according to the position calculation method described above. That is, we define as follows:
• “0” means that the coded symbol of TFCI for DSCH is holding, not transmitted, and that of TFCI for DCH is transmitted.
• “1” means that the coded symbol of TFCI for DCH is holding, not transmitted, and that of TFCI for DSCH is transmitted.
By using such presentation, mask patterns for all case are as shown in the following table A1.
TFCIDCH : TFCIDSCH
Mask for mapping position
1 : 9
00000001000000010000000100000001
2 : 8
00001000100001000100001000100001
3 : 7
00100100010010010010010001001001
4 : 6
01001010010100101001010010100101
5 : 5
01010101010101010101010101010101
6 : 4
10110101101011010110101101011010
7 : 3
11011011101101101101101110110110
8 : 2
11110111011110111011110111011110
9 : 1
11111110111111101111111011111110
Table A1. Masks for mapping position
We see an example to transmit the coded symbol. Before this, we define the i-th output coded symbol after puncturing for DCH as d1,i and the k-th outputted coded symbol after puncturing for DSCH as d2,k.
In 3 : 7 case, the first bit in mask for mapping rule is 0. Hence, the first coded symbol d2,0 of TFCI for DSCH is holding, not transmitted, and the coded symbol d1,0 of TFCI for DCH is transmitted. The second bit in mask for mapping rule is 0. Hence, the first coded symbol d2,0 of TFCI for DSCH which is not transmitted is holding again, not transmitted, and the coded symbol d1,1 of TFCI for DCH is transmitted. The third bit in mask for mapping rule is 1. Hence, the coded symbol d1,2 of TFCI for DCH is held, not transmitted, and the coded symbol d2,0 of TFCI for DSCH is transmitted. And so on.
According to this operation, the output symbol after symbol mapping is as following Fig A3.
d1,0
d1,1
d2,0
d1,2
d1,3
d2,1
d1,4
d1,5
d2,2
d1,6
d1,7
d2,3
d1,8
d1,9
d1,10
d2,4
d1,11
d1,12
d2,5
d1,13
d1,14
d2,6
d1,15
d1,16
d2,7
d1,17
d1,18
d2,8
d1,19
d1,20
d1,21
d2,9
Fig A3. Example of mapping rule in 3 : 7 case |
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.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TS 25.102: "UE Radio transmission and reception (TDD)".
[3] 3GPP TS 25.105: "BS Radio transmission and reception (TDD)".
[4] 3GPP TS 25.123: "RF parameters in support of RRM (TDD)".
[5] 3GPP TS 25.142: "Base Station conformance testing (TDD)".
[6] 3GPP TS 25.113: "Base Station EMC".
[7] 3GPP TR 25.942: "RF System scenarios".
[8] 3GPP TS 25.922: "Radio Resource Management Strategies".
[9] 3GPP TS 25.331: "Radio Resource Control (RRC) Protocol Specification".
[10] 3GPP TR 25.928: "1.28 Mcps UTRA TDD Physical Layer".
[11] 3GPP TS 25.214: "Physical layer procedures (FDD)".
[12] 3GPP TS 45.010: "Radio subsystem synchronization".
[13] 3GPP TS 25.225: "Physical layer; Measurements (TDD)".
[14] 3GPP TS 25.215: "Physical layer; Measurements (FDD)".
[15] 3GPP TS 25.306: "UE Radio Access capabilities".
[16] ITU-R recommendation SM.329: "Unwanted emissions in the spurious domain ".
[17] 3GPP RAN WG4 meeting #6, tdoc R4-990393: " FDD UE Blocking Requirement".
[18] 3GPP RAN WG4 meeting#7, tdoc R4-990457: " Blocking characteristics, Spurious response, Intermodulation characteristics for UE TDD".
[19] 3GPP RAN WG4 meeting#6, tdoc R4-990431: " Revised FDD UE Blocking Requirement". |
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.304, the UE shall perform the Cell Re-selection Evaluation process. |
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 the measurements is at least TmeasureNTDD/2 (see table 4.1).
If the UE has evaluated in Nserv successive measurements that the serving cell does not fulfill the cell selection criterion S the UE shall initiate the measurements of all neighbour cells indicated in the measurement control system information, regardless of the measurement rules currently limiting UE measurement activities.
If the UE has not found any new suitable cell based the on searches and measurements of the neighbour cells indicated in the measurement control system information for [TBD] s, the UE shall initiate cell selection procedures for the selected PLMN as defined in TS 25.304 [8]. |
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 measurements, which are taken so that the time difference between the measurements is at least TmeasureNTDD/2.
The filtering shall be such that the UE shall be capable of evaluating that an intra-frequency cell has become better than the serving cell within TevaluateNTDD (see table 4.1), from the moment the intra-frequency cell became at least [2]dB better ranked than the current serving cell, provided that Treselection timer is set to zero and PCCPCH RSCP is used as measurement quantity for cell reselection.
If parameter Treselection has value different from zero, the UE shall evaluate an intra-frequency cell better than the serving cell during the Treselection time, before the UE shall reselect the new cell. |
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 UE is camped on. The UE shall filter PCCPCH RSCP measurements of each measured inter-frequency cell using at least 2 measurements, which are taken so that the time difference between the measurements is at least TmeasureNTDD/2.
The filtering of PCCPCH RSCP shall be such that the UE shall be capable of evaluating that an already detected inter-frequency cell has become better ranked than the serving cell within (Ncarrier-1) * TevaluateNTDD from the moment the inter-frequency cell became at least [3]dB better than the current serving cell provided that Treselection timer is set to zero. For non-detected inter-frequency cells, the filtering shall be such that the UE shall be capable of evaluating that inter-frequency cell has become better ranked than the serving cell within 30s from the moment the inter-frequency cell became at least [3]dB better than the current serving cell provided that Treselection timer is set to zero.
If Treselection timer has a value different from zero, the UE shall evaluate an inter-frequency cell better than the serving cell during the Treselection time, before the UE shall reselect the new cell. |
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 * TmeasureTDD (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 3.84 Mcps TDD cells. The maximum number of carriers is 3.The UE shall filter PCCPCH RSCP measurements of each measured high chip rate TDD cell using at least 2 measurements, which are taken so that the time difference between the measurements is at least TmeasureTDD/2.
The filtering of PCCPCH RSCP shall be such that the UE shall be capable of evaluating that a high chip rate TDD cell has become better ranked than the serving cell within NTDDcarrier * TevaluateTDD from the moment the inter-frequency cell became at least [3] better ranked than the current serving cell provided that Treselection timer is set to zero. For non-detected inter-frequency cells, the filtering shall be such that the UE shall be capable of evaluating that inter-frequency cell has become better ranked than the serving cell within 30s from the moment the inter-frequency cell became at least [3]dB better than the current serving cell provided that Treselection timer is set to zero. |
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 UE shall filter CPICH RSCP measurements of each measured inter-frequency cell using at least 2 measurements. The measurement samples for each cell shall be as far as possible uniformly distributed over the averaging period.
CPICH RSCP is used as measurement quantity for cell reselection, the filtering shall be such that the UE shall be capable of evaluating that an already detected inter-frequency cell has become better ranked than the serving cell within NFDDcarrier * TevaluateFDD from the moment the inter-frequency cell became at least [5]dB better than the current serving cell provided that Treselection timer is set to zero. For non-detected inter-frequency cells, the filtering shall be such that the UE shall be capable of evaluating that inter-frequency cell has become better ranked than the serving cell within 30s from the moment the inter-frequency cell became at least [5]dB better than the current serving cell provided that Treselection timer is set to zero.
The ranking of the cells shall be made according to the cell reselection criteria specified in TS 25.304. The use of mapping functions is indicated in the broadcast. |
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 maintain a running average of 4 measurements for each cell. The measurement samples for each cell shall be as far as possible uniformly distributed over the averaging period.
The UE shall attempt to verify the BSIC for each of the 4 best ranked GSM BCCH carriers (the best ranked according to the cell reselection criteria defined in TS 25.304 [8]) at least every 30 seconds if GSM cells are measured according to the measurement rules. If a change of BSIC is detected for one GSM cell then that GSM BCCH carrier shall be treated as a new GSM neighbour cell.
If the UE detects a BSIC, which is not indicated in the measurement control system information, the UE shall not consider that GSM BCCH carrier in cell reselection. The UE also shall not consider the GSM BCCH carrier in cell reselection, if the UE can not demodulate the BSIC of that GSM BCCH carrier. |
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-frequency cell for paging reception. The interruption time shall not exceed [50]ms.
At inter-frequency and inter-RAT 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 for paging reception of the target inter-frequency cell. The interruption time must not exceed T_REP + [50] ms. T_REP is the longest repetition period for the system information required to be read by the UE to camp on the cell.
These requirements assume sufficient radio conditions, so that decoding of system information can be made without errors.
Table 4.1: TmeasureNTDD, TevaluateNTDD, TmeasureTDD, TevaluateTDD, TmeasureFDD, TevaluateFDD and TmeasureGSM
DRX cycle length [s]
Nserv [number of successive measurements]
TmeasureNTDD [s] (number of DRX cycles)
TevaluateNTDD [s] (number of DRX cycles)
TmeasureTDD [s] (number of DRX cycles)
TevaluateTDD [s] (number of DRX cycles)
0.08
4
0.64
(8 DRX cycles)
2.56
(32 DRX cycles)
0.64
(8 DRX cycles)
2.56
(32 DRX cycles)
0.16
4
0.64 (4)
2.56 (16)
0.64 (4)
2.56 (16)
0.32
4
1.28 (4)
5.12 (16)
1.28 (4)
5.12 (16)
0.64
4
1.28 (2)
5.12 (8)
1.28 (2)
5.12 (8)
1.28
2
1.28 (1)
6.4 (5)
1.28 (1)
6.4 (5)
2.56
2
2.56 (1)
7.68 (3)
2.56 (1)
7.68 (3)
5.12
1
5.12 (1)
10.24 (2)
5.12 (1)
10.24 (2)
Table 4.1 (prolongation)
DRX cycle length [s]
Nserv [number of successive measurements]
TmeasureFDD [s] (number of DRX cycles)
TevaluateFDD [s] (number of DRX cycles)
TmeasureGSM [s] (number of DRX cycles)
0.08
4
0.64
(8DRX cycles)
2.56
(32 DRX cycles)
2.56
(32 DRX cycles)
0.16
4
0.64 (4)
2.56 (16)
2.56 (16)
0.32
4
1.28 (4)
5.12 (16)
5.12 (16)
0.64
4
1.28 (2)
5.12 (8)
5.12 (8)
1.28
2
1.28 (1)
6.4 (5)
6.4 (5)
2.56
2
2.56 (1)
7.68 (3)
7.68 (3)
5.12
1
5.12 (1)
10.24 (2)
10.24 (2)
In idle mode, UE shall support DRX cycles lengths 0.64, 1.28, 2.56 and 5.12 s. |
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 frequencies besides the serving cell.
- the inter-frequency cells can be located on up to [x] carriers.
In addition the UE shall be able to monitor 32 GSM carriers if GSM is supported by the UE. UE measurement activity is controlled by measurement rules defined in in TS 25.304 [8], allowing the UE to limit its measurement activity if certain conditions are fulfilled. |
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. The UE measurements and which radio links the UE shall use is controlled by UTRAN with RRC signaling. For the handover preparation the UE receives from the UTRAN a list of cells (e.g. 1.28 Mcps TDD, or GSM). Which the UE shall monitor (see 'monitored set' in 3GPP TS 25.331 [9]) in its idle timeslots.
At the beginning of the measurement process the UE shall find synchronization to the cell to measure using the synchronization channel (DwPCH). This is described under 'cell search' in 3GPP TR 25.928 [10] ' if the monitored cell is a 1.28 Mcps TDD cell.For a TDD cell to monitor after this procedure the exact timing of the midamble of the P-CCPCH is known and the measurements can be performed. Depending on the UE implementation and if timing information about the cell to monitor is available, the UE may perform the measurements on the P-CCPCH directly without prior DwPCH synchronization. |
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 within Dhandover seconds from the end of the last TTI containing the RRC command.
If the access is delayed to an indicated activation time later than Dhandover seconds from the end of the last TTI containing the RRC command, the UE shall be ready to start the transmission of the new uplink DPCH at the designated activation time.
where:
Dhandover equals the RRC procedure delay defined in TS 25.331 [9] Section 13.5.2 plus the interruption time stated in section 4.2.1.2.2. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.1.2.2 Interruption time | The interruption time i.e. the time between the last TTI containing a transport block on the old DPCH and the time the UE starts transmission of the new uplink DPCCH, shall be less than the value in table 4.2. There is different requirement on the interruption time depending on if the cell is known or not.
A cell shall be regarded as known by the UE if it has been measured during the last 5 seconds or a dedicated connection existed between the UE and the cell during the last 5 seconds.
Table 4.2: TDD/ TDD handover – interruption time
cell in the handover command message
Maximum delay [ms]
Known Cell
Cell
1
[40]
[ 350]
The interruption time includes the time that can elapse till the appearance of the channel required for the synchronisation. And the the time that can elapse till the appearance of the DwPTS in which the new uplink SYNC1 shall be transmitted ,or in case of high chip rate TDD the new uplink DPCH, shall be transmitted , which can be up to one frame (10ms).
The requirement in Table 4.2 for the unknown cell shall apply if the signal quality of the unknown cell is good enough for successful synchronisation with one attempt.
NOTE: One synchronisation attempt can consist of coherent averaging using several frames. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.2 1.28 Mcps TDD/FDD Handover | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.2.1 Introduction | The purpose of 1.28 Mcps TDD/FDD handover is to change the mode between 1.28 Mcps TDD and FDD.
The handover procedure is initiated from UTRAN with a handover command message. The handover procedure causes the UE to change its frequency. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.2.2 Requirements | These requirements shall apply only to 1.28 McpsTDD/FDD UE.
The requirements do not apply if FDD macro-diversity is used. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.2.2.1 Handover delay | Procedure delay for all procedures, that can command a hard handover, are specified in 3GPP TS 25.331 [9] section 11.5.
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 be ready to start the transmission of the new uplink DPCCH within Dhandover s from the end of the last TTI containing the RRC command.
If the access is delayed to an indicated activation time later than Dhandover seconds from the end of the last TTI containing the RRC command, the UE shall be ready to start the transmission of the new uplink DPCCH at the designated activation time.
where:
Dhandover equals the RRC procedure delay defined in TS 25.331 [9] Section 13.5.2 plus the interruption time stated in section 5.2.2.2 plus the time required for any kind of baseband or RF reconfiguration due to the change of the UTRAN mode. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.2.2.2 Interruption time | The interruption time, i.e. the time between the end of the last TTI containing a transport block on the old DPCH and the time the UE starts transmission of the new uplink DPCCH, shall be less than the value in table 4.3 There is different requirement on the interruption time depending on if the cell is known or not.
The definition of known cell can be found in section 4.2.1.2.2.
Table 4.3: 1.28 Mcps TDD/FDD interruption time
cell in the handover command message
Maximum delay [ms]
Known cell
Unknown cell
1
[100 ]
[ 350]
The interruption time includes the interruption uncertainty when changing the timing from the old NTDD to the new FDD cell, which can be up to one frame (10ms) and the time required for measuring the downlink DPCCH channel as stated in TS 25.214 section 4.3.1.2 into account.
The requirement in Table 4.2.2.1 for the unknown cell shall apply if the signal quality of the unknown cell is good enough for successful synchronisation with one attempt. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.3 1.28 Mcps TDD/GSM Handover | In the early days of UMTS deployment it can be anticipated that the service area will not be as contiguous and extensive as existing second generation systems. It is also anticipated that UMTS network will be an overlay on the 2nd generation network and utilise the latter, in the minimum case, as a fall back to ensure continuity of service and maintain a good QoS as perceived by the user. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.3.1 Introduction | The purpose of inter-RAT handover from UTRAN 1.28 Mcps TDD to GSM is to transfer a connection between the UE and UTRAN 1.28 Mcps TDD to GSM. The handover procedure is initiated from UTRAN with a RRC message (HANDOVER FROM UTRAN COMMAND). The procedure is described in TS 25.331 section 8.3.7. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.3.2 Requirements | These requirements only apply to UE supporting GSM. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.3.2.1 Handover delay | When the UE receives a RRC HANDOVER FROM UTRAN COMMAND with the activation time "now" or earlier than the value in Table 4.4 from the end of the last TTI containing the RRC command, the UE shall be ready to transmit (as specified in 3GPP 45.010 [12]) on the new channel the new RAT within the value in Table 4.4 from the last TTI containing the RRC command, If the access is delayed to an indicated activation time later than the value in Table 4.4 from the end of the last TTI containing the RRC command, the UE shall be ready to transmit (as specified in 3GPP TS 45.010 [12]) on the channel of the new RAT at the designated activation time.
The UE shall process the RRC procedures for the RRC HANDOVER FROM UTRAN COMMAND within 50 ms. If the activation time is used, it corresponds to the CFN of the UTRAN channel.
Table 4.4: 1.28 Mcps TDD/GSM handover –handover delay
UE synchronisation status
handover delay [ms]
The UE has synchronised to the GSM cell before the HANDOVER FROM UTRAN COMMAND is received
90
The UE has not synchronised to the GSM cell before the HANDOVER FROM UTRAN COMMAND is received
190 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.3.2.2 Interruption time | The interruption time, i.e. the time between the end of last TTI containing a transport block on the old channel and the time the UE is ready to transmit on the new channel, shall be less than the value in Table 4.5. The requirement in Table 4.5 for the case, that UE is not synchronised to the GSM cell before the HANDOVER FROM UTRAN COMMAND is received, is valid when the signal quality of the GSM cell is good enough for successful synchronisation with one attempt.
Table 4.5: TDD/GSM handover - interruption time
Synchronisation status
Interruption time [ms]
The UE has synchronised to the GSM cell before the HANDOVER FROM UTRAN COMMAND is received
40
The UE has not synchronised to the GSM cell before the HANDOVER FROM UTRAN COMMAND is received
140 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.4 Cell Re-selection in CELL_FACH | Note: Data in this section needs to be revised.
Cell re-selection, especially inter-frequency (TDD or FDD) and inter-system (GSM), in Cell_FACH state is still under discussion in WG4., due to possible loss of FACH data during reselection process. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.4.1 Introduction | Common with TS 25.123 [3]. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.4.2 Requirements | Common with TS 25.123 [3]. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.4.2.1 Cell re-selection delay | Common with TS 25.123 [3]. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.4.2.1.1 All cells in the neighbour list belong to the same frequency | Common with TS 25.123 [3].
NOTE: The test parameter of this section will be found in B.2.4.1 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.4.2.1.2 The cells in the neighbour list belong to different frequencies | NOTE: This requirement should be reconsidered based on RAN2 decisions. the test of parameter of this section will be found in B.2.4.2.
The cell re-selection delay in CELL_FACH state shall be less than [x] seconds when the cells in the neighbour list belong to less than [x] frequencies.
NOTE: The test parameter of this section will be found in B.2.4. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.5 Cell Re-selection in CELL_PCH | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.5.1 Introduction | Common with re-selection in idle mode. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.5.2 Requirements | Same requirements as for cell re-selection in idle mode apply. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.6 Cell Re-selection in URA_PCH | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.6.1 Introduction | Common with re-selection in idle mode. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.2.6.2 Requirements | Same requirements as for cell re-selection in idle mode. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.3 Dynamic Channel Allocation | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.3.1 Introduction | Common with 25.123 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.3.2 Implementation Requirements | Common with 25.123 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.3.3 Number of timeslots to be measured | The number of down link timeslots to be measured in the UE is broadcasted on the BCH in each cell. In general, the number of downlink timeslots in question will be less than [6], but in worst case the UE shall be capable to measure [6] downlink timeslots. In case of “simple UE [FFS] timeslots shall at least be measured. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.3.3.1 Explanation | In NTDD there are 7 common timeslots and 3 special timeslots, in the 7 common timeslots Ts1 is always allocated to UL. So the number of downlink timeslots in question will be less than 6,in the worst case the UE shall be capable to measure 6 timeslots. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.3.4 Measurement reporting delay | In order to save battery lifetime, in idle mode no measurements are performed for DCA. ISCP measurements are started at all establishments. Taking into account that the measured interference of the timeslots is preferable averaged over [FFS] frames, the measurement reporting delay in connecting phase shall not exceed [FFS] milliseconds. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.4 Timing characterisitics | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.4.1 Timing Advance (TA) Requirements | For 1.28 Mcps TDD the timing advance in the UE is adjusted by means of uplink synchronisation. For the random access procedure the node B commands the UE to adjust its synchronisation shift by means of signalling the received position of the UpPTS in the FPACH. During the connection the node B measures the timing in the uplink and transmits a SS (Synchronisation Shift) command to the UE at least once per sub-frame.
These SS commands determined whether the UE synchronisation shift is either left unchanged, or adjusted 1 step up or 1 step down. The step size of the SS adjustment is (k/8)Tc where k (=1,2, …,8) is signalled by higher layer signalling. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.4.1.1 Uplink synchronization control requirements for UE for 1.28 Mcps TDD option | Uplink synchronization control is the ability of the UE transmitter to adjust its TX timing in accordance with one or more SS commands received in the downlink. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.4.1.1.1 Uplink synchronization control steps | The SS step is the change in UE transmission timing in response to a single SS command, SS_cmd, received by the UE. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.4.1.1.1.1 Minimum requirement | The UE transmitter shall have the capability of changing the transmission timing with a step size of 1/8, 2/8, 3/8, …, 1 chip according to the value of SS, n=(1,2,…,14) time slot after the SS_cmd arrived (closed loop). For the open loop any step being a multiple of 1/8 chip has to be allowed.
a) The minimum transmission timing step SS,min due to closed loop uplink synchronization control shall be within the range shown in Table 4.6.
b) In case uplink synchronization control implies to perform a bigger step than the minimum step the UE shall perform the a multiple number of minimum steps m. Within the implementation grid of the applicable timing steps of the UE the step being closest to the required step should be executed.
Table 4.6: Uplink synchronisation control range
SS_ cmd
Uplink synchronisation control range for minimum step
1/8 chip step size
Lower
Upper
Up
1/9 chip – 0.1 ppm
1/7 chip + 0.1 ppm
Down
1/9 chip – 0.1 ppm
1/7 chip + 0.1 ppm |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.4.1.1.2 Timing Advance (TADV) for 1.28 Mcps TDD | This measurement refers to TS 25.225 subsection 5.1.14. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.4.1.1.2.1 Accuracy requirements | Table 4.7
Parameter
Unit
Accuracy
Conditions
Range [chips]
Timing Advance
chips period
+/- 0.125
0, …, 255.875 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.4.1.1.2.2 Range/mapping | The reporting range for Timing Advance is from 0 ... 255.875 chips.
In table 4.8 the mapping of the measured quantity is defined. The signalling range may be larger than the guaranteed accuracy range.
Table 4.8
Reported value
Measured quantity value
Unit
TIMING_ADVANCE_0000
Timing Advance < 0
chip
TIMING_ADVANCE_0001
0 Timing Advance < 0.125
chip
TIMING_ADVANCE_0002
0.125 Timing Advance < 0.25
chip
…
…
…
TIMING_ADVANCE_1024
127.875 Timing Advance < 128
chip
…
…
…
TIMING_ADVANCE_2045
255.625 Timing Advance < 255.75
chip
TIMING_ADVANCE_2046
255.75 Timing Advance < 255.875
chip
TIMING_ADVANCE_2047
255.875 RX Timing Advance
chip
NOTE: This measurement can be used for timing advance (synchronisation shift) calculation for uplink synchronisation or location services. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.4.1.1.2.2.1 Explanation difference | In 3.84 Mcps TDD timing advance control is carried out by means of higher layer signalling: The network transmits a highly protected timing advance command containing the total timing advance and the UE executes it. Consequently the network can be sure of the timing advance applied by the UE.
In 1.28 Mcps TDD the network transmits SS symbols giving commands like a step up or down or no change at all in every sub-frame. These SS symbols are not protected by a special channel coding including CRC etc. Consequently, the network cannot know whether is commands have been executed or not. Thus, the network cannot obtain the timing advance of the UE by tracking its SS commands. Instead, the UE has to measure its timing advance and transmit it to the network by means of the timing advance measurement. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.4.2 Cell synchronisation accuracy | Common with 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.4.2.0 Explanation | Considering intersystem compatibility , cell synchronisaton accuracy is the same as 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.4.2.1 Definition | (void) |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.4.2.2 Minimum Requirements | (void) |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.5 UE Measurements Procedures | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.5.1 Measurements in CELL_DCH State | The monitor mechanism in this state is ffs for 1.28 chip rate TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.5.1.0 Explanation | This section contains requirements on the UE regarding measurement reporting in CELL_DCH State. Because of the difference between the frame structure of 1.28 Mcps and that of 3.84 Mcps, the idle time slots which can be used for monitoring will be different, hence the detail of this subclause would be different compared with 3.84 Mcps. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.5.1.1 Introduction | (void) |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.5.1.2 Requirements | (void) |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.5.2 Measurements in CELL_FACH State | Commons with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.5.2.0 Explanation | The section describes the requirements on the UE regarding measurement reporting in CELL_FACH state. The requirements independent with bandwidth and chip rate should be the same. Hence the contents need no modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.5.2.1 Introduction | (void) |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.5.2.2 Requirements | (void) |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6 Measurements Performance Requirements | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1 Measurements Performance for UE | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1 Performance for UE Measurements in Downlink (RX) | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.1 P-CCPCH RSCP (1.28 Mcps TDD) | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.1.1 Explanation | The result of this measurement is not energy and it is independent with the bandwidth, so there should not be modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.2 CPICH Measurements (FDD) | Common with 3.84 Mcps TDD. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.