A charging message processing method and related equipment, CHF cluster

Abstract

The present application discloses a billing message processing method and related equipment, and a CHF cluster, which relates to the field of communications and is applied to a CHF cluster. The CHF cluster includes an LB module and multiple CHF network elements, and each CHF network element includes a CAF, a service instance, and a network element shared memory, including: the LB module sends the billing message to the target CHF network element according to the mapping relationship; the CAF stores the billing data in the billing message into the network element shared memory, determines and notifies the service instance group, processes the billing data, and stores the processing result into the network element shared memory; when an exception occurs in the service instance, the target service instance is determined and notified from other service instances, so that the target service instance obtains the billing data that the abnormal service instance is responsible for from the network element shared memory for processing, and the processing result is stored in the network element shared memory. In the present application, when an exception occurs in a service instance, other service instances take data from the network element shared memory to continue processing, so as to ensure continuous processing of the billing message.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a charging message processing method and related equipment, and a CHF cluster. Background Art

[0002] With the rapid development of communication networks, users can use devices connected to the network to carry out activities such as communication and entertainment. When users use the network, traffic (the amount of data transmitted using the network) is generated and they need to pay fees to the operators or service providers that provide the network.

[0003] The core network system of the operator or service provider receives the billing message (including traffic request information, timestamp and other data) reported by the user device and sends it to the CHF for processing, generating bills and expense reports for users to pay. The CHF may contain service instances, which are responsible for processing various tasks and data related to billing.

[0004] When an exception or failure occurs in a service instance in a CHF, it is difficult to process subsequent billing messages of the CHF. Therefore, when an exception or failure occurs in a service instance, how to effectively process subsequent billing messages of the CHF is a technical problem that needs to be solved urgently. Summary of the invention

[0005] In view of the above problems, the present application provides a charging message processing method and related equipment, and a CHF cluster to achieve the purpose of processing subsequent charging messages of CHF network elements. The specific scheme is as follows:

[0006] In a first aspect, the present application provides a charging message processing method, which is applied to a charging function CHF cluster, wherein the CHF cluster includes a load sharing management LB module and multiple CHF network elements, each of which includes a charging access component CAF, multiple service instances and a network element shared memory, and the charging message processing method includes:

[0007] The LB module sends the acquired charging message belonging to the charging session to the target CHF network element according to the mapping relationship, wherein the mapping relationship is: the corresponding relationship between the charging session and the CHF network element;

[0008] The target CHF network element stores the billing data in the billing message into the network element shared memory through the CAF, determines and notifies a service instance group that processes the billing data, so that the service instance group obtains the billing data from the network element shared memory for processing, and stores the processing result in the network element shared memory, wherein the service instance group includes at least one service instance;

[0009] If the CAF determines that at least one service instance in the service instance group has an abnormality, it determines and notifies at least one target service instance from other service instances to process the billing data for which the service instance with the abnormality is responsible, so that the target service instance obtains the billing data for which the service instance with the abnormality is responsible from the network element shared memory for processing, and stores the processing result in the network element shared memory. The other service instances are service instances of the same type as the service instance with the abnormality, except for the service instance with the abnormality.

[0010] In a possible implementation, the CHF cluster further includes a cluster shared memory.

[0011] The target CHF network element stores the billing data in the billing message into the network element shared memory through the CAF, determines and notifies a service instance group that processes the billing data, so that the service instance group obtains the billing data from the network element shared memory for processing, and stores the processing result in the network element shared memory, including:

[0012] The target CHF network element stores the charging data in the charging message synchronously in the cluster shared memory and the network element shared memory through the CAF, determines and notifies the service instance group that processes the charging data, so that the service instance group obtains the charging data from the network element shared memory for processing, and synchronously stores the processing result in the cluster shared memory and the network element shared memory;

[0013] When the LB module determines that the target CHF network element is abnormal, a CHF network element is determined from other CHF network elements, and the target CHF network element is updated so that the updated target CHF network element obtains the data that the abnormal target CHF network element is responsible for processing from the cluster shared memory, and the other CHF network elements are CHF network elements other than the abnormal target CHF network element.

[0014] In a possible implementation, the method further includes:

[0015] The LB module selects the target CHF network element according to a load sharing algorithm in response to a request to establish a charging session;

[0016] A mapping relationship between the charging session and the target CHF network element is established, and the mapping relationship is stored in the cluster shared memory.

[0017] In a possible implementation, the method further includes:

[0018] When the target CHF network element is abnormal, the LB module selects a CHF network element from other CHF network elements according to a load sharing algorithm, and updates the target CHF network element, wherein the other CHF network elements are CHF network elements other than the abnormal target CHF network element;

[0019] The mapping relationship is updated so that the LB module sends subsequent charging messages belonging to the abnormal target CHF network element to the updated target CHF network element for processing.

[0020] In a possible implementation, the LB module includes an active LB module and a standby LB module, and the charging message processing method further includes:

[0021] When the active LB module fails, the standby LB module is started.

[0022] In a possible implementation, the CAF determines a service instance group for processing the charging data, including:

[0023] The CAF selects at least one service instance from a plurality of service instances in the target CHF network element according to a load sharing algorithm, and obtains a service instance group for processing the billing data.

[0024] A second aspect of the present application provides a CHF cluster, the CHF cluster comprising a load sharing management LB module and multiple CHF network elements, each of the CHF network elements comprising a charging access component CAF, multiple service instances and a network element shared memory,

[0025] The LB module is configured to: send the acquired charging message belonging to the charging session to the target CHF network element according to a mapping relationship, wherein the mapping relationship is: a corresponding relationship between the charging session and the CHF network element;

[0026] The target CHF network element is configured to: store the billing data in the billing message into the network element shared memory through the CAF, determine and notify the service instance group that processes the billing data, so that the service instance group obtains the billing data from the network element shared memory for processing, and stores the processing result in the network element shared memory, the service instance group includes at least one service instance;

[0027] The CAF is configured as follows: if it is determined that at least one service instance in the service instance group has an abnormality, at least one target service instance that processes the billing data for which the service instance with the abnormality is responsible is determined from other service instances and notified, so that the target service instance obtains the billing data for which the service instance with the abnormality is responsible from the network element shared memory for processing, and stores the processing result in the network element shared memory. The other service instances are service instances of the same type as the service instance with the abnormality, except for the service instance with the abnormality.

[0028] In a possible implementation, the CHF cluster further includes a cluster shared memory.

[0029] The target CHF network element stores the billing data in the billing message into the network element shared memory through the CAF, determines and notifies the service instance group that processes the billing data, so that the service instance group obtains the billing data from the network element shared memory for processing, and stores the processing result in the network element shared memory, and the specific configuration is:

[0030] The target CHF network element stores the charging data in the charging message synchronously in the cluster shared memory and the network element shared memory through the CAF, determines and notifies the service instance group that processes the charging data, so that the service instance group obtains the charging data from the network element shared memory for processing, and synchronously stores the processing result in the cluster shared memory and the network element shared memory;

[0031] The LB module is further configured to: when it is determined that the target CHF network element is abnormal, determine a CHF network element from other CHF network elements, and update the target CHF network element so that the updated target CHF network element obtains the data that the abnormal target CHF network element is responsible for processing from the cluster shared memory, and the other CHF network elements are CHF network elements other than the abnormal target CHF network element.

[0032] A third aspect of the present application provides an electronic device, comprising at least one processor and a memory connected to the processor, wherein:

[0033] The memory is used to store computer programs;

[0034] The processor is used to execute the computer program so that the electronic device can implement the billing message processing method of the above-mentioned first aspect or any implementation manner of the first aspect.

[0035] The fourth aspect of the present application provides a computer program product, including computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements the billing message processing method of the first aspect or any implementation of the first aspect.

[0036] By means of the above technical solution, the present application provides a method for processing billing messages and related equipment, and a CHF cluster. An additional network element shared memory is set in each CHF network element in the CHF cluster. When a newly acquired billing message needs to be processed, the LB module first determines the target CHF network element for processing the billing message, and then the CAF in the target CHF network element stores the billing data in the billing message into the network element shared memory, and determines and notifies the service instance that processes the billing message. The service instance can directly obtain the billing data from the network element shared memory for processing, and also store the processing result in the network element shared memory. Since the billing data and the processed results processed by the service instance will be stored in the network element shared memory, when at least one service instance in the service instance group that processes the billing data has an exception or failure, other normally operating service instances can take the billing data or processing results that the abnormal service instance is responsible for from the network element shared memory to continue subsequent processing, thereby ensuring the continuous processing of billing messages when an abnormality occurs in the service instance. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale.

[0038] Figure 1 A schematic diagram of the overall structure of a processing billing message provided for this application;

[0039] Figure 2 A schematic diagram of the interaction between an LB module and other modules provided in this application;

[0040] Figure 3 A signaling flow chart of information interaction provided for this application;

[0041] Figure 4 A flowchart of a method for processing billing messages provided in this application;

[0042] Figure 5 A hardware structure block diagram of an electronic device provided in this application. DETAILED DESCRIPTION

[0043] The following describes the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. The terms used in the implementation method section of the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application.

[0044] The embodiments of the present application are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0045] The terms "first", "second" etc. in the specification of the application and the above-mentioned drawings are used to distinguish similar objects, and need not be used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable in appropriate circumstances, and this is only to describe the distinction mode adopted by the objects of the same attributes when describing in the embodiments of the application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0046] Users can use devices connected to the network to carry out activities such as communication and entertainment. When users use the network, traffic (the amount of data transmitted using the network) is generated and they need to pay fees to the network operator or service provider. With the rapid advancement of the commercialization of 5G networks, the number of 5G users and network traffic have increased significantly in the fields of individual customers and vertical industries, accompanied by a large number of 5G billing messages that the network operator or service provider needs to process. The core network system of the operator or service provider receives the billing message reported by the user device (including traffic request information, timestamp and other data), and sends it to the CHF for billing message processing, generating bills and expense reports for users to pay fees. If the 5G billing message is not processed in time and the reliability is low, it will cause serious problems such as untimely response of mobile communication services, degraded service quality, service failure and loss of call records.

[0047] The existing solution for 5G billing message processing can solve some reliability and processing efficiency problems of 5G billing message processing to a certain extent. However, for abnormal CHF situations, such as when a service instance is abnormal or fails, it is difficult to ensure that 5G billing messages are not lost and that subsequent 5G billing messages are processed in an orderly manner.

[0048] In order to solve the above problems, an embodiment of the present application provides a method for processing a billing message, which receives a billing message sent by a 5G core network through a CHF cluster and processes it in the CHF cluster. The CHF cluster of the present method is based on a shared memory. When an exception or failure occurs in a service instance, other normally operating service instances can take the billing data or processing results that the abnormal service instance is responsible for from the shared memory to continue subsequent processing. Therefore, when an exception occurs in a service instance, the processing and response of the billing message can be completed efficiently and reliably, thereby improving the reliability and performance of the billing message processing. The billing message processing method of the embodiment of the present application is described in detail below in conjunction with the accompanying drawings.

[0049] Reference Figure 1 , Figure 1 The overall structure diagram of a processing charging message provided by the embodiment of the present application is as follows. Figure 1 As shown, the overall structure may include a 5G core network (communication network management hub), BD, and CHF cluster. The 5G core network may include multiple network elements, such as SMF (Session Management Function), AMF (Access and Mobility Management Function), and SMSF (Short Message Service Function). Each network element in the 5G core network may call the Nchf interface provided by CHF in accordance with the 3GPP specification through the CTF (Charging Trigger Function) module included, and send a charging message to the CHF cluster to complete the 5G converged charging process. The BD (Billing Domain) cooperates with the CHF cluster to complete the charging function and obtains the CDR transmitted by the CHF cluster from the FTP server. Among them, CDR (Call Detail Record) is a record generated by the operator based on the user's service usage for billing and statistical analysis.

[0050] The CHF cluster in this embodiment may include a VIP module (Virtual IP, virtual IP module), a load sharing management LB module, a HA module, and multiple CHF network elements (such as Figure 1 CHF1, CHF2...CHFn) and the cluster share memory, each CHF network element (such as Figure 1The structure in CHF1 shown in the figure, and the structures in CHF2…CHFn can all be as shown in CHF1) including the charging access component CAF, multiple service instances and network element shared memory. The CHF cluster provides the 5G core network with an Nchf interface that complies with the 3GPP specification. The CHF cluster can obtain 5G charging messages from the 5G core network through the Nchf interface to complete the 5G converged charging process.

[0051] The VIP module shields the IP information in the CHF cluster from the outside, only exposes the virtual IP, and establishes a mapping relationship between the virtual IP and the main LB module in the CHF cluster. The LB module includes the main LB module (such as Figure 1 LB1) and the backup LB module (such as Figure 1 LB2 shown in the figure), when the active LB module fails, the VIP module automatically switches the backup LB module to the active module, the active LB module to the backup module, and establishes a mapping relationship between the virtual IP and the new active module.

[0052] The LB module (Load Balancing) can be responsible for receiving service data and sharing the service data to a CHF network element in the CHF cluster according to the load sharing algorithm. The LB module can also receive data sent by the CHF network element and forward it to the corresponding external system (such as the 5G core network, BD, etc.). There is a heartbeat function between the LB module and the HA module, which can assist the HA module in maintaining the status of the LB module.

[0053] The HA module (High Availability) maintains the status of the LB module (which can be divided into normal heartbeat status and abnormal heartbeat status) through the heartbeat function between the LB module and the LB module. The HA module can select any LB module with a normal heartbeat status as the main module, and cooperate with the VIP module to complete the switching and maintenance of the main and standby status of the LB module.

[0054] The CHF network element can provide an Nchf interface to complete converged billing functions, including online billing processing, offline billing processing, CDR generation and transmission functions.

[0055] like Figure 2The diagram of the interaction between the LB module and other modules is shown. The LB module can be divided into a receiving module, a distribution module, a sending module and a heartbeat module. After the LB module obtains a message from the external system through the receiving module, it forwards it to the CHF through the distribution module. When distributing, if the LB module receives a request to establish a charging session (Charging Data Request [Initial]) of the Nchf interface, the message is forwarded to the CHF network element for processing, and the mapping relationship between the charging session and the CHF network element is recorded; if the LB module receives a request to process a charging message (Charging Data Request [Update]) or a request to terminate a charging session (Charging Data Request [Termination]) of the Nchf interface, the LB module directly forwards the message to the target CHF network element corresponding to the charging session according to the mapping relationship between the charging session and the CHF network element; if the LB module receives a processing result (Charging Data Response), the LB module directly forwards the message to the target CHF network element corresponding to the charging session according to the mapping relationship between the charging session and the CHF network element.

[0056] In this embodiment, the CHF network element may include multiple service instances, and the service instances in the CHF network element may be stateless services. Stateless services are a specific service architecture mode, which is characterized by: the service instance does not need to store persistent data locally, and the results of multiple instances responding to the same request are completely consistent. Figure 1 As shown, the service instances in the CHF network element can be mainly divided into CAF (Charging Access Function), OCF (Online Charging Function), CDF (Charging Data Function) and CGF (Charging Gateway Function). Each CHF network element includes 1 CAF, at least one OCF and at least one CDF. CGF is an optional integrated function of the CHF network element, which means that CGF can be integrated into the CHF network element or can be independent of the CHF network element. Therefore, the number of CGFs in the CHF network element can be 0, 1 or greater than 1. In this embodiment, CGF is integrated into the CHF network element, and the number is at least one.

[0057] CAF is used to distribute the billing messages sent by the 5G core network and distribute them to OCF and CDF for processing. OCF performs online billing processing, CDF performs offline billing processing, and CGF is used for subsequent CDR preprocessing, CDR routing and filtering, CDR file management, and CDR file transfer. CDR preprocessing may include CDR verification, merging and formatting, and persistent CDR storage; CDR routing and filtering may refer to: storing CDRs in separate files according to filtering criteria (such as CDR type, CDR parameters, and initiating CDF, etc.); CDR file management may refer to: CDR file creation, file opening or closing triggers, file deletion, etc.; CDR file transfer may refer to transferring CDR files to BD.

[0058] The CHF cluster exposes the virtual IP to the outside world through the VIP module to connect with the external system. When the CHF cluster in this embodiment expands the CHF network elements, the external system does not need to perceive the changes in the CHF cluster, nor does it need to change the configuration of the external system, change the processing flow or parameters. Similarly, after the CHF cluster is reduced in capacity, the external system does not need to modify the configuration of the external system, change the processing flow or parameters. Furthermore, the expanded CHF network elements can communicate with the LB module through the heartbeat mechanism, and the LB module can also schedule the expanded CHF network elements through the load sharing algorithm. Since the LB module schedules the expanded CHF network elements, it can be achieved that the CHF cluster is not aware of the external system after expansion.

[0059] So far, an example of a 5G charging session initiated by an SMF (CTF) is provided to simply illustrate the interaction between the 5G core network, BD, and CHF clusters. Figure 3 The signaling flow chart of information interaction is shown.

[0060] Step 1: The SMF (CTF) in the 5G core network sends a request to establish a charging session (ChargingData Request[Initial]) to the CHF cluster. The request to establish a charging session is sent to the VIP / LB module in the CHF cluster. The LB module forwards the message to a CHF network element in the CHF cluster according to the load sharing algorithm and establishes a mapping relationship between the charging session and the CHF network element.

[0061] Step 2: After receiving the request to establish a charging session, the CHF network element sends the request to establish a charging session to the BD through the VIP / LB module.

[0062] Step 3: After BD obtains the request to establish a charging session, it initiates a processing result (Charging Data Response) to the VIP / LB module in the CHF cluster. The LB module reads the mapping relationship between the charging session and the CHF network element and forwards the processing result to the CHF network element corresponding to the charging session.

[0063] Step 4: The CHF network element sends the processing result to the SMF (CTF) in the 5G core network through the VIP / LB module.

[0064] Of course, when processing subsequent charging messages in the charging session, the message sent by the SMF (CTF) in the 5G core network to the CHF cluster is: Charging Data Request [Update] .

[0065] Reference Figure 4 , Figure 4 A flowchart of a charging message processing method provided in an embodiment of the present application is shown as follows: Figure 4 As shown, a billing message processing method provided in an embodiment of the present application is applied to the above-mentioned CHF cluster, the CHF cluster includes a load sharing management LB module and multiple CHF network elements, each CHF network element includes a billing access component CAF, multiple service instances and a network element shared memory, the billing message processing method may include steps S10 to S12, and these steps are described in detail below.

[0066] S10. The LB module sends the obtained charging message belonging to the charging session to the target CHF network element according to the mapping relationship, where the mapping relationship is: the corresponding relationship between the charging session and the CHF network element;

[0067] S11. The target CHF network element stores the billing data in the billing message into the network element shared memory through the CAF, determines and notifies the service instance group that processes the billing data, so that the service instance group obtains the billing data from the network element shared memory for processing, and stores the processing result into the network element shared memory; the service instance group includes at least one service instance;

[0068] S12. If CAF determines that at least one service instance in the service instance group has an exception, it determines and notifies at least one target service instance from other service instances that processes the billing data for which the service instance with the exception is responsible, so that the target service instance obtains the billing data for which the service instance with the exception is responsible from the network element shared memory for processing, and stores the processing result in the network element shared memory. The other service instances are service instances of the same type as the service instance with the exception, except for the service instance with the exception.

[0069] A billing message processing method provided by an embodiment of the present application is provided with an additional network element shared memory in each CHF network element in a CHF cluster. When a newly acquired billing message needs to be processed, the LB module first determines the target CHF network element for processing the billing message, and then the CAF in the target CHF network element stores the billing data in the billing message into the network element shared memory, and determines and notifies the service instance for processing the billing message. The service instance can directly obtain the billing data from the network element shared memory for processing, and also store the processing result in the network element shared memory. Since the billing data processed by the service instance and the processed result will be stored in the network element shared memory, when at least one service instance in the service instance group processing the billing data is abnormal or fails, other normally operating service instances can take the billing data or processing results that the abnormal service instance is responsible for from the network element shared memory to continue subsequent processing, thereby ensuring the continuous processing of billing messages when an abnormality occurs in the service instance.

[0070] In addition to setting a network element shared memory in the CHF network element, this embodiment also sets a cluster shared memory in the CHF cluster. Therefore, in a possible implementation, the above step S11 may specifically include:

[0071] The target CHF network element stores the billing data in the billing message synchronously into the cluster shared memory and the network element shared memory through CAF, determines and notifies the service instance group that processes the billing data, so that the service instance group obtains the billing data from the network element shared memory for processing, and stores the processing results synchronously into the cluster shared memory and the network element shared memory.

[0072] Among them, the network element shared memory is the data storage part in the process of CHF network element processing billing messages. The network element shared memory can have multiple implementation methods, such as REDIS (an open source BSD license), in-memory data structure storage system, etc. The network element shared memory can be used as a database, cache and message middleware. Each service instance of the CHF network element shares the relevant data of the billing session through the network element shared memory, so that any service instance of the same type in the CHF network element can process billing data without distinction, and can realize stateless services within the CHF network element, greatly reducing the complexity of interaction between multiple service instances in the CHF network element. Furthermore, sharing billing data through shared memory can reduce the amount of data transmitted within the CHF network element, effectively improving the processing efficiency and performance of the billing process.

[0073] The mapping relationship may refer to the mapping relationship between the billing session and the CHF network element. The LB module may select the target CHF network element according to the load sharing algorithm in response to the request to establish the billing session, establish the mapping relationship between the billing session and the target CHF network element, and store the mapping relationship in the cluster shared memory. Then, when the target CHF network element is abnormal, the LB module may select a CHF network element from other CHF network elements according to the load sharing algorithm, update the target CHF network element and update the mapping relationship in the cluster shared memory, so that the LB module sends the subsequent billing message belonging to the abnormal target CHF network element to the updated target CHF network element for processing. Among them, the other CHF network elements are CHF network elements other than the abnormal target CHF network element.

[0074] The target CHF network element is one of the multiple CHF network elements in the CHF cluster. The target CHF network element has a mapping relationship with the billing session to which the billing message currently obtained by the LB module belongs, and is dedicated to processing all billing messages in the billing session. A user terminal initiating a data service can correspond to creating a billing session. The traffic statistics during the user terminal's continuation of the data service can represent the billing message in a billing session. A billing session can have multiple billing messages. For example, a user terminal watching a short video for a period of time can correspond to a billing session. During the process of watching the short video, the user terminal can trigger the SMF (CTF) to send multiple billing messages to the CHF cluster to count the traffic of the user terminal. Further, when the LB module determines that the target CHF network element is abnormal, a CHF network element can be determined from other CHF network elements, and the target CHF network element can be updated so that the updated target CHF network element obtains the data that the abnormal target CHF network element is responsible for processing from the cluster shared memory. The other CHF network elements are CHF network elements other than the abnormal target CHF network element. The configuration of the cluster shared memory in this embodiment facilitates that when a CHF network element in the CHF cluster fails and cannot provide services, the LB module can forward the subsequent billing messages of the billing session being processed by the failed CHF network element to other CHF network elements for processing, and other CHF network elements can directly obtain the data of the relevant billing messages from the cluster shared memory and continue to process the billing session, without affecting the billing processing of the CHF cluster due to the failed CHF network element. Of course, the LB module in this embodiment can include an active LB module and a standby LB module, and each function is implemented by the active LB module. When the active LB module fails, the standby LB module can be started. Therefore, this embodiment shares the billing session data of each CHF network element through the cluster shared memory of the CHF cluster, which can greatly simplify the compatible processing of the abnormal billing process caused by the CHF network element failure in the CHF cluster. In the case of abnormality in the billing processing module (CHF network element abnormality), the timely switching of the CHF network element by the main LB module and the shared data in the cluster shared memory can ensure that the 5G billing message is not lost and the subsequent 5G billing messages are processed in an orderly manner; after processing the first billing message, when the CHF network element is abnormal or fails, the keep-alive mechanism between the main LB module and the CHF network element is used to delete the faulty CHF network element and update the CHF network element and the shared data in the cluster shared memory, to ensure that the subsequent 5G billing messages can still be processed normally, thereby increasing the reliability of the CHF cluster and effectively improving the reliability and efficiency of 5G services.

[0075] In summary, this embodiment avoids the failure risk of 5G billing process and billing call records caused by failure of some nodes in the CHF cluster through layered shared memory (two layers of shared memory within the CHF cluster and within the CHF network element), and can effectively ensure the efficient and reliable processing of 5G billing process and billing call records.

[0076] Furthermore, when the CAF in this embodiment determines the service instance group for processing the billing data, it can select at least one service instance from multiple service instances in the target CHF network element according to the load sharing algorithm to obtain the service instance group for processing the billing data. When at least one service instance in the service instance group is abnormal, the CAF can also select at least one target service instance for processing the billing data for which the abnormal service instance is responsible according to the load sharing algorithm. Of course, this embodiment may not be limited to replacing the service instance only when the service instance is abnormal. Since each service instance can share data through the network element shared memory, the billing processing and the billing data are separated from each other. Therefore, the CAF can also determine whether to switch the service instance that continues to process the billing message according to the load status of each service instance, so that different billing messages in a billing session can be processed by any service instance of the same type, simplifying the architecture and improving resource utilization.

[0077] Among them, in this embodiment, the CHF network element may mainly include service instances of types such as CAF, OCF, CDF and CGF, and the service instance group for processing billing data determined by CAF may refer to a combination of CDF and CGF. Specifically, CAF determines the CDF and CGF for processing billing messages and notifies CDF, CDF obtains the billing data in the billing message from the network element shared memory and processes it, CDF stores the processing result in the network element shared memory and cluster shared memory synchronously and notifies CGF through internal messages, CGF obtains the processing result of CDF from the network element shared memory and processes it, and stores the processing result in the network element shared memory and cluster shared memory synchronously again. In the CHF network element, offline billing processing of billing messages is mainly implemented by CDF and CGF, and online billing processing of billing messages is implemented by OCF, and offline billing processing and online billing processing can be performed synchronously.

[0078] So far, an embodiment is provided to illustrate the process of performing a complete 5G billing in a CHF network element, involving the process of processing billing messages when establishing a billing session, the process of triggering the sending of billing messages, and the process of terminating the billing session.

[0079] When the SMF (CTF) in the 5G core network has established a PDU session (communication channel between the user terminal and the data network) with the user terminal, the process of processing the charging message when establishing the charging session can be shown in steps 5 to 9:

[0080] Step 5: The user terminal (UE) initiates a data service, and the SMF (CTF) sends a request to establish a charging session (Charging Data Request [Initial]) to the CHF cluster, requesting to establish a charging session and request a quota.

[0081] Step 6: After the CHF cluster obtains the request to establish a billing session, the active LB module selects the target CHF network element according to the load sharing algorithm, establishes a mapping relationship between the billing session and the target CHF network element, and stores the mapping relationship in the cluster shared memory. After the active LB module selects the target CHF network element, it forwards the request to establish a billing session to the target CHF network element.

[0082] Step 7: After the target CHF network element obtains the request to establish a billing session, it forwards it to the BD through the VIP / LB module, and the BD performs quota management, unit reservation, etc. At the same time, the target CHF network element converts the billing data in the request to establish a billing session into call record data, updates the offline call record, and synchronously stores the billing session related data in the network element shared memory and the cluster shared memory during the processing. The processing process of the target CHF network element can be specifically as follows: the billing data in the request to establish a billing session is synchronously stored in the network element shared memory and the cluster shared memory through CAF. CAF determines the CDF and CGF for processing the billing data based on the load sharing algorithm, and notifies CDF. CDF obtains the billing data in the billing message from the network element shared memory and processes it to obtain CDR data. CDF synchronously stores the acquired CDR data in the network element shared memory and the cluster shared memory and notifies CGF through internal messages. CGF obtains CDR data from the network element shared memory and performs CDR preprocessing, CDR routing and filtering, CDR file management and CDR file transfer (transferring files to BD) and other functions, and synchronously stores the processing results in the network element shared memory and the cluster shared memory again.

[0083] Step 8: After receiving the request to establish a charging session, BD reserves the response quota unit based on the internal centralized unit reservation batch price, and interacts with the ABMF (Account Balance Management Function) in the converged charging system to check whether the user account balance corresponding to the user terminal meets the quota unit reservation. If the user account has sufficient balance, BD performs the corresponding reservation unit action and sends the authorized reservation unit quota to the CHF cluster (the information form of the processing result can be expressed as: Charging Data Response) to support the continued use of the service.

[0084] Step 9: The CHF cluster forwards the authorized reserved unit quota to the SMF (CTF) through the VIP / LB module, so that the SMF (CTF) can continue content and service transmission based on the authorized reserved unit quota to support the continued use of the user terminal.

[0085] In the following two cases, SMF (CTF) sends a charging message (Charging Data Request [Update]) of the billing session to the CHF cluster. The two cases are: SMF (CTF) generates billing data related to services not subject to quota management based on the triggers of usage reports; SMF (CTF) generates billing data related to quota management based on the triggers associated with quota management. The processing flow when triggering the sending of the billing message can be shown as steps 10 to 12:

[0086] Step 10: When the CHF cluster receives the billing message, the active LB module reads the mapping relationship between the billing session and the CHF network element from the cluster shared memory, and forwards the billing message to the target CHF network element corresponding to the billing session. After the target CHF network element obtains the billing message, if the billing message carries a quota request, the billing message is forwarded to the BD through the VIP / LB module, and the BD performs quota management, unit reservation, etc. At the same time, the target CHF network element converts the billing data in the billing message into call record data, updates the offline call record, and synchronously stores the billing session related data in the network element shared memory and the cluster shared memory during the processing. (In this step, since the data related to the billing session in the processing process are all in the network element shared memory, the service instance for processing the billing message can be different from the service instance for processing the establishment of the billing session, and the CAF can select any one according to the load sharing algorithm. Furthermore, if the target CHF network element is abnormal, since the data related to the billing session in the processing process are all synchronized in the cluster shared memory and the main LB module can select any CHF network element according to the load sharing algorithm, the CHF network element for processing the billing message can be different from the CHF network element for processing the establishment of the billing session).

[0087] Step 11: After receiving the charging message, BD reserves the response quota unit based on the internal centralized unit reservation batch price, and interacts with the ABMF (Account Balance Management Function) in the converged billing system to check whether the user account balance corresponding to the user terminal meets the quota unit reservation. If the user account has sufficient balance, BD performs the corresponding reservation unit action and sends the authorized reservation unit quota to the CHF cluster (the information form of the processing result can be expressed as: Charging Data Response) to support the continued use of the service.

[0088] Step 12: The CHF cluster forwards the authorized reserved unit quota to the SMF (CTF) through the VIP / LB module, so that the SMF (CTF) can continue content and service transmission based on the authorized reserved unit quota to support the continued use of the user terminal.

[0089] During the continuous process of 5G data services, there may be multiple billing data requests triggered by quota management triggers or usage report triggers, and their processing processes can be as shown in steps 10 to 12 above.

[0090] When the SMF (CTF) in the 5G core network has terminated the PDU session with the user terminal, the processing process can be as shown in steps 13 to 17:

[0091] Step 13: SMF (CTF) reports a Charging Data Request (Termination) to the CHF cluster, requesting to release the charging session.

[0092] Step 14: When the CHF cluster obtains the request to terminate the billing session, the main LB module reads the mapping relationship between the billing session and the CHF network element from the cluster shared memory, and forwards the request to terminate the billing session to the target CHF network element corresponding to the billing session. After the target CHF network element obtains the request to terminate the billing session, it forwards the request to terminate the billing session to the BD through the VIP / LB module, and the BD performs quota management, unit reservation, etc. At the same time, the target CHF network element converts the billing data in the request to terminate the billing session into call record data, updates and closes the offline call record, and synchronously stores the billing session related data in the network element shared memory and the cluster shared memory during the processing. (Similarly, the service instance that processes the billing message can be different from the service instance when processing the request to terminate the billing session, and the CHF network element that processes the billing message can also be different from the CHF network element when processing the request to terminate the billing session).

[0093] Step 15: When BD receives the request to terminate the charging session, it processes the service termination usage through the batch pricing and user account accounting entities, deducts the usage and amount from the user account balance, and sends the processing result to the CHF cluster (the information form of the processing result can be expressed as: Charging Data Response).

[0094] Step 16: After receiving the processing result, the CHF cluster sends the processing result to the SMF (CTF) through the VIP / LB module.

[0095] Step 17: After receiving the processing result, SMF (CTF) ends the billing session process.

[0096] So far, an embodiment is provided to illustrate the process of continuing to complete 5G billing by other CHF network elements in the CHF cluster after a CHF network element fails.

[0097] SMF (CTF) reports the billing message to the CHF cluster, and the VIP / LB module reads the mapping relationship between the billing session and the CHF network element from the cluster shared memory, determines that the target CHF network element mapped by the billing session is CHF1, and forwards the billing message to CHF1 for processing. At this time, CHF1 fails and can no longer provide services.

[0098] The active LB module detects the keep-alive abnormality of CHF1 through the keep-alive mechanism with the CHF network element, and removes CHF1 from the available CHF.

[0099] If the SMF (CTF) times out waiting for the processing result, it resends the charging message to the CHF cluster according to the 3GPP specification.

[0100] The VIP / LB module reads the mapping relationship between the billing session and the CHF network element from the cluster shared memory, determines that the target CHF network element mapped by the billing session is CHF1 but CHF1 is not among the available CHF network elements, then selects CHF2 from the available CHF network elements for processing, and updates the mapping relationship between CHF1 and the billing session in the cluster shared memory to the mapping relationship between CHF2 and the billing session, and forwards the billing message to CHF2 for processing.

[0101] After CHF2 completes the processing, it sends the processing result to SMF (CTF) through the VIP / LB module.

[0102] SMF (CTF) receives the processing result and ends the interaction of this billing message.

[0103] Among them, the subsequent billing messages of the billing session are all processed by CHF2 until the billing session is closed. If CHF2 fails during the process, the VIP / LB module directly selects an available CHF network element to continue processing until the billing session is closed. This embodiment shows that in the case of an abnormality in the CHF network element, the timely switching of the CHF network element by the VIP / LB module can ensure that the 5G billing message is not lost and the subsequent 5G billing messages are processed in an orderly manner. After the first billing message, if the CHF network element is abnormal or fails, the VIP / LB module will delete the abnormal or failed CHF network element from the available CHF network elements and switch it to the available CHF network element, and the subsequent 5G billing messages can still be processed normally.

[0104] So far, an embodiment is provided to illustrate the process of continuing to complete 5G billing by the backup LB module after the main LB module fails.

[0105] SMF (CTF) reports the billing message to the CHF cluster, and the VIP / LB1 module reads the mapping relationship from the cluster shared memory, determines the target CHF network element, and forwards the billing message to the target CHF network element for processing. At this time, the LB1 module fails and cannot continue to provide services.

[0106] The HA module detects the abnormality of the LB1 module through the heartbeat mechanism between the HA module and the LB1 module, and assists the VIP module to switch the LB2 module to the primary module and the LB1 module to the backup module. Subsequent billing messages are completed by LB2 instead of LB1.

[0107] The target CHF network element sends the processing result to the SMF (CTF) through the VIP / LB2 module.

[0108] After the LB module is switched, the switched VIP / LB module continues to send and receive billing messages.

[0109] The above describes a charging message processing method provided by an embodiment of the present application. The following describes a CHF cluster that executes the above charging message processing method. The CHF cluster includes a load sharing management LB module and multiple CHF network elements. Each CHF network element includes a charging access component CAF, multiple service instances, and a network element shared memory.

[0110] The LB module may be configured to: send the acquired charging message belonging to the charging session to the target CHF network element according to the mapping relationship, the mapping relationship being: the corresponding relationship between the charging session and the CHF network element;

[0111] The target CHF network element may be configured to: store the billing data in the billing message into the network element shared memory through the CAF, determine and notify the service instance group that processes the billing data, so that the service instance group obtains the billing data from the network element shared memory for processing, and stores the processing result into the network element shared memory, the service instance group including at least one service instance;

[0112] CAF can be configured as follows: if it is determined that at least one service instance in the service instance group has an abnormality, then at least one target service instance that processes the billing data for which the abnormal service instance is responsible is determined from other service instances and notified, so that the target service instance obtains the billing data for which the abnormal service instance is responsible from the network element shared memory for processing, and stores the processing result in the network element shared memory. The other service instances are service instances of the same type as the abnormal service instance except for the abnormal service instance.

[0113] In one possible implementation, the CHF cluster also includes a cluster shared memory.

[0114] The target CHF network element stores the billing data in the billing message into the network element shared memory through CAF, determines and notifies the service instance group that processes the billing data, so that the service instance group obtains the billing data from the network element shared memory for processing, and stores the processing results in the network element shared memory. The specific configuration is:

[0115] The target CHF network element stores the billing data in the billing message into the cluster shared memory and the network element shared memory synchronously through CAF, determines and notifies the service instance group that processes the billing data, so that the service instance group obtains the billing data from the network element shared memory for processing, and stores the processing results into the cluster shared memory and the network element shared memory synchronously;

[0116] The LB module is also configured to: when it is determined that the target CHF network element is abnormal, determine a CHF network element from other CHF network elements, update the target CHF network element, so that the updated target CHF network element obtains the data that the abnormal target CHF network element is responsible for processing from the cluster shared memory, and the other CHF network elements are CHF network elements other than the abnormal target CHF network element.

[0117] In a possible implementation, the LB module may also be configured as:

[0118] The LB module responds to the request to establish a charging session and selects a target CHF network element according to a load sharing algorithm;

[0119] A mapping relationship between the charging session and the target CHF network element is established, and the mapping relationship is stored in the cluster shared memory.

[0120] In a possible implementation, the LB module may also be configured as:

[0121] When the target CHF network element is abnormal, a CHF network element is selected from other CHF network elements according to the load sharing algorithm, and the target CHF network element is updated, and the other CHF network elements are CHF network elements except the abnormal target CHF network element;

[0122] The mapping relationship is updated so that the LB module sends subsequent charging messages belonging to the abnormal target CHF network element to the updated target CHF network element for processing.

[0123] In a possible implementation, the LB module includes an active LB module and a standby LB module, and the CHF cluster can be configured as follows:

[0124] When the active LB module fails, the standby LB module is started.

[0125] In one possible implementation, CAF determines a service instance group that processes billing data, which can be specifically configured as follows:

[0126] The CAF selects at least one service instance from multiple service instances in the target CHF network element according to a load sharing algorithm, and obtains a service instance group for processing billing data.

[0127] The present application also provides an electronic device in an embodiment. Figure 5 As shown, it shows a schematic diagram of the structure of an electronic device suitable for implementing the embodiment of the present application. The electronic device in the embodiment of the present application may include but is not limited to fixed terminals such as mobile phones, laptops, PDAs (personal digital assistants), PADs (tablet computers), desktop computers, etc. Figure 5 The electronic device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0128] like Figure 5 As shown, the electronic device may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 to a random access memory (RAM) 503. When the electronic device is powered on, various programs and data required for the operation of the electronic device are also stored in the RAM 503. The processing device 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0129] Typically, the following devices may be connected to the I / O interface 505: an input device 506 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 508 including, for example, a memory card, a hard disk, etc.; and a communication device 509. The communication device 509 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. Although Figure 5 An electronic device having various devices is shown, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0130] An embodiment of the present application also provides a computer program product including computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements any one of the billing message processing methods provided in the embodiments of the present application.

[0131] A computer-readable storage medium is also provided in an embodiment of the present application. The storage medium carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement any billing message processing method provided in an embodiment of the present application.

[0132] It should also be noted that the cluster embodiment described above is only schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, in the cluster embodiment drawings provided by the present application, the connection relationship between the modules indicates that there is a communication connection between them, which can be specifically implemented as one or more communication buses or signal lines.

[0133] Through the description of the above implementation mode, the technicians in the field can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course, it can also be implemented by special hardware including special integrated circuits, special CPUs, special memories, special components, etc. In general, all functions completed by computer programs can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be various, such as analog circuits, digital circuits or special circuits. However, for the present application, software program implementation is a better implementation mode in more cases. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer floppy disk, a U disk, a mobile hard disk, a ROM, a RAM, a disk or an optical disk, etc., including a number of instructions to enable a computer device (which can be a personal computer, a training device, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0134] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0135] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. 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 a website site, a computer, a training device, or a 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, training device, or data center. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a training device, a data center, etc. that includes one or more available media integrations. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)), etc.

[0136] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0137] It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0138] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A charging message processing method, characterized in that: Applied to a charging function CHF cluster, the CHF cluster includes a load sharing management LB module and multiple CHF network elements, each of the CHF network elements includes a charging access component CAF, multiple service instances and a network element shared memory, and the charging message processing method includes: The LB module sends the acquired charging message belonging to the charging session to the target CHF network element according to the mapping relationship, wherein the mapping relationship is: the corresponding relationship between the charging session and the CHF network element; The target CHF network element stores the billing data in the billing message into the network element shared memory through the CAF, determines and notifies a service instance group that processes the billing data, so that the service instance group obtains the billing data from the network element shared memory for processing, and stores the processing result in the network element shared memory, wherein the service instance group includes at least one service instance; If the CAF determines that at least one service instance in the service instance group has an abnormality, it determines and notifies at least one target service instance from other service instances to process the billing data for which the service instance with the abnormality is responsible, so that the target service instance obtains the billing data for which the service instance with the abnormality is responsible from the network element shared memory for processing, and stores the processing result in the network element shared memory. The other service instances are service instances of the same type as the service instance with the abnormality, except for the service instance with the abnormality.

2. The charging message processing method according to claim 1, characterized in that: The CHF cluster also includes a cluster shared memory, The target CHF network element stores the billing data in the billing message into the network element shared memory through the CAF, determines and notifies a service instance group that processes the billing data, so that the service instance group obtains the billing data from the network element shared memory for processing, and stores the processing result in the network element shared memory, including: The target CHF network element stores the charging data in the charging message synchronously in the cluster shared memory and the network element shared memory through the CAF, determines and notifies the service instance group that processes the charging data, so that the service instance group obtains the charging data from the network element shared memory for processing, and synchronously stores the processing result in the cluster shared memory and the network element shared memory; When the LB module determines that the target CHF network element is abnormal, a CHF network element is determined from other CHF network elements, and the target CHF network element is updated so that the updated target CHF network element obtains the data that the abnormal target CHF network element is responsible for processing from the cluster shared memory, and the other CHF network elements are CHF network elements other than the abnormal target CHF network element.

3. The charging message processing method according to claim 2, characterized in that: Also includes: The LB module selects the target CHF network element according to a load sharing algorithm in response to a request to establish a charging session; A mapping relationship between the charging session and the target CHF network element is established, and the mapping relationship is stored in the cluster shared memory.

4. The method for processing charging messages according to claim 1, characterized in that: Also includes: When the target CHF network element is abnormal, the LB module selects a CHF network element from other CHF network elements according to a load sharing algorithm, and updates the target CHF network element, wherein the other CHF network elements are CHF network elements other than the abnormal target CHF network element; The mapping relationship is updated so that the LB module sends subsequent charging messages belonging to the abnormal target CHF network element to the updated target CHF network element for processing.

5. The charging message processing method according to claim 1, characterized in that: The LB module includes a main LB module and a standby LB module, and the charging message processing method further includes: When the active LB module fails, the standby LB module is started.

6. The method for processing charging messages according to claim 1, characterized in that: The CAF determines a service instance group for processing the billing data, including: The CAF selects at least one service instance from a plurality of service instances in the target CHF network element according to a load sharing algorithm, and obtains a service instance group for processing the billing data.

7. A CHF cluster, characterized in that: The CHF cluster includes a load sharing management LB module and multiple CHF network elements, each of which includes a charging access component CAF, multiple service instances and a network element shared memory. The LB module is configured to: send the acquired charging message belonging to the charging session to the target CHF network element according to a mapping relationship, wherein the mapping relationship is: a corresponding relationship between the charging session and the CHF network element; The target CHF network element is configured to: store the billing data in the billing message into the network element shared memory through the CAF, determine and notify the service instance group that processes the billing data, so that the service instance group obtains the billing data from the network element shared memory for processing, and stores the processing result in the network element shared memory, the service instance group includes at least one service instance; The CAF is configured as follows: if it is determined that at least one service instance in the service instance group has an abnormality, at least one target service instance that processes the billing data for which the service instance with the abnormality is responsible is determined from other service instances and notified, so that the target service instance obtains the billing data for which the service instance with the abnormality is responsible from the network element shared memory for processing, and stores the processing result in the network element shared memory. The other service instances are service instances of the same type as the service instance with the abnormality, except for the service instance with the abnormality.

8. The CHF cluster according to claim 7, characterized in that: The CHF cluster also includes a cluster shared memory, The target CHF network element stores the billing data in the billing message into the network element shared memory through the CAF, determines and notifies the service instance group that processes the billing data, so that the service instance group obtains the billing data from the network element shared memory for processing, and stores the processing result in the network element shared memory, and the specific configuration is: The target CHF network element stores the charging data in the charging message synchronously in the cluster shared memory and the network element shared memory through the CAF, determines and notifies the service instance group that processes the charging data, so that the service instance group obtains the charging data from the network element shared memory for processing, and synchronously stores the processing result in the cluster shared memory and the network element shared memory; The LB module is further configured to: when it is determined that the target CHF network element is abnormal, determine a CHF network element from other CHF network elements, and update the target CHF network element so that the updated target CHF network element obtains the data that the abnormal target CHF network element is responsible for processing from the cluster shared memory, and the other CHF network elements are CHF network elements other than the abnormal target CHF network element.

9. An electronic device, characterized in that: The method comprises at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs; The processor is used to execute the computer program so that the electronic device can implement the charging message processing method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that It comprises computer-readable instructions, and when the computer-readable instructions are executed on an electronic device, the electronic device implements the charging message processing method as claimed in any one of claims 1 to 6.

Images