24.3.1 V2X Uplink Communication / UE in RRC_Connected on an E-UTRAN cell / Utilisation of the UL SPS resources configured by eNB / Transmission
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
24.3.1.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state and configured to provide SPS assistance information }
ensure that {
when { UE prefers a SPS configuration}
then { the UE sends sps-AssistanceInformation in the message UEAssistanceInformation }
}
(2)
with { UE in E-UTRAN RRC CONNECTED state on a cell }
ensure that {
when { UE receives an RRCConnectionReconfiguration message containing sps-Config-v1430 to setup SPS configuration}
then { UE transmits data using the configured SPS resources }
}
(3)
with { UE in E-UTRAN RRC CONNECTED state on a cell }
ensure that {
when { UE receives an RRCConnectionReconfiguration message containing sps-Config-v1430 to release SPS configuration}
then { UE stops data transmission using the configured SPS resources }
}
24.3.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.6.10.2 and 5.3.10.5, TS 23.285, clause 4.4.5.2.
[TS 36.331, clause 5.6.10.2]
A UE capable of providing SPS assistance information in RRC_CONNECTED may initiate the procedure in several cases including upon being configured to provide SPS assistance information and upon change of SPS assistance information.
…
Upon initiating the procedure, the UE shall:
…
1> if configured to provide SPS assistance information:
2> if the UE did not transmit a UEAssistanceInformation message with sps-AssistanceInformation since it was configured to provide SPS assistance information; or
2> if the current SPS assistance information is different from the one indicated in the last transmission of the UEAssistanceInformation message:
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.6.10.3;
[TS 36.331, clause 5.3.10.5]
The UE shall:
1> reconfigure the semi-persistent scheduling in accordance with the received sps-Config;
[TS 23.285, clause 4.4.5.2]
The V2X messages can be delivered via Non-GBR bearer as well as GBR bearer.
The following standardized QCI values defined in TS 23.203 [12] can be used:
– QCI 3 and QCI 79 can be used for the unicast delivery of V2X messages;
24.3.1.3 Test description
24.3.1.3.1 Pre-test conditions
System Simulator:
– Cell 1
UE:
– E-UTRAN UE supporting V2X communication Via Uu.
Preamble:
– The UE is in state Loopback Activated (state 4) according to [18] using UE test loop mode A.
– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18] except for those listed in Table 24.3.1.3.3-4.
– The loop back size is set in such a way that one RLC SDU in DL shall result in 1 RLC SDU’s in UL of same size.
24.3.1.3.2 Test procedure sequence
Table 24.3.1.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
Trigger the UE to send UEAssistanceInformation message to request UL SPS grant for V2X communication over LTE-Uu from eNB. (Note) |
– |
– |
||
2 |
Check: Does the UE send a UEAssistanceInformation message within the next 20s? |
–> |
UEAssistanceInformation |
1 |
P |
3 |
The SS transmits an RRCConnectionReconfiguration message containing a sps-Config-v1430 |
<– |
RRCConnectionReconfiguration |
– |
– |
4 |
The UE transmits an RRCConnectionReconfigurationComplete message. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
5 |
The SS transmits a DL MAC PDU containing 10 RLC SDU’s on UM DRB. |
<– |
MAC PDU |
– |
– |
6 |
The UE transmits a Scheduling Request, indicating that loop back PDUs are ready for transmission in UL RLC |
–> |
(SR) |
||
7 |
The SS transmits an UL Grant using UE’s ul-SPS-V-RNTI in SF-Num ‘4’, NDI=0, ‘UL SPS configuration index’ set to ’000’B (i.e. sps-ConfigIndex-r14=1), allowing the UE to transmit one loop back PDU per MAC PDU. |
<– |
(UL SPS Grant) |
||
8 |
Check: Does the UE transmit a MAC PDU in SF-Num ‘8’ as per grant in step 7? |
–> |
MAC PDU |
2 |
P |
9 |
The SS transmits a HARQ ACK |
<– |
HARQ ACK |
– |
– |
10 |
Check: Does the UE transmit a MAC PDU in SF-Num ‘108(FDD)/107(TDD)’ as per grant in step 7? |
–> |
MAC PDU |
2 |
P |
11 |
The SS transmits a HARQ ACK |
<– |
HARQ ACK |
– |
– |
12 |
The SS transmits an UL Grant using UE’s ul-SPS-V-RNTI in SF-Num ‘124’, NDI=0, ‘UL SPS configuration index’ set to ’001’B (i.e. sps-ConfigIndex-r14=2), allowing the UE to transmit one loop back PDU per MAC PDU. |
<– |
(UL SPS Grant) |
||
13 |
Check: Does the UE transmit a MAC PDU in SF-Num ‘128’ as per grant in step 12? |
–> |
MAC PDU |
2 |
P |
14 |
The SS transmits a HARQ ACK |
<– |
HARQ ACK |
– |
– |
15 |
Check: Does the UE transmit a MAC PDU in SF-Num ‘178(FDD)/177(TDD)’ as per grant in step 12? |
–> |
MAC PDU |
2 |
P |
16 |
The SS transmits a HARQ ACK |
<– |
HARQ ACK |
– |
– |
17 |
Check: Does the UE transmit a MAC PDU in SF-Num ‘208(FDD)/207(TDD)’ as per grant in step 7? |
–> |
MAC PDU |
2 |
P |
18 |
The SS transmits a HARQ ACK |
<– |
HARQ ACK |
– |
– |
19 |
SS Transmits RRCConnectionReconfiguration to disable SPS-ConfigurationUL. |
<– |
– |
– |
– |
20 |
The UE transmits RRCConnectionReconfigurationComplete |
–> |
– |
– |
– |
21 |
Check: Does the UE transmit a MAC PDU in SF-Num ‘228 (FDD)/227(TDD)’ as per grant in step 12? |
–> |
MAC PDU |
3 |
F |
22 |
The SS transmits an OPEN UE TEST LOOP message to exit the UE test loop mode. |
<– |
OPEN UE TEST LOOP |
– |
– |
23 |
The UE transmits an OPEN UE TEST LOOP COMPLETE message. |
–> |
OPEN UE TEST LOOP COMPLETE |
– |
– |
24 |
The SS transmits a DEACTIVATE TEST MODE message to de-activate UE radio bearer test mode procedure. |
<– |
DEACTIVATE TEST MODE |
– |
– |
25 |
The UE transmits a DEACTIVATE TEST MODE COMPLETE message. |
–> |
DEACTIVATE TEST MODE COMPLETE |
– |
– |
Note: This indication may be triggered with the AT command(+CSPSAIR) with interface ="0". |
24.3.1.3.3 Specific message contents
Table 24.3.1.3.3-1: UEAssistanceInformation (Step 2)
Derivation path: 36.508 Table 4.6.1-26, conditions Normal |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
UEAssistanceInformation-r11 ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE{ |
||||
UEAssistanceInformation-r11-IEs SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
sps-AssistanceInformation-r14 SEQUENCE { |
||||
trafficPatternInfoListSL-r14 |
Not checked |
|||
trafficPatternInfoListUL-r14 SEQUENCE (SIZE (1..maxTrafficPattern-r14)) OF SEQUENCE{ |
||||
trafficPeriodicity-r14 |
Not checked |
|||
timingOffset-r14 |
Not checked |
|||
logicalChannelIdentityUL-r14 |
Not checked |
|||
messageSize-r14 |
Not checked |
|||
} |
||||
} |
||||
DelayBudgetReport-r14 |
Not Present |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
Table 24.3.1.3.3-2: RRCConnectionReconfiguration. RadioResourceConfigDedicated (Step 3)
Derivation path: 36.508 table 4.6.3-16 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RadioResourceConfigDedicated::= SEQUENCE { |
||||
sps-Config-v1430 ::= SEQUENCE { |
||||
ul-SPS-V-RNTI-r14 |
‘1034’H |
|||
sps-ConfigUL-ToAddModList-r14 SEQUENCE (SIZE (1..maxConfigSPS-r14)) SEQUENCE { |
||||
SPS-ConfigUL[1] ::= CHOICE { |
||||
setup SEQUENCE { |
||||
semiPersistSchedIntervalUL |
sf40 |
40 Subframe |
||
implicitReleaseAfter |
e4 |
|||
p0-Persistent |
Not Present |
|||
twoIntervalConfig |
Not Present |
|||
sps-ConfigIndex-r14 |
1 |
|||
semiPersistSchedIntervalUL-v1430 |
sf100 |
100 Subframe |
||
} |
||||
} |
||||
SPS-ConfigUL[2] ::= CHOICE { |
||||
setup SEQUENCE { |
||||
semiPersistSchedIntervalUL |
sf40 |
40 Subframe |
||
implicitReleaseAfter |
e4 |
|||
p0-Persistent |
Not Present |
|||
twoIntervalConfig |
Not Present |
|||
sps-ConfigIndex-r14 |
2 |
|||
semiPersistSchedIntervalUL-v1430 |
sf50 |
50 Subframe |
||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 24.3.1.3.3-3: RRCConnectionReconfiguration. RadioResourceConfigDedicated (step 19 of table 24.3.1.3.2-1)
Derivation path: 36.508 table 4.6.3-16 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RadioResourceConfigDedicated::= SEQUENCE { |
||||
sps-Config-v1430 ::= SEQUENCE { |
||||
ul-SPS-V-RNTI-r14 |
‘1034’H |
|||
sps-ConfigUL-ToReleaseList-r14 SEQUENCE (SIZE (1..maxConfigSPS-r14)) OF SEQUENCE { |
||||
SPS-ConfigIndex-r14[1] |
1 |
|||
SPS-ConfigIndex-r14[2] |
2 |
|||
} |
||||
} |
||||
} |
Table 24.3.1.3.3-4: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (preamble)
Derivation path: 36.508 Table 4.7.3-3 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
EPS QoS |
According to reference dedicated EPS bearer context #7 – in TS 36.508 table 6.6.2-1A |