hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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. |
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. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.3 Timeslot ISCP | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.3.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.4 UTRA carrier RSSI | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.4.1 Explanation | This measurement relies on the signal-detecting algorithm which independent with the bandwidth and chip rate, so it needs no modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.5 GSM carrier RSSI | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.5.1 Explanation | This measurement relies on GSM, so it needs no modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.6 SIR | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.6.1 Explanation | This measurement mainly used to meet the requirement of service performance which independent with the bandwidth and chip rate, so there should be no modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.7 Transport channel BLER | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.7.1 Explanation | This measurement is mainly used to meet the requirement of service performance which independent with the bandwidth and chip rate, so there should be no modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.8 SFN-SFN observed time difference | The measurement period for CELL_DCH state can be found in section 4.5. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.8.1 Accuracy requirements | Table 4.9: SFN-SFN observed time difference accuracy
Parameter
Unit
Accuracy
Conditions
Io [dBm]
SFN-SFN observed time difference
Chip
+/-0,5 for type 1 but +/- 0.125 for type 2
-94...-50 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.8.2 Range/mapping | The reporting range for SFN-SFN observed time difference type 1 is from 0 ... 3276800 chip.
In table 4.10 mapping of the measured quantity is defined. Signalling range may be larger than the guaranteed accuracy range.
Table 4.10
Reported value
Measured quantity value
Unit
T1_SFN-SFN_TIME _0000000
0 SFN-SFN observed t... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.8.3 Explanation difference | In 1.28 Mcps TDD there are 12800chips per frame while in 3.84 Mcps TDD there are 38400chips. According to this chip number difference, the observed time difference range in type 1 should be changed correspondingly.
There are 3 kind of special time slot (DwPTS, UpPTS and GP) in 1.28 Mcps TDD frame structure (see section... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.9 Observed time difference to GSM cell | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.9.1 Explanation | For different systems, the measurement that is used to realize the compatibility should be the same. So it is independent with bandwidth and chip rate and there should be no modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.10 UE GPS Timing of Cell Frames for LCS | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.10.1 Explanation | The GPS timing of cell frames should be the same for different systems having LCS, so it needs no modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.11 SFN-CFN observed time difference | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.11.1 Explanation | For the measurement used for the interwork between cells, which belong to the same system or different systems, should be the same and independent with bandwidth and chip rate. So it needs no modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.2 Performance for UE Measurements in Uplink (TX) | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.2.1 UE transmitted power | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.2.1.1 Explanation | The UE transmitted power is represented by energy density and it is independent with the bandwidth, so there should not be modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2 Measurements Performance for UTRAN | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1 Performance for UTRAN Measurements in Uplink (RX) | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.1 RSCP | Common with 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.2 Timeslot ISCP | Common with 3.84 Mcps TDD option |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.3 RSSI | Common with 3.84 Mcps TDD option |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.4 SIR | Common with 3.84 Mcps TDD option |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.5 Transport Channel BER | Common with 3.84 Mcps TDD option |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.6 RX Timing Deviation | The definition of RX Timing Deviation here is common with 3.84 Mcps but only accuracy and range are different between two TDD mode. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.6.1 Accuracy requirements | Table 4.12
Parameter
Unit
Accuracy
Conditions
Range [chips]
RX Timing Deviation
chips period
+/- 0.125
-128, …, 128 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.6.2 Range/mapping | The reporting range for RX Timing Deviation is from-128 ... 128 chips.
In table 4.13 mapping of the measured quantity is defined. Signaling range may be larger than the guaranteed accuracy range.
Table 4.13
Reported value
Measured quantity value
Unit
RX_TIME_DEV_0001
RX Timing Deviation < –128,000
chip
RX_TIME_DEV_0002... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.6.3 Explanation difference | In 3.84 Mcps TDD the ‘RX Timing Deviation’ measurement is only needed to report to the higher layer for timing advance calculation or location services. It does not need to measure this value continuously.
While in 1.28 Mcps TDD this measurement is not only reported to higher layer, but also severed as a physical signa... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.7 SYNC-UL Timing Deviation for 1.28 Mcps | This measurement refers to TS 25.225 [13]subsection 5.2.8.1. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.7.1 Accuracy requirements | Table 4.14
Parameter
Unit
Accuracy
Conditions
Range [chips]
SYNC-UL Timing Deviation
chips period
+/- 0.125
0, …, 255.875 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.7.2 Range/mapping | The reporting range for SYNC-UL Timing Deviation is from 0 ... 255.875 chips.
In table 4.15 the mapping of the measured quantity is defined. Signaling range may be larger than the guaranteed accuracy range.
Table 4.15
Reported value
Measured quantity value
Unit
SYNC_UL_TIME_DEV_0000
SYNC-UL Timing Deviation < 0
chip
SY... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.7.3 Explanation difference | In 1.28 Mcps TDD there is a two step approach for the random access procedure. In the first step the UpPCH is transmitted by the UE. The node B received the UpPCH and responds with the FPACH which contains the received position of the SYNC-UL sequence. This allows the UE to adjust its timing advance for the PRACH in or... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.2 Performance for UTRAN Measurements in Downlink (TX) | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.2.1 Transmitted carrier power | Common with 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.2.1.1 Explanation | These parameters in this section are not energy ,so they are independent with bandwidth . There need not to any change compare with the 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.2.2 Transmitted code power | Common with 3.84 Mcps TDD option.
4.6.2.2.2.1 explanation
These parameters in this section are not energy ,so they are independent with bandwidth. There need not to any change compare with the 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.7 FPACH physical layer information field definition (1.28 Mcps TDD) | 1.28 Mcps TDD introduces the FPACH (Forward Physical Access CHannel) which carries physical layer information. Two of these information fields are the ‘received starting position of the UpPCH’ (Uplink Pilot CHannel) and the ‘transmit power level command for the RACH message’. Both information fields are directly (recei... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.