CN106454788A - Method, system and device for realizing online charging - Google Patents
Method, system and device for realizing online charging Download PDFInfo
- Publication number
- CN106454788A CN106454788A CN201510488933.4A CN201510488933A CN106454788A CN 106454788 A CN106454788 A CN 106454788A CN 201510488933 A CN201510488933 A CN 201510488933A CN 106454788 A CN106454788 A CN 106454788A
- Authority
- CN
- China
- Prior art keywords
- server
- credit control
- dcca client
- reconnection
- dcca
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 230000002159 abnormal effect Effects 0.000 claims abstract description 17
- 230000003993 interaction Effects 0.000 claims abstract description 12
- 230000004044 response Effects 0.000 claims description 96
- 230000008569 process Effects 0.000 claims description 23
- 230000005856 abnormality Effects 0.000 claims description 11
- 230000008859 change Effects 0.000 claims description 10
- 238000011084 recovery Methods 0.000 claims description 6
- 230000000977 initiatory effect Effects 0.000 claims description 2
- 230000002688 persistence Effects 0.000 claims description 2
- 230000007246 mechanism Effects 0.000 abstract description 3
- 230000002085 persistent effect Effects 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 239000002904 solvent Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Telephonic Communication Services (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a method, a system and a device for realizing online charging. After the interaction of a DCCA terminal with a server gets abnormal, the DCCA client stores an unhandled bill locally or sends the unhandled bill to an offline charging system (OFCS), and maintains normal use of the service; and when preset reconnection conditions are met, the DCCA client is started and reconnected with the server. Through the technical scheme provided by the invention, after the interaction of the DCCA client with the server gets abnormal, the interaction between the DCCA client and the server will be restored. Thus, users are always online, and a mechanism for the server to continuously monitor the session of users is realized.
Description
Technical Field
The present invention relates to a permanent online technology for users, and particularly to a method and an apparatus for implementing online charging.
Background
In the fourth generation long term evolution (4G LTE) system, as data services are more and more widely applied, some services, such as social services, require users to be permanently online. If the user is interrupted during the data service using process, the user experience will be greatly affected. Therefore, two Failure processing modes of Failure retransmission (Support of Failure) and Failure processing (Support of Failure Handling) are defined in the 3GPP protocol 32299-c 40.
Wherein, the failed retransmission means: when the System includes a main Online Charging System (OCS) and a standby OCS, if interaction between a media Gateway (GW) and the main OCS fails, the GW needs to continue interacting with the standby OCS to maintain a session.
The failure processing means: when interaction between the GW and the master OCS fails, there is no standby OCS in the system or a processing mode after interaction between the GW and the standby OCS also fails. In the protocol RFC4006, 3 ways are defined for Credit-Control-Failure-Handling (Credit-Control-Failure-Handling). One is 0: represents termination (termination), one is 1: indicate Continuation (CONTINUE), yet another is 2: for indicating termination after RETRY (RETRY _ AND _ TERMINATE), refer to RFC4006 specifically, AND are not described here again.
Failure is inevitable no matter how stable the system is. As can be seen from the above description, if the retransmission fails and the spare OCS is not available, the service is terminated, which affects the user experience; or continue the service, the system changes to the offline charging mode, but at this time, the OCS cannot normally control and monitor the service even if it works normally, and the user may stay online for a long time due to the permanent online reason, which undoubtedly causes great trouble or loss to the operator's charging.
Besides the above link exception, if the OCS side has insufficient performance, the OCS also issues an unprocessed result code to the GW, for example: 3004-Diameter _ too _ busy, 3002-Diameter _ disable _ to _ sender, etc., which also results in the subsequent OCS not being able to control and monitor these services normally.
Disclosure of Invention
In order to solve the above technical problems, the present invention provides a method, a system and a device for implementing online charging, which can ensure that a user is permanently online and achieve a mechanism that an OCS can continuously monitor a user session.
In order to achieve the object of the present invention, the present invention provides a method for implementing online charging, which further comprises the following steps after a Diameter credit control application protocol DCCA client terminal and an online charging system server terminal are abnormal in interaction:
the DCCA client stores the unprocessed call ticket in the local or sends the unprocessed call ticket to an OFCS (off-line charging System), and continues to keep the normal use of the service;
and when the preset reconnection condition is met, the DCCA client starts to reestablish connection with the server.
Optionally, the method further comprises, before:
when an online charging user accesses, the DCCA client sends a credit control initial request to a server;
after the server side successfully authenticates the accessed online charging user, the server side returns the expanded credit control initial request response to the DCCA client side; wherein, the failure processing CCFH field in the credit control initial request response indicates to CONTINUE AND RECONNECT the CONTINUE _ AND _ RECONNECT to indicate that the DCCA client can CONTINUE the service AND retry after sensing the link failure;
or, locally configuring configuration information supporting reconnection after a session exception at the DCCA client.
Optionally, the DCCA client and the server interact with the exception and include:
during the on-line charging user service, the DCCA client triggers to send a credit control update request to a server; and the DCCA client side perceives the link abnormality; or,
during the on-line charging user service, the DCCA client triggers to send a credit control update request to a server; the server receives the credit control update request and issues a credit control update request response message to the DCCA client, wherein the carried result code is that the credit control update request response message cannot be processed; the DCCA client judges the abnormality according to the result code; or,
and the DCCA client finds out the link interruption or waits for the response timeout of the server and locally configures configuration information supporting reconnection after the session is abnormal.
Optionally, before the DCCA client triggering the sending of the credit control update request to the server, the method further includes: time threshold, traffic threshold arrival and charging condition change.
Optionally, the determining that the result code cannot be processed includes: the result code is a preset value, or 3004-busy cannot process, or 3002-undeliverable.
Optionally, the reconnection conditions include: link recovery, or a preset duration, or link congestion relief.
Optionally, the initiating, by the DCCA client, a connection reestablishment with the server includes:
the DCCA client constructs a credit control reconnection request message and sends the message to a server, and meanwhile, the message carries service charging information after self exception;
and the server deducts the fee of the user and simultaneously sends a credit control reconnection request response message carrying a quota to the DCCA client.
Optionally, the charging the user by the server, and sending a credit control reconnection request response message to the DCCA client includes:
after receiving a credit control reconnection request from a DCCA client, the server searches for a session according to a session ID:
if the session exists, the information in the request is deducted according to the own strategy, and new quota information is carried in a credit control reconnection request response according to a normal flow and returned to the DCCA client;
and if the server side finds that the session corresponding to the session ID does not exist and finds that the credit control request type is a reconnection request, the server side creates the session, performs authentication and rating processing simultaneously, and replies a credit control reconnection request response to the DCCA client side.
Optionally, the method further comprises: and the DCCA client receives a credit control reconnection request response and updates the session and the service content.
Optionally, the DCCA client is a media gateway; the server is an online charging system OCS or a policy and charging rule function PCRF.
The invention also provides a system for realizing online charging, which at least comprises a DCCA client and a server; wherein,
DCCA client end, which is used to interact with online charging system server end to be abnormal, store the unprocessed call ticket in local or send it to offline charging system OFCS, and keep the normal use of service; when the preset reconnection condition is met, the DCCA client starts to reestablish connection with the server;
and the server is used for receiving the reconnection request from the DCCA and returning a reconnection result.
Optionally, the DCCA client is further configured to: the DCCA client sends a credit control initial request to a server side; correspondingly, the server is further configured to: after successfully authenticating the accessed online charging user, returning the expanded credit control initial request response to the DCCA client; wherein, the failure processing CCFH field in the credit control initial request response indicates to CONTINUE AND RECONNECT the CONTINUE _ AND _ RECONNECT to indicate that the DCCA client can CONTINUE the service AND retry after sensing the link failure;
or, the DCCA client is configured with configuration information supporting reconnection after a session exception.
Optionally, when the DCCA client and the server interact abnormally, the DCCA client is specifically configured to:
triggering and sending a credit control updating request to a server side in the process of the online charging user service; and the DCCA client side perceives the link abnormality; or,
during the on-line charging user service, the DCCA client triggers to send a credit control update request to a server; at this time, the server is specifically configured to: receiving a credit control updating request, and issuing a credit control updating request response message to the DCCA client, wherein the credit control updating request response message carries a result code which cannot be processed; the DCCA client judges the abnormality according to the result code; or,
and after discovering the link interruption or waiting for the response timeout of the server, locally configuring configuration information supporting reconnection after the session is abnormal.
Optionally, before the DCCA client triggers sending the credit control update request to the server, the time threshold, the traffic threshold are reached, and the charging condition is changed.
Optionally, the determining that the result code cannot be processed includes: the result code is a preset value, or 3004-busy cannot process, or 3002-undeliverable.
Optionally, the reconnection conditions include: link recovery, or a preset duration, or link congestion relief.
Optionally, when the DCCA client starts to reestablish the connection with the server, the DCCA client is specifically configured to:
constructing a credit control reconnection request message and sending the message to a server, wherein the credit control reconnection request message carries service charging information after self exception;
the server is specifically configured to: and deducting the user, and simultaneously sending a credit control reconnection request response message to the DCCA client, wherein the credit control reconnection request response message carries a quota.
Optionally, the server is specifically configured to:
after receiving a credit control reconnection request from the DCCA client, searching a session according to a session ID:
if the session exists, the information in the request is deducted according to the own strategy, and new quota information is carried in a credit control reconnection request response according to a normal flow and returned to the DCCA client;
and if the server side finds that the session corresponding to the session ID does not exist and finds that the credit control request type is a reconnection request, the server side creates the session, performs authentication and rating processing simultaneously, and replies a credit control reconnection request response to the DCCA client side.
Optionally, the DCCA client is further configured to: and receiving a credit control reconnection request response, and updating the session and the service content.
Optionally, the DCCA client is a media gateway; the server is an online charging system OCS or a policy and charging rule function PCRF.
The invention also provides a device for realizing online charging, which at least comprises a continuous processing module and a reestablishment connection module, wherein,
the continuous processing module is used for storing the unprocessed call ticket in a local place or sending the unprocessed call ticket to the OFCS and continuously keeping the normal use of the service;
and the connection reestablishing module is used for starting to reestablish connection with the server side when the preset reconnection condition is met.
Optionally, the system further comprises an access processing module, configured to:
when the online charging user accesses, sending a credit control initial request to the server; at this time, the process of the present invention,
the persistence processing module is further to: and receiving an expanded credit control initial request response from the server, wherein the CCFH field of the credit control initial request response indicates continuation and reconnection so as to indicate that the service can be continued and retried after the link failure is sensed.
Optionally, the access processing module is further configured to:
triggering and sending a credit control updating request to the server side in the process of the online charging user service; when the link abnormity is sensed, the continuous processing module is informed; or,
triggering and sending a credit control updating request to the server side in the process of the online charging user service; and when a credit control update request response message from the server is received and the carried result code is that the credit control update request response message cannot be processed, the credit control update request response message is notified to the continuous processing module. Or,
after finding out the link interruption or waiting for the response timeout of the server, judging that the server is configured with the reconnection after supporting the session exception, and informing the continuous processing module.
Optionally, the reestablishment connection module is specifically configured to:
when the preset reconnection condition is met, constructing a credit control reconnection request message and sending the message to the server, wherein the credit control reconnection request message carries the service charging information after self exception;
and receiving a credit control reconnection request response message from the server, wherein the credit control reconnection request response message carries a quota.
Compared with the prior art, the technical scheme of the application comprises the steps that after the DCCA client side and the server side are abnormal in interaction, the DCCA client side stores an unprocessed ticket in a local place or sends the unprocessed ticket to an offline charging system (OFCS), and the normal use of the service is continuously kept; and when the preset reconnection condition is met, the DCCA client starts to reestablish connection with the server. By the technical scheme provided by the invention, after the interaction between the DCCA client and the server is abnormal, the interaction between the DCCA client and the server can be restored again, so that the user is ensured to be permanently online, and a mechanism for the server to continuously monitor the user session is realized.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a flow chart of a method for implementing online charging according to the present invention;
FIG. 2 is a schematic diagram of the structure of the device for implementing online charging according to the present invention;
FIG. 3 is a flowchart illustrating a first embodiment of implementing online charging according to the present invention;
FIG. 4 is a flowchart illustrating a second embodiment of implementing online charging according to the present invention;
FIG. 5 is a flowchart illustrating a third embodiment of implementing online charging according to the present invention;
fig. 6 is a flowchart illustrating a fourth embodiment of implementing online charging according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.
Fig. 1 is a flowchart of a method for implementing online charging according to the present invention, and as shown in fig. 1, after a Diameter credit control application protocol (DCCA) client interacts abnormally with a server, the method includes:
step 100: the DCCA client stores the unprocessed call ticket in the local or sends the unprocessed call ticket to an offline charging system (OFCS), and keeps normal service use.
The method also comprises the following steps:
when an online charging user accesses, a DCCA client, such as GW, sends a Credit Control initial Request (CCR, Credit-Control-Request) to a service end, such as OCS; after the OCS successfully authenticates the online charging user, the OCS returns an extended Credit Control initial request response to the GW, where a Credit Control Failure Handling (CCFH) field of the Credit Control initial request response may be set to 240, which indicates to CONTINUE AND RECONNECT (CONTINUE _ AND _ RECONNECT) to indicate that the GW may CONTINUE the service AND retry after sensing the link Failure. That is, the CCFH field being 240 means that, when the GW fails to interact with the active OCS, there is no standby OCS in the system, or the GW fails to interact with the standby OCS, the GW should keep the service being used normally, and reconnect to the OCS at an appropriate time, for example, when a preset reconnection condition is met. It should be noted that the CCFH field may be set to other values such as 241, as long as the CCFH field is used to indicate that the GW can continue to service and retry after sensing the link failure.
Or, the DCCA client, such as GW, is locally configured with configuration information supporting reconnection after a session exception.
It should be noted that, the extended credit control request response of the present invention may further include: and other fields except the CCFH field, such as automatic deduction Failure processing (Direct-locating-Failure-Handling AVP), trigger Type (Triger-Type AVP) and the like, or other numerical values of the CCFH field, so as to achieve the effect of identifying the reconnection needing to be supported.
The DCCA client and server interaction exception may include, but is not limited to:
in the process of online charging user service, a DCCA client, such as GW, triggers to send a credit control update request to a server, such as OCS, due to the reasons of time threshold, flow threshold arrival, charging condition change and the like; the GW senses link abnormality, for example, due to link interruption with the OCS or link congestion, and waits for a credit control update request response timeout of the OCS or other reasons, but at this time, the GW cannot know whether the OCS has already processed, so step 100 is performed.
Or,
in the process of online charging user service, a DCCA client, such as GW, triggers to send a credit control update request to a server, such as OCS, due to the reasons of time threshold, flow threshold arrival, charging condition change and the like; the OCS receives a credit control update request, for example, due to insufficient signaling congestion performance at the OCS side or background system maintenance and the like, the OCS cannot process the CCR request temporarily, and the OCS issues a credit control update request response message to the GW, wherein a result code is 3004; GW determines that OCS fails to deduct the fee according to result code 3004, and proceeds to step 100. Or, the OCS issues result codes that cannot be processed, such as 3004-busy cannot be processed (Diameter _ too _ busy), 3002-cause value that cannot be delivered (Diameter _ unable _ to _ delivery), to the GW due to reasons such as insufficient performance at the OCS side, and these scenarios are also applicable to the present invention.
Or,
after the DCCA client, such as GW, finds that the link is interrupted or waits for the response timeout of the service end, such as OCS, it determines that GW is locally configured with a reconnection after supporting the session exception, and then step 100 is performed.
Step 101: and when the preset reconnection condition is met, the DCCA client starts to reestablish connection with the server.
In this step, the reconnection conditions include, but are not limited to: link recovery, preset duration or link congestion relief, etc.
The step of the DCCA client starting and the server reestablishing the connection comprises the following steps:
a DCCA client, such as GW, constructs a credit control reconnection request message and sends the message to a server, such as OCS, and simultaneously carries service charging information after self-exception, namely the service used by an online charging user and corresponding information such as flow, time and the like;
the OCS deducts the fee of the user and simultaneously sends a credit control reconnection request response message to the GW, wherein the credit control reconnection request response message carries related information such as quota and the like.
After receiving the credit control reconnection request from the GW, the OCS searches for a Session according to a Session ID (Session-ID):
if the session exists, the information in the request is deducted according to the strategy of the OCS, and new quota information is carried in the credit control reconnection request response according to the normal flow and returned to the GW;
if the OCS finds that the Session corresponding to the Session-Id does not exist and finds that the credit control request type is a reconnection request, the OCS creates the Session, performs authentication and rating processing simultaneously, and replies a credit control reconnection request response to the GW.
Further, the method of the invention also comprises the following steps:
the DCCA client, such as GW, receives the credit control reconnection request response, and updates the session and the service content.
In the present invention, the DCCA client may be GW, and the server may be OCS, Policy and Charging Rules Function (PCRF), etc.
Correspondingly, the invention also provides a system for realizing online charging, which at least comprises a DCCA client and a server; wherein,
DCCA client end, which is used to interact with online charging system server end to be abnormal, store the unprocessed call ticket in local or send it to offline charging system OFCS, and keep the normal use of service; when the preset reconnection condition is met, the DCCA client starts to reestablish connection with the server;
and the server is used for receiving the reconnection request from the DCCA and returning a reconnection result.
Further, the air conditioner is provided with a fan,
the DCCA client is also used for: the DCCA client sends a credit control initial request to a server side; correspondingly, the server is also used for: after successfully authenticating the accessed online charging user, returning the expanded credit control initial request response to the DCCA client; wherein, the failure processing CCFH field in the credit control initial request response indicates to CONTINUE AND RECONNECT the CONTINUE _ AND _ RECONNECT to indicate that the DCCA client can CONTINUE the service AND retry after sensing the link failure;
or the DCCA client is configured with configuration information for supporting reconnection after the session exception.
In particular, the amount of the solvent to be used,
when the DCCA client and the server are abnormal, the DCCA client is specifically configured to:
triggering and sending a credit control updating request to a server side in the process of the online charging user service; and the DCCA client side perceives the link abnormality; or,
during the on-line charging user service, the DCCA client triggers to send a credit control update request to a server; at this time, the server is specifically configured to: receiving a credit control updating request, and issuing a credit control updating request response message to the DCCA client, wherein the credit control updating request response message carries a result code which cannot be processed; the DCCA client judges the abnormality according to the result code; or,
and after discovering the link interruption or waiting for the response timeout of the server, locally configuring configuration information supporting reconnection after the session is abnormal.
Before the DCCA client triggers the sending of the credit control update request to the server, the time threshold, the flow threshold are reached and the charging condition is changed.
Wherein, the result code is that the processing can not be processed comprises: the result code is a preset value, or 3004-busy cannot process, or 3002-undeliverable.
Wherein the reconnection conditions include: link recovery, or a preset duration, or link congestion relief.
When the DCCA client starts to reestablish the connection with the server, the DCCA client is specifically configured to:
constructing a credit control reconnection request message and sending the message to a server, wherein the credit control reconnection request message carries service charging information after self exception; at this time, the process of the present invention,
the server is specifically configured to: and deducting the user, and simultaneously sending a credit control reconnection request response message to the DCCA client, wherein the credit control reconnection request response message carries a quota. Wherein, the server is specifically configured to:
after receiving a credit control reconnection request from the DCCA client, searching a session according to a session ID:
if the session exists, the information in the request is deducted according to the own strategy, and new quota information is carried in a credit control reconnection request response according to a normal flow and returned to the DCCA client;
and if the server side finds that the session corresponding to the session ID does not exist and finds that the credit control request type is a reconnection request, the server side creates the session, performs authentication and rating processing simultaneously, and replies a credit control reconnection request response to the DCCA client side.
Further, the air conditioner is provided with a fan,
the DCCA client is also used for: and receiving a credit control reconnection request response, and updating the session and the service content.
The DCCA client is a media gateway; the service end is OCS or PCRF.
Fig. 2 is a schematic structural diagram of a device for implementing online charging according to the present invention, as shown in fig. 2, the device at least includes a persistent processing module and a connection reestablishment module, wherein,
the continuous processing module is used for storing the unprocessed call ticket in a local place or sending the unprocessed call ticket to an offline charging system (OFCS) and continuously keeping the normal use of the service;
and the connection reestablishing module is used for starting to reestablish connection with the server side when the preset reconnection condition is met.
The device of the invention also comprises an access processing module used for:
when an online charging user accesses, sending the CCR to a service end such as an OCS; at this time, the persistent processing module receives an extended credit control initial request response from the OCS, where the CCFH field of the credit control initial request response is 240, which indicates continuation AND reconnection (CONTINUE _ AND _ RECONNECT) to indicate that the service can be continued AND retried after sensing the link failure.
The access processing module is further configured to:
in the process of online charging user service, due to the reasons of time threshold, flow threshold arrival, charging condition change and the like, a credit control update request is triggered to be sent to a service terminal such as an OCS; and upon sensing a link failure, such as a link interruption with the OCS or a link congestion, the GW waits for a credit control update request response timeout of the OCS or other reasons to notify the persistent processing module.
Or,
in the process of online charging user service, due to the reasons of time threshold, flow threshold arrival, charging condition change and the like, a credit control update request is triggered to be sent to a service terminal such as an OCS; and receiving a credit control update request response message from the OCS, wherein the credit control update request response message carries a result code of 3004 or a result code which cannot be processed, such as a cause value of 3004-Diameter _ too _ busy or 3002-Diameter _ disable _ to _ delivery, and the like, and notifying the persistent processing module.
Or,
after finding out the link interruption or waiting for the response timeout of the service end such as the OCS, judging that the self is configured with the reconnection after supporting the session exception, and informing the continuous processing module.
Wherein,
the reestablishment connection module is specifically configured to:
when the preset reconnection condition is met, constructing a credit control reconnection request message and sending the message to a service terminal such as an OCS (online charging system), and simultaneously carrying abnormal service charging information, namely the service used by an online charging user and corresponding information such as flow and time;
and receiving a credit control reconnection request response message from the OCS, wherein the credit control reconnection request response message carries quota and other related information, and updating the session and service content.
The device of the invention can be used as an independent entity device and can also be arranged in GW.
The process of the present invention is described in detail below with reference to specific examples. In the following embodiments, a DCCA client is used as GW, and a server is used as OCS for example.
It should be noted that whether the OCS has a master OCS and whether the OCS supports failure retransmission (FailOver) is not limited to the protection scope of the present invention, and for simplicity, the following embodiment only illustrates the OCS without a master OCS as an example. In addition, the CCFH may be issued from the OCS or configured on the GW, and the flow is basically the same, and in the following embodiments, only the case where the CCFH is issued from the OCS is taken as an example for description.
Fig. 3 is a flowchart illustrating a first embodiment of implementing online charging according to the present invention, where in the first embodiment, CCFH is control _ AND _ receiving, AND a session exists on an OCS during reconnection, as shown in fig. 3, the method includes the following steps:
step 300: and accessing an online charging user.
Step 301: the GW sends a credit control initial request to the OCS.
The specific implementation of step 300 and step 301 belongs to the well-known technology of those skilled in the art, and will not be described herein.
Step 302: after the OCS successfully authenticates the user, it sends a credit control initial request response to the GW, in this embodiment, the CCFH in the credit control initial request response is 240, so as to indicate that the GW can continue the service and retry after sensing the link failure.
Step 303: it is assumed that, during the user service, the GW triggers a credit control update request due to the time threshold, the arrival of the traffic threshold, the change of the charging condition, and the like, that is, the GW sends the credit control update request to the OCS.
Step 304: the GW senses link failure, such as a link interruption with the OCS, link congestion, or other reasons, which cause the GW to wait for the OCS credit control update request response to time out.
Step 305: since the GW cannot know whether the OCS has already processed at this time, the GW stores the partial ticket (i.e. the charging information such as the traffic used by the user in the period from step 302 to step 303) locally or sends the partial ticket to the OFCS, and at the same time, the service is continuously kept from being normally used because the CCFH is 240.
Step 306: at a certain trigger point, for example, a preset connection reestablishment condition, such as a timing trigger or a trigger of sensing a link state change, the GW sends a credit control reconnection request to the OCS, where the credit control request type is a request indicated as connection reestablishment, such as 240, and carries service charging information in the time period after the GW senses an anomaly.
Step 307: the OCS deducts the fee of the user and simultaneously sends a credit control reconnection request response message to the GW, wherein the credit control reconnection request response message carries related information such as quota and the like.
Fig. 4 is a flowchart illustrating a second embodiment of implementing online charging according to the present invention, where in the second embodiment, it is assumed that a session does not exist on an OCS when a connection is reestablished. As shown in fig. 4, the method comprises the following steps:
the specific implementation of steps 400 to 406 is completely the same as that of steps 300 to 306, and is not described herein again.
Step 407: in this embodiment, it is assumed that the OCS fails to find the session according to the session ID, but if the OCS finds that the credit control request type is 240, the OCS recreates the session and authenticates the user.
Step 408: and the OCS sends a credit control reconnection request response to the GW, wherein the credit control request type is 240, and quota information of the service is carried.
Fig. 5 is a flowchart illustrating a third embodiment of implementing online charging according to the present invention, in the third embodiment, an OCS returns busy AND cannot be processed (3004-Diameter _ too _ busy), CCFH is CONTINUE _ AND _ recover, AND a session exists on the OCS during reconnection. As shown in fig. 5, the method comprises the following steps:
step 500: and accessing an online charging user.
Step 501: the GW sends a credit control initial request to the OCS.
Step 502: after the OCS successfully authenticates the user, it sends a credit control initial request response to the GW, where CCFH is 240, to indicate that the GW can continue the service and retry after sensing the link failure.
Step 503: it is assumed that, during the user service, the GW triggers a credit control update request due to the time threshold, the arrival of the traffic threshold, the change of the charging condition, and the like, that is, the GW sends the credit control update request to the OCS.
Step 504: in this embodiment, assuming that the OCS cannot process the CCR request temporarily due to insufficient signaling congestion performance at the OCS side or background system maintenance, the OCS issues a credit control update request response message to the GW, where the result code is 3004.
Step 505: GW determines that OCS has failed to deduct the fee according to result code 3004, stores the partial ticket (i.e. charging information such as the traffic used by the user in the period from step 502 to step 503) locally or sends the partial ticket to OFCS, and at the same time, according to CCFH of 240, continues to keep normal service usage unaffected.
Step 506: at a certain trigger point, such as a preset timing trigger, the GW sends a credit control reconnection request message to the OCS, where the message carries the current service and service usage information.
Step 507: and the OCS returns a credit control reconnection request response message to the GW, and if congestion or background operation maintenance is relieved, the user is subjected to fee deduction and pricing approval, and the subsequent flow is normal.
Fig. 6 is a flowchart illustrating a fourth embodiment of implementing online charging according to the present invention, in the fourth embodiment, an OCS does not carry a CCFH AVP, a GW locally configures and supports reconnection after a session is abnormal, and a session exists on the OCS during reconnection. As shown in fig. 6, the method comprises the following steps:
the flow of the fourth embodiment shown in fig. 6 is substantially the same as the first embodiment shown in fig. 3, except that: in step 602, the OCS does not carry CCFHAVP in the credit control initial request response, and in step 604, after the GW finds that the link is interrupted or waits for the OCS response timeout, the GW starts a subsequent reconnection procedure by determining that the GW is locally configured with a support session exception and then reconnects.
The above description is only a preferred example of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (24)
1. A method for realizing online charging is characterized in that after a Diameter credit control application protocol DCCA client terminal and a server terminal of an online charging system are abnormal in interaction, the method further comprises the following steps:
the DCCA client stores the unprocessed call ticket in the local or sends the unprocessed call ticket to an OFCS (off-line charging System), and continues to keep the normal use of the service;
and when the preset reconnection condition is met, the DCCA client starts to reestablish connection with the server.
2. The method of claim 1, further comprising, prior to the method:
when an online charging user accesses, the DCCA client sends a credit control initial request to a server;
after the server side successfully authenticates the accessed online charging user, the server side returns the expanded credit control initial request response to the DCCA client side; wherein, the failure processing CCFH field in the credit control initial request response indicates to CONTINUE AND RECONNECT the CONTINUE _ AND _ RECONNECT to indicate that the DCCA client can CONTINUE the service AND retry after sensing the link failure;
or, locally configuring configuration information supporting reconnection after a session exception at the DCCA client.
3. The method of claim 2, wherein the DCCA client interacting with the server for the exception comprises:
during the on-line charging user service, the DCCA client triggers to send a credit control update request to a server; and the DCCA client side perceives the link abnormality; or,
during the on-line charging user service, the DCCA client triggers to send a credit control update request to a server; the server receives the credit control update request and issues a credit control update request response message to the DCCA client, wherein the carried result code is that the credit control update request response message cannot be processed; the DCCA client judges the abnormality according to the result code; or,
and the DCCA client finds out the link interruption or waits for the response timeout of the server and locally configures configuration information supporting reconnection after the session is abnormal.
4. The method of claim 3, wherein before the DCCA client triggering the sending of the credit control update request to the server, further comprising: time threshold, traffic threshold arrival and charging condition change.
5. The method of claim 3, wherein the result code being non-processable comprises: the result code is a preset value, or 3004-busy cannot process, or 3002-undeliverable.
6. The method of claim 2, wherein the reconnection condition comprises: link recovery, or a preset duration, or link congestion relief.
7. The method of claim 2, wherein the DCCA client initiating a re-establishment of a connection with a server comprises:
the DCCA client constructs a credit control reconnection request message and sends the message to a server, and meanwhile, the message carries service charging information after self exception;
and the server deducts the fee of the user and simultaneously sends a credit control reconnection request response message carrying a quota to the DCCA client.
8. The method of claim 7, wherein the server deducting a fee from the user and sending a credit control reconnection request response message to the DCCA client comprises:
after receiving a credit control reconnection request from a DCCA client, the server searches for a session according to a session ID:
if the session exists, the information in the request is deducted according to the own strategy, and new quota information is carried in a credit control reconnection request response according to a normal flow and returned to the DCCA client;
and if the server side finds that the session corresponding to the session ID does not exist and finds that the credit control request type is a reconnection request, the server side creates the session, performs authentication and rating processing simultaneously, and replies a credit control reconnection request response to the DCCA client side.
9. The method according to any one of claims 1 to 8, further comprising: and the DCCA client receives a credit control reconnection request response and updates the session and the service content.
10. The method according to any one of claims 1 to 8, wherein the DCCA client is a media gateway; the server is an online charging system OCS or a policy and charging rule function PCRF.
11. A system for realizing online charging is characterized by at least comprising a DCCA client and a server; wherein,
DCCA client end, which is used to interact with online charging system server end to be abnormal, store the unprocessed call ticket in local or send it to offline charging system OFCS, and keep the normal use of service; when the preset reconnection condition is met, the DCCA client starts to reestablish connection with the server;
and the server is used for receiving the reconnection request from the DCCA and returning a reconnection result.
12. The system of claim 11, wherein the DCCA client is further configured to: the DCCA client sends a credit control initial request to a server side; correspondingly, the server is further configured to: after successfully authenticating the accessed online charging user, returning the expanded credit control initial request response to the DCCA client; wherein, the failure processing CCFH field in the credit control initial request response indicates to CONTINUE AND RECONNECT the CONTINUE _ AND _ RECONNECT to indicate that the DCCA client can CONTINUE the service AND retry after sensing the link failure;
or, the DCCA client is configured with configuration information supporting reconnection after a session exception.
13. The system of claim 12, wherein when the DCCA client interacts abnormally with the server, the DCCA client is specifically configured to:
triggering and sending a credit control updating request to a server side in the process of the online charging user service; and the DCCA client side perceives the link abnormality; or,
during the on-line charging user service, the DCCA client triggers to send a credit control update request to a server; at this time, the server is specifically configured to: receiving a credit control updating request, and issuing a credit control updating request response message to the DCCA client, wherein the credit control updating request response message carries a result code which cannot be processed; the DCCA client judges the abnormality according to the result code; or,
and after discovering the link interruption or waiting for the response timeout of the server, locally configuring configuration information supporting reconnection after the session is abnormal.
14. The system of claim 13 wherein the time threshold, the traffic threshold, and the charging condition change before the DCCA client triggers the sending of the credit control update request to the server.
15. The system of claim 13, wherein the result code being non-processable comprises: the result code is a preset value, or 3004-busy cannot process, or 3002-undeliverable.
16. The system of claim 12, wherein the reconnection condition comprises: link recovery, or a preset duration, or link congestion relief.
17. The system of claim 12, wherein when the DCCA client initiates reestablishment of the connection with the server, the DCCA client is specifically configured to:
constructing a credit control reconnection request message and sending the message to a server, wherein the credit control reconnection request message carries service charging information after self exception;
the server is specifically configured to: and deducting the user, and simultaneously sending a credit control reconnection request response message to the DCCA client, wherein the credit control reconnection request response message carries a quota.
18. The system of claim 17, wherein the server is specifically configured to:
after receiving a credit control reconnection request from the DCCA client, searching a session according to a session ID:
if the session exists, the information in the request is deducted according to the own strategy, and new quota information is carried in a credit control reconnection request response according to a normal flow and returned to the DCCA client;
and if the server side finds that the session corresponding to the session ID does not exist and finds that the credit control request type is a reconnection request, the server side creates the session, performs authentication and rating processing simultaneously, and replies a credit control reconnection request response to the DCCA client side.
19. The system according to any of claims 11-18, wherein the DCCA client is further configured to: and receiving a credit control reconnection request response, and updating the session and the service content.
20. The system according to any one of claims 11 to 18, wherein the DCCA client is a media gateway; the server is an online charging system OCS or a policy and charging rule function PCRF.
21. The device for realizing online charging is characterized by at least comprising a continuous processing module and a connection reestablishing module, wherein,
the continuous processing module is used for storing the unprocessed call ticket in a local place or sending the unprocessed call ticket to the OFCS and continuously keeping the normal use of the service;
and the connection reestablishing module is used for starting to reestablish connection with the server side when the preset reconnection condition is met.
22. The apparatus of claim 21, further comprising an access processing module configured to:
when the online charging user accesses, sending a credit control initial request to the server; at this time, the process of the present invention,
the persistence processing module is further to: and receiving an expanded credit control initial request response from the server, wherein the CCFH field of the credit control initial request response indicates continuation and reconnection so as to indicate that the service can be continued and retried after the link failure is sensed.
23. The apparatus of claim 22, wherein the access processing module is further configured to:
triggering and sending a credit control updating request to the server side in the process of the online charging user service; when the link abnormity is sensed, the continuous processing module is informed; or,
triggering and sending a credit control updating request to the server side in the process of the online charging user service; and receiving a credit control update request response message from the server, and notifying the continuous processing module when a result code carried by the credit control update request response message is that the credit control update request response message cannot be processed; or,
after finding out the link interruption or waiting for the response timeout of the server, judging that the server is configured with the reconnection after supporting the session exception, and informing the continuous processing module.
24. The apparatus of claim 22, wherein the reestablishment connection module is specifically configured to:
when the preset reconnection condition is met, constructing a credit control reconnection request message and sending the message to the server, wherein the credit control reconnection request message carries the service charging information after self exception;
and receiving a credit control reconnection request response message from the server, wherein the credit control reconnection request response message carries a quota.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510488933.4A CN106454788A (en) | 2015-08-11 | 2015-08-11 | Method, system and device for realizing online charging |
| PCT/CN2016/079592 WO2016180177A1 (en) | 2015-08-11 | 2016-04-18 | Method, system and device for realizing online charging |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510488933.4A CN106454788A (en) | 2015-08-11 | 2015-08-11 | Method, system and device for realizing online charging |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106454788A true CN106454788A (en) | 2017-02-22 |
Family
ID=57247748
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510488933.4A Pending CN106454788A (en) | 2015-08-11 | 2015-08-11 | Method, system and device for realizing online charging |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN106454788A (en) |
| WO (1) | WO2016180177A1 (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111555912A (en) * | 2020-04-24 | 2020-08-18 | 北京思特奇信息技术股份有限公司 | Method, device and computer storage medium for solving internet speed |
| CN112087310A (en) * | 2019-06-14 | 2020-12-15 | 中国电信股份有限公司 | Charging processing method, device and computer readable storage medium |
| CN112243204A (en) * | 2019-07-19 | 2021-01-19 | 华为技术有限公司 | Method, system and related equipment for processing charging |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101022348A (en) * | 2007-02-07 | 2007-08-22 | 华为技术有限公司 | Method, system and equipment for realizing on-line charge metering |
| CN101183953A (en) * | 2007-12-13 | 2008-05-21 | 中国移动通信集团广东有限公司 | Added charging method for online charging system |
| US20110202647A1 (en) * | 2009-08-10 | 2011-08-18 | Haipeng Jin | Method and Apparatus for Handling Policy and Charging Control Rule or Quality of Service Rule Modification Failures |
| CN102487323A (en) * | 2010-12-02 | 2012-06-06 | 中兴通讯股份有限公司 | Online charging service processing method, gateway and system |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8549116B2 (en) * | 2010-05-05 | 2013-10-01 | Alcatel Lucent | PCRF triggered rules cleanup |
| CN102291242A (en) * | 2011-08-25 | 2011-12-21 | 深圳市同洲视讯传媒有限公司 | Charging method and device |
| CN103702306A (en) * | 2012-09-27 | 2014-04-02 | 阿尔卡特朗讯 | Method and equipment for charging user equipment during charging failure of OCS (online charging system) |
-
2015
- 2015-08-11 CN CN201510488933.4A patent/CN106454788A/en active Pending
-
2016
- 2016-04-18 WO PCT/CN2016/079592 patent/WO2016180177A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101022348A (en) * | 2007-02-07 | 2007-08-22 | 华为技术有限公司 | Method, system and equipment for realizing on-line charge metering |
| CN101183953A (en) * | 2007-12-13 | 2008-05-21 | 中国移动通信集团广东有限公司 | Added charging method for online charging system |
| US20110202647A1 (en) * | 2009-08-10 | 2011-08-18 | Haipeng Jin | Method and Apparatus for Handling Policy and Charging Control Rule or Quality of Service Rule Modification Failures |
| CN102487323A (en) * | 2010-12-02 | 2012-06-06 | 中兴通讯股份有限公司 | Online charging service processing method, gateway and system |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112087310A (en) * | 2019-06-14 | 2020-12-15 | 中国电信股份有限公司 | Charging processing method, device and computer readable storage medium |
| CN112087310B (en) * | 2019-06-14 | 2023-06-02 | 中国电信股份有限公司 | Charging processing method, device and computer readable storage medium |
| CN112243204A (en) * | 2019-07-19 | 2021-01-19 | 华为技术有限公司 | Method, system and related equipment for processing charging |
| CN112243204B (en) * | 2019-07-19 | 2022-04-26 | 华为技术有限公司 | Method, system and related equipment for processing charging |
| US12068868B2 (en) | 2019-07-19 | 2024-08-20 | Huawei Technologies Co., Ltd. | Charging processing method and system, and related device |
| CN111555912A (en) * | 2020-04-24 | 2020-08-18 | 北京思特奇信息技术股份有限公司 | Method, device and computer storage medium for solving internet speed |
| CN111555912B (en) * | 2020-04-24 | 2023-04-07 | 北京思特奇信息技术股份有限公司 | Method, device and computer storage medium for solving internet speed |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2016180177A1 (en) | 2016-11-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2775755B1 (en) | Acquiring an online state of a terminal | |
| EP2664101B1 (en) | Recovery of a system for policy control and charging, said system having a redundancy of policy and charging rules function | |
| CN106452803B (en) | Method, system and device for realizing online charging | |
| EP2775661B1 (en) | Fault detection method and gateway | |
| CN106454788A (en) | Method, system and device for realizing online charging | |
| CN110546986B (en) | Methods, systems, and computer readable media for message flooding mitigation during access node-gateway (AN-GW) unavailability and after AN-GW recovery | |
| CN109040295A (en) | Determination method and device, terminal and the storage medium of abnormal broken line | |
| EP3024210B1 (en) | Method and apparatus for providing service in user equipment of mobile communication system | |
| KR20190038167A (en) | Method and apparatus for managing a pdn connection in a wireless communication system | |
| EP3849232B1 (en) | Method and device for processing gx session exception | |
| US10701552B2 (en) | Enhanced dynamic feature support in wireless diameter-based networks | |
| CN106067857B (en) | Method and device for preventing user from being forced off-line | |
| EP3086579B1 (en) | Switching methods and devices for charging system | |
| US20170026524A1 (en) | Charging method and apparatus | |
| CN101133657A (en) | Method and apparatus to facilitate foreign agent actions with respect to home agent nonresponsiveness | |
| CN110121215B (en) | Data connection establishment method and device of 5G terminal and 5G terminal | |
| CN112804277A (en) | Load control information sending method, device, equipment and storage medium | |
| WO2016180227A1 (en) | Recovery method, device and system for credit control session | |
| CN113438613B (en) | Method, device, system and medium for paying by abnormal user | |
| CN111371569B (en) | Online charging method, online charging device, computer equipment and storage medium | |
| CN102883308B (en) | A kind of Origin-State-Id AVP sending method based on Diameter and device | |
| WO2016150143A1 (en) | Cats charging method, and charging-message request sending method and apparatus | |
| EP3433975B1 (en) | Real-time co-ordinated fulfillment of refill transactions of a user account in a communication system | |
| CN117835287A (en) | Network function management method and device, electronic equipment and storage medium | |
| CN115019442A (en) | Gas station information processing method and device and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20170222 |
|
| WD01 | Invention patent application deemed withdrawn after publication |