WO2024125384A1 - 计费方法与装置 - Google Patents

计费方法与装置 Download PDF

Info

Publication number
WO2024125384A1
WO2024125384A1 PCT/CN2023/137073 CN2023137073W WO2024125384A1 WO 2024125384 A1 WO2024125384 A1 WO 2024125384A1 CN 2023137073 W CN2023137073 W CN 2023137073W WO 2024125384 A1 WO2024125384 A1 WO 2024125384A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
function network
charging
billing
terminal device
Prior art date
Application number
PCT/CN2023/137073
Other languages
English (en)
French (fr)
Inventor
柴晓前
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024125384A1 publication Critical patent/WO2024125384A1/zh

Links

Definitions

  • the present application relates to the field of communications, and more specifically, to a charging method and device.
  • the online and offline billing integration architecture includes a core network, a billing system, and an accounting domain.
  • the billing system can provide online and/or offline billing functions for users communicating with the core network.
  • the billing trigger function network element in the core network requests the billing system to perform billing processing for the user.
  • the core network and the billing system are generally deployed in different regions, for example, each billing system corresponds to a region, and for example, one or more core networks correspond to a region.
  • the billing system at the home location usually performs billing processing for the terminal device.
  • the billing system at the home location changes, especially when the user moves across regions, in order for the billing system at the home location to perform billing processing for the user, a large amount of billing data needs to be frequently transmitted across regions, which will occupy too many network resources and consume a lot of operating costs.
  • scenarios that require frequent cross-regional transmission will become more and more common, and the pressure on the network will also increase.
  • the present application provides a billing method and device, which can save network resources and thus reduce operating costs.
  • a charging method is provided, which can be executed by a first charging function network element, or can also be executed by a component (such as a chip or circuit) of the first charging function network element, and this application does not limit this.
  • a component such as a chip or circuit
  • the method may include: a first billing function network element receives a first billing request from a billing trigger function network element, the first billing request is used to request billing for a terminal device; the first billing function network element sends a data acquisition request to other billing function network elements, the data acquisition request is used to request first user data; the first billing function network element receives the first user data from the other billing function network elements; the first billing function network element performs billing processing on the terminal device according to the first user data.
  • the network providing services for the terminal device may also change.
  • the network closest to the current location of the terminal device provides services for the terminal device. Since the network where the billing trigger function network element is located is the network currently providing services to the terminal device, the network where the billing trigger function network element is located is the network closest to the current location of the terminal device.
  • a core network has a corresponding billing function network element. If the billing function network element corresponding to the network where the billing trigger function network element is located performs billing processing for the terminal device, the billing function network element closest to the terminal device can perform billing processing for the terminal device.
  • the first billing function network element after the first billing function network element receives the first billing request from the billing trigger function network, it performs billing processing according to the first user data obtained from other billing function network elements. Compared with the billing function network element of the home location of the terminal device performing billing processing for the terminal device, it can avoid frequent cross-regional transmission of billing data, save network resources, and thus reduce operating costs.
  • the above solution can reduce the possibility of billing failure, thereby improving the reliability of the network, while also reducing the adverse effects on the service use of the terminal device when a billing network line fails, thereby improving the user experience of the terminal device.
  • the user data of the terminal device includes one or more of the following: charging resource context data, account data, policy data, and data of a charging gateway function.
  • the first user data is part or all of the user data of the terminal device.
  • the first charging function network element sends data to other charging function network elements. Before obtaining the request, the method further includes: the first charging function network element determines to obtain the first user data from the other charging function network element.
  • charging data (such as call records) is frequently generated, or the charging data needs to be updated in real time. Therefore, the charging function network element near the terminal device needs to frequently transmit the charging data generated by the terminal device to the home charging function network element.
  • the above-mentioned scheme is that the first billing function network element can perform billing processing for the terminal device as long as it obtains user data from other billing function network elements. There is no need to transmit billing data with other billing function network elements.
  • the billing processing is performed by the billing function network element in the home location, which can avoid frequent cross-regional transmission of billing data, save network resources, and thus reduce operating costs.
  • the other billing function network element is a second billing function network element, which is a network element that provides billing service functions for the terminal device before the first billing function network element provides billing service functions for the terminal device.
  • the second billing function network element is a network element that performs billing processing for the terminal device before the first billing function network element performs billing processing for the terminal device, wherein the "before” here is understood as a concept in terms of time sequence.
  • the second billing function network element is the network element that performs billing processing for the terminal device before the first billing function network element performs billing processing for the terminal device, wherein the "before” here is understood as a concept in terms of time sequence.
  • the second billing function network element is the network element that performs billing processing for the terminal device before the location of the terminal device changes
  • the first billing function network element is the network element that performs billing processing for the terminal device after the location of the terminal device changes.
  • first billing function network element and the second billing function network element belong to different converged billing systems.
  • the above solution can realize the interaction between different converged billing systems and improve the flexibility of the billing system.
  • the other billing function network element is a management and billing function network element, which is used to maintain the correspondence between the terminal device and the billing function network element that currently performs billing processing for the terminal device.
  • the management and billing function network element assists in transmitting user data between different converged billing systems, and each converged billing system only needs to interact with the management and billing function network element to transmit user data.
  • the complexity of multi-system interaction can be reduced.
  • the method also includes: the first billing function network element receives second user data from the other billing function network element, and the second user data is generated by the second billing function network element for the terminal device after the first billing function network element receives the first user data; the first billing function network element updates the first user data according to the second user data.
  • the billing process on the first billing function network element can also start, and the first billing function network element can obtain the first user data that has been generated.
  • the first billing function network element can continue to obtain the second user data. This can improve the flexibility of the first billing function network element in obtaining user data of the terminal device.
  • the first charging function network element updates the first user data according to the second user data before performing charging processing on the terminal device, and then performs charging processing according to the updated first user data.
  • the method before the first billing function network element receives the first user data from the other billing function network element, or before the first billing function network element performs the billing processing, the method also includes: the first billing function network element sends a first billing response to the billing triggering function network element, and the first billing response is used to indicate the release of the service of the terminal device.
  • the above solution can reduce the problem of timeout in processing the first billing request due to the first billing function network element taking too long to obtain the first user data from other billing function network elements and/or the first billing function network element taking too long to perform billing processing.
  • the method after the first billing function network element executes the billing processing, the method also includes: the first billing function network element sends a second billing response to the billing trigger function network element, and the second billing response is used to indicate that the billing processing has been executed, or the second billing response includes the result of the billing processing.
  • the above scheme enables the charging triggering function network element to provide services to the terminal device according to the result of the charging processing.
  • the method after the first billing function network element receives the first user data, the method also includes: the first billing function network element sends an indication message to the billing trigger function network element, the indication message being used to indicate a re-request to execute billing on the terminal device; the first billing function network element receives a second billing request from the billing trigger function network element, the second billing request being used to request to execute billing on the terminal device.
  • the first user data includes data for performing the billing process.
  • the method further includes: the first charging function network element sends a third charging response to the charging triggering function network element, the third charging response includes a result of the charging process, or is used to indicate that the charging process has been executed.
  • the above scheme enables the charging triggering function network element to provide services to the terminal device according to the result of the charging processing.
  • the first billing function network element first obtains data for executing billing processing from other billing function network elements, which can reduce the problem of the first billing function network element taking too long to obtain the first user data from other billing function network elements, resulting in a long billing processing time.
  • the other billing function network element is the second billing function network element, and the first billing request includes the address information of the second billing function network element; or, the method further includes: the first billing function network element sends an address information acquisition request to the management and billing function network element or the network storage function network element, and the address information request is used to request the address information of the service billing function network element that is currently performing billing processing on the terminal device; the first billing function network element receives the address information of the second billing function network element from the management and billing function network element or the network storage function network element.
  • the first charging request obtains the address information of the second charging function network element so as to obtain the user data of the terminal device from the second charging function network element.
  • the method also includes: the first billing function network element sends a notification to the management billing function network element or the network storage function network element, and the notification is used to indicate that the service billing function network element currently performing billing processing for the terminal device is the first billing function network element.
  • the above scheme is to manage the billing function network element or the network storage function network element to update the billing function network element currently providing billing service for the terminal device to the first billing function network element.
  • a charging method which can be executed by a charging trigger function network element, or can also be executed by a component (such as a chip or circuit) of the charging trigger function network element, and this application does not limit this.
  • a charging trigger function network element can be executed by a charging trigger function network element, or can also be executed by a component (such as a chip or circuit) of the charging trigger function network element, and this application does not limit this.
  • the following is an example of execution by a charging trigger function network element.
  • the method may include: the billing trigger function network element obtains the address information of the first billing function network element based on the information of the billing trigger function network element and/or the location information of the terminal device, and the first billing function network element is a candidate billing function network element for providing billing services to the terminal device; the billing trigger function network element sends a first billing request to the first billing function network element based on the address information, and the first billing request is used to request billing processing to be performed on the terminal device.
  • the charging triggering function network element selects a candidate charging function network element and requests the candidate charging function network element to perform charging processing for the terminal device.
  • the billing trigger function network element obtains the address information of the first billing function network element based on the information of the billing trigger function network element and/or the location information of the terminal device, including: the billing trigger function network element sends an address information request to the management and billing function network element or the network storage function network element, the address information request is used to request to obtain the address information of a candidate billing function network element for performing billing processing on the terminal device, the address information request includes the location information of the terminal device and/or the information of the billing trigger function network element; the billing trigger function network element receives the address information of the first billing function network element from the management and billing function network element or the network storage function network element.
  • the billing trigger function network element obtains the address information of the first billing function network element based on the information of the billing trigger function network element and/or the location information of the terminal device, including: the billing trigger function network element determines, in the local configuration information, the address information of the first billing function network element corresponding to the location information of the terminal device and/or the information of the billing trigger function network element.
  • the first billing request includes address information of a second billing function network element
  • the second billing function network element is a network element that provides billing service functions to the terminal device before the first billing function network element provides billing service functions to the terminal device.
  • the above scheme enables the first charging function network element to obtain the user data of the terminal device from the second charging function network element according to the address information.
  • the method further includes: the billing trigger function network element receives a first billing response from the first billing function network element, and the first billing response is used to indicate the release of the service of the terminal device.
  • the above solution can reduce the problem of timeout in processing the first billing request due to the first billing function network element taking too long to obtain the first user data from other billing function network elements and/or the first billing function network element taking too long to perform billing processing.
  • the method after the billing trigger function network element receives the first billing response, the method also includes: the billing trigger function network element receives a second billing response from the first billing function network element, and the second billing response is used to indicate that the billing processing has been performed, or includes the result of the billing processing.
  • the above scheme enables the charging triggering function network element to provide services to the terminal device according to the result of the charging processing.
  • the method after the billing trigger function network element receives the first billing response, the method also includes: the billing trigger function network element receives indication information from the first billing function network element, and the indication information is used to indicate a re-request to execute billing on the terminal device; the billing trigger function network element sends a second billing request to the first billing function network element based on the indication information, and the second billing request is used to request to execute billing on the terminal device.
  • the above solution enables the charging trigger function network element to determine when the first charging function network element performs charging processing.
  • the method further includes: the billing trigger function network element receives a third billing response from the first billing function network element, and the third billing response includes a result of the billing processing.
  • the above scheme enables the charging triggering function network element to provide services to the terminal device according to the result of the charging processing.
  • a charging method is provided, which can be executed by a management and charging function network element, or can also be executed by a component (such as a chip or circuit) of the management and charging function network element, and this application does not limit this.
  • a component such as a chip or circuit
  • this application does not limit this.
  • the following is an example of execution by a management and charging function network element.
  • the method may include: a management and billing function network element stores a first correspondence between a terminal device and a second billing function network element, the second billing function network element being a service billing function network element that currently performs billing processing on the terminal device; the management and billing function network element receives operation requests from other function network elements; and the management and billing function network element processes the operation request according to the first correspondence.
  • other functional network elements may include network elements within the converged billing system, network elements within the core network, or network elements outside the converged billing system and the core network.
  • the above scheme stores the first corresponding relationship to assist other functional network elements in obtaining data related to the terminal device, data related to providing billing services for the terminal device, and data related to the second billing functional network element.
  • the operation request is used to request the address information of the service billing function network element
  • the management and billing function network element processes the operation request according to the first correspondence, including: in response to the operation request, the management and billing function network element sends the address information of the second billing function network element to the other function network elements.
  • the above solution can assist other functional network elements to obtain the address information of the second billing functional network element, so that other functional network elements can determine the service billing functional network element.
  • the other functional network element is a first billing function network element, which is a network element that provides billing service functions for the terminal device after the second billing function network element provides billing service functions for the terminal device, and the operation request is used to request first user data of the terminal device;
  • the management and billing function network element processes the operation request according to the first correspondence, including: the management and billing function network element sends a data acquisition request to the second billing function network element, and the data acquisition request is used to request the first user data of the terminal device;
  • the management and billing function network element receives the first user data from the second billing function network element, and the first user data is used to perform billing processing for the terminal device;
  • the management and billing function network element sends the first user data to the first billing function network element.
  • the management and billing function network element assists in transmitting user data between different converged billing systems, and each converged billing system only needs to interact with the management and billing function network element to transmit user data.
  • the complexity of multi-system interaction can be reduced.
  • the method further includes: the management and billing function network element updating the first corresponding relationship to a second corresponding relationship between the terminal device and the first billing function network element.
  • the recipient of the user data is determined to be the network element that currently provides billing services for the terminal device, and the correspondence between the terminal device and the network element that currently provides billing services for the terminal device is updated, so as to facilitate subsequent assistance to other functional network elements in obtaining data related to the terminal device, data related to providing billing services to the terminal device, and data related to the second billing function network element.
  • the operation request is used to indicate that the service function network element is a first billing function network element
  • the first billing function network element is a network element that provides billing service functions for the terminal device after the second billing function network element provides billing service functions for the terminal device.
  • the management and billing function network element processes the operation request according to the first correspondence, including: the management and billing function network element receives a notification from the first billing function network element, and the notification is used to indicate that the service billing function network element currently performing billing processing for the terminal device is the first billing function network element; the management and billing function network element updates the first correspondence to the first billing function network element according to the notification.
  • the management billing function network element assists in transmitting user data between different converged billing systems, it determines the network element that currently provides billing services to the terminal device based on the notification to the first billing function network element, and updates the correspondence between the terminal device and the network element that currently provides billing services to the terminal device, so as to facilitate subsequent assistance to other functional network elements in obtaining data related to the terminal device, data related to providing billing services to the terminal device, and data related to the second billing function network element.
  • the operation request is used to request query or modification of the fourth user data of the terminal device, and the management and billing function network element processes the operation request according to the first correspondence, including: the management and billing function network element forwards the operation request to the second billing function network element according to the first correspondence; the management and billing function network element receives the processing result of the operation request from the second billing function network element; and the management and billing function network element sends the processing result to the other function network elements.
  • other functional network elements do not belong to the network that provides services for the terminal device, and do not belong to the billing system that currently provides billing services for the terminal device, and do not belong to the candidate billing system that provides billing services for the terminal device.
  • other functional network elements are network elements outside the converged billing architecture provided by this application, such as CRM, recharge server, accounting system, billing capability open platform, etc.
  • the above solution manages the interaction between the charging function network element and the network element outside the converged charging architecture, so that the network element outside the converged charging architecture can obtain the user data of the terminal device.
  • the network element outside the converged charging architecture does not need to perceive whether the charging function network element providing charging services for the terminal device has changed, which saves the complexity of processing the network element outside the converged charging architecture.
  • the method also includes: the management and billing function network element receives an address information request from a billing trigger function network element, the address information request is used to request address information of a candidate billing function network element that performs billing processing on the terminal device, the address information request includes one or more of the following: location information of the terminal device, information of the billing trigger function network element; in response to the address information request, the management and billing function network element sends the address information of the first billing function network element to the billing trigger function network element.
  • the management charging function network element provides the charging trigger function network element with information of the candidate charging function network element, so that the charging trigger function network element requests the candidate charging function network element to perform charging processing for the terminal device.
  • a communication device comprising: at least one processor, configured to execute a computer program or instruction stored in a memory to execute a method in any possible implementation of the first to third aspects above.
  • the device further comprises a memory for storing computer programs or instructions.
  • the device further comprises a communication interface, and the processor reads the computer programs or instructions stored in the memory through the communication interface.
  • the apparatus is a communication device (such as a first charging function network element, such as a charging triggering function network element, and such as a management charging function network element).
  • a communication device such as a first charging function network element, such as a charging triggering function network element, and such as a management charging function network element.
  • the device is a chip, a chip system or a circuit used in a communication device (such as a first charging function network element, a charging triggering function network element, or a management charging function network element).
  • a communication device such as a first charging function network element, a charging triggering function network element, or a management charging function network element.
  • the present application provides a processor for executing the methods provided in the first to third aspects above.
  • a communication system including a first billing function network element and a billing trigger function network element, the first billing function network element is used to implement the method in any possible implementation manner of the above-mentioned first aspect, and the billing trigger function network element is used to implement the method in any possible implementation manner of the above-mentioned second aspect.
  • the communication system further includes a management and billing function network element, which is used to implement the method in any possible implementation manner of the third aspect above.
  • a computer-readable storage medium which stores a program code for execution by a device, wherein the program code includes a method for executing any possible implementation of the first to third aspects above.
  • a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute a method in any possible implementation of the first to third aspects.
  • a communication method including: the billing trigger function network element obtains the address information of the first billing function network element according to the information of the billing trigger function network element and/or the location information of the terminal device; the billing trigger function network element sends a first billing request to the first billing function network element according to the address information, and the first billing request is used to request billing processing for the terminal device; the first billing function network element receives the first billing request from the billing trigger function network element, and the first billing request is used to request billing for the terminal device; the first billing function network element sends a data acquisition request to other billing function network elements, and the data acquisition request is used to request the first user of the terminal device the first charging function network element receives the first user data from the other charging function network element; the first charging function network element performs charging processing on the terminal device according to the first user data.
  • the other billing function network element is a second billing function network element or a management billing function network element
  • the management billing function network element is used to maintain the correspondence between the terminal device and the billing function network element that currently performs billing processing for the terminal device.
  • the second billing function network element is a network element that provides billing service functions to the terminal device before the first billing function network element provides billing service functions to the terminal device.
  • FIG. 1 shows a billing architecture 100 applicable to an embodiment of the present application.
  • FIG. 2 shows a system architecture 200 applicable to an embodiment of the present application.
  • FIG3 shows a schematic diagram of a charging method 300 provided in the present application.
  • FIG. 4 shows a schematic diagram of a specific example of the billing method 300 provided in the present application.
  • FIG. 5 shows a schematic diagram of a charging method 400 provided in the present application.
  • FIG. 6 shows a schematic diagram of a billing method 500 provided in the present application.
  • FIG. 7 shows a schematic diagram of a billing method 600 provided in the present application.
  • FIG8 shows a schematic diagram of a billing method 700 provided in the present application.
  • FIG. 9 shows a schematic diagram of a billing method 800 provided in the present application.
  • FIG. 10 shows a schematic diagram of a billing method 900 provided in the present application.
  • FIG. 11 shows a schematic diagram of a billing method 1000 provided in the present application.
  • FIG12 is a schematic block diagram of a communication device provided in the present application.
  • FIG. 13 is another schematic block diagram of the communication device provided in the present application.
  • the technical solution provided in this application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) communication system (or called the new radio (new radio, NR) system), the fourth generation (4th generation, 4G) communication system (or called the long term evolution (long term evolution, LTE) system), LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) system, etc.
  • the technical solution provided in this application can also be applied to future communication systems, such as the sixth generation (6th generation, 6G) mobile communication system, etc.
  • 3GPP 3rd Generation Partnership Project
  • the core network (CN) domain uses a unified interface (ie, Nchf interface) to communicate with the converged charging system (CCS).
  • the CCS communicates with the billing domain (BD) via the Bx interface.
  • the charging trigger function is located in the CN domain network element or the service server of the service domain, and is used to execute service logic or service control (such as controlling the release of services according to the quota granted by the charging system).
  • CTF provides the session management function (SMF) of data services for the 5G core network, or the IMS application server (AS) of (IP multimedia subsystem, IMS) voice services.
  • SMF session management function
  • AS IMS application server
  • IMS IP multimedia subsystem
  • the present application does not limit the one-to-one correspondence between the CN domain and the CCS.
  • CCS is connected to CTF in CN domain or service domain, and is used to receive billing request from CTF, perform billing processing, and send billing processing result to CTF so that CTF can adjust the billing operation for user service.
  • the billing request carries quota application information and usage information of CTF, and also carries relevant information based on the billing request and the user service, such as user type, customer information, account balance, service white/blacklist, account balance change trend, remaining validity period of package, etc.
  • CCS is a converged charging system that integrates online and offline. It can provide only online charging function (essentially an online charging system) or only offline charging function (essentially an offline charging system) or provide both online and offline charging functions (essentially a converged charging system).
  • CCS includes multiple functions, such as charging function (CHF), account balance management function (ABMF), rating function (RF), charging gateway function (CGF), etc.
  • CHF charging function
  • ABMF account balance management function
  • RF rating function
  • CGF charging gateway function
  • CHF includes online charging function (OCF) and charging data function (CDF).
  • OCF online charging function
  • CDF charging data function
  • OCF is used to provide quota management function
  • CDF provides call record generation function for charging events received from CTF or CEF (charging enablement function) through Nchf.
  • ABMF used to manage user account balances, including account reservation, locking, deduction, etc.
  • RF determines the usage of network resources on behalf of OCF. OCF provides RF with necessary information obtained from charging events and receives the pricing results through the Re reference point.
  • CGF is used to perform the following functions: receiving charging data records (CDR) from CDF in near real time; CDR preprocessing; CDR verification, merging and formatting; CDR error handling; persistent storage of call records; call record routing and filtering, that is, storing call records in separate files according to filtering conditions such as call record type, call record parameters, source CDF, etc.; CDR file management, such as file creation, file open/close triggers, and file deletion; and transferring CDR files to BD.
  • CDR charging data records
  • Each CCS has a matching BD, which can perform billing processing for the UE based on the CDR file received from the CGF.
  • the system architecture 200 applicable to the embodiment of the present application is illustrated below with reference to FIG2.
  • the system architecture 200 includes a management charging function (management CHF, M-CHF), a serving converged charging system (serving CCS, S-CCS), a candidate converged charging system (candidate CCS, C-CCS) and a CTF.
  • management CHF management CHF
  • M-CHF serving converged charging system
  • serving CCS serving CCS
  • S-CCS serving converged charging system
  • candidate converged charging system candidate converged charging system
  • CTF candidate converged charging system
  • the dotted boxes represent external systems, wherein the external systems include a customer relationship management (CRM) system, a recharge server, a billing capability open platform, an accounting system, etc.
  • CRM customer relationship management
  • the billing architecture included in each dotted circle in FIG2 can be understood as a specific example of the above-mentioned billing architecture 100. It should be noted that the present application does not limit the one-to-one correspondence between the CTF and the CCS included in each dotted circle, that is, the present application does not limit the one-to-one correspondence between the CTF and the S-CCS in the left dotted circle, and the present application does not limit the one-to-one correspondence between the CTF and the C-CCS in the right dotted circle.
  • M-CHF can interact with an external system or with one or more CCSs.
  • the one or more CCSs include an S-CCS and one or more C-CCSs.
  • Figure 2 takes the interaction between M-CHF and an S-CCS and a C-CCS as an example, but this application does not limit the number of S-CCSs and C-CCSs.
  • each CCS corresponds to an area. When the UE moves into the area corresponding to a CCS, the CCS is the nearest CCS of the UE.
  • S-CCS For a user equipment (UE), the CCS that currently provides billing functions for the UE.
  • S-CCS includes:
  • S-CHF Serving CHF
  • AMBF It is the account balance management function, which saves the user's account information and performs account balance management.
  • the batch pricing function implements batch pricing for the service quota or usage according to the service information, rate group, etc.
  • CGF Write the information before or after pricing into the call record file.
  • PCF policy control function
  • a candidate CCS for providing a charging function for the UE For a certain UE, a candidate CCS for providing a charging function for the UE. It is understandable that the C-CCS currently does not provide a charging function for the UE, but in some cases it can become the S-CCS of the user, thereby providing a charging function for the UE. For example, the some cases may be the case where the C-CCS is currently the nearest CCS of the UE.
  • C-CCS includes a candidate charging function (candidate CHF, C-CHF).
  • C-CHF is connected to CTF and is a candidate CCS for performing charging processing on the UE. It is understandable that C-CHF currently does not perform charging processing on the UE, but in some cases it can become the S-CHF of the user and thus perform charging processing on the UE.
  • the charging processing includes quota management and CDR generation.
  • C-CCS also includes functions such as ABMF, RF, and CGF, but C-CCS does not have the user data of the UE and does not perform billing processing on the service usage of the UE.
  • the C-CCS may currently be the S-CCS of other UEs.
  • S-CCS can change with the location of the UE
  • C-CCS can also change with the location of the UE.
  • S-CCS currently provides billing functions for the UE; when the UE moves across regions, for example, when C-CCS becomes the nearest CCS of the UE, the C-CCS in FIG2 can become the S-CCS of the UE, and the S-CCS in FIG2 can become the C-CCS of the UE.
  • S-CHF may change as the location of the UE changes
  • C-CHF may also change as the location of the UE changes.
  • the description of the interaction between the CHF and the CTF in this application can be understood as the interaction between the CCS to which the CHF belongs and the CTF.
  • the second charging function network element or the second CHF involved in this application is the S-CHF of the UE before the update, and the second CHF belongs to the second CCS.
  • the first charging function network element or the first CHF is the S-CHF of the UE after the update, and the first CHF belongs to the first CCS.
  • billing function network element in this application is mainly explained using CHF as an example.
  • the billing function network element in this application can also be a roaming charging function network element, or other billing function network elements with similar functions, and this application does not limit this.
  • the user data of the terminal device includes one or more of the following: billing resource context data, account data, policy data, and billing gateway function data.
  • the second CCS migrates user data to the first CCS.
  • the user data is data inside the second CCS, and the user data is used to provide billing functions for the UE.
  • the data migration is performed by the second CHF and the first CHF respectively.
  • the data migration involved in this application refers to data migration between CCs, not just data migration between CHFs belonging to different CCSs.
  • the user data may include: billing resource context data (real-time temporary data) inside the second CHF, persistent user data in the AMBF in the second CCS, data in the RF in the second CCS, CGF data in the second CCS, etc.
  • persistent user data may also be referred to as user account data, including user name, type, account balance, package, package balance, contracted services, wholesale price information, etc.
  • data in RF may be, for example, policy data applied to users, such as wholesale price policies, etc.
  • the user data migrated in this application can be data in various forms such as format files, compressed format files, data directly carried in messages, etc. This application does not limit this.
  • CTF is located in the CN domain network element or the service domain service server, and is used to execute service logic or service control (such as controlling the release of services according to the quota granted by the billing system).
  • CTF is the SMF that provides data services for the 5G core network, or the IMS AS that provides IMS voice services.
  • CTF can also be the AMF of the 5G core network, or it can be other functions, which are not limited in this application.
  • the charging trigger function network element After the location of the terminal device changes, it connects with the charging trigger function network element, for example, establishes a protocol data unit (PDU) session, etc.
  • the charging trigger function network element requests the first CHF to charge the terminal device.
  • the M-CHF is used to store the correspondence between the UE and the S-CHF and update the correspondence when the S-CHF changes.
  • the M-CHF is used to receive S-CCS queries for a certain UE.
  • the M-CHF does not store the user data of the UE locally.
  • M-CHF interacts with external systems and provides external systems with the ability to access the user data of the UE. After receiving a request from the external system, M-CHF dynamically determines the S-CHF of the UE based on the stored correspondence between the UE and the S-CHF, sends the request of the external system to access the user data of the UE to the S-CHF of the UE, and returns the response to the external system after receiving the corresponding response from the S-CHF.
  • BD Please refer to the description of BD in the billing architecture 100.
  • the billing processing of the current user must be performed by the user's home CHF.
  • the visited CHF generates a call bill for roaming settlement between operators, and sends the call bill to the home CHF through the visited SMF, and the home CHF performs billing processing for the UE.
  • the billing processing of the current user must be performed by the user's home CHF.
  • the present application proposes a billing method and device, especially for the case where users move across regions, aiming to improve the success rate of billing and user experience.
  • FIG3 shows a schematic diagram of a charging method 300 provided in the present application.
  • a charging triggering function network element sends a first charging request to a first charging function network element, and correspondingly, the first charging function network element receives the first charging request from the charging triggering function network element.
  • the first charging request is used to request charging of the terminal device.
  • the billing trigger function network element may first obtain the address information of the first billing function network element, and then execute S301 according to the address information.
  • the address information may also be referred to as addressing information; the address information may be, for example, the address and identifier of the first billing function network element.
  • the billing trigger function network element obtains the address information of the first billing function network element according to the information of the billing trigger function network element and/or the location information of the terminal device; the billing trigger function network element sends a first billing request to the first billing function network element according to the address information, and the first billing request is used to request billing processing for the terminal device.
  • the billing trigger function network element may also obtain the address information of the first billing function network element from the policy control function network element and the billing configuration file.
  • the following describes how the billing trigger function network element obtains the address information of the first billing function network element according to the information of the billing trigger function network element and/or the location information of the terminal device in combination with specific examples.
  • Example 1-1 The charging trigger function network element obtains the address information of the first charging function network element from other network elements according to the information of the charging trigger function network element and/or the location information of the terminal device.
  • the billing trigger function network element sends an address information request to the management and billing function network element or the network storage function network element, and correspondingly, the management and billing function network element or the network storage function network element receives the address information request from the billing trigger function network element.
  • the address information request is used to request to obtain the address information of the candidate billing function network element used to perform billing processing on the terminal device, and the address information request includes the location information of the terminal device and/or the information of the billing trigger function network element.
  • the management and billing function network element or the network storage function network element sends the address information of the first billing function network element to the billing trigger function network element, and correspondingly, the billing trigger function network element receives the address information of the first billing function network element from the management and billing function network element or the network storage function network element.
  • the following implementation method is given as to how the management and billing function network element or the network storage function network element determines the first billing function network element.
  • the management and charging function network element determines the first charging function network element according to the location information of the terminal device and/or the information of the charging triggering function network element, as well as the information of the candidate charging function network elements.
  • the network storage function network element determines the first charging function network element according to the serving network function network element (serving NF) currently serving the terminal device.
  • the serving NF may be a charging trigger function network element or other network function network element; for another example, in a data connection network, the serving NF may be an AMF, an SMF, a cell where the terminal device is located, etc.
  • the network storage function network element stores address information, and the corresponding relationship between the serving NF and the address information, When the network storage function network element receives the serving NF information from the charging trigger function network element, it can provide the charging trigger function network element with "CHF Info" in Table 1, that is, the address information of the first charging function network element.
  • the billing trigger function network element obtains the address information of the first billing function network element from the local according to the information of the billing trigger function network element and/or the location information of the terminal device. Specifically, the billing trigger function network element determines the address information of the first billing function network element corresponding to the location information of the terminal device and/or the information of the billing trigger function network element in the local configuration information according to the location information of the terminal device and/or the information of the billing trigger function network element.
  • the first charging function network element sends a data acquisition request #1 to other charging function network elements.
  • the other charging function network elements receive the data acquisition request #1 from the first charging function network element.
  • the data acquisition request #1 is used to request user data of the terminal device.
  • the data acquisition request #1 may be a first charging request forwarded by the first charging function network element.
  • method 300 further includes: the first charging function network element determines to obtain user data of the terminal device from other charging function network elements.
  • the first charging function network element may determine to obtain user data of the terminal device from other charging function network elements based on the fact that the user data of the terminal device is not stored in the local configuration.
  • the first user data includes data used to perform billing processing, such as account balance, etc.
  • the first user data may be all user data of the terminal device, or may be part of the user data of the terminal device.
  • the other billing function network element is a second billing function network element
  • the second billing function network element is a network element that provides billing service functions for the terminal device before the first billing function network element provides billing service functions for the terminal device.
  • providing billing services for terminal devices involved in this application can also be referred to as performing billing processing for terminal devices.
  • the other charging function network element is a management and charging function network element, which is used to maintain the correspondence between the terminal device and the charging function network element that currently performs charging processing for the terminal device.
  • the first billing function network element performs billing processing on the terminal device according to the first user data.
  • the billing process includes: granting quotas, batch pricing, account locking, etc.
  • the billing process includes: opening a call bill, recording, etc.
  • the method 300 further includes: the first charging function network element sends a third charging response to the charging trigger function network element, and accordingly, the charging trigger function network element receives the third charging response from the first charging function network element.
  • the third charging response includes the result of the charging process, or indicates that the charging process has been performed.
  • the first user data is all the data in the user data of the terminal device.
  • the present application provides the following implementations.
  • implementation mode 1 after receiving the first charging request, the first charging function network element directly returns a provisional response to the charging trigger function network element, and then the first charging function network element returns a formal response to the charging trigger function network element after completing the charging process.
  • implementation mode 1 can be implemented through the following example.
  • implementation 1 includes step 1 and step 2.
  • implementation 1 includes step 1, step b, step c, and step 2.
  • step a may be included before step 1 in implementation 1.
  • Step 1 before S303, the first billing function network element sends a first billing response to the billing trigger function network element, and accordingly, the billing trigger function network element receives the first billing response from the first billing function network element.
  • the first billing response is used to indicate that the service of the terminal device is released.
  • the first billing response is used to indicate that no billing processing is performed.
  • the first billing function network element grants a quota to the billing trigger function network element in the absence of user data of the terminal device, and directly releases the service of the terminal device, and the first billing response can be sent.
  • the first billing response can be sent when the service should not or cannot be used.
  • step 1 in step a, after S302, the first charging function network element receives a data acquisition response message #1 from another charging function network element, and the data acquisition response message #1 is used to respond to the data acquisition request message #1.
  • the data acquisition response message #1 is used to indicate that the user data of the terminal device will be sent to the first charging function network element. Accordingly, the first charging function network element performs step 1 according to the data acquisition response message #1.
  • Step 2 After S304, the first charging function network element sends a second charging response to the charging trigger function network element, and accordingly, the charging trigger function network element receives the second charging response from the first charging function network element.
  • the second charging response is used to indicate that the charging process has been performed, and/or the second charging response includes the result of the first charging function network element performing the charging process on the terminal device.
  • step 2 after S304, the first charging function network element terminates the session of the terminal device on the charging triggering function network element, or, for the online charging mode, the first charging function network element restarts quota management.
  • implementation method 1 also includes: step b, the first billing function network element sends indication information to the billing trigger function network element, and accordingly, the billing trigger function network element receives the indication information from the first billing function network element.
  • the indication information is used to trigger or indicate a re-request to perform billing on the terminal device.
  • step c before S304, the billing trigger function network element sends a second billing request to the first billing function network element, and accordingly, the first billing function network element receives the second billing request from the billing trigger function network element.
  • the second billing request is used to request to perform billing on the terminal device. Exemplarily, the second billing request is used to trigger S304.
  • the first charging function network element first migrates data used for performing charging processing from other charging function network elements so as to perform charging processing as quickly as possible, and then migrates other user data from other charging function network elements.
  • implementation mode 2 may include step 1' and step 2'.
  • Step 1' the first user data only includes data used to perform billing processing.
  • the first billing function network element sends a third billing response to the billing trigger function network element. Accordingly, the billing trigger function network element receives the third billing response from the first billing function network element.
  • Step 2' after S303, other charging function network elements send third user data to the first charging function network element, and correspondingly, the first charging function network element receives the third user data of the terminal device from other charging function network elements.
  • the third user data is data other than the first user data in the user data of the terminal device.
  • first charging function network element and other charging function network elements can complete the migration of user data of the terminal device once or multiple times.
  • Example 2-1 The first charging function network element and other charging function network elements can complete the migration of user data of the terminal device at one time, that is, the above-mentioned first user data is all user data of the terminal device.
  • Example 2-1 a possible scenario of Example 2-1 may be that before the first charging function network element starts to perform charging processing on the terminal device, the second charging function network element has finished performing charging processing on the terminal device.
  • this scenario may specifically refer to method 500 or 600 below.
  • Example 2-2 The user data of the terminal device can also be migrated between the first billing function network element and other billing function network elements in multiple times, that is, the above-mentioned first user data is part of the user data of the terminal device.
  • method 300 also includes: other billing function network elements send second user data to the first billing function network element, and accordingly, the first billing function network element receives the second user data from other billing function network elements.
  • the second user data is generated by the second billing function network element for the terminal device after the first billing function network element receives the first user data.
  • the first billing function network element can update the first user data according to the second user data.
  • the second user data includes billing data; optionally, the second user data can also include user identification, usage and other data.
  • the data type included in the second user data can be a subset of the data type included in the first user data.
  • a possible scenario of Example 2-2 may be that when the first billing function network element starts to perform billing processing on the terminal device, the second billing function network element has not yet finished performing billing processing on the terminal device.
  • the second user data may be user data generated by the second billing function network element for the terminal device after the first billing function network element starts to perform billing processing on the terminal device.
  • this scenario may specifically refer to method 700 or 800 below.
  • Fig. 4 shows a schematic diagram of a specific example of the charging method 300 provided in the present application. Specific examples are given below for other charging function network elements, namely, the second charging function network element or the management charging function network element.
  • the other charging function network element in the method 300 is a second charging function network element, and the second charging function network element autonomously switches with the first charging function network element and autonomously migrates user data.
  • the first billing function network element sends a data acquisition request #1 to the second billing function network element according to the address information of the second billing function network element, and accordingly, the second billing function network element receives the data acquisition request #1 from the first billing function network element.
  • the method 300 further includes: the first charging function network element may obtain the address information of the second charging function network element in a variety of ways.
  • the address information may also be referred to as addressing information, such as the address and identifier of the second charging function network element.
  • Example 3-1 The first charging function network element obtains the address information of the second charging function network element from the charging triggering function network element.
  • the first charging request in S301 includes the address information of the second charging function network element, and the first charging function network element obtains the address information from the first charging request.
  • the charging trigger function network element may obtain the address information of the second charging function network element in a variety of ways.
  • the billing trigger function network element requests the management and billing function network element for the address information of the service billing function network element that currently performs billing processing on the terminal device.
  • the management and billing function network element stores the first correspondence between the terminal device and the second billing function network element.
  • the management and billing function network element sends the address information of the second billing function network element to the billing trigger function network element, and accordingly, the billing trigger function network element receives the address information from the management and billing function network element.
  • the billing trigger function network element obtains the address information of the second billing function network element from the terminal device.
  • the billing trigger function network element is SMF
  • the billing trigger function network element obtains the address information of the second billing function network element from AMF.
  • the billing trigger function network element can negotiate with the previous billing trigger function network element that provided services to the terminal device (hereinafter referred to as the previous billing trigger function network element for the sake of convenience) to obtain the address information of the second billing function network element.
  • the billing trigger function network element obtains the address information of the second billing function network element during the process of service migration between the billing trigger function network element and the previous billing trigger function network element.
  • the first billing function network element obtains the address information of the second billing function network element from the management and billing function network element.
  • the first billing function network element sends an address information acquisition request to the management and billing function network element, and accordingly, the management and billing function network element receives the address information acquisition request from the first billing function network element.
  • the address information request is used to request the address information of the service billing function network element that currently performs billing processing on the terminal device.
  • the management and billing function network element sends the address information of the second billing function network element to the first billing function network element, and accordingly, the first billing function network element receives the address information of the second billing function network element from the management and billing function network element.
  • method 300 further includes: when the second billing function network element is a service billing function network element that currently performs billing processing on the terminal device, the management billing function network element stores a first correspondence between the terminal device and the second billing function network element. The management billing function network element determines the second billing function network element according to the first correspondence.
  • the first billing function network element obtains the address information of the second billing function network element from the network storage function network element.
  • the first billing function network element sends an address information acquisition request to the network storage function network element, and accordingly, the network storage function network element receives the address information acquisition request from the first billing function network element.
  • the address information request is used to request the address information of the service billing function network element that currently performs billing processing on the terminal device.
  • the network storage function network element sends the address information of the second billing function network element to the first billing function network element, and accordingly, the first billing function network element receives the address information of the second billing function network element from the network storage function network element.
  • the network storage function network element stores address information, as well as the correspondence between the user permanent identifier (SUPI) or the generic public subscription identifier (GPSI) and the address information, and the role of the address information.
  • SUPI user permanent identifier
  • GPSI generic public subscription identifier
  • the network storage function network element receives the SUPI or GPSI from the first billing function network element, it can provide the first billing function network element with the "CHF Info" in Table 2, that is, the address information of the second billing function network element according to Table 2.
  • method 300 further includes: when the second billing function network element is a service billing function network element that currently performs billing processing on the terminal device, the network storage function network element stores the first correspondence between the terminal device and the second billing function network element. The network storage function network element determines the second billing function network element according to the first correspondence.
  • the second billing function network element sends the first user data of the terminal device to the first billing function network element, and accordingly, the first billing function network element receives the first user data of the terminal device from the second billing function network element.
  • the method 300 further includes: the second charging function network element deleting the first user data.
  • method 300 further includes: the management charging function network element updates the service charging function network element according to the notification. For example, step A and step B.
  • Step A The first charging function network element sends a notification to the management and charging function network element, and accordingly, the management and charging function network element receives the notification from the first charging function network element, wherein the notification is used to indicate that the service charging function network element currently performing charging processing for the terminal device is the first charging function network element.
  • Step B When the management and billing function network element has stored the first correspondence, the management and billing function network element may update the first correspondence to the second correspondence between the terminal device and the first billing function network element according to the notification.
  • the management and billing function network element stores the address information of the first billing function network element while storing the first correspondence.
  • the management and billing function network element also updates the address information of the second billing function network element to the address information of the first billing function network element.
  • method 300 further includes: the network storage function network element updates the service charging function network element according to the notification. For example, step A' and step B'.
  • Step A' The first charging function network element sends a notification to the network storage function network element, and accordingly, the network storage function network element receives the notification from the first charging function network element.
  • the notification is used to indicate that the service charging function network element currently performing charging processing for the terminal device is the first charging function network element.
  • Step B' in the case where the network storage function network element has stored the first correspondence, the network storage function network element can update the first correspondence to the second correspondence between the terminal device and the first billing function network element according to the notification.
  • the network storage function network element stores the address information of the first billing function network element while storing the first correspondence.
  • the network storage function network element also updates the address information of the second billing function network element to the address information of the first billing function network element.
  • the other charging function network element in the method 300 is a management and charging function network element, which assists in switching the charging function network element and migrating user data.
  • the first charging function network element sends a data acquisition request to the management and charging function network element, and accordingly, the management and charging function network element receives the data acquisition request from the first charging function network element.
  • the data acquisition request is used to request user data of the terminal device.
  • the first charging function network element pre-configures the address information of the management and charging function network element, and the first charging function network element sends a data acquisition request to the management and charging function network element according to the address information.
  • method 300 may include S306 and S307 .
  • S306 The management and charging function network element sends a data acquisition request to the second charging function network element.
  • the second charging function network element receives the data acquisition request from the management and charging function network element.
  • the data acquisition request is used to request user data of the terminal device.
  • the method 300 further includes: when the second charging function network element is a service charging function network element currently performing charging processing on the terminal device, the management charging function network element stores the first correspondence between the terminal device and the second charging function network element. Thus, the management charging function network element performs S306 according to the first correspondence.
  • the second charging function network element sends the first user data to the management and charging function network element, and correspondingly, the management and charging function network element receives the first user data from the second charging function.
  • the first user data is used to perform billing processing for the terminal device.
  • the method 300 further includes: the second charging function network element deleting the first user data.
  • method 300 also includes: step C, the management and billing function network element updates the first correspondence to a second correspondence between the terminal device and the first billing function network element; and/or, the management and billing function network element updates the billing function network element that currently provides billing services to the terminal device to the first billing function network element; and/or, the management and billing function network element updates the address information of the billing function network element that currently provides billing services to the terminal device to the address information of the first billing function network element.
  • the management and charging function network element sends the first user data to the first charging function network element. Accordingly, the first charging function network element receives the first user data from the terminal device that manages the charging function network element.
  • method 300 may further include: the second charging function network element sends the third user data to the management and charging function network element, and accordingly, the management and charging function network element receives the third user data from the second charging function.
  • the management and charging function network element sends the third user data to the first charging function network element, and accordingly, the first charging function network element receives the third user data from the terminal device of the management and charging function network element.
  • the management and billing function network element can interact with network elements belonging to the converged billing architecture, such as the billing triggering function network element, the first billing function network element, and the second billing function network element, in addition to the method 300, and can also interact with network elements outside the converged billing architecture.
  • network elements belonging to the converged billing architecture such as the billing triggering function network element, the first billing function network element, and the second billing function network element, in addition to the method 300.
  • An example of the interaction between the management and billing function network element and the network elements outside the converged billing architecture is given below in conjunction with FIG.
  • FIG5 shows a schematic diagram of a charging method 400 provided in the present application.
  • a management and billing function network element stores a first correspondence between a terminal device and a second billing function network element, where the second billing function network element is a service billing function network element that currently performs billing processing on the terminal device.
  • network elements are network elements outside the converged billing architecture, such as CRM, recharge server, accounting system, billing capability open platform, etc.
  • the operation request may be used to request information of a service charging function network element, or may be used to request user data of a terminal device.
  • the charging management function network element processes the operation request according to the first corresponding relationship.
  • the management charging function network element sends the address information of the second charging function network element to other function network elements.
  • the operation request is used to request to query or modify the fourth user data of the terminal device.
  • the fourth user data can be part or all of the user data of the terminal device.
  • the management and billing function network element sends the operation request to the second billing function network element according to the first corresponding relationship, and accordingly, the second billing function network element receives the operation request from the management and billing function network element.
  • the second billing function network element sends the processing result of the operation request to the management and billing function network element, and accordingly, the management and billing function network element receives the processing result of the operation request from the second billing function network element.
  • the management and billing function network element sends the processing result to other functional network elements, and accordingly, other functional network elements receive the processing result of the operation request from the management and billing function network element.
  • the other functional network element is CRM
  • the fourth user data includes the user contract data of the terminal device
  • the operation request is used to request to query or configure or update the user contract data.
  • the other functional network element is a recharge server
  • the fourth user data includes data used to recharge the terminal device, such as packages, balances, etc.
  • the operation request is used to request to recharge the terminal device, such as querying packages or modifying balances.
  • the other functional network element is an accounting system
  • the fourth user data is the bill of the terminal device, and the operation request is used to request to query the bill.
  • the other functional network element is a billing capability open platform
  • the fourth user data is wholesale price information
  • the operation request is used to request to query wholesale price information.
  • methods 500 to 1000 are all described by taking the CHF that provides billing services to the UE in the scenario where the user is online as an example, and methods 900 and 1000 are both described by taking the CHF that provides billing services to the UE in the scenario where the user is offline as an example.
  • method 500 and method 600 and method 700 and method 800 the difference between method 500 and method 600 and method 700 and method 800 is that in method 500 and method 600, the UE accesses the CN by switching through session and service continuity (SSC) mode 2, so that the user data of the terminal device can be migrated between the first billing function network element and other billing function network elements at one time; in method 700 and method 800, the UE accesses the CN by switching through SSC mode 3, and the user data of the terminal device can be migrated between the first billing function network element and other billing function network elements in multiple times.
  • SSC session and service continuity
  • the UE switches to access the CN through SSC mode 2, and switches to the CHF that provides billing services for the UE.
  • the terminal device takes UE as an example
  • the billing trigger function network element takes SMF2 as an example
  • the previous billing trigger function network element takes SMF1 as an example
  • the first billing function network element takes CHF1 as an example
  • the second billing function network element takes CHF2 as an example
  • the management billing function network element takes M-CHF as an example for explanation.
  • the difference between method 500 and method 600 is that method 500 corresponds to the solution in method 300 where the other billing function network element is the second billing function network element, and method 600 corresponds to the solution in method 300 where the other billing function network element is the management billing function network element.
  • FIG. 6 shows a schematic diagram of a billing method 500 provided in the present application.
  • the UE transmits uplink (UL) or downlink (DL) data with UPF1 through PDU session #1.
  • SMF1 determines that UPF relocation needs to be performed.
  • SMF1 determines to switch to a CHF that provides billing services for the UE.
  • S501a PDU session_session management context status notification request/response (Nsmf_PDUSession_SMContext StatusNotify Request/Response) is performed between AMF and SMF1.
  • PDU session release process between UE and UPF1 please refer to standard 3GPP TS23.502 for details.
  • SMF1 sends a termination request to CHF2, and correspondingly, CHF2 receives the termination request from SMF1.
  • the termination request may also be referred to as an accounting end request.
  • the billing end request includes the last usage of the UE PDU session, which can be understood as the traffic usage between the last billing request sent by SMF1 and the termination request.
  • the billing end request includes the traffic usage of the terminal device. For example, when the user is online, the traffic usage is the quota usage; when the user is offline, the traffic usage is the statistical usage.
  • SMF1 initiates the process of releasing the billing resources of the UE PDU session between SMF1 and CHF2.
  • CHF2 sends a termination response to SMF1, and correspondingly, SMF1 receives the termination response from CHF2.
  • the termination response request may also be referred to as a billing termination response.
  • PDU session establishment process between UE and UPF2 please refer to standard 3GPP TS23.502 for details.
  • the PDU sessions established by the UE with UPF2 and UPF1 are different.
  • the UE transmits UL/DL data with UPF2 via PDU session #2.
  • SMF2 sends an initial charging request for PDU session #2 to CHF1, and correspondingly, CHF1 receives the initial charging request from SMF2.
  • SMF2 is triggered to send a billing request to CHF1.
  • the method for SMF2 to locate CHF1 may refer to Example 1-1 or Example 1-2 in method 300 .
  • SMF2 sends an initial charging request to CHF1, and correspondingly, CHF1 receives the initial charging request from SMF2.
  • CHF1 determines CHF2.
  • CHF1 determines the method of CHF2 can refer to Example 3-1, Example 3-2, or Example 3-3 in method 300.
  • SMF2 acts as a charging trigger function webpage, and the way in which SMF2 obtains the address information of CHF2 can be as follows: SMF2 receives the addressing information of CHF2 of the UE from UE or SMF1, for example, the addressing information of CHF2 can be carried in the service request. Then SMF2 sends an initial charging request to CHF, and the charging request carries the addressing information of CHF2.
  • CHF1 sends a user data migration request to CHF2, and correspondingly, CHF2 receives the user data migration request from CHF1.
  • the user data migration request is used to request migration of user data of the UE.
  • CHF2 sends user data to CHF1, and correspondingly, CHF1 receives user data from CHF2.
  • CHF2 deletes the user data.
  • CHF1 processes the initial charging request.
  • CHF1 sends an initial charging response to SMF2.
  • CHF1 notifies M-CHF or NRF that the current charging function network element providing charging service for UE is switched to CHF1.
  • This application does not limit the sequence of S510 and S509, and S510 is performed after all user data of UE is migrated between CHF1 and CHF2.
  • the M-CHF or NRF updates the serving CHF of the UE.
  • the "charging function network element currently providing charging services for the UE" is referred to as a service charging function network element or a service CHF.
  • step A and step B For details, please refer to step A and step B, or step A' and step B'.
  • FIG. 7 shows a schematic diagram of a billing method 600 provided in the present application.
  • CHF1 sends a user data migration request #1 to M-CHF, and correspondingly, M-CHF receives the user data migration request #1 from CHF1.
  • the user data migration request #1 is used to request the migration of user data of the UE.
  • M-CHF sends a user data migration request #2 to CHF2, and accordingly, CHF2 receives the user data migration request #2 from M-CHF.
  • CHF2 sends user data to M-CHF, and correspondingly, M-CHF receives user data from CHF2.
  • M-CHF sends user data to CHF1, and correspondingly, CHF1 receives user data from M-CHF.
  • CHF2 deletes the user data.
  • CHF1 processes the initial charging request.
  • S609 The M-CHF updates the serving CHF of the UE.
  • step C For details, please refer to step C.
  • CHF1 sends an initial charging response to SMF2.
  • method 700 and method 800 taking the scenario of a user online as an example, the UE switches to access the CN through SSC mode 3, and switches to the CHF that provides billing services for the UE.
  • the terminal device takes UE as an example
  • the billing trigger function network element takes SMF2 as an example
  • the previous billing trigger function network element takes SMF1 as an example
  • the first billing function network element takes CHF1 as an example
  • the second billing function network element takes CHF2 as an example
  • the management billing function network element takes M-CHF as an example for explanation.
  • the difference between method 700 and method 800 is that method 700 corresponds to the solution in method 300 where the other billing function network element is the second billing function network element, and method 800 corresponds to the solution in method 300 where the other billing function network element is the management billing function network element.
  • FIG8 shows a schematic diagram of a billing method 700 provided in the present application.
  • the UE transmits UL/DL data with UPF1 through PDU session #1.
  • SMF1 determines that UPF/SMF relocation needs to be performed.
  • SMF1 determines to switch to a CHF that provides billing services for the UE.
  • S701a PDU session_session management context status notification request/response (Nsmf_PDUSession_SMContext StatusNotify Request/Response) is performed between AMF and SMF1.
  • N1N2 message transmission is performed between AMF and SMF1, that is, Namf_Communication_N1N2MessageTransfer is performed between AMF and SMF1.
  • AMF sends a PDU session modification command (PDU Session Modification Command) to the UE, and accordingly, the UE receives the PDU session modification command from the AMF.
  • PDU Session Modification Command PDU Session Modification Command
  • UE sends a PDU session modification command confirmation (PDU Session Modification Command ACK) to AMF, and accordingly, AMF receives the PDU session modification command confirmation from the UE.
  • PDU Session Modification Command ACK PDU Session Modification Command
  • AMF sends an update session management context request (Nsmf_PDUSession_UpdateSM ContextRequest) message to SMF1, and accordingly, SMF1 receives an update session management context request message from AMF.
  • Nsmf_PDUSession_UpdateSM ContextRequest update session management context request
  • SMF1 sends an update session management context response (Nsmf_PDUSession_UpdateSM ContextResponse) message to AMF, and accordingly, AMF receives an update session management context response message from SMF1.
  • Nsmf_PDUSession_UpdateSM ContextResponse update session management context response
  • a PDU session establishment process initiated by the UE is established between the UE and the UPF.
  • the PDU sessions established by the UE with UPF2 and UPF1 are different.
  • the UE transmits UL/DL data with UPF1 through PDU session #2.
  • CHF2 sends user data #1 to CHF1, and correspondingly, CHF1 receives user data #1 from CHF2.
  • user data #1 is part of the user data of the UE, for example, user data #1 includes account data, billing data generated or recorded after billing resources are created, and the like.
  • CHF1 sends an initial charging response to SMF2.
  • PDU session release process between UE and UPF1 please refer to standard 3GPP TS23.502 for details.
  • CHF2 sends user data #2 to CHF1, and correspondingly, CHF1 receives user data #2 from CHF2.
  • user data #2 is part of the user data of the UE.
  • user data #2 is the user data of the UE except user data #1.
  • user data #2 includes billing data generated by CHF2 after S711b is executed.
  • the billing data may include one or more of the following: usage, PDU session information, user location, quality of service (QOS) corresponding to the traffic, etc.
  • QOS quality of service
  • CHF2 deletes the user data.
  • CHF1 may update user data #1 according to user data #2 to obtain updated user data.
  • CHF1 processes the initial charging request.
  • FIG. 9 shows a schematic diagram of a billing method 800 provided in the present application.
  • CHF2 sends user data #1 to M-CHF, and correspondingly, M-CHF receives user data #1 from CHF2.
  • M-CHF sends user data #1 to CHF1, and correspondingly, CHF1 receives user data #1 from M-CHF.
  • user data #1 is part of the user data of the UE, for example, user data #1 includes account data, billing data generated or recorded after billing resources are created, and the like.
  • CHF2 sends user data #2 to M-CHF, and correspondingly, M-CHF receives user data #2 from CHF2.
  • M-CHF sends user data #2 to CHF1, and correspondingly, CHF1 receives user data #2 from M-CHF.
  • user data #2 is part of the user data of the UE.
  • user data #2 is the data in the user data of the UE except user data #1.
  • user data #2 includes the billing data generated by CHF2 after S811b is executed, and the billing data may include one or more of the following: usage, PDU session information, user location, quality of service (QOS) corresponding to the traffic, etc.
  • QOS quality of service
  • CHF2 deletes the user data.
  • CHF1 may update user data #1 according to user data #2 to obtain updated user data.
  • CHF1 processes the initial charging request.
  • the CHF that switches to provide billing services for UE in the scenario where the user is offline is used as an example for explanation.
  • the terminal device takes UE as an example
  • the billing trigger function network element takes AMF2 as an example
  • the previous billing trigger function network element takes AMF1 as an example
  • the first billing function network element takes CHF1 as an example
  • the second billing function network element takes CHF2 as an example
  • the management billing function network element takes M-CHF as an example for explanation.
  • the difference between method 900 and method 1000 is that method 900 corresponds to the solution in which the other billing function network element in method 300 is the second billing function network element, and method 1000 corresponds to the solution in which the other billing function network element in method 300 is the management billing function network element.
  • FIG. 10 shows a schematic diagram of a billing method 900 provided in the present application.
  • UE sends a registration request to RAN, and accordingly, RAN receives the registration request from UE.
  • RAN sends a registration request to AMF1, and accordingly, AMF1 receives the registration request from RAN.
  • AMF1 sends a UE context transfer request to AMF2, and accordingly, AMF2 receives the UE context transfer request from AMF1.
  • AMF1 sends a UE context transfer response to AMF2, and accordingly, AMF2 receives a UE context transfer response from AMF1.
  • FIG. 11 shows a schematic diagram of a billing method 1000 provided in the present application.
  • Figures 12 and 13 are schematic diagrams of the structures of possible communication devices provided in the embodiments of the present application. These communication devices can be used to implement the functions of the first billing function network element or the billing trigger function network element or the management billing function network element in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments.
  • the communication device can be the first billing function network element or the billing trigger function network element or the management billing function network element, and can also be a module (such as a chip) applied to the first billing function network element or the billing trigger function network element or the management billing function network element.
  • the communication device 1100 includes a processing unit 1110 and a transceiver unit 1120.
  • the communication device 1100 is used to implement the functions of the first charging function network element or charging trigger function network element or management charging function network element or subscription data management network element or mobility management network element in the method embodiments shown in Figs. 3 to 11 above.
  • the transceiver unit 1120 is used to receive a first billing request from the billing trigger function network element, and the first billing request is used to request billing for the terminal device; the transceiver unit 1120 is also used to send a data acquisition request to other billing function network elements, and the data acquisition request is used to request user data of the terminal device; the transceiver unit 1120 is also used to receive the first user data of the terminal device from the other billing function network elements; the processing unit 1110 is used to perform billing processing on the terminal device according to the first user data.
  • the processing unit 1110 is used to obtain the address information of the first billing function network element according to the information of the billing trigger function network element and/or the location information of the terminal device, and the first billing function network element is a candidate billing function network element for providing billing services to the terminal device;
  • the transceiver unit 1120 is used to send a first billing request to the first billing function network element according to the address information, and the first billing request is used to request to perform billing processing on the terminal device.
  • the processing unit 1110 is used to store a first correspondence between a terminal device and a second billing function network element, and the second billing function network element is a service billing function network element that currently performs billing processing on the terminal device;
  • the transceiver unit 1120 is used to receive operation requests from other function network elements;
  • the management and billing function network element processes the operation request according to the first correspondence.
  • the communication device 1200 includes a processor 1210 and an interface circuit 1220.
  • the processor 1210 and the interface circuit 1220 are coupled to each other.
  • the interface circuit 1220 may be a transceiver or an input/output interface.
  • the communication device 1200 may further include a memory 1230 for storing instructions executed by the processor 1210 or storing input data required by the processor 1210 to execute instructions or storing data generated after the processor 1210 executes instructions.
  • the processor 1210 is used to implement the function of the processing unit 1110
  • the interface circuit 1220 is used to implement the function of the transceiver unit 1120 .
  • the first billing function network element chip implements the function of the first billing function network element in the above-mentioned method embodiment.
  • the first billing function network element chip receives information from other modules (such as a radio frequency module or an antenna) in the first billing function network element, and the information is sent to the first billing function network element by the billing trigger function network element or the management billing function network element; or, the first billing function network element chip sends information to other modules (such as a radio frequency module or an antenna) in the first billing function network element, and the information is sent by the first billing function network element to the billing trigger function network element or the management billing function network element.
  • modules such as a radio frequency module or an antenna
  • the terminal chip implements the function of the billing trigger function network element in the above-mentioned method embodiment.
  • the chip of the billing trigger function network element receives information from other modules (such as a radio frequency module or an antenna) in the billing trigger function network element, and the information is sent to the billing trigger function network element by the first billing function network element or the management billing function network element; or, the chip of the billing trigger function network element sends information to other modules (such as a radio frequency module or an antenna) in the base station, and the information is sent to the first billing function network element by the billing trigger function network element or the management billing function network element.
  • modules such as a radio frequency module or an antenna
  • the terminal chip implements the function of the management and billing function network element in the above-mentioned method embodiment.
  • the chip of the management and billing function network element receives information from other modules (such as a radio frequency module or an antenna) in the management and billing function network element, and the information is sent to the management and billing function network element by the first billing function network element or the billing trigger function network element; or, the chip of the management and billing function network element sends information to other modules (such as a radio frequency module or an antenna) in the base station, and the information is sent to the first billing function network element by the management and billing function network element or the billing trigger function network element.
  • modules such as a radio frequency module or an antenna
  • the processor in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the method steps in the embodiments of the present application can be implemented in hardware or in software instructions that can be executed by a processor.
  • the software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor so that the processor The processor can read information from the storage medium and write information to the storage medium.
  • the storage medium can also be a component of the processor.
  • the processor and the storage medium can be located in an ASIC.
  • the ASIC can be located in a base station or a terminal.
  • the processor and the storage medium can also exist in a base station or a terminal as discrete components.
  • the computer program product includes one or more computer programs or instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device or other programmable device.
  • the computer program or instruction may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instruction may be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired or wireless means.
  • the computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server, data center, etc. that integrates one or more available media.
  • the available medium may be a magnetic medium, for example, a floppy disk, a hard disk, a tape; it may also be an optical medium, for example, a digital video disc; it may also be a semiconductor medium, for example, a solid-state hard disk.
  • the computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.
  • “at least one” means one or more, and “more than one” means two or more.
  • “And/or” describes the association relationship of associated objects, indicating that three relationships may exist.
  • a and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.
  • the character “/” generally indicates that the previous and next associated objects are in an “or” relationship; in the formula of the present application, the character “/” indicates that the previous and next associated objects are in a “division” relationship.
  • “Including at least one of A, B and C” can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B and C.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)
  • Charge And Discharge Circuits For Batteries Or The Like (AREA)

Abstract

本申请提供了一种计费的方法和装置，该方法包括：就近为终端设备服务的网络中包括计费触发功能网元。计费触发功能网元与第一计费功能网元属于同一个融合计费架构。计费触发功能网元向第一计费功能网元请求为终端设备执行计费处理。第一计费功能网元从第二计费功能网元或管理功能网元获取终端设备的用户数据，并根据用户数据执行计费处理。其中，第二计费功能网元是在第一计费功能网元为终端设备执行计费处理之前，为终端设备执行计费处理的网元，管理计费功能网元用于维护终端设备以及当前为终端设备执行计费处理的计费功能网元的对应关系。本申请提供的方法和装置，能够避免计费数据的频繁跨区域传输，节省网络资源，降低运营成本。

Description

计费方法与装置
本申请要求在2022年12月16日提交中国国家知识产权局、申请号为202211627892.9的中国专利申请的优先权，发明名称为“计费方法与装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，更具体地，涉及一种计费方法与装置。
背景技术
目前，在线计费与离线计费融合架构中，包括核心网、计费***以及账务域。其中，计费***能够为与核心网通信的用户提供在线和/或离线计费功能。具体地，由核心网中的计费触发功能网元请求计费***为用户执行计费处理。并且，核心网和计费***一般是分区域部署的，例如每个计费***对应一个区域，再例如一个或多个核心网对应一个区域。
在通过融合计费架构对用户进行计费的场景下，通常由归属地的计费***为终端设备执行计费处理。然而，当用户的位置发生变化时，特别是用户跨区域移动时，要实现归属地的计费***为用户执行计费处理，需要频繁地跨区域传输大量的计费数据，这将占用过多的网络资源，从而消耗大量运营成本。并且，随着经济和社会的发展，需要频繁跨区域传输的场景将越发普遍，对网络造成的压力也会越发增大。
因此，如何对用户进行计费处理，以节省网络资源，成为亟待解决的问题。
发明内容
本申请提供一种计费方法与装置，能够节省网络资源，从而降低运营成本。
第一方面，提供了一种计费方法，该方法可以由第一计费功能网元执行，或者，也可以由第一计费功能网元的组成部件(例如芯片或者电路)执行，本申请对此不作限定。为了便于描述，下面以由第一计费功能网元执行为例进行说明。
该方法可以包括：第一计费功能网元接收来自计费触发功能网元的第一计费请求，该第一计费请求用于请求对终端设备执行计费；该第一计费功能网元向其他计费功能网元发送数据获取请求，该数据获取请求用于请求第一用户数据；该第一计费功能网元接收来自该其他计费功能网元的第一用户数据；该第一计费功能网元根据该第一用户数据对该终端设备执行计费处理。
可以理解的是，当终端设备的位置发生变化后，为终端设备提供服务的网络也可能发生变化，一般由终端设备当前位置就近的网络为终端设备提供服务。由于计费触发功能网元所在的网络为当前为终端设备提供服务的网络，因此计费触发功能网元所在的网络为离终端设备当前位置最近的网络。以在线和离线融合计费架构为例，一套核心网有对应的计费功能网元。如果由计费触发功能网元所在的网络对应的计费功能网元为终端设备执行计费处理，则能实现离终端设备最近的计费功能网元为终端设备执行计费处理。
上述方案，第一计费功能网元接收计费触发功能网第一计费请求后，根据从其他计费功能网元获取的第一用户数据执行计费处理。相比于由终端设备的归属地计费功能网元为终端设备执行计费处理，能够避免计费数据的频繁跨区域传输，节省网络资源，从而降低运营成本。
还可以理解的是，在由用户的归属地计费功能网元执行计费处理的情况下，网络故障或延迟导致的计费失败的可能性很高，从而网络的可靠性很低。
上述方案，能够降低计费失败的可能性，从而提高网络的可靠性，同时也减少的计费网络线路出现故障时对终端设备的业务使用造成不良影响的情况，提升了终端设备的用户体验。
本申请中，终端设备的用户数据包括以下一项或多项：计费资源上下文数据、账户数据、策略数据、计费网关功能的数据。第一用户数据为终端设备的用户数据中的部分或全部数据。
结合第一方面，在第一方面的某些实现方式中，在第一计费功能网元向其他计费功能网元发送数据 获取请求之前，该方法还包括：该第一计费功能网元确定从该其他计费功能网元获取该第一用户数据。
可以理解的是，在由用户的归属地计费功能网元执行计费处理的情况下，计费数据(例如话单)是频繁产生的，或者说计费数据是需要实时更新的。因此需要由终端设备就近的计费功能网元将终端设备产生的计费数据频繁地传输给归属地计费功能网元。
上述方案相比于频繁传输的计费数据，第一计费功能网元只要从其他计费功能网元获取用户数据之后，就能为终端设备执行计费处理，就不需要再和其他计费功能网元传输计费数据，由归属地的计费功能网元执行计费处理，能够避免计费数据的频繁跨区域传输，节省网络资源，从而降低运营成本。
结合第一方面，在第一方面的某些实现方式中，该其他计费功能网元为第二计费功能网元，该第二计费功能网元是在该第一计费功能网元为该终端设备提供计费服务功能之前，为该终端设备提供计费服务功能的网元。
或者，所述第二计费功能网元是在所述第一计费功能网元为所述终端设备执行计费处理之前，为所述终端设备执行计费处理的网元，其中，这里的之前理解为时序上的概念。所述第二计费功能网元是第一计费功能网元的前一个为所述终端设备执行计费处理的网元，其中，这里的前一个为时序上的前一个。或者，第二计费功能网元是终端设备的位置发生变化之前为所述终端设备执行计费处理的网元，第一计费功能网元是终端设备的位置发生变化之后为所述终端设备执行计费处理的网元。
可以理解的是，第一计费功能网元和第二计费功能网元属于不同的融合计费***。
上述方案，能够实现不同的融合计费***之间的交互，提升计费***的灵活性。
结合第一方面，在第一方面的某些实现方式中，该其他计费功能网元为管理计费功能网元，该管理计费功能网元用于维护该终端设备以及当前为该终端设备执行计费处理的计费功能网元的对应关系。
上述方案，由管理计费功能网元协助不同的融合计费***之间传输用户数据，每个融合计费***只需与管理计费功能网元交互即可传输用户数据。相比于不同的融合计费***之间的直接交互，可以多***交互的复杂度。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该第一计费功能网元接收来自该其他计费功能网元的第二用户数据，该第二用户数据是在该第一计费功能网元接收该第一用户数据之后，由该第二计费功能网元为该终端设备的生成的；该第一计费功能网元根据该第二用户数据更新该第一用户数据。
上述方案，在第二计费功能网元上的计费流程结束之前，第一计费功能网元上的计费流程也可以开始，第一计费功能网元就可以获取已经生成的第一用户数据。并且，在第二计费功能网元上的计费流程结束之后，第一计费功能网元可以继续获取第二用户数据。能够提升第一计费功能网元获取终端设备的用户数据的灵活性。
可选地，第一计费功能网元在对终端设备执行计费处理之前根据第二用户数据更新第一用户数据，随后根据更新后的第一用户数据执行计费处理。
结合第一方面，在第一方面的某些实现方式中，在该第一计费功能网元接收来自该其他计费功能网元的该第一用户数据之前，或，在该第一计费功能网元执行所述计费处理之前，该方法还包括：该第一计费功能网元向该计费触发功能网元发送第一计费响应，该第一计费响应用于指示放通该终端设备的业务。
上述方案，能够减少第一计费功能网元从其他计费功能网元获取第一用户数据时间过长和/或第一计费功能网元执行计费处理的时间过长而导致对第一计费请求的处理超时的问题。
结合第一方面，在第一方面的某些实现方式中，在该第一计费功能网元执行该计费处理之后，该方法还包括：该第一计费功能网元向该计费触发功能网元发送第二计费响应，该第二计费响应用于指示已经执行该计费处理，或者，该第二计费响应包括该计费处理的结果。
上述方案，以便于计费触发功能网元根据计费处理的结果为终端设备提供服务。
结合第一方面，在第一方面的某些实现方式中，在该第一计费功能网元接收该第一用户数据之后，该方法还包括：该第一计费功能网元向该计费触发功能网元发送指示信息，该指示信息用于指示重新请求对终端设备执行计费；该第一计费功能网元接收来自该计费触发功能网元的第二计费请求，该第二计费请求用于请求对终端设备执行计费。
上述方案，以便于计费触发功能网元确定第一计费功能网元何时执行计费处理。
结合第一方面，在第一方面的某些实现方式中，该第一用户数据包括用于执行该计费处理的数据， 在该第一计费功能网元执行该计费处理之后，该方法还包括：该第一计费功能网元向该计费触发功能网元发送第三计费响应，该第三计费响应包括该计费处理的结果，或者，用于指示已经执行所述计费处理。
上述方案，以便于计费触发功能网元根据计费处理的结果为终端设备提供服务。
结合第一方面，在第一方面的某些实现方式中，该第一用户数据包括用于执行该计费处理的数据，包括：该第一用户数据仅包括用于执行该计费处理的数据，在该第一计费功能网元接收该第一用户数据之后，该方法还包括：该第一计费功能网元从该其他计费功能网元接收该终端设备的第三用户数据，该第三用户数据为该终端设备的用户数据中除该第一用户数据以外的数据。
上述方案，第一计费功能网元先从其他计费功能网元获取用于执行计费处理的数据，够减少第一计费功能网元从其他计费功能网元获取第一用户数据时间过长而导致执行计费处理时长过长的问题。
结合第一方面，在第一方面的某些实现方式中，该其他计费功能网元为该第二计费功能网元，该第一计费请求包括该第二计费功能网元的地址信息；或者，该方法还包括：该第一计费功能网元向管理计费功能网元或网络存储功能网元发送地址信息获取请求，该地址信息请求用于请求当前对该终端设备执行计费处理的服务计费功能网元的地址信息；该第一计费功能网元从该管理计费功能网元或网络存储功能网元接收该第二计费功能网元的地址信息。
上述方案，第一计费请求通过获取第二计费功能网元的地址信息，以便于从第二计费功能网元获取终端设备的用户数据。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该第一计费功能网元向管理计费功能网元或网络存储功能网元发送通知，该通知用于指示当前为该终端设备执行计费处理的服务计费功能网元为该第一计费功能网元。
上述方案，以便于管理计费功能网元或网络存储功能网元将当前为终端设备提供计费服务的计费功能网元更新为第一计费功能网元。
第二方面，提供了一种计费方法，该方法可以由计费触发功能网元执行，或者，也可以由计费触发功能网元的组成部件(例如芯片或者电路)执行，本申请对此不作限定。为了便于描述，下面以由计费触发功能网元执行为例进行说明。
该方法可以包括：计费触发功能网元根据该计费触发功能网元的信息和/或终端设备的位置信息获取第一计费功能网元的地址信息，所述第一计费功能网元是为对该终端设备提供计费服务的候选计费功能网元；该计费触发功能网元根据该地址信息向该第一计费功能网元发送第一计费请求，该第一计费请求用于请求对该终端设备执行计费处理。
上述方案，计费触发功能网元选择候选计费功能网元，并请求该候选计费功能网元为终端设备执行计费处理。
结合第二方面，在第二方面的某些实现方式中，该计费触发功能网元根据该计费触发功能网元的信息和/或终端设备的位置信息获取该第一计费功能网元的地址信息，包括：该计费触发功能网元向管理计费功能网元或网络存储功能网元发送地址信息请求，该地址信息请求用于请求获取用于对终端设备执行计费处理的候选计费功能网元的地址信息，该地址信息请求包括该终端设备的位置信息和/或该计费触发功能网元的信息；该计费触发功能网元接收来自该管理计费功能网元或该网络存储功能网元的该第一计费功能网元的地址信息。
结合第二方面，在第二方面的某些实现方式中，该计费触发功能网元根据该计费触发功能网元的信息和/或终端设备的位置信息获取该第一计费功能网元的地址信息，包括：该计费触发功能网元根据该终端设备的位置信息和/或该计费触发功能网元的信息，在本地配置信息中确定与该终端设备的位置信息和/或该计费触发功能网元的信息对应的该第一计费功能网元的地址信息。
结合第二方面，在第二方面的某些实现方式中，该第一计费请求包括第二计费功能网元的地址信息，该第二计费功能网元是在该第一计费功能网元为该终端设备提供计费服务功能之前，为该终端设备提供计费服务功能的网元。
上述方案，以便于第一计费功能网元根据该地址信息从第二计费功能网元获取终端设备的用户数据。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该计费触发功能网元接收来自该第一计费功能网元的第一计费响应，该第一计费响应用于指示放通该终端设备的业务。
上述方案，能够减少第一计费功能网元从其他计费功能网元获取第一用户数据时间过长和/或第一计费功能网元执行计费处理的时间过长而导致对第一计费请求的处理超时的问题。
结合第二方面，在第二方面的某些实现方式中，在该计费触发功能网元接收该第一计费响应之后，该方法还包括：该计费触发功能网元接收来自该第一计费功能网元的第二计费响应，该第二计费响应用于指示已经执行该计费处理，或，包括该计费处理的结果。
上述方案，以便于计费触发功能网元根据计费处理的结果为终端设备提供服务。
结合第二方面，在第二方面的某些实现方式中，在该计费触发功能网元接收该第一计费响应之后，该方法还包括：该计费触发功能网元接收来自该第一计费功能网元的指示信息，该指示信息用于指示重新请求对终端设备执行计费；该计费触发功能网元根据该指示信息向该第一计费功能网元发送第二计费请求，该第二计费请求用于请求对终端设备执行计费。
上述方案，以便于计费触发功能网元确定第一计费功能网元何时执行计费处理。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该计费触发功能网元接收来自该第一计费功能网元的第三计费响应，该第三计费响应包含该计费处理的结果。
上述方案，以便于计费触发功能网元根据计费处理的结果为终端设备提供服务。
第三方面，提供了一种计费方法，该方法可以由管理计费功能网元执行，或者，也可以由管理计费功能网元的组成部件(例如芯片或者电路)执行，本申请对此不作限定。为了便于描述，下面以由管理计费功能网元执行为例进行说明。
该方法可以包括：管理计费功能网元存储终端设备与第二计费功能网元的第一对应关系，该第二计费功能网元为当前对该终端设备执行计费处理的服务计费功能网元；该管理计费功能网元接收来自其他功能网元的操作请求；该管理计费功能网元根据该第一对应关系处理该操作请求。
可选地，其他功能网元可以包括融合计费***内的网元，还可以包括核心网内的网元，还可以包括融合计费***和核心网以外的网元。
上述方案，通过存储第一对应关系，以便于协助其他功能网元获取与终端设备相关的数据、与为终端设备提供计费服务相关的数据、与第二计费功能网元相关的数据。
结合第三方面，在第三方面的某些实现方式中，该操作请求用于请求该服务计费功能网元的地址信息，该管理计费功能网元根据该第一对应关系处理该操作请求，包括：响应于该操作请求，该管理计费功能网元向该其他功能网元发送该第二计费功能网元的地址信息。
上述方案，能够协助其他功能网元获取第二计费功能网元的地址信息，以便于其他功能网元确定服务计费功能网元。
结合第三方面，在第三方面的某些实现方式中，该其他功能网元为第一计费功能网元，该第一计费功能网元是在该第二计费功能网元为该终端设备提供计费服务功能之后为该终端设备提供计费服务功能的网元，该操作请求用于请求该终端设备的第一用户数据；该管理计费功能网元根据该第一对应关系处理该操作请求，包括：该管理计费功能网元向该第二计费功能网元发送数据获取请求，该数据获取请求用于请求该终端设备的第一用户数据；该管理计费功能网元接收来自该第二计费功能网元的第一用户数据，该第一用户数据用于为该终端设备执行计费处理；该管理计费功能网元向该第一计费功能网元发送该第一用户数据。
上述方案，由管理计费功能网元协助不同的融合计费***之间传输用户数据，每个融合计费***只需与管理计费功能网元交互即可传输用户数据。相比于不同的融合计费***之间的直接交互，可以多***交互的复杂度。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该管理计费功能网元将该第一对应关系更新为该终端设备与该第一计费功能网元的第二对应关系。
上述方案，管理计费功能网元协助不同的融合计费***之间传输用户数据之后，将用户数据的接收方确定为当前为终端设备提供计费服务的网元，并更新终端设备与当前为终端设备提供计费服务的网元的对应关系，以便于后续协助其他功能网元获取与终端设备相关的数据、与为终端设备提供计费服务相关的数据、与第二计费功能网元相关的数据。
结合第三方面，在第三方面的某些实现方式中，该操作请求用于指示该服务功能网元为第一计费功能网元，该第一计费功能网元是在该第二计费功能网元为该终端设备提供计费服务功能之后为该终端设备提供计费服务功能的网元，该管理计费功能网元根据该第一对应关系处理该操作请求，包括：该管理计费功能网元接收来自该第一计费功能网元的通知，该通知用于指示当前为该终端设备执行计费处理的服务计费功能网元为该第一计费功能网元；该管理计费功能网元根据该通知将该第一对应关系更新为该 终端设备与该第一计费功能网元的第二对应关系。
上述方案，管理计费功能网元协助不同的融合计费***之间传输用户数据之后，根据通知第一计费功能网元确定为当前为终端设备提供计费服务的网元，并更新终端设备与当前为终端设备提供计费服务的网元的对应关系，以便于后续协助其他功能网元获取与终端设备相关的数据、与为终端设备提供计费服务相关的数据、与第二计费功能网元相关的数据。
结合第三方面，在第三方面的某些实现方式中，该操作请求用于请求查询或修改该终端设备的第四用户数据，该管理计费功能网元根据该第一对应关系处理该操作请求，包括：该管理计费功能网元根据该第一对应关系向该第二计费功能网元转发该操作请求；该管理计费功能网元接收来自第二计费功能网元的该操作请求的处理结果；该管理计费功能网元向该其他功能网元发送该处理结果。
示例性地，其他功能网元不属于为终端设备提供服务的网络，且不属于当前为终端设备提供计费服务的计费***，且不属于为终端设备提供计费服务的候选计费***。换句话说，其他功能网元为本申请提供的融合计费架构之外的网元，例如可以是CRM、充值服务器、账务***、计费能力开放平台等。
上述方案，管理计费功能网元与融合计费架构之外的网元交互，使得融合计费架构之外的网元能够获取终端设备的用户数据。并且，融合计费架构之外的网元可以不需要感知为终端设备提供计费服务的计费功能网元是否变化，节省了融合计费架构之外的网元处理的复杂程度。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该管理计费功能网元接收来自计费触发功能网元的地址信息请求，该地址信息请求用于请求对该终端设备执行计费处理的候选计费功能网元的地址信息，该地址信息请求包括以下一项或多项：该终端设备的位置信息、该计费触发功能网元的信息；响应于该地址信息请求，该管理计费功能网元向该计费触发功能网元发送第一计费功能网元的地址信息。
上述方案，管理计费功能网元向计费触发功能网元提供候选计费功能网元的信息，以便于计费触发功能网元请求该候选计费功能网元为终端设备执行计费处理。
第四方面，提供一种通信装置，该装置包括：至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述第一方面至第三方面中任一种可能实现方式中的方法。
可选地，该装置还包括存储器，用于存储的计算机程序或指令。可选地，该装置还包括通信接口，处理器通过通信接口读取存储器存储的计算机程序或指令。
在一种实现方式中，该装置为通信设备(如第一计费功能网元，又如计费触发功能网元，再如管理计费功能网元)。
在另一种实现方式中，该装置为用于通信设备(如第一计费功能网元，又如计费触发功能网元，再如管理计费功能网元)的芯片、芯片***或电路。
第五方面，本申请提供一种处理器，用于执行上述第一方面至第三方面提供的方法。
对于处理器所涉及的发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则可以理解为处理器输出和接收、输入等操作，也可以理解为由射频电路和天线所进行的发送和接收操作，本申请对此不做限定。
第六方面，提供了一种通信***，包括第一计费功能网元、计费触发功能网元，该第一计费功能网元用于实现上述第一方面任一种可能实现方式中的方法，该计费触发功能网元用于实现上述第二方面任一种可能实现方式中的方法。
可选地，该通信***还包括管理计费功能网元，该管理计费功能网元用于实现上述第三方面任一种可能实现方式中的方法。
第七方面，提供一种计算机可读存储介质，该计算机可读介质存储用于设备执行的程序代码，该程序代码包括用于执行上述第一方面至第三方面任一种可能实现方式中的方法。
第八方面，提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面至第三方面任一种可能实现方式中的方法。
第九方面，提供了一种通信方法，包括：计费触发功能网元根据该计费触发功能网元的信息和/或终端设备的位置信息获取该第一计费功能网元的地址信息；该计费触发功能网元根据该地址信息向该第一计费功能网元发送第一计费请求，该第一计费请求用于请求对该终端设备进行计费处理；第一计费功能网元接收来自计费触发功能网元的第一计费请求，该第一计费请求用于请求对终端设备执行计费；该第一计费功能网元向其他计费功能网元发送数据获取请求，该数据获取请求用于请求该终端设备的第一用 户数据；该第一计费功能网元接收来自该其他计费功能网元的第一用户数据；该第一计费功能网元根据该第一用户数据对该终端设备执行计费处理。
可选地，该其他计费功能网元为第二计费功能网元或管理计费功能网元，该管理计费功能网元用于维护该终端设备以及当前为该终端设备执行计费处理的计费功能网元的对应关系，该第二计费功能网元是在该第一计费功能网元为该终端设备提供计费服务功能之前，为该终端设备提供计费服务功能的网元。
附图说明
图1示出了本申请实施例适用的一种计费架构100。
图2示出了本申请实施例适用的***架构200。
图3示出了本申请提供的计费的方法300的示意图。
图4示出了本申请提供的计费的方法300的具体示例的示意图。
图5示出了本申请提供的计费的方法400的示意图。
图6示出了本申请提供的计费的方法500的示意图。
图7示出了本申请提供的计费的方法600的示意图。
图8示出了本申请提供的计费的方法700的示意图。
图9示出了本申请提供的计费的方法800的示意图。
图10示出了本申请提供的计费的方法900的示意图。
图11示出了本申请提供的计费的方法1000的示意图。
图12是本申请提供的通信装置的一种示意性框图。
图13是本申请提供的通信装置的另一种示意性框图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。方法实施例中的具体操作方法也可以应用于装置实施例或***实施例中。其中，在本申请的描述中，除非另有说明，“多个”的含义是两个或两个以上。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
可以理解的是，在本申请中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”以及其他各种术语标号等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、***、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请提供的技术方案可以应用于各种通信***，例如：第五代(5th generation，5G)通信***(或称为新无线(new radio，NR)***)、***(4th generation，4G)通信***(或称为长期演进(long term evolution，LTE)***)、LTE频分双工(frequency division duplex，FDD)***、LTE时分双工(time division duplex，TDD)***等。本申请提供的技术方案还可以应用于未来的通信***，如第六代(6th generation，6G)移动通信***等。
在4G网络中，在线计费和离线计费采用了不同的架构，用户需要在开户时选定付费类型。而在5G网络中，为了支持5G业务的开展，第三代合作伙伴计划(3rd generation partnership project，3GPP)引进了在线计费和离线计费融合的计费架构。下面结合图1举例说明本申请实施例适用的一种计费架构100。
如图1所示，在计费架构100中，核心网(core network，CN)域(domain)采用统一接口(即Nchf接口)与融合计费***(converged charging system，CCS)通信。CCS通过Bx接口与账务域(billing domain，BD)通信。
一、CN域/业务域
计费触发功能(charging trigger function，CTF)位于CN域网元或者业务域的业务服务器，用于执行业务逻辑或者业务控制(如根据计费***配额授予，控制业务的放通)。例如，CTF为5G核心网提供数据业务的会话管理功能(session management function，SMF)，或者(IP multimedia subsystem，IMS)语音业务的IMS应用服务器(application server，AS)。
需要说明的是，在计费架构100中，本申请并不限定CN域与CCS是一一对应的。
二、CCS
CCS与CN域或业务域的CTF连接，用于接收来自CTF的计费请求，进行计费处理，并向CTF发送计费处理结果，以使该CTF调整对用户业务进行的计费操作。其中，该计费请求携带CTF的配额申请信息、使用量信息等，还携带基于该计费请求、以及该用户业务的相关信息，如用户类型、客户信息、账户余额、业务白/黑名单、账户余额变化趋势、套餐剩余有效期等。
CCS是融合了在线和离线的融合计费***。其可以只提供在线计费功能(实质上是在线计费***)或者只提供离线计费功能(实质上是离线计费***)或者同时提供在线计费功能和离线计费功能(实质上是融合计费***)。
CCS包括多个功能，例如计费功能(charging function，CHF)、账户余额管理功能(account balance management function，ABMF)、批价功能(rating function，RF)、计费网关功能(charging gateway function，CGF)等。
1、CHF：CHF包括在线计费功能(online charging function，OCF)和计费数据功能(charging data function，CDF)。其中，OCF用于提供配额管理功能；CDF为通过Nchf从CTF或CEF(charging enablement function，计费使能功能)接收的计费事件提供话单生成功能。
2、ABMF：用于管理用户的账户余额，包括账户预留、锁定、扣减等。
3、RF：RF代表OCF确定网络资源的使用量。其中，OCF向RF提供从计费事件获得的必要信息，并通过Re参考点接收批价结果。
4、CGF：CGF用于执行如下功能：从CDF准实时接收计费数据记录(charging data record，CDR)；CDR预处理；CDR的验证、合并和格式化；CDR错误处理；话单持久化存储；话单路由和过滤，即根据话单类型、话单参数、源CDF等过滤条件将话单存储在单独的文件中；CDR文件管理，例如文件创建、文件打开/关闭触发器、文件删除；将CDR文件传到BD。
三、BD
每个CCS有配套的BD，BD可以基于从CGF接收到的CDR文件，为UE执行账务(billing)处理。
下面结合图2举例说明本申请实施例适用的***架构200。如图2所示，***架构200包括管理计费功能(management CHF，M-CHF)、服务融合计费***(serving CCS，S-CCS)、候选融合计费***(candidate CCS，C-CCS)和CTF。
如图2所示，虚线方框代表外部***，其中，外部***包括客户关系管理(customer relationship management，CRM)***、充值服务器，计费能力开放平台、账务***等。图2中的每个虚线圆圈包括的计费架构可以理解为上述计费架构100的一种具体示例。需要说明的是，本申请并不限定每个虚线圆圈包括的CTF和CCS是一一对应的，即本申请不限定左侧虚线圆圈内的CTF与S-CCS一一对应，本申请不限定右侧虚线圆圈内的CTF与C-CCS一一对应。
M-CHF可以与外部***交互，也可以与一个或多个CCS交互。例如，针对一个UE而言，该一个或多个CCS包括一个S-CCS和一个或多个C-CCS，图2中以M-CHF与一个S-CCS和一个C-CCS交互为例，但本申请对S-CCS和C-CCS的数量不作限定。一种实现方式中，每个CCS对应一个区域，当该UE移动到某个CCS对应的区域内时，该CCS为该UE的就近的CCS。
一、S-CCS
对于某个用户设备(user equipment，UE)而言，为该UE当前提供计费功能的CCS。S-CCS包括：
1、服务计费功能(serving CHF，S-CHF)：与CTF对接，用于当前对该UE执行计费处理。其中，计费处理包括配额管理和CDR生成。
2、AMBF：为账户余额管理功能，保存该用户的账户信息，执行账户余额的管理。
3、RF：批价功能，其根据业务信息、费率组等，执行业务的配额或使用量的批价等，为该用户的业务使用执行批价；
4、CGF：将批价前或批价后的信息写入话单文件。
另外，CN域的策略控制功能(policy control function，PCF)与该S-CCS对接，基于该UE的账户(counter)进行策略控制(policy control)。
二、C-CCS
对于某个UE而言，用于为该UE提供计费功能的候选的CCS。可以理解的是，C-CCS当前不为该UE提供计费功能，但在一些情况下能够成为该用户的S-CCS，从而为UE提供计费功能。例如，该一些情况可以是C-CCS当前为该UE的就近的CCS的情况。
C-CCS包括候选计费功能(candidate CHF，C-CHF)。C-CHF与CTF对接，用于对该UE执行计费处理的候选CCS。可以理解的是，C-CHF当前不对该UE执行计费处理，但在某些情况下能够成为该用户的S-CHF，从而对该UE执行计费处理。其中，计费处理包括配额管理和CDR生成。
C-CCS还包括ABMF、RF、CGF等功能，但C-CCS没有该UE的用户数据，不对该UE的业务使用执行计费处理。
可以理解的是，该C-CCS当前可以是其他UE的S-CCS。
可以理解的是，针对S-CCS和C-CCS，S-CCS可以随着该UE的位置变化而变化，C-CCS也可以随着该UE的位置变化而变化。例如，如图2所示，***架构200中，当前由S-CCS为该UE提供计费功能；当UE进行跨区域移动后，例如在C-CCS成为该UE的就近的CCS的情况下，图2中的C-CCS可以变为该UE的S-CCS，图2中的S-CCS可以变为该UE的C-CCS。
类似地，还可以理解的是，针对S-CHF和C-CHF，S-CHF可以随着该UE的位置变化而变化，C-CHF也可以随着该UE的位置变化而变化。
需要说明的是，由于CCS中的CHF负责与CTF交互，本申请涉及CHF与CTF交互的描述，均可以理解为该CHF所属的CCS与CTF交互。
本申请中涉及的第二计费功能网元或第二CHF为该UE的更新前的S-CHF，第二CHF属于第二CCS，第一计费功能网元或第一CHF为该UE的更新后的S-CHF，第一CHF属于第一CCS。
还需要说明的是，本申请中的计费功能网元主要以CHF为例进行说明，本申请中的计费功能网元还可以是漫游计费功能(roaming charging function)网元，或者其他具备类似功能的计费功能网元，本申请对此不做限定。
三、用户数据
本申请中，终端设备的用户数据包括以下一项或多项：计费资源上下文数据、账户数据、策略数据、计费网关功能的数据。
在S-CCS由第二CCS更新为第一CCS的情况下，第二CCS迁移用户数据到第一CCS。该用户数据为第二CCS内部的数据，该用户数据用于为该UE提供计费功能。具体地，由第二CHF和第一CHF分别执行数据迁移。需要说明的是，本申请中涉及的数据迁移均指CCS之间的数据迁移，而不仅仅指分别属于不同的CCS的CHF之间的数据迁移。例如，在该场景下，该用户数据可以包括：第二CHF内部的计费资源上下文数据(实时的临时数据)、第二CCS中的AMBF中的持久化用户数据、第二CCS中的RF中的数据、第二CCS中的CGF数据等。其中，持久化用户数据也可以称为用户账户数据，包括用户名称、类型、账户余额、套餐、套餐余量、签约的业务、批价信息等；RF中的数据例如可以是应用于用户的策略数据，例如批价策略等。
本申请中迁移的用户数据可以是格式文件、压缩后的格式文件、直接携带在消息中的数据等多种形式的数据，本申请对此不做限定。
四、CTF
CTF位于CN域网元或者业务域业务服务器，用于执行业务逻辑或者业务控制(如根据计费***配额授予，控制业务的放通)。例如，CTF为5G核心网提供数据业务的SMF，或者IMS语音业务的IMS AS。或者，CTF还可以是5G核心网的AMF，或者，还可以是其他功能，本申请对此不做限定。
本申请中，终端设备的位置发生改变后，与计费触发功能网元连接，例如建立协议数据单元(protocol data unit，PDU)会话等。计费触发功能网元请求第一CHF对终端设备进行计费。
五、M-CHF
M-CHF用于保存该UE与S-CHF的对应关系，并在S-CHF发生变化时更新该对应关系。M-CHF用于接收针对某个UE的S-CCS查询。M-CHF不在本地保存UE的用户数据。
M-CHF与外部***等交互，为外部***提供访问该UE的用户数据的能力。其中，M-CHF在接收到外部***的请求后，根据保存的UE与S-CHF的对应关系，动态确定该UE的S-CHF，将外部***访问该UE的用户数据的请求发送给该UE的S-CHF，并在从S-CHF接收到对应的响应后，将该响应返回外部***。
六、BD：可以参照计费架构100中对BD的描述。
目前，针对不同运营商网络间漫游的计费方案中，以及，针对同一运营商网络的不同区域间的计费方案中，当前用户的计费处理均需由该用户的归属地CHF执行。例如，针对不同运营商网络间漫游的计费方案中，拜访地CHF生成用于运营商之间漫游结算的话单，并通过拜访地SMF将该话单发送给归属地CHF，由归属地CHF针对UE执行计费处理。再例如，针对同一运营商网络的不同区域间的计费方案中，对于同一运营商网络的不同区域，当前用户的计费处理需由该用户的归属地CHF执行。由上可知，用户不论移动到哪里，该用户的在线计费处理需要由归属地CHF执行，离线话单也需要路由回归属地CHF。这种跨站点计费方法对站点组网要求高，当网络被划分为多个区域(如：中国的按照省份部署、欧洲的一网跨多国、沿海国家的运营商网络覆盖多个岛屿)时，需要部署多套核心网和计费***(每个计费***对应一个区域)，该情况下如果仍由归属地CHF执行计费处理，则计费请求需要从拜访地路由回到归属地。由于跨区域网络间采用光缆连接，若光缆发生故障，则导致拜访地核心网无法触发计费请求到归属地计费***或者路由延迟太大，从而造成计费失败等问题，极大影响用户的业务使用。另外，大量用户频繁跨区域移动(如大量用户在一个区域生活且在另一个区域工作)的场景下，大量的计费数据也需要频繁跨区域传输。随着经济和社会的发展，大量用户频繁跨区域移动的场景越发普遍，信令网承受的压力越来越大，不仅使得运营成本越来越高，计费失败的可能性也会更高。
有鉴于此，本申请提出一种计费方法与装置，特别是针对用户跨区域移动的情况，旨在提高计费的成功率以及用户体验。
下面结合图3至图11介绍本申请提供的计费方法100至方法1000。
图3示出了本申请提供的计费的方法300的示意图。
S301，计费触发功能网元向第一计费功能网元发送第一计费请求，相应地，第一计费功能网元接收来自计费触发功能网元的第一计费请求。
其中，第一计费请求用于请求对终端设备执行计费。
可选地，在S301之前，计费触发功能网元可以先获取第一计费功能网元的地址信息，再根据该地址信息执行S301。其中，地址信息也可以称为寻址信息；地址信息例如第一计费功能网元的地址、标识等。例如，计费触发功能网元根据计费触发功能网元的信息和/或终端设备的位置信息获取第一计费功能网元的地址信息；计费触发功能网元根据地址信息向第一计费功能网元发送第一计费请求，第一计费请求用于请求对终端设备进行计费处理。再例如，计费触发功能网元还可以从策略控制功能网元、计费配置文件获取第一计费功能网元的地址信息。下面结合具体示例介绍计费触发功能网元如何根据计费触发功能网元的信息和/或终端设备的位置信息获取第一计费功能网元的地址信息。
示例1-1，计费触发功能网元根据计费触发功能网元的信息和/或终端设备的位置信息从其他网元获取第一计费功能网元的地址信息。
具体地，计费触发功能网元向管理计费功能网元或网络存储功能网元发送地址信息请求，相应地，管理计费功能网元或网络存储功能网元接收来自计费触发功能网元的地址信息请求。其中，地址信息请求用于请求获取用于对终端设备执行计费处理的候选计费功能网元的地址信息，地址信息请求包括终端设备的位置信息和/或计费触发功能网元的信息。管理计费功能网元或网络存储功能网元向计费触发功能网元发送第一计费功能网元的地址信息，相应地，计费触发功能网元接收来自管理计费功能网元或网络存储功能网元的第一计费功能网元的地址信息。其中，关于管理计费功能网元或网络存储功能网元如何确定第一计费功能网元，给出以下实现方式。
一种实现方式中，管理计费功能网元根据终端设备的位置信息和/或计费触发功能网元的信息，以及候选计费功能网元的信息，确定第一计费功能网元。
另一种实现方式中，网络存储功能网元根据当前为终端设备服务的网络功能网元(serving network function，serving NF)确定第一计费功能网元。例如，serving NF可以是计费触发功能网元或其他网络功能网元；再例如，在数据连接网络中，serving NF可以是AMF、SMF、终端设备所在的小区(cell)等。作为一个示例，如表1所示，网络存储功能网元存储地址信息，以及serving NF与地址信息的对应关系， 以及该地址信息的作用。当网络存储功能网元接收来自计费触发功能网元的serving NF的信息，可以根据表1为计费触发功能网元提供表1中的“CHF Info”，即第一计费功能网元的地址信息。
表1
示例1-2，计费触发功能网元根据计费触发功能网元的信息和/或终端设备的位置信息从本地获取第一计费功能网元的地址信息。具体地，计费触发功能网元根据终端设备的位置信息和/或计费触发功能网元的信息，在本地配置信息中确定与终端设备的位置信息和/或计费触发功能网元的信息对应的第一计费功能网元的地址信息。
S302，第一计费功能网元向其他计费功能网元发送数据获取请求#1，相应地，其他计费功能网元接收来自第一计费功能网元的数据获取请求#1。
其中，数据获取请求#1用于请求终端设备的用户数据。示例性地，数据获取请求#1可以是第一计费功能网元转发的第一计费请求。
可选地，在S302之前，方法300还包括：第一计费功能网元确定从其他计费功能网元获取终端设备的用户数据。例如，第一计费功能网元可以根据本地配置中未存储该终端设备的用户数据，确定从其他计费功能网元获取终端设备的用户数据。
S303，其他计费功能网元向第一计费功能网元发送终端设备的第一用户数据，相应地，第一计费功能网元从其他计费功能网元接收终端设备的第一用户数据。
其中，第一用户数据包括用于执行计费处理的数据，例如账户余额等。第一用户数据可以是终端设备的全部用户数据，也可以是终端设备的部分用户数据。
一种可能的实现方式中，其他计费功能网元为第二计费功能网元，第二计费功能网元是在第一计费功能网元为终端设备提供计费服务功能之前，为终端设备提供计费服务功能的网元。
可以理解的是，本申请中涉及的为终端设备提供计费服务也可以称为，为终端设备执行计费处理。
另一种可能的实现方式中，其他计费功能网元为管理计费功能网元，该管理计费功能网元用于维护终端设备以及当前为终端设备执行计费处理的计费功能网元的对应关系。
下文将结合图4分别介绍其他计费功能网元为第二计费功能网元或管理计费功能网元的情况下，方法300的具体示例。
S304，第一计费功能网元根据第一用户数据对终端设备执行计费处理。
示例性地，用户在线场景下，计费处理包括：授予配额、批价、账户锁定等。用户离线场景下，计费处理包括：打开话单，进行记录等。
上述方案，
可选地，在S304之后，方法300还包括：第一计费功能网元向计费触发功能网元发送第三计费响应，相应地，计费触发功能网元接收来自第一计费功能网元的第三计费响应。其中，第三计费响应包含该计费处理的结果，或指示已经执行计费处理。
示例性地，第一用户数据为该终端设备的用户数据中的全部数据。
可以理解的是，第一计费功能网元从其他用户迁移用户数据中的全部数据可能耗时过长，导致第一计费功能网元对第一计费请求的处理时间过长，从而导致从接收到第一计费请求至向计费触发功能网元发送计费响应的时间过长，相应地也会使得计费触发功能网元的处理延迟。为了减少第一计费功能网元对第一计费请求的处理时间过长或计费触发功能网元的处理延迟的情况，本申请给出以下几种实现方式。
实现方式1，第一计费功能网元接收到第一计费请求后直接向计费触发功能网元返回临时响应，随后第一计费功能网元执行完计费处理之后再向计费触发功能网元返回正式响应。具体地，实现方式1可以通过如下示例实现。
例如，实现方式1包括步骤1和步骤2。再例如，实现方式1包括步骤1、步骤b、步骤c和步骤2。可选地，实现方式1中的步骤1之前可以包括步骤a。下面将详细介绍各个步骤。
步骤1，在S303之前，第一计费功能网元向计费触发功能网元发送第一计费响应，相应地，计费触发功能网元接收来自第一计费功能网元的第一计费响应。其中，第一计费响应用于指示放通终端设备的业务。或者，第一计费响应用于指示未执行计费处理。例如在线计费时，第一计费功能网元在没有终端设备的用户数据的情况下给计费触发功能网元授予配额，直接放通终端设备的业务，可以发送第一计费响应。再例如，离线计费时，不应该或不能使用该业务的情况下，可以发送第一计费响应。
可选地，在步骤1之前，步骤a，在S302之后，第一计费功能网元接收来自其他计费功能网元的数据获取响应消息#1，该数据获取响应消息#1用于响应数据获取请求消息#1。例如，数据获取响应消息#1用于指示将向第一计费功能网元发送终端设备的用户数据。相应地，第一计费功能网元根据数据获取响应消息#1执行步骤1。
步骤2，在S304之后，第一计费功能网元向计费触发功能网元发送第二计费响应，相应地，计费触发功能网元接收来自第一计费功能网元的第二计费响应。其中，第二计费响应用于指示已经执行计费处理，和/或，第二计费响应包括第一计费功能网元对终端设备执行计费处理的处理结果。
或者，在步骤2的另一种实现方式中，S304之后，第一计费功能网元中止计费触发功能网元上的终端设备的会话，或者，针对在线计费模式，第一计费功能网元重新开始配额管理。
可选地，在步骤2之前，在S303之后，实现方式1还包括：步骤b，第一计费功能网元向计费触发功能网元发送指示信息，相应地，计费触发功能网元接收来自第一计费功能网元的指示信息。其中，指示信息用于触发或指示重新请求对终端设备执行计费。步骤c，在S304之前，计费触发功能网元向第一计费功能网元发送第二计费请求，相应地，第一计费功能网元接收来自计费触发功能网元的第二计费请求。其中，第二计费请求用于请求对终端设备执行计费。示例性地，第二计费请求用于触发S304。
实现方式2，第一计费功能网元先从其他计费功能网元迁移用于执行计费处理的数据，以便于尽快执行计费处理；再从其他计费功能网元迁移其他用户数据。具体地，实现方式2可以包括步骤1’和步骤2’。
步骤1’，第一用户数据仅包括用于执行计费处理的数据，在S304之后，第一计费功能网元向计费触发功能网元发送第三计费响应，相应地，计费触发功能网元接收来自第一计费功能网元的第三计费响应。
步骤2’，在S303之后，其他计费功能网元向第一计费功能网元发送第三用户数据，相应地，第一计费功能网元从其他计费功能网元接收终端设备的第三用户数据。其中，第三用户数据为终端设备的用户数据中除第一用户数据以外的数据。
还可以理解的是，第一计费功能网元与其他计费功能网元之间可以一次或分多次将终端设备的用户数据迁移结束。
示例2-1，第一计费功能网元与其他计费功能网元之间可以一次将终端设备的用户数据迁移结束，即上述第一用户数据为终端设备的全部用户数据。
例如，示例2-1的一种可能的场景可以是，在第一计费功能网元开始对终端设备执行计费处理之前，第二计费功能网元对终端设备执行计费处理已经结束。示例性地，该场景具体可以参照下文的方法500或600。
示例2-2，第一计费功能网元与其他计费功能网元之间也可以分多次迁移终端设备的用户数据，即上述第一用户数据为终端设备的部分用户数据。可选地，方法300还包括：其他计费功能网元向第一计费功能网元发送第二用户数据，相应地，第一计费功能网元接收来自其他计费功能网元的第二用户数据。其中，第二用户数据是在第一计费功能网元接收第一用户数据之后，由第二计费功能网元为终端设备的生成的。第一计费功能网元可以根据第二用户数据更新第一用户数据。示例性地，第二用户数据包括计费数据；可选地，第二用户数据还可以包括用户标识、用量等数据。换句话说，第二用户数据包括的数据类型可以是第一用户数据包括的数据类型的子集。
例如，示例2-2的一种可能的场景可以是，在第一计费功能网元开始对终端设备执行计费处理时，第二计费功能网元对终端设备执行计费处理还未结束。示例性地，第二用户数据可以是第一计费功能网元开始对终端设备执行计费处理后，第二计费功能网元为终端设备生成的用户数据。示例性地，该场景具体可以参照下文的方法700或800。
图4示出了本申请提供的计费的方法300的具体示例的示意图。下面分别针对其他计费功能网元为第二计费功能网元或管理计费功能网元给出具体示例。
如图4中的(a)所示，方法300中的其他计费功能网元为第二计费功能网元，由第二计费功能网元与第一计费自主进行切换和自主迁移用户数据。
作为S302的一个具体示例，S302’，第一计费功能网元根据第二计费功能网元的地址信息向第二计费功能网元发送数据获取请求#1，相应地，第二计费功能网元接收来自第一计费功能网元的数据获取请求#1。
可选地，在S302之前，方法300还包括：第一计费功能网元可以通过多种方式获取第二计费功能网元的地址信息。其中，地址信息也可以称为寻址信息，例如第二计费功能网元的地址、标识等。
示例3-1，第一计费功能网元从计费触发功能网元获取第二计费功能网元的地址信息。例如，S301中的第一计费请求包括第二计费功能网元的地址信息，第一计费功能网元从第一计费请求中获取该地址信息。
可选地，在示例3-1之前，计费触发功能网元可以通过多种方式获取第二计费功能网元的地址信息。
例如，计费触发功能网元向管理计费功能网元请求当前对终端设备执行计费处理的服务计费功能网元的地址信息。第二计费功能网元为当前对终端设备执行计费处理的服务计费功能网元的情况下，管理计费功能网元存储终端设备与第二计费功能网元的第一对应关系。管理计费功能网元向计费触发功能网元发送所述第二计费功能网元的地址信息，相应地，计费触发功能网元接收来自管理计费功能网元的地址信息。
再例如，计费触发功能网元从终端设备获取第二计费功能网元的地址信息。或者，计费触发功能网元为SMF的情况下，计费触发功能网元从AMF获取第二计费功能网元的地址信息。或者，该计费触发功能网元作为当前为终端设备提供服务的计费触发功能网元，可以与前一个为终端设备提供服务的计费触发功能网元(为了方便说明，以下称为前一个计费触发功能网元)进行协商，获取第二计费功能网元的地址信息。具体例如，计费触发功能网元与前一个计费触发功能网元进行业务迁移的过程中获取第二计费功能网元的地址信息。
示例3-2，第一计费功能网元从管理计费功能网元获取第二计费功能网元的地址信息。第一计费功能网元向管理计费功能网元发送地址信息获取请求，相应地，管理计费功能网元接收来自第一计费功能网元的地址信息获取请求。其中，地址信息请求用于请求当前对终端设备执行计费处理的服务计费功能网元的地址信息。管理计费功能网元向第一计费功能网元发送第二计费功能网元的地址信息，相应地，第一计费功能网元从管理计费功能网元接收第二计费功能网元的地址信息。
可选地，在示例3-2之前，方法300还包括：第二计费功能网元为当前对终端设备执行计费处理的服务计费功能网元的情况下，管理计费功能网元存储终端设备与第二计费功能网元的第一对应关系。管理计费功能网元根据第一对应关系确定第二计费功能网元。
示例3-3，第一计费功能网元从网络存储功能网元获取第二计费功能网元的地址信息。第一计费功能网元向网络存储功能网元发送地址信息获取请求，相应地，网络存储功能网元接收来自第一计费功能网元的地址信息获取请求。其中，地址信息请求用于请求当前对终端设备执行计费处理的服务计费功能网元的地址信息。网络存储功能网元向第一计费功能网元发送第二计费功能网元的地址信息，相应地，第一计费功能网元从网络存储功能网元接收第二计费功能网元的地址信息。作为一个示例，如表2所示，网络存储功能网元存储地址信息，以及用户永久标识(subscription permanent identifier，SUPI)或通用公共用户标识(generic public subscription identifier，GPSI)与地址信息的对应关系，以及该地址信息的作用。当网络存储功能网元接收来自第一计费功能网元的SUPI或GPSI，可以根据表2为第一计费功能网元提供表2中的“CHF Info”，即第二计费功能网元的地址信息。
表2
可选地，在示例3-3之前，方法300还包括：第二计费功能网元为当前对终端设备执行计费处理的服务计费功能网元的情况下，网络存储功能网元存储终端设备与第二计费功能网元的第一对应关系。网络存储功能网元根据第一对应关系确定第二计费功能网元。
作为S303的一个具体示例，S303’，第二计费功能网元向第一计费功能网元发送终端设备的第一用户数据，相应地，第一计费功能网元从第二计费功能网元接收终端设备的第一用户数据。
可选地，在第二计费功能网元向第一计费功能网元发送第一用户数据之后，方法300还包括：第二计费功能网元删除该第一用户数据。
可选地，在执行示例3-2的情况下，在S303之后，方法300还包括：管理计费功能网元根据通知更新服务计费功能网元。例如，步骤A和步骤B。
步骤A，第一计费功能网元向管理计费功能网元发送通知，相应地，管理计费功能网元接收来自第一计费功能网元的通知。其中，该通知用于指示当前为终端设备执行计费处理的服务计费功能网元为第一计费功能网元。
步骤B，在管理计费功能网元已经存储第一对应关系的情况下，管理计费功能网元可以根据该通知将第一对应关系更新为终端设备与第一计费功能网元的第二对应关系。可选地，管理计费功能网元存储第一对应关系的同时也存储了第一计费功能网元的地址信息。在将第一对应关系更新为第二对应关系时，管理计费功能网元也将第二计费功能网元的地址信息更新为第一计费功能网元的地址信息。
可选地，在执行示例3-3的情况下，在S303之后，方法300还包括：网络存储功能网元根据通知更新服务计费功能网元。例如，步骤A’和步骤B’。
步骤A’：第一计费功能网元向网络存储功能网元发送通知，相应地，网络存储功能网元接收来自第一计费功能网元的通知。其中，该通知用于指示当前为终端设备执行计费处理的服务计费功能网元为第一计费功能网元。
步骤B’，在网络存储功能网元已经存储第一对应关系的情况下，网络存储功能网元可以根据该通知将第一对应关系更新为终端设备与第一计费功能网元的第二对应关系。可选地，网络存储功能网元存储第一对应关系的同时也存储了第一计费功能网元的地址信息。在将第一对应关系更新为第二对应关系时，网络存储功能网元也将第二计费功能网元的地址信息更新为第一计费功能网元的地址信息。
如图4中的(b)所示，方法300中的其他计费功能网元为管理计费功能网元，由管理计费功能网元协助进行计费功能网元的切换和用户数据的迁移。
作为S302的一个具体示例，S302”，第一计费功能网元向管理计费功能网元发送数据获取请求，相应地，管理计费功能网元接收来自第一计费功能网元的数据获取请求。其中，数据获取请求用于请求终端设备的用户数据。
例如，第一计费功能网元预配置管理计费功能网元的地址信息，第一计费功能网元根据该地址信息向管理计费功能网元发送数据获取请求。
可选地，在S302之后，方法300可以包括S306和S307。
S306，管理计费功能网元向第二计费功能网元发送数据获取请求，相应地，第二计费功能网元接收来自管理计费功能网元的数据获取请求。
其中，数据获取请求用于请求终端设备的用户数据。
可选地，在S306之前，方法300还包括：第二计费功能网元为当前对终端设备执行计费处理的服务计费功能网元的情况下，管理计费功能网元存储终端设备与第二计费功能网元的第一对应关系。从而，管理计费功能网元根据第一对应关系执行S306。
S307，第二计费功能网元向管理计费功能网元发送第一用户数据，相应地，管理计费功能网元接收来自第二计费功能的第一用户数据。
其中，第一用户数据用于为终端设备执行计费处理。
可选地，在S307之后，方法300还包括：第二计费功能网元删除该第一用户数据。
可选地，在S307之后，方法300还包括：步骤C，管理计费功能网元将第一对应关系更新为终端设备与第一计费功能网元的第二对应关系；和/或，管理计费功能网元将当前为终端设备提供计费服务的计费功能网元更新为第一计费功能网元；和/或，管理计费功能网元将当前为终端设备提供计费服务的计费功能网元的地址信息更新为第一计费功能网元的地址信息。
作为S303的一个具体示例，S303”，管理计费功能网元向第一计费功能网元发送第一用户数据，相 应地，第一计费功能网元接收来自管理计费功能网元的终端设备的第一用户数据。
可选地，在方法300执行上述实现方式2的情况下，方法300还可以包括：第二计费功能网元向管理计费功能网元发送第三用户数据，相应地，管理计费功能网元接收来自第二计费功能的第三用户数据。管理计费功能网元向第一计费功能网元发送第三用户数据，相应地，第一计费功能网元接收来自管理计费功能网元的终端设备的第三用户数据。
可以理解的是，管理计费功能网元除了可以按照上述方法300所述，与计费触发功能网元、第一计费功能网元、第二计费功能网元等属于融合计费架构的网元交互，还能够与融合计费架构之外的网元交互。下面结合图5给出管理计费功能网元与融合计费架构之外的网元交互的示例。
图5示出了本申请提供的计费的方法400的示意图。
S401，管理计费功能网元存储终端设备与第二计费功能网元的第一对应关系，第二计费功能网元为当前对终端设备执行计费处理的服务计费功能网元。
S402，其他功能网元向管理计费功能网元发送操作请求，相应地，管理计费功能网元接收来自其他功能网元的操作请求。
示例性地，其他功能网元为融合计费架构之外的网元，例如可以是CRM、充值服务器、账务***、计费能力开放平台等。
示例性地，该操作请求可以用于请求服务计费功能网元的信息，或者，可以用于请求终端设备的用户数据。
S403，管理计费功能网元根据第一对应关系处理操作请求。
作为S403的具体示例#1，假设操作请求用于请求服务计费功能网元的地址信息。管理计费功能网元向其他功能网元发送第二计费功能网元的地址信息。
作为S403的具体示例#2，假设操作请求用于请求查询或修改所述终端设备的第四用户数据。其中，该第四用户数据可以是终端设备的用户数据中的部分或全部数据。步骤一，管理计费功能网元根据第一对应关系向第二计费功能网元发送所述操作请求，相应地，第二计费功能网元接收来自管理计费功能网元的所述操作请求。步骤二，第二计费功能网元向管理计费功能网元发送所述操作请求的处理结果，相应地，管理计费功能网元接收来自第二计费功能网元的所述操作请求的处理结果。步骤三，管理计费功能网元向其他功能网元发送所述处理结果，相应地，其他功能网元接收来自管理计费功能网元的所述操作请求的处理结果。
结合S403的具体示例#2，针对不同的其他功能网元进一步给出具体示例。例如，其他功能网元为CRM，第四用户数据包括终端设备的用户签约数据，操作请求用于请求查询或配置或更新用户签约数据。再例如，其他功能网元为充值服务器，第四用户数据包括用于为终端设备充值的数据，例如套餐、余额等，操作请求用于请求为终端设备充值，例如查询套餐或修改余额。再例如，其他功能网元为账务***，第四用户数据为终端设备的账单，操作请求用于请求查询账单。再例如，其他功能网元为计费能力开放平台，第四用户数据为批价信息，操作请求用于请求查询批价信息。
下面将针对方法300分别给出不同场景下的具体示例，包括方法500至方法1000。例如，方法500至方法800均以用户在线的场景下，切换为UE提供计费服务的CHF为例进行说明，方法900和方法1000均以用户离线的场景下，切换为UE提供计费服务的CHF为例进行说明。
具体地，方法500和方法600，与方法700和方法800的区别在于：方法500和方法600中UE通过会话和服务连续性(session and service continuity，SSC)模式(mode)2切换接入CN，从而第一计费功能网元与其他计费功能网元之间可以一次将终端设备的用户数据迁移结束；方法700和方法800中UE通过SSC mode 3切换接入CN，第一计费功能网元与其他计费功能网元之间可以分多次迁移终端设备的用户数据。
方法500和方法600中，以用户在线的场景为例，UE通过SSC mode 2切换接入CN，并切换为UE提供计费服务的CHF。具体地，终端设备以UE为例，计费触发功能网元以SMF2为例，前一个计费触发功能网元以SMF1为例，第一计费功能网元以CHF1为例，第二计费功能网元以CHF2为例，管理计费功能网元以M-CHF为例进行说明。方法500和方法600的区别在于：方法500对应方法300中其他计费功能网元为第二计费功能网元的方案，方法600对应方法300中其他计费功能网元为管理计费功能网元的方案。
图6示出了本申请提供的计费的方法500的示意图。
UE通过PDU会话#1与UPF1传输上行(uplink，UL)或下行(downlink，DL)数据。
S501，SMF1确定需要执行UPF重定位。
或者，可以理解为，SMF1确定要切换为UE提供计费服务的CHF。
可选地，S501a，AMF与SMF1之间进行PDU会话_会话管理上下文状态通知请求/响应(Nsmf_PDUSession_SMContext StatusNotify Request/Response)。
S502，UE与UPF1的PDU会话释放流程，具体参见标准3GPP TS23.502。
S503a，SMF1向CHF2发送终止请求(termination request)，相应地，CHF2接收来自SMF1的终止请求。
或者，终止请求也可以称为计费结束请求。
其中，计费结束请求中包括该UE PDU会话的最后用量，该最后用量可以理解为SMF1发送上一个计费请求到该终止请求之间的流量的用量。或者，计费结束请求中包括终端设备的流量的用量，例如，用户在线的场景下，流量的用量为配额的使用量；用户离线的场景下，流量的用量为统计的使用量。
可以理解的是，SMF1发起释放SMF1与CHF2间该UE PDU会话的计费资源的流程。
S503b，CHF2向SMF1发送终止响应(termination response)，相应地，SMF1接收来自CHF2的终止响应。
或者，终止响应求也可以称为计费结束响应。
S504，UE与UPF2的PDU会话建立流程，具体参见标准3GPP TS23.502。
其中，UE分别与UPF2和UPF1建立的PDU会话不同。
UE通过PDU会话#2与UPF2传输UL/DL数据。
作为S301的一个具体示例，S505，SMF2向CHF1发送PDU会话#2的初始计费请求，相应地，CHF1接收来自SMF2的初始计费请求。
示例性地，SMF2在该UE发起与UPF2的PDU session建立流程时，触发SMF2向CHF1发送计费请求。
示例性地，SMF2定位CHF1的方法可以参见方法300中的示例1-1或示例1-2。
S505，SMF2向CHF1发送初始计费请求，相应地，CHF1接收来自SMF2的初始计费请求。
S506，CHF1确定CHF2。
示例性地，CHF1如何确定CHF2方法可以参见方法300中的示例3-1或示例3-2或示例3-3。具体地，针对示例3-1，SMF2作为计费触发功能网页，SMF2获取CHF2的地址信息的方式可以如下所述：SMF2从UE或者SMF1接收该UE的CHF2的寻址信息，例如CHF2的寻址信息可以携带在业务请求中。随后SMF2向CHF发送初始计费请求，该计费请求中携带CHF2的寻址信息。
作为S302的一个具体示例，S507a，CHF1向CHF2发送用户数据迁移请求，相应地，CHF2接收来自CHF1的用户数据迁移请求。
其中，该用户数据迁移请求用于请求迁移UE的用户数据。
作为S303的一个具体示例，S507b，CHF2向CHF1发送用户数据，相应地，CHF1接收来自CHF2的用户数据。
可选地，在S507b之后，CHF2删除用户数据。
作为S304的一个具体示例，S508，CHF1处理初始计费请求。
S509，CHF1向SMF2发送初始计费响应。
S510，CHF1通知M-CHF或者NRF，当前为UE提供计费服务的计费功能网元切换为CHF1。本申请不限制S510与S509的先后顺序，S510在CHF1和CHF2之间迁移完UE的全部用户数据之后进行。
S511、M-CHF或者NRF更新该UE的服务CHF。
为方便说明，本申请中将“当前为UE提供计费服务的计费功能网元”称为服务计费功能网元或服务CHF。
具体可以参见步骤A和步骤B，或，步骤A’和步骤B’。
图7示出了本申请提供的计费的方法600的示意图。
S601至S605可以参见S501至S505的描述。
作为S302的一个具体示例，S606a，CHF1向M-CHF发送用户数据迁移请求#1，相应地，M-CHF接收来自CHF1的用户数据迁移请求#1。
其中，用户数据迁移请求#1用于请求迁移UE的用户数据。
S607a，M-CHF向CHF2发送用户数据迁移请求#2，相应地，CHF2接收来自M-CHF的用户数据迁移请求#2。
S607b，CHF2向M-CHF发送用户数据，相应地，M-CHF接收来自CHF2的用户数据。
作为S303的一个具体示例，S606b，M-CHF向CHF1发送用户数据，相应地，CHF1接收来自M-CHF的用户数据。
可选地，在S607b之后，CHF2删除用户数据。
作为S304的一个具体示例，S608，CHF1处理初始计费请求。
S609、M-CHF更新该UE的服务CHF。
具体可以参见步骤C。
S610，CHF1向SMF2发送初始计费响应。
需要说明的是，本申请不限制S608、S609和S610的先后顺序，S609在M-CHF将UE的全部用户数据迁移给CHF1后即可执行。
方法700和方法800中，以用户在线的场景为例，UE通过SSC mode 3切换接入CN，并切换为UE提供计费服务的CHF。具体地，终端设备以UE为例，计费触发功能网元以SMF2为例，前一个计费触发功能网元以SMF1为例，第一计费功能网元以CHF1为例，第二计费功能网元以CHF2为例，管理计费功能网元以M-CHF为例进行说明。方法700和方法800的区别在于：方法700对应方法300中其他计费功能网元为第二计费功能网元的方案，方法800对应方法300中其他计费功能网元为管理计费功能网元的方案。
图8示出了本申请提供的计费的方法700的示意图。
UE通过PDU会话#1与UPF1传输UL/DL数据。
S701，SMF1确定需要执行UPF/SMF重定位。
或者，可以理解为，SMF1确定要切换为UE提供计费服务的CHF。
可选地，S701a，AMF与SMF1之间进行PDU会话_会话管理上下文状态通知请求/响应(Nsmf_PDUSession_SMContext StatusNotify Request/Response)。
S702，AMF与SMF1之间进行N1N2消息传递，即AMF与SMF1之间进行Namf_Communication_N1N2MessageTransfer。
S703a，AMF向UE发送PDU会话修改命令(PDU Session Modification Command)，相应地，UE接收来自AMF的PDU会话修改命令。
S703b，UE向AMF发送PDU会话修改命令确认(PDU Session Modification Command ACK)，相应地，AMF接收来自UE的PDU会话修改命令确认。
S703c，AMF向SMF1发送更新会话管理上下文请求(Nsmf_PDUSession_UpdateSM ContextRequest)消息，相应地，SMF1接收来自AMF的更新会话管理上下文请求消息。
S703d，SMF1向AMF发送更新会话管理上下文响应(Nsmf_PDUSession_UpdateSM ContextResponse)消息，相应地，AMF接收来自SMF1的更新会话管理上下文响应消息。
S704，UE与UPF之间建立由UE发起的PDU会话建立流程。
其中，UE分别与UPF2和UPF1建立的PDU会话不同。
UE通过PDU会话#2与UPF1传输UL/DL数据。
S705至S707a可以参见S505至S507a的描述。
作为S303的一个具体示例，S707b，CHF2向CHF1发送用户数据#1，相应地，CHF1接收来自CHF2的用户数据#1。
示例性地，用户数据#1为UE的部分用户数据。例如用户数据#1包括账户数据、创建计费资源后生成或记录的计费数据等。
S708，CHF1向SMF2发送初始计费响应。
S709，UE与UPF1的PDU会话释放流程，具体参见标准3GPP TS23.502。
S710a和S710b可以参见S503a和S503b的描述。
S711，CHF2向CHF1发送用户数据#2，相应地，CHF1接收来自CHF2的用户数据#2。
其中，用户数据#2为UE的部分用户数据。示例性地，用户数据#2为UE的用户数据中除用户数据#1 以外的数据。例如用户数据#2包括S711b执行后由CHF2生成的计费数据，该计费数据可以包括以下一项或多项：用量、PDU会话信息、用户的位置、流量对应的服务质量(quality of service，QOS)等。
可选地，在S711b之后，CHF2删除用户数据。
可选地，在S711b之后，CHF1可以根据用户数据#2对用户数据#1进行更新，获得更新后的用户数据。
作为S304的一个具体示例，S712，CHF1处理初始计费请求。
S713和S714可以参见S510和S511的描述。
图9示出了本申请提供的计费的方法800的示意图。
S801至S805可以参见S701至S705的描述。
S806a和S807a可以参见S606a和S607a的描述。
S807b，CHF2向M-CHF发送用户数据#1，相应地，M-CHF接收来自CHF2的用户数据#1。
作为S303的一个具体示例，S806b，M-CHF向CHF1发送用户数据#1，相应地，CHF1接收来自M-CHF的用户数据#1。
示例性地，用户数据#1为UE的部分用户数据。例如用户数据#1包括账户数据、创建计费资源后生成或记录的计费数据等。
S808至S810b可以参见S708至S710b对应的描述。
S811a，CHF2向M-CHF发送用户数据#2，相应地，M-CHF接收来自CHF2的用户数据#2。
S811b，M-CHF向CHF1发送用户数据#2，相应地，CHF1接收来自M-CHF的用户数据#2。
其中，用户数据#2为UE的部分用户数据。示例性地，用户数据#2为UE的用户数据中除用户数据#1以外的数据。例如用户数据#2包括S811b执行后由CHF2生成的计费数据，该计费数据可以包括以下一项或多项：用量、PDU会话信息、用户的位置、流量对应的服务质量(quality of service，QOS)等。
可选地，在S811b之后，CHF2删除用户数据。
可选地，在S811b之后，CHF1可以根据用户数据#2对用户数据#1进行更新，获得更新后的用户数据。
作为S304的一个具体示例，S812，CHF1处理初始计费请求。
S813可以参见S609的描述。
方法900和方法1000中，以用户离线的场景下，切换为UE提供计费服务的CHF为例进行说明。具体地，终端设备以UE为例，计费触发功能网元以AMF2为例，前一个计费触发功能网元以AMF1为例，第一计费功能网元以CHF1为例，第二计费功能网元以CHF2为例，管理计费功能网元以M-CHF为例进行说明。方法900和方法1000的区别在于：方法900对应方法300中其他计费功能网元为第二计费功能网元的方案，方法1000对应方法300中其他计费功能网元为管理计费功能网元的方案。
图10示出了本申请提供的计费的方法900的示意图。
S901，UE向RAN发送注册请求，相应地，RAN接收来自UE的注册请求。
S902，RAN选择AMF。
S903，RAN向AMF1发送注册请求，相应地，AMF1接收来自RAN的注册请求。
S904，AMF1向AMF2发送UE上下文传输请求，相应地，AMF2接收来自AMF1的UE上下文传输请求。
S905，AMF1向AMF2发送UE上下文传输响应，相应地，AMF2接收来自AMF1的UE上下文传输响应。
S906至S912可以参见S505至S511对应的描述。
图11示出了本申请提供的计费的方法1000的示意图。
S1001至S1006可以参见S901至S906的描述。
S1007a至S1010可以参见S606a至S1011的描述。
图12和图13为本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可以用于实现上述方法实施例中第一计费功能网元或计费触发功能网元或管理计费功能网元的功能，因此也能实现上述方法实施例所具备的有益效果。在本申请的实施例中，该通信装置可以是第一计费功能网元或计费触发功能网元或管理计费功能网元，还可以是应用于第一计费功能网元或计费触发功能网元或管理计费功能网元的模块(如芯片)。
如图12所示，通信装置1100包括处理单元1110和收发单元1120。通信装置1100用于实现上述图3-图11中所示的方法实施例中第一计费功能网元或计费触发功能网元或管理计费功能网元或签约数据管理网元或移动管理网元的功能。
当通信装置1100用于实现图3所示的方法实施例中第一计费功能网元的功能时：收发单元1120，用于接收来自计费触发功能网元的第一计费请求，该第一计费请求用于请求对终端设备执行计费；收发单元1120，还用于向其他计费功能网元发送数据获取请求，该数据获取请求用于请求该终端设备的用户数据；收发单元1120，还用于接收来自该其他计费功能网元的该终端设备的第一用户数据；处理单元1110，用于根据该第一用户数据对该终端设备执行计费处理。
当通信装置1100用于实现图3所示的方法实施例中计费触发功能网元的功能时：处理单元1110，用于根据该计费触发功能网元的信息和/或终端设备的位置信息获取第一计费功能网元的地址信息，所述第一计费功能网元是为对该终端设备提供计费服务的候选计费功能网元；收发单元1120，用于根据该地址信息向该第一计费功能网元发送第一计费请求，该第一计费请求用于请求对该终端设备执行计费处理。
当通信装置1100用于实现图4中的(b)所示的方法实施例中的管理计费功能网元的功能时：处理单元1110，用于存储终端设备与第二计费功能网元的第一对应关系，该第二计费功能网元为当前对该终端设备执行计费处理的服务计费功能网元；收发单元1120，用于接收来自其他功能网元的操作请求；该管理计费功能网元根据该第一对应关系处理该操作请求。
有关上述处理单元1110和收发单元1120更详细的描述可以参考图3-图11所示的方法实施例中相关描述。
如图13所示，通信装置1200包括处理器1210和接口电路1220。处理器1210和接口电路1220之间相互耦合。可以理解的是，接口电路1220可以为收发器或输入输出接口。可选的，通信装置1200还可以包括存储器1230，用于存储处理器1210执行的指令或存储处理器1210运行指令所需要的输入数据或存储处理器1210运行指令后产生的数据。
当通信装置1200用于实现图13所示的方法时，处理器1210用于实现上述处理单元1110的功能，接口电路1220用于实现上述收发单元1120的功能。
当上述通信装置为应用于第一计费功能网元的芯片时，该第一计费功能网元芯片实现上述方法实施例中的第一计费功能网元的功能。该第一计费功能网元芯片从第一计费功能网元中的其它模块(如射频模块或天线)接收信息，该信息是由计费触发功能网元或管理计费功能网元发送给第一计费功能网元的；或者，该第一计费功能网元芯片向第一计费功能网元中的其它模块(如射频模块或天线)发送信息，该信息是第一计费功能网元发送给计费触发功能网元或管理计费功能网元的。
当上述通信装置为应用于计费触发功能网元的芯片时，该终端芯片实现上述方法实施例中计费触发功能网元的功能。该计费触发功能网元的芯片从计费触发功能网元中的其它模块(如射频模块或天线)接收信息，该信息是第一计费功能网元或管理计费功能网元发送给计费触发功能网元的；或者，该计费触发功能网元的芯片向基站中的其它模块(如射频模块或天线)发送信息，该信息是计费触发功能网元或管理计费功能网元发送给第一计费功能网元的。
当上述通信装置为应用于管理计费功能网元的芯片时，该终端芯片实现上述方法实施例中管理计费功能网元的功能。该管理计费功能网元的芯片从管理计费功能网元中的其它模块(如射频模块或天线)接收信息，该信息是第一计费功能网元或计费触发功能网元发送给管理计费功能网元的；或者，该管理计费功能网元的芯片向基站中的其它模块(如射频模块或天线)发送信息，该信息是管理计费功能网元或计费触发功能网元发送给第一计费功能网元的。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其它通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法步骤可以在硬件中实现，也可以在可由处理器执行的软件指令中实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器、闪存、只读存储器、可编程只读存储器、可擦除可编程只读存储器、电可擦除可编程只读存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理 器能够从该存储介质读取信息，且可向该存储介质写入信息。存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于基站或终端中。处理器和存储介质也可以作为分立组件存在于基站或终端中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序或指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字视频光盘；还可以是半导体介质，例如，固态硬盘。该计算机可读存储介质可以是易失性或非易失性存储介质，或可包括易失性和非易失性两种类型的存储介质。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A,B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式中，字符“/”，表示前后关联对象是一种“相除”的关系。“包括A，B和C中的至少一个”可以表示：包括A；包括B；包括C；包括A和B；包括A和C；包括B和C；包括A、B和C。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。

Claims (32)

  1. 一种计费方法，其特征在于，包括：
    第一计费功能网元接收来自计费触发功能网元的第一计费请求，所述第一计费请求用于请求对终端设备执行计费；
    所述第一计费功能网元向其他计费功能网元发送数据获取请求，所述数据获取请求用于请求所述终端设备的第一用户数据；
    所述第一计费功能网元接收来自所述其他计费功能网元的所述第一用户数据；
    所述第一计费功能网元根据所述第一用户数据对所述终端设备执行计费处理。
  2. 根据权利要求1所述的方法，其特征在于，在所述第一计费功能网元向其他计费功能网元发送数据获取请求之前，所述方法还包括：
    所述第一计费功能网元确定从所述其他计费功能网元获取所述所述第一用户数据。
  3. 根据权利要求1或2所述的方法，其特征在于，所述其他计费功能网元为第二计费功能网元或管理计费功能网元，所述管理计费功能网元用于维护所述终端设备以及当前为所述终端设备执行计费处理的计费功能网元的对应关系，所述第二计费功能网元是在所述第一计费功能网元为所述终端设备执行计费处理之前，为所述终端设备执行计费处理的网元。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一计费功能网元接收来自所述其他计费功能网元的第二用户数据，所述第二用户数据是在所述第一计费功能网元接收所述第一用户数据之后，由所述第二计费功能网元为所述终端设备的生成的；
    所述第一计费功能网元根据所述第二用户数据更新所述第一用户数据。
  5. 根据权利要求1至3中任一项所述的方法，其特征在于，在所述第一计费功能网元接收来自所述其他计费功能网元的所述第一用户数据之前，所述方法还包括：
    所述第一计费功能网元向所述计费触发功能网元发送第一计费响应，所述第一计费响应用于指示放通所述终端设备的业务。
  6. 根据权利要求5所述的方法，其特征在于，在所述第一计费功能网元执行所述计费处理之后，所述方法还包括：
    所述第一计费功能网元向所述计费触发功能网元发送第二计费响应，所述第二计费响应包括所述计费处理的结果。
  7. 根据权利要求6所述的方法，其特征在于，在所述第一计费功能网元接收所述第一用户数据之后，所述方法还包括：
    所述第一计费功能网元向所述计费触发功能网元发送指示信息，所述指示信息用于指示重新请求对终端设备执行计费；
    所述第一计费功能网元接收来自所述计费触发功能网元的第二计费请求，所述第二计费请求用于请求对终端设备执行计费。
  8. 根据权利要求1至3中任一项所述的方法，其特征在于，所述第一用户数据包括用于执行所述计费处理的数据，在所述第一计费功能网元执行所述计费处理之后，所述方法还包括：
    所述第一计费功能网元向所述计费触发功能网元发送第三计费响应，所述第三计费响应包括该计费处理的结果。
  9. 根据权利要求8所述的方法，其特征在于，所述第一用户数据仅包括用于执行所述计费处理的数据，
    在所述第一计费功能网元接收所述第一用户数据之后，所述方法还包括：
    所述第一计费功能网元从所述其他计费功能网元接收所述终端设备的第三用户数据，所述第三用户数据为所述终端设备的用户数据中除所述第一用户数据以外的数据。
  10. 根据权利要求3至9中任一项所述的方法，其特征在于，所述其他计费功能网元为所述第二计费功能网元，
    所述第一计费请求包括所述第二计费功能网元的地址信息；或者，
    所述方法还包括：
    所述第一计费功能网元向管理计费功能网元或网络存储功能网元发送地址信息获取请求，所述地址信息请求用于请求当前对所述终端设备执行计费处理的服务计费功能网元的地址信息；所述第一计费功能网元从所述管理计费功能网元或网络存储功能网元接收所述第二计费功能网元的地址信息。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    所述第一计费功能网元向管理计费功能网元或网络存储功能网元发送通知，所述通知用于指示当前为所述终端设备执行计费处理的服务计费功能网元为所述第一计费功能网元。
  12. 一种计费方法，其特征在于，包括：
    计费触发功能网元根据所述计费触发功能网元的信息和/或终端设备的位置信息获取第一计费功能网元的地址信息，所述第一计费功能网元是为对该终端设备提供计费服务的候选计费功能网元；
    所述计费触发功能网元根据所述地址信息向所述第一计费功能网元发送第一计费请求，所述第一计费请求用于请求对所述终端设备执行计费处理。
  13. 根据权利要求12所述的方法，其特征在于，所述计费触发功能网元根据所述计费触发功能网元的信息和/或终端设备的位置信息获取所述第一计费功能网元的地址信息，包括：
    所述计费触发功能网元向管理计费功能网元或网络存储功能网元发送地址信息请求，所述地址信息请求用于请求获取用于对终端设备执行计费处理的候选计费功能网元的地址信息，所述地址信息请求包括所述终端设备的位置信息和/或所述计费触发功能网元的信息；
    所述计费触发功能网元接收来自所述管理计费功能网元或所述网络存储功能网元的所述第一计费功能网元的地址信息。
  14. 根据权利要求12所述的方法，其特征在于，所述计费触发功能网元根据所述计费触发功能网元的信息和/或终端设备的位置信息获取所述第一计费功能网元的地址信息，包括：
    所述计费触发功能网元根据所述终端设备的位置信息和/或所述计费触发功能网元的信息，在本地配置信息中确定与所述终端设备的位置信息和/或所述计费触发功能网元的信息对应的所述第一计费功能网元的地址信息。
  15. 根据权利要求12至14中任一项所述的方法，其特征在于，
    所述第一计费请求包括第二计费功能网元的地址信息，所述第二计费功能网元是在所述第一计费功能网元为所述终端设备执行计费处理之前，为所述终端设备执行计费处理的网元。
  16. 根据权利要求12至15中任一项所述的方法，其特征在于，所述方法还包括：
    所述计费触发功能网元接收来自所述第一计费功能网元的第一计费响应，所述第一计费响应用于指示放通所述终端设备的业务。
  17. 根据权利要求16所述的方法，其特征在于，在所述计费触发功能网元接收所述第一计费响应之后，所述方法还包括：
    所述计费触发功能网元接收来自所述第一计费功能网元的第二计费响应，所述第二计费响应包括该计费处理的结果。
  18. 根据权利要求16所述的方法，其特征在于，在所述计费触发功能网元接收所述第一计费响应之后，所述方法还包括：
    所述计费触发功能网元接收来自所述第一计费功能网元的指示信息，所述指示信息用于指示重新请求对终端设备执行计费；
    所述计费触发功能网元根据所述指示信息向所述第一计费功能网元发送第二计费请求，所述第二计费请求用于请求对终端设备执行计费。
  19. 根据权利要求12或13所述的方法，其特征在于，所述方法还包括：
    所述计费触发功能网元接收来自所述第一计费功能网元的第三计费响应，所述第三计费响应包括所述计费处理的结果。
  20. 一种计费方法，其特征在于，包括：
    管理计费功能网元存储终端设备与第二计费功能网元的第一对应关系，所述第二计费功能网元为当前对所述终端设备执行计费处理的服务计费功能网元；
    所述管理计费功能网元接收来自其他功能网元的操作请求；
    所述管理计费功能网元根据所述第一对应关系处理所述操作请求。
  21. 根据权利要求20所述的方法，其特征在于，所述操作请求用于请求所述服务计费功能网元的地 址信息，
    所述管理计费功能网元根据所述第一对应关系处理所述操作请求，包括：
    响应于所述操作请求，所述管理计费功能网元向所述其他功能网元发送所述第二计费功能网元的地址信息。
  22. 根据权利要求20所述的方法，其特征在于，所述其他功能网元为第一计费功能网元，所述第一计费功能网元是在所述第二计费功能网元为所述终端设备执行计费处理之后为所述终端设备执行计费处理的网元，所述操作请求用于请求所述终端设备的第一用户数据；
    所述管理计费功能网元根据所述第一对应关系处理所述操作请求，包括：
    所述管理计费功能网元向所述第二计费功能网元发送数据获取请求，所述数据获取请求用于请求所述终端设备的用户数据；
    所述管理计费功能网元接收来自所述第二计费功能网元的第一用户数据，所述第一用户数据用于为所述终端设备执行计费处理；
    所述管理计费功能网元向所述第一计费功能网元发送所述第一用户数据。
  23. 根据权利要求22所述的方法，其特征在于，所述方法还包括：
    所述管理计费功能网元将所述第一对应关系更新为所述终端设备与所述第一计费功能网元的第二对应关系。
  24. 根据权利要求20或21所述的方法，其特征在于，所述操作请求用于指示所述服务功能网元为第一计费功能网元，所述第一计费功能网元是在所述第二计费功能网元为所述终端设备执行计费处理之后为所述终端设备执行计费处理的网元，
    所述管理计费功能网元根据所述第一对应关系处理所述操作请求，包括：
    所述管理计费功能网元接收来自所述第一计费功能网元的通知，所述通知用于指示当前为所述终端设备执行计费处理的服务计费功能网元为所述第一计费功能网元；
    所述管理计费功能网元根据所述通知将所述第一对应关系更新为所述终端设备与所述第一计费功能网元的第二对应关系。
  25. 根据权利要求20所述的方法，其特征在于，所述操作请求用于请求查询或修改所述终端设备的第四用户数据，
    所述管理计费功能网元根据所述第一对应关系处理所述操作请求，包括：
    所述管理计费功能网元根据所述第一对应关系向所述第二计费功能网元转发所述操作请求；
    所述管理计费功能网元接收来自第二计费功能网元的所述操作请求的处理结果；
    所述管理计费功能网元向所述其他功能网元发送所述处理结果。
  26. 根据权利要求20至25中任一项所述的方法，其特征在于，所述方法还包括：
    所述管理计费功能网元接收来自计费触发功能网元的地址信息请求，所述地址信息请求用于请求对所述终端设备执行计费处理的候选计费功能网元的地址信息，所述地址信息请求包括以下一项或多项：所述终端设备的位置信息、所述计费触发功能网元的信息；
    响应于所述地址信息请求，所述管理计费功能网元向所述计费触发功能网元发送第一计费功能网元的地址信息。
  27. 一种通信装置，其特征在于，所述装置包括一个或多个功能模块，所述一个或多个功能模块：用于执行如权利要求1至11中任一项所述的方法，或者用于执行如权利要求12至19中任一项所述的方法，或者用于执行如权利要求20至26中任一项所述的方法。
  28. 一种通信装置，其特征在于，包括：
    处理器，用于执行存储器中存储的计算机程序，以使得所述装置执行如权利要求1至11中任一项所述的方法，或者以使得所述装置执行如权利要求12至19中任一项所述的方法，或者以使得所述装置执行如权利要求20至26中任一项所述的方法。
  29. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当所述计算机指令在计算机上运行时，使得所述计算机执行如权利要求1至11中任一项所述的方法，或者，执行如权利要求12至19中任一项所述的方法，或者，执行如权利要求20至26中任一项所述的方法。
  30. 一种芯片，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于读取并执行所述存储器中存储的所述计算机程序，当所述计算机程序被执行时，所述处理器执行如权利要求1至11中任一项所述的方法，或者，执行如权利要求12至19中任一项所述的方法，或者，执行如权利要求20至26中任一项所述的方法。
  31. 一种通信方法，其特征在于，包括：
    计费触发功能网元根据所述计费触发功能网元的信息和/或终端设备的位置信息获取所述第一计费功能网元的地址信息；
    所述计费触发功能网元根据所述地址信息向所述第一计费功能网元发送第一计费请求，所述第一计费请求用于请求对所述终端设备进行计费处理；
    第一计费功能网元接收来自计费触发功能网元的第一计费请求，所述第一计费请求用于请求对终端设备执行计费；
    所述第一计费功能网元向其他计费功能网元发送数据获取请求，所述数据获取请求用于请求所述终端设备的第一用户数据；
    所述第一计费功能网元接收来自所述其他计费功能网元的所述第一用户数据；
    所述第一计费功能网元根据所述第一用户数据对所述终端设备执行计费处理。
  32. 根据权利要求31所述的方法，其特征在于，所述其他计费功能网元为第二计费功能网元或管理计费功能网元，所述管理计费功能网元用于维护所述终端设备以及当前为所述终端设备执行计费处理的计费功能网元的对应关系，所述第二计费功能网元是在所述第一计费功能网元为所述终端设备执行计费处理之前，为所述终端设备执行计费处理的网元。
PCT/CN2023/137073 2022-12-16 2023-12-07 计费方法与装置 WO2024125384A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211627892.9A CN118215013A (zh) 2022-12-16 2022-12-16 计费方法与装置
CN202211627892.9 2022-12-16

Publications (1)

Publication Number Publication Date
WO2024125384A1 true WO2024125384A1 (zh) 2024-06-20

Family

ID=91449578

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/137073 WO2024125384A1 (zh) 2022-12-16 2023-12-07 计费方法与装置

Country Status (2)

Country Link
CN (1) CN118215013A (zh)
WO (1) WO2024125384A1 (zh)

Also Published As

Publication number Publication date
CN118215013A (zh) 2024-06-18

Similar Documents

Publication Publication Date Title
JP6988004B2 (ja) 集中型ユニットと分散型ユニットのアーキテクチャにおける通信方法および通信デバイス
US11224084B2 (en) Method for registering terminal in wireless communication system and apparatus therefor
CN108347748B (zh) 服务质量参数的获取方法、装置及***
CN110167082B (zh) 网络的切换方法、装置及***，切换确定方法及装置
EP3557913A1 (en) Network slice selection policy updating method and apparatus
WO2018161803A1 (zh) 一种网络切片的选择方法及装置
WO2019174505A1 (zh) 一种基于网络切片的通信方法及装置
CN110366145B (zh) 通信方法、装置及***
US10945180B2 (en) Mobility management method, apparatus, and system
EP4142218A1 (en) Slice access method, device and system
CN109314909B (zh) 一种锚点网关的切换方法、装置及***
WO2020001402A1 (zh) 一种管理监控事件的方法及装置
WO2021168715A1 (zh) 一种发现应用的方法、装置及***
EP3703420A1 (en) Session context processing method, network elements, and terminal device
WO2022030254A2 (en) Access network node, user equipment, network function node and control method
WO2024037611A1 (zh) 注册信息同步方法、装置、设备及介质
JP2021530149A (ja) リダイレクション方法、通信システム及び通信装置
CN113660703A (zh) 根据应用功能请求朝向局域数据网络的流量路由
US20220210702A1 (en) Communication Method and Apparatus
WO2020244435A1 (zh) 用于发送终端策略的方法、装置和***
EP4221360A1 (en) Data transmission methods in amf entity, smf entity and mme entity for transmitting buffered downklink data of a ue in eps-to-5gs mobility
JP2022524738A (ja) 課金方法および装置
WO2024125384A1 (zh) 计费方法与装置
WO2022253137A1 (zh) 接入业务的方法、装置和***
WO2017215487A1 (zh) SGwU地址的传输方法及装置、MME、SGSN