Patent Description:
In the current network resource charging specified by the 3rd Generation Partnership Project (3GPP) each Network Function performs charging by initiating a new charging request for a specific user equipment (UE), usually defined by an International Mobile Subscriber Identity (IMSI). For instance, if charging for a UE attachment to a network is wanted, an Access Management Function (AMF) will trigger a charging event through a Charging Function (CHF) for the IMSI that is included in the attach message, and later if charging for data transmission is wanted a Session Management Function (SMF) will setup its own charging for this with the CHF.

Charging identifiers for resources used for PDU sessions with the UE are post processed to correlate the events for charging purposes. <CIT> (corresponding to <CIT>) discloses a mechanism for coordinating charging for a multimedia session between a UE and a remote host on both an application/session level and on an IP/access bearer level. A token associated with the multimedia session is generated and used to correlate session charges for operations performed in the packet-switched access network and for operations performed in the multimedia system. <CIT> discloses that an SMF receives from an AMF a PDU session create request message requesting establishment of a PDU session for a wireless device. In response to the PDU session create request message, the SMF sends to a CHF a charging policy request message requesting charging policy information for the PDU session. The SMF receives from the CHF a response message comprising the charging policy information for the PDU session. The charging policy information comprises a first charging method. Based on the charging policy information, the SMF determines a charging control rule for the PDU session. The SMF enforces the charging control rule. <NPL>, describes <NUM> system, charging services and pCR TS <NUM> Proposal on Message flow of the Service Operation 3GPP DRAFT; S5-<NUM> REL-<NUM> PCR <NUM>, http://www. org/ftp/tsg%S5Fsa/WG5%SFTM/TSGS5%5F119AH/Docs/S5%2D184045% 2Ezip, describes that an SMF sends a Nchf_ConvergedCharging_Create request to the CHF to create resource for starting charging. PDU session information, requested quota and notification URI for Nchf_ConvergedCharging_Notify service operation are included in the request body. At successful operation, "<NUM> Created" response is returned. In the "<NUM> Created" response, the CHF includes a Location header field and the allocated quota in the body. The Location header field shall contain the URI of the created resource. The SMF shall use the URI received in the Location header in subsequent requests to the CHF for the same PDU session.

When an operator would like to have all parts for the service delivery consolidated, independent of the node or function producing the information, it requires that first all charging information events are sorted and correlated. It is difficult or sometimes not possible for the system to know if all parts of the service delivery have been found, i.e. how to determine which functions and nodes have been part of the service delivery. One approach is to sort and correlate all charging information events based on the UE and the time of events, but the events can only be consolidated through post processing by a system. The system cannot provide the operator more real-time information since the information requires a lot of processing to find the entity handling the charging and/or to correlate the information in order. For these types of scenarios and because of the substantial number of steps needed to process and put all information together makes the event information inaccessible in real-time or near real-time.

Some embodiments of the present disclosure are directed to a method by an AMF of a communications system. The method includes responding to receipt of a network attach request message of a UE requesting attachment to a network of the communication system, by sending a charging data request message toward a CHF containing a notification for the CHF to keep a charging data resource to track charging for network resources used for communications associated with UE while attached to the network. The method receives a response message of the CHF containing a reference for the charging data resource associated with the UE while attached to the network. The method responds to receiving a protocol data unit (PDU) session establishment request message of the UE, by sending a PDU session establishment request message containing the reference for the charging data resource toward a SMF.

Some other related embodiments are directed to a method by a CHF of a communications system. The method includes responding to receipt of a charging data request message of a UE requesting attachment to a network of the communication system and containing a notification for the CHF to keep a charging data resource to track charging for network resources used for communications while the UE is attached to the network, by sending a response message containing a reference for the charging data resource. The method responds to receipt of a charging data request message for a PDU session requested by the UE, by sending a charging data response message. The method tracks charging for network resources used for communications during the PDU session with the UE using the reference for the charging data resource.

Other further related embodiments are directed to AMF, CHF, apparatuses.

In some of these embodiments, an AMF of a communications system includes at least one processor, and at least one memory coupled to the at least one processor and including computer readable program code that when executed by the at least one processor causes the at least one processor to perform operations. The operations are configured to respond to receipt of a network attach request message of a UE requesting attachment to a network of the communication system, by sending a charging data request message toward a CHF containing a notification for the CHF to keep a charging data resource to track charging for network resources used for communications associated with UE while attached to the network. The operations are further configured to receive a response message of the CHF containing a reference for the charging data resource associated with the UE while attached to the network. The operations are further configured to respond to receipt of a PDU session establishment request message of the UE, by sending a PDU session establishment request message containing the reference for the charging data resource toward a SMF.

In some of these embodiments, a CHF of a communications system includes at least one processor, and at least one memory coupled to the at least one processor and including computer readable program code that when executed by the at least one processor causes the at least one processor to perform operations. The operations are configured to respond to receiving a charging data request message of a UE request attachment to a network of the communication system and containing a notification for the CHF to keep a charging data resource to track charging for network resources used for communications while the UE is attached to the network, by sending a response message containing a reference for the charging data resource. The operations are further configured to respond to receipt of a charging data request message for a PDU session requested by the UE by sending a charging data response message. The operations are further configured to track charging for network resources used for communications during the PDU session with the UE using the reference for the charging data resource.

Potential advantages of these and other embodiments disclosed herein include that the AMF shares the reference for the charging data resource with the SMF by including it as content in its message, and the SMF can correspondingly share the reference with the CHF by including it as content in its message. In this manner, the CHF can operate to add the charging for the PDU session resource utilization to the reference that was shared by the AMF. Because the same reference can thereby be used for one or more PDU sessions established with the UE, a charging function or billing function can directly determine all resource charging for the UE using the shared reference. This avoids the need to perform post processing operations and enables more real-time management based on all charging associated with the shared reference.

It is noted that aspects described with respect to one embodiment may be incorporated in different embodiments although not specifically described relative thereto. That is, all embodiments and/or features of any embodiments can be combined in any way and/or combination. Moreover, other AMFs, CHFs, and corresponding methods and computer program products according to embodiments will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such other AMFs, CHFs, and corresponding methods and computer program products be included within this description and protected by the accompanying claims.

Aspects of the present disclosure are illustrated by way of example and are not limited by the accompanying drawings. In the drawings:.

Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of various present inventive concepts to those skilled in the art.

<FIG> is a block diagram of a communications system having functions configured in accordance with some embodiments of the present disclosure. Referring to <FIG>, the communication system includes a user equipment (UE) <NUM>, an access management function (AMF) <NUM>, a user plane function (UPF) <NUM>, a session management plane function (SMF) <NUM>, and a charging function (CHF) <NUM>. The AMF <NUM>, UPF <NUM>, SMF <NUM>, and CHF <NUM> may be part of the <NUM> Core Network (5GC).

Example operations performed by the nodes of the communications system of <FIG> are now explained in the context of the steps shown in <FIG> in accordance with some embodiments of the present disclosure.

<FIG> is a combined data flow diagram and flowchart illustrating a sequence of operations and data flows between functions of the communications system of <FIG> for UE network attach procedures, PDU session establishment, and UE network detach procedures and use of a shared reference for a charging data resource associated with the UE in accordance with some embodiments of the present disclosure. Although various arrows are used to convey example communication directions, the illustrated arrows are not limiting and the communications can occur in the opposite directions to those illustrated and often occur in both directions. Moreover, the communications can occur through intermediary network functions other than those shown.

Referring to <FIG>, in step <NUM>, the UE <NUM>, which can be identified by an International Mobile Subscriber Identity (IMSI), sends an attachment request message containing the IMSI which is passed to the AMF <NUM> to initiate a network attach operation. Although not shown, the UE <NUM> communicates with the AMF <NUM> via a radio access network, which may be a NG-RAN (Next Generation Radio Access Network).

The CHF <NUM> is responsible for converged online charging and offline charging functionalities, and provides quota, re-authorization triggers, rating conditions and is notified about usage reports from the SMF <NUM>. In step <NUM>, the AMF <NUM> responsively sends a charging data request message toward the CHF <NUM> which contains a notification for the CHF <NUM> to keep a charging data resource to track charging for network resources used for communications associated with UE <NUM> while the UE <NUM> is attached to the network. The charging data resource can be REST based and created to provide service to the AMF <NUM> for tracking charging data until further notice (e.g., terminate resource notice) is received from the AMF <NUM>. Thus, the CHF <NUM> of <FIG> and <FIG> is requested by the AMF <NUM> to keep the charging data resource active for tracking and accumulating charging for use of network resources for the UE while the UE remains attached the network. The CHF responds to charging messages which reference the charging data resource by accumulating those charges under the charging data resource. The charging data resource may, for example, include a record structure in which charging messages cause corresponding charging entries to be added to the record structure. These operations are in sharp contrast to prior existing AMF and CHF operations, whereby the CHF would create a charging data resource, report a charge for the charging data resource to a billing system, and then close the charging data resource.

In step <NUM>, the CHF <NUM> creates the charging data resource which can include as part of REST the CHF <NUM> creating a database entry where charging data is stored for the UE <NUM> (e.g., stored with an associated to the UE IMSI). The CHF <NUM> then responds to the AMF <NUM> by sending <NUM> a charging data response containing a reference for the charging data resource associated with the UE <NUM> while attached. The reference for the charging data resource is also referred to as a "charging resource reference" and "reference" for brevity. In practice, the reference can be a Uniform Resource Identifier (URI) that includes of a string of characters that unambiguously identifies a particular charging data resource record at the CHF <NUM> which is used to track charging for network resources used for communications (e.g., Protocol Data Unit (PDU) session(s)) with the UE <NUM>.

In step <NUM>, the AMF <NUM> stores the reference for the charging data resource in a local memory of the AMF <NUM> or connected memory (e.g., User Data Repository) with a persistent association to the UE <NUM> (e.g., identified by IMSI), and sends network attach information in a message passed to the UE <NUM>. The UE <NUM> uses the network attach information to complete attachment to the network.

Although the UE <NUM> would not normally be notified of the reference for the charging data resources, in some embodiments the reference may be included in the message communicated in step <NUM> with the attach information. Informing the UE <NUM> of the resource may be useful in proximity services for the UE <NUM>. Proximity services (ProSe) provides mechanisms for UEs to discover other UEs in close proximity and to communicate with those other UEs directly, such as without the data path being routed via the network infrastructure. For example, a public safety officer can use ProSe services to discover local presence of another public safety officer and communicate (transmit user plane traffic) directly therebetween.

In step <NUM>, awhile later, the UE <NUM> requests establishment of a PDU session by sending a PDU session establishment request message, which is passed to the AMF <NUM>, that contains the reference for the charging data resource. For <NUM> session management, the SMF <NUM> is primarily responsible for interacting with the decoupled data plane, creating updating and removing Protocol Data Unit (PDU) sessions and managing session context with the UPF <NUM>. Both the UE <NUM> and a radio access network (e.g., gNB) may employ the Next Generation Application Protocol (NGAP) to carry Non Access Stratum (NAS) messages across the N1 or N2 reference interfaces in order to request a new PDU session. The AMF <NUM> receives these requests and handles connectivity and/or mobility management while forwarding session management requirements over the N11 interface to the SMF <NUM>. The AMF <NUM> determines which SMF <NUM> is best suited to handle a connection request by querying a Network Repository Function (NRF).

Messages received over the N11 interface represent a trigger to add, modify or delete a PDU session across the user plane. The SMF <NUM> sends messages to the UPF <NUM> over the N4 reference interface using the Packet Forwarding Control Protocol (PFCP). During session establishment or modification, the SMF <NUM> also interacts with a Policy Control Function (PCF) over the N7 interface and the subscriber profile information stored within the Unified Data Management (UDM) function (N10), which assumes the role previously performed by the Home subscriber Server (HSS).

In the illustrative example of <FIG>, the AMF <NUM> retrieves from its local memory or connected memory (e.g., User Data Repository) the reference for the charging data resource which is associated with the UE <NUM> (e.g., identified by IMSI), and sends (step <NUM>) an instruction message, which is passed to the SMF <NUM>, to establish the PDU session and includes the retrieved reference for the charging data resource in the instruction message. It is noted that the UE <NUM> can have multiple simultaneously ongoing PDU sessions and/or can have a series of spaced apart in time PDU sessions while the UE remains attached to the network. Moreover, any two or more of these PDU sessions may extend through different SMFs within the communications system architecture. Thus, by the AMF <NUM> providing each of the SMFs the reference for the charging data resource during establishment of respective PDU sessions, each of the SMFs are thereby able to use that shared reference to perform charging by the CHF <NUM> so that network resources used for those PDU sessions are all charged to the same shared reference.

In step <NUM>, the SMF <NUM> starts a charging data request by operations that include sending toward the CHF <NUM> a charging data request message for the PDU session, where the charging data request message contains the reference for the charging data resource that was received from the AMF <NUM>. The CHF <NUM> responsively adds the PDU session charging to the reference for the charging data resource. Thus, instead of creating a new reference for the PDU session, the CHF <NUM> uses the earlier reference sent to the AMF <NUM> (step <NUM>) to track additional resource charging for the PDU session for the UE <NUM> (e.g., identified by IMSI). The CHF <NUM> adds other previous or subsequent charging for the UE <NUM> that arises from other PDU sessions and/or other network resource(s) utilization by the UE <NUM> to the same resource for the charging data resource while the UE <NUM> remains attached to the network.

Accordingly, the AMF <NUM> shares the reference with the SMF <NUM> by including it as content in the message of step <NUM>, and the SMF <NUM> correspondingly shares the reference with the CHF <NUM> by including it as content in the message of step <NUM>. In this manner, the CHF <NUM> can operate to add the charging for the PDU session resource utilization to the reference that was shared by the AMF <NUM>. Because the same reference is thereby used for one or more PDU sessions established with the UE <NUM>, a charging function or billing function can directly determine all resource charging for the UE <NUM> which is associated with the shared reference. This avoids the need to perform post processing operations described above in the context of previously existing systems and enables more real-time management based on the charging made for the shared reference.

In step <NUM>, the CHF <NUM> sends a charging data response message, which is passed to the SMF <NUM>, confirming the start of the charging data session for the PDU session of the UE <NUM>. The CHF <NUM> charges for use of the network resource(s) by the UE during the PDU session. As noted above, the UE <NUM> can have multiple simultaneously ongoing PDU sessions and/or can have a series of spaced apart in time PDU sessions while the UE remains attached to the network. The CHF <NUM> is configured to use the same reference for the charging data resource to track charging for network resources used for communications during the one or more PDU sessions. By receiving the reference in each of the charging data request messages for each of the PDU sessions, the CHF <NUM> is thereby able to charge to the same reference.

In step <NUM>, the SMF <NUM> receives the charging data response message of the CHF <NUM> and responsively continues its interaction with the AMF <NUM> for the PDU session establishment, including sending a PDU session establishment message passed to the AMF <NUM>. In step <NUM>, the AMF <NUM> responsively interacts with the UE <NUM> for the PDU session establishment, including sending a PDU session establishment accepted message passed to the UE <NUM>.

The charging data response message sent in step <NUM> and the PDU session establishing message sent in step <NUM> may contain the reference for the charging data resource. When the CHF <NUM> includes the reference in the charging data response message, this enables the AMF <NUM> and/or the SMF <NUM> to confirm that the CHF <NUM> is capable of using the reference provided by the AMF <NUM>, via the SMF <NUM>, for the PDU session that is being established for the UE <NUM> and, otherwise if not included by the CHF <NUM>, the AMF <NUM> and/or the SMF <NUM> can resort to a process for generating a new reference for charging resources used for the PDU session. Inclusion of the reference in the charging data response message can alternatively or additionally enable the SMF <NUM> to operate more stateless by not requiring the SMF <NUM> to maintain a mapping between the charging data request sent in step <NUM> and the confirmatory charging data response received in step <NUM>. Inclusion of the reference in the charging data response message may alternatively or additionally provide another way for the SMF <NUM> and/or the AMF <NUM> to match the response from the CHF <NUM> to the PDU session being established for the UE <NUM>, which can increase reliability of the charge tracking operations.

In step <NUM>, awhile later after the UE <NUM> has transmitted and received data while the PDU session remains established, the UE <NUM> requests detachment from the network, including by transmitting a network detach request message passed to the AMF <NUM>.

In step <NUM>, the AMF <NUM> responsively creates a charging data request message requesting termination of resource for the network disconnection, and associated termination of the reference for the charging data resource. The charging data request message is passed to the CHF <NUM> to request the CHF <NUM> to archive the (REST based) resource that has been used for the UE <NUM> (e.g., identified by IMSI). The AMF <NUM> retrieves the reference for the charging data resource from its local memory or connected memory (e.g., User Data Repository), such as using the identifier of the UE <NUM> (e.g., the IMSI) as a lookup pointer, and includes the reference in the charging data request message.

In step <NUM>, the CHF <NUM> responsively closes the resource and sends a charging data response message, which may include the reference, which is passed to the AMF <NUM>. The AMF <NUM> responsively sends in step <NUM> an attach information message used by the UE <NUM> to detach from the network. The CHF <NUM> operation to close the resource may include removing or otherwise updating its database entries associated with the received reference for the charging data resource, and sending a message to a billing system (billing functional node) of the communications network that contains billing information generated based on the entries from the CHF <NUM> database that were or continue to be associated with the reference for the charging data resource. The CHF <NUM> can operate to close the resource of the reference for the charging data resource. Although detachment of the UE <NUM> from the network would normally herein cause the CHF <NUM> to close the resource, such that a subsequent network attachment operation (e.g., steps <NUM>-<NUM>) would trigger the CHF <NUM> to generate a new reference, in some other embodiments the CHF <NUM> keeps the reference active in its database associated with the UE <NUM> (e.g., IMSI) for future reuse for charging for network resource utilization associated when the UE <NUM> again reattaches to the network and initiates future PDU session(s).

The charging data response message sent in step <NUM> may contain the reference for the charging data resource. When the CHF <NUM> includes the reference in the charging data response message, this enables the AMF <NUM> to operate more stateless by not requiring the AMF <NUM> to maintain in local memory or connected memory (e.g., User Data Repository) information providing a mapping between the reference included in the charging data request sent in step <NUM> and the confirmatory charging data response that is subsequently received in step <NUM>.

One or more of the messages communicated to the CHF <NUM> may be based on Nchf_ConvergedCharging_Create/Update/Release. One or more of the messages communicated to the SM <NUM> may be based on Nsmf_PDUSession_Create/Modify/Release.

<FIG> is a block diagram of an electronic node <NUM> of the communications system architecture of <FIG>, such as the AMF <NUM>, the CHF <NUM>, and/or the SMF <NUM> containing elements that are configured according to some embodiments. The electronic node <NUM> can include one or more network interfaces <NUM> (referred to as "network interface" for brevity), one or more processors <NUM> (referred to as "processor" for brevity), and one or more memories <NUM> (referred to as "memory" for brevity) containing program code <NUM>.

The network interface <NUM> may be configured to communicate through a wired interface, e.g., Ethernet, and/or wireless interface, e.g., wireless transceiver, according to one or more proprietary protocols and/or industry standardized protocols, e.g., WiFi, 3GPP <NUM>, <NUM> (NR), etc. The processor <NUM> may include one or more data processing circuits, such as a general purpose and/or special purpose processor (e.g., microprocessor and/or digital signal processor) that may be collocated or distributed across one or more networks. The processor <NUM> is configured to execute program code <NUM> in the memory <NUM>, described below as a computer readable medium, to perform some or all of the operations and methods that are described above for one or more of the embodiments of an AMF, a CHF, and/or a SMF, such as regarding one or more of the embodiments described herein in the context of <FIG>, <FIG>, and <FIG>.

The above and more general operations and methods that can be performed by an AMF, a SMF, and a CHF are now explained with reference to <FIG>.

<FIG> are flowcharts of operations by an AMF in accordance with some embodiments of the present disclosure.

Referring initially to <FIG>, the AMF is configured to respond to receipt <NUM> of a network attach request message of a UE requesting attachment to a network of the communication system, by sending <NUM> (also <NUM> in <FIG>) a charging data request message toward a CHF containing a notification for the CHF to keep a charging data resource to track charging for network resources used for communications associated with UE while attached to the network. The AMF receives <NUM> (also <NUM> in <FIG>) a response message of the CHF containing a reference for the charging data resource associated with the UE while attached to the network. The AMF responds to receipt (<NUM> in <FIG>) of a PDU session establishment request message of the UE, by sending <NUM> (also <NUM> in <FIG>) a PDU session establishment request message containing the reference for the charging data resource toward a session management plane function, SMF.

The reference for the charging data resource may be a Uniform Resource Identifier (URI) composed of a string of characters that unambiguously identifies a charging data resource record at the CHF which is used to track charging for network resources used for communications during one or more PDU sessions with the UE.

As was explained above, the same reference can be used for a series of PDU sessions with the UE. In a further related embodiment, the AMF responds to receiving another PDU session establishment request message of the UE, by sending another PDU session establishment request message containing the reference for the charging data resource toward the SMF. The PDU session establishment request message and the another PDU session establishment request message are received while the UE maintains attachment to the network without performing an intervening request to detach from the network.

Some further embodiments are directed to operations that occur when the UE requests to detach from the network. In the example embodiment of <FIG>, the AMF responds to receiving (<NUM> in <FIG>) a network detach request message of the UE requesting detachment from the network, by sending <NUM> (also <NUM> in <FIG>) a charging data request message toward the CHF including a notification to terminate use of the reference for the charging data resource. The operation to send <NUM> the charging data request message can include retrieving <NUM> the reference for the charging data resource from local memory of the AMF or connected memory (e.g., User Data Repository) using an identifier of the UE as a lookup pointer.

The AMF and/or another network function may forward the reference for the charging data resource to a Short Message Service Function (SMSF) and/or a Network Exposure Function (NEF).

<FIG> are flowcharts of operations by a CHF in accordance with some embodiments of the present disclosure.

Referring initially to <FIG>, the CHF is configured to respond to receipt (<NUM> in <FIG>) of a charging data request message of a UE requesting attachment to a network of the communication system and containing a notification for the CHF to keep a charging data resource to track charging for network resources used for communications while the UE is attached to the network, by sending <NUM> (also <NUM> in <FIG>) a response message containing a reference for the charging data resource ;.

The CHF responds to receipt (<NUM> in <FIG>) of a charging data request message for a PDU session requested by the UE, by sending <NUM> (also <NUM> in <FIG>) a charging data response message. The CHF then tracks <NUM> charging for network resources used for communications during the PDU session with the UE using the reference for the charging data resource.

Again, the reference for the charging data resource may be a URI composed of a string of characters that unambiguously identifies a charging data resource record at the CHF which is used to track charging for network resources used for communications during one or more PDU sessions with the UE.

As was explained above, the same reference can be used for a series of PDU sessions with the UE. In a further related embodiment, the CHF is configured to respond to receipt of another charging data request message for another PDU session requested by the UE by sending another charging data response message, and tracking additional charging for additional network resources used for communications during the another PDU session with the UE using the reference for the charging data resource.

The charging data request for the PDU session and the another charging data request message for the another PDU session are received while the UE maintains attachment to the network without performing an intervening request to detach from the network.

The charging data response message may include the reference for the charging data resource. In one embodiment, the CHF embeds <NUM> (also <NUM> in <FIG>) the reference for the charging data resource in the charging data response message sent by the CHF responsive to receiving (<NUM> in <FIG>) the charging data request for the PDU session requested by the UE.

Some further embodiments are directed to operations that occur when the UE requests to detach from the network. In the example embodiment of <FIG>, the CHF responds to receipt (<NUM> in <FIG>) of a charging data request message of the AMF or the SMF to terminate use of the reference for the charging data resource, by closing the charging data resource and sending <NUM> (also <NUM> in <FIG>) a charging data response message toward the AMF or the SMF.

The charging data request message may include the reference for the charging data resource.

The CHF may be configured to respond to receipt of a charging data request message of the AMF or the SMF to terminate use of the reference for the charging data resource, by removing or updating <NUM> its database entries associated with the reference for the charging data resource, and by sending <NUM> a message to a billing system node of the communications network that contains billing information generated based on the entries from the CHF database associated with the reference for the charging data resource.

<FIG> is a flowchart of operations by a SMF in accordance with some embodiments of the present disclosure. Referring to <FIG>, the SMF is configured to respond to receipt (<NUM> in <FIG>) of a PDU session establishment request message related to a UE requesting attachment to a network of the communications system and that contains a reference for a charging data resource associated with the UE while attached to the network, by sending <NUM> (also <NUM> in <FIG>) toward a CHF a charging data request message for the PDU session that contains the reference for the charging data resource and by starting a charging session for the PDU session using the reference. The SMF also responds to receipt (<NUM> in <FIG>) of a charging data response message of the CHF, by communicating <NUM> (also <NUM> in <FIG>) with an AMF to establish the PDU session for the UE.

The communication <NUM> with the AMF to establish the PDU session for the UE may include sending a PDU session establishment message toward the AMF.

In some further embodiments, the charging data response message includes the reference. In one further embodiment, the SMF embeds the reference for the charging data resource in the PDU session establishment message sent by the SMF responsive to receiving the charging data response message of the CHF.

The reference for the charging data resource may be a URI composed of a string of characters that unambiguously identifies a charging data resource record at the CHF which is used to track charging for network resources used for communications during the PDU session with the UE.

The SMF may be further configured to forward the reference for the charging data resource to a SMSF and/or a NEF.

In the above-description of various embodiments of the present disclosure, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense expressly so defined herein.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various aspects of the present disclosure.

Like reference numbers signify like elements throughout the description of the figures.

Various abbreviations used herein include the following:.

Claim 1:
A method by an access management function, AMF, of a communications system, the method comprising:
responsive to receiving (<NUM>) a network attach request message of a user equipment, UE, requesting attachment to a network of the communication system, sending (<NUM>, <NUM>) a charging data request message toward a charging function, CHF, containing a notification for the CHF to keep a charging data resource to track charging for network resources used for communications associated with UE while attached to the network;
receiving (<NUM>, <NUM>) a response message of the CHF containing a reference for the charging data resource associated with the UE while attached to the network;
responsive to receiving (<NUM>) a protocol data unit, PDU, session establishment request message of the UE, sending (<NUM>, <NUM>) a PDU session establishment request message containing the reference for the charging data resource toward a session management plane function, SMF.