CN104335539B - System for performing DIAMETER premature beats - Google Patents

System for performing DIAMETER premature beats Download PDF

Info

Publication number
CN104335539B
CN104335539B CN201380027543.6A CN201380027543A CN104335539B CN 104335539 B CN104335539 B CN 104335539B CN 201380027543 A CN201380027543 A CN 201380027543A CN 104335539 B CN104335539 B CN 104335539B
Authority
CN
China
Prior art keywords
diameter
overload
message
session
avp
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201380027543.6A
Other languages
Chinese (zh)
Other versions
CN104335539A (en
Inventor
A·B·罗奇
B·A·坎贝尔
S·E·马克默菲
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tekelec Global Inc
Original Assignee
Tekelec Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tekelec Inc filed Critical Tekelec Inc
Publication of CN104335539A publication Critical patent/CN104335539A/en
Application granted granted Critical
Publication of CN104335539B publication Critical patent/CN104335539B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H04L43/0882—Utilisation of link capacity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities

Abstract

According on one side, theme described herein includes the system for performing Diameter premature beats.The system is at Diameter routing nodes.The system includes the network interface for receiving Diameter message.The system also includes Diameter premature beats units, its overload conditions for being configured to the Diameter sessions that detection is associated with Diameter message, and the instruction of the overload conditions is delivered to the 2nd Diameter nodes using the Diameter message of the purposes for being defined for being different from premature beats.

Description

System for performing DIAMETER premature beats
Prioity claim
The U.S. Provisional Patent Application Serial No.61/624,237's submitted to this application claims on April 13rd, 2012 is preferential Power, during the disclosure of which is hereby incorporated by reference in their entirety.
Technical field
Theme described herein is related to the method and system for processing Diameter message.More specifically, herein Described theme is related to method, system and computer-readable medium for performing Diameter premature beats.
Background technology
Diameter be for computer network certification, authorize and (AAA) agreement that accounts, be the succession of Radius. Diameter basic agreements are the agreements defined in international engineering task (IETF) Request For Comments (RFC) 3588 Be hereby incorporated by reference in their entirety herein in.Diameter message is used per framework user, and with request-response message Form is present.Diameter response messages return to request source by using the same path of hop-by-hop transmission route request message.
Can be for exchanging Diameter message between the Diameter nodes for performing various functions.For example, mobility Management entity (MME) and home subscriber server (HSS) can be interacted, and for certification, be authorized and/or (AAA) use that accounts On the way.Because communication network performs diversified function using Diameter message, thereby it is ensured that Diameter nodes are Work correctly and like that as expected particularly significant.
It is accordingly, there are to the method for performing Diameter premature beats, system and computer-readable medium Demand.
The content of the invention
According on one side, theme described herein includes the system for performing Diameter premature beats.System At Diameter routing nodes.System includes the network interface for receiving Diameter message.System also includes Diameter premature beats units, its overload shape for being configured to the Diameter sessions that detection is associated with Diameter message Condition, and using the purposes for being defined for being different from premature beats Diameter message come by the instruction of the overload conditions It is delivered to the 2nd Diameter nodes.
Theme described herein can be realized with the software being combined with hardware and/or firmware.For example, this place is retouched The theme stated can be realized with the software by computing device.In an exemplary realization, theme described herein can To be realized using the computer-readable medium that have stored thereon computer executable instructions, held when by the processor of computer During row, the instruction control computer performs step.It is adapted to carry out the exemplary computer readable of theme described herein Medium includes non-transient (non-transitory) equipment, such as disk memory devices, chip memory devices, FPGA Device and application specific integrated circuit.Moreover, it is achieved that the computer-readable medium of theme described herein may be located at single setting In standby or calculating platform, or can be distributed across multiple equipment or calculating platform.
As used herein, term " node " refers to one or more processors and the physical computing of memory is put down Platform.
As used herein, term " function " or " module " refer to for realize feature described herein and hardware And/or the software that firmware is combined.
Brief description of the drawings
The preferred embodiment of theme described herein is illustrated referring now to each accompanying drawing, wherein, same reference is compiled Number represent same parts, wherein：
Fig. 1 be show an embodiment according to theme described herein for performing showing for Diameter premature beats The diagram of example property environment；
Fig. 2 is the exemplary Diameter premature beats information for showing the embodiment according to theme described herein Diagram；
Fig. 3 is the exemplary Diameter overload levels information for showing the embodiment according to theme described herein Diagram；
Fig. 4 be an embodiment according to theme described herein is shown with showing that Diameter premature beats are associated The diagram of example property message；
Fig. 5 is to show being associated with Diameter premature beats for another embodiment according to theme described herein The diagram of example message；And
Fig. 6 be show an embodiment according to theme described herein for performing showing for Diameter premature beats The flow chart of example property treatment.
Specific embodiment
According to theme described herein, there is provided by perform the system of Diameter premature beats, method and based on Calculation machine computer-readable recording medium.Advantageously, some aspects of described herein theme can be used for management Diameter overload (examples Such as, when flow or treatment load may or should be processed more than node) or other situations.For example, according to described herein This theme each side Diameter intermediaries (for example, Diameter routing nodes (DRN) or Diameter signalling route devices (DSR)) can determine that overload level (is for example monitored and/or reports construction, for describing, specifying, define and/or constraining overload Event and acted to each side concerned, the related premature beats of entity or region).In this example, can be by Diameter meetings Words are assigned to one or more Diameter overload levels, such as field (realm), using, main frame, overload packet, session or Connection.Depending on overload level, Diameter intermediaries can notify the situation of the overload related to overload level to give node (example Such as, start node), the node can mitigate or attempt to mitigate the overload related to overload level, such as by will be impacted Diameter message is sent to the node of another non-overloaded or stops impacted communication.Simultaneously will overload by using overload level Situation notified to interdependent node, some aspects of theme described herein can be used to mitigate overload or with overload The associated relevant issues of Diameter entities (such as application, node, packet, session, connection, field etc.), without showing Write the Diameter entities for influenceing other non-overloaded.
Now with detailed reference to the exemplary embodiment of theme described herein, theirs are shown in various figures Example.As possible, same or analogous part is just indicated using identical reference in whole accompanying drawing.
Fig. 1 be show an embodiment according to theme described herein for performing showing for Diameter premature beats The diagram of example property environment 100.Exemplary environments 100 can include one or more networks, it is possible to including one or more Diameter nodes, such as Diameter client 102-106, Diameter routing nodes (DRN) or Diameter intermediaries (DA) 108, and Diameter server 112-116.
Each in Diameter client 102-106 can be represented for from Diameter server 112-116 Any suitable entity that one or more are serviced is asked (for example, the calculating including at least one processor and memory is flat Platform).For example, Diameter client 102 can be sent for asking by the application of the master control of Diameter server 112 (host) The Diameter request messages of one or more services at place.Each in Diameter server 112-116 can table Show for any suitable entity for providing or performing one or more services for Diameter client 102-106 (for example, bag Include the calculating platform of at least one processor and memory).For example, Diameter server 112 can be in response to receiving simultaneously Process Diameter request messages and send Diameter response messages (for example, Diameter response messages).
Exemplary Diameter client 102-106 or Diameter server 112-116 can include mobile management Entity (MME), home subscriber server (HSS), Certificate Authority and (AAA) server that accounts, bearing binding and event report work( Can (BBERF), gateway (SGW), grouped data network gateway (PDN GW), charging data function (CDF), online charging system System, off-line accounting system, policy and charging enforcement function (PCEF), policy, billing and rule functional (PCRF), user profile Repository (SPR), Diameter intermediaries, network node, policy engine, strategic server, application function (AF), application service Device, Diameter signalings intermediary, Long Term Evolution (LTE) node, Internet Protocol (IP) IP multimedia subsystem, IMS (IMS) network section Point, server, associated nodes, node, database, SGW, gateway, monitoring node, Diameter message processor, data Collecting platform, multi-protocol signalings gateway, multi-protocol signalings router, or calculating platform.
DA 108 can be performed for any of the function of Diameter premature beats and/or correlation described herein Suitable entity.For example, DA 108 can with one or more processors and for receive or transmit one of message or Realized in the calculating platform of multiple network interfaces.The example of DA 108 can include but are not limited to DSR, DRN, Diameter In route intermediary, Diameter relayings intermediary, Diameter redirections intermediary, Diameter conversion intermediaries or Diameter agencies It is situated between.
DA 108 can be included for receiving, processing and/or routeing various message (for example, protocol data unit (PDU)) Function, it is possible to including the various communication interfaces for being communicated with Diameter nodes, such as third generation affiliate Plan (3GPP) LTE communication interface and other (such as non-LTE) communication interfaces.In certain embodiments, receive, treatment and/or Routing function can be included in one or more modules.For example, DA 108 can include or can access for receive with The associated Diameter signaling messages of multiple different Diameter signaling interfaces (such as S9, S6a, S11, Cx and Dx) One or more modules.
In certain embodiments, DA 108 can be by other Diameter interface Diameter messages.For example, DA 108 can be by following interface Diameter message：LTE interface, IMS interfaces, ietf specification interface, 3GPP specifications connect Mouth, third generation partner program 2 (3GPP2) Standard Interface, ETSI (ETSI) Standard Interface, international telecommunication Alliance (ITU) Standard Interface, package axle cable (PacketCable) Standard Interface, service forum (MSF) Standard Interface, Sh more connect Mouth, Dx, Ro interface, Rf interface, Sp interfaces, Gx interfaces, Rx interface, Gz interfaces, Gy interfaces, Gq interface, Zh interfaces, Dz connect Mouth, Zn interfaces, Ty interfaces, Tx interfaces, Dw interfaces, Wa interfaces, Wd interfaces, Wx interfaces, Wm interfaces, Wg interfaces, Pr interfaces, Gr connect Mouth, Gr+ interfaces, Gi interfaces, Wo interfaces, Wf interfaces, Re interfaces, S6 interfaces, S2 interfaces, SW interfaces, Sta interfaces, S7 interfaces, H2 Interface, E2 interfaces, E4 interfaces, E5 interfaces, A3 interfaces, A4 interfaces, Rr interfaces, Gq' interfaces, TC-6 interfaces, TC-7 interfaces, TC-8 Interface, TC-9 interfaces, TC-10 interfaces, TC-11 interfaces, DB-0 interfaces, DB-2 interfaces, BI-1 interfaces, LOC-1 interfaces, Rw connect Mouth, Pkt-mm-2 interfaces, P-CSCF-PAM interfaces, Pkt-laes-2 interfaces, MM10 interfaces, MZ interfaces, Gmb interfaces or Zn' connect Mouthful.
DA 108 can be with logical between convenient Diameter client 102-106 and Diameter server 112-116 Letter.For example, Diameter client 102 can be by Diameter request messages (for example, the request of Diameter session establishments disappears Breath) it is sent to DA 108.Diameter request messages can require that one or more are serviced from Diameter server 112.DA 108 can route, relay and/or change the request or sound between Diameter client 102 and Diameter server 112 Should.After receiving and processing Diameter request messages, Diameter server 112 can be by Diameter response messages (for example, Diameter session establishments response message) is sent to DA 108.Diameter response messages can in response to by The Diameter request messages that Diameter client 102 is produced.Diameter response messages can be provided and arrived by DA 108 Diameter client 102.
DA 108 or therein modules can perform one or many before Diameter message is provided to another node Individual function.For example, before Diameter response messages are provided to Diameter client 102, DA 108 or therein moulds Block can change Diameter message, and the modification is by the insertion in the Diameter message of modification or including Diameter mistakes Carry control information or other related data and make.In certain embodiments, Diameter premature beats information can be deposited One or more property values in the payload part of the Diameter message positioned at modification are stored up in (AVP).
DA 108 can include Diameter premature beats unit (DOC) 110.DOC 110 can be performed for Any suitable entity of the function of Diameter premature beats, overload management and/or correlation (is such as performed on a processor Module or software).For example, DOC 110 may be configured to control or attempt to mitigate overload or serviced with the Diameter of overload Device 112-116 associated other problemses.DOC 110 may be configured to determine one or more Diameter overload levels. Diameter overload levels can include field, using, main frame, overload packet, session or connection.For example, DOC 110 can be by Each Diameter session is assigned to overload packet, and overload packet is corresponding to the service request for being assigned to special session Diameter server.
In certain embodiments, DOC 110 can be based on the relation between network topology and session, node and topology, To determine the overload level to other nodes to be delivered.If for example, the connection from specific area cause overload, upwards The overload level for swimming transmission can be selected as " field ", to control the flow of (throttle) from the field.Another In individual example, if individually connection or session cause to overload and cause overload without other connections or session, overload Scope can be configured so that " connection " or " session ", with control come it is self-corresponding connection or session flow, while allowing it He connects or session continues transmitted traffic and need not control.
DOC 110 may be configured to monitor or detect from one or more Diameter nodes, field, using or its The overload of his entity.For example, DOC 110 can subscribe to Diameter server 112-116, or can periodically or non-week Phase property ground (for example, based on some factors dynamically) is to Diameter server 112-116 poll overload messages.In this example In, when the instruction that during DA 108 or DOC 110 receive Diameter server is overloaded, DA 108 or DOC 110 can point out disappearing for the Diameter for being overloaded overload packets to the transmission of each in Diameter client 102-106 Breath.
In certain embodiments, DOC 110 may be configured to that some information are provided or used based on hop-by-hop.Example Such as, as Diameter request messages are propagated through in a network, intermediate node can be removed and carried by previous node or previous dive The Diameter premature beats information (for example, storage is in Load-Info AVP) of confession, it is possible to overloaded using the Diameter Control information.In this example, intermediate node can be altered or modified the Diameter premature beats information that receives and can be with Some information changed are reinserted in the Load-Info AVP of their own, for example, is forwarding the message to another section Before point.
In certain embodiments, when to supporting that premature beats or the node of overload management send response, node (for example, One in DA 108 or Diameter server 112-116) one or more Load-Info AVP can be included, carried Carry the information of related and load correlation.In certain embodiments, it is if there is multiple Load-Info AVP, then each Load-Info AVP can be associated from different overload levels.
In certain embodiments, Diameter client 102-106 can be in response to understanding upstream node (for example, DA One in 108 or Diameter server 112-116) overloaded and taken various actions.Exemplary action can include one The request of a little types relative to the client first that other types asks, select the replacement peer-to-peer for treatment (for example, only Respect the overload attribute of the peer-to-peer), send error message or to fall to abandon or abandon Diameter message.In some implementations Example in, Diameter client 102-106 can according to provided premature beats information (such as overload measurement or Load reduction process provided in Overload-Control-Metric AVP) perform it is any necessary to shaping its flow Action.
In certain embodiments, Diameter client 102-106 can select it is most desired (for example, it is available most Low-load) Diameter server 112 when use Diameter premature beats information.
In certain embodiments, DA 108 can be in response to understanding upstream node (for example, Diameter server 112- One in 116) overloaded and taken various actions.Exemplary action can include instruction client executing, and one or more are moved Work, some type of request are relative to the peer-to-peer that the priorization, selection that other types are asked are substituted (as long as example, respect should The overload attribute of peer-to-peer), send error message (for example, DIAMETER_UNABLE_TO_DELIVER message, DIAMETER_ PEER_IN_OVERLOAD message, Diameter_TOO_BUSY message or transient fault message) or fall to abandon or abandon Diameter message.In certain embodiments, Diameter client 102-106 can be according to the premature beats information for being provided (measurement such as provided in Overload-Control-Metric AVP) is any necessary to shaping its flow to perform Action.
In certain embodiments, DA 108 can select it is desired (for example, available minimum load or minimum overload ) Diameter server 112 when use Diameter premature beats information.
In certain embodiments, DA 108 and/or other overload perceive nodes be configured for comprising The Diameter message of the AVP of Diameter premature beats information or correlation is quickly processed.For example, can ignore less normal The overload level and/or the AVP of correlation seen, or associated treatment can be blocked.
In certain embodiments, Diameters message can be constructed, to allow that intermediate node quickly determines message Whether comprising the related information of premature beats, for example, need not parse all AVP.For example, when Diameter premature beats information is deposited When new bit or order mark can be set in the header portion of Diameter message, or Diameter message can be by Load-Info AVP 200 are positioned as the AVP in its Diameter payload part.
Although Fig. 1 depicts DA 108 and is communicated with various Diameter nodes (for example, being received from these nodes Diameter message), however, it will be understood that DA 108 can be by extra and/or different interface, with the section described Point and other nodes (description) are communicated.It is further appreciated that DA 108 can include it is less, extra or different Module and/or component.
Fig. 2 is the exemplary Diameter premature beats information for showing the embodiment according to theme described herein Diagram.Exemplary Diameter premature beats information can be stored in Diameter message, it is possible to for perform with The associated one or more aspects of Diameter premature beats.For example, Diameter premature beats information can be stored in category During property value is to (AVP), such as Load-Info (load-information) AVP 200, it is possible to positioned at Diameter message data or In payload part.In certain embodiments, Load-Info AVP 200 can be packet or compound AVP, it is possible to One or more AVP comprising the information for storing premature beats information or correlation.
In certain embodiments, Diameter premature beats information or Load-Info AVP 200 can be inserted into respectively In kind Diameter message.For example, Load-Info AVP 200 can be included in from overload perceive or including DOC In the Diameter message of 110 Diameter nodes.
Embodiment with reference to shown in Fig. 2, Load-Info AVP 200 can include Load-Info headers AVP 202nd, Overload-Control-Metric (premature beats measurement) AVP 204, Overload-Information-Scope (overload messages scope) AVP 206, Supported-Scopes (scope supported) AVP 208, Overload-Control- Algorithm (overload control algorithms) AVP 210, Period-Of-Validity (effective period of time) AVP 212, conversation Or overload packet AVP 214, load AVP 216, and/or extra AVP 218.
Load-Info headers AVP 202 can include for identify Load-Info AVP 200 and/or correlation (for example Comprising) any information of AVP.For example, Load-Info headers AVP 202 can include header identifier and/or other letters Breath, such as points out AVP's included in the length or size or Load-Info AVP 200 of Load-Info AVP 200 The value of quantity.
Overload-Control-Metric AVP 204 can include for determine overload any information and/or Person can include load reduction process or other actions being associated with premature beats.Depending on load present level and/or The overload algorithm realized, the information provided in Overload-Control-Metric AVP 204 can be with difference.For example, When " message is fallen to abandon " algorithm is used, Overload-Control-Metric AVP 204 are it can be pointed out that should fall to abandon or do not send out The percentage of the request sent.In another example, when " speed control " algorithm is used, Overload-Control- Metric AVP 204 are it can be pointed out that the maximum quantity of the request that each second sends.In certain embodiments, in Overload- Information provided in Control-Metric AVP 204 can be to whole or in pointed Diameter overload levels A little requests are effective.
In certain embodiments, Overload-Control-Metric AVP 204 can use Unsigned32 data Type format.In certain embodiments, Overload-Control-Metric AVP 204 can be Load-Info AVP First (non-header) AVP in 200, it is possible to which each Load-Info AVP 200 just occurs once.
Overload-Information-Scope AVP 206 can comprising for determine Diameter overload levels or Any information (for example, Diameter overload levels information) of context, for example, can be used for which is pointed out to sender Diameter entity overload messages are related.For example, Overload-Information-Scope AVP 206 may indicate that The subset of the request that overload messages and/or premature beats process should be applied to.Overload-Information-Scope AVP 206 can include wide-style and detail section.In certain embodiments, Overload-Information-Scope AVP 206 can be second (non-header) AVP in Load-Info AVP 200, it is possible to each Load-Info AVP 200 Just occur once.Discussed with reference to Fig. 3 extra with what Overload-Information-Scope AVP 206 were associated Information.
Supported-Scopes AVP 208 can be included for pointing out that what can be supported (is such as saved by Diameter Point) Diameter overload levels any information.For example, Supported-Scopes AVP 208 it can be pointed out that such as field, Using the subset of the Diameter overload levels of, main frame, overload packet, session or connection.In certain embodiments, Supported-Scopes AVP 208 can be included in Capabilities-Exchange-Request (CER) message or In Capabilities-Exchange-Answer (CEA) message.
In certain embodiments, Supported-Scopes AVP 208 can use Unsigned64 data forms. Supported-Scopes AVP 208 can include the bitmap of the scope for pointing out to be supported by client.For example, for initial six The support of individual scope (such as field, using, main frame, overload packet, session or connection) can be enforceable, it is possible to not with Signal (be not included in bitmap).In this example, least significant bit may indicate that the support for the 7th scope, Each subsequent bit all represents another wide-style.In each embodiment using Unsigned64 data forms, Supported-Scopes AVP 208 can allow to support up to 72 scopes (including initial six scopes) altogether.At some In embodiment, new Diameter overload levels can be defined by extra extension.If not supporting spreading range, can save The Supported-Scopes AVP 208 slightly (such as from Load-Info AVP 200).
Overload-Control-Algorithm AVP 210 can be comprising for pointing out for reducing, breaking away from or mitigate The algorithm of load or any information of process.For example, Overload-Control-Algorithm AVP 210 are it can be pointed out that " disappear Breath loss " algorithm, wherein when node overload, node abandons the message for receiving.In another example, Overload- Control-Algorithm AVP 210 it can be pointed out that " speed control " algorithm, if wherein rate value beyond threshold value value or Scope, then restraining is transmitted or receiving velocity.In another example, Overload-Control-Algorithm AVP 210 can With point out indicate sender stop send communication or transmit a communication to another node for process algorithm.In some embodiments In, Overload-Control-Algorithm AVP 210 can be included in CER message or CEA message.
Period-Of-Validity AVP 212 can be included for pointing out that the node that overload is perceived should basis Diameter premature beats information operates any information how long.For example, Period-Of-Validity AVP 212 can To point out enforce one or more number of seconds for acting (for example, premature beats measurement or load reduction process).One In a little embodiments, Period-Of-Validity AVP 212 can be optional, or if Overload-Control- The non-zeros of Metric AVP 204 can be then required.
Overload packet AVP 214 can be comprising for identifying or associating independently of other Diameter overload level entities Or construction (for example field, main frame, using etc.) a conversation any information.For example, overload packet AVP 214 can be with Point out to apply, multiple Diameter messages that field or other scopes are independently reported or related session.In some implementations In example, overload packet AVP 214 can be optional, and/or Diameter requests in a session can occur Or in response.In certain embodiments, the Diameter overload packets for being identified in overload packet AVP 214 can be in a meeting Continue in the duration of words or multiple sessions constant.In certain embodiments, overload packet AVP 214 can be readable with user The text formatting for taking, such as UTF8 character strings (UTF8String) data form.
In certain embodiments, when Diameter nodes are for some requests but not all possible request overload, AVP 214 can be grouped with operating overload.For example, if DA 108 supports more than one field, DA 108 can be by flow It is routed to the group node and another group node for field " B " for field " A ".If field " A " server overload But field " B " server does not overload, then DA 108 effectively overloads for field A, but for field B nonoverloads.Herein In example, DA 108 may provide for the instruction of the overload of field " A " server so that originator node can perform one or Multiple action, with the load on field " A " server for mitigating overload.Similar situation is likely to appear in needs using outside Resource is used for some and applies but be not used in the node of other application.
Load AVP 216 can include any information for given load information or load metric.In some embodiments In, it is possible to use various algorithms generate load metric.Some algorithms can generate the utilization rate for reflecting most affined resource Load metric, and can be the linear expression of such utilization rate.For example, load metric may indicate that in Diameter sections Percentage used at point or available resource.In certain embodiments, load AVP 214 can use Unsigned32 Data type format, it is possible to including 0 and 232Numeral between -1 (4,294,967,295), loads for representing, wherein, 0 is " completely non-loaded ", 4,294,967,295 is " maximum capacity ".In certain embodiments, load AVP 214 can be optional , and/or can just occur once with every Load-Info AVP 200.
In certain embodiments, if load AVP 216 includes the value more than zero, overload procedure can be effective, can refer to Show client according to the overload control algorithms or process consulted to take action.In certain embodiments, if load AVP 216 It is not included in Load-Info AVP 200, then can uses the load value previously established.
In certain embodiments, when it is possible, it is possible to use load AVP 216 (and is not aligned avoiding overload scene Reacted in the overload situations for occurring).Information provided in load AVP 216 can also be used for several by peer-to-peer Selected in otherwise equivalent server.For example, the information provided in load AVP 216 can be answered as weighting factor Use the server selection algorithm that DA 108 is used.In another example, the information provided in load AVP 216 can be with It is used for independently realizing back off algorithm (for example, based on a certain preferable reception or transmission rate, returning or other technologies by peer-to-peer By message queueing).
Server Load SRV weights
A 10% 20
B 40% 20
C 80% 60
Table 1
In certain embodiments, the load information in load AVP 216 can be used to be distributed between various nodes and bear Carry.For example, it is contemplated that load information as shown in table 1 is delivered to DA 108 or Diameter by server " A ", " B " and " C " Client 102.Load information can be applied to name server by DA108 or Diameter client 102 as follows (DNS) service log (SRV) weight：Server " A "：(100%-10%) × 20=18, server " B "：(100%-60%) × 20=12, server " C "：(100%-80%) × 60=12.DA 108 or Diameter client 102 can be then according to This 18/12/12 measurement come distributed load (for example, 43% flow goes to server " A ", 28.5% go to server " B " and Each in " C ").In other examples, load value can be applied to any capacity weighted information, for example, being different from table 1 In DNS SVR weights information.
Extra AVP 218 can represent any other AVP for storing the related information of Diameter premature beats. For example, Load-Back-Up AVP process Diameter requests in the case of may indicate that for being changed into overload in present node disappearing The minor node of breath.
Although Fig. 2 depicts exemplary Diameter premature beats information, including Load-Info AVP 200 and it is various its He is AVP, it will be appreciated that some Diameter premature beats information can include less, extra or different AVP Or information.
Fig. 3 is the exemplary Diameter overload levels information for showing the embodiment according to theme described herein 300 diagram.Diameter overload levels information 300 can be stored in Diameter message, it is possible to for perform with The associated one or more aspects of Diameter premature beats.For example, Diameter overload levels information 300 can be stored Such as the property value of Overload-Information-Scope AVP 206 to (AVP) in, and may be located at Diameter In the data or payload part of message.In certain embodiments, Diameter overload levels information 400 can be stored 32 In bit octet string (OctetString) data type AVP and can be embedded in the another of such as Load-Info AVP 200 In one AVP.
In certain embodiments, the AVP of Diameter overload levels information 400 or correlation can be inserted into various In Diameter message.For example, Load-Info AVP 200 can be included in from overload perceiving or including DOC's 110 In any Diameter message that Diameter nodes send.
Embodiment with reference to shown in Fig. 3, Diameter overload levels information 300 can include the He of range section 302 Detail section 304.Range section 302 can include any letter for pointing out one or more Diameter overload level types Breath.For example, range section information can be value, bit, mark or text.Exemplary range type can include destination-neck Domain, using, destination-main frame, overload packet, connection and session.
Detail section 304 can include any information for defining or describing Diameter overload levels.In some realities In applying example, detail section 304 can be included in AVP and be stored with various data forms, the data form such as The text that the people of UTF8String data forms or OctetString data forms can read.For example, with range of application type phase The detail section 304 of association can include the application-ID AVP for identifying application-specific.It is associated with territory type Detail section 304 can include for identify specific area Diameter identity (for example, complete fully qualified domain name (FQDN)) or Related AVP.The detail section 304 being associated with overload packet type can include the packet for identifying specific overload packet The AVP of title and/or correlation.The detail section 304 being associated with session wide-style can be included for identifying special session Session-ID and/or correlation AVP.The detail section 304 being associated with join domain type can be included for identifying spy Determine the information of session.
In certain embodiments (such as in the case where existing or using multiple scopes), can by from different overload models With enclosing the associated infologic of type together with (∧).If for example, Diameter sessions and destination-territory and Range of application is associated, then can be for the Diameter message application Diameter premature beats in both matching field and application Information (for example, load reduction process).
(for example wherein there are or use multiple scopes) in certain embodiments, can by with similar overload level type Associated infologic ground or (∨) are together.If for example, Diameter sessions and destination-territory and applying model Enclose associated, then can overload control for any one Diameter message application Diameter in matching field or application Information (for example, load reduction process) processed.
Fig. 4 be an embodiment according to theme described herein is shown with showing that Diameter premature beats are associated The diagram of example property message.In fig. 4 in shown embodiment, Diameter client 102 and Diameter server 112- 116 can be communicated using DA 108.In certain embodiments, Diameter client 102 and Diameter server 112-116 can be that overload is perceived (for example, can include the function of DOC 110 and/or correlation).For example, Diameter is objective Family end 102 or Diameter server 112-116 can determine or perceive the overload level of various message or session, can ring Load reduction process or other actions should be performed in the instruction of overload, and/or can use, read or carry in general manner For Diameter premature beats information.
In step 1, Diameter request messages can be sent to DA 108 from Diameter client 102.For example, DA 108 can be received from Diameter client 102 and required from a 's in multiple Diameter server 112-116 The session establishment request of service.In this example, Diameter client 102 may not see Diameter server 112- 116。
In step 2, DA 108 can receive Diameter request messages, it is determined that overload packet and/or determination One or more in Diameter server 112-116 are used to perform the service being associated with Diameter request messages. In some embodiments, DA 108 can send one or more message (not to Diameter client 102 and/or other nodes Show), for recognizing that what is determined overloads the overload being grouped and/or for monitoring entity.For example, DA 108 can by with reception To the associated Diameter sessions of Diameter message be assigned to overload packet.In this example, it is assumed that by each session It is assigned to the overload packet corresponding with the Diameter server of the service request for being assigned to special session.In this example In, DA 108 can determine that Diameter request messages are associated with overload packet " C ", and will be processed by server 116.
In step 3, Diameter request messages can be route, relayed or be otherwise provided to by DA 108 Diameter server 116.In certain embodiments, Diameter request messages can be changed, is overloaded with including Diameter Control information, the overload level being such as associated with message and the load metric being associated with DA 108.Diameter is serviced Device 116 can receive Diameter request messages, and perform the various services being associated with treatment Diameter request messages. After treatment Diameter request messages, Diameter server 116 can send Diameter response messages, it is possible to including Various premature beats information.
In certain embodiments, when DA 108 recognizes next upstream node overloads when, DA 108 can perform one or Action (for example, to minimize or mitigate the load that with upstream node is associated) of the multiple for shaping correlative flow.One In a little embodiments, report overload can correspond to suitably overload context or scope.If for example, existed using " R " Overloaded at Diameter server 114, but application " S " at Diameter server 114 is without overloading, then and DA 108 can be with With overload level type " application " one or more nodes are given by the overload notification at Diameter server 114, it is possible to Point out only to be overloaded using " R ".In this example, Diameter client 102-106 can receive instruction, and only control The flow of the application " R " at request Diameter server 114.In another example, (answered in the absence of other natural regionalizations With, field etc.) in the case of, DA 108 can by each in Diameter server 112-116 be assigned to they from Oneself " overload context ".In this example, in response to receiving the instruction of the overload of a certain Diameter server 114, It is negative in Diameter sessions 114 to reduce or mitigate that Diameter client 102-106 can perform one or more actions Carry.
In certain embodiments, Diameter server 112-116 can be included for performing and Diameter overload controls The function of the associated one or more aspects of system.For example, Diameter servers 112-116 can be overload perceiving. Diameter server 112-116 may be configured to return the stream for receiving by indicating to be sent to peer-to-peer overload Amount.For example, Diameter server 112-116 may be configured to load metric (percentage use or remaining resource Than) report to DA 108, Diameter client 102-106 or other nodes.Judgement (the example being associated with report overload measurement Such as, what is reported and is reported to whom) can be determined by home server strategy, remote node or operator.
In certain embodiments, when the load, Diameter server 112-116 may be configured to refuse with a speed The affairs of the peer-to-peer perceived from non-overloaded, the speed will be pressed down with these peer-to-peers if premature beats are supported really The speed of system is identical.By refusing affairs, Diameter server 112-116 can prevent the peer-to-peer that overload is perceived from not propped up Hold the peer-to-peer " hungry to death " of overload management.Although indicating capacity to be still exceeded if having sent overload, Diameter services Device 112-116 may be configured to refuse affairs, even if they are from the node of overload perception.
In step 4, Diameter response messages can be sent to DA 108 from Diameter server 116. Diameter response messages can include Diameter premature beats information, such as point out 99% at Diameter server 116 The load metric that is currently being used of resource.
In steps of 5, Diameter response messages can be route, relayed or be otherwise provided to by DA 105 Diameter client 102.In certain embodiments, Diameter response messages can be changed, is overloaded with including Diameter Control information, the overload level being such as associated with message and the load metric being associated with DA 108.
In certain embodiments, a finger for being overloaded in DA 108 receives Diameter server 112-116 When showing, DA 108 can send to each in Diameter client 102-106 and point out Diameter overload packets by mistake The message of load.In certain embodiments, Diameter premature beats information with " back of the body is carried on the back (piggyback) " or can be inserted into and wear Cross in the existing Diameter message of DA 108, such as the Diameter response messages from Diameter server 116. After receiving the instruction of overload, in the Diameter client 102-106 of the session with the overload packet corresponding to overload Each can control corresponding to the overload packet flow (such as Diameter message).Can be with uncontrolled corresponding to it The flow of remaining overload packet (packet do not overloaded for example).
In step 6, Diameter server 116 may become overload.For example, Diameter server 116 can be true Fixed its 100% resource is currently being used or cannot process extra message.As response, can be by Diameter message (such as Device-Watchdog-Request (DWR) or Device-Watchdog-Answer (DWA) message) is sent to one Or multiple nodes, such as DA 108 or Diameter client 102-106.In certain embodiments, DWR message and DWA message Can be used to allow exchange load information during other static connections.
In step 7, can be sent from Diameter server 116 to DA 108 comprising Diameter premature beats information The Diameter request messages of (such as Load-Info AVP 200).Diameter premature beats information can include various types of The information of the overload correlation of type, the instruction such as overloaded, overload packet are (for example, identical with the overload packet determined by DA 108 Or it is different), effective period of time and any other relevant information.
In step 8, Diameter request messages can be route, relayed or be otherwise provided to by DA 108 Diameter client 102.In certain embodiments, Diameter request messages can be changed, is overloaded with including Diameter Control information, the overload level being such as associated with message and negative at Diameter server 116 for breaking away from or mitigating The overload control algorithms of load.
Diameter client 102 can receive the Diameter request messages comprising Diameter premature beats information. In response to receiving Diameter premature beats information, Diameter client 102 can be within a period of time (for example, being based on The effective period of time of the association being associated with Diameter premature beats information) stop being led to Diameter server 116 Letter, or perform another action for mitigating the load at Diameter server 116.For example, can be by Diameter client 102 Control the flow of the Diameter server 116 corresponding to overload packet " C ".In this example, Diameter client 102 Can continue to use the Diameter server 112 and 116 for corresponding to packet A and B completely.
Fig. 5 is to show being associated with Diameter premature beats for another embodiment according to theme described herein The diagram of example message.In Figure 5 in shown embodiment, Diameter client 500 and Diameter server 502 Can be communicated in the case where intermediate node (such as DA 108) is not used.In certain embodiments, Diameter client End 500 and Diameter server 502 can include being serviced as described above for Diameter client 102 and Diameter respectively Similar function described by device 112.In certain embodiments, Diameter client 500 and Diameter server 502 can Being that overload is perceived (for example, can include function of DOC 110 and/or correlation).For example, Diameter client 500 or Diameter server 502 can determine or perceive the overload level of various message or session, can be in response to the finger of overload Show and perform load reduction process or other actions, and/or can use, read or provide Diameter mistakes in general manner Carry control information.
In step 1, Diameter request messages can be sent to Diameter services from Diameter client 500 Device 502.For example, Diameter request messages can ask user profile from the SPR at Diameter server 502.
Diameter server 502 can receive Diameter request messages, and determine with Diameter request messages and/ Or the overload packet that the Diameter sessions of correlation are associated.In certain embodiments, can based on available information come using or Specify overload packet or other overload levels.For example, Diameter server 502 or DOC therein 110 can be based on Whether Diameter server 502 can process whether request or request need using random access memory (RAM) resource (on-disk) local data library inquiry is coiled to specify the session of message and/or correlation.In this example, it is possible to use RAM Resource come process and need not inquire about local data base on disk request can be assigned to overload packet " A ", can be processed but It is to need the request for accessing local data base on disk to be assigned to overload to be grouped " B ".
In step 2, Diameter response messages can be sent to Diameter client from Diameter server 502 End 500.Diameter response messages can include Diameter premature beats information, such as overload packet (such as overload packet " A ") and point out the load metric that at Diameter server 502 99% resource is currently being used.Diameter client 500 Diameter response messages can be received and the Diameter response messages are correspondingly processed.For example, Diameter client 500 Subsequent Diameter message can be sent to Diameter server 502.In another example, Diameter client 500 can attempt to find in response to recognizing Diameter server 502 almost entirely to overload and another less overload Diameter server.
In step 3, another Diameter request messages can be sent to from Diameter client 500 Diameter server 502.For example, Diameter request messages can be to from the SPR at Diameter server 502 The request of extensive user profile.
Diameter server 502 can receive Diameter request messages, and determine with Diameter request messages and/ Or the overload packet that the Diameter sessions of correlation are associated.For example, Diameter server 502 or DOC therein 110 can Overload packet " B " is assigned to by the session of Diameter request messages and/or correlation, because Diameter request messages can be with It is required that local data base on inquiry disk.
In step 4, another Diameter response messages can be sent to Diameter from Diameter server 502 Client 500.Diameter response messages can include Diameter premature beats information, and such as overload packet is (for example, overload Packet " B ") and point out the load metric that at Diameter server 116 99% resource is currently being used.Diameter client End 500 can receive Diameter response messages, and correspondingly process Diameter response messages.
In steps of 5, Diameter server 502 may become overload.Diameter server 502 can determine it 100% resource is currently being used or cannot process extra message.Whether local data is required based on request wherein Whether storehouse or request only require that RAM resources are specified overload to be grouped in the example of " A " and " B " to session, when Diameter services Device 502 is experienced overload due to the I/O bottlenecks being associated with local data base but can be meeting that RAM resources are only required in service During the request of words, Diameter server 502 can send the overload notification message for being grouped B rather than packet A.For example, Diameter message (for example, Device-Watchdog-Request message) can be sent.
In step 6, can be sent from Diameter server 502 to Diameter client 500 comprising Diameter The Diameter request messages of premature beats information (for example, Load-Info AVP 200).Diameter premature beats information can With including the related information of various types of overloads, the instruction such as overloaded, overload packet (such as overload packet " B "), effectively Time period and any other relevant information.
Diameter client 502 can receive the Diameter request messages comprising Diameter premature beats information. In response to receiving Diameter premature beats information, Diameter client 502 can be controlled asks to overload packet " B " Ask, and the communication that " A " is associated is grouped without restraining and overload.
Fig. 6 be show an embodiment according to theme described herein for performing showing for Diameter premature beats The flow chart of example property treatment.In certain embodiments, exemplary process described herein or some of part can be in DA 108th, DOC 110, Diameter intermediaries, Diameter server 112, Diameter client 102, Diameter nodes with And/or performed at another module of person or node, or performed by them.
Embodiment with reference to shown in Fig. 6, in step 600, can be received at communication interface or by it Diameter message.For example, the Diameter request messages from Diameter client 102 can be received at DA 108.
In step 602, the overload conditions of the Diameter sessions being associated with Diameter message can be detected.Example Such as, can be overloaded using " X ", Diameter message can be that request carrys out the treatment of self-application " X " or using using " X " A part for Diameter sessions.
In step 604, it is possible to use existing Diameter message --- for example DWA message, DWR message, CER disappear Breath, CEA message or be defined for be different from premature beats purposes any Diameter message --- by overload conditions Instruction is delivered to the 2nd Diameter nodes.In certain embodiments, Diameter overload levels can include node, field, Using, main frame, packet, session or connection.
In certain embodiments, the overload being associated with Diameter overload levels can be detected.For example, DA 108 or DOC 110 may be configured to monitor one or more nodes, field, using, session or other overload entities.Identifying or examining Various monitoring technology can be used when surveying overload, for example by poll, by the monitored node of subscription or by from one Or multiple monitored nodes receive the instruction of overload.
In certain embodiments, method referred to above can overload related property value pair using one or more (AVP) (such as Load-Info AVP 200) transmits the instruction of overload conditions, it is possible to one or more overloads are related AVP is inserted into Diameter message.
In certain embodiments, the 2nd Diameter nodes in method referred to above can use the mistake for receiving The instruction of load situation mitigates a Diameter nodes (such as DA 108) or the 3rd Diameter nodes are (for example Diameter client 102) place the load being associated with Diameter overload levels.
In certain embodiments, the 2nd Dianmeter nodes in method referred to above can include Diameter The start node of message, Diameter client, Diameter server, Diameter intermediaries, DRN or DSR.
In certain embodiments, the Diameter overload levels in method referred to above can include node, field, Using, main frame, packet, session or connection.
In certain embodiments, the Diameter nodes in method referred to above can include Diameter generations Reason, Diameter server, Diameter client, DRN or DSR.
In certain embodiments, the Diameter message in method referred to above can be included from Diameter visitors The Diameter session establishments request message at family end, the Diameter session establishments response message from Diameter server, Diameter request messages, Diameter response messages or Diameter response messages.
In certain embodiments, method as described above can include what detection was associated with Diameter overload levels Overload, including detection and the 2nd Diameter nodes, field, using, main frame, packet, session or connect the overload being associated.
In certain embodiments, the instruction of the overload in method referred to above can be identified corresponding to overload Session and Diameter message in the overload packet of Diameter nodes.
In certain embodiments, the 2nd Diameter nodes in method referred to above can be by Diameter message Or the session of correlation be assigned to overload packet, and by this specify be delivered to a Diameter nodes.
In certain embodiments, the Diameter nodes in method referred to above can be in the finger of transmission overload It is grouped using the overload specified by the 2nd Diameter nodes when showing.
In certain embodiments, the Diameter nodes in method referred to above can be by Diameter message Or the session of correlation is assigned to the overload packet different from the overload packet specified by the 2nd Diameter nodes, and transmitting It is grouped using the overload specified by a Diameter nodes during instruction of load.
In certain embodiments, the Diameter nodes in method referred to above can will have the first characteristic Diameter message or correlation session be assigned to the first overload packet, by have the second characteristic other Diameter disappear The session of breath or correlation is assigned to the packet of the second overload, and is related to the overload of the first characteristic in response to detecting, by what is overloaded Indicate to be delivered to one or more originator nodes with the communication for being assigned to the packet of the first overload.
In certain embodiments, non-transitory computer-readable medium can have stored thereon executable instruction, when Executable instruction by computer computing device when control computer executed step.Performed step can be included in communication Interface receives Diameter message, detects the overload conditions of the Diameter sessions being associated with Diameter message, and The instruction of overload conditions is delivered to the 2nd Diameter nodes using existing Diameter message.
It is appreciated that in the case of the scope of theme described without departing from here, thus it is possible to vary described herein The various details of theme.Additionally, foregoing description be served only for explanation and without limitation.

Claims (8)

1. a kind of system for performing Diameter premature beats, the system includes：
First Diameter nodes, including：
At least one network interface, for receiving the first Diameter message；And
Diameter premature beats units, are configured to the overload conditions that are associated with the first Diameter message of detection and make The instruction of the overload conditions is passed with the second Diameter message of the purposes for being defined for being different from premature beats The 2nd Diameter nodes are delivered to, wherein a Diameter nodes include being configured to determine that in the Diameter of overload packet It is situated between, wherein the first Diameter message includes being asked from the session establishment of Diameter client, wherein the Diameter The overload conditions detect from the Diameter server that service is provided to the Diameter client in intermediary, wherein second Overload determined by Diameter message mark is grouped, and wherein described Diameter intermediaries will ask with the session establishment Associated session is assigned to the overload packet.
2. the system as claimed in claim 1, wherein, the instruction of overload conditions includes Diameter overload levels.
3. system as claimed in claim 2, wherein, Diameter overload levels include node, field, using, main frame, session And one in connection.
4. the system as claimed in claim 1, wherein, session is assigned to overload packet by the Diameter server, and will The specified of the session is delivered to the Diameter intermediaries.
5. system as claimed in claim 4, wherein, the Diameter intermediaries the instruction of overload conditions is delivered to it is described It is grouped using the overload specified by the Diameter intermediaries during Diameter client.
6. system as claimed in claim 4, wherein, be assigned to different from by described for the session by the Diameter intermediaries The overload of the overload packet that Diameter server is specified is grouped, and is used by described when the instruction of overload conditions is transmitted The overload packet that Diameter intermediaries specify.
7. the system as claimed in claim 1, wherein, the session is assigned to overload packet by the Diameter intermediaries.
8. the system as claimed in claim 1, wherein, the session with the first characteristic is assigned to the by a Diameter nodes One overload packet, is assigned to the packet of the second overload, and be related to the first spy in response to detecting by the session with the second characteristic Property overload conditions by it is described instruction be delivered to be assigned to the first overload packet session one or more originator section Point.
CN201380027543.6A 2012-04-13 2013-04-15 System for performing DIAMETER premature beats Active CN104335539B (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201261624237P 2012-04-13 2012-04-13
US61/624,237 2012-04-13
PCT/US2013/036664 WO2013155535A1 (en) 2012-04-13 2013-04-15 Methods, systems, and computer readable media for performing diameter overload control

Publications (2)

Publication Number Publication Date
CN104335539A CN104335539A (en) 2015-02-04
CN104335539B true CN104335539B (en) 2017-07-04

Family

ID=49326096

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201380027543.6A Active CN104335539B (en) 2012-04-13 2013-04-15 System for performing DIAMETER premature beats

Country Status (5)

Country Link
US (1) US9699045B2 (en)
EP (1) EP2837147B1 (en)
JP (1) JP6059336B2 (en)
CN (1) CN104335539B (en)
WO (1) WO2013155535A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10027760B2 (en) 2015-05-22 2018-07-17 Oracle International Corporation Methods, systems, and computer readable media for short and long term policy and charging rules function (PCRF) load balancing
US10103955B2 (en) 2015-10-01 2018-10-16 Oracle International Corporation Methods, systems, and computer readable media for transmitting diameter peer status information
US10149143B2 (en) 2016-08-30 2018-12-04 Oracle International Corporation Methods, systems, and computer readable media for realm-based routing of diameter request messages

Families Citing this family (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8326958B1 (en) 2009-01-28 2012-12-04 Headwater Partners I, Llc Service activation tracking system
US10783581B2 (en) 2009-01-28 2020-09-22 Headwater Research Llc Wireless end-user device providing ambient or sponsored services
US10057775B2 (en) * 2009-01-28 2018-08-21 Headwater Research Llc Virtualized policy and charging system
US10248996B2 (en) 2009-01-28 2019-04-02 Headwater Research Llc Method for operating a wireless end-user device mobile payment agent
US9571559B2 (en) 2009-01-28 2017-02-14 Headwater Partners I Llc Enhanced curfew and protection associated with a device group
US9557889B2 (en) 2009-01-28 2017-01-31 Headwater Partners I Llc Service plan design, user interfaces, application programming interfaces, and device management
US9858559B2 (en) 2009-01-28 2018-01-02 Headwater Research Llc Network service plan design
US10492102B2 (en) 2009-01-28 2019-11-26 Headwater Research Llc Intermediate networking devices
US9954975B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Enhanced curfew and protection associated with a device group
US9955332B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Method for child wireless device activation to subscriber account of a master wireless device
US11218854B2 (en) 2009-01-28 2022-01-04 Headwater Research Llc Service plan design, user interfaces, application programming interfaces, and device management
US9351193B2 (en) 2009-01-28 2016-05-24 Headwater Partners I Llc Intermediate networking devices
US9578182B2 (en) 2009-01-28 2017-02-21 Headwater Partners I Llc Mobile device and service management
US10264138B2 (en) 2009-01-28 2019-04-16 Headwater Research Llc Mobile device and service management
US9860390B2 (en) 2011-08-10 2018-01-02 Tekelec, Inc. Methods, systems, and computer readable media for policy event record generation
KR20130064906A (en) * 2011-12-09 2013-06-19 삼성전자주식회사 Method and apparatus for load balancing in communication system
US9432864B2 (en) * 2012-05-29 2016-08-30 Alcatel Lucent Generic persistence in a diameter routing agent
US10477385B2 (en) 2012-07-20 2019-11-12 Tekelec, Inc. Methods, systems and computer readable media for distributing policy rules to the mobile edge
WO2014159862A1 (en) 2013-03-14 2014-10-02 Headwater Partners I Llc Automated credential porting for mobile devices
US9450872B2 (en) * 2013-06-24 2016-09-20 Oracle International Corporation Methods, systems and computer readable media for collecting and distributing diameter overload control information to non-adjacent nodes
US9369386B2 (en) 2013-07-31 2016-06-14 Oracle International Corporation Methods, systems, and computer readable media for destination-host defined overload scope
US9391897B2 (en) 2013-07-31 2016-07-12 Oracle International Corporation Methods, systems, and computer readable media for mitigating traffic storms
US9240949B2 (en) 2013-07-31 2016-01-19 Oracle International Corporation Methods, systems and computer readable media for predicting overload conditions using load information
US9537775B2 (en) 2013-09-23 2017-01-03 Oracle International Corporation Methods, systems, and computer readable media for diameter load and overload information and virtualization
US11388082B2 (en) 2013-11-27 2022-07-12 Oracle International Corporation Methods, systems, and computer readable media for diameter routing using software defined network (SDN) functionality
US9888001B2 (en) * 2014-01-28 2018-02-06 Oracle International Corporation Methods, systems, and computer readable media for negotiating diameter capabilities
EP3108664B1 (en) 2014-02-20 2019-05-01 Markport Limited Enhanced traffic management during signaling storms
US9515932B2 (en) * 2015-02-06 2016-12-06 Oracle International Corporation Methods, systems, and computer readable media for conducting priority and compliance based message traffic shaping
US9680965B2 (en) * 2015-04-01 2017-06-13 Alcatel-Lucent Usa Inc. Software upgrades for offline charging systems within a network
US9699076B2 (en) 2015-06-09 2017-07-04 Oracle International Corporation Methods, systems, and computer readable media for implementing intelligent policy and charging rules function (PCRF) overload control
US9603044B2 (en) * 2015-06-10 2017-03-21 Cisco Technology, Inc. Use of traffic load reduction indicator for facilitating mobility management entity overload control function
US10069673B2 (en) 2015-08-17 2018-09-04 Oracle International Corporation Methods, systems, and computer readable media for conducting adaptive event rate monitoring
CN106549771A (en) * 2015-09-23 2017-03-29 中兴通讯股份有限公司 The overload controlling method and device of charging request message
US9800504B2 (en) 2015-10-20 2017-10-24 Oracle International Corporation Methods, systems, and computer readable media diverting diameter traffic from an overloaded policy and charging rules function (PCRF)
US10110421B2 (en) 2015-10-29 2018-10-23 Oracle International Corporation Methods, systems, and computer readable media for using link aggregation group (LAG) status information
US10104516B2 (en) * 2016-03-30 2018-10-16 Nokia Of America Corporation Dynamic distribution in an offline charging system
US10225762B2 (en) * 2017-03-28 2019-03-05 Oracle International Corporation Methods, systems, and computer readable media for message flood suppression during access node-gateway (AN-GW) unavailability and after AN-GW restoration
WO2019068360A1 (en) * 2017-10-06 2019-04-11 Telefonaktiebolaget Lm Ericsson (Publ) Differentiated abatement of charging requests in case of overload at online charging system
US10687206B2 (en) * 2018-01-30 2020-06-16 Hewlett Packard Enterprise Development Lp Response messages including information elements not indicated as requested
US11765618B2 (en) * 2020-03-20 2023-09-19 Nokia Technologies Oy Wireless communication system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102090042A (en) * 2008-05-01 2011-06-08 阿尔卡特朗讯美国公司 Message restriction for Diameter servers
CN102239481A (en) * 2007-12-01 2011-11-09 朗讯科技公司 Ims diameter router with load balancing

Family Cites Families (69)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100442610B1 (en) * 2002-04-22 2004-08-02 삼성전자주식회사 Flow control method of radius protocol
US7701854B2 (en) 2003-11-17 2010-04-20 International Business Machines Corporation Differentiated handling of SIP messages for VoIP call control
US7522517B1 (en) 2003-11-18 2009-04-21 Sprint Communications Company Lp. Communication system with multipoint circuit bonding
US8582567B2 (en) 2005-08-09 2013-11-12 Avaya Inc. System and method for providing network level and nodal level vulnerability protection in VoIP networks
US7805517B2 (en) 2004-09-15 2010-09-28 Cisco Technology, Inc. System and method for load balancing a communications network
US7552206B2 (en) 2004-10-27 2009-06-23 Microsoft Corporation Throttling service connections based on network paths
FI20050494A0 (en) 2005-05-10 2005-05-10 Nokia Corp Provision of a service in a communication system
US20070083927A1 (en) 2005-10-11 2007-04-12 Intel Corporation Method and system for managing denial of services (DoS) attacks
US8170055B2 (en) 2005-12-29 2012-05-01 Alcatel Lucent Method of converting between radius message and diameter messages
US7522581B2 (en) 2006-08-01 2009-04-21 International Business Machines Corporation Overload protection for SIP servers
CN101163139B (en) 2006-10-11 2010-12-15 国际商业机器公司 Method and equipment for refusing SIP message of redundancy retransmission
CN101212420B (en) 2006-12-27 2010-09-29 华为技术有限公司 Redirector, relay and route information configuration system and update method
US7953884B2 (en) * 2006-12-29 2011-05-31 Alcatel-Lucent Usa Inc. Method and apparatus for overload control and audit in a resource control and management system
US20080170497A1 (en) 2007-01-11 2008-07-17 Moo Ryong Jeong Proactive Per-Class Load Management
CN101247321B (en) 2007-02-14 2012-07-04 华为技术有限公司 Method, device and system for routing diagnosis in network based on diameter protocol
US7742417B2 (en) 2007-02-16 2010-06-22 International Business Machines Corporation Burst traffic smoothing for SIP processing elements
CN101277175B (en) 2007-03-30 2012-02-29 国际商业机器公司 Method and device for improving conversation starting protocol server performance
US8782085B2 (en) 2007-04-10 2014-07-15 Apertio Limited Variant entries in network data repositories
KR20090029348A (en) * 2007-09-18 2009-03-23 삼성전자주식회사 Apparatus and method for call distribution in diameter system
US8201219B2 (en) * 2007-09-24 2012-06-12 Bridgewater Systems Corp. Systems and methods for server load balancing using authentication, authorization, and accounting protocols
US9749404B2 (en) * 2008-04-17 2017-08-29 Radware, Ltd. Method and system for load balancing over a cluster of authentication, authorization and accounting (AAA) servers
US20090310484A1 (en) 2008-04-17 2009-12-17 Dorgham Sisalem Methods, systems, and computer readable media for session initiation protocol (sip) overload control
WO2009137956A1 (en) 2008-05-15 2009-11-19 朗讯科技公司 A method and a network element for controlling the end-to-end overload based on the diameter application
CN102160452B (en) 2008-06-05 2015-02-04 凯敏公司 Method and system for providing mobility management in network
EP2311228B1 (en) 2008-07-31 2017-09-06 Tekelec, Inc. Methods, systems, and computer readable media for throttling traffic to an internet protocol (ip) network server using alias hostname identifiers assigned to the ip network server with a domain name system (dns)
US10203993B2 (en) 2009-02-18 2019-02-12 International Business Machines Corporation Method and system for continuous optimization of data centers by combining server and storage virtualization
US8964696B2 (en) 2009-02-19 2015-02-24 Telefonaktiebolaget L M Ericsson (Publ) Traffic control for roaming subscribers
KR101279001B1 (en) 2009-05-15 2013-07-30 무라다기카이가부시끼가이샤 Relay communication system and first relay server
CN102656845B (en) * 2009-10-16 2015-04-01 泰克莱克股份有限公司 Methods, systems, and computer readable media for providing diameter signaling router with integrated monitoring and/or firewall functionality
US8355395B2 (en) 2009-10-20 2013-01-15 At&T Intellectual Property I, L.P. Controlling registration floods in VoIP networks via DNS
US9432451B2 (en) 2009-12-15 2016-08-30 Tekelec, Inc. Methods, systems, and computer readable media for communicating media server capabilities and status information between media servers and a media resource broker
US8787174B2 (en) 2009-12-31 2014-07-22 Tekelec, Inc. Methods, systems, and computer readable media for condition-triggered policies
US20110171958A1 (en) 2010-01-11 2011-07-14 Suzann Hua Mobile device usage management via home subscriber server operation and profile
JP5537349B2 (en) * 2010-02-11 2014-07-02 Ｋｄｄｉ株式会社 Method and system for changing SIP server while terminal connection is continued
WO2011100603A2 (en) 2010-02-12 2011-08-18 Tekelec Methods, systems, and computer readable media for providing peer routing at a diameter node
US8532110B2 (en) * 2010-02-12 2013-09-10 Tekelec, Inc. Methods, systems, and computer readable media for diameter protocol harmonization
IN2012CN10350A (en) * 2010-06-15 2015-07-31 Tekelec Inc
US8897134B2 (en) 2010-06-25 2014-11-25 Telefonaktiebolaget L M Ericsson (Publ) Notifying a controller of a change to a packet forwarding configuration of a network element over a communication channel
EP3328136B1 (en) 2010-08-18 2020-04-08 BlackBerry Limited Method to maintain call continuity
US9118593B2 (en) 2010-10-07 2015-08-25 Enghouse Networks Limited System and method for best value routing
EP2634977A4 (en) 2010-10-28 2015-01-07 Nec Corp Network system and method for controlling communication traffic
EP2638671B1 (en) 2010-11-10 2015-09-09 Nec Corporation Method for supporting congestion management in a congestion exposure-enabled network
US8824370B2 (en) 2010-12-16 2014-09-02 Openet Telecom Ltd. Methods, systems and devices for dynamic context-based routing
US20120221693A1 (en) 2011-02-25 2012-08-30 Alcatlel-Lucent Canada Inc. Temporary restrictions and rollback
US20120221445A1 (en) 2011-02-28 2012-08-30 Alcatel-Lucent Usa Inc. Method and apparatus for detecting duplicate accounting records in distributed network
US8547908B2 (en) * 2011-03-03 2013-10-01 Tekelec, Inc. Methods, systems, and computer readable media for enriching a diameter signaling message
EP2692096A1 (en) 2011-03-29 2014-02-05 NEC Europe Ltd. User traffic accountability under congestion in flow-based multi-layer switches
US8879431B2 (en) * 2011-05-16 2014-11-04 F5 Networks, Inc. Method for load balancing of requests' processing of diameter servers
US8873398B2 (en) 2011-05-23 2014-10-28 Telefonaktiebolaget L M Ericsson (Publ) Implementing EPC in a cloud computer with openflow data plane
US20120303796A1 (en) 2011-05-27 2012-11-29 Alcate-Lucent Canada Inc. Mapping accounting avps to monitoring keys for wireline subscriber management
US8953443B2 (en) 2011-06-01 2015-02-10 At&T Intellectual Property I, L.P. Method and apparatus for providing congestion management for a wireless communication network
US10425336B2 (en) 2011-06-24 2019-09-24 Centurylink Intellectual Property Llc System and method of adaptive congestion management
US9860390B2 (en) 2011-08-10 2018-01-02 Tekelec, Inc. Methods, systems, and computer readable media for policy event record generation
US9311160B2 (en) 2011-11-10 2016-04-12 Verizon Patent And Licensing Inc. Elastic cloud networking
US9350671B2 (en) 2012-03-22 2016-05-24 Futurewei Technologies, Inc. Supporting software defined networking with application layer traffic optimization
US9225635B2 (en) 2012-04-10 2015-12-29 International Business Machines Corporation Switch routing table utilizing software defined network (SDN) controller programmed route segregation and prioritization
US8797902B2 (en) 2012-05-29 2014-08-05 Alcatel Lucent Routing decision context objects
WO2014063723A1 (en) 2012-10-22 2014-05-01 Nokia Solutions And Networks Oy Methods, apparatuses, system, related computer program product for routing and processing policy requests related to group subscription
US9066275B2 (en) 2012-12-27 2015-06-23 Cellco Partnership Method and system to improve device pinging
US10333779B2 (en) 2013-04-10 2019-06-25 Huawei Technologies Co., Ltd. System and method for providing a software defined protocol stack
EP2987275B1 (en) 2013-04-15 2018-07-25 Telefonaktiebolaget LM Ericsson (publ) Enhanced qos control in pcrf
US9450872B2 (en) 2013-06-24 2016-09-20 Oracle International Corporation Methods, systems and computer readable media for collecting and distributing diameter overload control information to non-adjacent nodes
US9240949B2 (en) 2013-07-31 2016-01-19 Oracle International Corporation Methods, systems and computer readable media for predicting overload conditions using load information
US9391897B2 (en) 2013-07-31 2016-07-12 Oracle International Corporation Methods, systems, and computer readable media for mitigating traffic storms
US9369386B2 (en) 2013-07-31 2016-06-14 Oracle International Corporation Methods, systems, and computer readable media for destination-host defined overload scope
US9537775B2 (en) 2013-09-23 2017-01-03 Oracle International Corporation Methods, systems, and computer readable media for diameter load and overload information and virtualization
US11388082B2 (en) 2013-11-27 2022-07-12 Oracle International Corporation Methods, systems, and computer readable media for diameter routing using software defined network (SDN) functionality
US9674046B2 (en) 2014-10-21 2017-06-06 At&T Intellectual Property I, L.P. Automatic detection and prevention of network overload conditions using SDN
US10027760B2 (en) 2015-05-22 2018-07-17 Oracle International Corporation Methods, systems, and computer readable media for short and long term policy and charging rules function (PCRF) load balancing

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102239481A (en) * 2007-12-01 2011-11-09 朗讯科技公司 Ims diameter router with load balancing
CN102090042A (en) * 2008-05-01 2011-06-08 阿尔卡特朗讯美国公司 Message restriction for Diameter servers

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10027760B2 (en) 2015-05-22 2018-07-17 Oracle International Corporation Methods, systems, and computer readable media for short and long term policy and charging rules function (PCRF) load balancing
US10103955B2 (en) 2015-10-01 2018-10-16 Oracle International Corporation Methods, systems, and computer readable media for transmitting diameter peer status information
US10149143B2 (en) 2016-08-30 2018-12-04 Oracle International Corporation Methods, systems, and computer readable media for realm-based routing of diameter request messages

Also Published As

Publication number Publication date
JP2015518336A (en) 2015-06-25
EP2837147A4 (en) 2016-01-13
US9699045B2 (en) 2017-07-04
JP6059336B2 (en) 2017-01-11
CN104335539A (en) 2015-02-04
US20130275583A1 (en) 2013-10-17
EP2837147B1 (en) 2022-04-27
WO2013155535A1 (en) 2013-10-17
EP2837147A1 (en) 2015-02-18

Similar Documents

Publication Publication Date Title
CN104335539B (en) System for performing DIAMETER premature beats
US9369386B2 (en) Methods, systems, and computer readable media for destination-host defined overload scope
CN105580317B (en) Methods, systems, and computer readable media for DIAMETER load and overload information and virtualization
CN102893556B (en) Method, system and equipment for source peer-to-peer Diameter based on capacity load Sharing
CN103166985B (en) A kind of GSLB dispatching method, data transmission method, apparatus and system
CN105765921B (en) For carrying out method, system and the equipment of DIAMETER routing using software defined network function
KR102083814B1 (en) Data processing method and device
JP2013168139A (en) Load balancing device, load balancing method and hierarchized data center system
JP2010517387A (en) Service processing method and service processing system, and policy control and billing rule function
CN112534779A (en) Method for updating PFD rules for an application and related network nodes
EP2764658B1 (en) Method for using intelligent router in charging system and apparatus associated therewith
CN109818997A (en) A kind of load-balancing method, system and storage medium
JP5916877B2 (en) Method, system, and computer program for testing a DIAMETER routing node
WO2016048928A1 (en) Cdf tracking for offline charging
WO2012001514A3 (en) Management of serving gateways for enhanced performance
CN106161561A (en) A kind of realize the method for Differentiated Services, device and load-balanced server
JP5154313B2 (en) SIP message distribution method and SIP message distribution apparatus
CN106375355A (en) Load balancing processing method and apparatus
US10103955B2 (en) Methods, systems, and computer readable media for transmitting diameter peer status information
CN105939404B (en) The acquisition methods and device of NAT resource
US20160226765A1 (en) Information transmission method and apparatus
CN105191226B (en) For adjusting the method and arrangement of the service quality of dedicated channel based on service awareness
CN113037859B (en) Session information management method, device, exchange equipment and medium
CN106487890A (en) A kind of cross-node communication network requesting method based on XMPP
EP2974165B1 (en) Method for indicating routing capacity related data or routing delay related data by means of signalling messages in a core network of a telecommunications network using diameter messages, a mobile communication networks

Legal Events

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