WO2006076850A1 - Procede de traitement pour la gestion de surcharge de dispositif dans un reseau de communication - Google Patents
Procede de traitement pour la gestion de surcharge de dispositif dans un reseau de communication Download PDFInfo
- Publication number
- WO2006076850A1 WO2006076850A1 PCT/CN2006/000006 CN2006000006W WO2006076850A1 WO 2006076850 A1 WO2006076850 A1 WO 2006076850A1 CN 2006000006 W CN2006000006 W CN 2006000006W WO 2006076850 A1 WO2006076850 A1 WO 2006076850A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- overload
- service
- overloaded
- route
- peripheral
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/11—Identifying congestion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/122—Avoiding congestion; Recovering from congestion by diverting traffic away from congested entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/17—Interaction among intermediate nodes, e.g. hop by hop
Definitions
- the present invention relates to a Diff-serv (Differentiated Service) technology with an independent bearer layer, and more particularly to a processing technology for dealing with device overload in a communication network that distinguishes Diff-serv, especially an IP telecommunication network.
- Diff-serv Differentiated Service
- the differentiated service model only sets the priority guarantee Qo$ measure. Although the QoS measure has the characteristics of high line utilization, the specific effect is difficult to predict. Therefore, in order to further improve the QoS technology, the industry began to differentiate the service model for the backbone network into a separate bearer control layer, and establish a special QoS signaling mechanism that differentiates the service model. This differentiated service model is called a differentiated service model with an independent bearer control layer.
- FIG. 1 is a structural diagram of a differentiated service model with an independent bearer control layer applied to an IP telecommunication network.
- the bearer control layer 102 is placed between the bearer network 103 and the service control layer 101.
- the Call Agent (CA) in the service control layer 101 is a service server, such as a softswitch, a video on demand (VOD) control server, a routing gatekeeper (GK, Gate Keeper), etc., and the CA receives a call request from the user equipment.
- CA Call Agent
- the proxy user equipment completes the call and exchange, only two CAs are given in this figure, but the CA involved in a call may also have one or one; in the bearer control layer 102, bearer network resource management (CM) has passed the dynamics
- CM bearer network resource management
- the learning or static configuration has the topology of the core node, the label switched path (LSP) and the path resource information of the bearer network.
- LSP label switched path
- the resource manager calculates the service path resource information and pre-
- bearer network resource manager 1 bearer network resource manager 1 (104), bearer network resource manager 2 (105), and bearer network resource manager 3 (106).
- each bearer network resource manager transmits signaling request and result of the service to the service and the routing path information allocated for the service request.
- each bearer network resource manager manages a specific bearer network area! This specific bearer network area is referred to as the corresponding management domain of the bearer network resource manager. In this figure, the bearer network resource management is performed.
- the ER" core router and BR belong to the bearer network and are collectively referred to as the connection node (CN, Connection N ⁇ de).
- the terminal equipment of the service connection has a wide range of distribution, and the signaling process involved in the service connection also has a large number of intermediate devices.
- the service When the service is connected or disconnected, the service may appear.
- some devices are running at full load, when the device is overloaded, a corresponding processing mechanism is needed to eliminate the unfavorable factors caused by the overload of the device.
- the overload processing mechanism is lacking in the prior art.
- the related device of the service connection cannot reasonably automatically guide the establishment of the subsequent service connection and cause the network to operate. The efficiency is very low, and the processing delay of the business connection is very long. Summary of the invention
- the main object of the present invention is to provide a parent network overload in a communication network.
- the processing method when the device is overloaded, enables the related devices of the service connection to automatically and automatically guide the establishment of the subsequent service connection, improve the operation efficiency of the network, and shorten the delay of the service connection.
- the technical solution adopted by the present invention is:
- a method for processing equipment overload in a communication network is applicable to a communication network having an independent bearer control layer, and the method includes:
- the overload threshold is set in the device involved in the service connection. During the operation, the device detects whether the processing capability of the device is overloaded. If the device is overloaded, the device sends an overload alarm carrying the address of the overload device to its peripheral device. The message, the peripheral device receiving the 3 ⁇ 4 load alarm message, limits the service passing through the overload device.
- the specific method for the peripheral device to limit the service of the overloaded device is: the peripheral device adjusts the routing policy, and preferentially selects a route that does not pass the overloaded device for the service connection.
- the specific method for the peripheral device to preferentially select a route that does not pass through the device for the service connection is:
- the route that passes the device is marked with an overload identifier, and in the process of selecting a route for the service connection, the route with no overload identifier is preferentially selected; or the priority of the redundant route routed through the device is increased; or The priority of routing through the device is reduced.
- the specific method for the peripheral device to perform the service through the overload device is: the peripheral device restricts the service connection of the service device through the overload device.
- the method further includes: the peripheral device returns an overload alarm response to the overload device after limiting the service passing the overload device; and the overload device detects whether the processing capability of the overload device returns to normal after receiving the response, if If the device returns to normal, the device sends an overload alarm recovery message carrying its own address to its neighboring device.
- the peripheral device that receives the overload alarm recovery message cancels or gradually cancels the service to the overloaded device.
- the method further includes: the overload device detects whether the processing capability of the device returns to normal in real time, and if not, restores the overloaded alarm message carrying the own address to the peripheral device at a predetermined time, and receives the periphery of the overload alarm message.
- the device continues to restrict the service passing the overloaded device; if it returns to normal, the device sends an overload alarm recovery message carrying its own address to its neighboring device; the peripheral device that receives the overload alarm ' ⁇ complex message cancels or gradually cancels the pair
- the traffic passing through the overloaded device is limited.
- the method further comprises: determining, by the peripheral device, whether the service passing through the device is restricted, and determining whether an overload alarm message or an overload alarm recovery message from the overload device is received within a predetermined time, and if not, canceling Or gradually cancel the service passing through the overloaded device to be restricted; if the overloaded alert message is received, the service of the overloaded device is further restricted; if the overloaded alert recovery message is received, the overloaded device is cancelled or gradually cancelled.
- Business restrictions To: cancel the overload indicator of the route passing through the device, or restore the priority of the redundant route passing through the backup route to the original state, or restore the priority of the route passing the device to the original state.
- the specific method for canceling the restriction on the service passing through the overload device is: canceling the restriction on the traffic volume of the service connection through the overload device.
- the method further includes: the overload threshold is divided into one or more overload levels, and the device determines the overload level after detecting the overload, and carries the overload level information in the overload alarm message;
- the peripheral device that receives the overload alarm message limits the service passing through the overload device according to the overload level information.
- the peripheral device of the overload device is an upstream device of the overload device on a specific service connection or a specific service information transmission path.
- the overload threshold is determined according to the processing capability of the device.
- the processing capability of the device is: a running capability of the CPU, a usage of the memory space, a message queue processing capability, or any combination of the three.
- the device involved in the service connection is a control device of a communication network bearer control layer
- the peripheral device is a control device carrying a control layer, a connection contact of a bearer layer, a call agent of a service control layer, or the three random combination.
- the device involved in the service connection is a connection node of a communication network bearer layer
- the peripheral device is a control device carrying a control layer.
- control device of the communication network bearer control layer is a bearer network resource manager, a bearer policy manager, or a bearer resource/policy manager.
- the invention detects whether the device is overloaded in real time when the device is running, if a fish is overloaded, the corresponding level of the overload alarm message is sent to the peripheral device or the upstream device, and the surrounding translation or the upstream device receives the overload alarm message, and then adjusts its own route.
- the policy is to preferentially select a route for the service connection that does not pass the device, and restrict the service connection to use the route passing through the overload device in the routing table according to the overload level to control the service connection service volume. Therefore, the present invention can detect the operation of the network in advance of the establishment of the service connection. Once a related device is overloaded, in the process of establishing the service connection, the related device connected with the service automatically and automatically establishes the subsequent service connection to the node.
- FIG. 1 is a structural diagram of a differentiated service model with an independent bearer control layer applied to an IP power grid;
- FIG. 3 is a flowchart of an overload control when an upstream and downstream relationship of a device is clear according to an embodiment of the present invention
- the core idea of the present invention is: In a communication network having an independent bearer control layer, an overload threshold is set in the device involved in the service connection. During the operation, the device detects whether its processing capability reaches an overload in real time, and if so, sends an overload alarm to its peripheral devices. The overload alarm carries the address of the overload device, and the peripheral device that receives the overload alarm limits the service passing through the overload device.
- the communication network in the embodiment of the present invention is described by taking an ip telecommunication network as an example.
- the technical solutions for implementing the present invention in other communication networks are the same as the technical solutions for implementing the present invention in an IP telecommunication network.
- the processing capability of the device in the present invention mainly refers to the running capacity of the CPU of the device, the occupation of the memory space, and the processing capability of the message queue, for example, the number of instructions currently executed by the CPU, the number of message queues in the memory space, and storage.
- the capacity of the memory block of the business connection/session control information, and so on. are converted into a percentage as a processing capacity overload threshold.
- the overload threshold may have an overload level, which may be a single level or two or more levels. For example, if the CPU of a device executes 200 MIPS (Million Instructions Per Second) per second, the overload level of the processing capability can be set to 1, 2, and 3, and the threshold value. 80%, 90%, 100% respectively.
- the level 1 threshold is reached, and the overload level is 1 level.
- the level 2 is reached.
- Threshold value the overload level at this time is level 2; if current If the MIPS is above 200', the level 3 threshold is reached, and the overload level is 3 i.
- Another example Assume that a device can store 1000 message packets in the memory space, and set the overload level of the processing capability to 1, 2, and 3, and the thresholds correspond to 80%, 90%, and 100%, respectively. between message packets 800 to 900, the overload of level 1; the range 900 to 1000, then the overload level 2; If 1000 or more, the overload level 3; level.
- threshold values are not limited to the percentages listed above. Specifically, the person skilled in the art knows that the percentage of the above-mentioned thresholds can be defined according to the reliability of the device, for example: According to the correspondence between the processing capability of the device in operation and the probability of error or abnormal probability, Based on the reliability of the equipment, determine the threshold value of the equipment overload level.
- the device When the processing capability of a device reaches a certain overload level, the device sends a corresponding level of overload alarm message to the peripheral device.
- the content of the overload alarm message may be extended according to the specific application of the network.
- the category and address of the overload device are mainly included.
- the address is an IP address or other device identifier, such as a MAC address in an Ethernet.
- the contents of the overload alarm message are shown in Table 1:
- the device type is divided into a control device carrying a control layer and a bearer layer network device.
- the control device carrying the control layer mainly refers to the resource manager, the policy manager, and the resource/policy manager in the bearer control layer.
- the bearer layer network device mainly refers to the CN.
- the overload alarm message of the present invention is a single level alarm, and the overload alarm message does not need to include level information;
- the alarm, and in the overload warning message also includes the level information of the overload alarm.
- a person skilled in the art can perform the self-defined overload alarm level according to the overload alarm content.
- the overload alarm level is divided into three levels, which are respectively associated with the overload level ⁇ of the system processing capability. As shown in table 2:
- the establishment of the service connection is usually initiated by the CA, and the service routing and path resource calculation and allocation on the CM are performed, and the QoS policy information is sent to the edge node of the bearer network, and then the response is sent to the CA, and then notified by the CA.
- the user starts communication, and the CN of the bearer network starts forwarding the service flow and performs QoS control.
- the CA and the home CM at the origin of the service connection are not contiguous, a part of the CM in the control layer needs to be carried over to complete the proxy process, that is, proxying between the CA and the home CM at the originating end.
- the CN may also initiate a service connection establishment request to the CM.
- a service connection establishment request to the CM.
- the upstream and downstream sequence of the routing path established on the service connection and the transmission path of the service information there is an upstream and downstream relationship between the related devices for a certain service connection or service information transmission road front. Since the routing process is generally performed from the upstream to the downstream in the routing process, in order to improve the efficiency, if the processing capability of a certain device reaches an overload between devices that can determine the upstream and downstream relationship, the device only sends the upstream device to the upstream device. I4 alarm. However, for the above-mentioned different service connection establishment processes, the upstream and downstream relationships in the IP telecommunication network are not completely determined.
- the device around a device may be its upstream device, and may be its downstream device.
- the CA in the service control layer is the upstream device of the CM in the bearer control layer; if the CM does not have the proxy operation, the service connection initiated by different CAs may cause one of the CMs, for example, CM1.
- CM is another upstream device of CM, such as CM2, may also cause CM1 to be a downstream device of CM2; if the CM has a proxy operation, according to the message request direction established by the service connection, the requester is the upstream device;
- the CN initiates a service connection establishment request, and then M is a downstream device of the CN; otherwise, if the CN passively receives the service connection establishment of the CM, the CM is an upstream device of the CN.
- the present invention separately proposes two solutions. That is: overload control when the upstream-downstream relationship between devices is not clear (ie, two-way overload control), and overload control when the upstream-downstream relationship between devices is clear.
- 2 is an overload control device when the upstream and downstream relationship of the device is unclear according to an embodiment of the present invention;
- the process includes: Step 201: During the running process, the device carrying the control layer and the bearer layer detects whether the processing capability of the device reaches a certain overload level in real time, and if yes, sends a corresponding to the peripheral device. Level device overload alarm message.
- the device overload alarm message carries the device type of the device and the IP address of the device. It is assumed here that the device type is a resource manager device, and peripheral devices adjacent to the overload device are peripheral device A and peripheral device B.
- the device carrying the control layer and the bearer layer is a CN carrying a control layer and a CN carrying a layer.
- the CM If the CM is overloaded, the CM sends an overload alarm message to the neighboring CM, CA or CN, and the device type in the overload alarm message is CM; if the CN is overloaded, the CN goes to the surrounding CM The overload alarm message is sent, and the device type in the overload alarm message is CN.
- Step 202 The peripheral device that receives the overload alarm limits the service passing the overload device according to the internal ⁇ of the overload alarm. Specifically, it mainly includes two restrictions. On one hand, it restricts the routing of service connections by adjusting the service routing strategy, and on the other hand, limits the traffic volume of the service connection.
- the specific manner for adjusting the service routing policy to limit the routing of the service connection is as follows: According to the IP address of the overloaded device, the peripheral device determines that the routing table in the routing table is a redundant route of the route through which the apricot exists, that is, the path is determined first. The destination user terminal address of the route of the overloaded device, and then determines whether there is a route that can reach the same destination address and does not bypass the overloaded device.
- the route is a redundant route. If there is a redundant route, step 202A is performed; otherwise, execution is performed. Step 202B. In step 202A, the priority of the redundant route is increased, or the priority of the route passing through the device is lowered. Therefore, when routing the service connection, the redundant route is preferentially selected to ensure the QoS of the service connection; or, The route passing through the device is marked with an overload identifier. When routing a service connection, the route with the overload identifier cannot be preferentially selected to ensure the QoS of the service connection.
- step 202B the route passing through the device is marked with an overload identifier.
- the route with the overload identifier cannot be preferentially selected, thereby ensuring the QoS of the connection.
- the specific manner of limiting the traffic volume of the service connection is as follows: According to the level of the overload alarm message, the traffic volume of the service connection of the route passing through the device is correspondingly restricted.
- the traffic here refers to the data traffic established by the service connection. If the overload alarm is of multiple levels, the leveling limits the traffic of the service connection. For high-level overload alarms, the traffic of more routes passing through the device is rejected; for low-level overload alarms, the traffic of routes that pass less than the carrier is rejected. For example, for the overload level 1, 2, or 3 in the above example, since the maximum processing capacity of the overload device is 80 1 ⁇ 2, 90 %, and 100 % respectively, the limited traffic corresponding to the overload level is also mapped to 80.
- Step 203 The peripheral device returns an alarm response to the overload device.
- Step 204 The device sends an overload alarm recovery message to the peripheral device, where the device carries the type of the device and the IP address of the device to cancel the overload alarm message.
- Step 205 The peripheral device of the overload device receives the overload alarm recovery command i to cancel or gradually cancel the restriction on the service of the routing device in the routing table in step 202.
- the method mainly includes canceling the limitation of the two aspects. On the one hand, the routing restriction of the service connection is cancelled by the voice adjustment service routing strategy, and the traffic limitation of the service connection is cancelled on the other hand.
- the specific way to cancel the restriction on the service connection by adjusting the service routing policy is as follows:
- the priority of the adjusted redundant route is restored to the original state; or the priority of the route passing through the device is restored to the original state; or the overload identifier of the route passing through the device is cancelled.
- the overload identifier of the route passing through the device is cancelled.
- Step 206 The peripheral device returns an overload alarm recovery response to the overload device, to indicate that the peripheral device cancels the restriction on the corresponding service.
- the upstream and downstream of the devices are clear.
- the advance planning refers to: Clearly configuring whether each device in the IP telecommunication network can send an overload alarm when it is overloaded, and if it can send, determine its upstream device.
- FIG. 3 is a flow chart of overloading when the upstream and downstream relationship of the device is clear according to an embodiment of the present invention.
- the downstream device sends only the corresponding level of the overload alarm message to its neighboring upstream device.
- the specific processing is shown in FIG. 3, and the steps 301 to 306 are respectively the same as the above-mentioned steps 201 to 206, and will not be described here.
- the peripheral device returns an overload alarm response to the overload device after the service of the overload device is restricted. After receiving the response, the overload device detects whether the processing capability of the overload device returns to normal. The device sends an overload alarm recovery message carrying its own address to its own peripheral device.
- peripheral device of the present invention may not return an overload alert response.
- the processing method at this time is different from the above embodiment:
- the overload device detects whether its processing capability returns to normal if it does not receive the overload alarm response. If the device does not return to normal, the device sends an overload alarm message carrying its own address to the peripheral device at a predetermined time. The peripheral device that receives the overload alarm message continues to restrict the service passing through the overload device. If the device returns to normal, the device goes to itself. The peripheral device sends a 4-load alarm recovery with its own address. Re-message; The peripheral device that receives the overload alarm recovery message cancels or gradually cancels the restriction on the service passing through the overloaded device.
- the peripheral device may determine whether an overload alarm message or an overload alarm recovery message from the overload device is received within a predetermined time after limiting the service passing through the overload device, and if not, cancel or gradually cancel the route.
- the service of the overload device is restricted. Through the process of dynamic adjustment, the problem that the peripheral device can continue to restrict the service due to the restriction of the service when the latest information of the overloaded device is not received can be prevented; The overload alarm message continues to restrict the service passing through the overload device; if the overload alarm recovery message is received, the service for the service that has been negotiated is cancelled or gradually cancelled.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Description
一种通信网络中应对设备过载的处理方法 技术领域
本发明涉及有独立承载层的区分服务模型 (Diff-serv, Differentiated Service)技术, 尤其是涉及一种在应用区分 Diff-serv 的通信 1¾络尤其是 IP电信网中, 应对设备过载的处理技术。 发明背景
随着互联网(Internet )规模的不断增大,各种服务质量(QoS , Quality of Service )技术应运而生。 因此, 互联网工程任务组 (IETF, Internet Engineering Task Force)建议了很多服务模型和机制,以满足 Q 的需求。 目前业界比较认可的是在网络的接入和边缘使用综合服务模型
(Int-Serv, Integrated Service),在网络的核心使用区分服务模型 fc>iff-serv, Differentiated Service)。 区分服务模型仅设定优先等级保障 Qo$措施, 该 QoS措施虽然有线路利用率高的特点, 但具体的效果难以预 。 因此, 为了进一步完善 QoS技术, 业界开始为骨干网区分服务模型 j入一个独 立的承载控制层, 建立一套专门的区分服务模型的 QoS信令机制。 这个 区分服务模型被称为有独立承载控制层的区分服务模型。
图 1为有独立的承载控制层的区分服务模型应用于 IP电信网的结构 图。如图 1所示,承载控制层 102置于承载网络 103和业务控制层 101之间。 在业务控制层 101中的呼叫代理(CA, Call Agent )为业务服务器, 比如 软交换、 视频点播(VOD )控制服务器、 路由网守(GK , Gate Keeper ) 等, CA接收用户设备的呼叫请求,代理用户设备完成呼叫的请^和交换, 本图中只给出两个 CA, 但是一个呼叫所涉及的 CA也可能有^个, 也可 能有一个; 在承载控制层 102中, 承载网资源管理器(CM )埠过动态学
习或者静态配置拥有承载网上的核心节点、 标签交换路径(LSP, Label Switched Path )的拓朴结构和路径资源信息,当收到 CA来的资源申请时, 资源管理器计算业务路径资源信息并预留路径资源; 本图 1中 ;只给出三 个承载网资源管理器, 即承载网资源管理器 1 ( 104 ) 、 承载网资源管理 器 2 ( 105 )和承载网资源管理器 3 ( 106 ) , 但承载网资源管琿器的个数 不是一定的, 各个承载网资源管理器相互之间通过信令传递蓉户的业务 宽申请请求和结果、 以及为业务申请分配的路由路径信息專: 在承载 网 103中, 每个承载网资源管理器管理一个特定的承载网区域!, 这个特 定的承载网区域被称为所对应的承载网资源管理器的管理域, 本图中为 承载网资源管理器 1的管理域 107、 承载网资源管理器 2的管理域 108和承 载网资源管理器 3的管理域 109,管理域 107中包括边缘路由器(ER, Edge Router ) 1 10、 核心路由器 111和边界路由器 (BR, Border Router ) 112, 其中, ER能够将用户设备的呼叫业务流接入到承载网或引出 载网, 管 理域 108和管理域 109中也包括核心路由器和边界路由器。 ER」核心路由 器和 BR都属于承载网, 统称为连接节点 (CN, Connection N^de ) 。
通信网絡尤其是 IP 电信网中, 业务连接的终端设备分希范围比较 广, 业务连接的信令过程涉及的中间设备也比较多, 在大容章业务连接 上、 下线的时候, 可能会出现某些设备满负荷运行的情况, 设备过载 时, 需要相应的处理机制消除设备过载导致的不利因素。 但是, 现有技 术中缺乏过载处理机制, 当承载控制层、 或承载层中的设备出现过载情 况时, 会导致业务连接的相关设备无法合理地自动疏导后续业务连接的 建立, 并导致网络的运营效率很低, 业务连接的处理时延很长。 发明内容
有鉴于此, 本发明的主要目的是提供一种通信网络中 父會过载
的处理方法, 当设备过载时, 使得业务连接的相关设备合理地自动疏导 后续业务连接的建立,提高网絡的运营效率,缩短业务连接的处逑时延。 为了实现上述目的, 本发明采用的技术方案是:
一种通信网络中应对设备过载的处理方法, 适用于具有独立承载控 制层的通信网络, 该方法包括:
在业务连接所涉及的设备中设置过载门限, 所述设备在运行过程 中, 实时检测自身的处理能力是否过载, 如果过载, 则该过珠设备向自 身的周边设备发送携带过载设备地址的过载告警消息, 收到 ¾载告警消 息的周边设备对途经该过载设备的业务进行限制。
优选地, 所述周边设备对途经所述过载设备的业务进行限制的具体 方法为: 所述周边设备调整路由策略, 为业务连接优先选用未途经该过 载设备的路由。
优选地, 所述周边设备为业务连接优先选用未途经所述 载设备的 路由的具体方法为:
将途经过载设备的路由标上过载标识, 在后续为业务连接选择路由 的过程中, 优先选择没有过载标识的路由; 或者, 将途经过 设备路由 的冗余路由的优先级升高; 或者, 将途经过载设备路由的优先级降低。
优选地, 所述周边设备对途经所述过载设备的业务进行 i制的具体 方法为: 所述周边设备限制业务连接途经该过载设备的业务壹。
优选地, 所述方法进一步包括: 所述周边设备对途经所述过载设备 的业务进行限制后向过载设备返回过载告警响应; 过载设备收到该响应 后实时检测自身的处理能力是否恢复正常, 如果恢复正常, 则该设备向 自身的周边设备发送携带自身地址的过载告警恢复消息; 收到过载告警 恢复消息的周边设备取消或逐渐取消对途经该过载设备的 务进行限
制。 '
优选地, 该方法进一步包括: 过载设备实时检测自身的处理能力是 否恢复正常, 如果没有恢复正常, 则在预定的时间重新向周边设备发送 携带自身地址的过载告警消息, 收到过载告警消息的周边设备继续对途 经该过载设备的业务进行限制; 如果恢复正常, 则该设备向自身的周边 设备发送携带自身地址的过载告警恢复消息; 收到过载告警 'ΐλ复消息的 周边设备取消或逐渐取消对途经该过载设备的业务进行限制。,
优选地, 该方法进一步包括: 所述周边设备对途经所述 ¾载设备的 业务进行限制后判断在预定的时间内是否收到来自过载设备的过载告 警消息或者过载告警恢复消息, 如果没有则取消或逐渐取消 ^途经该过 载设备的业务进行限制; 如果收到过载告警消息则继续对途 该过载设 备的业务进行限制; 如果收到过载告警恢复消息, 则取消或逐渐取消对 途经该过载设备的业务进行限制。 为: 取消途经过载设备的路由的过载标识, 或者将途经过载谀备路由的 冗余路由的优先级恢复为原状态, 或者将途经过载设备的路 ά的优先级 恢复为原状态。
优选地, 所述取消对途经所述过载设备的业务进行限制的具体方法 为: 取消对业务连接途经该过载设备的业务量的限制。
优选地, 该方法进一步包括: 所述过载门限分为一个或十个以上的 过载级别, 所述设备在检测到自身过载后, 判断过载级别, 并在过载告 警消息中携带过载级别信息; 所述收到过载告警消息的周边设备依照该 过载级别信息分等级对途经该过载设备的业务进行限制。
优选地, 所述过载设备的周边设备为该过载设备在特定业务连接或 特定业务信息传输路径上的上游设备。
优选地, 所述过载门限根据所述设备的处理能力进衧确定。
优选地, 所述设备的处理能力为: CPU的运行能力、 内存空间的占 用情况、 消息队列处理能力、 或该三者的任意組合。
优选地, 所述业务连接涉及的设备为通信网络承载控制层的控制设 备, 所述周边设备为承载控制层的控制设备、 承载层的连接接点、 业务 控制层的呼叫代理、 或该三者的任意组合。
优选地, 所述业务连接所涉及的设备为通信网络承载层的连接节 点, 所述周边设备为承载控制层的控制设备。
优选地, 所述通信网络承载控制层的控制设备为承载网资源管理 器、 承载策略管理器、 或者为承载资源 /策略管理器。
由于本发明在设备运行时, 实时检测自身是否过载, 一鱼过载, 则 向周边设备或上游设备发送相应级别的过载告警消息, 周边译备或上游 设备收到过载告警消息后, 调整自身的路由策略, 为业务连接优先选择 没有途经过载设备的路由, 并按照过载级别相应限制业务连接使用路由 表内途经所述过载设备的路由, 控制业务连接的业务量。 因此, 本发明 可在业务连接建立前提前探测网络的运行情况, 一旦某一相关设备过 载, 在业务连接的建立过程中, 则使与业务连接的相关设备合理自动将 后续业务连接疏导建立到没有过载设备的路由上, 从而使得网络的 QoS 信令流量分布更加合理, 提高业务连接的接通率和网络的运营效率, 使 得业务服务器, 例如 CA, 缩短业务连接的建立的信令处理时 ¾。 附图简要说明 图 1为有独立的承载控制层的区分服务模型应用于 IP电 网的结构 图;
图 2为本发明实施例所述设备上下游关系不明确时进行过载控制的
流程图;
图 3 为本发明实施例所述设备上下游关系明确时过载控制的流程
实施本发明的方式
下面结合附图和具体实施例进一步说明本发明的实施方法。
本发明的核心思想为: 在有独立的承载控制层的通信网络中, 在业 务连接所涉及的设备中设置过载门限。 所述设备在运行过程中, 实时检 测自身的处理能力是否达到过载, 如果达到, 则向其周边设备发送过载 告警。 该过载告警中携带过载设备的地址, 收到过载告警的周边设备对 途经该过载设备的业务进行限制。 本发明的实施例中的通信网络以 ip电信网为例进行说明 |,其他通信 网络中实施本发明的技术方案与在 IP 电信网中实施本发明的技术方案 相同。
本发明所述的设备处理能力主要是指设备的 CPU 的运行能力、 内 存空间的占用情况、 以及消息队列的处理能力等, 例如: CPU当前执行 的指令数量, 内存空间中的消息队列数量、存放业务连接 /会话控制信息 的内存块的容量等等。 将这些因素折算成一个百分比, 作为处理能力过 载门限值。 过载门限可以有过载级别, 所述过载级别可以为单个级别, 也可以为两个或两个以上个级别。例如:假设某设备的 CPU每秒执行的 兆指信令 MIPS ( Million Instructions Per Second ) 的个数为 200个, 可 将处理能力的过载级别设定为 1、 2、 3级, 其门限值分别对 80 %、 90 %、 100 %。 如果该设备的 CPU当前的 MIPS在 160到 180之间, 则达 到 1级门限值,此时的过载级别为 1级; 同理,如果当前的 IvJlPS在 180 到 200之间, 则到达 2级门限值, 此时的过载级别为 2级; 如果当前的
MIPS在 200'以上, 则到达 3级门限值, 此时的过载级别为 3 i级。 又如: 假设某设备的内存空间可存 1000 个消息包, 将处理能力的过载级别设 定为 1、 2、 3级, 其门限值分别对应 80 %、 90 %、 100 % , 禾当前内 存的消息包在 800到 900之间, 则过载级别为 1级; 在 900到 1000之 间, 则过载级别为 2级; 如果在 1000以上, 则过载级别为 3 ;级。
上述各级门限值不只限于上述所列出的百分比。 具体的, | 领域的 普通技术人员知道, 上述各级门限值的百分比可根据设备的可靠性来自 行定义, 例如: 根据设备在运行中处理能力与出错概率或异常概率的对 应关系, 在保证设备可靠性的基础上, 确定设备过载级别的门限值。
当某个设备的处理能力到达某一过载級别时, 则该设备向周边设备 发送相应级别的过载告警消息。 该过载告警消息的内容可以稂据网络具 体应用情况进行扩展, 本实施例中, 主要包括过载设备的类€和地址。 所述地址为 IP地址或其他设备标识, 例如以太网中的 MAC ψ址。 过载 告警消息的内容如表 1所示:
上述表 1中, 设备类型分为承载控制层的控制设备以及承载层网络 设备。 承载控制层的控制设备主要指承载控制层中的资源管理器、 策略 管理器、 和或集.资源管理和策略管理为一身的资源 /策略管理器, 承载层 网络设备主要指 CN。 对应于所设置的过载级别, 本发明所述的过载告警消息寸以是单一 级别的报警, 此时过载告警消息中不需包括级别信息; 也可以为多级别
报警, 并在所述的过载告警消息中, 还包括过载告警的级别信息。 本领 域的技术人员可以根据过载告警内容进行自行定义过载告警级别的数 量。 作为一具体应用,'在本实施例中, 根据上述举例中过载級别的门限 值, 过载告警级别分为 3级, 分别与***处理能力的过载级 ^相关联。 如表 2所示:
表 2
如上述表 2所述, 过载级别的门限值越大, 则发送的过载告警级别 越高。 如果某设备的当前处理能力已经达到最大***处理能力的 80 % 时, 则开始向周边设备发送 1级过载告警, 如果达到最大***处理能力 的 90 %时, 则开始向周边设备发送 2级过载告警, 如果达到最大***处 理能力的 100 %时, 则开始向周边设备发送 3级过载告警。 周边设备收到对应级别的过载告警消息后, 进行相应的 务连接数 据流量控制。 如收到最高级别的过载告警时, 设备拒绝所有新的业务连 接或者少量的新业务连接消息, 当没有收到过载告警时, 则处理所有业 务连接消息。 在 IP电信网中, 业务连接的建立通常是由 CA发起, 经过 CM上的 业务路由和路径资源计算和分配,向承载网的边缘节点下发 QoS策略信 息, 然后响应给 CA, 再由 CA通知用户开始进行通信, 由承载网上的 CN开始进行业务流的转发并进行 QoS控制。 其中当 CA和业务连接起 源端的归属 CM不相邻接的时候, 还需承载控制层中的一部分 CM完成 代理过程, 即在 CA和所述起源端的归属 CM之间进行代理。:另外, 在
'某些情况下也可由 CN主动向 CM发起业务连接建立请求。 上述业务连 接的具体建立过程可以参考中国专利申请号为 03156391.0 和 03157145.X的专利申请文件, 此处不再描述。
由于在业务连接建立的路由路径以及在业务信息的传输路径上存 在上下游的顺序, 因此针对某条业务连接或业务信息传输路锋, 相关的 设备之间存在上下游的关系。 由于选路过程中一般是从上游到下游依次 进行选路, 因此为了提高效率, 在能确定上下游关系的设备 间, 如果 某一设备的处理能力达到过载, 则该设备只向其上游设备发 i4告警。 但 是, 针对上述不同的业务连接建立过程, IP电信网中各个设夸的上下游 关系也不十分确定, 某设备周边的设备可能是其上游设备, 可能是其 下游设备。 例如: 从承载控制层的角度出发, 业务控制层中的 CA为承 载控制层中 CM的上游设备; CM在没有代理操作发生的情况下, 不同 CA发起的业务连接可能导致其中一个 CM, 例如 CM1, 是另一 CM, 例如 CM2, 的上游设备, 也可能导致 CM1是 CM2的下游设备; CM在 有代理操作发生的情况下, 根据业务连接建立的消息请求方向, 发起请 求者为上游设备;如果 CN主动发起业务连接建立请求,那么 M是 CN 的下游设备;反之,如果 CN被动接收 CM的业务连接建立请 ,则 CM 是 CN的上游设备。在 IP电信网中,设备与设备之间在具体某次业务连 接或业务信息的传输路径上肯定存在上下游关系, 但从大用卢量的业务 连接来看, 很难严格分清设备与设备之间的上下游关系。 针对上述两种情况, 本发明分别提出了两种解决的实施方式。 即: 设备之间上下游关系不明确时的过载控制 (即双向过载控制), 以及设 备之间上下游关系明确时的过载控制。 图 2为本发明实施例所述设备上下游关系不明确时进行过载控制的
流程图, 这种情况下, 一旦某设备过载时, 该设备向其周边设备发送过 载告警。 如图 2所示, 该流程包括: 步骤 201、 承载控制层和承载层的设备在运行过程中, 都实时检测 自身的处理能力是否达到某个过载级别, 如果达到, 则向其周边设备发 送相应级别的设备过载告警消息。 所述设备过载告警消息中携带本设备 的设备类型和本设备 IP地址。 此处假设该设备类型为资源管理器设备, 与过载设备相邻的周边设备为周边设备 A和周边设备 B。
本实施例中, 按照表 2所述的过载级别, 如果本设备的当前处理能 力已经达到该设备最大处理能力的 80 %时,则开始向周边设务发送 1级 过载告警; 如果随着该设备处理的更加繁忙, 告警级别相应增加, 即: 如果达到该设备最大处理能力的 90 %时,则开始向周边设备 送 2级过 载告警; 如果达到最大***处理能力的 100 %时, 则开始向周边设备发 送 3级过载告警。 上述步骤 201中, 所述承载控制层和承载层的设备是承载控制层的 CM和承载层的 CN。 如果是 CM出现过载, 则该 CM向其周边相邻的 CM、 CA 或 CN发送过载告警消息, 且过载告警消息中的设备类型为 CM;如果是 CN出现过载,则该 CN向其周边的 CM发送过载^警消息, 且过载告警消息中的设备类型为 CN。
步骤 202、 收到过载告警的周边设备根据过载告警的内 ί对途经该 过载设备的业务进行限制。 具体的, 主要包括两方面的限制, 一方面是通过调整业务路由策略 对业务连接的选路进行限制, 另一方面是对业务连接的业务量进行限 制。
其中, 调整业务路由策略对业务连接的选路进行限制的具体方式 为: 根据过载设备的 IP地址,周边设备判断自身路由表中是杏存在途经 过载设备的路由的冗余路由, 即首先确定途经过载设备的路由的目的用 户终端地址, 然后判断是否存在可到达同一目的地址、 且不绎过过载设 备的路由, 该路由为冗余路由, 如果存在冗余路由, 则执行步骤 202A; 否则, 执行步骤 202B。 步骤 202A、 将冗余路由的优先级升高, 或将途经过载设备的路由 的优先级降低, 因此在为业务连接选择路由时会优先选择冗余路由, 从 而保证业务连接的 QoS; 或者, 将途经过载设备的路由标上过载标识, 在为业务连接选择路由时, 不能优先选择有过载标识的路由, 从而保证 业务连接的 QoS。
步骤 202B、将途经过载设备的路由标上过载标识,在为业务连接选 择路由时, 不能优先选择该有过载标识的路由, 从而保证 4务连接的 QoS。
所述对业务连接的业务量进行限制的具体方式为: 根据过载报警消 息的级别, 对途经过载设备的路由的业务连接的业务量进行相应限制。 此处的业务量是指业务连接建立的数据流量。 如果过载告警为多个级 别, 则分等级对业务连接的业务量进行限制。 对于高级别的过载报警, 则拒绝较多途经过载设备的路由的业务量; 对于低级別的过载告警, 则 拒绝较少途经过载设备的路由的业务量。 例如: 针对上述例于中的过载 级别 1、 2、 或 3 , 由于分别对应过载设备最大处理能力的 80 ½、 90 %、 和 100 % , 因此与过载级别所对应的限制业务量也映射为 80 %、 90 %、 和 100 % ; 即当收到 1级过载告警时, 周边设备拒绝途经过珠设备的路 由的 80 %业务量; 当收到 2级过载告警时, 周边设备拒绝途经过载设备
的路由的 90 %业务量; 同理, 当收到 3级过载告警时, 周边设备拒绝途 经过载设备的路由的 100 %业务量。 本发明所述根据过载级别限制途经 过载设备的路由的业务量不限于上述的对应值, 本领域的技术人员可根 据具体需要, 自行配置不同级别所映射的限制业务量。 步骤 203、 周边设备向所述过载设备返回告警响应。 如果随着过载设备处理能力恢复正常, 小于最小级别门限值后, 即 小于最大处理能力的 80 %后, 则执行步驟 204。 步驟 204、 设备向其周边设备发送过载告警恢复消息,,其中携带 该设备的类型和该设备的 IP地址, 以取消过载告警消息。 步骤 205、 过载设备的周边设备收到过载告警恢复命令 i 取消或 逐渐取消步骤 202中对路由表内途经过载设备的业务进行限制。 具体的, 主要包括取消两方面的限制, 一方面是通过调聲业务路由 策略取消对业务连接的选路限制, 另一方面是取消对业务连接的业务量 限制。 其中, 通过调整业务路由策略取消对业务连接选路限制的具体方式 为:
当存在冗余路由时, 将调整过的冗余路由的优先级恢复为原状态; 或者, 将途经过载设备的路由的优先级恢复为原状态; 或者, 取消途经 过载设备的路由的过载标识。 当不存在冗余路由时, 取消途经过载设备的路由的过载标识。 取消对业务连接选路限制后, 在为业务连接选择路由时, 与设备不 过载时选择路由的情况相同, 即恢复现有正常的选路机制。 同时, 在取消对业务连接的业务量的限制后, 该周边设备对业务连
接的业务量不进行限制, 恢复现有正常的控制机制。
步骤 206、 周边设备向过载设备返回过载告警恢复响应,,以表示周 边设备取消对的相应业务的限制。
如果 IP电信网中通过提前规划, 使得设备之间的上下游 系明确, 为了提高效率, 当设备发生过载时, 只需向其上游设备发送 载告警消 息。 此处, 提前规划是指: 明确配置 IP电信网中的各个设备 过载时能 否发送过载告警, 如果能发送, 则还要确定其上游设备。
图 3 为本发明实施例所述设备上下游关系明确时过载挂制的流程 图。 该流程中, 当某下游设备发生过载时, 则该下游设备只向其相邻的 上游设备发送对应级别的过载告警消息。 具体的处理过程如图 3所示, 步骤 301至步驟 306分别与上述步驟 201至步骤 206对应相同, 此处不 再叙述。
上述的实施例中周边设备在对途经所述过载设备的业务进行限制 后向过载设备返回过载告警响应,过载设备收到该响应后实时检测自身 的处理能力是否恢复正常, 如果恢复正常, 则该设备向自身 ¾周边设备 发送携带自身地址的过载告警恢复消息。
另外, 本发明所述的周边设备还可以不返回过载告警响应。 这时的 处理方式与上述实施例有以下区别:
当周边设备不返回过载告警响应, 或者所发送的过载告警响应由于 某种原因没有达到过载设备时, 过载设备在没有收到过载告警响应的情 况下, 实时检测自身的处理能力是否恢复正常, 如果没有恢复正常, 则 在预定的时间重新向周边设备发送携带自身地址的过载告警消息, 收到 过载告警消息的周边设备继续对途经该过载设备的业务进行限制; 如果 恢复正常, 则该设备向自身的周边设备发送携带自身地址的 4载告警恢
复消息; 收到过载告警恢复消息的周边设备取消或逐渐取消对途经该过 载设备的业务进行限制。
另外, 所述周边设备对途经所述过载设备的业务进行限制后也可判 断在预定的时间内是否收到来自过载设备的过载告警消息或者过载告 警恢复消息, 如果没有则取消或逐渐取消对途经该过载设备的业务进行 限制, 通过这种动态调整的过程, 可以防止周边设备在没有收到过载设 备最近的情况信息时, 继续对业务进行限制所导致的业务质音降低的问 题; 如果收到过载告警消息则继续对途经该过载设备的业务进行限制; 如果收到过载告警恢复消息, 则取消或逐渐取消对途经该迓孰议备的业 务进行限制。
以上所述, 仅为本发明较佳的具体实施方式, 但本发明的保护范围 并不局限于此, 任何熟悉该技术的人在本发明所揭露的技术范围内, 可 轻易想到的变化或替换, 都应涵盖在本发明的保护范围之内。
Claims
权利要求书
U 一种通信网络中应对设备过载的处理方法, 适用于具有独立承 载控制层的通信网络, 其特征在于, 该方法包括:
在业务连接所涉及的设备中设置过载门限, 所述设备在运行过程 中, 实时检测自身的处理能力是否过载, 如果过载, 则该过载设备向自 身的周边设备发送携带过载设备地址的过载告警消息, 收到过载告警消 息的周边设备对途经该过载设备的业务进行限制。
2、 根据权利要求 1 所述的方法, 其特征在于, 所述周¾设备对途 经所述过载设备的业务进行限制的具体方法为: 所述周边设务调整路由 策略, 为业务连接优先选用未途经该过载设备的路由。
3、 根据权利要求 2 所述的方法, 其特征在于, 所述周 设备为业 务连接优先选用未途经所述过载设备的路由的具体方法为:
将途经过载设备的路由标上过载标识, 在后续为业务连接选择路由 的过程中, 优先选择没有过载标识的路由; 或者, 将途经过载设备路由的冗余路由的优先级升高;
或者, 将途经过载设备路由的优先级降低。
4、 根据权利要求 1 所述的方法, 其特征在于, 所述周边设备对途 经所述过载设备的业务进行限制的具体方法为: 所述周边设务限制业务 连接途经该过载设备的业务量。
5、 根据权利要求 1 所述的方法, 其特征在于, 所述方 进一步包 括: 所述周边设备对途经所述过载设备的业务进行限制后向过载设备返 回过载告警响应; 过载设备收到该响应后实时检测自身的处理能力是否 恢复正常, 如果恢复正常, 则该设备向自身的周边设备发送携带自身地 址的过载告警恢复消息; 收到过载告警恢复消息的周边设备取消或逐渐
取消对途经该过载设备的业务进行限制。
.
6、 根据权利要求 1 所述的方法, 其特征在于, 该方法进 ^步包括: 过载设备实时检测自身的处理能力是否恢复正常, 如果没有' 1來复正常, 则在预定的时间重新向周边设备发送携带自身地址的过载告膂消息, 收 到过载告警消息的周边设备继续对途经该过载设备的业务进行限制; 如 果恢复正常, 则该设备向自身的周边设备发送携带自身地址的过载告警 恢复消息; 收到过载告警恢复消息的周边设备取消或逐渐取消对途经该 过载设备的业务进行限制。
7、 根据权利要求 5或 6 所述的方法, 其特征在于, 该方法进一步 包括: 所述周边设备对途经所述过载设备的业务进行限制后判断在预定 的时间内是否收到来自过载设备的过载告警消息或者过载肯警恢复消 息, 如果没有则取消或逐渐取消对途经该过载设备的业务进 限制; 如 果收到过载告警消息则继续对途经该过载设备的业务进行限 ; 如果收 到过载告警恢复消息, 则取消或逐渐取消对途经该过载设备的业务进行 限制。
8、 根据权利要求 7所述的方法, 其特征在于, 所述取清对途经所 述过载设备的业务进行限制的具体方法为: 取消途经过载设备的路由的 过载标识, 或者将途经过载设备路由的冗余路由的优先级恢复为原状 态, 或者将途经过载设备的路由的优先级恢复为原状态。
9、 根据权利要求 7所述的方法, 其特征在于, 所述取消对途经所 述过载设备的业务进行限制的具体方法为: 取消对业务连接 经该过载 设备的业务量的限制。
10、根据权利要求 1 所述的方法,其特征在于,该方法进广步包括: 所述过载门限分为一个或一个以上的过载级别, 所述设备在检测到自身 过载后, 判断过载级别, 并在过载告警消息中携带过载级別信息; 所述
收到过载告警消息的周边设备依照该过载级别信息分等级对途经该过 载设备的业务进行限制。
11、 根据权利要求 1至 6任一项、 或 10 所述的方法, 其特征在于, 所述过载设备的周边设备为该过载设备在特定业务连接或特定业务信 息传输路径上的上游设备。
12、 根据权利要求 1至 6任一项、 或 10所述的方法, 其 征在于, 所述过载门限根据所述设备的处理能力进行确定。
13、 根据权利要求 12所述的方法, 其特征在于, 所述设备的处理 能力为: CPU的运行能力、 内存空间的占用情况、 消息队列处理能力、 或该三者的任意组合。
14、 根据权利要求 1所述的方法, 其特征在于, 所述业务连接涉及 的设备为通信网络承载控制层的控制设备, 所述周边设备为承载控制层 的控制设备、 承载层的连接接点、 业务控制层的呼叫代理、 珠该三者的 任意组合。
15、 根据权利要求 1所述的方法, 其特征在于, 所述业务连接所涉 及的设备为通信网络承载层的连接节点, 所述周边设备为承我控制层的 控制设备。
16、 根据权利要求 14或 15所述的方法, 其特征在于, 所述通信网 络承载控制层的控制设备为承载网资源管理器、 承载策略管理器、 或者 为承载资源 /策略管理器。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP06703261A EP1843537A1 (en) | 2005-01-19 | 2006-01-05 | A process method for dealing with device overload in the communication network |
US11/826,905 US20080219167A1 (en) | 2005-01-19 | 2007-07-19 | Method, system and device for processing device overload in communication network |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200510001776.6 | 2005-01-19 | ||
CNA2005100017766A CN1809051A (zh) | 2005-01-19 | 2005-01-19 | 一种ip电信网中应对设备过载的处理方法 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/826,905 Continuation US20080219167A1 (en) | 2005-01-19 | 2007-07-19 | Method, system and device for processing device overload in communication network |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006076850A1 true WO2006076850A1 (fr) | 2006-07-27 |
Family
ID=36691980
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2006/000006 WO2006076850A1 (fr) | 2005-01-19 | 2006-01-05 | Procede de traitement pour la gestion de surcharge de dispositif dans un reseau de communication |
Country Status (4)
Country | Link |
---|---|
US (1) | US20080219167A1 (zh) |
EP (1) | EP1843537A1 (zh) |
CN (1) | CN1809051A (zh) |
WO (1) | WO2006076850A1 (zh) |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2009134265A1 (en) * | 2008-05-01 | 2009-11-05 | Lucent Technologies Inc | Message restriction for diameter servers |
US20100257009A1 (en) * | 2009-04-01 | 2010-10-07 | National Ict Australia Limited | Service orientated computer system with multiple quality of service controls |
CN101902295B (zh) * | 2009-05-26 | 2013-08-21 | 国际商业机器公司 | 控制应用服务器的负载接收速率的方法及装置 |
KR101489418B1 (ko) | 2010-04-22 | 2015-02-03 | 후아웨이 테크놀러지 컴퍼니 리미티드 | 혼잡/과부하 제어 방법 및 장치 |
WO2012159269A1 (zh) * | 2011-05-25 | 2012-11-29 | 华为数字技术有限公司 | 网络拥塞处理方法、装置和*** |
US8839243B2 (en) * | 2012-04-23 | 2014-09-16 | International Business Machines Corporation | Remediating resource overload |
JP6217190B2 (ja) * | 2013-07-05 | 2017-10-25 | 富士通株式会社 | パケット中継装置、パケット中継システム、パケット中継方法 |
WO2015067306A1 (en) * | 2013-11-06 | 2015-05-14 | Telefonaktiebolaget L M Ericsson (Publ) | Method and device for controlling processing load of a network node |
JP6375849B2 (ja) * | 2014-10-09 | 2018-08-22 | 富士通株式会社 | ファイルシステム、管理装置の制御プログラム、および、ファイルシステムの制御方法 |
CN107608788B (zh) * | 2017-08-29 | 2020-08-07 | 北京三快在线科技有限公司 | 一种控制方法、装置及设备 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1996015609A2 (en) * | 1994-11-11 | 1996-05-23 | Nokia Telecommunications Oy | Overload prevention in a telecommunications network node |
KR20030043473A (ko) * | 2001-11-28 | 2003-06-02 | 엘지전자 주식회사 | 브이오아이피 스케쥴링 방식의 변경 방법 |
KR20030088811A (ko) * | 2002-05-15 | 2003-11-20 | 삼성전자주식회사 | 공중 네트워크를 사용하는 패킷 코어 네트워크에서 서비스품질 우선 순위 유지 방법 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6424624B1 (en) * | 1997-10-16 | 2002-07-23 | Cisco Technology, Inc. | Method and system for implementing congestion detection and flow control in high speed digital network |
US6831895B1 (en) * | 1999-05-19 | 2004-12-14 | Lucent Technologies Inc. | Methods and devices for relieving congestion in hop-by-hop routed packet networks |
US20020089934A1 (en) * | 2001-01-09 | 2002-07-11 | Urrahx Corporation | System and method for identifying congested links in computer network |
JP4588262B2 (ja) * | 2001-07-04 | 2010-11-24 | 富士通株式会社 | ルータ及びネットワークにおける一時停止方法 |
JP4041944B2 (ja) * | 2001-10-18 | 2008-02-06 | 日本電気株式会社 | ネットワークの混雑制御システムと混雑制御ノード、及び混雑制御プログラム |
US7113477B1 (en) * | 2001-11-09 | 2006-09-26 | Alcatel | Traffic measurement collection in a telecommunication network |
US7295516B1 (en) * | 2001-11-13 | 2007-11-13 | Verizon Services Corp. | Early traffic regulation techniques to protect against network flooding |
US7403496B2 (en) * | 2004-09-28 | 2008-07-22 | Motorola, Inc. | Method and apparatus for congestion relief within an ad-hoc communication system |
-
2005
- 2005-01-19 CN CNA2005100017766A patent/CN1809051A/zh active Pending
-
2006
- 2006-01-05 WO PCT/CN2006/000006 patent/WO2006076850A1/zh active Application Filing
- 2006-01-05 EP EP06703261A patent/EP1843537A1/en not_active Withdrawn
-
2007
- 2007-07-19 US US11/826,905 patent/US20080219167A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1996015609A2 (en) * | 1994-11-11 | 1996-05-23 | Nokia Telecommunications Oy | Overload prevention in a telecommunications network node |
KR20030043473A (ko) * | 2001-11-28 | 2003-06-02 | 엘지전자 주식회사 | 브이오아이피 스케쥴링 방식의 변경 방법 |
KR20030088811A (ko) * | 2002-05-15 | 2003-11-20 | 삼성전자주식회사 | 공중 네트워크를 사용하는 패킷 코어 네트워크에서 서비스품질 우선 순위 유지 방법 |
Also Published As
Publication number | Publication date |
---|---|
EP1843537A1 (en) | 2007-10-10 |
CN1809051A (zh) | 2006-07-26 |
US20080219167A1 (en) | 2008-09-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2006076850A1 (fr) | Procede de traitement pour la gestion de surcharge de dispositif dans un reseau de communication | |
US8082361B2 (en) | Method and system for providing a mobile IP network with non-path dependent intra domain quality of service | |
CN100358321C (zh) | 下一代网络中实现用户请求模式资源预留的方法 | |
US8165021B2 (en) | Policy-based resource management | |
US7792985B2 (en) | Method for implementing information flow transmission in next generation network | |
WO2006094446A1 (fr) | Procede pour obtenir la reservation de ressources pour un mode de demande d'agent dans ngn | |
WO2006094447A1 (en) | A method for implementing the access configuration mode resource reservation in the next generation network | |
WO2004064325A1 (fr) | Systeme et procede de distribution des ressources dans un reseau de communications | |
WO2005125104A1 (fr) | Procede de transmission securisee de flux de services sur un reseau ip | |
WO2007076661A1 (fr) | Procede de gestion d'encombrement et dispositif de reseau pour service de multidiffusion en temps reel | |
WO2009036663A1 (fr) | Procédé, dispositif et système pour superviser l'état de service d'un nœud de réseau homologue à homologue | |
WO2007082448A1 (fr) | Procédé de qualité de service (qos) garantie, dispositif de gestion de ressources et système d'accès multi-services | |
WO2007016848A1 (fr) | Procédé de traitement d'une demande de conversion adresse/port de réseau dans un réseau de communication | |
WO2018082597A1 (zh) | 拥塞控制方法及装置、基站 | |
JP2007312159A (ja) | Ip通信制御システム及び制御方法並びに制御プログラム | |
WO2006034657A1 (fr) | Procede de gestion de ressources interdomaines | |
US8135005B2 (en) | Communication control system, communication control method, routing controller and router suitably used for the same | |
US7506050B2 (en) | Method for checking transmission resources of a packet-oriented communication network when there are topology changes | |
US7953015B2 (en) | Method for ensuring reliability in network | |
WO2009103192A1 (zh) | 资源分配方法及资源释放方法 | |
JP2004515179A (ja) | 分散されたネットワークアクセスシステムのためのプログラム可能なアクセス装置 | |
US8792823B2 (en) | Approach for quality of service control on un-wanted services (e.g. voice over internet protocol or multimedia) over wireline and wireless IP network | |
JP2010219655A (ja) | 代理中継サーバ、帯域管理サーバ、ルータ装置、ファイル転送システム、方法およびプログラム | |
CN101146053A (zh) | 下一代网络中实现用户请求模式资源预留的方法 | |
WO2009065343A1 (fr) | Procédé, système et équipement pour la confirmation de dispositifs edge |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2006703261 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2006703261 Country of ref document: EP |