CN109936672B

CN109936672B - Online charging method and device

Info

Publication number: CN109936672B
Application number: CN201711349282.6A
Authority: CN
Inventors: 包贤德; 刘秀娟
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-12-15
Filing date: 2017-12-15
Publication date: 2021-03-02
Anticipated expiration: 2037-12-15
Also published as: CN109936672A

Abstract

The embodiment of the application discloses an online charging method and device, which are used for improving the dynamic capacity expansion capability of a CBPAdapter of a fused charging route distribution node, avoiding the CBPAdapter from becoming a system resource bottleneck and improving the system reliability. The method in the embodiment of the application comprises the following steps: the first CBPAdapter receives an initial charging request message of a target service, wherein the initial charging request message at least comprises a session number and a user number of the target service; the first CBPAdapter determining the first CBPAPP from the cluster of CBPAPPs; and the first CBPAdapter sends the initial charging request message to the first CBPAPP, so that the first CBPAPP determines a target fusion charging session data node (CBPSDB) for storing the session data of the target service according to the session number, and determines a target fusion charging data node (CBPMDB) for storing the user data of the target service according to the user number.

Description

Online charging method and device

Technical Field

The present application relates to the field of communications, and in particular, to an online charging method and apparatus.

Background

The services of the internet and the internet of things are developed vigorously nowadays, and the service characteristics of high concurrency, always online and the like require that the charging system has super-large computing capacity and storage capacity, thereby causing great challenges to the system architecture and processing capacity of the charging system.

Currently, an Online Charging System (OCS) architecture shown in fig. 1 is adopted, a converged charging routing distribution node (CBPAdapter) is responsible for solving a message routing, a converged charging application node (CBPAPP) is responsible for service logic processing, and a converged charging data node (CBPMDB) is responsible for storing user data and session data. The user data refers to user information data, including user account, package, balance, opened service, etc., the session data is temporary data, stored is the state information of the service being used by the user, usually contains a session number for identifying the session data; the CBPAdapter is a dual-machine networking, the CBPAPP is a single-machine cluster networking, and the CBPMDB is a dual-machine cluster networking.

In the existing OCS scheme, due to the limitation of the storage capacity of a single node, the user data is usually stored in a plurality of CBPMDB nodes in a partitioned manner according to a certain mapping rule, and the mapping rule of the user number and the CBPMDB (for example, in the form of a number routing table) is stored as independent data in the CBPAdapter. According to the subscriber number mapping rule, the CBPMDB corresponding to the subscriber number is called "CBPMDB to which the subscriber belongs". When the current user uses the service by surfing the internet, the Session Data (Session Data) of the user needs to be stored in the CBPMDB to which the user belongs, and a memory bank is used in the cbpaddapter node to cache the routing Mapping relationship between the Session number and the CBPMDB, such as a Session routing Mapping relationship (Dialog Route Mapping) shown in fig. 2, so that when a fee deduction message triggered by the user by surfing the internet is reported to the cbpaddapter for processing, the cbpaddapter can use the routing Mapping relationship between the Session number recorded in the memory bank and the CBPMDB to inquire the Session Data of the user.

User routing data is concentrated on the CBPAdapter node and stored in a routing table form, with the increase of the number of users and the traffic volume and under high-capacity high-concurrency impact, the data volume of routing mapping (the mapping relation between a user number and CBPMDB and the mapping relation between a session number and BPMDB) is larger and larger, and because the CBPAdapter node is deployed in a dual-computer networking mode, resources are not easy to expand automatically, and the CBPAdapper node is easy to become the bottleneck of system resources.

Disclosure of Invention

The embodiment of the application provides an online charging method and device, which are used for improving the dynamic capacity expansion capability of a CBPAdapter of a fused charging route distribution node, avoiding the CBPAdapter from becoming a system resource bottleneck and improving the system reliability.

A first aspect of the present application provides an online charging method, where the online charging method is applied to an online charging system, where the online charging system includes a CBPAdapter cluster and a CBPAPP cluster, where the CBPAdapter cluster includes a first CBPAdapter and at least one second CBPAdapter, and the CBPAPP cluster includes a first CBPAPP and at least one second CBPAPP, and includes: the first CBPAdapter receives an initial charging request message of a target service, wherein the initial charging request message at least carries a session number and a user number of the target service; the first CBPAdapter determining the first CBPAPP from a plurality of CBPAPPs included in the CBPAPP cluster; and the first CBPAdapter sends the initial charging request message to the first CBPAPP, so that the first CBPAPP determines a target fusion charging session data node (CBPSDB) for storing the session data of the target service according to the session number, and the first CBPAPP determines a target fusion charging data node (CBPMDB) for storing the user data of the target service according to the user number. According to the embodiment of the application, the user data and the session data are separated from the CBPAdapter of the fused charging route distribution node, the dynamic capacity expansion capability of the CBPAdapter of the fused charging route distribution node is improved, the CBPAdapter is prevented from becoming a system resource bottleneck, and the system reliability is improved.

In a possible design, in a first implementation manner of the first aspect of the embodiment of the present application, after the first cbpapapter sends the initial charging request message to the first CBPAPP, the online charging method further includes: the first CBPAdapter receives an initial charging request response message sent by the first CBPAPP; and the first CBPAdapter sends the initial charging request response message to a core network connected with the first CBPAdapter.

In a possible design, in a second implementation manner of the first aspect of the embodiment of the present application, after the first CBPAdapter sends the initial charging request response message to a core network connected to the first CBPAdapter, the online charging method further includes: and the first CBPAdapter receives the update charging request message of the target service and updates data according to the update charging request message.

In a possible design, in a third implementation manner of the first aspect of the embodiment of the present application, the receiving, by the first CBPAdapter, an update charging request message of the target service, and performing data update according to the update charging request message includes: step 1: the first CBPAdapter receives an update charging request message of the target service, wherein the update charging request message at least comprises the session number; step 2: the first CBPAdapter determining the first CBPAPP from the cluster of CBPAPPs; and step 3: the first CBPAdapter sends the update charging request message to the first CBPAPP, so that the first CBPAPP updates the session data of the target service stored in the target CBPSDB according to the session number and updates the user data of the target service stored in the target CBPMDB according to the session data; and circularly executing the step 1 to the step 3 until the target service is finished, and deleting the session data on the target CBPSDB by the first CBPAPP.

In a possible design, in a fourth implementation manner of the first aspect of the embodiment of the present application, the receiving, by the first CBPAdapter, an update charging request message of the target service, and performing data update according to the update charging request message includes: step 1: the first CBPAdapter receives an update charging request message of the target service, wherein the update charging request message at least comprises the conversation number and the user number; step 2: the first CBPAdapter determining the first CBPAPP from the cluster of CBPAPPs; and step 3: the first CBPAdapter sends the update charging request message to the first CBPAPP, so that the first CBPAPP updates the session data of the target service stored in the target CBPSDB according to the session number and updates the user data of the target service stored in the target CBPMDB according to the user number; and circularly executing the step 1 to the step 3 until the target service is finished, and deleting the session data on the target CBPSDB by the first CBPAPP.

A second aspect of the present application provides an online charging method, which is applied to an online charging system, where the online charging system includes a CBPAdapter cluster including a first CBPAdapter and at least one second CBPAdapter, and a CBPAPP cluster including a first CBPAPP and at least one second CBPAPP, and includes: the first CBPAPP receives an initial charging request message of a target service sent by the first CBPAdapter, wherein the initial charging request message at least comprises a session number and a user number of the target service; the first CBPAPP determines a target fusion charging session data node CBPSDB for storing the session data of the target service according to the session number; the first CBPAPP determines a target fusion charging data node CBPMDB for storing the user data of the target service according to the user number; the first CBPAPP updates user data stored on the target CBPMDB; the first CBPAPP updates session data stored on the target CBPSDB. According to the embodiment of the application, the routing mapping relation is replaced by the session routing algorithm and the user data routing algorithm, the session data of the user is separated from the CBPMDB and stored in the independent CBPSDB, the mapping relation between the user data and the CBPMDB is recorded on the CBPSDB, and when the CBPAPp processes the updating charging message, the CBPAPp can find the user number according to the session number in the mapping relation, and then find the user data for updating. The dynamic capacity expansion capability of the CBPAPP of the fusion charging application node is improved, the CBPAPP is prevented from becoming a system resource bottleneck, and the system reliability is improved.

In a possible design, in a first implementation manner of the second aspect of the embodiment of the present application, after the first CBPAPP updates the session data stored on the target CBPSDB, the online charging method further includes: the first CBPAPP sends an initial charging request response message to the first CBPAdapter.

In a possible design, in a second implementation manner of the second aspect of the embodiment of the present application, after the first CBPAPP sends an initial charging request response message to the first CBPAdapter, the online charging method further includes: the first CBPAPP receives an update charging request message of a target service sent by the first CBPAdapter, wherein the update charging request message at least comprises a session number of the target service; and the first CBPAP updates data according to the update charging request message.

In a possible design, in a third implementation manner of the second aspect of the embodiment of the present application, the updating, by the first CBPAP, data according to the update charging request message includes: step 1: the first CBPAP receives an update charging request message of the target service sent by the first CBPAdapter, wherein the update charging request message comprises the session number; step 2: the first CBPAP updates session data of the target service stored on the target CBPSDB, wherein the target CBPSDB corresponds to the session number; and step 3: the first CBPAP determines the user number of the target service according to the session data; and 4, step 4: the first CBPAP updates user data of the target service stored on the target CBPMDB according to the user number, wherein the target CBPMDB corresponds to the user number; and circularly executing the step 1 to the step 4 until the target service is finished, and deleting the session data on the target CBPSDB by the first CBPAPP.

In a possible design, in a fourth implementation manner of the second aspect of the embodiment of the present application, the updating, by the first CBPAP, data according to the update charging request message includes: step 1: the first CBPAP receives an update charging request message of the target service sent by the first CBPAdapter, wherein the update charging request message comprises the session number and the user number; step 2: the first CBPAP updates session data of the target service stored on the target CBPSDB, wherein the target CBPSDB corresponds to the session number; and step 3: the first CBPAP updates user data of the target service stored on the target CBPMDB according to the user number, wherein the target CBPMDB corresponds to the user number; and circularly executing the step 1 to the step 3 until the target service is finished, and deleting the session data on the target CBPSDB by the first CBPAPP.

A third aspect of the present application provides an online charging apparatus, which is applied to an online charging system, where the online charging system includes a CBPAdapter cluster and a CBPAPP cluster, where the CBPAdapter cluster includes a first CBPAdapter and at least one second CBPAdapter, and the CBPAPP cluster includes a first CBPAPP and at least one second CBPAPP, and includes: a first receiving unit, configured to receive an initial charging request message of a target service, where the initial charging request message at least includes a session number and a user number of the target service; a determining unit configured to determine the first CBPAPP from the CBPAPP cluster; a first sending unit, configured to send the initial charging request message to the first CBPAPP, so that the first CBPAPP determines, according to the session number, a target fused charging session data node CBPSDB that stores session data of the target service, and determines, according to the user number, a target fused charging data node CBPMDB that stores user data of the target service. According to the embodiment of the application, the user data and the session data are separated from the CBPAdapter, the dynamic capacity expansion capability of the CBPAdapter is improved, the CBPAdapter is prevented from becoming a system resource bottleneck, and the system reliability is improved.

In a possible design, in a first implementation manner of the third aspect of the embodiment of the present application, the online charging apparatus further includes: a second receiving unit, configured to receive an initial charging request response message sent by the first CBPAPP; a second sending unit, configured to send the initial charging request response message to a core network connected to the first CBPAdapter.

In a possible design, in a second implementation manner of the third aspect of the embodiment of the present application, the online charging apparatus further includes: and the processing unit is used for receiving the charging updating request message of the target service and updating data according to the charging updating request message.

In a possible design, in a third implementation manner of the third aspect of the embodiment of the present application, the processing unit is specifically configured to: step 1: receiving an update charging request message of the target service, wherein the update charging request message at least comprises the session number; step 2: determining the first CBPAPP from the CBPAPP cluster; and step 3: sending the update charging request message to the first CBPAPP, so that the first CBPAPP updates the session data of the target service stored in the target CBPSDB according to the session number, and updates the user data of the target service stored in the target CBPMDB according to the session data; and circularly executing the step 1 to the step 3 until the target service is finished, and deleting the session data on the target CBPSDB by the first CBPAPP.

In a possible design, in a fourth implementation manner of the third aspect of the embodiment of the present application, the processing unit is further specifically configured to: step 1: receiving an update charging request message of the target service, wherein the update charging request message at least comprises the conversation number and the user number; step 2: determining the first CBPAPP from the CBPAPP cluster; and step 3: sending the update charging request message to the first CBPAPP, so that the first CBPAPP updates the session data of the target service stored in the target CBPSDB according to the session number and updates the user data of the target service stored in the target CBPMDB according to the user number; and circularly executing the step 1 to the step 3 until the target service is finished, and deleting the session data on the target CBPSDB by the first CBPAPP.

A fourth aspect of the present application provides an online charging apparatus, where the online charging apparatus is applied to an online charging system, where the online charging system includes a CBPAdapter cluster and a CBPAPP cluster, where the CBPAdapter cluster includes a first CBPAdapter and at least one second CBPAdapter, and the CBPAPP cluster includes a first CBPAPP and at least one second CBPAPP, and includes: a first receiving unit, configured to receive an initial charging request message of a target service sent by the first cbpadapetter, where the initial charging request message at least includes a session number and a user number of the target service; a first determining unit, configured to determine, according to the session number, a target convergence charging session data node CBPSDB that stores session data of the target service; a second determining unit, configured to determine, according to the user number, a target fusion charging data node CBPMDB that stores the user data of the target service; the first updating unit is used for updating the user data stored on the target CBPMDB; and the second updating unit is used for updating the session data stored on the target CBPSDB. According to the embodiment of the application, the routing mapping relation is replaced by the session routing algorithm and the user data routing algorithm, the session data of the user is separated from the CBPMDB and stored in the independent CBPSDB, the mapping relation between the user data and the CBPMDB is recorded on the CBPSDB, and when the CBPAPp processes the updating charging message, the CBPAPp can find the user number according to the session number in the mapping relation, and then find the user data for updating. The dynamic capacity expansion capability of the CBPAPP of the fusion charging application node is improved, the CBPAPP is prevented from becoming a system resource bottleneck, and the system reliability is improved.

In a possible design, in a first implementation manner of the fourth aspect of the embodiment of the present application, the online charging apparatus further includes: a first sending unit, configured to send an initial charging request response message to the first CBPAdapter.

In a possible design, in a second implementation manner of the fourth aspect of the embodiment of the present application, the online charging apparatus further includes: a second receiving unit, configured to receive an update charging request message of a target service sent by the first cbpadapetter, where the update charging request message at least includes a session number of the target service; and the third updating unit is used for updating data according to the charging updating request message.

In a possible design, in a third implementation manner of the fourth aspect of the embodiment of the present application, the third updating unit is specifically configured to: step 1: receiving an update charging request message of the target service sent by the first CBPAdapter, wherein the update charging request message comprises the session number; step 2: updating the session data of the target service stored on the target CBPSDB, wherein the target CBPSDB corresponds to the session number; and step 3: determining the user number of the target service according to the session data; and 4, step 4: updating the user data of the target service stored in the target CBPMDB according to the user number, wherein the target CBPMDB corresponds to the user number; and circularly executing the step 1 to the step 4 until the target service is finished, and deleting the session data on the target CBPSDB by the first CBPAPP.

In a possible design, in a fourth implementation manner of the fourth aspect of the embodiment of the present application, the processing unit is further specifically configured to: step 1: receiving an update charging request message of the target service sent by the first CBPAdapter, wherein the update charging request message comprises the session number and the user number; step 2: updating the session data of the target service stored on the target CBPSDB, wherein the target CBPSDB corresponds to the session number; and step 3: updating the user data of the target service stored in the target CBPMDB according to the user number, wherein the target CBPMDB corresponds to the user number; and circularly executing the step 1 to the step 3 until the target service is finished, and deleting the session data on the target CBPSDB by the first CBPAPP.

A fifth aspect of the present application provides a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to perform the method of the above-described aspects.

A sixth aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the above aspects.

According to the technical scheme, the embodiment of the application has the following advantages:

the first CBPAdapter receives an initial charging request message of a target service, wherein the initial charging request message at least comprises a session number and a user number of the target service; the first CBPAdapter determining the first CBPAPP from the cluster of CBPAPPs; and the first CBPAdapter sends the initial charging request message to the first CBPAPP, so that the first CBPAPP determines a target fusion charging session data node (CBPSDB) for storing the session data of the target service according to the session number, and determines a target fusion charging data node (CBPMDB) for storing the user data of the target service according to the user number. In the embodiment of the application, the first cbpapapter distributes the initial charging request to the first CBPAPP according to the load condition of the CBPAPP cluster, so that the first CBPAPP determines the target CBPSDB for storing the session data of the target service, and determines the target CBPMDB for storing the user data of the target service through a user routing algorithm, thereby improving the dynamic capacity expansion capability of the cbpapapter of the fused charging routing distribution node, avoiding the cbpapapter from becoming the bottleneck of system resources, and improving the system reliability.

Drawings

FIG. 1 is a schematic diagram of a network architecture of a basic online charging system;

FIG. 2 is a schematic diagram of a network architecture of an online charging system adopted in the prior art;

fig. 3 is a schematic diagram of a network architecture of an online charging system adopted in the embodiment of the present application;

fig. 4 is a schematic diagram of an embodiment of an online charging method in the embodiment of the present application;

fig. 5 is a schematic diagram of another embodiment of an online charging method in the embodiment of the present application;

FIG. 6 is a schematic diagram of an embodiment of an online charging apparatus in the embodiment of the present application;

fig. 7 is a schematic diagram of another embodiment of an online charging apparatus in the embodiment of the present application;

fig. 8 is a schematic diagram of another embodiment of an online charging apparatus in the embodiment of the present application;

fig. 9 is a schematic diagram of another embodiment of an online charging apparatus in the embodiment of the present application.

Detailed Description

The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises," "comprising," or "having," and any variations thereof, are intended to cover non-exclusive inclusions, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

The embodiment of the present application can be applied to a converged charging System (CBS) architecture as shown in fig. 3, where the CBS architecture includes: a CBPAdapter cluster, a CBPAPP cluster, a CBPAdapter cluster, a CBPMDB cluster, and a CBPSDB cluster, where the CBPAdapter cluster is responsible for solving message routing, the CBPAPP cluster is responsible for service logic processing, the pmcbdb cluster is used for storing user data of a target service, and the CBPSDB cluster is used for storing session data of the target service.

Compared with the prior art, in the CBS architecture shown in fig. 2, the CBPAdapter is changed from dual-machine deployment to single-machine cluster networking deployment, and only the capability of message distribution is reserved. Stripping the local memory bank query function of the original CBPMDB position to CBPAPp; stripping user session data from the CBPMDB and storing the user session data in the CBPSDB; the function of CBPAdapter for storing a session routing mapping table and a user routing rule is stripped, and the memory bank of the CBPAdapter is removed; the CBPApp uses a user routing algorithm and a session routing algorithm to acquire location information of the CBPMDB and the CBPSDB.

For understanding, a specific flow of the embodiment of the present application is described below, and the embodiment of the present application and the subsequent embodiments provide an online charging method, which is applied to an online charging system that includes a converged charging route distribution node cbpapapter cluster and a converged charging application node cbpappp cluster, where the cbpapapter cluster includes a first cbpapapter and at least one second cbpapapter, and the CBPAPP cluster includes the first CBPAPP and at least one second CBPAPP.

It should be noted that, the first CBPAdapter is a preferred CBPAdapter determined according to the load balancing requirement, the second CBPAdapter is an alternative CBPAdapter determined according to the load balancing requirement, and the current load of the first CBPAdapter is smaller than that of the second CBPAdapter; the first CBPAPP is a preferred CBPAPP determined according to the load balancing requirement, and the second CBPAPepter is an alternative CBPAPP determined according to the load balancing requirement, wherein the current load of the first CBPAPP is smaller than that of the second CBPAPP.

Referring to fig. 4, in a scenario where an update charging message of a target service simultaneously carries a session number and a user number, an embodiment of an online charging method in the embodiment of the present application includes:

401. the first CBPAdapter receives an initial charging request message for a target service.

The first CBPAdapter receives an initial charging request message of a target service, wherein the initial charging request message at least comprises a session number and a user number of the target service.

It should be noted that the first CBPAdapter is the CBPAdapter with the smallest current load determined by the CBPAdapter cluster according to the current load condition of each CBPAdapter in the cluster, and the CBPAdapter cluster may expand or contract the CBPAdapter in the cluster according to the actual load condition to meet the service requirement.

It is to be understood that the target service may be a data service, for example, internet access, and the like, and the initial charging request message may further include information such as a message type, and the message type may include: an initial charging request message, an update charging request message, and a terminate charging request message.

402. The first cbpapper determines a first CBPAPP from the CBPAPP cluster.

The first cbpapper determines a first CBPAPP from the CBPAPP cluster.

It should be noted that the first CBPAPP is the CBPAPP with the smallest current load determined by the CBPAPP cluster according to the current load condition of each CBPAPP in the cluster, and the CBPAPP cluster may perform capacity expansion or capacity reduction on the CBPAPPs in the cluster according to the actual load condition to meet the service requirement.

403. The first cbpapapter sends the initial charging request message to the first CBPAPP.

And the first CBPAdapter sends an initial charging request message of the target service to the first CBPAPP, wherein the initial charging request message at least comprises the session number and the user number of the target service.

It should be noted that each target service has a session number and is associated with a subscriber number of a subscriber using the service, and the subscriber number is unique.

404. And the first CBPAPP determines a target fusion charging session data node CBPSDB for storing the session data of the target service according to the session number.

And the first CBPAPP determines a target fusion charging session data node CBPSDB for storing the session data of the target service according to the session number.

It should be noted that the session data is temporary data, and the session data stores state information of the target service being used by the user, for example, when the user is surfing the internet, the user has a piece of internet session data, and when the target service is used, the session data is deleted synchronously. The session data includes a session number identifying the session data.

405. And the first CBPAPP determines a target fusion charging data node CBPMDB for storing the user data of the target service according to the user number.

And the first CBPAPP determines a target fusion charging data node CBPMDB for storing the user data of the target service according to the user number.

It should be noted that the user data refers to user information data, which includes an account, a package, a balance, an open service, and the like of the user.

406. The first CBPAPP updates the user data stored on the target CBPMDB.

The first CBPAPP updates the user data stored on the target CBPMDB.

Specifically, the first CBPAPP searches the target CBPMDB according to the subscriber number included in the initial charging request message, and updates the subscriber data stored in the target CBPMDB. For example, the account balance, package remaining flow and other data in the user data may be modified and updated.

It should be noted that, the first CBPAPP calculates the target CBPMDB storing the user data through a user routing algorithm, where the user routing algorithm may be a consistent hash algorithm, or may be another algorithm, and is not limited herein.

407. The first CBPAPP updates session data stored on the target CBPSDB.

The first CBPAPP updates session data stored on the target CBPSDB.

Specifically, the first CBPAPP searches the target CBPSDB according to the session number included in the initial charging request message, and updates the session data stored in the target CBPSDB.

It should be noted that, the first CBPAPP calculates the target CBPSDB storing the session data through a session routing algorithm, where the session routing algorithm may be a consistent hash algorithm, or may be another algorithm, and is not limited herein.

It is understood that step 407 and step 406 do not have a specific sequence, and step 407 may precede step 406, or may follow step 406, or may be executed simultaneously with step 406, which is not limited herein.

408. The first CBPAPP sends an initial charging request response message to the first cbpapapter.

The first CBPAPP sends an initial charging request response message to the first cbpapapter.

It should be noted that, after the first CBPAPP completes the update of the session data, the first CBPAPP sends an initial charging request response message to the first CBPAdapter, so that the first cbpapapter updates the relevant data through the same session number and user number after receiving the update charging request message.

409. The first CBPAdapter sends an initial charging request response message to a core network connected to the first CBPAdapter.

The first CBPAdapter sends an initial charging request response message to a core network connected to the first CBPAdapter.

It should be noted that the core network is connected to the CBPAdapter cluster, the CBPAdapter cluster manages each Slave converged charging routing distribution node (Slave CBPAdapter) through a Master converged charging routing distribution node (Master CBPAdapter), and the first CBPAdapter is a Slave CBPAdapter allocated to the core network by the Master CBPAdapter in the CBPAdapter cluster.

410. The first CBPAdapter receives an update charging request message of the target service.

And when the duration corresponding to the initial charging request message is finished, the first CBPAdapter receives an updating charging request message of the target service, wherein the updating charging request message at least comprises a conversation number and a user number.

It can be understood that the first CBPAdapter is a Slave CBPAdapter allocated by the Master CBPAdapter in the CBPAdapter cluster for the core network. The first CBPAdapter is a Slave CBPAdapter with an idle or small load, and the first CBPAdapter receiving the update charging request message and the first CBPAdapter receiving the initial charging request message may be the same hardware device or different hardware devices.

411. The first cbpapper determines a first CBPAPP from the CBPAPP cluster.

The first cbpapper determines a first CBPAPP from the CBPAPP cluster.

It can be understood that the first CBPAPP is a CBPAPP with a small load in the CBPAPP cluster, and the first CBPAPP receiving the update charging request message and the first CBPAPP receiving the initial charging request message may be the same hardware device or different hardware devices.

412. The first cbpapapter sends an update charging request message to the first CBPAPP.

And the first CBPAdapter sends an update charging request message of the target service to the first CBPAPP, wherein the update charging request message at least comprises the session number and the user number of the target service.

413. The first CBPAP updates session data of the target service stored on the target CBPSDB.

The first CBPAP updates session data of the target service stored on the target CBPSDB, and the target CBPSDB corresponds to the session number. Specifically, the session number carried in the update charging request message is the same as the session number carried in the initial charging request message, and is the same session number.

414. The first CBPAP updates the user data of the target service stored on the target CBPMDB according to the user number.

And the first CBPAP updates the user data of the target service stored on the target CBPMDB according to the user number, wherein the target CBPMDB corresponds to the user number.

It should be noted that the user number carried in the updated charging request message is the same as the user number carried in the initial charging request message, and is the same user number.

415. The first CBPAPP sends an update charging request response message to the first cbpapapter.

The first CBPAPP sends an update charging request response message to the first cbpapapter.

It should be noted that, after the first CBPAPP completes the update of the user data, the first CBPAPP sends an update charging request response message to the first CBPAdapter.

416. The first CBPAdapter sends an update charging request response message to a core network connected to the first CBPAdapter.

The first CBPAdapter sends an update charging request response message to a core network connected to the first CBPAdapter.

It should be noted that steps 410 to 416 are executed in a loop until the target service is ended and the first CBPAPP deletes the session data on the target CBPSDB.

In the embodiment of the application, because the CBPAdapter does not store a session routing mapping table and a user routing rule any more, and the CBPAdapter depends on a memory library, when the capacity of the CBPAdapter cannot meet the service requirement, the CBPAdapter cluster and the CBPSDB cluster can realize automatic balanced capacity expansion, so that the real horizontal expansion of the cluster is realized, and the CBPAdapter is prevented from becoming the bottleneck of system resources; when the capacity of the CBPAdapter is more free, the CBPAdapter cluster and the CBPSDB cluster are subjected to capacity reduction, and the maintenance cost of equipment is saved.

Referring to fig. 5, in a scenario where an update charging message of a target service only carries a session number, an embodiment of an online charging method in the embodiment of the present application includes:

501. the first CBPAdapter receives an initial charging request message for a target service.

502. The first cbpapper determines a first CBPAPP from the CBPAPP cluster.

The first cbpapper determines a first CBPAPP from the CBPAPP cluster.

503. The first cbpapapter sends the initial charging request message to the first CBPAPP.

504. And the first CBPAPP determines a target fusion charging session data node CBPSDB for storing the session data of the target service according to the session number.

505. And the first CBPAPP determines a target fusion charging data node CBPMDB for storing the user data of the target service according to the user number.

506. The first CBPAPP updates the user data stored on the target CBPMDB.

The first CBPAPP updates the user data stored on the target CBPMDB.

Specifically, the first CBPAPP searches the target CBPMDB according to the subscriber number included in the initial charging request message, and updates the subscriber data stored in the target CBPMDB. For example, account balances, package remaining flows, etc. in the user data may be updated with modifications.

507. The first CBPAPP updates session data stored on the target CBPSDB.

The first CBPAPP updates session data stored on the target CBPSDB.

It is understood that step 507 has no specific sequence with step 506, and step 507 may be performed before step 506, or after step 506, or simultaneously with step 506, which is not limited herein.

508. The first CBPAPP sends an initial charging request response message to the first cbpapapter.

509. The first CBPAdapter sends an initial charging request response message to a core network connected to the first CBPAdapter.

Steps 501 to 509 are similar to steps 401 to 409, and are not described herein again.

510. The first CBPAdapter receives an update charging request message of the target service.

And when the time length corresponding to the initial charging request message is finished, the first CBPAdapter receives an updating charging request message of the target service, wherein the updating charging request message at least comprises a session number. Specifically, the session number carried in the update charging request message is the same as the session number carried in the initial charging request message, and is the same session number.

511. The first cbpapper determines a first CBPAPP from the CBPAPP cluster.

The first cbpapper determines a first CBPAPP from the CBPAPP cluster.

512. The first cbpapapter sends an update charging request message to the first CBPAPP.

And the first CBPAdapter sends an update charging request message of the target service to the first CBPAPP, wherein the update charging request message at least comprises the session number of the target service.

513. The first CBPAP updates session data of the target service stored on the target CBPSDB.

And the first CBPAP updates the session data of the target service stored in the target CBPSDB, the target CBPSDB corresponds to the session number, and acquires the session data, wherein the session data carries the user number.

514. The first CBPAP determines a subscriber number of the target service from the session data.

The first CBPAP determines a subscriber number of the target service from the session data.

515. The first CBPAP updates the user data of the target service stored on the target CBPMDB according to the user number.

It should be noted that the update charging request message does not carry the subscriber number, and the subscriber number is included in the session data.

516. The first CBPAPP sends an update charging request response message to the first cbpapapter.

517. The first CBPAdapter sends an update charging request response message to a core network connected to the first CBPAdapter.

It should be noted that, the steps 510 to 517 are executed in a loop until the target service is ended and the first CBPAPP deletes the session data on the target CBPSDB.

The online charging method in the embodiment of the present application is described above, and referring to fig. 6, the online charging device in the embodiment of the present application is described below, where an embodiment of the online charging device in the embodiment of the present application includes:

a first receiving unit 601, configured to receive an initial charging request message of a target service, where the initial charging request message at least includes a session number and a user number of the target service;

a determining unit 602, configured to determine the first CBPAPP from the CBPAPP cluster;

a first sending unit 603, configured to send the initial charging request message to the first CBPAPP, so that the first CBPAPP determines, according to the session number, a target fused charging session data node CBPSDB for storing the session data of the target service, and determines, according to the user number, a target fused charging data node CBPMDB for storing the user data of the target service.

In a possible implementation, the online charging apparatus may further include:

a second receiving unit 604, configured to receive an initial charging request response message sent by the first CBPAPP;

a second sending unit 605, configured to send the initial charging request response message to a core network connected to the first CBPAdapter.

a processing unit 606, configured to receive the charging update request message of the target service, and update data according to the charging update request message.

In a possible implementation, the processing unit 606 is specifically configured to:

step 1: receiving an update charging request message of the target service, wherein the update charging request message at least comprises the session number;

step 2: determining the first CBPAPP from the CBPAPP cluster;

and step 3: sending the update charging request message to the first CBPAPP, so that the first CBPAPP updates the session data of the target service stored in the target CBPSDB according to the session number, and updates the user data of the target service stored in the target CBPMDB according to the session data;

and circularly executing the step 1 to the step 3 until the target service is finished, and deleting the session data on the target CBPSDB by the first CBPAPP.

step 1: receiving an update charging request message of the target service, wherein the update charging request message at least comprises the conversation number and the user number;

step 2: determining the first CBPAPP from the CBPAPP cluster;

and step 3: sending the update charging request message to the first CBPAPP, so that the first CBPAPP updates the session data of the target service stored in the target CBPSDB according to the session number and updates the user data of the target service stored in the target CBPMDB according to the user number;

According to the embodiment of the application, the user data and the session data are separated from the CBPAdapter of the fused charging route distribution node, the dynamic capacity expansion capability of the CBPAdapter of the fused charging route distribution node is improved, the CBPAdapter is prevented from becoming a system resource bottleneck, and the system reliability is improved.

Referring to fig. 7, another embodiment of the online charging apparatus in the embodiment of the present application includes:

a first receiving unit 701, configured to receive an initial charging request message of a target service sent by the first CBPAdapter, where the initial charging request message at least includes a session number and a user number of the target service;

a first determining unit 702, configured to determine, according to the session number, a target convergence charging session data node CBPSDB that stores session data of the target service;

a second determining unit 703, configured to determine, according to the user number, a target fusion charging data node CBPMDB that stores the user data of the target service;

a first updating unit 704, configured to update the user data stored on the target CBPMDB;

a second updating unit 705, configured to update the session data stored on the target CBPSDB.

a first sending unit 706, configured to send an initial charging request response message to the first CBPAdapter.

a second receiving unit 707, configured to receive an update charging request message of a target service sent by the first cbpadapetter, where the update charging request message at least includes a session number of the target service;

a third updating unit 708, configured to perform data updating according to the update charging request message.

In a possible implementation, the third updating unit 708 is specifically configured to:

step 1: receiving an update charging request message of the target service sent by the first CBPAdapter, wherein the update charging request message comprises the session number;

step 2: updating the session data of the target service stored on the target CBPSDB, wherein the target CBPSDB corresponds to the session number;

and step 3: determining the user number of the target service according to the session data;

and 4, step 4: updating the user data of the target service stored in the target CBPMDB according to the user number, wherein the target CBPMDB corresponds to the user number;

and circularly executing the step 1 to the step 4 until the target service is finished, and deleting the session data on the target CBPSDB by the first CBPAPP.

step 1: receiving an update charging request message of the target service sent by the first CBPAdapter, wherein the update charging request message comprises the session number and the user number;

and step 3: updating the user data of the target service stored in the target CBPMDB according to the user number, wherein the target CBPMDB corresponds to the user number;

According to the embodiment of the application, the routing mapping relation is replaced by the session routing algorithm and the user data routing algorithm, the session data of the user is separated from the CBPMDB and stored in the independent CBPSDB, the mapping relation between the user data and the CBPMDB is recorded on the CBPSDB, and when the CBPAPp processes the updating charging message, the CBPAPp can find the user number according to the session number in the mapping relation, and then find the user data for updating. The dynamic capacity expansion capability of the CBPAPP of the fusion charging application node is improved, the CBPAPP is prevented from becoming a system resource bottleneck, and the system reliability is improved.

Fig. 6 to 7 respectively describe the online charging apparatus in the embodiment of the present application in detail from the perspective of the modular functional entity, and the online charging apparatus in the embodiment of the present application is described in detail from the perspective of hardware processing.

Fig. 8 is a schematic structural diagram of an online charging apparatus provided in an embodiment of the present application, where the online charging apparatus 800 may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 801 (e.g., one or more processors) and a memory 809, and one or more storage media 808 (e.g., one or more mass storage devices) storing applications 809 or data 809. Memory 809 and storage media 808 can be, among other things, transient or persistent storage. The program stored on the storage medium 808 may include one or more modules (not shown), each of which may include a series of instructions operating on an online charging apparatus. Still further, the processor 801 may be configured to communicate with a storage medium 808, and execute a series of instruction operations in the storage medium 808 on the online charging apparatus 800.

The online charging apparatus 800 may also include one or more power supplies 802, one or more wired or wireless network interfaces 803, one or more input-output interfaces 804, and/or one or more operating systems 805, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc. Those skilled in the art will appreciate that the online charging apparatus configuration shown in fig. 8 does not constitute a limitation of the online charging apparatus, and may include more or less components than those shown, or combine some components, or a different arrangement of components.

The following describes each component of the online charging apparatus in detail with reference to fig. 8:

the processor 801 is a control center of the online charging apparatus and may perform processing according to the set online charging method. The processor 801 connects various parts of the entire online charging apparatus using various interfaces and lines, performs various functions of the online charging apparatus and processes data by operating or executing software programs and/or modules stored in the memory 809 and calling data stored in the memory 809, thereby implementing online charging.

The memory 809 may be used to store software programs and modules, and the processor 801 executes various functional applications and data processing of the online charging apparatus 800 by running the software programs and modules stored in the memory 809. The memory 809 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function (such as determining the first CBPApp, etc.), and the like; the storage data area may store data created according to the use of the online charging apparatus (such as a load status of the CBPAdapter cluster, etc.), and the like. Further, the memory 809 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. The program of the online charging method provided in the embodiment of the present application and the received initial/updated charging request message are stored in the memory, and when needed to be used, the processor 801 calls from the memory 809.

Fig. 9 is a schematic structural diagram of an online charging apparatus provided in an embodiment of the present application, where the online charging apparatus 900 may have a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 901 (e.g., one or more processors) and a memory 909, and one or more storage media 908 (e.g., one or more mass storage devices) for storing applications 907 or data 906. Memory 909 and storage media 908 can be, among other things, transient storage or persistent storage. The program stored on the storage medium 908 may include one or more modules (not shown), each of which may include a series of instructions operating on an online charging apparatus. Further, the processor 901 may be configured to communicate with the storage medium 908, and execute a series of instruction operations in the storage medium 908 on the online charging apparatus 900.

The online charging apparatus 900 may also include one or more power supplies 902, one or more wired or wireless network interfaces 903, one or more input-output interfaces 904, and/or one or more operating systems 905, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc. Those skilled in the art will appreciate that the configuration of the online charging apparatus shown in fig. 9 does not constitute a limitation of the online charging apparatus, and may include more or less components than those shown, or combine some components, or a different arrangement of components.

The following describes each component of the online charging apparatus in detail with reference to fig. 9:

the processor 901 is a control center of the online charging apparatus, and may perform processing according to the set online charging method. The processor 901 connects various parts of the entire online charging apparatus using various interfaces and lines, performs various functions of the online charging apparatus and processes data by running or executing software programs and/or modules stored in the memory 909 and calling data stored in the memory 909, thereby implementing online charging.

The memory 909 may be used to store software programs and modules, and the processor 901 performs various functional applications and data processing of the online charging apparatus 900 by running the software programs and modules stored in the memory 909. The memory 909 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function (such as determining CBPSDB from session number, etc.), and the like; the storage data area may store data created according to the use of the online charging apparatus (such as a session routing algorithm, etc.), and the like. Further, the memory 909 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device. The program of the online charging method provided in the embodiment of the present application and the received initial/updated charging request message are stored in a memory, and when needed to be used, the processor 901 calls from the memory 909.

The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device, such as a server, a data center, etc., that is integrated with one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the units is only one logical functional division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. An online charging method, applied to an online charging system including a fused charging route distribution node (CBPAdapter) cluster and a fused charging application node (CBPAPP) cluster, wherein the CBPAdapter cluster includes a first CBPAdapter and at least one second CBPAdapter, and the CBPAPP cluster includes a first CBPAPP and at least one second CBPAPP, the online charging method comprising:

the first CBPAdapter receives an initial charging request message of a target service, wherein the initial charging request message at least comprises a session number and a user number of the target service;

the first CBPAdapter determining the first CBPAPP from the cluster of CBPAPPs;

and the first CBPAdapter sends the initial charging request message to the first CBPAPP, so that the first CBPAPP determines a target fusion charging session data node (CBPSDB) for storing the session data of the target service according to the session number, and determines a target fusion charging data node (CBPMDB) for storing the user data of the target service according to the user number.

2. The online charging method of claim 1, wherein after the first cbpapapter sends the initial charging request message to the first CBPAPP, the online charging method further comprises:

the first CBPAdapter receives an initial charging request response message sent by the first CBPAPP;

and the first CBPAdapter sends the initial charging request response message to a core network connected with the first CBPAdapter.

3. The online charging method of claim 2, wherein after the first CBPAdapter sends the initial charging request response message to a core network connected to the first CBPAdapter, the online charging method further comprises:

and the first CBPAdapter receives the update charging request message of the target service and updates data according to the update charging request message.

4. The online charging method of claim 3, wherein the receiving, by the first CBPAdapter, the update charging request message of the target service, and the updating data according to the update charging request message comprises:

step 1: the first CBPAdapter receives an update charging request message of the target service, wherein the update charging request message at least comprises the session number;

step 2: the first CBPAdapter determining the first CBPAPP from the cluster of CBPAPPs;

and step 3: the first CBPAdapter sends the update charging request message to the first CBPAPP, so that the first CBPAPP updates the session data of the target service stored in the target CBPSDB according to the session number and updates the user data of the target service stored in the target CBPMDB according to the session data;

5. The online charging method of claim 3, wherein the receiving, by the first CBPAdapter, the update charging request message of the target service, and the updating data according to the update charging request message comprises:

step 1: the first CBPAdapter receives an update charging request message of the target service, wherein the update charging request message at least comprises the conversation number and the user number;

and step 3: the first CBPAdapter sends the update charging request message to the first CBPAPP, so that the first CBPAPP updates the session data of the target service stored in the target CBPSDB according to the session number and updates the user data of the target service stored in the target CBPMDB according to the user number;

6. An online charging method, applied to an online charging system including a fused charging route distribution node (CBPAdapter) cluster and a fused charging application node (CBPAPP) cluster, wherein the CBPAdapter cluster includes a first CBPAdapter and at least one second CBPAdapter, and the CBPAPP cluster includes a first CBPAPP and at least one second CBPAPP, the online charging method comprising:

the first CBPAPP receives an initial charging request message of a target service sent by the first CBPAdapter, wherein the initial charging request message at least comprises a session number and a user number of the target service;

the first CBPAPP determines a target fusion charging session data node CBPSDB for storing the session data of the target service according to the session number;

the first CBPAPP determines a target fusion charging data node CBPMDB for storing the user data of the target service according to the user number;

the first CBPAPP updates user data stored on the target CBPMDB;

the first CBPAPP updates session data stored on the target CBPSDB.

7. The online charging method of claim 6, wherein after the first CBPAPP updates the session data stored on the target CBPSDB, the online charging method further comprises:

the first CBPAPP sends an initial charging request response message to the first CBPAdapter.

8. The online charging method of claim 7, wherein after the first CBPAPP sends an initial charging request response message to the first CBPAdapter, the online charging method further comprises:

the first CBPAPP receives an update charging request message of a target service sent by the first CBPAdapter, wherein the update charging request message at least comprises a session number of the target service;

and the first CBPAPP updates data according to the charging updating request message.

9. The online charging method of claim 8, wherein the updating the data by the first CBPAPP according to the update charging request message comprises:

step 1: the first CBPAPP receives an update charging request message of the target service sent by the first CBPAdapter, wherein the update charging request message comprises the session number;

step 2: the first CBPAPP updates the session data of the target service stored on the target CBPSDB, wherein the target CBPSDB corresponds to the session number;

and step 3: the first CBPAPP determines the user number of the target service according to the session data;

and 4, step 4: the first CBPAPP updates the user data of the target service stored in the target CBPMDB according to the user number, wherein the target CBPMDB corresponds to the user number;

10. The online charging method of claim 8, wherein the updating the data by the first CBPAPP according to the update charging request message comprises:

step 1: the first CBPAPP receives an update charging request message of the target service sent by the first CBPAdapter, wherein the update charging request message comprises the session number and the user number;

and step 3: the first CBPAPP updates the user data of the target service stored in the target CBPMDB according to the user number, wherein the target CBPMDB corresponds to the user number;

11. An online charging apparatus applied to an online charging system including a fused charging route distribution node (CBPAdapter) cluster and a fused charging application node (CBPAPP) cluster, wherein the CBPAdapter cluster includes a first CBPAdapter and at least one second CBPAdapter, and the CBPAPP cluster includes a first CBPAPP and at least one second CBPAPP, comprising:

a first receiving unit, configured to receive an initial charging request message of a target service, where the initial charging request message at least includes a session number and a user number of the target service;

a determining unit configured to determine the first CBPAPP from the CBPAPP cluster;

a first sending unit, configured to send the initial charging request message to the first CBPAPP, so that the first CBPAPP determines, according to the session number, a target fused charging session data node CBPSDB that stores session data of the target service, and determines, according to the user number, a target fused charging data node CBPMDB that stores user data of the target service.

12. The online charging apparatus according to claim 11, wherein the online charging apparatus further comprises:

a second receiving unit, configured to receive an initial charging request response message sent by the first CBPAPP;

a second sending unit, configured to send the initial charging request response message to a core network connected to the first CBPAdapter.

13. The apparatus of claim 12, wherein the online charging apparatus further comprises:

and the processing unit is used for receiving the charging updating request message of the target service and updating data according to the charging updating request message.

14. The apparatus according to claim 13, wherein the processing unit is specifically configured to:

step 2: determining the first CBPAPP from the CBPAPP cluster;

15. The apparatus according to claim 13, wherein the processing unit is further specifically configured to:

step 2: determining the first CBPAPP from the CBPAPP cluster;

16. An online charging apparatus applied to an online charging system including a fused charging route distribution node (CBPAdapter) cluster and a fused charging application node (CBPAPP) cluster, wherein the CBPAdapter cluster includes a first CBPAdapter and at least one second CBPAdapter, and the CBPAPP cluster includes a first CBPAPP and at least one second CBPAPP, comprising:

a first receiving unit, configured to receive an initial charging request message of a target service sent by the first cbpadapetter, where the initial charging request message at least includes a session number and a user number of the target service;

a first determining unit, configured to determine, according to the session number, a target convergence charging session data node CBPSDB that stores session data of the target service;

a second determining unit, configured to determine, according to the user number, a target fusion charging data node CBPMDB that stores the user data of the target service;

the first updating unit is used for updating the user data stored on the target CBPMDB;

and the second updating unit is used for updating the session data stored on the target CBPSDB.

17. The apparatus of claim 16, wherein the online charging apparatus further comprises:

a first sending unit, configured to send an initial charging request response message to the first CBPAdapter.

18. The apparatus of claim 17, wherein the online charging apparatus further comprises:

a second receiving unit, configured to receive an update charging request message of a target service sent by the first cbpadapetter, where the update charging request message at least includes a session number of the target service;

and the third updating unit is used for updating data according to the charging updating request message.

19. The apparatus according to claim 18, wherein the third updating unit is specifically configured to:

20. The apparatus according to claim 18, wherein the third updating unit is specifically configured to:

21. A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the method of any one of claims 1-10.