WO2008134959A1 - Procédé et système pour réaliser un équilibrage de charge dans un réseau à commutation par paquets - Google Patents

Procédé et système pour réaliser un équilibrage de charge dans un réseau à commutation par paquets Download PDF

Info

Publication number
WO2008134959A1
WO2008134959A1 PCT/CN2008/070772 CN2008070772W WO2008134959A1 WO 2008134959 A1 WO2008134959 A1 WO 2008134959A1 CN 2008070772 W CN2008070772 W CN 2008070772W WO 2008134959 A1 WO2008134959 A1 WO 2008134959A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
target network
load
unit
load status
Prior art date
Application number
PCT/CN2008/070772
Other languages
English (en)
Chinese (zh)
Inventor
Bo Zheng
Qing Zhou
Youzhu Shi
Hongbo Liao
Original Assignee
Huawei Technologies Co., Ltd.
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
Priority claimed from CNA2007101067263A external-priority patent/CN101304366A/zh
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008134959A1 publication Critical patent/WO2008134959A1/fr

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
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering

Definitions

  • the present invention relates to the field of packet switching network technologies, and in particular, to a method and system for implementing load balancing in a packet network.
  • SIP Session Initiation Protocol
  • ITU-T International Telecommunication Union-T Sector
  • European Telecommunications Standards Institute the International Telecommunication Union-T Sector
  • NGN next generation network
  • 3GPP 3rd Generation Partnership Project
  • IMS IP Multimedia Subsystem
  • the load status may indicate the degree of use of the resource required by the network element to process the request, and may also indicate whether the network element is available. For example, if the load status indicates that the network element is in a fault state, the network element is unavailable; if the load status indicates that the network element is in normal state Status, then the network element is available. When a resource of a network element in the network is insufficient to accept a new service request, the network element is said to enter an overload state.
  • the resource may be all capabilities of the network element for processing a request, including central processing unit (CPU) processing power, memory, input/output resources, storage capabilities, etc.; sometimes may also include extended resources, such as the network The database or domain name system used by the meta (Domain Name System, DNS).
  • unbalanced network element load distribution may occur in the network: One or more network elements in the network are overloaded at a certain time, or even enter an overload state. Other network elements are under light load, network resources are not fully utilized, and network congestion may also occur.
  • the prior art provides a load balancing method to solve the above problems.
  • the so-called load balancing method is to determine whether the network element is overloaded or the load is too light according to the load status of the network element, and allocate tasks between the mutually replaced network elements to achieve substantially equivalent load of the network elements, and ensure high efficiency of the network equipment. run.
  • the specific method of the load balancing method in the prior art is as follows: In a packet network, a plurality of servers correspond to the same network domain name, and a DNS server is used to distribute tasks to these servers in a balanced manner, thereby achieving load balancing.
  • this method has many limitations: First, it can only achieve load balancing within the same domain name, and cannot achieve load balancing among multiple domain names.
  • the existing DNS server is used to implement load balancing within the domain name. The solution only solves a small part of the load balancing problem in the packet network. In many cases, it is necessary to implement load balancing without relying on the DNS server, and there is no corresponding solution in the prior art. Summary of the invention
  • the embodiment of the present invention provides a method for implementing load balancing in a packet network, which can be widely applied to various situations in a packet network that require load balancing.
  • the method comprises the following steps:
  • the embodiment of the invention further provides a system for implementing load balancing in a packet network, comprising: at least two target network elements that can replace each other;
  • An acquisition unit configured to acquire a load status of each target network element, and send the acquired load status to the status processing unit;
  • a state processing unit configured to select at least one target network element with a lighter load according to a load status of the target network element from the collection unit, and send the identifier of the selected target network element to the selection unit;
  • the selecting unit is configured to process the service to the corresponding target network element according to the target network element identifier from the state processing unit.
  • An embodiment of the present invention further provides an apparatus for implementing load balancing in a packet network, including: an acquisition unit, a state processing unit, and a selection unit;
  • the collecting unit is configured to acquire a load status of each target network element in the packet network, and send the acquired load status to the status processing unit;
  • the state processing unit is configured to select at least one non-fault target network element with a light load according to a load status of the target network element from the collection unit, and send the identifier of the selected target network element to the selection unit;
  • the selecting unit is configured to route the service to the corresponding target network element according to the target network element identifier from the state processing unit.
  • 1 is a logic architecture diagram of an embodiment of the present invention
  • FIG. 3 is a flowchart of implementing S-CSCF load balancing processing according to an embodiment of the present invention
  • FIG. 4 is a flowchart of implementing P-CSCF load balancing processing according to an embodiment of the present invention
  • FIG. 5 is a flowchart of implementing I-CSCF load balancing processing according to an embodiment of the present invention.
  • the logical architecture of the system in the embodiment of the present invention is as shown in FIG. 1, and includes a target network element 101, an acquisition unit 102, a state processing unit 103, and a selection unit 104.
  • the target network element 101 is used to provide the load status of the local network element.
  • the target network element may be any network element in the packet network that needs to consider load balancing, such as a proxy call session control function entity in the IMS network (Proxy-Call Session Control). Function, P-CSCF), Serving Call Session Control Function Entity (S-CSCF), Query Call Session Control Function Entity (I-CSCF), Application Server (AS), Media Gateway Control Function Entity (Media Gateway Control Function) , MGCF), Breakout Gateway Control Function (BGCF), Interconnection Border Control Function (IBCF), Multimedia Resource Function Controller (MRFC), or emergency call Network elements such as the Session Control Function Entity (E-CSCF).
  • the number of mutually replaceable target network elements 101 should be greater than 1. For example, if the target network element 101 is a P-CSCF, the number of P-CSCFs should be greater than 1.
  • the acquisition unit 102 is responsible for collecting the load status from the target network element 101 and passing the load status to the status processing unit 103 for processing.
  • the collecting unit 102 may be located in the target network element 101, or in a network element other than the target network element, or in a user equipment (UE).
  • UE user equipment
  • the P-CSCF when the load balancing of the P-CSCF is considered, the P-CSCF is taken as the target network element 101 in FIG. 1, and the collecting unit 102 may be located in a Dynamic Host Configuration Protocol (DHCP) server or a GPRS gateway serving node (GGSN). ), Home Subscriber Server (HSS) or Network Management Server.
  • DHCP Dynamic Host Configuration Protocol
  • GGSN GPRS gateway serving node
  • HSS Home Subscriber Server
  • the protocols that can be used for E1 interface communication between the target network element 101 and the collection unit 102 include, but are not limited to, SIP protocol, Diameter protocol, DHCP, Hypertext Transfer Protocol (HTTP), network management protocol, and internal interface protocol.
  • the state processing unit 103 implements a certain load balancing policy according to the load state of the target network element 101 received from the collecting unit 102, and sends the identifier of the target network element to the selected network element 104.
  • the state processing unit 103 may be located in a network element where the collection unit 102 is located, or in a different network element from the collection unit 102, or in a user equipment (UE).
  • the load balancing policy depends on the carrier's policy and implementation. The basic principle is to select the S-CSCF with a light load in the non-faulty network element.
  • the protocols available for E2 interface communication between the acquisition unit 102 and the status processing unit 103 include, but are not limited to, the SIP protocol, the Diameter protocol, the network management protocol, and the internal interface protocol.
  • Selection unit 104 is operative to route the user request to the target network element specified by state processing unit 103.
  • the selecting unit 104 may be located in a network element where the state processing unit 103 is located, or in a different network element from the state processing unit 103, or in a user equipment (UE).
  • the user request may be a user request from other network elements received by the selection unit 104, or may be a user request generated by the selection unit 104 itself.
  • the protocols that can be used for E3 interface communication between the selection unit 104 and the state processing unit 103 include, but are not limited to, the SIP protocol, the Diameter protocol, the DHCP protocol, the HTTP protocol, the network management protocol, and the internal interface protocol.
  • the collecting unit 102 may further include a timing triggering subunit for timing, and requesting a load state from the target network element 101 when the timing reaches a predetermined threshold;
  • the collecting unit 102 further includes an event triggering subunit, and the event triggering subunit is configured to request a load state from the target network element 101 when receiving the registration request, the session request, or the load request of the state processing unit. Then, the target network element 101 returns the current load status to the collection unit 102 according to the received request.
  • the collecting unit 102 may further include a reporting sub-unit for periodically reporting the load status of the target network element to the state processing unit 103.
  • the reporting sub-unit is configured to determine whether the load status received by the collecting unit 102 exceeds a preset threshold, and if so, the load status is reported to the status processing unit 103;
  • the reporting subunit is configured to trigger the reporting of the load status to the state processing unit 103 according to the specific event.
  • the state processing unit 103 may further include:
  • timing triggering subunit for timing requesting a load status from the collecting unit 102 when the timing reaches a predetermined threshold
  • state processing unit 103 further includes an event triggering subunit for requesting load status from acquisition unit 102 when a particular event occurs.
  • the collection unit 102, the state processing unit 103, or the selection unit 104 may be located in the same network element, and may be located in more than one network element or in more than one network element and user equipment.
  • the method for implementing load balancing according to the embodiment of the present invention is as shown in FIG. 2, and includes the following steps:
  • Step 201 The collecting unit collects a load status from the target network element, and the state processing unit obtains a load status from the collecting unit.
  • the load status of the acquisition unit is derived from the target network element. Specifically, it may be any one of the following methods or any combination thereof:
  • the target network element periodically reports its own load status to the collection unit.
  • the target network element determines whether its own load status exceeds a preset threshold, and if so, then Reporting its own load status to the acquisition unit;
  • the collecting unit periodically requests the load status from the target network element, or when the load request of the registration request/session request/state processing unit comes, triggers the collecting unit to request the load status from the target network element.
  • the load status received by the state processing unit is derived from the collecting unit, and may be any one of the following modes or any combination thereof:
  • the collecting unit periodically reports the load status of the target network element to the state processing unit;
  • the collecting unit determines whether the received load state exceeds a preset threshold, and if so, reports the load status to the state processing unit;
  • the collecting unit is triggered to report the load status to the status processing unit according to the specific event; for example, when the registration/session request reaches the target network element, the collecting unit is triggered to report the load status to the status processing unit;
  • the state processing unit periodically requests the load state from the collection unit, or triggers the state processing unit to request the load state according to the specific event. For example, when the registration/session request reaches the uplink network element, the trigger state processing unit requests the load state from the collection unit.
  • Step 202 The state processing unit performs load balancing processing according to the received load state of the target network element.
  • the state processing unit performs load balancing processing, that is, selecting a target network element with a lower load in the non-faulted target network element according to the reported load status of each target network element, and transmitting the selected target network element identifier to the selection unit.
  • the identifier of the target network element may be a Uniform Resource Locator (URL) or a domain name of the target network element.
  • Step 203 The selecting unit routes the user request according to the target network element specified by the received state processing unit.
  • the selecting unit selects a target network element from the specified target network element, and forwards the request to the target network element. If the target unit receives the target network element address/domain name, the user request is sent to the target network element corresponding to the target network element address/domain name.
  • the load balancing scheme of the S-CSCF is first introduced by an embodiment.
  • the S-CSCF is mainly used in the IMS network system to trigger the service to the corresponding AS according to the user request from the user equipment.
  • an appropriate S-CSCF can be selected according to the load state of the S-CSCF when the user registers, and the subsequent session request of the user is performed through the selected S-CSCF, thereby realizing the user's monthly service. Load balancing of the S-CSCF.
  • the target network element is an S-CSCF
  • the acquisition unit, the state processing unit, and the selection unit are all located in the I-CSCF.
  • the I-CSCF queries the HSS to obtain the capability set of the S-CSCF required by the user service, and the I-CSCF selects the S-CSCF that satisfies the capability set requirement; There are multiple CSCFs, and the I-CSCF selects the appropriate S-CSCF according to the load status of these S-CSCFs, and then routes the registration request to the S-CSCF.
  • FIG. 3 shows a process of performing load balancing processing on the S-CSCF after the UE initiates the registration request in this embodiment.
  • the I-CSCF obtains the load status of each optional S-CSCF.
  • the I-CSCF can obtain the load status of the S-CSCF through the request, or the S-CSCF reports its own load status to the I-CSCF.
  • the S-CSCF can obtain the address of the I-CSCF in the network through configuration, and report the load status according to the I-CSCF address.
  • the I-CSCF periodically requests or the S-CSCF periodically or exceeds the threshold to report the load status; or subscribes to the load status of the S-CSCF through the SIP SUBSCRIBE. , the load status is returned in the SIP NOTIFY message; or the I-CSCF sends a registration request or session request from the user to the S-CSCF, and the S-CSCF registers the response message or the session response message (eg, 100) Returning load status in Trying ).
  • the SIP NOTIFY message or the I-CSCF sends a registration request or session request from the user to the S-CSCF, and the S-CSCF registers the response message or the session response message (eg, 100) Returning load status in Trying ).
  • the load status is returned in the session response message as described above.
  • the SIP message is extended as follows in the embodiment of the present invention:
  • Load-Status 80
  • the Load-Status header field gives the current server load level of 80%
  • Step 301 The UE initiates a registration request and routes to the I-CSCF via the P-CSCF.
  • the P-CSCF is omitted in both Figure 3 and the following process description.
  • Step 302 to step 303 The 1-CSCF requests the HSS for the S-CSCF capability set required by the user service, and the HSS returns the capability set of the S-CSCF to the I-CSCF.
  • the I-CSCF requests the HSS to request the S-CSCF capability set through a User Authority Request (UAR) command; and the HSS returns the S-CSCF capability set through the user authorization response (User Authority Answer) , UAA ) command implementation.
  • UAR User Authority Request
  • UAA User Authority Answer
  • Step 304 The I-CSCF selects an S-CSCF that meets the capability set required by the user according to the received S-CSCF capability set. If there are multiple S-CSCFs that meet the user-required capability set, the I-CSCF receives the To the load status of the S-CSCF, implement a certain load balancing policy, and troubleshoot the S-CSCF, and select at least one S-CSCF from the non-faulty S-CSCF.
  • the I-CSCF may first implement a certain load balancing policy according to the received load state of the S-CSCF, and troubleshoot the S-CSCF, and select a lighter S-CSCF from the non-faulty S-CSCF; According to the received S-CSCF capability set, the load is lighter.
  • the S-CSCF is selected in the S-CSCF to meet the capability set required by the user.
  • the load balancing policy depends on the carrier's policy and implementation.
  • the basic principle is to select the S-CSCF with a light load in the non-faulty network element.
  • Step 305 The I-CSCF forwards the registration request to the S-CSCF selected according to the load balancing policy.
  • Step 306 to step 307 The S-CSCF returns a registration response message, which is forwarded by the I-CSCF and finally sent to the UE.
  • Step 308 to step 309 After receiving the registration response message, the UE sends a second registration request to the S-CSCF, and the routing process is the same as steps 301-305, except that the HSS only returns the designated S-CSCF to the I-CSCF. Routing information;
  • the S-CSCF returns a 200 (OK) response to the UE to indicate that the registration is successful.
  • both the acquisition unit and the state processing unit can be located in other network elements.
  • the acquisition unit and the state processing unit can both be located in the HSS, and the HSS implements a certain load balancing policy according to the collected load status, and selects a load comparison.
  • a light S-CSCF and simultaneously returning to the I-CSCF a message carrying the lightly loaded S-CSCF address identifier and the capability set of the S-CSCF requested by the user; the I-CSCF further receives the S- according to the capability In the CSCF address identifier, an S-CSCF that meets the capability set of the user is selected.
  • the message returned by the HSS to the I-CSCF may carry the S-CSCF address information in the Attribute Value Pair (AVP) in the Diameter protocol, and the AVP parameter includes the address identifier of the S-CSCF.
  • AVP Attribute Value Pair
  • the acquisition unit and the state processing unit may also not be concentrated on the same network element.
  • the acquisition unit may be located in the HSS, and the state processing unit may be located in the I-CSCF.
  • the HSS then returns the load status and capability set of the S-CSCF to the I-CSCF.
  • the AVP can be loaded with load status information in the Diameter protocol.
  • the AVP parameter includes an address identifier of the target network element.
  • the load status value of the target NE may be loaded with load status information in the Diameter protocol.
  • the I-CSCF obtains the load status of the S-CSCF before receiving the registration request.
  • the I-CSCF may also trigger the load when the S-CSCF needs to be made, such as when the registration request arrives. Status acquisition operation.
  • all S-CSCFs in the network can be obtained, and the load of some related S-CSCFs can be obtained as needed.
  • the target network element is a P-CSCF
  • the collection unit and the state processing unit are both located in a dynamic host configuration protocol (DHCP) server
  • the selection unit is a UE.
  • the processing flow of this embodiment is shown in FIG. 4, and includes the following steps:
  • Step 401 The DHCP server collects the load status of each P-CSCF.
  • the P-CSCF reports the load status to the DHCP server
  • the DHCP server requests the P-CSCF for its load status.
  • the P-CSCF can obtain the address of the DHCP server through configuration or other methods, and periodically report the load status to the DHCP server. When the load status exceeds the preset threshold, the P-CSCF triggers the reporting of the load status to the DHCP server.
  • the DHCP server can periodically request the load status of the P-CSCF based on the configured P-CSCF address.
  • the P-CSCF supports the SIP protocol, while the DHCP server uses the DHCP protocol. E1 interface communication can use SIP or DHCP, or other protocols.
  • Step 402 The UE initiates a DHCP server request.
  • Step 403 The DHCP server removes the faulty P-CSCF according to the load balancing policy, and selects an appropriate P-CSCF from the non-faulty P-CSCF.
  • Step 404 The DHCP server returns the appropriate P-CSCF to the UE.
  • the DHCP server is a state processing unit.
  • the UE also It can be a state processing unit, and the return status of the P-CSCF is returned in the above message.
  • This extended option contains a description of the domain name/address and load status.
  • the requested option code 47 should be added in the Option Request Option (ORO).
  • OPTION 47 containing the load status will be returned when the DHCP responds.
  • Step 405 The UE initiates a registration request according to the received P-CSCF.
  • the DHCP server is a state processing unit.
  • the UE when the UE is a state processing unit, when the UE receives a list of domain names/addresses and load states of multiple P-CSCFs, according to the load balancing principle, select an appropriate P. - The CSCF initiates a registration request.
  • both the collection unit and the state processing unit are DHCP servers.
  • both the acquisition unit and the state processing unit can be located in other network elements, and may not be concentrated on the same network element.
  • the collection unit is located in the network management server, and the state processing unit is located in the UE or the network management server.
  • the DHCP server obtains the load status of the P-CSCF before receiving the DHCP request.
  • the P-CSCF load status acquisition operation can also be triggered by the DHCP server when a P-CSCF selection is required, such as when a DHCP request arrives.
  • all P-CSCFs in the network can be obtained, and the loads of related P-CSCFs can be obtained as needed.
  • the load balancing process of the I-CSCF is described below by way of an embodiment.
  • the target network element is an I-CSCF
  • the acquisition unit is located
  • the state processing unit is located
  • the selection unit is located at the P-CSCF.
  • Step 501 The P-CSCF collects the load status of each I-CSCF.
  • the methods of collection are divided into two categories, that is, the P-CSCF requests its I-CSCF for its load status or The I-CSCF reports its own load status to the P-CSCF.
  • the I-CSCF can obtain the address of the P-CSCF in a configured manner, and report the load status of the P-CSCF to the P-CSCF of the address periodically or when the threshold is exceeded.
  • the P-CSCF can obtain the address of the I-CSCF through a DNS query, and request the load status of the I-CSCF when the periodicity or registration/session request comes.
  • the P-CSCF periodically requests or the I-CSCF periodically or exceeds the threshold to report the load status; or subscribes to the load status of the I-CSCF through the SIP SUBSCRIBE message, and the load status is in NOTIFY.
  • the message is returned to the P-CSCF; or the session response message (such as lOO Trying) returns the load status to the P-CSCF.
  • Step 502 The P-CSCF receives the registration/session request
  • Step 503 The P-CSCF removes the fault I-CSCF according to the collected load status, combines the load balancing policy, and selects an appropriate ⁇ j I-CSCF from the fault I-CSCF.
  • Step 504 The P-CSCF routes the registration/session request to the selected I-CSCF.
  • both the acquisition unit and the state processing unit are P-CSCFs.
  • both the acquisition unit and the state processing unit can be located in other network elements, and may not be concentrated on the same network element. If the collection unit is located in the network management server, the status processing unit is located in the P-CSCF or the network management server.
  • the P-CSCF obtains the load status of the I-CSCF before receiving the registration/session request.
  • the I-CSCF load status acquisition operation can also be triggered by the P-CSCF when an I-CSCF selection is required, such as when a registration/session request arrives.
  • all the I-CSCFs in the network can be obtained, and the load of some related I-CSCFs can be obtained as needed.
  • the load balancing of the I-CSCF by the P-CSCF is described, and the load balancing of the network elements other than the S-CSCF/MGCF/AS/target network element to the I-CSCF is similar.
  • the IBCF is similar in location to the I-CSCF in the network, and its load balancing is similar to the I-CSCF. It can be seen from the above technical solution that the target network element reports its own load status, and according to the load status, the target network element with a light load can be selected to perform services, thereby implementing load balancing processing on the target network element.
  • the solution of the invention does not depend on a specific network element, and can be widely deployed in various parts of the packet network, and has high practical value.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé permettant de réaliser un équilibrage de charge dans un réseau à commutation par paquets, ce procédé consistant à : acquérir des états de charge d'au moins deux éléments de réseau cibles (101) qui sont interchangeables; sélectionner l'élément de réseau cible (101) avec une charge sans défaut et une charge inférieure en fonction des états de charge obtenus; acheminer le service vers l'élément de réseau cible (101) sélectionné. L'invention concerne également un système permettant de réaliser l'équilibrage de charge dans un réseau à commutation par paquets, l'équilibrage de charge pouvant être réalisé dans chaque partie d'un réseau à commutation par paquets, indépendamment d'un élément de réseau spécifique.
PCT/CN2008/070772 2007-05-08 2008-04-22 Procédé et système pour réaliser un équilibrage de charge dans un réseau à commutation par paquets WO2008134959A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200710108029 2007-05-08
CN200710108029.1 2007-05-08
CNA2007101067263A CN101304366A (zh) 2007-05-08 2007-06-15 一种分组网络中实现负载均衡的方法、装置和系统
CN200710106726.3 2007-06-15

Publications (1)

Publication Number Publication Date
WO2008134959A1 true WO2008134959A1 (fr) 2008-11-13

Family

ID=39943122

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/070772 WO2008134959A1 (fr) 2007-05-08 2008-04-22 Procédé et système pour réaliser un équilibrage de charge dans un réseau à commutation par paquets

Country Status (1)

Country Link
WO (1) WO2008134959A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017000142A1 (fr) * 2015-06-29 2017-01-05 华为技术有限公司 Procédé de gestion de charge de p-cscf, et passerelle
CN114615698A (zh) * 2020-12-09 2022-06-10 中国移动通信集团四川有限公司 一种ibcf互通网关负荷调整方法和装置

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004004245A1 (fr) * 2002-06-28 2004-01-08 Nokia Corporation Dispositifs d'equilibrage de force et son procede
CN1479466A (zh) * 2002-08-29 2004-03-03 深圳市中兴通讯股份有限公司 一种分组数据服务节点间的集群方法
US20060018304A1 (en) * 2004-07-23 2006-01-26 Samsung Electronics Co., Ltd. Apparatus and method for scalable call-processing system
CN1913465A (zh) * 2005-08-11 2007-02-14 中兴通讯股份有限公司 无线局域网的负载均衡方法
CN1921479A (zh) * 2005-08-23 2007-02-28 中兴通讯股份有限公司 一种流媒体系统负荷分担方法及其系统
CN1925417A (zh) * 2005-08-31 2007-03-07 华为技术有限公司 一种核心网络节点上报负载信息的方法及装置
CN1937557A (zh) * 2006-09-05 2007-03-28 华为技术有限公司 结构化对等网络系统及其负载查询、转移及资源查找方法

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004004245A1 (fr) * 2002-06-28 2004-01-08 Nokia Corporation Dispositifs d'equilibrage de force et son procede
CN1479466A (zh) * 2002-08-29 2004-03-03 深圳市中兴通讯股份有限公司 一种分组数据服务节点间的集群方法
US20060018304A1 (en) * 2004-07-23 2006-01-26 Samsung Electronics Co., Ltd. Apparatus and method for scalable call-processing system
CN1913465A (zh) * 2005-08-11 2007-02-14 中兴通讯股份有限公司 无线局域网的负载均衡方法
CN1921479A (zh) * 2005-08-23 2007-02-28 中兴通讯股份有限公司 一种流媒体系统负荷分担方法及其系统
CN1925417A (zh) * 2005-08-31 2007-03-07 华为技术有限公司 一种核心网络节点上报负载信息的方法及装置
CN1937557A (zh) * 2006-09-05 2007-03-28 华为技术有限公司 结构化对等网络系统及其负载查询、转移及资源查找方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017000142A1 (fr) * 2015-06-29 2017-01-05 华为技术有限公司 Procédé de gestion de charge de p-cscf, et passerelle
CN114615698A (zh) * 2020-12-09 2022-06-10 中国移动通信集团四川有限公司 一种ibcf互通网关负荷调整方法和装置

Similar Documents

Publication Publication Date Title
US10743175B2 (en) Method, apparatus, and system for disaster recovery of IMS
JP5301549B2 (ja) Ｉｐマルチメディア・サブシステム・ネットワークにおける障害復旧
US8666402B2 (en) Method for triggering user registration in IP multimedia subsystem
CN101304366A (zh) 一种分组网络中实现负载均衡的方法、装置和系统
US7742421B2 (en) Systems, methods, and computer program products for distributing application or higher layer communications network signaling entity operational status information among session initiation protocol (SIP) entities
US9591082B2 (en) Method and system of transferring a message in a session initiation protocol based communications network
JP4981971B2 (ja) 接続先セッションコントローラ、ｉｐマルチメディア・サブシステム及び当該システムにおけるセッション登録方法
EP2174461B1 (fr) Procédé et appareil à usage dans un réseau de communications
EP2705647B1 (fr) Procédé et élément de réseau pour l'affectation de serveur s-cscf dans un réseau multimédia sur ip basé sur l'ims
US20170230428A1 (en) Session initiation protocol (sip) communications over trusted hardware
JP2009544200A (ja) ネットワークにアクセスする方法、システムおよびデバイス
EP2091186A1 (fr) Procédé, réseau et dispositif pour acheminer une session
WO2011057551A1 (fr) Procédé et sous-système multimédia ip pour obtenir un équilibrage de charge parmi des dispositifs de réseau
WO2008116373A1 (fr) Procédé de traitement de service d'urgence
WO2011120366A1 (fr) Procédé, dispositif et système d'obtention d'informations de charge d'une station de base radio
WO2008134959A1 (fr) Procédé et système pour réaliser un équilibrage de charge dans un réseau à commutation par paquets
WO2010127529A1 (fr) Procédé et système d'établissement d'un service de sous-système multimédia par internet
WO2009076865A1 (fr) Méthode, appareil et système de détection d'une application non sip d'un utilisateur ims
WO2012097714A1 (fr) Procédé et système pour qu'un centre de commutation de communications mobiles obtienne des données d'un point de contrôle ims
WO2012097718A1 (fr) Procédé et système d'acquisition d'informations du nœud de contrôle ims pour un centre de commutation mobile

Legal Events

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

Ref document number: 08734130

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08734130

Country of ref document: EP

Kind code of ref document: A1