4.8 Reference configurations
38.508-13GPP5GSPart 1: Common test environmentRelease 17TSUser Equipment (UE) conformance specification
4.8.1 Radio configurations
– RRCReconfiguration-DRB(n, m)
Table 4.8.1-1: RRCReconfiguration-DRB (n, m)
|
Derivation Path: Table 4.6.1-13 with condition NR. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
radioBearerConfig |
RadioBearerConfig-DRB-NR(n,m) |
||
|
} |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
masterCellGroup |
CellGroupConfig-DRB(n, m) |
OCTET STRING (CONTAINING CellGroupConfig) |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
– RRCReconfiguration-HO
Table 4.8.1-1A: RRCReconfiguration-HO
|
Derivation Path: Table 4.6.1-13. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
radioBearerConfig |
RadioBearerConfig with conditions SRB_NR_PDCP and DRBn and Re-establish_PDCP |
RBConfig_KeyChange |
|
|
RadioBearerConfig with conditions DRBn and Recover_PDCP |
RBConfig_NoKeyChange |
||
|
secondaryCellGroup |
Not present |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
masterCellGroup |
CellGroupConfig with conditions PCell_change |
OCTET STRING (CONTAINING CellGroupConfig) |
|
|
masterKeyUpdate |
Not present |
||
|
masterKeyUpdate SEQUENCE { |
RBConfig_KeyChange |
||
|
keySetChangeIndicator |
false |
Horizontal key derivation |
|
|
nextHopChainingCount |
NextHopChainingCount |
||
|
nas-Container |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
Condition |
Explanation |
|
RBConfig_KeyChange |
RadioBearerConfig to perform Intra-NR handover with security key change |
|
RBConfig_NoKeyChange |
RadioBearerConfig to perform Intra-NR handover without security key change |
– RRCReconfiguration-SRB2-DRB(n, m)
Table 4.8.1-1B: RRCReconfiguration-SRB2-DRB(n, m)
|
Derivation Path: Table 4.6.1-13 with condition NR. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
radioBearerConfig |
RadioBearerConfig-SRB2-DRB(n,m) |
||
|
} |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
masterCellGroup |
CellGroupConfig-SRB2-DRB(n, m) |
OCTET STRING (CONTAINING CellGroupConfig) |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
– RRCReconfiguration-NR-DC-DRB
Table 4.8.1-1CA: RRCReconfiguration-NR-DC-DRB
|
Derivation Path: Table 4.6.1-13 with condition NR-DC. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
radioBearerConfig |
Not present |
||
|
} |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
masterCellGroup |
Not present |
MCG(s) and SCG |
|
|
CellGroupConfig with condition DRB(n+m+1) |
OCTET STRING (CONTAINING CellGroupConfig) |
MCG(s) and split |
|
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
radioBearerConfig2 |
RadioBearerConfig with conditions DRB(n+m+1) and SCG_DRB and SecondaryKeys |
OCTET STRING (CONTAINING RadioBearerConfig) DRB(n,m) already configured on MCG |
MCG(s) and SCG |
|
RadioBearerConfig with conditions DRB(n+m+1) and SCG_DRB and Split and SecondaryKeys |
OCTET STRING (CONTAINING RadioBearerConfig) DRB(n,m) already configured on MCG |
MCG(s) and split |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
– RRCReconfiguration-NE-DC-DRB
Table 4.8.1-1CB: RRCReconfiguration-NE-DC-DRB
|
Derivation Path: Table 4.6.1-13 with condition NE-DC. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
radioBearerConfig |
Not present |
||
|
} |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
masterCellGroup |
Not present |
MCG(s) and SCG |
|
|
CellGroupConfig with condition DRB(n+m+1) |
OCTET STRING (CONTAINING CellGroupConfig) |
MCG(s) and split |
|
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
radioBearerConfig2 |
RadioBearerConfig with conditions DRB(n+m+1) and SCG_DRB and SecondaryKeys |
OCTET STRING (CONTAINING RadioBearerConfig) DRB(n,m) already configured on MCG |
MCG(s) and SCG |
|
RadioBearerConfig with conditions DRB(n+m+1) and SCG_DRB and Split and SecondaryKeys |
OCTET STRING (CONTAINING RadioBearerConfig) DRB(n,m) already configured on MCG |
MCG(s) and split |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
– RRCReconfiguration-Speech
Table 4.8.1-1C: RRCReconfiguration-Speech
|
Derivation Path: Table 4.6.1-13 with condition NR. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
radioBearerConfig |
RadioBearerConfig-Speech |
||
|
} |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
masterCellGroup |
CellGroupConfig-DRB(0.1) |
OCTET STRING (CONTAINING CellGroupConfig) |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
– RRCReconfiguration-Video
Table 4.8.1-1D: RRCReconfiguration-Video
|
Derivation Path: Table 4.6.1-13 with condition NR. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
radioBearerConfig |
RadioBearerConfig-Video |
||
|
} |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
masterCellGroup |
CellGroupConfig-DRB(0,2) |
OCTET STRING (CONTAINING CellGroupConfig) |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
– CellGroupConfig-DRB(n, m)
Table 4.8.1-2: CellGroupConfig-DRB(n, m)
|
Derivation Path: Table 4.6.3-19: CellGroupConfig |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLCH)) OF RLC-BearerConfig { |
n+m entries |
BID is the total number of established DRBs in the UE, before applying the contents of this IE |
|
|
RLC-BearerConfig[k, k=1..n] |
RLC-BearerConfig with conditions AM and DRBj (with j=BID+k) |
entry (1..n+1) |
n>0 |
|
RLC-BearerConfig[k, k=n+1..n+m] |
RLC-BearerConfig with conditions UM and DRBj (with j=BID+k) |
entry (n+1..n+m) |
m>0 |
|
} |
|||
|
} |
|||
|
Condition |
Explanation |
|
n>0 |
n is greater than zero |
|
m>0 |
m is greater than zero |
– CellGroupConfig-SRB3
Table 4.8.1-2A: CellGroupConfig-SRB3
|
Derivation Path: Table 4.6.3-19: CellGroupConfig with condition EN-DC. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLCH)) OF RLC-BearerConfig { |
2 entries |
||
|
RLC-BearerConfig[1] |
RLC-BearerConfig with conditions AM and DRB2 |
entry 1 |
|
|
RLC-BearerConfig[2] |
RLC-BearerConfig with condition SRB3 |
entry 2 |
|
|
} |
|||
|
} |
|||
– CellGroupConfig-SRB2-DRB(n, m)
Table 4.8.1-2B: CellGroupConfig-SRB2-DRB(n, m)
|
Derivation Path: Table 4.6.3-19: CellGroupConfig |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLCH)) OF RLC-BearerConfig { |
1+n+m entries |
||
|
RLC-BearerConfig[1] |
RLC-BearerConfig with condition SRB2 |
entry 1 |
|
|
RLC-BearerConfig[k, k=2..n+1] |
RLC-BearerConfig with conditions AM and DRBj |
entry (2..n+1) j is allocated according to internal TTCN mapping |
n>0 |
|
… |
… |
||
|
RLC-BearerConfig[k, k=n+2..n+m+1] |
RLC-BearerConfig with conditions UM and DRBj |
entry (n+2..n+m+1) j is allocated according to internal TTCN mapping |
m>0 |
|
} |
|||
|
mac-CellGroupConfig |
Not present |
||
|
physicalCellGroupConfig |
Not present |
||
|
spCellConfig |
Not present |
||
|
} |
|||
– RadioBearerConfig-DRB (n, m)
Table 4.8.1-3: RadioBearerConfig-DRB (n, m)
|
Derivation Path: Table 4.6.3-132 and condition EN-DC. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioBearerConfig ::= SEQUENCE { |
|||
|
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod { |
n+m entries |
BID is the total number of established DRBs in the UE, before applying the contents of this IE |
|
|
DRB-ToAddMod[k=1..n+m] SEQUENCE { |
entry (1..n+m) |
||
|
cnAssociation CHOICE { |
|||
|
eps-BearerIdentity |
l, l=BID+5..BID+4+n+m |
||
|
} |
|||
|
drb-Identity |
l, l=BID+1..BID+n+m |
||
|
reestablishPDCP |
Not present |
||
|
recoverPDCP |
Not present |
||
|
pdcp-Config |
PDCP-Config |
k <= n |
|
|
PDCP-Config with condition UM |
k > n |
||
|
} |
|||
|
} |
|||
|
} |
|||
– RadioBearerConfig-DRB-NR(n, m)
Table 4.8.1-3A: RadioBearerConfig-DRB-NR(n, m)
|
Derivation Path: Table 4.6.3-132. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioBearerConfig ::= SEQUENCE { |
|||
|
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod { |
n+m entries |
BID is the total number of established DRBs in the UE, before applying the contents of this IE |
|
|
DRB-ToAddMod[k=1..n+m] SEQUENCE { |
entry (1..n+m) |
||
|
cnAssociation CHOICE { |
|||
|
sdap-Config |
SDAP-Config |
||
|
} |
|||
|
drb-Identity |
BID+k |
k=1..n+m |
|
|
reestablishPDCP |
Not present |
||
|
recoverPDCP |
Not present |
||
|
pdcp-Config |
PDCP-Config |
k <= n |
|
|
PDCP-Config with condition UM |
k > n |
||
|
} |
|||
|
} |
|||
|
} |
|||
– RadioBearerConfig-SRB2-DRB (n, m)
Table 4.8.1-4: RadioBearerConfig-SRB2-DRB (n, m)
|
Derivation Path: Table 4.6.3-132 and condition SRB2. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioBearerConfig ::= SEQUENCE { |
|||
|
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod { |
n+m entries |
||
|
DRB-ToAddMod[k=1..n+m] := SEQUENCE { |
entry (1..n+m) |
||
|
cnAssociation CHOICE { |
|||
|
sdap-Config |
SDAP-Config |
SDAP-Config is configured according to internal TTCN mapping |
|
|
} |
|||
|
drb-Identity |
j |
j is allocated according to internal TTCN mapping |
|
|
reestablishPDCP |
Not present |
||
|
recoverPDCP |
Not present |
||
|
pdcp-Config |
PDCP-Config |
(1<k <= n) OR (k=1 AND NOT NR_split) |
|
|
PDCP-Config with condition UM |
k > n |
||
|
PDCP-Config with condition NR_split |
k=1 AND NR_split |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
– RadioBearerConfig-Speech
Table 4.8.1-5: RadioBearerConfig-Speech
|
Derivation Path: Table 4.6.3-132 and condition SRB2. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioBearerConfig ::= SEQUENCE { |
|||
|
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod { |
1 entry |
||
|
DRB-ToAddMod[1] SEQUENCE { |
|||
|
cnAssociation CHOICE { |
|||
|
sdap-Config SEQUENCE { |
SDAP-Config |
||
|
defaultDRB |
false |
||
|
} |
|||
|
} |
|||
|
drb-Identity |
j |
j is allocated according to internal TTCN mapping |
|
|
reestablishPDCP |
Not present |
||
|
recoverPDCP |
Not present |
||
|
pdcp-Config |
PDCP-Config with condition UM |
||
|
} |
|||
|
} |
|||
|
} |
|||
– RadioBearerConfig-Video
Table 4.8.1-6: RadioBearerConfig-Video
|
Derivation Path: Table 4.6.3-132 and condition SRB2. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioBearerConfig ::= SEQUENCE { |
|||
|
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod { |
2 entries |
||
|
DRB-ToAddMod [1] SEQUENCE { |
entry 1 |
||
|
cnAssociation CHOICE { |
|||
|
sdap-Config SEQUENCE { |
SDAP-Config |
||
|
defaultDRB |
false |
||
|
} |
|||
|
} |
|||
|
drb-Identity |
j |
j is allocated according to internal TTCN mapping |
|
|
reestablishPDCP |
Not present |
||
|
recoverPDCP |
Not present |
||
|
pdcp-Config |
PDCP-Config with condition UM |
||
|
} |
|||
|
DRB-ToAddMod [2] SEQUENCE { |
entry 2 |
||
|
cnAssociation CHOICE { |
|||
|
sdap-Config SEQUENCE { |
SDAP-Config |
||
|
defaultDRB |
false |
||
|
} |
|||
|
} |
|||
|
drb-Identity |
k |
k is allocated according to internal TTCN mapping |
|
|
reestablishPDCP |
Not present |
||
|
recoverPDCP |
Not present |
||
|
pdcp-Config |
PDCP-Config with condition UM |
||
|
} |
|||
|
} |
|||
|
} |
|||
4.8.2 5GC configurations
4.8.2.1 Reference QoS rules
Table 4.8.2.1-1: Reference QoS rule #1
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS rules |
|||
|
QoS rule |
|||
|
QoS rule identifier |
‘0000 0001’B |
1 (unique per PDU session) |
|
|
Rule operation code |
‘001’B |
Create new QoS rule |
|
|
DQR bit |
‘1’B |
The QoS rule is the default QoS rule. |
|
|
Number of packet filters |
‘0001’B |
1 packet filters |
|
|
Packet filter list |
See table 4.8.2.2-1 |
Packet filter list #1 |
|
|
QoS rule precedence |
‘1111 1111’B |
255 (unique per PDU session; If the default QoS rule contains a match-all packet filter, then the highest precedence value shall be used for the default QoS rule.) |
|
|
Spare bit |
‘0’B |
||
|
Segregation |
‘0’B |
Spare |
|
|
QoS flow identifier (QFI) |
’00 0001’B |
QFI 1 (Table 4.8.2.3-1) |
|
Table 4.8.2.1-2: Reference QoS rule #2
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS rules |
|||
|
QoS rule |
|||
|
QoS rule identifier |
‘0000 0010’B |
2 (unique per PDU session) |
|
|
Rule operation code |
‘001’B |
Create new QoS rule |
|
|
DQR bit |
‘1’B |
The QoS rule is the default QoS rule. |
|
|
Number of packet filters |
‘0001’B |
1 packet filter |
|
|
Packet filter list |
See table 4.8.2.2-1 |
Packet filter list #1 |
|
|
QoS rule precedence |
‘1111 1111’B |
255 (unique per PDU session; If the default QoS rule contains a match-all packet filter, then the highest precedence value shall be used for the default QoS rule.) |
|
|
Spare bit |
‘0’B |
||
|
Segregation |
‘0’B |
Spare |
|
|
QoS flow identifier (QFI) |
’00 0010’B |
QFI 2 (Table 4.8.2.3-2) |
|
Table 4.8.2.1-3: Reference QoS rule #3
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS rules |
|||
|
QoS rule |
|||
|
QoS rule identifier |
‘0000 0011’B |
3 (unique per PDU session) |
|
|
Rule operation code |
‘001’B |
Create new QoS rule |
|
|
DQR bit |
‘0’B |
The QoS rule is the non-default QoS rule. |
|
|
Number of packet filters |
‘0001’B |
1 packet filter |
|
|
Packet filter list |
See table 4.8.2.2-2 |
Packet filter list #2 |
|
|
QoS rule precedence |
‘0000 0011’B |
3 (unique per PDU session) |
|
|
Spare bit |
‘0’B |
||
|
Segregation |
‘0’B |
Spare |
|
|
QoS flow identifier (QFI) |
’00 0001’B |
QFI 1 (Table 4.8.2.3-1) |
|
Table 4.8.2.1-4: Reference QoS rule #4
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS rules |
|||
|
QoS rule |
|||
|
QoS rule identifier |
‘0000 0100’B |
4 (unique per PDU session) |
|
|
Rule operation code |
‘001’B |
Create new QoS rule |
|
|
DQR bit |
‘1’B |
The QoS rule is the default QoS rule. |
|
|
Number of packet filters |
‘0001’B |
1 packet filter |
|
|
Packet filter list |
See table 4.8.2.2-3 |
Packet filter list #3 |
|
|
QoS rule precedence |
‘0000 00100’B |
4 (unique per PDU session) |
|
|
Spare bit |
‘0’B |
||
|
Segregation |
‘0’B |
Spare |
|
|
QoS flow identifier (QFI) |
’00 0010’B |
QFI 2 (Table 4.8.2.3-2) |
|
Table 4.8.2.1-4a: Reference QoS rule #4a
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS rules |
|||
|
QoS rule |
|||
|
QoS rule identifier |
‘0000 1111’B |
15 (unique per PDU session) |
|
|
Rule operation code |
‘001’B |
Create new QoS rule |
|
|
DQR bit |
‘0’B |
The QoS rule is the non-default QoS rule. |
|
|
Number of packet filters |
‘0001’B |
1 packet filter |
|
|
Packet filter list |
See table 4.8.2.2-3a |
Packet filter list #3a |
|
|
QoS rule precedence |
‘0000 1111’B |
15 (unique per PDU session) |
|
|
Spare bit |
‘0’B |
||
|
Segregation |
‘0’B |
Spare |
|
|
QoS flow identifier (QFI) |
’00 0100’B |
QFI 4 (Table 4.8.2.3-2a) |
|
Table 4.8.2.1-5: Reference QoS rule #5
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS rules |
|||
|
QoS rule |
|||
|
QoS rule identifier |
‘0000 0101’B |
5 (unique per PDU session) |
|
|
Rule operation code |
‘001’B |
Create new QoS rule |
|
|
DQR bit |
‘0’B |
The QoS rule is the non-default QoS rule. |
|
|
Number of packet filters |
‘0001’B |
1 packet filter |
|
|
Packet filter list |
See table 4.8.2.2-4 |
Packet filter list #4 |
|
|
QoS rule precedence |
‘0000 0101’B |
5 (unique per PDU session) |
|
|
Spare bit |
‘0’B |
||
|
Segregation |
‘0’B |
Spare |
|
|
QoS flow identifier (QFI) |
’00 0101’B |
QFI 5 (Table 4.8.2.3-3) |
|
Table 4.8.2.1-6: Reference QoS rule #6
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS rules |
|||
|
QoS rule |
|||
|
QoS rule identifier |
‘0000 0110’B |
6 (unique per PDU session) |
|
|
Rule operation code |
‘001’B |
Create new QoS rule |
|
|
DQR bit |
‘0’B |
The QoS rule is the non-default QoS rule. |
|
|
Number of packet filters |
‘0001’B |
1 packet filter |
|
|
Packet filter list |
See table 4.8.2.2-5 |
Packet filter list #5 |
|
|
QoS rule precedence |
‘0000 0110’B |
6 (unique per PDU session) |
|
|
Spare bit |
‘0’B |
||
|
Segregation |
‘0’B |
Spare |
|
|
QoS flow identifier (QFI) |
’00 0110’B |
QFI 6 (Table 4.8.2.3-4) |
|
Table 4.8.2.1-7: Reference QoS rule #7
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS rules |
|||
|
QoS rule |
IMS_VOICE |
||
|
QoS rule identifier |
‘0000 0011’B |
3 (unique per PDU session) |
|
|
Rule operation code |
‘001’B |
Create new QoS rule |
|
|
DQR bit |
‘0’B |
The QoS rule a non-default QoS rule. |
|
|
Number of packet filters |
‘0001’B |
1 packet filter |
|
|
Packet filter list |
See table 4.8.2.2-6 |
Packet filter list #6 |
|
|
QoS rule precedence |
‘0000 0001’B |
1 (unique per PDU session) |
|
|
Spare bit |
‘0’B |
||
|
Segregation |
‘0’B |
Spare |
|
|
QoS flow identifier (QFI) |
’00 0111’B |
QFI 7 (Table 4.8.2.3-5) |
|
|
QoS rule |
IMS_VIDEO |
||
|
QoS rule identifier |
‘0000 0100’B |
4 (unique per PDU session) |
|
|
Rule operation code |
‘001’B |
Create new QoS rule |
|
|
DQR bit |
‘0’B |
The QoS rule a non-default QoS rule. |
|
|
Number of packet filters |
‘0001’B |
1 packet filter |
|
|
Packet filter list |
See table 4.8.2.2-7 |
Packet filter list #7 |
|
|
QoS rule precedence |
‘0000 0010’B |
2 (unique per PDU session) |
|
|
Spare bit |
‘0’B |
||
|
Segregation |
‘0’B |
Spare |
|
|
QoS flow identifier (QFI) |
’00 1000’B |
QFI 8 (Table 4.8.2.3-6) |
|
|
Condition |
Explanation |
|
IMS_VOICE |
If this QoS rule is used to setup an IMS voice session |
|
IMS_VIDEO |
If this QoS rule is used to setup an IMS video session |
Table 4.8.2.1-8: Reference QoS rule #8
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS rules |
|||
|
QoS rule |
|||
|
QoS rule identifier |
‘0000 0111’B |
7 (unique per PDU session) |
|
|
Rule operation code |
‘001’B |
Create new QoS rule |
|
|
DQR bit |
‘1’B |
The QoS rule is the default QoS rule. |
|
|
Number of packet filters |
‘0001’B |
1 packet filter |
|
|
Packet filter list |
See table 4.8.2.2-1 |
Packet filter list #1 |
|
|
QoS rule precedence |
‘1111 1111’B |
255 (unique per PDU session; If the default QoS rule contains a match-all packet filter, then the highest precedence value shall be used for the default QoS rule.) |
|
|
Spare bit |
‘0’B |
||
|
Segregation |
‘0’B |
Spare |
|
|
QoS flow identifier (QFI) |
’00 1001’B |
QFI 9 (Table 4.8.2.3-7) |
|
4.8.2.2 Reference packet filters
Table 4.8.2.2-1: Packet filter list #1
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Packet filter list |
|||
|
Packet filter direction |
‘11’B |
bidirectional |
|
|
Packet filter identifier |
‘0001’B |
Id 1 |
|
|
Component type 1 ID |
‘0000 0001’B |
Match-all type |
|
Table 4.8.2.2-2: Packet filter list #2
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Packet filter list |
|||
|
Packet filter direction |
‘11’B |
bidirectional |
|
|
Packet filter identifier |
‘0010’B |
Id 2 |
|
|
Component type 1 ID |
0 0 0 1 0 0 0 0 |
IPv4 remote address type |
remoteIPv4 |
|
0 0 1 0 0 0 0 1 |
IPv6 remote address type/prefix lenght type |
remoteIPv6 |
|
|
Component type 1 Value |
10.10.10.2 255.255.255.255 |
See Note 1 |
remoteIPv4 |
|
C0C0:C0C0:C0C0:C002 C0C0:C0C0:C0C0:C0C0/ 64 |
See Note 1 |
remoteIPv6 |
|
|
Note 1: This IP address is also the address of an IP server able to send a flow of downlink IP packets to the UE. remoteIPv4 applies if the UE has acquired an IPv4 address only, remoteIPv6 applies if the UE has acquired an IPv6 address only, or both an IPv6 and an IPv4 address. |
|||
Table 4.8.2.2-3: Packet filter list #3
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Packet filter list |
|||
|
Packet filter direction |
‘11’B |
bidirectional |
|
|
Packet filter identifier |
‘0011’B |
Id 3 |
|
|
Component type 1 ID |
0 0 0 1 0 0 0 0 |
IPv4 remote address type |
remoteIPv4 |
|
0 0 1 0 0 0 0 1 |
IPv6 remote address type/prefix lenght type |
remoteIPv6 |
|
|
Component type 1 Value |
10.10.10.3 255.255.255.255 |
See Note 1 |
remoteIPv4 |
|
C0C0:C0C0:C0C0:C003 C0C0:C0C0:C0C0:C0C0/ 64 |
See Note 1 |
remoteIPv6 |
|
|
Note 1: This IP address is also the address of an IP server able to send a flow of downlink IP packets to the UE. remoteIPv4 applies if the UE has acquired an IPv4 address only, remoteIPv6 applies if the UE has acquired an IPv6 address only, or both an IPv6 and an IPv4 address. |
|||
Table 4.8.2.2-3a: Packet filter list #3a
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Packet filter list |
|||
|
Packet filter direction |
‘11’B |
bidirectional |
|
|
Packet filter identifier |
‘1111’B |
Id 15 |
|
|
Component type 1 ID |
0 0 0 1 0 0 0 0 |
IPv4 remote address type |
remoteIPv4 |
|
0 0 1 0 0 0 0 1 |
IPv6 remote address type/prefix lenght type |
remoteIPv6 |
|
|
Component type 1 Value |
10.10.10.30 255.255.255.255 |
See Note 1 |
remoteIPv4 |
|
C0C0:C0C0:C0C0:C030 C0C0:C0C0:C0C0:C0C0/ 64 |
See Note 1 |
remoteIPv6 |
|
|
Note 1: This IP address is also the address of an IP server able to send a flow of downlink IP packets to the UE. remoteIPv4 applies if the UE has acquired an IPv4 address only, remoteIPv6 applies if the UE has acquired an IPv6 address only, or both an IPv6 and an IPv4 address. |
|||
Table 4.8.2.2-4: Packet filter list #4
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Packet filter list |
|||
|
Packet filter direction |
‘11’B |
bidirectional |
|
|
Packet filter identifier |
‘0100’B |
Id 4 |
|
|
Component type 1 ID |
0 0 0 1 0 0 0 0 |
IPv4 remote address type |
remoteIPv4 |
|
0 0 1 0 0 0 0 1 |
IPv6 remote address type/prefix lenght type |
remoteIPv6 |
|
|
Component type 1 Value |
10.10.10.4 255.255.255.255 |
See Note 1 |
remoteIPv4 |
|
C0C0:C0C0:C0C0:C004 C0C0:C0C0:C0C0:C0C0/ 64 |
See Note 1 |
remoteIPv6 |
|
|
Note 1: This IP address is also the address of an IP server able to send a flow of downlink IP packets to the UE. remoteIPv4 applies if the UE has acquired an IPv4 address only, remoteIPv6 applies if the UE has acquired an IPv6 address only, or both an IPv6 and an IPv4 address. |
|||
Table 4.8.2.2-5: Packet filter list #5
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Packet filter list |
|||
|
Packet filter direction |
‘11’B |
bidirectional |
|
|
Packet filter identifier |
‘0101’B |
Id 5 |
|
|
Component type 1 ID |
0 0 0 1 0 0 0 0 |
IPv4 remote address type |
remoteIPv4 |
|
0 0 1 0 0 0 0 1 |
IPv6 remote address type/prefix lenght type |
remoteIPv6 |
|
|
Component type 1 Value |
10.10.10.5 255.255.255.255 |
See Note 1 |
remoteIPv4 |
|
C0C0:C0C0:C0C0:C005 C0C0:C0C0:C0C0:C0C0/ 64 |
See Note 1 |
remoteIPv6 |
|
|
Note 1: This IP address is also the address of an IP server able to send a flow of downlink IP packets to the UE. remoteIPv4 applies if the UE has acquired an IPv4 address only, remoteIPv6 applies if the UE has acquired an IPv6 address only, or both an IPv6 and an IPv4 address. |
|||
Table 4.8.2.2-6: Packet filter list #6
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Packet filter list |
|||
|
Packet filter direction |
‘11’B |
bidirectional |
|
|
Packet filter identifier |
0110’B |
Id 6 |
|
|
Component type 1 ID |
0 1 0 1 0 0 0 1 |
Remote port range type |
|
|
Component type 1 Value |
media port |
SS speech media port as used in the SDP negotiation (RTP remote port); see Note 1 |
|
|
media port + 1 |
RTCP remote port; see Note 1 |
||
|
Component type 2 ID |
0 0 1 1 0 0 0 0 |
Protocol identifier/Next header type |
|
|
Component type 2 Value |
17 |
UDP |
|
|
Note 1: According to to TS 26.114 [45] and RFC 4566 [46] a "media port" can be understood as the transport port to which a media stream is sent. |
|||
Table 4.8.2.2-7: Packet filter list #7
|
Derivation Path: TS 24.501, table 9.11.4.13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Packet filter list |
|||
|
Packet filter direction |
‘11’B |
bidirectional |
|
|
Packet filter identifier |
0111’B |
Id 7 |
|
|
Component type 1 ID |
0 1 0 1 0 0 0 1 |
Remote port range type |
|
|
Component type 1 Value |
media port |
SS video media port as used in the SDP negotiation (RTP remote port); see Note 1 |
|
|
media port + 1 |
RTCP remote port; see Note 1 |
||
|
Component type 2 ID |
0 0 1 1 0 0 0 0 |
Protocol identifier/Next header type |
|
|
Component type 2 Value |
17 |
UDP |
|
|
Note 1: According to to TS 26.114 [45] and RFC 4566 [46] a "media port" can be understood as the transport port to which a media stream is sent. |
|||
4.8.2.3 Reference QoS flow descriptions
Table 4.8.2.3-1: Reference QoS flow #1
|
Derivation Path: TS 24.501, table 9.11.4.12 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS flow descriptions |
|||
|
QoS flow description |
|||
|
QFI |
‘00 0001’B |
QFI 1 |
|
|
Operation code |
‘001’B |
Create new QoS flow description |
|
|
E bit |
‘1’B |
Parameters list is included |
|
|
Number of parameters |
’00 0001’B |
1 parameter |
|
|
Number of parameters |
’00 0010’B |
2 parameters |
Interworking_with_EPS |
|
5QI |
‘0000 1001’B |
5QI 9 |
|
|
EPS bearer identity |
Any not yet assigned value different to ‘5’ |
Interworking_with_EPS |
|
|
Condition |
Explanation |
|
Interworking_with_EPS |
If this flow is used in the Authorized QoS flow descriptions IE of a PDU SESSION ESTABLISHMENT ACCEPT message or PDU SESSION MODIFICATION COMMAND message also including the Mapped EPS bearer context IE. |
Table 4.8.2.3-2: Reference QoS flow #2
|
Derivation Path: TS 24.501, table 9.11.4.12 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS flow descriptions |
|||
|
QoS flow description |
|||
|
QFI |
‘00 0010’B |
QFI 2 |
|
|
Operation code |
‘001’B |
Create new QoS flow description |
|
|
E bit |
‘1’B |
Parameters list is included |
|
|
Number of parameters |
’00 0001’B |
1 parameter |
|
|
Number of parameters |
’00 0010’B |
2 parameters |
Interworking_with_EPS |
|
5QI |
‘0000 0101’B |
5QI 5 |
|
|
EPS bearer identity |
‘0101 0000’B |
EBI 5 |
Interworking_with_EPS |
|
EPS bearer identity |
Any not yet assigned value different from ‘5’ |
EmergencySession AND Interworking_with_EPS |
|
|
Condition |
Explanation |
|
Interworking_with_EPS |
If this flow is used in the Authorized QoS flow descriptions IE of a PDU SESSION ESTABLISHMENT ACCEPT message or PDU SESSION MODIFICATION COMMAND message also including the Mapped EPS bearer context IE. |
|
EmergencySession |
If this flow is used in the Authorized QoS flow descriptions IE of a PDU Session Establishment Accept message for an emergency PDU session |
Table 4.8.2.3-2a: Reference QoS flow #2a
|
Derivation Path: TS 24.501, table 9.11.4.12 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS flow descriptions |
|||
|
QoS flow description |
|||
|
QFI |
‘00 0100’B |
QFI 4 |
|
|
Operation code |
‘001’B |
Create new QoS flow description |
|
|
E bit |
‘1’B |
Parameters list is included |
|
|
Number of parameters |
’00 0001’B |
1 parameter |
|
|
5QI |
‘0000 0101’B |
5QI 5 |
|
Table 4.8.2.3-3: Reference QoS flow #3
|
Derivation Path: TS 24.501, table 9.11.4.12 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS flow descriptions |
|||
|
QoS flow description |
|||
|
QFI |
‘00 0101’B |
QFI 5 |
|
|
Operation code |
‘001’B |
Create new QoS flow description |
|
|
E bit |
‘1’B |
Parameters list is included |
|
|
Number of parameters |
’00 0001’B |
1 parameter |
|
|
5QI |
‘0000 0101’B |
5QI 5 |
|
Table 4.8.2.3-4: Reference QoS flow #4
|
Derivation Path: TS 24.501, table 9.11.4.12 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS flow descriptions |
|||
|
QoS flow description |
|||
|
QFI |
‘00 0110’B |
QFI 6 |
|
|
Operation code |
‘001’B |
Create new QoS flow description |
|
|
E bit |
‘1’B |
Parameters list is included |
|
|
Number of parameters |
’00 0001’B |
1 parameter |
|
|
5QI |
‘0000 0101’B |
5QI 5 |
|
Table 4.8.2.3-5: Reference QoS flow #5
|
Derivation Path: TS 24.501, table 9.11.4.12 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS flow descriptions |
|||
|
QoS flow description |
|||
|
QFI |
‘00 0111’B |
QFI 7 |
|
|
Operation code |
‘001’B |
Create new QoS flow description |
|
|
E bit |
‘1’B |
Parameters list is included |
|
|
Number of parameters |
’00 0101’B |
5 parameter |
|
|
Number of parameters |
’00 0110’B |
6 parameters |
Interworking_with_EPS |
|
5QI |
‘0000 0001’B |
5QI 1 |
|
|
GFBR uplink |
‘040002’H |
128 Kbps |
|
|
GFBR downlink |
‘040002’H |
128 Kbps |
|
|
MFBR uplink |
‘040005’H |
320 Kbps |
|
|
MFBR downlink |
‘040005’H |
320 Kbps |
|
|
EPS bearer identity |
Any not yet assigned value different to ‘5’ |
EBI 6 |
Interworking_with_EPS |
|
Condition |
Explanation |
|
Interworking_with_EPS |
If this flow is used in the Authorized QoS flow descriptions IE of a PDU SESSION ESTABLISHMENT ACCEPT message or PDU SESSION MODIFICATION COMMAND message also including the Mapped EPS bearer context IE. |
Table 4.8.2.3-6: Reference QoS flow #6
|
Derivation Path: TS 24.501, table 9.11.4.12 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS flow descriptions |
|||
|
QoS flow description |
|||
|
QFI |
‘00 1000’B |
QFI 8 |
|
|
Operation code |
‘001’B |
Create new QoS flow description |
|
|
E bit |
‘1’B |
Parameters list is included |
|
|
Number of parameters |
’00 0101’B |
5 parameter |
|
|
Number of parameters |
’00 0110’B |
6 parameters |
Interworking_with_EPS |
|
5QI |
‘0000 0010’B |
5QI 2 |
|
|
GFBR uplink |
‘020012’H |
72 Kbps |
|
|
GFBR downlink |
‘020012’H |
72 Kbps |
|
|
MFBR uplink |
‘030033’H |
816 Kbps |
|
|
MFBR downlink |
‘030033’H |
816 Kbps |
|
|
EPS bearer identity |
Any not yet assigned value different to ‘5’ |
EBI 7 |
Interworking_with_EPS |
|
Condition |
Explanation |
|
Interworking_with_EPS |
If this flow is used in the Authorized QoS flow descriptions IE of a PDU SESSION ESTABLISHMENT ACCEPT message or PDU SESSION MODIFICATION COMMAND message also including the Mapped EPS bearer context IE. |
Table 4.8.2.3-7: Reference QoS flow #7
|
Derivation Path: TS 24.501, table 9.11.4.12 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS flow descriptions |
|||
|
QoS flow description |
|||
|
QFI |
‘00 1001’B |
QFI 9 |
|
|
Operation code |
‘001’B |
Create new QoS flow description |
|
|
E bit |
‘1’B |
Parameters list is included |
|
|
Number of parameters |
’00 0001’B |
1 parameter |
|
|
5QI |
‘0101 0010’B |
5QI 82 |
|
4.8.3 Common test UICC and USIM parameters
This clause defines default parameters for programming the elementary files of the test UICC when running conformance test cases defined in 3GPP TS 38.523-1[12].
4.8.3.1 General
See clause 4.9.1 in 3GPP TS 36.508 [2] for the definition of test algorithm for
– authentication via EPC;
– authentication via 5GC using 5G AKA based primary authentication and key agreement procedure.
– authentication via 5GC using EAP-AKA’ based primary authentication and key agreement procedure, further the Derivation of MSK, EMSK and other keys shaall be as derived as clause 3.3 of IETF RFC 5448 [31], using Key derivation function HMAC-SHA-256 algorithm.
4.8.3.2 Default parameters for the test USIM and ISIM
Same as clause 4.9.2 in 3GPP TS 36.508 [2] for
– authentication via EPC;
– authentication via 5GC using 5G AKA based primary authentication and key agreement procedure.
– authentication via 5GC using EAP-AKA’ based primary authentication and key agreement procedure.
4.8.3.3 Default settings for the Elementary Files (EFs)
Same as clause 4.9.3 in 3GPP TS 36.508 [2] for
– authentication via EPC;
– authentication via 5GC using 5G AKA based primary authentication and key agreement procedure
– authentication via 5GC using EAP-AKA’ based primary authentication and key agreement procedure.
4.8.3.3.1 Modified contents of the USIM Elementary Files
Table 4.8.3.3.1-1: EFUST (USIM Service Table)
|
Services |
Activated |
Version |
Condition |
|
|---|---|---|---|---|
|
Service n°122 |
5GS Mobility Management Information |
Optional |
5GC |
|
|
Service n°123 |
5GS Security Parameters |
Optional |
5GC |
|
|
Service n°124 |
Subscription identifier privacy support |
Optional |
5GC |
|
|
Service n°125 |
SUCI calculation by the USIM |
Optional |
5GC |
|
|
Service n°126 |
UAC Access Identities Configuration |
Optional |
5GC |
|
|
Service n°127 |
Control plane-based steering of UE in VPLMN |
Optional |
5GC |
|
|
Service n°128 |
Call control on PDU Session by USIM |
Optional |
||
|
Service n°129 |
5GS Operator PLMN List |
Optional |
||
|
Note: Only 5GS related services indicated |
||||
|
Condition |
Explanation |
|
5GC |
Authentication via 5GC |
4.8.3.3.2 Contents of Elementary Files at the DF5GS level
This clause defines the default contents of Elementary Files (EF) that are specific for 5GS and which are grouped in Data File (DF) structure 5GS.
EF5GS3GPPLOCI (5GS 3GPP location information)
File size: 20 Bytes
Default values: Bytes 1 to 13 (HEX): FF FF FF FF FF FF FF FF FF FF FF FF FF (5G-GUTI)
Bytes 14 to 19 (HEX): 42 F6 18 FF FF FE (Last visited registered TAI in 5GS for 3GPP access)
Byte 20 (BIN): 00000001 (5GS update status for 3GPP access = "5U2 not updated")
Bytes 14 to 19: TAI-MCC = 246 (bytes 14 to 15) and TAI-MNC = 81 (byte 16) are frequently used. The TAC (bytes 17 to 19) is set to "FF FF FE" since this, in conjunction with byte 20 setting of "01", is used to ensure that the UE performs registration at the beginning of a test.
Bytes in this file (e.g. GUTI in bytes 1 to 13) may be updated as a result of a registration attempt by the UE.
EF5GSN3GPPLOCI (5GS non-3GPP location information)
File size: 20 Bytes
Default values: Bytes 1 to 13 (HEX): FF FF FF FF FF FF FF FF FF FF FF FF FF (5G-GUTI)
Bytes 14 to 19 (HEX): 42 F6 18 FF FF FE (Last visited registered TAI in 5GS for non-3GPP access)
Byte 20 (BIN): 00000001 (5GS update status for non-3GPP access = "5U2 not updated")
Bytes 14 to 19: TAI-MCC = 246 (bytes 14 to 15) and TAI-MNC = 81 (byte 16) are frequently used. The TAC (bytes 17 to 19) is set to "FF FF FE" since this, in conjunction with byte 20 setting of "01", is used to ensure that the UE performs registration at the beginning of a test.
Bytes in this file (e.g. GUTI in bytes 1 to 13) may be updated as a result of a registration attempt by the UE.
EF5GS3GPPNSC (5GS 3GPP Access NAS Security Context)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [33], annex E.
EF5GSN3GPPNSC (5GS non-3GPP Access NAS Security Context)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [33], annex E.
EF5GAUTHKEYS (5G authentication keys)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [33], annex E.
EFUAC_AIC (UAC Access Identities Configuration)
The programming of this EF is a test house option.
EFSUCI_Calc_Info (Subscription Concealed Identifier Calculation Information EF)
The programming of this EF is a test house option.
EFOPL5G (5GS Operator PLMN List)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [33], annex E.
4.8.3.3.3 Default settings of UICC and USIM for V2X
EFUST (USIM Service Table):
Same as clause 4.9.3.4 of TS 36.508 [2].
EFVST (V2X Service Table)
If service n°119 is "available" in the USIM Service Table, this file shall be present. This EF indicates the coding of the V2X management objects and which V2X services are available.
File size: 2 Bytes
Default values: Bytes 1 to 2 (HEX): 01 02
Coding of the V2X management objects is according to 3GPP TS 24.588 [113].
Service n°2 V2X policy configuration data over PC5 is supported.
NOTE: The default value for NR support of V2X services is different from that for LTE V2X in clause 4.9.3.4 of TS 36.508 [2].
EFV2XP_PC5 (V2X data policy over PC5)
If service n°2 is "available" in EFVST, this file shall be present. This EF contains V2X in 5GS UE policies over PC5. The format of the V2X in 5GS UE policies over PC5 are specified in 3GPP TS 24.588 [113].
The V2X in 5GS UE policies over PC5 contents:
Table 4.8.3.3.3-1: V2X data policy over PC5
|
Description |
Value |
M/O |
Length (bytes) |
|
V2X data policy over PC5 Tag |
‘A0’ |
M |
1 |
|
Length |
Note 1 |
M |
Note 2 |
|
Validity timer |
‘FF FF FF FF FF FF FF FF FF FF’H |
M |
X1 |
|
Indicator bits |
‘1000 0000’B |
M |
1 |
|
Served by E-UTRA or served by NR Tag |
’80’ |
M |
1 |
|
Length |
X2 |
M |
Note 2 |
|
Served by E-UTRA or served by NR information |
See Table 4.7.5.5-2 |
M |
X2 |
|
Not served by E-UTRA and not served by NR Tag |
’81’ |
O |
1 |
|
Length |
X3 |
O |
Note 2 |
|
Not served by E-UTRA and not served by NR information |
See Table 4.7.5.5-6 |
O |
X3 |
|
V2X service identifier to Tx profiles mapping rules Tag |
’82’ |
O |
1 |
|
Length |
X4 |
O |
Note 2 |
|
V2X service identifier to Tx profiles mapping rules information |
See Table 4.7.5.5-12 |
X4 |
|
|
Privacy config Tag |
’83’ |
O |
1 |
|
Length |
X5 |
O |
Note 2 |
|
Privacy config information |
See Table 4.7.5.5-15 |
X5 |
|
|
V2X communication over PC5 in E-UTRA Tag |
’84’ |
O |
1 |
|
Length |
X6 |
O |
Note 2 |
|
V2X communication over PC5 in E-UTRA information |
See Table 4.7.5.5-19 |
O |
X6 |
|
V2X communication over PC5 in NR Tag |
’85 |
O |
1 |
|
Length |
X7 |
O |
Note 2 |
|
V2X communication over PC5 in NR Information |
See Table 4.7.5.5-31 |
O |
X7 |
|
Note 1: This is the total size of the constructed TLV object. Note 2: The length is coded according to ISO/IEC 8825-1 [35]. |
|||
4.8.4 DNN/APN configurations
The present subclause provides DNN/APN configurations required for flexible PDU/PDN handling. Table 4.8.4-1 provides configurations for the types on DNN/APN handled in the present version of the test specification. If in the future new PDU types need to be handled, then new DNN/APN configuration(s) may be added.
Table 4.8.4-1: DNN/APN configurations, first set
|
Configurations |
Config #1 |
Config #2 |
Config #3 |
|
DNN/APN type |
internet |
ims |
urllc |
|
DNN/APN ID |
pc_APN_ID_Internet |
pc_APN_ID_IMS |
pc_APN_ID_URLLC |
|
5GC QoS rule |
Reference QoS rule #1 as specified in subclause 4.8.2.1. |
Reference QoS rule #2 as specified in subclause 4.8.2.1. |
Reference QoS rule #8 as specified in subclause 4.8.2.1. |
|
EPC default bearer context |
Reference default EPS bearer context #1 as specified in TS 36.508 [10], Table 6.6.1-1. |
Reference default EPS bearer context #2 as specified in TS 36.508 [10], Table 6.6.1-1. |
N/A |
|
EPC dedicated bearer context |
Reference dedicated EPS bearer context #1 as specified in TS 36.508 [10], Table 6.6.2-1. |
Reference dedicated EPS bearer context #4 as specified in TS 36.508 [10], Table 6.6.2-1. |
N/A |
|
IP address allocation |
Yes |
Yes |
Yes |
|
IMS registration |
No |
Yes NOTE 1 |
No |
|
SST condition (NOTE 2) |
SST_eMBB |
SST_eMBB |
SST_URLLC |
|
NOTE 1: For PDN establishment the Procedure for IMS signalling according to TS 36.508 [2], subclause 4.5A.3 applies; for PDU establishment the Procedure for IMS signalling according to TS 34.229-5 [47], Annex A.2 applies. NOTE 2: The possible values of the SST condition are defined in Table 4.6.0.1-5. |
|||
Table 4.8.4-2: DNN/APN configurations, second set
|
Configurations |
Config #4 |
Config #5 |
|
DNN/APN type |
miot |
v2x |
|
DNN/APN ID |
pc_APN_ID_MIoT |
pc_APN_ID_V2X |
|
5GC QoS rule |
FFS |
FFS |
|
EPC default bearer context |
N/A |
N/A |
|
EPC dedicated bearer context |
N/A |
N/A |
|
IP address allocation |
Yes |
Yes |
|
IMS registration |
No |
No |
|
SST condition (NOTE 1) |
SST_MIoT |
SST_V2X |
|
NOTE 1: The possible values of the SST condition are defined in Table 4.6.0.1-5. |
||
4.8.5 URSP configurations
4.8.5.1 General
FFS
4.8.5.2 UE Route Selection Policy Rules
Table 4.8.5.2-1: UE Route Selection Policy Rule #1
|
Derivation Path: TS 24.526, Figure 5.2.1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
URSP rules |
1 entry |
||
|
URSP rule |
|||
|
Rule Precedence |
1 |
||
|
Traffic descriptor |
|||
|
Traffic descriptor component type identifier |
‘1000 1000’B |
DNN type |
|
|
Traffic descriptor component |
|||
|
Application descriptors |
Not present |
||
|
IP descriptors |
Not present |
||
|
Domain descriptors |
Not present |
||
|
Non-IP descriptors |
Not present |
||
|
DNN |
FFS |
||
|
Connection Capabilities |
Not present |
||
|
List of Route Selection Descriptors |
Route Selection Descriptor #1 |
Table 4.8.5.3-1 |
|
4.8.5.3 Route Selection Descriptors
Table 4.8.5.3-1: Route Selection Descriptor #1
|
Derivation Path: TS 24.526, Figure 5.2.4 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Route Selection Descriptor Precedence |
1 |
||
|
Route selection descriptor contents |
|||
|
Route selection descriptor component type identifier |
‘0000 0010’B |
S-NSSAI type |
|
|
‘0000 0100’B |
DNN type |
||
|
Route selection descriptor component |
|||
|
SSC Mode Selection |
Not present |
||
|
Network Slice Selection |
FFS |
S-NSSAI type |
|
|
DNN Selection |
FFS |
DNN type |
|
|
PDU Session Type Selection |
Not present |
||
|
Non-Seamless Offload indication |
Not present |
||
|
Access Type preference |
Not present |
||
|
Condition |
Explanation |
|
S-NSSAI type |
The Route selection descriptor component type is S-NSSAI |
|
DNN type |
The Route selection descriptor component type is DNN |