13.2.3 PC5 unicast / Link modification
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
13.2.3.1 Test Purpose (TP)
(1)
with { UE having set up a V2X PDU session over PC5}
ensure that {
when { UE receives a DIRECT LINK MODIFICATION REQUEST to add a QoS flow to be used on an added unicast SL-DRB }
then { UE can communicate using the newly added QoS flow on added SL-DRB }
}
(2)
with { UE having set up a V2X PDU session over PC5}
ensure that {
when { UE receives a DIRECT LINK MODIFICATION REQUEST to modify a QoS flow associated with the SL-DRB}
then { UE can communicate on the SL-DRB using the newly modified QoS }
}
(3)
with { UE having set up a V2X PDU session over PC5}
ensure that {
when { UE receives a DIRECT LINK MODIFICATION REQUEST to delete a QoS flow and associated SL-DRB is released}
then { UE releases the SL-DRB and its associated QoS flow and sends the complete message}
}
13.2.3.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.587, subclause 6.1.2.3.2, 6.1.2.3.3. Unless otherwise stated these are Rel-16 requirements.
[TS 24.587, subclause 6.1.2.3.2]
The initiating UE shall meet the following pre-conditions before initiating this procedure for adding a new V2X service to the existing PC5 unicast link:
a) there is a PC5 unicast link between the initiating UE and the target UE; and
b) the pair of application layer IDs and the network layer protocol of this PC5 unicast link are identical to those required by the application layer in the initiating UE for this V2X service.
c) the security policy corresponding to the V2X service identifier (e.g. ITS-AID of the new V2X service) is aligned with the security policy of the existing PC5 unicast link.
After receiving the service data or request from the upper layers, the initiating UE shall perform the PC5 QoS flow match as apecified in clause 6.1.2.13. If there is no matched PC5 QoS flow, the initiating UE shall derive the PC5 QoS parameters and assign the PQFI(s) for the PC5 QoS flows(s) to be established as specified in clause 6.1.2.12.
If the PC5 unicast link modification procedure is to add new PC5 QoS flow(s) to the existing PC5 unicast link, the initiating UE shall create a DIRECT LINK MODIFICATION REQUEST message. In this message, initiating UE:
a) shall include the PQFI(s) and the corresponding PC5 QoS parameters, including the V2X service identifier(s); and
b) shall include the link modification operation code set to "add new PC5 QoS flow(s) to the existing PC5 unicast link ".
If the PC5 unicast link modification procedure is to modify the PC5 QoS parameters for existing PC5 QoS flow(s) in the existing PC5 unicast link, the initiating UE shall create a DIRECT LINK MODIFICATION REQUEST message. In this message, the initiating UE:
a) shall include the PQFI(s) and the corresponding PC5 QoS parameters, including the V2X service identifier(s); and
b) shall include the link modification operation code set to "modify PC5 QoS parameters of the existing PC5 QoS flow(s)".
If the PC5 unicast link modification procedure is to associate new V2X service(s) with existing PC5 QoS flow(s), the initiating UE shall create a DIRECT LINK MODIFICATION REQUEST message. In this message, the initiating UE:
a) shall include the PQFI(s) and the corresponding PC5 QoS parameters, including the V2X service identifier(s); and
b) shall include the link modification operation code set to "associate new V2X service(s) with existing PC5 QoS flow(s)".
If the PC5 unicast link modification procedure is to remove the associated V2X service(s) from existing PC5 QoS flow(s), the initiating UE shall create a DIRECT LINK MODIFICATION REQUEST message. In this message, the initiating UE:
a) shall include the PQFI(s) and the corresponding PC5 QoS parameters including the V2X service identifier(s); and
b) shall include the link modification operation code set to "remove V2X service(s) from existing PC5 QoS flow(s)".
If the PC5 unicast link modification procedure is to remove any PC5 QoS flow(s) from the existing PC5 unicast link, the initiating UE shall create a DIRECT LINK MODIFICATION REQUEST message. In this message, the initiating UE:
a) shall include the PQFI(s); and
b) shall include the link modification operation code set to "remove existing PC5 QoS flow(s) from the existing PC5 unicast link".
After the DIRECT LINK MODIFICATION REQUEST message is generated, the initiating UE shall pass this message to the lower layers for transmission along with the initiating UE’s layer-2 ID for unicast communication and the target UE’s layer-2 ID for unicast communication, and start timer T5001. The UE shall not send a new DIRECT LINK MODIFICATION REQUEST message to the same target UE while timer T5001 is running.
Figure 6.1.2.3.2: PC5 unicast link modification procedure
[TS 24.587, subclause 6.1.2.3.3]
If the DIRECT LINK MODIFICATION REQUEST message is accepted, the target UE shall respond with the DIRECT LINK MODIFICATION ACCEPT message.
If the DIRECT LINK MODIFICATION REQUEST message is to add a new V2X service, add new PC5 QoS flow(s) or modify any existing PC5 QoS flow(s) in the PC5 unicast link, the target UE shall include in the DIRECT LINK MODIFICATION ACCEPT message:
a) the PQFI(s), the corresponding PC5 QoS parameters and the V2X service identifier(s) that the target UE accepts.
If the DIRECT LINK MODIFICATION REQUEST message is to remove an existing V2X service from the PC5 unicast link, the target UE shall delete the V2X service identifier received in the DIRECT LINK MODIFICATION REQUEST message and the corresponding PQFI(s) and PC5 QoS parameters from the profile associated with the PC5 unicast link.
If the DIRECT LINK MODIFICATION REQUEST message is to remove existing PC5 QoS flow(s) from the PC5 unicast link, the target UE shall delete the PQFI(s) and the corresponding PC5 QoS parameters from the profile associated with the PC5 unicast link.
If the DIRECT LINK MODIFICATION REQUEST message is to add a new V2X service, add new PC5 QoS flow(s) or modify any existing PC5 QoS flow(s) in the PC5 unicast link, after sending the DIRECT LINK MODIFICATION ACCEPT message, the target UE shall provide the added or modified PQFI(s) and corresponding PC5 QoS parameters along with PC5 link identifier to the lower layer.
If the DIRECT LINK MODIFICATION REQUEST message is to remove an existing V2X service or to remove the existing PC5 QoS flow(s) from the PC5 unicast link, after sending the DIRECT LINK MODIFICATION ACCEPT message, the target UE shall provide the removed PQFI(s) along with the PC5 link identifier to the lower layer.
If the target UE accepts the PC5 unicast link modification request, then the target UE may perform the PC5 QoS flow establishment over PC5 unicast link as specified in clause 6.1.2.12 and perform the PC5 QoS flow match over PC5 unicast link as specified in clause 6.1.2.13.
13.2.3.3 Test description
13.2.3.3.1 Pre-test conditions
System Simulator:
– NR-SS-UE
– NR-SS-UE1 operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.
– GNSS simulator
– The GNSS simulator is started and configured for Scenario #1.
– NR-SS-UE 1 is synchronised on GNSS.
UE:
– UE is authorised to perform NR sidelink communication.
– The UE is equipped with a USIM containing default values as per TS 38.508-1 [4] clause 4.8.3.3.3.
– UE is synchronised on GNSS.
Preamble:
– The UE is in state 4-A with Test Mode (On), Test Loop Function (Off) as defined in TS 38.508-1 [4], Table 4.5.7.2-1 using generic procedure parameter Sidelink (On), NR-SS-UE initiating unicast mode NR sidelink communication, Cast Type (Unicast), GNSS Sync (On).
13.2.3.3.2 Test procedure sequence
Table 13.2.3.3.2-1: Main behaviour
|
Procedure |
Message Sequence |
TP |
Verdict |
||
|
U – S |
Message |
||||
|
1 |
The NR-SS-UE1 transmits a DIRECT LINK MODIFICATION REQUEST to add a QoS flow |
<– |
PC5-S: DIRECT LINK MODIFICATION REQUEST |
– |
– |
|
2 |
Check: Does the UE transmit a DIRECT LINK MODIFICATION ACCEPT message? |
–> |
PC5-S: DIRECT LINK MODIFICATION ACCEPT |
1 |
P |
|
3 |
The NR-SS-UE sends a RRCReconfigurationSidelink message to establish a unicast mode SL-DRB#2. |
<– |
PC5-RRC: RRCReconfigurationSidelink |
– |
– |
|
4 |
Check: Does the UE send a RRCReconfigurationCompleteSidelink message? |
–> |
PC5-RRC: RRCReconfigurationCompleteSidelink |
1 |
P |
|
5 |
Check: Does the test result of generic test procedure in TS 38.508-1 subclause 4.9.31 indicate that the UE has user plane connectivity on SL-DRB#2? |
– |
– |
1 |
– |
|
6 |
The NR-SS-UE1 transmits a DIRECT LINK MODIFICATION REQUEST to modify the QoS flow associated with SL=DRB#2. |
<– |
PC5-S: DIRECT LINK MODIFICATION REQUEST |
– |
– |
|
7 |
Check: Does the UE transmit a DIRECT LINK MODIFICATION ACCEPT message? |
–> |
PC5-S: DIRECT LINK MODIFICATION ACCEPT |
2 |
P |
|
8 |
Check: Does the test result of generic test procedure in TS 38.508-1 subclause 4.9.31 indicate that the UE has user plane connectivity on SL-DRB#2? |
– |
– |
2 |
– |
|
9 |
The NR-SS-UE1 transmits a DIRECT LINK MODIFICATION REQUEST to release a QoS flow associated with SL=DRB#2 |
<– |
PC5-S: DIRECT LINK MODIFICATION REQUEST |
– |
– |
|
10 |
Check: Does the UE transmit a DIRECT LINK MODIFICATION ACCEPT message? |
–> |
PC5-S: DIRECT LINK MODIFICATION ACCEPT |
3 |
P |
|
11 |
The NR-SS-UE sends a RRCReconfigurationSidelink message to indicate release of unicast mode SL DRB. |
<– |
PC5-RRC: RRCReconfigurationSidelink |
– |
– |
|
12 |
Check: The UE sends a RRCReconfigurationSidelinkComplete message? |
–> |
PC5-RRC: RRCReconfigurationSidelinkComplete |
3 |
P |
13.2.3.3.3 Specific message contents
Table 13.2.3.3.3-1: Message DIRECT LINK MODIFICATION REQUEST (step 1, Table 13.2.3.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.4-9 with condition Rx |
Table 13.2.3.3.3-2: Message DIRECT LINK MODIFICATION ACCEPT (step 2, Table 13.2.3.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.4-10 |
Table 13.2.3.3.3-3: RRCReconfigurationSidelink (step 3, Table 13.2.3.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.6.1A-3 Conditions RX and SL_DRB |
|||||
|
RRCReconfigurationSidelink ::= SEQUENCE { |
|||||
|
criticalExtensions CHOICE { |
|||||
|
rrcReconfigurationSidelink-r16 SEQUENCE { |
|||||
|
slrb-ConfigToAddModList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-Config-r16 { |
1 entry |
||||
|
SLRB-Config-r16[1] SEQUENCE { |
entry 1 |
||||
|
sl-SDAP-ConfigPC5-r16 SEQUENCE { |
|||||
|
sl-MappedQoS-FlowsToAddList-r16 SEQUENCE (SIZE (1.. maxNrofSL-QFIsPerDest-r16)) OF SL-PQFI-r16 { |
1 entry |
||||
|
SL-PQFI-r16[1] |
2 |
entry 1 |
|||
|
} |
|||||
|
} |
|||||
|
sl-MAC-LogicalChannelConfigPC5-r16 SEQUENCE { |
|||||
|
sl-LogicalChannelIdentity-r16 |
LogicalChannelIdentity with condition DRB2 |
||||
|
} |
|||||
|
} |
|||||
|
} |
|||||
|
} |
|||||
|
} |
|||||
|
} |
|||||
Table 13.2.3.3.3-4: RRCReconfigurationSidelink (step 4, Table 13.2.3.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.6.1A-3 Conditions RX and SL_DRB |
Table 13.2.3.3.3-5: Message DIRECT LINK MODIFICATION REQUEST (step 6, Table 13.2.3.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.4-9 with condition Rx |
|||||
|
Information Element |
Value/remark |
Comment |
Condition |
||
|
Link modification operation code |
‘0000 0100’B |
Modify PC5 QoS parameters of the existing PC5 QoS flow(s) |
|||
|
QoS flow descriptions |
|||||
|
Length of PC5 QoS flow descriptions contents |
Set to the actual length of ‘PC5 QoS flow descriptions contents’ in bytes |
||||
|
PC5 QoS flow description 1 |
|||||
|
PQFI |
’00 0010’B |
||||
|
Operation Code |
‘011’B |
Modify existing PC5 QoS flow description |
|||
|
Number of parameters |
5 |
||||
|
E |
1 |
parameters list is included |
|||
|
Associated V2X service identifiers |
|||||
|
Length of V2X service identifier contents |
’04’H |
||||
|
V2X service identifier 1 |
’00 00 00 02’H |
||||
|
Parameters list |
|||||
|
Parameter 1 |
|||||
|
Parameter identifier |
’01’H |
PQI |
|||
|
Length of parameter contents |
1 |
||||
|
Parameter contents |
23 |
Platooning between UEs, See Table 5.4.4-1 in TS 23.287[xx] |
|||
|
Parameter 2 |
|||||
|
Parameter identifier |
’02’H |
GFBR |
|||
|
Length of parameter contents |
3 |
||||
|
Parameter contents |
‘0000 0111 0000 0000 0000 1100’B |
12 * 4Mbps = 48Mbps. |
|||
|
Parameter 3 |
|||||
|
Parameter identifier |
’03’H |
MFBR |
|||
|
Length of parameter contents |
3 |
||||
|
Parameter contents |
‘0000 0111 0000 0000 0001 1000’B |
24 * 4Mbps = 96Mbps. |
|||
|
Parameter 4 |
|||||
|
Parameter identifier |
’04’H |
Averaging window |
|||
|
Length of parameter contents |
2 |
||||
|
Parameter contents |
‘0000 0111 1101 0000’B |
2000ms |
|||
|
Parameter 5 |
|||||
|
Parameter identifier |
’06’H |
Default priority level |
|||
|
Length of parameter contents |
1 |
||||
|
Parameter contents |
3 |
||||
Table 13.2.3.3.3-6: Message DIRECT LINK MODIFICATION ACCEPT (step 7, Table 13.2.3.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.4-10 |
|||||
|
QoS flow descriptions |
|||||
|
PC5 QoS flow descriptions IEI |
’79’H |
||||
|
Length of PC5 QoS flow descriptions contents |
Set to the actual length of ‘PC5 QoS flow descriptions contents’ in bytes |
||||
|
PC5 QoS flow description 1 |
|||||
|
PQFI |
’00 0010’B |
||||
|
Operation Code |
‘011’B |
Modify existing PC5 QoS flow description |
|||
|
Number of parameters |
5 |
||||
|
E |
1 |
parameters list is included |
|||
|
Associated V2X service identifiers |
|||||
|
Length of V2X service identifier contents |
’04’H |
||||
|
V2X service identifier 1 |
’00 00 00 02’H |
||||
|
Parameters list |
|||||
|
Parameter 1 |
|||||
|
Parameter identifier |
’01’H |
PQI |
|||
|
Length of parameter contents |
1 |
||||
|
Parameter contents |
23 |
Platooning between UEs, See Table 5.4.4-1 in TS 23.287[xx] |
|||
|
Parameter 2 |
|||||
|
Parameter identifier |
’02’H |
GFBR |
|||
|
Length of parameter contents |
3 |
||||
|
Parameter contents |
‘0000 0111 0000 0000 0000 1100’B |
12 * 4Mbps = 48Mbps. |
|||
|
Parameter 3 |
|||||
|
Parameter identifier |
’03’H |
MFBR |
|||
|
Length of parameter contents |
3 |
||||
|
Parameter contents |
‘0000 0111 0000 0000 0001 1000’B |
24 * 4Mbps = 96Mbps. |
|||
|
Parameter 4 |
|||||
|
Parameter identifier |
’04’H |
Averaging window |
|||
|
Length of parameter contents |
2 |
||||
|
Parameter contents |
‘0000 0111 1101 0000’B |
2000ms |
|||
|
Parameter 5 |
|||||
|
Parameter identifier |
’06’H |
Default priority level |
|||
|
Length of parameter contents |
1 |
||||
|
Parameter contents |
3 |
||||
Table 13.2.3.3.3-7: Message DIRECT LINK MODIFICATION REQUEST (step 9, Table 13.2.3.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.4-9 with condition Rx |
|||||
|
Information Element |
Value/remark |
Comment |
Condition |
||
|
Link modification operation code |
‘0000 0101’B |
Remove existing PC5 QoS flow(s) from the existing PC5 unicast link |
|||
|
QoS flow descriptions |
|||||
|
Length of PC5 QoS flow descriptions contents |
Set to the actual length of ‘PC5 QoS flow descriptions contents’ in bytes |
||||
|
PC5 QoS flow description 1 |
|||||
|
PQFI |
’00 0010’B |
||||
|
Operation Code |
‘010’B |
Delete existing PC5 QoS flow description |
|||
|
Number of parameters |
0 |
||||
|
E |
0 |
parameters list is not included |
|||
|
Associated V2X service identifiers |
|||||
|
Length of V2X service identifier contents |
’04’H |
||||
|
V2X service identifier 1 |
’00 00 00 02’H |
||||
Table 13.2.3.3.3-8: Message DIRECT LINK MODIFICATION ACCEPT (step 10, Table 13.2.3.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.4-10 with condition RX |
|||||
|
QoS flow descriptions |
|||||
|
PC5 QoS flow descriptions IEI |
’79’H |
||||
|
Length of PC5 QoS flow descriptions contents |
Set to the actual length of ‘PC5 QoS flow descriptions contents’ in bytes |
||||
|
PC5 QoS flow description 1 |
|||||
|
PQFI |
’00 0010’B |
||||
|
Operation Code |
‘010’B |
Delete existing PC5 QoS flow description |
|||
|
Number of parameters |
0 |
||||
|
E |
0 |
parameters list is not included |
|||
|
Associated V2X service identifiers |
|||||
|
Length of V2X service identifier contents |
’04’H |
||||
|
V2X service identifier 1 |
’00 00 00 02’H |
||||
Table 13.2.3.3.3-9: RRCReconfigurationSidelink (step 11, Table Table 13.2.3.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.6.1A-3 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
RRCReconfigurationSidelink ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcReconfigurationSidelink-r16 SEQUENCE { |
|||
|
slrb-ConfigToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-PC5-ConfigIndex-r16 { |
1 entry |
||
|
SLRB-PC5-ConfigIndex-r16 [1] |
2 |
entry 1 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||