WO2007143926A1

WO2007143926A1 - An ims network charging system and method

Info

Publication number: WO2007143926A1
Application number: PCT/CN2007/001799
Authority: WO
Inventors: Guangbing Yan; Haiyan Jian; Leibin Wang; Lion Zhao
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-06-09
Filing date: 2007-06-06
Publication date: 2007-12-21
Also published as: CN1983937A; CN100426725C

Abstract

There are an IMS network charging system and a method. The method includes: when a special charging identifier which indicates makeing charging processing is not present in the charging request received from a network element (NE), the charging entity adds a special charging identifier to the charging response sent to the NE based on the charging policy; when a special charging identifier is present in the charging response, the NE adds the special charging identifier to the service request sent to the subsequent NE or to the service response sent to the previous NE; when a special charging identifier is present, the subsequent NE and the previous NE determine whether send a charging request to the corrsponding charging entity based on the special charging identifier and the charging policy, and adds the special charging identifier to the service request sent to the subsequent NE or the service response sent to the previous NE; and after the corresponding charging entity identifies that a special charging identifier is present, it determines whether make charging processing based on the special charging identifier and the charging policy. Thus the repeated charging for the user service is avoided.

Description

IMS network charging system and method

The present invention relates to the field of communications, and in particular, to an IMS network charging system and method. Background technique

IMS is a subsystem superimposed on the existing packet domain in the WCDMA network added in the 3GPP R5 phase. The packet domain is used as the bearer channel for the upper layer control signaling and media transmission, and the SIP protocol is introduced as the service control protocol. It is easy to expand and easy to combine media. It provides rich multimedia services by separating service control from bearer control. The main functional entities in IMS include CSCF, which controls user registration and session control functions, and centralized management user subscription. The home subscriber server HSS of the data, the application server AS providing various service logic control functions, and the charging collection function CCF for offline charging and the online charging system OCS for online charging.

FIG. 1 is a schematic block diagram of a charging system architecture. The charging related system architecture defined in the 3GPP standard is as shown in FIG. 1 , wherein the functions and mechanisms of each charging entity are described as follows:

First, CGF function:

1. Receive CDRs from the CDF;

2. Preprocessing of CDRs;

(1) verification, merging and CDR format processing;

(2) CDR error handling;

(3) Preservation of CDRs.

3. The CDR filter and the root filter rule store the CDR in the classified file, where the filtering rule may include: a CDR type, a CDR parameter, a CDF that generates a CDR, and the like;

4, CDR file management, including file creation, file open / close trigger, file deletion;

5. The CDR file is transferred to the billing domain BD.

Second, the CDF function:

1. Construct a CDR based on a single charging event. 2. Construct a CDR based on a collection of several charging events.

3. Each billing event is for a certain CDR.

4. There is no necessary synchronization relationship between receiving the charging event and creating the CDR. The CDF will receive and process billing events in a near real-time manner and generate CDRs.

5. There can be a one-to-one or one-to-many relationship between CDF and NE.

6. All billing events used to construct a CDR must originate from the same NE.

Third, the billing function of OCS is:

1. Online charging function OCF: Online charging function OCF includes two modules, one is based on the accounting function of the session, and the other is the event-based charging function.

The session-based charging function is responsible for online charging of networks and user sessions, such as: voice calls, PDP context charging for GPRS, or charging for IMS sessions.

The event-based charging function performs event-based online charging, also known as content charging, and is associated with an application server or service network element, including a SIP application server.

2. Rate function RF: The rate function determines the price of network resources based on the behavior of the online charging function OCF. The OCF is responsible for obtaining and providing the necessary information from the billing event to the RF, and then obtaining the output rate from the response. The RF can handle a wide range of rate types, such as: rates for data traffic (eg, based on charging initiated by the access network entity, ie, bearer-level charging); rate of session/connection events (based on SIP application-initiated) Billing, ie subsystem-level billing); rate of business events (based on WEB content or MMS billing, ie service level billing).

3. Account management function: Account management function ABMF completes the management of user accounts in OCS. 2 is a schematic diagram of a charging process of an IMS network element in a process of processing a service, as described in the 3GPP standard.

The charging process of the IMS network element in the process of processing the service is shown in Figure 2. The charging process for the user is as follows:

1. The user initiates a service request to the network element.

2. The network element sends a charging authorization request to the charging entity to apply for authorization.

3. The charging entity determines that the user can perform the service, and delivers the charging authorization to respond.

4. The network element forwards the service request. 5. The network element receives the service response.

6. The network element initiates a charging start request to the charging entity.

7. The charging entity starts charging, and the charging is started to respond.

8. The network element returns the service response to the user and monitors the business process.

9. The network element detects the process of the service, and periodically sends a charging update request to the charging entity.

10. The charging entity updates the charging information, and sends a charging update response.

11. The user terminates the service and sends a service termination request to the network element.

12. The network element sends a charging termination request to the charging entity.

13. The charging entity terminates the charging, and the charging termination response is sent.

14. The network element forwards the service termination request.

15. The network element receives the service termination response.

16. The network element sends a service termination response to the user.

In an IMS network, when multiple network elements have accounting interfaces, multiple network elements perform charging processing on the same service. In this case, the service performed by the user only needs to perform charging processing on one of the network elements, and all the network elements do not need to perform charging processing on the service of the user, or the service is a free service (such as an emergency). Call), do not need to do billing processing on any network element. Currently, in the 3GPP charging mechanism, there is no charging cooperative processing mechanism, and the user service cannot be charged only in a specific network element, but not in other network elements.

3 is a schematic diagram of a charging process of a plurality of network elements having an accounting interface. As shown in FIG. 3, for a user service, the service flow passes through the calling S-CSCF, the calling AS1, the AS2, and the called S- CSCF, etc., its business process is: 1 2 3 4 5 6, where the calling S-CSCF, the calling AS1, the AS2, and the called S-CSCF all have charging interfaces, and need to send charging information to the charging entity.

The disadvantages of the prior art are as follows: Under the current charging mechanism, it is impossible to implement the charging process only for the calling S-CSCF or one of the ASs, and the other network elements do not need to charge the user service. Processing needs. Summary of the invention The embodiment of the present invention provides a network charging system and method, which is used to implement charging processing for a user's service request only on a certain network element or a plurality of network elements having an accounting interface, so as to avoid duplication of user services. fee.

The IMS network charging system provided by the embodiment of the present invention includes:

The network element side charging processing device is located on the network element side with the charging interface, and is used to identify whether there is a special charging identifier indicating that the charging processing is not required in the service request/response or the charging request/response. In the case of the charging identifier, determining whether to send the charging request including the special charging identifier to the charging entity according to the special charging identifier and the charging policy, and sending the service request including the special charging identifier to the subsequent network element or to the front The network element sends a service response including a special charging identifier;

The charging entity side charging processing device is located at the charging entity side, and is configured to identify whether a special charging identifier exists in the charging request, and if there is no special charging identifier, perform charging processing, and according to the charging policy It is determined whether the special charging identifier is added to the charging response sent to the network element, and if there is a special charging identifier, determining whether to perform the charging processing according to the special charging identifier and the charging policy.

The embodiment of the invention further provides an IMS network charging method, which includes the following steps:

In the case that there is no special charging identifier indicating that the charging process is not required in the charging request received from the network element, the charging entity adds the special charging identifier to the charging sent to the network element according to the charging policy. In response

If the special charging identifier exists in the charging response received from the charging entity, the network element adds the special charging identifier to the service request or the previous network element sent to the subsequent network element. Business response

If the special charging identifier exists in the service request or the service response, the subsequent network element and the preceding network element determine whether to send the charging to the corresponding charging entity according to the special charging identifier and the charging policy. Requesting, and adding the special charging identifier to a service request sent to a subsequent network element or a service response of a preceding network element;

After the corresponding charging entity identifies that the special charging identifier exists in the charging request, determining whether to perform charging processing according to the special charging identifier and the charging policy. The embodiment of the present invention can implement the service request for the user only in a certain network element or a network element having a charging interface. [There is a charging process, or the network element of the free service does not perform charging processing, and the shielding is performed. The charging process of some of the network elements is removed, thereby avoiding repeated charging of user service requests and simplifying the processing of the charging system. DRAWINGS

1 is a schematic block diagram of a charging system architecture in the background art;

2 is a schematic diagram of a charging process of the IMS network element in the process of processing a service in the background; FIG. 3 is a schematic diagram of a charging process of a plurality of network elements having a charging interface in the background art; FIG. A schematic block diagram of the IMS network charging system in the embodiment;

FIG. 5 is a schematic flowchart of an implementation process of an IMS network charging method according to an embodiment of the present invention; FIG.

6 is a schematic flowchart of a detailed implementation process of the IMS network charging method in the embodiment of the present invention; FIG. 7 is a schematic flowchart of an implementation process of the charging process according to the first embodiment of the present invention; FIG. 9 is a schematic flowchart of an implementation process of a charging process according to Embodiment 3 of the present invention; FIG. 10 is a schematic flowchart of Embodiment 4 of the embodiment of the present invention; FIG. 11 is a schematic flowchart of an implementation process of a charging process according to Embodiment 5 of the embodiment of the present invention. detailed description

Specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

4 is a schematic block diagram of an IMS network charging system. As shown in FIG. 4, the IMS network charging system in the embodiment of the present invention includes: a network element side charging processing device 401, located on a network element side with an accounting interface, for identifying a service request/response or charging request/response Whether there is a special charging identifier indicating that the charging processing is not required, and if there is a special charging identifier, determining whether to send the charging including the special charging identifier to the charging entity according to the special charging identifier and the charging policy Requesting, and sending a service request including a special charging identifier to a subsequent network element or transmitting a service response including a special charging identifier to the preceding network element. The network element side charging processing apparatus 401 includes: a network element side identifying module 401-1, configured to identify whether a special charging identifier exists in the service request/response and the charging response; the network element side determining module 401-2, In the case that there is no special charging identifier, it is determined whether to send a charging request including a special charging identifier to the charging entity according to the service request and the charging policy; if the special charging identifier exists, the network element side is indicated The identifier adding module adds a special charging identifier; and the network element side identifier adding module 401-3 is configured to add the special charging identifier to the charging request sent to the charging entity according to the indication of the network element side determining module, or Add to the service request sent to the subsequent NE or the service response of the previous NE.

The charging entity side charging processing device 402 is located at the charging entity side, and is used to identify whether there is a special charging identifier in the charging request, and if there is no special charging identifier, perform charging processing, and according to the charging The policy determines whether to add a special charging identifier to the charging response sent to the network element, and if there is a special charging identifier, determine whether to perform charging processing according to the special charging identifier and the charging policy.

The charging entity side charging processing device 402 includes: a charging entity side identifying module 402-1, configured to identify whether a special charging identifier exists in the charging request; and a charging entity side determining module 402-2, configured to If there is no special charging identifier, it is determined according to the service charging policy or the user subscription information whether to add the special charging identifier to the charging response sent to the network element; and in the case where the special charging identifier exists, according to The special charging identifier and the service charging policy determine whether to perform charging processing; and the charging entity side identifier adding module 402-3 is configured to add the special charging identifier to the network according to the indication of the charging entity side determining module. The billing response in the meta.

The charging policy includes at least one of the following information: a service charging policy, user subscription information, and a local charging policy of the network element. The special billing identifier can be a free logo. The header field or parameter of the extended call control protocol message may be adapted to carry the special charging identifier. It is also possible to carry a special charging identifier by extending the parameters in the charging interface protocol message.

The IMS network charging system of the embodiment of the present invention can be used for an online meter, a system, and an offline charging system.

FIG. 5 is a schematic diagram of an implementation process of an IMS network charging method. As shown in FIG. 5, the IMS network charging method in the embodiment of the present invention includes the following steps: Step 501: If there is no special charging identifier indicating that the charging process is not required in the charging request received from the network element, the charging entity adds the special charging identifier to the network element according to the charging policy. Billing response;

Step 502: When a special charging identifier exists in the charging response received from the charging entity, the network element adds the special charging identifier to the service request sent to the subsequent network element or the service response of the preceding network element.

Step 503: If a special charging identifier exists in the service request or the service response, the subsequent network element and the preceding network element determine whether to send the charging request to the corresponding charging entity according to the special charging identifier and the charging policy, and The charging identifier is added to the service request sent to the subsequent network element or the service response of the preceding network element;

Step 504: After identifying the special charging identifier in the charging request, the corresponding charging entity determines whether to perform charging processing according to the special charging identifier and the charging policy.

The foregoing charging policy includes at least one of the following: a service charging policy, user subscription information, and a local charging policy of the network element.

The above step 501 can include:

Step a, identifying whether there is a special charging identifier in the charging request received from the network element; and step b, in the case that there is no special charging identifier, the charging entity is based on the service charging policy or the user subscription information. Determine if a special charging ID needs to be added to the charging response sent to the network element.

The above step 502 can include:

Step c: The network element checks whether a special charging identifier exists in the charging response received from the charging entity;

Step d: In the case that a special charging identifier exists, the network element adds the special charging identifier to the service request sent to the subsequent network element or the service response of the preceding network element.

The above step 503 can include:

Step e, the subsequent network element and the preceding network element check whether there is a special charging identifier in the service request and the service response; Step f: If there is a special charging identifier, determine whether to send a charging request to the corresponding charging entity according to the special charging identifier and the local charging policy, and add the special charging identifier to the service request sent to the subsequent network element or The business response of the previous network element.

The above step 504 can include:

Step g, the corresponding charging entity checks whether there is a special charging identifier in the charging request; Step h, in the case that there is a special charging identifier, the corresponding charging entity determines whether to calculate according to the special charging identifier and the service charging policy Fee processing.

The special charging identifier can be carried by extending the header field or parameters of the call control protocol message. The special charging identifier can also be carried by extending the parameters in the charging interface protocol message.

The above IMS network charging method can be used for an online charging system and an offline charging system.

6 is a schematic flowchart of a detailed implementation process of an IMS network charging method. When an IMS network has an accounting interface for multiple network elements, when a service request arrives at a network element having an accounting interface (such as S-CSCF, AS, etc.) When the network element adds a service logic for processing the charging process of the service request, its business logic is as shown in FIG. 6, and includes the following steps:

Step 601: The S-CSCF/AS#1 receives the service request message.

Step 602: The S-CSCF/AS#1 sends a charging request to the charging entity #1.

Step 603, a) the charging entity #1 performs the corresponding charging process; b) the charging entity #1 determines whether the special charging identifier needs to be inserted in the response message according to the service charging policy or the user subscription information, and the subsequent network element according to this The special billing identifier determines whether the service needs to be billed.

Step 604: If the special charging identifier needs to be inserted, the charging entity #1 sends an accounting response message with a special charging identifier to the S-CSCF/AS#1.

Step 605: After receiving the charging response with the special charging identifier, the S-CSCF/AS#1 performs corresponding service processing and inserts the special charging identifier into the service request message, and forwards the service request message to the next hop. Network element.

Step 606: a) After receiving the service request message, the S-CSCF/AS#2 checks whether the message carries the special charging identifier; b) the S-CSCF/AS#2 determines according to the special charging identifier and the local charging policy. Whether to send a charging request to the charging entity #2. Step 607: If the charging request needs to be sent to the charging entity #2, the S-CSCF/AS#2 inserts a special charging identifier in the charging request message, and sends the charging request message to the charging entity #2.

Step 608: a) After receiving the charging request message, the charging entity #2 checks whether the message carries a special charging identifier; b) the charging entity #2 determines whether it needs to be done according to the special charging identifier and the service charging policy. The corresponding billing process.

Step 609: The charging entity #2 returns an accounting response message.

Step 610: The S-CSCF/AS#2 forwards the service request message, and carries the special charging identifier transmitted by the last hop network element in the service request message.

With this method, the service request to the user can be performed only on one or a few network elements with an accounting interface, or the user service can be processed freely, and the charging process of other network elements is blocked. It can avoid repeated charging for user service requests and simplify the processing of the billing system.

Example 1:

7 is a schematic flowchart of an implementation process of a charging process in Embodiment 1, as shown in FIG. 7, a network element in an IMS network receives a SIP service request without a special charging identifier, and a service charging policy configuration on the charging entity is shown in FIG. To implement the charging process in the subsequent network element, the implementation process of the foregoing invention includes the following steps: Step 701: The S-CSCF/AS receives the SIP service request message, and the request message does not carry the special charging identifier.

Step 702: The S-CSCF/AS sends a charging authorization request message to the charging entity.

Step 703: a) the charging entity performs charging authorization processing; b) the charging entity determines that a special charging identifier needs to be inserted in the response message according to the service charging policy or the user subscription information, and the subsequent network element does not need to perform charging again. deal with.

Step 704: The ten-fee entity sends a charging authorization response message to the S-CSCF/AS, where the special charging identifier is carried, and the subsequent network element is not required to perform charging processing.

Step 705: The S-CSCF/AS identifies the special charging identifier from the charging authorization response message, performs corresponding service processing, and inserts the special charging identifier into the service request message when the SIP service request is forwarded. The subsequent network element can identify the special charging identifier in the SIP service request, and according to the special charging standard Know no longer do billing processing.

Step 706: The S-CSCF/AS receives the SIP service response returned by the subsequent network element.

Step 707: The S-CSCF/AS sends a charging start request to the charging entity.

Step 708: The charging entity returns a charging start response to the S-CSCF/AS.

In step 709, the S-CSCF/AS inserts a special charging identifier according to the special charging identifier delivered by the charging entity in the previous SIP service request, and the previous network element may be inserted according to the special charging identifier. Do the corresponding billing process.

Example 2:

8 is a schematic flowchart of an implementation process of a charging process in Embodiment 2. As shown in FIG. 8, a network element in an IMS network receives a SIP service request with a special charging identifier, and the identifier is that the subsequent network element does not need to perform charging. Processing, according to the local charging policy of the S-CSCF/AS, does not need to perform charging processing. The implementation process of applying the above invention includes the following steps:

Step 801: The S-CSCF/AS receives the SIP service request message, where the request message carries a special charging identifier.

Step 802: a) The S-CSCF/AS identifies the special charging identifier in the SIP service request. b) The S-CSCF/AS determines that the charging request is not required to be sent to the charging entity according to the configured local charging policy. After the S-CSCF/AS performs the corresponding SIP service processing, the SIP service request message is forwarded, and the SIP service request message carries the special charging identifier transmitted by the previous hop network element, and the subsequent network element can be based on the special The fee identification is handled accordingly.

Step 804: The S-CSCF/AS receives the SIP service response message sent by the subsequent network element.

Step 805: The S-CSCF/AS forwards the SIP service response message.

Example 3:

9 is a schematic flowchart of an implementation process of a charging process in Embodiment 3. As shown in FIG. 9, a network element in an IMS network receives a SIP service request with a special charging identifier, and the identifier is that the subsequent network element does not need to perform charging. Processing, but according to the local charging policy of the S-CSCF/AS, the charging process needs to be performed. The implementation process of applying the above invention includes the following steps: Step 901: The S-CSCF/AS receives the SIP service request message, where the request message carries a special charging identifier.

Step 902: a) The S-CSCF/AS identifies the special charging identifier in the SIP service request; b) The S-CSCF/AS determines that the charging request message needs to be sent to the charging entity according to the configured local charging policy.

Step 903: The S-CSCF/AS sends a charging authorization request message to the charging entity, and inserts a special charging identifier in the charging authorization request message.

Step 904: a) the charging entity identifies the special charging identifier in the charging authorization request; b) the charging entity determines whether the charging authorization processing needs to be performed according to the special charging identifier and the service charging policy.

Step 905: After performing the corresponding charging authorization process, the charging entity sends a charging authorization response message to the S-CSCF/AS.

Step 906: The S-CSCF/AS forwards the SIP service request message, and carries the special charging identifier transmitted by the last hop network element in the SIP service request message.

Example 4:

10 is a schematic flowchart of an implementation process of a charging process according to Embodiment 4, as shown in FIG. 10, a network element in an IMS network receives a SIP service request without a special charging identifier, and the network element performs normal charging processing, and The fee entity does not carry the special charging identifier in the charging authorization response message. However, when the network element receives the SIP service response, it identifies that the SIP service response message carries a special charging identifier. The implementation process of applying the above invention includes the following Steps:

Step 1001: The S-CSCF/AS receives a SIP service request message, where the request message does not carry a special charging identifier.

Step 1002: The S-CSCF/AS performs normal charging processing, and sends a charging authorization request message to the charging entity.

Step 1003: The charging entity performs charging authorization processing, and determines, according to the service charging policy or the user subscription information, that the special charging identifier is not inserted in the response message, and the charging entity sends a charging authorization response message to the S-CSCF/AS. .

Step 1004: The S-CSCF/AS performs corresponding service processing, and forwards the SIP service request message. Step 1005: The S-CSCF/AS receives the SIP service response message returned by the subsequent network element, and identifies the It carries a special billing identifier.

Step 1006: The S-CSCF/AS sends a charging start request message to the charging entity, and inserts the special charging identifier in the request message.

Step 1007, a) the charging entity identifies the special charging identifier in the charging start request message; b) the charging entity determines to perform the corresponding charging processing according to the special charging identifier and the service charging policy, and the charging or not fee.

Step 1008: The charging entity returns a charging start response message to the S-CSCF/AS.

Step 1009: The S-CSCF/AS forwards the SIP service response message, and inserts a special charging identifier in the response message, and the preceding network element can perform corresponding charging processing according to the special charging identifier.

Example 5

11 is a schematic flowchart of an implementation process of a charging process in Embodiment 5. As shown in FIG. 11, a network element in an IMS network receives a SIP service request without a special charging identifier, and the network element can identify that the service is a free service ( For example, an emergency call is required, but according to the local charging policy of the S-CSCF/AS, the charging process is required. The application process of the above includes the following steps:

Step 1101: The S-CSCF/AS receives the SIP service request message, and the request message does not carry the special charging identifier.

Step 1102, a) The S-CSCF/AS identifies that the service is a free service (such as an emergency call); b) The S-CSCF/AS determines that the charging request message needs to be sent to the charging entity according to the configured local charging policy.

Step 1103: The S-CSCF/AS sends a charging authorization request message to the charging entity, and inserts a special charging identifier in the charging authorization request message, indicating that the service does not need to be charged.

Step 1104: a) the charging entity identifies the special charging identifier in the charging authorization request; b) the charging entity determines whether the charging authorization processing needs to be performed according to the special charging identifier and the service charging policy.

Step 1105: After performing the corresponding charging authorization process, the charging entity sends a charging authorization response message to the S-CSCF/AS.

In step 1106, the S-CSCF/AS forwards the SIP service request message, and inserts a special charging identifier in the SIP service request message, and the subsequent identification of the service does not need to perform charging processing. The subsequent network element can no longer charge the service according to the special charging identifier. Example 6

In the IMS network, the service request message of the foregoing embodiment may be a SIP protocol message, and the P-Charging-Vector header field of the SIP protocol is extended to deliver a special charging identifier. The P-Charging-Vector header i or is defined as follows:

P-Charging- Vector = "P-Charging- Vector" HCOLON icid-value

*(SEMI charge-params)

Charge-params = icid-gen-addr I orig-ioi I

Term-ioi I generic-param

Iicid-value = "icid-value" EQUAL gen-value icid-gen-addr = "icid-generated-at" EQUAL host orig-ioi = "orig-ioi" EQUAL gen-value term-ioi = "term-ioi" EQUAL gen-value generic-param = token [ EQUAL gen-value ]

The generic-param parameter can be extended in the form of: charging-flag = true/false, where the parameter true indicates that the accounting process needs to be performed later, and false indicates that the subsequent accounting processing is not required. The example of the entire service request message is as follows:

INVITE sip:joe@example.com SIP/2.0

Via: SIP/2.0AJDP P 1.home 1.net:5060;branch=z9hG4bK34ghi7a

Via: SIP/2.0/UDP 192.0.2.4:5060;branch=z9hG4bKnashds7

To: sip:joe@example.com

From: sip:ual@homel .net;tag=456248

Call-ID: 843817637684230998sdasdh09

CSeq: 18 INVITE

Contact: sip:ual@192.0.2.4

P-Charging- Vector: icid-value= 1234bc9876e;

Iicid-generated-at=192.0.6.8;

Orig-ioi=home 1.net;

Charging-flag=false With this method, the service request to the user can be performed only on one or some of the network elements with the charging interface, or the network elements of the free service are not charged, and some of the networks are blocked. The charging process of the element can avoid repeated charging of the user service request and simplify the processing process of the charging system.

In the embodiment of the present invention, the charging process can also be performed by the following method. In the case that multiple network elements have charging interfaces, the charging process can also be centralized and processed in the charging system. Each network element sends a charging request to the charging system for the same service request of the user. After receiving all the charging requests, the charging system separates the charging request of the same service for all charging requests, and these Request to do the merge process to complete the billing for the same service.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Rights request

An IMS network charging system, wherein the system comprises:

The network element side charging processing device is located on the network element side with the charging interface, and is used to identify the service request or response, or whether there is a special charging identifier indicating that the charging processing is not required in the charging request or the response. In the case of the special charging identifier,

Determining, according to the special charging identifier and the charging policy, whether to send a charging request including the special charging identifier to the charging entity;

Sending a service request including the special charging identifier to a subsequent network element or sending a service response including the special charging identifier to a preceding network element;

The charging entity side charging processing device is located at the charging entity side, and is configured to identify whether the special charging identifier exists in the charging request,

If the special charging identifier does not exist, performing charging processing, and determining, according to the charging policy, whether to add the special charging identifier to a charging response sent to the network element; In the case of the special charging identifier, it is determined whether to perform charging processing according to the special charging identifier and the charging policy.

The IMS network charging system according to claim 1, wherein the charging policy comprises: one of a service charging policy, user subscription information, and a local charging policy of the network element or a combination thereof.

The IMS network charging system according to claim 1, wherein the network element side charging processing device comprises:

a network element side identifying module, configured to identify whether the special charging identifier exists in the service request or the response and the charging response;

a network element side determining module, configured to determine, according to the service request and the charging policy, whether to send an accounting request including the special charging identifier to the charging entity, if the special charging identifier does not exist And in the case that the special charging identifier is present, instructing the network element side identifier adding module to add the special charging identifier; The network element side identifier adding module is configured to add the special charging identifier to the charging request sent to the charging entity according to an indication of the network element side determining module, or add to send Go to the service request of the subsequent NE or the service response of the previous NE.

The IMS network charging system according to claim 1, wherein the charging entity side charging processing device comprises:

a billing entity side identifying module, configured to identify whether the special billing identifier exists in the billing request^

a billing entity side determining module, configured to determine, according to the service charging policy or user subscription information, whether to add the special charging identifier to the network element, if the special charging identifier does not exist And determining, in the case of the charging response, whether the charging process is performed according to the special charging identifier and the service charging policy;

The charging entity side identifier adding module is configured to add the special charging identifier to the charging response sent to the network element according to the indication of the charging entity side determining module.

The IMS network charging system according to claim 1, wherein the special charging identifier comprises a free identification.

The IMS network charging system according to any one of claims 1 to 5, wherein the special charging identifier is carried by extending a header field or a parameter of a call control protocol message;

Or, the special charging identifier is carried by extending parameters in the charging interface protocol message.

An IMS network charging method, the method includes the following steps: in a case where there is no special charging identifier indicating that charging processing is not required in the charging request received from the network element, The charging entity adds the special charging identifier to the charging response sent to the network element according to the charging policy;

If the special charging identifier exists in the service request or the service response, the subsequent network element and the preceding network element determine whether to perform the corresponding charging according to the special charging identifier and the charging policy. Sending a charging request, and adding the special charging identifier to a service request sent to a subsequent network element or a service response of a preceding network element;

After the corresponding charging entity identifies that the special charging identifier exists in the charging request, determining whether to perform charging processing according to the special charging identifier and the charging policy.

The charging method of the IMS network according to claim 7, wherein the charging policy comprises: one of a service charging policy, a user subscription information, and a local charging policy of the network element or a combination thereof.

The IMS network charging method according to claim 7, wherein, in the case that there is no special charging identifier indicating that charging processing is not required in the charging request received from the network element, The step of the charging entity adding the special charging identifier to the charging response sent to the network element according to the charging policy includes:

Step a, identifying whether the special charging identifier exists in the charging request received from the network element; and

Step b: In the case that the special charging identifier does not exist, the charging entity determines whether a special charging identifier needs to be added to the charging response sent to the network element according to the service charging policy or the user subscription information.

The IMS network charging method according to claim 7, wherein, in the case that the special charging identifier exists in the charging response received from the charging entity, the network element The step of adding the special charging identifier to the service request sent to the subsequent network element or the service response of the preceding network element includes:

Step c, the network element checks whether the special charging identifier exists in the charging response received from the charging entity;

Step d: In the case that the special charging identifier exists, the network element adds the special charging identifier to a service request sent to a subsequent network element or a service response of a preceding network element.

The IMS network charging method according to claim 7, wherein, in the case that the special charging identifier exists in the service request or the service response, the subsequent network element and the front network element Determining whether to send a report to the corresponding charging entity according to the special charging identifier and charging policy And the step of adding the special charging identifier to the service request sent to the subsequent network element or the service response of the preceding network element, including:

Step e, the subsequent network element and the preceding network element check whether the special charging identifier exists in the service request and the service response;

Step f: If the special charging identifier exists, determine whether to send an accounting request to the corresponding charging entity according to the special charging identifier and the local charging policy, and add the special charging identifier to the subsequent sending The service request of the network element or the service response of the preceding network element.

The IMS network charging method according to claim 7, wherein the corresponding charging entity identifies that the special charging identifier exists in the charging request, according to the special charging identifier and The charging policy determines whether to perform charging processing steps, including:

Step g, the corresponding charging entity checks whether the special charging identifier exists in the charging request;

Step h: In the case that the special charging identifier exists, the corresponding charging entity determines whether to perform charging processing according to the special charging identifier and the service charging policy.

The IMS network charging method according to any one of claims 7 to 12, wherein the special charging identifier is carried by extending a header field or a parameter of a call control protocol message; or, by using an extension meter The parameter in the fee interface protocol message carries the special charging identifier.