Solution for supporting charging

Abstract

Embodiments of the present disclosure relate to a solution for supporting charging. An access management device in a first network sends, to a policy control device via an interface between the access management device and the policy control device in a second network, a request for access information of a terminal device maintained in the second network, the access information being used to charge a packet data unit (PDU) session of the terminal device, the PDU session is established in the first network via the second network; receiving access information of the terminal device from the policy control device in the second network via the interface; and sending the access information to the session management device in the first network. According to the invention, the first network can obtain the information for charging from the second network, and the charging between operators can be correctly realized.

Description

Technical Field

[0001] Various example embodiments relate to the field of telecommunications, and in particular, to methods, devices, apparatuses, and computer-readable storage media for supporting charging. Background Art

[0002] In the field of communications, in order to provide efficient and reliable solutions for utilizing wireless communication networks, continuous development is underway. Each new generation of technology faces technical challenges in handling different situations and processes required to connect and serve devices connected to the wireless network. In order to meet the increasing demand for wireless data services since the deployment of the fourth-generation (4G) communication system, efforts have been made to develop improved fifth-generation (5G) or pre-5G communication systems. The new communication system is capable of supporting various types of service applications for terminal devices.

[0003] With the development of charging technology in 5G networks, a new charging solution involving different network charging is needed. Summary of the Invention

[0004] Generally, example embodiments of the present disclosure provide a solution for supporting charging.

[0005] In a first aspect, an access management device in a first network is provided. The access management device includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the access management device to at least: send a request for access information of a terminal device maintained in a second network to a policy control device via an interface between the access management device and the policy control device in the second network, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; receive, via the interface, the access information of the terminal device in the second network from the policy control device in the second network; and send the access information of the terminal device in the second network to a session management device in the first network.

[0006] In a second aspect, a session management device in a first network is provided. The session management device includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the session management device to at least: receive, from an access management device in the first network, access information of a terminal device maintained in a second network, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; and send a charging request including the access information of the terminal device in the second network to a charging device in the first network.

[0007] In a third aspect, a charging device in a first network is provided. The charging device includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the charging device to at least: receive a charging request from a session management device in the first network, the charging request including access information maintained by a terminal device in a second network, the access information being used to charge a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; generate a charging data record (CDR) of the PDU session in the first network based on the access information of the terminal device in the second network; and send the CDR in the first network to a accounting device in the first network.

[0008] In a fourth aspect, a first accounting device in a first network is provided. The first accounting device includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first accounting device to at least: receive a first charging data record (CDR) of a packet data unit (PDU) session of a terminal device in the first network from a charging device in the first network, the PDU session being established in the first network via the second network; receive a second CDR of the PDU session in the second network from a second accounting device in the second network; and associate the first CDR and the second CDR.

[0009] In a fifth aspect, a policy control device in a second network is provided. The policy control device includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the policy control device to at least: receive, via an interface between an access management device in the first network and the policy control device, a request for access information maintained by a terminal device in the second network, the access information being used to charge a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; and send, via the interface, the access information of the terminal device in the second network to the access management device in the first network.

[0010] In a sixth aspect, a session management device in a second network is provided. The session management device includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the session management device to at least: receive charging correlation information of a packet data unit (PDU) session of a terminal device from a policy control device in the second network, the PDU session being established in the first network via the second network; and send a charging request including the charging correlation information to a charging device in the second network device.

[0011] In a seventh aspect, a charging device in a second network is provided. The charging device includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the charging device to at least: receive a charging request from a session management device in the second network, the charging request including charging correlation information of a packet data unit (PDU) session of a terminal device, the PDU session being established in a first network via the second network; generate a charging data record (CDR) of the PDU session in the second network based on the charging correlation information; and send the CDR in the second network to a charging settlement device in the second network.

[0012] In an eighth aspect, a second charging settlement device in a second network is provided. The second charging settlement device includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second charging settlement device to at least: receive a charging data record (CDR) of a packet data unit (PDU) session of a terminal device in the second network from a charging device in the second network, the PDU session being established in a first network via the second network; and send the CDR to a first charging settlement device in the first network.

[0013] In a ninth aspect, a method implemented at an access management device in a first network is provided. The method includes: sending, at the access management device in the first network, a request for access information of a terminal device maintained in a second network to a policy control device via an interface between the access management device and the policy control device in the second network, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; receiving, via the interface, the access information of the terminal device in the second network from the policy control device in the second network; and sending the access information of the terminal device in the second network to a session management device in the first network.

[0014] In a tenth aspect, a method implemented at a session management device in a first network is provided. The method includes: receiving, at the session management device in the first network, the access information of the terminal device maintained in the second network from an access management device in the first network, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; and sending a charging request including the access information of the terminal device in the second network to a charging device in the first network.

[0015] In an eleventh aspect, a method implemented at a charging device in a first network is provided. The method includes: receiving, at the charging device in the first network, a charging request from a session management device in the first network, the charging request including access information maintained by a terminal device in a second network, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; generating a charging data record (CDR) of the PDU session in the first network based on the access information of the terminal device in the second network; and sending the CDR in the first network to a accounting device in the first network.

[0016] In a twelfth aspect, a method implemented at a first accounting device in a first network is provided. The method includes: receiving, at the first accounting device in the first network, a first charging data record (CDR) of a packet data unit (PDU) session of a terminal device in the first network from a charging device in the first network, the PDU session being established in the first network via the second network; receiving a second CDR of the PDU session in the second network from a second accounting device in the second network; and associating the first CDR and the second CDR.

[0017] In a thirteenth aspect, a method implemented at a policy control device in a second network is provided. The method includes: receiving, at the policy control device in the second network, a request for access information maintained by a terminal device in the second network via an interface between an access management device in the first network and the policy control device, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; and sending, via the interface, the access information of the terminal device in the second network to the access management device in the first network.

[0018] In a fourteenth aspect, a method implemented at a session management device in a second network is provided. The method includes: receiving, at the session management device in the second network, charging correlation information of a packet data unit (PDU) session of a terminal device from a policy control device in the second network, the PDU session being established in the first network via the second network; and sending a charging request including the charging correlation information to a charging device in the second network device.

[0019] In a fifteenth aspect, a method implemented at a charging device in a second network is provided. The method includes: receiving, at the charging device in the second network, a charging request from a session management device in the second network, the charging request including charging correlation information of a packet data unit (PDU) session of a terminal device, the PDU session being established in a first network via the second network; generating, based on the charging correlation information, a charging data record (CDR) of the PDU session in the second network; and sending the CDR in the second network to a charging accounting device in the second network.

[0020] In a sixteenth aspect, a method implemented at a second charging accounting device in a second network is provided. The method includes: receiving, at the second charging accounting device in the second network, a charging data record (CDR) of a packet data unit (PDU) session of a terminal device in the second network from a charging device in the second network, the PDU session being established in a first network via the second network; and sending the CDR to a first charging accounting device in the first network.

[0021] In a seventeenth aspect, a device is provided. The device includes: means for sending, at an access management device in a first network, a request for access information maintained in a second network for a terminal device to a policy control device via an interface between the access management device and the policy control device in the second network, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; means for receiving, via the interface, the access information of the terminal device in the second network from the policy control device in the second network; and means for sending the access information of the terminal device in the second network to a session management device in the first network.

[0022] In an eighteenth aspect, a device is provided. The device includes: means for receiving, at a session management device in a first network, the access information maintained in a second network for a terminal device from an access management device in the first network, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; and means for sending a charging request including the access information of the terminal device in the second network to a charging device in the first network.

[0023] In a nineteenth aspect, an apparatus is provided. The apparatus includes: means for receiving, at a charging device in a first network, a charging request from a session management device in the first network, the charging request including access information maintained for a terminal device in a second network, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; means for generating, based on the access information of the terminal device in the second network, a charging data record (CDR) of the PDU session in the first network; and means for sending the CDR in the first network to a charging accounting device in the first network.

[0024] In a twentieth aspect, an apparatus is provided. The apparatus includes: means for receiving, at a first charging accounting device in a first network, a first charging data record (CDR) of a packet data unit (PDU) session of a terminal device in the first network from a charging device in the first network, the PDU session being established in the first network via the second network; means for receiving a second CDR of the PDU session in the second network from a second charging accounting device in the second network; and means for correlating the first CDR and the second CDR.

[0025] In a twenty-first aspect, an apparatus is provided. The apparatus includes: means for receiving, at a policy control device in a second network, a request for access information maintained for a terminal device in the second network from an access management device via an interface between the access management device and the policy control device in the first network, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; and means for sending, via the interface, the access information of the terminal device in the second network to the access management device in the first network.

[0026] In a twenty-second aspect, an apparatus is provided. The apparatus includes: means for receiving, at a session management device in a second network, charging correlation information of a packet data unit (PDU) session of a terminal device from a policy control device in the second network, the PDU session being established in the first network via the second network; and means for sending a charging request including the charging correlation information to a charging device in the second network device.

[0027] In a twenty-third aspect, an apparatus is provided. The apparatus includes: means for receiving, at a charging device in the second network, a charging request from a session management device in the second network, the charging request including charging correlation information of a packet data unit (PDU) session of a terminal device, the PDU session being established in the first network via the second network; means for generating, based on the charging correlation information, a charging data record (CDR) of the PDU session in the second network; and means for sending the CDR in the second network to a charging accounting device in the second network.

[0028] In a twenty-fourth aspect, an apparatus is provided. The apparatus includes: means for receiving, at a second accounting device in a second network, a charging data record (CDR) of a packet data unit (PDU) session of a terminal device in the second network from a charging device in the second network, the PDU session being established in a first network via the second network; and means for sending the CDR to a first accounting device in the first network.

[0029] In a twenty-fifth aspect, a non-transitory computer-readable medium is provided, the non-transitory computer-readable medium including program instructions for causing an apparatus to at least execute the method according to any one of the ninth to sixteenth aspects described above.

[0030] In a twenty-sixth aspect, a non-transitory computer-readable medium is provided, the non-transitory computer-readable medium including program instructions stored thereon for at least executing the method according to any one of the ninth to sixteenth aspects described above.

[0031] In a twenty-seventh aspect, a computer program including instructions is provided, which when executed by an apparatus causes the apparatus to at least: send, via an interface between an access management device in a first network and a policy control device in a second network, a request for access information maintained in the second network of a terminal device to the policy control device, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; receive, via the interface, the access information of the terminal device in the second network from the policy control device in the second network; and send the access information of the terminal device in the second network to a session management device in the first network.

[0032] In a twenty-eighth aspect, a computer program including instructions is provided, which when executed by an apparatus causes the apparatus to at least: receive, from an access management device in a first network, the access information maintained in the second network of a terminal device, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; and send a charging request including the access information of the terminal device in the second network to a charging device in the first network.

[0033] In a twenty-ninth aspect, there is provided a computer program comprising instructions which, when executed by a device, cause the device to at least: receive a charging request from a session management device in a first network, the charging request including access information maintained for a terminal device in a second network, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; generate a charging data record (CDR) for the PDU session in the first network based on the access information of the terminal device in the second network; and send the CDR in the first network to a charging device in the first network.

[0034] In a thirtieth aspect, there is provided a computer program comprising instructions which, when executed by a device, cause the device to at least: receive a first charging data record (CDR) for a packet data unit (PDU) session of a terminal device in a first network from a charging device in the first network, the PDU session being established in the first network via a second network; receive a second CDR for the PDU session in the second network from a second charging device in the second network; and associate the first CDR and the second CDR.

[0035] In a thirty-first aspect, there is provided a computer program comprising instructions which, when executed by a device, cause the device to at least: receive, via an interface between an access management device and a policy control device in a first network, a request for access information maintained for a terminal device in a second network, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; and send, via the interface, the access information of the terminal device in the second network to the access management device in the first network.

[0036] In a thirty-second aspect, there is provided a computer program comprising instructions which, when executed by a device, cause the device to at least: receive charging relevance information for a packet data unit (PDU) session of a terminal device from a policy control device in a second network, the PDU session being established in the first network via the second network; and send a charging request including the charging relevance information to a charging device in a second network device.

[0037] In a thirty-third aspect, there is provided a computer program comprising instructions which, when executed by a device, cause the device to at least: receive a charging request from a session management device in a second network, the charging request including charging relevance information for a packet data unit (PDU) session of a terminal device, the PDU session being established in the first network via the second network; generate a charging data record (CDR) for the PDU session in the second network based on the charging relevance information; and send the CDR in the second network to a charging device in the second network.

[0038] In a thirty-fourth aspect, there is provided a computer program comprising instructions which, when executed by a device, cause the device to at least: receive, from a charging device in a second network, a charging data record (CDR) of a packet data unit (PDU) session of a terminal device in the second network, the PDU session being established in a first network via the second network; and send the CDR to a first accounting device in the first network.

[0039] In a thirty-fifth aspect, there is provided an access management device in a first network, the access management device comprising: a first sending circuit system configured to send, via an interface between the access management device and a policy control device in a second network, a request for access information maintained in the second network for the terminal device to the policy control device, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; a receiving circuit system configured to receive, via the interface, the access information of the terminal device from the policy control device in the second network; and a second sending circuit system configured to send the access information of the terminal device in the second network to a session management device in the first network.

[0040] In a thirty-sixth aspect, there is provided a session management device in a first network, the session management device comprising: a receiving circuit system configured to receive, from an access management device in the first network, access information maintained in the second network for the terminal device, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; and a sending circuit system configured to send a charging request including the access information of the terminal device in the second network to a charging device in the first network.

[0041] In a thirty-seventh aspect, there is provided a charging device in a first network, the charging device comprising: a receiving circuit system configured to receive a charging request from a session management device in the first network, the charging request including access information maintained in the second network for the terminal device, the access information being used for charging a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; a generating circuit system configured to generate a charging data record (CDR) of the PDU session in the first network based on the access information of the terminal device in the second network; and a sending circuit system configured to send the CDR in the first network to an accounting device in the first network.

[0042] In a thirty-eighth aspect, a first accounting device in a first network is provided. The first accounting device includes: a first receiving circuit system configured to receive a first charging data record (CDR) of a packet data unit (PDU) session of a terminal device in the first network from a charging device in the first network, where the PDU session is established in the first network via a second network; a second receiving circuit system configured to receive a second CDR of the PDU session in the second network from a second accounting device in the second network; and an associating circuit system configured to associate the first CDR and the second CDR.

[0043] In a thirty-ninth aspect, a policy control device in a second network is provided. The policy control device includes: a receiving circuit system configured to receive, via an interface between an access management device and the policy control device in the first network, a request for access information maintained for the terminal device in the second network, where the access information is used for charging a packet data unit (PDU) session of the terminal device, and the PDU session is established in the first network via the second network; and a sending circuit system configured to send, via the interface, the access information of the terminal device in the second network to the access management device in the first network.

[0044] In a fortieth aspect, a session management device in a second network is provided. The session management device includes: a receiving circuit system configured to receive charging relevance information of a packet data unit (PDU) session of a terminal device from a policy control device in the second network, where the PDU session is established in the first network via the second network; and a sending circuit system configured to send a charging request including the charging relevance information to a charging device in the second network device.

[0045] In a forty-first aspect, a charging device in a second network is provided. The charging device includes: a receiving circuit system configured to receive a charging request from a session management device in the second network, where the charging request includes charging relevance information of a packet data unit (PDU) session of a terminal device, and the PDU session is established in the first network via the second network; a generating circuit system configured to generate a charging data record (CDR) of the PDU session in the second network based on the charging relevance information; and a sending circuit system configured to send the CDR in the second network to an accounting device in the second network.

[0046] In a forty-second aspect, a second accounting device in a second network is provided. The second accounting device includes: a receiving circuit system configured to receive a charging data record (CDR) of a packet data unit (PDU) session of a terminal device in the second network from a charging device in the second network, where the PDU session is established in the first network via the second network; and a sending circuit system configured to send the CDR to a first accounting device in the first network.

[0047] It should be understood that the Summary of the Invention section is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Through the following description, other features of the present disclosure will become readily understandable. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0049] Figure 1A An example communication network in which embodiments of the present disclosure can be implemented is illustrated;

[0050] Figure 1B A schematic diagram illustrating a non-roaming architecture of a 5G core network with untrusted non-3GPP access is shown;

[0051] Figure 1C A schematic diagram illustrating access to an independent non-public network service via a PLMN is shown;

[0052] Figure 1D A schematic diagram illustrating access to a PLMN service via an independent non-public network is shown;

[0053] Figure 2 A call flow diagram according to some embodiments of the present disclosure is shown;

[0054] Figure 3 A call flow diagram according to some other embodiments of the present disclosure is shown;

[0055] Figure 4 A call flow diagram according to some other embodiments of the present disclosure is shown;

[0056] Figure 5 A schematic diagram illustrating a solution architecture for supporting 5G SNPN charging according to some embodiments of the present disclosure is shown;

[0057] Figure 6 A schematic diagram illustrating a solution architecture for supporting 5G SNPN charging according to some other embodiments of the present disclosure is shown;

[0058] Figure 7 A schematic diagram illustrating a method implemented at an access management device in a first network according to some embodiments of the present disclosure is shown;

[0059] Figure 8 A schematic diagram illustrating a method implemented at a session management device in a first network according to some embodiments of the present disclosure is shown;

[0060] Figure 9The figure illustrates a schematic diagram of a method implemented at a charging device in a first network according to some embodiments of the present disclosure;

[0061] Figure 10 The figure illustrates a schematic diagram of a method implemented at a first accounting device in a first network according to some embodiments of the present disclosure;

[0062] Figure 11 The figure illustrates a schematic diagram of a method implemented at a policy control device in a second network according to some embodiments of the present disclosure;

[0063] Figure 12 The figure illustrates a schematic diagram of a method implemented at a session management device in a second network according to some embodiments of the present disclosure;

[0064] Figure 13 The figure illustrates a schematic diagram of a method implemented at a charging device in a second network according to some embodiments of the present disclosure;

[0065] Figure 14 The figure illustrates a schematic diagram of a method implemented at a second accounting device in a second network according to some embodiments of the present disclosure;

[0066] Figure 15 The figure illustrates a simplified block diagram of a device suitable for implementing embodiments of the present disclosure; and

[0067] Figure 16 The figure illustrates a block diagram of an example computer-readable medium according to some embodiments of the present disclosure;

[0068] Throughout the drawings, the same or similar reference numerals denote the same or similar elements. Detailed Description

[0069] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described for illustrative purposes only and help those skilled in the art understand and implement the present disclosure, and do not represent any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various other ways than those described below.

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

[0071] In this disclosure, references to "one embodiment", "an embodiment", "example 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. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is within the knowledge of those skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0072] It should be understood that although terms such as "first" and "second" 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 embodiment, a first element may be termed a second element, and similarly, a second element may be termed a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0073] The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the example embodiments. The singular forms "a", "an", and "the" as used herein also include the plural forms unless the context clearly dictates otherwise. Further understood, the terms "comprises", "comprising", "has", "having", "includes", and / or "containing", when used herein, specify the presence of the 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. As used herein, "at least one of the following: <list of two or more elements>" and "at least one of <list of two or more elements>" and similar phrases (where the list of two or more elements is joined by "and" or "or") refer to at least any one of these elements, or at least any two or more of these elements, or all of these elements.

[0074] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0075] (a) A pure hardware circuit implementation (such as an implementation using only analog and / or digital circuitry), and

[0076] (b) A combination of hardware circuitry and software, such as (if applicable):

[0077] (i) A combination of (multiple) analog and / or digital hardware circuitry and software / firmware, and

[0078] (ii) Any part of (multiple) hardware processors (including (multiple) digital signal processors), software, and (multiple) memories with software, which work together to enable a device (such as a mobile phone or a server) to perform various functions), and

[0079] (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or parts of (multiple) microprocessors, which require software (e.g., firmware)

[0080] to operate, but the software can be absent when not required to operate.

[0081] The definition of the circuitry is suitable for all uses of the term in this application, including in any claim. As another example, as used in this application, the term circuitry also encompasses an implementation of only a hardware circuit or a processor (or multiple processors) or a part of a hardware circuit or a processor and its accompanying software and / or firmware. For example, if applicable to a particular claim element, the term circuitry also encompasses a baseband integrated circuit or a processor integrated circuit for a mobile device, or a similar integrated circuit in a server, a cellular network device, or other computing or network devices.

[0082] As used herein, the term "communication network" refers to a network that follows any suitable communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), NarrowBand Internet of Things (NB-IoT), etc. In addition, the communication between a terminal device and a network device in a communication network can be performed according to any suitable generation of communication protocols, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocols, and / or any other protocol known currently or to be developed in the future. Embodiments of the present disclosure can be applied to various communication systems. Considering the rapid development of communication, of course, there will also be future types of communication technologies and systems that can be used to embody the present disclosure. It should not be regarded as limiting the scope of the present disclosure to the above systems.

[0083] As used herein, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives services from the network. Depending on the terms and technologies applied, the network device can refer to a base station (BS) or an access point (AP), such as Node B (NodeB or NB), evolved Node B (eNodeB or eNB), NR NB (also known as gNB), remote radio unit (RRU), radio header (RH), remote radio head (RRH), relay, low-power node (such as femto, pico), etc.

[0084] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, a user equipment (UE), 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, mobile phones, cellular phones, smart phones, IP voice (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), game terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded equipment (LEE), laptop mounted equipment (LME), USB dongles, smart devices, wireless customer premise equipment (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automation processing chain environment), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment", and "UE" may be used interchangeably.

[0085] Private wireless is an independent network focused on industrial operation assets and users. Private wireless networks provide better privacy, data security, compliance, and network performance, and well meet the needs of many critical mission vertical industries.

[0086] Non-public network is basically a term defined by 3GPP for the deployment of 5G private networks. Two main deployments are defined in 3GPP: Standalone Non-Public Network (SNPN) and Public Network Integrated Non-Public Network (PNI-NPN).

[0087] Currently, 3GPP has just started to study the charging aspects of enhanced support for non-public networks starting from Rel-18, and the latest technical report 3GPP TR 28.828 V0.3.0 (2022-07) is still in the drafting stage. There are few topics, use cases, potential requirements, and problems recorded in this technical report, and no solutions to address these problems have been made public. SNPN charging is a very new and hot work item in 3GPP.

[0088] So far, there has been no solution on how to support SNPN charging. How to generate revenue and monetize NPN network services is a very important topic for both NPN operators and network operators. More generally, there is no solution to charge for network services provided by an overlay network to terminal devices maintained in an underlying network. The present disclosure provides a solution, particularly for charging of a Standalone Non-Public Network (SNPN) using an underlying / overlay 5G network.

[0089] The principles and embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. First, refer to Figure 1A , which illustrates an example communication system 100 in which embodiments of the present disclosure can be implemented. The system 100 may include a plurality of terminal devices 110. For example, Figure 1A one terminal device 110 is shown in. The system 100 may also include a core network 130 and a core network 140 (abbreviated as CN), and the core network 130 and the core network 140 may be different core networks.

[0090] For example, in some embodiments, the core network 130 may be a Standalone Non-Public Network (SNPN), and the core network 140 may be a Public Land Mobile Network (PLMN). In some other embodiments, the core network 130 may be a PLMN, and the core network 140 may be an SNPN. The terminal device 110 may communicate with the core network (CN) 130. For example, the terminal device 110 may communicate with an access management device in the CN 130. The CN 130 and the CN 140 may exchange data via an interface between them. The system 100 may also include a device 120. For example, the device 120 may be a base station 120. The device 120 may communicate with both the terminal device 110 and the CN 130. It should be understood that the number of the above devices is for illustrative purposes only and does not represent any limitation.

[0091] Communication in the communication system 100 may be implemented according to any suitable (plural) communication protocols, including but not limited to cellular communication protocols such as the first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), and fifth generation (5G), wireless local area network communication protocols such as those of the Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocols known currently or to be developed in the future. In addition, the communication may utilize any suitable wireless communication technologies, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplexing (FDD), Time Division Duplexing (TDD), Multiple Input Multiple Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), and / or any other technologies known currently or to be developed in the future.

[0092] Figure 1B The diagram illustrates a schematic diagram of a non-roaming architecture of a 5G core network with untrusted non-3GPP access. The SNPN 5GS deployment is based on the architecture described in clause 4.2.3 of TS23.501, i.e., the 5GC architecture with untrusted non-3GPP access, as Figure 1B As shown, it is used to access SNPN services via PLMN (and vice versa). Figure 1B In the figure, N represents an interface, for example, N2 represents an N2 interface, and will not be further explained below. In order to access SNPN services, a UE that has successfully registered with a PLMN via 3GPP access can perform another registration with the SNPN via the PLMN user plane (using the credentials of the SNPN). In order to obtain access to non-public network services while the UE resides in the NG-RAN of the PLMN, the UE obtains an IP connection, discovers and establishes a connection with the N3IWF in the independent non-public network. The architecture for accessing SNPN services via the PLMN is as follows: Figure 1C As shown, Figure 1C A schematic diagram illustrating access to standalone non-public network services via a PLMN is illustrated. To access PLMN services, a UE in SNPN access mode that has successfully registered with the SNPN may perform another registration with the PLMN via the SNPN user plane (using the credentials of the PLMN). To gain access to PLMN services while the UE is residing in a NG-RAN of a standalone non-public network, the UE obtains an IP connection, discovers and establishes a connection with the N3IWF in the PLMN. The architecture for accessing PLMN services via SNPN is shown in FIG. Figure 1D As shown, Figure 1D A schematic diagram illustrating access to PLMN services via an independent non-public network is illustrated.

[0093] exist Figure 1C In the deployment architecture of SNPN, SNPN is the overlay network and PLMN is the underlying network. The N3IWF in the SNPN network isolates and hides the underlying PLMN network, and currently, the SNPN overlay network cannot obtain the underlying network billing information (or access information) to implement UE billing in the SNPN based on the access network information of the PLMN network, nor can it associate the billing data generated in the PLMN network with the billing data generated in the SNPN network to correctly implement inter-operator billing or settlement between the PLMN operator and the SNPN operator for the UE subscribed to the PLMN that allows access to the SNPN service.

[0094] exist Figure 1D In the deployment architecture, PLMN is the overlay network and SNPN is the underlying network. The N3IWF in the PLMN network isolates and hides the underlying SNPN network. Figure 1DSimilar to the above deployment, the PLMN overlay network cannot obtain the underlying network charging information to implement UE charging in the PLMN based on the access network information of the SNPN network, nor can it correlate the charging data generated in the SNPN network with the charging data generated in the PLMN network to correctly implement the inter-operator charging or settlement between the SNPN operator and the PLMN operator for UEs that subscribe to the SNPN allowing access to the PLMN service.

[0095] Figure 2 FIG. 200 is a call flow diagram illustrating some embodiments in accordance with the present disclosure. As Figure 2 shown, in a first network, an access management device 250 in the first network may send (2110) a request 2005 for access information 2015 maintained in a second network for a terminal device 110 to a policy control device 220 via an interface between the access management device and the policy control device in the second network, where the access information is used for charging a packet data unit (PDU) session of the terminal device 110. The terminal device 110 is not Figure 2 shown in the figure.

[0096] In a second network, a policy control device 220 in the second network may receive (2120) the request 2005 for the access information 2015 maintained in the second network for the terminal device 110 from the access management device 250 in the first network via the interface, where the access information is used for charging the PDU session of the terminal device 110. The PDU session is established in the first network via the second network. The policy control device 220 in the second network may send (2130) the access information 2015 maintained in the second network for the terminal device 110 to the access management device 250 in the first network via the interface.

[0097] In the first network, the access management device 250 in the first network may receive (2140) the access information 2015 of the terminal device 110 in the second network from the policy control device 220 in the second network via the interface. In this way, the first network may obtain the access information from the second network.

[0098] In a first network, an access management device 250 in the first network may send (2150) access information 2015 of a terminal device 110 in a second network to a session management device 260 in the first network. The session management device 260 in the first network may receive (2160) the access information 2015 maintained by the terminal device 110 in the second network from the access management device 250 in the first network. The access information is used for charging the PDU session of the terminal device 110, and the session management device may send (2170) a charging request 2025 to a charging device 270 in the first network. The charging request 2025 may include, but is not limited to, the access information 2015 of the terminal device 110 in the second network. In other words, the charging request 2025 may include other information. The access information 2015 is used for charging the PDU session of the terminal device 110. The charging device 270 in the first network may receive (2180) the charging request 2025 from the session management device 260 in the first network. The charging device 270 in the first network may generate (2190) a charging data record (CDR) (i.e., the first CDR 2035) of the PDU session in the first network based on the access information 2015 of the terminal device 110 in the second network, and send (2200) the CDR 2035 in the first network to a accounting device (i.e., the first accounting device) 280 in the first network. The first accounting device 280 may receive (2210) the first CDR 2035 of the PDU session of the terminal device 110 in the first network from the charging device 270 in the first network. In this way, the first network realizes charging for the terminal device 110 based on the access information 2015 obtained from the second network. After step 2190, the charging device 270 in the first network may also send a charging response message to the session management device 260 in the first network (this step is not shown in Figure 2 ).

[0099] In a second network, a session management device 210 in the second network may receive (2220) charging correlation information 2045 of a PDU session of a terminal device 110 from a policy control device 220 in the second network, and send (2230) a charging request 2055 to a charging device 230 in the second network device, and the charging request 2055 includes, but is not limited to, the charging correlation information 2045 of the PDU session of the terminal device 110. The charging correlation information 2045 will be further described below. The charging device 230 in the second network may receive (2240) the charging request 2055 including the charging correlation information 2045 from the session management device 210 in the second network, and generate (2250) a charging data record (CDR) of the PDU session in the second network (i.e., the second CDR 2065) based on the charging correlation information 2045; and send (2260) the CDR 2065 in the second network to a charging device (i.e., the second charging device) 240 in the second network. In the second network, the second charging device 240 in the second network may receive (2270) the CDR 2065 of the PDU session of the terminal device 110 in the second network from the charging device 230 in the second network, and send (2280) the CDR 2065 to a first charging device 280 in the first network.

[0100] Therefore, in the first network, the first charging device 280 in the first network may receive (2290) the CDR 2065 (the second CDR) of the PDU session in the second network from the second charging device 240 in the second network, and associate (2300) the first CDR 2035 and the second CDR 2065.

[0101] In this way, the charging data generated in the first network and the charging data generated in the second network can be associated to correctly implement inter-operator charging or settlement between the first network operator and the second network operator for the terminal device 110 in the second network that subscribes to the service allowing access to the first network.

[0102] In some embodiments, the first network is a public land mobile network (PLMN), and the second network is an independent non-public network (SNPN). In some other embodiments, the first network is an SNPN, and the second network is a PLMN.

[0103] In some embodiments, the access information 2015 may include at least one of the following: an identifier of charging for the PDU session of the second network, an identifier of the second network, the location of the terminal device 110, or the access technology of the terminal device 110.

[0104] In some embodiments, the session management device 260 in the first network may generate charging correlation information 2045 for charging the PDU session in the first network, and send the charging correlation information 2045 to the access management device 250 in the first network. Specifically, the session management device 260 in the first network may generate the charging correlation information 2045 after receiving a charging response message indicating a successful response from the charging device 270 in the first network.

[0105] Accordingly, the access management device 250 in the first network may receive the charging correlation information 2045 of the PDU session in the first network from the session management device 260 in the first network, and send the charging correlation information 2045 to the policy control device 220 in the second network via the interface between the access management device 250 and the policy control device 220. The policy control device 220 in the second network may receive the charging correlation information 2045 of the PDU session in the first network from the access management device 250 in the first network via this interface, and send the charging correlation information 2045 to the session management device 210 in the second network device.

[0106] In some embodiments, the CDR 2065 in the second network may include the charging correlation information 2045, so that the charging correlation information 2045 from the first network can be used to correlate the first CDR 2035 and the second CDR 2065.

[0107] In some embodiments, the interface may be protected via a Secure Edge Protection Proxy (SEPP). In this way, the above new interface provided by the embodiments of the present disclosure can be protected via the SEPP, and the policy and charging information of the underlying and overlay information can be exchanged between the PCF (an example of the policy control device 220 or implemented in the policy control device 220) in the underlying network (an example of the second network) and the AMF (an example of the access management device 250 or implemented in the access management device 250) in the overlay network (an example of the first network).

[0108] In some embodiments, the charging correlation information 2045 may include at least one of the following: an identifier for charging the PDU session assigned by the session management device 260, the address of the session management device 260 in the first network, or the identifier of the first network.

[0109] In some embodiments, the charging device 230 may generate the CDR 2065 in the second network by performing inter-operator charging based on the wholesale tariff of the provider of the first network for the PDU session of the terminal device 110.

[0110] In some embodiments, the first network may be an overlay network, such as CN 140. The second network may be an underlying network, such as CN 130. In some embodiments, the overlay network may include an AMF, an SMF, a CHF, and a charging system, etc. The underlying network may include a PCF, an SMF, a CHF, and a charging system, etc.

[0111] When a UE (an example of the terminal device 110) attempts to create a PDU session in the overlay network, the AMF in the overlay network will invoke a request to the PCF in the underlying network to obtain the underlying access network charging information (also referred to as access information, such as PLMN ID + network ID, user location information, access technology, etc.) maintained in the PCF of the underlying network via a newly introduced interface. The AMF then passes the underlying access network charging information to the SMF (session management function) of the overlay network in the PDU session creation request.

[0112] In some embodiments, when the SMF in the overlay network sends a PDU session creation response message to the AMF, the response message will include overlay network charging correlation information (e.g., the PDU session charging ID assigned by the SMF, the SMF address of the overlay network, PLMN ID + network ID (PLMN + the network ID that will identify the SNPS network)). The AMF will notify or update the overlay network charging correlation information to the PCF of the underlying network, and this information is further passed by the PCF to the SMF of the underlying network.

[0113] In some embodiments, when the SMF in the overlay network generates a charging data request (also referred to as a charging request) for the overlay CHF (charging function), the charging data measured by the overlay network reports the service usage of the overlay network. The charging data request will also include the underlying access network information (such as user location, radio access technology). In this way, the CHF in the overlay network will correctly charge the network service data and perform charging service control based on the access network information of the underlying network.

[0114] In some embodiments, when the SMF in the underlying network generates a charging data request for the CHF in the underlying network, the charging data metered by the underlying network requires reporting the service usage of each UE to the overlay network via the underlying network. In addition to the normal charging from the SMF to the CHF, the SMF should also include overlay network charging correlation information (e.g., PDU session charging ID, SMF address of the overlay network, PLMN ID network ID + network ID of the SNPN). The CDR (Charging Data Record) generated by the CHF in the underlying network should also reflect this overlay network charging correlation information. In this way, the embodiments of the present disclosure will enable inter-operator charging and settlement (between the underlying network operator and the overlay network operator), and the underlying CHF performs wholesale charging for each UE and for each overlay network service over the underlying network. The embodiments of the present disclosure will also enable the overlay network operator to correlate the CDRs received from the underlying network provider with the CDRs generated in the overlay network, enabling correct revenue assurance and settlement and avoiding overcharging revenue from the underlying network provider.

[0115] Figure 3 FIG. 300 is a call flow diagram illustrating some other embodiments in accordance with the present disclosure. Figure 4 FIG. 400 is a call flow diagram illustrating some other embodiments in accordance with the present disclosure. Refer to Figure 3 and Figure 4 and the above embodiments of the present disclosure, the overlay network is an example of a first network, and the underlying network is an example of a second network. In the overlay network. The AMF 306 in the overlay network is an example of an access management device in the first network. The SMF 307 in the overlay network is an example of a session management device in the first network. The CHF 308 in the overlay network is an example of a charging device in the first network. The accounting system 309 in the overlay network is an example of a first accounting device in the first network. The PCF 303 in the underlying network is an example of a policy control device in the second network. The SMF 302 in the underlying network is an example of a session management device in the second network. The CHF 304 in the underlying network is an example of a charging device in the second network. The accounting system 305 in the underlying network is an example of a second accounting device in the second network. The UE 301 is an example of the terminal device 110.

[0116] As Figure 3As shown, the CHF 308 in the overlay network uses the access information to the underlying network to charge the services of the UE 301 in the overlay network via the underlying network. The UE 301 requests PDU session establishment / modification (310) from the AMF 306 in the overlay network via the N3IWF (Non-3GPP Interworking Function). The AMF 306 in the overlay network retrieves the underlying network access information of the UE 301 (PLMNID, NID, UE 301 location, access technology, etc.) maintained in the PCF 303 of the underlying network (320). The AMF 306 in the overlay network transfers the underlying network access information of the UE 301 to the SMF 307 in the overlay network in the Nsmf_PDUSession_Create(Update)SMContext request (330). When the charging report is triggered, the SMF 307 in the overlay network reports the underlying network access information to the CHF 308 in the overlay network in the charging data request (or charging request) message (340). The CHF 308 in the overlay network performs data charging for the services of the UE 301 based on the underlying network access information (i.e., charges the PDU session of the terminal device 110) (350). The CHF 308 may send a CDR / Rated CDR including the underlying network access information to the accounting system 309 in the overlay network (in the overlay network) (360).

[0117] As Figure 4As shown, the CHF 304 in the underlying network includes overlay network charging correlation information for inter-operator charging between the underlying network provider and the overlay network provider. The SMF 307 in the overlay network is ready to establish a PDU session and allocates a charging ID (410) for the PDU session. The charging ID of the PDU session is an example of an identifier for charging the PDU session allocated by the session management device. The SMF 307 in the overlay network includes the charging ID, SMF ID, PLMN ID, and NID (420) in the Nsmf_Communication_N1N2MessageTransfer message to the AMF 306 of the overlay network. The AMF 306 of the overlay network notifies / updates the overlay network charging correlation information (charging ID, SMF ID, PLMN ID, and NID) to the PCF 303 in the underlying network (430). The PCF 303 in the underlying network updates the overlay network charging correlation information into its own PDU session context of the underlying network SMF 302 (440). When the SMF 302 in the underlying network generates a charging request for the CHF 304 in the underlying network and the overlay network charging correlation information in the charging data request (i.e., the charging request) will be sent to the CHF 304 in the underlying network (450). The CHF 304 in the underlying network performs wholesale charging based on the tariffs of the overlay network provider to charge the services of the UE to the overlay network data network (i.e., the overlay network) via the underlying network (460). The CHF 304 may send a CDR / Rating CDR including the overlay network charging correlation information to the accounting system 305 in the underlying network (470). Invoice and Rating CDR, including the overlay network charging correlation information from the underlying network provider to the overlay network provider, to collect revenue (480).

[0118] Figure 5 FIG. illustrates a schematic diagram showing a solution architecture for supporting 5G SNPN charging according to some embodiments of the present disclosure. As Figure 5 shown, the SNPN CN is the underlying network, and the PLMN CN is the overlay network. The UE services of the PLMN data connection pass through the SNPN underlying network.

[0119] The SMF in the SNPN CN reports a data charging request for the services of the UE's data connection with the NPN service to the SNPN CHF. The party being charged is the UE subscriber, and the charging party is the SNPN provider.

[0120] The SMF in the PLMN CN will report a data charging request for the services of the UE's data connection with the PLMN data service via the NPN to the PLMN CHF. The party being charged is the UE subscriber, and the charging party is the PLMN provider.

[0121] The SMF in the SNPN CN will also report a data charging request for the service of the data connection of the UE with the PLMN data service via the NPN to the SNPN CHF. The party to be charged is the PLMN provider, and the charging party is the SNPN provider.

[0122] Embodiments of the present disclosure enable the CHF in the PLMN CN to charge the service data flow of each PDU session of the UE by using the underlying network access information of the UE service from the NPN underlying network to the PLMN DN (data network). Figure 5 Enhancements to the relevant interfaces are shown to enable the AMF in the PLMN CN to query the access network information maintained in the PCF in the NPN CN. Then, the AMF in the PLMN CN transmits the underlying network access charging information to the SMF in the PLMN CN, and this SMF also includes the underlying network access information in the data charging request to the CHF in the PLMN CN.

[0123] In some embodiments, the specific steps are as follows: S1, when the UE requests PDU session establishment / modification from the AMF in the PLMN CN via the N3IWF, the AMF in the PLMN CN will send a request via the newly introduced interface to the PCF in the underlying NPN CN to query the user location of the UE, access technology + PLMN ID / NID, etc., and access network information. The PCF in the underlying NPN CN will return the underlying access network information of the UE to the AMF in the overlay network. S2, the AMF in the overlay network includes the access network information of the UE in the Nsmf_PDUSession_CreateSMContext Request / Update CreateSMContext request, and sends this message to the SMF in the PLMN CN. S3, the SMF in the PLMN CN will send a data charging request (with underlying network access information) to the CHF in the PLMN CN, so that the CHF in the PLMN CN will be able to use the underlying network access data to charge the data service of the UE transmitted on the underlying NPN network.

[0124] Embodiments of the present disclosure enable the SNPN CHF to perform inter-operator charging based on the wholesale tariffs of the PLMN to charge and rate the services of each UE from the NPN underlying network to the PLMN DN. Figure 5It shows the enhancement of the relevant interfaces to support the AMF in the PLMN overlay network to pass the PDU session charging ID + SMF ID + PLMN ID to the SMF in the NPN underlying network via the PCF in the underlying network through the newly introduced interface. S4, when the PDU session is ready to be established in the PLMN CN, the SMF in the PLMN CN will generate a PDU session charging ID for the UE's PDU session in the PLMN. The SMF will return the charging ID + SMF ID + PLMN ID to the AMF in the Nsmf_Communication_N1N2MessageTransfer message. S5, the AMF will notify / update the overlay network charging correlation information (PDU session charging ID + SMF ID + PLMN ID) to the PCF in the NPN CN via the newly introduced interface. S6, the PCF in the NPN will further update the overlay network charging correlation information to the SMF in the NPN. S7, when the UE establishes a data connection with the PLMN service via the NPN underlying network. The SMF in the underlying NPN will report a data charging request (including the overlay network charging correlation information: PDU session charging ID + SMF ID + PLMN ID) to the CHF in the NPN CN, so that the CHF in the NPN CN will be able to perform inter-operator charging on the wholesale tariffs of each service data flow per UE on the NPN underlying network based on the PLMN ID. S8, the NPN accounting system will send a rating CDR to the PLMN to collect revenue. S9, using the overlay network / PLMN charging correlation information in the rating CDR from the NPN provider (i.e., overlay network PDU session charging ID + SMF ID + PLMN ID), the PLMN accounting system can associate the CDR of the NPN provider with the CDR generated by the PLMN CHF to ensure revenue and avoid overcharging from the NPN provider.

[0125] Figure 6 The figure illustrates a schematic diagram showing a solution architecture for supporting 5G S-NPN charging according to some other embodiments of the present disclosure. As Figure 6 shown, the PLMN CN is the underlying network, and the NPN CN is the overlay network. The UE traffic of the NPN data connection passes through the PLMN underlying network. The SMF in the PLMN CN reports a data charging request for the traffic of the UE's data connectivity to the PLMN service to the PLMN CHF. The party being charged is the UE subscriber, and the charging party is the PLMN provider.

[0126] The SMF in the NPN CN will report a data charging request for the traffic of the UE's data connectivity via the PLMN CN to the NPN data service to the NPN CHF. The party being charged is the UE subscriber, and the charging party is the NPN provider.

[0127] The SMF in the PLMN CN will also report a data charging request for the service of the data connectivity of the UE with the NPN data service via the PLMN CN to the PLMN CHF. The party to be charged is the NPN provider, and the charging party is the PLMN provider.

[0128] Embodiments of the present disclosure enable the CHF in the NPN CN to charge for the service data flow of each PDU session of the UE by using the underlying network access information of the UE service from the underlying PLMN network to the NPN DN (data network). Figure 6 Illustrated is the enhancement of the relevant interfaces to enable the AMF in the NPN CN to query the access network information maintained in the PCF in the PLMN CN. Then, the AMF in the NPN CN transmits the underlying network access charging information to the SMF in the NPN CN, and this SMF also includes the underlying network access information in the data charging request to the CHF in the NPN CN. The detailed steps are as follows: S1, when the UE requests PDU session establishment / modification from the AMF in the NPN CN via the N3IWF, the AMF will send a request to the PCF in the underlying PLMN CN to query access network information such as the UE's user location, access technology + PLMN ID, etc. via the newly introduced interface. The PCF returns the UE's underlying access network information to the AMF. S2, the AMF includes the UE's access network information in the Nsmf_PDUSession_CreateSMContext Request / Update request and sends this message to the SMF in the NPN CN. S3, the SMF in the NPN CN will send a data charging request (with underlying network access information) to the CHF in the NPN CN, so that the CHF in the NPN CN will be able to charge for the data service transmitted by the UE on the underlying PLMN network by using the underlying network access information.

[0129] Embodiments of the present invention enable the PLMN CHF to perform inter-operator charging based on the wholesale tariff of the NPN to charge and rate the services of each UE from the underlying PLMN network to the NPN DN. Figure 6Enhancements to the relevant interfaces are shown to support the AMF in the NPN CN to pass the overlay network charging correction information (PDU session charging ID + SMF ID + PLMN ID + NID) to the PCF in the PLMN CN via the newly introduced interface. S4, when the PDU session is ready to be established in the NPN CN, the SMF in the NPN CN generates a PDU session charging ID for the PDU session of the UE in the NPN. The SMF includes the charging ID + SMF ID + PLMN ID + NID in the Nsmf_Communication_N1N2MessageTransfer message to the AMF. S5, the AMF notifies / updates the overlay network charging correlation information (PDU session charging ID + SMF ID + PLMN ID + NID) to the PCF in the PLMN CN via the newly introduced interface. S6, the PCF in the PLMN further updates the overlay network charging correlation information to the SMF in the PLMN. S7, when the UE establishes data connectivity with the NPN service via the PLMN underlying network. The SMF in the underlying PLMN network reports a data charging request (including the overlay network charging correlation information: PDU session charging ID + SMF ID + PLMN ID + NID) to the PLMN CHF, so that the CHF in the PLMN CN can perform inter-operator charging based on the wholesale tariff of each service data flow of each UE on the PLMN underlying network provided by the NPN provider. S8, the PLMN accounting system sends a rating CDR to the NPN to collect revenue. S9, using the overlay network / NPN CN charging correlation information in the rating CDR from the PLMN provider (i.e., overlay network PDU session charging ID + SMF ID + PLMN ID + NID), the NPN accounting system can correlate the CDR from the PLMN provider with the CDR generated by the NPN CHF to ensure revenue and avoid overcharging from the PLMN provider.

[0130] Figure 7 FIG. illustrates a schematic diagram of a method 700 implemented at an access management device in a first network according to some other embodiments of the present disclosure. At block 710, the access management device may send a request for access information maintained in the second network for the terminal device 110 to the policy control device via an interface between the access management device and the policy control device in the second network, where the access information is used for charging the packet data unit (PDU) session of the terminal device 110. The PDU session is established in the first network via the second network. At block 720, the access management device may receive the access information of the terminal device 110 in the second network from the policy control device in the second network via the interface. At block 730, the access management device may send the access information of the terminal device 110 in the second network to the session management device in the first network.

[0131] In some embodiments, the first network is a Public Land Mobile Network (PLMN), and the second network is a Standalone Non-Public Network (SNPN). In some other embodiments, the first network is an SNPN, and the second network is a PLMN.

[0132] In some embodiments, the access information includes at least one of the following: an identifier for charging of a PDU session of the second network (i.e., the PDU session charging ID of the second network), an identifier of the second network, the location of the terminal device 110, or the access technology of the terminal device 110.

[0133] In some embodiments, the access management device may receive charging correlation information of a PDU session in the first network from a session management device in the first network; and send the charging correlation information to a policy control device in the second network via the interface.

[0134] In some embodiments, the interface is protected via a Secure Edge Protection Proxy (SEPP).

[0135] Figure 8 A schematic diagram illustrating a method 800 implemented at a session management device in a first network according to some other embodiments of the present disclosure is shown. At block 810, the session management device in the first network may receive access information maintained in the second network of the terminal device 110 from an access management device in the first network, where the access information is used to charge for a Packet Data Unit (PDU) session of the terminal device 110. The PDU session is established in the first network via the second network. At block 820, the session management device in the first network may send a charging request to a charging device in the first network, where the charging request includes the access information of the terminal device 110 in the second network.

[0136] In some embodiments, the session management device may generate charging correlation information for charging the PDU session in the first network; and send the charging correlation information to an access management device in the first network.

[0137] In some embodiments, the first network is a Public Land Mobile Network (PLMN), and the second network is a Standalone Non-Public Network (SNPN). In some other embodiments, the first network is an SNPN, and the second network is a PLMN.

[0138] In some embodiments, the charging correlation information includes at least one of the following: an identifier for charging of the PDU session assigned by the session management device, the address of the session management device in the first network, or an identifier of the first network.

[0139] In some embodiments, the access information includes at least one of the following: an identifier for charging of a PDU session of the second network (i.e., the PDU session charging ID of the second network), an identifier of the second network, the location of the terminal device 110, or the access technology of the terminal device 110.

[0140] Figure 9 FIG. illustrates a schematic diagram of a method 900 implemented at a charging device in a first network according to some other embodiments of the present disclosure. At block 910, the charging device in the first network may receive a charging request from a session management device in the first network, the charging request including access information maintained by the terminal device 110 in the second network. The access information is used to charge a packet data unit (PDU) session of the terminal device 110, and the PDU session is established in the first network via the second network. At block 920, the charging device in the first network may generate a charging data record (CDR) of the PDU session in the first network based on the access information of the terminal device 110 in the second network. At block 930, the charging device in the first network may send the CDR in the first network to a billing device in the first network.

[0141] In some embodiments, the first network is a public land mobile network (PLMN), and the second network is an independent non-public network (SNPN). In some other embodiments, the first network is an SNPN, and the second network is a PLMN.

[0142] In some embodiments, the access information includes at least one of the following: an identifier for charging of a PDU session of the second network (i.e., the PDU session charging ID of the second network), an identifier of the second network, the location of the terminal device 110, or the access technology of the terminal device 110.

[0143] Figure 10 FIG. illustrates a schematic diagram of a method 1000 implemented at a first billing device in a first network according to some other embodiments of the present disclosure. At block 1010, the first billing device may receive a first charging data record (CDR) of a packet data unit (PDU) session of the terminal device 110 in the first network from a charging device in the first network. The PDU session is established in the first network via the second network. At block 1020, the first billing device may receive a second CDR of the PDU session in the second network from a second billing device in the second network. At block 1030, the first billing device may associate the first CDR and the second CDR.

[0144] In some embodiments, the first network is a public land mobile network (PLMN), and the second network is an independent non-public network (SNPN). In some other embodiments, the first network is an SNPN, and the second network is a PLMN.

[0145] Figure 11 FIG. illustrates a schematic diagram of method 1100 implemented at a policy control device in a second network according to some other embodiments of the present disclosure. At block 1110, the policy control device may receive, via an interface between the access management device in the first network and the policy control device, a request for access information maintained in the second network for the terminal device 110, the access information being used to bill for the packet data unit (PDU) session of the terminal device 110, and the PDU session being established in the first network via the second network. At block 1120, the policy control device may send, via the interface, the access information of the terminal device 110 in the second network to the access management device in the first network.

[0146] In some embodiments, the policy control device may receive, via the interface, charging correlation information for the PDU session in the first network from the access management device in the first network; and send the charging correlation information to the session management device in the second network device.

[0147] In some embodiments, the interface is protected via a Secure Edge Protection Proxy (SEPP).

[0148] In some embodiments, the access information includes at least one of the following: an identifier for charging of the PDU session of the second network (i.e., the PDU session charging ID of the second network), an identifier of the second network, the location of the terminal device 110, or the access technology of the terminal device 110.

[0149] In some embodiments, the first network is a Public Land Mobile Network (PLMN), and the second network is a Standalone Non-Public Network (SNPN). In some other embodiments, the first network is an SNPN, and the second network is a PLMN.

[0150] Figure 12 FIG. illustrates a schematic diagram of method 1200 implemented at a session management device in a second network according to some other embodiments of the present disclosure. At block 1210, the session management device may receive, from a policy control device in the second network, charging correlation information for the packet data unit (PDU) session of the terminal device 110, and the PDU session is established in the first network via the second network. At block 1220, the session management device may send a charging request including the charging correlation information to a charging device in the second network device.

[0151] In some embodiments, the charging correlation information includes at least one of the following: an identifier for charging of the PDU session assigned by the session management device in the first network, the address of the session management device in the first network, or an identifier of the first network.

[0152] In some embodiments, the first network is a Public Land Mobile Network (PLMN), and the second network is a Standalone Non-Public Network (SNPN). In some other embodiments, the first network is an SNPN, and the second network is a PLMN.

[0153] Figure 13 FIG. illustrates a schematic diagram of a method 1300 implemented at a charging device in a second network according to some other embodiments of the present disclosure. At block 1310, the charging device in the second network may receive a charging request from a session management device in the second network, the charging request including charging correlation information of a Packet Data Unit (PDU) session of the terminal device 110, and the PDU session is established in the first network via the second network. At block 1320, the charging device in the second network may generate a Charging Data Record (CDR) of the PDU session in the second network based on the charging correlation information. In step 1330, the charging device in the second network may send the CDR in the second network to an accounting device in the second network.

[0154] In some embodiments, the charging correlation information includes at least one of the following: an identifier of charging for the PDU session assigned by a session management device in the first network, an address of the session management device in the first network, or an identifier of the first network.

[0155] In some embodiments, the charging device may generate the CDR in the second network by performing inter-operator charging based on the wholesale tariff of the terminal device 110 for the PDU session by the provider of the first network.

[0156] In some embodiments, the CDR in the second network includes the charging correlation information.

[0157] In some embodiments, the first network is a Public Land Mobile Network (PLMN), and the second network is a Standalone Non-Public Network (SNPN). In some other embodiments, the first network is an SNPN, and the second network is a PLMN.

[0158] Figure 14 FIG. illustrates a schematic diagram of a method 1400 implemented at a second accounting device in a second network according to some other embodiments of the present disclosure. At block 1410, the second accounting device in the second network may receive a Charging Data Record (CDR) of a Packet Data Unit (PDU) session of the terminal device 110 in the second network from a charging device in the second network, and the PDU session is established in the first network via the second network. At block 1420, the second accounting device in the second network may send the CDR to a first accounting device in the first network.

[0159] In some embodiments, the first network is a Public Land Mobile Network (PLMN), and the second network is a Standalone Non-Public Network (SNPN). In some other embodiments, the first network is an SNPN, and the second network is a PLMN.

[0160] In some embodiments, an apparatus (e.g., an access management device in the first network (the core network 140 may be an example of the first network)) capable of performing any of the methods in method 700 may include components for performing the corresponding steps of method 700. The components may be implemented in any suitable form. For example, the components may be implemented in circuitry or software modules.

[0161] In some embodiments, the apparatus includes components for sending, at an access management device in the first network, a request for access information maintained in the second network for a terminal device 110 to a policy control device via an interface between the access management device and the policy control device in the second network, the access information being used for charging for a Packet Data Unit (PDU) session of the terminal device 110, the PDU session being established in the first network via the second network; components for receiving, via the interface, the access information of the terminal device 110 in the second network from the policy control device in the second network; and components for sending the access information of the terminal device 110 in the second network to a session management device in the first network.

[0162] In some embodiments, the first network is a Public Land Mobile Network (PLMN), and the second network is a Standalone Non-Public Network (SNPN), or the first network is an SNPN, and the second network is a PLMN.

[0163] In some embodiments, the access information includes at least one of the following: an identifier for charging of the PDU session in the second network (i.e., PDU session charging ID), an identifier of the second network, the location of the terminal device 110, or the access technology of the terminal device 110.

[0164] In some embodiments, the access management device further includes components for receiving, from a session management device in the first network, charging correlation information of the PDU session in the first network; and components for sending the charging correlation information to a policy control device in the second network via the interface.

[0165] In some embodiments, the interface is protected via a Secure Edge Protection Proxy (SEPP).

[0166] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 700. In some embodiments, the apparatus includes at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured to cause the apparatus to perform, together with the at least one processor.

[0167] In some embodiments, an apparatus (e.g., a session management device in core network 140) capable of performing any of the methods in method 800 may include components for performing the corresponding steps of method 800. The components may be implemented in any suitable form. For example, the components may be implemented in circuitry or software modules.

[0168] In some embodiments, the apparatus includes components for receiving, at a session management device in a first network, access information maintained in a second network of a terminal device 110 from an access management device in the first network, the access information being used for charging for a packet data unit (PDU) session of the terminal device 110, the PDU session being established in the first network via the second network; and components for sending a charging request to a charging device in the first network, the charging request including the access information of the terminal device 110 in the second network.

[0169] In some embodiments, the session management device further includes components for generating charging correlation information for charging for the PDU session in the first network; and components for sending the charging correlation information to an access management device in the first network.

[0170] In some embodiments, the first network is a public land mobile network (PLMN), and the second network is a standalone non-public network (SNPN); or the first network is an SNPN, and the second network is a PLMN.

[0171] In some embodiments, the charging correlation information includes at least one of the following: an identifier of the charging for the PDU session assigned by the session management device, an address of the session management device in the first network, or an identifier of the first network.

[0172] In some embodiments, the access information includes at least one of the following: an identifier of the PDU session charging in the second network (i.e., PDU session charging ID), an identifier of the second network, the location of the terminal device 110, or the access technology of the terminal device 110.

[0173] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 800. In some embodiments, the apparatus includes at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured to cause the apparatus to perform, together with the at least one processor.

[0174] In some embodiments, an apparatus (e.g., a charging device in core network 140) capable of performing any of the methods of method 900 may include components for performing the corresponding steps of method 900. The components may be implemented in any suitable form. For example, the components may be implemented in circuitry or software modules.

[0175] In some embodiments, the apparatus includes components for receiving a charging request from a session management device in a first network, the charging request including access information maintained in a second network for a terminal device 110, the access information being used to charge for a packet data unit (PDU) session of the terminal device 110, the PDU session being established in the first network via the second network; components for generating a charging data record (CDR) for the PDU session in the first network based on the access information of the terminal device 110 in the second network; and components for sending the CDR in the first network to a charging device in the first network.

[0176] In some embodiments, the first network is a public land mobile network (PLMN), and the second network is a standalone non-public network (SNPN); or the first network is an SNPN, and the second network is a PLMN.

[0177] In some embodiments, the access information includes at least one of the following: an identifier for PDU session charging in the second network (i.e., PDU session charging ID), an identifier of the second network, the location of the terminal device 110, or the access technology of the terminal device 110.

[0178] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 900. In some embodiments, the apparatus includes at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured to cause the apparatus to perform, together with the at least one processor.

[0179] In some embodiments, an apparatus (e.g., a first charging device in core network 140) capable of performing any of the methods of method 1000 may include components for performing the corresponding steps of method 1000. The components may be implemented in any suitable form. For example, the components may be implemented in circuitry or software modules.

[0180] In some embodiments, the apparatus includes components for receiving, at a first charging device in a first network, a first charging data record (CDR) of a packet data unit (PDU) session of a terminal device 110 in the first network from a charging device in the first network, the PDU session being established in the first network via a second network; components for receiving a second CDR of the PDU session in the second network from a second charging device in the second network; and components for correlating the first CDR and the second CDR.

[0181] In some embodiments, the first network is a public land mobile network (PLMN), and the second network is a standalone non-public network (SNPN); or the first network is an SNPN, and the second network is a PLMN.

[0182] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 1000. In some embodiments, the apparatus includes at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to perform.

[0183] In some embodiments, an apparatus (e.g., a policy control device in a second network (core network 130 can be an example of the second network)) capable of performing any method of method 1100 may include components for performing the corresponding steps of method 1100. The components may be implemented in any suitable form. For example, the components may be implemented in circuitry or software modules.

[0184] In some embodiments, the apparatus includes components for receiving, at a policy control device in a second network, a request for access information maintained in the second network for the terminal device 110 from an access management device via an interface between the access management device in the first network and the policy control device, the access information being used for charging the PDU session of the terminal device 110, the PDU session being established in the first network via the second network; and components for sending, via the interface, the access information of the terminal device 110 in the second network to the access management device in the first network.

[0185] In some embodiments, the policy control device further includes components for receiving, via the interface, charging correlation information of the PDU session in the first network from the access management device in the first network; and components for sending the charging correlation information to a session management device in the second network device.

[0186] In some embodiments, the interface is protected via a secure edge protection proxy (SEPP).

[0187] In some embodiments, the access information includes at least one of the following: an identifier for PDU session charging of the second network (i.e., PDU session charging ID), an identifier of the second network, the location of the terminal device 110, or the access technology of the terminal device 110.

[0188] In some embodiments, the first network is a Public Land Mobile Network (PLMN), and the second network is a Standalone Non-Public Network (SNPN); or the first network is an SNPN, and the second network is a PLMN.

[0189] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 1100. In some embodiments, the apparatus includes at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to perform.

[0190] In some embodiments, an apparatus (e.g., a session management device in the core network 130) capable of performing any method of method 1200 may include components for performing the corresponding steps of method 1200. The components may be implemented in any suitable form. For example, the components may be implemented in circuitry or software modules.

[0191] In some embodiments, the apparatus includes components for receiving, at a session management device in the second network, charging relevance information of a Packet Data Unit (PDU) session of the terminal device 110 from a policy control device in the second network, the PDU session being established in the first network via the second network; and components for sending a charging request including the charging relevance information to a charging device in the second network device.

[0192] In some embodiments, the charging relevance information includes at least one of the following: an identifier for charging of the PDU session allocated by a session management device in the first network, the address of the session management device in the first network, or an identifier of the first network.

[0193] In some embodiments, the first network is a Public Land Mobile Network (PLMN), and the second network is a Standalone Non-Public Network (SNPN); or the first network is an SNPN, and the second network is a PLMN.

[0194] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 1200. In some embodiments, the apparatus includes at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to perform.

[0195] In some embodiments, an apparatus (e.g., a charging device in the core network 130) capable of performing any of the methods of method 1300 may include components for performing the corresponding steps of method 1300. The components may be implemented in any suitable form. For example, the components may be implemented in circuitry or software modules.

[0196] In some embodiments, the apparatus includes components for receiving, at a charging device in a second network, a charging request from a session management device in the second network, the charging request including charging correlation information for a packet data unit (PDU) session of the terminal device 110, the PDU session being established in a first network via the second network; components for generating a charging data record (CDR) for the PDU session in the second network based on the charging correlation information; and components for sending the CDR in the second network to a charging device in the second network.

[0197] In some embodiments, the charging correlation information includes at least one of the following: an identifier for charging of the PDU session assigned by a session management device in the first network, an address of the session management device in the first network, or an identifier of the first network.

[0198] In some embodiments, the components for generating the CDR in the second network include components for performing inter-operator charging based on a wholesale tariff of the terminal device 110 for the PDU session according to the offering of the first network.

[0199] In some embodiments, the CDR in the second network includes the charging correlation information.

[0200] In some embodiments, the first network is a public land mobile network (PLMN), and the second network is a standalone non-public network (SNPN); or the first network is an SNPN, and the second network is a PLMN.

[0201] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 1300. In some embodiments, the apparatus includes at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured to cause the apparatus to perform in conjunction with the at least one processor.

[0202] In some embodiments, an apparatus (e.g., a second charging device in the core network 130) capable of performing any of the methods of method 1400 may include components for performing the corresponding steps of method 1400. The components may be implemented in any suitable form. For example, the components may be implemented in circuitry or software modules.

[0203] In some embodiments, the apparatus includes components for receiving, at a second accounting device in a second network, a charging data record (CDR) of a packet data unit (PDU) session of a terminal device 110 in the second network from a charging device in the second network, where the PDU session is established in a first network via the second network; and components for sending the CDR to a first accounting device in the first network.

[0204] In some embodiments, the first network is a public land mobile network (PLMN), and the second network is a standalone non-public network (SNPN); or the first network is an SNPN, and the second network is a PLMN.

[0205] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 1400. In some embodiments, the apparatus includes at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to perform.

[0206] Figure 15 is a simplified block diagram of a device 1500 suitable for implementing embodiments of the present disclosure. The device 1500 may be provided to implement a communication device, such as Figure 1A a device in the core network 130 or core network 140 as shown, or the core network 130 or core network 140. As shown, the device 1500 includes one or more processors 1510, one or more memories 1540 coupled to the processors 1510, and one or more transmitters and / or receivers (TX / RX) 1540 coupled to the processors 1510.

[0207] The TX / RX 1540 is used for two-way communication. The TX / RX 1540 has at least one antenna to facilitate communication. The communication interface may represent any interface required for communication with other network elements.

[0208] The processor 1510 may be of any type suitable for a local technical network and, by way of non-limiting example, may include one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 1500 may have multiple processors, such as an application-specific integrated circuit chip that is subordinate in time to a clock synchronized with a main processor.

[0209] The memory 1520 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1524, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic storage devices and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1522 and other volatile memories that do not persist during a power outage.

[0210] The computer program 1530 includes computer-executable instructions that are executed by the associated processor 1510. The program 1530 may be stored in the ROM 1524. The processor 1510 may perform any suitable actions and processing by loading the program 1530 into the RAM 1522.

[0211] Embodiments of the present disclosure may be implemented by the program 1530 such that the device 1500 may execute any process of the present disclosure referred to Figures 2 to 14 in the discussion. Embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0212] In some embodiments, the program 1530 may be tangibly embodied in a computer-readable medium, which may be included in the device 1500 (such as in the memory 1520) or in other storage devices accessible by the device 1500. The device 1500 may load the program 1530 from the computer-readable medium into the RAM 1522 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 16 An example of a computer-readable medium 1600 in the form of a CD or DVD is shown. The program 1530 is stored on the computer-readable medium.

[0213] Generally, various embodiments of the present disclosure may be implemented using hardware or special-purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented using hardware, while other aspects may be implemented using firmware or software that may be executed by a controller, microprocessor, or other computing device. Although the various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, by way of non-limiting example, the blocks, devices, systems, techniques, or methods described herein may be implemented using hardware, software, firmware, special-purpose circuits or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0214] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in program modules, which are executed in a device on a target real or virtual processor to perform the methods 700 to 1400 referred to above Figures 2 to 14 The methods 700 to 1400 described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of program modules can be combined or split among program modules as needed. The machine-executable instructions of program modules can be executed within a local or distributed device. In a distributed device, program modules can be located in both local and remote storage media.

[0215] The program code for performing the methods of the present disclosure can be written in any combination of one or more programming languages. The program code can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when the program code is executed by the processor or controller, the functions / operations specified in the flowchart and / or block diagram are implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

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

[0217] The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer-readable storage medium will include an electrical connection having one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The term "non-transitory" as used herein is a limitation on the medium itself (i.e., tangible, rather than a signal), rather than a limitation on the persistence of data storage (e.g., RAM versus ROM).

[0218] Moreover, although the operations are described in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in sequential order, or that all of the illustrated operations be performed to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented separately or in any suitable subcombination in multiple embodiments.

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

Claims

1. An access management device in a first network, comprising: At least one processor; And At least one memory storing instructions that, when executed by the at least one processor, cause the access management device to at least: Send, via an interface between the access management device and a policy control device in a second network, a request for access information maintained in the second network, the access information being used for charging for a packet data unit (PDU) session of a terminal device, the PDU session being established in the first network via the second network; Receive, via the interface, the access information of the terminal device in the second network from the policy control device in the second network; And Send the access information of the terminal device in the second network to a session management device in the first network.

2. The access management device according to claim 1, wherein: The first network is a public land mobile network (PLMN), and the second network is a standalone non-public network (SNPN); or The first network is an SNPN, and the second network is a PLMN.

3. The access management device according to claim 1 or 2, wherein the access information includes at least one of the following: An identifier for charging of the PDU session in the second network, An identifier of the second network, The location of the terminal device, or The access technology of the terminal device.

4. The access management device according to any one of claims 1 to 3, wherein the access management device is further caused to: Receive, from the session management device in the first network, charging correlation information for the PDU session in the first network; and Send the charging correlation information to the policy control device in the second network via the interface.

5. The access management device according to any one of claims 1 to 4, wherein the interface is protected via a secure edge protection proxy (SEPP).

6. A session management device in a first network, comprising: At least one processor; And At least one memory storing instructions that, when executed by the at least one processor, cause the session management device to at least: Receive, from an access management device in the first network, access information of a terminal device maintained in a second network, the access information being used for charging for a packet data unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; And Send a charging request to a charging device in the first network, the charging request including: the access information of the terminal device in the second network.

7. The session management device according to claim 6, wherein the session management device is further caused to: Generate charging correlation information for charging the PDU session in the first network; and Send the charging correlation information to the access management device in the first network.

8. The session management device according to claim 6 or 7, wherein: The first network is a Public Land Mobile Network (PLMN), and the second network is a Standalone Non-Public Network (SNPN); or The first network is an SNPN, and the second network is a PLMN.

9. The session management device according to claim 7, wherein the charging correlation information includes at least one of the following: An identifier allocated by the session management device for charging of the PDU session, The address of the session management device in the first network, or The identifier of the first network.

10. The session management device according to any one of claims 6 to 9, wherein the access information includes at least one of the following: An identifier for charging of the PDU session of the second network, The identifier of the second network, The location of the terminal device, or The access technology of the terminal device.

11. A charging device in a first network, comprising: At least one processor; And At least one memory storing instructions which, when executed by the at least one processor, cause the charging device to at least: Receive a charging request from a session management device in the first network, the charging request including: access information maintained by a terminal device in a second network for charging a Packet Data Unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; Generate a Charging Data Record (CDR) in the first network for the PDU session based on the access information of the terminal device in the second network; and Send the CDR in the first network to a billing device in the first network.

12. The charging device according to claim 11, wherein the first network is a Public Land Mobile Network (PLMN), and the second network is a Standalone Non-Public Network (SNPN); or The first network is an SNPN, and the second network is a PLMN.

13. The charging device according to claim 11 or 12, wherein the access information includes at least one of the following: An identifier for charging of the PDU session for the second network, The identifier of the second network, The location of the terminal device, or The access technology of the terminal device.

14. A first billing device in a first network, comprising: At least one processor; And At least one memory storing instructions which, when executed by the at least one processor, cause the first billing device to at least: Receive a first Charging Data Record (CDR) in the first network for a Packet Data Unit (PDU) session of a terminal device from a charging device in the first network, the PDU session being established in the first network via a second network; Receive a second CDR in the second network for the PDU session from a second billing device in the second network; and Associate the first CDR and the second CDR.

15. According to claim 14, the first billing device, wherein: The first network is a Public Land Mobile Network (PLMN), and the second network is a Standalone Non-Public Network (SNPN); or The first network is an SNPN, and the second network is a PLMN.

16. A policy control device in a second network, comprising: At least one processor; And At least one memory storing instructions which, when executed by the at least one processor, cause the policy control device to at least: Receive, via an interface between an access management device in a first network and the policy control device, a request from the access management device for access information maintained in the second network for a terminal device, the access information being used for charging for a Packet Data Unit (PDU) session of the terminal device, the PDU session being established in the first network via the second network; And Send, via the interface, the access information of the terminal device in the second network to the access management device in the first network.

17. The policy control device according to claim 16, wherein the policy control device is further caused to: Receive, via the interface, charging relevance information for the PDU session in the first network from the access management device in the first network; and Send the charging relevance information to a session management device in the second network device.

18. The policy control device according to claim 16 or 17, wherein the interface is protected via a Secure Edge Protection Proxy (SEPP).

19. The policy control device according to any one of claims 16 to 18, wherein the access information includes at least one of the following: An identifier for charging for the PDU session for the second network, An identifier of the second network, The location of the terminal device, or The access technology of the terminal device.

20. The policy control device according to any one of claims 16 to 19, wherein: The first network is a Public Land Mobile Network (PLMN), and the second network is a Standalone Non-Public Network (SNPN); or The first network is an SNPN, and the second network is a PLMN.

21. A session management device in a second network, comprising: At least one processor; And At least one memory storing instructions which, when executed by the at least one processor, cause the session management device to at least: Receive, from a policy control device in the second network, charging relevance information for a Packet Data Unit (PDU) session of a terminal device, the PDU session being established in the first network via the second network; And Send a charging request including the charging relevance information to a charging device in the second network device.

22. The session management device according to claim 21, wherein the charging relevance information includes at least one of the following: An identifier for charging for the PDU session assigned by a session management device in the first network, The address of the session management device in the first network, or An identifier of the first network.

23. The session management device according to claim 21 or 22, wherein: the first network is a Public Land Mobile Network (PLMN), and the second network is a Standalone Non-Public Network (SNPN); or the first network is an SNPN, and the second network is a PLMN.

24. A charging device in a second network, comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the charging device to at least: receive a charging request from a session management device in the second network, the charging request including: charging relevance information for a Packet Data Unit (PDU) session of a terminal device, the PDU session being established in a first network via the second network; generate, based on the charging relevance information, a Charging Data Record (CDR) in the second network for the PDU session; and send the CDR in the second network to a billing device in the second network.

25. The charging device according to claim 24, wherein the charging relevance information includes at least one of the following: an identifier for charging of the PDU session assigned by a session management device in the first network, the address of the session management device in the first network, or an identifier of the first network.

26. The charging device according to claim 24, wherein the charging device is caused to generate the CDR in the second network by: performing inter-operator charging based on the wholesale tariff of the terminal device for the PDU session by the provider of the first network.

27. The charging device according to claim 24, wherein the CDR in the second network includes: The charging relevance information.

28. The charging device according to any one of claims 24 to 28, wherein: the first network is a Public Land Mobile Network (PLMN), and the second network is a Standalone Non-Public Network (SNPN); or the first network is an SNPN, and the second network is a PLMN.

29. A second billing device in a second network, comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the second billing device to at least: receive, from a charging device in the second network, a Charging Data Record (CDR) in the second network for a Packet Data Unit (PDU) session of a terminal device, the PDU session being established in a first network via the second network; and send the CDR to a first billing device in the first network.

30. The second billing device according to claim 29, wherein: the first network is a Public Land Mobile Network (PLMN), and the second network is a Standalone Non-Public Network (SNPN); or the first network is an SNPN, and the second network is a PLMN.

31. A method, comprising: At an access management device in a first network, a request for access information maintained for a terminal device in a second network is sent to a policy control device via an interface between the access management device and the policy control device in the second network, where the access information is used to charge for a packet data unit (PDU) session of the terminal device, and the PDU session is established in the first network via the second network; Receive the access information of the terminal device in the second network from the policy control device in the second network via the interface; And Send the access information of the terminal device in the second network to a session management device in the first network.

32. A method includes: At a session management device in a first network, receive access information maintained for a terminal device in a second network from an access management device in the first network, where the access information is used to charge for a packet data unit (PDU) session of the terminal device, and the PDU session is established in the first network via the second network; And Send a charging request to a charging device in the first network, where the charging request includes: the access information of the terminal device in the second network.

33. A method includes: At a charging device in a first network, receive a charging request from a session management device in the first network, where the charging request includes: access information maintained for a terminal device in a second network, and the access information is used to charge for a packet data unit (PDU) session of the terminal device, and the PDU session is established in the first network via the second network; Generate a charging data record (CDR) for the PDU session in the first network based on the access information of the terminal device in the second network; and Send the CDR in the first network to a accounting device in the first network.

34. A method includes: At a first accounting device in a first network, receive a first charging data record (CDR) for a packet data unit (PDU) session of a terminal device in the first network from a charging device in the first network, where the PDU session is established in the first network via a second network; Receive a second CDR for the PDU session in the second network from a second accounting device in the second network; and Associate the first CDR and the second CDR.

35. A method includes: At a policy control device in a second network, receive a request for access information maintained for a terminal device in the second network from an access management device in the first network via an interface between the access management device in the first network and the policy control device, where the access information is used to charge for a packet data unit (PDU) session of the terminal device, and the PDU session is established in the first network via the second network; And Send the access information of the terminal device in the second network to the access management device in the first network via the interface.

36. A method includes: At a session management device in a second network, receive charging correlation information for a packet data unit (PDU) session of a terminal device from a policy control device in the second network, where the PDU session is established in a first network via the second network; And Send a charging request including the charging correlation information to a charging device in the second network device.

37. A method, comprising: At a charging device in a second network, receive a charging request from a session management device in the second network, where the charging request includes: charging correlation information for a packet data unit (PDU) session of a terminal device, where the PDU session is established in a first network via the second network; Based on the charging correlation information, generate a charging data record (CDR) for the PDU session in the second network; and Send the CDR in the second network to a billing device in the second network.

38. A method, comprising: At a second billing device in a second network, receive a charging data record (CDR) for a packet data unit (PDU) session of a terminal device in the second network from a charging device in the second network, where the PDU session is established in a first network via the second network; And Send the CDR to a first billing device in the first network.

39. A device, comprising: A component for sending, at an access management device in a first network, a request for access information maintained in a second network for a terminal device to the policy control device via an interface between the access management device and the policy control device in the second network, where the access information is used for charging a packet data unit (PDU) session of the terminal device, and the PDU session is established in the first network via the second network; A component for receiving, via the interface, the access information of the terminal device in the second network from the policy control device in the second network; And A component for sending the access information of the terminal device in the second network to a session management device in the first network.

40. A device, comprising: A component for receiving, at a session management device in a first network, access information maintained in a second network for a terminal device from an access management device in the first network, where the access information is used for charging a packet data unit (PDU) session of the terminal device, and the PDU session is established in the first network via the second network; And A component for sending a charging request to a charging device in the first network, where the charging request includes: the access information of the terminal device in the second network.

41. A device, comprising: A component for receiving a charging request at a charging device in a first network from a session management device in the first network, the charging request including: access information maintained by a terminal device in a second network, the access information being used for charging a packet data unit (PDU) session of the terminal device, and the PDU session being established in the first network via the second network; A component for generating a charging data record (CDR) for the PDU session in the first network based on the access information of the terminal device in the second network; and A component for sending the CDR in the first network to a charging settlement device in the first network.

42. An apparatus, comprising: A component for receiving, at a first charging settlement device in a first network, a first charging data record (CDR) for a packet data unit (PDU) session of a terminal device in the first network from a charging device in the first network, the PDU session being established in the first network via a second network; A component for receiving a second CDR for the PDU session in the second network from a second charging settlement device in the second network; And A component for correlating the first CDR and the second CDR.

43. An apparatus, comprising: A component for receiving, at a policy control device in a second network, a request for access information maintained by a terminal device in the second network from an access management device via an interface between the access management device and the policy control device in the first network, the access information being used for charging a packet data unit (PDU) session of the terminal device, and the PDU session being established in the first network via the second network; And A component for sending the access information of the terminal device in the second network to the access management device in the first network via the interface.

44. An apparatus, comprising: A component for receiving, at a session management device in a second network, charging relevance information for a packet data unit (PDU) session of a terminal device from a policy control device in the second network, the PDU session being established in the first network via the second network; And A component for sending a charging request including the charging relevance information to a charging device in the second network device.

45. An apparatus, comprising: A component for receiving, at a charging device in a second network, a charging request from a session management device in the second network, the charging request including: charging relevance information for a packet data unit (PDU) session of a terminal device, and the PDU session being established in a first network via the second network; A component for generating a charging data record (CDR) for the PDU session in the second network based on the charging relevance information; and A component for sending the CDR in the second network to a charging settlement device in the second network.

46. An apparatus, comprising: A component for receiving, at a second accounting device in a second network, a charging data record (CDR) of a packet data unit (PDU) session for a terminal device in the second network from a charging device in the second network, wherein the PDU session is established in a first network via the second network; and A component for sending the CDR to a first accounting device in the first network.

47. A non-transitory computer-readable medium comprising program instructions that, when executed by a device, cause the device to perform at least the method according to any one of claims 31 to 38.

Images