在5G(NR)網(wǎng)絡(luò)中當(dāng)終端需要進(jìn)行上行數(shù)據(jù)傳輸時(shí),其需要向網(wǎng)絡(luò)側(cè)的gNB申請(qǐng)資源和上行資源的調(diào)度;其原理與LTE網(wǎng)絡(luò)相同,其詳細(xì)內(nèi)容如下: 整理:kangguoying20200723
1.SR(調(diào)度請(qǐng)求)用途 整理:kangguoying20200723
調(diào)度請(qǐng)求SR(Scheduling Request)是物理層一種特殊消息,用于UE向網(wǎng)絡(luò)請(qǐng)求發(fā)送UL調(diào)度授權(quán)(DCI Format 0_0 /0_1) ,以便UE能夠在PUSC信道上傳輸數(shù)據(jù)。 換句話說(shuō),SR是從UE到網(wǎng)絡(luò)的上行物理層消息,表示“我有些數(shù)據(jù)要發(fā)送給你。能給我一些資源,讓我發(fā)送數(shù)據(jù)好嗎”? 整理:kangguoying20200723
2. SR(調(diào)度請(qǐng)求)發(fā)送 整理:kangguoying20200723
UE怎么發(fā)送SR消息?UE通過(guò)PUCCH (或通過(guò)PUSCH中的UCI) 發(fā)送。不是所有PUCCH格式都可以攜帶SR,有些PUCCH格式可以攜帶,有些則不能。 UE使用某種PUCCH格式根據(jù)情況發(fā)送SR(具體請(qǐng)參閱PUCCH格式頁(yè))。
SR在物理層的另一個(gè)含義是,你不能用RRC/NAS ASN解碼器來(lái)解碼。 整理:kangguoying20200723
許多eNB或測(cè)試設(shè)備可以讓你將其日志轉(zhuǎn)換成 wireshark 文件;但是除非設(shè)備供應(yīng)商提供具體的 wireshark 分隔符,否則很可能你不會(huì)在 wireshark 中看到SR消息。 通常這些設(shè)備供應(yīng)商提供自己的日志查看器這種低層消息。 整理:kangguoying20200723
3.SR(調(diào)度消息)控制 整理:kangguoying20200723
誰(shuí)來(lái)控制SR過(guò)程呢? 盡管SR消息是一種物理層消息,但它是由MAC層來(lái)進(jìn)行控制的(與許多其他物理層信道是由MAC層控制相同 ),SR進(jìn)程(何時(shí)發(fā)送)也是由MAC層控制的(詳見(jiàn)38.3215.4.4),其過(guò)程如下圖所示。 整理:kangguoying20200723
4.RRC層的相關(guān)參數(shù)
SchedulingRequestConfig ::= SEQUENCE { 整理:kangguoying20200723
schedulingRequestToAddModList SEQUENCE (SIZE 1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestToAddMod OPTIONAL, 整理:kangguoying20200723
schedulingRequestToReleaseList SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestId OPTIONAL -- Need N} 整理:kangguoying20200723
SchedulingRequestToAddMod ::= SEQUENCE { 整理:kangguoying20200723
schedulingRequestId SchedulingRequestId, 整理:kangguoying20200723
sr-ProhibitTimer ENUMERATED {ms1, ms2, ms4, ms8, ms16, ms32, ms64, ms128}
sr-TransMax ENUMERATED {n4, n8, n16, n32, n64, spare3, spare2, spare1}}
schedulingRequestId : Used to modify a SR configuration and to indicate, in LogicalChannelConfig, the SR configuration to which a logical channel is mapped and to indicate, in SchedulingRequestresourceConfig, the SR configuration for which a scheduling request resource is used. 整理:kangguoying20200723 整理:kangguoying20200723
sr-ProhibitTimer : Timer for SR transmission in ms on PUCCH
sr-TransMax : Maximum number of SR transmissions
LogicalChannelConfig ::= SEQUENCE { 整理:kangguoying20200723
ul-SpecificParameters SEQUENCE {
priority INTEGER (1..16), 整理:kangguoying20200723
prioritisedBitRate ENUMERATED {kBps0, kBps8, kBps16, kBps32, kBps64, kBps128, 整理:kangguoying20200723kBps256,kBps512, kBps1024, kBps2048, kBps4096, kBps8192, kBps16384, kBps32768, kBps65536, infinity},
bucketSizeDuration ENUMERATED {ms5, ms10, ms20, ms50, ms100, ms150, ms300, ms500, ms1000, spare7, spare6, spare5, spare4, spare3,spare2, spare1}, 整理:kangguoying20200723
allowedServingCells 整理:kangguoying20200723
SEQUENCE (SIZE (1..maxNrofServingCells-1)) OF ServCellIndex OPTIONAL,
allowedSCS-List SEQUENCE (SIZE (1..maxSCSs)) OF SubcarrierSpacing 整理:kangguoying20200723
maxPUSCH-Duration ENUMERATED {ms0p02, ms0p04, ms0p0625, ms0p125, ms0p25, ms0p5, spare2, spare1}
configuredGrantType1Allowed ENUMERATED {true} OPTIONAL, 整理:kangguoying20200723
logicalChannelGroup INTEGER (0..maxLCG-ID) OPTIONAL, -- Need R
schedulingRequestID SchedulingRequestId OPTIONAL, -- Need R 整理:kangguoying20200723
logicalChannelSR-Mask BOOLEAN, 整理:kangguoying20200723
logicalChannelSR-DelayTimerApplied BOOLEAN, ...,
bitRateQueryProhibitTimer ENUMERATED { s0, s0dot4, s0dot8, s1dot6, s3, s6, s12,s30} OPTIONAL -- Need R } OPTIONAL, -- Cond UL...} 整理:kangguoying20200723
logicalChannelSR-Mask : Controls SR triggering when a configured uplink grant of type1 or type2 is configured. true indicates that SR masking is configured for this logical channel 整理:kangguoying20200723
logicalChannelSR-DelayTimerApplied : Indicates whether to apply the delay timer for SR transmission for this logical channel. Set to false if logicalChannelSR-DelayTimer is not included in BSR-Config.
原文來(lái)自:[url]http://www.sharetechnote.com/[/url] 整理:kangguoying20200723