That means for example that the reported value of TIMING_ADVANCE_01 gives the measured quantity value between 2 and 3 Ts. It states that the reported value is in resolution of 2Ts upto a value of 4096Ts. Second question is about granularity of the reported value from the table 10.3.1-1. But this is not possible according to other references where it is calculated that max distance is around 100 km.Ģ. First question is how is it possible to have Tadv = 49232 Ts? That would mean that maximum distance Dmax = C * Ts / 2 = 240.390 km between UE and eNodeB. There is a reference to 36.133 chapter 10.3.1 where Table 10.3.1-1 describes the mapping of the reported value to the measured quantity value.ġ. Hi, my questions are related to the values of Timing Advance Type 1 and Type 2 reported by eNodeB according to 36.455 chapter 9.2.5 E-CID Measurement Result. Value of Timing Advance Command value and start/restart timeAlignmentTimer Uplink resources but UE doesn’t have valid PUCCH resources for SchedulingRequest etc…After the reception of RAR, the UE shall ignore the received TimingĪdvance Command value and shouldn’t restart the timeAlignmentTimerĪ Timing Advance Command MAC CE is received, the UE shall apply the received Is already running: This could be in situations like UE is requesting for Procedure in connected mode and timeAlignmentTimer Timing Advance Command is received in MAC RAR as part of contention based Random Access Received in RAR and starts/restart the timeAlignmentTimer The reception of RAR, the UE shall apply the Timing Advance Command value Timing Advance Command is received in MAC RAR as part of non-contention based RandomĪccess procedure (ex: PDCCH Order): After If the contention is not resolved/successful, then the UE stops timeAlignmentTimer, else, the UE Procedure etc…After the reception of RAR, the UE shall apply the Timing AdvanceĬommand value received in RAR and start timeAlignmentTimer. Mode), Initial access from RRC_IDLE, during RRC Connection Re-establishment Is not already running: This case may arise in situations like, timeAlignmentTimer has expired (connected Timing Advance Command is received in MAC RAR but timeAlignmentTimer
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |