WO2009137956A1 - Diameter应用的端到端过载控制方法和网络单元 - Google Patents

Diameter应用的端到端过载控制方法和网络单元 Download PDF

Info

Publication number
WO2009137956A1
WO2009137956A1 PCT/CN2008/000946 CN2008000946W WO2009137956A1 WO 2009137956 A1 WO2009137956 A1 WO 2009137956A1 CN 2008000946 W CN2008000946 W CN 2008000946W WO 2009137956 A1 WO2009137956 A1 WO 2009137956A1
Authority
WO
WIPO (PCT)
Prior art keywords
overload control
overload
application
diameter
request
Prior art date
Application number
PCT/CN2008/000946
Other languages
English (en)
French (fr)
Inventor
陈旭
牛永波
皇海辉
Original Assignee
朗讯科技公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 朗讯科技公司 filed Critical 朗讯科技公司
Priority to EP08748501.7A priority Critical patent/EP2280520A4/en
Priority to KR1020107028231A priority patent/KR101440670B1/ko
Priority to JP2011508785A priority patent/JP5242773B2/ja
Priority to PCT/CN2008/000946 priority patent/WO2009137956A1/zh
Priority to CN200880129218XA priority patent/CN102027725A/zh
Priority to US12/990,847 priority patent/US20110061061A1/en
Publication of WO2009137956A1 publication Critical patent/WO2009137956A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0892Network architectures or network communication protocols for network security for authentication of entities by using authentication-authorization-accounting [AAA] servers or protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection

Definitions

  • the present invention relates to the field of communications, and more particularly to an end-to-end overload control method for Diameter applications and a network element implementing the method. Background technique
  • the Diameter out protocol defined in RFC 3588 is intended to provide an Authentication, Authorization, and Accounting (AAA) framework for applications such as network-in-service or mobile IP.
  • AAA Authentication, Authorization, and Accounting
  • the current Diameter standard document specifies the message format, transport, error reporting, billing, and security services to be used by all Diameter applications.
  • Protocol elements consist of numerous commands and AVPs (attribute value pairs) that pass authentication, authorization, and accounting information between clients, agents, and servers. However, whether it is a client, a proxy or a server, the session request can be actively sent, and the other party gives a response, so it is also called an agreement between peer entities.
  • Command codes, AVP values, and categories can all be extended by application needs and rules.
  • IP networks more and more standards, specifications, and IP products use Diameter as AAA and other control protocols.
  • the IP networks herein are, for example, the IPQoS Control Subsystem defined in the TISAPN, 3GPP, 3GPP2 standards, Next Generation Network (NGN), and IP Multimedia Subsystem (IMS).
  • NTN Next Generation Network
  • IMS IP Multimedia Subsystem
  • Diameter is a relatively new protocol, there is no existing method for end-to-end Diameter application overload control. This is a major drawback in the Diameter protocol because overload control is one of the key features of the product due to capacity, performance and reliability. Summary of the invention
  • the present invention provides sufficient end-to-end overload control and products using the Diameter protocol for Diameter applications.
  • the Diameter application server/client
  • the present invention proposes a method for performing overload control between a first application and a second application based on the Diameter protocol, including:
  • the overload control information is set and sent to the second application; and the second application takes an action according to the overload control information.
  • the overload control information is sent to the second application via a Diameter response message.
  • the overload control information is transmitted to the second application via a call disconnection request CGR message.
  • the overload control information is a combined overload attribute value pair.
  • the combined overload attribute value pair includes a load level attribute value pair defining a current state of the load, an overload control duration attribute value pair defining an overload control duration, and an overload control action attribute value pair defining an action taken during an overload control duration And a request transmission frequency attribute value pair that defines a transmission frequency of the request message during the duration of the overload control.
  • the invention also proposes a network unit based on the Diameter protocol, which comprises an overload control initiating device, the overload control initiating device being configured to: set overload control information to be sent to the opposite end of communication with the network unit when an overload occurs Network unit.
  • the present invention also provides a network unit based on the Diameter protocol, which includes an overload control response device, and the overload control response device is configured to: when receiving the overload control information sent by the opposite end, according to the The overload control information takes action.
  • the overload control mechanism of the present invention is an end-to-end overload control mechanism between the Diameter server and the Diameter client, such that overload information, requests and responses can be sent from one Diameter application to any other via more than one Diameter agent or relay node.
  • the Diameter application, and the intermediate Diameter agent or relay node does not have to support or know the method or take any action, they simply forward the Diameter command / AVP transparently, which will save the workload on these intermediate Diameter nodes.
  • FIG. 1 shows an example of initiating Diameter overload control via a Diameter response message in accordance with an embodiment of the present invention
  • FIG. 2 illustrates an example of initiating Diameter overload control via a specific CGR/CGA command, in accordance with an embodiment of the present invention
  • Figure 3 illustrates an example of canceling overload control in accordance with an embodiment of the invention
  • FIG. 4 illustrates an example of an overload control initiating device included in a Diameter application, in accordance with an embodiment of the present invention
  • FIG. 5 illustrates an example of an overload control response device included in a Diameter application, in accordance with an embodiment of the present invention. detailed description
  • AAR and AAA DIAMETER messages are used as requests and responses for specific applications in embodiments of the invention, and indeed the method of the present invention can be implemented by means of any DIAMETER request and response.
  • Figure 1 shows an example of initiating Diameter overload control via a Diameter response message.
  • the entities involved are Application A, Application B, Application A can be a Diameter server, Application B is a Diameter client, or Application A can be a Diameter client, and Application B is a Diameter server, whether it is a server or a client. It is possible for the machine to initiate an overload control request.
  • Level nodes we call them "intermediate nodes". These intermediate nodes only need to transparently forward overload request or response messages without participating in overload control.
  • step 101 it is assumed that the application A sends an AAR (authentication, authorization request) to the application B, and the intermediate node transparently forwards the AAR request.
  • step 102 the application B finds that the AAR message cannot be processed, for example because the load is heavy; then in step 103, the application B fills the overload AVP in the response AAA message to be sent back to the application A and sets the value of the resultcode AVP to " Too busy”.
  • step 104 the application B sends the response AAA message to the application A.
  • the intermediate node does not participate in the overload control, and transparently forwards the message to the application A.
  • application A accepts the response AAA message it discovers the overloaded AVP in the message and takes the corresponding action according to the value of the overload AVP, as shown in step 105.
  • the overload AVP herein may be a combined Over-load_AVP, which is to implement the present invention.
  • the new Diameter AVP proposed by the overload control mechanism includes a load status and overload control request for the Diameter application end-to-end overload control, and the AVP can be included in any Diameter response message or included in any Diameter command.
  • Combination Over-load—AVP can contain the following sub-AVPs:
  • Load_level_AVP the load level AVP, which represents the load status of the Diameter application. Its value can be, for example, overload—minor, overload_critical, normal, and so on. Of course, the level can be more carefully divided according to actual needs.
  • Overload_duration_AVP the overload control duration AVP. This AVP indicates the expiration date of the overload control request.
  • o 2 - only send requests for replying with Diameter; o 3 - send the request only at a frequency lower than the value in the AVP;
  • AVP This AVP indicates the maximum transmission frequency that the requested party can send to the party requesting the overload control.
  • the application for initiating the overload control in the present invention may be a diameter client or a diameter server.
  • step 105 when application A receives the response AAA message, it discovers the overloaded AVP in the message and takes the corresponding action according to the value of the overload AVP.
  • the action taken by the application A is based on the combination of Over-load-AVP, that is, the aforementioned Load Level AVP Overload duration AVP, Overload-Action AVP, and Request-sending frequency AVP.
  • the Load level is set.
  • AVP overload minor
  • Overload Action AVP 3
  • Request sending frequency AVP 60 seconds
  • Overload duration - AVP 900 seconds.
  • This set of values means that the request is sent to the party that initiated the overload control (ie, Application B) at a frequency of less than 60 seconds for a duration of 900 seconds.
  • step 105 alleviates the load of application B.
  • Overload_duration—AVP expires, the end-to-end overload control ends, and Application B determines whether it needs to start the overload control again based on its current load status. If necessary, initiate overload control again.
  • 2 illustrates an example of initiating Diameter overload control via a particular CGR/CGA command, in accordance with an embodiment of the present invention. It is particularly important to mention here that CGR/CGA is a new Diameter command that is extended to support the Diameter end-to-end overload control based on the RFC 3588 protocol. This command contains the combination Over_load_ AVP mentioned above.
  • the CGR command that is, the call disconnection request, sends the request to specifically request the remote end to start the overload control process according to the over-load AVP in the command.
  • the CGA command that is, the call break response, sends the CGA command back from the far end if the CGR is accepted or not accepted.
  • application A such as a Diameter client or a Diameter server, finds itself in an overload state, as shown in step 201.
  • the application B receives the CGR request command, decodes the overload AVP, and then determines whether the action can be taken according to the AVP value.
  • the application B determines that the action can be taken according to the AVP value, that is, the load control can be performed in conjunction with the application A, it generates a CGA response command paired with the CGR, and sends the response command CGA to the application A as a reply.
  • the value of resultcodeAVP is set to "2001" ( DIAMETER - SUCCESS ), which means that the request is successful.
  • step 205 application A and application B take corresponding actions based on the value of the overload AVP to perform overload control.
  • Application B no longer sends a request to Application A for a duration of 900 seconds. It was not until 900 seconds expired that the two parties began normal communication.
  • Related request/response messages or CGR/CGA commands in which the forwarding of messages or commands for these intermediate nodes is omitted in the embodiment with reference to FIG. The description is made to make the description of the present invention clearer.
  • the overloaded AVP value can be added to the Diameter response message to notify the other party to start the overload control during the session, or can actively generate the CGR message and the message when it finds that it is in an overload condition. Add an overload AVP value to invite the other party to start overload control.
  • the specific overload control action between Application A and Application B depends on the value of the overload AVP.
  • step 303 application B receives the CGR request command, decodes the overload AVP, and then takes an action to cancel the overload control it is using.
  • step 304 the application B generates a CGA response command, and sends a response command CGA to the application A as a reply, in which the value of the resultcodeAVP is set to
  • FIG. 4 shows a block diagram of an overload control initiating device 400 included in a Diameter application according to an embodiment of the present invention.
  • the Diameter application corresponds to the application A given in Figure 2, namely the overload control initiator.
  • Application A can be a Diameter server or it can be Diameter client.
  • the application A installs the overload control initiation device 400 of the present invention.
  • the device 400 can include an overload control information setting module 401, an assembly module 402, a CGR message generation module 403, and a send response message module 404.
  • the overloaded AVP is assembled, it is sent to the peer according to the existing status via the DIAMETER response message or CGR. In this embodiment, the CGR is sent to the peer.
  • the CGR generation module 403 in the figure is used to generate a CGR command, and the set combination Overload_AVP is added to the CGR generation module 403 by the assembly module 402 to generate a CGR command message, and the related transmission device of the application A (not shown) Show) sending the CGR message to Application B. It is conceivable that if the overload AVP is sent to the peer through a response message such as AAA Diameter, then in this case, the assembled overload AVP is sent to the opposite end via the send response message module 404, which is carried in the Diameter response message.
  • FIG. 5 shows a functional block diagram of the overload control response device 500 of the application B corresponding to the overload control initiating device 400 of the application A in FIG.
  • the apparatus 500 further includes a CGA generation module 501, an overload control initiation module 501, a timer 504, a timer 505, and the like.
  • the CGA 501 receives the CGR request command, decodes the overloaded AVP, and then determines whether an action can be taken in accordance with the AVP value.
  • the application B determines that the action can be taken according to the AVP value, that is, the application A can be used for overload control, it generates a CGA response command paired with the CGR, and sends the response command CGA to the application A as a reply, in which the response command is used.
  • the value of resultcode AVP is set to "2001", which means that the request is successful.
  • FIG. 4 and 5 illustrate an overload control initiating device 400 and an overload control response device 500, respectively, in accordance with an embodiment of the present invention, which are known to those skilled in the art in understanding the principles of the present invention.
  • the apparatus and modules may be implemented by computer software, and the apparatus and modules themselves may be variously modified within the scope of the basic idea of the invention.
  • both the Diameter server and the Diameter client can actively initiate overload control, and both can respond to the overload control initiated by the peer. Therefore, the Diameter application preferably includes both an overload control initiator. Also included is an overload control response device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Computer And Data Communications (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明提出一种在基于Diameter协议的第一应用和第二应用之间进行过载控制的方法,该方法包括:当第一应用过载时,设置过载控制信息并发送到第二应用;以及,第二应用根据所述过载控制信息采取动作。本发明还提出一种基于Diameter协议、包括过载控制发起装置的网络单元,该过载控制发起装置被配置为:当发生过载时设置过载控制信息以发送到和所述网络单元通信的对端网络单元。另外,本发明还提出一种基于Diameter协议、包括过载控制响应装置的网络单元,该过载控制响应装置被配置为:当接收到对端发送来的过载控制信息时,根据所述过载控制信息采取动作。

Description

Diameter应用的端到端过载控制方法和网络单元 技术领域
本发明涉及通信领域,更具体地涉及 Diameter应用的端到端过载控制 方法和实现该方法的网络单元。 背景技术
RFC 3588中定义的 Diameter 出协议旨在为诸如网^ 入服务或移 动 IP的应用提供认证、 授权和计费(AAA )框架。 当前的 Diameter标准 文件规定了要被所有的 Diameter应用使用的消息格式、 传输、 错误报告、 计费和安全服务。 协议元素由众多命令和 AVP (属性值对)构成, 可以在 客户机、 代理、 服务器之间传递认证、 授权和计费信息。 但是不管是客户 机、 代理还 ^艮务器, 都可以主动发出会话请求, 对方给予应答, 所以也 被称为对等实体间的协议。 命令代码、 AVP值和种类都可以按应用需要和 规则进行扩展。
在 IP网络中, 越来越多的标准、 规范和 IP产品使用 Diameter作为 AAA和其他控制协议。 这里的 IP网络例如 TISAPN、 3GPP、 3GPP2标 准中定义的 IPQoS控制子系统、 下一代网络(NGN )、 IP 多媒体子系统 ( IMS )。 Diameter是用于不同单元之间的接口的最普遍的协议。
由于 Diameter相对来说是一种新协议, 还没有用于端到端 Diameter 应用过载控制的现有方法。这是 Diameter协议中的一大缺陷, 因为考虑到 容量、 性能和可靠性, 过载控制是产品的关键功能之一。 发明内容
为了克服上迷缺陷,本发明为 Diameter应用提供了足够的端到端过载 控制和使用 Diameter协议的产品。 采用本发明, Diameter应用 (服务器 / 客户机)可以告诉其远端 Diameter应用其负载状态和过载控制请求,这样 当过载发生时, 两端都可以采取行动, 以保护当前的和重要的 Diameter 会话, 并且迅速地使过载状态回到正常。
为此,本发明提出了一种在基于 Diameter协议的第一应用和第二应用 之间进行过载控制的方法, 包括:
当笫一应用过载时, 设置过载控制信息并发送到第二应用; 以及 第二应用根据所述过载控制信息采取动作。
才艮据本发明的一个实施例,所述过载控制信息经由 Diameter响应消息 发送到所述第二应用。
才艮据本发明的另一个实施例 , 所述过载控制信息经由呼叫间断请求 CGR消息发送到所述第二应用。
根据本发明的实施例, 所述过载控制信息是组合的过载属性值对。 所 述组合的过载属性值对包括定义负载当前状态的负载等级属性值对, 定义 过载控制持续时间的过载控制持续时间属性值对、 定义过载控制持续时间 内采取的动作的过载控制动作属性值对、 定义过载控制持续时间内请求消 息的发送频率的请求发送频率属性值对。
本发明还提出一种基于 Diameter协议的网络单元,其包括过载控制发 起装置, 所述过载控制发起装置被配置为: 当发生过载时设置过载控制信 息以发送到和所述网络单元通信的对端网络单元。
另夕卜,本发明还提出一种基于 Diameter协议的网络单元,其包括过载 控制响应装置, 所述过载控制响应装置被配置为: 当接收到对端发送来的 过载控制信息时, 根据所述过载控制信息采取动作。
本发明的过载控制机制是 Diameter服务器和 Diameter客户机之间端 到端的过载控制机制, 这样过载信息、 请求和响应可以经由多于一个 Diameter 代理或中继节点从一个 Diameter 应用被发送到任一个其它 Diameter应用, 并且中间 Diameter代理或中继节点不必支持或知道该方 法或采取任何行动, 它们只是将 Diameter命令 /AVP透明地转发, 这将节 省在这些中间 Diameter节点上的工作量。 附图说明
图 1 示出 据本发明的实施例, 经由 Diameter 响应消息来启动 Diameter过载控制的例子;
图 2示出根据本发明的实施例, 经由特定的 CGR/CGA命令来启动 Diameter过载控制的例子;
图 3示出才艮据发明的实施例取消过载控制的例子;
图 4根据本发明的实施例示出 Diameter应用包含的过载控制发起装置 的例子; 以及
图 5根据本发明的实施例示出 Diameter应用包含的过载控制响应装置 的例子。 具体实施方式
下面连同表示本发明原理的附图一起提供本发明的一个或多个实施 例的详细描述。 尽管结合这些实施例来描述本发明, 但是本发明并不局限 于任何实施例。本发明的范围由权利要求书限定,并且包括各种可选方式、 修改和等效替换。 为了完整地理解本发明, 在下面的描述中提出了许多特 定的细节。 提供这些细节完全出于举例的目的, 本发明可以在不具有这些 特定细节的部分或全部的情况下根据权利要求书而实现。 为清楚起见, 与 本发明相关的技术领域中已知的技术资料不再详细描述, 以避免不必要地 模糊本发明。
在这里需要特别说明的是, 在发明的实施例中使用 AAR 和 AAA DIAMETER 消息作为具体应用的请求和响应, 实际上本发明的方法可以 借助于任何 DIAMETER的请求和响应来实现。
图 1示出经由 Diameter响应消息来启动 Diameter过载控制的例子。 在该例子中, 涉及到的实体是应用 A、 应用 B, 应用 A可以是 Diameter 服务器,应用 B是 Diameter客户机,或者应用 A可以是 Diameter客户机, 应用 B是 Diameter服务器 , 无论 务器还是客户机都有可能主动发起 过载控制请求。 另外, 应用 A和应用 B之间可能存在一个或多个代理 /中 级节点, 我们称它们为 "中间节点", 这些中间节点在不参与过载控制的 情况下, 只需要透明地转发过载请求或响应消息。 在图 1中, 如步骤 101 所示, 假设应用 A向应用 B发送 AAR (认证、 授权请求), 中间节点透明 转发该 AAR请求。 步骤 102中, 应用 B发现自己例如因为负载较重不能 处理该 AAR消息; 那么在步驟 103中, 应用 B在准备向应用 A回送的响 应 AAA消息中填充过载 AVP并将 resultcode AVP的值设置为 "too busy"。 在步骤 104中, 应用 B向应用 A发送该响应 AAA消息, 同样地, 中间节 点不参与过载控制, 透明地将该消息转发给应用 A。 最后, 在应用 A接受 该响应 AAA消息时, 它发现消息中的过载 AVP, 并依据过载 AVP的值采 取相应的动作, 如步骤 105所示。
为了描述步骤 105中进行的具体过载控制动作, 先介绍一下本发明中 的过载 AVP, 根据本发明的优选实施例, 这里的过载 AVP 可以是组合 Over— load— AVP, 该 AVP是为实现本发明的过载控制机制而提出的新的 Diameter AVP, 其中包含了负载状态和过载控制请求, 用于 Diameter应 用端到端过载控制, 并且该 AVP可以包含在任何 Diameter响应消息或者 包含在任何 Diameter命令中。组合 Over— load— AVP可以包含以下子 AVP:
• Load_level_AVP, 即负载等级 AVP, 该 AVP表示 Diameter应用 的负载状态,它的值可以是例如 overload— minor (轻微过载)、 overload_critical (严重过载)、 normal (正常)等。 当然, 根据实 际需要可以对等级作更细致的划分。
• Overload_duration_AVP, 即过载控制持续时间 AVP。 该 AVP表 示过载控制请求的使用期限。
• Overload— Action— AVP, 即被请求进行过载控制的 Diameter应用 一方需要采取的动作。 下面的例子给出值为 0 - 4时相应的过载控 制动作:
o 0—不要再发送任何请求;
o 1— 只发送紧急请求;
o 2 -只对在用 Diameter 回话发送请求; o 3 -只以低于该 AVP中的值的频率发送请求;
o 4 -取消过载控制动作。这种情况用于当 diameter应用不再 过载并且希望取消之前的 overload—AVP。
o 其它可能的值。
• Request—sending— frequency—AVP。这个 AVP表示被请求的一方可 以向请求过载控制的一方发送的最大发送频率, 当然, 如前面所 述, 本发明中发起过载控制的应用可以是 diameter客户机, 也可 以是 diameter服务器。
在该例中, 如前面已经提到的, 步骤 105 中, 在应用 A接收该响应 AAA消息时, 它发现消息中的过载 AVP, 并依据过载 AVP的值采取相应 的动作。应用 A采取的动作的依据是组合 Over— load— AVP, 即前面提到的 Load level AVP Overload duration AVP、 Overload— Action AVP 以及 Request— sending frequency AVP , 例如 , 在该实施例 中 , 设定 Load level AVP = overload minor (轻微过载 ), Overload Action AVP = 3, Request sending frequency AVP = 60 秒, Overload duration— AVP = 900秒。 该組值意味着, 在 900秒的持续时间内, 以低于 60秒的频率向发 起过载控制的一方 (即应用 B )发送请求。
那么在步骤 105 中, 应用 A 响应于应用 B 的请求, 才艮据组合 Over— load— AVP的值, 在应用 B的配合下主要执行以下过载控制动作: 例 如, 应用 A在接收该响应 AAA消息时, 等待 60秒以后, 才会向应用 B 发送一个 AAR请求, 应用 B正常地处理该消息, 然后向应用 A发送例如 resultcode = 2001的 AAA响应消息; 应用 A接收 AAA响应消息,再过 60 秒之后, 应用 A才会向应用 B发送另一个 AAR请求, 应用 B正常地处理 该消息,然后向应用 A发送例如 resultcode = 2001的 AAA响应消息, , 类似的处理一直进行着, 直到 900秒的持续时间期满。
步骤 105中的处理,减轻了应用 B的负载。当 Overload—duration— AVP 期满时, 端到端过载控制结束, 应用 B会根据目前其负载状态确定是否需 要再次启动过载控制。 如果需要则再次发起过载控制。 图 2示出根据本发明的实施例, 经由特定的 CGR/CGA命令来启动 Diameter过载控制的例子。 这里特別需要提一下的是, CGR/CGA是为支 持 Diameter端到端过载控制,在 RFC 3588协议基础上扩展的新 Diameter 命令。 该命令包含以上提到的组合 Over_load— AVP。 CGR命令, 即呼叫 间断请求,发送该请求意味着专门请求远端根据该命令中的 over-load AVP 开始过载控制过程。 CGA命令, 即呼叫间断响应, 在 CGR被接受或者不 被接受的情况下, 从远端发回该 CGA命令。
在该例子中,诸如 Diameter客户机或 Diameter服务器的应用 A发现 自己处于过载状态, 如步骤 201所示。 这里, 取决于应用 A的具体应用情 况可以有艮多种现有技术来 "发现" 过载, 例如最常见的通过 CPU或内 存的使用情况来判断是否过载, 用户由此可以自己设定相应的过载门限。 在步驟 202 中, 应用 A组装过载 AVP值, 例如设定 Load_level—AVP = overload— critical, Overload— Action— AVP = 0, Overload— duration— AVP = 900秒, 设定好的組合 Overload— AVP 丈入 CGR命令中, 并且向应用 B 发送该 CGR请求命令。 在步骤 203中, 应用 B接收 CGR请求命令, 对 过载 AVP进行解码, 然后确定是否能依照 AVP值采取动作。 在步骤 204 中,如果应用 B确定可以依照 AVP值采取动作,也就是说可以配合应用 A 进行过载控制, 它会生成与 CGR配对的 CGA响应命令,并且将响应命令 CGA发送给应用 A作为回复,在该响应命令中, resultcodeAVP的值皮设 置为 "2001" ( DIAMETER— SUCCESS ), 该值意味着告诉对方请求成功。
最后, 在步骤 205中, 应用 A和应用 B基于过载 AVP的值采取相应 的动作来进行过载控制。 根据組合 OverJoad_AVP 的一組值, 特别是 Overload— Action— AVP = 0, Overload— duration— AVP = 900秒, 应用 B在 900秒的持续时间内, 不再向应用 A发送请求。 直到 900秒时间届满, 双 方才开始正常的通信。 需要注意的是, 如前文所述, 应用 A和应用 B之间 可能存在一个或多个起代理和中继作用的中间节点, 这些中间节点在不参 与过载控制的情况下,只需要透明地转发相关请求 /响应消息或 CGR/CGA 命令, 在参照图 2的实施例中省略了对于这些中间节点转发消息或命令的 描述, 以使得本发明的描述更加清晰。
以上参照图 1和图 2的描述给出了如何触发过载控制机制的例子。 通 过描述, 本领域技术人员很清楚地认识到可以在会话过程中通过在 Diameter响应消息中添加过载 AVP值来通知对方开始过载控制, 也可以 在发现自己处于过载状况时主动生成 CGR 消息以及在消息中添加过载 AVP值来邀请对方开始过载控制。 应用 A和应用 B之间的具体过载控制 动作取决于过载 AVP的值。
在结合图 1和图 2的实施例中, 有可能出现这样的情况, 即在过载控 制持续时间未达到时,之前处于过载情况而发起过载控制的 Diameter应用 发现自己已经处于正常负载状况。 在这种情况下, 没有必要再把过载控制 过程进行下去, 处于这样的考虑, 图 3示出根据发明的实施例取消过载控 制的例子。
在图 3中,应用 A用 CGR命令启动了 Diameter过载控制,但是一段 时间后, 可能还没有等到整个负载控制过程结束, 应用 A发现自己的工作 负载回到了正常状态, 如步骤 301所述, 这时, 它希望远端了解这种改变, 以便结束过载控制。 于是在步骤 302中, 应用 A组装过载 AVP值, 例如 设定 Load— level— AVP = normal (正常), Overload Action— AVP = cancel
(取消), 设定好的組合 Overload— AVP CGR命令中, 并且向应用
B发送该 CGR请求命令。 在步驟 303中, 应用 B接收 CGR请求命令, 对过载 AVP进行解码, 然后采取动作取消它正在使用的过载控制。 接着, 在步骤 304中, 应用 B生成 CGA响应命令, 并且将响应命令 CGA发送 给应用 A作为回复, 在该响应命令中, resultcodeAVP的值被设置为
"2001" , 该值意味着告诉对方请求取消过载控制的操作成功。 最后, 在步 骤 305中, 应用 A和应用 B都回到 Diameter会话 /事务处理的正常控制状 态。
图 4示出根据本发明实施例的 Diameter应用所包含的过载控制发起装 置 400的结构图。为了描述方便,该 Diameter应用对应于图 2中给出的应 用 A, 即过载控制发起方。 应用 A 可以是 Diameter 服务器也可以是 Diameter客户机。 如图所示, 应用 A安装了本发明的过载控制发起装置 400, 装置 400可以包括过载控制信息设置模块 401、 装配模块 402、 CGR 消息生成模块 403以及发送响应消息模块 404。过载控制信息设置模块 401 响应于例如负载状态感知模块(图中未示出 )等的其它功能单元 "发现 " 的过载状态设置组合的过载 AVP 值, 例如设定 Load—level_AVP - overload— critical, Overload Action AVP = 0, Overload— duration AVP = 900秒。 过载 AVP装配完成后, 根据现有状态经 DIAMETER响应消息或 CGR发给对端, 在本实施例中, 由 CGR发给对端。 图中的 CGR生成模 块 403用于生成 CGR命令, 设定好的组合 Overload— AVP通过装配模块 402被添加到 CGR生成模块 403中生成 CGR命令消息,并且由应用 A的 相关发送装置(图中未示出) 向应用 B发送该 CGR消息。 可以设想, 如 果过载 AVP通过 AAA Diameter之类的响应消息发送给对端 ,那么在这种 情况下, 装配好的过载 AVP经发送响应消息模块 404, 承载于 Diameter 响应消息中被发送到对端。
相应地, 图 5给出与图 4中的应用 A的过载控制发起装置 400相对应 的应用 B的过载控制响应装置 500的功能框图。装置 500进一步包括 CGA 生成模块 501、 过载控制启动模块 501、 定时器 504、 定时器 505等。 CGA 501接收 CGR请求命令,对过载 AVP进行解码,然后确定是否能依照 AVP 值采取动作。 如果应用 B确定可以依照 AVP值采取动作, 也就是说可以 配合应用 A进行过载控制, 它会生成与 CGR配对的 CGA响应命令, 并 且将响应命令 CGA发送给应用 A作为回复, 在该响应命令中, resultcode AVP 的值被设置为 "2001", 该值意味着告诉对方请求成功。 过载控制启 动模块 502 用于根据組合的 AVP 值中的过载控制信息, 特别是 Overload— Action— AVP = 0, Overload_duration_AVP = 900 秒, 采取相应 的动作来进行过载控制。 这里, 假设定时器 504是用于对过载控制持续时 间进行计时的定时器, 那么过载控制响应装置 500在开始过载控制时启动 定时器 504, 在 900秒的定时器超时时间内, 过载控制启动模块 502将同 时根据 Overload— Action一 AVP = 0 (该值意味着不再发送任何请求), 抑制 AAR请求的发送, 直到该持续时间期满。
图 4和图 5分别根据特定实施例介绍了根据本发明实施例的过载控制 发起装置 400和过载控制响应装置 500, 对于本领域技术人员而言, 在了 解本发明原理的基^ I上, 这些装置和模块可以通过计算机软件来实现, 而 且这些装置和模块本身可以在本发明基本思想的范围内进行各种修改。 另 外, 由于根据本发明的 Diameter 应用, 无论是 Diameter 服务器还是 Diameter客户机, 都可以主动发起过载控制, 并且都可以响应对端发起的 过载控制, 因此, Diameter应用优选地既包括过载控制发起装置, 也包括 过载控制响应装置。
尽管已经结合了特定装置和特定的实施细节描述了本发明的原理, 应 当理解, 本说明书是以举例方式作出的, 而不是对本发明范围的限制。 通 过考虑此处公开的本发明的基本原则和实施例, 对于本领域技术人员来 说, 本发明的其它实施例将变得显而易见。 本发明的范围由所附的权利要 求限定。

Claims

权利要求
1. 一种在基于 Diameter协议的第一应用和第二应用之间进行过载控 制的方法, 包括:
当笫一应用过载时, 设置过载控制信息并发送到第二应用; 以及 第二应用根据所述过载控制信息采取动作。
2, 如权利要求 1所述的过载控制方法,其中所述过载控制信息经由任 何 Diameter响应消息发送到所述第二应用。
3. 如权利要求 1所述的过载控制方法,其中所述过载控制信息经由呼 叫间断请求 CGR发送到所述第二应用。
4. 如权利要求 3所述的过载控制方法,进一步包括所述第二应用向所 述第一应用返回呼叫间断响应 CGA。
5. 如权利要求 1所迷的过载控制方法, 其中, 所述过载控制信息是组 合的过载属性值对, 所述组合的过载属性值对包括以下过载属性值对中的 一个或多个:
负载等级属性值对, 用于定义负载当前状态;
过载控制持续时间属性值对, 用于定义过载控制持续时间;
过载控制动作属性值对, 用于定义过载控制持续时间内采取的动作; 以及
请求发送频率属性值对, 用于定义过载控制持续时间内请求消息的发 送频率。
6. 如权利要求 5所迷的过载控制方法,进一步包括在所述过载控制持 续时间内, 如果所述第一应用的负载状态已经恢复到正常状态, 则向所述 第二应用发送取消过载控制的命令消息。
7. 如权利要求 5所述的过载控制方法,其中所述动作包括下面组中的 任何一个: 不再发送任何请求消息、 只发送紧急请求、 只为在用 Diameter 会话发送请求、 只以低于属性值对中定义的请求发送频率发送请求、 取消 过载控制。
8. —种基于 Diameter协议的网络单元, 其包括过载控制发起装置, 所述过载控制发起装置被配置为: 当发生过载时设置过载控制信息以发送 到和所述网络单元通信的对端网络单元。
9. 如权利要求 8所述的网絡单元,其中所述过载控制发起装置被进一 步配置为将所述过载控制信息添加到任何 Diameter响应消息。
10. 如权利要求 8所述的网络单元, 其中所述过载控制发起装置被进 一步配置为生成呼叫间断请求 CGR。
11. 如权利要求 10所述的网络单元,其中所述过载控制发起装置被进 一步配置为将所述过载控制信息添加到所述呼叫间断请求 CGR。
12. 一种基于 Diameter协议的网络单元, 其包括过载控制响应装置, 所述过载控制响应装置被配置为: 当接收到对端发送来的过载控制信息 时, 根据所述过载控制信息采取动作。
13. 如权利要求 12所述的网络单元,其中所述过载控制响应装置被进 一步配置为: 当接收到对端发送的呼叫间断请求 CGR时, 生成呼叫间断 响应 CGA。
PCT/CN2008/000946 2008-05-15 2008-05-15 Diameter应用的端到端过载控制方法和网络单元 WO2009137956A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
EP08748501.7A EP2280520A4 (en) 2008-05-15 2008-05-15 METHOD AND NETWORK ELEMENT FOR CORRECTING END-TO-END OVERLOAD BASED ON DIAMETER APPLICATION
KR1020107028231A KR101440670B1 (ko) 2008-05-15 2008-05-15 과부하 제어 방법 및 다이어미터 프로토콜 기반의 네트워크 요소
JP2011508785A JP5242773B2 (ja) 2008-05-15 2008-05-15 ダイアメータアプリケーションに基づいて、エンドツーエンド過負荷を制御するための方法およびネットワーク要素
PCT/CN2008/000946 WO2009137956A1 (zh) 2008-05-15 2008-05-15 Diameter应用的端到端过载控制方法和网络单元
CN200880129218XA CN102027725A (zh) 2008-05-15 2008-05-15 Diameter应用的端到端过载控制方法和网络单元
US12/990,847 US20110061061A1 (en) 2008-05-15 2008-05-15 Method and network elements of end-to-end overload control for diameter applications

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2008/000946 WO2009137956A1 (zh) 2008-05-15 2008-05-15 Diameter应用的端到端过载控制方法和网络单元

Publications (1)

Publication Number Publication Date
WO2009137956A1 true WO2009137956A1 (zh) 2009-11-19

Family

ID=41318329

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/000946 WO2009137956A1 (zh) 2008-05-15 2008-05-15 Diameter应用的端到端过载控制方法和网络单元

Country Status (6)

Country Link
US (1) US20110061061A1 (zh)
EP (1) EP2280520A4 (zh)
JP (1) JP5242773B2 (zh)
KR (1) KR101440670B1 (zh)
CN (1) CN102027725A (zh)
WO (1) WO2009137956A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101123405B1 (ko) 2010-08-31 2012-03-23 주식회사 인스프리트 Diameter 프로토콜을 사용하여 종단간 혼잡제어를 하는 노드시스템 및 그 제어방법

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9860390B2 (en) 2011-08-10 2018-01-02 Tekelec, Inc. Methods, systems, and computer readable media for policy event record generation
US9281950B2 (en) 2011-10-07 2016-03-08 Alcatel Lucent Method for using intelligent router in charging system and apparatus associated therewith
CN103095484B (zh) * 2011-11-01 2019-01-08 中兴通讯股份有限公司 一种as异常的处理方法及系统
US8756455B2 (en) 2011-11-17 2014-06-17 Microsoft Corporation Synchronized failover for active-passive applications
EP2837147B1 (en) * 2012-04-13 2022-04-27 Tekelec, Inc. System for performing diameter overload control
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
US11159980B2 (en) * 2014-07-22 2021-10-26 Parallel Wireless, Inc. Signaling storm reduction from radio networks
US9680965B2 (en) * 2015-04-01 2017-06-13 Alcatel-Lucent Usa Inc. Software upgrades for offline charging systems within a network
US9917729B2 (en) 2015-04-21 2018-03-13 Oracle International Corporation Methods, systems, and computer readable media for multi-layer orchestration in software defined networks (SDNs)
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
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
US10103955B2 (en) 2015-10-01 2018-10-16 Oracle International Corporation Methods, systems, and computer readable media for transmitting diameter peer status information
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)
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

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1889563A (zh) * 2005-06-30 2007-01-03 华为技术有限公司 基于Diameter协议的负载控制方法
CN101150512A (zh) * 2007-10-23 2008-03-26 中兴通讯股份有限公司 实现通信链路负载均衡的方法

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5548533A (en) * 1994-10-07 1996-08-20 Northern Telecom Limited Overload control for a central processor in the switching network of a mobile communications system
FI97185C (fi) * 1994-11-11 1996-10-25 Nokia Telecommunications Oy Ylikuormituksen esto tietoliikenneverkon solmussa
US5878224A (en) * 1996-05-24 1999-03-02 Bell Communications Research, Inc. System for preventing server overload by adaptively modifying gap interval that is used by source to limit number of transactions transmitted by source to server
JP2001339465A (ja) * 2000-05-26 2001-12-07 Mitsubishi Electric Corp メッセージフロー制御方法および通信システム
US20020173316A1 (en) * 2001-02-12 2002-11-21 Nortel Networks Limited Method and system for preventing access overload in mobile phone systems
JP2004172782A (ja) * 2002-11-19 2004-06-17 Fujitsu Ltd サービス制御ネットワークシステム
JP2005027192A (ja) * 2003-07-04 2005-01-27 Fujitsu Ltd ネットワーク・アドレス割当装置
US7768909B1 (en) * 2003-10-28 2010-08-03 At&T Intellectual Property Ii, L.P. Congestion control in an IP network
JP4189379B2 (ja) * 2004-12-27 2008-12-03 株式会社日立製作所 アプリケーション運用制御方法およびシステム
US8045473B2 (en) * 2005-11-28 2011-10-25 Cisco Technology, Inc. Tailored relief for congestion on application servers for real time communications
JP4830486B2 (ja) * 2005-12-27 2011-12-07 株式会社ナカヨ通信機 無線lanシステムおよび無線lan端末
US8312120B2 (en) * 2006-08-22 2012-11-13 Citrix Systems, Inc. Systems and methods for providing dynamic spillover of virtual servers based on bandwidth
US8660009B2 (en) * 2008-01-30 2014-02-25 Telefonaktiebolaget L M Ericsson (Publ) Core network processing load reduction

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1889563A (zh) * 2005-06-30 2007-01-03 华为技术有限公司 基于Diameter协议的负载控制方法
CN101150512A (zh) * 2007-10-23 2008-03-26 中兴通讯股份有限公司 实现通信链路负载均衡的方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101123405B1 (ko) 2010-08-31 2012-03-23 주식회사 인스프리트 Diameter 프로토콜을 사용하여 종단간 혼잡제어를 하는 노드시스템 및 그 제어방법

Also Published As

Publication number Publication date
KR20110014209A (ko) 2011-02-10
EP2280520A4 (en) 2015-03-18
EP2280520A1 (en) 2011-02-02
CN102027725A (zh) 2011-04-20
KR101440670B1 (ko) 2014-09-19
US20110061061A1 (en) 2011-03-10
JP2011521334A (ja) 2011-07-21
JP5242773B2 (ja) 2013-07-24

Similar Documents

Publication Publication Date Title
WO2009137956A1 (zh) Diameter应用的端到端过载控制方法和网络单元
JP5173607B2 (ja) 通信システム
US20050213580A1 (en) System and method for enforcing policies directed to session-mode messaging
US7484240B2 (en) Mechanism to allow authentication of terminated SIP calls
WO2005114906A1 (fr) Procede et systeme d'obtention d'informations d'etat de noeuds de reseau sip
WO2007016851A1 (fr) Procede etablissant un canal de transmission de donnees pour dialogue en ligne afin de realiser la transmission du message
WO2006010312A1 (fr) Procede d'information de la modification de capacite au terminal au reseau
JP5318871B2 (ja) 時間依存通信を最適化する方法及び通信ノード
WO2007098714A1 (fr) Dispositif et procédé de contrôle de session
JP5504315B2 (ja) ページモードメッセージング
JP2008501265A (ja) プロトコルのためのタイマー制御情報の供給
WO2009018755A1 (fr) Procédé de session multi-terminal, système de communication et dispositifs associés
JP5265584B2 (ja) Sipベースのメディアサービスにおけるセッション制御
US20060271686A1 (en) Combining SIP requests with SIP responses
WO2010072129A1 (zh) 一种注册方法、边界代理设备及通信系统
WO2008141562A1 (fr) Procédé et système de réalisation de service de messagerie, et serveur d'application de messagerie
CN112261336B (zh) 一种融合gb28181协议实现手机视频通信的方法
WO2007095837A1 (fr) Procédé, dispositif et système de réception par un terminal d'un message de confirmation
WO2014117506A1 (zh) 一种向群组成员发送多媒体消息的方法及设备
WO2012071882A1 (zh) 会话检测方法、装置及会话初始协议服务器
JP5355357B2 (ja) 基地局装置、無線端末装置、および呼セッション維持方法
WO2010020121A1 (zh) 消息发送过程中切换终端的方法及设备
JP4905325B2 (ja) コンテンツ提供システムおよび監視サーバ
US8688848B2 (en) Method of establishing a media link for transmitting a large message mode CPM message to a group
CN111327562B (zh) 一种会话的检测方法、会话系统及存储介质

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200880129218.X

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08748501

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 12990847

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2008748501

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2011508785

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 8086/CHENP/2010

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 20107028231

Country of ref document: KR

Kind code of ref document: A