hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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... |
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 shal... |
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 re... |
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.
... |
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 ... |
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 th... |
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 HANDO... |
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 ... |
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 [... |
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 t... |
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 transmissi... |
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... |
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 netwo... |
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... |
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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.