WO2024125382A1 - 计费方法和装置 - Google Patents

计费方法和装置 Download PDF

Info

Publication number
WO2024125382A1
WO2024125382A1 PCT/CN2023/137058 CN2023137058W WO2024125382A1 WO 2024125382 A1 WO2024125382 A1 WO 2024125382A1 CN 2023137058 W CN2023137058 W CN 2023137058W WO 2024125382 A1 WO2024125382 A1 WO 2024125382A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
function network
charging
billing
dedicated
Prior art date
Application number
PCT/CN2023/137058
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 WO2024125382A1 publication Critical patent/WO2024125382A1/zh

Links

Definitions

  • the present application relates to the field of communication technology, and in particular to a charging method and device.
  • the 3rd generation partnership project (3GPP) introduced a converged billing architecture: the core network uses a unified interface to communicate with the converged billing system, and the billing system selects online billing mode and/or offline billing mode according to user and business needs.
  • the offline billing mode is used for the traffic generated by users using 5G low-latency slices, while the remaining traffic uses the online billing mode.
  • H-CHF home charging function
  • the present application provides a billing method and device, which can save network resources and reduce operating costs.
  • a charging method is provided, which can be executed by a charging function network element or by a component of the charging function network element (such as a chip or circuit, etc.).
  • the charging function network element is used as an example for description.
  • the billing method includes: a billing function network element receives a billing request message from a billing trigger function network element, the billing request message is used to request billing for a terminal device; the billing function network element performs billing processing on the terminal device according to billing data of the terminal device, the billing data is received by the billing function network element from a dedicated billing function network element, and the dedicated billing function network element belongs to a billing system that persistently stores user data of the terminal device.
  • the charging function network element After receiving the charging request message from the charging triggering function network element, the charging function network element performs charging processing on the terminal device according to the charging data obtained from the dedicated charging function network element.
  • the above solution can reduce the cross-region transmission of a large amount of charging information generated during the charging process, thereby saving network resources and reducing operating costs.
  • the network when the network is divided into multiple regions (such as: China's deployment by province, Europe's one network across multiple countries, coastal countries' operator networks covering multiple islands, etc.), it is necessary to deploy multiple core networks and billing systems in multiple regions.
  • the home billing system is used to bill the terminal equipment, when the terminal equipment moves to an area outside the home area, a large amount of billing information (such as call records and other information) generated by the terminal equipment in real time needs to be routed to the terminal equipment's proprietary billing system.
  • the transmission of billing information will increase the pressure on the signaling network and operating costs, and waste a lot of network resources.
  • the above solution uses the nearest billing function network element of the terminal equipment (i.e., the billing function network element that receives the billing request message) to bill the terminal equipment, which can save network resources and reduce the impact on user service usage when the billing network line fails.
  • the method before the billing function network element performs billing processing on the terminal device based on the billing data of the terminal device, the method also includes: the billing function network element sends a billing data request message to the dedicated billing function network element; and the billing function network element receives the billing data from the dedicated billing function network element.
  • the billing function can request the billing data of the terminal device from the dedicated billing function network element so as to perform billing processing on the terminal device. That is to say, the above scheme uses the dedicated billing function network element of the terminal device to maintain the billing data of the terminal device, so that the billing data of the terminal device can be maintained and updated more conveniently. In the case that the service billing function network element of the terminal device is switched, the service billing function network element of the terminal device can directly obtain the billing data for billing from the dedicated billing function network element, and There is no need to migrate all user data, thus saving network resources.
  • the billing function network element sends a billing data request message to the dedicated billing function network element, including: when the billing function network element determines that there is no billing data in the local storage, the billing function network element sends the billing data request message to the dedicated billing function network element.
  • the billing function network element before the billing function network element requests the dedicated billing function network element to obtain billing data, it can first determine whether the billing data of the terminal device is stored in the local storage. If not, it will send a billing data request message to the dedicated billing function network element, thereby saving network resources in some cases.
  • the method also includes: the billing function network element sends a query request message to the network storage function network element, the query request message includes an identifier of the terminal device, and the query request message is used to request a query for the dedicated billing function network element corresponding to the terminal device; the billing function network element receives the address information of the dedicated billing function network element from the network storage function network element; the billing function network element sends a billing data request message to the dedicated billing function network element, including: the billing function network element sends a billing data request message to the dedicated billing function network element according to the address information.
  • the billing function network element can query the network storage function network element for the address information of the dedicated billing function network element, so as to obtain the billing data of the terminal device from the dedicated billing function network element, and thus perform billing processing on the terminal device based on the billing data of the terminal device, thereby avoiding the cross-region transmission of a large amount of billing data generated by the billing process to the visiting billing function network element, thereby saving network resources and reducing operating costs.
  • the method also includes: the billing function network element obtains the address information of the dedicated billing function network element from the billing request message; the billing function network element sends a billing data request message to the dedicated billing function network element, including: the billing function network element sends a billing data request message to the dedicated billing function network element according to the address information.
  • the billing trigger function network element can also carry the address information of the dedicated billing function network element in the billing request message.
  • the billing function network element can directly obtain the address information of the dedicated billing function network element from the billing request message. Therefore, when the billing function network element determines to obtain the user data of the terminal device from the dedicated billing function network element, it can directly send the billing request message to the dedicated billing function network element, thereby reducing the delay.
  • the billing function network element obtains the billing data of the terminal device, including: the billing function network element obtains the billing data of the terminal device in local storage.
  • the billing function network element locally stores the billing data of the terminal device, for example, the billing function network element obtains the billing data of the terminal device from a dedicated billing function network element in advance, the billing function network element can directly obtain the billing data of the terminal device from the local storage without having to obtain it from the dedicated billing function network element, thereby saving network resources.
  • the method after the billing function network element performs billing processing on the terminal device based on the billing data of the terminal device, the method also includes: the billing function network element sends the billing result to the dedicated billing function network element, and the billing result is data obtained after the billing function network element performs billing processing on the terminal device.
  • the billing function network element can send the billing result to the dedicated billing function network element so that the dedicated billing function network element can update the billing data of the terminal device maintained locally, avoiding problems caused by the failure to update the billing data, such as the dedicated billing function network element allocating traffic to the service billing function network element of the terminal device greater than the remaining traffic of the user package due to the failure to update the billing data.
  • a charging method is provided, which can be executed by a dedicated charging function network element or by a component of the dedicated charging function network element (such as a chip or circuit, etc.).
  • a dedicated charging function network element or by a component of the dedicated charging function network element (such as a chip or circuit, etc.).
  • the execution of the dedicated charging function network element is taken as an example for description.
  • the billing method includes: a dedicated billing function network element receives a billing data request message from a billing function network element, the billing data request message is used to request to obtain the billing data of the terminal device, and the dedicated billing function network element belongs to a billing system that persistently stores the user data of the terminal device; in response to the billing data request message, the dedicated billing function network element sends the billing data to the billing function network element, and the billing data is used to perform billing processing on the terminal device.
  • the dedicated billing function network element can send the billing data used for billing processing of the terminal device to the billing function network element, so that the billing function network element can directly perform billing processing on the terminal device. This can reduce the cross-zone transmission of a large amount of billing information generated in the billing process, thereby saving network resources and reducing operating costs.
  • the method further includes: the dedicated billing function network element receives a first billing result from other billing function network elements, the first billing result being data obtained after the other billing function network elements perform billing processing on the terminal device, the other billing function network elements being network elements that provide billing services for the terminal device before the billing function network element; the dedicated billing function network element charges the terminal device according to the first billing result; If the billing data of the terminal device needs to be updated to the billing function network element, the dedicated billing function network element sends the updated billing data to the billing function network element.
  • the dedicated billing function network element can determine whether it is necessary to update the billing data to the billing function network element. For example, the dedicated billing function network element updates the user data of the terminal device according to the first billing result. If the updated user data shows that the user's package balance is less than the traffic allocated to the billing function network element by the dedicated billing function network element through the billing data, the dedicated billing function network element determines that it is necessary to update the billing data of the terminal device to the billing function network element. In this case, the dedicated billing function network element sends the updated billing data to the billing function network element to avoid problems caused by the failure to update the billing data, such as the user's traffic exceeding the traffic in the package due to the failure to update the billing data.
  • the method further includes: the dedicated billing function network element records that the billing function network element is the network element that currently provides billing services for the terminal device.
  • the dedicated billing function network element can record that the billing function network element is the network element that currently provides billing services for the terminal device, or in other words, the dedicated billing function network element saves the information of the current service billing function network element of the terminal device (i.e., the information of the billing function network element). In this way, the dedicated billing function network element can determine who the current service billing function network element of the terminal device is, so that it can subsequently interact with the service billing function network element of the terminal device to provide services for the terminal device.
  • the method also includes: the dedicated billing function network element receives a query request message, a query request for the dedicated billing function network element of the terminal device, the query request message includes an identifier of the terminal device, and the query request message is used to request a query for the network element that currently provides billing services for the terminal device; the dedicated billing function network element returns the address information of the dedicated billing function network element of the terminal device based on the record.
  • other network elements can query the network element currently providing billing services for the terminal device through the dedicated billing function network element, so as to provide corresponding services to the terminal device through the billing function network element.
  • the method also includes: the dedicated billing function network element receives the billing result from the billing function network element, and the billing result is the data obtained after the billing function network element performs billing processing on the terminal device; the dedicated billing function network element updates the billing data according to the billing result.
  • the billing function network element can send the billing result to the dedicated billing function network element so that the dedicated billing function network element can update the billing data of the terminal device maintained locally, avoiding problems caused by the failure to update the billing data, such as the dedicated billing function network element allocating traffic to the service billing function network element of the terminal device greater than the remaining traffic of the user package due to the failure to update the billing data.
  • a charging method is provided, which can be executed by a charging trigger function network element or by a component of the charging trigger function network element (such as a chip or circuit, etc.).
  • a charging trigger function network element or by a component of the charging trigger function network element (such as a chip or circuit, etc.).
  • a dedicated charging function network element is used as an example for description.
  • the billing method includes: the billing trigger function network element obtains the address information of the 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 billing request message to the billing function network element according to the address information, and the billing request message is used to request the billing function network element to bill the terminal device.
  • the billing trigger function network element requests the billing function network element corresponding to the information of the billing trigger function network element and/or the location information of the terminal device to perform billing processing on the terminal device, that is, the billing trigger function network element triggers the billing function network element near the terminal device to perform billing processing on the terminal device, thereby reducing the cross-zone transmission of a large amount of billing data generated in the billing process, thereby saving network resources and reducing operating costs.
  • the billing trigger function network element obtains the address information of the 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 a query request message to the network storage function network element, the query request message 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 query request message 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 billing function network element from the storage function network element.
  • the billing trigger function network element can query the address information of the billing function network element corresponding to the information of the billing trigger function network element and/or the location information of the terminal device through the network storage function network element, so as to trigger the billing function network element to perform billing processing on the terminal device, thereby reducing the cross-region transmission of a large amount of billing data generated in the billing process, thereby saving network resources and reducing operating costs.
  • the billing trigger function network element obtains the address information of the billing function network element according to 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 the location information of the terminal device and/or the location information of the terminal device 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 information of the billing triggering function network element corresponds to the address information of the billing function network element.
  • the address information of the billing function network element can be directly obtained from the local configuration information so as to trigger the billing function network element to perform billing processing on the terminal device, thereby reducing the cross-zone transmission of a large amount of billing data generated in the billing process, thereby saving network resources and reducing operating costs.
  • the charging request message includes address information of a dedicated charging function network element, and the dedicated charging function network element belongs to a charging system that persistently stores user data of the terminal device.
  • the billing trigger function network element can carry the address information of the dedicated billing function network element in the billing request message, so that the billing function network element can directly obtain the address information of the dedicated billing function network element from the billing request message, without having to obtain the address information of the billing function network element through other processes, thereby reducing latency.
  • a billing method which includes: a billing trigger function network element sends a billing request message to a billing function network element, the billing request message is used to request billing processing for a terminal device; the billing function network element receives the billing request message from the billing trigger function network element; the billing function network element performs billing processing on the terminal device according to the billing data of the terminal device, the billing data is received by the billing function network element from a dedicated billing function network element, and the dedicated billing function network element belongs to a billing system that persistently stores user data of the terminal device.
  • the method before the billing function network element performs billing processing on the terminal device based on the billing data of the terminal device, the method also includes: the billing function network element sends a billing data request message to the dedicated billing function network element; in response to the billing data request message, the dedicated billing function network element sends the billing data to the billing function network element; and the billing function network element receives the billing data from the dedicated billing function network element.
  • the billing function network element sends a billing data request message to the dedicated billing function network element, including: when the billing function network element determines that there is no billing data in the local storage, the billing function network element sends the billing data request message to the dedicated billing function network element.
  • the method also includes: the billing function network element obtains the address information of the dedicated billing function network element; the billing function network element sends a billing data request message to the dedicated billing function network element, including: the billing function network element sends a billing data request message to the dedicated billing function network element according to the address information.
  • the billing function network element obtains the address information of the dedicated billing function network element, including: the billing function network element sends a query request message to the network storage function network element, the query request message includes the identifier of the terminal device, and the query request message is used to request a query for the dedicated billing function network element corresponding to the terminal device; the network storage function network element determines the dedicated billing function network element based on the identifier of the terminal device; the network storage function network element sends the address information of the dedicated billing function network element to the billing function network element; the billing function network element receives the address information of the dedicated billing function network element from the network storage function network element.
  • the billing function network element obtains the address information of the dedicated billing function network element, including: the billing function network element obtains the address information of the dedicated billing function network element from the billing request message.
  • the billing function network element obtains the billing data of the terminal device, including: the billing function network element obtains the billing data of the terminal device in local storage.
  • the method after the billing function network element performs billing processing on the terminal device based on the billing data of the terminal device, the method also includes: the billing function network element sends the billing result to the dedicated billing function network element, and the billing result is the data obtained after the billing function network element performs billing processing on the terminal device; the dedicated billing function network element receives the billing result from the billing function network element.
  • the method also includes: the dedicated billing function network element receives a first billing result from other billing function network elements, the first billing result being data obtained after the other billing function network element performs billing processing on the terminal device, and the other billing function network element is a network element that provides billing services to the terminal device before the billing function network element; the dedicated billing function network element determines whether it is necessary to update the billing data of the terminal device to the billing function network element based on the first billing result; if it is necessary to update the billing data of the terminal device to the billing function network element, the dedicated billing function network element sends the updated billing data to the billing function network element; and the billing function network element receives the updated billing data from the dedicated function network element.
  • the method further includes: the dedicated billing function network element records that the billing function network element is the network element that currently provides billing services for the terminal device.
  • a charging device comprising: a transceiver module for receiving a charging trigger function network element; A billing request message, which is used to request billing for a terminal device; a processing module, which is used to perform billing processing on the terminal device based on the billing data of the terminal device, the billing data is received by the billing device from a dedicated billing function network element, and the dedicated billing function network element belongs to a billing system that persistently stores user data of the terminal device.
  • the transceiver module is further used to send a billing data request message to the dedicated billing function network element; and receive the billing data from the dedicated billing function network element.
  • the processing module is specifically used to send the billing data request message to the dedicated billing function network element through the transceiver module when it is determined that the billing data is not stored in the local storage.
  • the processing module is also used to obtain address information of the dedicated billing function network element; the processing module is specifically used to send a billing data request message to the dedicated billing function network element according to the address information.
  • the transceiver module is specifically used to send a query request message to the network storage function network element, the query request message includes an identifier of the terminal device, and the query request message is used to request a query for the dedicated billing function network element corresponding to the terminal device; and, receive the address information of the dedicated billing function network element from the network storage function network element.
  • the transceiver module is specifically used to obtain the address information of the dedicated charging function network element from the charging request message.
  • the processing module is specifically used to obtain the billing data of the terminal device in the local storage.
  • the transceiver module is also used to send a billing result to the dedicated billing function network element, and the billing result is data obtained after the billing function network element performs billing processing on the terminal device.
  • a billing device which includes: a transceiver module for receiving a billing data request message from a billing function network element, the billing data request message is used to request to obtain the billing data of the terminal device, the dedicated billing function network element belongs to a billing system that persistently stores user data of the terminal device; and, sending the billing data to the billing function network element, the billing data is used to perform billing processing on the terminal device.
  • the transceiver module is also used to receive a first billing result from other billing function network elements, the first billing result being data obtained after the other billing function network elements perform billing processing on the terminal device, and the other billing function network elements are network elements that provide billing services to the terminal device before the billing function network element;
  • the billing device also includes a processing module, used to determine whether it is necessary to update the billing data of the terminal device to the billing function network element based on the first billing result; the processing module is also used to send the updated billing data to the billing function network element through the transceiver module when it is necessary to update the billing data of the terminal device to the billing function network element.
  • the processing module is further used to record that the billing function network element is the network element that currently provides billing services for the terminal device.
  • the transceiver module is also used to receive a billing result from the billing function network element, and the billing result is data obtained after the billing function network element performs billing processing on the terminal device.
  • a billing device which includes: a processing module, used to obtain the address information of the billing function network element based on the information of the billing trigger function network element and/or the location information of the terminal device; a transceiver module, used to send a billing request message to the billing function network element according to the address information, and the billing request message is used to request the billing function network element to bill the terminal device.
  • the transceiver module is specifically used to send a query request message to the network storage function network element, the query request message is used to request address information of a candidate billing function network element for performing billing processing on the terminal device, the query request message includes location information of the terminal device and/or information of the billing trigger function network element; and, receiving the address information of the billing function network element from the storage function network element.
  • the processing module is specifically used to determine, in the local configuration information, the address information of the 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 charging request message includes address information of a dedicated charging function network element, and the dedicated charging function network element belongs to a charging system that persistently stores user data of the terminal device.
  • a communication device which may be a charging function network element or a chip for a charging function network element.
  • the device has the function of implementing the method implemented in the first aspect.
  • the function may be implemented by hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • a communication device which may be a dedicated charging function network element or a dedicated charging function network element.
  • the device has the function of implementing the method implemented in the second aspect.
  • the function can be implemented by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • a communication device which may be a charging trigger function network element, or a chip for a charging trigger function network element.
  • the device has the function of implementing the method implemented in the third aspect.
  • the function may be implemented by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • a communication device which includes: a memory for storing programs; a processor for executing the programs stored in the memory, and when the program stored in the memory is executed, the processor is used to execute the method provided in any one of the first to third aspects above.
  • the present application provides a processor for executing the methods provided in the above aspects.
  • the process of sending the above information and obtaining/receiving the above information in the above methods can be understood as the process of the processor outputting the above information and the process of the processor receiving the input above information.
  • the processor When outputting the above information, the processor outputs the above information to the transceiver so that it can be transmitted by the transceiver. After the above information is output by the processor, it may also need to undergo other processing before reaching the transceiver.
  • the transceiver obtains/receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to undergo other processing before being input into the processor.
  • the receiving request message mentioned in the above method can be understood as the processor receiving input information.
  • the processor may be a processor specifically used to execute these methods, or may be a processor that executes computer instructions in a memory to execute these methods, such as a general-purpose processor.
  • the memory may be a non-transitory memory, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or may be separately arranged on different chips.
  • ROM read-only memory
  • a computer-readable storage medium which stores a program code for execution by a device, wherein the program code includes a method for executing the method provided in any one of the first to third aspects above.
  • a computer program product comprising instructions is provided.
  • the computer program product When the computer program product is run on a computer, the computer executes the method provided in any one of the first to third aspects above.
  • a chip which includes a processor and a communication interface.
  • the processor reads instructions stored in a memory through the communication interface to execute the method provided in any one of the first to third aspects above.
  • the chip may also include a memory, in which instructions are stored, and the processor is used to execute the instructions stored in the memory.
  • the processor is used to execute the method provided in any one of the first to third aspects above.
  • a communication system which includes a billing function network element for executing the method shown in the first aspect, a dedicated billing function network element for executing the method shown in the second aspect, and a billing trigger function network element for executing the method shown in the third aspect.
  • FIG. 1 is a schematic diagram of a billing architecture 100 applicable to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a network architecture 200 applicable to an embodiment of the present application.
  • FIG3( a ) is a schematic diagram of a system architecture 300 ( a ) applicable to an embodiment of the present application.
  • FIG3( b ) is a schematic diagram of a system architecture 300 ( b ) applicable to an embodiment of the present application.
  • FIG. 4 is an exemplary flow chart of a method 400 provided in an embodiment of the present application.
  • FIG. 5 is an exemplary flow chart of a method 500 provided in an embodiment of the present application.
  • FIG. 6 is an exemplary flow chart of a method 600 provided in an embodiment of the present application.
  • FIG. 7 is an exemplary flow chart of a method 700 provided in an embodiment of the present application.
  • FIG. 8 is an exemplary flow chart of a method 800 provided in an embodiment of the present application.
  • FIG. 9 is an exemplary flow chart of a method 900 provided in an embodiment of the present application.
  • FIG. 10 is an exemplary flowchart of a method 1000 provided in an embodiment of the present application.
  • FIG. 11 is an exemplary flowchart of a method 1100 provided in an embodiment of the present application.
  • FIG. 12 is an exemplary flowchart of a method 1200 provided in an embodiment of the present application.
  • FIG. 13 is an exemplary flowchart of a method 1300 provided in an embodiment of the present application.
  • FIG. 14 is a schematic block diagram of a communication device provided in accordance with an embodiment of the present application.
  • FIG15 is a schematic block diagram of a communication device provided in another embodiment of the present application.
  • FIG16 is a schematic block diagram of a communication device provided in yet another embodiment of the present application.
  • the information enabled by the information is called information to be enabled.
  • the information to be enabled can be directly enabled, such as the information to be enabled itself or the index of the information to be enabled.
  • the information to be enabled can also be indirectly enabled by enabling other information, wherein there is an association relationship between the other information and the information to be enabled. It is also possible to enable only a part of the information to be enabled, while the other parts of the information to be enabled are known or agreed in advance.
  • the enabling of specific information can also be achieved by means of the arrangement order of each piece of information agreed in advance (such as specified by the protocol), thereby reducing the enabling overhead to a certain extent.
  • the common parts of each piece of information can also be identified and enabled uniformly to reduce the enabling overhead caused by enabling the same information separately.
  • pre-configuration may include pre-definition, for example, protocol definition.
  • pre-definition can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including each network element), and this application does not limit its specific implementation method.
  • the "storage” or “saving” involved in the embodiments of the present application may refer to storage in one or more memories.
  • the one or more memories may be set separately or integrated in an encoder or decoder, a processor, or a communication device.
  • the one or more memories may also be partially set separately and partially integrated in a decoder, a processor, or a communication device.
  • the type of memory may be any form of storage medium, and the present application is not limited to this.
  • the “protocol” involved in the embodiments of the present application may refer to a standard protocol in the communication field, such as a 4G/5G protocol, a new radio (NR) protocol, and related protocols used in future communication systems, and the present application does not limit this.
  • a standard protocol in the communication field such as a 4G/5G protocol, a new radio (NR) protocol, and related protocols used in future communication systems, and the present application does not limit this.
  • 3GPP 3rd Generation Partnership Project
  • the following is an example of a billing architecture 100 applicable to an embodiment of the present application, with reference to FIG1 .
  • each network function (NF) in the core network (CN) domain uses a unified service interface Nchf to connect to the converged charging system (CCS).
  • the CTF in the CN domain can trigger the CCS to provide charging services to users through the Nchf interface.
  • the CCS selects the online charging mode or the offline charging mode according to the user and business requirements.
  • CTF is located in the business system and is used to execute business logic or business control (such as controlling the release of services according to the quota granted by the billing system).
  • CTF provides the session management function (SMF) network element for data services in the 5G core network, or the IMS application server (AS) for the Internet protocol (IP) multimedia subsystem (IMS) voice service, or the edge configuration server (ECS) or edge enabler server (EES) or edge application server (EAS) in the MEC scenario, etc.
  • SMF session management function
  • AS IMS application server
  • IMS Internet protocol
  • EES edge enabler server
  • EAS edge application server
  • CCS refers to a converged charging system that integrates the online charging mode and the offline charging mode.
  • CCS can provide only online charging functions (essentially an online charging system), or only offline charging functions (essentially an offline charging system), or both online and offline charging functions (essentially a converged charging system).
  • Online charging refers to the process of collecting charging information during a session, determining in real time whether there is enough quota for communication authorization and charging
  • offline charging refers to the process of billing through the generation of call log files through communication behavior.
  • CCS includes 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 can receive a billing request from CTF through the service-based billing interface.
  • the billing request will carry CTF's quota application information, usage information, etc.
  • CHF can perform billing based on the received billing request and relevant information of the user's service (such as user type, customer information, account balance, service whitelist/blacklist, account balance change trend, remaining validity period of the package, etc.), and send the billing processing result to CTF so that CTF can adjust the billing operation for the user's service.
  • ABMF ABMF is used to manage user account balances, including account reservation, locking, and deduction.
  • RF is used to determine the required tariff, price or usage based on the service usage request and user information. For example, RF receives the charging event information provided by the online charging function (OCF), determines the usage of OCF network resources, and returns the pricing result to OCF.
  • OCF online charging function
  • CGF is used to perform the following functions: receive CDRs from CDF in real time; pre-process CDRs; verify, merge and format CDRs; handle CDR errors; store persistent records; route and filter records, i.e. store records in separate files based on record type, record parameters, source CDF and other filtering conditions; manage CDR files, such as file creation, file open/close triggers, and file deletion; and transfer CDR files to the billing domain (BD). It is understood that each CCS has a matching BD, which can perform billing processing for the UE based on the CDR files received from the CGF.
  • 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.
  • Figure 2 a possible network architecture diagram of the CN domain in the billing architecture 100 shown in Figure 1 is introduced in combination with Figure 2. It can be understood that Figure 2 only uses the 5G system as an example for illustration, but the present application is not limited thereto, and the present application may also be applicable to other network systems in the future.
  • the network architecture is, for example, the 5G system (5GS) defined in the 3rd Generation Partnership Project (3GPP) protocol TS23.501.
  • the network architecture can be divided into two parts: access network (AN) and core network (CN).
  • the access network can be used to implement functions related to wireless access, and the core network includes multiple logical functional entities.
  • the following is a brief introduction to each network element or device shown in Figure 3:
  • User equipment can be called terminal equipment, terminal device, access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.
  • Terminal equipment can be a device that provides voice/data connectivity to users, for example, a handheld device with wireless connection function, a vehicle-mounted device, etc.
  • terminals can be: mobile phone, tablet computer (pad), computer with wireless transceiver function (such as laptop computer, PDA, etc.), mobile Internet device (mobile internet device, MID), virtual reality (VR) equipment, augmented reality (AR) equipment, wireless terminal in industrial control, wireless terminal in self driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home Wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks, or terminal devices in future evolved public land mobile communication networks (PLMNs), etc.
  • PLMNs public land mobile communication networks
  • the terminal device can also be a terminal device in the Internet of Things (IoT) system.
  • IoT Internet of Things
  • Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-object interconnection.
  • IoT technology can achieve massive connections, deep coverage, and terminal power saving through narrow band (NB) technology, for example.
  • NB narrow band
  • terminal devices can also include smart printers, train detectors, etc. Their main functions include collecting data (part of the terminal equipment), receiving control information and downlink data from network devices, and sending electromagnetic waves to transmit uplink data to network devices.
  • the user equipment can be any device that can access the network.
  • the terminal equipment and the access network equipment can communicate with each other using a certain air interface technology.
  • the user equipment can be used to act as a base station.
  • the user equipment can act as a scheduling entity that provides sidelink signals between user equipment in V2X or D2D, etc.
  • a cell phone and a car communicate with each other using sidelink signals.
  • a cell phone and a smart home device communicate with each other without relaying the communication signal through a base station.
  • Radio access network (R)AN) equipment used to provide network access for authorized user devices in a specific area, and can use transmission tunnels with different service qualities according to the level of user equipment and business requirements.
  • (R)AN can manage wireless resources, provide access services for user equipment, and then complete the forwarding of control signals and user equipment data between user equipment and the core network.
  • (R)AN can also be understood as a base station in a traditional network.
  • the access network device in the embodiment of the present application can be any communication device with wireless transceiver function for communicating with user equipment.
  • the access network device includes but is not limited to an evolved Node B (eNB) or a gNB in a 5G, such as NR, system, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU).
  • eNB evolved Node B
  • TRP transmission point
  • TP transmission point
  • BBU baseband unit
  • DU distributed unit
  • the gNB may include a centralized unit (CU) and a DU.
  • the gNB may also include an active antenna unit (AAU).
  • the CU implements some functions of the gNB, and the DU implements some functions of the gNB.
  • the CU is responsible for processing non-real-time protocols and services, and implements the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers.
  • the DU is responsible for processing physical layer protocols and real-time services, and implements the functions of the radio link control (RLC), media access control (MAC) and physical (PHY) layers.
  • the AAU implements some physical layer processing functions, RF processing and related functions of active antennas.
  • the access network device may be a device including one or more of a CU node, a DU node, and an AAU node.
  • the CU may be classified as an access network device in an access network (radio access network, RAN), or the CU may be classified as an access network device in a core network (core network, CN), and this application does not limit this.
  • UPF User plane function
  • QoS quality of service
  • the user plane network element may still be a UPF network element, or may have other names, which is not limited in this application.
  • Access and mobility management function (AMF) network element The access and mobility management function network element is mainly used for mobility management and access management, etc., and can be used to implement other functions of MME functions except session management, such as access authorization/authentication and other functions.
  • AMF Access and mobility management function
  • the access and mobility management network element may still be AMF, or may have other names, which is not limited in this application.
  • Session management function (SMF) network element mainly used for session management, allocation and management of Internet protocol (IP) addresses of user equipment, selection of endpoints of manageable user plane functions, policy control and charging function interfaces, and downlink data notification.
  • IP Internet protocol
  • the session management function network element is referred to as "SMF”.
  • SMF is a type of session management network element.
  • the session management network element can still be SMF, or it can also be This application does not limit its name.
  • PCF Policy control function
  • the policy control network element may still be a PCF network element, or may have other names, which are not limited in this application.
  • NRF Network repository function
  • NF network function
  • NRF can be used to save the description information of NF entities and the services they provide.
  • NRF can also realize on-demand configuration of network functions and services and interconnection between NFs.
  • Application function (AF) network element used for data routing affected by applications, wireless access network open function network element, interacting with the policy framework for policy control, etc.
  • AF application function
  • the application function network element may still be an AF network element, or may have other names, which is not limited in this application.
  • Unified data management (UDM) network element used to process UE identification, access authentication, registration and mobility management, etc.
  • unified data management may still be a UDM network element, or it may have other names, which is not limited in this application.
  • DN is a network outside the operator network.
  • the operator network can access multiple DNs.
  • a variety of services can be deployed on DN, which can provide data and/or voice services to terminal devices.
  • DN is the private network of a smart factory.
  • the sensors installed in the workshop of the smart factory can be terminal devices.
  • the control server of the sensors is deployed in DN, and the control server can provide services for the sensors.
  • the sensors can communicate with the control server, obtain the instructions of the control server, and transmit the collected sensor data to the control server according to the instructions.
  • DN is the internal office network of a company.
  • the mobile phones or computers of the company's employees can be terminal devices.
  • the employees' mobile phones or computers can access the information and data resources on the company's internal office network.
  • each network element can communicate with each other through the interface shown in the figure.
  • the UE and AMF can interact through the N1 interface, and the interaction message can be called N1 message (N1Message).
  • the RAN and AMF can interact through the N2 interface, and the N2 interface can be used for sending non-access stratum (NAS) messages, etc.
  • the RAN and UPF can interact through the N3 interface, and the N3 interface can be used to transmit user plane data, etc.
  • the SMF and UPF can interact through the N4 interface, and the N4 interface can be used to transmit information such as tunnel identification information of the N3 connection, data cache indication information, and downlink data notification messages.
  • the UPF and DN can interact through the N6 interface, and the N6 interface can be used to transmit user plane data, etc.
  • the relationship between other interfaces and each network element is shown in FIG2 , and for the sake of brevity, they are not described in detail here.
  • the present application provides a communication system 300(a), which includes a billing trigger function network element, a billing function network element and a dedicated billing function network element.
  • the billing trigger function network element is used to send a billing request message to the billing function network element, and the billing request message is used to request billing processing for the terminal device;
  • the billing function network element is used to perform billing processing on the terminal device according to the billing data of the terminal device, wherein the billing data is received by the billing function network element from a dedicated billing function network element, and the dedicated billing function network element belongs to a billing system that persistently stores user data of the terminal device.
  • the billing function network element is also used to send a billing data request message to the dedicated billing function network element; the dedicated billing function network element is also used to send the billing data to the billing function network element according to the billing data request message; the billing function network element is also used to receive the billing data from the dedicated billing function network element.
  • the billing function network element after receiving the billing request message from the billing trigger function network element, performs billing processing on the terminal device according to the user data obtained from the dedicated billing function network element, thereby reducing the cross-zone transmission of a large amount of billing information generated in the billing process, thereby saving network resources and reducing operating costs.
  • the communication system 300(a) shown in (a) of FIG3 may be applied to the charging architecture 100 shown in FIG1.
  • the charging function network element in the communication system 300(a) may correspond to the CHF in FIG1
  • the charging trigger function network element in the communication system 300(a) may correspond to the CTF in FIG1.
  • the dedicated charging function network element in the communication system 300(a) corresponds to the CHF in the home CCS.
  • system Architecture 300 (b) includes a dedicated CCS and CCS1 , and optionally, CCS2 .
  • dedicated CCS is a billing system configured by the operator to persistently store the UE user data (user data includes user name, contracted package, account balance, bill, call record, etc.).
  • dedicated CCS is the CCS of the UE's contracted area in the UE's home public land mobile network (PLMN).
  • PLMN public land mobile network
  • Dedicated CCS provides an interface with external systems (such as customer relationship management (CRM) system, recharge server, accounting system, billing capability opening, etc.), that is, external systems can perform related operations on UE through dedicated CCS.
  • external systems such as customer relationship management (CRM) system, recharge server, accounting system, billing capability opening, etc.
  • CCM customer relationship management
  • the external communication system queries the UE bill through dedicated CCS, or, after the external communication system completes the recharge of the UE, it synchronizes the UE account data to dedicated CCS.
  • the dedicated CCS includes a dedicated CHF, which is used to directly modify and operate the persistent user data of the user.
  • the dedicated CHF is also used to determine the UE's serving CHF and coordinate changes in the UE's Serving CHF.
  • the Serving CHF belongs to the UE's serving CCS
  • the UE's Serving CCS refers to the CCS that currently provides billing services for the UE.
  • the dedicated billing system in this application refers to the dedicated CCS, and may also refer to the dedicated CHF in the dedicated CCS.
  • CCS1 is a candidate CCS for the UE except the dedicated CCS, where the candidate CCS refers to a CCS that can provide billing services for the UE, or refers to a CCS that may become the serving CCS for the UE, or refers to a CCS other than the dedicated CCS in the UE's home PLMN.
  • the present application does not limit the number of candidate CCSs of the UE. That is, in addition to dedicated CCS and CCS1, the UE may also have one or more other candidate CCSs, such as CCS2, which is not limited in the present application.
  • any one of the dedicated CCS, CCS1, and CCS2 may become the serving CCS of the UE, that is, the Serving CCS of the UE may change as the position of the UE changes.
  • the dedicated CCS when the UE moves to the coverage area of the dedicated CCS (for example, from the coverage area of CCS1/CCS2 to the coverage area of the dedicated CCS), the dedicated CCS will serve as the serving CCS of the UE; when the UE moves to the coverage area of CCS1 (for example, from the coverage area of dedicated CCS/CCS2 to the coverage area of CCS1), CCS1 will serve as the serving CCS of the UE; when the UE moves to the coverage area of CCS2 (for example, from the coverage area of dedicated CCS/CCS1 to the coverage area of CCS2), CCS2 will serve as the serving CCS of the UE. That is to say, in the embodiment of the present application, the CCS closest to the UE is used as the Serving CCS of the UE.
  • the above-mentioned network architecture applied to the embodiment of the present application is only an example, and the network architecture applicable to the embodiment of the present application is not limited to this.
  • Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiment of the present application, that is, the network architecture and business scenarios described in the embodiment of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiment of the present application, and do not constitute a limitation on the technical solutions provided in the embodiment of the present application.
  • Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiment of the present application are also applicable to similar technical problems.
  • network elements or devices listed in the above network architecture are only exemplary, and the network architecture applicable to the present application may also include other network elements or devices, which is not limited in the present application.
  • the communication device in the embodiment of the present application includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also called main memory).
  • the operating system can be any one or more computer operating systems that implement business processing through a process, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system.
  • the application layer includes applications such as a browser, an address book, a word processing software, and an instant messaging software.
  • the embodiment of the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application.
  • the execution subject of the method provided in the embodiment of the present application can be a terminal device or a network device, or a functional module in a terminal device or a network device that can call and execute a program.
  • a computer-readable medium may include, but is not limited to: a magnetic storage device (e.g., a hard disk, a floppy disk, or a magnetic tape, etc.), an optical disk (e.g., a compact disc (CD), a digital versatile disc (DVD), etc.), a smart card, and a flash memory device.
  • a magnetic storage device e.g., a hard disk, a floppy disk, or a magnetic tape, etc.
  • an optical disk e.g., a compact disc (CD), a digital versatile disc (DVD), etc.
  • smart card e.g., a smart card, and a flash memory device.
  • the storage medium may be a device (e.g., an erasable programmable read-only memory (EPROM), a card, a stick or a key drive, etc.).
  • EPROM erasable programmable read-only memory
  • the various storage media described herein may represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing and/or carrying instructions and/or data.
  • FIG4 shows an exemplary flow chart of a method 400 provided in an embodiment of the present application.
  • a charging function network element close to the terminal device i.e., a charging function network element that receives a charging request message from a charging triggering function network element
  • a dedicated charging function network element maintains the charging data of the terminal device.
  • charging trigger function network element #1 sends charging request message #1 to charging function network element #1.
  • charging function network element #1 receives the charging request message #1 from the charging trigger function network element #1.
  • the terminal device after the terminal device switches to the billing trigger function network element #1 due to location movement, it triggers the establishment of a service session with the billing trigger function network element #1. It can be understood that for the online billing scenario, the terminal device triggers the establishment of a service session with the billing trigger function network element #1 after terminating the service session with the old billing function network element; for the offline billing scenario, the terminal device directly triggers the service session with the billing trigger function network element #1.
  • the old billing trigger function network element mentioned here refers to the network element that provided services to the terminal device before the billing trigger function network element #1.
  • the billing trigger function network element #1 When the billing trigger function network element #1 receives a service request for the terminal device, it sends a billing request message #1 to the billing function network element #1, and the billing request message #1 is used to request billing processing for the terminal device. For example, when the terminal device moves to the coverage area of the network where the billing trigger function network element #1 is located, it initiates a registration request or a protocol data unit session establishment request to the billing trigger function network element #1. After receiving the above request from the terminal device, the billing trigger function network element #1 sends a billing request message #1 to the billing function network element #1.
  • the billing trigger function network element #1 sends a billing request message #1 to the billing function network element #1 through the dedicated billing function network element of the terminal device, and the dedicated billing function network element belongs to a billing system that persistently stores the user data of the UE. For example, the billing trigger function network element #1 queries the dedicated billing function network element corresponding to the terminal device, and then sends a billing request message #1 to the dedicated billing function network element. After receiving the billing request message #1, the dedicated billing function network element queries the billing function network element #1. For example, the dedicated billing function network element is pre-configured with a correspondence between the billing trigger function network element and the billing function network element (including the correspondence between the billing trigger function network element #1 and the billing function network element #1).
  • the dedicated billing function network element determines the billing function network element #1 corresponding to the billing trigger function network element #1 based on the pre-configured information. Further, the dedicated billing trigger function network element redirects the billing request message #1 to the billing function network element #1.
  • the billing trigger function network element #1 or the dedicated billing function network element may also carry the address information of the dedicated billing function network element in the billing request message #1, such as the Internet Protocol address information of the dedicated billing function network element, or the identification information of the dedicated billing function network element.
  • the present application does not limit the specific implementation manner in which the charging trigger function network element #1 queries the dedicated charging function network element corresponding to the terminal device. Two possible examples are given below.
  • Example 1 Billing trigger function network element #1 queries the dedicated billing function network element corresponding to the terminal device through the network storage function network element.
  • the network storage function network element stores the association relationship between the identification information of the terminal device and the address information of the dedicated billing function network element as shown in Table 1, wherein the address information of the dedicated billing function network element is information used to determine the dedicated billing function network element, for example, the address information of the dedicated billing function network element may be the identification information or address information of the dedicated billing function network element.
  • “SUPI/GPSI” represents the identification of the terminal device
  • “dedicated CHFInfo” represents the address information of the dedicated billing function network element corresponding to the terminal device. It can be understood that the network storage function network element may store the association relationship between one or more groups of terminal device identification information and the address information of the dedicated billing function network element, and this application does not limit this.
  • the charging trigger function network element #1 may send a query request message to the network storage function network element, and carry the terminal device identifier (such as the SUPI or GPSI of the terminal device) in the query request message.
  • the network storage function network element queries the dedicated charging function network element corresponding to the terminal device identifier according to the terminal device identifier carried in the query request message, and then returns the address information of the dedicated charging function network element to the charging trigger function network element #1.
  • the billing function network element #1 determines the address information of the dedicated billing function network element corresponding to the location information of the terminal device and/or the information of the billing trigger function network element #1 in the local configuration information based on the location information of the terminal device and/or the information of the billing trigger function network element #1, and then sends a billing request message #1 to the dedicated billing function network element based on the address information.
  • the billing trigger function network element #1 queries the address information of the billing function network element #1 through the dedicated billing function network element, and then sends the billing request message #1 to the billing function network element #1 according to the address information.
  • the implementation method in which the dedicated billing function network element determines the address information of the billing function network element #1 can refer to the example in the first possible implementation, which will not be repeated here.
  • the billing trigger function network element #1 can also carry the address information of the dedicated billing function network element in the billing request message #1.
  • the billing trigger function network element #1 obtains the address information of the billing function network element #1 based on the information of the billing trigger function network element #1 and/or the location information of the terminal device, and then sends a billing request message to the billing function network element #1 based on the address information.
  • the charging trigger function network element #1 sends a query request message to the network storage function network element, the query request message is used to request to obtain the address information of the candidate charging function network element used to perform charging processing on the terminal device, and the query request message includes the location information of the terminal device and/or the information of the charging trigger function network element #1.
  • the network storage function network element queries the address information of the candidate charging function network element corresponding to the location information of the terminal device and/or the information of the charging function network element #1.
  • the network storage function network element stores the corresponding relationship between the Serving NF and the address information of the charging function network element as shown in Table 2.
  • “Serving NF ID” represents the information of the Serving NF of the terminal device (i.e., the charging trigger function network element #1, or it may be other network elements that provide services to the terminal device), and "location” represents the location information of the terminal device.
  • “CHFInfo” represents the address information of the charging function network element #1 corresponding to the location information of the terminal device and/or the information of the charging trigger function network element #1.
  • the network storage function network element queries the billing function network element #1 corresponding to the location information of the terminal device and/or the information of the billing function network element based on the location information of the terminal device and/or the information of the billing function network element carried in the query request message, and then returns the address information of the billing function network element #1 to the billing trigger function network element #1.
  • the billing trigger function network element #1 determines the address information of the billing function network element #1 corresponding to the location information of the terminal device and/or the information of the billing trigger function network element #1 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 #1, and then sends a billing request message to the billing function network element #1 according to the address information.
  • the local configuration information may be pre-configured on the billing trigger function network element #1, or may be configured to the billing trigger function network element by other network elements, and this application does not limit this.
  • the charging triggering function network element #1 determines the address information of the charging function network element #1 through the charging system address information in the policy sent by the PCF, and then sends the charging request message #1 to the charging function network element #1 according to the address information.
  • the billing function network element #1 bills the terminal device according to the billing data #1 of the terminal device.
  • the billing function network element #1 bills the terminal device according to the billing data #1 of the terminal device, or the billing function network element #1 processes the billing request message #1 according to the billing data #1 of the terminal device, or the billing function network element #1 becomes the service billing function network element of the terminal device.
  • the billing function network element #1 performs operations such as granting quota, batch price, and locking account balance on the terminal device according to the billing data #1; for offline billing, the billing function network element #1 performs operations such as opening a call record, processing the call record, and returning a response on the terminal device according to the billing data #1.
  • the billing data #1 is received by the billing function network element #1 from the dedicated billing function network element.
  • the billing data #1 here refers to the data required for billing the terminal device, such as user account data (user name, type, account balance, package, batch price information), policy data applied to the user (such as batch price policy, etc.), etc.
  • the network element that provides billing services to the terminal device before the billing function network element #1 can be a dedicated billing network element, or it can be other candidate billing function network elements (such as billing function network element #2) other than the billing function network element #1 and the dedicated billing function network element. This application does not limit this.
  • the billing function network element #1 obtains the billing data #1 of the terminal device.
  • the following is an exemplary description of the specific implementation method of the billing function network element #1 obtaining the billing data #1 of the terminal device for two possible situations.
  • the billing function network element #1 obtains the billing data #1 of the terminal device from the local storage.
  • the billing function network element #1 determines whether the billing data #1 of the terminal device is stored in the local storage. If the billing function network element #1 stores the billing data #1 locally, the billing function network element #1 can directly obtain the billing data #1 from the local storage.
  • the billing function network element #1 is the billing data #1 of the terminal device received in advance from the dedicated billing function network element before S401.
  • the billing function network element #1 is already the service billing function network element of the terminal device, and obtains and saves the billing data #1 of the terminal device from the dedicated billing function network element. But then the user goes offline and then comes back online, then the billing function network element #1 can directly obtain the billing data #1 from the local storage.
  • the dedicated billing function network element may recycle the billing data #1 from the billing function network element #1. Therefore, the billing data #1 maintained locally by the billing function network element can be considered to be the latest billing data.
  • the charging function network element #1 sends a charging data request message #1 to the dedicated charging function network element.
  • the dedicated charging function network element receives the charging data request message #1 from the charging function network element #1.
  • the billing function network element #1 may directly send a billing data request message #1 to the dedicated billing function network element to request to obtain the billing data #1 of the terminal device; or, when it is determined that there is no billing data #1 of the terminal device in the local storage, the billing function network element #1 may send a billing data request message #1 to the dedicated billing function network element to request to obtain the billing data #1 of the terminal device.
  • the billing data request message #1 can be the billing request message #1 received by the billing function network element #1 (that is, the billing function network element #1 forwards the received billing request message #1 to the dedicated billing function network element), or it can be a newly generated message by the billing function network element #1. This application does not limit this.
  • the charging function network element #1 before sending the charging data request message #1 to the dedicated charging function network element, the charging function network element #1 obtains the address information of the dedicated charging function network element, that is, determines the dedicated charging function network element.
  • the billing function network element #1 queries the network storage function network element for the address information of the dedicated billing function network element corresponding to the terminal device according to the identification of the terminal device.
  • the specific method is similar to the first possible implementation method shown in S401, in which the billing trigger function network element #1 queries the dedicated billing function network element corresponding to the terminal device through the network storage function network element.
  • the billing function network element #1 can also query the address information of the dedicated billing function network element through other network elements or devices that store the correspondence between the terminal device and the dedicated billing function network element, and this application does not limit this.
  • the billing trigger function network element #1 or the dedicated billing function network element can carry the address information of the dedicated billing function network element in the billing request message #1 (for details, please refer to the description of part S401). In this case, the billing function network element #1 obtains the address information of the dedicated billing function network element from the billing request message #1.
  • the dedicated billing function network element records that billing function network element #1 is the network element currently providing billing services for the terminal device, or in other words, the dedicated billing function network element saves the information of the current service billing function network element of the terminal device (i.e., the information of billing function network element #1).
  • the dedicated billing function network element can determine who the current service billing function network element of the terminal device is, so that it can subsequently interact with the service billing function network element of the terminal device to provide services for the terminal device.
  • the dedicated charging function network element sends charging data #1 to charging function network element #1.
  • charging function network element #1 receives charging data #1 from the dedicated charging function network element.
  • the dedicated billing function network element after receiving the billing data request message #1 from the billing function network element #1, the dedicated billing function network element locally queries the billing data #1 of the terminal device, and then sends the billing data #1 to the billing function network element #1.
  • the billing data #1 sent by the dedicated billing function network element can be a format file, a compressed format file, information in CDATA format directly carried in the message, and other forms of data, which are not limited in this application.
  • the dedicated billing function network element implicitly indicates that the billing function network element #1 is the service billing function network element of the terminal device by sending the billing data #1 of the terminal device to the billing function network element #1. That is, after the terminal device receives the billing data #1 from the dedicated billing function network element, it switches to the service billing function network element of the terminal device.
  • the dedicated billing function network element can send the billing data #1 at one time, or it can send the billing data #1 multiple times during the billing process, and this application does not limit this.
  • the billing data #1 sent by the dedicated billing function network element to the billing function network element #1 may include only part of the user data of the terminal device, such as the billing data #1 is only the data in the user data of the terminal device used for billing the terminal device, or the billing data #1 may also include all the data in the user data of the terminal device, and the present application does not To be limited.
  • the charging function network element #1 sends the charging result #1 to the dedicated charging function network element.
  • the dedicated charging function network element receives the charging result #1 from the charging function network element #1.
  • the billing function network element #1 sends the billing result #1 to the dedicated billing function network element, wherein the billing result #1 here refers to the data obtained after the billing function network element #1 performs the billing process on the terminal device, for example, the billing result #1 includes data such as user usage, account balance change, and package balance change. It is understandable that the billing function network element #1 can send the billing data #1 to the dedicated billing function network element at one time after the billing is completed, or send the billing data #1 to the dedicated billing function network element multiple times during the billing process, and this application does not limit this.
  • the dedicated billing function network element updates the user data of the terminal device according to the billing result #1.
  • the billing function network element #1 performs billing processing on the terminal device, so some temporary data of the billing process does not need to be transmitted in the signaling network, thereby saving network resources and reducing operating costs.
  • the billing data of the terminal equipment is centrally managed by a dedicated billing function network element, which can only send part of the data for the billing function network element to bill the terminal equipment, thereby further reducing the pressure on the signaling network and improving the efficiency of billing.
  • the service billing function network element of the terminal device can be switched to billing function network element #2.
  • the following is an exemplary description in conjunction with process 2.
  • the charging trigger function network element #2 sends a charging request message #2 to the charging function network element #2.
  • the charging function network element #2 receives the charging request message #2 from the charging trigger function network element #2.
  • charging trigger function network element #2 when receiving a service request for a terminal device, charging trigger function network element #2 sends a charging request message #2 to charging function network element #2, and the charging request message #2 is used to request charging for the terminal device.
  • the way in which charging trigger function network element #2 sends charging request message #2 to charging function network element #2 is similar to the way in which charging trigger function network element #1 sends charging request message #1 to charging function network element #1 in S401, and for the sake of brevity, it will not be repeated here.
  • the charging function network element #2 sends a charging data request message #2 to the dedicated charging function network element.
  • the dedicated charging function network element receives the charging data request message #2 from the charging function network element #2.
  • the charging function network element #2 after receiving the charging request message #2 from the charging trigger function network element #2, the charging function network element #2 sends a charging data request message #2 to the dedicated charging function network element to request to obtain the charging data of the terminal device.
  • the charging function network element #2 may send a charging data request message #2 to the dedicated charging function network element when determining that there is no charging data of the terminal device in the local storage.
  • the billing function network element #2 determines the dedicated billing function network element.
  • the specific scheme is similar to the way in which the billing function network element #1 determines the dedicated billing function network element in S402b. For the sake of brevity, it will not be repeated here.
  • the dedicated charging function network element sends charging data #2 to charging function network element #2.
  • charging function network element #2 receives the charging data #2 from the dedicated charging function network element.
  • S406 is similar to S402c, except that in S406, the charging data #2 sent by the dedicated charging function network element to the charging function network element #2 is the charging data updated after S403.
  • the specific implementation process is not limited.
  • the dedicated charging function network element sends the charging data #2 of the terminal device to the charging function network element
  • the dedicated charging function network element determines whether it is necessary to update the charging data of the terminal device to the charging function network element #2 according to the charging result #3.
  • the charging result #3 is the data obtained after the charging function network element #1 performs the charging process on the terminal device after S403.
  • the billing function network element #1 may still bill the terminal device after S403 until the billing function network element #1 receives the termination request message.
  • the billing function network element then sends the billing result #3 generated between sending the billing result #1 and receiving the termination request message to the dedicated billing function network element.
  • the dedicated billing function network element determines whether it needs to update the billing data to the billing function network element #2 based on the billing result #3.
  • the billing data #2 sent by the dedicated billing function network element to the billing function network element #2 in S406 is part of the user data of the terminal device.
  • the quota provided by the dedicated billing function network element to the billing function network element #2 through the billing data #2 is 200M
  • the billing result #3 indicates that the terminal device has used 400M
  • the dedicated billing function network element provides the billing function network element #2 through the billing data #2
  • the quota is 200M.
  • the quota provided is greater than the balance of the terminal device (the balance is 100M).
  • the dedicated charging function network element determines that the charging data of the terminal device needs to be updated to the charging function network element #2.
  • the dedicated charging function network element sends the updated charging data to the charging function network element #2.
  • the terminal device can continue to perform charging processing on the terminal device according to the updated charging data.
  • the billing function network element #2 bills the terminal device.
  • the charging function network element #2 sends the charging result #2 to the dedicated charging function network element, wherein the charging result #2 is the data obtained after the charging function network element #2 charges the terminal device.
  • the dedicated charging function network element receives the charging result #2 from the charging function network element #2.
  • S407-S408 are similar to S402-S403, the difference is that S407-S408 are executed by billing function network element #2, and S402-S403 are executed by billing function network element #1. For the sake of brevity, they are not repeated here.
  • the dedicated billing function network element After receiving the data after the billing processing from the billing function network element #2, the dedicated billing function network element updates the user data of the terminal device.
  • the service billing function network element of the terminal device can be switched to the dedicated billing function network element #2.
  • the following is an exemplary description in conjunction with process 3.
  • the charging trigger function network element #3 sends a charging request message #3 to the dedicated charging function network element.
  • the dedicated charging function network element receives the charging request message #3 from the charging trigger function network element #3.
  • the charging trigger function network element #3 when receiving a service request for a terminal device, the charging trigger function network element #3 sends a charging request message #3 to the dedicated charging function network element, and the charging request message #3 is used to request charging for the terminal device.
  • the way in which the charging trigger function network element #3 sends the charging request message #3 to the dedicated charging function network element is similar to the way in which the charging trigger function network element #1 sends the charging request message #1 to the charging function network element #1 in S401, and for the sake of brevity, it will not be repeated here.
  • the dedicated billing function network element bills the terminal device according to the billing data #3.
  • the dedicated charging function network element queries the charging data #3 corresponding to the terminal device, and then charges the terminal device according to the charging data #3. It can be understood that the charging data #3 is the charging data updated by the dedicated charging function network element after S408.
  • the billing function network element closest to the terminal device i.e., the billing function network element that receives the billing request message from the billing trigger function network element
  • the network when the network is divided into multiple regions (such as: China's deployment according to provinces, Europe's one network across multiple countries, and the operator network of coastal countries covering multiple islands, etc.), it is necessary to deploy multiple core networks and billing systems in multiple regions.
  • the home billing system is used to bill the terminal device, when the terminal device moves to an area outside the home area, it is necessary to route a large amount of billing information (such as call records and other information) generated by the terminal device in real time to the proprietary billing system of the terminal device, thereby increasing the pressure on the signaling network and operating costs.
  • the above scheme uses the nearest billing function network element to the terminal device (i.e. the billing function network element that receives the billing request message) to bill the terminal device, which can save network resources and reduce the impact on user service usage when a billing network line fails.
  • the terminal device is UE
  • the dedicated charging function network element is a dedicated CHF (dedicated CHF)
  • the charging trigger function network element is SMF or MEC CTF
  • the charging function network element is CHF as an example for explanation.
  • FIG5 shows an exemplary flow chart of a method 500 provided in an embodiment of the present application.
  • the serving CHF of the UE is switched from dedicated CHF to CHF1.
  • SSC mode 2 is a service and session continuity mode.
  • SSC mode 2 when the session anchor point is changed, the connection between UE and the original PDU session anchor point is first released, and then the connection between UE and the new PDU session anchor point is established, and the intermediate service will be interrupted.
  • the method 500 is exemplarily described below in conjunction with each step in FIG. 5 .
  • S501, UE and UPF1 establish PDU session #1, and transmit data through PDU session #1.
  • the specific process is not limited in this application.
  • SMF1 triggers dedicated CHF to charge the UE.
  • the specific process is not limited in this application.
  • SMF1 determines to execute the switching of UPF.
  • SMF1 determines that it is necessary to switch to the UPF that provides services for the UE, where SMF1 is the SMF that provides services for the PDU session #1 of the UE. For example, when the UE moves and UPF1 can no longer provide services for the UE, or when the signal between UPF1 and the UE is poor, SMF1 determines that it is necessary to switch to the UPF that provides services for the UE.
  • SMF1 sends a session management context status notification request message to AMF.
  • AMF receives the session management context status notification request message from SMF1.
  • SMF1 when SMF1 determines to switch UPF, it sends a session management context status notification request (Nsmf_PDUSession_SMContextStatusNotify Request) message to AMF.
  • the session management context status notification request message is used to instruct AMF to release PDU session #1.
  • S504 sends a session management context status notification response message to SMF1.
  • SMF1 receives the session management context status notification response message from AMF.
  • AMF after AMF receives the session management context status notification request message from SMF1, it returns a session management context status notification response (Nsmf_PDUSession_SMContextStatusNotify Response) message to SMF1.
  • Nsmf_PDUSession_SMContextStatusNotify Response a session management context status notification response
  • AMF triggers the release process of PDU session #1 according to the session management context status notification request message, that is, triggers UE to disconnect from UPF 1.
  • the specific process can be referred to the existing protocol and will not be repeated here.
  • SMF1 sends a termination request message #1 to the dedicated CHF.
  • the dedicated CHF receives the termination request message #1 from SMF1.
  • SMF1 sends a termination request message #1 to a dedicated CHF, which is the network element currently providing billing services for the UE.
  • the termination request message #1 is used to request the termination of the billing session corresponding to PDU session #1, that is, to release the billing resources for PDU session #1 between SMF1 and dedicated CHF.
  • the dedicated CHF sends a termination response message to SMF1.
  • SMF1 receives the termination response message from the dedicated CHF.
  • dedicated CHF releases the billing resources and returns a termination response message #1.
  • the termination response message #1 includes the final usage of PDU session #1, i.e., the user traffic usage between the last initial request (i.e., billing request) and this termination request message #1.
  • the user traffic usage refers to the usage for the quota
  • the user traffic usage refers to the statistical traffic usage.
  • the UE triggers the establishment process of PDU session #2 between UPF2.
  • the specific process can refer to the existing protocol and will not be repeated here.
  • SMF2 sends an initial request message #1 to CHF1.
  • CHF1 receives the initial request message #1 from SMF2.
  • SMF2 receives the session management context creation request (Nsm_PDUSession_CreateSMContext Request) message for PDU session #2 from AMF, SMF2 sends an initial request (initial request) message #1 for PDU session #2 to CHF1, wherein SMF2 is the SMF providing service for PDU session #2, and the initial request message #1 is used to request charging of the UE for the PDU session #2.
  • Nsm_PDUSession_CreateSMContext Request session management context creation request
  • initial request message #1 is used to request charging of the UE for the PDU session #2.
  • SMF2 sending the initial request message #1 to CHF1 can refer to S401 of method 400, in which the billing trigger function network element #1 sends the billing request message #1 to the billing function network element #1.
  • SMF2 in S509 corresponds to the billing trigger function network element #1 in S401
  • CHF1 in S509 corresponds to the billing function network element #1 in S401
  • the initial request message #1 in S509 corresponds to the billing request message #1 in S401, which will not be repeated here.
  • CHF1 sends an initial request message #2 to the dedicated CHF.
  • the dedicated CHF receives the initial request message #2 from CHF1.
  • the dedicated CHF sends charging data to CHF1.
  • CHF1 receives the charging data from the dedicated CHF.
  • CHF1 sends an initial request message #2 to the dedicated CHF to request to obtain the billing data of the UE.
  • the dedicated CHF returns the billing data of the UE according to the request of CHF1.
  • the specific process can refer to S402b-S402c in method 400.
  • the dedicated CHF and CHF1 in S510-S511 correspond to the dedicated billing function network element and billing function network element #1 in S402b-S402c respectively
  • the initial request message #2 in S510 corresponds to the billing data request message #1 in S402b
  • the billing data in S511 corresponds to the billing data #1 in S402c.
  • CHF1 after CHF1 receives the charging data from the dedicated CHF, it charges the UE according to the charging data.
  • the specific process can be referred to S402 in the method 400, which will not be described in detail here.
  • SMF2 and CHF1 perform subsequent billing interaction (such as an update request message of the billing process), and the specific process is not limited in this application.
  • CHF1 sends an initial response message to SMF2.
  • SMF2 receives the initial response message from CHF1.
  • CHF1 after receiving the charging data from the dedicated CHF, CHF1 returns an initial response message to SMF2, where the initial response message is used to respond to the initial request message #1. It is to be understood that the present application does not limit the execution order of S512 and S513.
  • SMF2 sends a termination request message #2 to CHF1.
  • CHF1 receives the termination request message #2 from SMF2.
  • CHF1 sends a termination response message #2 to SMF2.
  • SMF2 receives the termination response message #2 from CHF1.
  • SMF1 sends a termination request message #2 to CHF1 to request the termination of the billing session corresponding to PDU session #2, that is, to release the billing resources between SMF2 and CHF1 for the PDU session #1.
  • CHF1 sends the charging result to the dedicated CHF.
  • the dedicated CHF receives the charging result from CHF1.
  • S516 is similar to S403 in method 400 and will not be described in detail here.
  • the UE's nearest CHF1 obtains the UE's billing data through dedicated CHF and provides billing services to the UE, thereby reducing the cross-zone transmission of a large amount of billing information generated during the billing process, saving network resources and reducing operating costs.
  • FIG6 shows an exemplary flow chart of a method 600 provided in an embodiment of the present application.
  • the method 600 it is assumed that the serving CHF of the UE is switched from CHF1 to CHF2.
  • the method 600 is described by taking the switching of the PDU session of the UE through SSC mode2 in the online charging scenario as an example.
  • method 600 may be implemented independently or in combination with method 500.
  • method 600 may be a solution executed after method 500.
  • the method 600 is exemplarily described below in conjunction with each step in FIG. 6 .
  • S601, UE and UPF2 establish PDU session #2, and transmit data through the PDU session #2.
  • the specific process is not limited in this application.
  • SMF2 triggers CHF1 to charge the UE, and the specific process is not limited in this application. If method 600 is implemented in combination with method 500, S601 may correspond to S508-S513 in method 500.
  • S602 determines to execute UPF switching.
  • SMF1 sends a session management context status notification request message to AMF.
  • S604 sends a session management context status notification response message to SMF1.
  • S602 - S604 are similar to S502 - S504 in method 500 and are not described in detail here.
  • AMF triggers the release process of PDU session #2 according to the session management context status notification request message, that is, triggers UE to disconnect from UPF2.
  • the specific process can be referred to the existing protocol and will not be repeated here.
  • SMF2 sends a termination request message to CHF1.
  • CHF1 receives the termination request message from SMF2.
  • SMF2 sends a termination request message #1 to CHF1, where CHF1 is the network element currently providing billing services for the UE.
  • the termination request message #1 is used to request the termination of the charging session corresponding to the PDU session #2, that is, to release the charging resources for the PDU session #2 between SMF2 and CHF1.
  • CHF1 sends a termination response message #1 to SMF2.
  • SMF2 receives the termination response message #1 from CHF1.
  • CHF1 releases the billing resources and returns a termination response message #1.
  • the termination response message #1 includes the last usage of PDU session #2.
  • CHF1 sends the charging result #1 to the dedicated CHF.
  • the dedicated CHF receives the charging result #1 from CHF1.
  • S608 is similar to S403 in method 400 and will not be described in detail here. It is understandable that if method 600 is implemented in combination with method 500, S608 may correspond to S514 in method 500.
  • the UE triggers the establishment process of PDU session #3 between it and UPF3.
  • the specific process can refer to the existing protocol and will not be repeated here.
  • S610 SMF3 sends an initial request message #1 to CHF2.
  • CHF2 receives the initial request message #1 from SMF3.
  • SMF3 sends an initial request message #1 for PDU session #3 to CHF2, wherein SMF3 is the SMF providing service for PDU session #3, and the initial request message #1 is used to request billing of the UE for the PDU session #3.
  • S610 is similar to S404 in method 400.
  • SMF3 in S610 corresponds to billing trigger function network element #2 in S404
  • CHF2 in S610 corresponds to billing function network element #2 in S404
  • the initial request message #1 in S610 corresponds to billing request message #2 in S404. The specific process will not be repeated here.
  • CHF1 sends an initial request message #2 to the dedicated CHF.
  • the dedicated CHF receives the initial request message #2 from CHF1.
  • the dedicated CHF sends the billing data to CHF1.
  • CHF1 receives the billing data from the dedicated CHF.
  • CHF1 sends an initial request message #2 to the dedicated CHF to request the UE's billing data.
  • the dedicated CHF returns the UE's billing data according to the request of CHF1.
  • the dedicated CHF and CHF2 in S611-S612 correspond to the dedicated billing function network element and billing function network element #2 in S402b-S402c, respectively.
  • the initial request message #2 in S611 corresponds to the billing data request message #2 in S405, and the billing data in S612 corresponds to the billing data #2 in S406, which will not be described in detail here.
  • CHF2 After CHF2 receives the charging data from the dedicated CHF, it charges the UE according to the charging data.
  • the specific process can be referred to S407 in method 400, which will not be described in detail here.
  • SMF3 and CHF2 perform subsequent billing interaction (such as an update request message of the billing process, or a termination request message of the end of billing, etc.), and the specific process is not limited in this application.
  • CHF2 sends an initial response message to SMF3.
  • SMF3 receives the initial response message from CHF2.
  • CHF2 after receiving the charging data from the dedicated CHF, CHF2 returns an initial response message to SMF3, where the initial response message is used to respond to the initial request message #1. It is to be understood that the present application does not limit the execution order of S613 and S614.
  • SMF3 sends a termination request message #2 to CHF2.
  • CHF2 receives the termination request message #2 from SMF3.
  • CHF2 sends a termination response message #2 to SMF3.
  • SMF3 receives the termination response message #2 from CHF2.
  • SMF3 sends a termination request message #2 to CHF2 to request the termination of the billing session corresponding to PDU session #2, that is, to release the billing resources between SMF3 and CHF2 for the PDU session #1.
  • CHF2 sends the charging result #2 to the dedicated CHF.
  • the dedicated CHF receives the charging result #2 from CHF2.
  • S617 is similar to S408 in method 400 and will not be described in detail here.
  • the UE's nearest CHF2 obtains the UE's billing data through dedicated CHF and provides billing services to the UE, thereby reducing the cross-zone transmission of a large amount of billing information generated during the billing process, saving network resources and reducing operating costs.
  • FIG7 shows an exemplary flow chart of a method 700 provided in an embodiment of the present application.
  • the method 700 it is assumed that the serving CHF of the UE is switched from CHF2 to dedicated CHF.
  • the method 700 is described by taking the switching of the PDU session of the UE through SSC mode2 in the online charging scenario as an example.
  • method 700 may be implemented independently, or may be implemented in combination with method 500 and/or method 600.
  • method 700 may be a solution executed after method 600.
  • the method 700 is exemplarily described below in conjunction with each step in FIG. 7 .
  • S701, UE and UPF3 establish PDU session #3, and transmit data through PDU session #3.
  • the specific process is not limited in this application.
  • SMF3 triggers CHF2 to charge the UE, and the specific process is not limited in this application. If method 700 is implemented in combination with method 600, S701 may correspond to S509-S614 in method 600.
  • SMF1 determines to execute the switching of UPF.
  • SMF1 sends a session management context status notification request message to AMF.
  • S704 sends a session management context status notification response message to SMF1.
  • S702 - S704 are similar to S502 - S504 in method 500 and are not described in detail here.
  • AMF triggers the release process of PDU session #3 according to the session management context status notification request message, that is, triggers UE to disconnect from UPF3.
  • the specific process can be referred to the existing protocol and will not be repeated here.
  • SMF3 sends a termination request message to CHF2.
  • CHF2 receives the termination request message from SMF3.
  • SMF3 sends a termination request message to CHF2, which is the network element currently providing billing services for the UE.
  • the termination request message is used to request the termination of the charging session corresponding to PDU session #3, that is, to release the charging resources for PDU session #2 between SMF3 and CHF2.
  • CHF2 sends a termination response message to SMF3.
  • SMF2 receives the termination response message from CHF1.
  • CHF2 releases the billing resources and returns a termination response message, which includes the last usage of PDU session #3.
  • CHF2 sends the charging result to the dedicated CHF.
  • the dedicated CHF receives the charging result from CHF2.
  • S708 is similar to S403 in method 400 and will not be described in detail here. It is understandable that if method 700 is implemented in combination with method 600, then S708 may correspond to S615 in method 600.
  • the UE triggers the establishment process of PDU session #4 between UPF4.
  • the specific process can refer to the existing protocol and will not be repeated here.
  • SMF4 sends an initial request message to the dedicated CHF.
  • the dedicated CHF receives the initial request message from SMF4.
  • SMF4 sends an initial request message for PDU session #4 to the dedicated CHF, wherein SMF4 is the SMF providing services for PDU session #4, and the initial request message is used to request billing of the UE for the PDU session #4.
  • S710 is similar to S409 in method 400.
  • SMF4 in S710 corresponds to the billing trigger function network element #3 in S404
  • the dedicated CHF in S710 corresponds to the dedicated billing function network element in S404
  • the initial request message in S710 corresponds to the billing request message #3 in S404. The specific process will not be repeated here.
  • the dedicated CHF charges the UE according to the charging data.
  • S711 is similar to S410 in method 400 and will not be described again for the sake of brevity.
  • the dedicated CHF sends an initial response message to SMF4.
  • SMF4 receives the initial response message from the dedicated CHF.
  • the dedicated CHF returns an initial response message to SMF4, where the initial response message is used to respond to the initial request message. It is understandable that the present application does not limit the execution order of S711 and S712.
  • dedicated CHF provides billing service for UE according to the billing data of UE maintained locally, thereby reducing the cross-zone transmission of a large amount of billing information generated in the billing process, saving network resources and reducing operating costs.
  • FIG8 shows an exemplary flow chart of a method 800 provided in an embodiment of the present application.
  • the serving CHF of the UE is switched from dedicated CHF to CHF1.
  • SSC mode 3 is a service and session continuity mode different from SSC mode 2.
  • SSC mode 3 before the user plane changes (i.e., the session anchor point changes), a connection with a new PDU session anchor point is established to ensure service continuity.
  • the method 800 is exemplarily described below in conjunction with each step in FIG. 8 .
  • S801, UE and UPF1 establish PDU session #1, and transmit data through PDU session #1.
  • the specific process is not limited in this application.
  • SMF1 determines to execute UPF/SMF switching.
  • S803, SMF1 sends a session management context status notification request message to AMF.
  • AMF receives the session management context status notification request message from SMF1.
  • S804 sends a session management context status notification response message to SMF1.
  • SMF1 receives the session management context status notification response message from AMF.
  • S801 - S804 are similar to S501 - S504 in method 500 , and are not described again here for the sake of brevity.
  • SMF1 sends an N1N2 message delivery request message to AMF.
  • AMF receives the N1N2 message from SMF1. Delivers the request message.
  • the N1N2 message transfer (Namf_Communication_N1N2MessageTransfer) request message includes PDU session ID, SMF relocation indication information, N1SM container, etc.
  • PDU session ID is the identifier of PDU session #1
  • SMF relocation indication information is used to indicate whether to request reallocation of SMF.
  • AMF sends an N1N2 message delivery response message to SMF1.
  • SMF1 receives the N1N2 message delivery response message from AMF.
  • the N1N2 message delivery response message is used to respond to the N1N2 message delivery request message.
  • AMF sends a PDU session modification command to the UE.
  • the UE receives the PDU session modification command from the AMF.
  • the PDU session modification command includes the information carried in the above-mentioned N1N2 message transfer request message.
  • the UE sends a PDU session modification command confirmation message to the AMF.
  • the AMF receives the PDU session modification command confirmation message from the UE.
  • the PDU session modification command message confirmation message is used to respond to the PDU session modification command.
  • AMF sends an update session management context request (Nsmf PDUSession UpdateSMContext Request) message to SMF1.
  • SMF1 receives the update session management context request message from AMF.
  • the AMF sends the N1SM container received from the RAN to the AMF via an update session management context request message.
  • SMF1 sends an update session management context response (Nsmf PDUSession UpdateSMContext Response) message to AMF.
  • AMF receives the update session management context response message from SMF1.
  • the update session management context response message is used to respond to the update session management context request message.
  • the UE determines whether to trigger the establishment of PDU session #2 with UPF2.
  • the specific process is not limited in this application.
  • SMF2 sends an initial request message #1 to CHF1.
  • CHF1 receives the initial request message #1 from SMF2.
  • CHF1 sends an initial request message #2 to the dedicated CHF.
  • the dedicated CHF receives the initial request message #2 from CHF1.
  • the dedicated CHF sends the billing data to CHF1.
  • CHF1 receives the billing data from the dedicated CHF.
  • CHF1 charges the UE according to the charging data.
  • CHF1 sends an initial response message to SMF2.
  • SMF2 receives the initial response message from CHF1.
  • S812-S816 are similar to S509-S513 in method 500 and will not be described in detail here.
  • SMF1 triggers the release process of PDU session #1.
  • the specific process is not limited in this application.
  • SMF1 sends a termination request message #1 to the dedicated CHF.
  • the dedicated CHF receives the termination request message #1 from SMF1.
  • SMF1 sends a termination request message #1 to a dedicated CHF, which is the network element that currently provides billing services to the UE before CHF1.
  • the termination request message #1 is used to request the termination of the billing session corresponding to PDU session #1, that is, to release the billing resources for PDU session #1 between SMF1 and dedicated CHF.
  • the dedicated CHF sends a termination response message #1 to SMF1.
  • SMF1 receives the termination response message #1 from the dedicated CHF.
  • dedicated CHF releases the billing resources and returns a termination response message including the last usage of PDU session #1.
  • SMF2 sends a termination request message #2 to CHF1.
  • CHF1 receives the termination request message #2 from SMF2.
  • CHF1 sends a termination response message #2 to SMF2.
  • SMF2 receives the termination response message #2 from CHF1.
  • SMF1 sends a termination request message #2 to CHF1 to request the termination of the billing session corresponding to PDU session #2, that is, to release the billing resources between SMF2 and CHF1 for the PDU session #1.
  • CHF1 sends the charging result to the dedicated CHF.
  • the dedicated CHF receives the charging result from CHF1.
  • S822 is similar to S403 in method 400 and will not be described in detail here.
  • the location change of the UE causes the serving CHF of the UE to change (such as the serving CHF changes from The dedicated CHF is switched to CHF1)
  • the CHF1 near the UE obtains the UE's billing data through the dedicated CHF and provides billing services for the UE, thereby reducing the cross-zone transmission of a large amount of billing information generated during the billing process, saving network resources and reducing operating costs.
  • FIG9 shows an exemplary flow chart of a method 900 provided in an embodiment of the present application.
  • the method 900 it is assumed that the serving CHF of the UE is switched from CHF1 to CHF2.
  • the method 900 is described by taking the switching of the PDU session of the UE through SSC mode 3 in the online charging scenario as an example.
  • method 900 may be implemented independently or in combination with method 800.
  • method 900 may be a solution executed after method 800.
  • the method 900 is exemplarily described below in conjunction with each step in FIG. 9 .
  • S901-S906 are similar to S801-S806 in method 800, and for the sake of brevity, they are not repeated here.
  • S907, SMF2 sends a termination request message #1 to CHF1.
  • CHF1 receives the termination request message #1 from SMF2.
  • SMF2 may send a termination request message #1 to CHF1, which is the network element currently providing billing services for the UE.
  • the termination request message #1 is used to request to terminate the billing session corresponding to PDU session #2, that is, to release the billing resources between SMF2 and CHF1 for the PDU session #2.
  • S908 CHF1 sends a termination response message #1 to SMF2.
  • SMF2 receives the termination response message #1 from CHF1.
  • S909, CHF1 sends the charging result #1 to the dedicated CHF.
  • the dedicated CHF receives the charging result #1 from CHF1.
  • CHF1 can send charging result #1 to the dedicated CHF, where charging result #1 refers to data obtained after charging function network element #1 performs charging processing on the terminal device.
  • charging result #1 refers to data obtained after charging function network element #1 performs charging processing on the terminal device.
  • AMF sends a PDU session modification command to the UE.
  • the UE receives the PDU session modification command from the AMF.
  • UE sends a PDU session modification command confirmation message to AMF.
  • AMF receives the PDU session modification command confirmation message from UE.
  • AMF sends a request message for updating session management context to SMF1.
  • SMF1 receives the request message for updating session management context from AMF.
  • SMF1 sends an update session management context response message to AMF.
  • AMF receives the update session management context response message from SMF1.
  • S910-S914 are similar to S807-S811 in method 800, and for the sake of brevity, they are not repeated here.
  • SMF3 sends an initial request message #1 to CHF2.
  • CHF2 receives the initial request message #1 from SMF2.
  • CHF2 sends an initial request message #2 to the dedicated CHF.
  • the dedicated CHF receives the initial request message #2 from CHF2.
  • the dedicated CHF sends the charging data to CHF2.
  • CHF2 receives the charging data from the dedicated CHF.
  • CHF2 charges the UE according to the charging data.
  • CHF2 sends an initial response message to SMF3.
  • SMF3 receives the initial response message from CHF2.
  • S915-S919 are similar to S610-S614 in method 500, and will not be described in detail here.
  • SMF2 triggers the release process of PDU session #2.
  • the specific process is not limited in this application.
  • S921 SMF2 sends a termination request message to CHF1.
  • CHF1 receives the termination request message from SMF2.
  • SMF2 sends a termination request message to CHF1, which is the network element that provides billing services to the UE before CHF2.
  • the termination request message is used to request the termination of the billing session corresponding to PDU session #1, that is, to release the billing resources for PDU session #1 between SMF1 and dedicated CHF.
  • CHF1 sends a termination response message to SMF2.
  • SMF2 receives the termination response message from CHF1.
  • CHF1 After CHF1 receives the termination request message from SMF1, it releases the billing resources and returns a termination response.
  • the termination response message includes the final usage of PDU session #2.
  • S923, CHF1 sends the charging result #2 to the dedicated CHF.
  • the dedicated CHF receives the charging result #2 from CHF1.
  • CHF1 if CHF1 generates a new charging result #2 after S909, CHF1 sends the charging result #2 to the dedicated CHF.
  • S924 the dedicated CHF sends updated billing data to CHF2.
  • CHF2 receives the updated billing data from the dedicated CHF.
  • the dedicated CHF determines whether it is necessary to update the billing data to CHF2. If it is necessary to update the billing data to CHF2, the dedicated CHF sends the updated billing data to CHF2. For details, please refer to the examples given after S406 in method 400, which will not be repeated here.
  • CHF2 charges the UE according to the updated charging data.
  • CHF2 charges the UE according to the updated charging data.
  • CHF2 receives the termination request message #2 from SMF3.
  • CHF2 sends a termination response message #2 to SMF3.
  • SMF3 receives the termination response message #2 from CHF2.
  • SMF3 sends a termination request message #2 to CHF2 to request the termination of the billing session corresponding to PDU session #3, that is, to release the billing resources between SMF3 and CHF2 for the PDU session #1.
  • CHF2 sends the charging result #3 to the dedicated CHF.
  • the dedicated CHF receives the charging result #3 from CHF2.
  • S928 is similar to S408 in method 400 and will not be described in detail here.
  • the UE's nearest CHF2 obtains the UE's billing data through dedicated CHF and provides billing services to the UE, thereby reducing the cross-zone transmission of a large amount of billing information generated during the billing process, saving network resources and reducing operating costs.
  • FIG10 shows an exemplary flow chart of a method 1000 provided in an embodiment of the present application.
  • the method 1000 it is assumed that the serving CHF of the UE is switched from CHF2 to a dedicated CHF.
  • the method 1000 is described by taking the switching of the PDU session of the UE through SSC mode 3 in an online charging scenario as an example.
  • method 1000 may be implemented independently or in combination with method 800 and/or 900.
  • method 1000 may be a solution executed after method 900.
  • the method 1000 is exemplarily described below in conjunction with the various steps in FIG. 10 .
  • S1001-S1006 are similar to S801-S806 in method 800, and for the sake of brevity, they are not repeated here.
  • S1007, SMF3 sends a termination request message #1 to CHF2.
  • CHF2 receives the termination request message #1 from SMF3.
  • S1008 CHF2 sends a termination response message #1 to SMF3.
  • SMF3 receives the termination response message #1 from CHF2.
  • S1009, CHF2 sends the charging result #1 to the dedicated CHF.
  • the dedicated CHF receives the charging result #1 from CHF2.
  • S1007-S1009 are similar to S907-S909 in method 900, and for the sake of brevity, they are not repeated here.
  • AMF sends a PDU session modification command to the UE.
  • the UE receives the PDU session modification command from the AMF.
  • UE sends a PDU session modification command confirmation message to AMF.
  • AMF receives the PDU session modification command confirmation message from UE.
  • AMF sends a request message for updating session management context to SMF3.
  • SMF3 receives the request message for updating session management context from AMF.
  • S1013, SMF3 sends an update session management context response message to AMF.
  • AMF receives the update session management context response message from SMF3.
  • S1010-S1014 are similar to S807-S811 in method 800, and for the sake of brevity, they are not repeated here.
  • SMF3 sends an initial request message #1 to CHF2.
  • CHF2 receives the initial request message #1 from SMF2.
  • S1016 The dedicated CHF charges the UE according to the charging data.
  • the dedicated CHF sends an initial response message to SMF4.
  • SMF4 receives the initial response message from the dedicated CHF.
  • S1015-S1017 are similar to S710-S712 in method 700 and will not be described in detail here.
  • SMF3 sends a termination request message #2 to CHF2.
  • CHF2 receives the termination request message #2 from SMF3.
  • CHF2 sends a termination response message #2 to SMF3.
  • SMF3 receives the termination response message #2 from CHF2.
  • S1018-S1020 are similar to S920-S922 in method 900 and will not be repeated here.
  • S1021, CHF2 sends charging result #2 to the dedicated CHF.
  • the dedicated CHF receives the charging result #2 from CHF2.
  • CHF2 if CHF2 generates a new charging result #2 after S1009, CHF2 sends the charging result #2 to the dedicated CHF.
  • the dedicated CHF charges the UE according to the updated charging data.
  • the dedicated CHF determines updated charging data according to the charging result #2, and charges the UE according to the updated charging data.
  • dedicated CHF provides billing service for UE according to the billing data of UE maintained locally, thereby reducing the cross-zone transmission of a large amount of billing information generated in the billing process, saving network resources and reducing operating costs.
  • FIG. 11 shows an exemplary flowchart of a method 1100 provided in an embodiment of the present application.
  • method 1100 is described by taking the offline billing scenario as an example of charging the UE during the process of the UE registering with the network through the AMF.
  • the method 1100 is exemplarily described below in conjunction with the various steps in FIG. 11 .
  • UE sends a registration request message to RAN.
  • RAN receives the registration request message from UE.
  • RAN sends a registration request message to AMF1.
  • AMF1 receives the registration request message from UE.
  • the UE triggers a registration request message to the RAN.
  • the RAN selects the AMF (denoted as AMF1) that provides services for the UE, and then the RAN routes the received registration request message to AMF1.
  • AMF1 AMF1
  • AMF1 sends a UE context transfer request message to AMF2.
  • AMF2 receives the UE context transfer request message from AMF1.
  • AMF1 determines the AMF (denoted as AMF2) that last provided services to the UE according to the GUTI carried in the registration request message. Then AMF1 sends a UE context transfer (Namf_Communication_UEContextTransfer) request message to AMF2 to request the UE context information, and the UE context transfer request message includes the UE identifier.
  • AMF2 determines the AMF (denoted as AMF2) that last provided services to the UE according to the GUTI carried in the registration request message.
  • AMF1 sends a UE context transfer (Namf_Communication_UEContextTransfer) request message to AMF2 to request the UE context information, and the UE context transfer request message includes the UE identifier.
  • UE context transfer Namf_Communication_UEContextTransfer
  • AMF2 sends a UE context transfer response message to AMF1.
  • AMF1 receives the UE context transfer response message from AMF2.
  • AMF2 after AMF2 receives the UE context transfer request message from AMF1, it obtains the UE context information of the UE in the database according to the UE identifier, and then sends the UE context information to AMF1 through a UE context transfer response message.
  • S1101-S1105 only exemplarily describe some steps in the UE registration process. The detailed process can be referred to the existing protocol and will not be repeated here.
  • AMF1 sends an initial request message #1 to CHF1.
  • CHF1 receives the initial request message #1 from AMF1.
  • AMF1 sends an initial request message #1 to CHF1, where the initial request message #1 is used to request charging for the UE.
  • the specific implementation method of AMF1 sending the initial request message #1 to CHF1 can refer to S401 of method 400, where the billing trigger function network element #1 sends the billing request message #1 to the billing function network element #1.
  • the AMF1 in S1106 corresponds to the billing trigger function network element #1 in S401
  • the CHF1 in S1106 corresponds to the billing function network element #1 in S401
  • the initial request message #1 in S1106 corresponds to the billing request message #1 in S401, which will not be repeated here.
  • the network element that provides billing service for the UE before CHF1 may be CHF1, or other CHFs, such as CHF2, or a dedicated CHF, and this application does not limit this.
  • S1107, CHF1 sends an initial request message #2 to the dedicated CHF.
  • the dedicated CHF receives the initial request message #2 from CHF1.
  • the dedicated CHF sends the billing data to CHF1.
  • CHF1 receives the billing data from the dedicated CHF.
  • CHF1 when there is no billing data in the local storage of CHF1, CHF1 sends an initial request message #2 to the dedicated CHF to request to obtain the billing data of the UE.
  • the dedicated CHF returns the billing data of the UE according to the request of CHF1.
  • the specific process can refer to S402b-S402c in method 400.
  • the dedicated CHF and CHF1 in S1107-S1108 correspond to the dedicated billing function network element and billing function network element #1 in S402b-S402c respectively
  • the initial request message #2 in S1107 corresponds to the billing data request message #1 in S402b
  • the billing data in S1108 corresponds to the billing data #1 in S402c, which will not be repeated here.
  • CHF1 obtains the charging data of the UE, it charges the UE according to the charging data.
  • the specific process can be referred to S402 in the method 400, which will not be described in detail here.
  • AMF1 and CHF1 perform subsequent billing interaction (such as an update request message of the billing process, or a termination request message of the end of billing, etc.), and the specific process is not limited in this application.
  • CHF1 sends an initial response message to AMF1.
  • AMF1 receives the initial response message from CHF1.
  • CHF1 after receiving the billing data from the dedicated CHF, CHF1 returns an initial response message to AMF1, where the initial response message is used to respond to the initial request message #1. It is understandable that the present application does not limit the execution order of S1109 and S1110.
  • AMF1 sends a termination request message to CHF1.
  • CHF1 receives the termination request message from AMF1.
  • CHF1 sends a termination response message #2 to SMF2.
  • SMF2 receives the termination response message #2 from CHF1.
  • AMF1 sends a termination request message to CHF1 to request the end of the billing session, that is, to release the billing resources between AMF and CHF1.
  • CHF1 sends the charging result to the dedicated CHF.
  • the dedicated CHF receives the charging result from CHF1.
  • S1113 is similar to S403 in method 400 and will not be described in detail here.
  • AMF triggers the UE's nearest CHF1 to obtain the UE's billing data through dedicated CHF, and provides billing services to the UE, thereby reducing the cross-zone transmission of a large amount of billing information generated during the billing process, saving network resources, and reducing operating costs.
  • the solution provided in the embodiment of the present application can also be applied to MEC scenarios.
  • MEC scenarios For example, when a user accesses an MEC service, if the CHF of the UE changes, the solution shown in method 400 can be executed to charge the UE.
  • the following describes two solutions for charging the UE in MEC scenarios in conjunction with Figures 12 and 13.
  • MEC1 CTF and MEC2 CTF both refer to CTFs in the MEC scenario, wherein MEC2 CTF is the CTF that provides services to the UE before MEC1 CTF, and CHF1 and CHF2 are both network elements that provide billing services to the UE, wherein CHF2 provides billing services to the UE after CHF1, that is, in method 1200 and method 1300, the serving CHF of the UE is switched from CHF1 to CHF2.
  • Method 1200 and method 1300 are two possible implementations of process 1 and process 2 in method 400 in the MEC scenario.
  • the dedicated charging function network element is a dedicated CHF (dedicated CHF)
  • charging trigger function network element #1 is MEC1 CTF
  • charging trigger function network element #2 is MEC2 CTF
  • charging function network element #1 is CHF1
  • charging function network element #2 is CHF2.
  • FIG12 shows an exemplary flow chart of a method 1200 provided in an embodiment of the present application.
  • the billing session between MEC1 CTF and CHF1 is terminated first, and then the billing session between MEC2 CTF and CHF2 is established.
  • the method 1200 is exemplarily described below in conjunction with the various steps in FIG12.
  • MEC1 CTF sends an initial request message #1 to CHF1.
  • CHF1 receives the initial request message #1 from MEC1 CTF.
  • MEC1 CTF sends an initial request message #1 to CHF1 to request CHF1 to charge the UE's service on MEC1.
  • the specific process may refer to the description of S401 in method 400, wherein MEC1 CTF in S1201 may correspond to billing trigger function network element #1 in S401, and CHF1 in S1201 may correspond to billing function network element #1 in S401, which will not be repeated here.
  • S1202, CHF1 sends an initial request message #2 to the dedicated CHF.
  • the dedicated CHF receives the initial request message #2 from CHF1. Fee request message #2.
  • CHF1 when no charging data of the UE is stored in the local storage of CHF1, CHF1 sends an initial request message #2 to the dedicated CHF.
  • the specific process may refer to the description of S402b in method 400, wherein the initial request message #2 in S1202 may correspond to the charging data request message #1 in S402b, which will not be described in detail here.
  • the dedicated CHF sends the billing data #1 to CHF1.
  • CHF1 receives the billing data #1 from the dedicated CHF.
  • the dedicated CHF after receiving the initial request message #2 from CHF1, the dedicated CHF locally queries the UE's charging data #1, and then sends the charging data #1 to CHF1.
  • the specific process can be referred to the description of S402c in method 400, which will not be repeated here.
  • CHF1 performs billing processing on the UE according to the billing data #1.
  • CHF1 obtains the charging data of the UE, it performs charging processing on the UE.
  • the specific process can be referred to the description of S402 in the method 400, which will not be repeated here.
  • CHF1 sends an initial response message #1 to MEC1 CTF.
  • MEC1 CTF receives the initial response message #1 from CHF1.
  • MEC1 CTF sends a termination request message #1 to CHF1.
  • CHF1 receives the termination request message #1 from MEC1 CTF.
  • MEC1 CTF sends a termination request message to CHF1 to request to terminate the billing resource termination billing request for the MEC service of the user between MEC1 and CHF1.
  • CHF1 sends a termination response message #1 to MEC1 CTF.
  • MEC1 CTF receives the termination response message #1 from CHF1.
  • MEC1 CTF sends a termination request message to CHF1 to request the release of billing resources for the MEC service between MEC1 CTF and CHF1.
  • CHF1 receives the termination request message #1 from SMF1, it releases the billing resources and returns a termination response message.
  • CHF1 sends the charging result #1 to the dedicated CHF.
  • the dedicated CHF receives the charging result #1 from CHF1.
  • S1208 is similar to S403 in method 400 and will not be described in detail here.
  • MEC2 CTF sends an initial request message #3 to CHF2.
  • CHF2 receives the initial request message #3 from MEC2 CTF.
  • MEC2 CTF sends an initial request message #3 to CHF1 to request CHF2 to charge the UE's service on MEC2.
  • the specific implementation method may refer to the description of S404 in method 400, wherein the initial request message #3 in S1209 may correspond to the charging request message #2 in S404, which will not be described in detail here.
  • CHF2 sends an initial request message #4 to the dedicated CHF.
  • the dedicated CHF receives the initial request message #4 from CHF2.
  • CHF2 after receiving the initial request message #3 from CHF1, CHF2 sends an initial request message #4 to the dedicated CHF to request to obtain the charging data #2 of the UE.
  • the specific process can be referred to the description of S405 in the method 400, wherein the initial request message #4 in S1210 can correspond to the charging data request message #2 in S405, which will not be described here.
  • dedicated CHF sends billing data #2 to CHF2.
  • CHF2 receives the billing data #2 from dedicated CHF.
  • the dedicated CHF after receiving the initial request message #4 from CHF2, the dedicated CHF locally queries the UE's charging data #2, and then sends the charging data #2 to CHF2.
  • the specific process can be referred to the description of S406 in method 400, which will not be repeated here.
  • CHF2 performs billing processing on the UE according to the billing data #1.
  • CHF2 obtains the charging data of the UE, it performs charging processing on the UE.
  • the specific process can be referred to the description of S407 in the method 400, which will not be repeated here.
  • CHF2 sends an initial response message #1 to MEC2 CTF.
  • MEC2 CTF receives the initial response message #1 from CHF2.
  • MEC2 CTF sends a termination request message #2 to CHF2.
  • CHF2 receives the termination request message #2 from MEC2 CTF.
  • CHF2 sends a termination response message #2 to MEC2 CTF.
  • MEC2 CTF receives the termination response message #2 from CHF2.
  • CHF2 sends the charging result #2 to the dedicated CHF.
  • the dedicated CHF receives the charging result #2 from CHF2.
  • S1216 is similar to S408 in method 400 and will not be described again for the sake of brevity.
  • the MEC CTF triggers the UE's nearest CHF to provide billing services for the UE.
  • the UE's nearest CHF obtains the user's billing data through a dedicated CHF and performs billing processing on the UE based on the billing data, thereby reducing the cross-zone transmission of a large amount of billing information generated during the billing process, saving network resources and reducing operating costs.
  • FIG. 13 shows an exemplary flow chart of a method 1300 provided in an embodiment of the present application.
  • the billing of MEC2 CTF and CHF2 is first established, and then the billing of MEC1 CTF and CHF1 is terminated.
  • the method 1300 is exemplarily described below in conjunction with the various steps in FIG. 13 .
  • S1301-S1305 are similar to S1201-S1205 in method 1200, and for the sake of brevity, they are not repeated here.
  • MEC1 CTF sends an initial request message #3 to CHF2.
  • CHF2 receives the initial request message #3 from MEC1 CTF.
  • MEC2 CTF sends an initial request message #3 to CHF2 to request CHF2 to charge the UE's service on MEC2.
  • the specific implementation method can refer to the description of S404 in method 400, where the initial request message #3 in S1306 can correspond to the charging request message #2 in S404, which will not be repeated here.
  • S1307-S1310 are similar to S1210-S1213 in method 1200 and are not repeated here.
  • MEC1 CTF sends a termination request message #1 to CHF1.
  • CHF1 receives a termination request message #1 from MEC1 CTF.
  • MEC1 CTF sends a termination request message to CHF1 to request to terminate the billing resources of the user's MEC service between MEC1 and CHF1.
  • timing of MEC2 CTF sending the initial request message #3 to CHF2 is before or after the billing session between MEC1 CTF and CHF1 ends depends on the timing of the user service session switching on the network side.
  • CHF1 sends a termination response message #1 to MEC1 CTF.
  • MEC1 CTF receives the termination response message #1 from CHF1.
  • CHF1 sends the charging result #1 to the dedicated CHF.
  • the dedicated CHF receives the charging result #1 from CHF1.
  • S1313 is similar to S403 in method 400 and will not be described again here.
  • S1314-S1316 are similar to S1214-S1216 in method 1200 and will not be repeated here for the sake of brevity.
  • the MEC CTF triggers the UE's nearest CHF to provide billing services for the UE.
  • the UE's nearest CHF obtains the user's billing data through a dedicated CHF and performs billing processing on the UE based on the billing data, thereby reducing the cross-zone transmission of a large amount of billing information generated during the billing process, saving network resources and reducing operating costs.
  • the embodiments of the present application also provide corresponding devices, which include modules for executing the corresponding methods in the above-mentioned method embodiments.
  • the module can be software, hardware, or a combination of software and hardware. It can be understood that the technical features described in the above-mentioned method embodiments are also applicable to the following device embodiments. Therefore, the contents not described in detail can be referred to the above method embodiments, and for the sake of brevity, they will not be repeated here.
  • FIG14 is a schematic block diagram of a communication device 10 provided in an embodiment of the present application.
  • the device 10 includes a transceiver module 11 and/or a processing module 12.
  • the transceiver module 11 can implement corresponding communication functions, and the processing module 12 is used to perform data processing, or in other words, the transceiver module 11 is used to perform operations related to receiving and sending, and the processing module 12 is used to perform other operations besides receiving and sending.
  • the transceiver module 11 can also be called a communication interface or a communication unit.
  • the device 10 may also include a storage module 13, which can be used to store instructions and/or data.
  • the processing module 12 can read the instructions and/or data in the storage module so that the device implements the actions of the device or network element in the aforementioned method embodiments.
  • the device 10 may correspond to the billing function network element in the above method embodiment (eg, the billing function network element in FIG. 4 , or CHF1 or CHF2 in FIG. 5-FIG 13 ), or a component of the billing function network element (eg, a chip).
  • the billing function network element in the above method embodiment eg, the billing function network element in FIG. 4 , or CHF1 or CHF2 in FIG. 5-FIG 13
  • a component of the billing function network element eg, a chip
  • the device 10 can implement the steps or processes executed by the billing function network element in the above method embodiment, wherein the transceiver module 11 can be used to execute the transceiver-related operations of the billing function network element in the above method embodiment, and the processing module 12 can be used to execute the processing-related operations of the billing function network element in the above method embodiment.
  • the transceiver module 11 is used to receive a charging request message from a charging trigger function network element.
  • the request message is used to request billing for the terminal device;
  • the processing module 12 is used to perform billing processing on the terminal device according to the billing data of the terminal device, and the billing data is received by the billing device from a dedicated billing function network element, and the dedicated billing function network element belongs to a billing system that persistently stores user data of the terminal device.
  • the device 10 may correspond to the dedicated charging function network element in the above method embodiment (for example, the dedicated charging function network element in FIG. 4 , or the dedicated CHF in FIGS. 5 to 13 , or a component (such as a chip) of the dedicated charging function network element.
  • the dedicated charging function network element in the above method embodiment for example, the dedicated charging function network element in FIG. 4 , or the dedicated CHF in FIGS. 5 to 13 , or a component (such as a chip) of the dedicated charging function network element.
  • the device 10 can implement the steps or processes executed by the dedicated billing function network element in the above method embodiment, wherein the transceiver module 11 can be used to execute the operations related to the transmission and reception of the dedicated billing function network element in the above method embodiment, and the processing module 12 can be used to execute the operations related to the processing of the dedicated billing function network element in the above method embodiment.
  • the transceiver module 11 is used to receive a billing data request message from a billing function network element, where the billing data request message is used to request billing data of a terminal device, and the dedicated billing function network element belongs to a billing system that persistently stores user data of the terminal device; and to send the billing data to the billing function network element, where the billing data is used to perform billing processing on the terminal device.
  • the device 10 may correspond to the billing trigger function network element in the above method embodiment (for example, the billing trigger function network element in Figure 4, or the SMF in Figures 5 to 10 (such as SMF1 and SMF2 in Figure 5 or 8, SMF2 and SMF3 in Figure 6 or 9, SMF3 and SMF4 in Figure 7 or 10), or the AMF in Figure 11 (including AMF1 and AMF2), or the MEC CTF in Figure 12 or 13 (including MEC1 CTF and MEC2 CTF), or a component of the billing trigger function network element (such as a chip).
  • the device 10 can implement the steps or processes executed by the billing trigger function network element in the above method embodiment, wherein the transceiver module 11 can be used to execute the transceiver-related operations of the billing trigger function network element in the above method embodiment, and the processing module 12 can be used to execute the processing-related operations of the billing trigger function network element in the above method embodiment.
  • the processing module 12 is used to obtain the address information of the billing function network element based on the information of the billing trigger function network element and/or the location information of the terminal device; the transceiver module 11 is used to send a billing request message to the billing function network element, and the billing request message is used to request the billing function network element to bill the terminal device.
  • module here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a combined logic circuit and/or other suitable components that support the described functions.
  • ASIC application specific integrated circuit
  • processor such as a shared processor, a dedicated processor or a group processor, etc.
  • memory for executing one or more software or firmware programs, a combined logic circuit and/or other suitable components that support the described functions.
  • the device 10 can be specifically the billing function network element in the above-mentioned embodiment, and can be used to execute the various processes and/or steps corresponding to the billing function network element in the above-mentioned method embodiments; or, the device 10 can be specifically the billing trigger function network element in the above-mentioned embodiment, and can be used to execute the various processes and/or steps corresponding to the billing trigger function network element in the above-mentioned method embodiments. To avoid repetition, it will not be repeated here.
  • the device 10 of each of the above schemes has the function of implementing the corresponding steps performed by the device (such as a billing function network element, or a billing trigger function network element) in the above method.
  • This function can be implemented by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver module can be replaced by a transceiver (for example, the sending unit in the transceiver module can be replaced by a transmitter, and the receiving unit in the transceiver module can be replaced by a receiver), and other units, such as processing modules, can be replaced by processors to respectively perform the transceiver operations and related processing operations in each method embodiment.
  • the transceiver module 11 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing module may be a processing circuit.
  • FIG15 is a schematic diagram of another communication device 20 provided in an embodiment of the present application.
  • the device 20 includes a processor 21, which is used to perform operations related to processing in the above method embodiments.
  • the processor 21 is one or more.
  • the device 20 also includes a transceiver 22, which is used to receive and/or send signals.
  • the processor 21 is used to control the transceiver 22 to receive and/or send signals.
  • the transceiver 22 is one or more.
  • the device 20 further includes a memory 23, which is used to store computer programs or instructions and/or data.
  • the memory 23 can be integrated with the processor 21, or can be separately provided, and the processor 21 can read the computer program or instructions stored in the memory 22 to execute the methods in the above method embodiments.
  • the memory 23 is one or more.
  • the device 20 is used to implement the operations performed by the charging function network element in each of the above method embodiments.
  • the device 20 is used to implement the operations performed by the charging trigger function network element in the above method embodiments.
  • processors mentioned 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, discrete gate or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.
  • the memory mentioned in the embodiments of the present application may be a volatile memory and/or a non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.
  • the volatile memory may be a random access memory (RAM).
  • a RAM may be used as an external cache.
  • RAM includes the following forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced SDRAM
  • SLDRAM synchronous link DRAM
  • DR RAM direct rambus RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.
  • memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.
  • FIG16 is a schematic diagram of a chip system 30 provided in an embodiment of the present application.
  • the chip system 30 (or also referred to as a processing system) includes a logic circuit 31 and an input/output interface 32.
  • the logic circuit 31 can be a processing circuit in the chip system 30.
  • the logic circuit 31 can be coupled to the storage unit and call the instructions in the storage unit so that the chip system 30 can implement the methods and functions of each embodiment of the present application.
  • the input/output interface 32 can be an input/output circuit in the chip system 30, outputting information processed by the chip system 30, or inputting data or signaling information to be processed into the chip system 30 for processing.
  • the chip system 30 is used to implement the operations performed by the charging function network element in the above various method embodiments.
  • the logic circuit 31 is used to implement the processing-related operations performed by the billing function network element in the above method embodiments, such as the billing function network element in the embodiment shown in Figure 4, or the processing-related operations performed by the CHF in Figures 5 to 13;
  • the input/output interface 32 is used to implement the sending and/or receiving-related operations performed by the billing function network element in the above method embodiments, such as the sending and/or receiving-related operations performed by the billing function network element in the embodiment shown in Figure 4 or the CHF in Figures 5 to 13.
  • the chip system 30 is used to implement the operations performed by the dedicated charging function network element in the above various method embodiments.
  • the logic circuit 31 is used to implement the processing-related operations performed by the dedicated billing function network element in the above method embodiments, such as the dedicated billing function network element in the embodiment shown in Figure 4, or the processing-related operations performed by the dedicated CHF in Figures 5 to 13;
  • the input/output interface 32 is used to implement the sending and/or receiving-related operations performed by the billing function network element in the above method embodiments, such as the sending and/or receiving-related operations performed by the billing function network element in the embodiment shown in Figure 4 or the dedicated CHF in Figures 5 to 13.
  • the chip system 30 is used to implement the operations performed by the charging trigger function network element in the above method embodiments.
  • the logic circuit 31 is used to implement the processing-related operations performed by the billing trigger function network element in the above method embodiments, such as the billing trigger function network element in the embodiment shown in Figure 4, or the SMF in Figures 5 to 10, or the AMF in Figures 11 to 13, or the MEC CTF in Figures 14 to 16;
  • the input/output interface 32 is used to implement the sending and/or receiving-related operations performed by the billing trigger function network element in the above method embodiments, such as the billing trigger function network element in the embodiment shown in Figure 4, or the SMF in Figures 5 to 10, or the AMF in Figures 11 to 13, or the MEC CTF in Figures 14 to 16.
  • An embodiment of the present application also provides a computer-readable storage medium on which computer instructions for implementing the methods executed by the device in the above-mentioned method embodiments are stored.
  • the computer when the computer program is executed by a computer, the computer can implement the method executed by the charging function network element in each embodiment of the above method.
  • the computer when the computer program is executed by a computer, the computer can implement the method executed by the charging trigger function network element in each embodiment of the above method.
  • the present application also provides a computer program product, which includes instructions, which when executed by a computer, implement the above methods.
  • the method is executed by a device (such as a charging function network element, or a charging trigger function network element).
  • An embodiment of the present application also provides a communication system, including the aforementioned billing function network element and billing trigger function network element.
  • the disclosed devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer may be a personal computer, a server, or a billing trigger function network element, etc.
  • the computer instructions 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 instructions may be transmitted from one website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center.
  • the computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)).
  • the aforementioned available medium includes, but is not limited to, various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Charge And Discharge Circuits For Batteries Or The Like (AREA)

Abstract

本申请提供了一种计费方法、装置和系统，应用于融合计费领域，该方法包括：计费功能网元接收来自计费触发功能网元的计费请求消息之后，根据终端设备的计费数据对该终端设备进行计费，其中，该计费请求消息用于请求对该终端设备进行计费，该计费数据是该计费功能网元从专用计费功能网元接收到的，该专用计费功能网元属于持久化存储该该终端设备的用户数据的计费系统。通过上述方案，可以减少计费过程产生的大量计费信息的跨区传输，降低信令网压力，提高网络韧性。

Description

计费方法和装置
本申请要求在2022年12月16日提交中国国家知识产权局、申请号为202211627897.1的中国专利申请的优先权，发明名称为“计费方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种计费方法和装置。
背景技术
第五代(5th generation，5G)网络中，第三代合作伙伴计划(3rd generation partnership project，3GPP)引进了融合计费架构：核心网采用统一接口与融合计费系统通信，计费系统根据用户及业务需求选择在线计费模式和/或离线计费模式，例如，对用户使用5G低时延切片所产生的流量采用离线计费模式，而其余流量采用在线计费模式。
在通过融合计费架构对用户进行计费的场景下，需要由用户的归属地计费功能网元(home charging function，H-CHF)对用户进行计费处理。然而，如果用户的位置发生了变化，可能需要频繁地跨区域传输终端设备的计费信息到H-CHF，因此需要消耗较多的网络资源，对网络的可靠性要求比较高，从而极大增加了运营成本。
因此，如何对用户进行计费处理，以节省网络资源，是当前需要考虑的问题。
发明内容
本申请提供了一种计费方法和装置，可以节省网络资源，降低运营成本。
第一方面，提供了一种计费方法，该方法可以由计费功能网元执行，也可以由计费功能网元的组成部件(如芯片或电路等)执行。为了方便，这里以计费功能网元执行为例进行说明。
该计费方法包括：计费功能网元接收来自计费触发功能网元的计费请求消息，该计费请求消息用于请求对终端设备进行计费；该计费功能网元根据该终端设备的计费数据对该终端设备进行计费处理，该计费数据是该计费功能网元从专用计费功能网元接收到的，该专用计费功能网元属于持久化存储该终端设备的用户数据的计费系统。
基于上述方案，计费功能网元在接收到来自计费触发功能网元的计费请求消息之后，根据从专用计费功能网元获取到的计费数据，对终端设备进行计费处理。通过上述方案可以减少计费过程产生的大量的计费信息的跨区传输，从而节省网络资源，降低运营成本。
例如，当网络被划分为多个区域(如：中国的按照省份部署、欧洲的一网跨多国、沿海国家的运营商网络覆盖多个岛屿等)，需要在多个区域部署多套核心网和计费系统，如果采用归属地计费系统对终端设备进行计费的话，在终端设备移动到归属区域以外的区域的情况下，需要将终端设备实时产生的大量计费信息(如话单等信息)路由到终端设备的专有计费系统，计费信息的传输会增加信令网压力和运营成本，浪费大量网络资源。而上述方案采用终端设备就近的计费功能网元(即接收到计费请求消息的计费功能网元)对终端设备进行计费，可以节省网络资源，并且可以降低计费网络线路出现故障时对用户业务使用造成的影响。
结合第一方面，在第一方面的某些实现方式中，在该计费功能网元根据该终端设备的计费数据对该终端设备进行计费处理之前，该方法还包括：该计费功能网元向该专用计费功能网元发送计费数据请求消息；该计费功能网元接收来自该专用计费功能网元的该计费数据。
基于上述方案，计费功能可以向专用计费功能网元请求终端设备的计费数据，以便对该终端设备进行计费处理。也就是说，上述方案采用终端设备的专用计费功能网元维护终端设备的计费数据，从而可以更加方便地对终端设备的计费数据进行维护和更新，在终端设备的服务计费功能网元发生切换的情况下，终端设备的服务计费功能网元可以直接从专用计费功能网元获取用于进行计费的计费数据即可，而 不需要迁移所有的用户数据，从而可以节省网络资源。
结合第一方面，在第一方面的某些实现方式中，该计费功能网元向该专用计费功能网元发送计费数据请求消息，包括：该计费功能网元在确定本地存储中没有该计费数据的情况下，向该专用计费功能网元发送该计费数据请求消息。
基于上述方案，计费功能网元在向专用计费功能网元请求获取计费数据之前，可以先判断本地存储中是否存有该终端设备的计费数据，如果没有的话，才向专用计费功能网元发送计费数据请求消息，从而可以在一些情况下节省网络资源。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：该计费功能网元向网络存储功能网元发送查询请求消息，该查询请求消息包括该终端设备的标识，该查询请求消息用于请求查询该终端设备对应的该专用计费功能网元；该计费功能网元接收来自该网络存储功能网元的该专用计费功能网元的地址信息；该计费功能网元向该专用计费功能网元发送计费数据请求消息，包括：该计费功能网元根据该地址信息向该专用计费功能网元发送计费数据请求消息。
基于上述方案，计费功能网元可以向网络存储功能网元查询专用计费功能网元的地址信息，以便可以从专用计费功能网元获取终端设备的计费数据，从而可以根据终端设备计费数据对该终端设备进行计费处理，避免了将计费过程产生的大量的计费数据跨区传输到拜访地计费功能网元，从而节省网络资源，降低运营成本。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：该计费功能网元从该计费请求消息中获取该专用计费功能网元的地址信息；该计费功能网元向该专用计费功能网元发送计费数据请求消息，包括：该计费功能网元根据该地址信息向该专用计费功能网元发送计费数据请求消息。
基于上述方案，计费触发功能网元还可以将专用计费功能网元的地址信息携带在计费请求消息中，在这种情况下，计费功能网元可以直接从该计费请求消息中获取该专用计费功能网元的地址信息，因此计费功能网元在确定向专用计费功能网元获取终端设备的用户数据的情况下，可以直接向专用计费功能网元发送计费请求消息，从而可以减少时延。
结合第一方面，在第一方面的某些实现方式中，该计费功能网元获取该终端设备的计费数据，包括：该计费功能网元在本地存储中获取该终端设备的计费数据。
基于上述方案，如果计费功能网元本地存储该该终端设备的计费数据，例如计费功能网元提前从专用计费功能网元获取了该终端设备的计费数据，则计费功能网元可以直接从本地存储中获取该终端设备的计费数据，而不需要再从专用计费功能网元获取，从而可以节省网络资源。
结合第一方面，在第一方面的某些实现方式中，在该计费功能网元根据该终端设备的计费数据对该终端设备进行计费处理之后，该方法还包括：该计费功能网元向该专用计费功能网元发送计费结果，该计费结果是该计费功能网元对该终端设备进行计费处理之后得到的数据。
基于上述方案，计费功能网元在对终端设备执行计费处理之后，可以将计费结果发送给专用计费功能网元，以便专用计费功能网元可以更新本地维护的终端设备的计费数据，避免因计费数据没有更新所带来的问题，如由于计费数据没有更新导致专用计费功能网元为终端设备的服务计费功能网元分配的流量大于用户套餐的剩余流量。
第二方面，提供了一种计费方法，该方法可以由专用计费功能网元执行，也可以由专用计费功能网元的组成部件(如芯片或电路等)执行。为了方便，这里以专用计费功能网元执行为例进行说明。
该计费方法包括：专用计费功能网元接收来自计费功能网元的计费数据请求消息，该计费数据请求消息用于请求获取终端设备的计费数据，该专属计费功能网元属于持久化存储该终端设备的用户数据的计费系统；响应于该计费数据请求消息，该专用计费功能网元向该计费功能网元发送该计费数据，该计费数据用于对该终端设备进行计费处理。
基于上述方案，专用计费功能网元可以将用于对终端设备进行计费处理的计费数据，发送给计费功能网元，以便该计费功能网元可以直接对终端设备进行计费处理，这样就可以减少计费过程产生的大量的计费信息的跨区传输，从而节省网络资源，降低运营成本。
结合第二方面，在第二方面的某些实现方式中，在该专用计费功能网元向该计费功能网元发送终端设备的计费数据之后，该方法还包括：该专用计费功能网元接收来自其他计费功能网元的第一计费结果，该第一计费结果为该其他计费功能网元对该终端设备进行计费处理之后得到的数据，该其他计费功能网元是在该计费功能网元之前为该终端设备提供计费服务的网元；该专用计费功能网元根据该第一计费结 果，判断是否需要向该计费功能网元更新该终端设备的计费数据；在需要向该计费功能网元更新该终端设备的计费数据的情况下，该专用计费功能网元向该计费功能网元发送更新后的计费数据。
基于上述方案，如果专用计费功能网元在向计费功能网元发送了终端设备的计费数据之后，又从其他计费功能网元接收到了第一计费结果，则专用计费功能网元可以判断是否需要向计费功能网元更新计费数据，例如，专用计费功能网元根据第一计费结果更新终端设备的用户数据，如果更新后的用户数据显示用户的套餐余量小于专用计费功能网元通过计费数据分配给计费功能网元的流量，则专用计费功能网元确定需要向计费功能网元更新终端设备的计费数据。在这种情况下，专用计费功能网元向该计费功能网元发送更新后的计费数据，避免因计费数据没有更新所带来的问题，如由于计费数据没有更新导致用户使用的流量超过了套餐中的流量。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该专用计费功能网元记录该计费功能网元是当前为该终端设备提供计费服务的网元。
基于上述方案，专用计费功能网元可以记录计费功能网元是当前为终端设备提供计费服务的网元，或者说，专用计费功能网元保存终端设备当前的服务计费功能网元的信息(即计费功能网元的信息)。这样专用计费功能网元便可以确定终端设备当前的服务计费功能网元是谁，以便后续可以与终端设备的服务计费功能网元进行交互以为终端设备提供服务。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该专用计费功能网元接收查询请求消息，该终端设备的专用计费功能网元的查询请求，该查询请求消息包括携带该终端设备标识，该查询请求消息用于请求查询当前为该终端设备提供计费服务的网元；该专用计费功能网元根据该记录返回该终端设备的专用计费功能网元的地址信息。
基于上述方案，其他网元可以通过专用计费功能网元查询当前为终端设备提供计费服务的网元，以便通过该计费功能网元为终端设备提供相应的服务。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该专用计费功能网元接收来自该计费功能网元的计费结果，该计费结果为该计费功能网元对该终端设备进行计费处理之后得到的数据；该专用计费功能网元根据该计费结果更新该计费数据。
基于上述方案，计费功能网元在对终端设备执行计费处理之后，可以将计费结果发送给专用计费功能网元，以便专用计费功能网元可以更新本地维护的终端设备的计费数据，避免因计费数据没有更新所带来的问题，如由于计费数据没有更新导致专用计费功能网元为终端设备的服务计费功能网元分配的流量大于用户套餐的剩余流量。
第三方面，提供了一种计费方法，该方法可以由计费触发功能网元执行，也可以由计费触发功能网元的组成部件(如芯片或电路等)执行。为了方便，这里以专用计费功能网元执行为例进行说明。
该计费方法包括：计费触发功能网元根据该计费触发功能网元的信息和/或终端设备的位置信息获取该计费功能网元的地址信息；该计费触发功能网元根据该地址信息，向该计费功能网元发送计费请求消息，该计费请求消息用于请求该计费功能网元对该终端设备进行计费。
基于上述方案，计费触发功能网元请求与该计费触发功能网元的信息和/或终端设备的位置信息对应的计费功能网元对该终端设备进行计费处理，即该计费触发功能网元触发终端设备就近的计费功能网元对该终端设备进行计费处理，从而可以减少计费过程产生的大量的计费数据的跨区传输，从而节省网络资源，降低运营成本。
结合第三方面，在第三方面的某些实现方式中，该计费触发功能网元根据该计费触发功能网元的信息和/或终端设备的位置信息获取该计费功能网元的地址信息，包括：该计费触发功能网元向网络存储功能网元发送查询请求消息，该查询请求消息用于请求获取用于对终端设备执行计费处理的候选计费功能网元的地址信息，该查询请求消息包括该终端设备的位置信息和/或该计费触发功能网元的信息；该计费触发功能网元接收来自该存储功能网元的该计费功能网元的地址信息。
基于上述方案，计费触发功能网元可以通过网络存储功能网元查询与该计费触发功能网元的信息和/或终端设备的位置信息对应的计费功能网元的地址信息，以便触发该计费功能网元对该终端设备进行计费处理，从而可以减少计费过程产生的大量的计费数据的跨区传输，从而节省网络资源，降低运营成本。
结合第三方面，在第三方面的某些实现方式中，该计费触发功能网元根据该计费触发功能网元的信息和/或终端设备的位置信息获取该计费功能网元的地址信息，包括：该计费触发功能网元根据该终端设备的位置信息和/或该计费触发功能网元的信息，在本地配置信息中确定与该终端设备的位置信息和/或该 计费触发功能网元的信息对应的该计费功能网元的地址信息。
基于上述方案，计费触发功能网元如果预配置有与该计费触发功能网元的信息和/或终端设备的位置信息对应的计费功能网元的地址信息，则可以直接从本地配置信息中获取该计费功能网元的地址信息，以便触发该计费功能网元对该终端设备进行计费处理，从而可以减少计费过程产生的大量的计费数据的跨区传输，从而节省网络资源，降低运营成本。
结合第三方面，在第三方面的某些实现方式中，该计费请求消息包括专用计费功能网元的地址信息，该专用计费功能网元属于持久化存储该终端设备的用户数据的计费系统。
基于上述方案，计费触发功能网元可以将专用计费功能网元的地址信息携带在计费请求消息中，这样计费功能网元便可以直接从该计费请求消息中获取该专用计费功能网元的地址信息，而不需要通过其他流程获取计费计费功能网元的地址信息，从而可以降低时延。
第四方面，提供了一种计费方法，该方法包括：计费触发功能网元向计费功能网元发送计费请求消息，该计费请求消息用于请求对终端设备进行计费处理；该计费功能网元接收来自该计费触发功能网元的该计费请求消息；该计费功能网元根据该终端设备的计费数据对该终端设备进行计费处理，该计费数据是该计费功能网元从专用计费功能网元接收到的，该专用计费功能网元属于持久化存储该终端设备的用户数据的计费系统。
结合第四方面，在第四方面的某些实现方式中，在该计费功能网元根据该终端设备的计费数据对该终端设备进行计费处理之前，该方法还包括：该计费功能网元向该专用计费功能网元发送计费数据请求消息；响应于该计费数据请求消息，该专用计费功能网元向该计费功能网元发送该计费数据；该计费功能网元接收来自该专用计费功能网元的该计费数据。
结合第四方面，在第四方面的某些实现方式中，该计费功能网元向该专用计费功能网元发送计费数据请求消息，包括：该计费功能网元在确定本地存储中没有该计费数据的情况下，向该专用计费功能网元发送该计费数据请求消息。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：该计费功能网元获取该专用计费功能网元的地址信息；该计费功能网元向该专用计费功能网元发送计费数据请求消息，包括：该计费功能网元根据该地址信息向该专用计费功能网元发送计费数据请求消息。
结合第四方面，在第四方面的某些实现方式中，该计费功能网元获取该专用计费功能网元的地址信息，包括：该计费功能网元向网络存储功能网元发送查询请求消息，该查询请求消息包括该终端设备的标识，该查询请求消息用于请求查询该终端设备对应的该专用计费功能网元；该网络存储功能网元根据该终端设备的标识确定该专用计费功能网元；该网络存储功能网元向该计费功能网元发送该专用计费功能网元的地址信息；该计费功能网元接收来自该网络存储功能网元的该专用计费功能网元的地址信息。
结合第四方面，在第四方面的某些实现方式中，该计费功能网元获取该专用计费功能网元的地址信息，包括：该计费功能网元从该计费请求消息中获取该专用计费功能网元的地址信息。
结合第四方面，在第四方面的某些实现方式中，该计费功能网元获取该终端设备的计费数据，包括：该计费功能网元在本地存储中获取该终端设备的计费数据。
结合第四方面，在第四方面的某些实现方式中，在该计费功能网元根据该终端设备的计费数据对该终端设备进行计费处理之后，该方法还包括：该计费功能网元向该专用计费功能网元发送计费结果，该计费结果是该计费功能网元对该终端设备进行计费处理之后得到的数据；该专用计费功能网元接收来自该计费功能网元的该计费结果。
结合第四方面，在第四方面的某些实现方式中，在该专用计费功能网元向该计费功能网元发送终端设备的计费数据之后，该方法还包括：该专用计费功能网元接收来自其他计费功能网元的第一计费结果，该第一计费结果为该其他计费功能网元对该终端设备进行计费处理之后得到的数据，该其他计费功能网元是在该计费功能网元之前为该终端设备提供计费服务的网元；该专用计费功能网元根据该第一计费结果，判断是否需要向该计费功能网元更新该终端设备的计费数据；在需要向该计费功能网元更新该终端设备的计费数据的情况下，该专用计费功能网元向该计费功能网元发送更新后的计费数据；该计费功能网元接收来自该专用功能网元的该更新后的计费数据。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：该专用计费功能网元记录该计费功能网元是当前为该终端设备提供计费服务的网元。
第五方面，提供了一种计费装置，该计费装置包括：收发模块，用于接收来自计费触发功能网元的 计费请求消息，该计费请求消息用于请求对终端设备进行计费；处理模块，用于根据该终端设备的计费数据对该终端设备进行计费处理，该计费数据是该计费装置从专用计费功能网元接收到的，该专用计费功能网元属于持久化存储该终端设备的用户数据的计费系统。
结合第五方面，在第五方面的某些实现方式中，该收发模块，还用于向该专用计费功能网元发送计费数据请求消息；以及，接收来自该专用计费功能网元的该计费数据。
结合第五方面，在第五方面的某些实现方式中，该处理模块，具体用于在确定本地存储中没有该计费数据的情况下，通过该收发模块向该专用计费功能网元发送该计费数据请求消息。
结合第五方面，在第五方面的某些实现方式中，该处理模块，还用于获取该专用计费功能网元的地址信息；该处理模块，具体用于根据该地址信息向该专用计费功能网元发送计费数据请求消息。
结合第五方面，在第五方面的某些实现方式中，该收发模块，具体用于向网络存储功能网元发送查询请求消息，该查询请求消息包括该终端设备的标识，该查询请求消息用于请求查询该终端设备对应的该专用计费功能网元；以及，接收来自该网络存储功能网元的该专用计费功能网元的地址信息。
结合第五方面，在第五方面的某些实现方式中，该收发模块，具体用于从该计费请求消息中获取该专用计费功能网元的地址信息。
结合第五方面，在第五方面的某些实现方式中，该处理模块，具体用于在本地存储中获取该终端设备的计费数据。
结合第五方面，在第五方面的某些实现方式中，该收发模块，还用于向该专用计费功能网元发送计费结果，该计费结果是该计费功能网元对该终端设备进行计费处理之后得到的数据。
第六方面，提供了一种计费装置，该计费装置包括：收发模块，用于接收来自计费功能网元的计费数据请求消息，该计费数据请求消息用于请求获取终端设备的计费数据，该专属计费功能网元属于持久化存储该终端设备的用户数据的计费系统；以及，向该计费功能网元发送该计费数据，该计费数据用于对该终端设备进行计费处理。
结合第六方面，在第六方面的某些实现方式中，该收发模块，还用于接收来自其他计费功能网元的第一计费结果，该第一计费结果为该其他计费功能网元对该终端设备进行计费处理之后得到的数据，该其他计费功能网元是在该计费功能网元之前为该终端设备提供计费服务的网元；该计费装置还包括处理模块，用于根据该第一计费结果，判断是否需要向该计费功能网元更新该终端设备的计费数据；该处理模块，还用于在需要向该计费功能网元更新该终端设备的计费数据的情况下，通过该收发模块向该计费功能网元发送更新后的计费数据。
结合第六方面，在第六方面的某些实现方式中，该处理模块，还用于记录该计费功能网元是当前为该终端设备提供计费服务的网元。
结合第六方面，在第六方面的某些实现方式中，该收发模块，还用于接收来自该计费功能网元的计费结果，该计费结果为该计费功能网元对该终端设备进行计费处理之后得到的数据。
第七方面，提供了一种计费装置，该计费装置包括：处理模块，用于根据该计费触发功能网元的信息和/或终端设备的位置信息获取该计费功能网元的地址信息；收发模块，用于根据该地址信息向该计费功能网元发送计费请求消息，该计费请求消息用于请求该计费功能网元对该终端设备进行计费。
结合第七方面，在第七方面的某些实现方式中，该收发模块，具体用于向网络存储功能网元发送查询请求消息，该查询请求消息用于请求获取用于对终端设备执行计费处理的候选计费功能网元的地址信息，该查询请求消息包括该终端设备的位置信息和/或该计费触发功能网元的信息；以及，接收来自该存储功能网元的该计费功能网元的地址信息。
结合第七方面，在第七方面的某些实现方式中，该处理模块，具体用于根据该终端设备的位置信息和/或该计费触发功能网元的信息，在本地配置信息中确定与该终端设备的位置信息和/或该计费触发功能网元的信息对应的该计费功能网元的地址信息。
结合第七方面，在第七方面的某些实现方式中，该计费请求消息包括专用计费功能网元的地址信息，该专用计费功能网元属于持久化存储该终端设备的用户数据的计费系统。
第八方面，提供了一种通信装置，该装置可以是计费功能网元，还可以是用于计费功能网元的芯片。该装置具有实现上述第一方面所实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第九方面，提供了一种通信装置，该装置可以是专用计费功能网元，还可以是用于专用计费功能网 元的芯片。该装置具有实现上述第二方面所实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十方面，提供了一种通信装置，该装置可以是计费触发功能网元，还可以是用于计费触发功能网元的芯片。该装置具有实现上述第三方面所实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十一方面，提供一种通信装置，该装置包括：存储器，用于存储程序；处理器，用于执行存储器存储的程序，当存储器存储的程序被执行时，处理器用于执行上述第一方面至第三方面中任一方面提供的方法。
第十二方面，本申请提供一种处理器，用于执行上述各方面提供的方法。在执行这些方法的过程中，上述方法中有关发送上述信息和获取/接收上述信息的过程，可以理解为由处理器输出上述信息的过程，以及处理器接收输入的上述信息的过程。在输出上述信息时，处理器将该上述信息输出给收发器，以便由收发器进行发射。该上述信息在由处理器输出之后，还可能需要进行其他的处理，然后再到达收发器。类似的，处理器接收输入的上述信息时，收发器获取/接收该上述信息，并将其输入处理器。更进一步的，在收发器收到该上述信息之后，该上述信息可能需要进行其他的处理，然后再输入处理器。
基于上述原理，举例来说，前述方法中提及的接收请求消息可以理解为处理器接收输入的信息。
对于处理器所涉及的发射、发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则均可以更加一般性的理解为处理器输出和接收、输入等操作，而不是直接由射频电路和天线所进行的发射、发送和接收操作。
在实现过程中，上述处理器可以是专门用于执行这些方法的处理器，也可以是执行存储器中的计算机指令来执行这些方法的处理器，例如通用处理器。上述存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
第十三方面，提供一种计算机可读存储介质，该计算机可读介质存储用于设备执行的程序代码，该程序代码包括用于执行上述第一方面至第三方面中任一方面提供的方法。
第十四方面，提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面至第三方面中任一方面提供的方法。
第十五方面，提供一种芯片，该芯片包括处理器与通信接口，该处理器通过该通信接口读取存储器上存储的指令，执行上述第一方面至第三方面中任一方面提供的方法。
可选地，作为一种实现方式，该芯片还可以包括存储器，该存储器中存储有指令，该处理器用于执行该存储器上存储的指令，当该指令被执行时，该处理器用于执行上述第一方面至第三方面中任一方面提供的方法。
第十六方面，提供了一种通信系统，该通信系统包括用于执行如第一方面所示方法的计费功能网元，以及用于执行如第二方面所示方法的专用计费功能网元，以及用于执行如第三方面所示方法的计费触发功能网元。
附图说明
图1是适用于本申请实施例的一种计费架构100的示意图。
图2是适用于本申请实施例的一种网络架构200的示意图。
图3的(a)是适用于本申请实施例的一种系统架构300(a)的示意图。
图3的(b)是适用于本申请实施例的一种系统架构300(b)的示意图。
图4是本申请实施例提供的方法400的示例性流程图。
图5是本申请实施例提供的方法500的示例性流程图。
图6是本申请实施例提供的方法600的示例性流程图。
图7是本申请实施例提供的方法700的示例性流程图。
图8是本申请实施例提供的方法800的示例性流程图。
图9是本申请实施例提供的方法900的示例性流程图。
图10是本申请实施例提供的方法1000的示例性流程图。
图11是本申请实施例提供的方法1100的示例性流程图。
图12是本申请实施例提供的方法1200的示例性流程图。
图13是本申请实施例提供的方法1300的示例性流程图。
图14是本申请一个实施例提供的通信装置的示意性框图。
图15是本申请另一个实施例提供的通信装置的示意性框图。
图16是本申请又一个实施例提供的通信装置的示意性框图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。
为了便于理解本申请实施例，首先做出以下几点说明。
1、在本申请实施例的描述中，除非另有说明，“多个”的含义是两个或两个以上。
2、在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
3、在本申请中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的范围。本申请中所涉及的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。例如，本申请的说明书和权利要求书及附图中的术语“第一”、“第二”、“第三”、“第四”以及其他各种术语标号等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。
4、术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
5、在本申请中，“用于指示”可以理解为“使能”，“使能”可以包括直接使能和间接使能。当描述某一信息用于使能A时，可以包括该信息直接使能A或间接使能A，而并不代表该信息中一定携带有A。
将信息所使能的信息称为待使能信息，则具体实现过程中，对待使能信息进行使能的方式有很多种，例如但不限于，可以直接使能待使能信息，如待使能信息本身或者该待使能信息的索引等。也可以通过使能其他信息来间接使能待使能信息，其中该其他信息与待使能信息之间存在关联关系。还可以仅仅使能待使能信息的一部分，而待使能信息的其他部分则是已知的或者提前约定的。例如，还可以借助预先约定(例如协议规定)的各个信息的排列顺序来实现对特定信息的使能，从而在一定程度上降低使能开销。同时，还可以识别各个信息的通用部分并统一使能，以降低单独使能同样的信息而带来的使能开销。
6、在本申请中，“预配置”可包括预先定义，例如，协议定义。其中，“预先定义”可以通过在设备(例如，包括各个网元)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。
7、本申请实施例中涉及的“存储”或“保存”，可以是指的保存在一个或者多个存储器中。所述一个或者多个存储器，可以是单独的设置，也可以是集成在编码器或者译码器，处理器、或通信装置中。所述一个或者多个存储器，也可以是一部分单独设置，一部分集成在译码器、处理器、或通信装置中。存储器的类型可以是任意形式的存储介质，本申请并不对此限定。
8、本申请实施例中涉及的“协议”可以是指通信领域的标准协议，例如可以包括4G/5G协议、新空口(new radio，NR)协议以及应用于未来的通信系统中的相关协议，本申请对此不做限定。
9、本申请说明书附图部分的示意图中的虚线所示的箭头或方框表示可选的步骤或可选的模块。
在4G网络中，在线计费和离线计费采用了不同的架构，用户需要在开户时选定付费类型。而在5G网络中，为了支持5G业务的开展，第三代合作伙伴计划(3rd generation partnership project，3GPP)引进了在线计费和离线计费融合的计费架构。
下面结合图1举例说明本申请实施例适用的一种计费架构100。
在计费架构100中，核心网(core network，CN)域的各个网络功能(network function，NF)采用统一的服务化接口Nchf与融合计费系统(converged charging system，CCS)连接。CN域中的CTF可以通过Nchf接口触发CCS对用户提供计费服务，CCS根据用户及业务需求来选择在线计费模式或者离线计费模式。
其中，CTF位于业务系统，用于执行业务逻辑或者业务控制(如根据计费系统配额授予，控制业务的放通)，例如，CTF为5G核心网提供数据业务的会话管理功能(session management function，SMF)网元，或者是因特网协议(internet protocol，IP)多媒体子系统(IP multimedia subsystem，IMS)语音业务的IMS应用服务器(application server，AS)，或者是MEC场景下的边缘配置服务器(edge configuration server,ECS)或边缘使能服务器(edge enabler server，EES)或边缘应用服务器(edge application server，EAS)等。
CCS指的是融合了在线计费(online charging)模式和离线计费(offline charging)模式的融合计费系统。CCS可以只提供在线计费功能(实质上是在线计费系统)，或者只提供离线计费功能(实质上是离线计费系统)，或者同时提供在线计费功能和离线计费功能(实质上是融合计费系统)。其中在线计费指的是在会话进行过程中收集计费信息、实时判断是否有足够配额可以通信的授权及计费过程，离线计费指的是通过通信行为产生话单文件进行计费的过程。
CCS包括计费功能(charging function，CHF)、账户余额管理功能(account balance management function，ABMF)、批价功能(rating function，RF)、计费网关功能(charging gateway function，CGF)等。下面对CCS中的各种功能作简单介绍。
(1)CHF：CHF可以通过服务化计费接口，从CTF接收计费请求，该计费请求会携带CTF的配额申请信息、使用量信息等。CHF可以基于接收到的计费请求以及用户业务的相关信息(如用户类型、客户信息、账户余额、业务白/黑名单、账户余额变化趋势、套餐剩余有效期等)，进行计费处理，并向CTF发送计费处理结果，以便CTF调整针对用户业务的计费操作。
(2)ABMF：ABMF用于管理用户的账户余额，包括账户预留、锁定、扣减等。
(3)RF：RF用于根据业务使用请求和用户信息确定需要的资费、价格或使用量。例如，RF接收在线计费功能(online charging function，OCF)提供的计费事件信息，确定OCF网络资源的使用量，并返回批价结果给OCF。
(4)CGF：CGF用于执行如下功能：从CDF实时接收CDR；对CDR进行预处理；CDR的验证、合并和格式化；CDR错误处理；话单持久化存储；话单路由和过滤，即根据话单类型、话单参数、源CDF等过滤条件将话单存储在单独的文件中；CDR文件管理，例如文件创建、文件打开/关闭触发器、文件删除；将CDR文件传到财务域(billing domain，BD)。可以理解的是，每个CCS有配套的BD，BD可以基于从CGF接收到的CDR文件，为UE执行Billing处理。
本申请提供的技术方案可以应用于各种通信系统，例如：第五代(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)移动通信系统等。
下面以5G系统为例，结合图2介绍图1所示的计费架构100中的CN域的一种可能的网络架构图。可以理解的是，图2仅以5G系统为例进行说明，但本申请并不限于此，本申请还可能适用于未来其他网络系统中。
如图2所示，该网络架构例如是第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)协议TS23.501中定义的5G系统(the 5th generation system，5GS)。该网络架构可以分为接入网(access network，AN)和核心网(core network，CN)两部分。其中，接入网可用于实现无线接入有关的功能，核心网包括多个逻辑功能实体。下面对图3中示出的各网元或设备进行简单介绍：
1、用户设备(user equipment，UE)：可以称为终端设备(terminal equipment)、终端装置、接入终端、用户单元、用户站、移动站、移动台(mobile station，MS)、移动终端(mobile terminal，MT)、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备可以是一种向用户提供语音/数据连通性的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例可以为：手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑(如笔记本电脑、掌上电脑等)、移动互联网设备(mobile internet device，MID)、虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家 庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等。
此外，终端设备还可以是物联网(Internet of things，IoT)系统中的终端设备。IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物-物互连的智能化网络。IoT技术可以通过例如窄带(narrow band，NB)技术，做到海量连接，深度覆盖，终端省电。
此外，终端设备还可以包括智能打印机、火车探测器等，主要功能包括收集数据(部分终端设备)、接收网络设备的控制信息与下行数据，并发送电磁波，向网络设备传输上行数据。
应理解，用户设备可以是任何可以接入网络的设备。终端设备与接入网设备之间可以采用某种空口技术相互通信。
可选地，用户设备可以用于充当基站。例如，用户设备可以充当调度实体，其在V2X或D2D等中的用户设备之间提供侧行链路信号。比如，蜂窝电话和汽车利用侧行链路信号彼此通信。蜂窝电话和智能家居设备之间通信，而无需通过基站中继通信信号。
2、(无线)接入网((radio)access network，(R)AN)设备：用于为特定区域的授权用户设备提供入网功能，并能够根据用户设备的级别，业务的需求等使用不同服务质量的传输隧道。
(R)AN能够管理无线资源，为用户设备提供接入服务，进而完成控制信号和用户设备数据在用户设备和核心网之间的转发，(R)AN也可以理解为传统网络中的基站。
示例性地，本申请实施例中的接入网设备可以是用于与用户设备通信的任意一种具有无线收发功能的通信设备。该接入网设备包括但不限为演进型节点B(evolved Node B，eNB)或5G，如，NR，系统中的gNB，或，传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或，分布式单元(distributed unit，DU)等。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。gNB还可以包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB的部分功能。比如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理(physical，PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。由于RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来，因而，在这种架构下，高层信令，如RRC层信令，也可以认为是由DU发送的，或者，由DU+AAU发送的。可以理解的是，接入网设备可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。此外，可以将CU划分为接入网(radio access network，RAN)中的接入网设备，也可以将CU划分为核心网(core network，CN)中的接入网设备，本申请对此不做限定。
3、用户面功能(user plane function，UPF)网元：用于分组路由和转发以及用户面数据的服务质量(quality of service，QoS)处理等。为叙述方便，本申请实施例中，用户面功能网元被简称为“UPF”。
在未来通信系统中，用户面网元仍可以是UPF网元，或者，还可以有其它的名称，本申请不做限定。
4、接入和移动管理功能(access and mobility management function，AMF)网元：接入和移动管理功能网元主要用于移动性管理和接入管理等，可以用于实现MME功能中除会话管理之外的其它功能，例如，接入授权/鉴权等功能。为叙述方便，本申请实施例中，接入和移动管理功能网元被简称为“AMF”。
在未来通信系统中，接入和移动管理网元仍可以是AMF，或者，还可以有其它的名称，本申请不做限定。
5、会话管理功能(session management function，SMF)网元：主要用于会话管理、用户设备的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。为叙述方便，本申请实施例中，会话管理功能网元被简称为“SMF”。
SMF为会话管理网元的一种。在未来通信系统中，会话管理网元仍可以是SMF，或者，还可以有其 它的名称，本申请不做限定。
6、策略控制功能(policy control function，PCF)网元：用于指导网络行为的统一策略框架，为控制面功能网元(例如AMF，SMF等)提供策略规则信息等。
在未来通信系统中，策略控制网元仍可以是PCF网元，或者，还可以有其它的名称，本申请不做限定。
7、网络存储功能(network repository function，NRF)网元：主要提供服务注册、发现和授权，并维护可用的网络功能(network function，NF)实例信息，例如，NRF可以用于保存NF实体以及其提供的服务的描述信息等，另外，NRF还可以实现网络功能和服务的按需配置以及NF之间的互连。
8、应用功能(application function，AF)网元：用于进行应用影响的数据路由，无线接入网络开放功能网元，与策略框架交互进行策略控制等。为叙述方便，本申请实施例中，应用功能网元被简称为“AF”。
在未来通信系统中，应用功能网元仍可以是AF网元，或者，还可以有其它的名称，本申请不做限定。
9、统一数据管理(unified data management，UDM)网元：用于处理UE标识，接入鉴权，注册以及移动性管理等。
在未来通信系统中，统一数据管理仍可以是UDM网元，或者，还可以有其它的名称，本申请不做限定。
10、数据网络(data network，DN)：DN是位于运营商网络之外的网络，运营商网络可以接入多个DN，DN上可部署多种业务，可为终端设备提供数据和/或语音等服务。例如，DN是某智能工厂的私有网络，智能工厂安装在车间的传感器可为终端设备，DN中部署了传感器的控制服务器，控制服务器可为传感器提供服务。传感器可与控制服务器通信，获取控制服务器的指令，根据指令将采集的传感器数据传送给控制服务器等。又例如，DN是某公司的内部办公网络，该公司员工的手机或者电脑可为终端设备，员工的手机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
在图2所示的网络架构中，各网元之间可以通过图中所示的接口通信。如图所示，UE和AMF之间可以通过N1接口进行交互，交互消息例如可以称为N1消息(N1Message)。RAN和AMF之间可以通过N2接口进行交互，N2接口可以用于非接入层(non-access stratum，NAS)消息的发送等。RAN和UPF之间可以通过N3接口进行交互，N3接口可以用于传输用户面的数据等。SMF和UPF之间可以通过N4接口进行交互，N4接口可以用于传输例如N3连接的隧道标识信息，数据缓存指示信息，以及下行数据通知消息等信息。UPF和DN之间可以通过N6接口进行交互，N6接口可以于传输用户面的数据等。其他接口与各网元之间的关系如图2中所示，为了简洁，这里不一一详述。
可以理解的是，图2所示的网络架构中，是以各个网元之间采用点对点接口进行通信为例进行说明的，但本申请不限于此，即各个网元之间还可以采用其他类型的接口(如服务化接口)进行通信。
为了解决背景技术部分提到的问题，如图3的(a)所示，本申请提供了一种通信系统300(a)，该系统300(a)包括计费触发功能网元、计费功能网元和专用计费功能网元。
其中，作为一种可能的示例，该计费触发功能网元，用于向计费功能网元发送计费请求消息，该计费请求消息用于请求对终端设备进行计费处理；该计费功能网元，用于根据该终端设备的计费数据对该终端设备进行计费处理，其中，该计费数据是该计费功能网元从专用计费功能网元接收到的，该专用计费功能网元属于持久化存储该终端设备的用户数据的计费系统。
可选地，该计费功能网元，还用于向该专用计费功能网元发送计费数据请求消息；该专用计费功能网元，还用于根据该计费数据请求消息，向该计费功能网元发送该计费数据；该计费功能网元，还用于接收来自该专用计费功能网元的该计费数据。
示例性地，本申请实施例提供的通信系统中，计费功能网元在接收到来自计费触发功能网元的计费请求消息之后，根据从专用计费功能网元获取到的用户数据，对终端设备进行计费处理，可以减少计费过程产生的大量计费信息的跨区传输，从而节省网络资源，降低运营成本。
应理解，图3的(a)中各网元之间的具体交互过程可以参照图4所示的方法的流程，具体实现方案可以参见方法400的详细说明。
图3的(a)所示的通信系统300(a)可以应用于图1所示的计费架构100中，在这种情况下，通信系统300(a)中的计费功能网元可对应于图1中的CHF，通信系统300(a)中的计费触发功能网元可对应于图1中的CTF。可以理解的是，通信系统300(a)中的专用计费功能网元对应于归属CCS中的CHF。
下面结合图3的(b)举例说明本申请实施例适用的系统架构300(b)。如图3的(b)所示，系统 架构300(b)包括专用CCS和CCS1，可选地，还包括CCS2。
其中，专用CCS(dedicated CCS)为运营商配置的、持久化存储该UE用户数据的计费系统(用户数据包括用户名、签约的套餐、账户余额、账单、话单等)，例如，dedicated CCS为UE的归属公共陆地移动网络(public land mobile network，PLMN)中，UE签约地区的CCS。每个UE对应一个dedicated CCS。
dedicated CCS提供与外部系统(例如客户关系管理(customer relationship management，CRM)系统、充值服务器、账务系统、计费能力开放等)之间的接口，即外部系统可以通过dedicated CCS执行针对UE的相关操作，例如，外部通信系统通过dedicated CCS查询UE的账单，或者，外部通信系统完成UE的充值之后，向dedicated CCS同步UE账户数据。
dedicated CCS包括专用CHF(dedicated CHF)，dedicated CHF用于直接修改和操作持久化的该用户的用户数据。dedicated CHF还用于确定UE的服务CHF(Serving CHF)，以及协调UE的Serving CHF的变化。其中，Serving CHF属于UE的服务CCS(Serving CCS)，UE的Serving CCS指的是当前为UE提供计费服务的CCS。本申请中的专有计费系统指dedicated CCS，也可以指dedicated CCS中的dedicated CHF。
CCS1为除了dedicated CCS以外的UE的候选CCS，其中，候选CCS指的是可以为UE提供计费服务的CCS，或者指的是可能成为UE的serving CCS的CCS，或者指的是UE的归属PLMN内除dedicated CCS以外的的某个CCS。
可以理解的是，本申请不限定UE的候选CCS的数量。也就是说，除dedicated CCS和CCS1以外，UE还可能存在其他一个或多个候选CCS，如CCS2，本申请对此不作限定。
在本申请实施例中，随着UE位置的变化，dedicated CCS、CCS1、CCS2中的任一个都可能成为UE的serving CCS，也就是说，UE的Serving CCS可能会随着UE的位置变化而发生变化。例如，当UE移动到dedicated CCS的覆盖区域(例如从CCS1/CCS2的覆盖区域移动到dedicated CCS的覆盖区域)，dedicated CCS将作为UE的serving CCS；当UE移动到CCS1的覆盖区域(例如从dedicated CCS/CCS2的覆盖区域移动到CCS1的覆盖区域)，CCS1将作为UE的serving CCS；当UE移动到CCS2的覆盖区域(例如从dedicated CCS/CCS1的覆盖区域移动到CCS2的覆盖区域)，CCS2将作为UE的serving CCS。也就是说，本申请实施例中，采用UE就近的CCS作为UE的Serving CCS。
可以理解的是，上述应用于本申请实施例的网络架构仅是一种示例，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例，即本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
还可以理解的是，上述网络架构中列举的网元或设备仅为示例性说明，适用于本申请的网络架构还可以包括其他网元或设备，本申请对此不作限定。
还可以理解的是，上述网元或设备的命名仅为便于区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除在4G网络、5G网络以及未来其它的网络中采用其他命名的可能。例如，在6G网络中，上述各个网元中的部分或全部可以沿用4G/5G中的术语，也可能采用其他名称等。
在本申请实施例中的通信设备包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。该硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。该操作系统可以是任意一种或多种通过进程(Process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。该应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。并且，本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是终端设备或网络设备，或者，是终端设备或网络设备中能够调用程序并执行程序的功能模块。
此外，本申请实施例的各个方面或特征可以通过方法或装置实现，或者通过使用标准编程和/或工程技术的制品实现。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器 件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
以下，以网元之间的交互为例详细说明本申请实施例提供的通信方法。应理解，本申请中的各实施例中术语和步骤可以互相参考。本申请中的方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。
图4示出了本申请实施例提供的方法400的示例性流程图。在方法400中，采用终端设备就近的计费功能网元(即从计费触发功能网元接收到计费请求消息的计费功能网元)为终端设备进行计费，并且由专用计费功能网元维护终端设备的计费数据。下面结合图4中的各个步骤对方法400作示例性说明。
S401，计费触发功能网元#1向计费功能网元#1发送计费请求消息#1。对应地，计费功能网元#1接收来自该计费触发功能网元#1的该计费请求消息#1。
示例性地，终端设备由于位置移动，切换到计费触发功能网元#1后，触发建立与该计费触发功能网元#1之间的业务会话。可以理解的是，对于在线计费的场景，终端设备在结束了与旧的计费功能网元之间的业务会话之后，再触发建立与该计费触发功能网元#1之间的业务会话；对于离线计费场景，终端设备直接触发与该计费触发功能网元#1之间的业务会话。其中，这里所述的旧的计费触发功能网元指的是在计费触发功能网元#1之前为该终端设备提供服务的网元。该计费触发功能网元#1在接收到针对终端设备的业务请求的情况下，向计费功能网元#1发送计费请求消息#1，该计费请求消息#1用于请求对该终端设备进行计费处理。例如，终端设备在移动到计费触发功能网元#1所在网络的覆盖区域的情况下，向计费触发功能网元#1发起注册请求或协议数据单元会话建立请求，计费触发功能网元#1在接收到终端设备的上述请求之后，向计费功能网元#1发送计费请求消息#1。
下面对计费触发功能网元#1向计费功能网元#1发送计费请求消息#1的具体实现方式作示例性说明。
在第一种可能的实现方式中，计费触发功能网元#1通过终端设备的专用计费功能网元向计费功能网元#1发送计费请求消息#1，该专用计费功能网元属于持久化存储该UE的用户数据的计费系统。例如，计费触发功能网元#1查询终端设备对应的专用计费功能网元，然后向该专用计费功能网元发送计费请求消息#1，专用计费功能网元接收到计费请求消息#1之后，查询计费功能网元#1。例如，专用计费功能网元预配置有计费触发功能网元与计费功能网元之间的对应关系(包括计费触发功能网元#1与计费功能网元#1之间的对应关系)，在这种情况下，专用计费功能网元根据预配置的信息确定与计费触发功能网元#1对应的计费功能网元#1。进一步地，专用计费触发功能网元将计费请求消息#1重定向到计费功能网元#1。可选地，在这种实现方式中，计费触发功能网元#1或者专用计费功能网元还可以在计费请求消息#1中携带该专用计费功能网元的地址信息，如专用计费功能网元的互联网协议地址信息，或者是专用计费功能网元的标识信息。
可以理解的是，本申请不限定计费触发功能网元#1查询终端设备对应的专用计费功能网元的具体实现方式。下面给出两种可能的示例。
示例一，计费触发功能网元#1通过网络存储功能网元查询终端设备对应的专用计费功能网元。例如，网络存储功能网元存储有如表1所示的终端设备的标识信息与专用计费功能网元的地址信息之间的关联关系，其中，专用计费功能网元的地址信息为用于确定专用计费功能网元的信息，例如，专用计费功能网元的地址信息可以是专用计费功能网元的标识信息或地址信息。在表1中，“SUPI/GPSI”表示终端设备的标识，“dedicated CHFInfo”表示终端设备对应的专用计费功能网元的地址信息。可以理解的是，网络存储功能网元可能存储一组或多组终端设备的标识信息与专用计费功能网元的地址信息之间的关联关系，本申请对此不作限定。
表1
计费触发功能网元#1可以向网络存储功能网元发送查询请求消息，并在该查询请求消息中携带终端设备的标识(如终端设备的SUPI或GPSI)。网络存储功能网元根据该查询请求消息中携带的终端设备的标识，查询与该终端设备的标识对应的专用计费功能网元，然后将该专用计费功能网元的地址信息返回给计费触发功能网元#1。
示例二，计费功能网元#1根据该终端设备的位置信息和/或该计费触发功能网元#1的信息，在本地配置信息中确定与该终端设备的位置信息和/或该计费触发功能网元#1的信息对应的该专用计费功能网元的地址信息，然后根据该地址信息向专用计费功能网元发送计费请求消息#1。
在第二种可能的实现方式中，计费触发功能网元#1通过专用计费功能网元查询计费功能网元#1的地址信息，然后根据该地址信息向计费功能网元#1发送该计费请求消息#1。其中专用计费功能网元确定计费功能网元#1的地址信息的实现方式可参考第一种可能的实现方式中的示例，这里不再赘述。可选地，在这种实现方式中，计费触发功能网元#1还可以在计费请求消息#1中携带该专用计费功能网元的地址信息。
在第三种可能的实现方式中，计费触发功能网元#1根据计费触发功能网元#1的信息和/或终端设备的位置信息获取计费功能网元#1的地址信息，然后根据该地址信息向计费功能网元#1发送计费请求消息。
例如，计费触发功能网元#1向网络存储功能网元发送查询请求消息，该查询请求消息用于请求获取用于对终端设备执行计费处理的候选计费功能网元的地址信息，该查询请求消息包括该终端设备的位置信息和/或该计费触发功能网元#1的信息。网络存储功能网元接收到来自计费触发功能网元#1的该查询请求消息之后，查询与该终端设备的位置信息和/或计费功能网元#1的信息对应的候选计费功能网元的地址信息。具体例如，网络存储功能网元存储有如表2所示的Serving NF与计费功能网元的地址信息之间的对应关系。在表2中，“Serving NF ID”表示终端设备的Serving NF(即计费触发功能网元#1，或者也可能是为终端设备提供服务的其他网元)的信息，“location”表示终端设备的位置信息。“CHFInfo”表示终端设备的位置信息和/或计费触发功能网元#1的信息对应的计费功能网元#1的地址信息。
表2
网络存储功能网元根据查询请求消息中携带的终端设备的位置信息和/或计费功能网元的信息，查询与该终端设备的位置信息和/或计费功能网元的信息对应的计费功能网元#1，然后将该计费功能网元#1的地址信息返回给计费触发功能网元#1。
在第四种可能的实现方式中，该计费触发功能网元#1根据该终端设备的位置信息和/或该计费触发功能网元#1的信息，在本地配置信息中确定与该终端设备的位置信息和/或该计费触发功能网元#1的信息对应的该计费功能网元#1的地址信息，然后根据该地址信息向计费功能网元#1发送计费请求消息。可以理解的是，该本地配置信息可以是预配置在该计费触发功能网元#1上的，也可以是其他网元配置给该计费触发功能网元的，本申请对此不做限定。
在第五种可能的实现方式中，计费触发功能网元#1通过PCF下发的policy中的计费系统地址信息确定计费功能网元#1的地址信息，然后根据该地址信息向计费功能网元#1发送该计费请求消息#1。
S402，计费功能网元#1根据终端设备的计费数据#1对该终端设备进行计费。
示例性地，计费功能网元#1根据终端设备的计费数据#1对该终端设备进行计费，或者说，计费功能网元#1根据该终端设备的计费数据#1对该计费请求消息#1进行处理，或者说，计费功能网元#1成为终端设备的服务计费功能网元。例如，对于在线计费，计费功能网元#1根据计费数据#1对终端设备执行授予配额、批价、账户余额的锁定等操作；对于离线计费，计费功能网元#1根据计费数据#1对终端设备执行打开话单进行记录、话单处理、返回响应等操作。
其中，该计费数据#1是计费功能网元#1从专用计费功能网元接收到的。这里的计费数据#1指的是用于对终端设备进行计费所需要的数据，如用户账户数据(用户名称、类型、账户余额、套餐、批价信息)、应用于用户的策略数据(如：批价策略等)等。
可以理解的是，在计费功能网元#1之前为终端设备提供计费服务的网元，可以是专用计费网元，也可以是除计费功能网元#1和专用计费功能网元以外的其他候选计费功能网元(如计费功能网元#2)，本申请对此不作限定。
可选地，在S402之前，计费功能网元#1获取终端设备的计费数据#1。
下面针对两种可能的情况，对计费功能网元#1获取终端设备的计费数据#1的具体实现方式作示例性说明。
情况1：
S402a，计费功能网元#1在本地存储中获取终端设备的计费数据#1。
示例性地，计费功能网元#1接收到计费请求消息#1之后，判断本地存储中是否存有终端设备的计费数据#1，如果计费功能网元#1本地存有计费数据#1的话，计费功能网元#1可以直接在本地存储中获取该计费数据#1。
可以理解的是，在这种情况下，计费功能网元#1是在S401之前预先从专用计费功能网元接收到的该终端设备的计费数据#1。例如，在S401之前，计费功能网元#1已经是终端设备的服务计费功能网元，并从专用计费功能网元获取并保存了终端设备的计费数据#1。但之后用户下线之后又重新上线，则此时计费功能网元#1可以直接从本地存储中获取该计费数据#1。可以理解的是，由于本申请实施例中是由专用计费功能网元维护终端设备的计费数据的，因此如果终端设备的计费数据发生了变化，则专用计费功能网元或从计费功能网元#1回收计费数据#1。因此，计费功能网元本地维护的计费数据#1可以认为是最新的计费数据。
情况2：
S402b，计费功能网元#1向专用计费功能网元发送计费数据请求消息#1。对应地，专用计费功能网元接收来自计费功能网元#1的该计费数据请求消息#1。
示例性地，计费功能网元#1可以在接收到计费请求消息#1之后，直接向专用计费功能网元发送计费数据请求消息#1，以请求获取终端设备的计费数据#1；或者，计费功能网元#1也可以在确定本地存储中没有该终端设备的计费数据#1的情况下，向专用计费功能网元发送计费计费数据请求消息#1，以请求获取终端设备的计费数据#1。
可以理解的是，该计费数据请求消息#1可以是计费功能网元#1接收到的计费请求消息#1(即计费功能网元#1将接收到的计费请求消息#1转发给专用计费功能网元)，也可以是计费功能网元#1新生成的消息，本申请对此不作限定。
可选地，计费功能网元#1在向专用计费功能网元发送计费数据请求消息#1之前，获取该专用计费功能网元的地址信息，即确定该专用计费功能网元。
例如，计费功能网元#1根据终端设备的标识，向网络存储功能网元查询与该终端设备对应的专用计费功能网元的地址信息。具体方式与S401所示的第一种可能的实现方式中，计费触发功能网元#1通过网络存储功能网元查询终端设备对应的专用计费功能网元的实现方式类似，为了简洁，这里不再赘述。或者，计费功能网元#1也可以通过其他存储有终端设备与专用计费功能网元的对应关系的网元或设备查询该专用计费功能网元的地址信息，本申请对此不作限定。
又例如，计费触发功能网元#1或专用计费功能网元可以在计费请求消息#1中携带该专用计费功能网元的地址信息(具体可参考S401部分的描述)，在这种情况中，计费功能网元#1从计费请求消息#1中获取专用计费功能网元的地址信息。
可选地，专用计费功能网元记录计费功能网元#1是当前为终端设备提供计费服务的网元，或者说，专用计费功能网元保存终端设备当前的服务计费功能网元的信息(即计费功能网元#1的信息)。这样专用计费功能网元便可以确定终端设备当前的服务计费功能网元是谁，以便后续可以与终端设备的服务计费功能网元进行交互以为终端设备提供服务。
S402c，专用计费功能网元向计费功能网元#1发送计费数据#1。对应地，计费功能网元#1接收来自专用计费功能网元的计费数据#1。
示例性地，专用计费功能网元接收来自计费功能网元#1的该计费数据请求消息#1之后，在本地查询该终端设备的计费数据#1，然后将该计费数据#1发送给计费功能网元#1。
其中，专用计费功能网元下发的计费数据#1可以是格式文件、压缩后的格式文件、直接携带在消息中的CDATA格式的信息等多种形式的数据，本申请不作限定。
可以理解的是，专用计费功能网元通过向计费功能网元#1发送该终端设备的计费数据#1，隐性指示计费功能网元#1作为终端设备的服务计费功能网元。即终端设备接收到来自专用计费功能网元的计费数据#1之后，即切换为终端设备的服务计费功能网元。
还可以理解的是，专用计费功能网元可以一次性下发该计费数据#1，也可以在计费过程中分多次下发该计费数据#1，本申请对此不作限定。
还可以理解的是，在本申请实施例中，专用计费功能网元向计费功能网元#1下发的计费数据#1，可以仅包括终端设备的用户数据中的部分数据，如计费数据#1仅为终端设备的用户数据中用于对终端设备进行计费处理的数据，或者，计费数据#1也可以包括终端设备的用户数据中的全部数据，本申请对此不 作限定。
S403，计费功能网元#1向专用计费功能网元发送计费结果#1。对应地，专用计费功能网元接收来自计费功能网元#1的该计费结果#1。
示例性地，计费功能网元#1在对终端设备进行计费处理之后，将计费结果#1发送给专用计费功能网元，其中，这里的计费结果#1指的是计费功能网元#1对终端设备执行计费处理之后得到的数据，例如，计费结果#1包括用户使用量、账户余额变化、套餐余额变化等数据。可以理解的是，计费功能网元#1可以在计费结束之后一次性向专用计费功能网元发送该计费数据#1，也可以在计费过程分多次向专用计费功能网元发送该计费数据#1，本申请对此不作限定。
对应地，专用计费功能网元接收来自计费功能网元#1的计费结果#1之后，根据该计费结果#1更新终端设备的用户数据。
通过上述S401-S403的流程(记为流程1)，由计费功能网元#1对终端设备执行了计费处理，因此计费过程的一些临时数据不需要在信令网传输，从而可以节省网络资源，降低运营成本。
并且，终端设备的计费数据由专用计费功能网元统一管理，专用计费功能网元可以仅下发部分数据用于计费功能网元对终端设备进行计费，从而进一步降低信令网压力，提高计费的效率。
可选地，在流程1之后，如果终端设备从计费功能网元#1的计费系统的覆盖区域，移动到了计费功能网元#2的计费系统的覆盖区域，终端设备的服务计费功能网元可以切换为计费功能网元#2。下面结合流程2做示例性说明。
S404，计费触发功能网元#2向计费功能网元#2发送计费请求消息#2。对应地，计费功能网元#2接收来自计费触发功能网元#2的该计费请求消息#2。
示例性地，计费触发功能网元#2在接收到针对终端设备的业务请求的情况下，向计费功能网元#2发送计费请求消息#2，该计费请求消息#2用于请求对该终端设备进行计费。其中，计费触发功能网元#2向计费功能网元#2发送计费请求消息#2的方式，与S401中计费触发功能网元#1向计费功能网元#1发送计费请求消息#1的方式类似，为了简洁，这里不再赘述。
S405，计费功能网元#2向专用计费功能网元发送计费数据请求消息#2。对应地，专用计费功能网元接收来自计费功能网元#2的该计费数据请求消息#2。
示例性地，计费功能网元#2接收来自计费触发功能网元#2的计费请求消息#2之后，向专用计费功能网元发送计费数据请求消息#2，以请求获取终端设备的计费数据。
可选地，计费功能网元#2可以在确定本地存储中没有所述终端设备的计费数据的情况下，向专用计费功能网元发送计费数据请求消息#2。
可选地，计费功能网元#2在向专用计费功能网元发送计费数据请求消息#2之前，确定该专用计费功能网元，具体方案与S402b中计费功能网元#1确定专用计费功能网元的方式类似，为了简洁，这里不再赘述。
S406，专用计费功能网元向计费功能网元#2发送计费数据#2。对应地，计费功能网元#2接收来自专用计费功能网元的该计费数据#2。
可以理解的是，S406与S402c类似，区别在于S406中，专用计费功能网元向计费功能网元#2发送的计费数据#2是在S403之后更新后的计费数据。具体实现过程不作限定。
可选地，在专用计费功能网元向该计费功能网元发送终端设备的计费数据#2之后，如果专用计费功能网元接收来自计费功能网元#1的计费结果#3，则专用计费功能网元根据该计费结果#3判断是否需要向计费功能网元#2更新终端设备的计费数据。其中，计费结果#3为计费功能网元#1在S403之后对终端设备执行计费处理之后得到的数据。
例如，在终端设备通过会话和服务连续模式(session and service continuity mode，SSC)3进行会话的切换的情况下，计费功能网元#1在S403之后可能仍然在对终端设备进行计费，直到计费功能网元#1接收到终止请求消息之后，计费功能网元将从发送计费结果#1到接收到终止请求消息之间生成的计费结果#3发送给专用计费功能网元。
专用计费功能网元根据该计费结果#3判断是否需要向计费功能网元#2更新计费数据。例如，专用计费功能网元在S406向计费功能网元#2下发的计费数据#2是终端设备的用户数据中的部分数据，如终端设备的套餐余额为500M，而专用计费功能网元通过计费数据#2向计费功能网元#2提供的配额为200M，同时计费结果#3指示终端设备使用了400M，由于专用计费功能网元通过计费数据#2向计费功能网元#2提 供的配额大于终端设备的余额了(余额为100M)，在这种情况下，专用计费功能网元确定需要向计费功能网元#2更新该终端设备的计费数据。
在需要向计费功能网元#2更新该终端设备的计费数据的情况下，专用计费功能网元向该计费功能网元#2发送更新后的计费数据。终端设备可以根据更新后的计费数据继续对终端设备执行计费处理。
S407，计费功能网元#2对终端设备进行计费。
S408，计费功能网元#2向专用计费功能网元发送计费结果#2，其中，该计费结果#2是计费功能网元#2对终端设备进行计费之后得到的数据。对应地，专用计费功能网元接收来自计费功能网元#2的该计费结果#2。
可以理解的是S407-S408与S402-S403类似，区别在于S407-S408由计费功能网元#2执行，S402-S403由计费功能网元#1执行，为了简洁，这里不再赘述。
专用计费功能网元接收来自计费功能网元#2的计费处理之后的数据之后，更新终端设备的用户数据。
可选地，在流程2之后，如果终端设备从计费功能网元#2的计费系统的覆盖区域，移动到了专用计费功能网元的计费系统的覆盖区域，终端设备的服务计费功能网元可以切换为专用计费功能网元#2。下面结合流程3作示例性说明。
S409，计费触发功能网元#3向专用计费功能网元发送计费请求消息#3。对应地，专用计费功能网元接收来自计费触发功能网元#3的该计费请求消息#3。
示例性地，计费触发功能网元#3在接收到针对终端设备的业务请求的情况下，向专用计费功能网元发送计费请求消息#3，该计费请求消息#3用于请求对该终端设备进行计费。其中，计费触发功能网元#3向专用计费功能网元发送计费请求消息#3的方式，与S401中计费触发功能网元#1向计费功能网元#1发送计费请求消息#1的方式类似，为了简洁，这里不再赘述。
S410，专用计费功能网元根据计费数据#3对终端设备进行计费。
示例性地，专用计费功能网元接收来自计费触发功能网元的计费请求消息#3之后，查询该终端设备对应的计费数据#3，然后根据该计费数据#3对该终端设备进行计费。可以理解的是，该计费数据#3是专用计费功能网元在S408之后更新后的计费数据。
可以理解的是，本申请对流程1-流程3的执行顺序不作限定。
在上述方案中，在终端设备的位置变化导致终端设备的服务计费功能网元发生变化的情况下，终端设备就近的计费功能网元(即从计费触发功能网元接收到计费请求消息的计费功能网元)通过专用计费功能网元获取终端设备的计费数据，并为终端设备提供计费服务。通过上述方案，可以减少计费过程产生的大量计费信息的跨区传输，从而节省网络资源，降低信令网压力以及运营成本，提高网络韧性。例如，当网络被划分为多个区域(如：中国的按照省份部署、欧洲的一网跨多国、沿海国家的运营商网络覆盖多个岛屿等)，需要在多个区域部署多套核心网和计费系统，如果采用归属地计费系统对终端设备进行计费的话，在终端设备移动到归属区域以外的区域的情况下，需要将终端设备实时产生的大量计费信息(如话单等信息)路由到终端设备的专有计费系统，从而增加了信令网压力和运营成本。而上述方案采用终端设备就近的计费功能网元(即接收到计费请求消息的计费功能网元)对终端设备进行计费，可以节省网络资源，并且可以降低计费网络线路出现故障时对用户业务使用造成的影响。
下面结合图5-图13介绍本申请实施例提供的计费方法500-1300。可以理解的是，方法500-方法1300是方法400应用在5G通信系统的几种可能的实现方式。在方法500-方法1300中，以终端设备为UE、专用计费功能网元为专用CHF(dedicated CHF)、计费触发功能网元为SMF或MEC CTF、计费功能网元为CHF为例进行说明。
图5示出了本申请实施例提供的方法500的示例性流程图。在方法500中，假设UE的serving CHF由dedicated CHF切换为CHF1。
需要说明的是，方法500是以在线计费场景下，UE通过SSC mode2进行PDU会话的切换为例进行说明的。其中SSC mode2是一种业务和会话连续性模式，在SSC mode2中，在会话锚点变更时，先释放UE与原来的PDU会话锚点的的连接，再建立UE与新的PDU会话锚点的连接，中间业务会中断。
下面结合图5中的各个步骤对方法500作示例性说明。
S501，UE与UPF1建立有PDU会话#1，并通过PDU会话#1进行数据传输。具体过程本申请不作限定。
可以理解的是，在PDU会话#1的建立过程，SMF1触发专用CHF(dedicated CHF)对UE进行计费， 具体过程本申请不作限定。
S502，SMF1确定执行UPF的切换。
示例性地，SMF1确定需要切换为UE提供服务的UPF，其中，SMF1是为UE的PDU会话#1提供服务的SMF。例如，由于UE的位置移动，导致UPF1无法再为UE提供服务，或者UPF1与UE之间的信号较差时，SMF1确定需要切换为UE提供服务的UPF。
可选地，S503，SMF1向AMF发送会话管理上下文状态通知请求消息。对应地，AMF接收来自SMF1的该会话管理上下文状态通知请求消息。
示例性地，SMF1在确定切换UPF的情况下，向AMF发送会话管理上下文状态通知请求(Nsmf_PDUSession_SMContextStatusNotify Request)消息，该会话管理上下文状态通知请求消息用于指示AMF释放PDU会话#1。
可选地，S504，AMF向SMF1发送会话管理上下文状态通知响应消息。对应地，SMF1接收来自AMF的该会话管理上下文状态通知响应消息。
示例性地，AMF接收来自SMF1的会话管理上下文状态通知请求消息之后，向SMF1返回会话管理上下文状态通知响应(Nsmf_PDUSession_SMContextStatusNotify Response)消息。
S505，针对PDU会话#1的释放流程。
示例性地，AMF根据会话管理上下文状态通知请求消息，触发PDU会话#1的释放流程，即触发UE断开与UPF1的连接。具体过程可参考现有协议，这里不再赘述。
S506，SMF1向专用CHF发送终止请求消息#1。对应地，专用CHF接收来自SMF1的该终止请求消息#1。
示例性地，在PDU会话#1释放之后，SMF1向专用CHF(dedicated CHF)发送终止请求(termination request)消息#1，该专用CHF是当前为UE提供计费服务的网元。
该终止请求消息#1用于请求结束PDU会话#1对应的计费会话，即释放SMF1与dedicated CHF之间的针对该PDU会话#1的计费资源。
S507，专用CHF向SMF1发送终止响应消息。对应地，SMF1接收来自专用CHF的该终止响应消息。
示例性地，dedicated CHF接收来自SMF1的termination request消息#1之后，释放计费资源，并返回终止响应(termination response)消息#1。
该终止响应消息#1包括PDU会话#1的最后用量，即上一个initial request(即计费请求)到这一个终止请求消息#1之间用户流量的用量，其中，对于在线计费场景，用户流量的用量指的是针对配额的使用量，对于离线计费场景，用户流量的用量指的是统计的流量的使用量。
S508，UE与UPF2之间的PDU会话#2的建立流程。
示例性地，在PDU会话#1释放流程结束之后，UE触发与UPF2之间的PDU会话#2的建立流程，具体过程可参考现有协议，这里不再赘述。
S509，SMF2向CHF1发送初始请求消息#1。对应地，CHF1接收来自SMF2的该初始请求消息#1。
示例性地，SMF2在PDU会话#2的建立流程中，例如在SMF2接收到来自AMF的针对PDU会话#2的会话管理上下文创建请求(Nsm_PDUSession_CreateSMContext Request)消息之后，SMF2向CHF1发送针对PDU会话#2的初始请求(initial request)消息#1，其中，SMF2是为PDU会话#2提供服务的SMF，该初始请求消息#1用于请求针对该PDU会话#2对UE进行计费。
其中SMF2向CHF1发送初始请求消息#1的具体实现方式可参考方法400的S401中，计费触发功能网元#1向计费功能网元#1发送计费请求消息#1的实现方式，例如，S509中的SMF2对应于S401中的计费触发功能网元#1，S509中的CHF1对应于S401中的计费功能网元#1，S509中的初始请求消息#1对应于S401中的计费请求消息#1，这里不再赘述。
S510，CHF1向专用CHF发送初始请求消息#2。对应地，专用CHF接收来自CHF1的该初始请求消息#2。
S511，专用CHF向CHF1发送计费数据。对应地，CHF1接收来自专用CHF的该计费数据。
示例性地，CHF1向专用CHF发送初始请求消息#2，以请求获取UE的计费数据。专用CHF根据CHF1的请求，返回UE的计费数据。具体过程可参考方法400中的S402b-S402c，例如，S510-S511中的专用CHF和CHF1分别对应S402b-S402c中的专用计费功能网元和计费功能网元#1，S510中的初始请求消息#2对应于S402b中的计费数据请求消息#1，S511中的计费数据对应于S402c中的计费数据#1，这里 不再赘述。
S512，CHF1根据计费数据对UE进行计费。
示例性地，CHF1接收到来自专用CHF的计费数据之后，根据该计费数据对UE进行计费。具体过程可参考方法400中的S402，这里不再赘述。
可选地，SMF2与CHF1之间执行后续计费交互(如计费过程的update请求消息)，具体过程本申请不作限定。
S513，CHF1向SMF2发送初始响应消息。对应地，SMF2接收来自CHF1的该初始响应消息。
示例性地，CHF1接收来自专用CHF的计费数据之后，向SMF2返回初始响应消息，该初始响应消息用于响应于初始请求消息#1。可以理解的是，本申请不限定S512和S513执行的先后顺序。
S514，SMF2向CHF1发送终止请求消息#2。对应地，CHF1接收来自SMF2的该终止请求消息#2。
S515，CHF1向SMF2发送终止响应消息#2。对应地，SMF2接收来自CHF1的该终止响应消息#2。
示例性地，在PDU会话#2释放之后(图中没有示出)，SMF1向CHF1发送终止请求(termination request)消息#2，以请求结束PDU会话#2对应的计费会话，即释放SMF2与CHF1之间的针对该PDU会话#1的计费资源。
S516，CHF1向专用CHF发送计费结果。对应地，专用CHF接收来自CHF1的该计费结果。
S516与方法400中的S403类似，这里不再赘述。
通过上述方案，在UE的位置变化导致UE的serving CHF发生变化的情况下(如serving CHF由dedicated CHF切换为CHF1)，UE就近的CHF1通过dedicated CHF获取UE的计费数据，并为UE提供计费服务，从而可以减少计费过程产生的大量计费信息的跨区传输，节省网络资源，降低运营成本。
图6示出了本申请实施例提供的方法600的示例性流程图。在方法600中，假设UE的serving CHF由CHF1切换为CHF2。并且，方法600是以在线计费场景下，UE通过SSC mode2进行PDU会话的切换为例进行说明的。
可以理解的是，方法600可以独立实施，也可以与方法500结合实施。例如，方法600可以是在方法500之后执行的方案。
下面结合图6中的各个步骤对方法600作示例性说明。
S601，UE与UPF2建立有PDU会话#2，并通过该PDU会话#2进行数据传输。具体过程本申请不作限定。
可以理解的是，在PDU会话#2的建立过程，SMF2触发CHF1对UE进行计费，具体过程本申请不作限定。如果将方法600与方法500结合实施，则S601可对应于方法500中的S508-S513。
S602，SMF1确定执行UPF的切换。
可选地，S603，SMF1向AMF发送会话管理上下文状态通知请求消息。
可选地，S604，AMF向SMF1发送会话管理上下文状态通知响应消息。
S602-S604与方法500中的S502-S504类似，这里不再赘述。
S605，针对PDU会话#2的释放流程。
示例性地，AMF根据会话管理上下文状态通知请求消息，触发PDU会话#2的释放流程，即触发UE断开与UPF2的连接。具体过程可参考现有协议，这里不再赘述。
S606，SMF2向CHF1发送终止请求消息。对应地，CHF1接收来自SMF2的该终止请求消息。
示例性地，在PDU会话#2释放之后，SMF2向CHF1发送终止请求(termination request)消息#1，其中CHF1是当前为UE提供计费服务的网元。
该终止请求消息#1用于请求结束PDU会话#2对应的计费会话，即释放SMF2与CHF1之间的针对该PDU会话#2的计费资源。
S607，CHF1向SMF2发送终止响应消息#1。对应地，SMF2接收来自CHF1的该终止响应消息#1。
示例性地，CHF1接收来自SMF2的终止请求消息之后，释放计费资源，并返回终止响应(termination response)消息#1。该termination response消息#1包括PDU会话#2的最后用量。
S608，CHF1向专用CHF发送计费结果#1。对应地，专用CHF接收来自CHF1的该计费结果#1。
S608与方法400中的S403类似，这里不再赘述。可以理解的是，如果将方法600与方法500结合实施，则S608可对应于方法500中的S514。
S609，UE与UPF2之间的PDU会话#2的建立流程。
示例性地，在PDU会话#2释放流程结束之后，UE触发与UPF3之间的PDU会话#3的建立流程，具体过程可参考现有协议，这里不再赘述。
S610，SMF3向CHF2发送初始请求消息#1。对应地，CHF2接收来自SMF3的该初始请求消息#1。
示例性地，SMF3在PDU会话#3的建立流程中，向CHF2发送针对PDU会话#3的初始请求(initial request)消息#1，其中，SMF3是为PDU会话#3提供服务的SMF，该初始请求消息#1用于请求针对该PDU会话#3对UE进行计费。
S610与方法400中的S404类似，例如，S610中的SMF3对应于S404中的计费触发功能网元#2，S610中的CHF2对应于S404中的计费功能网元#2，S610中的初始请求消息#1对应于S404中的计费请求消息#2，具体过程这里不再赘述。
S611，CHF1向专用CHF发送初始请求消息#2。对应地，专用CHF接收来自CHF1的该初始请求消息#2。
S612，专用CHF向CHF1发送计费数据。对应地，CHF1接收来自专用CHF的该计费数据。
示例性地，CHF1向专用CHF发送初始请求消息#2，以请求获取UE的计费数据。专用CHF根据CHF1的请求，返回UE的计费数据。具体过程可参考方法400中的S405-S406，例如，S611-S612中的专用CHF和CHF2分别对应S402b-S402c中的专用计费功能网元和计费功能网元#2，S611中的初始请求消息#2对应于S405中的计费数据请求消息#2，S612中的计费数据对应于S406中的计费数据#2，这里不再赘述。
S613，CHF2根据计费数据对UE进行计费。
示例性地，CHF2接收到来自专用CHF的计费数据之后，根据该计费数据对UE进行计费。具体过程可参考方法400中的S407，这里不再赘述。
可选地，SMF3与CHF2之间执行后续计费交互(如计费过程的update请求消息，或者计费结束的termination请求消息等)，具体过程本申请不作限定。
S614，CHF2向SMF3发送初始响应消息。对应地，SMF3接收来自CHF2的该初始响应消息。
示例性地，CHF2接收来自专用CHF的计费数据之后，向SMF3返回初始响应消息，该初始响应消息用于响应于初始请求消息#1。可以理解的是，本申请不限定S613和S614执行的先后顺序。
S615，SMF3向CHF2发送终止请求消息#2。对应地，CHF2接收来自SMF3的该终止请求消息#2。
S616，CHF2向SMF3发送终止响应消息#2。对应地，SMF3接收来自CHF2的该终止响应消息#2。
示例性地，在PDU会话#3释放之后(图中没有示出)，SMF3向CHF2发送终止请求(termination request)消息#2，以请求结束PDU会话#2对应的计费会话，即释放SMF3与CHF2之间的针对该PDU会话#1的计费资源。
S617，CHF2向专用CHF发送计费结果#2。对应地，专用CHF接收来自CHF2的该计费结果#2。
S617与方法400中的S408类似，这里不再赘述。
通过上述方案，在UE的位置变化导致UE的serving CHF发生变化的情况下(如serving CHF由CHF1切换为CHF2)，UE就近的CHF2通过dedicated CHF获取UE的计费数据，并为UE提供计费服务，从而可以减少计费过程产生的大量计费信息的跨区传输，节省网络资源，降低运营成本。
图7示出了本申请实施例提供的方法700的示例性流程图。在方法700中，假设UE的serving CHF由CHF2切换为dedicated CHF。并且，方法700是以在线计费场景下，UE通过SSC mode2进行PDU会话的切换为例进行说明的。
可以理解的是，方法700可以独立实施，也可以与方法500和/或方法600结合实施。例如，方法700可以是在方法600之后执行的方案。
下面结合图7中的各个步骤对方法700作示例性说明。
S701，UE与UPF3建立有PDU会话#3，并通过该PDU会话#3进行数据传输。具体过程本申请不作限定。
可以理解的是，在PDU会话#3的建立过程，SMF3触发CHF2对UE进行计费，具体过程本申请不作限定。如果将方法700与方法600结合实施，则S701可对应于方法600中的S509-S614。
S702，SMF1确定执行UPF的切换。
可选地，S703，SMF1向AMF发送会话管理上下文状态通知请求消息。
可选地，S704，AMF向SMF1发送会话管理上下文状态通知响应消息。
S702-S704与方法500中的S502-S504类似，这里不再赘述。
S705，针对PDU会话#2的释放流程。
示例性地，AMF根据会话管理上下文状态通知请求消息，触发PDU会话#3的释放流程，即触发UE断开与UPF3的连接。具体过程可参考现有协议，这里不再赘述。
S706，SMF3向CHF2发送终止请求消息。对应地，CHF2接收来自SMF3的该终止请求消息。
示例性地，在PDU会话#3释放之后，SMF3向CHF2发送终止请求(termination request)消息，该CHF2是当前为UE提供计费服务的网元。
该终止请求消息用于请求结束PDU会话#3对应的计费会话，即释放SMF3与CHF2之间的针对该PDU会话#2的计费资源。
S707，CHF2向SMF3发送终止响应消息。对应地，SMF2接收来自CHF1的该终止响应消息。
示例性地，CHF2接收来自SMF3的终止请求消息之后，释放计费资源，并返回终止响应(termination response)消息。该termination response消息包括PDU会话#3的最后用量。
S708，CHF2向专用CHF发送计费结果。对应地，专用CHF接收来自CHF2的该计费结果。
S708与方法400中的S403类似，这里不再赘述。可以理解的是，如果将方法700与方法600结合实施，则S708可对应于方法600中的S615。
S709，UE与UPF4之间的PDU会话#4的建立流程。
示例性地，在PDU会话#4释放流程结束之后，UE触发与UPF4之间的PDU会话#4的建立流程，具体过程可参考现有协议，这里不再赘述。
S710，SMF4向专用CHF发送初始请求消息。对应地，专用CHF接收来自SMF4的该初始请求消息。
示例性地，SMF4在PDU会话#4的建立流程中，向专用CHF发送针对PDU会话#4的初始请求(initial request)消息，其中，SMF4是为PDU会话#4提供服务的SMF，该初始请求消息用于请求针对该PDU会话#4对UE进行计费。
S710与方法400中的S409类似，例如，S710中的SMF4对应于S404中的计费触发功能网元#3，S710中的专用CHF对应于S404中的专用计费功能网元，S710中的初始请求消息对应于S404中的计费请求消息#3，具体过程这里不再赘述。
S711，专用CHF根据计费数据对UE进行计费。
S711与方法400中的S410类似，为了简洁，这里不再赘述。
S712，专用CHF向SMF4发送初始响应消息。对应地，SMF4接收来自专用CHF的该初始响应消息。
示例性地，专用CHF向SMF4返回初始响应消息，该初始响应消息用于响应于初始请求消息。可以理解的是，本申请不限定S711和S712执行的先后顺序。
通过上述方案，在UE的位置变化导致UE的serving CHF发生变化的情况下(如serving CHF由CHF2切换为dedicated CHF)，dedicated CHF根据本地维护的UE的计费数据，为UE提供计费服务，从而可以减少计费过程产生的大量计费信息的跨区传输，节省网络资源，降低运营成本。
图8示出了本申请实施例提供的方法800的示例性流程图。在方法800中，假设UE的serving CHF由dedicated CHF切换为CHF1。
需要说明的是，方法800是以在线计费场景下，UE通过SSC mode3进行PDU会话的切换为例进行说明的。其中SSC mode3是一种不同于SSC mode2的业务和会话连续性模式，在SSC mode3中，在用户面改变(即会话锚点改变)之前，先建立与新的PDU会话锚点间的连接，以保证业务的连续性。
下面结合图8中的各个步骤对方法800作示例性说明。
S801，UE与UPF1建立有PDU会话#1，并通过PDU会话#1进行数据传输。具体过程本申请不作限定。
S802，SMF1确定执行UPF/SMF的切换。
可选地，S803，SMF1向AMF发送会话管理上下文状态通知请求消息。对应地，AMF接收来自SMF1的该会话管理上下文状态通知请求消息。
可选地，S804，AMF向SMF1发送会话管理上下文状态通知响应消息。对应地，SMF1接收来自AMF的该会话管理上下文状态通知响应消息。
S801-S804与方法500中的S501-S504类似，为了简洁，这里不再赘述。
S805，SMF1向AMF发送N1N2消息传递请求消息。对应地，AMF接收来自SMF1的该N1N2消息 传递请求消息。
示例性地，该N1N2消息传输(Namf_Communication_N1N2MessageTransfer)请求消息包括PDU session ID、SMF重定位指示信息、N1SM container等。其中，PDU session ID为PDU会话#1的标识，SMF重定位指示信息用于指示是否请求重新分配SMF。
S806，AMF向SMF1发送N1N2消息传递响应消息。对应地，SMF1接收来自AMF的该N1N2消息传递响应消息。该N1N2消息传递响应消息用于响应于N1N2消息传递请求消息。
S807，AMF向UE发送PDU会话修改命令。对应地，UE接收来自AMF的该PDU会话修改命令。
示例性地，该PDU会话修改命令中包括上述N1N2消息传递请求消息中携带的信息。
S808，UE向AMF发送PDU会话修改命令确认消息。对应地，AMF接收来自UE的该PDU会话修改命令确认消息。该PDU会话修改命令消息确认消息用于响应于PDU会话修改命令。
S809，AMF向SMF1发送更新会话管理上下文请求(Nsmf PDUSession UpdateSMContext Request)消息。对应地，SMF1接收来自AMF的该更新会话管理上下文请求消息。
示例性地，AMF通过更新会话管理上下文请求消息，向AMF发送从RAN接收到的N1SM container。
S810，SMF1向AMF发送更新会话管理上下文响应(Nsmf PDUSession UpdateSMContext Response)消息。对应地，AMF接收来自SMF1的该更新会话管理上下文响应消息。该更新会话管理上下文响应消息用于响应于更新会话管理上下文请求消息。
S811，UE与UPF2之间的PDU会话#2的建立流程。
示例性地，UE接收到PDU会话修改命令之后，确定是否触发建立与UPF2之间的PDU会话#2。具体过程本申请不作限定。
S812，SMF2向CHF1发送初始请求消息#1。对应地，CHF1接收来自SMF2的该初始请求消息#1。
S813，CHF1向专用CHF发送初始请求消息#2。对应地，专用CHF接收来自CHF1的该初始请求消息#2。
S814，专用CHF向CHF1发送计费数据。对应地，CHF1接收来自专用CHF的该计费数据。
S815，CHF1根据计费数据对UE进行计费。
S816，CHF1向SMF2发送初始响应消息。对应地，SMF2接收来自CHF1的该初始响应消息。
可以理解的是，S812-S816与方法500中的S509-S513类似，这里不再赘述。
S817，针对PDU会话#1的释放流程。
示例性地，在PDU会话#2建立完成之后，SMF1触发PDU会话#1的释放流程。具体过程本申请不作限定。
S818，SMF1向专用CHF发送终止请求消息#1。对应地，专用CHF接收来自SMF1的该终止请求消息#1。
示例性地，在PDU会话#1释放之后，SMF1向专用CHF(dedicated CHF)发送终止请求(termination request)消息#1，该专用CHF是当前是在CHF1之前为UE提供计费服务的网元。
该终止请求消息#1用于请求结束PDU会话#1对应的计费会话，即释放SMF1与dedicated CHF之间的针对该PDU会话#1的计费资源。
S819，专用CHF向SMF1发送终止响应消息#1。对应地，SMF1接收来自专用CHF的该终止响应消息#1。
示例性地，dedicated CHF接收来自SMF1的termination request消息之后，释放计费资源，并返回终止响应(termination response)消息。该termination response消息包括PDU会话#1的最后用量。
可以理解的是，本申请不限定S818-S819，与S812-S816的先后顺序。
S820，SMF2向CHF1发送终止请求消息#2。对应地，CHF1接收来自SMF2的该终止请求消息#2。
S821，CHF1向SMF2发送终止响应消息#2。对应地，SMF2接收来自CHF1的该终止响应消息#2。
示例性地，在PDU会话#2释放之后(图中没有示出)，SMF1向CHF1发送终止请求(termination request)消息#2，以请求结束PDU会话#2对应的计费会话，即释放SMF2与CHF1之间的针对该PDU会话#1的计费资源。
S822，CHF1向专用CHF发送计费结果。对应地，专用CHF接收来自CHF1的该计费结果。
S822与方法400中的S403类似，这里不再赘述。
通过上述方案，在UE的位置变化导致UE的serving CHF发生变化的情况下(如serving CHF由 dedicated CHF切换为CHF1)，UE就近的CHF1通过dedicated CHF获取UE的计费数据，并为UE提供计费服务，从而可以减少计费过程产生的大量计费信息的跨区传输，节省网络资源，降低运营成本。
图9示出了本申请实施例提供的方法900的示例性流程图。在方法900中，假设UE的serving CHF由CHF1切换为CHF2。并且，方法900是以在线计费场景下，UE通过SSC mode3进行PDU会话的切换为例进行说明的。
可以理解的是，方法900可以独立实施，也可以与方法800结合实施。例如，方法900可以是在方法800之后执行的方案。
下面结合图9中的各个步骤对方法900作示例性说明。
可以理解的是S901-S906与方法800中的S801-S806类似，为了简洁，这里不再赘述。
可选地，S907，SMF2向CHF1发送终止请求消息#1。对应地，CHF1接收来自SMF2的该终止请求消息#1。
示例性地，SMF2可以在接收到针对PDU会话#1的N1N2消息传递响应消息#1之后，向CHF1发送终止请求(termination request)消息#1，该CHF1是当前为UE提供计费服务的网元。该终止请求消息#1用于请求结束PDU会话#2对应的计费会话，即释放SMF2与CHF1之间的针对该PDU会话#2的计费资源。
可选地，S908，CHF1向SMF2发送终止响应消息#1。对应地，SMF2接收来自CHF1的该终止响应消息#1。
可选地，S909，CHF1向专用CHF发送计费结果#1。对应地，专用CHF接收来自CHF1的该计费结果#1。
示例性地，CHF1可以在对UE进行计费处理之后，向专用CHF发送计费结果#1，该计费结果#1指的是计费功能网元#1对终端设备执行计费处理之后得到的数据。具体可参考方法400中的S403部分的描述，这里不再赘述。
S910，AMF向UE发送PDU会话修改命令。对应地，UE接收来自AMF的该PDU会话修改命令。
S911，UE向AMF发送PDU会话修改命令确认消息。对应地，AMF接收来自UE的该PDU会话修改命令确认消息。
S912，AMF向SMF1发送更新会话管理上下文请求消息。对应地，SMF1接收来自AMF的该更新会话管理上下文请求消息。
S913，SMF1向AMF发送更新会话管理上下文响应消息。对应地，AMF接收来自SMF1的该更新会话管理上下文响应消息。
S914，UE与UPF2之间的PDU会话#2的建立流程。
可以理解的是，S910-S914与方法800中的S807-S811类似，为了简洁，这里不再赘述。
S915，SMF3向CHF2发送初始请求消息#1。对应地，CHF2接收来自SMF2的该初始请求消息#1。
S916，CHF2向专用CHF发送初始请求消息#2。对应地，专用CHF接收来自CHF2的该初始请求消息#2。
S917，专用CHF向CHF2发送计费数据。对应地，CHF2接收来自专用CHF的该计费数据。
S918，CHF2根据计费数据对UE进行计费。
S919，CHF2向SMF3发送初始响应消息。对应地，SMF3接收来自CHF2的该初始响应消息。
可以理解的是，S915-S919与方法500中的S610-S614类似，这里不再赘述。
S920，针对PDU会话#2的释放流程。
示例性地，在PDU会话#2建立完成之后，SMF2触发PDU会话#2的释放流程。具体过程本申请不作限定。
S921，SMF2向CHF1发送终止请求消息。对应地，CHF1接收来自SMF2的该终止请求消息。
示例性地，在PDU会话#2释放之后，SMF2向CHF1发送终止请求(termination request)消息，CHF1是在CHF2之前为UE提供计费服务的网元。
该终止请求消息用于请求结束PDU会话#1对应的计费会话，即释放SMF1与dedicated CHF之间的针对该PDU会话#1的计费资源。
S922，CHF1向SMF2发送终止响应消息。对应地，SMF2接收来自CHF1的该终止响应消息。
示例性地，CHF1接收来自SMF1的termination request消息之后，释放计费资源，并返回终止响应 (termination response)消息。该termination response消息包括PDU会话#2的最后用量。
可选地，S923，CHF1向专用CHF发送计费结果#2。对应地，专用CHF接收来自CHF1的该计费结果#2。
示例性地，如果CHF1在S909之后还生成了新的计费结果#2，则CHF1将该计费结果#2发送给专用CHF。
可选地，S924，专用CHF向CHF2发送更新后的计费数据。对应地，CHF2接收来自专用CHF的该更新后的计费数据。
示例性地，专用CHF接收来自CHF的该更新后的计费数据之后，判断是否需要向CHF2更新计费数据。在需要向CHF2更新计费数据的情况下，专用CHF向CHF2发送更新后的计费数据。具体可参考方法400中的S406之后给出的示例，这里不再赘述。
可选地，S925，CHF2根据更新后的计费数据对UE进行计费。
示例性地，如果CHF2接收到了来自专用CHF的更新后的计费数据，则CHF2根据更新后的计费数据对UE进行计费。
S926，SMF3向CHF2发送终止请求消息#2。对应地，CHF2接收来自SMF3的该终止请求消息#2。
S927，CHF2向SMF3发送终止响应消息#2。对应地，SMF3接收来自CHF2的该终止响应消息#2。
示例性地，在PDU会话#3释放之后(图中没有示出)，SMF3向CHF2发送终止请求(termination request)消息#2，以请求结束PDU会话#3对应的计费会话，即释放SMF3与CHF2之间的针对该PDU会话#1的计费资源。
S928，CHF2向专用CHF发送计费结果#3。对应地，专用CHF接收来自CHF2的该计费结果#3。
示例性地，S928与方法400中的S408类似，这里不再赘述。
通过上述方案，在UE的位置变化导致UE的serving CHF发生变化的情况下(如serving CHF由CHF1切换为CHF2)，UE就近的CHF2通过dedicated CHF获取UE的计费数据，并为UE提供计费服务，从而可以减少计费过程产生的大量计费信息的跨区传输，节省网络资源，降低运营成本。
图10示出了本申请实施例提供的方法1000的示例性流程图。在方法1000中，假设UE的serving CHF由CHF2切换为专用CHF。并且，方法1000是以在线计费场景下，UE通过SSC mode3进行PDU会话的切换为例进行说明的。
可以理解的是，方法1000可以独立实施，也可以与方法800和/或900结合实施。例如，方法1000可以是在方法900之后执行的方案。
下面结合图10中的各个步骤对方法1000作示例性说明。
可以理解的是S1001-S1006与方法800中的S801-S806类似，为了简洁，这里不再赘述。
可选地，S1007，SMF3向CHF2发送终止请求消息#1。对应地，CHF2接收来自SMF3的该终止请求消息#1。
可选地，S1008，CHF2向SMF3发送终止响应消息#1。对应地，SMF3接收来自CHF2的该终止响应消息#1。
可选地，S1009，CHF2向专用CHF发送计费结果#1。对应地，专用CHF接收来自CHF2的该计费结果#1。
可以理解的是S1007-S1009与方法900中的S907-S909类似，为了简洁，这里不再赘述。
S1010，AMF向UE发送PDU会话修改命令。对应地，UE接收来自AMF的该PDU会话修改命令。
S1011，UE向AMF发送PDU会话修改命令确认消息。对应地，AMF接收来自UE的该PDU会话修改命令确认消息。
S1012，AMF向SMF3发送更新会话管理上下文请求消息。对应地，SMF3接收来自AMF的该更新会话管理上下文请求消息。
S1013，SMF3向AMF发送更新会话管理上下文响应消息。对应地，AMF接收来自SMF3的该更新会话管理上下文响应消息。
S1014，UE与UPF3之间的PDU会话#2的建立流程。
可以理解的是，S1010-S1014与方法800中的S807-S811类似，为了简洁，这里不再赘述。
S1015，SMF3向CHF2发送初始请求消息#1。对应地，CHF2接收来自SMF2的该初始请求消息#1。
S1016，专用CHF根据计费数据对UE进行计费。
S1017，专用CHF向SMF4发送初始响应消息。对应地，SMF4接收来自专用CHF的该初始响应消息。
可以理解的是，S1015-S1017与方法700中的S710-S712类似，这里不再赘述。
S1018，针对PDU会话#3的释放流程。
S1019，SMF3向CHF2发送终止请求消息#2。对应地，CHF2接收来自SMF3的该终止请求消息#2。
S1020，CHF2向SMF3发送终止响应消息#2。对应地，SMF3接收来自CHF2的该终止响应消息#2。
S1018-S1020与方法900中的S920-S922类似，这里不再赘述。
可选地，S1021，CHF2向专用CHF发送计费结果#2。对应地，专用CHF接收来自CHF2的该计费结果#2。
示例性地，如果CHF2在S1009之后还生成了新的计费结果#2，则CHF2将该计费结果#2发送给专用CHF。
可选地，S1022，专用CHF根据更新后的计费数据对UE进行计费。
示例性地，如果专用CHF接收到了来自CHF2的计费结果#2，则专用CHF根据计费结果#2确定更新后的计费数据，并根据更新后的计费数据对UE进行计费。
通过上述方案，在UE的位置变化导致UE的serving CHF发生变化的情况下(如serving CHF由CHF2切换为dedicated CHF)，dedicated CHF根据本地维护的UE的计费数据，为UE提供计费服务，从而可以减少计费过程产生的大量计费信息的跨区传输，节省网络资源，降低运营成本。
图11示出了本申请实施例提供的方法1100的示例性流程图。
需要说明的是，方法1100是以离线计费场景下，在UE通过AMF注册到网络的过程中，对UE进行计费为例进行说明的。
下面结合图11中的各个步骤对方法1100作示例性说明。
S1101，UE向RAN发送注册请求消息。对应地，RAN接收来自UE的该注册请求消息。
S1102，RAN选择AMF。
S1103，RAN向AMF1发送注册请求消息。对应地，AMF1接收来自UE的该注册请求消息。
示例性地，由于UE位置移动，UE触发注册请求(registration request)消息给RAN，RAN接收到来自UE的注册请求消息之后，选择为UE提供服务的AMF(记为AMF1)，然后RAN将接收到的注册请求消息路由到AMF1。
可选地，S1104，AMF1向AMF2发送UE上下文传输请求消息。对应地，AMF2接收来自AMF1的该UE上下文传输请求消息。
示例性地，AMF1接收到注册请求消息之后，根据该注册请求消息中携带的GUTI，确定上一次为UE提供服务的AMF(记为AMF2)。然后AMF1向AMF2发送UE上下文传输(Namf_Communication_UEContextTransfer)请求消息，以请求获取UE的上下文信息，该UE上下文传输请求消息中包括UE的标识。
S1105，AMF2向AMF1发送UE上下文传输响应消息。对应地，AMF1接收来自AMF2的该UE上下文传输响应消息。
示例性地，AMF2接收到来自AMF1的UE上下文传输请求消息之后，根据UE的标识在数据库中获取UE的UE的上下文信息，然后通过UE上下文传输响应消息将该UE的上下文信息发送给AMF1。
可以理解的是，S1101-S1105仅示例性地描述了UE注册流程中的部分步骤，详细过程可参考现有协议，这里不再赘述。
S1106，AMF1向CHF1发送初始请求消息#1。对应地，CHF1接收来自AMF1的该初始请求消息#1。
示例性地，AMF1在UE的注册流程中，例如AMF1在接收到UE上下文传输响应消息之后，向CHF1发送初始请求消息#1，该初始请求消息#1用于请求对UE进行计费。
可以理解的是，AMF1向CHF1发送初始请求消息#1的具体实现方式可参考方法400的S401中，计费触发功能网元#1向计费功能网元#1发送计费请求消息#1的实现方式，例如，S1106中的AMF1对应于S401中的计费触发功能网元#1，S1106中的CHF1对应于S401中的计费功能网元#1，S1106中的初始请求消息#1对应于S401中的计费请求消息#1，这里不再赘述。
可以理解的是，在CHF1之前为UE提供计费服务的网元，可以是CHF1，也可以是其他CHF，如CHF2，或专用CHF，本申请对此不作限定。
可选地，S1107，CHF1向专用CHF发送初始请求消息#2。对应地，专用CHF接收来自CHF1的该初始请求消息#2。
可选地，S1108，专用CHF向CHF1发送计费数据。对应地，CHF1接收来自专用CHF的该计费数据。
示例性地，在CHF1本地存储中没有计费数据的情况下，CHF1向专用CHF发送初始请求消息#2，以请求获取UE的计费数据。专用CHF根据CHF1的请求，返回UE的计费数据。具体过程可参考方法400中的S402b-S402c，例如，S1107-S1108中的专用CHF和CHF1分别对应S402b-S402c中的专用计费功能网元和计费功能网元#1，S1107中的初始请求消息#2对应于S402b中的计费数据请求消息#1，S1108中的计费数据对应于S402c中的计费数据#1，这里不再赘述。
S1109，CHF1根据计费数据对UE进行计费。
示例性地，CHF1获取UE的计费数据之后，根据该计费数据对UE进行计费。具体过程可参考方法400中的S402，这里不再赘述。
可选地，AMF1与CHF1之间执行后续计费交互(如计费过程的update请求消息，或者计费结束的termination请求消息等)，具体过程本申请不作限定。
S1110，CHF1向AMF1发送初始响应消息。对应地，AMF1接收来自CHF1的该初始响应消息。
示例性地，CHF1接收来自专用CHF的计费数据之后，向AMF1返回初始响应消息，该初始响应消息用于响应于初始请求消息#1。可以理解的是，本申请不限定S1109和S1110执行的先后顺序。
S1111，AMF1向CHF1发送终止请求消息。对应地，CHF1接收来自AMF1的该终止请求消息。
S1112，CHF1向SMF2发送终止响应消息#2。对应地，SMF2接收来自CHF1的该终止响应消息#2。
示例性地，在UE的PDU会话释放之后(图中没有示出)，AMF1向CHF1发送终止请求(termination request)消息，以请求结束计费会话，即释放AMF与CHF1之间的计费资源。
S1113，CHF1向专用CHF发送计费结果。对应地，专用CHF接收来自CHF1的该计费结果。
S1113与方法400中的S403类似，这里不再赘述。
通过上述方案，在UE的位置变化导致UE的serving CHF发生变化的情况下(如serving CHF由dedicated CHF切换为CHF1)，在UE的注册流程，AMF触发UE就近的CHF1通过dedicated CHF获取UE的计费数据，并为UE提供计费服务，从而可以减少计费过程产生的大量计费信息的跨区传输，节省网络资源，降低运营成本。
本申请实施例提供的方案还可以应用于MEC场景中。例如，在用户访问MEC业务时，如果UE的CHF发生了变化，则可以执行如方法400所示的方案，对UE进行计费。下面结合图12和图13介绍两种MEC场景下对UE进行计费的方案。
需要说明的是，在图12的方法1200以及图13的方法1300中，MEC1 CTF和MEC2 CTF均指的是MEC场景下的CTF，其中MEC2 CTF是在MEC1 CTF之前为UE提供服务的CTF，CHF1和CHF2都是为UE提供计费服务的网元，其中CHF2是在CHF1之后为UE提供计费服务的，也就是说，在方法1200和方法1300中，UE的serving CHF由CHF1切换为CHF2。
方法1200和方法1300是方法400中的流程1和流程2应用在MEC场景下的两种可能的实现方式。在方法1200和方法1300中，以专用计费功能网元为专用CHF(dedicated CHF)、计费触发功能网元#1为MEC1 CTF、计费触发功能网元#2为MEC2 CTF、计费功能网元#1为CHF1、计费功能网元#2为CHF2为例进行说明。
图12示出了本申请实施例提供的方法1200的示例性流程图。在方法1200中，先结束MEC1 CTF与CHF1之间的计费会话，然后再建立MEC2 CTF与CHF2之间的计费会话。下面结合图12中的各个步骤对方法1200作示例性说明。
S1201，MEC1 CTF向CHF1发送初始请求消息#1。对应地，CHF1接收来自MEC1 CTF的该初始请求消息#1。
示例性地，在用户在MEC1上的业务开始后，MEC1 CTF向CHF1发送初始请求消息#1，以请求CHF1对UE在MEC1上的业务进行计费。
具体过程可参考方法400中的S401部分的描述，其中S1201中的MEC1 CTF可对应于S401中的计费触发功能网元#1，S1201中的CHF1可对应于S401中的计费功能网元#1，这里不再赘述。
可选地，S1202，CHF1向专用CHF发送初始请求消息#2。对应地，专用CHF接收来自CHF1的该计 费请求消息#2。
示例性地，在CHF1本地存储中没有存储有UE的计费数据的情况下，CHF1向专用CHF发送初始请求消息#2。具体过程可参考方法400中的S402b部分的描述，其中，S1202中的初始请求消息#2可以对应于S402b中的计费数据请求消息#1，这里不再赘述。
可选地，S1203，专用CHF向CHF1发送计费数据#1。对应地，CHF1接收来自专用CHF的该计费数据#1。
示例性地，专用CHF接收来自CHF1的该初始请求消息#2之后，在本地查询UE的计费数据#1，然后将该计费数据#1发送给CHF1。具体过程可参考方法400中的S402c部分的描述，这里不再赘述。
S1204，CHF1根据计费数据#1对UE进行计费处理。
示例性地，CHF1获取UE的计费数据之后，对UE进行计费处理。具体过程可参考方法400中的S402部分的描述，这里不再赘述。
S1205，CHF1向MEC1 CTF发送初始响应消息#1。对应地，MEC1 CTF接收来自CHF1的初始响应消息#1。
S1206，MEC1 CTF向CHF1发送终止请求消息#1。对应地，CHF1接收来自MEC1 CTF的终止请求消息#1。
示例性地，MEC1 CTF向CHF1发送终止请求(termination request)消息，以请求结束MEC1与CHF1间该用户的MEC业务的计费资源结束计费请求。
S1207，CHF1向MEC1 CTF发送终止响应消息#1。对应地，MEC1 CTF接收来自CHF1的该终止响应消息#1。
示例性地，MEC1 CTF向CHF1发送终止请求消息，以请求释放MEC1 CTF与CHF1间的MEC业务的计费资源。CHF1接收来自SMF1的终止请求消息#1之后，释放计费资源，并返回终止响应(termination response)消息。
S1208，CHF1向专用CHF发送计费结果#1。对应地，专用CHF接收来自CHF1的该计费结果#1。
S1208与方法400中的S403类似，这里不再赘述。
S1209，MEC2 CTF向CHF2发送初始请求消息#3。对应地，CHF2接收来自MEC2 CTF的该初始请求消息#3。
示例性地，根据MEC实现的业务会话切换方法或者MEC上配置的切换模式，在MEC1 CTF与CHF1之间的计费会话结束之后，且在用户在MEC2上的业务开始后，MEC2 CTF向CHF1发送初始请求消息#3，以请求CHF2对UE在MEC2上的业务进行计费。
具体实现方式可参考方法400中的S404部分的描述，其中S1209中的初始请求消息#3可对应于S404中的计费请求消息#2，这里不再赘述。
S1210，CHF2向专用CHF发送初始请求消息#4。对应地，专用CHF接收来自CHF2的该初始请求消息#4。
示例性地，CHF2接收来自CHF1的初始请求消息#3之后，向专用CHF发送初始请求消息#4，以请求获取UE的计费数据#2。具体过程可参考方法400中的S405部分的描述，其中S1210中的初始请求消息#4可对应于S405中个的计费数据请求消息#2，这里不再赘述。
S1211，专用CHF向CHF2发送计费数据#2。对应地，CHF2接收来自专用CHF的该计费数据#2。
示例性地，专用CHF接收来自CHF2的该初始请求消息#4之后，在本地查询UE的计费数据#2，然后将该计费数据#2发送给CHF2。具体过程可参考方法400中的S406部分的描述，这里不再赘述。
S1212，CHF2根据计费数据#1对UE进行计费处理。
示例性地，CHF2获取UE的计费数据之后，对UE进行计费处理。具体过程可参考方法400中的S407部分的描述，这里不再赘述。
S1213，CHF2向MEC2 CTF发送初始响应消息#1。对应地，MEC2 CTF接收来自CHF2的初始响应消息#1。
S1214，MEC2 CTF向CHF2发送终止请求消息#2。对应地，CHF2接收来自MEC2 CTF的终止请求消息#2。
S1215，CHF2向MEC2 CTF发送终止响应消息#2。对应地，MEC2 CTF接收来自CHF2的该终止响应消息#2。
S1216，CHF2向专用CHF发送计费结果#2。对应地，专用CHF接收来自CHF2的该计费结果#2。
可以理解的是，S1216与方法400中的S408类似，为了简洁，这里不再赘述。
通过上述方案，在MEC场景下，在UE的位置变化导致UE的serving CHF发生变化的情况下，MEC CTF触发UE就近的CHF为UE提供计费服务，UE就近的CHF通过专用CHF获取用户的计费数据，并根据该计费数据对UE进行计费处理，从而可以减少计费过程产生的大量计费信息的跨区传输，节省网络资源，降低运营成本。
图13示出了本申请实施例提供的方法1300的示例性流程图。在方法1300中，先建立MEC2 CTF与CHF2的计费，然后结束MEC1 CTF与CHF1的计费。下面结合图13中的各个步骤对方法1300作示例性说明。
可以理解的是，S1301-S1305与方法1200中的S1201-S1205类似，为了简洁，这里不再赘述。
S1306，MEC1 CTF向CHF2发送初始请求消息#3。对应地，CHF2接收来自MEC1 CTF的该初始请求消息#3。
示例性地，在用户在MEC2上的业务开始后，MEC2 CTF向CHF2发送初始请求消息#3，以请求CHF2对UE在MEC2上的业务进行计费。具体实现方式可参考方法400中的S404部分的描述，其中S1306中的初始请求消息#3可对应于S404中的计费请求消息#2，这里不再赘述。
可以理解的是，在执行S1306的时候，MEC1 CTF和CHF1的计费结束还没有结束。
S1307-S1310与方法1200中的S1210-S1213类似，这里不再赘述。
S1311，MEC1 CTF向CHF1发送终止请求消息#1。对应地，CHF1接收来自MEC1 CTF的终止请求消息#1。
示例性地，在MEC2 CTF与CHF2之间的计费建立完成之后，MEC1 CTF向CHF1发送终止请求(termination request)消息，以请求结束MEC1与CHF1间该用户的MEC业务的计费资源结束计费请求。
可以理解的是，MEC2 CTF向CHF2发送初始请求消息#3的时机是在MEC1 CTF与CHF1之间的计费会话结束之前还是之后，取决于网络侧用户业务会话切换的时机。
S1312，CHF1向MEC1 CTF发送终止响应消息#1。对应地，MEC1 CTF接收来自CHF1的该终止响应消息#1。
S1313，CHF1向专用CHF发送计费结果#1。对应地，专用CHF接收来自CHF1的该计费结果#1。
S1313与方法400中的S403类似，这里不再赘述。
S1314-S1316与方法1200中的S1214-S1216类似，为了简洁，这里不再赘述。
通过上述方案，在MEC场景下，在UE的位置变化导致UE的serving CHF发生变化的情况下，MEC CTF触发UE就近的CHF为UE提供计费服务，UE就近的CHF通过专用CHF获取用户的计费数据，并根据该计费数据对UE进行计费处理，从而可以减少计费过程产生的大量计费信息的跨区传输，节省网络资源，降低运营成本。
相应于上述各方法实施例给出的方法，本申请实施例还提供了相应的装置，该装置包括用于执行上述各个方法实施例相应的模块。该模块可以是软件，也可以是硬件，或者是软件和硬件结合。可以理解的是，上述各方法实施例所描述的技术特征同样适用于以下装置实施例，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
图14是本申请实施例提供的通信装置10的示意性框图。该装置10包括收发模块11和/或处理模块12。收发模块11可以实现相应的通信功能，处理模块12用于进行数据处理，或者说该收发模块11用于执行接收和发送相关的操作，该处理模块12用于执行除了接收和发送以外的其他操作。收发模块11还可以称为通信接口或通信单元。
可选地，该装置10还可以包括存储模块13，该存储模块13可以用于存储指令和/或数据，处理模块12可以读取存储模块中的指令和/或数据，以使得装置实现前述各个方法实施例中设备或网元的动作。
在第一种设计中，该装置10可对应于上文方法实施例中的计费功能网元(例如图4中的计费功能网元，或是图5-图13中的CHF1或CHF2)，或者是计费功能网元的组成部件(如芯片)。
该装置10可实现对应于上文方法实施例中的计费功能网元执行的步骤或者流程，其中，收发模块11可用于执行上文方法实施例中计费功能网元的收发相关的操作，处理模块12可用于执行上文方法实施例中计费功能网元的处理相关的操作。
在一种可能的实现方式，收发模块11，用于接收来自计费触发功能网元的计费请求消息，该计费请 求消息用于请求对终端设备进行计费；处理模块12，用于根据该终端设备的计费数据对该终端设备进行计费处理，该计费数据是该计费装置从专用计费功能网元接收到的，该专用计费功能网元属于持久化存储该终端设备的用户数据的计费系统。
在第二种设计中，该装置10可对应于上文方法实施例中的专用计费功能网元(例如图4中的专用计费功能网元，或是图5至图13中的专用CHF，或者是专用计费功能网元的组成部件(如芯片)。
该装置10可实现对应于上文方法实施例中的专用计费功能网元执行的步骤或者流程，其中，收发模块11可用于执行上文方法实施例中专用计费功能网元的收发相关的操作，处理模块12可用于执行上文方法实施例中专用计费功能网元的处理相关的操作。
在一种可能的实现方式，收发模块11，用于接收来自计费功能网元的计费数据请求消息，该计费数据请求消息用于请求获取终端设备的计费数据，该专属计费功能网元属于持久化存储该终端设备的用户数据的计费系统；以及，向该计费功能网元发送该计费数据，该计费数据用于对该终端设备进行计费处理。
在第三种设计中，该装置10可对应于上文方法实施例中的计费触发功能网元(例如图4中的计费触发功能网元，或是图5至图10中的SMF(如图5或图8中的SMF1和SMF2，图6或图9中的SMF2和SMF3，图7或图10中的SMF3和SMF4，)，或是图11中的AMF(包括AMF1和AMF2)，或是图12或图13中的MEC CTF(包括MEC1 CTF和MEC2 CTF)，或者是计费触发功能网元的组成部件(如芯片)。
该装置10可实现对应于上文方法实施例中的计费触发功能网元执行的步骤或者流程，其中，收发模块11可用于执行上文方法实施例中计费触发功能网元的收发相关的操作，处理模块12可用于执行上文方法实施例中计费触发功能网元的处理相关的操作。
在一种可能的实现方式，处理模块12，用于根据该计费触发功能网元的信息和/或终端设备的位置信息获取该计费功能网元的地址信息；收发模块11，用于向该计费功能网元发送计费请求消息，该计费请求消息用于请求该计费功能网元对该终端设备进行计费。
应理解，各模块执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
还应理解，这里的装置10以功能模块的形式体现。这里的术语“模块”可以指应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中，本领域技术人员可以理解，装置10可以具体为上述实施例中的计费功能网元，可以用于执行上述各方法实施例中与计费功能网元对应的各个流程和/或步骤；或者，装置10可以具体为上述实施例中的计费触发功能网元，可以用于执行上述各方法实施例中与计费触发功能网元对应的各个流程和/或步骤，为避免重复，在此不再赘述。
上述各个方案的装置10具有实现上述方法中的设备(如计费功能网元，或计费触发功能网元)所执行的相应步骤的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块；例如收发模块可以由收发机替代(例如，收发模块中的发送单元可以由发送机替代，收发模块中的接收单元可以由接收机替代)，其它单元，如处理模块等可以由处理器替代，分别执行各个方法实施例中的收发操作以及相关的处理操作。
此外，上述收发模块11还可以是收发电路(例如可以包括接收电路和发送电路)，处理模块可以是处理电路。
图15是本申请实施例提供另一种通信装置20的示意图。该装置20包括处理器21，处理器21用于执行上文各方法实施例中与处理相关的操作。可选地，处理器21为一个或多个。该装置20还包括收发器22，收发器22用于信号的接收和/或发送。例如，处理器21用于控制收发器22进行信号的接收和/或发送。可选地，收发器22为一个或多个。
可选地，如图15所示，该装置20还包括存储器23，存储器23用于存储计算机程序或指令和/或数据。该存储器23可以与处理器21集成在一起，或者也可以分离设置，处理器21可以读取存储器22存储的计算机程序或指令，以执行上文各方法实施例中的方法。可选地，存储器23为一个或多个。
作为一种方案，该装置20用于实现上文各个方法实施例中由计费功能网元执行的操作。
作为另一种方案，该装置20用于实现上文各个方法实施例中由计费触发功能网元执行的操作。
应理解，本申请实施例中提及的处理器可以是中央处理模块(central processing unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器和/或非易失性存储器。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。例如，RAM可以用作外部高速缓存。作为示例而非限定，RAM包括如下多种形式：静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
图16是本申请实施例提供一种芯片系统30的示意图。该芯片系统30(或者也可以称为处理系统)包括逻辑电路31以及输入/输出接口(input/output interface)32。
其中，逻辑电路31可以为芯片系统30中的处理电路。逻辑电路31可以耦合连接存储单元，调用存储单元中的指令，使得芯片系统30可以实现本申请各实施例的方法和功能。输入/输出接口32，可以为芯片系统30中的输入输出电路，将芯片系统30处理好的信息输出，或将待处理的数据或信令信息输入芯片系统30进行处理。
作为一种方案，该芯片系统30用于实现上文各个方法实施例中由计费功能网元执行的操作。
例如，逻辑电路31用于实现上文方法实施例中由计费功能网元执行的处理相关的操作，如，图4所示实施例中的计费功能网元，或是图5至图13中的CHF执行的处理相关的操作；输入/输出接口32用于实现上文方法实施例中由计费功能网元执行的发送和/或接收相关的操作，如图4所示实施例中的计费功能网元或是图5至图13中的CHF执行的发送和/或接收相关的操作。
作为另一种方案，该芯片系统30用于实现上文各个方法实施例中由专用计费功能网元执行的操作。
例如，逻辑电路31用于实现上文方法实施例中由专用计费功能网元执行的处理相关的操作，如，图4所示实施例中的专用计费功能网元，或是图5至图13中的专用CHF执行的处理相关的操作；输入/输出接口32用于实现上文方法实施例中由计费功能网元执行的发送和/或接收相关的操作，如图4所示实施例中的计费功能网元或是图5至图13中的专用CHF执行的发送和/或接收相关的操作。
作为又一种方案，该芯片系统30用于实现上文各个方法实施例中由计费触发功能网元执行的操作。
例如，逻辑电路31用于实现上文方法实施例中由计费触发功能网元执行的处理相关的操作，如，图4所示实施例中的计费触发功能网元，或是图5至图10中的SMF，或是图11至图13中的AMF，或是图14至图16中的MEC CTF执行的处理相关的操作；输入/输出接口32用于实现上文方法实施例中由计费触发功能网元执行的发送和/或接收相关的操作，如，图4所示实施例中的计费触发功能网元，或是图5至图10中的SMF，或是图11至图13中的AMF，或是图14至图16中的MEC CTF执行的发送和/或接收相关的操作。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述各方法实施例中由设备执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法各实施例中由计费功能网元执行的方法。
又如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法各实施例中由计费触发功能网元执行的方法。
本申请实施例还提供一种计算机程序产品，包含指令，该指令被计算机执行时以实现上述各方法实 施例中由设备(如计费功能网元，又如计费触发功能网元)执行的方法。
本申请实施例还提供了一种通信系统，包括前述的计费功能网元和计费触发功能网元。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。此外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。例如，所述计算机可以是个人计算机，服务器，或者计费触发功能网元等。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD)等。例如，前述的可用介质包括但不限于：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种计费方法，其特征在于，包括：
    计费功能网元接收来自计费触发功能网元的计费请求消息，所述计费请求消息用于请求对终端设备进行计费；
    所述计费功能网元根据所述终端设备的计费数据对所述终端设备进行计费处理，所述计费数据是所述计费功能网元从专用计费功能网元接收到的，所述专用计费功能网元属于持久化存储所述终端设备的用户数据的计费系统。
  2. 根据权利要求1所述的方法，其特征在于，在所述计费功能网元根据所述终端设备的计费数据对所述终端设备进行计费处理之前，所述方法还包括：
    所述计费功能网元向所述专用计费功能网元发送计费数据请求消息；
    所述计费功能网元接收来自所述专用计费功能网元的所述计费数据。
  3. 根据权利要求2所述的方法，其特征在于，所述计费功能网元向所述专用计费功能网元发送计费数据请求消息，包括：
    所述计费功能网元在确定本地存储中没有所述计费数据的情况下，向所述专用计费功能网元发送所述计费数据请求消息。
  4. 根据权利要求2或3所述的方法，其特征在于，所述方法还包括：
    所述计费功能网元获取所述专用计费功能网元的地址信息；
    所述计费功能网元向所述专用计费功能网元发送计费数据请求消息，包括：
    所述计费功能网元根据所述地址信息向所述专用计费功能网元发送计费数据请求消息。
  5. 根据权利要求4所述的方法，其特征在于，所述计费功能网元获取所述专用计费功能网元的地址信息，包括：
    所述计费功能网元向网络存储功能网元发送查询请求消息，所述查询请求消息包括所述终端设备的标识，所述查询请求消息用于请求查询所述终端设备对应的所述专用计费功能网元；
    所述计费功能网元接收来自所述网络存储功能网元的所述专用计费功能网元的地址信息。
  6. 根据权利要求4所述的方法，其特征在于，所述计费功能网元获取所述专用计费功能网元的地址信息，包括：
    所述计费功能网元从所述计费请求消息中获取所述专用计费功能网元的地址信息。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，在所述计费功能网元根据所述终端设备的计费数据对所述终端设备进行计费处理之后，所述方法还包括：
    所述计费功能网元向所述专用计费功能网元发送计费结果，所述计费结果是所述计费功能网元对所述终端设备进行计费处理之后得到的数据。
  8. 一种计费方法，其特征在于，包括：
    专用计费功能网元接收来自计费功能网元的计费数据请求消息，所述计费数据请求消息用于请求获取终端设备的计费数据，所述专属计费功能网元属于持久化存储所述终端设备的用户数据的计费系统；
    响应于所述计费数据请求消息，所述专用计费功能网元向所述计费功能网元发送所述计费数据，所述计费数据用于对所述终端设备进行计费处理。
  9. 根据权利要求8所述的方法，其特征在于，在所述专用计费功能网元向所述计费功能网元发送终端设备的计费数据之后，所述方法还包括：
    所述专用计费功能网元接收来自其他计费功能网元的第一计费结果，所述第一计费结果为所述其他计费功能网元对所述终端设备进行计费处理之后得到的数据，所述其他计费功能网元是在所述计费功能网元之前为所述终端设备提供计费服务的网元；
    所述专用计费功能网元根据所述第一计费结果，判断是否需要向所述计费功能网元更新所述终端设备的计费数据；
    在需要向所述计费功能网元更新所述终端设备的计费数据的情况下，所述专用计费功能网元向所述计费功能网元发送更新后的计费数据。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述专用计费功能网元记录所述计费功能网元是当前为所述终端设备提供计费服务的网元。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    所述专用计费功能网元接收查询请求消息，所述查询请求消息包括所述终端设备标识，所述查询请求消息用于请求查询当前为所述终端设备提供计费服务的网元；
    所述专用计费功能网元根据所述记录返回所述计费功能网元的地址信息。
  12. 根据权利要求9至11中任一项所述的方法，其特征在于，所述方法还包括：
    所述专用计费功能网元接收来自所述计费功能网元的计费结果，所述计费结果为所述计费功能网元对所述终端设备进行计费处理之后得到的数据
    所述专用计费功能网元根据所述计费结果更新所述计费数据。
  13. 一种计费方法，其特征在于，包括：
    计费触发功能网元根据所述计费触发功能网元的信息和/或终端设备的位置信息获取所述计费功能网元的地址信息；
    所述计费触发功能网元根据所述地址信息，向所述计费功能网元发送计费请求消息，所述计费请求消息用于请求所述计费功能网元对所述终端设备进行计费。
  14. 根据权利要求13所述的方法，其特征在于，所述计费触发功能网元根据所述计费触发功能网元的信息和/或终端设备的位置信息获取所述计费功能网元的地址信息，包括：
    所述计费触发功能网元向网络存储功能网元发送查询请求消息，所述查询请求消息用于请求获取用于对终端设备执行计费处理的候选计费功能网元的地址信息，所述查询请求消息包括所述终端设备的位置信息和/或所述计费触发功能网元的信息；
    所述计费触发功能网元接收来自所述存储功能网元的所述计费功能网元的地址信息。
  15. 根据权利要求13所述的方法，其特征在于，所述计费触发功能网元根据所述计费触发功能网元的信息和/或终端设备的位置信息获取所述计费功能网元的地址信息，包括：
    所述计费触发功能网元根据所述终端设备的位置信息和/或所述计费触发功能网元的信息，在本地配置信息中确定与所述终端设备的位置信息和/或所述计费触发功能网元的信息对应的所述计费功能网元的地址信息。
  16. 根据权利要求13至15中任一项所述的方法，其特征在于，所述计费请求消息包括专用计费功能网元的地址信息，所述专用计费功能网元属于持久化存储该UE用户数据的计费系统。
  17. 一种计费方法，其特征在于，包括：
    计费触发功能网元向计费功能网元发送计费请求消息，所述计费请求消息用于请求对终端设备进行计费处理；
    所述计费功能网元接收来自所述计费触发功能网元的所述计费请求消息；
    所述计费功能网元根据所述终端设备的计费数据对所述终端设备进行计费处理，所述计费数据是所述计费功能网元从专用计费功能网元接收到的，所述专用计费功能网元属于持久化存储所述终端设备的用户数据的计费系统。
  18. 根据权利要求17所述的方法，其特征在于，在所述计费功能网元根据所述终端设备的计费数据对所述终端设备进行计费处理之前，所述方法还包括：
    所述计费功能网元向所述专用计费功能网元发送计费数据请求消息；
    响应于所述计费数据请求消息，所述专用计费功能网元向所述计费功能网元发送所述计费数据；
    所述计费功能网元接收来自所述专用计费功能网元的所述计费数据。
  19. 根据权利要求18所述的方法，其特征在于，所述计费功能网元向所述专用计费功能网元发送计费数据请求消息，包括：
    所述计费功能网元在确定本地存储中没有所述计费数据的情况下，向所述专用计费功能网元发送所述计费数据请求消息。
  20. 根据权利要求18或19所述的方法，其特征在于，所述方法还包括：
    所述计费功能网元获取所述专用计费功能网元的地址信息；
    所述计费功能网元向所述专用计费功能网元发送计费数据请求消息，包括：
    所述计费功能网元根据所述地址信息向所述专用计费功能网元发送计费数据请求消息。
  21. 根据权利要求20所述的方法，其特征在于，所述计费功能网元获取所述专用计费功能网元的地 址信息，包括：
    所述计费功能网元向网络存储功能网元发送查询请求消息，所述查询请求消息包括所述终端设备的标识，所述查询请求消息用于请求查询所述终端设备对应的所述专用计费功能网元；
    所述网络存储功能网元根据所述终端设备的标识确定所述专用计费功能网元；
    所述网络存储功能网元向所述计费功能网元发送所述专用计费功能网元的地址信息；
    所述计费功能网元接收来自所述网络存储功能网元的所述专用计费功能网元的地址信息。
  22. 根据权利要求20所述的方法，其特征在于，所述计费功能网元获取所述专用计费功能网元的地址信息，包括：
    所述计费功能网元从所述计费请求消息中获取所述专用计费功能网元的地址信息。
  23. 根据权利要求17至22中任一项所述的方法，其特征在于，在所述计费功能网元根据所述终端设备的计费数据对所述终端设备进行计费处理之后，所述方法还包括：
    所述计费功能网元向所述专用计费功能网元发送计费结果，所述计费结果是所述计费功能网元对所述终端设备进行计费处理之后得到的数据；
    所述专用计费功能网元接收来自所述计费功能网元的所述计费结果。
  24. 根据权利要求17至23中任一项所述的方法，其特征在于，在所述专用计费功能网元向所述计费功能网元发送终端设备的计费数据之后，所述方法还包括：
    所述专用计费功能网元接收来自其他计费功能网元的第一计费结果，所述第一计费结果为所述其他计费功能网元对所述终端设备进行计费处理之后得到的数据，所述其他计费功能网元是在所述计费功能网元之前为所述终端设备提供计费服务的网元；
    所述专用计费功能网元根据所述第一计费结果，判断是否需要向所述计费功能网元更新所述终端设备的计费数据；
    在需要向所述计费功能网元更新所述终端设备的计费数据的情况下，所述专用计费功能网元向所述计费功能网元发送更新后的计费数据；
    所述计费功能网元接收来自所述专用功能网元的所述更新后的计费数据。
  25. 根据权利要求17至24中任一项所述的方法，其特征在于，所述方法还包括：
    所述专用计费功能网元记录所述计费功能网元是当前为所述终端设备提供计费服务的网元。
  26. 一种通信装置，其特征在于，所述装置包括：用于执行如权利要求1至7中任一项所述的方法的模块，或者用于执行如权利要求8至12中任一项所述的方法的模块，或者用于执行如权利要求13至16中任一项所述的方法的模块。
  27. 一种通信装置，其特征在于，包括：
    处理器，用于执行存储器中存储的计算机程序，以使得所述装置执行如权利要求1至7中任一项所述的方法，或者以使得所述装置执行如权利要求8至12中任一项所述的方法，或者以使得所述装置执行如权利要求13至16中任一项所述的方法。
  28. 一种计算机程序产品，其特征在于，所述计算机程序产品包括用于执行如权利要求1至7中任一项所述的方法的指令，或者，所述计算机程序产品包括用于执行如权利要求8至12中任一项所述的方法的指令，或者，所述计算机程序产品包括用于执行如权利要求13至16中任一项所述的方法的指令或者。
  29. 一种计算机可读存储介质，其特征在于，包括：所述计算机可读存储介质存储有计算机程序；所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至7中任一项所述的方法，或者使得所述计算机执行如权利要求8至12中任一项所述的方法，或者使得所述计算机执行如权利要求13至16中任一项所述的方法。
  30. 一种通信系统，其特征在于，包括计费功能网元、专用计费功能网元和计费触发功能网元，
    其中，所述计费功能网元用于执行如权利要求1至7中任一项所述的方法，所述专用计费功能用于执行如权利要求8至12中任一项所述的方法，所述计费触发功能网元用于执行如权利要求13至16中任一项所述的方法。
PCT/CN2023/137058 2022-12-16 2023-12-07 计费方法和装置 WO2024125382A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211627897.1A CN118215014A (zh) 2022-12-16 2022-12-16 计费方法和装置
CN202211627897.1 2022-12-16

Publications (1)

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

Family

ID=91449580

Family Applications (1)

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

Country Status (2)

Country Link
CN (1) CN118215014A (zh)
WO (1) WO2024125382A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110417560A (zh) * 2018-04-28 2019-11-05 华为技术有限公司 计费的方法、装置及系统
CN112449316A (zh) * 2019-08-30 2021-03-05 华为技术有限公司 一种漫游计费的处理方法、装置及系统
CN113068139A (zh) * 2017-11-16 2021-07-02 华为技术有限公司 一种融合计费的方法和设备
US20220247827A1 (en) * 2021-01-29 2022-08-04 Nokia Technologies Oy Apparatus, methods, and computer programs

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113068139A (zh) * 2017-11-16 2021-07-02 华为技术有限公司 一种融合计费的方法和设备
CN110417560A (zh) * 2018-04-28 2019-11-05 华为技术有限公司 计费的方法、装置及系统
CN112449316A (zh) * 2019-08-30 2021-03-05 华为技术有限公司 一种漫游计费的处理方法、装置及系统
US20220247827A1 (en) * 2021-01-29 2022-08-04 Nokia Technologies Oy Apparatus, methods, and computer programs

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on charging aspects for enhanced support of non-public networks (Release 18)", 3GPP TR 28.828, no. V0.4.0, 21 September 2022 (2022-09-21), pages 1 - 40, XP052210834 *
HUAWEI: "Discussion paper on online charging and offline charging", 3GPP TSG SA WG5 (TELECOM MANAGEMENT) MEETING #120, S5- 185106, 10 August 2018 (2018-08-10), XP051542958 *
NOKIA, NOKIA SHANGHAI BELL: "Correction on Registration flows and message content", 3GPP TSG SA WG5 MEETING 136-E TDOC, S5-212098, 22 February 2021 (2021-02-22), XP051980587 *

Also Published As

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

Similar Documents

Publication Publication Date Title
WO2020063317A1 (zh) 一种通信方法及装置
JP7184922B2 (ja) Ｕｅのためにポリシーを構成するための方法、装置、及びシステム
EP3737157B1 (en) Switching pdu sessions with the same dnn from a 5g network to pdn connections of a 4g network having the same apn
CN110831007B (zh) 用户面完整性保护方法、装置及设备
CN111586770B (zh) 一种会话管理的方法及装置
WO2022089164A1 (zh) 多路径传输方法和通信装置
CN113873478A (zh) 通信方法及装置
CN111031538A (zh) 一种鉴权的方法及装置
CN113811025A (zh) 一种释放中继连接的方法、设备及系统
EP4322657A1 (en) Information transmission method, system, and apparatus
WO2024125382A1 (zh) 计费方法和装置
CN113573297A (zh) 一种通信方法及装置
WO2024125383A1 (zh) 计费方法、装置和系统
CN116939512A (zh) 群组通信的方法、装置和系统
CN113412679B (zh) 通信方法及装置
KR102536522B1 (ko) 서버의 제어 방법 및 서버
WO2024066436A1 (zh) 一种通信方法及装置
WO2024067669A1 (zh) 通信方法和装置
CN117729597B (zh) 候选小区配置信息的处理方法、设备、存储介质及产品
CN114868426B (zh) 一种网络切片重定向的方法和装置
WO2023246620A1 (zh) 通信方法、装置和系统
WO2024104246A1 (zh) 通信方法和通信装置
CN111869309B (zh) 在无线通信系统中建立用于与局域网通信的会话的方法、装置和系统
KR20240034877A (ko) 보안 송신 채널을 확립하기 위한 방법, 키 결정 방법, 및 통신 장치
CN117135752A (zh) 一种用于切换的通信方法和通信装置