School of Specs 24.501v20.0.0

3GPP 24.501 v20.0.0 — the document's own text

D.6.8 VPS URSP configuration

Taught in 5. Finding your way around TS 24.501 (CT1 — the group that writes what your phone says, in depth), 4. Inside TS 24.501, the document at the centre (CT1 — the group that writes what your phone says, overview).

The purpose of the VPS URSP configuration information element is to transfer the VPS URSP configuration from the PCF to the UE. The VPS URSP configuration contains zero or more tuples. Each tuple contains the tuple ID identifying the tuple, the network descriptor identifying one or more VPLMNs, and zero or more UPSCs of HPLMN's UE policy sections which contain solely one or more UE policy parts with the UE policy part type set to "URSP", such that the URSP rules in those one or more UE policy parts are applicable to the VPLMN and its equivalent PLMN.

The VPS URSP configuration information element is coded as shown in figure D.6.8.1, figure D.6.8.2, figure D.6.8.3, figure D.6.8.4, figure D.6.8.5, figure D.6.8.6, figure D.6.8.7, figure D.6.8.8, figure D.6.8.9, and table D.6.8.1.

The VPS URSP configuration is type 6 information element with a minimum length of 3 octets and a maximum length of 65533 octets.

87654321
VPS URSP configuration IEIoctet 1
Length of VPS URSP configuration contentsoctet 2octet 3
0Spare0Spare0Spare0Spare0Spare0SpareRToctet 4
Tuple 1octet 5*octet a*
Tuple 2octet (a+1)*octet b*
octet (b+1)*octet c*
Tuple Noctet (c+1)*octet z*

Figure D.6.8.1: VPS URSP configuration information element

87654321
Length of tuple contentsoctet a+1octet a+2
Tuple IDoctet a+3
Network descriptoroctet a+4octet e
UPSC 1octet (e+1)*octet (e+2)*
UPSC 2octet (e+3)*octet (e+4)*
octet (e+5)*octet (e+n*2e-2)*
UPSC noctet (e+n*2-1)*octet (e+n*2)* = octet b*

Figure D.6.8.2: Tuple

87654321
Number of network descriptor entriesoctet a+4
Network descriptor entry 1octet (a+5)octet f
Network descriptor entry 2octet (f+1)*octet g*
...octet (g+1)*octet h*
Network descriptor entry moctet (h+1)*octet e*

Figure D.6.8.3: Network descriptor

87654321
Network descriptor entry typeoctet f+1
Network descriptor entry valueoctet (f+2)*octet g*

Figure D.6.8.4: Network descriptor entry

87654321
Number of PLMN IDsoctet (f+2)
PLMN ID 1octet (f+3)octet (f+5)
PLMN ID 2octet (f+6)*octet (f+8)*
...
PLMN ID moctet (m*3+f)*octet (m*3+f+2)* = octet g*

Figure D.6.8.5: Network descriptor entry value for network descriptor entry type set to "one or more VPLMNs"

MCC digit 2MCC digit 1octet f+6
MNC digit 3MCC digit 3octet f+7
MNC digit 2MNC digit 1octet f+8

Figure D.6.8.6: PLMN ID

87654321
Number of MCCsoctet (f+2)
MCC pair 1octet (f+3)octet (f+5)
MCC pair 2octet (f+6)*octet (f+8)*
...
MCC pair moctet (m*3+f)*octet (m*3+f+2)*
Odd MCCoctet (m*3+f+3)*octet (m*3+f+4)* = octet g*

Figure D.6.8.7: Network descriptor entry value for network descriptor entry type set to "one or more MCCs"

MCC 1 digit 2MCC 1 digit 1octet f+6
MCC 2 digit 3MCC 1 digit 3octet f+7
MCC 2 digit 2MCC 2 digit 1octet f+8

Figure D.6.8.8: MCC pair

MCC digit 2MCC digit 1octet (m*3+f+3)
0Spare0Spare0Spare0SpareMCC digit 3octet (m*3+f+4) = octet g

Figure D.6.8.9: Odd MCC

Table D.6.8.1: VPS URSP configuration information element

Replacement type (octet 4, bits 1 and 2)
Bits
21
01per-tuple replacement
10full list of tuples
All other values are reserved.
Tuple ID (octet a+3)
This field contains the binary encoding of the tuple ID. The value of the tuple ID is set by the PCF.
Network descriptor entry type (octet f+1)
Bits
87654321
00000001one or more VPLMNs
00000010one or more MCCs
00000011any VPLMN
All other values are reserved.
If the network descriptor entry type field is set to "one or more VPLMNs" or "one or more MCCs", then the network descriptor entry value field is present. If the network descriptor entry type field is set to "any VPLMN", then the network descriptor entry value field is absent.
Number of PLMN IDs (octet (f+2) of the network descriptor entry value for network descriptor entry type set to "one or more VPLMNs")
The number of PLMN IDs field indicates the number of the PLMN IDs in the network descriptor entry value field.
MCC, Mobile country code (octet f+6 and bits 4 to 1 of octet f+7 of the PLMN ID, octet f+6 and bits 4 to 1 of octet f+7 of the MCC pair, and octet f+8 and bits 8 to 5 of octet f+7 of the MCC pair, octet m*3+f+3 and bits 4 to 1 of m*3+f+4 of the odd MCC)
The MCC field is coded as in ITU-T Recommendation E.212 [42], annex A.
MNC, Mobile network code (bits 8 to 5 of octet f+7, and octet f+8)
The coding of this field is the responsibility of each administration but BCD coding shall be used. The MNC shall consist of 2 or 3 digits. If a network operator decides to use only two digits in the MNC, MNC digit 3 shall be coded as "1111".
Number of MCCs (octet (f+2) of the network descriptor entry value for network descriptor entry type set to "one or more MCCs")
The number of MCCs field indicates the number of the MCCs in the network descriptor entry value field. If the number of MCCs field is an odd value, then the odd MCC field is present otherwise the odd MCC field is absent.
UPSC (octets e+3 to e+4)
This field contains the binary encoding of the UPSC of an UPSI of a UE policy section of the HPLMN (see NOTE), which contains solely one or more UE policy parts with the UE policy part type set to "URSP", such that the URSP rules in those one or more UE policy parts are applicable to the VPLMN and its equivalent PLMN.
NOTE: PLMN ID of the UPSI is not indicated.