Content for TS 24.501 Word version: 18.5.0

1… 3… 4… 4.4… 4.4.3… 4.5… 4.5.3… 4.6… 4.7… 4.9… 4.15… 5… 5.2… 5.3… 5.3.2… 5.3.7… 5.3.19… 5.4… 5.4.1.3… 5.4.2… 5.4.4… 5.4.5… 5.4.6… 5.5… 5.5.1.2.4 5.5.1.2.5… 5.5.1.3… 5.5.1.3.4 5.5.1.3.5… 5.5.2… 5.6… 5.6.2… 6… 6.1.4… 6.2… 6.3… 6.3.2… 6.3.3… 6.4… 6.4.1.4… 6.4.2… 6.5… 7… 8… 8.2.9… 8.3… 9… 9.11.2… 9.11.2.10… 9.11.3… 9.11.3.4… 9.11.3.8… 9.11.3.14… 9.11.3.18C… 9.11.3.29… 9.11.3.33… 9.11.3.39… 9.11.3.45… 9.11.3.50… 9.11.3.53A… 9.11.3.68… 9.11.3.75… 9.11.4… 9.11.4.10… 9.11.4.13… 9.11.4.16… 9.11.4.30… 9.12 10… A… B… C… D… D.6… D.6.3… D.6.8 D.7…

D.6.8 VPS URSP configuration

D.6.8 VPS URSP configuration |R18| p. 1105

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.

Reproduction of 3GPP TS 24.501, Fig. D.6.8.1: VPS URSP configuration information element

Figure D.6.8.1: VPS URSP configuration information element

Reproduction of 3GPP TS 24.501, Fig. D.6.8.2: Tuple

Figure D.6.8.2: Tuple

Reproduction of 3GPP TS 24.501, Fig. D.6.8.3: Network descriptor

Figure D.6.8.3: Network descriptor

Reproduction of 3GPP TS 24.501, Fig. D.6.8.4: Network descriptor entry

Figure D.6.8.4: Network descriptor entry

Reproduction of 3GPP TS 24.501, Fig. D.6.8.5: Network descriptor entry value for network descriptor entry type set to "one or more VPLMNs"

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

Reproduction of 3GPP TS 24.501, Fig. D.6.8.6: PLMN ID

Figure D.6.8.6: PLMN ID

Reproduction of 3GPP TS 24.501, Fig. D.6.8.7: Network descriptor entry value for network descriptor entry type set to "one or more MCCs"

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

Reproduction of 3GPP TS 24.501, Fig. D.6.8.8: MCC pair

Figure D.6.8.8: MCC pair

Reproduction of 3GPP TS 24.501, Fig. D.6.8.9: Odd MCC

Figure D.6.8.9: Odd MCC

Table D.6.8.1: VPS URSP configuration information element


Bits 2 1
0 1	per-tuple replacement
1 0	full list of tuples
All other values are reserved.
Replacement type (octet 4, bits 1 and 2)
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 8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 1	one or more VPLMNs
0 0 0 0 0 0 1 0	one or more MCCs
0 0 0 0 0 0 1 1	any 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 m3+f+3 and bits 4 to 1 of m3+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.