NR - Slot Configuration

 


        NR中的上下行时隙配置取决于tdd-UL-DL-ConfigurationCommontdd-UL-DL-ConfigurationDedicated以及SFI。

      tdd-UL-DL-ConfigurationCommon为小区级别配置,tdd-UL-DL-ConfigurationDedicated为UE专属配置,SFI是通过DCI来指示上下行时隙格式变化。

一 tdd-UL-DL-ConfigurationCommon

         tdd-UL-DL-ConfigurationCommon的配置如下,一般存在于SIB1信息中。   

TDD-UL-DL-ConfigCommon ::=          SEQUENCE{

referenceSubcarrierSpacing          SubcarrierSpacing,

pattern1           TDD-UL-DL-Pattern,

pattern2          TDD-UL-DL-Pattern       OPTIONAL,-- Need R

    ...

}

 

TDD-UL-DL-Pattern ::=               SEQUENCE{

    dl-UL-TransmissionPeriodicity      ENUMERATED {ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10},

    nrofDownlinkSlots                   INTEGER(0..maxNrofSlots),

    nrofDownlinkSymbols             INTEGER (0..maxNrofSymbols-1),

    nrofUplinkSlots                        INTEGER (0..maxNrofSlots),

    nrofUplinkSymbols                  INTEGER (0..maxNrofSymbols-1),

    ...,

    [[

    dl-UL-TransmissionPeriodicity-v1530    ENUMERATED {ms3, ms4}                                               OPTIONAL-- Need R

    ]]

}

        以参考子载波间隔为30KHz,周期为0.5ms,结合示例可以理解TDD-UL-DL-Pattern中的各项代表的含义。Slot中符号数减去nrofDownlinkSymbols与 nrofUplinkSymbols之和,剩余的符号称之为Flexible Symbol

 

u

子载波间隔

Normal  CP Slot长度

0

15KHz

1ms

1

30KHz

0.5ms

2

60KHz

0.25ms

3

120KHz

0.125ms

 

周期

适用子载波间隔

Slot

0.625ms

120KHz

5

1.25

60KHz/120KHz

5/10

2.5

30KHz/60KHz/120KHz

5/10/20

        对于部分非整数ms的周期配置中,对于参考子载波间隔有要求,保证周期内是整数个Slot。

        从上面的配置中可以看到,patter1和pattern2的配置都一样,可以分别配置两种周期,但是周期之和(单位为ms)必须能被20整数。对于pattern2是可选配置。

        需要注意的是,实际BWP中的时隙格式需要根据BWP的子载波间隔进行转换,参考子载波间隔必须小于等于BWP的子载波间隔。

 

二 tdd-UL-DL-ConfigurationDedicated

      tdd-UL-DL-ConfigurationDedicated是UE专属配置,不过这个配置只能修改tdd-UL-DL-ConfigurationCommon配置中的Flexible Symbol。Flesible Symbol即由周期内除去配置的上下行Slot/上下行符号数后的符号。

 

TDD-UL-DL-ConfigDedicated ::=       SEQUENCE{

    slotSpecificConfigurationsToAddModList      SEQUENCE(SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotConfig       OPTIONAL,-- Need N

    slotSpecificConfigurationsToreleaseList     SEQUENCE(SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotIndex        OPTIONAL,-- Need N

    ...

}

 

TDD-UL-DL-SlotConfig ::=            SEQUENCE{

    slotIndex                           TDD-UL-DL-SlotIndex,

    symbols                            CHOICE {

        allDownlink                        NULL,

        allUplink                            NULL,

        explicit                           SEQUENCE {

     nrofDownlinkSymbols     INTEGER (1..maxNrofSymbols-1)               

     nrofUplinkSymbols         INTEGER(1..maxNrofSymbols-1)

        }

    }

}

TDD-UL-DL-SlotIndex ::=             INTEGER(0..maxNrofSlots-1)

 

        tdd-UL-DL-ConfigurationDedicated中配置的是Slot符号指示数组,基本元素为TDD-UL-DL-SlotConfig,通过其中的slotIndex确定Slot位置,可以将该Slot指示为全下行符号,全上行符号,或者上行符号数/下行符号数。

       tdd-UL-DL-ConfigurationDedicated不能将tdd-UL-DL-ConfigurationCommon指示的下行符号变更为上行符号,上行符号变更为下行符号。

 

    tdd-UL-DL-ConfigurationCommon和tdd-UL-DL-ConfigurationDedicated配置确定后的上下行配置后,上下行符号的使用比较明确。

  • 上行符号上不能接收PDCCH/PDSCH/CSI-RS
  • 下行符号上不能发送PUSCH/PUCCH/PRACH/SRS
  • Higher layers不能在同一个Flexible符号上既配置有发送又配置有接收,例如RRC配置的一些周期性接收和周期性发送
  • SSB符号位置不期望被配置成上行符号,如果PUSCH/PUCCH/PRACH符号与SSB任一符号重叠,则不能发送PUSCH/PUCCH/PRACH;SSB符号位置也不能发送SRS
  • PRACH Occasion,即配置为发送PRACH的符号位置不能配置为下行符号,包括PRACH符号前的Ngap符号,如果PDSCH/PDCCH/CSI-RS与其任一符号重叠,则不能接收PDSCH/PDCCH/CSI-RS

 

        Flexible 符号上调度,比较灵活,DCI调度决定了在该符号位置是下行接收还是发送。

 

    对于TDD,higher layers配置的PDSCH/CSI-RS在Flexible符号上,此时如果有DCI format 0-0/0-1/1-0/1-1/2-3调度的PUSCH/PUCCH/PRACH/SRS发送符号有在Flexible符号上,那么不配置PDSCH/CSI-RS接收;否则,可以配置PDSCH/CSI-RS接收。

 

    对于TDD,higher layers配置的PUSCH/PUCCH/PRACH/SRS发送符号在Flexible集合内,如果接收到DCI format 1-0/1-1/0-1指示的PDSCH/CSI-RS接收,在发送符号满足时间间隔要求的前提下,不发送PUSCH/PUCCH/PRACH/SRS。

        对于SFI改变上下行时隙/符号配置,后面再进行学习总结。欢迎关注公众号“自由之路66”!

 


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

### NR RAR Window in 5G NR Protocol Specifications In the context of 5G New Radio (NR), Random Access Response (RAR) window plays a crucial role during the random access procedure, which is essential for establishing initial connections or recovering from radio link failures. The RAR message contains information necessary for UE to continue with connection establishment procedures. The duration of the RAR window depends on system configuration parameters such as subcarrier spacing and slot length[^1]. Specifically, it starts immediately after transmitting Msg1 (preamble sequence). UEs must monitor PDCCH channels carrying RA-RNTI within this predefined time interval following preamble transmission to receive corresponding RAR messages. For normal CP configurations under different numerologies supported by 5G NR: - With μ=0 (15 kHz SCS): RAR window spans over 8 slots. - For μ=1 (30 kHz SCS): This reduces to 4 slots due to shorter slot durations. - When using higher numerology like μ=2 (60 kHz SCS): Only 2 slots are allocated for monitoring potential responses. Implementation Details Concerning NR RAR Windows Include Ensuring Timely Monitoring And Decoding Of Downlink Control Information (DCI). ```python def calculate_rar_window_slots(subcarrier_spacing): """ Calculate number of slots covered by RAR window based on given subcarrier spacing index mu Args: subcarrier_spacing (int): Numerology parameter indicating subcarrier spacing used Returns: int: Number of slots constituting the RAR window period """ mapping = {0: 8, 1: 4, 2: 2} return mapping.get(subcarrier_spacing, "Invalid Subcarrier Spacing Index") # Example usage demonstrating calculation for various SC spacings print(f"μ=0 results in {calculate_rar_window_slots(0)} slots.") print(f"μ=1 results in {calculate_rar_window_slots(1)} slots.") print(f"μ=2 results in {calculate_rar_window_slots(2)} slots.") ``` --related questions-- 1. What factors influence variability in RAR window timing across diverse deployment scenarios? 2. How does the design choice of subcarrier spacing impact overall latency experienced during random access attempts? 3. Can you explain how contention resolution works post-reception of an RAR message? 4. In what ways do network operators configure settings related to the RAR process to optimize performance metrics?
评论 4
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值