在5G（NR）网络中当终端需要进行上行数据传输时，其需要向网络侧的gNB申请资源和上行资源的调度；其原理与LTE网络相同，其详细内容如下：
1.SR(调度请求)用途
调度请求SR(Scheduling Request)是物理层一种特殊消息，用于UE向网络请求发送UL调度授权(DCI Format 0_0 /0_1) ，以便UE能够在PUSC信道上传输数据。换句话说，SR是从UE到网络的上行物理层消息，表示“我有些数据要发送给你。能给我一些资源，让我发送数据好吗”？
2. SR(调度请求)发送
UE怎么发送SR消息？UE通过PUCCH (或通过PUSCH中的UCI) 发送。不是所有PUCCH格式都可以携带SR，有些PUCCH格式可以携带，有些则不能。UE使用某种PUCCH格式根据情况发送SR(具体请参阅PUCCH格式页)。
SR在物理层的另一个含义是，你不能用RRC/NAS ASN解码器来解码。
许多eNB或测试设备可以让你将其日志转换成 wireshark 文件；但是除非设备供应商提供具体的 wireshark 分隔符，否则很可能你不会在 wireshark 中看到SR消息。通常这些设备供应商提供自己的日志查看器这种低层消息。
3.SR(调度消息)控制 、
谁来控制SR过程呢？ 尽管SR消息是一种物理层消息，但它是由MAC层来进行控制的（与许多其他物理层信道是由MAC层控制相同 )，SR进程(何时发送)也是由MAC层控制的(详见38.3215.4.4)，其过程如下图所示。
4.RRC层的相关参数
SchedulingRequestConfig ::= SEQUENCE { schedulingRequestToAddModList SEQUENCE (SIZE 1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestToAddMod OPTIONAL,
schedulingRequestToReleaseList SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestId OPTIONAL -- Need N}
SchedulingRequestToAddMod ::= SEQUENCE {schedulingRequestId SchedulingRequestId, 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.
sr-ProhibitTimer : Timer for SR transmission in ms on PUCCH
sr-TransMax : Maximum number of SR transmissions
LogicalChannelConfig ::= SEQUENCE {
ul-SpecificParameters SEQUENCE {
priority INTEGER (1..16),
prioritisedBitRate ENUMERATED {kBps0, kBps8, kBps16, kBps32, kBps64, kBps128, kBps256,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},
allowedServingCells
SEQUENCE (SIZE (1..maxNrofServingCells-1)) OF ServCellIndex OPTIONAL,
allowedSCS-List SEQUENCE (SIZE (1..maxSCSs)) OF SubcarrierSpacing
maxPUSCH-Duration ENUMERATED {ms0p02, ms0p04, ms0p0625, ms0p125, ms0p25, ms0p5, spare2, spare1}
configuredGrantType1Allowed ENUMERATED {true} OPTIONAL,
logicalChannelGroup INTEGER (0..maxLCG-ID) OPTIONAL, -- Need R
schedulingRequestID SchedulingRequestId OPTIONAL, -- Need R
logicalChannelSR-Mask BOOLEAN,
logicalChannelSR-DelayTimerApplied BOOLEAN, ...,
bitRateQueryProhibitTimer ENUMERATED { s0, s0dot4, s0dot8, s1dot6, s3, s6, s12,s30} OPTIONAL -- Need R } OPTIONAL, -- Cond UL...}
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
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.
https://www./article-156041-1.html | 
