Content for TS 23.316 Word version: 18.2.0

1… 4… 4.5… 4.7… 4.10… 4.10b… 4.11… 5… 6… 7… 7.2.2… 7.2.3… 7.2.4… 7.3… 7.6… 7.7… 8… 9… 9.5… 10… A…

9.5 Non-session management related policy information 9.5.1 Access and mobility related policy information 9.5.2 UE access selection and PDU Session selection related policy information 9.5.3 Policy Control Request Triggers relevant for AMF and wireline access type 9.6 Configuration and Management from ACS 9.6.1 General 9.6.2 ACS Discovery 9.6.3 ACS Information Configuration by the 3rd party 9.6.4 URSP for FN RG 9.7 new PCRT (Policy Control Request Trigger) 9.8 AF-based service parameter provisioning for TNAP ID 9.9 Policy control subscription information management
...

9.5 Non-session management related policy information p. 81

9.5.1 Access and mobility related policy information p. 81

This clause specifies the delta related to Access and Mobility related policy information defined in clause 6.1.2.1 of TS 23.503 for 5G-RG and FN-RG.

The access and mobility policy control encompass the management of service area restrictions for a 5G-BRG or a 5G-CRG connecting to 5GC via W-5GAN or simultaneously via NG-RAN and W-5GAN.

The management of service area restrictions enables the PCF of the serving PLMN or SNPN to modify the service area restrictions based on operator defined policies at any time, either by expanding a list of allowed GLIs or HFC Node IDs or by reducing the list of non-allowed GLIs or HFC Node IDs. Operator defined policies in the PCF may depend on input data such as time of day, or UE context information provided by other NFs, etc.

The AMF reports the subscribed service area restrictions in NG-RAN received from UDM during 5G-RG Registration in NG-RAN procedure when local policies in the AMF indicate that Access and Mobility Control is enable within the PLMN or SNPN. The AMF may request update of the service area restrictions applicable to NG-RAN when the policy control request triggers listed in clause 6.1.2.5 of TS 23.503 are met.

The AMF reports the subscribed service area restrictions in W-5GAN received from UDM during 5G-RG Registration in W-5GAN procedure when local policies in the AMF indicate that Access and Mobility Control is enable within the PLMN or SNPN. The AMF may request update of the service area restrictions applicable to W-5GAN when the policy control request triggers listed in clause 9.5.3 are met.

The AMF receives the modified service area restrictions from the PCF and then use them as described in clause 4.3.3.3.

No mobility events, such a change of UE location or change of AMF applies when provisioning the service area restrictions for a 5G-BRG or a 5G-CRG when connected via W-5GAN.

The PCF may provide the service area restrictions applicable to a 5G-RG connected to 5GC via W-5GAN or via NG-RAN or simultaneously connected to 5GC via W-5GAN and NG-RAN to AMF. The PCF may provide the service area restrictions applicable to a FN-CRG to the AMF.

The Service Area Restrictions provided to AMF for a 5G-RG connected via NG-RAN is according to the information listed in listed in clause 6.5 of TS 23.503.

The Service Area Restrictions provided to AMF for a 5G-RG connected via W-5GAN is according to the information listed in Table 9.5-1.

For a 5G-RG simultaneously connected to 5GC via W-5GAN and NG-RAN the PCF provides Service Area Restrictions for both W-5GAN and NG-RAN.

The Service Area Restrictions provided to AMF for a FN-CRG connected via W-5GAN is according to the information listed in Table 9.5-1.

Table 9.5-1: Access and mobility related policy control information for 5G-RG and FN-CRG accessing via W-5GAN

Information name	Description	Category	PCF permitted to modify in a AM context in the AMF	Scope
Service Area Restrictions for a 5G-BRG	This part defines the service area restrictions applicable for a 5G-BRG
List of allowed GLIs	List of allowed GLIs (NOTE 2) (NOTE 3).	Conditional (NOTE 1)	Yes	AM context
List of non-allowed GLIs	List of non-allowed GLIs (NOTE 3).	Conditional (NOTE 1)	Yes	AM context
Service Area Restrictions for a 5G-CRG or for a FN-CRG	This part defines the service area restrictions applicable for a 5G-CRG or for a FN-CRG
List of allowed HFC Node IDs	List of allowed HFC Node IDs (NOTE 2)	Conditional (NOTE 1)	Yes	AM context
List of non-allowed HFC Node IDs	List of non-allowed HFC Node IDs (NOTE 2).	Conditional (NOTE 1)	Yes	AM context
NOTE 1: If service area restrictions is enabled. NOTE 2: Either the list of allowed (GLIs or HFC Node IDs) or the list of non-allowed (GLIs or HFC Node IDs) are provided by the PCF.

The list of allowed GLIs or the list of allowed HFC Node IDs indicates the locations where the 5G-RG is allowed to be registered, see clause 4.3.3.3 for the description on how AMF uses this information.

9.5.2 UE access selection and PDU Session selection related policy information p. 82

9.5.2.1 5G-RG p. 82

This clause specifies the delta related to UE policy distribution defined in clause 6.1.2.2 of TS 23.503 and related to URSP defined in clause 6.6 of TS 23.503 for 5G-RG.

If the PCF provides the URSP policy to the 5G-RG, the PCF should neither include NSWO indication nor any ANDSP policies. The 5G-RG shall ignore any NSWO indication or any ANDSP policies if received from the 5GC. The 5G-RG shall use the URSP policy as specified in TS 23.503, for example for the association of application and PDU session, slices, etc.

The URSP indicates for the application of Auto-Configuration Server (ACS) which PDU session type, NSSAI and/or DNN is to be used. The 5G-RG establishes the connectivity to the management entity (e.g. ACS) via user plane connection on a PDU session according to the URSP.

UE Policy procedures defined in clause 6.1.2.2 of TS 23.503 are applicable as follows:

Roaming is not applicable to W-5GAN access in this release of specification.

In order to support the case when AUN3 devices may be connected via 5G-RG, specific URSP rules may be configured by the PCF for the SUPI associated with the AUN3 device.

UE Route Selection Policy information targeting an AUN3 device (i.e. sent to a 5G-RG in the NAS connection corresponding to an AUN3 device) follows the structure defined in clause 6.2.2 of TS 23.503 with following differences:

As an AUN3 can have only one PDU Session, its URSP shall contain a match all TD.

In order to support the case when NAUN3 devices may be connected via 5G-RG, specific URSP rules may be configured by the PCF on 5G-RG.

URSP rules for NAUN3 devices connected to 5G-RG follow the structure defined in clause 6.6.2 of TS 23.503 and may contain any combination of the following traffic descriptors:

IP Descriptors: For IP traffic from NAUN3 devices connected to 5G-RG, IP descriptors are matched against header information contained in IP packets sent by NAUN3 devices; IP descriptors are only applicable for traffic from NAUN3 devices if network address translation (NAT) is performed for that traffic.
Non-IP descriptors: For Ethernet traffic from NAUN3 devices connected to 5G-RG, Non-IP descriptors are matched against header information contained in Ethernet frames sent by NAUN3 devices.
Connectivity Group ID: For traffic from a NAUN3 device connected to 5G-RG, Connectivity Group ID in the URSP rule is matched against the Connectivity Group ID that the NAUN3 device is associated with (see clause 4.10b).

9.5.2.2 FN-RG p. 83

This clause specifies the delta related to UE policy distribution defined in clause 6.1.2.2 of TS 23.503 and related to URSP defined in clause 6.6 of TS 23.503 for 5G-RG.

If the PCF provides the URSP rules related to FN-RG to the W-AGF, the PCF should not include NSWO indication. The PCF should not provide ANDSP policies. The W-AGF shall ignore any NSWO indication or any ANDSP policies if received from the 5GC.

The W-AGF shall use the URSP policy as specified in TS 23.503 with the following modifications:

Traffic descriptor;
the Application Descriptor is not applicable;
the DNN is not applicable;
The Connection Capabilities Descriptor is not applicable.

If the PCF sends UE policy (e.g. URSP), the W-AGF shall store it for the duration that FN-RG is registered. When the FN-RG is deregistered, the UE policy can be removed. Whether it is done immediately, or after a certain period (e.g. for quick recovery from disconnection or fault), or stored permanently it is left to implementation and is out of the scope of this TS.

If the URSP for the FN-RG are present in W-AGF (e.g. pre-configured or received from PCF) the W-AGF shall use them as defined for a UE with URSP.

If the URSP for the FN-RG are not present in W-AGF, the W-AGF acts based on local configuration, as defined for a UE without URSP.

It is assumed that the FN-RG configuration (provided via BBF TR-069 [18]/BBF TR-369 [19]), the URSP rules and the local configuration in the W-AGF are consistent with each other. If the W-AGF detects conflicting requirements based on URSP, local configuration, or requests from the FN-RG, then the URSP rules takes precedence since they are considered the most updated and aligned to the current 5G system conditions.

UE Policy procedures defined in clause 6.1.2.2 of TS 23.503 are applicable with the following modification:

Roaming is not applicable to W-5GAN access in this release of specification.

9.5.3 Policy Control Request Triggers relevant for AMF and wireline access type p. 83

The Policy Control Request Triggers relevant for AMF and wireline access type define the conditions when the AMF shall interact again with PCF after the AM Policy Association. PCR triggers defined in Table 6.1.2.5-1 in TS 23.503 are supported for W-5GAN scenario with the following not supporting ones:

Location change (tracking area).
Change of UE presence in Presence Reporting Area.
RFSP index change.
UE-AMBR change.
PLMN change.

Additionally, the following PCR triggers are added regarding the wireline access type:

Table 9.5.3-1: Policy Control Request Triggers relevant for AMF and wireline access type

Policy Control Request Trigger	Description	Condition for reporting
Access Type change (NOTE 1)	The Access Type and the RAT Type has changed	PCF (AM Policy)
NOTE 1: The RAT type is reported for 3GPP access, or when the 5G-RG or FN-RG registers over wireline access (i.e. W-AGF).

The UE Policy related PCR triggers like location change, PRA change and PLMN change are not applicable for wireline access.

9.6 Configuration and Management from ACS p. 84

9.6.1 General p. 84

Once the 5G-RG connects to 5GC, the 5G-RG shall establish a PDU session for interaction with the ACS to support the functionalities as described in BBF TR-069 [18] or in BBF TR-369 [19].

9.6.2 ACS Discovery p. 84

The ACS information may be associated to the RG subscription in the UDM / UDR. In this case the ACS information may be provided to the RG with at least one of the following methods:

via DHCP interaction if the RG sends DHCP signalling indicating a request for ACS information. The RG sends a DHCPv4 request including a request for ACS information and receives ACS information from the DHCP as specified in BBF TR-069 [18] section 3.1 for ACS Discovery or in BBF TR-369 [19] R-DIS.1 and R-DIS.2.
during the PDU session establishment procedure via PCO (protocol Configuration Option) sent in N1 SM message if the 5G-RG has asked to be provided with ACS information via PCO. This applies for 5G-RG only.

The ACS information (e.g. URL of the ACS) is defined in BBF TR-069 [18] or in BBF TR-369 [19].

If the RG performs ACS discovery via DHCP process and the SMF is not the DHCP server (e.g. in the case of Ethernet PDU session), the ACS URL is provided by the external DHCP server. In this case, the whole process is transparent to the 5GC and the 5GC is not aware of the ACS information. If the RG performs ACS discovery via DHCP process and the SMF is the DHCP server the ACS information is provided by SMF as part of DHCP process and the SMF shall support the DHCP procedure defined in BBF TR-069 [17] Amendment 6 section 3.2 or in USP (BBF TR-369 [19]).

If the SMF is to provide ACS information to the RG (via PCO or DHCP), it gets this ACS information from SMF subscription data.

The request of ACS information via PCO or via DHCP are mutually exclusive.

The RG may be pre-configured with an ACS information.

The 5G-RG shall consider the ACS information received with the following descending priority order:

ACS information received during the DHCP process.
ACS information received during the PDU session establishment procedure from SMF PCO. This applies for 5G-RG only.
The pre-configured ACS information in the RG.

9.6.3 ACS Information Configuration by the 3rd party p. 85

The ACS information may be configured by a 3rd party AF to the 5GC per subscriber when the SMF is to provide ACS information to the RG. Subsequently, the ACS discovery via PCO or via DHCP with the DHCP server in the SMF may apply as described in clause 9.6.2.

Reproduction of 3GPP TS 23.316, Fig. 9.6.3-1: ACS information configuration procedure

Figure 9.6.3-1: ACS information configuration procedure

The ACS information configuration procedure enables the 3rd party AF to configure the ACS information (e.g. URL or IP address) to the 5GC.

Step 1.

The 3rd party AF provides the ACS information, in the Nnef_ParameterProvision_Update Request to the NEF as in step 1 of TS 23.502 Figure 4.15.6.2-1.

Step 2.

As in step 2 of TS 23.502 Figure 4.15.6.2-1 where the provisioned data is the ACS information.

Step 3.

As in steps 3 and 4 of TS 23.502 Figure 4.15.6.2-1 where the provisioned data is the ACS information.

Step 4.

As in step 5 of TS 23.502 Figure 4.15.6.2-1.

Step 5.

As in step 6 of TS 23.502 Figure 4.15.6.2-1.

Step 6.

As in step 6 of TS 23.502 Figure 4.15.6.2-1 in order to update SMF with ACS information.

9.6.4 URSP for FN RG p. 85

A W-AGF needs to be able to determine the (DNN, S-NSSAI) parameters of the PDU Sessions it requests on behalf of a FN RG. The W-AGF requests such PDU Sessions upon data trigger (e.g. PPPoE , DHCP, etc.) received over a data path identified by a VLAN and a GLI; this is defined in BBF specifications (BBF TR-456 [9] and BBF TR-470 [38]).

Thus the W-AGF needs to be configured to request different PDU Sessions for different VLAN(s) terminated at different FN RG(s).

The corresponding W-AGF configuration about parameters of the PDU Sessions to request for a GLI corresponds to URSP that the W-AGF receives from the PCF for a SUPI corresponding to a GLI.

The URSP(s) may be used to map VLAN(s) at transport level (S-tags as defined in BBF TR-470 [38]) on the V interface of the W-AGF (identifying the target service of the corresponding data flows, e.g. internet / IMS Voice / IPTV) towards Route Selection components including PDU Session type, DNN, S-NSSAI, SSC mode, etc.

9.7 new PCRT (Policy Control Request Trigger) p. 86

The Policy Control Request Triggers relevant for SMF are described in clause 6.1.3.5 of TS 23.503 with the clarification and difference shown in this clause.

Table 9.7-1

Policy Control Request Trigger	Description	Difference compared with Table 6.2 and Table A.4.3-2 in TS 23.203	Conditions for reporting	Motivation
5G-RG join to a multicast group	The 5G-RG has joined to an IP Multicast Group (NOTE 1).	New	PCF	To support IPTV as defined in clause 7.7.1
5G-RG Leave to a multicast group	The 5G-RG has left an IP Multicast Group (NOTE 1).	New	PCF	To support IPTV as defined in clause 7.7.1
NOTE 1: When the SMF reports this condition it indicates the corresponding IP multicast Addressing information.

9.8 AF-based service parameter provisioning for TNAP ID |R18| p. 86

To support location dependent policies when a UE connects using trusted non-3GPP access procedures via a TNAP collocated with a 5G-RG, as described in Figure 4.10-1, an AF may provide one or more TNAP IDs for a UE. A TNAP IDs provided by an AF refers to a TNAP that is collocated with a 5G-RG.

The guidance provided by the AF is sent to the HPLMN of the UE and may apply to a single UE identified by GPSI The request cannot be sent with Any UE or a group of UE as a target.

For TNAP service parameter provisioning (i.e., creating, updating and deleting), the Nnef_ServiceParameter service defined in clause 4.15.6.7 of TS 23.502 is performed with the following modification:

Service Description contains an AF service Identifier indicating that the request is for providing TNAP information.
The GPSI of the target UE is provided.
Service Parameters include TNAP ID(s).

The PCF may compare the TNAP ID provided by the AF with the TNAP ID received in the User Location Information when the UE connects via trusted non-3GPP access. The PCF may apply different policies depending on whether UE is at the TNAP/RG indicated by the AF or not. In case the PCF has both subscribed TNAP ID and AF-provided TNAP ID, the PCF decides based on configuration whether to apply both or one of them.

9.9 Policy control subscription information management |R18| p. 86

This clause specifies the delta related to policy control subscription information defined in clause 6.2.1.3 of TS 23.503 for 5G-RG and FN-RG.

To support that the PCF of a UE may, as described in clause 4.10, take the TNAP ID into account in policy decisions when the UE connects via trusted non-3GPP access over wireline access, following information may be supported in PDU Session policy control subscription information for the UE that is defined in Table 6.2-2 of TS 23.503:

Table 9.9-1: Extract of Table 6.2-2 of TS 23.503 [4]

Information name	Description	Category
List of TNAP ID(s)	The list of identifiers of TNAP collocated with 5G-RG associated with the subscriber	Optional