Data flow charging reporting by user plane function

Abstract

Example embodiments of the present disclosure relate to data flow charging reporting by user plane function(s). A method includes generating a charging identifier that identifies at least one data flow of a terminal device; and sending session request information to a second apparatus configured to provide a user plane function, UPF, the session request information including the charging identifier and access information of at least one network node, wherein a respective one of the at least one network node is configured to provide a network function related to charging of the at least one data flow based on user plane information related to the at least one data flow received from the user plane function.

Description

Technical Field

[0001] Various exemplary embodiments of this disclosure generally relate to the telecommunications field, and more specifically to methods, apparatus, devices, and computer-readable storage media for reporting data stream billing via user plane functions. Background Technology

[0002] The communication system architecture employs a service-based design, where the core network comprises network functions (NFs) that provide services accessible by authorized NFs. Communication between these NFs is facilitated via a RESTful API (Representative State Transition Application Programming Interface). Each NF can discover and select other NFs or their services through a local configuration or network repository function (NRF), which maintains configuration files for registered NFs.

[0003] In the core network architecture, Functions Within Networks (NFs) can be categorized based on their specific functions. Key NFs include the Access and Mobility Management Function (AMF), responsible for access control and mobility management; and the Policy Control Function (PCF), which handles policy and charging decisions. The Session Management Function (SMF) manages the user plane at the User Plane Function (UPF). This management is performed via a point-to-point (P2P) N4 interface, enabling direct communication between the SMF and UPF. Summary of the Invention

[0004] In a first aspect of this disclosure, a first apparatus is provided. The first apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus to at least: generate a charging identifier for at least one data stream identifying a terminal device; and send session request information to a second apparatus configured to: provide a User Plane Function (UPF), the session request information including: the charging identifier and access information for at least one network node, wherein a corresponding network node of the at least one network node is configured to: provide network functions related to the charging of the at least one data stream based on the user plane information related to the at least one data stream received from the UPF.

[0005] In a second aspect of this disclosure, a second apparatus is provided. The second apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus to at least: receive session request information from a first apparatus, the first apparatus being configured to: provide a Session Management Function (SMF), the session request information including: a charging identifier and access information of at least one network node, wherein the charging identifier identifies at least one data flow of a terminal device, and a corresponding network node of the at least one network node is configured to: provide charging-related network functions for the at least one data flow based on user plane information associated with the at least one data flow; determine user plane information associated with the at least one data flow based on the charging identifier; and send a notification to the at least one network node based on the access information of the at least one network node, the notification including: user plane information associated with the at least one data flow.

[0006] In a third aspect of this disclosure, a third apparatus is provided. The third apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the third apparatus to at least: receive a notification from a second apparatus configured to provide user plane functions, the notification including: user plane information relating to at least one data stream of a terminal device identified by a billing identifier; and, based on the received user plane information, perform billing-related network functions relating to the at least one data stream.

[0007] In a fourth aspect of this disclosure, a method is provided. The method includes: generating a charging identifier for at least one data stream identifying a terminal device; and sending session request information to a second device configured to: provide a User Plane Function (UPF), the session request information including: the charging identifier and access information for at least one network node, wherein a corresponding network node of the at least one network node is configured to: provide network functions related to the charging of the at least one data stream based on the user plane information related to the at least one data stream received from the UPF.

[0008] In a fifth aspect of this disclosure, a method is provided. The method includes: receiving session request information from a first device configured to: provide a session management function (SMF), the session request information including: a charging identifier and access information of at least one network node, wherein the charging identifier identifies at least one data flow of a terminal device, and a corresponding network node of the at least one network node is configured to: provide charging-related network functions for the at least one data flow based on user plane information associated with the at least one data flow; determine user plane information associated with the at least one data flow based on the charging identifier; and send a notification to the at least one network node based on the access information of the at least one network node, the notification including: user plane information associated with the at least one data flow.

[0009] In a sixth aspect of this disclosure, a method is provided. The method includes: receiving a notification from a second means configured to provide user plane functionality, the notification including: user plane information relating to at least one data stream of a terminal device identified by a charging identifier; and performing a charging-related network function relating to the at least one data stream based on the received user plane information.

[0010] In a seventh aspect of this disclosure, a first apparatus is provided. The first apparatus includes: components for generating a charging identifier for at least one data stream identifying a terminal device; and components for sending session request information to a second apparatus configured to: provide a User Plane Function (UPF), the session request information including: the charging identifier and access information for at least one network node, wherein a corresponding network node of the at least one network node is configured to: provide network functions related to the charging of the at least one data stream based on the user plane information related to the at least one data stream received from the UPF.

[0011] In an eighth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: components for receiving session request information from a first apparatus, the first apparatus being configured to: provide a Session Management Function (SMF), the session request information including: a charging identifier and access information of at least one network node, wherein the charging identifier identifies at least one data flow of a terminal device, and a corresponding network node of the at least one network node is configured to: provide charging-related network functions for the at least one data flow based on user plane information associated with the at least one data flow; components for determining user plane information associated with the at least one data flow based on the charging identifier; and components for sending a notification to the at least one network node based on the access information of the at least one network node, the notification including: user plane information associated with the at least one data flow.

[0012] In a ninth aspect of this disclosure, a third apparatus is provided. The third apparatus includes: components for receiving a notification from a second apparatus configured to provide user plane functions, the notification including: user plane information relating to at least one data stream of a terminal device identified by a billing identifier; and components for performing billing-related network functions relating to the at least one data stream based on the received user plane information.

[0013] In a tenth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to the fourth aspect.

[0014] In the eleventh aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to the fifth aspect.

[0015] In a twelfth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to a sixth aspect.

[0016] It should be understood that the summary section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to be used to limit the scope of this disclosure. Other features of this disclosure will become apparent from the following description. Attached Figure Description

[0017] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which:

[0018] Figure 1 An example communication environment in which example embodiments of this disclosure may be implemented is shown;

[0019] Figure 2 The control panel protocol stack according to some example embodiments of the present disclosure is illustrated via Sxa, Sxb, Sxc, combinations of Sxa / Sxb, N4, and N4mb;

[0020] Figure 3 The signaling flow for protocol data unit session initiation and notification is shown according to some example embodiments of the present disclosure;

[0021] Figure 4A A flowchart is shown for a first process of obtaining location information of a terminal device via a control panel-based configuration, according to some example embodiments of the present disclosure;

[0022] Figure 4B A flowchart is shown of a second process for obtaining location information of a terminal device via a control panel-based configuration, according to some example embodiments of the present disclosure;

[0023] Figure 5A A flowchart is shown for a first process of obtaining location information of a terminal device via a user panel-based configuration, according to some example embodiments of the present disclosure;

[0024] Figure 5B A flowchart is shown of a second process for obtaining location information of a terminal device via a user panel-based configuration, according to some example embodiments of the present disclosure;

[0025] Figure 6 A flowchart is shown illustrating a method implemented at a first device according to some exemplary embodiments of the present disclosure;

[0026] Figure 7 A flowchart is shown illustrating a method implemented at a second device according to some exemplary embodiments of the present disclosure;

[0027] Figure 8 A flowchart is shown illustrating a method implemented at a third device according to some example embodiments of the present disclosure;

[0028] Figure 9 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and

[0029] Figure 10 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.

[0030] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0031] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0032] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0033] In this disclosure, references to "an embodiment," "an embodiment," "an example embodiment," etc., indicate that the described embodiments may include specific features, structures, or characteristics, but not every embodiment necessarily includes that specific feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a specific feature, structure, or characteristic is described in connection with an embodiment, those skilled in the art will recognize that, whether explicitly described or not, incorporating other embodiments to affect such a feature, structure, or characteristic is within their knowledge.

[0034] It should be understood that although the terms "first" and "second," etc., preceding nouns, may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another, and they do not restrict the order of the nouns. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0035] As used herein, “at least one of the following: ” and “at least one of ” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0036] As used herein, unless otherwise expressly stated, the “responding to A” execution step does not indicate that the step is executed immediately after “A” occurs, and one or more intermediate steps may be included.

[0037] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that when the terms “comprising,” “including,” “having,” “having,” “including,” and / or “containing” are used herein, they specify the presence of the stated features, elements, and / or components, but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0038] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuit systems); and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits having software / firmware, and (ii) Any part of a hardware processor(s) having software (including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions); and (c) (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but may be absent when operation is not required.

[0039] This definition of circuit system applies to all uses of the term in this application (including in any claim). As another example, as used in this application, the term circuit system also covers only hardware circuitry or a processor (or multiple processors) or portions of hardware circuitry or a processor and its accompanying software and / or firmware implementation. For example, and if applicable to a particular claim element, the term circuit system also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices or other computing or network devices.

[0040] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in the communication network can be performed according to any suitable intergenerational communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), sixth-generation (6G) communication protocols, and / or any other currently known or to be developed in the future. Embodiments of this disclosure can be applied to various communication systems. Due to the rapid development of communication, there will naturally be future types of communication technologies and systems that can be utilized to implement this disclosure. The scope of this disclosure should not be considered limited to the systems described above.

[0041] As used herein, the term "network device" refers to a node in a communications network through which terminal devices access the network and receive services. Depending on the terminology and technology applied, a network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Head (RH), a Remote Radio Head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low-power node (such as a femtosecond or picosecond), a non-terrestrial network (NTN) or non-terrestrial network device (such as satellite network device, low Earth orbit (LEO) satellite, and geostationary orbit (GEO) satellite), aerospace network device, and so on. In some example embodiments, the Radio Access Network (RAN) separation architecture includes a centralized unit (CU) and a distributed unit (DU) at the IAB donor node. The IAB node includes a mobile terminal (IAB-MT) portion that behaves similarly to a user equipment (UE) facing the parent node; and a DU portion of the IAB node that behaves similarly to a base station facing the next-hop IAB node.

[0042] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, UE, subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile terminal (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0043] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication, such as communication between a terminal device and a network device, such as resources in the time domain, resources in the frequency domain, resources in the spatial domain, resources in the code domain, or any other combination of time-domain, frequency-domain, spatial-domain, and / or code-domain resources that enable communication. In the following, unless otherwise expressly stated, resources in both the frequency and time domains will be used as examples of transmission resources to describe some exemplary embodiments of this disclosure. Note that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0044] Figure 1 An example communication environment 100 in which example embodiments of the present subject matter can be implemented is shown. For example... Figure 1 As shown, the communication environment 100 may involve one or more RAN nodes 110-1, 110-2...110-N, through which terminal devices (e.g., UEs) can obtain access to the communication system. RAN nodes 110-1, 110-2...110-N may be collectively referred to or individually as RAN node 110. It should be understood that although only two RAN nodes are shown, the RAN of the communication environment 100 may have any suitable number of RAN nodes.

[0045] The communication environment 100 may also involve a core network (CN), which may include NFs such as Access and Mobility Management Functions (AMF) 120. AMF 120 may be configured to provide various functions related to security, access management and authorization for terminal equipment (e.g., UE).

[0046] The CN may also include a Session Management Element (SMF) 130, which is configured to implement the SMF within the CN. The SMF 130 is also configured to interact with the decoupled data plane, create, update, and remove Protocol Data Unit (PDU) sessions, and utilize User Plane Function (UPF) 140 to manage session context for end devices (e.g., UEs). The SMF 130 is in or included in a network node configured to provide the SMF. The UPF 140 is in or included in a network node configured to provide user plane functions. Figure 1 As shown, RAN node 110 can be connected to AMF 120 for control plane interaction and can be connected to UPF 140 for user plane interaction.

[0047] The core network (CN) can include various network service nodes (NFs). These NFs can be configured to provide specific services and / or interact with services provided by RAN node 110. NFs are responsible for facilitating basic functions such as network slice management, enforcement of policies and accounting rules, authentication and authorization, and other related operations.

[0048] Within an NF, an NF can be specifically designed to handle charging-related functions within the core network. For example, an NF may include Policy Control Function (PCF) 150-1 and Charging Function (CHF) 150-2 related to charging functions for terminal devices. PCF 150-1 and CHF 150-2 may sometimes be collectively referred to or separately as NF 150 related to charging functions.

[0049] The PCF 150-1 is responsible for managing policy decisions within the network, including Quality of Service (QoS) enforcement and flow-based accounting. The PCF 150-1 can interact with other network functions, such as the SMF 130, to ensure that policy rules are correctly applied to user sessions and data flows.

[0050] In some examples, CHF 150-2 can play a key role in the monetization of network services. CHF 150-2 can collect, process, and provide billing-related data, enabling real-time or offline billing for network usage. CHF 150-2 interacts with PCF 150-1 to apply billing rules based on predefined policies and service usage by connected devices.

[0051] Additionally, the core network may include various other NFs, such as UDM 160-1, UDSF 160-2, and other (multiple) NFs 160-3 (collectively referred to as NF 160), which may be configured to provide other specific services and / or interact with services provided by RAN node 110.

[0052] UDM 160-1 corresponds to the Unified Data Management (UDM) function. UDM 160-1 can manage structured subscription data, such as user identifiers, authentication credentials, and subscription profiles.

[0053] UDSF 160-2 corresponds to the Unstructured Data Storage Function (UDSF). UDSF 160-2 provides storage for unstructured data, such as application-specific configurations, log information, or other network-related data that does not conform to structured formats. UDSF 160-2 enables flexible data storage and retrieval through its service-based API, supporting various network functions, including policy and accounting enforcement.

[0054] These NFs can work together to enable efficient operation and management of the core network, ensuring that the network can support a wide range of services and use cases, while maintaining robust policy enforcement, billing mechanisms, and service level guarantees.

[0055] It should be understood that Figure 1 The number of network nodes and terminal devices shown is provided for illustrative purposes and does not imply any limitation. The communication environment 100 may include any suitable number of network nodes and terminal devices.

[0056] Communication in communication environment 100 can be implemented according to any suitable communication protocol(s), including but not limited to cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), and sixth-generation (6G), wireless local area network communication protocols, such as IEEE 802.11, and / or any other currently known or to be developed in the future. Furthermore, the communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other currently known or to be developed in the future.

[0057] Figure 2 An example protocol stack architecture 200 for communication between control plane (CP) and user plane (UP) functions in a 5G network is shown. The diagram illustrates the interaction across reference points Sx (Serving Gateway Control Plane and User Plane Interface), N4, and N4mb (N4 Multicast / Broadcast Interface), which facilitates the exchange of signaling and control information between the CP and UP.

[0058] like Figure 2 As shown, both the CP and UP functions can implement a layered protocol stack, which consists of multiple layers, each performing a specific function to ensure seamless communication. This protocol stack may include the following layers:

[0059] PFCP (Packet Forwarding Control Protocol): Located at the top layer of the stack, PFCP handles signaling between CP and UP functions, enabling session management and user plane configuration. PFCP allows CP functions to provide UP functions with instructions regarding traffic routing, QoS rules, and traffic control.

[0060] UDP (User Datagram Protocol): Under PFCP, UDP can provide a transport layer for PFCP messages, providing a connectionless communication mechanism between CP and UP functions.

[0061] IP (Internet Protocol): The IP layer is responsible for network addressing and routing, ensuring that packets are correctly forwarded between CP and UP nodes.

[0062] L2 (Layer 2): The data link layer (L2) can provide a reliable transmission medium, facilitating the encapsulation and delivery of packets across the network.

[0063] L1 (Layer 1): The physical layer (L1) can define the electrical, optical, or radio frequency signals used for the physical transmission of data between the CP and UP functions.

[0064] Bidirectional communication across these layers between CP and UP functions ensures effective coordination of control plane and data plane operations. The Sx, N4, and N4mb reference points can be used as interfaces to enable bidirectional interaction, which is crucial for implementing a Control-and-Forward Separation (CUPS) architecture in current networks.

[0065] In addition to supporting the N4 interface, UPF can also implement a RESTful API for enhanced functionality. For example, services exposed via events through the NuPF interface (represented as "...") Nupf_EventExposure The "service" can provide UPF-related information to the Consumer Network Function (NF); while the service that retrieves the location and access information of terminal devices (represented as "...") Nupf_GetUE PrivateIPaddrAndIdentifiers The service can expose UPF information about details related to Network Address Translation (NAT) and Subscription Permanent Identifier (SUPI), supporting network functions that require these specific data points.

[0066] In current communication systems, billing functions can be implemented through coordinated interaction between the SMF, CHF, PCF, and UPF. The SMF can interact with the CHF and PCF, exchanging information based on information received from other control panels (NFs) and user plane information received from the UPF.

[0067] The SMF can manage subscriber-related information, including QoS data flow levels and PDU session level data. To minimize complexity, only information can be requested from the UPF, while higher-level session and subscriber information is retained at the SMF.

[0068] To facilitate usage reporting, the SMF can generate URRs based on locally configured policies and Policy and Charging Control (PCC) rules. These URRs can be sent to the UPF and associated with Packet Detection Rules (PDRs) to handle specific traffic corresponding to the URR. The SMF can assign monitoring keys to each URR and maintain a mapping between monitoring keys and URRs. Additionally, the SMF can configure reporting triggers for the UPF based on predefined policies and send these triggers to the UPF.

[0069] UPF can monitor traffic based on URR and report usage information back to SMF. SMF can further enrich the data with additional information (such as UE location) before forwarding it to CHF and PCF. This process ensures accurate billing, policy enforcement, and QoS management within the current communication system.

[0070] Service-based architecture (SBA) offers significant potential, particularly in the communication between the UPF and NFs, including the CHF and PCF, via implicit subscriptions and direct notifications. However, for billing-related functions, existing communication systems do not provide the UPF with mechanisms for implicit subscriptions or direct notifications from the UPF for billing functions.

[0071] In an example embodiment of this disclosure, a solution for data flow billing reporting via user plane functions is provided. This solution enables implicit subscription and direct notification in data flow billing reporting via a User Plane Function (UPF). In this solution, the User Plane Function (SMF) generates a billing identifier that uniquely identifies at least one data flow associated with an end device. This billing identifier is included in session request information sent to the UPF. Additionally, the session request information contains access information for at least one Network Function (NF), which is configured to perform network functions related to the billing of the identified data flow. Through this solution, the SMF facilitates implicit subscription to billing updates, while the UPF, together with the NF(s), establishes direct notification to ensure efficient and accurate billing reporting for the identified data flow.

[0072] By leveraging implicit subscription and direct notification mechanisms, the UPF is enabled to process user plane information related to data flows and notify relevant network nodes (such as the CHF and PCF) for billing purposes. This solution effectively facilitates implicit subscriptions on behalf of other NFs, as well as direct notifications from the UPF, thereby bridging existing gaps in the billing functionality framework.

[0073] In some example embodiments, the location information of the terminal device may need to be included in usage reports when the radio access technology (RAT) changes or location changes occur, as these events can affect billing. Therefore, in some example embodiments, the proposed solution may also introduce mechanisms to incorporate the location information of the terminal device through both control panel-based and user panel-based methods, and may include the location information of the terminal device (e.g., UE) during billing and usage monitoring processes.

[0074] Figure 3 Signaling flow 300 for session initiation and session notification according to some example embodiments of this disclosure is shown. Signaling flow 300 will refer to... Figure 1 The signaling flow 300 involves SMF 130, UPF 140, and one or more NF150s. In this document, SMF 130 may sometimes be referred to as the "first device". In this document, UPF 140 may sometimes be referred to as the "second device". In this document, NF may sometimes be referred to as the "third device".

[0075] Multiple NFs 150 may include one or more NFs configured to provide charging-related network functions for at least one data flow based on user plane information associated with at least one data flow received from UPF140. In some examples, if an NF 150 is configured to provide charging functions, it may sometimes be referred to as "CHF"; or if an NF 150 is configured to provide policy control functions, it may sometimes be referred to as "PCF".

[0076] In signaling flow 300, SMF 130 generates (306) a charging identifier for at least one data flow identifying the terminal device. This at least one data flow may include one or more QoS flows and / or PDU sessions. In some examples, the charging identifier (ID) may be configured to group multiple QoS flows and / or PDU sessions of UPF 140 to associate these QoS data flows and / or sessions for charging-related notifications, as will be described later.

[0077] In some example embodiments, SMF 130 may receive a request from a terminal device that requests the establishment of a PDU session, and upon receiving the PDU session establishment request, SMF 130 may establish a policy association with PCF, and PCF may establish a CHF session for spending restrictions.

[0078] In some example embodiments, SMF 130 may receive (304) at least one container related to billing from (multiple) NF 150s. In some example embodiments, NF 150 may send (302) at least one container related to billing to SMF 130. In some example embodiments, if NF 150 is configured to provide policy control functionality, then NF 150 may be a PCF. In some example embodiments, if NF 150 is configured to provide billing functionality, then NF 150 may be a CHF. In some examples, containers sent from CHF are related to data usage reporting, and containers sent from PCF are related to data usage monitoring.

[0079] SMF 130 sends a (308) session request message to UPF 140, which is configured to provide user plane functionality. The session request message includes at least the accounting identifier and access information of at least one network node, i.e., the access information of (multiple) NF 150s.

[0080] UPF 140 receives (310) session request information from SMF 130, which is configured to provide session management functions. As described above, the session request information includes at least one billing identifier and access information of NF 150.

[0081] In some example embodiments, session request information may be included in a session establishment request sent from SMF 130 to UPF 140 during the session establishment process. In some examples, the session establishment request invoked by SMF 130 may be a Nupf session establishment request (non-user plane function). In some example embodiments, session request information may be included in a session modification request sent from SMF 130 to UPF 140 during the session modification process. In some examples, the session modification request invoked by SMF 130 may be a Nupf session modification.

[0082] In some example embodiments, SMF 130 may indicate access information of the Access and Mobility Management Function (AMF) to UPF 140 via session request information. In some examples, the AMF access information may include the corresponding AMF address and the instance identifier of the AMF set.

[0083] In some example embodiments, SMF 130 may alternatively or additionally indicate the subscriber permanent identifier (SUPI) of the terminal device to UPF 140 via a session request message.

[0084] In some example embodiments, SMF 130 may alternatively or additionally indicate to UPF 140 via session request information at least one billing counter for the terminal device. In some example embodiments, SMF 130 may alternatively or additionally indicate via session request information at least one cost limit for the terminal device.

[0085] In some example embodiments, SMF 130 may alternatively or additionally indicate to UPF 140 via session request information at least one container related to billing provided by NF 150. In some examples, at least one container provided to SMF 130 by PCF 150-1 may be a usage monitoring container. In some examples, at least one container provided to SMF 130 by CHF 150-2 may be a usage reporting container.

[0086] In some examples, in addition to at least one container, SMF 130 may also indicate selection details for PCF 150-1 via session request information, where the selection details for PCF 150-1 correspond to the PCF address, PCF set, and PCF request ID set during the establishment of the Npcf service. In some examples, in addition to at least one container, SMF 130 may indicate selection details for CHF 150-2 via session request information, where the selection details for CHF 150-2 correspond to the CHF address, CHF set, and CHF request ID set during the establishment of the Nchf service (e.g., ...). ConvergedCharging The service handles both online and offline billing modes; OfflineOnlyCharging This service only handles offline billing.

[0087] In some example embodiments, SMF 130 may alternatively or additionally indicate via a session request information indication flag whether UPF 14 also needs to send user plane information to SMF 130.

[0088] In some examples, UPF 140 may send (312) a response acknowledging receipt of the session request information to SMF 130, and SMF 130 may receive (314) a response acknowledging receipt of the session request information. In some examples, the response may include a session establishment response, which also acknowledges the establishment of the session if the session request information was sent in the session establishment request. In some examples, the response may include a session modification response, which also acknowledges modification of the session if the session request information was sent in the session modification request.

[0089] In some example implementations, SMF 130 can send access information of UPF 140 to (multiple) NF 150s. In some examples, the access information of UPF 140 can be sent to other NFs via notification messages. In some examples, after a session is established, SMF 130 or UPF 140 can provide access information of UPF 150 to (multiple) NF 150s, which may include the UPF address and instance identifier of the UPF set, enabling direct communication between UPF 140 and (multiple) NF 150s for any updates regarding billing.

[0090] Using the session request information received from SMF 130, UPF 140 determines (316) user plane information associated with at least one data flow based on the billing identifier indicated in the session request information. In some examples, UPF 140 may prepare billing reports and related triggers after receiving the session request information.

[0091] UPF 140 sends a (318) notification to NF 150 based on the access information of NF 150, the notification including user plane information related to at least one data flow. NF 150 receives a (320) notification from UPF 140, which is configured to provide user plane functionality, the notification including user plane information related to at least one data flow of a terminal device identified by a charging identifier.

[0092] In some example embodiments, UPF 140 may send a notification to CHF including a usage report associated with at least one data stream, the trigger type of the usage report, and location information of the terminal device. In some examples, when a trigger condition is met (such as a Quality Processing Trigger (QHT) being met), UPF 140 may send a notification to CHF addressed based on address information received by UPF 140 in the container, including details corresponding to the usage report and the corresponding trigger type. In some examples, CHF may send a (322) response to UPF 140, which may include an updated usage quota and an updated trigger (if any). In some examples, UPF 140 may receive a (324) response from CHF, which may include an updated usage quota and an updated trigger (if any).

[0093] In some example embodiments, UPF 140 may send a notification to PCF including usage monitoring information related to at least one data flow. In some example embodiments, UPF 140 may receive from PCF update information related to usage quotas and / or triggering of at least one update for usage reports related to at least one data flow.

[0094] In some examples, when triggering conditions (such as QHT) are met, the UPF 140 can send a notification to the PCF, addressed based on address information received by the UPF 140 in the container. This notification includes details corresponding to the usage report and the corresponding trigger type. In some examples, the PCF can send a response to the UPF 140, which may include updated usage quotas and updated triggers (if any).

[0095] In some example embodiments, UPF 140 may send a (328) notification to SMF 130, the notification including user plane information related to at least one data stream. In some example embodiments, SMF 130 may receive a (330) notification from UPF 140, the notification including user plane information related to at least one data stream.

[0096] In some examples, if the flag is set in the session request information, the UPF 140 can also report to the SMF 130 about the usage reports that the UPF 140 has previously sent to the CHF, and the usage monitoring items that the UPF 140 has previously sent to the PCF.

[0097] Multiple NF 150s perform (326) network functions related to the billing of at least one data flow based on received user plane information. For example, PCF 150-1 may receive usage monitoring reports from UPF 140, which may include detailed information such as data flow usage and monitoring events, to perform policy control functions by enforcing usage restrictions or triggering specific actions. Similarly, CHF 150-2 may receive usage reports from UPF 140, which may include information such as data consumption of end devices and session duration, to calculate and apply corresponding billing rules for the data flow.

[0098] exist Figure 3 In stream 300, at least one NF 150 is configured to communicate directly with UPF 140 to obtain user plane information related to the data stream(s) of the terminal device. This direct communication allows the NF 150 to efficiently implement billing-related functions. The process involves implicit subscription and direct notification, ensuring timely access to the required data stream information without the need for unnecessary intermediaries.

[0099] To achieve correct billing for at least one data stream, usage reporting is required when the RAT or location information of the terminal device changes. This disclosure introduces mechanisms, using both control panel-based and user panel-based methods, to incorporate the terminal device's location information and include it in the billing and usage monitoring process. Various options will be described in detail below. References will be made below. Figure 4A , Figure 4B , Figure 5A ,as well as Figure 5B These embodiments will be described below.

[0100] like Figure 4A and Figure 4B As shown, an example embodiment of the CP-based method could be that the AMF or SMF notifies the UPF via the SBI interface. It should be understood that this notification only occurs when the terminal device's mobility parameters change during the established PDU session. The SMF can provide AMF address information, such as address and instance ID, during the session establishment / modification process. The UPF can subscribe to the AMF for the terminal device to receive updated terminal device location information.

[0101] Other or alternative locations, such as Figure 4B As shown, the UPF can provide the SMF with a subscription flag for terminal device location information during the N4 session establishment / modification response process. The SMF can subscribe to UE location information from the AMF on behalf of the UPF, which provides the UPF address information. The AMF can use the UPF address information to provide the UPF with the terminal device location information.

[0102] like Figure 5A and Figure 5B As shown, an example embodiment of the UP-based method can enhance the current N3 header, so the enhanced N3 header includes terminal device mobility information. Specifically, the UPF determines changes in mobility parameters associated with the UE. Configuration for the RAN node in the core network to provide terminal device mobility parameters for a session via N3 can be performed via the control panel using the PDU session establishment / modification and N2 PDU session resource establishment / modification procedures. Configuration for the RAN to provide mobility parameters for a session via N3 can be performed via the user panel during the tunnel establishment process. Mobility parameters can be sent in the GTP-U (extended) header.

[0103] The following describes two example embodiments for obtaining terminal device location information: a control panel-based method and a user panel-based method. Figure 4A and Figure 4B An example embodiment of the CP-based method is shown, while Figure 5A and Figure 5B An example embodiment of the UP-based method is shown.

[0104] Figure 4A Signaling stream 400A based on a first CP for obtaining terminal device location information via UPF subscription to AMF is shown according to some example embodiments of the present disclosure.

[0105] Signaling streams 400A and 400B involve AMF 120, SMF 130, UPF 140, and UDM / UDSF 160-1 / 160-2. In this document, AMF 120 may sometimes be referred to as the "fourth device".

[0106] like Figure 4A As shown, SMF 130 sends (410) session request information to UPF 140, and UPF 140 receives (412) session request information from SMF 130. In some example embodiments, the session request information may be session establishment request information or session modification request information. In some examples, in addition to including, as referenced... Figure 3 In addition to the parameters described in detail in the above paragraphs, the session request information may also include AMF 120 access information, such as the AMF 120's address and configuration information.

[0107] In some examples, if SMF 130 does not include AMF access information in the session request information sent to UPF 140, UPF 140 may send an acquisition request (414) to UDM / UDSF 160-1 / 160-2. In some examples, if SMF 130 does not include AMF access information in the session request information sent to UPF 140, UDM / UDSF 160-1 / 160-2 may receive an acquisition request (416) from UPF 140.

[0108] In some examples, UPF 140 can be configured to communicate with UDM / UDSF 160-1 / 160-2 to obtain access information of the service AMF 120 of the terminal device identified by SUPI via a NudmGet request. In some examples, UDM / UDSF160-1 / 160-2 can send (418) access information of AMF 120 to UPF 140, and UPF 140 can receive (420) access information of AMF 120 from UDM / UDSF160-1 / 160-2.

[0109] In some example embodiments, based on the receipt of session request information, UPF 140 may send (422) a subscription request for mobility events of the terminal device based on AMF access information to AMF 120, AMF 120 being configured to provide AMF, the subscription request including the terminal device's SUPI. In some example embodiments, based on the receipt of session request information, AMF 120 may receive (424) a subscription request for mobility events of the terminal device based on AMF access information from UPF 140, the subscription request including the terminal device's SUPI.

[0110] In some embodiments, UPF 140 may subscribe to the event exposure service of AMF 120 regarding the mobility events of the UE. In some examples, UPF 140 may also subscribe to events other than the mobility events of the terminal device, such as the terminal device connectivity events.

[0111] In some example embodiments, AMF 120 may send a (426) response to UPF 140, wherein the response includes mobility information of the terminal device. In some example embodiments, UPF 140 may receive a (438) response from AMF 120, wherein the response includes mobility information of the terminal device.

[0112] Figure 4B Signaling stream 400B is shown for a second CP-based method for obtaining terminal device location information by subscribing to an AMF via an SMF on behalf of a UPF, according to some example embodiments of the present disclosure.

[0113] like Figure 4B As shown, SMF 130 sends (410) session request information to UPF 140, and UPF 140 receives (412) session request information from SMF 130. In some example embodiments, the session request information may be session establishment request information or session modification request information. In some examples, in addition to including, as referenced... Figure 3 In addition to the parameters described in detail in the above paragraphs, the session request information may also include AMF 120 access information, such as the AMF 120's address and configuration information.

[0114] In some examples, if SMF 130 does not include AMF access information in the session request information sent to UPF 140, UPF 140 may send an acquisition request (414) to UDM / UDSF 160-1 / 160-2. In some examples, if SMF 130 does not include AMF access information in the session request information sent to UPF 140, UDM / UDSF 160-1 / 160-2 may receive an acquisition request (416) from UPF 140.

[0115] In some examples, UPF 140 can be configured to communicate with UDM / UDSF 160-1 / 160-2 to obtain access information of the service AMF 120 of the terminal device identified by SUPI via a NudmGet request. In some examples, UDM / UDSF160-1 / 160-2 can send (418) access information of AMF 120 to UPF 140, and UPF 140 can receive (420) access information of AMF 120 from UDM / UDSF160-1 / 160-2.

[0116] In some example embodiments, UPF 140 may send (430) subscription information for mobility events of the terminal device at AMF 120 to SMF 130, the subscription information including an indication of the mobility event, the SUPI of the terminal device, and access information of AMF 120. In some example embodiments, UPF 140 may receive (432) subscription information for mobility events of the terminal device at AMF 120 from UPF 140, the subscription information including an indication of the mobility event, the SUPI of the terminal device, and access information of AMF 120.

[0117] In some examples, SMF 130 may send a (434) subscription request to AMF 120 for an implicit subscription by UPF 140 on behalf of the terminal device mobility event, wherein the subscription request may include the address and configuration information of UPF 140, and subscription information via UPF 140. In some examples, AMF 120 may receive a (436) subscription request from SMF 130 for an implicit subscription by UPF 140 on behalf of the terminal device mobility event, wherein the subscription request may include the address and configuration information of UPF 140, and subscription information via UPF 140.

[0118] In some example embodiments, AMF 120 may send a (438) response to UPF 140, wherein the response includes mobility information of the terminal device. In some example embodiments, UPF 140 may receive a (440) response from AMF 120, wherein the response includes mobility information of the terminal device.

[0119] Figure 5A Signaling flow 500A for a method based on a first UE for obtaining UE location information, according to some example embodiments of this disclosure, is shown. In the method based on the first UP, the UPF instructs the RAN node to provide UE location information via the N3 interface through the N2 interface.

[0120] Signaling flows 500A and 500B involve RAN nodes 110, AMF 120, SMF 130, and UPF 140. SMF 130 may sometimes be referred to as the "first device" in this document. UPF 140 may sometimes be referred to as the "second device" in this document. AMF 120 may sometimes be referred to as the "fourth device" in this document.

[0121] like Figure 5AAs shown, in some examples, RAN node 110 can send an uplink (UL) non-access stratum (NAS) signaling transmission request to AMF 120. In some examples, AMF 120 can receive an uplink (UL) non-access stratum (NAS) signaling transmission request from RAN node 110.

[0122] In some examples, AMF 120 can send a (514) PDU session creation request to SMF 130. In some examples, SMF 130 can receive a (516) PDU session creation request from AMF 120.

[0123] In some examples, SMF 130 can send (518) session request information to UPF 140. In some examples, UPF 140 can receive (520) session request information from SMF 130.

[0124] In some examples, UPF 140 may send a (522) session response to SMF 130. In some examples, SMF 130 may receive a (524) session response from UPF 140. This session response may indicate that the UE location information was requested by UPF 140 from RAN node 110 via the N3 interface.

[0125] In some examples, SMF 130 may send a (526) session response to AMF 120. In some examples, AMF 120 may receive a (528) session response from SMF 130. This session response may indicate that the UE location information was requested by UPF 140 from RAN node 110 via the N3 interface.

[0126] In some examples, AMF 120 may send a (530) session response to RAN node 110. In some examples, RAN node 110 may receive a (532) session response from AMF 120. This session response may indicate that the UE location information was requested by UPF 140 from RAN node 110 via the N3 interface.

[0127] In some examples, RAN node 110 may send an acknowledgment response (534) to AMF 120. In some examples, AMF 120 may receive an acknowledgment response (536) from RAN node 110. This acknowledgment response confirms the establishment of the PDU session.

[0128] In some examples, AMF 120 can send an acknowledgment response (538) to SMF 130. In some examples, SMF 130 can receive an acknowledgment response (540) from AMF 120. This acknowledgment response confirms the establishment of the PDU session.

[0129] In some examples, SMF 130 can send an acknowledgment response (542) to UPF 140. In some examples, UPF 140 can receive an acknowledgment response (544) from SMF 130. This acknowledgment response confirms the establishment of the PDU session.

[0130] In some examples, after confirming the PDU session establishment, RAN node 110 may send a (546) ULUP packet to UPF 140, wherein UE location information may be included in the GTP-U (GPRS Tunneling Protocol-User Plane) extended header via the N3 interface. In some examples, after confirming the PDU session establishment, UPF 140 may receive a UL UP packet from RAN node 110, wherein UE location information may be included in the GTP-U (GPRS Tunneling Protocol-User Plane) extended header via the N3 interface.

[0131] Figure 5B Signaling flow 500B for a second UE-based method for obtaining UE location information, according to some example embodiments of this disclosure, is shown. In this method, the UPF instructs the RAN node to provide UE location information via the N3 interface.

[0132] In signaling flow 500B, after the establishment of a PDU session following the same steps described in detail in the preceding sections.

[0133] The N3 interface / GTP-U tunnel establishment process is described below. In some examples, UPF 140 may send (552) a request for UE location information to RAN node 110, wherein the request includes an indication that the UE location is requested from RAN node 110 via the N3 interface. In some examples, RAN node 110 may receive (554) a request for UE location information from UPF 140, wherein the request includes an indication that the UE location is requested from RAN node 110 via the N3 interface.

[0134] In some examples, for UL packets sent from the UE, RAN node 110 is configured to include UE location information in the GTP-U (extended) header via the N3 interface.

[0135] Figure 6 A flowchart of an example method 600 implemented at a first device according to some exemplary embodiments of the present disclosure is shown. For the purposes of discussion, method 600 will be discussed from... Figure 1 The perspective of the first device is described, wherein the first device is SMF130 or the first device is included in SMF130, which is configured to provide session management functions.

[0136] At block 610, the first device generates a billing identifier for at least one data stream that identifies the terminal device.

[0137] At block 620, the first device sends session request information to the second device, which is configured to provide a User Plane Function (UPF). The session request information includes a billing identifier and access information of at least one network node, wherein a corresponding network node of the at least one network node is configured to provide billing-related network functions for at least one data stream based on user plane information related to at least one data stream received from the user plane function.

[0138] In some example embodiments, method 600 further includes: receiving at least one container related to billing from at least one network node; and wherein the session request information further includes at least one container.

[0139] In some example embodiments, method 600 further includes receiving user plane information associated with at least one data stream from a second device.

[0140] In some example embodiments, the session request information may further include at least one of the following: access information of the Access and Mobility Management Function (AMF), the Subscriber Permanent Identifier (SUPI) of the terminal device, at least one billing counter for the terminal device, or at least one spending limit for the terminal device.

[0141] In some example embodiments, method 600 further includes sending UPF access information to at least one network node.

[0142] In some example embodiments, at least one network node includes at least one of the following: a first network node configured to provide a billing function (CHF), or a second network node configured to provide a policy control function.

[0143] In some example embodiments, the session request information is sent to the second device in a session establishment request or session modification request.

[0144] In some example embodiments, method 600 further includes: receiving from a second device subscription information for mobility events of a terminal device at an AMF, the subscription information including: an indication of the mobility event, the SUPI of the terminal device, and access information of the AMF; and sending a subscription request to the AMF, the subscription request including: an indication of the mobility event, the SUPI of the terminal device, and access information of the UPF.

[0145] In some example embodiments, method 600 further includes: receiving an instruction from a second device requesting a radio access network (RAN) node to provide location information of a terminal device through an interface between the RAN node and the UPF; and sending the instruction to the RAN node.

[0146] In some example embodiments, the first device is a network node or the first device is included in a network node configured to provide session management functionality.

[0147] Figure 7 A flowchart of an example method 700 implemented at a second device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, method 700 will be discussed from... Figure 1 The angle of the second device in the description is described, wherein the second device is UPF140 or the second device is included in UPF140, which is configured to provide user plane functionality.

[0148] At block 710, the second device receives session request information from the first device, which is configured to provide a session management function (SMF). The session request information includes a billing identifier and access information of at least one network node, wherein the billing identifier identifies at least one data stream of the terminal device, and a corresponding network node of the at least one network node is configured to provide billing-related network functions for the at least one data stream based on user plane information associated with the at least one data stream.

[0149] At block 720, the second device determines user plane information associated with at least one data stream based on the billing identifier.

[0150] At block 730, the second device sends a notification to at least one network node based on access information of at least one network node, the notification including user plane information related to at least one data stream.

[0151] In some example embodiments, the session request information also indicates a flag for indicating whether the second device sends user plane information to the first device, and wherein the first device is further configured to send user plane information related to at least one data stream to the first device based on the session request information including the flag.

[0152] In some example embodiments, the session request information also indicates at least one of the following: access information of at least one container, access and mobility management function (AMF) related to billing provided by at least one network node, subscriber permanent identifier (SUPI) of the terminal device, at least one billing counter for the terminal device, or at least one spending limit for the terminal device.

[0153] In some example embodiments, method 700 further includes: receiving update information related to the use of quotas from a first network node, and / or triggering at least one update for a usage report related to at least one data stream.

[0154] In some example embodiments, method 700 further includes: receiving update information related to the use of quotas from a second network node, and / or triggering at least one update for a usage report related to at least one data flow.

[0155] In some example embodiments, session request information is sent to the second device in a session establishment request or session modification request.

[0156] In some example embodiments, method 700 further includes: receiving session request information, sending a subscription request to a fourth device for access information based on AMF to the terminal device for mobility events of the terminal device, the fourth device being configured to provide AMF, the subscription request including the terminal device's SUPI; and receiving mobility information of the terminal device from the fourth device.

[0157] In some example embodiments, method 700 further includes: sending subscription information for mobility events of a terminal device at an AMF to a first device, the subscription information including: indication of mobility events, SUPI of the terminal device, and access information of the AMF; and receiving mobility information of the terminal device from a fourth device configured to provide the AMF.

[0158] In some example embodiments, method 700 further includes: sending an instruction to a first device requesting a radio access network (RAN) node to provide location information of a terminal device through an interface between the RAN node and the second device; receiving confirmation of the instruction from the RAN node; and receiving mobility information of the terminal device from the RAN node through the interface between the RAN node and the second device.

[0159] In some example embodiments, method 700 further includes: sending an instruction to the RAN node requesting the RAN node to provide location information of the terminal device through an interface between the RAN node and the second device; and receiving mobility information of the terminal device from the RAN node through the interface between the RAN node and the second device.

[0160] In some example embodiments, the mobility information of the terminal device is included in the header of the uplink user plane packet through the interface between the RAN node and the second device.

[0161] In some example embodiments, the second device is a network node or the second device is included in a network node configured to provide user plane functionality.

[0162] Figure 8 A flowchart of an example method 800 implemented at a third device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, method 800 will be discussed from... Figure 1 The perspective of a third device is described, wherein the third device is NF150 or the third device is included in NF150, which is configured to provide billing-related functions.

[0163] At block 810, the third device receives a notification from the second device configured to provide user plane functionality, the notification including user plane information related to at least one data stream of a terminal device identified by a billing identifier.

[0164] At block 820, the third device performs network functions related to the billing of at least one data stream based on the received user plane information.

[0165] In some example embodiments, method 800 further includes: sending at least one container related to billing to a first device, the first device being configured to provide session management functionality; and wherein the session request information further includes at least one container.

[0166] In some example embodiments, method 800 further includes: receiving access information of the UPF from the first device; and sending a response to the notification to the second device based on the access information of the UPF.

[0167] In some example embodiments, the third device is configured to provide a billing function (CHF), and wherein the third device is configured to: receive a notification from the second device, the notification including: a usage report related to at least one data stream, a trigger type of the usage report, and location information of the terminal device; and perform the CHF based on the usage report, the trigger type, and the location information of the terminal device.

[0168] In some example embodiments, method 800 further includes: receiving a notification from a second device, the notification including: usage monitoring information related to at least one data stream; and performing PCF based on the usage monitoring information.

[0169] In some example embodiments, method 800 further includes: sending update information related to usage quotas to a second device based on UPF access information, and / or triggering at least one update for usage reports related to at least one data stream.

[0170] In some example embodiments, a first means (e.g., a first means, wherein the first means is) capable of performing any of the methods in method 600 Figure 1 The SMF 130 or the first device is included in Figure 1The SMF 130 in the system may include components for performing the corresponding operations of method 600. These components can be implemented in any suitable form. For example, the components can be implemented in a circuit system or a software module. The second device can serve as... Figure 1 The SMF 130 is implemented or included in Figure 1 In SMF 130.

[0171] In some example embodiments, the first apparatus includes: a component for generating a charging identifier for at least one data stream identifying a terminal device; and a component for sending session request information to a second apparatus configured to: provide a User Plane Function (UPF), the session request information including: the charging identifier and access information of at least one network node, wherein a corresponding network node of the at least one network node is configured to: provide network functions related to the charging of at least one data stream based on the user plane information related to the at least one data stream received from the user plane function.

[0172] In some example embodiments, the first apparatus further includes: a component for receiving at least one container related to billing from at least one network node; and wherein the session request information further includes at least one container.

[0173] In some example embodiments, the first device further includes a component for receiving user plane information associated with at least one data stream from the second device.

[0174] In some example embodiments, the session request information may further include at least one of the following: access information of the Access and Mobility Management Function (AMF), the Subscriber Permanent Identifier (SUPI) of the terminal device, at least one billing counter for the terminal device, or at least one spending limit for the terminal device.

[0175] In some example embodiments, the first device further includes a component for sending UPF access information to at least one network node.

[0176] In some example embodiments, at least one network node includes at least one of the following: a first network node configured to provide a billing function (CHF), or a second network node configured to provide a policy control function.

[0177] In some example embodiments, the session request information is sent to the second device in a session establishment request or session modification request.

[0178] In some example embodiments, the first apparatus further includes: a component for receiving subscription information for mobility events of a terminal device at an AMF from the second apparatus, the subscription information including: an indication of the mobility event, the SUPI of the terminal device, and access information of the AMF; and a component for sending a subscription request to the AMF, the subscription request including: an indication of the mobility event, the SUPI of the terminal device, and access information of the UPF.

[0179] In some example embodiments, the first device further includes: a component for receiving an instruction from the second device, the instruction requesting the Radio Access Network (RAN) node to provide location information of the terminal device through an interface between the RAN node and the UPF; and a component for sending the instruction to the RAN node.

[0180] In some example embodiments, the first device is a network node or the first device is included in a network node configured to provide session management functionality.

[0181] In some example embodiments, a second means (e.g., a second means, wherein the second means is) capable of performing any of the methods in method 700 Figure 1 The UPF 140 or the second device is included. Figure 1 The UPF 140 in the document may include components for performing the corresponding operations of method 700. These components can be implemented in any suitable form. For example, the components can be implemented in a circuit system or a software module. The second device can serve as... Figure 1 UPF 140 is implemented or included in Figure 1 In UPF 140.

[0182] In some example embodiments, the second apparatus includes: a component for receiving session request information from a first apparatus, the first apparatus being configured to: provide a Session Management Function (SMF), the session request information including: a charging identifier and access information of at least one network node, wherein the charging identifier identifies at least one data flow of a terminal device, and a corresponding network node of the at least one network node is configured to: provide charging-related network functions for the at least one data flow based on user plane information associated with the at least one data flow; a component for determining user plane information associated with the at least one data flow based on the charging identifier; and a component for sending a notification to the at least one network node based on the access information of the at least one network node, the notification including: user plane information associated with the at least one data flow.

[0183] In some example embodiments, the session request information also indicates a flag for indicating whether the second device sends user plane information to the first device, and wherein the first device is further configured to include a component for sending user plane information related to at least one data stream to the first device based on the session request information including the flag.

[0184] In some example embodiments, the session request information also indicates at least one of the following: access information of at least one container, access and mobility management function (AMF) related to billing provided by at least one network node, subscriber permanent identifier (SUPI) of the terminal device, at least one billing counter for the terminal device, or at least one spending limit for the terminal device.

[0185] In some example embodiments, the second apparatus further includes: a component for receiving update information related to the use of quotas from the first network node, and / or for triggering at least one update of a use report related to at least one data stream.

[0186] In some example embodiments, the second apparatus further includes components for receiving update information related to usage quotas from a second network node, and / or for triggering at least one update to a usage report related to at least one data stream.

[0187] In some example embodiments, session request information is sent to the second device in a session establishment request or session modification request.

[0188] In some example embodiments, the second device further includes: a component for sending a subscription request for mobility events of the terminal device based on AMF access information to a fourth device, the fourth device being configured to provide AMF, the subscription request including the terminal device's SUPI; and a component for receiving mobility information of the terminal device from the fourth device.

[0189] In some example embodiments, the second device further includes: a component for sending subscription information for mobility events of a terminal device at the AMF to the first device, the subscription information including: an indication of the mobility event, the SUPI of the terminal device, and access information of the AMF; and a component for receiving mobility information of the terminal device from a fourth device configured to provide the AMF.

[0190] In some example embodiments, the second device further includes: a component for sending an instruction to the first device, the instruction requesting a radio access network (RAN) node to provide location information of a terminal device through an interface between the RAN node and the second device; a component for receiving confirmation of the instruction from the RAN node; and a component for receiving mobility information of the terminal device from the RAN node through the interface between the RAN node and the second device.

[0191] In some example embodiments, the second device further includes: a component for sending an instruction to the RAN node requesting the RAN node to provide location information of the terminal device through an interface between the RAN node and the second device; and a component for receiving mobility information of the terminal device from the RAN node through the interface between the RAN node and the second device.

[0192] In some example embodiments, the mobility information of the terminal device is included in the header of the uplink user plane packet through the interface between the RAN node and the second device.

[0193] In some example embodiments, the second device is a network node or the second device is included in a network node configured to provide user plane functionality.

[0194] In some example embodiments, a third means capable of performing any of the methods in method 800 (e.g., a third means, wherein the third means is...) Figure 1 The NF 150 or the third device is included. Figure 1 The NF 150 in the document may include components for performing the corresponding operations of method 800. These components can be implemented in any suitable form. For example, the components can be implemented in a circuit system or a software module. A third device can be used as... Figure 1 NF 150 is implemented or included in Figure 1 In NF 150.

[0195] In some example embodiments, the third means includes: a component for receiving a notification from a second means configured to provide user plane functionality, the notification including: user plane information relating to at least one data stream of a terminal device identified by a billing identifier; and a component for performing billing-related network functions relating to the at least one data stream based on the received user plane information.

[0196] In some example embodiments, the third device further includes: a component for sending at least one container related to billing to the first device, the first device being configured to provide session management functionality; and wherein the session request information further includes at least one container.

[0197] In some example embodiments, the third device further includes: a component for receiving access information of the UPF from the first device; and a component for sending a response to the notification to the second device based on the access information of the UPF.

[0198] In some example embodiments, the third device is configured to provide a billing function (CHF), and wherein the third device is configured to: receive a notification from the second device, the notification including: a usage report related to at least one data stream, a trigger type of the usage report, and location information of the terminal device; and perform the CHF based on the usage report, the trigger type, and the location information of the terminal device.

[0199] In some example embodiments, the third device further includes: a component for receiving a notification from the second device, the notification including: usage monitoring information related to at least one data stream; and a component for performing PCF based on the usage monitoring information.

[0200] In some example embodiments, the third device further includes: a component for sending update information related to usage quotas to the second device based on UPF access information, and / or for triggering at least one update of usage reports related to at least one data stream.

[0201] Figure 9 This is a simplified block diagram of a device 900 suitable for implementing an example embodiment of the present disclosure. Device 900 can be provided to implement a communication device, such as... Figure 1 The RAN node 110, AMF 120, SMF 130, UPF 140, NF 150, or NF 160 shown are illustrated. As shown, device 900 includes one or more processors 910, one or more memories 920 coupled to processor 910, and one or more communication modules 940 coupled to processor 910.

[0202] Communication module 940 is used for bidirectional communication. Communication module 940 has one or more interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface required for communication with other network elements. In some example embodiments, communication module 940 may include at least one antenna.

[0203] Processor 910 can be of any type suitable for a local technology network, and by way of non-limiting example, can include one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 900 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock synchronized with the main processor.

[0204] Memory 920 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to: read-only memory (ROM) 924, electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to: random access memory (RAM) 922 and other volatile memories that will not persist during power outages.

[0205] Computer program 930 includes computer-executable instructions that are executed by an associated processor 910. The instructions of program 930 may include instructions for performing operations / actions of some example embodiments of this disclosure. The instructions of program 930 may be stored in memory, such as ROM 924. Processor 910 can perform any suitable actions and processes by loading program 930 into RAM 922.

[0206] Example embodiments of this disclosure can be implemented by program 930, enabling device 900 to execute any process of this disclosure, as referenced. Figures 2 to 8 The exemplary embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.

[0207] In some example embodiments, program 930 may be tangibly contained in a computer-readable medium, which may be included in device 900 (e.g., in memory 920) or in other storage devices accessible by device 900. Device 900 may load program 930 from the computer-readable medium into RAM 922 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. As used herein, the term "non-transitory" is a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., RAM and ROM).

[0208] Figure 10 An example of a computer-readable medium 1000 that can be in the form of a CD, DVD, or other optical storage disk is shown. The computer-readable medium 1000 has a program 930 stored thereon.

[0209] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while others may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0210] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions (such as those included in program modules) that are executed in a device on a target physical or virtual processor to perform any of the methods described above. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. The functionality of program modules can be combined or split among program modules as needed in various embodiments. The machine-executable instructions for program modules can be executed on local or distributed devices. In distributed devices, program modules can reside on both local and remote storage media.

[0211] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0212] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0213] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more lines, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0214] Furthermore, although the operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order or sequence shown, or that all of the operations shown be performed to achieve the desired result. In certain situations, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the foregoing discussion, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features specific to particular embodiments. Unless expressly stated otherwise, certain features described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless expressly stated otherwise, various features described in the context of a single embodiment may also be implemented separately or in any suitable sub-combination in multiple embodiments.

[0215] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. A first device for communication, comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions, the instructions, when executed by the at least one processor, cause the first device to at least: Generate a billing identifier for at least one data stream that identifies the terminal device; as well as A session request message is sent to a second device configured to provide a User Plane Function (UPF). The session request message includes the billing identifier and access information of at least one network node, wherein a corresponding network node of the at least one network node is configured to provide a network function related to the billing of the at least one data stream based on the user plane information related to the at least one data stream received from the UPF.

2. The first device according to claim 1, wherein the first device is further configured to: Receive at least one container related to billing from the at least one network node; and The session request information also includes the at least one container.

3. The first device according to claim 1 or 2, wherein the session request information further includes a flag for indicating whether the second device sends the user plane information to the first device, and wherein the first device is further configured to: Receive the user plane information associated with the at least one data stream from the second device.

4. The first apparatus according to any one of claims 1 to 3, wherein the session request information further comprises at least one of the following: Access information for the Access and Mobility Management Function (AMF); The subscriber permanent identifier SUPI of the terminal device; At least one billing counter for the terminal device; or At least one cost limit for the terminal device.

5. The first device according to any one of claims 1 to 4, wherein the first device is further configured to: The access information of the UPF is sent to the at least one network node.

6. The first apparatus according to any one of claims 1 to 5, wherein the at least one network node comprises at least one of the following: The first network node, configured to provide billing functionality (CHF), or The second network node is configured to provide policy control functions.

7. The first apparatus according to any one of claims 1 to 6, wherein the session request information is sent to the second apparatus in a session establishment request or a session modification request.

8. The first device according to any one of claims 1 to 7, wherein the first device is further configured to: The second device receives subscription information for mobility events of the terminal device at the AMF, the subscription information including: The indication of the mobility event, the SUPI of the terminal device, and the access information of the AMF; as well as A subscription request is sent to the AMF, the subscription request including: the indication of the mobility event, the SUPI of the terminal device, and the access information of the UPF.

9. The first device according to any one of claims 1 to 7, wherein the first device is further configured to: The device receives an instruction requesting the Radio Access Network (RAN) node to provide the location information of the terminal device through the interface between the RAN node and the UPF. The instruction is sent to the RAN node.

10. The first apparatus according to any one of claims 1 to 9, wherein the first apparatus is a network node or the first apparatus is included in the network node, the network node being configured to provide session management functionality.

11. A second means for communication, comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions, the instructions, when executed by the at least one processor, cause the second means to at least: The system receives session request information from a first device configured to provide a session management function (SMF). The session request information includes a billing identifier and access information of at least one network node. The billing identifier identifies at least one data stream of the terminal device, and a corresponding network node of the at least one network node is configured to provide billing-related network functions for the at least one data stream based on user plane information associated with the at least one data stream. Based on the billing identifier, user plane information related to the at least one data stream is determined; and Based on the access information of the at least one network node, a notification is sent to the at least one network node, the notification including: user plane information related to the at least one data stream.

12. The second apparatus of claim 11, wherein the session request information further indicates a flag for indicating whether the second apparatus sends the user plane information to the first apparatus, and wherein the first apparatus is further configured to: Based on the session request information, which also includes the flag, the user plane information related to the at least one data stream is sent to the first device.

13. The second apparatus according to claim 11 or 12, wherein the session request information further indicates at least one of the following: At least one container related to billing provided by the at least one network node; Access information for the Access and Mobility Management Function (AMF); The subscriber permanent identifier SUPI of the terminal device; At least one billing counter for the terminal device; or At least one cost limit for the terminal device.

14. The second apparatus according to any one of claims 11 to 13, wherein the at least one network node includes a first network node configured to provide a charging function (CHF), and wherein the second apparatus is such that: Send a notification to the first network node, the notification including: The usage report associated with the at least one data stream, the trigger type of the usage report, and the location information of the terminal device; and The second device is further configured to: The first network node receives update information related to the use of quotas and / or triggers at least one update for a usage report related to the at least one data stream.

15. The second means according to any one of claims 11 to 14, wherein at least one network node includes a second network node configured to provide a policy control function (PCF), and wherein the second means is such that: Send a notification to the second network node, the notification including: Usage monitoring information related to the at least one data stream; and The second device is further configured to: Receive update information related to quota usage from the second network node, and / or trigger at least one update for usage reports related to the at least one data stream.

16. The second apparatus according to any one of claims 11 to 15, wherein the session request information is sent to the second apparatus in a session establishment request or a session modification request.

17. The second device according to any one of claims 11 to 16, wherein the second device is further configured to: Based on the receipt of the session request information, a subscription request for mobility events of the terminal device based on AMF access information is sent to a fourth device, the fourth device being configured to provide the AMF, the subscription request including the SUPI of the terminal device; and The fourth device receives the mobility information of the terminal device.

18. The second device according to any one of claims 11 to 16, wherein the second device is further configured to: Send subscription information for mobility events of the terminal device at the AMF to the first device, the subscription information including: The indication of the mobility event, the SUPI of the terminal device, and the access information of the AMF; as well as The terminal device receives mobility information from a fourth device configured to provide the AMF.

19. The second device according to any one of claims 11 to 16, wherein the second device is further configured to: Send an instruction to the first device, the instruction requesting the Radio Access Network (RAN) node to provide the location information of the terminal device through the interface between the RAN node and the second device; Receive confirmation of the indication from the RAN node; and The RAN node receives the mobility information of the terminal device through the interface between the RAN node and the second device.

20. The second device according to any one of claims 11 to 16, wherein the second device is further configured to: Send an instruction to the RAN node, the instruction requesting the RAN node to provide the location information of the terminal device through the interface between the RAN node and the second device; and The RAN node receives the mobility information of the terminal device through the interface between the RAN node and the second device.

21. The second apparatus according to claim 19 or 20, wherein the mobility information of the terminal device is included in the header of an uplink user plane packet through the interface between the RAN node and the second apparatus.

22. The second apparatus according to any one of claims 11 to 21, wherein the second apparatus is a network node or the second apparatus is included in the network node, the network node being configured to provide user plane functionality.

23. A third means for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the third device to at least: Receive a notification from a second device configured to provide user plane functionality, the notification including: user plane information related to at least one data stream of a terminal device identified by a billing identifier; as well as Based on the received user plane information, perform network functions related to billing of the at least one data stream.

24. The third device according to claim 23, wherein the third device is further configured to: Send at least one container related to billing to a first device, the first device being configured to provide session management functionality; and The session request information also includes the at least one container.

25. The third device according to claim 24, wherein the third device is further configured to: Receive access information of the UPF from the first device; and Based on the access information of the UPF, a response to the notification is sent to the second device.

26. The third device according to any one of claims 23 to 25, wherein the third device is configured to provide a billing function (CHF), and wherein the third device is such that: Receive a notification from the second device, the notification including: The usage report associated with the at least one data stream, the trigger type of the usage report, and the location information of the terminal device; as well as The CHF is executed based on the usage report, the trigger type, and the location information of the terminal device.

27. The third means according to any one of claims 23 to 25, wherein the third means is configured to provide a policy control function (PCF), and wherein the third means is such that: Receive a notification from the second device, the notification including: Usage monitoring information related to the at least one data stream; as well as The PCF is performed based on the monitoring information used.

28. The third device according to claim 27, wherein the third device is further configured to: Based on the access information of the UPF, send update information related to the usage quota to the second device, and / or trigger at least one update for the usage report related to the at least one data stream.

29. A method for communication, comprising: Generate a billing identifier for at least one data stream that identifies the terminal device; as well as A session request message is sent to a second device configured to provide a User Plane Function (UPF). The session request message includes the billing identifier and access information of at least one network node, wherein a corresponding network node of the at least one network node is configured to provide a billing-related network function for the at least one data stream based on the user plane information related to the at least one data stream received from the UPF.

30. A method for communication, comprising: The system receives session request information from a first device configured to provide a session management function (SMF). The session request information includes a billing identifier and access information of at least one network node. The billing identifier identifies at least one data stream of the terminal device, and a corresponding network node of the at least one network node is configured to provide billing-related network functions for the at least one data stream based on user plane information associated with the at least one data stream. Based on the billing identifier, user plane information related to the at least one data stream is determined; and Based on the access information of the at least one network node, a notification is sent to the at least one network node, the notification including: user plane information related to the at least one data stream.

31. A method for communication, comprising: Receive a notification from a second device configured to provide user plane functionality, the notification including: user plane information related to at least one data stream of a terminal device identified by a billing identifier; and Based on the received user plane information, perform network functions related to the billing of the at least one data stream.

32. A first means for communication, comprising: Components for generating a billing identifier for at least one data stream that identifies a terminal device; as well as A component for sending session request information to a second device configured to provide a User Plane Function (UPF), the session request information including the billing identifier and access information of at least one network node, wherein a corresponding network node of the at least one network node is configured to provide a billing-related network function for the at least one data stream based on the user plane information related to the at least one data stream received from the UPF.

33. A second means for communication, comprising: A component for receiving session request information from a first device, the first device being configured to provide a session management function (SMF), the session request information including a billing identifier and access information of at least one network node, wherein the billing identifier identifies at least one data stream of a terminal device, and a corresponding network node of the at least one network node is configured to provide billing-related network functions for the at least one data stream based on user plane information associated with the at least one data stream. Components for determining user plane information associated with the at least one data stream based on the billing identifier; and A component for sending a notification to the at least one network node based on the access information of the at least one network node, the notification including: user plane information related to the at least one data stream.

34. A third means for communication, comprising: Components for receiving notifications from a second device configured to provide user plane functionality, the notifications including: user plane information related to at least one data stream of a terminal device identified by a billing identifier; and Components for performing network functions related to billing of the at least one data stream based on the received user plane information.

35. A computer-readable medium comprising instructions stored thereon for causing a device to perform at least the method of claim 32, the method of claim 33, or the method of claim 34.

Images