CN106454788A - Method, system and device for realizing online charging - Google Patents

Method, system and device for realizing online charging Download PDF

Info

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
service
credit control
diameter credit
dcca client
request
Prior art date
Application number
CN201510488933.4A
Other languages
Chinese (zh)
Inventor
杨明贵
林凯
刘昱婷
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to CN201510488933.4A priority Critical patent/CN106454788A/en
Publication of CN106454788A publication Critical patent/CN106454788A/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Metering, charging or billing arrangements specially adapted for data wireline or wireless communications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24Accounting or billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/04Arrangements for maintaining operational condition

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

A kind of method, system and device realizing online charging

Technical field

The present invention relates to the permanent online technique of user, espespecially a kind of method and device realizing online charging.

Background technology

In forth generation Long Term Evolution (4G LTE) system, the application with data service is more and more extensive, Some business social activity business etc., require that user is forever online.If the user while using data service During be interrupted, can strong influence Consumer's Experience.For this defined in 3GPP agreement 32299-c40 Failure retransmits (Support of Failover) and failure handling (Support of Failure Handling) two Plant failure handling mode.

Wherein, unsuccessfully retransmit and refer to:Include primary Online Charging System (OCS, Online in systems Charging System) and during standby OCS, if WMG (GW) interacts mistake with primary OCS Lose, then need to continue and standby OCS interaction is to keep session.

Failure handling refers to:When GW interacts unsuccessfully with primary OCS, do not have in system standby OCS or Person interacts the processing mode after also failing with standby OCS.Agreement RFC4006 is lost to diameter credit control Lose process (Credit-Control-Failure-Handling) and define 3 kinds of modes.One kind is 0:Represent eventually Only (TERMINATE), one kind is 1:Represent and continue (CONTINUE), also one kind is 2: Represent and terminate (RETRY_AND_TERMINATE) after retrying, specifically can be found in RFC4006, this In repeat no more.

No matter how stable system is, and failure is all unavoidable.From the above description, it will be seen that If also fail or there is no standby OCS after unsuccessfully retransmitting, or terminating business, the body of impact user Test;Continuation business, system switchs to offline charging mode, but now, even if the follow-up normal work of OCS Make, also these business normally cannot be controlled and monitor, and due to forever online due to, user Possible consistently online for a long time, so, undoubtedly can give the charging of operator bring very big puzzlement or Loss.

Except above-mentioned link extremely in addition to, if the reason such as OCS side performance deficiency, OCS also can be under GW Send out the result code that cannot process, such as:3004-Diameter_too_busy、3002- The reason Diameter_unable_to_deliver value etc., now equally also resulting in follow-up OCS cannot be right These business are normally controlled and are monitored.

Content of the invention

In order to solve above-mentioned technical problem, the present invention provide a kind of method realizing online charging, system and Device, ensure that user is forever online, and reaches the mechanism that OCS can continue to monitor user conversation.

In order to reach the object of the invention, the invention provides a kind of method realizing online charging, Diameter diameter credit control application protocol DCCA client interacts abnormal with Online Charging System service end Afterwards, also include:

Untreated ticket is stored in local or is sent to off-line accounting system by DCCA client OFCS, and continue holding business and normally use;

Meet pre-set when reconnecting condition, DCCA client terminal start-up and service end re-establish Connect.

Alternatively, also include before the method:

When online charging user accesses, described DCCA client sends diameter credit control to service end and initially please Ask;

Described service end carries out to the online charging user accessing authenticating after success, to described DCCA client End returns the diameter credit control initial request response after extension;Wherein, in the response of diameter credit control initial request Failure handling CCFH field represents and continues and reconnect CONTINUE_AND_RECONNECT, with Indicate that described DCCA client can continue business after perceiving link failure and retry;

Or, described DCCA client locally configured have support session exception after reconnect configuration letter Breath.

Alternatively, described DCCA client interacts abnormal inclusion with service end:

In described online charging customer service is carried out, described DCCA client triggers and sends to service end Diameter credit control updates request;And described DCCA client to perceive link abnormal;Or,

In described online charging customer service is carried out, described DCCA client triggers and sends to service end Diameter credit control updates request;Described service end receives diameter credit control and updates request, and to described DCCA visitor Family end issues diameter credit control and updates request response, and wherein carrying result code is to process;Described DCCA client, according to result code, judges exception;Or,

After described DCCA client finds link down or waits service end response timeout, and itself is originally Be configured with and support the configuration information that reconnects after session exception.

Alternatively, described DCCA client triggers to send before diameter credit control updates request to service end and goes back Including:Time threshold, traffic threshold reach and billing conditions change.

Alternatively, described result code be cannot process including:Described result code be the value pre-setting or 3004- hurries and cannot process or 3002- is undeliverable.

Alternatively, the described condition that reconnects includes:Link-recovery or preset duration or link congestion solution Remove.

Alternatively, described DCCA client terminal start-up re-establish with service end be connected including:

Described DCCA client construction diameter credit control reconnects request message and is sent to service end, simultaneously Carry the service charging information from after exception;

Described service end is deducted fees to user, sends diameter credit control weight to described DCCA client simultaneously Connection request response message, wherein carries quota.

Alternatively, described service end is deducted fees to user, sends letter to described DCCA client simultaneously Reconnect request response with control to include:

The diameter credit control that described service end receives from DCCA client reconnects after request, according to session ID searches session:

If this session exists, the strategy according to itself is deducted fees to the information in this request, and presses Normal flow by new quota information carry diameter credit control reconnect return in request response described DCCA client;

The corresponding session if described service end finds this session id does not exist, and finds diameter credit control simultaneously Request type is attached most importance to connection request, then create session, is authenticated simultaneously and wholesale price is processed, and to institute State DCCA client reply diameter credit control and reconnect request response.

Alternatively, the method also includes:Described DCCA client receives diameter credit control and reconnects request sound Should, more new session and business tine.

Alternatively, described DCCA client is WMG;Described service end is Online Charging System OCS or strategy and charging rule functions PCRF.

Present invention also offers a kind of system realizing online charging, at least include DCCA client, clothes Business end;Wherein,

DCCA client is abnormal for interacting with Online Charging System service end, by untreated ticket It is stored in local or is sent to off-line accounting system OFCS, and continue holding business and normally use;? Meet pre-set when reconnecting condition, DCCA client terminal start-up is re-established with service end and is connected;

Service end, for receiving the request of the reconnect from DCCA, returns and reconnects result.

Alternatively, described DCCA client is additionally operable to:Online charging user accesses, described DCCA visitor Family end sends diameter credit control initial request to service end;Correspondingly, described service end is additionally operable to:To access Online charging user carry out authenticate success after, to described DCCA client return extension after credit control Initial request response processed;Wherein, the failure handling CCFH field list in the response of diameter credit control initial request Show and continue and reconnect CONTINUE_AND_RECONNECT, to indicate described DCCA client End can be continued business after perceiving link failure and be retried;

Or, in described DCCA client, it is configured with the configuration information reconnecting after supporting session exception.

Alternatively, when described DCCA client interacts exception with service end, described DCCA client Specifically for:

In described online charging customer service is carried out, trigger and send diameter credit control renewal request to service end; And described DCCA client to perceive link abnormal;Or,

In described online charging customer service is carried out, described DCCA client triggers and sends to service end Diameter credit control updates request;Now, described service end specifically for:Receive diameter credit control and update request, And issue diameter credit control renewal request response to described DCCA client, wherein carrying result code is Cannot process;Described DCCA client, according to result code, judges exception;Or,

After finding link down or waiting service end response timeout, and own local is configured with support session The configuration information reconnecting after exception.

Alternatively, before described DCCA client triggers and sends diameter credit control renewal request to service end, Time threshold, traffic threshold reach and billing conditions change.

Alternatively, described result code be cannot process including:Described result code be the value pre-setting or 3004- hurries and cannot process or 3002- is undeliverable.

Alternatively, the described condition that reconnects includes:Link-recovery or preset duration or link congestion solution Remove.

Alternatively, when described DCCA client terminal start-up is re-established with service end and is connected, described DCCA Client specifically for:

Construction diameter credit control reconnects request message and is sent to service end, carries from after exception simultaneously Service charging information;

Described service end specifically for:User is deducted fees, sends to described DCCA client simultaneously Diameter credit control reconnects request response, wherein carries quota.

Alternatively, described service end specifically for:

Receive the diameter credit control from described DCCA client and reconnect after request, according to session id Search session:

If this session exists, the strategy according to itself is deducted fees to the information in this request, and presses Normal flow by new quota information carry diameter credit control reconnect return in request response described DCCA client;

The corresponding session if described service end finds this session id does not exist, and finds diameter credit control simultaneously Request type is attached most importance to connection request, then create session, is authenticated simultaneously and wholesale price is processed, and to institute State DCCA client reply diameter credit control and reconnect request response.

Alternatively, described DCCA client is additionally operable to:Receive diameter credit control and reconnect request response, more New session and business tine.

Alternatively, described DCCA client is WMG;Described service end is Online Charging System OCS or strategy and charging rule functions PCRF.

Invention further provides a kind of device realizing online charging, at least include lasting processing module, weight Build link block, wherein,

Continue processing module, for untreated ticket being stored in local or being sent to OFCS, and Continue holding business normally to use;

Rebuild link block, for pre-setting in satisfaction when reconnecting condition, start and service end weight New foundation connects.

Alternatively, also include accessing processing module, be used for:

When online charging user accesses, send diameter credit control initial request to described service end;Now,

The described processing module that continues is additionally operable to:Receive the diameter credit control after the extension of described service end Initial request responds, and wherein, the CCFH field of diameter credit control initial request response represents and continues and reconnect Connect, business can be continued after perceiving link failure and retry to indicate.

Alternatively, described access processing module is additionally operable to:

In described online charging customer service is carried out, trigger and send diameter credit control renewal to described service end Request;And when perceiving link exception, notify described lasting processing module;Or,

In described online charging customer service is carried out, trigger and send diameter credit control renewal to described service end Request;And receive the diameter credit control from described service end and update request response, wherein carry knot When fruit code is to process, notify described lasting processing module.Or,

After finding link down or waiting service end response timeout, judge itself to be configured with support session Reconnect after exception, notify described lasting processing module.

Alternatively, described reconstruction link block specifically for:

Meet pre-set when reconnecting condition, construction diameter credit control reconnect request message and send To described service end, carry the service charging information from after exception simultaneously;

Receive the diameter credit control from described service end and reconnect request response, wherein carry quota.

Compared with prior art, technical scheme include interacting with service end in DCCA client different Untreated ticket is stored in local or is sent to off-line accounting system by Chang Hou, DCCA client , and continue holding business and normally use (OFCS);Meet pre-set when reconnecting condition, DCCA client terminal start-up is re-established with service end and is connected.The technical scheme being provided by the present invention, DCCA client is interacted after exception with service end, can again recover between DCCA client and service end Interaction it is ensured that user is forever online, and achieve the mechanism that service end continues to monitor user conversation.

Other features and advantages of the present invention will illustrate in the following description, and, partly from froming the perspective of Become apparent in bright book, or understood by implementing the present invention.The purpose of the present invention is excellent with other Point can be realized by specifically noted structure in description, claims and accompanying drawing and obtain.

Brief description

Accompanying drawing described herein is used for providing a further understanding of the present invention, constitutes of the application Point, the schematic description and description of the present invention is used for explaining the present invention, does not constitute to the present invention's Improper restriction.In the accompanying drawings:

The flow chart that Fig. 1 realizes the method for online charging for the present invention;

Fig. 2 realizes the composition structural representation of the device of online charging for the present invention;

Fig. 3 realizes the schematic flow sheet of the first embodiment of online charging for the present invention;

Fig. 4 realizes the schematic flow sheet of the second embodiment of online charging for the present invention;

Fig. 5 realizes the schematic flow sheet of the 3rd embodiment of online charging for the present invention;

Fig. 6 realizes the schematic flow sheet of the fourth embodiment of online charging for the present invention.

Specific embodiment

For making the object, technical solutions and advantages of the present invention become more apparent, below in conjunction with accompanying drawing Embodiments of the invention are described in detail.It should be noted that in the case of not conflicting, this Shen Please in embodiment and the feature in embodiment can mutual combination in any.

The flow chart that Fig. 1 realizes the method for online charging for the present invention, as shown in figure 1, in Diameter Diameter credit control application protocol (DCCA) client is interacted after exception with service end, including:

Step 100:Untreated ticket is stored in local or is sent to offline meter by DCCA client Charge system (OFCS), and continue holding business and normally use.

Also include before this step:

When online charging user accesses, DCCA client such as GW can send credit to service end such as OCS Control initial request (CCR, Credit-Control-Request);OCS reflects to online charging user After power success, return the diameter credit control initial request response after extension to GW, wherein, at the beginning of diameter credit control Begin to ask diameter credit control failure handling (CCFH, the Credit-Control-Failure-Handling) word of response Section can represent and continue and reconnect for being arranged to 240 (CONTINUE_AND_RECONNECT), permissible after perceiving link failure to indicate GW Continuation business simultaneously retries.That is, CCFH field is 240 it is meant that working as GW and primary OCS Interact unsuccessfully, after not having standby OCS in system or interacting unsuccessfully with standby OCS, GW should protect Business of holding continue normal use, and be in due course as meet pre-set reconnect during condition with OCS reconnects.It should be noted that CCFH field can also be arranged to other values such as 241, As long as indicating that GW can continue business after perceiving link failure and retry for representing.

Or, DCCA client as locally configured in GW have support session exception after the configuration that reconnects Information.

It should be noted that can also be further in the credit control request response after the extension of the present invention Including:Other fields in addition to CCFH field, such as auto deduction failure handling (Direct-Debiting-Failure-Handling AVP), trigger type (Triger-Type AVP) etc., Or other numerical value of CCFH, the effect supporting to reconnect to reach identification to need.

Wherein, DCCA client is interacted with service end and extremely can include but is not limited to:

In online charging customer service is carried out, DCCA client such as GW is due to time threshold, flow The reason such as thresholding arrival and billing conditions change, can trigger and send diameter credit control more to service end such as OCS New request;It is abnormal that GW perceives link, be such as likely due to OCS link down it is also possible to The reasons such as link congestion, GW waits the diameter credit control of OCS to update request response timeout or other reasonses, But now GW cannot know whether OCS is treated, so, enter step 100.

Or,

In online charging customer service is carried out, DCCA client such as GW is due to time threshold, flow The reason such as thresholding arrival and billing conditions change, can trigger and send diameter credit control more to service end such as OCS New request;OCS receives diameter credit control and updates request, such as due to the signaling congestion performance of OCS side is not enough Or the reasons such as background system maintenance, OCS temporarily cannot process this CCR request, and OCS is under GW Send out diameter credit control and update request response, wherein carrying result code is 3004;GW is according to result code 3004, judge that OCS fails and deduct fees, enter step 100.Or, OCS side is due to performance not The reasons such as foot, OCS can issue, to GW, the result code that cannot process, and such as 3004- hurries and cannot process (Diameter_too_busy), the reason 3002- (Diameter_unable_to_deliver) undeliverable Value etc., these scenes are equally applicable to the present invention.

Or,

After DCCA client such as GW finds link down or waits service end such as OCS response timeout, Judge GW locally configured have support session exception after reconnect, then enter step 100.

Step 101:Meet pre-set when reconnecting condition, DCCA client terminal start-up and service End re-establishes connection.

In this step, the condition of reconnecting includes but is not limited to:Link-recovery, preset duration or link are gathered around Plug releasing etc..

DCCA client terminal start-up in this step re-establish with service end be connected including:

DCCA client such as GW construction diameter credit control reconnects request message and is sent to service end such as OCS, carry simultaneously the service charging information from after exception be online charging user use business and Corresponding flow, the information such as time;

OCS deducts fees to user, sends diameter credit control to GW simultaneously and reconnects request response, Wherein carry the relevant informations such as quota.

Wherein, the diameter credit control that OCS receives from GW reconnects after request, according to session id (Session-Id) search session:

If this session exists, the strategy according to OCS is deducted fees to the information in this request, and presses New quota information is carried to reconnect in request response in diameter credit control and returns to GW by normal flow;

The corresponding session if OCS finds this Session-Id does not exist, and finds that diameter credit control please simultaneously Ask type to attach most importance to connection request, then OCS creates session, authenticated simultaneously and wholesale price is processed, and to GW replys diameter credit control and reconnects request response.

Further, the inventive method also includes:

DCCA client such as GW receives diameter credit control and reconnects request response, more new session and business Content.

In the present invention, DCCA client can be GW, and service end can be OCS, strategy and charging Rule functional (PCRF, Policy and Charging Rules Function) etc..

Correspondingly, the present invention also provides a kind of system realizing online charging, at least includes DCCA client End, service end;Wherein,

DCCA client is abnormal for interacting with Online Charging System service end, by untreated ticket It is stored in local or is sent to off-line accounting system OFCS, and continue holding business and normally use;? Meet pre-set when reconnecting condition, DCCA client terminal start-up is re-established with service end and is connected;

Service end, for receiving the request of the reconnect from DCCA, returns and reconnects result.

Further,

DCCA client is additionally operable to:Online charging user accesses, and described DCCA client is to service end Send diameter credit control initial request;Correspondingly, service end is additionally operable to:The online charging user accessing is entered After row authentication success, return the diameter credit control initial request response after extension to described DCCA client; Wherein, the failure handling CCFH field in the response of diameter credit control initial request represents and continues and reconnect CONTINUE_AND_RECONNECT, with indicate described DCCA client perceiving link therefore Business can be continued after barrier and retry;

Or, in DCCA client, it is configured with the configuration information reconnecting after supporting session exception.

Specifically,

When DCCA client interacts exception with service end, DCCA client specifically for:

In described online charging customer service is carried out, trigger and send diameter credit control renewal request to service end; And described DCCA client to perceive link abnormal;Or,

In described online charging customer service is carried out, described DCCA client triggers and sends to service end Diameter credit control updates request;Now, described service end specifically for:Receive diameter credit control and update request, And issue diameter credit control renewal request response to described DCCA client, wherein carrying result code is Cannot process;Described DCCA client, according to result code, judges exception;Or,

After finding link down or waiting service end response timeout, and own local is configured with support session The configuration information reconnecting after exception.

Before DCCA client triggers and sends diameter credit control renewal request to service end, time threshold, Traffic threshold reaches and billing conditions change.

Wherein, result code be cannot process including:Described result code is the value or 3004- pre-setting Busy cannot process or 3002- is undeliverable.

Wherein, reconnect condition to include:Link-recovery or preset duration or link congestion release.

When DCCA client terminal start-up and service end re-establish and are connected, DCCA client specifically for:

Construction diameter credit control reconnects request message and is sent to service end, carries from after exception simultaneously Service charging information;Now,

Service end specifically for:User is deducted fees, sends credit to described DCCA client simultaneously Control and reconnect request response, wherein carry quota.Wherein, described service end specifically for:

Receive the diameter credit control from described DCCA client and reconnect after request, according to session id Search session:

If this session exists, the strategy according to itself is deducted fees to the information in this request, and presses Normal flow by new quota information carry diameter credit control reconnect return in request response described DCCA client;

The corresponding session if described service end finds this session id does not exist, and finds diameter credit control simultaneously Request type is attached most importance to connection request, then create session, is authenticated simultaneously and wholesale price is processed, and to institute State DCCA client reply diameter credit control and reconnect request response.

Further,

DCCA client is additionally operable to:Receive diameter credit control and reconnect request response, more new session and industry Business content.

Wherein, DCCA client is WMG;Service end is OCS or PCRF.

Fig. 2 realizes the composition structural representation of the device of online charging for the present invention, as shown in Fig. 2 extremely Few inclusion continues processing module, rebuilds link block, wherein,

Continue processing module, for being stored in local by untreated ticket or being sent to offline charging system Unite (OFCS), and continue holding business and normally use;

Rebuild link block, for pre-setting in satisfaction when reconnecting condition, start and service end weight New foundation connects.

Apparatus of the present invention also include accessing processing module, are used for:

When online charging user accesses, send CCR to service end such as OCS;Now, persistently process mould Block can receive the response of the diameter credit control initial request after the extension of OCS, wherein, at the beginning of diameter credit control The CCFH field beginning to ask response is 240, represents and continues and reconnect (CONTINUE_AND_RECONNECT), can be continued after perceiving link failure with indicating Business simultaneously retries.

Access processing module to be additionally operable to:

In online charging customer service is carried out, because time threshold, traffic threshold reach and charging bar The reasons such as part change, can trigger and send diameter credit control renewal request to service end such as OCS;And perceiving Link is abnormal, is such as likely due to OCS link down it is also possible to the reason such as link congestion, GW The diameter credit control waiting OCS updates request response timeout or other reasonses, notifies to continue processing module.

Or,

In online charging customer service is carried out, because time threshold, traffic threshold reach and charging bar The reasons such as part change, can trigger and send diameter credit control renewal request to service end such as OCS;And receive Update request response from the diameter credit control of OCS, wherein carry result code and be 3004 or cannot process Result code, such as 3004-Diameter_too_busy, 3002-Diameter_unable_to_deliver The reason value etc., notify continue processing module.

Or,

After finding link down or waiting service end such as OCS response timeout, judge itself to be configured with and prop up Reconnect after holding session exception, notify to continue processing module.

Wherein,

Rebuild link block specifically for:

Meet pre-set when reconnecting condition, construction diameter credit control reconnect request message and send To service end such as OCS, carry the service charging information from after exception is that online charging user uses simultaneously Business and corresponding flow, the information such as time;

Receive the diameter credit control from OCS and reconnect request response, wherein carry the correlations such as quota Information, and more new session and business tine.

Apparatus of the present invention can be as independent community's device it is also possible to be arranged in GW.

With reference to specific embodiment, the inventive method is described in detail.In following examples with DCCA client is GW, and service end is described for as a example OCS.

It should be noted that whether whether OCS have active and standby and support unsuccessfully to retransmit (FailOver) not For limit in protection scope of the present invention, for simplicity, in example below only so that dereliction is for OCS as a example Explanation.In addition, CCFH can issue from OCS it is also possible to configure on GW, the basic phase of its flow process Same, only illustrated as a example OCS issues by CCFH in following examples.

Fig. 3 realizes the schematic flow sheet of the first embodiment of online charging for the present invention, in first embodiment, With CCFH as CONTINUE_AND_RECONNECT, session on OCS when reconnecting exists for Example, as shown in figure 3, comprise the following steps:

Step 300:Online charging user accesses.

Step 301:GW sends diameter credit control initial request to OCS.

Step 300 and step 301 implement the known technology belonging to those skilled in the art, here Repeat no more.

Step 302:After OCS carries out to user authenticating success, send diameter credit control initial request to GW Response, in the present embodiment, the CCFH in the response of diameter credit control initial request is 240, in order to indicate GW can continue business after perceiving link failure and retry.

Step 303:In assuming that customer service carries out, GW reached due to time threshold, traffic threshold and The reasons such as billing conditions change, triggering diameter credit control updates request, and that is, GW sends diameter credit control to OCS Update request.

Step 304:It is abnormal that GW perceives link, be probably such as with OCS link down it is also possible to It is that the reasons such as link congestion lead to GW to wait the diameter credit control of OCS to update request response timeout, or Other reasonses.

Step 305:Because now GW cannot know whether OCS is treated, so this part is talked about Single (charge information such as flow using from the user of step 302 to step 303 this period) storage Local or be sent to OFCS, it is 240 according to CCFH, so continue holding business normally making simultaneously With unaffected.

Step 306:In certain trigger point, the reconstruction condition of contact such as pre-setting, such as clocked flip Or perceive link-state change triggering etc., GW sends diameter credit control to OCS and reconnects request, its Middle credit control request type is to be expressed as rebuilding the request such as 240 connecting, and carries from GW sense simultaneously Know the service charging information of this period after exception.

Step 307:OCS deducts fees to user, sends diameter credit control to GW simultaneously and reconnects request Response message, wherein carries the relevant informations such as quota.

Fig. 4 realizes the schematic flow sheet of the second embodiment of online charging for the present invention, in second embodiment, When assuming to rebuild connection, the upper session of OCS does not exist.As shown in figure 4, comprising the following steps:

Implementing of step 400~step 406 is completely the same with step 300~step 306, here not Repeat again.

Step 407:It is assumed that OCS searches conversation failure according to session id in the present embodiment, but, OCS finds that credit control request type is 240, then OCS re-creates session and user reflected simultaneously Power etc. is processed.

Step 408:OCS sends diameter credit control to GW and reconnects request response, and wherein diameter credit control please Ask type to be 240, carry the quota information of business simultaneously.

Fig. 5 realizes the schematic flow sheet of the 3rd embodiment of online charging for the present invention, in 3rd embodiment, Return to hurry with OCS and cannot process (3004-Diameter_too_busy), CCFH is CONTINUE_AND_RECONNECT, as a example on OCS when reconnecting, session exists.As Fig. 5 Shown, comprise the following steps:

Step 500:Online charging user accesses.

Step 501:GW sends diameter credit control initial request to OCS.

Step 502:After OCS carries out to user authenticating success, send diameter credit control initial request to GW Response, wherein CCFH is 240, in order to indicate that GW can continue business after perceiving link failure And retry.

Step 503:In assuming that customer service carries out, GW reached due to time threshold, traffic threshold and The reasons such as billing conditions change, triggering diameter credit control updates request, and that is, GW sends diameter credit control to OCS Update request.

Step 504:OCS receives diameter credit control and updates request, it is assumed that due to OCS side in the present embodiment Signaling congestion performance is not enough or the reason such as background system maintenance, OCS temporarily cannot process this CCR Request, OCS can issue diameter credit control to GW and update request response, and wherein result code is 3004.

Step 505:GW, according to result code 3004, judges that OCS fails and deducts fees, by this part Ticket (charge information such as flow using from the user of step 502 to 503 this period) is stored in Local or be sent to OFCS, it is 240 according to CCFH, so continue holding business normally using simultaneously Unaffected.

Step 506:The clocked flip such as pre-setting in certain trigger point, GW sends letter to OCS Reconnect request message with controlling, wherein carry current business and business service condition information.

Step 507:OCS to GW return diameter credit control reconnect request response, and congestion or Person's consistency operation is safeguarded and is released, then user is deducted fees and wholesale price is processed, follow-up process is normal.

Fig. 6 realizes the schematic flow sheet of the fourth embodiment of online charging for the present invention, in fourth embodiment, CCFH AVP is not carried with OCS, reconnects, when reconnecting after GW locally configured support session exception As a example the upper session of OCS exists.As shown in fig. 6, comprising the following steps:

The flow process of the fourth embodiment shown in Fig. 6 is essentially identical with the first embodiment shown in Fig. 3, different Part is:In step 602, OCS does not carry CCFH in the response of diameter credit control initial request AVP, in step 604, after GW finds link down or waits OCS response timeout, by sentencing Disconnected GW is locally configured have support session exception after reconnect, then start and subsequently reconnect flow process.

The above, the only preferred embodiments of the present invention, it is not intended to limit the protection model of the present invention Enclose.All any modification, equivalent substitution and improvement within the spirit and principles in the present invention, done etc., Should be included within the scope of the present invention.

Claims (24)

1. a kind of method realizing online charging is it is characterised in that apply association in Diameter diameter credit control View DCCA client is interacted after exception with Online Charging System service end, also includes:
Untreated ticket is stored in local or is sent to off-line accounting system by DCCA client OFCS, and continue holding business and normally use;
Meet pre-set when reconnecting condition, DCCA client terminal start-up and service end re-establish Connect.
2. method according to claim 1 is it is characterised in that also include before the method:
When online charging user accesses, described DCCA client sends diameter credit control to service end and initially please Ask;
Described service end carries out to the online charging user accessing authenticating after success, to described DCCA client End returns the diameter credit control initial request response after extension;Wherein, in the response of diameter credit control initial request Failure handling CCFH field represents and continues and reconnect CONTINUE_AND_RECONNECT, with Indicate that described DCCA client can continue business after perceiving link failure and retry;
Or, described DCCA client locally configured have support session exception after reconnect configuration letter Breath.
3. method according to claim 2 is it is characterised in that described DCCA client and clothes The interaction of business end is abnormal to be included:
In described online charging customer service is carried out, described DCCA client triggers and sends to service end Diameter credit control updates request;And described DCCA client to perceive link abnormal;Or,
In described online charging customer service is carried out, described DCCA client triggers and sends to service end Diameter credit control updates request;Described service end receives diameter credit control and updates request, and to described DCCA visitor Family end issues diameter credit control and updates request response, and wherein carrying result code is to process;Described DCCA client, according to result code, judges exception;Or,
After described DCCA client finds link down or waits service end response timeout, and itself is originally Be configured with and support the configuration information that reconnects after session exception.
4. method according to claim 3 is it is characterised in that described DCCA client triggers Send before diameter credit control updates request to service end and also include:Time threshold, traffic threshold reach and Billing conditions change.
5. method according to claim 3 is it is characterised in that described result code is to process bag Include:Described result code is that the value pre-setting or 3004- hurry and cannot process or 3002- is undeliverable.
6. method according to claim 2 is it is characterised in that the described condition that reconnects includes:Chain Road is recovered or preset duration or link congestion releasing.
7. method according to claim 2 is it is characterised in that described DCCA client terminal start-up Re-establish with service end be connected including:
Described DCCA client construction diameter credit control reconnects request message and is sent to service end, simultaneously Carry the service charging information from after exception;
Described service end is deducted fees to user, sends diameter credit control weight to described DCCA client simultaneously Connection request response message, wherein carries quota.
8. method according to claim 7 is it is characterised in that described service end is detained to user Take, reconnect request response to described DCCA client transmission diameter credit control simultaneously and include:
The diameter credit control that described service end receives from DCCA client reconnects after request, according to session ID searches session:
If this session exists, the strategy according to itself is deducted fees to the information in this request, and presses Normal flow by new quota information carry diameter credit control reconnect return in request response described DCCA client;
The corresponding session if described service end finds this session id does not exist, and finds diameter credit control simultaneously Request type is attached most importance to connection request, then create session, is authenticated simultaneously and wholesale price is processed, and to institute State DCCA client reply diameter credit control and reconnect request response.
9. the method according to any one of claim 1~8 is it is characterised in that the method also includes: Described DCCA client receives diameter credit control and reconnects request response, more new session and business tine.
10. the method according to any one of claim 1~8 is it is characterised in that described DCCA is objective Family end is WMG;Described service end is Online Charging System OCS or strategy and charging rule functions PCRF.
A kind of 11. systems realizing online charging it is characterised in that at least including DCCA client, Service end;Wherein,
DCCA client is abnormal for interacting with Online Charging System service end, by untreated ticket It is stored in local or is sent to off-line accounting system OFCS, and continue holding business and normally use;? Meet pre-set when reconnecting condition, DCCA client terminal start-up is re-established with service end and is connected;
Service end, for receiving the request of the reconnect from DCCA, returns and reconnects result.
12. systems according to claim 11 it is characterised in that described DCCA client also For:Online charging user accesses, and described DCCA client sends diameter credit control to service end and initially please Ask;Correspondingly, described service end is additionally operable to:The online charging user accessing is carried out authenticate after success, Return the diameter credit control initial request response after extension to described DCCA client;Wherein, diameter credit control Failure handling CCFH field in initial request response represents and continues and reconnect CONTINUE_AND_RECONNECT, with indicate described DCCA client perceiving link therefore Business can be continued after barrier and retry;
Or, in described DCCA client, it is configured with the configuration information reconnecting after supporting session exception.
13. systems according to claim 12 are it is characterised in that in described DCCA client When interacting exception with service end, described DCCA client specifically for:
In described online charging customer service is carried out, trigger and send diameter credit control renewal request to service end; And described DCCA client to perceive link abnormal;Or,
In described online charging customer service is carried out, described DCCA client triggers and sends to service end Diameter credit control updates request;Now, described service end specifically for:Receive diameter credit control and update request, And issue diameter credit control renewal request response to described DCCA client, wherein carrying result code is Cannot process;Described DCCA client, according to result code, judges exception;Or,
After finding link down or waiting service end response timeout, and own local is configured with support session The configuration information reconnecting after exception.
14. systems according to claim 13 are it is characterised in that described DCCA client is touched Before being sent to service end transmission diameter credit control renewal request, time threshold, traffic threshold reach and charging Condition changes.
15. systems according to claim 13 are it is characterised in that described result code is to process Including:Described result code is that the value pre-setting or 3004- hurry and cannot process or 3002- is undeliverable.
16. systems according to claim 12 are it is characterised in that the described condition that reconnects includes: Link-recovery or preset duration or link congestion release.
17. systems according to claim 12 are it is characterised in that described DCCA client opens Dynamic re-establish when being connected with service end, described DCCA client specifically for:
Construction diameter credit control reconnects request message and is sent to service end, carries from after exception simultaneously Service charging information;
Described service end specifically for:User is deducted fees, sends to described DCCA client simultaneously Diameter credit control reconnects request response, wherein carries quota.
18. systems according to claim 17 it is characterised in that described service end specifically for:
Receive the diameter credit control from described DCCA client and reconnect after request, according to session id Search session:
If this session exists, the strategy according to itself is deducted fees to the information in this request, and presses Normal flow by new quota information carry diameter credit control reconnect return in request response described DCCA client;
The corresponding session if described service end finds this session id does not exist, and finds diameter credit control simultaneously Request type is attached most importance to connection request, then create session, is authenticated simultaneously and wholesale price is processed, and to institute State DCCA client reply diameter credit control and reconnect request response.
19. systems according to any one of claim 11~18 are it is characterised in that described DCCA Client is additionally operable to:Receive diameter credit control and reconnect request response, more new session and business tine.
20. systems according to any one of claim 11~18 are it is characterised in that described DCCA Client is WMG;Described service end is Online Charging System OCS or strategy and charging rule functions PCRF.
A kind of 21. devices realizing online charging it is characterised in that at least include lasting processing module, Rebuild link block, wherein,
Continue processing module, for untreated ticket being stored in local or being sent to OFCS, and Continue holding business normally to use;
Rebuild link block, for pre-setting in satisfaction when reconnecting condition, start and service end weight New foundation connects.
22. devices according to claim 21 it is characterised in that also include access processing module, For:
When online charging user accesses, send diameter credit control initial request to described service end;Now,
The described processing module that continues is additionally operable to:Receive the diameter credit control after the extension of described service end Initial request responds, and wherein, the CCFH field of diameter credit control initial request response represents and continues and reconnect Connect, business can be continued after perceiving link failure and retry to indicate.
23. devices according to claim 22 are it is characterised in that described access processing module is also used In:
In described online charging customer service is carried out, trigger and send diameter credit control renewal to described service end Request;And when perceiving link exception, notify described lasting processing module;Or,
In described online charging customer service is carried out, trigger and send diameter credit control renewal to described service end Request;And receive the diameter credit control from described service end and update request response, wherein carry knot When fruit code is to process, notify described lasting processing module;Or,
After finding link down or waiting service end response timeout, judge itself to be configured with support session Reconnect after exception, notify described lasting processing module.
24. devices according to claim 22 are it is characterised in that described reconstruction link block is concrete For:
Meet pre-set when reconnecting condition, construction diameter credit control reconnect request message and send To described service end, carry the service charging information from after exception simultaneously;
Receive the diameter credit control from described service end and reconnect request response, wherein carry quota.
CN201510488933.4A 2015-08-11 2015-08-11 Method, system and device for realizing online charging CN106454788A (en)

Priority Applications (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

Applications Claiming Priority (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

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 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)

Citations (4)

* Cited by examiner, † Cited by third party
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)

* Cited by examiner, † Cited by third party
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)

Patent Citations (4)

* Cited by examiner, † Cited by third party
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

Also Published As

Publication number Publication date
WO2016180177A1 (en) 2016-11-17

Similar Documents

Publication Publication Date Title
DE60314673T2 (en) Medium and method for controlling service progression between different domains
KR101042745B1 (en) System and method for reestablishing the session between terminal and server
US9641697B2 (en) Policy and charging control method, V-PCRF and V-OCS
EP1662702B1 (en) Call control with converged application server logic and gateway logic in IMS networks
EP2441232B1 (en) Methods, apparatuses, and related computer program product for network element recovery
US20130329713A1 (en) Process method about the service connection between the wireless local area network and user terminal
CN104094577B (en) Method and apparatus for evaluating the state of mobile body indirectly
CN101631360B (en) Method, device and system for realizing load balancing
CN102075897B (en) Method and system for charging mobile data service
KR101844755B1 (en) Terminate a charging session for an always on ip connectivity session
CN103392353B (en) Wireless network capacity open system, gateway, agent and method
CN101646270B (en) Method, system, mobility management entity and memory device for maintaining service continuity
US9798680B2 (en) Policy control method and apparatus for terminal peripheral
US20080147551A1 (en) System and Method for a SIP Server with Online Charging
CN103329480A (en) Session redundancy among a server cluster
US20100008218A1 (en) Termination Message for Wireless Wide Area Network Routers
WO2009134265A1 (en) Message restriction for diameter servers
US9407512B2 (en) Method and apparatus for controlling terminal's access to a wireless network
EP3301957B1 (en) Charging method, network device, and charging system
CN107295354A (en) Connect the live method for building up of wheat and device in a kind of network direct broadcasting
US20060286963A1 (en) Controlling provision of services in a communications network
DE602005002524T2 (en) IMS gateway and online billing method in IMS networks
CN102710554A (en) Distributed message system and service status detection method thereof
WO2015154350A1 (en) Internet access traffic sharing method, device and terminal
WO2009065354A1 (en) A method, a system and a device for access prompt information processing

Legal Events

Date Code Title Description
PB01 Publication
C06 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination