WO2009115041A1 - 一种过载处理的方法及装置 - Google Patents

一种过载处理的方法及装置 Download PDF

Info

Publication number
WO2009115041A1
WO2009115041A1 PCT/CN2009/070860 CN2009070860W WO2009115041A1 WO 2009115041 A1 WO2009115041 A1 WO 2009115041A1 CN 2009070860 W CN2009070860 W CN 2009070860W WO 2009115041 A1 WO2009115041 A1 WO 2009115041A1
Authority
WO
WIPO (PCT)
Prior art keywords
mme
pool
overlapping area
access
base station
Prior art date
Application number
PCT/CN2009/070860
Other languages
English (en)
French (fr)
Inventor
郭小龙
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP09721642.8A priority Critical patent/EP2265054B1/en
Publication of WO2009115041A1 publication Critical patent/WO2009115041A1/zh

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/122—Avoiding congestion; Recovering from congestion by diverting traffic away from congested entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0247—Traffic management, e.g. flow control or congestion control based on conditions of the access network or the infrastructure network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/22—Performing reselection for specific purposes for handling the traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices

Definitions

  • the present invention relates to a technique for equalizing network resources, and in particular to a method and apparatus for overload processing. Background technique
  • the existing communication network can balance the network resources by means of load balancing, load rebalancing, and overload processing.
  • the S ⁇ system can realize the allocation of network resources through load balancing, load rebalancing, and overload processing.
  • the load balancing refers to the initial access of the user equipment UE or the UE just entering a certain resource pool (Pool).
  • the pool means that the user equipment UE does not need to change the serving MME (Mobility Management Entity).
  • the RAN node of the radio access network has a many-to-many connection with the MME in the pool of the MME resource pool, and the RAN node of the radio access network cannot find the MME information accessed by the UE, and cannot find the MME code carried by the UE (MMEC).
  • the radio access network (RAN) node selects a most suitable core network node for the UE, such as the lightest load MME; load rebalance refers to operation Maintenance, such as O&M (Opera and Management), balance the load between core network nodes, such as MME, and offload some UEs from one core network node to other core network nodes.
  • Overload processing refers to When a core network node, such as an MME, is overloaded and exceeds a certain threshold, the core network node needs to indicate that part of the RAN node is prohibited from continuing to access the core network node to prevent it from continuing to overload until it collapses.
  • an MME is overloaded, if only overload processing is performed, only the MME can be guaranteed. No further load increase, but the load will not be significantly reduced.
  • the load of the MME will be in an overload phase for a long time, and the load can be slowly reduced by some user equipment UEs releasing the connection or moving to other pools, and If the MME is overloaded for a long time, and the MME of the entire pool is overloaded, the UE in the pool will not be able to access the network for a long time, causing the user satisfaction to decrease, and the network cannot be overloaded. Make new communications.
  • the inventors have found that the existing overload processing can only prevent further load from being intensified by preventing new users from accessing, and cannot quickly reduce the load of the overloaded device, and cannot balance network resources in time. Therefore, the probability that the user is denied by the network or cannot access the network is large, which affects the user experience.
  • the embodiments of the present invention provide a method and an apparatus for overload processing.
  • the solution provided by the embodiment of the present invention can quickly reduce the load of an overloaded device and balance network resources in time.
  • a method of overload processing comprising:
  • the user equipment UE in the overlapping area is transferred to the resource pool that overlaps with the resource pool in which the overloaded core network node is located.
  • a method of overload processing comprising:
  • a mobility management entity MME comprising:
  • An information obtaining module configured to acquire load information of a Pool that overlaps with a Pool in which the MME is located;
  • the UE transfer module is configured to transfer, according to the load information acquired by the information acquiring module, the UE that needs to access the MME to a pool that is overlapped with the pool to which the MME belongs.
  • a base station comprising:
  • the load information receiving module is configured to receive the load information sent by the mobility management entity MME, and the MME selection module is configured to select, for the UE, the MME that can be accessed according to the load information received by the load information receiving module.
  • the embodiment of the present invention can quickly reduce the load of the overloaded device, reduce the possibility that the user is denied or unable to access the network, and can allow more users to access. , increased user satisfaction.
  • FIG. 1 is a connection diagram of an MME and an eNodeB in a SAE system according to an embodiment of the present invention
  • FIG. 2 is a flow chart of information exchange between Poo 1 in the S AE system according to an embodiment of the present invention.
  • the method and device for overload processing provided by the embodiments of the present invention can reasonably balance system resources and reduce the probability that a user is denied or cannot access the network by the network.
  • the present invention will now be described in further detail by way of specific embodiments.
  • the load balancing mechanism in the network When the load balancing mechanism in the network is better, the load of each node in the network is relatively balanced. If one of the nodes is overloaded, the other nodes may also be overloaded or partially overloaded. At this time, if it is still in the overloaded E A simple de-loading operation in Poo l, that is, load rebalancing, is likely to cause the MME to be fully overloaded until the system crashes.
  • the network load balancing mechanism is better, for example, the network notifies the RAN node of its load information in real time, so that the RAN node always selects the core network device with the lightest load. At this time, if an MME in the Poo is overloaded, Other MMEs may also be overloaded, or mostly overloaded.
  • the UE that accesses the overloaded MME in the overlapping area is transferred to another Pool that has the overlapping area i or the pool to which the overloaded MME belongs, allowing the UE to access.
  • the MME in the MME Pool is overloaded, if the MME obtains the load information of other pools that have an overlapping area with the pool to which the MME belongs, and the other pools are not overloaded to allow the UE to access, the MME that is overloaded may be in the node.
  • the user is transferred to another pool with an overlapping area. For example, as shown in FIG. 1 , if there is a Pool 2 in the overlapping area with the Pool 1 and the Pool 2 is not overloaded, the MME 1 may transfer the user in the overlapping area of the node to the Pool 2 or transfer the user of the eNodeB 2 to the Pool 2 .
  • the load of the MME 2 can be greatly reduced, and the load of the Poolll can be further reduced.
  • a MME may take the following operations to implement the operation of the MME from the overloaded MME to the non-overloaded pool in the overlapping area of the pool to which the overloaded MME belongs:
  • the Pool that the MME belongs to the Pool has the load sending query message Load Query, and the Pool that has the overlapping area of the Pool to which the overloaded MME belongs has returned the load report Load Report, and reports its own load status. If the pool with the owning pool has the overlapping area i or the pool is not overloaded.
  • the MME sends a load start message Offload Start to the pool that has the overlapping area i or the pool to which the owning pool belongs, and transfers the part or all of the UE that accesses the overloaded MME to the non-overloaded pool with the overlapping area of the owning pool. Further, when an MME in the pool is overloaded, the MME may also actively send a notification to the pool in the Overlapping area. It is required that the pool in the Overlapping area does not perform the de-loading operation on the pool; or when the MME is overloaded, the load information is periodically obtained from the Pool in the Overlapping area.
  • the MME may load the UE in the overlapping area to the existing Overlapping area Pool. If the pool in the Overlapping area is also overloaded, the MME stops loading the UE to the pool. When all the Overlapping areas are overloaded, the OLT stops.
  • the MME performs an overload processing overload handling operation, that is, denying access to all UEs (except emergency services).
  • an MME is overloaded, and after the load information is obtained from the pool in the Overlapping area, the operation of the unloaded UE to the pool in the Overlapping area is performed. If the pool in the Overlapping area is overloaded, the other pools need to be notified to stop loading the UE to the pool. Operation.
  • MME1 in the Pooll is overloaded, and the MME load of the Pool2 in the overlapping area is queried. If the MME load of the Pool2 is sufficiently small, the MME1 can perform the operation of unloading the UE to the Pool2, and the MME of the Pool2 also If an overload occurs, the MME1 needs to be notified to stop performing the operation of unloading the UE to the Pool2. In addition, when the load of MME1 is small enough, it also needs to send a load-stop message Offload Stop to Pool2, so that Pool2 knows that no other pools are going to load UEs. When Pool2 is also overloaded, it can load UEs to other pools. Before MME1 does not send Offload Stop to MME2, MME2 cannot send query load to Pool1 and perform offload UE to Pooll operation because Pooll is still overloaded.
  • the embodiment of the present invention provides a method for transferring a user who wants to access an overloaded MME in a pool to a Pool having an overlapping area with a pool to which the overloaded MME belongs:
  • the MME can obtain the load information of the MME with the overlapping pool. As described above, the MME that has the overlapping area with the Pool to which the overloaded MME belongs can allow sufficient users to access the MME.
  • the overloaded MME may To:
  • the overload start message used to reject the UE access when the overload processing is not sent The Overload Start message is sent to the eNodeB in the overlapping area i or the UE in the overlapping area i or the originating Attach/TAU. Specifically, the UE sends an Attach/TAU to the overloaded MME through the eNodeB in the overlapping area, and the MME returns an Attach Accept message or a TAU Accept message to the UE, where the special indication or special MMEC (MME Code), or other Pool is carried.
  • MME of the MME, or the MME initiates the release of the connection request, and carries a special reason. After receiving the connection, the UE will initiate the TAU again after the connection is released.
  • the RRC part of the TAU message carries the special indication or the special MMEC or the field carrying the MME information is empty.
  • the eNodeB considers it as the UE that just enters the pool and selects the MME of the other pool. Because the MME load of the pool exceeds the threshold, these overloaded MMEs will not be selected for the new UE. After the UE accesses other MMEs, the UE is overloaded. The MME obtains the context and does not interrupt the service.
  • the field that carries the destination MME indication or carries the MME information is empty, and the new MME is selected for the UE.
  • the new MME can find the old MME by using the global unique temporary identifier GUTI (Global Unique Temporary Identity) carried by the UE. And get the context.
  • GUTI Global Unique Temporary Identity
  • the MME may send an Overload Start message or other message, such as a new message, Overload Notification, indicating that these eNodeBs refuse to access the MME.
  • the UE is required to perform a new TAU.
  • the new TAU carries the indication or the field carrying the MME information in the RRC (Radio Resource Control) section is empty, and the eNodeB treats it as the newly entered UE, and selects the overloaded MME.
  • the owning pool has the MME of the Pool in the overlapping area.
  • the UE can be transferred to another Pool by re-initiating the location area to update the Re-TAU or handover (HO, Handover).
  • Re-TAU method Send a special message or indication to the UE, request the UE to release the connection and immediately initiate the TAU, such as sending a Re-TAU Indication message to the UE, or carrying the parameter "Re-TAU" in the existing message, and the TAU sent by the UE
  • the RRC part of the message carrying the special indication or the MMEC of the non-overloaded pool or the field carrying the MME information is empty, and the eNodeB regards it as the UE that newly enters the pool, and selects another MME with the idle resource pool. For example, load balancing can be utilized to select a suitable MME for the UE in the overlapping area.
  • the method for the UE to transfer to the pool with the idle resource and the pool to which the overloaded MME belongs has the overlapping area is as follows:
  • the MME Relocation operation is directly performed without releasing the original wireless connection of the UE, and the MME or the eNodeB selects the target MME for the UE.
  • the UE in the active state of the overlapping area and the UE that initiates the Attach/TAU are preferentially transferred to the UE in the base station closest to the pool according to the proximity of the pool to which the overlapping pool of the resource pool in which the overloaded MME is located overlaps. .
  • the UEs under the eNodeB4 are first transferred, so that these UEs have a smaller probability of entering the overloaded pool again, and the Pool may no longer be overloaded after the users are transferred, so there is no need to continue to transfer other users. If the UE is still in an overload state, the UE of the eNodeB3 or even the eNodeB2 can be transferred.
  • the UE that is definitely in the overlapping area may be paged first, such as the UE whose location TA list TA list is in the overlapping area, and then the UE that may be in the overlapping area, such as its partial TA list.
  • the TA in the area belongs to the overlapping area, and only paging in the overlapping area during paging.
  • the final load is calculated according to the weight, but if a pool MME is overloaded, then the weighting The calculated final result still cannot select the MME of the overload; or, when the MME is in overload, the MME sends an overload handling or other message to the eNodeB in the overlapping area i or the eNodeB to indicate that the MME is overloaded, and these eNodeBs select the newly entered UE to other Pool does not need to access this pool.
  • the specific method can be:
  • the load value of the MME gradually increases;
  • the MME sends an Overload Start or other message to the eNodeB in the overlapping area to indicate that the MME has an overload, and these eNodeBs will enter the new one.
  • the UE selects other pools instead of accessing the pool, and prepares for load balancing when the initial access is made.
  • the MME does not send a message, and the eNodeB selects the MME according to the load information of the MME and the weighting algorithm, but the probability of selecting the MME is extremely low;
  • the MME When the MME reaches the threshold 2, the MME starts to transfer the UE in the Idle state and the Active state in the overlapping area, and reduces the load of the MME.
  • the MME may gradually shift from the eNodeB whose distance is closer to the Pool in which the Pool to which the overloaded MME belongs has the overlapping area. Until the MME load is reduced to a certain extent or the UEs under the eNodeB of all overlapping areas are transferred.
  • the Idle state UE may be transferred first; and in order to reduce the load of the MME as soon as possible, the UE in the active state may be transferred first; the specific transfer mode may be defined by the operator.
  • the MME When the MME reaches the threshold 3, the MME sends an Overload Start message to the other eNodeBs or all eNodeBs, requesting the eNodeBs to reject the new access to the MME. At this time, the MME has a high load, and accessing the new UE may cause the MME to fail. The access of the UE may be rejected, and the user experience is deteriorated. Alternatively, when the MME transfers the UEs in the Overlapping area, or when the Pool with the overlapping area also overloads, the overloaded MME sends an Overload Start message to the eNodeB to trigger its denial of access by the UE to the MME (except emergency services). ).
  • the eNodeB may select the MME through load balancing, and different eNodeBs may preferentially select different MMEs. For example, as shown in FIG. 1, for example, when the UE accesses the eNodeB 2, since the eNodeB 2 is close to the MME Pool1, if the load of the MME in the MME Pool1 and the MME Pool2 is the same, the eNodeB 2 will preferentially select the MME Pool1. MME, because this can reduce MME migration,
  • MME Relocation is the probability of changing the MME. Taking FIG. 1 as an example, when the eNodeB 2 selects the MME in the MME Pool1, such as MME1, the MME Relocation will occur after the UE moves to the eNodeB 5, and the UE does not occur in the eNodeB 2 to the eNodeB4. If the eNodeB 2 selects the MME Pool2, In the MME, the MME Relocation occurs after the UE moves from the eNodeB 2 to the eNodeB 1. Since the eNodeB 1 and the MME in the MME Pool 2 are not connected, the MME must be replaced.
  • the weighting factor of eNodeB 3 for both pools may be the same, because the probability of MME Relocation is the same; the weighting factor of eNodeB 4 for two pools is 70% for Poolll; 100% for Pool2, and then according to the calculated final weighting factor Select MME. Even different eNodeBs in the same Pool can set different weighting factors for different MMEs according to their own locations or distances or connections from different MMEs in the pool.
  • the eNodeB can preferentially select the MME with a small MME migration probability.
  • the UE accessing the overlapping area may select the MME in another pool, although the probability of the MME Relocation is changed. Big.
  • the embodiment of the present invention further provides a solution to the situation that sometimes an MME is overloaded and other MMEs in the pool are not overloaded.
  • the load balancing method of the Load Balancing method cannot completely select the MME according to the load, or the device board of an MME fails.
  • the load of the MME becomes overloaded, and other MMEs are still normal.
  • the eNodeB refuses to access the device.
  • the user of the MME causes a situation in which the user satisfaction is degraded.
  • the embodiment of the present invention further proposes another solution:
  • the MME When an MME is overloaded, the MME sends an Overload Start message of the overload processing to all eNodeBs connected to it, and the eNodeB parses the MME that sends the Overload Start message.
  • the eNodeB does not receive the Overload Start message sent by all MMEs, or When the eNodeB receives an Overload Start message sent by the MME that is lower than a certain threshold, or the eNodeB receives an Overload Start message sent by the MME that is lower than a certain percentage, it considers that those that have not sent the Overload Start message or have previously sent Overload Start The MME that sent the Overload Stop message to the eNodeB is not overloaded. For example, a proportional threshold can also be set.
  • the basis of the threshold is that the MME that sends the Overload Start message to the eNodeB occupies all the MMEs connected to the eNodeB.
  • the ratio of the threshold is [0,1].
  • the MME that selects not to send the Overload Start message may consider the load balancing principle.
  • the eNodeB receives the UE access request to access the overloaded MME.
  • the eNodeB sends a reject message, which requires the UE to re-initiate the access, such as a TAU request, which needs to carry a special indication or an un-overloaded MME code in the RRC part, so that the eNodeB regards the access as a new access.
  • the eNodeB directly transfers the UE's access to the MMEs that do not send the Overload Start message.
  • the UE may acquire the UE context from the overloaded MME to ensure service continuity; or may not acquire the UE context, and the service restarts, such as overloading the MME.
  • the load is extremely high and cannot handle signaling situations.
  • the eNodeB When the eNodeB receives the Overload Start message sent by all the MMEs, or the eNodeB receives an Overload Start message sent by the MME that is higher than a certain percentage or threshold, it is considered that all the MMEs of the pool are overloaded, so that the eNodeB will be connected.
  • the incoming UE rejects (unless the UE that initiated the emergency service).
  • the message sent by all the MMEs in the pool will reject the UE access.
  • the eNodeB is the eNodeB in the overlapping area, the message sent by all the MMEs in the connected pool will be rejected.
  • the base station When there is no MME that allows the UE to access or the MME that allows the UE to access does not meet the threshold requirement, for example, when the number of MMEs is less than a certain threshold, the base station will reject the access request of the UE, and the denied access request of the UE may include the following.
  • Service request for non-emergency service service request of type paging response; RRC connection message containing non-access stratum message, such as tracking area location update request or attach request.
  • the MME may be considered to be in an overload overload state, and the MME sends an Overload Start message within a period of time; or the underlying protocol notifies the eNodeB that the MME link is faulty, such as
  • the heartbeat indication between the MME and the eNodeB indicates that the MME link is faulty, and the eNodeB also considers that the MME is overloaded and understands that the MME sends an Overload Start message to it (at a certain time), so the MME may still be described above. An overload occurs, but other MMEs of the same pool are not overloaded.
  • an MME to be overloaded may be used in combination with a situation in which a certain MME's MME is overloaded or partially overloaded.
  • the access overload may be first transferred. If the MME of the MME is not overloaded with the MME, the MME of the MME that has accessed the overload does not continue to overlap with the pool to which it belongs. In the pool of the zone.
  • the MME can determine that the UE also supports WiMAX and the UE is in the LTE and WiMAX common coverage area, the MME can request the UE to transfer.
  • RATs Radio Access Technology, wireless access
  • the method includes: when the UE is in an Active state, the MME initiates a handover request, and the UE is required to switch to WiMAX, or the MME sends signaling to the UE, requesting the UE to re-register or update the location area in the WiMAX.
  • the MME pages the UE, and after the UE transitions to Active, the UE processes according to the Active state.
  • the MME may also send an indication to the eNodeB of the overlapping area. After the UE accesses the eNodeBs, the eNodeB directly sends a UE indication, requesting the UE to reselect other RATs of the local RAT for access.
  • the embodiments of the present invention also provide related devices and systems:
  • the embodiment of the present invention provides a mobility management entity MME, where the MME includes an information acquisition module, and a UE transfer module, where the information acquisition module is configured to acquire the load information of the pool that overlaps with the pool to which the MME belongs.
  • the MME uses the UE to transfer the UE that needs to access the MME to the pool in which the pool to which the MME belongs overlaps.
  • the method for the UE to transfer the UE to the UE is the same as the solution provided by the foregoing method embodiment, and details are not described herein again.
  • an embodiment of the present invention further provides a base station, where the base station includes a load information receiving module, and an MME selection module.
  • the load information receiving module is configured to receive the load information sent by the MME entity.
  • the load information may include an overload start message, an unloading message offload, a load stop message, an offload stop, and the like.
  • the load information receiving module After receiving the load information, the load information receiving module notifies the load information.
  • the MME selects a module.
  • the MME selection module is configured to select a suitable MME according to the notification message sent by the load information receiving module.
  • the specific processing method is consistent with the solution provided by the foregoing method embodiment, and details are not described herein again.
  • the embodiment of the present invention also provides a network system composed of the foregoing MME and a base station, where the information exchange between the base station and the MME is the same as the method between the MME and the eNodeB in the SAE system in the method embodiment. The information interaction is not mentioned here.
  • the load of the overloaded device can be quickly reduced, the network resources are balanced, and the possibility that the user is denied or unable to access the network by the network is reduced, and the satisfaction of the user experience is improved.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

一种过载处理的方法及装置 本申请要求了 2008年 3月 21 日提交的， 申请号为 200810066200.1 , 发 明名称为 "一种过载处理的方法及装置" 的中国申请的优先权， 其全部内容 通过引用结合在本申请中。
技术领域
本发明涉及均衡网絡资源的技术， 具体涉及一种过载处理的方法及装置。 背景技术
在现有的用户设备 UE接入网絡或者用户使用网絡的过程中，由于 UE用户 的大量存在， 对网絡资源进行合理分配十分重要。 现有通信网絡可以通过负 载平衡， 负载再平衡， 过载处理等方式对网絡资源进行均衡分配。
以 S AE ( System Architectural Evolution , 系统架构演进 ) 系统为例， S ΑΕ 系统可以通过负载平衡、 负载再平衡、 过载处理等多种方式实现网絡资源的 分配。其中， 负载平衡是指用户设备 UE初始接入或 UE刚进入某资源池（Pool ) 时， 此处 Pool指， 用户设备 UE在其中移动不需要改变服务 MME ( Mobility Management Entity, 移动性管理实体） 的区域。 例如无线接入网絡 RAN节点 与该 MME资源池 Pool中的 MME存在多对多连接 ,无线接入网絡 RAN节点找不 到该 UE接入过的 MME信息， 找不到 UE携带的 MME码（MMEC, MME Code ) 对应的接入过的核心网节点， 则无线接入网 RAN ( Radio Access Network ) 节 点为 UE选择一个最合适的核心网节点， 如负载最轻的 MME; 负载再平衡指由 于操作维护， 如 O&M ( Operate and Management )等原因， 在核心网节点， 如 MME之间平衡负载， 将某些 UE从一个核心网节点去负载（offload ) , 转移到 其它核心网节点中； 过载处理指当一个核心网节点， 如 MME, 出现负载过重， 超过一定门限时， 核心网节点需要指示部分 RAN节点禁止继续接入该核心网 节点， 防止其继续过载直至崩溃。
如果某 MME发生过载， 如果只执行过载处理， 那么仅能够保证该 MME 不会进一步负载增加， 但是不会显著的减少负载， 该 MME的负载会长时间处 于过载阶段， 只能通过某些用户设备 UE释放连接或移动到其它 Pool来慢慢减 少负载， 而且由于 MME的长时间处于过载， eNodeB将长时间不能允许 UE接 入该 MME, 并且由于实际上整个 Pool的 MME都处于过载， 该 Pool内的 UE将长 时间无法接入网絡， 造成用户满意度下降， 网絡无法进行新的通信。
通过以 SAE系统为例描述的现有技术，发明人发现，现有的过载处理只能 通过阻止新用户接入防止进一步负载加剧， 而无法快速降低过载设备的负载， 并且无法及时均衡网絡资源， 因此导致用户被网絡拒绝或不能接入网絡的概 率较大， 影响用户体验。
发明内容
本发明实施例提供了过载处理的方法及装置， 釆用本发明实施例提供的 解决方案， 可以快速降低过载设备的负载， 及时均衡网絡资源。
本发明实施例的目的是通过以下技术方案实现的：
一种过载处理的方法， 包括：
当核心网节点过载时，将处于重叠区域的用户设备 UE转移到与所述过 载核心网节点所处的资源池有重叠区域的资源池。
一种过载处理的方法， 包括：
获取资源池中的核心网节点的负载信息；
解析所述负载信息， 将接入所述负载信息中指示的过载核心网节点的 用户设备 UE转移到所述资源池中允许 UE接入的核心网节点中。
一种移动性管理实体 MME, 包括：
信息获取模块， 用于获取与所述 MME 所处的 Pool 有重叠区域 overlapping的 Pool的负载信息；
UE转移模块， 用于根据所述信息获取模块获取的负载信息， 将要求接入 所述 MME的 UE转移到与所述 MME所属的 Pool有重叠区域 overlapping的 Pool 中。 一种基站， 包括：
负载信息接收模块， 用于接收移动性管理实体 MME发送的负载信息； MME选择模块，用于根据负载信息接收模块接收的负载信息为 UE选择可 以接入的 MME。
从本发明实施例提供的以上技术方案可以看出， 由于本发明实施例可以 快速降低过载设备的负载， 降低了用户被网絡拒绝或不能接入网絡的可能性， 并且可以允许更多用户接入， 提升了用户的满意度。
附图说明
图 1为本发明实施例 SAE系统中 MME和 eNodeB的连接图；
图 2为本发明实施例 S AE系统中 Poo 1间信息交互流程图。
具体实施方式
本发明实施例提供的过载处理的方法及装置， 可以合理均衡系统资源， 降低用户被网絡拒绝或不能接入网絡的概率。 以下通过各具体实施例， 对本 发明进一步详细说明。
当网絡中的负载平衡机制较好时， 网絡中的各节点负载相对比较均衡， 如果其中某节点过载， 则其他节点可能也均已过载， 或部分过载， 此时如果 仍然在过载丽 E所属的 Poo l内进行简单的去负载操作， 即负载再平衡， 则容易 导致 MME全面过载， 直至系统崩溃。 以 SAE系统为例， 如果网絡负载平衡机制 较好 , 如网絡实时通知 RAN节点其负载信息使得 RAN节点总是选择负载最轻的 核心网设备， 此时， 如果 Poo l中的某 MME过载， 则其他 MME可能也都过载， 或 者大部分过载。
在 SAE网絡中， 因为有 Flex的设计， 即在一个 Pool内， 有多个 CN ( Core Network, 核心网） 节点， 如 MME, 与 Pool内的所有 RAN节点， 如 eNodeB, 相连。 因此以 MME和 eNodeB为例， 在 Pool中的某 MME过载的情况下， 如果存 在 overlapping区域， overlapping区域即指，存在一个或若干个 eNodeB连接到两 个或多个 Pool, 如图 1所示， 以其中 eNodeB2为例， eNodeB2同时连接到 Pooll 和 Pool2 , 则 TA2称为 overlapping区域， 即属于多个 Pool的区域或与多个 Pool 有连接的区域， 在存在 overlapping的情况下， 可以进行如下过载处理：
将处于 overlapping区域的接入过载 MME的 UE转移到另一个与过载 MME 所属的 Pool有 overlapping区 i或的、 允许 UE接入的 Pool。
当 MME Pool中的某 MME发生过载， 那么意味着该 Pool内的其它 MME也 发生了过载， 不能简单地去负载（Offload ) , 即负载再平衡， 该 MME中的 UE, 否则这些 UE可能转移到该 Pool 1内其它过载的 MME , 而与过载 MME所属的 Pool有 overlapping区域的 Pool的 MME则不一定过载， 因此， 可以将处于 overlapping区域的用户转移到与过载 MME所属的 Pool有 overlapping区域的 Pool中的 MME, 这样， 能够大幅降低该 MME的负载。 当 MME Pool中的 MME 发生过载，如果 MME获取到与其所属 Pool有 overlapping区域的其他 Pool的负载 信息， 该其他 Pool未过载允许 UE接入， 则发生过载的 MME可以将本节点内的 处于 overlapping的用户转移到有 overlapping区域的其他 Pool中。 例如， 如图 1 所示， 与 Pool 1存在 overlapping区域的 Pool2, 且 Pool2未过载， 则 MME1可以将 本节点内的处于 overlapping区域的用户转移到 Pool2中，或者将 eNodeB2的用户 转移到 Pool2中的 MME3上， 这样， 能够大幅降低 MME2的负载， 进一步降低 Pooll的负载。
所属技术领域的技术人员可以釆取如下具体实施例操作， 以实现将 UE从 过载的 MME上转移到未过载的与过载 MME所属 Pool有 overlapping区域的 Pool 中： MME发生过载， 该 MME向与该 MME所属 Pool有 overlapping区域的 Pool 发送负载查询消息 Load Query,与过载 MME所属 Pool有 overlapping区域的 Pool 返回负载报告 Load Report , 报告自 己的负载状况， 如果与所属 Pool有 overlapping区 i或的 Pool未过载， 则 MME给该与所属 Pool有 overlapping区 i或的 Pool发送去负载启动消息 Offload Start,将接入过载的 MME的 UE部分或全部转 移到该未过载的与所属 Pool有 overlapping区域的 Pool上。 进一步地， 当 Pool中 的某 MME过载时， MME也可以主动向存在 Overlapping区域的 Pool发送通知， 要求存在 Overlapping区域的 Pool不要向本 Pool执行去负载操作； 或者当某 MME过载时， 周期性的向存在 Overlapping区域的 Pool获取负载信息， 当存在 Overlapping区域的 Pool允许新的 UE接入， 即未出现过载时， MME可以将 overlapping区域的 UE去负载到存在 Overlapping区域 Pool , 一旦存在 Overlapping区域的 Pool也出现过载， 则 MME停止去负载 UE到该 Pool, 当所有 存在 Overlapping区域 Pool都出现过载， 那么 MME执行过载处理 overload handling操作， 即拒绝所有 UE的接入（除紧急业务） 。 当一个 MME过载， 向 存在 Overlapping区域的 Pool获取负载信息后执行去负载 UE到存在 Overlapping 区域的 Pool的操作时， 一旦存在 Overlapping区域的 Pool出现过载， 则需要通知 其他 Pool停止去负载 UE到本 Pool的操作。
如图 2所示， 例如 Pooll中的 MME1出现过载， 查询存在 overlapping区域的 Pool2的 MME负载情况， 如果 Pool2的 MME负载足够小 , MME1就可执行去负 载 UE到 Pool2的操作 , 当 Pool2的 MME也出现过载 , 需要通知 MME1停止执行 去负载 UE到 Pool2的操作。 此外， 当 MME1的负载足够小， 也需要发送去负载 停止消息 Offload Stop给 Pool2 , 这样 Pool2了解没有其他 Pool向其去负载 UE , 当 Pool2也出现过载 , 就可以向其他 Pool去负载 UE。 在 MME1没有给 MME2发 送 Offload Stop之前， MME2不能向 Pooll发送查询负载和执行 offload UE到 Pooll的操作， 因为 Pooll仍然过载。
另外， 本发明实施例根据 UE所处的不同状态， 提供了将要接入某 Pool中 的过载 MME的用户转移到与过载 MME所属的 Pool具有 overlapping区域的 Pool 的方法：
具体操作为：
当 MME发生过载， 该 MME可以获取具有 overlapping Pool的 MME的负载 信息， 如上文所述， 此处不再赘述， 如果与过载 MME所属的 Pool具有 overlapping区域的 Pool的 MME能够允许足够用户接入：
A. 对于正在进行位置区域更新 TAU或附着 Attach的 UE, 过载的 MME可 以：
( 1 ) 不发送过载处理时用于拒绝 UE接入的过载启动消息 Overload Start 消息给处于 overlapping区 i或的 eNodeB , 转移处于 overlapping区 i或的发起 Attach/TAU的 UE。 具体包括： 这些 UE通过 overlapping区域的 eNodeB发起 Attach/TAU到过载的 MME, MME回复 Attach Accept消息或 TAU Accept消息到 UE, 其中携带特殊指示或特殊 MMEC ( MME Code, MME码）， 或者其他 Pool 的 MME的 MMEC, 或者， MME发起释放连接请求， 携带一个特殊的原因， UE收到后释放连接后会再次发起 TAU, TAU消息的 RRC部分携带特殊指示或 特殊 MMEC或者携带 MME信息的字段为空 , eNodeB将其看作刚进入 Pool的 UE, 为 UE选择其他 Pool的 MME, 因为本 Pool的 MME负载超过门限， 所以这 些过载的 MME不会为新 UE选择， UE接入其他 MME后， 向过载的 MME获取上 下文， 不会中断业务。
或者：
( 2 )发送 Overload Start或其他消息， 如新消息， Overload Notification, 给 overlapping区域的 eNodeB , 但前述各消息与普通的拒绝 UE接入的 overload Start消息不同， 这些消息不会直接拒绝 UE的接入， 而是将要接入的 UE直接转 移到新的 MME, 该新的 MME所属的 Pool为未过载的 Pool, 或者由 eNodeB发起 UE重新接入， 并在再次接入的消息中携带特殊指示， 例如该特殊指示可以是 参数" Re-TAU Indication", 或 cause原因值为" overload"等。 除特殊指示外， 还 可携带目的 MME指示或者携带 MME信息的字段为空， 为 UE选择新的 MME, 新的 MME可以通过 UE携带的全球唯一临时标识 GUTI ( Global Unique Temporary Identity )找到旧的 MME并获取上下文。
或者：
( 3 ) 向 overlapping区域的 eNodeB发送消息指示这些 eNodeB拒绝接入该 MME的 UE并要求其进行新的 TAU。 例如 MME可以发送 Overload Start消息或 其他消息，如新消息， Overload Notification,指示这些 eNodeB拒绝接入该 MME 的 UE并要求其进行新的 TAU, 新的 TAU在 RRC ( Radio Resource Control, 无 线资源控制）部分携带指示或者携带 MME信息的字段为空， eNodeB将其当作 新进入的 UE , 选择与过载 MME所属的 Pool具有 overlapping区域的 Pool的 MME。
B. 对于处于 overlapping区域的 Active状态的 UE: 可通过重新发起位置区 更新 Re-TAU或切换 ( HO, Handover ) 的方法将 UE转移到其他 Pool。
具体包括：
Re-TAU方法： 给 UE发送特殊消息或指示， 要求 UE释放连接并马上发起 TAU , 如发送 Re-TAU Indication消息给 UE , 或在现有消息中携带参数 "Re-TAU" , UE发送的 TAU消息中的 RRC部分携带特殊指示或非过载 Pool的 MMEC或者携带 MME信息的字段为空， eNodeB将其看作新进入 Pool的 UE,为 其选择另一具有空闲资源 Pool的 MME。 例如可以利用负载平衡， 为处于 overlapping区域的 UE选取合适的 MME。
通过切换实现 UE转移到具有空闲资源的与过载 MME所属的 Pool具有 overlapping区域的 Pool的方法为： 不释放 UE原有无线连接， 直接进行 MME Relocation操作， 由 MME或 eNodeB为 UE选择目标 MME。
C. 对处于 overlapping区域的 Active状态的 UE和发起 Attach/TAU的 UE,依 据与过载 MME所处的资源池 Pool有重叠区域 overlapping的 Pool的靠近程 度， 优先转移距离该 Pool最近的基站中的 UE。 例如， 如图 1所示， 先转移 eNodeB4下的 UE, 这样这些 UE有较小概率再次进入过载的 Pool, 而且可能转 移完这些用户后 Pool将不再过载了， 因此就没有必要继续转移其他用户了，如 果仍处于过载状态， 则可以再转移 eNodeB3乃至 eNodeB2的 UE。
D. 对于处于 overlapping区域的空闲 Idle状态的 UE: 先对其进行寻呼， 使 其转为激活 Active状态后， 按照 Active状态来处理。 对这些 UE来说， 可以先寻 呼肯定在 overlapping区域的 UE , 如其位置区列表 TA list中的 TA都在 overlapping区域的 UE, 再寻呼可能在 overlapping区域的 UE, 如其部分 TA list 中的 TA属于 overlapping区域， 寻呼时只在 overlapping区域寻呼。
E. 进一步， 对于新进入的处于 overlapping区域的 UE, 即 eNodeB无法为 此 UE找到对应旧节点， 按照负载平衡 load balancing原则， 按照加权算出最终 的负载， 但如果一个 Pool的 MME处于 overload, 那么加权算出的最后结果仍然 不能选择这些 overload的 MME; 或者， 当 MME处于 overload, MME向处于 overlapping区 i或的 eNodeB发送 overload handling或其他消息指示 MME出现 overload,请这些 eNodeB将新进入的 UE选择到其他 Pool而不要接入本 Pool。 具 体方法可以是：
设置 MME三个 overload门限 1 , 2, 3; MME的负载值逐渐升高； 当 MME达到门限 1 , MME向处于 overlapping区域的 eNodeB发送 Overload Start或其他消息指示 MME出现 overload, 请这些 eNodeB将新进入的 UE选择到 其他 Pool而不要接入本 Pool, 做到初始接入时即对负载平衡分配有所准备。 或 者 MME不发送消息 , 而 eNodeB会根据 MME的负载信息和加权算法来选择 MME, 但选择到该 MME的概率极低；
当 MME达到门限 2, MME开始转移处于 overlapping区域的处于 Idle状态和 Active状态的 UE , 将 MME的负载降低 , MME可能从距离与过载 MME所属的 Pool具有 overlapping区域的 Pool较近的 eNodeB开始逐渐转移， 直到 MME负载 降低到一定程度或者将所有 overlapping区域的 eNodeB下的 UE转移完。 为了减 少用户影响， 可能先转移 Idle状态 UE; 而为了尽快减少 MME的负载， 也可能 先转移处于 Active状态的 UE; 具体转移方式可由运营商定义。
当 MME达到门限 3 , MME发送 Overload Start消息给其他 eNodeB或所有 eNodeB, 请求这些 eNodeB拒绝新的接入到该 MME, 这时 MME的负载很高， 再接入新的 UE可能导致 MME瘫痪。 UE的接入可能被拒， 用户感受变差。 或 者， 当 MME将 Overlapping区域内的 UE都转移完， 或者当具有 overlapping区域 的 Pool也发生过载时，过载的 MME将发送 Overload Start 消息给 eNodeB触发其 拒绝 UE到该 MME的接入（除紧急业务） 。 在釆用前文所述的各实施例时， 如果 UE是初始接入， 则 eNodeB可以通过 负载平衡（load balancing )选择 MME, 而不同 eNodeB可能优先选择不同的 MME。 仍以图 1所示为例， 如当 UE接入 eNodeB 2, 由于 eNodeB 2靠近 MME Pooll , 这样如果在 MME Pooll和 MME Pool2内的 MME的负载相同的情况下 , eNodeB 2将优先选择 MME Pooll内的 MME, 因为这样能够减少 MME迁移 ,
( MME Relocation ) 即改变 MME 的概率。 以图 1为例 , 当 eNodeB 2 选择 MME Pooll内的 MME, 如 MME1 , 那么 UE移动到 eNodeB 5后才会发生 MME Relocation, UE在 eNodeB 2到 eNodeB4都不会发生 MME Relocation 如 果 eNodeB 2选择 MME Pool2中的 MME,则 UE从 eNodeB 2移动到 eNodeB 1后就 会发生 MME Relocation , 因为 eNodeB 1与 MME Pool2中的 MME没有连接， 必 须更换 MME。
因此， 负载平衡 load balancing可能对 overlapping区域内的 eNodeB有所不 同， 根据 eNodeB的位置信息 （ MME Relocation发生概率） 来配置 Pool的加权 因素， 如 4叚设 MME1的最大容量为 100万用户， MME2为 150万， MME3为 200 万， MME4为 150万； 如果非 overlapping区域的 eNodeB 如 eNodeB 1收到 MME 或配置加权因素为 MME1是 10, MME2是 15; 而处于 overlapping区域的 eNodeB 2对 Pooll的加权因素为 100%, 对 Pool2的加权因素为 80%, 这样 eNodeB2算出 的 MME的最终加权因素为 MME 1是 10 * 100%= 10； MME2是 15 * 100%= 15； MME3是 20*80%=16； MME4是 15*80%=12, 这样初始接入 eNodeB2的 UE按照 最终加权因素选择 MME。 而 eNodeB 3对两个 Pool的加权因素可能都一样， 因 为 MME Relocation的概率一样； eNodeB 4对两个 Pool的加权因素为对 Pooll为 70%; Pool2为 100%, 然后按照算出的最终加权因素来选择 MME。 甚至， 在相 同 Pool内的不同 eNodeB也可根据自己位置或者离 Pool内不同 MME的距离或连 接情况等设置给不同 MME设置不同的加权因素。
通过上面描述的 Load Balancing方法， 能够保证选择最合适的 MME, 既考 虑到 MME Relocation概率又考虑到 MME的负载 ,这样在 MME的负载相同的情 况下， eNodeB可以优先选择 MME迁移概率小的 MME, 但是在 MME的负载过 重情况下， 在 overlapping区域接入的 UE可能会选择到另一个 Pool中的 MME, 尽管这样导致 MME Relocation的概率变大。
另外本发明实施例还针对有时某 MME发生过载而 Pool内的其他 MME并 不会出现过载的情况提出解决方法。 例如负载平衡 Load Balancing方法不能完 全做到根据负载选择 MME, 或者某 MME的设备单板发生故障， 导致 MME的 负载一下变成过载， 而其他 MME仍然正常， 针对这种情况导致的 eNodeB拒 绝接入该 MME的用户， 造成用户满意度下降的情形， 本发明实施例还提出另 外一种解决方案：
当一个 MME发生过载 ,则该 MME将发送过载处理的 Overload Start消息给 所有与其有连接的 eNodeB , eNodeB对发送 Overload Start消息的 MME进行解 析， 当 eNodeB并非收到所有 MME发送的 Overload Start消息， 或当 eNodeB收到 低于一定门限值数量的 MME发送的 Overload Start消息， 或 eNodeB收到低于一 定比例的 MME发送的 Overload Start消息， 则认为那些没有发送 Overload Start 消息的或之前发过 Overload Start消息但后来又发送了 Overload Stop消息给 eNodeB的 MME并未过载， 例如也可以设比例门限值， 该门限值的基础是发送 Overload Start消息给 eNodeB的 MME占所有与该 eNodeB有连接的 MME的比 例， 该门限值的取值范围为 [0,1]。 当 eNodeB收到新接入该 Pool的用户接入， 则选择那些没有发送 Overload Start消息的 MME, 可考虑负载平衡原则， 当 eNodeB收到要接入到那些过载的 MME上去的 UE接入请求时， eNodeB来发送 拒绝消息，该拒绝消息要求 UE重新发起接入，如 TAU请求，该接入需要在 RRC 部分携带特殊指示或未过载 MME的编码等，使得 eNodeB将这些接入看作新接 入到该 Pool的用户接入， 选择那些没有发送 Overload Start消息的 MME接入， 可考虑负载平衡原则， 或者， eNodeB直接将 UE的接入转移到那些没有发送 Overload Start消息的 MME。 UE接入到这些 MME后 , 可向过载的 MME获取 UE 上下文，保证业务连续性；或者不获取 UE上下文，业务重新启动，如过载 MME 的负载极高无法处理信令的情况下。
当 eNodeB收到所有 MME发送的 Overload Start消息，或 eNodeB收到高于一 定比例或门限值数量的 MME发送的 Overload Start消息， 则认为该 Pool的所有 MME发生了过载， 这样 eNodeB才会对接入的 UE进行拒绝 （除非发起紧急业 务的 UE )。当 eNodeB是非 overlapping区域的 eNodeB时，收到 Pool内所有的 MME 发来的消息将拒绝 UE接入， 当 eNodeB是 overlapping区域的 eNodeB时， 收到连 接的 Pool内所有的 MME发来的消息将拒绝 UE接入，否则可将 UE拒绝并要求其 发起再次接入并接入到其他 Pool的未发送 Overload Start消息的 MME。
当不存在允许 UE接入的 MME或允许 UE接入的 MME不符合门限要求 , 例 如 MME数量小于一定门限时， 则基站将拒绝 UE的接入请求， UE的被拒绝的 接入请求可以包括下面一种或多种：
非紧急业务的业务请求； 类型为寻呼响应的业务请求； 包含非接入层消 息的 RRC连接消息， 如跟踪区位置更新请求或附着请求。
此外， 当 eNodeB接入某 MME被拒绝一定次数后， 也可认为该 MME处于 过载 overload状态， 并且该 MME在一段时间内发送了 Overload Start消息； 或者 底层协议通知 eNodeB该 MME链路出现故障 , 如 MME与 eNodeB之间通过心跳 指示指示该 MME链路故障， 则 eNodeB也认为该 MME overload并理解为该 MME发送了 Overload Start消息给它 （在一定时间） ， 因此仍可按上文描述的 某 MME出现过载， 但是同一 Pool的其他 MME并未过载的处理方式处理。
所属技术领域的技术人员可以理解， 上文描述的针对某一 MME出现过载 的解决方案可以与某一 Pool的 MME都出现过载或者部分出现过载的情况结合 使用， 例如， 可以先转移接入过载的 MME的 UE到同一 Pool的其他未过载的 MME上，如果此时过载的 MME已经转为未过载的状态则不继续其他操作， 否 则可以转移接入过载的 MME的 UE到与其所属的 Pool有 overlapping区域的 Pool 中。
此外， 如果一个区域存在多个 RAT ( Radio Access Technology, 无线接入 技术）， 当一个 RAT出现过载，那么可以将部分或全部多模 UE转移到其他 RAT 上。 如当 MME出现过载， 而 MME所覆盖的区域还存在其他 RAT, 如 WiMAX、 WLAN或 UMTS等 , 如果 MME能确定 UE也支持 WiMAX且 UE处于 LTE与 WiMAX共同覆盖区域， 那么 MME就可以请求 UE转移到 WiMAX, 具体包括： 当 UE处于 Active状态， 那么 MME发起切换请求， 要求 UE切换到 WiMAX, 或 者 MME向 UE发送信令 , 请求 UE重新在 WiMAX进行注册或者位置区更新。 当 UE处于 Idle状态， 那么 MME对 UE进行寻呼， UE转为 Active后， 按照 Active状 态 UE处理。 也可以是， MME向 overlapping区域的 eNodeB发送指示， 当 UE接 入这些 eNodeB后， eNodeB直接发送 UE指示， 请求 UE重新选择除本 RAT的其 他 RAT进行接入。
依据上文方法实施例描述的技术方案， 本发明实施例也提供了相关的装 置及系统：
本发明实施例提出了一种移动性管理实体 MME,该 MME包括信息获取模 块， UE转移模块， 该信息获取模块用于获取与该 MME所属的 Pool有重叠区域 overlapping的 Pool的负载信息， 当 MME自身出现过载的情况时， 该 MME使用 UE转移模块将要求接入该 MME的 UE转移到该 MME所属的 Pool有重叠区域 overlapping的 Pool中。 该 UE转移模块进行 UE转移的方法与前文方法实施例提 供的解决方案一致， 此处不再赘述。
另外， 本发明实施例还提供了一种基站， 该基站包括负载信息接收模块， MME选择模块。
负载信息接收模块用于接收 MME实体发送的负载信息， 例如该负载信息 可以包括过载启动消息 overload start， 去负载消息 offload , 去负载停止消息 offload stop等， 负载信息接收模块接收到负载信息后， 通知 MME选择模块。
MME选择模块用于根据负载信息接收模块发送的通知消息给 UE选择合 适的 MME。 具体的处理方法与前文方法实施例提供的解决方案一致， 此处不 再赘述。 相应的，本发明实施例也提供了一种由上述 MME和基站构成的网絡系统， 在该网絡系统中， 基站与 MME之间的信息交互同方法实施例中 SAE系统中的 MME和 eNodeB之间的信息交互 , 在此不再赞述。
同时， 所属技术领域的技术人员可以理解， 与 MME或基站具有相同功能 的其它核心网节点和接入网节点装置同样使用本发明实施例描述的解决方 案。
釆用本发明实施例提供的解决方案， 可以快速降低过载设备的负载， 及 时均衡网絡资源， 降低了用户被网絡拒绝或不能接入网絡的的可能性， 提升 用户体验的满意度。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流 程， 是可以通过计算机程序来指令相关的硬件来完成， 所述的程序可存储于 一计算机可读取存储介质中， 该程序在执行时， 可包括如上述各方法的实施 例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体（ Read-Only Memory, ROM )或随机存^ "i己忆体 ( Random Access Memory, RAM )等。
以上所述的具体实施例， 对本发明的目的、 技术方案和有益效果进行了 进一步详细说明， 所应理解的是， 以上所述仅为本发明的较佳实施例而已， 并非用于限定本发明的保护范围， 凡在本发明的精神和原则之内， 所作的任 何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。

Claims

权利 要 求 书
1、 一种过载处理的方法， 其特征在于， 包括：
当核心网节点过载时， 将处于重叠区域的用户设备 UE转移到与所述过 载核心网节点所处的资源池有重叠区域的资源池。
2、根据权利要求 1所述的方法， 其特征在于， 当所述核心网节点为移动 性管理实体 MME时， 将处于重叠区域 overlapping区域的用户设备 UE转移 到与所述 MME所处的资源池 Pool有重叠区域 overlapping区域的 Pool。
3、 根据权利要求 2 所述的方法， 其特征在于， 在将处于重叠区域 overlapping区域的用户设备 UE转移到与所述 MME所处的资源池 Pool有重 叠区 i或 overlapping区 i或的 Pool之前， 还包括：
获取与所述 MME所处的资源池 Pool有重叠区域的 Pool中的负载信息。
4、 根据权利要求 3 所述的方法， 其特征在于， 所述将处于重叠区域 overlapping区域的用户设备 UE转移到与所述 MME所处的资源池 Pool有重 叠区 i或 overlapping区 i或的 Pool包括：
所述 MME向与所述 MME所处 Pool有 overlapping区域的 Pool发送负载查 询消息。
5、 根据权利要求 2所述的方法， 其特征在于， 所述 overlapping区域为 属于多个 Pool的区域或与多个 Pool有连接的区域。
6、 根据权利要求 2所述的方法， 其特征在于， 对于正在 overlapping区 域进行位置区更新 TAU或附着 Attach的 UE,所述将处于重叠区域 overlapping 区域的用户设备 UE 转移到与所述 MME 所处的资源池 Pool 有重叠区域 overlapping区域的 Pool具体包括：
所述 MME回复附着接受消息 Attach Accept或位置区更新接受消息 TAU Accept,所述 Attach Accept或位置区更新接受消息 TAU Accept中携带特殊指示或 目标 MME的标识信息， 通知 UE重新接入网絡；
或者 所述 MME发送消息给 overlapping区域的基站， 所述基站将所述 UE直接转移 到新的 MME, 或由所述基站发起请求使得 UE重新接入， 或由所述基站拒绝接入 所述 MME的 UE并要求所述 UE进行新的 TAU。
7、 根据权利要求 6所述的方法， 其特征在于， UE重新接入网絡时， 所述 UE在 RRC部分携带特殊指示或携带网絡分配的 MME码 MMEC或携带 MME信息 的字段为空， 所述基站根据所述特殊指示或所述 MMEC或所述携带 MME信息的 字段为空， 为所述 UE选择与过载 MME所处的资源池 Pool有重叠区域 overlapping的 Pool。
8、 根据权利要求 2所述的方法， 其特征在于， 对处于 overlapping区域的激 活 Active状态的 UE, 所述将处于重叠区域 overlapping区域的用户设备 UE转移 到与所述 MME所处的资源池 Pool有重叠区域 overlapping区域的 Pool具体包 括：
通过重新发起位置区更新 Re-TAU、 切换 HO , 或 MME迁移 Relocation的方法 将 UE转移到与过载 MME所处的资源池 Pool有重叠区域 overlapping的 Pool。
9、 根据权利要求 2所述的方法， 其特征在于， 对处于 overlapping区域的 Active状态的 UE、 发起附着 Attach, 或位置区更新 TAU的 UE, 所述方法还包括： 优先转移位置最靠近与过载 MME所处的资源池 Pool有重叠区域 overlapping的 Pool的基站中的 UE。
10、 根据权利要求 2所述的方法， 其特征在于， 对于新进入的处于 overlapping区域的 UE, 所述将处于重叠区域 overlapping区域的用户设备 UE转 移到与所述 MME所处的资源池 Pool有重叠区域 overlapping区域的 Pool之前还 包括：
设置不同级别的 MME的过载门限值，对所述 UE选择如下操作中的任意一种 或其组合：
所述设置不同级别的 MME通知 overlapping区域的基站所述 MME发生过载， 通知所述基站将新进入的 UE转移到与所述 MME所处的 Pool有 overlapping区域 的 Pool中；
所述设置不同级别的 MME不发送消息， eNodeB根据 MME的负载信息和加 权算法来选择 MME;
所述设置不同级别的 MME开始转移处于 overlapping区域的处于 Idle状态和 Active状态的 UE;
所述设置不同级别的 MME从距离与所述 MME所处的 Pool有 overlapping区 域的 Pool较近的基站开始逐渐转移；
所述设置不同级别的 MME将 overlapping区域的 eNodeB下的 UE全部转移到 所述与所述 MME所处的 Pool有 overlapping区域的 Pool中；
所述设置不同级别的 MME通知基站拒绝所述 UE接入。
11、 根据权利要求 2所述的方法， 其特征在于， 还包括：
对新进入 Pool的 UE或对基站找不到 UE携带的 MMEC对应的 MME的 UE, 进行负载平衡， 并将所述 UE接入的基站的位置信息作为负载平衡的加 权因素。
12、 根据权利要求 2所述的方法， 其特征在于， 还包括：
所述 MME通知所述与所述 MME所处的 Pool有 overlapping区域的 Pool, 停止去负载 UE到所述 MME所属的 Pool。
13、 根据权利要求 2所述的方法， 其特征在于， 还包括：
所述 MME周期性的向与所述 MME所处的 Pool有 overlapping区域的 Pool获 取负载信息。
14、 根据权利要求 2所述的方法， 其特征在于， 还包括：
当 Pool出现负载时， 所述 Pool通知与所述 Pool有 overlapping区域的 Pool停止 去负载 UE到所述 Pool。
15、 一种过载处理的方法， 其特征在于， 包括：
获取资源池中的核心网节点的负载信息；
解析所述负载信息， 将接入所述负载信息中指示的过载核心网节点的用 户设备 UE转移到所述资源池中允许 UE接入的核心网节点中。
16、 根据权利要求 15所述的方法， 其特征在于， 其特征在于， 当所述核 心网节点为 MME时 , 所述方法包括：
获取资源池 Pool中的 MME的负载信息；
解析所述负载信息， 将接入所述负载信息中指示的过载 MME的用户设 备 UE转移到所述资源池 Pool中允许 UE接入的 MME。
17、根据权利要求 16所述的方法，其特征在于，所述获取 Pool中的 MME 的负载信息具体包括：
基站接收到 Pool中的 MME的过载启动消息 Overload Start消息。
18、 根据权利要求 16所述的方法， 其特征在于， 所述允许 UE接入的 MME具体包括， 没有发送给基站 Overload Start消息或给基站发送了 Overload Sto 消息的 MME。
19、根据权利要求 16所述的方法，其特征在于，所述解析所述负载信息， 将接入所述负载信息中指示的过载 MME的用户设备 UE转移到所述资源池 Pool中允许 UE接入的 MME之前， 还包括：
如果存在允许 UE接入的 MME或允许 UE接入的 MME大于一定门限时， 所述基站收到要接入到过载的 MME上去的 UE的接入请求时，所述基站发送拒 绝消息， 所述拒绝消息要求 UE重新发起接入； 或者所述基站直接将要接入到过 载的 MME上去的 UE转移到允许 UE接入的 MME。
20、 根据权利要求 19所述的方法， 所述 UE重新发起接入具体包括： UE在 RRC中携带特殊指示或携带基站分配的 MMEC, 所述特殊指示通知 基站 UE为新接入的 UE。
21、根据权利要求 16所述的方法，其特征在于， 当允许 UE接入的 MME 不符合预先设置的 MME门限要求时， 基站将拒绝 UE的接入请求， 该接入 请求包括下面任意一种或其组合：
非紧急业务的业务请求； 寻呼响应的业务请求；
包含非接入层消息的 RRC连接消息。
22、 根据权利要求 1或 16所述的方法， 其特征在于， 还包括：
当存在多个无线接入技术 RAT的情况下， 将所述 UE转移到所述 UE支 持的任一 RAT上。
23、 一种移动性管理实体 MME, 其特征在于， 包括：
信息获取模块， 用于获取与所述 MME所处的 Pool有重叠区域 overlapping 的 Pool的负载信息；
UE转移模块， 用于根据所述信息获取模块获取的负载信息，将要求接入所 述 MME的 UE转移到与所述 MME所属的 Pool有重叠区域 overlapping的 Pool 中。
24、 一种基站， 其特征在于， 包括：
负载信息接收模块， 用于接收移动性管理实体 MME发送的负载信息；
MME选择模块，用于根据负载信息接收模块接收的负载信息为 UE选择可以 接入的 MME。
PCT/CN2009/070860 2008-03-21 2009-03-18 一种过载处理的方法及装置 WO2009115041A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP09721642.8A EP2265054B1 (en) 2008-03-21 2009-03-18 Overload processing method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810066200.1 2008-03-21
CN2008100662001A CN101541040B (zh) 2008-03-21 2008-03-21 一种过载处理的方法及装置

Publications (1)

Publication Number Publication Date
WO2009115041A1 true WO2009115041A1 (zh) 2009-09-24

Family

ID=41090507

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/070860 WO2009115041A1 (zh) 2008-03-21 2009-03-18 一种过载处理的方法及装置

Country Status (3)

Country Link
EP (1) EP2265054B1 (zh)
CN (1) CN101541040B (zh)
WO (1) WO2009115041A1 (zh)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011062539A1 (en) 2009-11-23 2011-05-26 Telefonaktiebolaget L M Ericsson (Publ) Moving user equipment without service interruption technical field
WO2011062542A1 (en) * 2009-11-23 2011-05-26 Telefonaktiebolaget L M Ericsson (Publ) Self management of mobility management entity (mme) pools
WO2012020850A1 (en) * 2010-08-12 2012-02-16 Nec Corporation Communication system
US9107128B2 (en) 2009-11-06 2015-08-11 Blackberry Limited Methods and mechanisms to enable priority calls in a cell through pre-emption of other calls
WO2016000189A1 (zh) * 2014-06-30 2016-01-07 华为技术有限公司 网元选择实体及用户设备注册的方法
CN105516959A (zh) * 2014-10-20 2016-04-20 中兴通讯股份有限公司 终端卸载处理、终端注册处理方法及装置
CN102769931B (zh) * 2011-05-04 2017-08-25 中兴通讯股份有限公司 中继节点释放终端的方法及中继节点、终端
US10448297B2 (en) 2014-06-24 2019-10-15 Nec Corporation Network node, mobile terminal, base station and methods performed therein
US10512011B2 (en) 2014-06-24 2019-12-17 Nec Corporation Control node, network node, and methods performed therein

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010057198A1 (en) 2008-11-17 2010-05-20 Starent Networks, Corp Dynamic load balancing in a communication network
CN102638860A (zh) * 2011-02-11 2012-08-15 中兴通讯股份有限公司 一种中继节点切换方法及系统
CN102076016A (zh) * 2011-02-12 2011-05-25 普天信息技术研究院有限公司 中继系统的过载控制方法
CN102695208B (zh) * 2011-03-22 2015-01-28 中兴通讯股份有限公司 一种业务均衡分配方法和装置
JP5625134B2 (ja) * 2011-04-06 2014-11-12 エヌイーシーヨーロッパ リミテッドＮｅｃ Ｅｕｒｏｐｅ Ｌｔｄ． 進化型パケットシステムにおいてユーザ機器コンテキストを配信する方法およびシステム
CN102869055A (zh) * 2011-07-08 2013-01-09 中兴通讯股份有限公司 一种保证rn服务ue的服务连续性的方法和系统
US8948014B2 (en) * 2011-10-19 2015-02-03 Alcatel Lucent System and method for load balancing MMEs and MME pools
CN103947248B (zh) 2011-11-14 2018-07-20 阿尔卡特朗讯 基带信号处理群集
EP2592863B1 (en) * 2011-11-14 2014-01-08 Alcatel Lucent Distributed load balancing in a radio access network
CN103179160B (zh) * 2011-12-22 2016-01-27 中国移动通信集团公司 一种负载转移方法、装置及系统
KR101539053B1 (ko) * 2012-05-09 2015-07-22 주식회사 케이티 이동통신 시스템 및 이동성 관리 장치
US20130336283A1 (en) * 2012-06-15 2013-12-19 Nokia Siemens Networks Oy Overload control in mobility management entity
CN102739688A (zh) * 2012-07-06 2012-10-17 北京邮电大学 基于主动探测的sip网络过载控制系统和方法
RU2628700C2 (ru) * 2013-05-31 2017-08-25 Хуавэй Текнолоджиз Ко., Лтд. Способ, устройство и система для управления абонентским устройством
EP3278507B1 (en) * 2015-04-02 2020-10-28 Nokia Solutions and Networks Oy Method and apparatus providing mme redundancy across extended geographic areas
US9467843B1 (en) * 2015-05-15 2016-10-11 Rivada Networks, Llc Methods and system for dynamic spectrum arbitrage with a mobility load balancer gateway
CN108811168B (zh) 2016-08-12 2020-01-17 华为技术有限公司 无线网络的接入控制方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101039506A (zh) * 2006-03-15 2007-09-19 华为技术有限公司 一种移动管理实体/用户面实体迁移方法
CN101114927A (zh) * 2006-07-24 2008-01-30 华为技术有限公司 一种实现负载均衡的系统及方法
CN101114928A (zh) * 2006-07-24 2008-01-30 华为技术有限公司 一种实现负载均衡的系统及方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030028644A1 (en) * 2001-08-02 2003-02-06 Patrick Maguire System and method for load sharing within a core network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101039506A (zh) * 2006-03-15 2007-09-19 华为技术有限公司 一种移动管理实体/用户面实体迁移方法
CN101114927A (zh) * 2006-07-24 2008-01-30 华为技术有限公司 一种实现负载均衡的系统及方法
CN101114928A (zh) * 2006-07-24 2008-01-30 华为技术有限公司 一种实现负载均衡的系统及方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2265054A4 *

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9107128B2 (en) 2009-11-06 2015-08-11 Blackberry Limited Methods and mechanisms to enable priority calls in a cell through pre-emption of other calls
EP2504980A4 (en) * 2009-11-23 2016-10-26 Ericsson Telefon Ab L M MOVING A USER EQUIPMENT WITHOUT SERVICE INTERRUPTION TECHNICAL FIELD
EP2504980A1 (en) * 2009-11-23 2012-10-03 Telefonaktiebolaget L M Ericsson (PUBL) Moving user equipment without service interruption technical field
WO2011062539A1 (en) 2009-11-23 2011-05-26 Telefonaktiebolaget L M Ericsson (Publ) Moving user equipment without service interruption technical field
US8331224B2 (en) 2009-11-23 2012-12-11 Telefonaktiebolaget L M Ericsson (Publ) Self-management of mobility management entity (MME) pools
JP2013511888A (ja) * 2009-11-23 2013-04-04 テレフオンアクチーボラゲット エル エム エリクソン（パブル） モビリティ管理エンティティ（ｍｍｅ）プールの自己管理
EP2505018A4 (en) * 2009-11-23 2016-11-02 Ericsson Telefon Ab L M MOBILITY MANAGEMENT ENTITY POOLS AUTOGERATION (MS)
WO2011062542A1 (en) * 2009-11-23 2011-05-26 Telefonaktiebolaget L M Ericsson (Publ) Self management of mobility management entity (mme) pools
US10932174B2 (en) 2010-08-12 2021-02-23 Nec Corporation Communication system
WO2012020850A1 (en) * 2010-08-12 2012-02-16 Nec Corporation Communication system
EP3104644A1 (en) * 2010-08-12 2016-12-14 Nec Corporation Communication system
US9107129B2 (en) 2010-08-12 2015-08-11 Nec Corporation Communication system
US9560569B2 (en) 2010-08-12 2017-01-31 Nec Corporation Communication system
CN102769931B (zh) * 2011-05-04 2017-08-25 中兴通讯股份有限公司 中继节点释放终端的方法及中继节点、终端
US10448297B2 (en) 2014-06-24 2019-10-15 Nec Corporation Network node, mobile terminal, base station and methods performed therein
US10512011B2 (en) 2014-06-24 2019-12-17 Nec Corporation Control node, network node, and methods performed therein
WO2016000189A1 (zh) * 2014-06-30 2016-01-07 华为技术有限公司 网元选择实体及用户设备注册的方法
US20170311150A1 (en) * 2014-10-20 2017-10-26 Zte Corporation Method and Device for Processing Terminal Unloading and Processing Terminal Registration
US10616752B2 (en) * 2014-10-20 2020-04-07 Xi'an Zhongxing New Software Co., Ltd. Method and device for processing terminal unloading and processing terminal registration
CN105516959A (zh) * 2014-10-20 2016-04-20 中兴通讯股份有限公司 终端卸载处理、终端注册处理方法及装置

Also Published As

Publication number Publication date
EP2265054B1 (en) 2017-09-27
CN101541040A (zh) 2009-09-23
CN101541040B (zh) 2012-04-25
EP2265054A1 (en) 2010-12-22
EP2265054A4 (en) 2011-04-27

Similar Documents

Publication Publication Date Title
WO2009115041A1 (zh) 一种过载处理的方法及装置
US11678240B2 (en) Method and system for transferring user equipment in mobile communication system
US8509163B2 (en) Method and system for selecting network equipment
WO2018153253A1 (zh) 一种选择会话管理功能实体的方法、装置和系统
US8331938B2 (en) Moving user equipment without service interruption
JP5866132B2 (ja) デタッチ手順を行う方法及びその端末
JP6387351B2 (ja) ワイヤレスデバイスの入力を用いたネットワーク指向のシステム選択
JP5785216B2 (ja) アクセス制御方法、アクセス制御装置、および通信システム
WO2016112485A1 (zh) 一种寻呼用户设备的方法和mme
WO2020063649A1 (zh) 网络服务控制方法及通信设备
EP3528562B1 (en) Method for determining paging area, access network node and core network node
CN108370498B (zh) 传输方案的确定方法、装置和设备
KR101657861B1 (ko) 부하 조절
US20220330006A1 (en) Roaming method, apparatus, and system
WO2021139441A1 (zh) 用于语音业务的通信方法、装置和系统
WO2021134175A1 (zh) 一种漫游的方法、装置及系统
WO2008113300A1 (fr) Procédé, système et appareil pour sélectionner des dispositifs de réseau
JP2020523807A (ja) コアリソースの分配
WO2010088794A1 (zh) 处理演进网络中上下文的方法和系统
WO2023237046A1 (zh) 一种iab节点的移动性管理方法及相关设备
WO2012062193A1 (zh) Mtc切换中的拥塞控制方法及装置、系统
CN114846843A (zh) 请求分组数据网络连接信息的通信方法
WO2008134966A1 (fr) Procédé, terminal utilisateur, dispositif côté réseau et système de communication sans fil pour contrôle de la mesure

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: 09721642

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2009721642

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2009721642

Country of ref document: EP