WO2017050128A1

WO2017050128A1 - Overload control method and apparatus for accounting request

Info

Publication number: WO2017050128A1
Application number: PCT/CN2016/098324
Authority: WO
Inventors: 郭文洁
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-09-23
Filing date: 2016-09-07
Publication date: 2017-03-30
Also published as: CN106549771A

Abstract

An overload control method for an accounting request comprises: sending an accounting request (ACR) in a current session to a first charging data function unit; acquiring overload indication information from an accounting request answer (ACA) of the ACR sent by the first charging data function unit, the overload indication information carrying at least an overload grade and an overload control identifier; acquiring, according to the overload grade, a session identifier of a target session needing to perform overload control; and executing, according to an overload control mode indicated by the overload control identifier, an overload control operation on a to-be-sent ACR in the target session indicated by the session identifier, the overload control operation being at least used for indicating non-sending of the to-be-sent ACR in the target session to the first charging data function unit. The technical solution resolves the problem of low flexibility in overload control caused by a single Diameter overload control mode in the related art, thereby achieving the effect of flexible overload control.

Description

Overload control method and device for charging request message

Technical field

The present application relates to, but is not limited to, the field of communications, and in particular, to an overload control method and apparatus for a charging request message.

Background technique

At present, the Diameter overload control method of the existing offline charging interface Rf of the 3GPP (Third Generation Partnership Project) uses the "DIAMETER_TOO_BUSY" error response code to indicate that the charging interface has reached the overload state. If the charging trigger function (CTF, Charging Trigger Function) does not receive the accounting response message (ACA, Accounting Request Answer), it will usually receive the "Charging Data Function" (CDF). DIAMETER_TOO_BUSY" error response code. At this time, the CTF re-sends a buffered Accounting Request message (ACR, Accounting Request) to the CDF every other operator's configurable waiting time. When the number of repeated transmissions reaches the maximum number of repetitions configured by the operator, However, when the ACA response message is still not received, the CTF will perform the connection failure processing.

Further, if the cached ACR charging request message is not a new charging request message, but a subsequent ACR message of the ACR charging request message that was successfully sent to the broken CDF (for example, ACR [Interim] and/or ACR [ When Stop]), the CTF will send a buffered ACR Accounting Request message to the Broken CDF every other period of time that the operator can configure. This retransmission process is considered because the charging information cannot be lost. It will continue to repeat indefinitely until the link is restored.

It can be seen that the related technology realizes Diameter overload control by transmitting a buffered ACR charging request message every predetermined waiting time. In other words, the related technology adopts the same control mode for different overload levels, and the control is performed. There must be a problem with a single control method.

In view of the related art, an effective solution has not been proposed due to the low flexibility of the overload control caused by the relatively simple Diameter overload control mode.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the invention provides a method and a device for controlling the overload of the charging request message, so as to at least solve the problem that the flexibility of the overload control caused by the Diameter overload control mode is relatively simple in the related art.

According to an aspect of the embodiments of the present invention, a method for controlling an overload of a charging request message includes: transmitting an Accounting Request message (ACR) in a current session to a first charging data function unit; The overload indication information is obtained by the charging response message (ACA) of the ACR sent by the charging data function unit, where the overload indication information carries at least an overload level and an overload control identifier; and the overload control is required according to the overload level acquisition. The session identifier of the target session; performing an overload control operation on the ACR to be sent in the target session indicated by the session identifier according to the overload control mode indicated by the overload control identifier, wherein the overload control operation is at least And means for not sending the to-be-sent ACR in the target session to the first charging data function unit.

Optionally, performing an overload control operation on the to-be-sent ACR in the target session indicated by the session identifier according to the overload control mode indicated by the overload control identifier, including at least one of the following: proportionally The ACR to be sent in the target session is cached in an ACR queue in the local storage; all the ACRs to be sent in the target session are all cached in an ACR queue in the local storage; The ACR to be sent in the session is sent to the second charging data function unit; all the ACRs to be sent in the target session are all sent to the second charging data function unit.

Optionally, the obtaining the session identifier of the target session that needs to perform the overload control according to the overload level includes: acquiring the first session identifier of the current session as the target session if the overload level is a primary overload level a session identifier; if the overload level is a medium overload level, obtaining a first session identifier of the current session and a second session identifier of a historical session before the current session as a session identifier of the target session; The overload level is an advanced overload level, and the first session identifier of the current session and the history session before the current session are acquired. The second session identifier is used as the session identifier of the target session.

Optionally, the overload level is a primary overload level, and the overload control mode is performed according to the overload control mode indicated by the overload control identifier, and an overload control operation is performed on the ACR to be sent in the target session indicated by the session identifier, The method includes: proxiwardly buffering an ACR to be sent in the current session to the ACR queue in the local storage; or, proportionally sending an ACR to be sent in the current session to the second charging Data function unit.

Optionally, the overload level is a medium overload level, and the overload control mode is performed according to the overload control mode indicated by the overload control identifier, and an overload control operation is performed on the ACR to be sent in the target session indicated by the session identifier, Include: prorating the current session and the ACR to be sent in the historical session to the ACR queue in the local storage in proportion; or proportionally, the current session and the waiting in the historical session The sending ACR is sent to the second charging data function unit.

Optionally, the overload level is an advanced overload level, and the overload control mode is performed according to the overload control mode indicated by the overload control identifier, and an overload control operation is performed on the ACR to be sent in the target session indicated by the session identifier, The method includes: all the ACRs to be sent in the current session and the historical session are cached in the ACR queue in the local storage; or the ACR to be sent in the current session and the historical session are all Sended to the second charging data function unit.

Optionally, the overload indication information further includes a network element list corresponding to the overload level, where the network element list includes a network element to be overload controlled that matches the corresponding overload level. NE identifier.

Optionally, after the acquiring the overload indication information in the ACA of the ACR sent by the first charging data function unit, the method further includes: determining a network element identifier of the current network element where the current session is located. Whether it is included in the network element list carried by the overload indication information; if the network element identifier of the current network element where the current session is located is included in the network element list carried by the overload indication information And performing an overload control operation on the current network element.

Optionally, after the sending the ACR in the current session to the first charging data function unit, the method further includes: receiving an ACA carrying the overload level from the first charging data function unit, where The overload level is the first charging data function unit according to a current load The amount is determined.

Optionally, if the current load amount of the first charging data function unit is between a preset first predetermined threshold and a second predetermined threshold, the current overload level is the primary overload level; If the current load amount of the first charging data function unit is between the second predetermined threshold and the third predetermined threshold, the current overload level is the intermediate overload level; The current load amount of the first billing data function unit is greater than the pre-configured third predetermined threshold, and the current overload level is the advanced overload level; wherein the first predetermined threshold is less than the a second predetermined threshold, the second predetermined threshold being less than the third predetermined threshold.

According to another aspect of the present invention, an overload control apparatus for a charging request message is provided, comprising: a sending module, configured to send an Accounting Request message (ACR) in a current session to a first charging data function unit. The first obtaining module is configured to obtain the overload indication information from the charging response message (ACA) of the ACR sent by the first charging data function unit, where the overload indication information carries at least an overload level and an overload And a second acquisition module, configured to acquire, according to the overload level, a session identifier of the target session that needs to be subjected to overload control; the first processing module is configured to follow the overload control mode indicated by the overload control identifier, The ACR to be sent in the target session indicated by the session identifier performs an overload control operation, wherein the overload control operation is at least used to indicate that the target data in the target session is not to be sent to the first charging data function unit. ACR.

Optionally, the first processing module includes at least one of: a first cache unit configured to cache the ACR to be sent in the target session to an ACR queue in a local storage; the second cache a unit, configured to cache all the ACRs to be sent in the target session to an ACR queue in the local storage; the first sending unit is configured to send the ACR to be sent in the target session proportionally a second charging data function unit; the second sending unit is configured to send all the ACRs to be sent in the target session to the second charging data function unit.

Optionally, the second obtaining module includes: a first acquiring unit, configured to acquire a first session identifier of the current session as a session identifier of the target session, if the overload level is a primary overload level; The second obtaining unit is set to obtain if the overload level is a medium overload level Taking the first session identifier of the current session and the second session identifier of the historical session before the current session as the session identifier of the target session; and the third obtaining unit, if the overload level is the advanced overload level And acquiring a first session identifier of the current session and a second session identifier of the historical session before the current session as a session identifier of the target session.

Optionally, the first processing module further includes: a third cache unit, configured to cache the to-be-sent ACR in the current session to the local storage in proportion when the overload level is a primary overload level Or the third sending unit is configured to send the ACR to be sent in the current session to the second charging data function unit proportionally when the overload level is a primary overload level. .

Optionally, the first processing module further includes: a fourth buffer unit, configured to cache the current session and the ACR to be sent in the historical session to be proportionally when the overload level is a medium overload level In the ACR queue in the local storage; or, the fourth sending unit is configured to send the ACR to be sent in the current session and the historical session proportionally when the overload level is a medium overload level Giving the second billing data functional unit.

Optionally, the first processing module further includes: a fifth buffer unit, configured to cache all the ACRs to be sent in the current session and the historical session when the overload level is an advanced overload level In the ACR queue in the local storage; or, the fifth sending unit is configured to send all the ACRs to be sent in the current session and the historical session to the location when the overload level is a high level of overload The second charging data function unit is described.

Optionally, the device further includes: a determining module, configured to determine, after the first obtaining module obtains the overload indication information from the ACA of the ACR sent by the first charging data function unit, Whether the network element identifier of the current network element where the session is located is included in the network element list carried by the overload indication information; and the second processing module is configured to: if the network element of the current network element where the current session is located The identifier is included in the network element list carried by the overload indication information, and an overload control operation is performed on the current network element.

Optionally, the device further includes: a third processing module, configured to be in the sending module After receiving the ACR in the current session, the charging data function unit receives the ACA carrying the overload level from the first charging data function unit, where the overload level is the first charging data function unit Determined based on the current load.

The embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, which are implemented when the computer executable instructions are executed to implement the overload control method of the charging request message.

According to the embodiment of the present invention, the ACR in the current session is sent to the first charging data function unit, and the overload indication information is obtained from the ACA of the ACR sent by the first charging data function unit, where the overload indication information is at least Carrying an overload level and an overload control identifier; obtaining, according to the overload level, a session identifier of the target session that needs to be subjected to overload control; according to the overload control mode indicated by the overload control identifier, the target session indicated in the session identifier is to be sent The ACR performs an overload control operation, wherein the overload control operation is at least for indicating that the ACR to be transmitted in the target session is not sent to the first charging data function unit. Obtaining a different overload level of the first charging data function unit from the overload indication information to determine a current overload level of the first charging data function unit, thereby achieving different overload levels for the different target sessions in the ACR Afterwards, the ACR to be sent sent to the first charging data function unit performs a corresponding overload control operation to overcome the problem of low flexibility of the overload control caused by the single Diameter overload control mode in the related art. It is possible to adopt different overload control modes for different overload levels and flexibly carry out the effect of overload control. In addition, through flexible overload control, the accuracy of the overload control will be further improved to ensure the normal operation of the first billing data functional unit after the overload control.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

The drawings described herein are intended to provide a further understanding of the present application, and are intended to be a part of this application. In the drawing:

1 is a flowchart of overload control of a charging request message according to an embodiment of the present invention;

2 is a flow chart 1 of a Diameter overload control method on an offline charging interface according to an embodiment of the present invention;

3 is a second flowchart of a Diameter overload control method on an offline charging interface according to an embodiment of the present invention;

4 is a third flowchart of a Diameter overload control method on an offline charging interface according to an embodiment of the present invention;

5 is a flowchart 4 of a Diameter overload control method on an offline charging interface according to an embodiment of the present invention;

6 is a structural block diagram of an overload control apparatus for a charging request message according to an embodiment of the present invention;

7 is a structural block diagram 1 of an overload control apparatus for a charging request message according to an embodiment of the present invention;

8 is a structural block diagram 2 of an overload control apparatus for a charging request message according to an embodiment of the present invention;

9 is a structural block diagram 3 of an overload control apparatus for a charging request message according to an embodiment of the present invention;

10 is a structural block diagram 4 of an overload control apparatus for a charging request message according to an embodiment of the present invention;

11 is a structural block diagram 5 of an overload control apparatus for a charging request message according to an embodiment of the present invention;

12 is a structural block diagram 6 of an overload control apparatus for a charging request message according to an embodiment of the present invention;

FIG. 13 is a structural block diagram 7 of an overload control apparatus for a charging request message according to an embodiment of the present invention.

Embodiments of the invention

The present application will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

Embodiment 1

It should be noted that the terms "first", "second" and the like in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or order.

In this embodiment, an overload control method for a charging request message is provided. FIG. 1 is a flowchart of overload control of a charging request message according to an embodiment of the present invention. As shown in FIG. 1, the method includes the following steps:

Step S102, sending a charging request message (ACR) in the current session to the first charging data function unit;

In step S104, the overload indication information is obtained from the charging response message (ACA) of the ACR sent by the first charging data function unit, where the overload indication information carries at least an overload level and an overload control identifier;

Step S106: Acquire, according to the overload level, a session identifier of a target session that needs to perform overload control;

Step S108: Perform an overload control operation on the to-be-sent ACR in the target session indicated by the session identifier according to the overload control mode indicated by the overload control identifier, where the overload control operation is at least used to indicate that the first The billing data function unit sends the ACR to be sent in the target session.

Optionally, in this embodiment, the overload control method of the foregoing charging request message may be, but is not limited to, being applied to a Diameter overload control process, which is different from the related art in that the cached ACR is sent after every predetermined waiting time. Diameter overload control is implemented, but different overload control modes are adopted for different overload levels, which avoids the problem of low flexibility of overload control due to the single Diameter overload control mode in the related art.

Optionally, in this embodiment, the ACR may include, but is not limited to, an identification letter carrying a Diameter Overload Indication Conveyance (DOIC). interest.

Optionally, in this embodiment, the foregoing target session may include, but is not limited to, a current session, or a current session and a historical session. Wherein, the initial ACR message ACR[START] in the above historical session may be, but is not limited to, generated before the occurrence of an overload, the initial ACR message ACR[START] in the current session may include, but is not limited to, after the occurrence of an overload. That is, the start ACR message ACR[START] of the historical session in the CTF is generated before the start ACR message ACR[START] of the current session.

Optionally, in this embodiment, the overload control operation may include, but is not limited to, one of the following: buffering the ACR to be sent to the ACR queue in the local buffer, and sending the ACR to be sent to the second charging data function. unit. The ACR queue for buffering the ACR to be sent to the local buffer may include, but is not limited to, the following method: the ACR to be sent is cached to the ACR queue in the local buffer, and the ACR to be sent is cached. Go to the ACR queue in the local buffer. In addition, the foregoing sending the to-be-sent ACR to the second charging data function unit may include, but is not limited to, a method of proportionally transmitting the to-be-sent ACR to be sent to the first charging data function unit after the ACR in the current session. Sending, to the second charging data function unit, the current session and the to-be-sent ACR to be sent to the first charging data function unit after the ACR in the historical session before the current session to the second charging The data function unit sends all the to-be-sent ACRs to be sent to the first charging data function unit after the ACR in the current session and in the historical session before the current session to the second charging data function unit.

Optionally, in the embodiment, the overload level includes, but is not limited to, a primary overload level, a medium overload level, and an advanced overload level. The target session identifier that needs to be subjected to the overload control according to the overload level includes, but is not limited to, if the overload level is the primary overload level, the first session identifier of the current session is obtained as the session identifier of the target session; if the overload level is the intermediate overload level, Obtaining the first session identifier of the current session and the second session identifier of the historical session before the current session as the session identifier of the target session; if the overload level is the advanced overload level, acquiring the first session identifier of the current session and before the current session The second session identifier of the historical session is the session identifier of the target session. That is, the embodiment of the present invention dynamically selects the target session identifier according to the overload level, which avoids the problem that the flexibility of the overload control is low due to the single Diameter overload control mode in the related art.

Optionally, in this embodiment, according to the overload control mode indicated by the overload control identifier, performing overload control on the ACR to be sent sent to the first charging data function unit after the ACR in the target session indicated by the session identifier Operation, including but not limited to: prorating the ACR to be sent in the target session to the ACR queue in the local storage; or, all the ACRs to be sent in the target session are cached into the ACR queue in the local storage; or Transmitting the to-be-sent ACR in the target session to the second charging data function unit; or transmitting all the ACRs to be sent in the target session to the second charging data function unit. For example, the higher the percentage indicated by the overload control percentage information received by the CTF, the more session messages are cached in the ACR queue in the local storage, or the more the session messages are sent proportionally to the second charging data function unit. Therefore, the processing load of the first CDF is alleviated, so as to avoid the problem that the first CDF is overloaded in time.

Optionally, in this embodiment, the overload indication information further includes a network element list corresponding to the overload level, where the network element list includes, but is not limited to, an overload control that matches the corresponding overload level. The NE ID of the NE. The operator can configure the matched network element list information according to the overload level and charging priority of the CDF and bring it back to the CTF in the response message by the CDF. The CTF receives the reduced percentage and overload for the overload control from the CDF. After the level information and algorithm identification, it may be decided to adopt a corresponding overload control algorithm according to different overload level information.

Optionally, in this embodiment, the embodiment of the present invention provides that when the network deploys the first CDF (Primary CDF) and the second CDF (Secondary CDF), the CTF may select a new charging request that is to be cached proportionally. The message ACR[Start] and subsequent ACR[Interim] and ACR[Stop] are forwarded to the auxiliary CDF, thereby avoiding the problem of overload of the main CDF.

Through the above steps, the ACR in the current session is sent to the first charging data function unit; the overload indication information is obtained from the ACA of the ACR sent by the first charging data function unit, where the overload indication information carries at least an overload level. And an overload control identifier; obtaining, according to the overload level, a session identifier of the target session that needs to be overloaded; performing an overload on the ACR to be sent in the target session indicated by the session identifier according to the overload control mode indicated by the overload control identifier Control operation, wherein the overload control operation is at least for indicating that the ACR to be transmitted in the target session is not sent to the first charging data function unit. That is, in the above step, by acquiring the overload control identifier, and then, by the overload control mode indicated by the overload control flag, the target indicated by the session identifier is The ACR that is to be sent to the first charging data function unit after the ACR performs an overload control operation, and is different from the related art in that the buffered ACR is sent after every predetermined waiting time to implement Diameter overload control. . That is to say, the above-mentioned steps solve the problem that the flexibility of the overload control is low due to the single Diameter overload control mode, and the effect of optimizing the overload control is realized.

In an optional implementation manner, step S108 can be implemented in the following manner:

Step S11, the ACR in the target session is cached in proportion to the ACR queue in the local storage; or

Step S12: All the ACRs to be sent in the target session are cached into the ACR queue in the local storage; or

Step S13, the ACR to be sent in the target session is sent to the second charging data function unit according to a ratio; or

Step S14: All the ACRs to be sent in the target session are sent to the second charging data function unit.

Through any one of the foregoing steps S11 to S14, the ACR to be sent in the target session is cached in the local memory ACR queue by a certain percentage, so that after the overload state is eliminated, the ACR queue in the local memory is sequentially read. Take, because as an important operational data for the operator, the charging message cannot be discarded at will. For transmitting the ACR in the target session proportionally or completely to the second charging data function unit in the foregoing step, the first charging data unit may be effectively prevented from being overloaded.

In an optional implementation manner, step S106 can be implemented by the following steps:

Step S21: If the overload level is the primary overload level, obtain the first session identifier of the current session as the session identifier of the target session;

Step S22: If the overload level is the intermediate level, obtain the first session identifier of the current session and the second session identifier of the historical session before the current session as the session identifier of the target session;

Step S23: If the overload level is the advanced overload level, obtain the first session identifier of the current session and the second session identifier of the historical session before the current session as the session identifier of the target session.

It should be noted that, in this embodiment, the initial ACR message in the above historical session ACR[START] may, but is not limited to, be generated prior to the occurrence of an overload, the initial ACR message ACR[START] in the current session may include, but is not limited to, after an overload occurs. That is, the start ACR message ACR[START] of the historical session in the CTF is generated before the start ACR message ACR[START] of the current session.

Optionally, in this embodiment, if the overload level is a primary overload level, only the current ACR is the ACR [Start] in the current session and the subsequent ACR [interim] and ACR [Stop] of the ACR [Start]. The overload control operation is performed proportionally.

Optionally, in this embodiment, if the overload level is a medium overload level, the current ACR is the ACR [Start] in the current session and the subsequent ACR [interim] and ACR [Stop] of the ACR [Start]. And the subsequent ACR [interim] and ACR [Stop] in the history session, the overload control operation is performed proportionally.

Optionally, in this embodiment, if the overload level is an advanced overload level, the current ACR is the ACR [Start] in the current session and the subsequent ACR [interim] and ACR [Stop] of the ACR [Start]. And the subsequent ACR [interim] and ACR [Stop] in the history session, all perform the overload control operation.

The above steps S21 to S23 can dynamically select the target session identifier according to the overload level, thereby achieving the effect of effective overload control.

In an optional implementation manner of this embodiment, when the overload level is the primary overload level, step S108 can be implemented by the following method:

Step S31, the ACR to be sent in the current session is cached in proportion to the ACR queue in the local storage; or

Step S32, the ACR to be sent in the current session is sent to the second charging data function unit in proportion.

Optionally, in this embodiment, if the overload level is a primary overload level, only the current ACR to be sent is the ACR [Start] in the current session and the subsequent ACR [interim] and ACR of the ACR [Start]. [Stop], the overload control operation is performed proportionally. For example, if the current ACR is ACR[Start] in the current session and subsequent ACR[interim] and ACR[Stop] of the ACR[Start], the current ACR is proportionally controlled to the ACR queue in the local storage. Or, proportionally sent to the second billing data function unit.

The following is described in conjunction with the example shown in FIG. 2. FIG. 2 is an offline charging according to an embodiment of the present invention. A flowchart of a Diameter overload control method on an interface, wherein the primary CDF corresponds to the first CDF, and the secondary CDF corresponds to the second CDF. The primary CDF and the secondary CDF are Diameter servers, and the core network element is a Diameter client. The ACR in the current session is the new ACR, and the ACR in the historical session is the old ACR. As shown in FIG. 2, the method in this embodiment includes the following steps:

Step S201: During the session of the user equipment (UE, User Equipment), the charging trigger message (ACR) is normally sent to the CDF at the charging trigger point (CTF), and the CDF processes normally and returns a charging request response message (ACA). The identifier information supporting the Diameter Overload Indication Conveyance (DOIC) is carried in the ACR message.

In step S202, the primary CDF can determine the load status, for example, according to the occupancy rate of the central processing unit (CPU) and the pre-configured three-level overload threshold of the operator (for example, the three-level overload threshold may be the overload control start threshold, The session rejection threshold and the total session rejection threshold are used to perform an overload judgment and response message, which may be: if the load is found to be in the primary overload control interval (eg, overload control start threshold <CPU occupancy <session rejection threshold), the combination is carried in the response message. Type AVP (Attribute-Value-Pair) overload report: OC-OLR (Overload Control-Overload Report) and fill in OC-Reduction-Percentage (% reduction of overload control) The value and overload control level information (mainly involved in the primary overload control in Figure 2), and the overload control algorithm for charging is carried in the OC-OLR. The overload control algorithm identifier here is different from the default overload control algorithm (Loss Algorithm) of DOIC, because for the operator as the important operational data, the charging message cannot be discarded at will, so the overload control algorithm required by the CDF is applicable to the meter. The caching algorithm of the fee interface, and bring this identifier back to the CTF in the response message.

In step S203, the primary CDF sends a Diameter Accounting Response message containing the overload report message OC-OLR to the CTF.

Step S204, the CTF normally routes the old ACR message (such as: ACR [Interim] and ACR [Stop]) to the CDF, and the CTF receives the reduced percentage information (such as: OC-Reduction-Percentage) containing the overload control, and the overload control level. After the information and the response message identified by the required overload control algorithm, it was found that primary overload control was required. The CTF performs a charging overload control algorithm for all new ACR messages (new ACR [Start] and corresponding subsequent ACR [Interim] and ACR [Stop]), such as: Proportional random buffering of new ACR messages: when there is a secondary CDF When the CTF will be all The new ACR message (ACR[Start] and the corresponding subsequent ACR[Interim] and ACR[Stop]) are forwarded to the secondary CDF, and when there is no secondary CDF, the CTF caches all new ACR messages.

Step S205, the CTF sends the Diameter Accounting Request message ACR containing the DOIC charging identifier information to the second charging data function unit, that is, the secondary CDF in FIG. Wherein, when there is a secondary CDF, the CTF forwards all new ACR messages (ACR[Start] and corresponding subsequent ACR[Interim] and ACR[Stop]) to the secondary CDF.

Step S206, the CTF receives the Diameter Accounting Response message, where the charging response message ACA includes overload report information OC-OLR.

Step S207, after the overload control of the above steps, if the OC-Reduction-Percentage in the overload report AVP: OC-OLR returns to the normal range without control, the overload state of the charging interface Rf is released, and the core network element will cache the queue. The ACR messages in the order are sent out in order.

Through the above steps, the degree of overload is light, and the ACR queue to be sent sent to the first charging data function unit after the ACR in the current session may be cached to the ACR queue in the local storage; or proportionally The ACR to be sent sent to the primary charging data function unit after the ACR in the current session is sent to the secondary charging data function unit. Therefore, the control mode can be dynamically selected according to the overload level, and the problem of low flexibility of the overload control due to the single Diameter overload control mode in the related art is avoided.

In an optional implementation manner, when the overload level is the intermediate overload level, step S108 can also be implemented by the following steps:

Step S41, the current session and the ACR to be sent in the historical session are cached in proportion to the ACR queue in the local storage; or

Step S42, the current session and the ACR to be sent in the historical session are sent to the second charging data function unit in proportion.

Optionally, in this embodiment, if the overload level is a medium overload level, the current ACR to be sent is the ACR [Start] in the current session and the subsequent ACR [interim] and ACR of the ACR [Start]. [Stop], or subsequent ACR [interim] and ACR[Stop] in a history session, the overload control operation is performed proportionally. For example, if the current ACR is ACR[Start] in the current session and subsequent ACR[interim] and ACR[Stop] of the ACR[Start], or subsequent in the history session When ACR[interim] and ACR[Stop], the current ACR is proportionally controlled to the ACR queue in the local storage, or is proportionally sent to the second charging data function unit.

The following is a description of the example shown in FIG. 3. FIG. 3 is a second flowchart of a Diameter overload control method on an offline charging interface according to an embodiment of the present invention, wherein a primary CDF corresponds to a first CDF, and a secondary CDF corresponds to a second CDF. . The primary CDF and the secondary CDF are Diameter servers, and the core network element is a Diameter client. The ACR in the current session is a new ACR, and the ACR in the historical session is the old ACR. As shown in FIG. 3, the method in this embodiment includes the following steps:

In step S301, during the session of the UE, the charging trigger message (ACR) is normally sent to the CDF at the charging trigger point (CTF), and the CDF processes normally and returns an accounting response message (ACA). The identifier information supporting the Diameter Overload Indication Conveyance (DOIC) is carried in the ACR message.

In step 302, the CDF can determine the load condition, for example, according to the CPU occupancy rate and the operator's pre-configured three-level overload threshold (for example, the three-level overload threshold can be the overload control start threshold, the session rejection threshold, and the total session rejection threshold). The judgment and response message may be: if the load is found to be in the intermediate overload control interval (eg, session rejection threshold ≤ CPU occupancy < all session rejection threshold), carrying the combined AVP overload report in the response message: OC-OLR and filling in the OC -Reduction-Percentage value and overload control level information (this refers to intermediate overload control), and carry the overload control algorithm for charging in OC-OLR. The overload control algorithm identifier here is different from the DOIC default overload control algorithm Loss Algorithm, because the billing message cannot be discarded at will as an important operational data for the operator, so the overload control algorithm required by the CDF is applicable to the billing interface. The caching algorithm and bring this identifier back to the CTF in the response message.

Step S303, the CDF sends a Diameter Accounting Response message containing the overload report information OC-OLR to the CTF.

Step S304, after receiving the reduction percentage information (such as: OC-Reduction-Percentage) of the overload control, the overload control level information, and the response message of the required overload control algorithm identifier, the CTF finds that intermediate overload control is required. The CTF performs a charging overload control algorithm that does not send part of the old ACR messages (old ACR [Interim] and ACR [Stop]) to the CDF; the algorithm here is the CTF cache part of the old ACR message (old ACR [Interim] ] and ACR[Stop]). Wherein, the algorithm may be, for example, using a random algorithm to generate a number between 1 and 100, when the obtained value is small The ACR message is buffered when it is equal to or equal to the OC-Reduction-Percentage numerator. When a numerator with a value greater than OC-Reduction-Percentage is obtained, the CTF normally routes the ACR message to the CDF. .

Step S305, after the overload control, if the overload report AVP: OC-Reduction-Percentage in the OC-OLR returns to the normal range without control, the overload state of the charging interface Rf is released, and the core network element will cache the queue. ACR messages are sent out in order.

Through the above steps, it is realized that the control mode can be dynamically selected according to the overload level, and the overload is effectively controlled.

In an optional implementation manner of the embodiment of the present invention, when the overload level is the advanced overload level, step S108 can also be implemented by the following method:

Step S51: All the ACRs to be sent in the current session and the historical session are cached in the ACR queue in the local storage; or

Step S52: All the ACRs to be sent in the current session and the historical session are sent to the second charging data function unit.

Optionally, in this embodiment, if the overload level is an advanced overload level, the current ACR to be sent is the ACR [Start] in the current session and the subsequent ACR [interim] and ACR of the ACR [Start]. [Stop], or subsequent ACR [interim] and ACR[Stop] in a history session, the overload control operation is performed proportionally. For example, if the current ACR is ACR[Start] in the current session and subsequent ACR[interim] and ACR[Stop] of the ACR[Start], or subsequent ACR[interim] and ACR[Stop] in the history session, then Directly controlling the current ACR cache to the ACR queue in the local storage, or directly to the second charging data function unit.

The following is a description of the example shown in FIG. 4. FIG. 4 is a third flowchart of a Diameter overload control method on an offline charging interface according to an embodiment of the present invention, wherein a primary CDF corresponds to a first CDF, and a secondary CDF corresponds to a second CDF. . The primary CDF and the secondary CDF are Diameter servers, and the core network element is a Diameter client. The ACR in the current session is a new ACR, and the ACR in the history session is the old ACR. As shown in FIG. 4, the method provided in this embodiment includes the following steps:

In step S401, during the session of the UE, the charging trigger message (ACR) is normally sent to the CDF at the charging trigger point (CTF), and the CDF processes normally and returns an accounting response message (ACA). The identifier information supporting the Diameter Overload Indication Conveyance (DOIC) is carried in the ACR message.

In step S402, the CDF can determine the load condition, for example, according to the occupancy rate of the CPU and the pre-configured three-level overload threshold of the operator (for example, the three-level overload threshold can be the overload control start threshold, the session rejection threshold, and the total session rejection threshold). The judgment and response message may be: if the load is found to be in the advanced overload control interval (eg, CPU occupancy ≥ all session rejection threshold), carry the combined AVP overload report in the response message: OC-OLR and fill in OC-Reduction-Percentage The value and overload control level information (this refers to advanced overload control), and carries the overload control algorithm for charging in the OC-OLR. The overload control algorithm identifier here is different from the DOIC default overload control algorithm Loss Algorithm, because the billing message cannot be discarded at will as an important operational data for the operator, so the overload control algorithm required by the CDF is applicable to the billing interface. The caching algorithm and bring this identifier back to the CTF in the response message.

Step S403, the CDF sends a Diameter Accounting Response message containing the overload report information OC-OLR to the CTF.

Step S404, after receiving the reduction percentage information (such as: OC-Reduction-Percentage) of the overload control, the overload control level information, and the response message of the required overload control algorithm identifier, the CTF finds that advanced overload control is required. The CTF performs a charging overload control algorithm that does not send all ACR messages to the CDF. The algorithm here is that the CTF uses a random algorithm to cache all ACR messages.

Step S405, after the overload control, if the overload report AVP: OC-Reduction-Percentage in the OC-OLR returns to the normal range without control, the overload state of the charging interface Rf is released, and the core network element will cache the queue. ACR messages are sent out in order.

Through the above steps, it is further realized that the control mode can be dynamically selected according to the overload level, and the overload is effectively controlled.

It should be noted that the foregoing three optional implementation manners of step S108 are overload control embodiments corresponding to the overload level, but are not limited thereto. It can also be a holistic approach to integrated use.

In an optional implementation manner, the overload indication information further includes a network element list corresponding to the overload level, where the network element list includes a network of the network element to be overload controlled that matches the corresponding overload level. Meta logo.

Optionally, after step S104, the foregoing method further includes the following steps:

Step S61, determining whether the network element identifier of the current network element where the current session is located is included in the network element list carried by the overload indication information;

Step S62: If the network element identifier of the current network element where the current session is located is included in the network element list carried by the overload indication information, perform an overload control operation on the current network element.

Through step S61 and step S62, overload control of the core network element is implemented. For example, when the CTF finds that an ACR request message is from a network element to be overloaded according to the received network element list to be overloaded, the CTF performs a charging overload control algorithm, and does not send a partial ACR message to the CDF proportionally.

In an optional implementation manner, after the charging request message ACR in the current session is sent to the first charging data function unit, the method further includes the following steps:

Step S71: The first charging data function unit determines an overload level of the current first charging data function unit according to the current load quantity, and carries the current overload level in the ACA of the ACR.

In an optional implementation manner, step S71 includes: if the current load amount of the first billing data function unit is between the pre-configured first predetermined threshold and the second predetermined threshold, the current overload level is the primary overload level. If the current load amount of the first charging data function unit is between the pre-configured second predetermined threshold and the third predetermined threshold, the current overload level is a medium overload level; if the current charging data function unit current load The amount is greater than the pre-configured third predetermined threshold, and the current overload level is the advanced overload level; wherein the first predetermined threshold is less than the second predetermined threshold, and the second predetermined threshold is less than the third predetermined threshold.

It should be noted that the overload control start threshold, the session rejection threshold, and the total session rejection threshold in FIG. 5 respectively correspond to the first predetermined threshold, the second predetermined threshold, and the third predetermined threshold in step S71.

The following is a description of the example shown in FIG. 5. FIG. 5 is a flowchart 4 of a Diameter overload control method on an offline charging interface according to an embodiment of the present invention, wherein a primary CDF corresponds to a first CDF, and a secondary CDF corresponds to a second CDF. . The primary CDF and the secondary CDF are Diameter servers, and the core network element is a Diameter client. As shown in FIG. 5, the method in this embodiment includes the following steps:

Step S501: During the session of the UE, the charging triggering point (CTF) is normally sent. The request message (ACR) to the CDF, the CDF processes normally and returns an Accounting Response Message (ACA). The identifier information supporting the Diameter Overload Indication Conveyance (DOIC) is carried in the ACR message.

In step S502, the CDF can determine the load condition, for example, according to the CPU occupancy rate and the operator's pre-configured three-level overload threshold (for example, the three-level overload threshold can be the overload control start threshold, the session rejection threshold, and the total session rejection threshold). The judgment may be: when the overload control start threshold <CPU occupancy <session rejection threshold, it is a primary overload; when the session rejection threshold ≤ CPU occupancy < all session rejection threshold, it is an intermediate overload; when the CPU occupancy ≥ all sessions When the threshold is rejected, it is an advanced overload. Carry the combined AVP overload report in the response message: OC-OLR and fill in the value of OC-Reduction-Percentage and the overload control level information (primary overload, intermediate overload or advanced overload), and the list of network elements to be overload controlled (eg : Corresponding to the primary, overload, and advanced overload matching three low, medium, and high charging priority network element lists) and carrying the overload control algorithm for charging in the OC-OLR. The overload control algorithm identifier here is different from the DOIC default overload control algorithm Loss Algorithm, because the billing message cannot be discarded at will as an important operational data for the operator, so the overload control algorithm required by the CDF is applicable to the billing interface. The caching algorithm and bring this identifier back to the CTF in the response message.

Step S503, the CDF sends a Diameter Accounting Response message containing the overload report information OC-OLR to the CTF.

Step S504: When the CTF finds that an ACR request message is from the network element to be overloaded according to the received network element list to be overloaded, the CTF performs a charging overload control algorithm, and does not send part of the ACR message to the CDF proportionally: For example, using a random algorithm to generate a number between 1 and 100, when a numerator with a value less than or equal to OC-Reduction-Percentage is obtained, the ACR message is cached, and when a numerator with a value greater than OC-Reduction-Percentage is obtained, The CTF normally routes this ACR message to the CDF. For new ACR messages (new ACR[Start] and subsequent ACR[Interim] and ACR[Stop]), when there is a secondary CDF in the network, the CTF can add the new ACR [Start] to be cached and the corresponding subsequent ACR. The message is sent to the secondary CDF.

Step S505, when there is a secondary CDF, then the CTF forwards all new ACR messages (ACR[Start] and corresponding subsequent ACR[Interim] and ACR[Stop]) to the secondary CDF;

Step S506, the CTF receives the ACA message from the secondary CDF.

Step S507, after the overload control, if the overload report AVP: OC-Reduction-Percentage in the OC-OLR returns to the normal range without control, the overload state of the charging interface Rf is released, and the core network element will cache the queue. ACR messages are sent out in order.

Through the above steps, the technical effect that the overload control can be performed according to the network element calculation priority is realized.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform, or by hardware, but in many cases, the former is more Good implementation. Based on such understanding, the technical solution of the present application, which is essential or contributes to the related art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, CD-ROM). The instructions include a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present application.

Embodiment 2

In this embodiment, an overload control device for the charging request message is provided, and the device is used to implement the foregoing embodiment and the optional implementation manner, and details are not described herein. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 6 is a structural block diagram of an overload control apparatus for a charging request message according to an embodiment of the present invention. As shown in FIG. 6, the apparatus includes:

The sending module 62 is configured to send a charging request message (ACR) in the current session to the first charging data function unit;

The first obtaining module 64 is configured to obtain the overload indication information from the charging response message (ACA) of the ACR sent by the first charging data function unit, where the overload indication information carries at least an overload level and an overload control identifier;

The second obtaining module 66 is configured to acquire, according to the overload level, a session identifier of the target session that needs to perform overload control;

The first processing module 68 is configured to follow the overload control mode indicated by the overload control flag. And performing an overload control operation on the to-be-sent ACR in the target session indicated by the session identifier, where the overload control operation is at least used to indicate that the ACR to be sent in the target session is not sent to the first charging data function unit.

Optionally, in this embodiment, the overload control apparatus of the foregoing charging request message may be, but is not limited to, applied to a Diameter overload control process, which is different from the related art in that the cached ACR is sent after every predetermined waiting time. Diameter overload control is implemented, but different overload control modes are adopted for different overload levels, which avoids the problem of low flexibility of overload control due to the single Diameter overload control mode in the related art.

Optionally, in this embodiment, the foregoing ACR may include, but is not limited to, identifier information that supports Diameter Overload Indication Conveyance (DOIC).

Optionally, in this embodiment, the embodiment of the present invention provides that when the first CDF (Primary CDF) and the second CDF (Secondary CDF) are deployed in the network, the CTF may choose to cache the first proportionally. The new billing request message ACR[Start] and subsequent ACR[Interim] and ACR[Stop] are forwarded to the auxiliary CDF, thereby avoiding the problem of overload of the main CDF.

The device sends the ACR in the current session to the first charging data function unit, and obtains the overload indication information from the ACA of the ACR sent by the first charging data function unit, where the overload indication information carries at least an overload level. And an overload control identifier; obtaining, according to the overload level, a session identifier of the target session that needs to be overloaded; performing an overload on the ACR to be sent in the target session indicated by the session identifier according to the overload control mode indicated by the overload control identifier Control operation, wherein the overload control operation is at least for indicating that the ACR to be transmitted in the target session is not sent to the first charging data function unit. That is, the device, by acquiring the overload control identifier, and then transmitting the ACR to be sent to the first charging data function unit after the ACR in the target session indicated by the session identifier by the overload control mode indicated by the overload control identifier The overload control operation is performed, and unlike the related art, the Diameter overload control is implemented by transmitting the buffered ACR after every predetermined waiting time. That is to say, the above-mentioned steps solve the problem that the overload control is less flexible due to the single Diameter overload control mode, and the effect of optimizing the overload control is realized.

FIG. 7 is a structural block diagram 1 of an overload control apparatus for a charging request message according to an embodiment of the present invention. As shown in FIG. 7, the first processing module 68 in the apparatus includes at least one of the following:

The first buffer unit 72 is configured to cache the to-be-sent ACR in the target session to the ACR queue in the local storage.

The second buffer unit 74 is configured to cache all the ACRs to be sent in the target session into the ACR queue in the local storage;

The first sending unit 76 is configured to send the to-be-sent ACR in the target session to the second charging data function unit in proportion;

The second sending unit 78 is configured to send all the ACRs to be sent in the target session to the second charging data function unit.

Through the foregoing device, the ACR to be sent in the target session is cached in the local memory ACR queue by a certain percentage, so that after the overload state is eliminated, the ACR queue in the local storage is sequentially read, because for the operator As important operational data, billing messages cannot be discarded at will. And for the above-mentioned steps, the proportion of the ACR to be sent in the target session is proportional or full. The part is sent to the second charging data function unit, which can effectively prevent the first charging data unit from being overloaded.

FIG. 8 is a structural block diagram 2 of an overload control apparatus for a charging request message according to an embodiment of the present invention. As shown in FIG. 8, the second obtaining module 66 includes:

The first obtaining unit 82 is configured to acquire the first session identifier of the current session as the session identifier of the target session if the overload level is the primary overload level;

The second obtaining unit 84 is configured to acquire, as the intermediate overload level, the first session identifier of the current session and the second session identifier of the historical session before the current session as the session identifier of the target session;

The third obtaining unit 86 is configured to acquire, as the advanced overload level, the first session identifier of the current session and the second session identifier of the historical session before the current session as the session identifier of the target session.

It should be noted that, in this embodiment, the initial ACR message ACR[START] in the above historical session may be, but is not limited to, generated before the overload occurs, the initial ACR message ACR[START] in the current session may include but not Limited to occur after an overload occurs. That is, the start ACR message ACR[START] of the historical session in the CTF is generated before the start ACR message ACR[START] of the current session.

If the overload level is the primary overload level, the overload control operation is performed proportionally only if the current ACR is the ACR [Start] in the current session and the subsequent ACR [interim] and ACR [Stop] of the ACR [Start].

If the overload level is a medium overload level, then the current ACR is the ACR [Start] in the current session and the subsequent ACR [interim] and ACR [Stop] of the ACR [Start] and the subsequent ACR [interim] in the historical session. And ACR[Stop], the overload control operation is performed proportionally.

If the overload level is an advanced overload level, then the current ACR is the ACR [Start] in the current session and the subsequent ACR [interim] and ACR [Stop] of the ACR [Start] and the subsequent ACR [interim] in the historical session. And ACR[Stop], all perform overload control operations.

Through the device, the target session identifier can be dynamically selected according to the overload level, thereby achieving the effect of effective overload control.

FIG. 9 is a structural block diagram 3 of an overload control apparatus for a charging request message according to an embodiment of the present invention. As shown in FIG. 9, the first processing module 68 further includes:

The third buffer unit 92 is configured to cache the ACR to be sent in the current session to the ACR queue in the local storage in proportion when the overload level is the primary overload level; or

The third sending unit 94 is configured to send the ACR to be sent in the current session to the second charging data function unit proportionally when the overload level is the primary overload level.

If the overload level is the primary overload level, the overload control is performed proportionally only if the current ACR to be transmitted is the ACR [Start] in the current session and the subsequent ACR [interim] and ACR [Stop] of the ACR [Start]. operating. For example, if the current ACR is ACR[Start] in the current session and subsequent ACR[interim] and ACR[Stop] of the ACR[Start], the current ACR is proportionally controlled to the ACR queue in the local storage. Or, proportionally sent to the second billing data function unit.

The following is described in conjunction with the example shown in FIG. 2, in which the primary CDF corresponds to the first CDF and the secondary CDF corresponds to the second CDF. The ACR in the current session is the new ACR, and the ACR in the historical session is the old ACR. As shown in Figure 2, the device involves the following process:

Step S201: During the session of the UE, the charging trigger message (ACR) is normally sent to the CDF at the charging trigger point (CTF), and the CDF processes normally and returns a charging request response message (ACA), where, in the ACR message. Carrying identification information supporting Diameter Overload Indication Conveyance (DOIC).

In step S202, the primary CDF can determine the load condition, for example, according to the occupancy rate of the CPU and the pre-configured three-level overload threshold of the operator (for example, the three-level overload threshold may be an overload control start threshold, a session rejection threshold, and a total session rejection threshold). The overload judgment and response message may be: if the load is found to be in the primary overload control interval (eg, overload control start threshold <CPU occupancy <session rejection threshold), the combined AVP overload report is carried in the response message: OC-OLR and Fill in the OC-Reduction-Percentage value and overload control level information (mainly involved in the primary overload control in Figure 2), and carry the overload control algorithm for charging in the OC-OLR. The overload control algorithm identifier here is different from the DOIC default overload control algorithm Loss Algorithm, because the billing message cannot be discarded at will as an important operational data for the operator, so the overload control algorithm required by the CDF is applicable to the billing interface. Caching algorithm and identifying this in response message Brought back to CTF.

Step S204, the CTF normally routes the old ACR message (such as: ACR [Interim] and ACR [Stop]) to the CDF, and the CTF receives the reduced percentage information (such as: OC-Reduction-Percentage) containing the overload control, and the overload control level. After the information and the response message identified by the required overload control algorithm, it was found that primary overload control was required. The CTF performs a charging overload control algorithm for all new ACR messages (new ACR [Start] and corresponding subsequent ACR [Interim] and ACR [Stop]), such as: Proportional random buffering of new ACR messages: when there is a secondary CDF The CTF forwards all new ACR messages (ACR[Start] and corresponding subsequent ACR[Interim] and ACR[Stop]) to the secondary CDF, and the CTF caches all new ACR messages when there is no secondary CDF.

Step S207, after the overload control of the above process, if the OC-Reduction-Percentage in the overload report AVP:OC-OLR returns to the normal range without control, the overload state of the charging interface Rf is released, and the core network element will cache the queue. The ACR messages in the order are sent out in order.

With the above device, the degree of overload is light, and the ACR queue to be sent sent to the first charging data function unit after the ACR in the current session may be cached to the ACR queue in the local storage; or proportionally The ACR to be sent sent to the first charging data function unit after the ACR in the current session is sent to the secondary charging data function unit. Therefore, the control mode can be dynamically selected according to the overload level, and the problem of low flexibility of the overload control due to the single Diameter overload control mode in the related art is avoided.

Through the above steps, it is realized that the control mode can be dynamically selected according to the overload level, thereby avoiding the problem that the Diameter overload control mode is single in the related art.

FIG. 10 is a structural block diagram of an overload control apparatus for a charging request message according to an embodiment of the present invention. As shown in FIG. 10, the first processing module 68 further includes:

The fourth buffer unit 102 is configured to cache the current session and the ACR to be sent in the historical session to the ACR queue in the local storage in proportion when the overload level is the intermediate overload level; or

The fourth sending unit 104 is configured to, when the overload level is the intermediate overload level, send the current session and the ACR to be sent in the historical session to the second charging data function unit in proportion.

If the overload level is a medium overload level, the current ACR to be transmitted is ACR[Start] in the current session and subsequent ACR[interim] and ACR[Stop] of the ACR[Start], or subsequent in the historical session. The overload control operation is performed proportionally when ACR[interim] and ACR[Stop]. For example, if the current ACR is ACR[Start] in the current session and subsequent ACR[interim] and ACR[Stop] of the ACR[Start], or subsequent ACR[interim] and ACR[Stop] in the history session, then The current ACR cache is proportionally controlled to the ACR queue in the local storage, or is proportionally sent to the second charging data function unit.

The following is described in conjunction with the example shown in FIG. 3, in which the primary CDF corresponds to the first CDF and the secondary CDF corresponds to the second CDF. The ACR in the current session is the new ACR, and the ACR in the historical session is the old ACR. As shown in Figure 3, the device involves the following process:

In step S302, the CDF can determine the load condition, for example, according to the occupancy rate of the CPU and the pre-configured three-level overload threshold of the operator (for example, the three-level overload threshold can be the overload control start threshold, the session rejection threshold, and the total session rejection threshold). The judgment and response message may be: if the load is found to be in the intermediate overload control interval (eg, session rejection threshold ≤ CPU occupancy < all session rejection threshold), carrying the combined AVP overload report in the response message: OC-OLR and filling in the OC -Reduction-Percentage value and overload control level information (this refers to intermediate overload control), and carry the overload control algorithm for charging in OC-OLR. The overload control algorithm identifier here is different from the DOIC default overload control algorithm Loss Algorithm because for the operator As important operational data, the charging message cannot be discarded at will, so the overload control algorithm required by the CDF is a caching algorithm applicable to the charging interface, and this identifier is brought back to the CTF in the response message.

Step S304, after receiving the reduction percentage information (such as: OC-Reduction-Percentage) of the overload control, the overload control level information, and the response message of the required overload control algorithm identifier, the CTF finds that intermediate overload control is required. The CTF performs a charging overload control algorithm that does not send part of the old ACR messages (old ACR [Interim] and ACR [Stop]) to the CDF; the algorithm here is the CTF cache part of the old ACR message (old ACR [Interim] ] and ACR[Stop]). The algorithm may be, for example, using a random algorithm to generate a number between 1 and 100, and when the obtained value is less than or equal to the OC-Reduction-Percentage numerator, the ACR message is cached. When a numerator with a value greater than OC-Reduction-Percentage is obtained, the CTF normally routes the ACR message to the CDF.

Through the above device, it is further realized that the control mode can be dynamically selected according to the overload level, and the overload is effectively controlled.

11 is a block diagram 5 of a structure of an overload control apparatus for a charging request message according to an embodiment of the present invention. As shown in FIG. 11, the first processing module 68 further includes:

The fifth buffer unit 112 is configured to cache all the ACRs to be sent in the current session and the historical session to the ACR queue in the local storage when the overload level is the advanced overload level; or

The fifth sending unit 114 is configured to send all the ACRs to be sent in the current session and the historical session to the second charging data function unit when the overload level is the advanced overload level.

If the overload level is an advanced overload level, the current ACR to be transmitted is ACR[Start] in the current session and subsequent ACR[interim] and ACR[Stop] of the ACR[Start], or subsequent in the historical session. The overload control operation is performed proportionally when ACR[interim] and ACR[Stop]. example For example, if the current ACR is ACR[Start] in the current session and subsequent ACR[interim] and ACR[Stop] of the ACR[Start], or subsequent ACR[interim] and ACR[Stop] in the history session, then Directly controlling the current ACR cache to the ACR queue in the local storage, or directly to the second charging data function unit.

The following is described in conjunction with the example shown in FIG. 4, in which the primary CDF corresponds to the first CDF and the secondary CDF corresponds to the second CDF. The ACR in the current session is the new ACR, and the ACR in the historical session is the old ACR. As shown in FIG. 4, the device involves the following process:

Step S405, after the overload control, if the overload report is in the AVP: OC-OLR OC-Reduction-Percentage returns to the normal range without control, indicating that the overload state of the charging interface Rf is released, and the core network element sends the ACR message in the buffer queue in order.

Optionally, the overload indication information further includes a network element list corresponding to the overload level, where the network element list includes a network element identifier of the network element to be overload controlled that matches the corresponding overload level.

FIG. 12 is a structural block diagram 6 of an overload control apparatus for a charging request message according to an embodiment of the present invention. As shown in FIG. 12, the apparatus includes:

The determining module 122 is configured to determine whether the network element identifier of the current network element where the current session is located is included after the first obtaining module 64 obtains the overload indication information in the ACA of the ACR sent by the first charging data function unit. In the list of network elements carried by the overload indication information;

The second processing module 124 is configured to perform an overload control operation on the current network element if the network element identifier of the current network element where the current session is located is included in the network element list carried by the overload indication information.

Through the device, overload control of the core network element is realized. For example, when the CTF finds that an ACR request message is from a network element to be overloaded according to the received network element list to be overloaded, the CTF performs a charging overload control algorithm, and does not send a partial ACR message to the CDF proportionally.

13 is a structural block diagram of an overload control apparatus for a charging request message according to an embodiment of the present invention. As shown in FIG. 13, the apparatus includes:

The third processing module 132 is configured to receive, after the sending module 62 sends the ACR in the current session to the first charging data function unit, the ACA carrying the overload level from the first charging data function unit, where The overload level is determined by the first billing data function unit according to a current load amount.

Optionally, if the current load amount of the first billing data function unit is between the pre-configured first predetermined threshold and the second predetermined threshold, the current overload level is the primary overload level; The current load amount of the billing data function unit is located between the second predetermined threshold and the third predetermined threshold, and the current overload level is the intermediate overload level; if the first billing data function unit is current The load amount is greater than the pre-configured third predetermined threshold, then the current The overload level is the advanced overload level; wherein the first predetermined threshold is less than the second predetermined threshold, the second predetermined threshold being less than the third predetermined threshold.

The following description is made with reference to the example shown in FIG. 5. It should be noted that the overload control start threshold, the session rejection threshold, and the total session rejection threshold involved in FIG. 5 and the first predetermined threshold and the second predetermined threshold in step S71, respectively. The third predetermined threshold corresponds to that the primary CDF corresponds to the first CDF, and the secondary CDF corresponds to the second CDF. As shown in Figure 5, the device involves the following process:

Step S501: During the session of the UE, the charging trigger message (ACR) is normally sent to the CDF at the charging trigger point (CTF), and the CDF processes normally and returns an accounting response message (ACA). The identifier information supporting the Diameter Overload Indication Conveyance (DOIC) is carried in the ACR message.

Step S504: When the CTF finds that an ACR request message is from the network element to be overloaded according to the received network element list to be overloaded, the CTF performs a charging overload control algorithm, and does not send part of the ACR message to the CDF proportionally: For example, using a random algorithm to generate a number between 1 and 100, when a numerator with a value less than or equal to OC-Reduction-Percentage is obtained, the ACR message is sent. Cached up, when a numerator with a value greater than OC-Reduction-Percentage is obtained, the CTF normally routes the ACR message to the CDF. For new ACR messages (new ACR[Start] and subsequent ACR[Interim] and ACR[Stop]), when there is a secondary CDF in the network, the CTF can add the new ACR [Start] to be cached and the corresponding subsequent ACR. The message is sent to the secondary CDF.

Step S506, the CTF receives the ACA message from the secondary CDF.

It should be noted that the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are respectively located in multiple processes. In the device.

Embodiment 3

The embodiment of the invention further provides a computer readable storage medium. For the application scenarios and examples of the embodiment, refer to the foregoing Embodiment 1 and Embodiment 2, and details are not described herein. Optionally, in the embodiment, the computer readable storage medium may be configured to store program code for performing the following steps:

Step S1, sending an ACR in the current session to the first charging data function unit;

Step S2: Obtaining overload indication information from the ACA of the ACR sent by the first charging data function unit, where the overload indication information carries at least an overload level and an overload control identifier;

Step S3, acquiring, according to the overload level, a session identifier of a target session that needs to be subjected to overload control;

Step S4, performing an overload control operation on the to-be-sent ACR to be sent to the first charging data function unit in the target session indicated by the session identifier according to the overload control mode indicated by the overload control identifier, The overload control operation is at least used to indicate that all of the to-be-sent ACRs are not sent to the first charging data function unit.

Optionally, in this embodiment, the computer readable storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), and a mobile device. A variety of media that can store program code, such as hard disks, disks, or optical disks.

Optionally, in the embodiment, the processor performs the above steps S1 to S4 according to the program code stored in the computer readable storage medium.

For example, the examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

Those skilled in the art will appreciate that the above-described modules or steps of the present application can be implemented by a general-purpose computing device, which can be centralized on a single computing device or distributed over a network of multiple computing devices. They may be implemented by program code executable by the computing device such that they may be stored in the storage device for execution by the computing device and, in some cases, may be performed in a different order than that illustrated herein. Or the steps described, either separately as a single integrated circuit module, or as a single integrated circuit module. Thus, the application is not limited to any particular combination of hardware and software.

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

Industrial applicability

The embodiment of the present invention provides an overload control method and device for a charging request message, which overcomes the problem of low flexibility of overload control caused by a single Diameter overload control mode in the related art, thereby achieving different The overload level adopts different overload control modes to flexibly perform the effect of overload control.

Claims

An overload control method for a charging request message includes:

Sending a charging request message ACR in the current session to the first charging data function unit;

Obtaining the overload indication information from the charging response message ACA of the ACR sent by the first charging data function unit, where the overload indication information carries at least an overload level and an overload control identifier;

Obtaining, according to the overload level, a session identifier of a target session that needs to perform overload control;

Performing an overload control operation on the ACR to be sent in the target session indicated by the session identifier according to the overload control mode indicated by the overload control identifier, where the overload control operation is at least used to indicate that the The first charging data function unit transmits the ACR to be transmitted in the target session.
The method according to claim 1, wherein said performing an overload control operation on an ACR to be transmitted in said target session indicated by said session identifier according to an overload control mode indicated by said overload control flag, including the following At least one:

Proportionally buffering the to-be-sent ACR in the target session to an ACR queue in local storage;

Allocating the to-be-sent ACRs in the target session to an ACR queue in the local storage;

Transmitting the to-be-sent ACR in the target session to the second charging data function unit;

All the to-be-sent ACRs in the target session are sent to the second charging data function unit.
The method according to claim 2, wherein the obtaining the session identifier of the target session requiring overload control according to the overload level comprises:

If the overload level is a primary overload level, obtaining a first session identifier of the current session as a session identifier of the target session;

Obtaining a first session identifier of the current session if the overload level is a medium overload level And a second session identifier of the historical session before the current session as a session identifier of the target session;

If the overload level is an advanced overload level, obtain a first session identifier of the current session and a second session identifier of the historical session before the current session as a session identifier of the target session.
The method according to claim 3, wherein the overload level is a primary overload level, and the overload control mode indicated by the overload control flag is for the target session indicated by the session identifier. Send ACR to perform overload control operations, including:

Proportionally buffering the ACR to be sent in the current session to the ACR queue in the local storage; or

The ACR to be sent in the current session is sent to the second charging data function unit in proportion.
The method according to claim 3, wherein the overload level is a medium overload level, and the overload control mode indicated by the overload control flag is for the target session indicated by the session identifier. Send ACR to perform overload control operations, including:

Proportionally buffering the current session and the ACR to be sent in the historical session to the ACR queue in the local storage; or

The current session and the ACR to be sent in the historical session are sent to the second charging data function unit in proportion.
The method according to claim 3, wherein the overload level is an advanced overload level, and the overload control mode indicated by the overload control flag is for the target session indicated by the session identifier. Send ACR to perform overload control operations, including:

Allocating all the ACRs to be sent in the current session and the historical session to the ACR queue in the local storage; or

Sending all the to-be-sent ACRs in the current session and the historical session to the second charging data function unit.
The method according to claim 3, wherein the overload indication information further carries a network element list corresponding to the overload level, wherein the network element list includes the corresponding The network element identifier of the network element to be overload controlled that matches the overload level.
The method of claim 7, after the obtaining the overload indication information in the ACA of the ACR sent by the first charging data function unit, the method further includes:

Determining whether the network element identifier of the current network element where the current session is located is included in the network element list carried by the overload indication information;

And if the network element identifier of the current network element where the current session is located is included in the network element list carried by the overload indication information, performing an overload control operation on the current network element.
The method of claim 3, after the sending the ACR in the current session to the first charging data function unit, the method further comprises:

Receiving an ACA carrying the overload level from the first charging data function unit, wherein the overload level is the first charging data function unit according to a current load amount.
The method according to claim 9, wherein if the current load amount of the first billing data function unit is between a pre-configured first predetermined threshold and a second predetermined threshold, the current overload level The primary overload level; if the current load amount of the first charging data function unit is between the second predetermined threshold and the third predetermined threshold, the current overload level is The intermediate overload level; if the current load amount of the first billing data function unit is greater than the pre-configured third predetermined threshold, the current overload level is the advanced overload level; The first predetermined threshold is less than the second predetermined threshold, and the second predetermined threshold is less than the third predetermined threshold.
An overload control device for a charging request message includes:

a sending module, configured to send a charging request message ACR in the current session to the first charging data function unit;

The first obtaining module is configured to obtain the overload indication information from the charging response message ACA of the ACR sent by the first charging data function unit, where the overload indication information carries at least an overload level and an overload control identifier;

a second obtaining module, configured to acquire, according to the overload level, a session identifier of a target session that needs to perform overload control;

a first processing module configured to follow an overload control mode indicated by the overload control flag, Performing an overload control operation on the to-be-sent ACR in the target session indicated by the session identifier, wherein the overload control operation is at least used to indicate that the target session is not sent to the first charging data function unit ACR to be sent.
The apparatus of claim 11 wherein said first processing module comprises at least one of:

a first cache unit, configured to scale the ACR to be sent in the target session to an ACR queue in a local storage;

a second buffer unit, configured to cache all the ACRs to be sent in the target session into an ACR queue in the local storage;

a first sending unit, configured to send the to-be-sent ACR in the target session to the second charging data function unit proportionally;

The second sending unit is configured to send all the to-be-sent ACRs in the target session to the second charging data function unit.
The apparatus of claim 12, wherein the second acquisition module comprises:

a first obtaining unit, configured to acquire a first session identifier of the current session as a session identifier of the target session, if the overload level is a primary overload level;

a second obtaining unit, configured to acquire a first session identifier of the current session and a second session identifier of the historical session before the current session as the session of the target session, if the overload level is a medium overload level Identification

a third obtaining unit, configured to acquire a first session identifier of the current session and a second session identifier of the historical session before the current session as the session of the target session, if the overload level is an advanced overload level Logo.
The apparatus of claim 13, wherein the first processing module further comprises:

a third buffer unit, configured to cache the ACR to be sent in the current session to the ACR queue in the local storage proportionally when the overload level is a primary overload level; or

And a third sending unit, configured to send the ACR to be sent in the current session to the second charging data function unit proportionally when the overload level is a primary overload level.
The apparatus of claim 13, wherein the first processing module further comprises:

a fourth buffer unit, configured to cache, in the current session and the historical session, the ACR to be sent to the ACR queue in the local storage when the overload level is a medium overload level; or ,

The fourth sending unit is configured to send the current session and the ACR to be sent in the historical session to the second charging data function unit according to a ratio when the overload level is a medium overload level.
The apparatus of claim 13, wherein the first processing module further comprises:

a fifth buffer unit, configured to cache all the ACRs to be sent in the current session and the historical session to the ACR queue in the local storage when the overload level is an advanced overload level; or

The fifth sending unit is configured to send all the to-be-sent ACRs in the current session and the historical session to the second charging data function unit when the overload level is the advanced overload level.
The device according to claim 13, wherein the overload indication information further carries a network element list corresponding to the overload level, wherein the network element list includes a matching with the corresponding overload level. The NE ID of the NE to be overloaded.
The apparatus of claim 17 further comprising:

a determining module, configured to determine, after the first obtaining module obtains the overload indication information in the ACA of the ACR sent by the first charging data function unit, the network element identifier of the current network element where the current session is located Whether it is included in the list of network elements carried in the overload indication information;

a second processing module, configured to perform overload control on the current network element if the network element identifier of the current network element where the current session is located is included in the network element list carried by the overload indication information operating.
The apparatus of claim 13 further comprising:

a third processing module, configured to receive, after the sending module sends the ACR in the current session to the first charging data function unit, the ACA carrying the overload level from the first charging data function unit, where The overload level is the first charging data function unit according to the current The amount of load is determined.
The apparatus according to claim 19, wherein if said current load amount of said first billable data function unit is between a pre-configured first predetermined threshold and a second predetermined threshold, said current overload level The primary overload level; if the current load amount of the first charging data function unit is between the second predetermined threshold and the third predetermined threshold, the current overload level is The intermediate overload level; if the current load amount of the first billing data function unit is greater than the pre-configured third predetermined threshold, the current overload level is the advanced overload level; The first predetermined threshold is less than the second predetermined threshold, and the second predetermined threshold is less than the third predetermined threshold.