4.7.4 Contents of V2X messages
38.508-13GPP5GSPart 1: Common test environmentRelease 17TSUser Equipment (UE) conformance specification
Table 4.7.4-1 to -6: Void
– DIRECT LINK ESTABLISHMENT REQUEST
Table 4.7.4-7: DIRECT LINK ESTABLISHMENT REQUEST
Derivation Path: TS 24.587 [54] Table 7.3.1.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK ESTABLISHMENT REQUEST message identity |
‘0000 0001’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
V2X service identifiers |
||||
Length of V2X service identifier contents |
’04’H |
|||
V2X service identifier 1 |
’00 00 00 01’H |
|||
Source user info |
||||
Length of Application layer ID contents |
’04’H |
|||
Application Layer ID 1 |
’00 00 01 00’H |
Application Layer ID in initiating UE side |
||
UE security capabilities |
||||
Length of UE security capabilities contents |
’02’H |
|||
5G-EA algorithms |
‘1000 0000’B |
5G-EA0 supported |
||
5G-IA algorithms |
‘1000 0000’B |
5G-IA0 supported |
||
UE PC5 unicast signalling security policy |
‘0000 0000’B |
Signalling integrity protection not needed, Signalling ciphering not needed. |
||
Key establishment information container |
Not Present |
|||
Nonce_1 |
Not Present |
|||
MSBs of KNRP-sess ID |
Not Present |
|||
Target user info |
Not Checked |
Tx |
||
Target user info |
Rx |
|||
Application layer ID IEI |
’28’H |
|||
Length of Application layer ID contents |
’04’H |
|||
Application layer ID contents |
’00 00 11 00’H |
|||
KNRP ID |
Not Present |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK ESTABLISHMENT ACCEPT
Table 4.7.4-8: DIRECT LINK ESTABLISHMENT ACCEPT
Derivation Path: TS 24.587 [54] Table 7.3.1.1.1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
DIRECT LINK ESTABLISHMENT ACCEPT message identity |
‘0000 0010’B |
||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
|
Source user info |
|||
Length of Application layer ID contents |
’04’H |
||
Application Layer ID 1 |
’00 00 02 00’H |
Application Layer ID in target UE side |
|
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 0001’B |
||
Operation Code |
‘001’B |
Create new 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 01’H |
||
Parameters list |
|||
Parameter 1 |
|||
Parameter identifier |
’01’H |
PQI |
|
Length of parameter contents |
1 |
||
Parameter contents |
22 |
Sensor sharing, 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 0110 0000 0000 0000 1010’B |
10 * 1Mbps = 10Mbps. |
|
Parameter 3 |
|||
Parameter identifier |
’03’H |
MFBR |
|
Length of parameter contents |
3 |
||
Parameter contents |
‘0000 0110 0000 0000 0001 0100’B |
20 * 1Mbps = 20Mbps. |
|
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 |
4 |
||
Configuration of UE PC5 unicast user plane security protection |
‘0000 0000’B |
User plane integrity protection and ciphering is off |
|
IP address configuration |
Not Checked |
Tx |
|
IP address configuration |
Rx |
||
IP address configuration IEI |
’57’H |
||
IP address configuration content |
‘0000 0001’B |
IPv6 Router |
|
Link local IPv6 address |
Not Present |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK MODIFICATION REQUEST
Table 4.7.4-9: DIRECT LINK MODIFICATION REQUEST
Derivation Path: TS 24.587 [54] Table 7.3.4.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK MODIFICATION REQUEST message identity |
‘0000 0100’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
Link modification operation code |
‘0000 0011’B |
Add new PC5 QoS flow(s) to 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 |
‘001’B |
Create new 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 1010’B |
10 * 4Mbps = 40Mbps. |
||
Parameter 3 |
||||
Parameter identifier |
’03’H |
MFBR |
||
Length of parameter contents |
3 |
|||
Parameter contents |
‘0000 0111 0000 0000 0001 0100’B |
20 * 4Mbps = 80Mbps. |
||
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 |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK MODIFICATION ACCEPT
Table 4.7.4-10: DIRECT LINK MODIFICATION ACCEPT
Derivation Path: TS 24.587 [54] Table 7.3.5.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK MODIFICATION ACCEPT message identity |
‘0000 0101’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
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 |
‘001’B |
Create new 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 1010’B |
10 * 4Mbps = 40Mbps. |
||
Parameter 3 |
||||
Parameter identifier |
’03’H |
MFBR |
||
Length of parameter contents |
3 |
|||
Parameter contents |
‘0000 0111 0000 0000 0001 0100’B |
20 * 4Mbps = 80Mbps. |
||
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 |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK RELEASE REQUEST
Table 4.7.4-11: DIRECT LINK RELEASE REQUEST
Derivation Path: TS 24.587 [54] Table 7.3.6.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK RELEASE REQUEST message identity |
‘0000 0111’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
PC5 signalling protocol cause |
‘0110 1111’B |
Protocol error, unspecified |
Rx |
|
Not Checked |
Tx |
|||
MSB of KNRP ID |
Not Checked |
Tx |
||
’00 00’H |
Rx |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK RELEASE ACCEPT
Table 4.7.4-12: DIRECT LINK RELEASE ACCEPT
Derivation Path: TS 24.587 [54] Table 7.3.7.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK RELEASE ACCEPT message identity |
‘0000 1000’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
LSB of KNRP ID |
Not Checked |
Tx |
||
’00 00’H |
Rx |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK KEEPALIVE REQUEST
Table 4.7.4-13: DIRECT LINK KEEPALIVE REQUEST
Derivation Path: TS 24.587 [54] Table 7.3.8.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK KEEPALIVE REQUEST message identity |
‘0000 1001’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
Keep-alive counter |
’00 00 00 00’H |
Increase by 1 after each keep-alive procedure. |
||
Maximum inactivity period |
Not Checked |
Tx |
||
Maximum inactivity period |
Rx |
|||
Maximum inactivity period IEI |
’55’H |
|||
Maximum inactivity period contents |
’00 00 00 06’H |
6 seconds, higher value than T5003=5s |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK KEEPALIVE RESPONSE
Table 4.7.4-14: DIRECT LINK KEEPALIVE RESPONSE
Derivation Path: TS 24.587 [54] Table 7.3.9.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK KEEPALIVE RESPONSE message identity |
‘0000 1010’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
Keep-alive counter |
’00 00 00 01’H |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK AUTHENTICATION REQUEST
Table 4.7.4-15: DIRECT LINK AUTHENTICATION REQUEST
Derivation Path: TS 24.587 [54] Table 7.3.10.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK AUTHENTICATION REQUEST message identity |
‘0000 1011’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
Key establishment information container |
||||
Length of key establishment information container contents |
Not checked |
Tx |
||
’00’H |
Rx |
|||
Key establishment information container contents |
Not checked |
Tx |
||
Not Present |
Rx |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK AUTHENTICATION RESPONSE
Table 4.7.4-16: DIRECT LINK AUTHENTICATION RESPONSE
Derivation Path: TS 24.587 [54] Table 7.3.11.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK AUTHENTICATION RESPONSE message identity |
‘0000 1100’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
Key establishment information container |
||||
Length of key establishment information container contents |
Not checked |
Tx |
||
’00’H |
Rx |
|||
Key establishment information container contents |
Not checked |
Tx |
||
Not Present |
Rx |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK AUTHENTICATION REJECT
Table 4.7.4-17: DIRECT LINK AUTHENTICATION REJECT
Derivation Path: TS 24.587 [54] Table 7.3.12.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK AUTHENTICATION REJECT message identity |
‘0000 1101’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
PC5 signalling protocol cause value |
‘0110 1111’B |
Protocol error, unspecified |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK SECURITY MODE COMMAND
Table 4.7.4-18: DIRECT LINK SECURITY MODE COMMAND
Derivation Path: TS 24.587 [54] Table 7.3.13.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK SECURITY MODE COMMAND message identity |
‘0000 1110’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
Selected security algorithms |
‘0000 0000’B |
|||
UE security capabilities |
||||
Length of UE security capabilities contents |
’02’H |
|||
5G-EA algorithms |
‘1000 0000’B |
5G-EA0 supported |
||
5G-IA algorithms |
‘1000 0000’B |
5G-IA0 supported |
||
UE PC5 unicast signalling security policy |
||||
UE PC5 unicast signalling security policy IEI |
’59’H |
|||
Signalling integrity protection policy |
‘000’B |
Signalling integrity protection not needed |
||
Signalling ciphering policy |
‘000’B |
Signalling ciphering not needed. |
||
Nonce_2 |
Not Checked |
Tx |
||
Not Present |
Rx |
|||
LSBs of KNRP-sess ID |
Not Checked |
Tx |
||
Not Present |
Rx |
|||
Key establishment information container |
Not Checked |
Tx |
||
Not Present |
Rx |
|||
MSBs of KNRP ID |
Not Checked |
Tx |
||
Not Present |
Rx |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK SECURITY MODE COMPLETE
Table 4.7.4-19: DIRECT LINK SECURITY MODE COMPLETE
Derivation Path: TS 24.587 [54] Table 7.3.14.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK SECURITY MODE COMPLETE message identity |
‘0000 1111’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
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 0001’B |
|||
Operation Code |
‘001’B |
Create new 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 01’H |
|||
Parameters list |
||||
Parameter 1 |
||||
Parameter identifier |
’01’H |
PQI |
||
Length of parameter contents |
1 |
|||
Parameter contents |
22 |
Sensor sharing, 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 0110 0000 0000 0000 1010’B |
10 * 1Mbps = 10Mbps. |
||
Parameter 3 |
||||
Parameter identifier |
’03’H |
MFBR |
||
Length of parameter contents |
3 |
|||
Parameter contents |
‘0000 0110 0000 0000 0001 0100’B |
20 * 1Mbps = 20Mbps. |
||
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 |
4 |
|||
UE PC5 unicast user plane security policy |
‘0000 0000’B |
Signalling integrity protection not needed, Signalling ciphering not needed. |
||
IP address configuration |
Not Checked |
Tx |
||
IP address configuration |
Rx |
|||
IP address configuration IEI |
’57’H |
|||
IP address configuration content |
‘0000 0001’B |
IPv6 Router |
||
Link local IPv6 address |
Not Present |
Rx |
||
Not Checked |
Tx |
|||
LSBs of KNRP ID |
Not Checked |
Tx |
||
Not present |
Rx |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK SECURITY MODE REJECT
Table 4.7.4-20: DIRECT LINK SECURITY MODE REJECT
Derivation Path: TS 24.587 [54] Table 7.3.15.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK SECURITY MODE REJECT message identity |
‘0001 0000’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
PC5 signalling protocol cause |
‘0110 1111’B |
Protocol error, unspecified |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK REKEYING REQUEST
Table 4.7.4-21: DIRECT LINK REKEYING REQUEST
Derivation Path: TS 24.587 [54] Table 7.3.16.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK REKEYING REQUEST message identity |
‘0001 0001’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
UE security capabilities |
||||
Length of UE security capabilities contents |
’02’H |
|||
5G-EA algorithms |
‘1000 0000’B |
5G-EA0 supported |
||
5G-IA algorithms |
‘1000 0000’B |
5G-IA0 supported |
||
Key establishment information container |
Not Checked |
|||
Nonce_1 |
Not Checked |
|||
MSBs of KNRP-sess ID |
Not Checked |
|||
Re-authentication indication |
||||
Re-authentication indication IEI |
’56’H |
|||
Re-authentication indication contents |
‘0000 0000’B |
KNRP is not requested to be refreshed |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK REKEYING RESPONSE
Table 4.7.4-22: DIRECT LINK REKEYING RESPONSE
Derivation Path: TS 24.587 [54] Table 7.3.17.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK REKEYING RESPONSE message identity |
‘0001 0010’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK IDENTIFIER UPDATE REQUEST
Table 4.7.4-23: DIRECT LINK IDENTIFIER UPDATE REQUEST
Derivation Path: TS 24.587 [54] Table 7.3.18.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK IDENTIFIER UPDATE REQUEST message identity |
‘0001 0011’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
MSB of KNRP-sess ID |
Not checked |
Tx |
||
’00’H |
Rx |
|||
Source layer-2 ID |
’00 00 10’H |
|||
Source user info |
||||
Application layer ID IEI |
’57’H |
|||
Length of Application layer ID contents |
’04’H |
|||
Application Layer ID 1 |
’00 00 01 00’H |
Application Layer ID in initiating UE side |
||
Source link local IPv6 address |
Not present |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK IDENTIFIER UPDATE ACCEPT
Table 4.7.4-24: DIRECT LINK IDENTIFIER UPDATE ACCEPT
Derivation Path: TS 24.587 [54] Table 7.3.19.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK IDENTIFIER UPDATE ACCEPT message identity |
‘0001 0100’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
LSB of KNRP-sess ID |
Not checked |
Tx |
||
’00’H |
Rx |
|||
MSB of KNRP-sess ID |
Not checked |
Tx |
||
’00’H |
Rx |
|||
Source layer-2 ID |
’00 00 20’H |
|||
Target layer-2 ID |
’00 00 10’H |
|||
Target user info |
||||
Application layer ID IEI |
’28’H |
|||
Length of Application layer ID contents |
’04’H |
|||
Application Layer ID 1 |
’00 00 01 00’H |
Application Layer ID in initiating UE side |
||
Target link local IPv6 address |
Not Present |
|||
Source user info |
||||
Application layer ID IEI |
’57’H |
|||
Length of Application layer ID contents |
’04’H |
|||
Application Layer ID 1 |
’00 00 02 00’H |
Application Layer ID in target UE side |
||
Source link local IPv6 address |
Not Present |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK IDENTIFIER UPDATE ACK
Table 4.7.4-25: DIRECT LINK IDENTIFIER UPDATE ACK
Derivation Path: TS 24.587 [54] Table 7.3.20.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK IDENTIFIER UPDATE ACK message identity |
‘0001 0101’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
LSB of KNRP-sess ID |
Not checked |
Tx |
||
’00’H |
Rx |
|||
Target layer-2 ID |
’00 00 20’H |
|||
Target user info |
||||
Application layer ID IEI |
’28’H |
|||
Length of Application layer ID contents |
’04’H |
|||
Application Layer ID 1 |
’00 00 02 00’H |
Application Layer ID in target UE side |
||
Target link local IPv6 address |
Not Present |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK IDENTIFIER UPDATE REJECT
Table 4.7.4-26: DIRECT LINK IDENTIFIER UPDATE REJECT
Derivation Path: TS 24.587 [54] Table 7.3.21.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK IDENTIFIER UPDATE REJECT message identity |
‘0001 0110’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
PC5 signalling protocol cause |
‘0110 1111’B |
Protocol error, unspecified |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK MODIFICATION REJECT
Table 4.7.4-27: DIRECT LINK MODIFICATION REJECT
Derivation Path: TS 24.587 [54] Table 7.3.22.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK MODIFICATION REJECT message identity |
‘0000 0110’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
PC5 signalling protocol cause |
‘0110 1111’B |
Protocol error, unspecified |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |
– DIRECT LINK ESTABLISHMENT REJECT
Table 4.7.4-28: DIRECT LINK ESTABLISHMENT REJECT
Derivation Path: TS 24.587 [54] Table 7.3.23.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DIRECT LINK ESTABLISHMENT REJECT message identity |
‘0000 0011’B |
|||
Sequence number |
Not Checked |
0~255, uniquely identify a PC5 signalling message being sent or received |
Tx |
|
Incremented by TTCN by 1 for each outgoing new PC5 Signalling message. |
0~255, uniquely identify a PC5 signalling message being sent or received |
Rx |
||
PC5 signalling protocol cause |
‘0110 1111’B |
Protocol error, unspecified |
Condition |
Explanation |
Tx |
UE transmits and NR-SS-UE receives |
Rx |
UE receives and NR-SS-UE transmits |