Charging method and device

Abstract

The embodiment of the invention provides a charging method and device. A method performed by a first session management function (SMF) includes sending a protocol data unit (PDU) session creation request to a second SMF. The method further includes receiving, from a second SMF, a PDU session creation response including a first charging identifier for the PDU session. The method further includes sending a first charging data request to a first charging function, the first charging data request including the first charging identifier and a network function instance identifier of the second SMF.

Description

Priority Declaration This application claims priority to PCT application with international application number PCT / CN2023 / 075701 and international filing date February 13, 2023. Technical Field

[0001] Non-limiting and exemplary embodiments of the present disclosure generally relate to the field of communication technology, and particularly to methods and apparatus for billing. Background Art

[0002] This section introduces various aspects that may help to better understand the present disclosure. Therefore, the statements in this section should be read in this light and should not be understood as admissions about what is or is not in the prior art.

[0003] In a communication network, various sessions may exist, such as protocol data unit (PDU) sessions. For example, a user equipment (UE) may request PDU session establishment for a home-routed roaming scenario. The UE or the network may request PDU session modification for a home-routed roaming scenario. The UE may initiate a PDU session handover from an evolved packet system (EPS) to a 5GS (fifth generation system).

[0004] According to clause 5.1.4 of 3GPP TS 32.255 V17.8.0 (the disclosure of which is incorporated herein by reference in its entirety), a Session Management Function (SMF) Charging Identifier (ID) is generated at the first SMF that handles the PDU session initiation request. The first SMF is the SMF in the V-PLMN (Visited Public Land Mobile Network) for home-routed roaming PDU sessions. The Charging ID (i.e., ChargingId) assigned by the Visited Session Management Function (V-SMF) will be transmitted to the Home Session Management Function (H-SMF) in the HPLMN (Home Public Land Mobile Network).

[0005] According to clause 5.1.9 of 3GPP TS 32.255 V17.8.0, for PDU session handover from EPS to 5GS (in V-PLMN), the charging ID is transferred by the H-SMF to the V-SMF via the 'home provided charging ID' (i.e. homeProvidedChargingId). The V-SMF shall replace the existing charging ID previously generated by the V-SMF with this 'home provided charging ID'.

[0006] chargingId / homeProvidedChargingId is encoded as a 32-bit unsigned integer value. Table 1 shows an example of chargingId / homeProvidedChargingId. Table 1 Summary of the Invention

[0007] This Summary is provided in a simplified form to introduce selected concepts that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0008] There may be some problems with existing charging solutions. For example, in the home routing roaming scenario, the charging ID can be generated in the V-SMF (in the case of PDU session establishment using the V-SMF) or in the H-SMF (in the case of PDU session handover from EPS to 5GS using the V-SMF). SMFs on different physical nodes allocate charging IDs independently of each other, which can result in them being assigned the same charging ID.

[0009] For example, the charging identifier may be generated by V-SMF 1. When the charging identifier is transmitted to the H-SMF, the same charging identifier may have been used for other PDU sessions by the H-SMF and / or another V-SMF (V-SMF2) connected to the same H-SMF.

[0010] If the charging identifier is generated by the H-SMF and transmitted to the V-SMF, the same charging ID may have been used by the V-SMF connected to other H-SMFs.

[0011] Therefore, charging ID conflicts may occur between SMFs.In addition, when the same charging ID for different PDU sessions is sent to the charging function (CHF), a charging ID conflict may occur in the CHF.

[0012] To overcome or alleviate at least one of the above problems or other problems, embodiments of the present disclosure provide an improved solution for billing.

[0013] In a first aspect of the present disclosure, a method performed by a first session management function (SMF) is provided. The method includes sending a protocol data unit (PDU) session creation request to a second SMF. The method also includes receiving a PDU session creation response from the second SMF including a first charging identifier for the PDU session. The method also includes sending a first charging data request including the first charging identifier and a network function instance identifier of the second SMF to the first charging function.

[0014] In an embodiment, a combination of the first charging identifier and the network function instance identifier of the second SMF is used as an identifier of the charging data record.

[0015] In an embodiment, the method further comprises allocating a second charging identifier for the PDU session.The method further comprises sending an initial charging data request including the second charging identifier to the first charging function.

[0016] In an embodiment, the first charging data request further comprises a second charging identifier.

[0017] In an embodiment, the first charging identifier, the second charging identifier and the network function instance identifier of the second SMF are used as identifiers of the charging data record.

[0018] In an embodiment, the first charging identifier for the PDU session is received from the second SMF during at least one of Evolved Packet System (EPS) to Fifth Generation System (5GS) idle mode mobility, handover of a home-routed PDU session, or a PDU session establishment procedure for the home-routed PDU session.

[0019] In an embodiment, the network function instance identifier of the second SMF is included in the PDU session information.

[0020] In an embodiment, the first SMF is a visited SMF, the second SMF is a home SMF, and the first charging function is a visited charging function.

[0021] In a second aspect of the present disclosure, a method performed by a second SMF is provided. The method includes receiving a PDU session creation request from a first SMF during a PDU session establishment procedure for a home routing protocol data unit (PDU) session. The method also includes allocating a first charging identifier for the PDU session. The method also includes sending a PDU session creation response including the first charging identifier for the PDU session to the first SMF.

[0022] In an embodiment, a combination of the first charging identifier and the network function instance identifier of the second SMF is used as an identifier of the charging data record.

[0023] In an embodiment, the method further comprises sending a charging data request comprising the first charging identifier to the second charging function.

[0024] In an embodiment, the second charging function is a home charging function.

[0025] In an embodiment, the first SMF is a visited SMF and the second SMF is a home SMF.

[0026] In a third aspect of the present disclosure, a method performed by a first charging function is provided. The method includes receiving a first charging data request from a first session management function (SMF), the first charging data request including a first charging identifier for a protocol data unit (PDU) session and a network function instance identifier of a second SMF. The first charging identifier is assigned by the second SMF. The method further includes updating a charging data record based on the first charging data request.

[0027] In an embodiment, a combination of the first charging identifier and the network function instance identifier of the second SMF is used as an identifier of the charging data record.

[0028] In an embodiment, the first charging identifier is allocated by the second SMF.

[0029] In an embodiment, the method further includes receiving an initial charging data request from the first SMF, the initial charging data request including a second charging identifier for the PDU session. The second charging identifier is allocated by the first SMF. The method further includes opening a charging data record based on the initial charging data request.

[0030] In an embodiment, the first charging data request further comprises a second charging identifier.

[0031] In an embodiment, the first charging identifier, the second charging identifier and the network function instance identifier of the second SMF are used as identifiers of the charging data record.

[0032] In an embodiment, the network function instance identifier of the second SMF is included in the PDU session information.

[0033] In an embodiment, the first SMF is a visited SMF, the second SMF is a home SMF, and the first charging function is a visited charging function.

[0034] In a fourth aspect of the present disclosure, a first SMF is provided. The first SMF includes a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The first SMF is operable to send a protocol data unit (PDU) session creation request to a second SMF. The first SMF is further operable to receive a PDU session creation response from the second SMF including a first billing identifier for the PDU session. The first SMF is further operable to send a first billing data request to a first billing function, the first billing data request including the first billing identifier and a network function instance identifier of the second SMF.

[0035] In a fifth aspect of the present disclosure, a second SMF is provided. The second SMF includes a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The second SMF is operable to receive a PDU session creation request from a first SMF during a PDU session establishment procedure for a home routing protocol data unit (PDU) session. The second SMF is further operable to allocate a first billing identifier for the PDU session. The second SMF is further operable to send a PDU session creation response including the first billing identifier for the PDU session to the first SMF.

[0036] In a sixth aspect of the present disclosure, a first charging function is provided. The first charging function includes a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The first charging function is operable to receive a first charging data request from a first session management function (SMF), the first charging data request including a first charging identifier for a protocol data unit (PDU) session and a network function instance identifier of a second SMF. The first charging identifier is assigned by the second SMF. The first charging function is operable to update a charging data record based on the first charging data request.

[0037] In a seventh aspect of the present disclosure, a first SMF is provided. The first SMF includes a first sending module configured to send a protocol data unit (PDU) session creation request to a second SMF. The first SMF also includes a receiving module configured to receive a PDU session creation response including a first billing identifier for the PDU session from the second SMF. The first SMF also includes a second sending module configured to send a first billing data request to a first billing function, the first billing data request including the first billing identifier and a network function instance identifier of the second SMF.

[0038] In an embodiment, the first SMF further comprises an allocating module configured to allocate a second charging identifier for the PDU session.

[0039] In an embodiment, the first SMF further comprises a third sending module configured to send an initial charging data request comprising the second charging identifier to the first charging function.

[0040] In an eighth aspect of the present disclosure, a second SMF is provided. The second SMF includes a receiving module configured to receive a PDU session creation request from a first SMF during a PDU session establishment procedure for a home routing protocol data unit (PDU) session. The second SMF also includes an allocating module configured to allocate a first billing identifier for the PDU session. The second SMF also includes a first sending module configured to send a PDU session creation response including the first billing identifier for the PDU session to the first SMF.

[0041] In an embodiment, the second SMF further comprises a second sending module configured to send a charging data request comprising the first charging identifier to the second charging function.

[0042] In a ninth aspect of the present disclosure, a first charging function is provided. The first charging function includes a first receiving module configured to receive a first charging data request from a first session management function (SMF), the first charging data request including a first charging identifier for a protocol data unit (PDU) session and a network function instance identifier of a second SMF. The first charging identifier is assigned by the second SMF. The first charging function includes an updating module configured to update a charging data record based on the first charging data request.

[0043] In an embodiment, the first charging function further comprises a second receiving module configured to receive an initial charging data request including a second charging identifier for the PDU session from the first SMF. The second charging identifier is allocated by the first SMF.

[0044] In an embodiment, the first charging function further comprises an enabling module configured to enable charging data recording based on the initial charging data request.

[0045] In another aspect of the present disclosure, a computer program product is provided comprising instructions, which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of the first, second or third aspects.

[0046] In another aspect of the present disclosure, a computer-readable storage medium storing instructions is provided. When the instructions are executed by at least one processor, the instructions cause the at least one processor to perform the method according to any one of the first aspect, the second aspect, or the third aspect.

[0047] The embodiments herein can provide numerous advantages, the following being a non-exhaustive list of examples. In some embodiments herein, they can enable unique billing IDs within the billing system. In some embodiments, they can simplify billing ID generation and reporting. In some embodiments herein, they can avoid billing ID conflicts between SMFs. The embodiments herein are not limited to the features and advantages described above. Those skilled in the art will recognize additional features and advantages upon reading the detailed description below. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The above and other aspects, features and benefits of various embodiments of the present disclosure will become more fully apparent from the following detailed description taken in conjunction with the accompanying drawings, by way of example, in which like reference numerals or letters are used to designate like or equivalent elements. The accompanying drawings are illustrated to facilitate a better understanding of the embodiments of the present disclosure and are not necessarily drawn to scale, wherein:

[0049] Figure 1 Schematically illustrates a 5G system roaming architecture in a home routing scenario using reference point representation according to an embodiment of the present disclosure;

[0050] Figure 2 A flowchart illustrating a charging ID conflict in H-CHF according to an embodiment of the present disclosure is shown;

[0051] Figure 3 A flowchart illustrating a billing ID conflict in V-CHF according to an embodiment of the present disclosure is shown;

[0052] Figure 4 A flowchart of a method according to an embodiment of the present disclosure is shown;

[0053] Figure 5 A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0054] Figure 6a A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0055] Figure 6b A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0056] Figure 7a A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0057] Figure 7b A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0058] Figure 7c A flowchart of PDU session charging establishment in a roaming home routing scenario according to another embodiment of the present disclosure is shown;

[0059] Figure 8a is a block diagram of an apparatus suitable for practicing some embodiments of the present disclosure;

[0060] Figure 8b is a block diagram of a first SMF according to an embodiment of the present disclosure;

[0061] Figure 8c is a block diagram of a second SMF according to an embodiment of the present disclosure;

[0062] Figure 8d is a block diagram of a first billing function according to an embodiment of the present disclosure;

[0063] Figure 9 An example of a communication system according to an embodiment of the present disclosure is shown;

[0064] Figure 10 is a block diagram of a host according to an embodiment of the present disclosure;

[0065] Figure 11 A communication diagram illustrating a host communicating with a UE via a network node over a partial wireless connection according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0066] Embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only for the purpose of enabling those skilled in the art to better understand and therefore implement the present disclosure, and that no limitation on the scope of the present disclosure is suggested. References to features, advantages or similar language throughout the specification do not mean that all features and advantages that can be implemented with the present disclosure should be in or in any single embodiment of the present disclosure. On the contrary, language referring to features and advantages should be understood to mean that specific features, advantages or features described in conjunction with the embodiments are included in at least an embodiment of the present disclosure. In addition, in one or more embodiments, the features, advantages and characteristics described in the present disclosure may be combined in any suitable manner. Those skilled in the relevant art will recognize that the present disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be recognized in certain embodiments, while the additional features and advantages may not be present in all embodiments of the present disclosure.

[0067] As used herein, the term "network" refers to a network that complies with any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), Advanced LTE, Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and other wireless networks. A CDMA network can implement radio technologies such as Universal Terrestrial Radio Access (UTRA). UTRA includes WCDMA and other variants of CDMA. A TDMA network can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network can implement radio technologies such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, Ad-hoc networks, wireless sensor networks, etc. In the following description, the terms "network" and "system" can be used interchangeably. Furthermore, communication between two devices in a network may be performed according to any suitable communication protocol, including but not limited to communication protocols defined by standards organizations such as 3GPP. For example, the communication protocol may include first generation (1G), 2G, 3G, 4G, 4.5G, 5G, 6G communication protocols and / or any other protocol currently known or developed in the future.

[0068] The term "network device" or "network node" refers to any suitable network function (NF) that can be implemented in a (physical or virtual) network entity of a communication network. For example, a network function can be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on an appropriate platform (e.g., on a cloud infrastructure). For example, a 5G system (5GS) may include multiple NFs, such as access and mobility management function (AMF), session management function (SMF), authentication service function (AUSF), unified data management (UDM), policy control function (PCF), application function (AF), network exposure function (NEF), user plane function (UPF) and network repository function (NRF), radio access network (RAN), service communication agent (SCP), network data analysis function (NWDAF), network slice selection function (NSSF), network slice specific authentication and authorization function (NSSAAF), etc. For example, a 4G system (e.g., LTE (Long Term Evolution)) may include a Mobility Management Entity (MME), a Home Subscriber Server (HSS), a PCRF (Policy and Charging Rules Function), a Packet Data Network Gateway (PGW), a PGW Control Plane (PGW-C), a Serving Gateway (SGW), an SGW Control Plane (SGW-C), an E-UTRAN Node B (eNB), etc. In other embodiments, for example, depending on a specific network, the network functions may include different types of NFs.

[0069] The term "terminal device" refers to any terminal device that can access a communication network and receive services therefrom. By way of example and not limitation, a terminal device refers to a mobile terminal, user equipment (UE), or other suitable device. A UE may be, for example, a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT). Terminal devices may include, but are not limited to, portable computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, mobile phones, cellular phones, smartphones, voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable devices, personal digital assistants (PDAs), portable computers, desktop computers, wearable terminal devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPE), etc. In the following description, the terms "terminal device," "terminal," "user equipment," and "UE" may be used interchangeably. As an example, a terminal device may represent a UE configured for communicating in accordance with one or more communication standards promulgated by 3GPP (3rd Generation Partnership Project), such as 3GPP's LTE standard or NR standard. As used herein, a "user equipment" or "UE" may not necessarily have a "user" in terms of a human user who owns and / or operates the associated device. In some embodiments, a terminal device may be configured to send and / or receive information without direct human interaction. For example, when triggered by an internal or external event, or in response to a request from a communication network, a terminal device may be designed to send information to the network according to a predetermined schedule. Alternatively, a UE may represent a device that is intended to be sold to or operated by a human user but may not initially be associated with a specific human user.

[0070] As yet another example, in an Internet of Things (IoT) scenario, a terminal device may represent a machine or other device that performs monitoring and / or measurement, and sends the results of such monitoring and / or measurement to another terminal device and / or network device. In this case, the terminal device may be a machine-to-machine (M2M) device, which may be referred to as a machine type communication (MTC) device in the 3GPP context. As a specific example, the terminal device may be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (e.g., electricity meters), industrial machinery, or household or personal appliances, such as refrigerators, televisions, personal wearable devices (e.g., watches), etc. In other scenarios, the terminal device may represent a vehicle or other device that is capable of monitoring and / or reporting its operating status or other functions related to its operation.

[0071] References in the specification to "one embodiment," "an embodiment," "an exemplary embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is intended that it is within the knowledge of those skilled in the art to affect that feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0072] It should be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of the example 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 associated listed terms.

[0073] As used herein, the phrase "at least one of A and B" or "at least one of A or B" should be understood to mean "only A, only B, or both A and B." The phrase "A and / or B" should be understood to mean "only A, only B, or both A and B."

[0074] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the example embodiments. Unless the context clearly indicates otherwise, as used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well. It will be further understood that when used herein, the terms "include," "comprising," "having," "having," "containing," and / or "covering" specify the presence of stated features, elements, and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0075] Note that these terms are used herein only for convenience of description and to distinguish between nodes, devices, or networks, etc. As technology develops, other terms with similar / identical meanings may also be used.

[0076] In the following description and claims, unless defined otherwise, 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 belongs.

[0077] Although the subject matter described herein can be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to systems that conform to Figure 1 For simplicity, the communication system is described based on the exemplary system architecture shown. Figure 1The system architecture depicts only some exemplary elements. In practice, the communication system may further include any additional elements suitable for supporting communication between terminal devices or between a wireless device and another communication device (e.g., a landline phone, a service provider, or any other network node or terminal device). The communication system may provide communication and various types of services to one or more terminal devices, so that the terminal devices can access and / or use services provided by or via the communication system.

[0078] Figure 1 The 5G system roaming architecture in the case of a home routing scenario using reference point representation according to an embodiment of the present disclosure is schematically illustrated. Figure 1 The architecture is as described in 3GPP TS23.501V18.0.0 Figure 4 .2.4-6, the disclosures of which are incorporated herein by reference in their entirety. Figure 1 The system architecture may include some exemplary elements, such as AUSF, AMF, data network, visited NSSF (V-NSSF), home NSSF (H-NSSF), visited PCF (V-PCF), visited SMF (V-SMF), home SMF (H-SMF), UDM, UPF, AF, UE, (R)AN, NSSAAF (network slice specific authentication and authorization function), etc.

[0079] According to an exemplary embodiment, the UE may establish a signaling connection with the AMF via reference point N1, such as Figure 1 As shown in . This signaling connection enables NAS (Non-Access Stratum) signaling exchange between the UE and the core network, including the signaling connection between the UE and the (R)AN, and the N2 connection for the UE between the (R)AN and the AMF. The (R)AN can communicate with the UPF via reference point N3. The UE can establish a protocol data unit (PDU) session with the data network (e.g., the operator's network or the Internet) through the UPF via reference point N6.

[0080] The N38 reference point may be located between V-SMFs in the same VPLMN, or may be located between V-SMFs in different VPLMNs (to enable inter-PLMN mobility).

[0081] For the above roaming scenarios, each PLMN implements proxy functionality to ensure interconnection security and hide the topology on the inter-PLMN interface.

[0082] like Figure 1As further shown in FIG, it also shows some reference points, such as N1, N2, N3, N4, N6, N9, N11, N38, N16, N7, N5, N22, N15, N8, N24, N10, N58, N12, N31, N59, N13, etc. These reference points can support the interaction between NF services in NF. For example, these reference points can be implemented through corresponding NF service-based interfaces and by specifying some NF service consumers and providers and their interactions to execute specific system processes.

[0083] Figure 1 The various NFs shown in FIG may be responsible for functions such as session management, mobility management, authentication, security, etc. Figure 1 The various NFs shown in may include, for example, functions as defined in 3GPP TS 23.501 V18.0.0 clause 6.2.

[0084] Figure 2 and Figure 3 Some examples of problems with existing billing solutions are shown.

[0085] Figure 2 A flow chart of charging ID conflict in H-CHF according to an embodiment of the present disclosure is shown.

[0086] PDU session establishment process for user session 1.

[0087] Step 1. V-SMF1 receives Nsmf_PDUSession_CreateSMContext request.

[0088] Step 2. V-SMF1 assigns a charging ID with a value of x.

[0089] Step 3. V-SMF1 sends an Nsmf_PDUSession_Create request (chargingId: x) to H-SMF.

[0090] Step 4. H-SMF sends a Charging Data Request [Initial] (chargingId: x) to the Home Charging Function (H-CHF).

[0091] Step 5. H-SMF receives the charging data response from H-CHF.

[0092] Step 6. H-SMF sends an Nsmf_PDUSession_Create response to V-SMF1.

[0093] PDU session establishment process for user session 2

[0094] Step 7. V-SMF2 receives the Nsmf_PDUSession_CreateSMContext request.

[0095] Step 8. V-SMF2 assigns a charging ID with a value of x.

[0096] Step 9. V-SMF2 sends an Nsmf_PDUSession_Create request (chargingId: x) to H-SMF.

[0097] Step 10. H-SMF sends a charging data request [initial] (chargingId: x) to H-CHF.

[0098] Step 11. H-SMF receives charging data response from H-CHF.

[0099] V-SMF1 and V-SMF2 use the same charging ID and transmit the same charging ID to the H-SMF. The H-SMF sends different charging data requests [initial] with the same chargingId:x for different PDU sessions to the H-CHF. Therefore, a charging ID conflict occurs in the H-CHF.

[0100] Figure 2 The messages in may be the same as corresponding messages described in various 3GPP specifications (eg, 3GPP TS 29.502 V18.1.0, 3GPP TS 23.502 V18.0.0, 3GPP TS 32.255 V17.8.0, etc.).

[0101] Figure 3 A flow chart of billing ID conflict in V-CHF according to an embodiment of the present disclosure is shown.

[0102] PDU session establishment process for user session 1

[0103] Step 1. V-SMF receives Nsmf_PDUSession_CreateSMContext request

[0104] Step 2. V-SMF assigns a billing ID with a value of x.

[0105] Step 3. The V-SMF sends a charging data request (chargingId: x) to the visited CHF (V-CHF).

[0106] Step 4. V-SMF receives the charging data response from V-CHF.

[0107] Step 5. V-SMF sends an Nsmf_PDUSession_Create request (chargingId: x) to H-SMF1.

[0108] Step 6. V-SMF receives the Nsmf_PDUSession_Create response from H-SMF1.

[0109] Switching process from EPS to 5GS for user session 2

[0110] Step 7. V-SMF receives the Nsmf_PDUSession_CreateSMContext request.

[0111] Step 8. V-SMF sends an Nsmf_PDUSession_Create request to H-SMF2.

[0112] Step 9. V-SMF receives Nsmf_PDUSession_Create response (homeProvidedChargingId: x) from H-SMF2.

[0113] Step 10. The V-SMF sends a charging data request (chargingId: x) to the visited CHF.

[0114] Step 11. V-SMF receives the charging data response from V-CHF.

[0115] The V-SMF and H-SMF2 use the same Charging ID. The same Charging ID is also transmitted from the H-SMF to the V-SMF. The V-SMF sends different Charging Data Requests [Initial] with the same ChargingId:x for different PDU sessions to the V-CHF. Therefore, a Charging ID conflict occurs in the V-CHF.

[0116] Figure 3 The messages in may be the same as corresponding messages described in various 3GPP specifications (eg, 3GPP TS 29.502 V18.1.0, 3GPP TS 23.502 V18.0.0, 3GPP TS 32.255 V17.8.0, etc.).

[0117] Figure 4 A flowchart of a method according to an embodiment of the present disclosure is shown, which can be performed by an apparatus implemented in a first session management function (SMF), or an apparatus implemented at the first SMF, or an apparatus implemented as the first SMF, or an apparatus communicatively coupled to the first SMF. Therefore, the apparatus can provide components or modules for implementing various parts of method 400, as well as components or modules for implementing other processes in combination with other components.

[0118] At block 402, a first SMF may send a protocol data unit (PDU) session creation request to a second SMF.

[0119] The first SMF may be any suitable network device, node, entity or function capable of providing session management functionality. In an embodiment, the first SMF may be an intermediate SMF (I-SMF) or a visited SMF (V-SMF), as described in 3GPP TS 23.501 V18.0.0.

[0120] For example, because one or more UPFs belong to different SMF service areas and the UE is located in an area that cannot be controlled by the original SMF, the I-SMF may be the SMF inserted to support the PDU session. For example, because one or more UPFs belong to a visited network and the UE is located in a visited network that cannot be controlled by the home SMF, the V-SMF may be the SMF inserted to support the PDU session.

[0121] The second SMF may be any suitable network device, node, entity, or function capable of providing session management functionality. In an embodiment, the second SMF may be an SMF or a packet data network gateway control plane (PGW-C) combined with an SMF (PGW-C+SMF) or a home SMF or anchor SMF (A-SMF), as described in 3GPP TS 23.501 V18.0.0. For example, the H-SMF may be an SMF located in the home network.

[0122] In an embodiment, the first SMF is a visited SMF and the second SMF is a home SMF.

[0123] In an embodiment, the PDU session creation request may be an Nsmf_PDUSession_Create request as described in 3GPP TS 23.502 V18.0.0 and 3GPP TS 32.255 V17.8.0, etc.

[0124] For example, a PDU session creation request may be sent to the second SMF during Evolved Packet System (EPS) to Fifth Generation System (5GS) idle mode mobility, handover of a home-routed PDU session, or a PDU session establishment procedure of a home-routed PDU session, as described in 3GPP TS 23.502 V18.0.0 and 3GPP TS 32.255 V17.8.0.

[0125] At block 404, the first SMF may receive a PDU session creation response from the second SMF including a first charging identifier for the PDU session.

[0126] In an embodiment, the PDU session creation response may be an Nsmf_PDUSession_Create response, as described in 3GPP TS 23.502 V18.0.0 and 3GPP TS 32.255 V17.8.0, etc.

[0127] For example, the PDU session creation response may be received from the second SMF during Evolved Packet System (EPS) to Fifth Generation System (5GS) idle mode mobility, handover of a home-routed PDU session, or a PDU session establishment procedure of a home-routed PDU session, as described in 3GPP TS 23.502 V18.0.0 and 3GPP TS 32.255 V17.8.0, etc.

[0128] The first charging identifier may be any suitable identifier. The first charging identifier may be created to allow association of charging information. In an embodiment, the first charging identifier may be a home provided charging Id as described in 3GPP TS 32.255 V17.8.0.

[0129] As described in clause 5.1.4 of 3GPP TS 32.255 V17.8.0, for SMFs, including the case of I-SMF insertion, the charging identifier is assigned per PDU session. When each PDU session is established (i.e. a new PDU session ID is assigned), a new PDU session-specific SMF charging identifier is generated on the first SMF that handles the PDU session initiation request. This SMF charging identifier should be unique within the SMF that assigns it (this means that if an SMF set is used, the charging identifier is unique within the SMF set) and is then used in all subsequent messages for this PDU session. Once the charging identifier is assigned, the charging identifier should be used throughout the life cycle of the PDU session. In the event of an inter-system change or handover of a PDU session, the charging identifier will also be retained as long as the PDU session identifier is retained.

[0130] In an embodiment, the first charging identifier may exist during a handover of EPS to 5GS idle mode mobility or a HR PDU session. In an embodiment, the first charging identifier may exist during a PDU session establishment procedure of a HR PDU session.

[0131] In an embodiment, the chargingId information element (IE) in the SmContext (see clause 6.1.6.2.39 of 3GPP TS 32.255 V17.8.0) may be set to the value received in the homeProvidedChargingId IE during EPS to 5GS idle mode mobility or handover of an HR PDU session or PDU session establishment procedure of an HR PDU session.

[0132] In an embodiment, upon each establishment of a PDU session (ie, allocation of a new PDU session ID), a new PDU session specific SMF charging identifier is generated at the SMF in the H-PLMN and transmitted to the SMF in the V-PLMN.

[0133] At block 406, the first SMF may send a first charging data request to the first charging function, the first charging data request including the first charging identifier and the network function instance identifier of the second SMF.

[0134] The first charging function may be any suitable network device, node, entity or function capable of providing charging functionality.In an embodiment, the first charging function may be a visited charging function as described in 3GPP TS 23.501 V18.0.0 and 3GPP TS 32.255 V17.8.0.

[0135] In an embodiment, the first SMF is a visited SMF, the second SMF is a home SMF and the first charging function is a visited charging function.

[0136] In an embodiment, the first charging data request may be a charging data request as described in 3GPP TS 32.255 V17.8.0. For example, the first charging data request including the first charging identifier allocated by the second SMF may be of the [Update and Terminate] type. For example, the first charging data request including the first charging identifier allocated by the second SMF may be of the [Initial] type. 3GPP TS 32.255 V17.8.0 describes the Charging Data Request [Initial], Charging Data Request [Update], and Charging Data Request [Terminate]. 3GPP TS 32.255 V17.8.0 also describes the default trigger conditions for these charging data requests in the SMF.

[0137] In an embodiment, the first charging data request may be sent to the first charging function during at least one of Evolved Packet System (EPS) to Fifth Generation System (5GS) idle mode mobility, handover of a home-routed PDU session, or PDU session establishment of a home-routed PDU session.

[0138] In an embodiment, the network function instance identifier of the second SMF may be a network function instance identifier of an SMF in the H-PLMN.

[0139] In an embodiment, a combination of the first charging identifier and the network function instance identifier of the second SMF may be used as an identifier of the charging data record.

[0140] In an embodiment, the network function instance identifier of the second SMF may be included in the PDU session information, as described in clause 6.1.6.2.2.8 of 3GPP TS 32.291 V18.0.0, the disclosure of which is incorporated herein by reference in its entirety.

[0141] Figure 5 A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by an apparatus implemented in a first session management function (SMF), or an apparatus implemented at a first SMF, or an apparatus implemented as a first SMF, or an apparatus communicatively coupled to a first SMF. Therefore, the apparatus can provide components or modules for implementing various parts of method 500, as well as components or modules for implementing other processes in combination with other components. For the sake of brevity, descriptions of certain parts that have been described in the above embodiments are omitted here.

[0142] At block 502, the first SMF may allocate a second charging identifier for the PDU session. For example, when each PDU session is established (i.e., a new PDU session ID is allocated), a new PDU session-specific SMF charging identifier is generated at the first SMF that processes the PDU session initiation request.

[0143] In an embodiment, the first SMF (e.g., V-SMF) may allocate a second charging identifier for the PDU session during at least one of Evolved Packet System (EPS) to Fifth Generation System (5GS) idle mode mobility, handover of a home-routed PDU session, or a PDU session establishment process for a home-routed PDU session.

[0144] At block 504, the first SMF may send an initial charging data request including the second charging identifier to the first charging function.

[0145] In an embodiment, the initial charging data request may be a charging data request as described in 3GPP TS 32.255 V17.8.0. For example, the initial charging data request may have an [Initial] type. 3GPP TS 32.255 V17.8.0 describes the charging data request [Initial]. 3GPP TS 32.255 V17.8.0 also describes the default trigger condition for the charging data request [Initial] in the SMF.

[0146] In an embodiment, blocks 502 and 504 may be Figure 4 Blocks 402, 404, and 406 are executed before.

[0147] In an embodiment, the first charging data request may further include a second charging identifier.

[0148] In an embodiment, the first charging identifier, the second charging identifier and the network function instance identifier of the second SMF are used as identifiers of the charging data record.

[0149] In an embodiment, the V-SMF may or should use the charging ID provided by this home location together with the charging ID (the charging ID created by the V-SMF) in a subsequent charging data request message.

[0150] In an embodiment, for EPS handover to 5GS in a home routing scenario, a charging identifier for the EPS Packet Data Network (PDN) connection will be generated by the PGW-C+SMF in the HPLMN and transmitted to the SMF in the VPLMN.

[0151] In an embodiment, if the V-SMF has generated a charging identifier, the V-SMF may use the charging ID provided by the home location and the charging ID (the charging ID created by the V-SMF) in a subsequent charging data request message.

[0152] In an embodiment, in the home routing scenario, the parameter exchanged when the PDU session is established is the home-provided charging ID, which includes the charging ID allocated by the H-SMF and transmitted by the H-SMF to the V-SMF. The V-SMF can use the home-provided charging ID together with the charging ID (the charging ID created by the V-SMF) for subsequent charging data request messages.

[0153] In an embodiment, in a home routing scenario, the parameter exchanged during the PDU session handover from EPS to 5GS is the home-provided charging ID, which includes the charging ID assigned by the H-SMF to the original PDU session on EPS and transmitted by the H-SMF to the V-SMF. The V-SMF can use the home-provided charging ID together with the charging ID (created by the V-SMF) for subsequent charging data request messages.

[0154] In an embodiment, during the PDU session establishment, a Charging Data Request [Initial] may be sent to the CHF, indicating a "roaming user". The SMF in the VPLMN creates a Charging ID for the PDU session (V-SMF created Charging ID) and sends a Charging Data Request [Initial] to the CHF in the VPLMN. The H-SMF may send an Nsmf_PDUSession_Create response with a Charging ID (Home provided Charging ID) to the V-SMF. Based on the "Received PDU Session Condition" trigger, a Charging Data Request [Update] with the charging information received from the H-SMF is sent to the CHF, which includes the "Roaming Charging Profile" selected by the HPLMN, counting according to the QoS Flow Identifier (QFI) is enabled, the Charging ID (Visited created Charging ID), and the Home provided Charging ID.

[0155] In an embodiment, the first charging identifier for the PDU session is received from the second SMF during at least one of Evolved Packet System (EPS) to Fifth Generation System (5GS) idle mode mobility, handover of a home-routed PDU session, or PDU session establishment of a home-routed PDU session.

[0156] Figure 6a A flowchart of a method according to another embodiment of the present disclosure is shown. The method can be performed by an apparatus implemented in a second SMF, or an apparatus implemented at a second SMF, or an apparatus implemented as a second SMF, or an apparatus communicatively coupled to a second SMF. Therefore, the apparatus can provide components or modules for implementing various parts of method 600, as well as components or modules for implementing other processes in combination with other components. For the sake of brevity, descriptions of certain parts that have been described in the above embodiments are omitted here.

[0157] At block 602, a second SMF may receive a PDU session creation request from a first SMF during a PDU session establishment procedure for a home routing protocol data unit (PDU) session.

[0158] In an embodiment, the first SMF is a visited SMF and the second SMF is a home SMF.

[0159] At block 604, the second SMF may allocate a first charging identifier for the PDU session.

[0160] At block 606, the second SMF may send a PDU session creation response including a first charging identifier for the PDU session to the first SMF.

[0161] In an embodiment, a combination of the first charging identifier and the network function instance identifier of the second SMF is used as an identifier of the charging data record.

[0162] Figure 6b A flowchart of a method according to another embodiment of the present disclosure is shown. The method can be performed by an apparatus implemented in a second SMF, or an apparatus implemented at a second SMF, or an apparatus implemented as a second SMF, or an apparatus communicatively coupled to a second SMF. Therefore, the apparatus can provide components or modules for implementing various parts of method 610, as well as components or modules for implementing other processes in combination with other components. For the sake of brevity, descriptions of certain parts that have been described in the above embodiments are omitted here.

[0163] At block 612, the second SMF may send a charging data request including the first charging identifier to the second charging function.

[0164] The second charging function may be any suitable network device, node, entity or function capable of providing charging functionality. In an embodiment, the second charging function may be a home charging function, for example, as described in 3GPP TS 23.501 V18.0.0 and 3GPP TS 32.255 V17.8.0.

[0165] Figure 7a A flowchart of a method according to another embodiment of the present disclosure is shown. The method can be performed by an apparatus implemented in a first billing function, or an apparatus implemented at a first billing function, or an apparatus implemented as a first billing function, or an apparatus communicatively coupled to a first billing function. Thus, the apparatus can provide components or modules for implementing various parts of method 700, as well as components or modules for implementing other processes in conjunction with other components. For the sake of brevity, descriptions of certain parts already described in the above embodiments are omitted here.

[0166] At block 702, a first charging function may receive a first charging data request from a first session management function (SMF), the first charging data request including a first charging identifier for a protocol data unit (PDU) session and a network function instance identifier of a second SMF. The first charging identifier is assigned by the second SMF.

[0167] At block 704 , the first charging function may update the charging data record based on the first charging data request.

[0168] In an embodiment, if charging data recording has not been enabled before, or the first charging data request is an initial charging data request, the first charging function may enable charging data recording based on the first charging data request.

[0169] In an embodiment, a combination of the first charging identifier and the network function instance identifier of the second SMF is used as an identifier of the charging data record.

[0170] In an embodiment, the first charging identifier is allocated by the second SMF.

[0171] Figure 7b A flowchart of a method according to another embodiment of the present disclosure is shown. The method can be performed by an apparatus implemented in a first billing function, or an apparatus implemented at a first billing function, or an apparatus implemented as a first billing function, or an apparatus communicatively coupled to a first billing function. Thus, the apparatus can provide components or modules for implementing various parts of method 700, as well as components or modules for implementing other processes in conjunction with other components. For the sake of brevity, descriptions of certain parts already described in the above embodiments are omitted here.

[0172] At block 712, the first charging function may receive an initial charging data request from the first SMF including a second charging identifier for the PDU session.

[0173] In an embodiment, the second charging identifier is allocated by the first SMF.

[0174] At block 714 , the first billing function may enable billing data recording based on the initial billing data request.

[0175] In an embodiment, the first charging data request further comprises a second charging identifier.

[0176] In an embodiment, the first charging identifier, the second charging identifier and the network function instance identifier of the second SMF are used as identifiers of the charging data record.

[0177] In an embodiment, the network function instance identifier of the second SMF is included in the PDU session information.

[0178] In an embodiment, the first SMF is a visited SMF, the second SMF is a home SMF, and the first charging function is a visited charging function.

[0179] Figure 7c A flowchart of PDU session charging establishment in a roaming home routing scenario according to another embodiment of the present disclosure is shown.

[0180] Step 1-3a. The UE initiates a new PDU session. The AMF performs V-SMF and H-SMF selection.

[0181] Step 1. The UE sends a PDU session establishment request to the AMF.

[0182] Steps 2 to 3a.AMF sends Nsmf_PDUSession_CreateSMContext request to V-SMF.

[0183] Step 3ch-aV-SMF performs CHF selection. The UE is identified as a roaming user (the PLMN ID of the received SUPI (Subscription Permanent Identifier) ​​is different from the PLMN ID of the VPLMN), and the CHF is selected accordingly (the V-SMF may contain 5GS Cellular Internet of Things (CIoT) related information).

[0184] Step 3ch-b. The V-SMF sends a Charging Data Request [Initial] (Charging ID) to the V-CHF. A Charging Data Request [Initial] is sent to the CHF, indicating "Roaming User". The SMF in the V-PLMN allocates a Charging ID (Billing ID created by the visited location) and uses it when communicating with the V-CHF.

[0185] Step 3ch-cV-CHF turns on CDR (indicating "roaming user").

[0186] Step 3ch-d V-CHF sends Charging Data Response [Initial, Roaming Charging Profile] to V-SMF. V-CHF confirms by sending Charging Data Response [Initial] to SMF and optionally provides "Roaming Charging Profile" to V-SMF, which overrides the default roaming charging profile.

[0187] Step 3b.V-SMF sends Nsmf_PDUSession_CreateSMContext response to AMF.

[0188] Step 4-5. N4 session establishment is performed between V-UPF and V-SMF.

[0189] Step 6. The V-SMF sends an Nsmf_PDUSession_Create request (roaming charging profile) to the H-SMF. The SMF in the V-PLMN does not include the chargingId allocated in step 3ch to the SMF in the H-PLMN.

[0190] Step 7. H-SMF performs registration / subscription data retrieval / subscription.

[0191] Step 8. PDU session authentication / authorization.

[0192] Steps 9a-b to 11. Session management policy establishment or modification. The H-SMF performs UPF selection (not shown).

[0193] Step 11: The ch-aH-SMF performs CHF selection. Based on the identification that the UE is roaming in different PLMNs, a CHF is selected accordingly.

[0194] Step 11ch-b H-SMF sends a Charging Data Request [Initial, Roaming Charging Profile] to H-CHF. A Charging Data Request [Initial] is sent to CHF, indicating "roaming user", with the "Roaming Charging Profile" received from the VPLMN (H-SMF may include 5GS CIoT related information). The SMF in the H-PLMN may or should allocate a session-level charging Id and use it when communicating with the H-CHF.

[0195] Step 11ch-c. CHF turns on CDR (indicating "float out user").

[0196] Step 11ch-d. H-CHF sends Charging Data Response [Initial, Roaming Charging Profile] to H-SMF. CHF confirms by sending Charging Data Response [Initial] to H-SMF and provides the "Roaming Charging Profile" selected by HPLMN (the same as the Roaming Charging Profile received from the VPLMN, or the Roaming Charging Profile selected by it) to H-SMF.

[0197] Steps 12a-12b: The H-UPF and H-SMF establish an N4 session. The SMF initiates the N4 session establishment process with the selected UPF.

[0198] Step 12ch.H-SMF starts counting one or more QFIs. Counting by QFI is started.

[0199] The H-UPF sends the first downlink data to the V-UPF.

[0200] Step 13. The H-SMF sends an Nsmf_PDUSession_Create response (roaming charging profile) (home provided charging Id) to the V-SMF. The SMF in the H-PLMN may or should provide the session-level charging Id to the V-SMF via the home provided charging Id.

[0201] Step 13: The ch-aV-SMF sends a Charging Data Request [Update, Roaming Charging Profile] (Charging ID and Home-Provided Charging ID) to the V-CHF. Based on the "Received PDU Session Condition" trigger, a Charging Data Request [Update] is sent to the CHF with the charging information received from the H-SMF, including the "Roaming Charging Profile" selected by the HPLMN and the enabled per-QFI counting. The V-SMF may or should use this Home-Provided Charging ID together with the Charging ID (Visited-Created Charging ID) in subsequent Charging Data Request messages.

[0202] The V-SMF may include hSMF Nfinstance in the charging data request message sent to the V-CHF to help the V-CHF form a unique identifier for the charging data record.

[0203] Step 13ch-bV-CHF updates CDR.

[0204] Step 13ch-cV-CHF sends a charging data response [update] to V-SMF. CHF confirms by sending a charging data response [update] to V-SMF.

[0205] Step 14. V-SMF sends Namf_Communication_N1N2MessageTransfer to AMF and receives a response from AMF.

[0206] Steps 15 to 17. AMF-RAN-UE interaction.

[0207] The UE sends the first uplink data to the V-UPF, and the V-UPF sends it to the H-UPF.

[0208] Step 18.AMF sends Nsmf_PDUSession_UpdateSMContext request to V-SMF.

[0209] Steps 19a-b N4 session modification between V-UPF and V-SMF.

[0210] Step 19: The ch-a V-SMF sends a Charging Data Request [Update] (Charging ID and Home Provided Charging Id) to the V-CHF. The count for one or more rejected QFIs is closed. If necessary, a Charging Data Request [Update] is sent to the CHF for reporting.

[0211] Step 19ch-b. V-CHF updates CDR.

[0212] Step 19ch-c. V-CHF sends a charging data response [update] to V-SMF. CHF confirms by sending a charging data response [update] to V-SMF.

[0213] The V-UPF sends first downlink data to the UE.

[0214] Step 20. V-SMF sends Nsmf_PDUSession_UpdateSMContext response to AMF.

[0215] Step 22.IPv6 address configuration.

[0216] Step 23. The V-SMF sends an Nsmf_PDUSession_Update request to the H-SMF. The Nsmf_PDUSession_UpdateRequest is sent from the V-SMF to the H-SMF. The H-SMF is notified of the rejected QFI or QFIs.

[0217] Step 23 ch-a H-SMF sends a Charging Data Request [Update] to H-CHF. The count of one or more rejected QFIs is closed. If necessary, a Charging Data Request [Update] is sent to CHF for reporting.

[0218] Step 23ch-bH-CHF updates CDR.

[0219] Step 23: H-CHF sends a charging data response [update] to H-SMF. CHF confirms by sending a charging data response [update] to H-SMF.

[0220] Figure 7c Some of the messages in may be the same as corresponding messages as described in various 3GPP specifications (eg, 3GPP TS 29.502 V18.1.0, 3GPP TS 23.502 V18.0.0, 3GPP TS 32.255 V17.8.0, etc.). Figure 7c Certain messages and operations in (eg, steps 3ch-b, 6, steps 11ch, 13, 13ch, and 19ch-a) may be enhanced by embodiments of the present disclosure.

[0221] In an embodiment, in the home routing scenario, the charging ID is generated by the H-SMF.

[0222] In an embodiment, during the PDU session establishment process, the SMF in the V-PLMN may create a charging ID for the PDU session (visited created charging Id) and send a charging data request [initial] to the CHF in the V-PLMN.

[0223] In an embodiment, during the PDU session establishment process, the SMF in the H-PLMN can generate a charging ID and provide it to the V-SMF side via the charging ID provided by the home location. The V-SMF can use this charging ID provided by the home location and the charging ID generated by the SMF in the V-PLMN when communicating with the V-CHF. The V-CHF can use the combination of the charging ID generated by the V-PLMN and the charging ID provided by the home location to uniquely identify the charging record.

[0224] In an embodiment, the Charging Id generated by the SMF in the HPLMN may have a 32-bit unsigned integer value.

[0225] In an embodiment, a new attribute of H-SMF instance ID can be added in the N40 interface to help V-CHF use the combination of billing ID (for example, the billing ID provided by the home location, or the combination of the billing ID provided by the home location and the billing ID created by the visited location) and H-SMF instance ID as a unique identifier.

[0226] In an embodiment, during the PDU session establishment process, the H-SMF may provide the homeProvidedChargingId to the V-SMF.

[0227] In an embodiment, homeProvidedChargingId and Note 5 of Table 6.1.6.2.10-1 of 3GPP TS 29.502 V18.1.0 may be modified as follows. Table 6.1.6.2.10-1: Definition of PduSessionCreatedData type

[0228] In an embodiment, hSMF Nfinstance Id can be added to the PDUSessionInformation attribute. The combination of hSMFId and a billing ID (e.g., a billing ID provided by the home location, or a combination of a billing ID provided by the home location and a billing ID created by the visited location) can be a unique identifier for the billing data record in the V-CHF.

[0229] In an embodiment, Table 6.1.6.2.2.8-1 of 3GPP TS 32.291 V18.0.0 may add hSMFNfinstanceId. Table 6.1.6.2.2.8-1: Definition of PDUSessionInformation type

[0230] In an embodiment, sMFChargingId and sMFHomeProvidedChargingId in Table 6.1.6.2.2.6-1 of 3GPP TS 32.291 V18.0.0 may be modified as follows: Both U32-based and string-based charging IDs may exist in the N40 interface. Table 6.1.6.2.2.6-1: Definition of PDUSessionChargingInformation type

[0231] In an embodiment, 3GPP TS 32.255 V17.8.0 may be modified as follows.

[0232] 5.1.4 Billing Identifier

[0233] When each PDU session is established (i.e. a new PDU session id is allocated), the new PDU session specific SMF charging identifier SMF in H-PLMN is generated, and is transmitted to the SMF in the V-PLMN. The V-SMF may or should provide the home address The provided billing ID is used together with the billing ID (the billing ID created by the visitor) in the subsequent billing data request message. .

[0234] For EPS handover to 5GS in home routing scenario, the charging identifier for EPS PDN connection will be generated by PGW-C+SMF in HPLMN and transmitted to SMF in VPLMN. If V-SMF has already generated the charging identifier, then V- The SMF may or should use the charging ID provided by the home location together with the charging ID (charging ID created by the visit) for subsequent charging. Data request message .

[0235] 5.1.9.1 Overview

[0236] In the home routing scenario, the main parameters exchanged during PDU session establishment are:

[0237] The charging ID provided by the home location includes the charging ID allocated by the H-SMF and transmitted by the H-SMF to the V-SMF. The SMF may or should use the billing ID provided by the home location together with the billing ID (the billing ID created by the visited location) in subsequent billing. Fee data request message .

[0238] Parameters exchanged during PDU session handover from EPS to 5GS in home routing scenario:

[0239] The home-provided charging ID includes the charging ID assigned by the H-SMF to the original PDU session on the EPS and transmitted by the H-SMF to the V-SMF. The V-SMF may or should compare the billing ID provided by the home location with the billing ID (created by the visiting location) The created billing ID) is used together in the subsequent billing data request message .

[0240] 5.2.2.12.2 PDU Session Establishment

[0241] 3ch-b. Send a charging data request [initial] to CHF, indicating "roaming user". The SMF in VPLMN is created for The charging ID of the PDU session (the charging ID created by the visited location) and the charging data request [initial] are sent to the CHF in the VPLMN .

[0242] 13. From H-SMF to V-SMF Has a billing ID (billing ID provided by the home country) Nsmf_PDUSession_Create response.

[0243] 13ch-a. Based on the "Received PDU Session Condition" trigger, a Charging Data Request [Update] with the charging information received from the H-SMF is sent to the CHF, which includes the "Roaming Charging Profile" selected by the HPLMN and the counting by QFI is started And the billing ID (the billing ID created by the visiting location) and the billing ID provided by the home location .

[0244] The embodiments herein can provide numerous advantages, the following being a non-exhaustive list of examples. In some embodiments herein, they can enable unique billing IDs within the billing system. In some embodiments, they can simplify billing ID generation and reporting. In some embodiments herein, they can avoid billing ID conflicts between SMFs. The embodiments herein are not limited to the features and advantages described above. Those skilled in the art will recognize additional features and advantages upon reading the detailed description below.

[0245] Figure 8a 800 is a block diagram illustrating an apparatus suitable for practicing some embodiments of the present disclosure. For example, the first SMF or the second SMF or the first charging function described above may be implemented as or through the apparatus 800.

[0246] The apparatus 800 includes at least one processor 821 (e.g., a digital processor (DP)) and at least one memory (MEM) 822 coupled to the processor 821. The apparatus 800 may also include a transmitter TX and a receiver RX 823 coupled to the processor 821. The MEM 822 stores a program (PROG) 824. The PROG 824 may include instructions that, when executed on the associated processor 821, enable the apparatus 800 to operate in accordance with embodiments of the present disclosure. The combination of the at least one processor 821 and the at least one MEM 822 may form a processing device 825 suitable for implementing various embodiments of the present disclosure.

[0247] Various embodiments of the present disclosure may be implemented by a computer program executable by one or more of the processor 821 , software, firmware, hardware, or a combination thereof.

[0248] The MEM 822 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples.

[0249] Processor 821 may be of any type suitable to the local technical environment, and may include one or more of 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, as non-limiting examples.

[0250] In embodiments where the apparatus is implemented as or at a first SMF, the memory 822 stores instructions executable by the processor 821 , whereby the first SMF operates according to any of the methods described above in relation to the first SMF.

[0251] In embodiments where the apparatus is implemented as or at a second SMF, the memory 822 stores instructions executable by the processor 821 , whereby the second SMF operates according to any of the methods described above in relation to the second SMF.

[0252] In embodiments where the apparatus is implemented as or at a first billing function, the memory 822 stores instructions executable by the processor 821 whereby the first billing function operates according to any of the methods described above in relation to the first billing function.

[0253] Figure 8b 830 is a block diagram illustrating a first SMF according to an embodiment of the present disclosure. As shown in the figure, the first SMF 830 includes a first sending module 831, which is configured to send a protocol data unit (PDU) session creation request to the second SMF. The first SMF 830 also includes a receiving module 832, which is configured to receive a PDU session creation response including a first billing identifier for the PDU session from the second SMF. The first SMF 830 also includes a second sending module 833, which is configured to send a first billing data request including the first billing identifier and the network function instance identifier of the second SMF to the first billing function.

[0254] In an embodiment, the first SMF 830 further includes an allocation module 834 configured to allocate a second charging identifier for the PDU session.

[0255] In an embodiment, the first SMF 830 further comprises a third sending module 835 configured to send an initial charging data request including the second charging identifier to the first charging function.

[0256] Figure 8c 8 is a block diagram illustrating a second SMF according to an embodiment of the present disclosure. As shown in the figure, the second SMF 840 includes a receiving module 841, which is configured to receive a PDU session creation request from the first SMF during the PDU session establishment process of the home routing protocol data unit (PDU) session. The second SMF 840 also includes an allocation module 842, which is configured to allocate a first billing identifier for the PDU session. The second SMF 840 also includes a first sending module 843, which is configured to send a PDU session creation response including the first billing identifier for the PDU session to the first SMF.

[0257] In an embodiment, the second SMF 840 further comprises a second sending module 844 configured to send a charging data request comprising the first charging identifier to the second charging function.

[0258] Figure 8d850 is a block diagram illustrating a first charging function according to an embodiment of the present disclosure. As shown, the first charging function 850 includes a first receiving module 851 configured to receive a first charging data request from a first session management function (SMF), the first charging data request including a first charging identifier for a protocol data unit (PDU) session and a network function instance identifier of a second SMF. The first charging identifier is assigned by the second SMF. The first charging function 850 includes an updating module 852 configured to update a charging data record based on the first charging data request.

[0259] In an embodiment, the first charging function 850 further includes a second receiving module 853 configured to receive an initial charging data request from the first SMF, the initial charging data request including a second charging identifier for the PDU session. The second charging identifier is allocated by the first SMF.

[0260] In an embodiment, the first charging function 850 further includes an enabling module 854 configured to enable charging data recording based on the initial charging data request.

[0261] In addition, an exemplary overall communication system including a terminal device and a network node (eg, a first SMF or a second SMF or a first charging function) will be introduced below.

[0262] Figure 9 An example of a communication system QQ 100 is shown in accordance with some embodiments.

[0263] In this example, communication system QQ100 includes a telecommunications network QQ102, which includes an access network QQ104 (e.g., a radio access network (RAN)) and a core network QQ106, which includes one or more core network nodes QQ108. Access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network node QQ110), or any other similar third generation partnership project (3GPP) access node or non-3GPP access point. Network node QQ110 facilitates direct or indirect connection of user equipment (UE), such as connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UE QQ112) to core network QQ106 via one or more wireless connections.

[0264] Example wireless communications over wireless connections include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Additionally, in various embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals, whether via a wired or wireless connection. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar types of systems.

[0265] UE QQ 112 may be any of a variety of communication devices, including wireless devices that are arranged, configured, and / or operable to communicate wirelessly with network node QQ 110 and other communication devices. Similarly, network node QQ 110 is arranged, capable, configured, and / or operable to communicate directly or indirectly with UE QQ 112 and / or with other network nodes or devices in telecommunication network QQ 102 to enable and / or provide network access (e.g., wireless network access) and / or perform other functions (e.g., management in telecommunication network QQ 102).

[0266] In the depicted example, core network QQ 106 connects network node QQ 110 to one or more hosts (e.g., host QQ 116). These connections can be direct or indirect via one or more intermediate networks or devices. In other examples, the network node can be directly coupled to the host. Core network QQ 106 includes one or more core network nodes (e.g., core network node QQ 108), which are composed of hardware and software components. The features of these components can be substantially similar to those described for the UE, network nodes, and / or hosts, so that the description generally applies to the corresponding components of core network node QQ 108. Example core network nodes include one or more of the following: a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier dehiding function (SIDF), a unified data management (UDM), a security edge protection proxy (SEPP), a network exposure function (NEF), and / or a user plane function (UPF).

[0267] The host QQ 116 may be owned or controlled by a service provider other than the operator or provider of the access network QQ 104 and / or the telecommunications network QQ 102, and may be operated by or on behalf of the service provider. The host QQ 116 may host various applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services (e.g., retrieving and compiling data on various environmental conditions detected by multiple UEs), analytics functions, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and monitoring center, or any other such functions performed by a server.

[0268] Overall, Figure 9 The communication system QQ100 enables connectivity between UEs, network nodes, and hosts. In this sense, the communication system QQ100 can be configured to operate according to predefined rules or procedures, such as specific standards, including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE) and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standards (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards, such as LoRa and Sigfox.

[0269] In some examples, telecommunication network QQ 102 is a cellular network that implements 3GPP standardized features. Therefore, telecommunication network QQ 102 can support network slicing to provide different logical networks to different devices connected to telecommunication network QQ 102. For example, telecommunication network QQ 102 can provide ultra-reliable low-latency communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or provide massive machine type communication (mMTC) / massive IoT services to more UEs.

[0270] In some examples, the UE QQ 112 is configured to send and / or receive information without direct human interaction. For example, the UE can be designed to transmit information to the access network QQ 104 according to a predetermined timeline, when triggered by an internal or external event, or in response to a request from the access network QQ 104. In addition, the UE can be configured to operate in a single or multi-RAT or multi-standard mode. For example, the UE can operate using any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., be configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).

[0271] In this example, hub QQ 114 communicates with access network QQ 104 to facilitate indirect communication between one or more UEs (e.g., UE QQ 112c and / or QQ 112d) and a network node (e.g., network node QQ 110b). In some examples, hub QQ 114 can be a controller, a router, a content source and analyzer, or any other communication device described herein with respect to a UE. For example, hub QQ 114 can be a broadband router that enables a UE to access core network QQ 106. As another example, hub QQ 114 can be a controller that sends commands or instructions to one or more actuators in a UE. The commands or instructions can be received from a UE, network node QQ 110, or by executable code, scripts, processes, or other instructions in hub QQ 114. As another example, hub QQ 114 can be a data collector that acts as a temporary storage for UE data and, in some embodiments, can perform analysis or other processing of the data. As another example, hub QQ 114 can be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, the hub QQ 114 can retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, and then the hub QQ 114 provides it to the UE directly, after performing local processing, and / or after adding additional local content. In another example, the hub QQ 114 acts as a proxy server or coordinator for the UE, especially when one or more of the UEs are low-energy IoT devices.

[0272] Hub QQ 114 can have a constant / persistent or intermittent connection with network node QQ 110b. Hub QQ 114 can also allow for different communication schemes and / or schedules between hub QQ 114 and UEs (e.g., UE QQ 112c and / or QQ 112d) and between hub QQ 114 and core network QQ 106. In other examples, hub QQ 114 is connected to core network QQ 106 and / or one or more UEs via a wired connection. Furthermore, hub QQ 114 can be configured to connect to an M2M service provider via access network QQ 104 and / or to another UE via a direct connection. In certain scenarios, a UE can establish a wireless connection with network node QQ 110 while still being connected via hub QQ 114 via a wired or wireless connection. In some embodiments, hub QQ 114 can be a dedicated hub, i.e., a hub whose primary function is to route communications from a UE to network node QQ 110b and / or from network node QQ 110b to a UE. In other embodiments, hub QQ 114 may be a non-dedicated hub, ie, a device operable to route communications between UEs and network node QQ 110b, but which is additionally operable as a communications origin and / or endpoint for certain data channels.

[0273] Figure 10 is a block diagram of a host QQ 400 according to various aspects described herein, which may be Figure 9 As used herein, host QQ 400 may be or include a combination of various hardware and / or software, including processing resources in a standalone server, blade server, cloud-enabled server, distributed server, virtual machine, container, or server farm. Host QQ 400 may provide one or more services to one or more UEs.

[0274] Host QQ400 includes processing circuitry QQ402, which is operatively coupled to input / output interface QQ406, network interface QQ408, power supply QQ410, and memory QQ412 via bus QQ404. Other components may be included in other embodiments. The features of these components may be substantially similar to those described with respect to the terminal device, so that the descriptions thereof generally apply to the corresponding components of host QQ400.

[0275] Memory QQ412 can store one or more computer programs (including one or more host applications QQ414) and data QQ416, which can include user data, such as data generated by a UE for host QQ400 or data generated by host QQ400 for a UE. Embodiments of host QQ400 may utilize only a subset of the components shown or all of them. Host application QQ414 can be implemented in a container-based architecture and can provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for a variety of different classes, types, or implementations of UE (e.g., mobile phones, desktop computers, wearable display systems, heads-up display systems). Host application QQ414 can also provide user authentication and permission checks and can periodically report health, routing, and content availability to a central node (e.g., a device in the core network or on the edge). Thus, the host QQ 400 can select and / or indicate different hosts for over-the-top services for the UE. The host application QQ 414 can support various protocols, such as HTTP Live Streaming (HLS), Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0276] Figure 11 A communication diagram is shown in which a host QQ 602 communicates with a UE QQ 606 via a network node QQ 604 over a partially wireless connection according to some embodiments. Figure 11 To describe the UE discussed in the previous paragraphs (e.g. Figure 9 UE QQ112a), network node (e.g. Figure 9 network nodes QQ110a) and hosts (e.g. Figure 9 Host QQ116 and / or Figure 10 An example implementation of the host QQ400).

[0277] As with host QQ 400, embodiments of host QQ 602 include hardware, such as a communication interface, processing circuitry, and memory. Host QQ 602 also includes software, which is stored in or accessible by host QQ 602 and executed by the processing circuitry. The software includes a host application that is operable to provide services to a remote user, such as a UE QQ 606 connected via an over-the-top (OTT) connection QQ 650 extending between the UE QQ 606 and the host QQ 602. In providing services to the remote user, the host application can provide user data transmitted using the OTT connection QQ 650.

[0278] The network node QQ 604 includes hardware that enables the network node QQ 604 to communicate with the host QQ 602 and the UE QQ 606. The connection QQ 660 can be direct or through a core network (such as Figure 9 The core network QQ106) and / or one or more other intermediate networks (e.g., one or more public, private, or managed networks). For example, the intermediate network can be a backbone network or the Internet.

[0279] UE QQ606 includes hardware and software, the software is stored in UEQQ606 or can be accessed by UEQQ606, and can be executed by the processing circuit of UE. The software includes a client application, such as a web browser or an operator-specific "application", which is operable to provide services to human users or non-human users via UEQQ606 with the support of host QQ602. In host QQ602, the executing host application can communicate with the executing client application via OTT connection QQ650 terminated at UEQQ606 and host QQ602. When providing services to the user, the UE's client application can receive request data from the host application of the host and provide user data in response to the request data. OTT connection QQ650 can transmit both request data and user data. The UE's client application can interact with the user to generate user data, which is provided to the host application via OTT connection QQ650.

[0280] The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide connectivity between the host QQ602 and the UE QQ606. The connection QQ660 and the wireless connection QQ670 (via which the OTT connection QQ650 may be provided) have been drawn abstractly to illustrate communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicitly mentioning any intermediate devices and the precise routing of messages via these devices.

[0281] As an example of transmitting data via OTT connection QQ650, in step QQ608, host QQ602 provides user data, which can be performed by running a host application. In some embodiments, the user data is associated with a specific human user interacting with UE QQ606. In other embodiments, the user data is associated with UE QQ606, which shares data with host QQ602 without explicit human interaction. In step QQ610, host QQ602 initiates a transmission carrying the user data to UE QQ606. Host QQ602 may initiate the transmission in response to a request sent by UE QQ606. The request may be initiated by human interaction with UE QQ606 or by operation of a client application running on UE QQ606. In accordance with the teachings of the embodiments described in this disclosure, the transmission may be delivered via network node QQ604. Therefore, in step QQ612, in accordance with the teachings of the embodiments described throughout this disclosure, network node QQ604 transmits the user data carried in the transmission initiated by host QQ602 to UE QQ606. In step QQ614 , UE QQ606 receives the user data carried in the transmission. This reception may be performed by a client application running on UEQQ606 , which is associated with a host application running on host QQ602 .

[0282] In some examples, UE QQ 606 runs a client application that provides user data to host QQ 602. The user data can be provided as a reaction or response to data received from host QQ 602. Therefore, in step QQ 616, UE QQ 606 can provide the user data, which can be performed by running the client application. When providing the user data, the client application can also consider user input received from the user via the input / output interface of UE QQ 606. Regardless of the specific method of providing the user data, UE QQ 606 initiates the transmission of the user data to host QQ 602 via network node QQ 604 in step QQ 618. In step QQ 620, according to the teachings of the embodiments described in the present disclosure, network node QQ 604 receives the user data from UE QQ 606 and initiates the transmission of the received user data to host QQ 602. In step QQ 622, host QQ 602 receives the user data carried in the transmission initiated by UE QQ 606.

[0283] One or more of the various embodiments improves the performance of OTT services provided to UE QQ 606 using OTT connection QQ 650, where wireless connection QQ 670 forms the final leg. More specifically, in some embodiments herein, it enables unique billing IDs within the billing system. In some embodiments, it can simplify billing ID generation and reporting. In some embodiments herein, it can avoid billing ID conflicts between SMFs.

[0284] In an example scenario, host QQ602 can collect and analyze plant status information. As another example, host QQ602 can process audio and video data that may have been retrieved from the UE for use in creating a map. As another example, host QQ602 can collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, host QQ602 can store surveillance videos uploaded by the UE. As another example, host QQ602 can store or control access to media content such as video, audio, VR, or AR that can be broadcast, multicast, or unicast to the UE. As other examples, host QQ602 can be used for energy pricing, remote control of non-time-critical power loads to balance power generation demand, location services, presentation services (compiling charts of data collected from remote devices, etc., for example), or any other function that collects, retrieves, stores, analyzes, and / or transmits data.

[0285] In some examples, a measurement process may be provided for monitoring data rate, latency, and other factors that may be improved by one or more embodiments. An optional network function may also be provided for reconfiguring the OTT connection QQ650 between the host QQ602 and the UE QQ606 in response to changes in measurement results. The measurement process and / or the network function for reconfiguring the OTT connection may be implemented in the software and hardware of the host QQ602 and / or the UE QQ606. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection QQ650 passes. The sensors may participate in the measurement process by providing values ​​of the aforementioned monitored quantities or other physical quantities, from which the software may calculate or estimate the monitored quantities. Reconfiguration of the OTT connection QQ650 may include message formats, retransmission settings, preferred routing, and the like; reconfiguration does not require direct changes to the operation of the network node QQ604. Such processes and functions are known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates the host QQ602 in measuring throughput, propagation time, latency, and the like. The measurement can be achieved by software causing a message (particularly an empty or "dummy" message) to be transmitted using the OTT connection QQ650 while monitoring propagation time, errors, etc.

[0286] Embodiment 1. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising:

[0287] processing circuitry configured to provide user data; and

[0288] A network interface configured to initiate transmission of user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform operations as described above in relation to the network node to send user data from a host to the UE.

[0289] Embodiment 2. The host of the aforementioned embodiment, wherein:

[0290] The processing circuitry of the host is configured to run a host application that provides user data; and

[0291] The UE includes processing circuitry configured to run a client application associated with a host application to receive a transmission of user data from the host.

[0292] Embodiment 3. A method implemented in a host, the host being configured to operate in a communication system further comprising a network node and a user equipment (UE), the method comprising:

[0293] Providing user data to the UE; and

[0294] A transmission carrying user data is initiated to a UE via a cellular network including a network node, wherein the network node performs operations related to the network node as described above to send user data from a host to the UE.

[0295] Embodiment 4. The method of the aforementioned embodiment further comprises sending, at the network node, user data provided by the host for the UE.

[0296] Embodiment 5. The method of any of the previous two embodiments, wherein the user data is provided at the host by running a host application that interacts with a client application running on the UE, the client application being associated with the host application.

[0297] Embodiment 6. A communication system configured to provide an over-the-top service, the communication system comprising:

[0298] Host, including:

[0299] processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with an over-the-top service; and

[0300] A network interface configured to initiate transmission of user data to a cellular network node for transmission to a UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform operations as described above in relation to the network node to transmit user data from a host to the UE.

[0301] Embodiment 7. The communication system of the above embodiment further comprises:

[0302] Network nodes; and / or

[0303] User equipment.

[0304] Embodiment 8. The communication system of the first two embodiments, wherein:

[0305] The processing circuitry of the host is configured to run a host application to provide user data; and

[0306] The host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[0307] Embodiment 9. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising:

[0308] processing circuitry configured to initiate receipt of user data; and

[0309] A network interface is configured to receive user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform operations related to the network node as described above to receive user data from a UE for a host.

[0310] Embodiment 10. The host in the first two embodiments, wherein:

[0311] The processing circuitry of the host is configured to run a host application to provide user data; and

[0312] The host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[0313] Embodiment 11. The host of any of the preceding two embodiments, wherein initiating reception of user data comprises requesting the user data.

[0314] Embodiment 12. A method implemented by a host, the host being configured to operate in a communication system further comprising a network node and a user equipment (UE), the method comprising:

[0315] At the host, reception of user data from the UE is initiated, the user data originating from a transmission that the network node has received from the UE, wherein the network node performs operations as described above with respect to the network node to receive user data from the UE for the host.

[0316] Embodiment 13. The method of the aforementioned embodiment further comprises, at the network node, sending the received user data to the host.

[0317] Embodiment 14. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising:

[0318] processing circuitry configured to provide user data; and

[0319] A network interface configured to initiate transmission of user data to a cellular network for transmission to a user equipment (UE), wherein the UE includes a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform the UE-related operations described above to receive user data from a host.

[0320] Embodiment 15. The host of the preceding embodiment, wherein the cellular network further comprises a network node configured to communicate with the UE to send user data from the host to the UE.

[0321] Embodiment 16. The host of the first two embodiments, wherein:

[0322] The processing circuitry of the host is configured to run a host application to provide user data; and

[0323] The host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[0324] Embodiment 17. A method implemented by a host operating in a communication system further comprising a network node and a user equipment (UE), the method comprising:

[0325] Providing user data to the UE; and

[0326] A transmission carrying user data is initiated to the UE via a cellular network including a network node, wherein the UE performs UE-related operations as described above to receive user data from the host.

[0327] Embodiment 18. The method of the above embodiment further comprises:

[0328] At the host, a host application is run in association with the client application running on the UE to receive user data from the UE.

[0329] Example 19. The method of the above embodiment further comprises:

[0330] At the host, input data is sent to the client application running on the UE, the input data being provided by the running host application,

[0331] The user data is provided by the client application in response to input data from the host application.

[0332] Embodiment 20. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising:

[0333] processing circuitry configured to utilize user data; and

[0334] a network interface configured to receive a transmission of user data transmitted by a user equipment (UE) to a cellular network,

[0335] The UE includes a communication interface and a processing circuit, and the communication interface and the processing circuit of the UE are configured to perform the UE-related operations as described above to send user data to the host.

[0336] Embodiment 21. The host of the preceding embodiment, wherein the cellular network further comprises a network node configured to communicate with the UE to send user data from the UE to the host.

[0337] Embodiment 22. The host of the first two embodiments, wherein:

[0338] The processing circuitry of the host is configured to run a host application to provide user data; and

[0339] The host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[0340] Embodiment 23. A method implemented by a host, the host configured to operate in a communication system further including a network node and a user equipment (UE), the method comprising:

[0341] At the host, user data sent by the UE to the host via the network node is received, wherein the UE performs the UE-related operations described above to send the user data to the host:

[0342] Embodiment 24. The method of the above embodiment further comprises:

[0343] At the host, a host application is run in association with the client application running on the UE to receive user data from the UE.

[0344] Embodiment 25. The method of the above embodiment further comprises:

[0345] At the host, input data is sent to the client application running on the UE, the input data being provided by the running host application,

[0346] The user data is provided by the client application in response to input data from the host application.

[0347] The term unit or module may have a conventional meaning in the field of electronics, electrical devices and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, and the like, such as those described herein.

[0348] By using functional units, the first or second SMF can eliminate the need for fixed processors or memory, and can deploy arbitrary computing and storage resources from the first or second SMF in the communication system. The introduction of virtualization and network computing technologies can improve the efficiency of network resource utilization and network flexibility.

[0349] According to one aspect of the present disclosure, a computer program product is provided, which is tangibly stored on a computer-readable storage medium and includes instructions. When the instructions are executed on at least one processor, the instructions cause the at least one processor to perform any of the above methods.

[0350] According to one aspect of the present disclosure, a computer-readable storage medium is provided, which stores instructions. When the instructions are executed on at least one processor, the instructions enable the at least one processor to perform any of the above methods.

[0351] In addition, the present disclosure may also provide a carrier containing the above-mentioned computer program, wherein the carrier is an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium. The computer-readable storage medium may be, for example, an optical disc or an electronic storage device such as RAM (random access memory), ROM (read-only memory), flash memory, magnetic tape, CD-ROM, DVD, Blu-ray disc, etc.

[0352] The techniques described herein can be implemented in various ways such that a device that implements one or more functions of the corresponding device described using the embodiments includes not only prior art components, but also components for implementing one or more functions of the corresponding device described using the embodiments, and it can include separate components for each separate function, or can be configured to perform two or more functions. For example, these techniques can be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or a combination thereof. For firmware or software, implementation can be accomplished by modules (e.g., processes, functions, etc.) that perform the functions described herein.

[0353] Exemplary embodiments of the present invention have been described above with reference to block diagrams and flow charts of methods and apparatus. It will be understood that each block of the block diagrams and flow charts, and combinations of blocks in the block diagrams and flow charts, respectively, can be implemented by various components comprising computer program instructions. These computer program instructions can be loaded onto a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, such that the instructions executed on the computer or other programmable data processing device create components for implementing the functions specified in the flow chart block or blocks.

[0354] In addition, although operations are depicted in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in sequence, or that all illustrated operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although the above discussion contains several specific implementation details, these should not be interpreted as limitations on the scope of the subject matter described herein, but rather as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable subcombination.

[0355] While this specification contains many specific implementation details, these should not be interpreted as limitations on the scope of any implementation or the scope of what may be claimed, but rather as descriptions of features that may be specific to a particular embodiment of a particular implementation. Certain features described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable subcombination. Furthermore, while the features described above may be described as working in certain combinations and even initially claimed as such, one or more features from the claimed combination may be deleted from the combination in some cases, and the claimed combination may be directed to subcombinations or variations of subcombinations.

[0356] It will be apparent to those skilled in the art that, as technology advances, the present invention can be implemented in various ways. The above embodiments are provided to illustrate, not to limit, the present disclosure, and it should be understood that modifications and variations can be made without departing from the spirit and scope of the present disclosure, as readily understood by those skilled in the art. Such modifications and variations are considered to be within the scope of the present disclosure and the appended claims. The scope of protection of the present disclosure is defined by the appended claims.

Claims

1. A method (400) performed by a first session management function (SMF), comprising: Sending (402) a protocol data unit (PDU) session creation request to the second SMF; receiving (404) from the second SMF a PDU session creation response including a first charging identifier for the PDU session; as well as A first charging data request including the first charging identifier and the network function instance identifier of the second SMF is sent (406) to a first charging function.

2. The method according to claim 1, wherein A combination of the first charging identifier and the network function instance identifier of the second SMF is used as an identifier of a charging data record.

3. The method according to claim 1 or 2, further comprising: allocating (502) a second charging identifier for the PDU session; An initial charging data request including the second charging identifier is sent (504) to the first charging function.

4. The method according to claim 3, wherein: The first charging data request further includes the second charging identifier.

5. The method according to claim 4, wherein The first charging identifier, the second charging identifier and the network function instance identifier of the second SMF are used as identifiers of charging data records.

6. The method according to any one of claims 1 to 5, wherein The first charging identifier for the PDU session is received from the second SMF during at least one of the following: Evolved Packet System (EPS) to 5GS idle mode mobility, Handover of the Home Routing PDU session, or PDU session establishment process for home routing PDU session.

7. The method according to any one of claims 1 to 6, wherein The network function instance identifier of the second SMF is included in the PDU session information.

8. The method according to any one of claims 1 to 7, wherein The first SMF is a visited SMF, the second SMF is a home SMF, and the first charging function is a visited charging function.

9. A method (600) performed by a second session management function (SMF), comprising: receiving (602) a PDU session creation request from a first SMF during a PDU session establishment procedure for a home routing protocol data unit (PDU) session; allocating (604) a first charging identifier for the PDU session; as well as A PDU session creation response including the first charging identifier for the PDU session is sent (606) to the first SMF.

10. The method according to claim 9, wherein: A combination of the first charging identifier and the network function instance identifier of the second SMF is used as an identifier of a charging data record.

11. The method according to claim 9 or 10, further comprising: A charging data request including the first charging identifier is sent (612) to a second charging function.

12. The method according to claim 11, wherein The second charging function is a home charging function.

13. The method according to any one of claims 9 to 12, wherein: The first SMF is a visited SMF, and the second SMF is a home SMF.

14. A method (700) performed by a first charging function, comprising: receiving (702) a first charging data request from a first session management function (SMF), the first charging data request comprising a first charging identifier for a protocol data unit (PDU) session and a network function instance identifier of a second SMF, wherein the first charging identifier is allocated by the second SMF; and Based on the first billing data request, a billing data record is updated (704).

15. The method according to claim 14, wherein A combination of the first charging identifier and the network function instance identifier of the second SMF is used as an identifier of a charging data record.

16. The method according to claim 14 or 15, wherein: The first charging identifier is allocated by the second SMF.

17. The method according to any one of claims 14 to 16, further comprising: receiving (712) from the first SMF an initial charging data request including a second charging identifier for the PDU session, wherein the second charging identifier is assigned by the first SMF; and Based on the initial billing data request, the billing data record is started (714).

18. The method according to claim 17, wherein The first charging data request further includes the second charging identifier.

19. The method according to claim 18, wherein The first charging identifier, the second charging identifier and the network function instance identifier of the second SMF are used as identifiers of a charging data record.

20. The method according to any one of claims 14 to 19, wherein: The network function instance identifier of the second SMF is included in the PDU session information.

21. The method according to any one of claims 14 to 20, wherein: The first SMF is a visited SMF, the second SMF is a home SMF, and the first charging function is a visited charging function.

22. A first session management function SMF (800), comprising: Processor (821); as well as a memory (822) coupled to the processor (821), the memory (822) storing instructions executable by the processor (821), whereby the first SMF (800) is operable to: Send a protocol data unit (PDU) session creation request to the second SMF; receiving, from the second SMF, a PDU session create response including a first charging identifier for the PDU session; as well as A first charging data request including the first charging identifier and the network function instance identifier of the second SMF is sent to a first charging function.

23. The first SMF according to claim 22, wherein: The first SMF is further operable to perform the method of any one of claims 2 to 8.

24. A second session management function SMF (800), comprising: Processor (821); as well as a memory (822) coupled to the processor (821), the memory (822) storing instructions executable by the processor (821), whereby the second SMF (800) is operable to: receiving a PDU session creation request from the first SMF during a PDU session establishment procedure for a home routing protocol data unit (PDU) session; allocating a first charging identifier for the PDU session; as well as Sending a PDU session creation response including the first charging identifier for the PDU session to the first SMF.

25. The second SMF according to claim 24, wherein The second SMF is further operable to perform the method of any one of claims 10 to 13.

26. A first billing function (800), comprising: Processor (821); as well as a memory (822) coupled to the processor (821), the memory (822) storing instructions executable by the processor (821), whereby the first billing function (800) is operable to: receiving a first charging data request from a first session management function (SMF), the first charging data request comprising a first charging identifier for a protocol data unit (PDU) session and a network function instance identifier of a second SMF, wherein the first charging identifier is allocated by the second SMF; as well as Based on the first charging data request, a charging data record is updated.

27. The first charging function according to claim 26, wherein: The first charging function is further operable to perform the method of any one of claims 15 to 21.

28. A computer-readable storage medium storing instructions which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 21.

29. A computer program product comprising instructions which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 21.

Images