WO2014000179A1

WO2014000179A1 - Billing management method and device

Info

Publication number: WO2014000179A1
Application number: PCT/CN2012/077617
Authority: WO
Inventors: 吴先玉
Original assignee: 华为技术有限公司
Priority date: 2012-06-27
Filing date: 2012-06-27
Publication date: 2014-01-03
Also published as: CN103650416A

Abstract

Disclosed are a billing management method and device. The present invention relates to the field of communications. The method comprises: receiving an authentication and billing request sent by an access gateway, wherein the authentication and billing request carries a subscriber identity and an identity of a capability interface to be called; acquiring operator and billing information about a subscriber corresponding to the subscriber identity according to stored correspondences between the identity of the capability interface, the identity of an operator and product price information; and sending an expense subtraction message to the billing system of the operator of the subscriber corresponding to the subscriber identity, wherein the expense subtraction request message carries the billing information to enable the billing system to charge according to the billing information. The device comprises a receiving module, an acquisition module, and a sending module. The present invention can decrease operator costs and third-party usage costs.

Description

Billing management method and device

The present invention relates to the field of communications, and in particular, to a charging management method and device. Background art

In the field of communication, the SDP (Service Delivery Platform) includes an access gateway. The access gateway encapsulates the network capability and service support capability of the operator into a capability interface and is open to third parties. The third party can invoke the SDP. The capability interface uses the capabilities provided by the operator.

At present, one operator corresponds to one SDP, and the SDP stores the product price information of each product included in the operator, and each interface in the SDP corresponds to one product price information, when the third party needs to call one of the SDPs. When the interface is connected, the SDP obtains the product price information corresponding to the interface, obtains the charging information according to the price information of the product, and sends the charging information to the charging system of the operator.

In the process of implementing the present invention, the inventors have found that the prior art has at least the following problems:

At present, each operator needs to build a corresponding SDP, which increases the operating cost of the operator. If the third party needs to use the capabilities of multiple operators, the third party needs to access each operator's SDP and call the corresponding one. The interface increases the cost of using third parties. Summary of the invention

In order to reduce the cost of the operator and the cost of the third party, the present invention provides a charging management method and device. The technical solution is as follows:

A charging management method, the method comprising:

And receiving an authentication and charging request message sent by the access gateway, where the authentication and charging request message carries the user identifier and an identifier of the capability interface to be invoked;

Obtaining, according to the correspondence between the identifier of the stored capability interface, the identifier of the operator, and the product price information, the operator and the charging information to which the user corresponding to the user identifier belongs;

And sending the debit request message to the charging system of the operator to which the user corresponding to the user identifier is located, where the charging request message carries the charging information, so that the charging system performs the charging according to the charging information. fee. A billing management device, the device comprising:

a receiving module, configured to receive an authentication and charging request message sent by the access gateway, where the authentication charging request message carries a user identifier and an identifier of the capability interface to be invoked;

An acquiring module, configured to obtain, according to the corresponding relationship between the identifier of the stored capability interface, the identifier of the operator, and the product price information, the operator and the charging information to which the user corresponding to the user identifier belongs;

a sending module, configured to send a charging request message to the charging system of the operator to which the user corresponding to the user identifier is located, where the charging request message carries the charging information, so that the charging system is configured according to the Billing information is charged.

In the embodiment of the present invention, the authentication and charging request message sent by the access gateway is received, where the authentication charging request message carries the user identifier and the identifier of the capability interface to be invoked, according to the identifier and operation of the stored capability interface. Corresponding relationship between the quotient identifier and the product price information, obtaining the operator and billing information to which the user corresponding to the user identifier belongs, and sending a deduction request message to the billing system of the operator to which the user corresponding to the user identifier belongs. The charging request message carries the charging information, so that the charging system performs charging according to the charging information. In this way, the SDP can support multiple operators, multiple operators share one SDP, reduce the cost of the carrier, and when the third party uses the capabilities of multiple operators, only need to call a capability interface corresponding to the capability on the SDP. , reduce the cost of using third parties. DRAWINGS

FIG. 1 is a flowchart of a charging management method according to an embodiment of the present invention;

2 is a flowchart of storing user information according to another embodiment of the present invention;

3 is a flowchart of a charging management method according to another embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a charging management device according to another embodiment of the present invention. detailed description

The embodiments of the present invention will be further described in detail below with reference to the accompanying drawings. Referring to FIG. 1, an embodiment of the present invention provides a charging management method, including:

Step 101: The SDP receives an authentication and charging request message sent by the access gateway, where the authentication and charging request message carries a user identifier and an identifier of the capability interface to be called.

Step 102: The SDP obtains the operator and charging information to which the user corresponding to the user identifier belongs according to the identifier of the stored capability interface, the identifier of the operator, and the product price information. The charging information includes at least an identifier of the charging object, a charging fee, and a currency unit.

Step 103: The SDP sends a deduction request message to the charging system of the operator to which the corresponding user belongs, and the deduction request message carries the obtained charging information.

The foregoing step 102 may be specifically as follows:

1021: The SDP determines, according to the user identifier, an identifier of an operator to which the user corresponding to the user identifier belongs.

1022: The SDP obtains corresponding product price information, the obtained product price, from the identifier of the stored capability interface, the identifier of the operator, and the product price information according to the identifier of the capability interface to be invoked and the identifier of the operator. The information includes at least a product price, a currency unit, and a charging policy, and the charging policy includes at least payer information and charging rules;

1023: The SDP obtains an identifier of the charging object according to the paying party information included in the charging policy, and calculates a charging fee according to the product price and the charging policy.

The foregoing step 1021 may be specifically:

The SDP determines the range of the user ID to which the user ID belongs, and obtains the operator corresponding to the user ID range. The obtained operator is the operator to which the user corresponding to the user ID belongs.

The foregoing step 1023 may be specifically:

If the charging party information included in the charging policy is a user, the SDP determines that the identifier of the charging object is the user identifier; if the charging party information included in the charging policy is a third party, the SDP determines the identifier of the charging object. A third party's identification, and a billing fee based on the price of the product and the billing strategy.

Further, the method further includes:

The SDP obtains corresponding user information according to the user identifier from the corresponding relationship between the stored user identifier and the user information, where the user information includes at least a user status, and the user status includes a normal status or a suspended status, and is verified according to the user status. If the verification is passed, the operation of acquiring the operator and the charging information to which the user corresponding to the user identifier belongs is performed.

Further, the method further includes:

The SDP receives the user information synchronization request message sent by the information system of the operator, where the user information synchronization request message carries the user identifier and user information of the user of the operator, and the user information includes at least a user status, and the user status includes a normal status. Or a suspended state, storing the user ID and user information of the user.

In the embodiment of the present invention, the authentication and charging request message sent by the access gateway is received, where the authentication and charging request message carries the user identifier and the identifier of the capability interface to be invoked, according to the identifier of the stored capability interface, the operator. The correspondence between the identifier and the product price information acquires the operator and billing information to which the user corresponding to the user identifier belongs, and the billing information The information includes at least the identifier of the charging object, the charging fee, and the currency unit, and sends a charging request message to the charging system of the operator, and the charging request message carries the charging information. In this way, the SDP can support multiple operators, multiple operators share one SDP, reduce the cost of the operator, and when the third party uses the capabilities of multiple operators, only one capability interface corresponding to the capability needs to be called on the SDP. , reduce the cost of using third parties. The embodiment of the invention provides a charging management method. In this embodiment, the SDP includes an access gateway and a management platform. The SDP can support multiple operators by using the charging management method. Referring to FIG. 2, the management platform can establish users according to the following procedures 201 and 202. Correspondence between the identifier and the user information, including:

Step 201: The information system of the operator sends a user information synchronization request message to the management platform, where the user information synchronization request message carries at least the user identifier and user information of the user belonging to the operator.

The user information includes at least a user status, and the user status includes a suspended status and a normal status.

Step 202: The management platform receives the user information synchronization request message, and establishes a correspondence between the user identifier and the user information.

In this embodiment, the management platform may create a corresponding user database for each operator, and when the user information synchronization request message sent by the information system of an operator is received, the user identifier and user information of the user are established. Corresponding relationship, and then information about the correspondence between the established user identifier and the user information is stored in the user database corresponding to the operator.

The access gateway in the SDP encapsulates the network capability and/or service support capability of the operator into a capability interface, and the capability interface can open the network capability and/or service support capability of the operator to the third party. In this embodiment, the same network capability and/or service support capability provided by multiple operators corresponds to the same capability interface in the access gateway, and the technician establishes the identity of the capability interface and the identifier of the operator in the management platform in advance. Correspondence with product price information.

The product price information includes at least the product price, the currency unit, and the billing strategy. The charging policy defines the payer information and charging rules.

In this embodiment, the SDP can support multiple operators by using the foregoing method. Referring to FIG. 3, the method includes:

Step 301: The third party sends an interface call request message to the access gateway in the SDP, where the interface call request message carries the identifier of the third party, the identifier of the capability interface to be invoked, and the information to be sent, and the information to be sent includes the user identifier. And information content;

In this embodiment, the third party is an SP (Service Provider) and/or a CP (Content). Provider, content provider, etc., third parties can provide content and/or services to users, and users can use content and/or services provided by third parties.

The identifier of the capability interface to be invoked may be the name of the capability interface to be invoked, the information to be sent may be a short message or a multimedia message, and the capability interface to be invoked may be a short message service (Sms) for sending a short message. Message service) interface, etc.

In this embodiment, the information to be sent is used as the short message, and the capability interface to be invoked is taken as an example of the Sms interface. However, the description of the technical solution of the present invention is not provided as an example of the protection scope of the present invention. For example, the third party sends an interface call request message to the access gateway in the SDP, and the interface call request message carries the identifier IDA of the third party, the identifier sms of the Sms interface, and the short message to be sent, and the short message to be sent includes the user identifier. IDB and SMS content of the text message to be sent.

Step 302: The access gateway receives the call request message of the interface, and performs access authentication control and SLA (Service Level Agreement) policy control on the third party. After access authentication control and SLA policy control are performed on the third party, Sending an interface call response message to a third party;

Step 303: The access gateway sends an authentication and charging request message to the management platform in the SDP, where the authentication and charging request message carries the identifier of the third party, the user identifier, and the identifier of the capability interface to be invoked.

Specifically, the access gateway extracts the user identifier from the information to be sent, and sends an authentication and charging request message to the management platform in the SDP, where the authentication and charging request message carries the identifier of the third party, the extracted user identifier, and the to-be-called The identity of the capability interface.

For example, after receiving the identifier ID of the third party, the identifier sms of the Sms interface, and the interface call request message of the short message to be sent, the access gateway performs access authentication control and SLA policy control on the third party, and accesses the third party. After the authentication control is passed and the SLA policy is passed, the user identifier IDB is extracted from the short message to be sent, and the authentication and charging request message is sent to the management platform, where the authentication and charging request message carries the identifier IDA of the third party and the extracted user identifier. IDS and Sms interface identifier smso

Step 304: The management platform receives the authentication and charging request message, obtains the user status of the user corresponding to the user identifier, and performs verification according to the user status. If the verification succeeds, the operation corresponding to the user corresponding to the user identifier is determined. Specifically, the management platform receives the authentication and charging request message, where the authentication and charging request message carries the user identifier and the identifier of the capability interface to be invoked, and obtains the correspondence between the user identifier and the user information according to the user identifier. Corresponding user information is verified according to the user status included in the user information. If the user status included in the user information is in a suspended state, the verification fails. If the user status included in the user information is a normal status, The verification succeeds, and the operator to which the user corresponding to the user identifier belongs is determined according to the user identifier. If the verification fails, the management platform ends the operation and sends an exception message to notify the third party. Each operator corresponds to a user identifier range. When the user signs a contract with the operator, the operator assigns a user identifier to the user, and the user identifier is a user identifier in the range of the user identifier corresponding to the operator.

Correspondingly, the management platform determines, according to the user identifier, the operation of the operator to which the user corresponding to the user identifier belongs, which may be specifically: the management platform determines the range of the user identifier to which the user identifier belongs, and further obtains the operation corresponding to the user identifier range. The carrier obtained by the operator is the operator to which the user corresponding to the user ID belongs.

In this embodiment, the operator that the user corresponding to the user identifier belongs to may be determined according to the user identifier, and the corresponding relationship between the user identifier and the user information stored in the user database corresponding to the operator is obtained. The user information corresponding to the user identifier can improve the efficiency of obtaining user information.

The user state of the user is a suspended state, and the user state of the user may change from a normal state to a suspended state because the user owes a fee.

For example, the management platform receives the authentication and charging request message, where the authentication and charging request message carries the user identifier IDB and the identifier sms of the capability interface to be invoked, and obtains the correspondence between the user identifier and the user information according to the user identifier IDB. Corresponding user information is verified according to the user status included in the user information. If the user status included in the user information is normal, the verification is passed, and the user identification range in which the user identification is located is determined, and the user identifier is further obtained. The operator corresponding to the user ID range, and the ID of the operator is IDC.

Step 305: The management platform obtains a correspondence from the identifier of the stored capability interface, the identifier of the operator, and the product price information according to the identifier of the capability interface to be invoked and the identifier of the operator to which the user corresponding to the user identifier belongs. Product price information, the product price information includes at least product price, currency unit and billing strategy;

For example, the management platform is based on the identifier of the capability interface to be invoked and the identifier IDC of the operator to which the user corresponding to the user identifier IDB belongs, from the identifier of the stored capability interface, the identifier of the operator, and the product price information. Obtaining corresponding product price information, the product price information includes a product price, a currency unit, and a charging policy, and the paying party information defined by the charging policy is information such as a user.

Step 306: The management platform obtains the charging object and the charging fee according to the obtained product price and the charging policy, and sends a deduction request message to the charging system corresponding to the operator to which the corresponding user belongs, the deduction request The message carries the identifier, charging fee and currency unit of the obtained charging object;

Specifically, the management platform determines the charging object according to the charging party information included in the obtained charging policy, calculates the charging fee according to the obtained product price and the charging policy, and sends a deduction request message to the user corresponding to the user identifier. The billing system corresponding to the operator, the deduction request message carries the identifier of the determined billing object, the obtained billing fee, and the currency unit. If the obtained charging policy includes the paying party information, the determined charging object is the user corresponding to the user identifier, and the identifier of the charging object is the user identifier, if the obtained charging policy includes the payment If the party information is a third party, the determined charging object is a third party corresponding to the identifier of the third party, and the identifier of the charging object is the identifier of the third party.

The billing system receives the billing request message, where the billing request message carries the identifier of the billing object, the billing fee, and the currency unit, and the billing object corresponding to the identifier of the billing object is pre-paid with the operator. If the method is prepaid, the charging object corresponding to the identifier of the charging object is prepaid according to the charging fee and the currency unit. If the prepaid payment is successful, the charging response message is sent to the management platform, and the deduction response message is sent. If the prepaid payment fails, the charging response message is sent to the management platform, and the debit response message carries the identification information of the charging failure; if the charging object corresponding to the charging object identifier is in advance When the payment method of the operator signing is post-paid, the bill is generated, and the deduction response message is sent to the management platform, and the deduction response message carries the identification information of the successful billing.

For example, the management platform determines, according to the paying party information included in the obtained charging policy, that the charging object is the user corresponding to the user identifier IDB, calculates the charging fee according to the obtained product price and the charging policy, and sends a deduction fee. The request message is sent to the charging system corresponding to the operator to which the user corresponding to the IDB belongs, and the debit request message carries the identifier IDB of the determined charging object, the obtained charging fee and the currency unit; The payment method of the operator signing is prepaid, and the charging system receives the deduction request message, and prepays the charging object corresponding to the IDB of the charging object according to the charging fee and the currency unit, and the prepaid is successful. The deduction response message is sent, and the deduction response message carries the identification information of the charging success.

The charging policy includes at least the paying party information and the charging rule, and the management platform calculates the charging fee according to the product price and the charging rule in the charging policy. In addition, the management platform may also be based on the product price and the charging policy. The charging fee is calculated by one or more kinds of information other than the charging rule included in the charging rule and the charging policy. For example, the price of the product is one for each message, and the operator to which the user corresponding to the user ID is associated with the user has 100 free SMS messages per month, and the charging rule includes information such as the number of free short messages of 100, and the management platform. First, it is judged whether the number of free short messages used by the user in the current month reaches 100. If yes, the charging fee is calculated as 1 cent according to the product price, and if not, the obtained charging fee is 0.

Step 307: The management platform receives the chargeback response message sent by the charging system. If the chargeback response message carries the identifier information of the successful charging, the authentication and charging response message is sent to the access gateway, and the authentication and charging response message is sent. Carrying the identifier of the operator to which the user corresponding to the user identifier belongs;

If the deduction response message carries the identification information of the charging failure, the operation ends.

Step 308: The access gateway receives the authentication and charging response message, and invokes the corresponding according to the identifier of the capability interface to be invoked. The capability interface, and the information to be sent is sent to the capability component corresponding to the operator to which the user corresponding to the user identifier belongs by using the invoked capability interface;

After receiving the information to be sent, the capability component corresponding to the operator to which the user identifier corresponds is sent to the corresponding user according to the user identifier included in the information to be sent, and the reply is sent after the sending is completed. The response message is sent to the access gateway.

For example, for the short message, the capability component of the operator is the short message center. Correspondingly, the access gateway calls the corresponding Sms interface according to the identifier sms of the capability interface to be called, and sends the short message to be sent to the user identifier IDB through the Sms interface. The SMS center of the operator to which the user belongs, the short message center sends a short message to be sent to the corresponding user according to the user ID of the to-be-sent message, and sends a response message to the access gateway.

Step 309: The access gateway receives the response message sent by the capability component, and sends an authentication and charging confirmation request message to the management platform.

Step 310: After receiving the authentication and charging request message, the management platform sends a deduction confirmation request message to the charging system corresponding to the operator to which the user corresponding to the user identifier belongs;

The charging system performs the deduction confirmation operation after receiving the deduction confirmation request message, and then sends a deduction confirmation response message to the management platform.

Step 311: The management platform receives the charging system to send a deduction confirmation response message, and sends an authentication and charging confirmation response message to the access gateway.

In the embodiment of the present invention, the management platform receives the authentication and charging request message sent by the access gateway, where the authentication and charging request message carries the identifier of the third party, the user identifier, and the identifier of the capability interface to be invoked, according to the stored The identifier of the capability interface, the correspondence between the identifier of the operator and the product price information, the identifier of the third party, the identifier of the user, and the identifier of the capability interface to be invoked, obtain the operator and charging information of the user corresponding to the user identifier, The fee information includes at least the identifier of the billing object, the billing fee, and the currency unit, and the billing request message is sent to the billing system of the operator to which the user corresponding to the user identifier belongs, and the billing request message carries the billing information. The charging system is caused to perform charging according to the charging information. In this way, the SDP can support multiple operators, multiple operators share one SDP, reduce the cost of the carrier, and when the third party uses the capabilities of multiple operators, only need to call a capability interface corresponding to the capability on the SDP. , reduce the cost of using third parties. Referring to FIG. 4, an embodiment of the present invention provides a charging management device, including:

The receiving module 401 is configured to receive an authentication charging request message sent by the access gateway, where the authentication charging request message carries the user identifier and an identifier of the capability interface to be invoked; The obtaining module 402 is configured to obtain, according to the identifier of the stored capability interface, the identifier of the operator, and the product price information, the operator and the charging information to which the user corresponding to the user identifier belongs;

The sending module 403 is configured to send a charging request message to the charging system of the operator to which the corresponding user belongs, and the charging request message carries the obtained charging information, so that the charging system performs the charging information according to the charging information. Billing.

The charging information includes at least the identifier of the charging object, the charging fee, and the currency unit. The obtaining module 402 includes: a determining unit, configured to determine, according to the user identifier, an identifier of an operator to which the user corresponding to the user identifier belongs; An obtaining unit, configured to obtain corresponding product price information from the identifier of the stored capability interface, the identifier of the operator, and the product price information according to the identifier of the capability interface to be invoked and the identifier of the acquired operator, The product price information includes at least a product price, a currency unit, and a charging policy, and the charging policy includes at least payer information and charging rules;

And a second obtaining unit, configured to obtain an identifier of the charging object according to the paying party information included in the charging policy, and calculate a charging fee according to the product price and the charging policy.

The determining unit is configured to determine a range of user identifiers to which the user identifier belongs, and obtain an operator corresponding to the user identifier range, where the obtained operator is an operator to which the user corresponding to the user identifier belongs.

The second obtaining unit includes:

a first determining subunit, configured to: if the charging party information included in the charging policy is a user, determine that the identifier of the charging object is the user identifier;

a second determining subunit, configured to: if the charging party information included in the charging policy is a third party, determine that the identifier of the charging object is an identifier of the third party;

A calculation subunit, configured to calculate a charging fee according to the product price and the charging policy.

Further, the device further includes:

And a verification module, configured to obtain, according to the user identifier, the corresponding user information from the stored relationship between the user identifier and the user information, where the user information includes at least a user status, where the user status includes a normal status or a suspended status, according to the user information. The user status of the user identifier is verified by the user status, and if the verification is passed, the operation of acquiring the operator and the charging information of the user corresponding to the user identifier is performed.

Further, the device further includes:

a storage module, configured to receive a user information synchronization request message sent by an operator's information system, where the user information synchronization request message carries a user identifier and user information of a user to which the operator belongs, the user information includes at least a user status, and the user is stored. The user ID and user information of the user carried in the information synchronization request message.

In the embodiment of the present invention, the authentication charging request message sent by the access gateway is received, and the authentication charging request message carries The identifier of the user interface and the capability interface to be invoked, and the carrier and the charging information of the user corresponding to the user identifier are obtained according to the identifier of the stored capability interface, the identifier of the operator, and the product price information. The billing information includes at least the identifier of the billing object, the billing fee, and the currency unit, and the billing request message is sent to the billing system of the operator to which the user corresponding to the user identifier belongs, and the billing request message carries the billing information. And causing the charging system to perform charging according to the charging information. In this way, the SDP can support multiple operators, multiple operators share one SDP, reduce the cost of the carrier, and when the third party uses the capabilities of multiple operators, only need to call a capability interface corresponding to the capability on the SDP. , reduce the cost of using third parties. A person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium. The storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., which are within the spirit and scope of the present invention, should be included in the protection of the present invention. Within the scope.

Claims

claims

1. A billing management method, characterized by including:

The service distribution platform SDP receives the authentication and charging request message sent by the access gateway. The authentication and charging request message carries the user identification and the identification of the capability interface to be called;

According to the stored correspondence between the identification of the capability interface, the identification of the operator and the product price information, obtain the identification and billing information of the operator to which the user corresponding to the user identification belongs;

Send a deduction request message to the operator's charging system, so that the charging system performs charging according to the charging information, and the deduction request message carries the charging information.

2. The method of claim 1, wherein the charging information at least includes the identification of the charging object, the charging fee and the currency unit,

Obtaining the identification and billing information of the operator to which the user corresponds to the user identification based on the stored correspondence between the identification of the user identification, the identification of the capability interface, the identification of the operator and the product price information includes:

Determine the identity of the operator to which the user corresponding to the user identity belongs based on the user identity;

According to the identification of the capability interface to be called and the identification of the operator, the corresponding product price information is obtained from the corresponding relationship between the identification of the capability interface, the identification of the operator and the product price information, and the product price information is At least including product price, currency unit and billing strategy, the billing strategy at least includes payer information and billing rules;

Obtain the identification of the charging object according to the payer information included in the charging policy, and calculate the charging fee according to the product price and the charging policy.

3. The method of claim 2, wherein determining the operator to which the user corresponding to the user identification belongs based on the user identification includes:

Determine the user identification range to which the user identification belongs, and obtain the operator corresponding to the user identification range. The obtained operator is the operator to which the user corresponding to the user identification belongs.

4. The method of claim 2, wherein the authentication and charging request message also carries a third-party identifier, and the identifier of the charging object is obtained based on the payer information included in the charging policy, include:

If the payer information included in the charging policy is a user, it is determined that the identity of the charging object is the user identity; If the payer information included in the charging policy is a third party, it is determined that the identifier of the charging object is the identifier of the third party.

5. The method according to any one of claims 1 to 4, characterized in that, before obtaining the operator and billing information to which the user corresponding to the user identification belongs, it further includes:

Obtain corresponding user information from the stored correspondence between user identification and user information according to the user identification. The user information at least includes user status. The user status includes normal status or suspended status, and the user status is verified. , if the verification passes, then perform the operation of obtaining the operator and billing information to which the user corresponding to the user ID belongs.

6. The method according to any one of claims 1 to 5, characterized in that, the method further includes: receiving a user information synchronization request message sent by the operator's information system, the user information synchronization request message carrying The user identification and user information of the user belonging to the operator, the user information at least includes a user status, the user status includes a normal state or a suspended state, and the user identification and user information of the user are stored.

7. A billing management device, characterized in that the device includes:

A receiving module, configured to receive an authentication and accounting request message sent by the access gateway, where the authentication and accounting request message carries the user identifier and the identifier of the capability interface to be called;

An acquisition module, configured to obtain the operator and billing information of the user corresponding to the user ID based on the stored correspondence between the identification of the capability interface, the identification of the operator and the product price information;

A sending module, configured to send a deduction request message to the billing system of the operator to which the user corresponding to the user identification belongs. The deduction request message carries the billing information, so that the billing system can Billing information is used for billing.

8. The device according to claim 7, wherein the charging information at least includes the identification of the charging object, the charging fee and the currency unit,

The acquisition module includes:

A determining unit, configured to determine the identity of the operator to which the user corresponding to the user identity belongs based on the user identity; A first acquisition unit, configured to determine based on the identity of the capability interface to be called and the identity of the operator , obtain the corresponding product price information from the stored correspondence between the identification of the capability interface, the identification of the operator and the product price information. The product price information at least includes the product price, currency unit and billing strategy, and the billing The policy at least includes payer information and billing rules; The second obtaining unit is configured to obtain the identification of the charging object according to the payer information included in the charging policy, and calculate the charging fee according to the product price and the charging policy.

9. The device according to claim 8, characterized in that,

The determining unit is configured to determine the user identification range to which the user identification belongs, and obtain the operator corresponding to the user identification range, and the obtained operator is the operator to which the user corresponding to the user identification belongs.

10. The device according to claim 8, wherein the second acquisition unit includes:

The first determination subunit is configured to determine that the identity of the charging object is the user identity if the payer information included in the charging policy is a user;

The second determination subunit is configured to determine that the identifier of the charging object is the identifier of the third party if the payer information included in the charging policy is a third party;

The calculation subunit is used to calculate the charging fee according to the product price and the charging policy.

11. The device according to any one of claims 7 to 10, characterized in that the device further includes: a verification module, configured to obtain a correspondence between a stored user identification and user information based on the user identification. Corresponding user information is obtained from the relationship. The user information at least includes user status. The user status includes normal status or suspended status. Verification is performed based on the user status. If the verification is passed, the corresponding user identification is obtained. Operation of the operator and billing information to which the user belongs.

12. The device according to any one of claims 7 to 11, wherein the device further includes: a storage module configured to receive a user information synchronization request message sent by the operator's information system, the user The information synchronization request message carries the user identification and user information of the user belonging to the operator. The user information at least includes a user status. The user status includes a normal state or a suspended state. The user identification and user information of the user are stored.