Scheduling Request is triggered when UE is in uplink sync with eNodeB and doesn’t have any
PUSCH/PUCCH resource allocated for transmission of the new control plane or user plane data.
UE uses the SR-Configuration received in RRC connection setup or RRC reconfiguration request to determine the next Scheduling Request (SR) available opportunity (computes the frame and sub-frame).
SchedulingRequestConfig ::= CHOICE {
release NULL,
setup SEQUENCE {
sr-PUCCH-ResourceIndex INTEGER (0..2047),
sr-ConfigIndex INTEGER (0..157),
dsr-TransMax ENUMERATED {
n4, n8, n16, n32, n64, spare3, spare2, spare1}
}
}
Based on the ConfigIndex, UE-specific periodicity and subframe offset is determined as below.
SR configIndex (I)
|
SRperiodicity (ms)
|
SR subframe offset
|
0 – 4
|
5
|
I
|
5 – 14
|
10
|
I-5
|
15 – 34
|
20
|
I-15
|
35 – 74
|
40
|
I-35
|
75 – 154
|
80
|
I-75
|
155 – 156
|
2
|
I-155
|
157
|
1
|
I-157
|
SR indication is transmitted based on the configured sr-PUCCHResourceIndex in the SFN and sub-frame number which satisfies the below condition.
((SFN*10+subframe)-SRoffset) mod SRperiodicity = 0
Nevertheless SR will NOT be transmitted if:
- SR opportunity falls in measurement gap or
- SR-Prohibit status timer is running or
- DL PDCCH with UL resources is received
تحويل كودإخفاء محول الأكواد الإبتساماتإخفاء