Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.316  Word version:   16.3.0

Top   Up   Prev   Next
1…   4…   4.5…   4.7…   5…   6…   7…   7.2.2…   7.2.3…   7.2.4…   7.3…   7.6…   7.7…   8…   9…   10…   A…

 

9  Policy and Charging Control Framework and Configuration by ACSWord-p. 69
9.0  General
This clause specifies the delta related to Policy and charging control framework defined in TS 23.503 and the configuration of the 5G-RG by the ACS.
9.1  Session management related policy control
9.1.0  General
This clause specifies the delta related to UE policy distribution defined in TS 23.503, clause 6.1.3 for 5G-RG and FN-RG.
9.1.1  Session binding
The session binding mechanism defined in TS 23.503, clause 6.1.3.2.2 applies. In addition, the PDU session parameters considered for session binding are:
  • For IPv6 PDU session type, one or multiple UE IPv6 address or one or multiple IPv6 prefixes /64 or shorter prefixes.
  • For IPv4v6 PDU session type, one UE IPv4 address and one or multiple IPv6 prefixes /64 or shorter prefixes.
9.1.2  Policy Control Request Triggers relevant for SMF and wireline access type
The Policy Control Request Triggers relevant for SMF and wireline access define the conditions when the SMF shall interact again with PCF after a PDU Session established via W-5GAN. PCR triggers defined in Table 6.1.3.5 in TS 23.503 are supported for W-5GAN scenario with the following not supporting ones:
  • PLMN change.
  • Location change (serving area).
  • Location change (serving CN node in 5GS).
  • Location change (serving CN node in EPC).
  • Change of UE presence in Presence Reporting Area.
  • 3GPP PS Data Off status change.
  • GFBR of the QoS Flow can no longer (or can again) be guaranteed.
  • UE resumed form suspend data.
  • Manageable Ethernet Port detected.
  • Port Management Information Container available.
Additionally, the new triggers defined in clause 9.7 for IPTV service are also applied for a 5G-RG connected via W-5GAN scenario.
Up
9.2  Network Functions and entitiesWord-p. 70
9.2.1  General
This clause specifies the delta related to Network Function and entities defined in TS 23.503, clause 6.2 for 5G-RG and FN-RG.
The functional description of the NEF, NWDAF, UDR and CHF applies as described in TS 23.503.
9.2.2  Policy Control Function (PCF)
The PCF provides session management policy control for single access PDU sessions over non 3GPP wireline and multiaccess PDU sessions over both 3GPP and non 3GPP wireline access.
The session management related functionality defined in TS 23.503, clause 6.2.1 applies for 5G-RG and FN-RG, with the following modifications for W-5GAN:
  • Determination of Maximum Packet Loss Rate for UL/DL does not apply.
  • QoS Notification Control does not apply.
NOTE:
No requirements to support MPS or Mission Critical Services over wireline non 3GPP access are defined in this Release.
The non-session management related functionality defined in TS 23.503, clause 6.2.2 applies for 5G-RG and FN-RG, with the following modifications for W-5GAN:
  • the UE-AMBR control by the Visited Network does not apply.
  • the Service Area Restrictions for a FN-BRG does not apply.
  • the 5G-RG and FN-RG replaces the UE.
  • the PCF provides Access and mobility related policy control as described in clause 9.5.1.
  • the PCF provides UE access selection and PDU session selection
  • the PCF provides the UE access selection and PDU Session selection related policy control as defined in clause 9.5.2.
The policy control subscription data defined in TS 23.503 applies for 5G-RG and FN-RG connected via W-5GAN access, except for the definition of MPS data for a 5G-RG or FN-RG that is not applicable in this Release.
The policy control subscription data defined in TS 23.503 applies for a 5G-RG and FN-RG connected via W-5GAN, except for the definition of MPS data for a 5G-RG or FN-RG that is not applicable in this Release.
The V-PCF and H-PCF functionality does not apply for session and non-session policy control for 5G-RG and FN-RG users in this Release.
Up
9.2.3  Session Management Function (SMF)
The SMF enforces policy decisions related to service data flow detection, authorized QoS, charging, gating, traffic usage reporting, packet routing and forwarding and traffic steering for single access PDU session over W-5GAN and multiaccess PDU sessions over W-5GAN and 3GPP as defined in TS 23.503, clause 6.2.2 with the following modifications for W-5GAN:
  • Reporting RAN/NAS Release Cause over wireline is not supported.
  • The Maximum Packet Loss Rate for UL and DL is not forwarded to the wireline non-3GPP access.
Up
9.2.4  Application Function (AF)Word-p. 71
The AF requests for policy control functionality described in TS 23.503, clause 6.2.3 applies with the following clarification for W-5GAN:
  • Indication that the QoS targets can no longer (or can again) be fulfilled is not supported.
NOTE:
No requirements to support MPS or Mission Critical Services over wireline non 3GPP access are defined in this release.
9.2.5  Access and Mobility Management Function (AMF)
The policy control related functionality defined in TS 23.503 applies, with the clarification that the UE-AMBR control by the visited network is only applicable for a 5G-RG registered over 3GPP access.
9.3  Policy and charging control rule
Policy and charging control rule for 5G-RG PDU Session is described in TS 23.503, clause 6.3 with the clarification and difference in this clause.
9.3.1  PCC rule information to support IPTV service
  • PCF shall take Multicast Access Control list described in clause 7.7.1.1.4 as input to policy decision in the case of PDU Session used for IPTV service. PCC rules sent to SMF may indicate allowed IP Multicast Addressing information as defined in Table 9.3.1-1.
  • The "Gate status" is not applicable to IGMP transmitted over PDU Session used for IPTV service.
Comparing to Table 6.3.1 in TS 23.503, additional PCC rule information for PDU Session used for IPTV service is described in Table 9.3.1-1.
Information name
Description
Category
PCF permitted to modify for a dynamic PCC rule in the SMF
Differences compared with table 6.3. in TS 23.203

IPTV
This part defines the additional PCC rule information for PDU Session used for IPTV service.
IP Multicast traffic control information
indicates whether the service data flow, corresponding to the service data flow template, may be allowed or not allowed (NOTE 1).
Optional
Yes
Added

NOTE 1:
The corresponding IP Multicast Addressing information in provided in the SDF template. The SDF template may refer to "any" IP Multicast address (for example allowing the user to access to receive any IPTV channel).

Up
9.4  PDU Session related policy information
This clause specifies the delta related to PDU session related policy information defined in TS 23.503, clause 6.4 for 5G-RG and FN-RG.
9.5  Non-session management related policy informationWord-p. 72
9.5.1  Access and mobility related policy information
This clause specifies the delta related to Access and Mobility related policy information defined in TS 23.503, clause 6.1.2.1 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 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. 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 in 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. 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 TS 23.503, clause 6.5.
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.
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 enable.
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.
Up
9.5.2  UE access selection and PDU Session selection related policy informationWord-p. 73
9.5.2.1  5G-RG
This clause specifies the delta related to UE policy distribution defined in TS 23.503, clause 6.1.2.2 and related to URSP defined in TS 23.503, clause 6.6. 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 TS 23.503, clause 6.1.2.2 are applicable as follows:
  • Roaming is not applicable to W-5GAN access in this release of specification.
Up
9.5.2.2  FN-RG
This clause specifies the delta related to UE policy distribution defined in TS 23.503, clause 6.1.2.2 and related to URSP defined in TS 23.503, clause 6.6 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.
NOTE 1:
The FN-RG initiates the W-5GAN session with the W-AGF, for example PPPoE, and consequently the W-AGF does not receive any indication of the application used for that session (e.g. whether it used for web browsing or for any specific application) and any DNN indication from the application, hence the policy including the Application Descriptors and/or DNN will never match the traffic.
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 TS 23.503, clause 6.1.2.2 are applicable with the following modification:
  • Roaming is not applicable to W-5GAN access in this release of specification.
Up
9.5.3  Policy Control Request Triggers relevant for AMF and wireline access typeWord-p. 74
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 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:
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)
RG-TMBR
The Subscribed RG-TMBR 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.
Up
9.6  Configuration and Management from ACSWord-p. 75
9.6.1  General
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].
NOTE:
Whether and how to use the objects received from the ACS by RG is out of 3GPP scope.
9.6.2  ACS Discovery
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] clause 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 clause 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:
  1. ACS information received during the DHCP process.
  2. ACS information received during the PDU session establishment procedure from SMF PCO. This applies for 5G-RG only.
  3. The pre-configured ACS information in the RG.
Up
9.6.3  ACS Information Configuration by the 3rd party
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.
Up
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.
Up
9.6.4  URSP for FN RGWord-p. 76
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 (WT-456 [9] and WT-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).
NOTE 1:
The VLAN configuration depends on the served FN RG as a W-AGF service area can serve different Wireline access networks with different VLAN configurations.
The corresponding W-AGF configuration about parameters of the PDU Sesssions 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 WT-470) 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.
NOTE 2:
UDR policy data related with a FN-RG subscription (UE Policy Section, see clause 5.4.2.3 of TS 29.519) can be configured accordingly.
Up
9.7  new PCRT (Policy Control Request Trigger)
The Policy Control Request Triggers relevant for SMF are described in TS 23.503, clause 6.1.3.5 with the clarification and difference shown in this clause.
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.

NOTE:
The corresponding notification can be used by the PCF to manage Preview Rights related with an IP multicast flow corresponding to an IPTV channel. In this case the PCF is responsible to remove the 5G RG authorization to receive an IP multicast flow when the preview duration has elapsed.
Up

Up   Top   ToC