Extend Npcf_EventExposure by usage monitoring events

Abstract

Systems and methods for event notification in a core network of a cellular communication system are disclosed herein. In one embodiment, a method performed by a first policy and control function (PCF) associated with access management (AM) policy provisioning for a user equipment (UE), wherein the first PCF is included in a core network of a cellular communication system, includes subscribing to an event exposure service of a second PCF associated with session management (SM) policy provisioning for the UE. The method further includes receiving a report from the second PCF in response to subscribing to the event exposure service of the second PCF. In this way, separate deployments of the first PCF and the second PCF are enabled, and the first PCF, which is associated with AM policy provisioning for the UE, can still enforce the AM policy for the UE, e.g., based on UE data usage, e.g., for a particular service package.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims the benefit of provisional patent application serial number 62 / 969,367, filed February 3, 2020, the disclosure of which is incorporated herein in its entirety by this reference. TECHNICAL FIELD

[0003] The present disclosure relates to cellular communication systems, and more specifically, to event exposure in core networks of cellular communication systems. BACKGROUND

[0004] In the Third Generation Partnership Project (3GPP) Fifth Generation System (5GS), the Npcf_EventExposure service is provided by the Policy and Control Function (PCF) and enables a Network Function (NF) to subscribe to PCF events for a group of User Equipment (UE) or any UE accessing a combination of Data Network Name (DNN) and Single-Network Slice Selection Assistance Information (S-NSSAI) and obtain notifications about the PCF events. The Npcf_EventExposure service is described in 3GPP Technical Specification (TS) 23.502 V16.3.0, section 5.2.5.7, reproduced in the following excerpt from 3GPP TS 23.502 V16.3.0.

[0005] ********** Start of excerpt from 3GPP TS 23.502 **********

[0006] 5.2.5.7 Npcf_EventExposure service

[0007] 5.2.5.7.1 Overview

[0008] Service description: This service enables an NF to subscribe to PCF events for a group of UEs or any UE accessing a combination of (DNN, S-NSSAI) and obtain notifications about the PCF events.

[0009] These events that can be subscribed to by an NF consumer are described in TS 23.503

[20] clause 6.1.3.18.

[0010] The following service operations are defined for the Npcf_EventExposure service:

[0011] - Npcf_EventExposure_Subscribe.

[0012] - Npcf_EventExposure_UnSubscribe.

[0013] - Npcf_EventExposure_Notify.

[0014] 5.2.5.7.2 Npcf_EventExposure_Subscribe service operation

[0015] Service operation name: Npcf_EventExposure_Subscribe.

[0016] Description: The consumer NF uses this service operation to subscribe or modify event reporting for a group of UEs or any UE accessing a combination of (DNN, S-NSSAI).

[0017] NF consumer: NEF.

[0018] Input (mandatory): NF ID, target of event reporting (internal group identifier, or indication of targeting any UE accessing a combination of (DNN, S-NSSAI)), event ID(s) as defined in clause 5.2.5.7.1, notification target address (+ notification correlation ID) as defined in table 4.15.1-1, and event reporting information.

[0019] Input (optional): Event filter associated with each event ID.

[0020] Output (mandatory): Operation execution result indication. When the subscription is accepted: subscription correlation ID.

[0021] Output (optional): First corresponding event report (see clause 4.15.1) if corresponding information is available.

[0022] The NF consumer subscribes to event notifications by invoking Npcf_EventExposure to the PCF. The PCF allocates a subscription correlation ID for this subscription and responds to the consumer NF with this subscription correlation ID. The event identification of the receiving NF ID shall receive event reports for the NF.

[0023] 5.2.5.7.3 Npcf_EventExposure_Unsubscribe service operation

[0024] Service operation name: Npcf_EventExposure_Unsubscribe.

[0025] Description: The NF consumer uses this service operation to unsubscribe a group of UEs or any UE accessing a combination of (DNN, S-NSSAI) from a specific event.

[0026] Input (mandatory): Subscription correlation ID.

[0027] Input, optional: None.

[0028] Output (mandatory): Indication of operation execution result.

[0029] Output, optional: None.

[0030] 5.2.5.7.4 Npcf_EventExposure_Notify service operation

[0031] Service operation name: Npcf_EventExposure_Notify.

[0032] Description: This service operation reports events to consumers that have previously subscribed.

[0033] Input (mandatory): Event ID, corresponding UE ID (GPSI), notification correlation information, timestamp.

[0034] Input (optional): None.

[0035] Output (mandatory): None.

[0036] ********** End of excerpt from 3GPP TS 23.502 **********

[0037] The Npcf_EventExposure service is provided by the PCF as defined in “Table 5.2.5.1-1: NF services provided by PCF” in 3GPP TS 23.502, an excerpt of which is shown in Table 1 below:

[0038] Table 1. Npcf_EventExposure

[0039]

[0040] The Npcf_EventExposure service follows the mechanism defined by the EventExposure framework, which defines the EventIDs that the PCF can provide and the targets for event reporting to identify the target UEs in the PCF. The EventID Public Land Mobile Network (PLMN) identity (ID) change and access type change are defined in 3GPP TS 23.503 V16.3.0, as shown in Table 2.

[0041] Table 2. Event IDs reported by PCF

[0042] SUMMARY

[0043] Systems and methods for event notification in a core network of a cellular communication system are disclosed herein. In one embodiment, a method performed by a first policy and control function (PCF) associated with providing access management (AM) policy for a user equipment (UE), wherein the first PCF is comprised in a core network of a cellular communication system, the method comprising subscribing to an event exposure service of a second PCF associated with providing session management (SM) policy for the UE. The method further comprises receiving a report from the second PCF in response to subscribing to the event exposure service of the second PCF. In this way, separate deployments of the first PCF and the second PCF are enabled, and the first PCF associated with providing AM policy for the UE can still enforce the AM policy for the UE, e.g., based on UE data usage, e.g., for a particular service package.

[0044] In one embodiment, the event exposure service supports reporting usage monitoring information for the UE, and the report received from the second PCF comprises the usage monitoring information for the UE. In one embodiment, the usage monitoring information comprises information reporting that a predefined or preconfigured usage threshold has been reached by the UE. In one embodiment, the usage monitoring information comprises information reporting that a predefined or preconfigured usage threshold has been reset.

[0045] In one embodiment, the method further comprises receiving a request from an access and mobility management function (AMF) to create or modify an AM policy for the UE. Further, subscribing to the event exposure service of the second PCF comprises subscribing to the event exposure service of the second PCF in response to receiving the request from the AMF to create or modify the AM policy for the UE. In one embodiment, the method further comprises sending AM related policy information for the UE to the AMF. In one embodiment, the AM related policy information comprises a service area restriction. In one embodiment, the first PCF modifies a radio access technology (RAT) / frequency selection priority (RFSP) index used by the AMF to perform radio resource management functions with respect to the UE based on one or more operator policies that take into account the received usage monitoring information for the UE.

[0046] Corresponding embodiments of a network node for implementing the first PCF associated with providing AM policy for the UE are also disclosed. In one embodiment, a network node for implementing the first PCF associated with providing AM policy for the UE, wherein the first PCF is comprised in a core network of a cellular communication system, is adapted to subscribe to an event exposure service of a second PCF associated with providing SM policy for the UE. The network node is further adapted to receive a report from the second PCF in response to subscribing to the event exposure service of the second PCF.

[0047] In one embodiment, a network node for implementing a first PCF providing AM policy association for a UE, wherein the first PCF is comprised in a core network of a cellular communications system, comprises processing circuitry configured to cause the network node to subscribe to an event exposure service of a second PCF providing SM policy association for the UE. The processing circuitry is further configured to cause the network node to receive a report from the second PCF in response to subscribing to the event exposure service of the second PCF.

[0048] Embodiments of a method performed by a second PCF providing SM policy association for a UE are also disclosed, wherein the second PCF is comprised in a core network of a cellular communications system. In one embodiment, the method comprises receiving, from a first PCF providing AM policy association for the UE, a message subscribing to an event exposure service of the second PCF. The method further comprises sending, to the first PCF (210-AM), a report comprising usage monitoring information of the UE in response to receiving the message subscribing to the event exposure service of the second PCF.

[0049] In one embodiment, the event exposure service supports reporting usage monitoring information of the UE, and the report received from the second PCF comprises usage monitoring information of the UE. In one embodiment, the usage monitoring information comprises information reporting that the UE has reached a predefined or preconfigured usage threshold. In one embodiment, the usage monitoring information comprises information reporting that a predefined or preconfigured usage threshold has been reset.

[0050] Corresponding embodiments of a network node for implementing a second PCF providing SM policy association for a UE are also disclosed, wherein the second PCF is comprised in a core network of a cellular communications system. In one embodiment, the network node is adapted to receive, from a first PCF providing AM policy association for the UE, a message subscribing to an event exposure service of the second PCF. The network node is further adapted to send, to the first PCF, a report comprising usage monitoring information of the UE in response to receiving the message subscribing to the event exposure service of the second PCF.

[0051] In another embodiment, a network node for implementing a second PCF providing SM policy association for a UE, wherein the second PCF is comprised in a core network of a cellular communications system, comprises processing circuitry configured to cause the network node to receive, from a first PCF providing AM policy association for the UE, a message subscribing to an event exposure service of the second PCF. The processing circuitry is further configured to cause the network node to send, to the first PCF, a report comprising usage monitoring information of the UE in response to receiving the message subscribing to the event exposure service of the second PCF.

[0052] In one embodiment, a method performed in a core network of a cellular communications system includes, at a first PCF that provides an AM policy association for a UE, subscribing to an event exposure service of a second PCF that provides an SM policy association for the UE, and in response to subscribing to the event exposure service of the second PCF, receiving a report from the second PCF. The method further includes, at the second PCF that provides the SM policy association for the UE, receiving a message from the first PCF that subscribes to the event exposure service of the second PCF, and in response to receiving the message that subscribes to the event exposure service of the second PCF, sending a report to the first PCF.

[0053] In one embodiment, the event exposure service supports reporting usage monitoring information for the UE, and the report received from the second PCF includes the usage monitoring information for the UE. In one embodiment, the usage monitoring information includes information that the UE has reached a predefined or preconfigured usage threshold.

[0054] In one embodiment, the method further includes, at the first PCF, receiving a request from an AMF to create or modify an AM policy for the UE. Further, subscribing to the event exposure service of the second PCF includes subscribing to the event exposure service of the second PCF in response to receiving the request from the AMF to create or modify the AM policy for the UE. In one embodiment, the method further includes, at the first PCF, sending AM-related policy information for the UE to the AMF. In one embodiment, the first PCF modifies a RAT / RFSP index used by the AMF to perform radio resource management functions with respect to the UE based on one or more operator policies that take into account the received usage monitoring information for the UE. BRIEF DESCRIPTION OF DRAWINGS

[0055] The accompanying drawings, which are incorporated in and form a part of the specification, illustrate several aspects of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0056] Figure 1 An example of a cellular communications system in which embodiments of the present disclosure can be implemented is shown;

[0057] Figure 2 And Figure 3 An example of a cellular communications system in which embodiments of the present disclosure can be implemented is shown; Figure 1

[0058] Figure 4 ​Operation of an Access and Mobility (AM) policy and control function (PCF) (i.e., AM-PCF) and a session management (SM) PCF (i.e., SM-PCF) is shown, where, according to one example embodiment of the present disclosure, the AM-PCF subscribes to and fetches information from the SM-PCF using an extended Npcf_EventExposure service;

[0059] Figures 5 to 7 is a schematic block diagram of an example embodiment of a network node; and Figures 8 to 13 are various figures of changes made to Third Generation Partnership Project (3GPP) Technical Specifications (TSs) 23.502 V16.3.0 and 3GPP TS 23.503 V16.3.0 according to example embodiments of the present disclosure. DETAILED DESCRIPTION

[0060] The embodiments set forth below represent the necessary information to enable those with ordinary skill in the art to practice the embodiments and illustrate the best modes of practicing the embodiments. Upon reading the following description, one skilled in the art will understand how to implement and use the concept of the present disclosure and will recognize the same applies to and is applicable to other embodiments of the present disclosure not specifically described here. It will be understood that these concepts and applications fall within the scope of the present disclosure.

[0061] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to the embodiments set forth herein; rather, they are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0062] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the technical field of the relevant art, unless a different meaning is explicitly given and / or clearly contradicts the context. All references to a / an / the item, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one and only one instance of that item, apparatus, component, means, step, etc., unless explicitly indicated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless explicitly specified and / or inherently required. Any of the embodiments of any of the aspects disclosed herein can be applied to any other embodiment of any aspect of the present disclosure, wherever technically possible. Similarly, any advantages, features, functions, steps, etc. of any of the aspects of the disclosure can be applied to any other embodiment of any aspect of the disclosure, wherever technically possible. Further objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

[0063] Radio node: As used herein, a “radio node” is a radio access node or a wireless communication device.

[0064] Radio access node: As used herein, a “radio access node” or “radio network node” or “radio access network node” is any node in a radio access network (RAN) of a cellular communications network that operates to wirelessly transmit and / or receive signals. Some examples of radio access nodes include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high- power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, etc.), a relay node, a network node that implements partial functionality of a base station (e.g., a network node that implements a gNB-Central Unit (gNB-CU) or a network node that implements a gNB-Distributed Unit (gNB-DU)), or a network node that implements partial functionality of some other type of radio access node.

[0065] Core network node: As used herein, a “core network node” is any type of node in a core network, or any node that implements core network functionality. Some examples of core network nodes include, for example, a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), etc. Some other examples of core network nodes include nodes that implement an Access and Mobility Function (AMF), a UPF, a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), etc.

[0066] Communication device: As used herein, a “communication device” is any type of device that is capable of accessing a cellular communications network. Some examples of communication devices include, but are not limited to, a mobile phone, a smart phone, a sensor device, a meter, a vehicle, a household appliance, a medical appliance, a media player, a camera, or any type of consumer electronic device (such as, but not limited to, a television, a radio, a lighting arrangement, a tablet computer, a laptop computer, or a Personal Computer (PC)). A communication device can be a portable, hand-held, computer-comprised, or vehicle-mounted device that is capable of communicating voice and / or data via a wireless connection or a wired connection.

[0067] Wireless communication device: One type of communication device is a wireless communication device, which can be any type of wireless device that is capable of accessing (i.e., being served by) a wireless network (e.g., a cellular network). Some examples of wireless communication devices include, but are not limited to: a User Equipment (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (IoT) device. Such a wireless communication device can be a mobile phone, a smart phone, a sensor device, a meter, a vehicle, a household appliance, a medical appliance, a media player, a camera, or any type of consumer electronic device (such as, but not limited to, a television, a radio, a lighting installation, a tablet, a laptop, or a PC), or it can be integral to such a device. The wireless communication device can be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device that is capable of communicating voice and / or data via a wireless connection.

[0068] Network node: As used herein, “network node” is any node that is part of the radio access network or core network of a cellular communications network / system.

[0069] Note that the description given herein focuses on 3GPP cellular communications systems, and thus often uses terminology that is 3GPP LTE terminology or similar to 3GPP LTE terminology. However, the concepts disclosed herein are not limited to 3GPP systems.

[0070] Note that in the description herein, reference can be made to the term “cell”, however, especially with respect to 5G NR concepts, beams can be used instead of cells, and thus it is important to note that the concepts described herein are equally applicable to both cells and beams.

[0071] There are certain challenges. As stated in 3GPP TS 23.501 V16.3.0 clause 5.3.5, an Access and Mobility Management Function (AMF) can provide a Radio Access Technology (RAT) Frequency Selection Priority (RFSP) index to support Radio Resource Management (RRM) in the Radio Access Network (RAN). The index is stored in the Unified Data Management (UDM) and can be modified by the PCF based on policy.

[0072] As described in 3GPP TS 23.503 V16.3.0, it is possible for the PCF to modify the RFSP index based on operator policy that takes into account, for example, accumulated usage, load level information per network slice instance, etc. In order for the PCF to take into account accumulated usage, it is required that the PCF handling Access and Mobility (AM) related policy control (referred to herein as the “AM-PCF”) is the same as the PCF handling Session Management (SM) control (referred to herein as the “SM-PCF”). However, these PCFs can be different but still need to provide the functionality. In the same way, for the UE Aggregate Maximum Bit Rate (AMBR) (i.e., UE-AMBR) in the PCF handling AM policy association, similar dependencies can be foreseen. Other cases can be determined in the future.

[0073] The list of events reported by the PCF can be enhanced to report the current accumulated usage that the UE can have. One application of this event is the scenario of changing the RFSP index based on usage reporting as described in 3GPP TS 23.503 below:

[0074] The management of the RFSP index enables the PCF to modify the RFSP index used by the AMF to perform the radio resource management functions described in TS 23.501 [2] clause 5.3.4. The PCF modifies the RFSP index based on operator policy that takes into account, for example, accumulated usage, load level information per network slice instance, etc.

[0075] It is important that the PCF serving the AMF is not currently possible to be aware of the accumulated usage to enable it to influence the RFSP index value unless the PCF serving the AMF and the PCF serving the SMF are the same PCF (i.e., unless the AM-PCF and the SM-PCF are the same PCF).

[0076] One alternative approach can be to read the accumulated usage from the UDR and inform the PCF serving the AMF of the change. However, this solution would report any accumulated usage change that can not be needed for the RFSP index setting and does not allow to evaluate the RFSP index value based on different data plans that the operator can offer to its users and, therefore, this alternative is not considered as a suitable solution.

[0077] Certain aspects of the present disclosure and embodiments thereof can provide solutions to the above-described or other challenges. Based on the above discussion, embodiments are disclosed herein for extending the PCF EventExposure service to support reporting of usage thresholds reached per UE to consumers (i.e., NF consumers of the EventExposure service). Embodiments are also described herein for updating the AM Policy Association Establishment and Modification to expose the Npcf_EventExposure_Subscription and Notification service operations. Embodiments are also described herein for updating the AM Policy Association Termination, as the AM-PCF can send the Npcf_EventExposure_Unsubscribe.

[0078] Embodiments are disclosed herein for extending the Npcf_EventExposure service of the AM-PCF to subscribe to and get usage monitoring information (e.g., usage thresholds reached per UE) from the SM-PCF.

[0079] Certain embodiments can provide one or more of the following technical advantages. Embodiments disclosed herein can allow for separate deployment of the AM-PCF and the SM-PCF, and the AM-PCF can still enforce access and mobility policies based on the prescribed service bundled UE data usage.

[0080] Figure 1An example of a cellular communication system 100 that can implement embodiments of the present disclosure is shown. In the embodiments described herein, the cellular communication system 100 is a 5G system (5GS) including a next-generation RAN (NG-RAN) that can use 5G NR or a combination of 5G NR and LTE. In this example, the RAN includes base stations 102-1 and 102-2, which in the NG-RAN include either a 5G NR base station (gNB) or both a gNB and an LTE base station (referred to as an ng-eNB when connected to a 5G core (5CC)), controlling corresponding (macro)cells 104-1 and 104-2. Base stations 102-1 and 102-2 are generally referred to herein as base station 102, and are respectively referred to as base station 102. Similarly, (macro)cells 104-1 and 104-2 are generally referred to herein as (macro)cell 104, and are respectively referred to as (macro)cell 104. The RAN may also include multiple low-power nodes 106-1 to 106-4 that control corresponding small cells 108-1 to 108-4. Low-power nodes 106-1 to 106-4 may be small base stations (e.g., pico or femto base stations) or remote radio head ends (RRHs), etc. It is worth noting that, although not shown, one or more small cells 108-1 to 108-4 may alternatively be provided by base station 102. Low-power nodes 106-1 to 106-4 are generally referred to herein as low-power node 106, and are referred to individually as low-power node 106. Similarly, small cells 108-1 to 108-4 are generally referred to herein as small cell 108, and are referred to individually as small cell 108. The cellular communication system 100 also includes a core network 110, which is referred to in 5GS as the 5G core (5GC). Base station 102 (and optionally low-power nodes 106) is connected to the core network 110.

[0081] Base station 102 and low-power node 106 provide services to wireless communication devices 112-1 to 112-5 in corresponding cells 104 and 108. Wireless communication devices 112-1 to 112-5 are generally referred to herein as wireless communication device 112, and are referred to individually as wireless communication device 112. In the following description, wireless communication device 112 is generally a UE, but this disclosure is not limited thereto.

[0082] Figure 2 A wireless communication system represented as a 5G network architecture consisting of core network functions (NFs) is shown, where the interaction between any two NFs is represented by a point-to-point reference point / interface. Figure 2 Can be regarded as Figure 1 A specific implementation of System 100.

[0083] From the access side, Figure 2The illustrated 5G network architecture includes a plurality of UEs 112 connected to a RAN 102 or access network (AN) and an access and mobility function (AMF) 200. Generally, the R(AN) 102 includes a base station, e.g., an eNB or gNB, etc. From the core network side, Figure 2 The illustrated 5G core (5GC) NFs include a NSSF 202, an authentication server function (AUSF) 204, a UDM 206, the AMF 200, a session management function (SMF) 208, a PCF 210, and an application function (AF) 212.

[0084] In the specification standardization, the reference points of the 5G network architecture represent the interfaces used to form detailed call flows. The N1 reference point is defined to carry signaling between the UE 112 and the AMF 200. The reference points used to connect between the AN 102 and the AMF 200 and between the AN 102 and the UPF 214 are defined as N2 and N3, respectively. There is a reference point N11 between the AMF 200 and the SMF 208, which means that the SMF 208 is at least partially controlled by the AMF 200. The SMF 208 and the UPF 214 use N4 so that the UPF 214 can be set using control signals generated by the SMF 208 and the UPF 214 can report its status to the SMF 208. Respectively, N9 is the reference point for the connection between different UPFs 214, and N14 is the reference point for the connection between different AMFs 200. N15 and N7 are defined because the PCF 210 applies policies to the AMF 200 and the SMF 208, respectively. The AMF 200 needs N12 to perform authentication of the UE 112. N8 and N10 are defined because the AMF 200 and the SMF 208 need the subscription data of the UE 112.

[0085] The 5GC network aims to separate the user plane and the control plane. In the network, the user plane carries user traffic, while the control plane carries signaling. In Figure 2 In the network, the UPF 214 is in the user plane, and all other NFs (i.e., the AMF 200, the SMF 208, the PCF 210, the AF 212, the NSSF 202, the AUSF 204, and the UDM 206) are in the control plane. Separating the user plane and the control plane ensures that each plane resource can be scaled independently. It also allows the UPF to be deployed separately from the control plane functions in a distributed manner. In this architecture, the UPF can be deployed very close to the UE to shorten the round-trip time (RTT) between the UE and the data network for some applications that require low latency.

[0086] The core 5G network architecture is composed of modularized functions. For example, the AMF 200 and the SMF 208 are independent functions in the control plane. The separation of the AMF 200 and the SMF 208 allows independent evolution and scaling. Other control plane functions, such as the PCF 210 and the AUSF 204, can be separated as shown. Figure 2 The modularized function design enables the 5GC network to flexibly support various services.

[0087] Each NF interacts directly with another NF. Messages can be routed from one NF to another NF using intermediate functions. In the control plane, a set of interactions between two NFs is defined as a service so that it can be reused. This service enables support for modularity. The user plane supports interactions such as forwarding operations between different UPFs.

[0088] Figure 3 The 5G network architecture is shown, which uses service-based interfaces between NFs in the control plane, instead of Figure 2 point-to-point reference points / interfaces used in the 5G network architecture. However, the NFs described above with reference to Figure 2 correspond to the NFs shown in Figure 3 The services provided by the NFs to other authorized NFs can be exposed to the authorized NFs through the service-based interfaces. In Figure 3 the service-based interfaces are indicated by the letter “N” followed by the name of the NF, for example, Namf indicates the service-based interfaces of the AMF 200, and Nsmf indicates the service-based interfaces of the SMF 208, and so on. Figure 3 The NEF 300 and the NRF 302 in Figure 2 are not shown in the above-discussed Figure 2 However, it should be clarified that although not explicitly indicated in Figure 2 all the NFs depicted in Figure 3 may interact with the NEF 300 and the NRF 302 of

[0089] The Figure 2 and Figure 3Some of the properties of the NFs shown in the middle. The AMF 200 provides UE-based authentication, authorization, mobility management, etc. Even if the UE 112 uses multiple access technologies, it is basically connected to a single AMF 200 because the AMF 200 is independent of the access technology. The SMF 208 is responsible for session management and allocates an Internet Protocol (IP) address to the UE. It also selects and controls the UPF 214 for data transfer. If the UE 112 has multiple sessions, different SMFs 208 can be assigned to each session to manage them individually and possibly provide different functions for each session. The AF 212 provides information on packet flows to the PCF 210 responsible for policy control to support Quality of Service (QoS). Based on this information, the PCF 210 determines policies related to mobility and session management to enable the AMF 200 and the SMF 208 to function properly. The AUSF 204 supports authentication functions for UEs and the like, so it stores data for authentication and the like for UEs, while the UDM 206 stores subscription data for the UE 112. A data network (DN) that is not part of the 5G network provides Internet access or carrier services, etc.

[0090] NFs can be implemented as network elements on dedicated hardware, as software instances running on dedicated hardware, or as virtualized functions instantiated on an appropriate platform (e.g., a cloud infrastructure).

[0091] Embodiments are disclosed herein for extending the PCF EventExposure service (i.e., the Npcf_EventExposure service) to support reporting to consumers (i.e., NF consumers of the PCF EventExposure service) of usage thresholds reached per UE. Embodiments are also described herein for updating the AM Policy Association Establishment and Modification to expose the Npcf_EventExposure_Subscription and Notification service operations. Embodiments are also described herein for updating the AM Policy Association Termination, as the AM-PCF can send the Npcf_EventExposure_Unsubscribe.

[0092] Embodiments are disclosed herein for extending the Npcf_EventExposure service of the AM-PCF (denoted herein as AM-PCF 210-AM) to subscribe to and get usage monitoring information (e.g., usage thresholds reached per UE) from the SM-PCF (denoted herein as SM-PCF 210-SM).

[0093] Figure 4 The operation of the AM-PCF 210-AM and the SM-PCF 210-SM is illustrated, wherein, according to one example embodiment of the present disclosure, the AM-PCF 210-AM uses the extended Npcf_EventExposure service to subscribe to and get usage monitoring information (e.g., usage thresholds reached per UE) from the SM-PCF 210-SM. Specifically, this example procedure is the procedure for establishing AM policy association with a newly selected PCF. This procedure involves both roaming and non-roaming scenarios.

[0094] In the non-roaming case, the role of the V-PCF is performed by the PCF providing the AM policy association (i.e., the AM-PCF 210-AM), which can subscribe to the events reported by the PCF providing the SM policy association (i.e., the SM-PCF 210-SM). For the roaming scenario, the V-PCF interacts with the AMF 200 and does not perform interactions with the PCF providing the SM policy association (i.e., the SM-PCF 210-SM).

[0095] Figure 4 The steps of the procedure in FIG. 4 are as follows:

[0096] • Step 400: Based on the local policy, the AMF 200 decides to establish an AM policy association with the AM-PCF 210-AM, and then performs steps 402 to 404 under the following conditions.

[0097] • Step 402: [conditionally] if the AMF 200 has not obtained the access and mobility policy for the UE 112, or if the access and mobility policy in the AMF 200 is no longer valid, the AMF 200 requests the AM-PCF 210-AM to apply the operator policy from the AM-PCF 210-AM for the UE 112. The AMF 200 sends Npcf AMPolicyControl Create to the AM-PCF 210-AM to establish an AM policy control association with the AM-PCF 210-AM. This request includes the following information: the subscription permanent identifier (SUPI), the internal group (see TS 23.501, clause 5.9.7), the subscription notification indication, and (if available) the service area restriction, the radio access technology (RAT) / frequency selection priority (RFSP) index, the subscribed UE-AMBR, the allowed network slice selection assistance information (NSSAI), the general public subscription identifier (GPSI), which are retrieved from the UDM during the update location procedure, and can include the access type and RAT type, the permanent equipment identifier (PEI), the user location information (ULI), the UE time zone, and the serving network (PLMN ID, or PLMN ID and NID, see TS 23.501, clause 5.34).

[0098] • Step 404: The AM-PCF 210-AM checks the operator policy to determine if the RFSP index and / or the UE-AMBR value need to take into account the monitored usage for the SUPI and (DNN, S-NSSAI) (e.g., one or several combinations of (DNN, S-NSSAI)), and then sends the Npcf EventExposure Subscribe service operation to the SM-PCF 210-SM providing the SM policy association, including the SUPI, the DNN, the S-NSSAI, the events to set for usage reporting, and the thresholds (if applicable). Note that in some embodiments, the AM-PCF 200 can subscribe to be notified only when a UE usage threshold is reset.

[0099] • Step 406: The SM-PCF 210-SM providing the SM policy association reports to the AM-PCF 210-AM for the SUPI, the DNN, the S-NSSAI: (i) the usage, if any threshold or all thresholds are reached, and (ii) the subscription correlation ID. In one embodiment, the thresholds can also be sent.

[0100] • Step 408: The AM-PCF 210-AM responds to the Npcf AMPolicyControl Create service operation. The AM-PCF 210-AM provides the access and mobility related policy information (e.g. service area restrictions) defined in clause 6.5 of TS 23.503. In addition, the AM-PCF 210-AM can provide the AM policy associated policy control request trigger to the AMF 200.

[0101] The AMF 200 is implicitly subscribed in the AM-PCF 210-AM to be notified of changes in policy.

[0102] • Step 410: The [conditional] AMF 200 deploys the access and mobility related policy information including: storing the AM policy associated service area restrictions and policy control request trigger, providing the service area restrictions to the UE, and providing the RFSP index, UE-AMBR and service area restrictions to the NG-RAN as defined in TS 23.501.

[0103] Example embodiments of at least some aspects of the present disclosure are described below as changes to 3GPP TS 23.502 V16.3.0 and changes to 3GGP TS 23.503 V16.3.0. Changes are indicated by underlining, strikeout, or otherwise.

[0104] ********** Start of first change to 3GPP 23.502 **********

[0105] 4.16.1.2 Establishment of AM policy association with the newly selected PCF

[0106] [New - reproduced here as Figure 8 ]

[0107] Figure 4 .16.1.2-1 Establishment of AM policy association with the newly selected PCF

[0108] This procedure involves both roaming and non-roaming scenarios.

[0109] In the non-roaming case, the role of the V-PCF is performed by PCF providing AM policy association , The PCF can subscribe to events reported by the PCF providing SM policy association without performing interactions with the PCF providing SM policy association For the roaming scenario, the V-PCF interacts with the AMF The PCF checks the operator policy to determine if the RFSP index and / or the UE-AMBR value need to take into account the monitored usage cases for the SUPI and (DNN, S-NSSAI), then sends a Npcf_EventExposure_Subscribe service operation to the PCF providing SM policy association including the SUPI, DNN, S-NSSAI, the events set for usage reporting, and the thresholds (if applicable). .

[0110] 1. Based on local policy, the AMF decides to establish an AM policy association with the PCF and then performs steps 2 to 3 under the following conditions.

[0111] 2. [Conditional] If the AMF has not obtained the access and mobility policy for the UE, or if the access and mobility policy in the AMF is no longer valid, the AMF requests the PCF to apply the operator policy for the UE from the PCF. The AMF sends the Npcf_AMPolicyControl_Create to establish an AM policy control association with the PCF. This request includes the following information: SUPI, internal group (see clause 5.9.7 of TS 23.501 [2]), subscription notification indication, and (if available) service area restrictions, RFSP index, subscribed UE-AMBR, allowed NSSAI, GPSI, which are retrieved from the UDM during the update location procedure, and can include access type and RAT type, PEI, ULI, UE time zone, and serving network (PLMN ID, or PLMN ID and NID, see clause 5.34 of TS 23.501 [2]). The PCF responds to the Npcf_AMPolicyControl_Create service operation. The PCF provides the access and mobility related policy information (e.g. service area restrictions) as defined in clause 6.5 of TS 23.503

[20] . In addition, the PCF can provide the AM policy association policy control request triggers to the AMF.

[0112] 3. 4. The PCF providing SM policy association reports to the PCF the usage cases (if any or all thresholds are reached) and the subscription correlation Id for the SUPI, DNN, S-NSSAI. Figure 9 Figure 4 or by the Npcf_EventExposure_Notificcation triggered when a threshold is reached or reset

[0113] Figure 10 Figure 4

[0114] 5. The PCF responds to the Npcf_AMPolicyControl_Create service operation. The PCF provides the access and mobility related policy information (e.g. service area restrictions) as defined in clause 6.5 of TS 23.503

[20] . In addition, the PCF can provide the AM policy association policy control request triggers to the AMF. The AMF is implicitly subscribed in the PCF to be notified of changes in policy.

[0115] The PCF responds to the Npcf_AMPolicyControl_Create service operation.

[0116] 6. [Conditional] The AMF deploys the access and mobility related policy information, which includes: storing the service area restrictions and policy control request triggers of the AM policy association, providing the service area restrictions to the UE, and providing the RFSP index, UE-AMBR and service area restrictions to the NG-RAN, as defined in TS 23.501 [2].

[0117] ********** Next change to 3GPP 23.502 ********** ​

[0118] 4.16.2.2 AM policy association modification initiated by PCF

[0119] This procedure applies to AM policy association modification due to case B.

[0120] [Reproduced here unsubscribes from notifications from the PCF providing SM policy association (if needed), ]

[0121] Figure 5 .16.2.2-1: AM policy association modification initiated by PCF

[0122] This procedure involves roaming and non-roaming scenarios.

[0123] In non-roaming case, the role of V-PCF is performed by the PCF. For roaming scenario, the V-PCF interacts with the AMF.

[0124] NOTE: The V-PCF stores the access and mobility control policy information provided to the AMF.

[0125] 1. [Conditional] PCF determines locally Figure 5 Figure 11 New state of the UE context requires new policy.

[0126] 2. (V-)PCF makes policy decision.

[0127] 3. (V-)PCF sends Npcf_UpdateNotify which includes the AM policy association ID associated with the service area restrictions, UE-AMBR, RFSP index, or SUPI defined in TS 29.507

[32] .

[0128] 4. AMF deploys access and mobility related policy information including: storing the service area restrictions and policy control request triggers of the AM policy association, providing the service area restrictions to the UE, and providing the RFSP index, UE-AMBR and service area restrictions to the NG-RAN.

[0129] ********** Next change to 3GPP 23.502 **********

[0130] 4.16.3.2 AMF initiated AM policy association termination

[0131] [Reproduced here Figure 5 ]

[0132] Figure 12 .16.3.2-1: AMF initiated AM policy association termination

[0133] This procedure involves roaming and non-roaming scenarios.

[0134] In non-roaming case, the role of V-PCF is performed by the PCF. For roaming scenarios, the V-PCF interacts with the AMF.

[0135] 1. During de-registration procedure, or due to mobility in registration procedure or handover procedure with change of AMF and (V-)PCF, the AMF decides to terminate the AM policy association, then if an AM policy association is established with the (V-)PCF, steps 2 to 3 are executed.

[0136] 2. The AMF sends to the (V-)PCF a Npcf_AMPolicyControl_Delete service operation including the AM policy association ID.

[0137] 3. The (V-)PCF removes the policy context of the UE, Figure 5 , for deployment of the same PCF providing session and non-session management policies and replies to the AMF with a response including success or failure.

[0138] 4. The AMF removes the AM policy association of the UE, including the access and mobility control policies related to this UE. The AMF removes the subscription to the events detected by the AMF requested for this policy association.

[0139] **********Next change to 3GPP 23,502**********

[0140] 5.2.5.1 Overview

[0141] The following table shows the PCF services.

[0142] Table 5.2.5.1-1: NF services provided by the PCF

[0143]

[0144]

[0145] **********End of changes to 3GPP 23.502**********

[0146] **********First change to 3GPP 23.503**********

[0147] 5.2.1 Non-roaming architecture

[0148] The reference architecture of the policy and charging control framework of the 5G system consists of the functions of the policy control function (PCF), the session management function (SMF), the user plane function (UPF), the access and mobility management function (AMF), the network exposure function (NEF), the network data analytics function (NWDAF), the charging function (CHF), the application function (AF) and the UDR (Unified Data Repository).

[0149] Figure 13 .2.1-1 shows a service-based representation, and Figure 5 .2.1-1a shows a reference point representation of the reference architecture of the policy and charging control framework of the 5G system.

[0150] [Reproduced herein as considering for example cumulative usage cases ]

[0151] If the consumer PCF (providing non-session management policies for the UE) subscribes to notifications when a usage case reaches a certain threshold, or when the usage case is again below that threshold (e.g. at the end of a calendar period, or due to the provided credentials), or both, then the PCF (providing session management policies for the UE PDU session) notifies when that event is met. .2.1-1: Overall non-roaming reference architecture of the policy and charging control framework of the 5G system (service-based representation)

[0152] [Reproduced herein as When the same PCF provides non-session and session management policies, ]

[0153] When the PCF provides non-session management policies to the AMF and to the UE (as defined in 3GPP TS 23.501), then inputs from the AMF, NWDAF, UDR and the PCF providing session management policies are considered. .2.1-1a: Overall non-roaming reference architecture of the policy and charging control framework of the 5G system (reference point representation) When the PCF provides session management policies to the SMF as defined, then inputs from the SMF, AF, UDR, NWDAF, CHF are considered.

[0154] [Reproduced herein as The PCF providing session management policies can expose the facts related to the PDU session listed in clause 6.1.3.18, ]

[0155] Figure 5 2.1-1b: Overall non-roaming reference architecture for the policy and charging control framework of the 5G system (reference points table Figure 6

[0156] NOTE 1: The N4 reference point is not part of the 5G policy framework architecture, but is shown in the figure for completeness. The N4 reference point is defined in TS 23.501 [2].

[0157] NOTE 2: How the PCF / NEF stores / retrieves information related to policy subscription data or application data is defined in TS 23.501 [2].

[0158] The Nchf service for online and offline charging consumed by the SMF is defined in TS 32.240 [8].

[0159] The Nchf service for spending limit control consumed by the PCF is defined in TS 23.502 [3].

[0160] ********** Next change to 3GPP 23.503 **********

[0161] 6.1.2.1 Access and mobility related policy control

[0162] Access and mobility policy control includes management of service area restrictions, management of RFSP function and UE-AMBR, and management of SMF selection. This clause defines the management of service area restrictions and RFSP index for UEs registered over 3GPP access. The management of service area restrictions for 5G-RG or FN-CRG using W-5GAN is specified in TS 23.316

[27] .

[0163] The management of service area restrictions enables the PCF of the serving PLMN (e.g. V-PCF in roaming case) to modify the service area restrictions used by the AMF as specified in TS 23.501 [2] clause 5.3.4.

[0164] The subscription of the UE can contain service area restrictions that the PCF can further modify at any time based on operator-defined policies by extending the list of allowed TAIs, or by reducing the not allowed TAIs, or by increasing the maximum number of allowed TAIs. The operator-defined policies in the PCF can depend on input data, e.g. UE location, time of the day, information provided by other NFs, etc.

[0165] The AMF can report the subscribed service area restrictions received from the UDM at registration procedure or when the AMF changes, the reporting condition being that the local policy in the AMF indicates that access and mobility control is enabled. The AMF also reports the subscribed service area restrictions to the PCF when the policy control request trigger for service area restrictions change described in clause 6.1.2.5 is met. The AMF receives the modified service area restrictions from the PCF. The AMF stores them and then uses it to determine the mobility restrictions for the UE. The PCF can indicate to the AMF that there is no restriction for the service area.

[0166] The service area restrictions consist of a list of allowed TAIs or a list of not allowed TAIs and optionally a maximum number of allowed TAIs.

[0167] NOTE 1: The enforcement of the service area restrictions is performed by the UE when it is in CM-IDLE state while RRC is inactive or when it is in CM-CONNECTED state, and when the UE is located in the RAN / AMF while in CM-CONNECTED state.

[0168] Management of RFSP index enables the PCF to modify the RFSP index used by the AMF to perform the radio resource management functions described in clause 5.3.4 of TS 23.501 [2]. The PCF modifies the RFSP index based on operator policy taking into account, for example, cumulative usage, load level information per network slice instance, etc. The subscribed RFSP index can be further adjusted at any time by the PCF based on operator policy.

[0169] For radio resource management, the AMF can report the subscribed RFSP index received from the UDM at registration procedure or at AMF change. The condition for reporting is that the local policy in the AMF indicates that access and mobility control is enabled. When the subscription to RFSP index change to the PCF is met, the AMF reports the subscribed RFSP index to the PCF. The AMF receives the modified RFSP index from the PCF.

[0170] NOTE 2: Enforcement of RFSP index is performed in the RAN.

[0171] At AMF change, the source AMF informs the PCF that the UE context is removed in the AMF in case of inter-PLMN mobility.

[0172] Management of UE-AMBR enables the PCF to provide the UE-AMBR information to the AMF based on Figure 7 service network policy. The AMF can report the subscribed UE-AMBR received from the UDM. The condition for reporting is that the PCF provides the policy control request trigger to the AMF to report the subscriber UE-AMBR change. The AMF receives the modified UE-AMBR from the PCF. The AMF provides the UE-AMBR value for the service network to the RAN as described in clause 5.7.2.6 of TS 23.501 [2].

[0173] Management of SMF selection enables the PCF to instruct the AMF to contact the PCF during PDU session establishment procedure to perform DNN replacement as described in clause 5.6.1 of TS 23.501 [2]. During the UE registration procedure and at establishment of AM policy association, the PCF can provide the policy control request trigger SMF selection management and SMF selection management information (as part of the access and mobility management related policy control information (see clause 6.5)) to instruct the conditions to check whether to contact the PCF at PDU session establishment as specified in clause 6.1.2.5.

[0174] ********** Next change to 3GPP 23.503 **********

[0175] 6.1.3.18 Event reporting from PCF

[0176] The AF can subscribe / unsubscribe to event notifications from the PCF for the PDU Session to which the AF session is bound.

[0177] The events that the AF can subscribe to are listed in table 6.1.3.18-1.

[0178] Table 6.1.3.18-1: Events related to reporting from PCF

[0179]

[0180]

[0181]

[0182]

[0183] If the AF requests the PCF to report the PLMN identifier where the UE is currently located, the PCF shall provide the AF with this PLMN identifier if available. Otherwise, the PCF shall provide the corresponding PCC rules and policy control request triggers to report the PLMN change to the SMF. The PCF shall forward this information to the AF upon reception of the PLMN identifier from the SMF.

[0184] If the AF requests the PCF to report the change of access type, the PCF shall provide the AF with information about the access type currently used by the user and inform the AF about the change of access type when a change of access type is indicated. The PCF shall provide the corresponding policy control request triggers to report the access type information to the SMF. The PCF shall forward this information to the AF upon reception of the access type information from the SMF.

[0185] If the AF requests the PCF to report the signalling path status, the PCF shall report this to the AF for the AF session when PCC rules identifying signalling traffic from the SMF are indicated to be removed.

[0186] If the AF requests the PCF to report the access network charging correlation information, the PCF shall provide the AF with this access network charging correlation information, which the PCF will identify as usage reports including flow measurements once the access network charging correlation information is known at the PCF.

[0187] If the AF requests the PCF to report access network information, the PCF shall set the access network information reporting parameters in the corresponding PCC rules and provide them to the SMF along with the corresponding policy control request trigger. For those PCC rules based on preliminary service information, the PCF can assign the 5QI and ARP of the QoS flow associated with the default QoS rule to avoid the signalling to the UE. The PCF shall also set the corresponding policy control request trigger for the SMF. The PCF forwards the access network information to the AF upon its request after receiving the subsequent access network information report from the SMF corresponding to the AF session.

[0188] If the AF requests the PCF to report the usage of sponsored data connections, the PCF shall provide the corresponding PCC rules and policy control request triggers to the SMF. If the usage threshold provided by the AF is reached or the AF session is terminated, the PCF forwards such information to the AF.

[0189] If the AF requests the PCF to report service data flow deactivation, the PCF shall report the release of resources to the AF. The PCF shall forward this information to the AF upon receiving the removal of the PCC rules from the SMF.

[0190] If the AF requests the PCF to report when the QoS targets for a specific media flow are no longer (or can be met again), the PCF shall set the QNC indication in the corresponding PCC rules including the GBR or delay-critical GBR 5QI values and provide them to the SMF along with the corresponding policy control request trigger. At this point, the SMF informs that for those QoS flows to which those PCC rules are bound, the GFBR can no longer (or can be met again) be guaranteed, the PCF shall report the affected media flows to the AF and provide an indication that the QoS targets can no longer (or can be met again) be met. If additional information is received together with the SMF notification (see clause 5.7.2.4 of TS 23.501 [2]), the PCF shall forward it to the AF.

[0191] Figure 6 ​ ​

[0192] **********Next change to 3GPP 23.503**********

[0193] 6.2.1.2 Inputs to PCC decision

[0194] ​The PCF shall accept input for PCC decision from SMF, AMF, CHF, NWDAF (if present), UDR, and from AF (if AF is involved), and the PCF can use its own pre-defined information. These different nodes shall provide as much information as possible to the PCF. At the same time, the following information describes examples of the provided information. Depending on the specific scenario, all information can not be available or already provided to the PCF.

[0195] ​ ​

[0196] ​ ​ The AMF can provide the following information:

[0197] - SUPI;

[0198] - PEI of the UE;

[0199] - Location of the subscriber;

[0200] - Service area restrictions;

[0201] - RFSP index;

[0202] - RAT type;

[0203] - GPSI;

[0204] - Access type;

[0205] - Serving network identifier (PLMN ID or PLMN ID and NID, see clause 5.34 of TS 23.501 [2]);

[0206] - Allowed NSSAI;

[0207] - UE time zone;

[0208] - Subscribed UE-AMBR;

[0209] - Mapping of allowed NSSAI;

[0210] - S-NSSAI of the PDU session;

[0211] - Requested DNN.

[0212] NOTE 1: The access type and RAT type parameters shall allow extension to include new access types.

[0213] The UE can provide the following information:

[0214] - OS Id;

[0215] - PSI list;

[0216] - an indication that the UE supports ANDSP.

[0217] The SMF can provide the following information:

[0218] - the SUPI;

[0219] - the PEI of the UE;

[0220] - the IPv4 address of the UE;

[0221] - the IPv6 network prefix allocated to the UE;

[0222] - the default 5QI and default ARP;

[0223] - the request type (initial, modification, etc.);

[0224] - the type of PDU session (IPv4, IPv6, IPv4v6, Ethernet, unstructured);

[0225] - the access type;

[0226] - the RAT type;

[0227] - the GPSI;

[0228] - the internal group identifier;

[0229] - the location of the subscriber;

[0230] - the S-NSSAI;

[0231] - the NSI-ID (if available);

[0232] - the DNN;

[0233] - the service network identifier (PLMN ID or PLMN ID and NID, see clause 5.34 of TS 23.501 [2]);

[0234] - the application identifier;

[0235] - the allocated application instance identifier;

[0236] - the detected service data flow description;

[0237] - UE support for reflective QoS (as defined in clause 5.7.5.1 of TS 23.501 [2]);

[0238] - the number of supported packet filters for the signaled QoS rules (indicated by the UE as defined in clause 5.7.5.1 of TS 23.501 [2]);

[0239] - 3GPP PS data off state;

[0240] - DN authorization profile index (see clause 5.6.6 of TS 23.501 [2]);

[0241] - Session AMBR (see clause 5.6.6 of TS 23.501 [2]).

[0242] The UDR can provide information for subscribers connected to a specific DNN and S-NSSAI as described in subclause 6.2.1.3.

[0243] The UDR can provide the following ASP related policy information:

[0244] - ASP identifier;

[0245] - Transport policy and background data transfer reference ID, amount of data to be transferred for each UE, expected number of UEs.

[0246] NOTE 2: When a UDR serving the NEF is deployed and stores application requests, the UDR can provide related information on the impact of the AF on traffic routing.

[0247] The AF (if involved) can provide the following application session related information directly or via the NEF (e.g. based on SIP and SDP):

[0248] - Subscriber identifier;

[0249] - IP address of the UE;

[0250] - Media type;

[0251] - Media format, e.g. media format sub-field of the media announcement and all other parameter information (a=lines) associated with the media format;

[0252] - Bandwidth;

[0253] - Sponsored data connectivity information;

[0254] - Flow description, e.g. source and destination IP address and port number and protocol;

[0255] - AF application identifier;

[0256] - AF-Service-Identifier (AF Service Identifier), or alternatively, DNN and possibly S-NSSAI

[0257] - AF communication service identifier (e.g. IMS communication service identifier) that the UE provides via the AF;

[0258] - AF application event identifier;

[0259] - AF record information;

[0260] - flow status (for gating decisions);

[0261] - priority indicator that the PCF can use to guarantee service for higher relative priority application sessions;

[0262] NOTE 3: The AF priority information indicates session / application priority and is separate from the MPS 5GS priority indicator.

[0263] - emergency indicator;

[0264] - application service provider;

[0265] - DNAI;

[0266] - information on N6 traffic routing requirements;

[0267] - GPSI;

[0268] - internal group identifier;

[0269] - time validity condition;

[0270] - space validity condition;

[0271] - AF subscription for early and / or late notification related to UP management events;

[0272] - AF transaction identifier;

[0273] - TSN AF parameters;

[0274] - burst arrival time reference to TSN GM;

[0275] - periodicity reference to TSN GM;

[0276] - flow direction;

[0277] - delay requirement reference to TSN GM;

[0278] - QoS information to monitor;

[0279] - reporting frequency.

[0280] The AF can provide the following background data transfer related information via the NEF:

[0281] - background data transfer reference ID.

[0282] - background data transfer policy.

[0283] - amount per UE.

[0284] -UE number.

[0285] - Expected time window.

[0286] -Network area information.

[0287] CHF (if applicable) can provide subscribers with the following information:

[0288] - The policy counter status for each relevant policy counter.

[0289] NWDAF (if applicable) may provide the analytical information described in Clause 6.1.1.3.

[0290] ​ ​

[0291] Additionally, depending on the QoS flow attributes, the predefined information in the PCF can include additional rules based on the charging policies in the network, whether the subscriber is in its home network or roaming.

[0292] The 5QI in the PCC rule (see Clause 5.7.4 of TS 23.501[2]) is derived by the PCF from the AF or UDR interaction (if available). The input may be SDP information conforming to the operator's policy or other available application information.

[0293] The allocation and reservation priorities in the PCC rules are derived by the PCF from the AF or UDR interaction (if available) based on the operator's policy.

[0294] **********3GPP 23.503 Changes Completed**********

[0295] ​is a schematic block diagram of a network node 500 according to some embodiments of the disclosure. Optional features are represented by dashed boxes. The network node 500 can be, for example, a network node implementing an NF within the core network 110, e.g., an AM-PCF 210-AM or SM-PCF 210-SM as described herein. As illustrated, the network node 500 includes a control system 502 that includes one or more processors 504 (e.g., central processing units (CPUs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), etc.), memory 506, and a network interface 508. The one or more processors 504 are referred to herein as processing circuitry. The one or more processors 504 operate to provide one or more functions of the network node 500 as described herein (e.g., one or more functions of the AM-PCF 210-AM or SM-PCF 210-SM as described herein). In some embodiments, the functions are implemented in, for example, software stored in the memory 506 and executed by the one or more processors 504.

[0296] ​ is a schematic block diagram illustrating a virtualized embodiment of the network node 500 according to some embodiments of the disclosure. As used herein, a “virtualized” network node is an implementation of the network node 500 in which at least a portion of the functions of the network node 500 are implemented as virtual components (e.g., via virtual machines executing in physical processing nodes in a network). As illustrated, in this example, the network node 500 includes one or more processing nodes 600 coupled to or included as part of a network 602. Each processing node 600 includes one or more processors 604 (e.g., CPUs, ASICs, FPGAs, etc.), memory 606, and a network interface 608. In this example, the functions 610 of the network node 500 described herein (e.g., one or more functions of the AM-PCF 210-AM or SM-PCF 210-SM described herein) are implemented at the one or more processing nodes 600 or distributed across multiple processing nodes 600 in any desired manner. In some particular embodiments, some or all of the functions 610 of the network node 500 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment hosted by the processing nodes 600.

[0297] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of network node 500 or a node (e.g., processing node 600) implementing one or more functions of network node 500 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier containing the computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0298] ​ is a schematic block diagram of a network node 500 according to some other embodiments of the disclosure. Network node 500 includes one or more modules 700, each of which is implemented in software. Modules 700 provide the functionality of network node 500 described herein (e.g., one or more functions of an AM-PCF 210-AM or SM-PCF 210-SM described herein). The same applies to ​ processing node 600 of FIG. 6, where modules 700 can be implemented at one of processing nodes 600 or distributed across multiple processing nodes 600.

[0299] Any appropriate steps, methods, features, functions, or benefits disclosed herein can be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus can comprise a number of these functional units. These functional units can be implemented by processing circuitry, which can include one or more microprocessor or microcontrollers, as well as other digital hardware (which can include digital signal processors (DSPs), special-purpose computer chips, application- specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other controller or computer hardware). The processing circuitry can be configured to execute program code stored in memory to perform the functions of the disclosure described herein. The memory can include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage media, etc. Program code stored in memory can include program instructions for implementing telecommunication and / or data

[0300] While the processes in the drawings show particular orders of operations for certain embodiments of the disclosure, it can be appreciated that such order is an example (e.g., alternative embodiments can perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

[0301] Some example embodiments of the disclosure are as follows:

[0302] Embodiment 1 : A method performed by a first policy and control function (PCF) (210-AM) that provides access management (AM) policy association for a user equipment (UE), wherein the first PCF is comprised in a core network (110) of a cellular communications system (100), the method comprising: subscribing (404) to an event exposure service of a second PCF (210-SM) that provides session management (SM) policy association for the UE, wherein the event exposure service supports reporting usage monitoring information for the UE; and in response to subscribing (404) to the event exposure service of the second PCF (210-SM), receiving (406) a report from the second PCF (210-SM) comprising usage monitoring information for the UE.

[0303] Embodiment 2: The method of embodiment 1, wherein the usage monitoring information comprises information reporting that the UE has reached a predefined or preconfigured usage threshold.

[0304] Embodiment 3: The method of embodiment 1 or 2, further comprising: receiving (402) a request from an access and mobility management function (200) to create or modify an AM policy for the UE; wherein subscribing (404) to the event exposure service of the second PCF (210-SM) comprises subscribing (404) to the event exposure service of the second PCF (210-SM) in response to receiving (402) the request from the AMF (200) to create or modify the AM policy for the UE.

[0305] Embodiment 4: The method of embodiment 3, further comprising: sending (408) AM related policy information (e.g. service area restrictions) for the UE to the AMF (200).

[0306] Embodiment 5: The method of embodiment 3 or 4, wherein the first PCF (210-AM) modifies an RFSP index used by the AMF (200) to perform radio resource management functions with respect to the UE based on one or more operator policies that take into account the received usage monitoring information for the UE.

[0307] Embodiment 6: A method performed by a second policy and control function (PCF) (210-SM) providing a session management (SM) policy association for a user equipment (UE), wherein the second PCF (210-SM) is comprised in a core network (110) of a cellular communications system (100), the method comprising: receiving (404), from a first PCF (210-AM) providing an access management (AM) policy association for the UE, a message subscribing to an event exposure service of the second PCF (210-SM), wherein the event exposure service supports reporting of usage monitoring information for the UE; and in response to receiving (404) the message subscribing to the event exposure service of the second PCF (210-SM), sending (406) a report comprising the usage monitoring information for the UE to the first PCF (210-AM).

[0308] Embodiment 7: The method according to embodiment 6, wherein the usage monitoring information comprises information reporting that the UE has reached a predefined or preconfigured usage threshold.

[0309] Embodiment 8: A network node (500) adapted to perform the method according to any one of embodiments 1-7.

[0310] Embodiment 9: A method performed in a core network (110) of a cellular communications system (100), comprising:

[0311] • at a first policy and control function (PCF) (210-AM) providing an access management (AM) policy association for a user equipment (UE):

[0312] o subscribing (404) to an event exposure service of a second PCF (210-SM) providing a session management (SM) policy association for the UE, wherein the event exposure service supports reporting of usage monitoring information for the UE; and

[0313] o in response to subscribing (404) to the event exposure service of the second PCF (210-SM), receiving (406) a report from the second PCF (210-SM) comprising the usage monitoring information for the UE; and

[0314] • at the second PCF (210-SM) providing the SM policy association for the UE:

[0315] o receiving (404), from the first PCF (210-AM), a message subscribing to the event exposure service of the second PCF (210-SM); and

[0316] o in response to receiving (404) the message subscribing to the event exposure service of the second PCF (210-SM), sending (406) a report comprising usage monitoring information of the UE to the first PCF (210-AM).

[0317] Embodiment 10: The method of embodiment 9, wherein the usage monitoring information comprises information reporting that the UE has reached a predefined or preconfigured usage threshold.

[0318] Embodiment 11: The method of embodiment 9 or 10, further comprising: receiving (402), at the first PCF (210-AM), a request from an access and mobility management function (200) to create or modify an AM policy for the UE; wherein subscribing (404) to the event exposure service of the second PCF (210-SM) comprises subscribing (404) to the event exposure service of the second PCF (210-SM) in response to receiving (402) the request from the AMF (200) to create or modify the AM policy for the UE.

[0319] Embodiment 12: The method of embodiment 11, further comprising: sending (408), at the first PCF (210-AM), AM-related policy information (e.g., service area restrictions) of the UE to the AMF (200).

[0320] Embodiment 13: The method of embodiment 11 or 12, wherein the first PCF (210-AM) modifies the RFSP index used by the AMF (200) to perform radio resource management functions with respect to the UE based on one or more operator policies that take into account the received usage monitoring information of the UE.

[0321] At least some of the following acronyms can be used in this disclosure. If there is a discrepancy between acronyms, preference should be given to how it is used above. If listed multiple times below, the first listing should take precedence over any subsequent listing.

[0322] • 3GPP Third Generation Partnership Project

[0323] • 5G Fifth Generation

[0324] • 5GC Fifth Generation Core

[0325] • 5GS Fifth Generation System

[0326] • AF Application Function

[0327] • AMF Access and Mobility Management Function

[0328] • AN Access Network

[0329] • AP Access Point

[0330] • ASIC Application-Specific Integrated Circuit

[0331] • AUSF Authentication Server Function

[0332] • CPU Central Processing Unit

[0333] • DN Data Network

[0334] • DSP Digital Signal Processor

[0335] • eNB Enhanced or Evolved Node B

[0336] • EPS Evolved Packet System

[0337] • E-UTRA Evolved Universal Terrestrial Radio Access

[0338] • FPGA Field-Programmable Gate Array

[0339] • gNB New Radio Base Station

[0340] • gNB-DU New Radio Base Station Distributed Unit

[0341] • HSS Home Subscriber Server

[0342] • IoT Internet of Things

[0343] • IP Internet Protocol

[0344] • LTE Long Term Evolution

[0345] • MME Mobility Management Entity

[0346] • MTC Machine Type Communication

[0347] • NEF Network Exposure Function

[0348] • NF Network Function

[0349] • NR New Radio

[0350] • NRF Network Function Repository Function

[0351] • NSSF Network Slice Selection Function

[0352] • OTT Over-The-Top

[0353] • PC Personal Computer

[0354] • PCF Policy Control Function

[0355] • P-GW Packet Data Network Gateway

[0356] • QoS Quality of Service

[0357] • RAM Random Access Memory

[0358] • RAN Radio Access Network

[0359] • ROM Read Only Memory

[0360] • RRH Remote Radio Head

[0361] • RTT Round Trip Time

[0362] • SCEF Service Capability Exposure Function

[0363] • SMF Session Management Function

[0364] • UDM Unified Data Management

[0365] • UE User Equipment

[0366] • UPF User Plane Function

[0367] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

1. A method performed by a first policy and control function, PCF, (210-AM) that provides access management, AM, policy associations for a user equipment, UE, (112), wherein, The first PCF is comprised in a core network (110) of a cellular communications system (100), the method comprises: subscribing (404), by the first PCF (210-AM) providing AM policy association for the UE (112), to an event exposure service of a second PCF (210-SM) providing session management, SM, policy association for the UE (112); and receiving (406), in response to subscribing (404) to the event exposure service of the second PCF (210-SM), a report from the second PCF (210-SM) providing SM policy association for the UE.

2. The method of claim 1, wherein, The event exposure service supports reporting usage monitoring information of the UE (112), and the report received from the second PCF (210-SM) comprises usage monitoring information of the UE (112).

3. The method of claim 2, wherein, The usage monitoring information comprises information reporting that a predefined or preconfigured usage threshold has been reached by the UE (112).

4. The method of claim 2 or 3, wherein, The usage monitoring information comprises information reporting that a predefined or preconfigured usage threshold has been reset.

5. The method of claim 1, further comprising: receiving (402), from an access and mobility management function, AMF (200), a request to create or modify an AM policy for the UE (112); wherein subscribing (404) to the event exposure service of the second PCF (210-SM) comprises subscribing (404) to the event exposure service of the second PCF (210-SM) in response to receiving (402) the request to create or modify an AM policy for the UE (112) from the AMF (200).

6. The method of claim 5, further comprising: sending (408) AM related policy information of the UE (112) to the AMF (200).

7. The method of claim 6, wherein, The AM related policy information comprises service area restrictions.

8. The method of claim 5 or 6, wherein, The first PCF (210-AM) modifies a radio access technology, RAT / frequency selection priority, RFSP, index used by the AMF (200) to perform radio resource management functions with respect to the UE (112) based on one or more operator policies taking into account the received usage monitoring information of the UE (112).

9. A network node (500) for implementing a first policy and control function, PCF, (210-AM) providing access management, AM, policy association for a user equipment, UE, (112), wherein The first PCF is comprised in a core network (110) of a cellular communications system (100), the network node (500) comprises: a first module for subscribing (404), by the first PCF (210-AM) providing AM policy association for the UE (112), to an event exposure service of a second PCF (210-SM) providing session management, SM, policy association for the UE (112); and a second module for receiving (406), in response to subscribing (404) to the event exposure service of the second PCF (210-SM), a report from the second PCF (210-SM) providing SM policy association for the UE.

10. The network node (500) according to claim 9, wherein The network node (500) further comprises modules for performing the method according to any one of claims 2-8.

11. A network node (500) for implementing a first policy and control function (PCF) (210-AM) for providing access management AM policy association to a user equipment (UE) (112), wherein, The first PCF is comprised in a core network (110) of a cellular communications system (100), the network node comprises: processing circuitry (504; 604) configured to cause the network node (500) to: subscribe (404), by the first PCF (210-AM) providing AM policy association for the UE (112), to an event exposure service of a second PCF (210-SM) providing session management, SM, policy association for the UE (112); and in response to subscribing (404) to the event exposure service of the second PCF (210-SM), receive (406) a report from the second PCF (210-SM) providing SM policy association for the UE.

12. The network node (500) according to claim 11, wherein The processing circuitry (504; 604) is further configured to cause the network node (500) to perform the method according to any one of claims 2 to 8.

13. A method performed by a second policy and control function, PCF, (210-SM) that provides session management, SM, policy associations for a user equipment, UE, (112), wherein, The second PCF (210-SM) is comprised in a core network (110) of a cellular communications system (100), the method comprises: receiving (404), from a first PCF (210-AM) providing access management, AM, policy association for the UE, a message subscribing to an event exposure service of the second PCF (210-SM); and in response to receiving (404) the message subscribing to the event exposure service of the second PCF (210-SM), sending (406), to the first PCF (210-AM), a report comprising usage monitoring information of the UE.

14. The method of claim 13, wherein, The event exposure service supports reporting usage monitoring information of the UE (112), and the report received from the second PCF (210-SM) comprises usage monitoring information of the UE (112).

15. The method of claim 14, wherein, The usage monitoring information comprises information reporting that the UE has reached a predefined or preconfigured usage threshold.

16. The method of claim 14, wherein, The usage monitoring information comprises information reporting that a predefined or preconfigured usage threshold has been reset.

17. A network node (500) for implementing a second policy and control function, PCF, (210-SM) providing session management, SM, policy association for a user equipment, UE, (112), wherein The second PCF (210-SM) is comprised in a core network (110) of a cellular communications system (100), the network node (500) comprises: a first module for receiving (404), from a first PCF (210-AM) providing access management, AM, policy association for the UE, a message subscribing to an event exposure service of the second PCF (210-SM); and a second module for, in response to receiving (404) the message subscribing to the event exposure service of the second PCF (210-SM), sending (406), to the first PCF (210-AM), a report comprising usage monitoring information of the UE.

18. The network node (500) according to claim 17, wherein The network node (500) further comprises modules for performing the method according to any one of claims 14 to 16.

19. A network node (500) for implementing a second policy and control function, PCF, (210-SM) providing session management, SM, policy association for a user equipment, UE, (112), wherein The second PCF (210-SM) is comprised in a core network (110) of a cellular communications system (100), the network node (500) comprises: processing circuitry (504; 604) configured to cause the network node (500) to: receiving (404), from a first PCF (210-AM) that provides access management, AM, policy association for the UE, a message subscribing to an event exposure service of a second PCF (210-SM); and in response to receiving (404) the message subscribing to the event exposure service of the second PCF (210-SM), sending (406) a report comprising usage monitoring information of the UE to the first PCF (210-AM).

20. The network node (500) according to claim 19, wherein The processing circuitry (504; 604) is further configured to cause the network node (500) to perform the method according to any of claims 14 to 16.

21. A method performed in a core network (110) of a cellular communications system (100), comprising: • at a first policy and control function, PCF (210-AM), that provides access management, AM, policy association for a user equipment, UE: o subscribing (404), by the first PCF (210-AM) that provides AM policy association for the UE (112), to an event exposure service of a second PCF (210-SM) that provides session management, SM, policy association for the UE; and o in response to subscribing (404) to the event exposure service of the second PCF (210-SM), receiving (406) a report from the second PCF (210-SM) that provides SM policy association for the UE; and • at the second PCF (210-SM) that provides the SM policy association for the UE: o receiving (404), from the first PCF (210-AM), a message subscribing to the event exposure service of the second PCF (210-SM); and o in response to receiving (404) the message subscribing to the event exposure service of the second PCF (210-SM), sending (406) the report to the first PCF (210-AM).

22. The method of claim 21, wherein, The event exposure service supports reporting usage monitoring information of the UE (112), and the report received from the second PCF (210-SM) comprises usage monitoring information of the UE (112).

23. The method of claim 22, wherein, The usage monitoring information comprises information reporting that the UE has reached a predefined or preconfigured usage threshold.

24. The method of claim 21, further comprising: At the first PCF (210-AM): receiving (402), from an access and mobility management function, AMF (200), a request to create or modify an AM policy for the UE; wherein subscribing (404) to the event exposure service of the second PCF (210-SM) comprises subscribing (404) to the event exposure service of the second PCF (210-SM) in response to receiving (402) the request to create or modify an AM policy for the UE from the AMF (200).

25. The method of claim 24, further comprising: At the first PCF (210-AM), sending (408) AM related policy information of the UE to the AMF (200).

26. The method of claim 24 or 25, wherein, The first PCF (210-AM) modifies a Radio Access Technology, RAT, / Radio Frequency Selection Priority, RFSP, index used by the AMF (200) to perform radio resource management functions with respect to the UE based on one or more operator policies that take into account the received usage monitoring information of the UE.

Images