WO2007012259A1 - Procédé de contrôle de surcharge pour la passerelle multimédia d’accès et passerelle multimédia d’accès - Google Patents

Procédé de contrôle de surcharge pour la passerelle multimédia d’accès et passerelle multimédia d’accès Download PDF

Info

Publication number
WO2007012259A1
WO2007012259A1 PCT/CN2006/001692 CN2006001692W WO2007012259A1 WO 2007012259 A1 WO2007012259 A1 WO 2007012259A1 CN 2006001692 W CN2006001692 W CN 2006001692W WO 2007012259 A1 WO2007012259 A1 WO 2007012259A1
Authority
WO
WIPO (PCT)
Prior art keywords
call
media gateway
overload
priority
access media
Prior art date
Application number
PCT/CN2006/001692
Other languages
English (en)
French (fr)
Inventor
Weiyang Wang
Xiaoshuang Li
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
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to EP06753145.9A priority Critical patent/EP1906589B1/en
Publication of WO2007012259A1 publication Critical patent/WO2007012259A1/zh
Priority to US12/019,706 priority patent/US8068413B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1023—Media gateways
    • H04L65/1026—Media gateways at the edge
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1033—Signalling gateways
    • H04L65/1036—Signalling gateways at the edge
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1043—Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/756—Media network packet handling adapting media to device capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to an access media gateway overload control method and an access media gateway.
  • NGN Next Generation Network
  • the NGN is composed of a Media Gateway Controller (MGC), a Media Gateway (MG), a Signaling Gateway (SG), and an associated application server, and the Media Gateway includes an Access Media Gateway (AG) and a Relay Media Gateway (TG).
  • MGC Media Gateway Controller
  • MG Media Gateway
  • SG Signaling Gateway
  • TG Relay Media Gateway
  • the AG provides a user-side interface to connect to the user terminal device, such as a phone, terminates the subscriber line signaling, and interacts with the MGC through the H.248 or MGCP protocol to complete the media stream conversion.
  • the MGC is responsible for call control, and controls the AG to complete the establishment and release of the media stream connection through the H.248 or MGCP protocol.
  • the call processing capability of AG and MGC is limited.
  • the system design should ensure that the call processing capability of the system can meet the normal traffic load requirements.
  • the capacity of an AG is 2000 lines of POTS users.
  • the average traffic per user is O.lerlan.
  • the average duration of each call is 60s.
  • the average traffic of the AG is 200erian, and the call processing capability needs to reach 3.3CAPS. (Call Attempts Per Second, which is the number of calls per second), that is, 3.3 calls per second.
  • the user's traffic volume during the busy day or the busy day will greatly exceed O.lerlan, thus exceeding the normal processing capacity of the system.
  • An overload control mechanism is also provided to prevent the system from collapsing under heavy traffic shocks and to ensure business as much as possible.
  • the overload control of the AG equipment is actually to limit the call of the user when the system load reaches a certain threshold, so that the system load can be restored to the normal level as soon as possible, thereby preventing the system from collapsing.
  • Such a method of restricting a call to a user inevitably affects the user service in an overload situation, and how to minimize the impact on the user service depends on the selection of the call restriction policy.
  • the users of an AG device can be ordinary residential users or commercial users or government users. Different users have different requirements for service reliability. User calls under one AG device can be It is an ordinary call, or it can be an emergency call such as first aid or alarm. Different calls have different requirements for service reliability. Therefore, the key technology of the overload control of the AG equipment is to study a reasonable processing mechanism and a call restriction policy to ensure high priority calls as much as possible under overload.
  • One of the prior art techniques is to set multiple overload levels on the AG device, each level corresponding to a certain system load. For example, set three overload levels, where the first level overload corresponds to 70% CPU usage, the second level overload corresponds to 85 % CPU usage, and the third level overload corresponds to 95% CPU usage.
  • the system starts the call restriction according to the call restriction ratio. For example, when the level 3 overload control is used, 50% of the user calls are restricted when the first level is overloaded, 70% of the user calls are restricted when the second level is overloaded, and all user calls are restricted when the level 3 is overloaded.
  • 50% or 70% of the users are randomly selected to make a call restriction. For example, if 50% is restricted, 5 calls are rejected in every 10 calls; if 70% is restricted, every 10 calls are made. 7 calls were rejected.
  • the AG determines whether to limit the call according to the current overload level. If yes, directly reject the call, and release the busy tone or notification tone to the user. . Otherwise, the off-hook event is reported to the MGC through H.248/MGCP, and processed according to the normal call flow.
  • the AG determines whether to limit the call according to the current overload level, and if so, rejects the call in the Reply to the MGC. If the call is accepted in the Reply to the MGC, it is processed according to the normal call flow.
  • the disadvantage of the prior art is that: the priority of the call is not distinguished, and when all the calls of the AG are overloaded, the call is restricted according to the set call restriction ratio, so that the system can be protected from collapse under the impact of large traffic.
  • the connection of high priority calls will fail.
  • the second technique of the prior art is to set multiple overload levels on the AG device, each level corresponding to a certain system load. For example, set three overload levels, where the first level overload corresponds to 70% CPU usage, the second level overload corresponds to 85 % CPU usage, and the third level overload corresponds to 95% CPU usage.
  • the call restriction policy can limit the call according to the proportion of the user, or set the priority of the user or the priority of the call number, and limit the call according to the call priority.
  • the AG uses the H.248.11 Gateway Overload Control Packet to report the overload information of the AG to the MGC.
  • the AG rejects all calls when it reaches the highest level of overload, and processes it according to the normal call flow when other levels are overloaded, and does not initiate any call restriction.
  • the MGC restricts the calling and called of the AG according to the preset call restriction policy.
  • the AG basically does not limit calls. It mainly relies on the MGC to limit calls. It has higher functional requirements for MGC and has interoperability requirements.
  • the AG basically does not limit calls, and reports a large number of users picking up the phone to the MGC.
  • the impact on the MGC is large, and the MGC is overloaded.
  • the technical problem to be solved by the present invention is to overcome the shortcomings of the existing AG equipment overload control method, when the high priority call is guaranteed, the MGC is high, the MGC is overloaded, and the overload condition of the AG is not easily alleviated.
  • the AG equipment overload control method not only prioritizes the connection of high-priority calls, but also reduces the dependence on the MGC, prevents the MGC from being overloaded, and quickly relieves the overload of the AG and shortens the time affected by the service.
  • the AG device limits the call to the user as the calling party, including the following steps:
  • the access media gateway determines the overload level after the user with the user initiates the call as the calling party and detects the overload of the user;
  • the access media gateway determines whether the call is a high priority call to be guaranteed by the overload level, and if yes, reports an off-hook event, and processes according to a normal call flow; otherwise, the call is directly rejected.
  • the high priority call is a preset emergency call
  • an emergency call number map is configured on the access media gateway, or an emergency call number map is sent from the media gateway controller to the access media gateway when the system starts. .
  • step C Preferably, in the step C:
  • the access media gateway buffers the off-hook event, directly puts a dial tone and a number on the user port, and matches the number of the emergency call number to determine whether it is an emergency call. If it does not match, the call is determined to be an ordinary call.
  • the user port puts a busy tone or a notification tone to release the call; if it matches, it determines that the call is an emergency call;
  • the access media gateway reports an off-hook event to the media gateway controller, the media gateway controller After receiving the off-hook event, the device sends a normal number map to the access media gateway, and notifies the access media gateway to put a dial tone to the calling user port, and the access media gateway matches the cached number with the received normal number map. Then, according to the normal call process, the number is reported to the media gateway controller if it matches, and if there is no match, the user port is placed with a busy tone or a notification tone to release the call.
  • the high-priority call is a call of a preset high-priority user port, and the priority of the user port is configured on the access media gateway; in step C, the priority of the user port is queried.
  • the attribute determines whether the call is a high-priority user port.
  • the call to the high-priority user port reports the off-hook event to the media gateway controller, and processes according to the normal call flow; otherwise, the user port is directly placed with a busy tone or a notification tone. Release the call.
  • the high priority call is a preset emergency call and a high priority port call
  • an emergency call number map is configured on the access media gateway, or the media gateway controller accesses the media gateway when the system starts.
  • the emergency call number map is sent, and the priority of the user port is also configured on the access media gateway.
  • step C determining whether it is a high priority port call and an emergency call, if it is an emergency call or a high priority port If the call is made, the off-hook event is reported to the media gateway controller, and the normal call flow is processed; if neither is, the user port is directly placed with a busy tone or a notification tone to release the call.
  • an overload level and an overload value are configured on the access media gateway, and the access media gateway determines whether the overload is based on a preset overload level and an overload threshold, and an overload level.
  • the access media gateway overload control method provided by the present invention the access media gateway restricts the call of the user as the called party, and includes the following steps:
  • the access media gateway determines the overload level after receiving the call of the user with the call as the called party and detecting the overload of the user;
  • the media gateway controller determines in advance whether the call is an emergency call according to the called number analysis, and then sets an associated emergency call identifier or associated priority in the message sent to the access media gateway.
  • the access media gateway detects the associated emergency call identity or associated priority. If the emergency call identity is set or the associated priority is set to high priority, the call is a high priority call and is processed according to the normal call flow. If the emergency call identity is not set or the associated priority is set to low priority, the access media gateway is The call is rejected in the reply message sent to the Media Gateway Controller.
  • the access media gateway queries the priority attribute of the called user port according to the terminal identifier of the called user. If the called user port is a high priority port, the processing is performed according to a normal call flow. ; otherwise the call is rejected in the reply message sent to the Media Gateway Controller.
  • the media gateway controller determines in advance whether the call is an emergency call according to the called number analysis, and then sets an associated emergency call identifier or associated priority in the message sent to the access media gateway;
  • the access media gateway determines whether it is a high priority call according to the emergency call identifier or the associated priority and the priority attribute of the user port, if the emergency call identifier is set, or the associated priority is set to a high priority, or the called user If the port is a high-priority port, it is processed according to the normal call flow; otherwise, the call is rejected in the reply message sent to the media gateway controller.
  • the access media gateway reports the access media gateway to the media gateway controller by using the H.248.11 gateway overload control packet when an overload occurs.
  • the media gateway controller directly initiates a corresponding call restriction policy for the call to the access media gateway according to the overload level of the called access media gateway, and proportionally calls or preferentially guarantees a high priority call;
  • the policy is to prioritize high priority calls, and the media gateway controller directly rejects the normal call and sets the associated emergency call identity or sets the associated priority to high priority for the high priority call.
  • the access media gateway provided by the present invention is provided with:
  • Storage module stores different overload levels, and high priority calls to be guaranteed for each overload level; determines overload level module: determines the overload level after detecting the access media gateway overload;
  • the calling call restriction module determines whether the call is a high priority call to be guaranteed by the overload level when the user who is connected to the media gateway initiates the call as the calling party, and if yes, reports the off-hook event, and performs the normal call flow. Processing; otherwise the call is rejected directly. ⁇
  • the access media gateway provided by the present invention is provided with:
  • Storage module stores different overload levels, and high priority calls to be guaranteed for each overload level; determines overload level module: determines the overload level after detecting the access media gateway overload;
  • the called call restriction module when the access media gateway receives the call with the user as the called party, determines whether the call is a high priority call to be guaranteed by the overload level, and if so, processes according to a normal call flow; Otherwise the call is rejected to the Media Gateway Controller.
  • the invention has the following advantages:
  • the AG device of the present invention distinguishes the priority of the call, preferentially guarantees the connection of the high priority call when the AG device is overloaded, and sets the call restriction policy on the AG, and actively limits the call when overloaded, thereby reducing Less dependence on MGC, or no dependence on MGC at all.
  • the AG takes active call restriction measures when overloading, and shields the MGC from a large number of off-hook messages, which reduces the impact on the MGC and prevents the MGC from being overloaded. It also reduces the message interaction with the MGC and reduces the load on the AG. It can quickly alleviate the overload of the AG, thus shortening the time of business impact.
  • Figure 1 shows the basic network topology.
  • the overload call restriction policy of the AG of the present invention guarantees the connection of high priority calls under low level overload and rejects all calls when the highest level is overloaded.
  • High priority calls can be just preset emergency calls, such as 110, 119, 120, etc., or just calls to a preset high priority user port, or both emergency calls and high priority user ports.
  • the AG limits calls based on the overload level and the priority of the call. For example, if a secondary overload limit call is used, the connection of a high priority call (emergency call and/or high priority user port call) is guaranteed at the first level of overload, the normal call is rejected, and all calls are rejected during the secondary overload. If a three-level overload limit call is used, all high-priority calls (emergency calls and high-priority user port calls) are guaranteed during the first-level overload, and the normal call is rejected; the highest priority call is guaranteed during the secondary overload (emergency call or High priority user port calls); reject all calls when the level 3 is overloaded.
  • a secondary overload limit call the connection of a high priority call (emergency call and/or high priority user port call) is guaranteed at the first level of overload, the normal call is rejected, and all calls are rejected during the secondary overload.
  • Figure 1 shows the basic network topology.
  • the network management system or command line terminal manages MGC and AG through the management interface.
  • the overload level and overload threshold are set by default in the AG system, or the overload level and overload threshold are configured on the AG through the management interface. For example, three overload levels are set, and the overload is detected according to the CPU usage.
  • the first-level overload threshold is 70% CPU usage
  • the secondary overload threshold is 85% CPU usage
  • the third-level overload threshold is 95% CPU usage. .
  • the emergency call number map is configured on the AG through the management interface or the emergency call number map is obtained from the MGC when the AG system is started.
  • This emergency call number map only contains the dial plan of the emergency call, such as 119, 110, 120, etc., which is identical to the data structure of the positive constant map, but the content is different.
  • the number of emergency calls llx
  • the emergency call number is configured on the AG It is not related to the MGC.
  • the emergency call number map is configured on the MGC, the MGC and the AG need to cooperate with each other in the protocol and process.
  • Configure the priority of the AG user port through the management interface For example, configure the port connected to the common resident user as Low priority, configure the ports connecting government users and important business users to high priority.
  • the call handling mechanism of the AG is as follows.
  • the user of the AG device is the calling party.
  • the AG After the AG detects that the user picks up the phone, the AG first determines whether the system is overloaded according to the preset overload level and the overload threshold (the AG queries the current system resource usage, such as the CPU occupancy rate to determine whether the system is overloaded). If it is not overloaded, it will be processed according to the normal call flow. If it is overloaded, the corresponding call restriction policy will be adopted according to the overload level.
  • the AG's call restriction policies There are three types of AG's call restriction policies:
  • the AG will cache the off-hook event, directly put a dial tone on the user port and receive the number, and match the received number with the emergency call number map. If there is no match, it is determined that the call is a normal call, and a busy tone or a notification tone is directly sent to the user port to release the call; if it matches, the call is determined to be an emergency call;
  • the AG caches the number and the ⁇ El t Notify command reports the off-hook event to the MGC.
  • the MGC After receiving the off-hook event, the MGC sends a digital map to the AG through the Modify command, and notifies the AG to the calling user port. Put a dial tone.
  • the number stored on the AG is a number map that is used to determine whether a call is an emergency call.
  • the MGC delivers a normal number map.
  • the normal number map should contain dial plans for normal calls and emergency calls. Therefore, the AG actually has two numbers.
  • the standard call flow stipulation is that a dial tone is placed at this time.
  • the dial tone is not placed under the control of the MGC, but the dial tone is directly placed in advance. There is no need to execute the MGC's dial tone command.
  • the AG Since the AG has received the number, after receiving the Modify command, it only needs to match the cached number with the received number map, and then process it according to the normal call flow. If it matches, report the number through the Notify command. To the MGC, if there is no match, place a busy tone or notification tone on the user port to release the call.
  • the normal number map contains all the allowed dial plans, including emergency calls and normal calls, because the first time it has been matched with the emergency call number map and the normal call is filtered, so the second match with the normal number map actually Or the content of the emergency call is matched.
  • the second match is only to perform an abnormal protection, that is, to prevent the inconsistency between the emergency call number map and the corresponding content of the normal number map, and finally the normal number map issued by the MGC is taken as the standard.
  • the AG queries the priority of the off-hook port. If the off-hook port is a high-priority port, the off-hook event is reported to the MGC through the Notify command, and the normal call flow is processed. If the off-hook port is a normal port, the busy tone or notification tone is directly sent to the user port. To release the call.
  • the AG first queries the priority attribute of the off-hook port. If the off-hook port is a high-priority port, the Notify command is used to report the message to the MGC. The machine event is processed according to the normal call flow; if the off-hook port is a normal port, it is further processed according to the aforementioned call flow for ensuring the emergency call connection.
  • the user of the AG device is called as the called
  • the overload control mechanism of the AG includes the users under the overload AG as the calling and called, and the two can be combined at the same time.
  • the AG uses the H.248.11 gateway overload control packet to report the overload information of the AG to the MGC when the overload occurs.
  • the MGC initiates the corresponding call to the AG according to the overload level of the AG.
  • Call restriction policy can be either a proportional call or a priority guarantee for a high priority call. If the call restriction policy is to preferentially guarantee a high priority call, the MGC directly rejects the normal call, and sets the associated emergency call identifier or sets the associated priority to a high priority for the high priority call, if the MGC does not support the overloaded AG.
  • the MGC still processes all calls in the normal process, and the AG independently completes the call restriction as the called party.
  • the emergency call identity and associated priority are attributes of the context in H.248.
  • the association priority is used to indicate the order in which the MG processes the association, and the emergency call identifier is used to instruct the MG to preferentially process the call with the emergency call identity.
  • the MGC sends an Add message to the AG, creates an association, and sets the associated related attributes (including the emergency call identity or associated priority).
  • the AG determines whether the call is a high priority call based on the associated emergency call identity or associated priority. Because the AG user cannot analyze the called number when it is called, the AG cannot determine whether a call is an emergency call.
  • the MGC needs to identify the call.
  • the MGC identifies the call by setting the associated emergency call identifier or association priority. level.
  • the restricted call of the called AG and the restricted call of the MGC can be used independently of each other, that is, the MGC call restriction + the called AG restriction call, the MGC unlimited call + the called AG restriction call can be established, but the MGC is not allowed to call or the MGC is limited. Strategy choice The final limit call effect is different.
  • the AG does not report the overload information to the MGC when the overload occurs.
  • the AG independently completes the call with the user as the called call.
  • the AG After the AG receives the Add command sent by the MGC, the AG first determines whether the system is overloaded according to the preset overload level and the overload value (the AG queries the current system resource usage, such as the CPU usage to determine whether the system is overloaded). If it is not overloaded, it will be processed according to the normal call flow. If it is overloaded, the call restriction will be activated. There are three types of AG's call restriction policies.
  • the AG cannot determine whether the call is an emergency call, and the MGC can determine whether the call is an emergency call by the called number analysis, and then set the associated emergency call identifier or association in the Add message sent to the AG. Priority, the AG knows the priority of the call based on the associated emergency call identity or associated priority.
  • the AG detects the associated emergency call identifier or associated priority (if the MGC does not have a call restriction function, it may also have an emergency call identifier or an associated priority.
  • the call may be set.
  • Associated emergency call identifier If the emergency call identity is set or the associated priority is set to high priority, the AG considers the call to be a high priority call and processes it according to the normal call flow; if the emergency call identity is not set or the associated priority is set to For low priority, the AG considers the call to be a normal call and rejects the call in the Reply sent to the MGC.
  • the AG queries the priority of the called user port according to the terminal identifier of the called user (the terminal identifier is a string used by the MGC and the MG to uniquely identify a user port). Attributes. If the called user port is a high priority port, it is processed according to the normal call flow; if the called user port is a normal port, the call is rejected in the Reply sent to the MGC.
  • the MGC supports the associated emergency call identifier and associated priority
  • the user port priority may not be set.
  • the associated emergency call identifier or associated priority is to identify the priority of a call. There may be multiple cases of high priority: The priority of the calling port is high, and the priority of the called port is high. The priority of the AG querying the called port can only be adapted to the latter of the above two cases, so the MGC is set.
  • the method of the associated emergency call identifier or priority is better than the method of the AG querying the called port priority, but the MGC may not support the associated emergency call identifier and the associated priority, so the present invention queries the called port priority by querying Ways to meet different situations. (3) Limit calls based on the emergency call identity or associated priority and the priority attribute of the user port
  • the AG first detects the associated emergency call identity or associated priority. If the emergency call identity is set or the associated priority is set to high priority, the AG considers the call to be a high priority call and processes it according to the normal call flow; if the emergency call identity is not set or the associated priority is not set Or the associated priority is set to a low priority, and the AG further queries the priority attribute of the called user port according to the terminal identifier of the called user. If the called user port is a high priority port, it is processed according to the normal call flow; if the called user port is a normal port, the call is rejected in the Reply sent to the MGC. Here, the reverse can also be performed. Check the port and check the emergency call identifier.
  • the emergency call identifier is set, or the associated priority is set to high priority, or the called user port is a high priority port, press the normal call flow. Processing; if it is neither an emergency call nor a high priority port, the call is rejected in the response message sent to the MGC.
  • the present invention provides an AG device overload control method for protecting an AG system from crashes during high traffic load and effectively guaranteeing high priority calls (including emergency calls and/or high priority user port calls).
  • high priority calls including emergency calls and/or high priority user port calls.
  • the correlation with the MGC is small, and can be completely independent of the MGC implementation, and the interworking requirements with the MGC are low.
  • the MGC can shield a large number of users from off-hook messages, which can greatly reduce the impact on the MGC and effectively prevent the MGC from being overloaded.
  • there is less message interaction with the MGC during high traffic load which can quickly relieve the overload of the AG, and the service is affected for a short time.
  • the invention also provides an access media gateway, wherein the access media gateway is provided with a storage module, an overload level module and a calling restriction call module.
  • Storage module Stores different overload levels, and high priority calls to be guaranteed for each overload level, such as setting 3 overload levels, ensuring all high priority calls (emergency calls and high priority user port calls) during level 1 overload ), rejects the normal call; guarantees the highest priority call (emergency call or high priority user port call) during the secondary overload; rejects all calls during the three-level overload, etc., as described in the above method.
  • Determine the overload level module After detecting the overload of the access media gateway, determine the overload level, such as detecting the overload according to the CPU occupancy rate, the first-level overload threshold is 70% CPU usage, and the secondary overload threshold is 85% CPU usage. The rate, the three-level overload threshold is 95% of the CPU usage, etc., as described in the above method.
  • the calling call restriction module determines whether the call is a high priority call to be guaranteed by the overload level when the user who is connected to the media gateway initiates the call as the calling party, and if yes, reports the off-hook event, and performs the normal call flow. Processing; otherwise the call is rejected directly.
  • the calling call restriction module stores an emergency call number map, which may be configured in the calling P call module, or may be acquired from the MGC when the AG system is started; the calling call restriction module may Use to ensure the connection of emergency calls, ensure the connection of high-priority port calls, and ensure emergency calls at the same time
  • a call restriction policy such as a connection with a high priority port call restricts the calling call, as described in the above method.
  • the access media gateway of the present invention may also be provided with a storage module, an overload level module and a called call restriction module.
  • the storage module is as described above for the storage module in the access media gateway.
  • Determining the overload level module After detecting the overload of the access media gateway, determine the level of overload, as described above for determining the overload level module in the access media gateway. '
  • the called call restriction module when the access media gateway receives the call with the user as the called party, determines whether the call is a high priority call to be guaranteed by the overload level, and if so, processes according to a normal call flow; Otherwise the call is rejected to the Media Gateway Controller.
  • the called call restriction module can use the emergency call identifier or the associated priority to limit the call, limit the call according to the priority attribute of the user port, and limit the call policy according to the emergency call identifier or the associated priority and the priority attribute of the user port. To limit the called call. Specifically, it is described in the above method.
  • the access media gateway only the storage module, the overload level module and the calling call restriction module may be set; in the access media gateway, only the storage module, the overload level module and the called call restriction module may be set;
  • the media gateway can also be provided with a storage module, a determination overload level module, a calling call restriction module, and a called call restriction module.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

接入媒体网关过载控制方法和接入媒体网关
技术领域
本发明涉及通信技术领域， 尤其涉及一种接入媒体网关过载控制方法和接入媒体网 关。
发明背景
随着 NGN (下一代网络）的逐渐规模商用， NGN设备的可靠性必须得到充分保证。 由于用户话务量的不确定性以及设备处理能力的限制，话务量负荷超过设备正常处理能 力即过载的情况是会经常发生的， 如果过载导致设备部分或全部故障， 则会造成业务中 断， 因此设备的过载控制能力即在过载情况下的工作能力是影响设备可靠性乃至网各可 靠性的重要因素。
NGN由媒体网关控制器（ MGC )、 媒体网关（ MG )、 信令网关（ SG ) 以及相关的 应用服务器等设备組成， 媒体网关包括接入媒体网关 （AG ) 和中继媒体网关 （TG ), AG提供用户侧接口连接用户终端设备如话机，终结用户线路信令并通过 H.248或 MGCP 协议与 MGC进行交互， 完成媒体流转换。 MGC负责呼叫控制， 通过 H.248或 MGCP 协议控制 AG完成媒体流连接的建立和释放。
由于系统的 CPU运算速度等因素的限制， AG、 MGC的呼叫处理能力是有限的， 为保证业务的正常运营， 系统设计应保证系统的呼叫处理能力能够满足正常话务量负荷 要求。 例如 1个 AG的容量为 2000线 POTS用户， 每用户的平均话务量为 O.lerlan, 每 次呼叫的平均时长为 60s， 则 AG 的平均话务量为 200erian, 呼叫处理能力需要达到 3.3CAPS ( Call Attempts Per Second, 即每秒试呼次数）， 即每秒处理 3.3次呼叫。 但在 很多情况下例如节 "ί艮日或每一天的忙时用户话务量都会大大超过 O.lerlan, 从而超过系 统正常处理能力。 为了保证在大话务量负荷下系统的正常工作和业务的正常运营， 除了 在系统设计.时预留一定的余量以满足高负荷的要求外 （例如用户的平均话务量若为 O.lerlan, 则系统设计时按照 0.2erla 来进行设计）， 设备还提供过载控制机制以防止系 统在大话务量冲击下崩溃并尽可能保证业务。
AG设备的过载控制实际上就是在系统负荷达到某一门限时对用户呼叫进行限呼， 以使系统负荷尽快恢复到正常水平， 从而防止系统崩溃。 这种对用户呼叫进行限呼的方 法必然会对过载情况下的用户业务产生影响，如何将对用户业务的影响降到最小取决于 限呼策略的选择。 一台 AG设备下的用户可以是普通居民用户， 也可以是商业用户或政 府用户， 不同的用户对于业务可靠性的要求是不同的； 一台 AG设备下的用户呼叫可以 是普通呼叫， 也可以是急救、 报警等紧急呼叫， 不同的呼叫对于业务可靠性的要求也是 不同的。 因此 AG设备的过载控制的关键技术在于研究合理的处理机制和限呼策略， 在 过载下尽可能保证高优先级呼叫。
现有技术一是在 AG设备上设置多个过载级别，每一级对应一定的系统负荷。例如 设置 3个过载级别， 其中一级过载对应 70 %的 CPU占用率， 二级过载对应 85 %的 CPU 占用率， 三级过载对应 95 %的 CPU占用率。
在 AG设备上设置各级过载时的限呼用户比例， 当系统达到一定的过载级别时， 系 统按照限呼比例启动限呼。例如当采用 3级过载控制时，一级过载时对 50 %的用户呼叫 进行限呼，二级过载时对 70 %的用户呼叫进行限呼，三级过载时对所有用户呼叫进行限 呼。 进行限呼时， 随机选取 50 %或 70 %的用户呼叫进行限呼， 例如若 50 %限呼， 则在 每 10次呼叫中拒绝 5次呼叫； 若 70 %限呼， 则在每 10次呼叫中拒绝 7次呼叫。
对于 AG设备所带用户作为主叫的情况， 当 AG检测到用户摘机后， AG根据当前 的过载级别确定是否对该呼叫进行限呼， 若是则直接拒绝该呼叫， 对用户放忙音或通知 音。 否则通过 H.248/MGCP向 MGC上报摘机事件， 按照正常的呼叫流程进行处理。
对于 AG设备所带用户作为被叫的情况， 当 AG收到 MGC下发的 Add命令后， AG根据当前的过载级别确定是否对该呼叫进行限呼， 若是则在向 MGC的 Reply中拒 绝呼叫。 若否则在向 MGC的 Reply中接受呼叫， 按照正常的呼叫流程进行处理。
现有技术一的缺点是： 不区分呼叫的优先级，在 AG设备过载时对所有呼叫统一按 设置的限呼比例进行限呼， 这样虽然可以保护系统在大话务量冲击下免于崩溃， 但对高 优先级呼叫没有保证措施， 即使在轻度过载下也会导致高优先级呼叫的接续失败。
现有技术二是在 AG设备上设置多个过载级别，每一级对应一定的系统负荷。例如 设置 3个过载级别 , 其中一级过载对应 70 %的 CPU占用率， 二级过载对应 85 %的 CPU 占用率， 三级过载对应 95 %的 CPU占用率。
在 MGC设备上设置针对 AG过载的限呼策略。 限呼策略可以是按用户比例限呼， 也可以设置用户的优先级或呼叫号码的优先级， 按照呼叫优先级进行限呼。
当 AG检测到自身过载时，使用 H.248.11网关过载控制包向 MGC上报 AG的过载 信息。
AG在达到最高级别过载时拒绝所有呼叫，在其它级别过载时均按照正常的呼叫流 程进行处理， 不启动任何限呼。 MGC在收到 AG上报的过载信息后， 根据预设的限呼 策略对该 AG的主叫和被叫进行限呼。 现有技术二虽然可对高优先级呼叫进行保证， 但仍存在下列缺点：
1、 AG基本不做限呼， 主要依赖于 MGC进行限呼， 对 MGC的功能要求较高， 且 有互通要求。
2、 AG基本不做限呼， 将大量的用户摘机消息上报 MGC, 对 MGC的冲击大， 容 易造成 MGC过载。
3、 在过载下由于 AG仍然按正常的呼叫流程进行处理（除最高级别过载外）， AG 与 MGC之间交互消息仍然较多， AG的过载情况不容易得到緩解， 从而长时间影响业 务的正常使用。 发明内容
本发明所要解决的技术问题是：克服现有的 AG设备过载控制方法在保证高优先级 呼叫时， 对 MGC要求高， 易造成 MGC过载， 且 AG的过载情况不容易得到緩解的缺 点， 提供一种 AG设备过载控制方法， 不但优先保证高优先级呼叫的接续， 而且减少对 MGC的依赖， 防止 MGC过载， 并快速緩解 AG的过载， 缩短业务影响的时间。 本发明为解决上述技术问题所采用的技术方案为：
这种接入媒体网关过载控制方法， 由 AG设备对所带用户作为主叫进行限呼， 包括 以下步骤：
A、 在接入媒体网关上设置不同的过载级别， 以及每一过载级别所要保证的高优先 级呼叫；
B、 接入媒体网关在其所带用户作为主叫发起呼叫、 并检测到自身过载后， 确定过 载的级别；
C、 接入媒体网关确定所述呼叫是否为该过载级别所要保证的高优先级呼叫， 若是 则上报摘机事件， 按正常的呼叫流程进行处理； 否则直接拒绝该呼叫。
优选的， 所述的高优先级呼叫为预设的紧急呼叫 , 且接入媒体网关上配置有紧急 呼叫数图， 或系统启动时从媒体网关控制器向接入媒体网关下发紧急呼叫数图。
优选的 , 所述的步骤 C中：
接入媒体网关将摘机事件緩存， 直接对用户端口放拨号音、 收号并与紧急呼叫数 图做号码匹配以确定是否为紧急呼叫， 如果不匹配则确定该呼叫为普通呼叫， 直接对该 用户端口放忙音或通知音以释放呼叫； 如果匹配则确定该呼叫为紧急呼叫；
对于紧急呼叫， 接入媒体网关向媒体网关控制器上报摘机事件， 媒体网关控制器 收到摘机事件后向接入媒体网关下发正常数图， 并通知接入媒体网关向主叫用户端口放 拨号音， 接入媒体网关将緩存的号码与收到的正常数图进行匹配， 然后按正常的呼叫流 程处理， 即： 如果匹配则将号码上报给媒体网关控制器， 如果不匹配则对该用户端口放 忙音或通知音以释放呼叫。
优选的， 所述的高优先级呼叫为预设的高优先级用户端口的呼叫， 且接入媒体网 关上配置有用户端口的优先级； 所述的步骤 C中，通过查询用户端口的优先级属性确定 是否为高优先级用户端口的呼叫，对于高优先级用户端口的呼叫向媒体网关控制器上报 摘机事件， 按正常的呼叫流程进行处理； 否则直接对该用户端口放忙音或通知音以释放 呼叫。
优选的， 所述的高优先级呼叫同时为预设的紧急呼叫和高优先级端口呼叫， 接入 媒体网关上配置有紧急呼叫数图，或系统启动时从媒体网关控制器向接入媒体网关下发 紧急呼叫数图， 且接入媒体网关上还配置有用户端口的优先级； 所述的步骤 C中： 先后 确定是否为高优先级端口呼叫和紧急呼叫， 若是緊急呼叫或高优先级端口呼叫， 则向媒 体网关控制器上报摘机事件， 按正常的呼叫流程进行处理； 若两者都不是， 则直接对该 用户端口放忙音或通知音以释放呼叫。
可选的， 在接入媒体网关上配置过载级别和过载阐值， 接入媒体网关根据预设的 过载级別和过载阈值确定是否过载， 以及过载的级別。 本发明提供的接入媒体网关过载控制方法， 由接入媒体网关对所带用户作为被叫 的呼叫进行限呼， 包括以下步骤：
a、 在接入媒体网关上设置不同的过载级别， 以及每一过载级别所要保证的高优先 级呼叫；
b、 接入媒体网关在接收到其所带用户作为被叫的呼叫、 并检测到自身过载后， 确 定过载的级别；
c、 确定呼叫是否为该过载级别所要保证的高优先級呼叫， 若是则按正常的呼叫流 程进行处理； 否则向媒体网关控制器拒绝该呼叫。
优选的，所述的步骤 c中，事先由媒体网关控制器根据被叫号码分析确定该呼叫是 否是紧急呼叫， 然后在发送给接入媒体网关的消息中设置关联的紧急呼叫标识或关联优 先级； 接入媒体网关检测关联的紧急呼叫标识或关联的优先级， 如果紧急呼叫标识被设 置或关联优先级被设置为高优先级， 则该呼叫是高优先级呼叫， 按正常的呼叫流程进行 处理； 如果紧急呼叫标识未被设置或关联优先级被设置为低优先级， 则接入媒体网关在 发送给媒体网关控制器的应答消息中拒绝该呼叫。
优选的 ,所述的步骤 C中，接入媒体网关根据被叫用户的终端标识查询被叫用户端 口的优先级属性， 如果被叫用户端口是高优先级端口， 则按正常的呼叫流程进行处理； 否则在发送给媒体网关控制器的应答消息中拒绝该呼叫。
优选的所述的步驟 C中，事先由媒体网关控制器根据被叫号码分析确定该呼叫是否 是紧急呼叫， 然后在发送给接入媒体网关的消息中设置关联的紧急呼叫标识或关联优先 级；接入媒体网关先后根据紧急呼叫标识或关联优先级以及用户端口的优先级属性确定 是否为高优先级呼叫， 若紧急呼叫标识被设置， 或关联优先级被设置为高优先级， 或被 叫用户端口是高优先级端口， 则按正常的呼叫流程进行处理； 否则在发送给媒体网关控 制器的应答消息中拒绝该呼叫。
优选的， 若接入媒体网关或媒体网关控制器支持 H.248.11 网关过载控制包， 则接 入媒体网关在发生过载时使用 H.248.11 网关过载控制包向媒体网关控制器上报接入媒 体网关的过载信息， 由媒体网关控制器根据被叫接入媒体网关的过载级别直接对到该接 入媒体网关的呼叫启动相应的限呼策略， 按比例限呼或优先保证高优先级呼叫； 如果限 呼策略是优先保证高优先级呼叫， 则媒体网关控制器直接拒绝普通呼叫， 并对高优先级 呼叫设置关联的紧急呼叫标识或将关联优先级设置为高优先级。
本发明提供的接入媒体网关中设置有：
存储模块： 存储有不同的过载级别， 以及每一过载级别所要保证的高优先级呼叫； 确定过载级别模块： 检测到接入媒体网关过载后， 确定过载的级别；
主叫限呼模块： 在接入媒体网关所带用户作为主叫发起呼叫时确定所述呼叫是否 为该过载级别所要保证的高优先级呼叫， 若是则上报摘机事件， 按正常的呼叫流程进行 处理； 否则直接拒绝该呼叫。 ·
本发明提供的接入媒体网关中设置有：
存储模块： 存储有不同的过载级别， 以及每一过载级别所要保证的高优先級呼叫； 确定过载级别模块： 检测到接入媒体网关过载后， 确定过载的级别；
被叫限呼模块： 在接入媒体网关接收到其所带用户作为被叫的呼叫时确定所述呼 叫是否为该过载级别所要保证的高优先级呼叫， 若是则按正常的呼叫流程进行处理； 否 则向媒体网关控制器拒绝该呼叫。 本发明的有益效果为： 本发明 AG设备区分呼叫的优先级，在 AG设备过载时优先 保证高优先级呼叫的接续， 并在 AG上设置限呼策略， 在过载时主动限呼， 从而可以减 少对 MGC的依赖， 或完全不依赖 MGC。 AG在过载时采取主动的限呼措施， 对 MGC 屏蔽了大量的用户摘机消息，减轻了对 MGC的冲击，防止 MGC过载；也减少了与 MGC 之间的消息交互， 减轻了 AG的负荷， 可以快速緩解 AG的过载， 从而缩短业务影响的 时间。 ' 附图简要说明
图 1为基本网络拓朴图。
实施本发明的方式
下面根据附图和实施例对本发明作进一步详细说明：
本发明 AG的过载限呼策略是在低级別过载下保证高优先级呼叫的接续，在最高级 别过载时拒绝所有呼叫。 高优先级呼叫可以只是预设的紧急呼叫， 例如 110、 119、 120 等， 也可以只是预设的高优先级用户端口的呼叫， 或者同时包括紧急呼叫和高优先级用 户端口的呼叫。
AG根据过载级别和呼叫的优先级进行限呼。 例如如果采用二级过载限呼， 则在一 级过载时保证高优先级呼叫（紧急呼叫和 /或高优先级用户端口呼叫）的接续，拒绝普通 呼叫， 在二级过载时拒绝所有呼叫。 如果采用三级过载限呼， 则在一级过载时保证所有 高优先级呼叫 （紧急呼叫和高优先级用户端口呼叫）， 拒绝普通呼叫； 在二级过载时保 证最高优先级呼叫 （紧急呼叫或高优先级用户端口呼叫）； 在三级过载时拒绝所有呼叫。
如图 1为基本网络拓朴图， 网管系统或命令行终端通过管理接口对 MGC和 AG进 行管理。 AG系统内部默认设置过载级别和过载阈值， 或者通过管理接口在 AG上配置 过载级别和过载阈值。 例如设置 3个过载级别， 根据 CPU占用率检测过载， 一级过载 阈值为 70 %的 CPU占用率， 二级过载阔值为 85 %的 CPU占用率， 三级过载阈值为 95 %的 CPU占用率。
通过管理接口在 AG上配置紧急呼叫数图或者在 AG系统启动时从 MGC获取紧急 呼叫数图。 这个紧急呼叫数图只包含紧急呼叫的拨号计划， 如 119、 110、 120等， 与正 常数图的数据结构完全相同， 只是内容不同。 如紧急呼叫数图： llx|12x; 正常数图： [2-8]xxxxxx| 13xxxxxxxxx )0xxxxxxxxx|l [0124-9]x|E|F|x.Fo 紧急呼叫数图如果配置在 AG 上则与 MGC不相关； 紧急呼叫数图配置在 MGC上时，需要 MGC与 AG进行协议和流 程上的配合。
通过管理接口配置 AG用户端口的优先级,例如将连接普通居民用户的端口配置为 低优先级， 将连接政府机关用户、 重要商业用户的端口配置为高优先级。 AG的呼叫处 理机制如下。
1、 AG设备所带用户作为主叫
当 AG检测到用户摘机后， AG首先根据预设的过载级别和过载阔值确定系统是否 过载（由 AG查询当前系统资源的使用情况例如 CPU占用率来确定系统是否过载）。 如 果未过载则按照正常的呼叫流程处理， 如果过载则根据过载级别采取相应的限呼策略。 AG的限呼策略有以下三种：
( 1 )保证紧急呼叫的接续
a、 如果限呼策略是保证紧急呼叫的接续， 则 AG将摘机事件緩存， 直接对该用户 端口放拨号音并收号， 将收到的号码与紧急呼叫数图进行匹配。 如果不匹配则确定该呼 叫为普通呼叫， 直接对该用户端口放忙音或通知音以释放呼叫； 如果匹配则确定该呼叫 为紧急呼叫；
b、 对于紧急呼叫， AG将号码緩存， ^El t Notify命令向 MGC上报摘机事件； c、 MGC收到摘机事件后通过 Modify命令向 AG下发数图， 并通知 AG向主叫用 户端口放拨号音。 '
AG上存放的是专用于判断一个呼叫是否是紧急呼叫的数图， 此时 MGC下发的是 正常数图， 该正常数图应包含普通呼叫和紧急呼叫的拨号计划， 因此 AG实际上有两种 数图。
标准的呼叫流程规定是在此时放拨号音，但本发明由于在过载时 AG要自主进行收 号并分析， 因此未在 MGC的控制下放拨号音， 而是直接提前放了拨号音， 此时无需再 执行 MGC的放拨号音命令。
d、 AG因为已收完号， 因此在收到该 Modify命令后， 只需将緩存的号码与收到的 数图进行匹配， 然后按正常的呼叫流程进行处理， 如果匹配则通过 Notify命令上报号码 给 MGC, 如果不匹配则对该用户端口放忙音或通知音以释放呼叫。
正常数图包含了所有允许的拨号计划， 包括紧急呼叫和普通呼叫， 因为第一次已 与紧急呼叫数图进行过匹配， 并将普通呼叫过滤， 因此第二次与正常数图进行匹配实际 上还是匹配紧急呼叫的内容， 第二次匹配只是做一次异常保护， 即防止紧急呼叫数图与 正常数图的相应内容的不一致， 最终还是以 MGC下发的正常数图为准。
( 2 )保证高优先级端口呼叫的接续
如果限呼策略是保证高优先级端口呼叫的接续， 则 AG查询摘机端口的优先级属 性， 如果摘机端口是高优先级端口， 则通过 Notify命令向 MGC上报摘机事件， 按正常 的呼叫流程进行处理； 如果摘机端口是普通端口， 则直接对该用户端口放忙音或通知音 以释放呼叫。
( 3 ) 同时保证紧急呼叫的接续和高优先级端口呼叫的接续
如果限呼策略是同时保证紧急呼叫的接续和高优先级端口呼叫的接续，则 AG首先 查询摘机端口的优先级属性，如果摘机端口是高优先级端口，则通过 Notify命令向 MGC 上报摘机事件， 按正常的呼叫流程进行处理； 如果摘机端口是普通端口， 则进一步按照 前述的保证紧急呼叫接续的呼叫流程进行处理。
2、 AG设备所带用户作为被叫
被叫 AG过载时主叫 AG并不一定过载， 因此主叫 AG并不一定启动限呼。 AG的 过载控制机制包括过载 AG下带的用户作为主叫和被叫两种情况， 两者可以同时结合使 用。
如果 AG或 MGC支持 H.248.11网关过载控制包，则 AG在发生过载时使用 H.248.11 网关过载控制包向 MGC上报 AG的过载信息，由 MGC根据 AG的过载级别对到该 AG 的呼叫启动相应的限呼策略。 MGC 的限呼策略可以是按比例限呼， 也可以是优先保证 高优先级呼叫。 如果限呼策略是优先保证高优先级呼叫， 则 MGC直接拒绝普通呼叫， 并对高优先级呼叫设置关联的紧急呼叫标识或将关联优先级设置为高优先级， 如果 MGC不支持针对过载 AG的限呼功能，则 MGC对所有呼叫仍按正常流程进行处理， 由 AG独立完成所带用户作为被叫的限呼。
紧急呼叫标识和关联优先级都是 H.248中关联（ context )的属性。 关联优先级用于 指示 MG处理关联时的先后次序，紧急呼叫标识用于指示 MG优先处理带有紧急呼叫标 识的呼叫。 MGC向 AG发送 Add消息， 创建关联， 并设置关联的相关属性（包括紧急 呼叫标识或关联优先级）， AG根据关联的紧急呼叫标识或关联优先级确定这个呼叫是否 为高优先级呼叫。 因为 AG用户作为被叫时是无法分析被叫号码的， 所以 AG无法确定 一个呼叫是否是紧急呼叫， 需要 MGC对呼叫进行标识， MGC对呼叫进行标识的方法 就是设置关联的紧急呼叫标识或关联优先级。
这里描述的是 AG用户作为被叫的情况， 如果 MGC支持针对过载 AG的限呼， 则 可以减少到被叫 AG的呼叫， 此时被叫 AG既使没有限呼功能， 也可以减轻被叫 AG的 负荷。 被叫 AG的限呼与 MGC的限呼可以相互独立使用， 即 MGC限呼 +被叫 AG限 呼、 MGC不限呼 +被叫 AG限呼都可以成立， 但 MGC不限呼或 MGC限呼策略的选择 对于最终的限呼效果是不同的。
如果 AG或 MGC不支持 H.248.11网关过载控制包，则 AG在发生过载时不向 MGC 上报过载信息， 由 AG独立完成所带用户作为被叫的限呼。
当 AG收到 MGC发送的 Add命令后， AG首先根据预设的过载级别和过载阁值确 定系统是否过载（AG查询当前系统资源的使用情况例如 CPU 占用率确定系统是否过 载）。 如果未过载则按照正常的呼叫流程处理， 如果过载则启动限呼。 AG的限呼策略有 以下三种。
( 1 )根据紧急呼叫标识或关联优先级进行限呼
AG用户作为被叫时， AG无法确定该呼叫是否是紧急呼叫， 而 MGC可以通过被 叫号码分析确定该呼叫是否是紧急呼叫，然后在发送给 AG的 Add消息中设置关联的紧 急呼叫标识或关联优先级， AG根据关联的紧急呼叫标识或关联优先级得知该呼叫的优 先级。
AG检测关联的紧急呼叫标识或关联的优先级（如果 MGC没有限呼功能， 也可以 有紧急呼叫标识或关联优先级， 当 MGC根据被叫号码确定一个呼叫为紧急呼叫后， 可 以设置该呼叫的关联的紧急呼叫标识；)。 如果紧急呼叫标识被设置或关联优先级被设置 为高优先级， 则 AG认为该呼叫是高优先级呼叫， 按正常的呼叫流程进行处理； 如果紧 急呼叫标识未被设置或关联优先级被设置为低优先级， 则 AG认为该呼叫是普通呼叫， 在发送给 MGC的 Reply中拒绝该呼叫。
( 2 )根据用户端口的优先级属性进行限呼
如果 MGC不支持关联的紧急呼叫标识和关联的优先级，则 AG根据被叫用户的终 端标识（终端标识是 MGC和 MG用于唯一标识一个用户端口的字符串）查询被叫用户 端口的优先级属性。如果被叫用户端口是高优先级端口，则按正常的呼叫流程进行处理； 如果被叫用户端口是普通端口， 则在发送给 MGC的 Reply中拒绝该呼叫。
对于 AG用户作为被叫， 如果 MGC支持关联的紧急呼叫标识和关联优先级， 是可 以不用设置用户端口优先级的， 关联的紧急呼叫标识或关联优先级是标识一个呼叫的优 先级，一个呼叫如果是高优先级可能有多种情况： 主叫端口的优先级高、 被叫端口的优 先级高， AG查询被叫端口的优先级只能适应以上两种情况中的后一种， 因此 MGC设 置关联的紧急呼叫标识或优先级的方法要优于 AG查询被叫端口优先级的方法，但 MGC 有可能不支持关联的紧急呼叫标识和关联的优先級， 因此本发明通过查询被叫端口优先 级的方法来满足不同的情况。 ( 3 ) 同时根据紧急呼叫标识或关联优先级以及用户端口的优先级属性进行限呼
AG首先检测关联的紧急呼叫标识或关联的优先级。如果紧急呼叫标识被设置或关 联优先级被设置为高优先级， 则 AG认为该呼叫是高优先级呼叫， 按正常的呼叫流程进 行处理； 如果紧急呼叫标识未被设置或关联优先级未被设置或关联优先级被设置为低优 先级， 则 AG进一步根据被叫用户的终端标识查询被叫用户端口的优先级属性。 如果被 叫用户端口是高优先级端口， 则按正常的呼叫流程进行处理； 如果被叫用户端口是普通 端口， 则在发送给 MGC的 Reply中拒绝该呼叫。 这里也可以反过来， 先查端口再查紧 急呼叫标识， 若紧急呼叫标识被设置， 或关联优先级被设置为高优先级， 或被叫用户端 口是高优先級端口， 则按正常的呼叫流程进行处理； 若既不是紧急呼叫也不是高优先级 端口， 则在发送给 MGC的应答消息中拒绝该呼叫。
本发明提供了一种 AG设备过载控制方法，用于保护 AG系统在高话务量负荷时免 于崩溃， 同时有效保证高优先级呼叫（包括紧急呼叫和 /或高优先级用户端口的呼叫）的 接续， 与 MGC的相关性小， 并且可以完全独立于 MGC实施， 与 MGC的互通要求低。 在高话务量负荷时可对 MGC屏蔽大量的用户摘机消息，可以大大减轻对 MGC的冲击， 有效防止 MGC过载。 同时在高话务量负荷时与 MGC之间的消息交互少， 可以快速緩 解 AG的过载， 业务受影响的时间短。
本发明还提供一种接入媒体网关， 接入媒体网关中设置有存储模块、 确定过载级 别模块和主叫限呼模块。
存储模块： 存储有不同的过载级别， 以及每一过载级别所要保证的高优先级呼叫， 如设置 3个过载级别， 一级过载时保证所有高优先级呼叫 （紧急呼叫和高优先级用户端 口呼叫）， 拒绝普通呼叫； 在二级过载时保证最高优先级呼叫 （紧急呼叫或高优先級用 户端口呼叫）； 在三级过载时拒绝所有呼叫等， 具体如上述方法中的描述。
确定过载级别模块： 检测到接入媒体网关过载后， 确定过载的级别， 如根据 CPU 占用率检测过载， 一级过载阈值为 70 %的 CPU 占用率， 二级过载阔值为 85 %的 CPU 占用率， 三级过载阈值为 95 %的 CPU占用率等， 具体如上述方法中的描述。
主叫限呼模块： 在接入媒体网关所带用户作为主叫发起呼叫时确定所述呼叫是否 为该过载级别所要保证的高优先级呼叫， 若是则上报摘机事件， 按正常的呼叫流程进行 处理； 否则直接拒绝该呼叫。 主叫限呼模块中存储有紧急呼叫数图， 该紧急呼叫数图可 以是配置在主叫 P艮呼模块中的， 也可以是在 AG系统启动时从 MGC获取的； 主叫限呼 模块可以采用保证紧急呼叫的接续、 保证高优先级端口呼叫的接续、 同时保证紧急呼叫 和高优先级端口呼叫的接续等限呼策略来限制主叫呼叫， 具体如上述方法中的描述。 本发明的接入媒体网关中也可以设置有存储模块、 确定过载级别模块和被叫限呼 模块。
存储模块如上述对接入媒体网关中存储模块的描述。
确定过载级别模块： 检测到接入媒体网关过载后， 确定过载的級别， 如上述对接 入媒体网关中确定过载级别模块的描述。 '
被叫限呼模块： 在接入媒体网关接收到其所带用户作为被叫的呼叫时确定所述呼 叫是否为该过载级别所要保证的高优先级呼叫， 若是则按正常的呼叫流程进行处理； 否 则向媒体网关控制器拒绝该呼叫。被叫限呼模块可以采用根据紧急呼叫标识或关联优先 级进行限呼、 根据用户端口的优先级属性进行限呼、 同时根据紧急呼叫标识或关联优先 级和用户端口的优先级属性等限呼策略来限制被叫呼叫。 具体如上述方法中的描述。
接入媒体网关中可以仅设置有存储模块、 确定过载级别模块和主叫限呼模块； 接 入媒体网关中也可以仅设置有存储模块、 确定过载级別模块和被叫限呼模块; 接入媒体 网关中也可以同时设置有存储模块、确定过载級别模块、主叫限呼模块和被叫限呼模块。
本领域技术人员不脱离本发明的实质和精神， 可以有多种变形方案实现本发明， 以上所述仅为本发明较佳可行的实施例而已， 并非因此局限本发明的权利范围， 凡运用 本发明说明书及附图内容所作的等效变化， 均包含于本发明的权利范围之内。

Claims

权利要求
1、 一种接入媒体网关过载控制方法， 其特征在于： 由接入媒体网关对所带用户作 为主叫的呼叫进行限呼， 包括以下步骤：
A、在接入媒体网关上设置不同的过载级别，以及每一过载级别所要保证的高优先 级呼叫；
B、 接入媒体网关在其所带用户作为主叫发起呼叫、 并检测到自身过载后， 确定过 载的级别；
C、接入媒体网关确定所述呼叫是否为该过载级别所要保证的高优先级呼叫， 若是 则上报摘机事件， 按正常的呼叫流程进行处理； 否则直接拒绝该呼叫。
2、 根据权利要求 1所述的方法， 其特征在于， 所述的步驟 C中：
接入媒体网关将摘机事件緩存， 直接对用户端口放拨号音、 收号并与紧急呼叫数 图做号码匹配以确定是否为紧急呼叫， 如果不匹配则确定该呼叫为普通呼叫， 直接对该 用户端口放忙音或通知音以释放呼叫； 如果匹配则确定该呼叫为紧急呼叫；
对于紧急呼叫， 接入媒体网关向媒体网关控制器上报摘机事件， 媒体网关控制器 收到摘机事件后向接入媒体网关下发正常数图，并通知接入媒体网关向主叫用户端口放 拨号音， 接入媒体网关将緩存的号码与收到的正常数图进行匹配， 然后按正常的呼叫流 程处理， 即： 如果匹配则将号码上报给媒体网关控制器， 如果不匹配则对该用户端口放 忙音或通知音以释放呼叫。
3、 根据权利要求 2所述的方法， 其特征在于： 所述紧急呼叫数图为： 在接入媒体 网关上配置的紧急呼叫数图， 或系统启动时从媒体网关控制器向接入媒体网关下发的紧 急呼叫数图。
4、 根据权利要求 1所述的方法， 其特征在于： 所述的高优先级呼叫为预设的高优 先级用户端口的呼叫， 且接入媒体网关上配置有用户端口的优先级； 所述的步骤 C中， 通过查询用户端口的优先级属性确定是否为高优先级用户端口的呼叫，对于高优先级用 户端口的呼叫向媒体网关控制器上报摘机事件， 按正常的呼叫流程进行处理； 否则直接 对该用户端口放忙音或通知音以释放呼叫。
5、 根据权利要求 1所述的方法， 其特征在于： 所述的高优先级呼叫同时为预设的 紧急呼叫和高优先级端口呼叫， 接入媒体网关上配置有紧急呼叫数图， 或系统启动时从 媒体网关控制器向接入媒体网关下发紧急呼叫数图，且接入媒、体网关上还配置有用户端 口的优先级； 所述的步驟 C中： 先后确定是否为高优先级端口呼叫和紧急呼叫， 若是紧 急呼叫或高优先级端口呼叫， 则向媒体网关控制器上报摘机事件， 按正常的呼叫流程进 行处理； 若两者都不是， 则直接对该用户端口放忙音或通知音以释放呼叫。
6、 根据权利要求 1、 2 、 3、 4或 5所述的方法， 其特征在于： 在接入媒体网关上 配置过载级别和过载阈值， 接入媒体网关根据预设的过载级别和过载阈值确定是否过 载， 以及过载的级别。
7、 一种接入媒体网关过载控制方法， 其特征在于： 由接入媒体网关对所带用户作 为被叫的呼叫进行限呼， 包括以下步骤：
a、 在接入媒体网关上设置不同的过载级别， 以及每一过载级别所要保证的高优先 级呼叫；
b、 接入媒体网关在接收到其所带用户作为被叫的呼叫、 并检测到自身过载后， 确 定过载的级别；
c、 确定呼叫是否为该过载级别所要保证的高优先级呼叫， 若是则按正常的呼叫流 程进行处理； 否则向媒体网关控制器拒绝该呼叫。
8、 根据权利要求 7所述方法， 其特征在于： 所述的步驟 c中， 事先由媒体网关控 制器根据被叫号码分析确定该呼叫是否是紧急呼叫， 然后在发送给接入媒体网关的消息 中设置关联的紧急呼叫标识或关联优先级；接入媒体网关检测关联的紧急呼叫标识或关 联的优先级， 如果紧急呼叫标识被设置或关联优先级被设置为高优先级， 则该呼叫是高 优先级呼叫， 按正常的呼叫流程进行处理； 如果紧急呼叫标识未被设置或关联优先级被 设置为低优先級， 则接入媒体网关在发送给媒体网关控制器的应答消息中拒绝该呼叫。
9、 根据权利要求 7所述的方法， 其特征在于： 所述的步骤 c中， 接入媒体网关根 据被叫用户的终端标识查询被叫用户端口的优先级属性，如果被叫用户端口是高优先级 端口， 则按正常的呼叫流程进行处理； 否则在发送给媒体网关控制器的应答消息中拒绝 该呼叫。
10、根据权利要求 7所述的方法， 其特征在于： 所述的步骤 c中， 事先由媒体网关 控制器根据被叫号码分析确定该呼叫是否是紧急呼叫， 然后在发送给接入媒体网关的消 息中设置关联的紧急呼叫标识或关联优先级；接入媒体网关先后根据紧急呼叫标识或关 联优先级以及用户端口的优先级属性确定是否为高优先级呼叫， 若紧急呼叫标识被设 置， 或关联优先级被设置为高优先级， 或被叫用户端口是高优先级端口， 则按正常的呼 叫流程进行处理； 否则在发送给媒体网关控制器的应答消息中拒绝该呼叫。
11、 根据权利要求 6、 7、 8、 9或 10所述的方法， 其特征在于： 若接入媒体网关 或媒体网关控制器支持 H.248.11 网关过载控制包， 则接入媒体网关在发生过载时使用 H.248.11网关过载控制包向媒体网关控制器上报接入媒体网关的过载信息， 由媒体网关 控制器根据被叫接入媒体网关的过载级别直接对到该接入媒体网关的呼叫启动相应的 限呼策略， 按比例限呼或优先保证高优先级呼叫； 如果限呼策略是优先保证高优先级呼 叫， 则媒体网关控制器直接拒绝普通呼叫， 并对高优先级呼叫设置关联的紧急呼叫标识 或将关联优先级设置为高优先级。
12、 一种接入媒体网关， 其特征在于： 接入媒体网关中设置有：
存储模块： 存储有不同的过载级别， 以及每一过载级别所要保证的高优先級呼叫； 确定过载级别模块： 检测到接入媒体网关过载后, 确定过载的级别；
主叫限呼模块： 在接入媒体网关所带用户作为主叫发起呼叫时确定所述呼叫是否 为该过载级别所要保证的高优先级呼叫， 若是则上报摘机事件， 按正常的呼叫流程进行 处理； 否则直接拒绝该呼叫。
13、 一种接入媒体网关, 其特征在于： 接入媒体网关中设置有:
存储模块： 存储有不同的过载级别， 以及每一过载级别所要保证的高优先级呼叫； 确定过载级别模块: 检测到接入媒体网关过载后， 确定过载的級别;'
被叫限呼模块： 在接入媒体网关接收到其所带用户作为被叫的呼叫时确定所述呼 叫是否为该过载级别所要保证的高优先级呼叫， 若是则按正常的呼叫流程进行处理； 否 则向媒体网关控制器拒绝该呼叫。
PCT/CN2006/001692 2005-07-27 2006-07-17 Procédé de contrôle de surcharge pour la passerelle multimédia d’accès et passerelle multimédia d’accès WO2007012259A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP06753145.9A EP1906589B1 (en) 2005-07-27 2006-07-17 An overload control method for the access media gateway and an access media gateway
US12/019,706 US8068413B2 (en) 2005-07-27 2008-01-25 Overload control method for access media gateway and corresponding access media gateway

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200510036255.4 2005-07-27
CNB2005100362554A CN100411482C (zh) 2005-07-27 2005-07-27 接入媒体网关过载控制方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/019,706 Continuation US8068413B2 (en) 2005-07-27 2008-01-25 Overload control method for access media gateway and corresponding access media gateway

Publications (1)

Publication Number Publication Date
WO2007012259A1 true WO2007012259A1 (fr) 2007-02-01

Family

ID=37298561

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/001692 WO2007012259A1 (fr) 2005-07-27 2006-07-17 Procédé de contrôle de surcharge pour la passerelle multimédia d’accès et passerelle multimédia d’accès

Country Status (5)

Country Link
US (1) US8068413B2 (zh)
EP (1) EP1906589B1 (zh)
CN (1) CN100411482C (zh)
RU (1) RU2391790C2 (zh)
WO (1) WO2007012259A1 (zh)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101232439B (zh) * 2007-01-22 2010-07-28 华为技术有限公司 过载控制方法、系统和装置
US9497229B2 (en) * 2007-05-16 2016-11-15 At&T Intellectual Property I, L.P. Methods and apparatus to manage internet protocol (IP) multimedia subsystem (IMS) network capacity
CN101583148B (zh) * 2008-05-16 2012-07-25 华为技术有限公司 一种通信设备过载处理方法及装置
CN101299714A (zh) * 2008-05-19 2008-11-05 华为技术有限公司 流控的方法、装置和系统
US9467308B2 (en) 2008-08-01 2016-10-11 At&T Intellectual Property I, L.P. Methods and apparatus to control synchronization in voice over internet protocol networks after catastrophes
US8194581B1 (en) * 2008-11-04 2012-06-05 Cellco Partnership Account holder notification for an infracting mobile station or mobile directory number (MDN)
US9432409B2 (en) * 2009-03-12 2016-08-30 At&T Intellectual Property I, L.P. Apparatus and method for managing emergency calls
CN102164358B (zh) * 2010-02-24 2014-03-05 华为技术有限公司 业务处理的方法和装置
JP5807055B2 (ja) 2010-04-22 2015-11-10 ホアウェイ・テクノロジーズ・カンパニー・リミテッド 輻輳／過負荷制御方法および装置
CN102143608B (zh) * 2010-12-29 2014-04-23 北京握奇数据系统有限公司 一种智能卡及其处理指令的方法
GB2494385B (en) 2011-08-31 2018-06-06 Metaswitch Networks Ltd Transmitting and forwarding data
US20130135998A1 (en) * 2011-11-30 2013-05-30 Nokia Siemens Networks Oy Techniques to Reduce Congestion in a Core Network and Other Elements Within a Wireless Network
WO2014037333A1 (en) 2012-09-04 2014-03-13 Nokia Siemens Networks Oy Method, apparatus, computer program product and system for identifying, managing and tracking congestion
EP2991291B1 (en) * 2013-05-13 2018-01-31 Huawei Technologies Co., Ltd. Overload control method and device
CN104092829A (zh) * 2014-07-21 2014-10-08 苏州工业园区服务外包职业学院 基于语音识别的语音呼叫方法和接入网关
CN109151147A (zh) * 2017-06-27 2019-01-04 中兴通讯股份有限公司 拨号音的产生方法及装置、终端、存储介质和处理器
CN110120913A (zh) * 2019-06-04 2019-08-13 重庆梅安森科技股份有限公司 一种多功能融合通信网关
CN111092998A (zh) * 2020-02-21 2020-05-01 深圳震有科技股份有限公司 一种电话紧急呼叫方法、系统及储存介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020159576A1 (en) * 2001-04-25 2002-10-31 Adams Richard Anthony Method for overload control in a telecommunications network and apparatus therefor
US20040165529A1 (en) * 2002-07-26 2004-08-26 Lg Electronics Inc. Overload control method of high speed data communication system
DE10341071B3 (de) * 2003-09-05 2005-03-24 Siemens Ag Verfahren zur Überlastabwehr, besonders für Call Processsing Plattformen

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5450483A (en) * 1993-11-18 1995-09-12 British Telecommunications P.L.C. Method of controlling overloads in a telecommunications network
DE19834674A1 (de) * 1998-07-31 2000-02-03 Ericsson Telefon Ab L M Verfahren, Vermittlungsstelle, Telekommunikationssystem und Mobilstation für ein vorübergehendes selektives nationales Roaming bei vorgegebenen Netzbetriebsbedingungen in einem Mobilfunk-Kommunikationssystem
US6405250B1 (en) * 1999-01-25 2002-06-11 Lucent Technologies Inc. Network management system based on passive monitoring and proactive management for formulation behavior state transition models
US6591301B1 (en) * 1999-06-07 2003-07-08 Nortel Networks Limited Methods and systems for controlling network gatekeeper message processing
DE60008483T2 (de) * 1999-11-09 2004-06-24 Nortel Networks Ltd., St. Laurent Telefondiensten in einem Kommunikationsnetzwerk
US20010038690A1 (en) * 1999-12-30 2001-11-08 Douglas Palmer Method and apparatus for management and synchronization of telephony services with video services over an HFC network
GB0016351D0 (en) * 2000-07-03 2000-08-23 Nokia Networks Oy Interaction in a communication system
GB2370448B (en) * 2001-04-28 2003-03-26 Ericsson Telefon Ab L M Cost control in a SIP based network
US20030031302A1 (en) * 2001-05-10 2003-02-13 General Instrument Corporation Extendable call agent simulator
US20080002669A1 (en) * 2001-09-14 2008-01-03 O'brien Ray Packet voice gateway
JP3853765B2 (ja) * 2002-11-08 2006-12-06 Ｎｅｃインフロンティア株式会社 パケット圧縮方式及びパケット復元方式並びにパケット圧縮方法及びパケット復元方法
US7486621B2 (en) * 2003-05-30 2009-02-03 Alcatel-Lucent Usa Inc. Method and apparatus for load sharing and overload control for packet media gateways under control of a single media gateway controller
US7420962B2 (en) * 2003-09-26 2008-09-02 Lucent Technologies Inc. Method for management of voice-over IP communications of various relative priority levels
US8730804B2 (en) * 2004-02-25 2014-05-20 British Telecommunications Public Limited Company Overload control in a communications network
CN1307850C (zh) * 2004-05-09 2007-03-28 中兴通讯股份有限公司 一种无线通信系统接纳控制方法
GB2414891B (en) * 2004-06-04 2007-11-07 Marconi Comm Ltd Communications system
US8762567B2 (en) * 2004-08-13 2014-06-24 Alcatel Lucent Adaptive permutation group method for overload control
US20060045016A1 (en) * 2004-08-31 2006-03-02 Dawdy Jay J Method and apparatus for managing packet data network loading
CN100471208C (zh) * 2005-01-02 2009-03-18 华为技术有限公司 在卡号业务中主叫用户重新发起呼叫的方法
JP4729926B2 (ja) * 2005-01-07 2011-07-20 沖電気工業株式会社 Ｉｐ電話システム
US9137330B2 (en) * 2005-03-16 2015-09-15 Alcatel Lucent Method of dynamically adjusting quality of service (QoS) targets
US7957276B2 (en) * 2005-04-28 2011-06-07 Telcordia Licensing Company, Llc Call admission control and preemption control over a secure tactical network
CN100488111C (zh) * 2005-05-15 2009-05-13 华为技术有限公司 基于终端感知业务的wimax动态qos实现方法
US20070025341A1 (en) * 2005-07-28 2007-02-01 Texas Instruments Incorporated Device, system and/or method for provisioning a device in a packet network
US20080037532A1 (en) * 2005-08-20 2008-02-14 Sykes Edward A Managing service levels on a shared network
US8315245B2 (en) * 2005-09-21 2012-11-20 At&T Intellectual Property I, L.P. Overload call control in a VoIP network
US7688724B2 (en) * 2005-12-23 2010-03-30 Avaya Inc. Call admission control for mobility-capable telecommunications terminals
FR2897492B1 (fr) * 2006-02-16 2008-09-26 Alcatel Sa Procede et dispositif de fourniture de donnees multimedia lors de l'etablissement d'un appel telephonique
US8184549B2 (en) * 2006-06-30 2012-05-22 Embarq Holdings Company, LLP System and method for selecting network egress

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020159576A1 (en) * 2001-04-25 2002-10-31 Adams Richard Anthony Method for overload control in a telecommunications network and apparatus therefor
US20040165529A1 (en) * 2002-07-26 2004-08-26 Lg Electronics Inc. Overload control method of high speed data communication system
DE10341071B3 (de) * 2003-09-05 2005-03-24 Siemens Ag Verfahren zur Überlastabwehr, besonders für Call Processsing Plattformen

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP1906589A4 *
ZHANG YUNYONG ET AL.: "Maximum running revenue based parlay gateway overload control", JOURNAL ON COMMUNICATIONS, vol. 26, no. 3, March 2005 (2005-03-01), pages 92 - 97, XP008076397 *

Also Published As

Publication number Publication date
CN100411482C (zh) 2008-08-13
EP1906589A1 (en) 2008-04-02
US20080117809A1 (en) 2008-05-22
EP1906589A4 (en) 2008-08-13
CN1859710A (zh) 2006-11-08
RU2008104414A (ru) 2009-09-10
EP1906589B1 (en) 2013-04-10
RU2391790C2 (ru) 2010-06-10
US8068413B2 (en) 2011-11-29

Similar Documents

Publication Publication Date Title
WO2007012259A1 (fr) Procédé de contrôle de surcharge pour la passerelle multimédia d’accès et passerelle multimédia d’accès
US8855613B2 (en) Monitoring mobile phone communications
WO2008040237A1 (fr) Procédé, système, terminal et serveur destinés à l'interception de courrier électronique indésirable dans le domaine de la téléphonie ip
US7395057B2 (en) System and method for reconnecting dropped cellular phone calls
US8817609B2 (en) Communications system and method for load management
EP1440586B1 (en) Method and system of managing a call in a telecommunication system
CN101170747A (zh) 中继状态调节方法和装置
US8879566B2 (en) Method for grouping terminations
WO2012146088A1 (zh) 漏话提示装置及方法
JP2008502236A (ja) 着信呼の処理方法
WO2009012667A1 (fr) Procédé et dispositif pour effectuer un contrôle d'accès d'utilisateur
GB2479651A (en) Overload handling of messages with importance ratings, possibly dependent upon messages stage in connection setup
WO2006076850A1 (fr) Procede de traitement pour la gestion de surcharge de dispositif dans un reseau de communication
GB2334176A (en) Setting-up internet calls using ISDN signalling
JP4503526B2 (ja) 呼制御方法および呼制御システム
JP2001516531A (ja) 登録プロトコル
WO2011009256A1 (zh) 分布式接入网关系统
WO2010043184A1 (zh) 一种限制主叫用户呼叫的方法、系统和装置
JP2006033004A (ja) 通信装置、呼処理制御装置および通信システム
EP1942631B1 (en) Method and system of managing a call in a telecommunication system
WO2009121256A1 (zh) 支持紧急业务的方法和系统、以及分组控制功能实体
JP3319457B2 (ja) 電話音声応答システム
JP2007235442A (ja) 無線ｉｐ電話制御システム
CN1719789A (zh) 软交换监听系统
EP2347630A1 (en) Method for grouping terminations

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 12019706

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2006753145

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2008104414

Country of ref document: RU

WWP Wipo information: published in national office

Ref document number: 2006753145

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 12019706

Country of ref document: US