WO2015070414A1 - 拥塞控制方法、装置及系统 - Google Patents

拥塞控制方法、装置及系统 Download PDF

Info

Publication number
WO2015070414A1
WO2015070414A1 PCT/CN2013/087124 CN2013087124W WO2015070414A1 WO 2015070414 A1 WO2015070414 A1 WO 2015070414A1 CN 2013087124 W CN2013087124 W CN 2013087124W WO 2015070414 A1 WO2015070414 A1 WO 2015070414A1
Authority
WO
WIPO (PCT)
Prior art keywords
congestion
participating
notification message
mme
sgsn
Prior art date
Application number
PCT/CN2013/087124
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 PCT/CN2013/087124 priority Critical patent/WO2015070414A1/zh
Priority to CN201380004566.5A priority patent/CN104969621B/zh
Priority to EP18152260.8A priority patent/EP3376795B1/en
Priority to EP13897406.8A priority patent/EP3062560B1/en
Publication of WO2015070414A1 publication Critical patent/WO2015070414A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/02Access restriction performed under specific conditions
    • H04W48/06Access restriction performed under specific conditions based on traffic conditions

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a congestion control method, apparatus, and system. Background technique
  • MVNO Mobile Virtual Network Operator
  • Mobile network operators with their own operating licenses can also develop their own users and provide services by leasing other mobile network operators' networks (also commonly referred to as network shares), which can also be seen as MVNO.
  • network shares also be seen as MVNO.
  • MVNO mobile network operators' networks
  • an MNO network may serve multiple MVNOs.
  • the MNO needs to manage network resources for different MVNOs, for example, assign different radio access resources, maximum users, and maximum bearers to different MVNOs. (Bearer) / Packet Data Protocol (PDP) resources, available services, etc.
  • the network resource can be represented by the quantity. For example, the maximum number of users of an MVNO is 1000. It can also be represented by a resource occupancy ratio. For example, a certain MVNO can use 40% of the wireless access resources of the mobile network.
  • the MNO manages and controls network resources of different MVNOs to ensure that all MVNOs of the service have sufficient network resources available.
  • the network resource usage of an MVNO reaches the preset value (maximum data, or maximum percentage, etc.)
  • the congestion may be some Too many user equipments (User Equipments, hereinafter referred to as UEs) of one or more MVNOs cause excessive resources, while other MVNO resources are used normally; the congestion may also be occupied by all MVNO UEs. More, causing device congestion on network devices. How to perform corresponding congestion control for different MVNOs is a problem that needs to be solved.
  • UEs User Equipments
  • a radio access network Radio access network, hereinafter referred to as: RAN
  • RAN Radio access network
  • the congestion information may include a congested cell identifier (cell ID)
  • the core network device receives
  • the unified congestion control is performed for the entire cell, such as the Policy and Charging Rule Function (hereinafter referred to as PCRF) or the service server reduces the packet transmission, or reduces the service quality (QoS). ), reducing the occupation of UE resources in the congested cell.
  • PCRF Policy and Charging Rule Function
  • QoS service quality
  • Embodiments of the present invention provide a congestion control method, apparatus, and system, which can distinguish between different participating operators for congestion control, and implement accurate and efficient congestion control for specific congestion objects and congestion causes.
  • an embodiment of the present invention provides a congestion control method, including:
  • the core network device receives the congestion notification message sent by the RAN device when the RAN device detects that one or more participating operators are congested, and the congestion notification message includes the participating operator identifier that is congested, and the participating operator is the mobile The virtual network operator MVNO or the operator of the shared carrier network;
  • the core network device performs congestion control on the participating operators corresponding to the participating operator identifiers according to the congestion notification message.
  • the congestion notification message further includes any one or combination of the following:
  • Congestion reasons of participating operators that are congested resource usage of participating operators in a congested cell where congestion occurs, other available cell information of the RAN device or neighboring RAN devices of the RAN device, and the RAN device or Adjacent RAN device of the RAN device.
  • the resource usage of the participating operators corresponding to the participating operator identifiers in the other available cells.
  • the core network device is a mobility management entity MME/serving GPRS support node SGSN
  • the core network device The congestion notification message sent by the receiving radio access network RAN device when detecting that one or more participating operators are congested includes:
  • the MME/SGSN receives a congestion notification message sent by the RAN device when detecting that one or more participating operators are congested;
  • the MME/SGSN records the congestion notification message, and sends a congestion notification response message to the RAN device;
  • the core network device performs congestion control on the participating operators corresponding to the participating operator identifier according to the congestion notification message, including:
  • the MME/SGSN sends an access reject message to the UE according to the participating operator information and the congestion notification message included in the access request.
  • the access request is an attach request in a 4G network
  • the access request is a service request initiated by the UE.
  • the access request is a tracking area update request
  • the access request is a routing area update request
  • the access request is a primary/secondary PDP context establishment or modification request initiated by the UE;
  • the access reject message further includes: an access reject reason and an idle cell indication information, where the UE selects to access the idle cell indicated by the idle cell indication information.
  • the core network device includes an MME/SGSN, a serving gateway S-GW, and a packet data network gateway PG W a gateway GPRS support node GGSN and a policy and charging rule function entity PCRF, the core network device receiving a congestion notification message sent by the radio access network RAN device when detecting that one or more participating operators are congested, including: The MME/SGSN receives a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested;
  • the MME/SGSN records the congestion notification message, and sends a congestion notification response message to the RAN device;
  • the core network device performs congestion control on the participating operators corresponding to the participating operator identifier according to the congestion notification message, including:
  • the PCRF sends an IP connection access network IP-CAN session modification request to the P-GW/GGSN; the P-GW/GGSN initiates a bearer setup to the MME/SGSN through the S-GW according to the IP-CAN session modification request.
  • a request for modifying, the bearer setup/modification request includes an International Mobile Subscriber Identity (IMSI) information of the UE/the participating operator identifier of the UE;
  • IMSI International Mobile Subscriber Identity
  • the MME/SGSN rejects the bearer setup/modification request according to the IMSI information/participating operator identity and the congestion notification message.
  • the method further includes:
  • the MME/SGSN initiates a bearer setup/modification rejection response to the P-GW/GGSN by using an S-GW, where the bearer setup/modification rejection response includes a reject reason;
  • the P-GW/GGSN sends an IP-CAN session modification response message to the PCRF, where the IP-C AN session modification response message includes the rejection reason.
  • the MME/SGSN sends a congestion mitigation response message to the RAN device.
  • the core network device includes an MME/SGSN, an S-GW, a P-GW/GGSN, and a PCRF.
  • the congestion notification message sent by the core network device when the RAN device detects that one or more participating operators are congested including:
  • the MME/SGSN receives a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested;
  • the MME/SGSN sends a bearer update request message to the P-GW/GGSN by using the S-GW, where the bearer update request message includes content of the congestion notification message;
  • the P-GW/GGSN records the bearer update request message, and sends a congestion notification response message to the RAN device by using the S-GW and the MME/SGSN;
  • the core network device performs congestion control on the participating operators corresponding to the participating operator identifier according to the congestion notification message, including:
  • the PCRF sends an IP connection access network IP-CAN session modification request to the P-GW/GGSN;
  • the P-GW/GGSN rejects the IP-CAN session modification request according to the congestion notification message and the type of the IP-CAN session modification request.
  • the method further includes:
  • the P-GW/GGSN sends an IP-CAN session modification response message to the PCRF, and the IP-CAN session modification response message includes a rejection reason.
  • the method further includes:
  • the P-GW/GGSN sends a congestion mitigation response message to the RAN device by using the S-GW and the MME/SGSN.
  • the core network device includes an S-GW, a P-GW/GGSN, and a PCRF, where the core network device
  • the congestion notification message sent by the receiving radio access network RAN device when detecting that one or more participating operators are congested includes:
  • the P-GW/GGSN receives, by the S-GW, a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested;
  • the RAN device sends a congestion notification response message
  • the core network device performs congestion control on the participating operators corresponding to the participating operator identifier according to the congestion notification message, including:
  • the PCRF sends an IP-CAN session modification request to the P-GW/GGSN;
  • the P-GW/GGSN rejects the IP-CAN session modification request according to the congestion notification message and the type of the IP-CAN session modification request.
  • the method further includes:
  • the P-GW/GGSN sends an IP-CAN session modification response message to the PCRF, and the IP-CAN session modification response message includes a rejection reason.
  • the method further includes:
  • the P-GW/GGSN receives, by the S-GW, a congestion mitigation notification message sent when the RAN device detects that the participating operator congestion condition is congested in the RAN device;
  • the P-GW/GGSN sends a congestion mitigation response message to the RAN device through the S-GW.
  • an embodiment of the present invention provides a congestion control method, including:
  • the RAN device detects the occurrence of congestion according to the resource usage of the participating operators, which is the mobile virtual network operator MVNO or the operator of the shared carrier network;
  • the RAN device When the RAN device detects that one or more of the participating operators are congested, sending a congestion notification message to the core network device related to the participating operator that is congested, where the congestion notification message includes congestion.
  • the participating operator identifier is used by the core network device to perform congestion control on the participating operators corresponding to the participating operator identifier.
  • the congestion notification message further includes any one or combination of the following:
  • Congestion reasons of participating operators that are congested resource usage of participating operators in a congested cell where congestion occurs, other available cell information of the RAN device or neighboring RAN devices of the RAN device, and the RAN device or Adjacent RAN device of the RAN device.
  • the resource usage of the participating operators corresponding to the participating operator identifiers in the other available cells.
  • the core network device is an MME/SGSN, and when the RAN device detects one or more When the participating operators are congested, the congestion notification message is sent to the core network device related to the participating operator that is congested, including:
  • the RAN device When the RAN device detects that one or more of the participating operators are congested, sending a congestion notification message to the MME/SGSN related to the participating operator that is congested, and the MME/SGSN records the Congesting the notification message, and performing congestion control on the participating operators corresponding to the participating operator identifier according to the congestion notification message;
  • the method further includes: the RAN device receiving a congestion notification response message sent by the MME/SGSN.
  • the core network device includes an MME/SGSN, an S-GW, a P-GW/GGSN, and a PCRF.
  • the RAN device detects that one or more of the participating operators are congested, the RAN device sends a congestion notification message to the core network device related to the participating operator that is congested, including:
  • the RAN device When the RAN device detects that one or more of the participating operators are congested, sending a congestion notification message to the MME/SGSN related to the participating operator that is congested for the MME/SGSN record office. Congestion notification message;
  • the method further includes: the RAN device receiving a congestion notification response message sent by the MME/SGSN.
  • the RAN device receives a congestion mitigation response message sent by the MME/SGSN.
  • the core network device includes an MME/SGSN, an S-GW, a P-GW/GGSN, and The PCRF, when the RAN device detects that one or more of the participating operators are congested, sends a congestion notification message to the core network device related to the participating operator that is congested, including:
  • the RAN device When the RAN device detects that one or more of the participating operators are congested, sending a congestion notification message to the MME/SGSN related to the participating operator that is congested, for the MME/SGSN to pass the Sending, by the S-GW, a bearer update request message to the P-GW/GGSN, where the bearer update request message includes content of the congestion notification message;
  • the method further includes:
  • the RAN device receives a congestion notification response message sent by the P-GW/GGSN through the S-GW and the MME/SGSN.
  • the method further includes:
  • the P-GW/GGSN sends the congestion mitigation notification message; the RAN device receives a congestion mitigation response message sent by the P-GW/GGSN through the S-GW and the MME/SGSN.
  • the core network device includes an S-GW, a P-GW/GGSN, and a PCRF, where the RAN device When detecting that one or more of the participating operators are congested, sending a congestion notification message to the core network device related to the participating operator that is congested includes:
  • the RAN device When the RAN device detects that one or more of the participating operators are congested, sending a congestion notification message to the S-GW related to the participating operator that is congested for the S-GW Transmitting the congestion notification message by the P-GW/GGSN;
  • the method further includes:
  • the RAN device receives a congestion notification response message sent by the P-GW/GGSN through the S-GW.
  • the method further includes:
  • the RAN device detects that the participating carrier congestion occurs in the RAN device. Sending a congestion mitigation notification message to the S-GW, where the S-GW sends the congestion mitigation notification message to the P-GW/GGSN;
  • the RAN device receives a congestion mitigation response message sent by the P-GW/GGSN through the S-GW.
  • an embodiment of the present invention provides a core network device, including:
  • a receiving module configured to receive a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested, where the congestion notification message includes a participating operator identifier that is congested, and the participating operator An operator that moves the virtual network operator MVNO or the shared carrier network;
  • a processing module configured to perform congestion control on the participating operators corresponding to the participating operator identifiers according to the congestion notification message.
  • the congestion notification message further includes any one or combination of the following:
  • Congestion reasons of participating operators that are congested resource usage of participating operators in a congested cell where congestion occurs, other available cell information of the RAN device or neighboring RAN devices of the RAN device, and the RAN device or The resource usage of the participating operators corresponding to the participating operator identifiers in the other available cells of the neighboring RAN device of the RAN device.
  • the core network device is a mobility management entity MME/serving GPRS support node SGSN, where the MME/SGSN includes :
  • a first receiving module configured to receive a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested
  • a first sending module configured to record the congestion notification message, and send a congestion notification response message to the RAN device
  • the first receiving module is further configured to receive an access request sent by the user equipment UE by using the RAN device, where the access request includes the participating operator information to be accessed;
  • the first processing module is configured to send an access reject message to the UE according to the participating operator information and the congestion notification message included in the access request.
  • the access request is an attach request
  • the access request is a service request initiated by the UE.
  • the access request is a tracking area update request
  • the access request is a routing area update request
  • the access request is a primary/secondary PDP context establishment or modification request initiated by the UE;
  • the access reject message further includes: an access reject reason and an idle cell indication information, where the UE selects to access the idle cell indicated by the idle cell indication information.
  • the core network device includes an MME/SGSN, a serving gateway S-GW, and a packet data network gateway PG W/
  • a second receiving module configured to receive a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested
  • a second sending module configured to record the congestion notification message, and send a congestion notification response message to the RAN device
  • the PCRF includes:
  • a third sending module configured to send an IP connection access network IP-CAN session modification request to the P-GW/GGSN;
  • the P-GW/GGSN includes:
  • a fourth sending module configured to initiate a bearer setup/modification request to the MME/SGSN by using an S-GW according to the IP-CAN session modification request, where the bearer setup/modification request includes an IMSI information of an international mobile subscriber identity of the UE /UE's participating operator ID;
  • the MME/SGSN further includes:
  • a second processing module configured to reject the bearer setup/modification request according to the IMSI information/participating operator identifier and the congestion notification message.
  • the second sending module is further configured to:
  • the fourth sending module is further configured to: send an IP-CAN session modification response message to the PCRF, where the IP-CAN session modification response message includes the rejection reason.
  • the second receiving module is further configured to:
  • the core network device includes an MME/SGSN, an S-GW, a P-GW/GGSN, and a PCRF.
  • the MME/SGSN includes:
  • a third receiving module configured to receive a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested;
  • a fifth sending module configured to send, by using the S-GW, a bearer update request message to the P-GW/GGSN, where the bearer update request message includes content of the congestion notification message;
  • the P-GW/GGSN includes :
  • a fourth receiving module configured to receive the bearer update request message
  • a sixth sending module configured to record the bearer update request message, and send a congestion notification response message to the RAN device by using the S-GW and the MME/SGSN;
  • the PCRF includes:
  • a seventh sending module configured to send an IP connection access network IP-CAN session modification request to the P-GW/GGSN;
  • the P-GW/GGSN further includes:
  • a third processing module configured to reject the IP-CAN session modification request according to the type of the congestion notification message and the IP-CAN session modification request.
  • the sixth sending module is further configured to: send an IP-CAN session modification response message to the PCRF,
  • the IP-CAN session modification response message includes a reason for rejection.
  • the third receiving module is further And a method for: receiving, by the RAN device, a congestion mitigation notification message sent when a participating operator congestion condition mitigation occurs in the RAN device;
  • the fifth sending module is further configured to: send, by using the S-GW, the congestion mitigation notification message to the P-GW/GGSN;
  • the sixth sending module is further configured to: send a congestion mitigation response message to the RAN device by using the S-GW and the MME/SGSN.
  • the core network device includes an S-GW, a P-GW/GGSN, and a PCRF, where the P-GW / GGSN includes:
  • a fifth receiving module configured to receive, by using the S-GW, a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested;
  • a seventh sending module configured to record the congestion notification message, and send a congestion notification response message to the RAN device by using the S-GW;
  • the PCRF includes:
  • An eighth sending module configured to send an IP-CAN session modification request to the P-GW/GGSN; the P-GW/GGSN includes:
  • a fourth processing module configured to reject the IP-CAN session modification request according to the type of the congestion notification message and the IP-CAN session modification request.
  • the seventh sending module is further configured to:
  • the fifth receiving module is further used to Receiving, by the S-GW, a congestion mitigation notification message sent when the RAN device detects that the participating operator congestion condition in the RAN device is relieved;
  • the seventh sending module is further configured to: send a congestion mitigation response message to the RAN device by using the S-GW.
  • a fourth aspect of the present invention provides a radio access network device, including:
  • a detecting module configured to detect a congestion occurrence according to resource usage of the participating operators, where The participating operator is an operator of the mobile virtual network operator MVNO or the shared carrier network; and a sending module, configured to: when the detecting module detects that one or more of the participating operators are congested, causing congestion
  • the participating network device of the participating operator sends a congestion notification message, where the congestion notification message includes a participating operator identifier that is congested, and is used by the core network device to perform the participating operator corresponding to the participating operator identifier. Congestion control.
  • the congestion notification message further includes any one or combination of the following:
  • Congestion reasons of participating operators that are congested resource usage of participating operators in a congested cell where congestion occurs, other available cell information of the RAN device or neighboring RAN devices of the RAN device, and the RAN device or The resource usage of the participating operators corresponding to the participating operator identifiers in the other available cells of the neighboring RAN device of the RAN device.
  • the core network device is an MME/SGSN
  • the sending module is configured to:
  • the detecting module detects that one or more of the participating operators are congested, sending a congestion notification message to the MME/SGSN related to the participating operator that is congested for the MME/SGSN record office. Congestion notification message, and performing congestion control on the participating operators corresponding to the participating operator identifier according to the congestion notification message;
  • the radio access network device further includes:
  • the first receiving module is configured to receive a congestion notification response message sent by the MME/SGSN.
  • the core network device includes an MME/SGSN, an S-GW, a P-GW/GGSN, and a PCRF.
  • the sending module is used to:
  • the detecting module detects that one or more of the participating operators are congested, sending a congestion notification message to the MME/SGSN related to the participating operator that is congested for the MME/SGSN record office. Congestion notification message;
  • the radio access network device further includes:
  • the second receiving module is configured to receive a congestion notification response message sent by the MME/SGSN.
  • the sending module is further configured to:
  • the first receiving module or the second receiving module is further configured to:
  • the core network device includes an MME/SGSN, an S-GW, a P-GW/GGSN, and a PCRF.
  • the sending module is used to:
  • the detecting module detects that one or more of the participating operators are congested, sending a congestion notification message to the MME/SGSN related to the participating operator that is congested, for the MME/SGSN to pass the Sending, by the S-GW, a bearer update request message to the P-GW/GGSN, where the bearer update request message includes content of the congestion notification message;
  • the radio access network device further includes:
  • a third receiving module configured to receive a congestion notification response message sent by the P-GW/GGSN by using the S-GW and the MME/SGSN.
  • the sending module is further configured to:
  • the detecting module Sending, by the detecting module, a congestion mitigation notification message to the MME/SGSN, where the detecting module detects that the congestion of the participating operators in the RAN device is relieved, and the MME/SGSN is used by the S-GW
  • the P-GW/GGSN sends the congestion mitigation notification message;
  • the third receiving module is further configured to receive a congestion mitigation response message sent by the P-GW/GGSN through the S-GW and the MME/SGSN.
  • the core network device includes an S-GW, a P-GW/GGSN, and a PCRF, where the sending module is used by the sending module In:
  • the detecting module detects that one or more of the participating operators are congested, sending a congestion notification message to the S-GW related to the participating operator that is congested, for the S-GW to apply to the S-GW Transmitting the congestion notification message by the P-GW/GGSN;
  • the radio access network device further includes:
  • a fourth receiving module configured to receive the P-GW/GGSN sent by the S-GW The plug notification response message.
  • the sending module is further configured to:
  • the fourth receiving module is further configured to receive a congestion mitigation response message sent by the P-GW/GGSN through the S-GW.
  • the embodiment of the present invention provides a communication system, comprising the core network device according to any one of the twelfth possible implementation manners of the third aspect to the third aspect, and the fourth to fourth aspects The RAN device of any of the eighth possible embodiments.
  • the congestion control method, device, and system provided by the embodiment of the present invention receive, by the core network device, a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested, and the congestion notification message includes the participating operator that is congested. logo. Then, according to the congestion notification message, congestion control is performed on the participating operators corresponding to the participating operator identifiers. Therefore, it is possible to distinguish between different participating operators for congestion control, and to implement accurate and efficient congestion control for specific congestion objects and congestion causes, and to protect the number of connection resources and bandwidth resources of participating operators that are not congested.
  • Embodiment 1 is a flowchart of Embodiment 1 of a congestion control method according to the present invention
  • Embodiment 2 is a flowchart of Embodiment 2 of a congestion control method according to the present invention
  • Embodiment 3 is a signaling interaction diagram of Embodiment 3 of a congestion control method according to the present invention.
  • Embodiment 4 is a signaling interaction diagram of Embodiment 4 of a congestion control method according to the present invention.
  • 5 is a signaling interaction diagram of Embodiment 5 of a congestion control method according to the present invention
  • 6 is a signaling interaction diagram of Embodiment 6 of a congestion control method according to the present invention
  • Embodiment 7 is a schematic structural diagram of Embodiment 1 of a core network device according to the present invention.
  • Embodiment 8 is a schematic structural diagram of Embodiment 1 of a RAN device according to the present invention.
  • Embodiment 9 is a schematic structural diagram of Embodiment 2 of a core network device according to the present invention.
  • FIG. 10 is a schematic structural diagram of Embodiment 2 of a RAN device according to the present invention.
  • the technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention.
  • the embodiments are a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.
  • the embodiment of the present invention provides a congestion control method, which can be implemented according to different congestion types in a scenario where an operator contracts with a plurality of virtual operators and a radio access network (Radio access network (hereinafter referred to as RAN) device is congested.
  • RAN Radio access network
  • the congestion status of different MVNOs is removed, and the connection number resources and bandwidth resources of the MVNO without congestion are protected, and the resource refinement control in the multi-MVNO state is also realized.
  • Embodiment 1 is a flowchart of Embodiment 1 of a congestion control method according to the present invention.
  • This embodiment uses a core network device as an execution entity as an example.
  • the core network device in this embodiment includes devices supporting different access technologies in a 3GPP network.
  • mobility management devices such as Serving GPRS Support Node (SGSG) supporting 2G/3G network access, Mobility Management Entity (hereinafter referred to as MME) supporting 4G network access ), 4G-SGSN, etc.
  • gateway devices such as Gateway GPRS Support Node (Gateway GPRS Support Node, hereinafter referred to as: GGSN), Serving Gateway (hereinafter referred to as S-GW), Packet Data Network Gateway (Packet Data Network) Gateway, hereinafter referred to as: P-GW).
  • GGSN Gateway GPRS Support Node
  • S-GW Serving Gateway
  • Packet Data Network Gateway Packet Data Network Gateway
  • the method in this embodiment may include:
  • the core network device receives a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested, and the congestion notification message includes the participating operator identifier that is congested.
  • the participating operators refer to the operators or MVNOs sharing the carrier network.
  • the participating operator identifier may be, for example, an MVNO identifier or an International Mobile Subscriber Identity (IMSI) number corresponding to the MVNO.
  • IMSI International Mobile Subscriber Identity
  • the core network device performs congestion control on the participating operators corresponding to the operator identifier according to the congestion notification message.
  • the congestion notification message also includes any one or combination of the following:
  • Congestion causes of congested participating operators, resource usage of participating operators in congested cells where congestion occurs, other available cell information of neighboring RAN devices of RAN equipment or RAN equipment, and neighboring RANs of RAN equipment or RAN equipment
  • the congestion of the participating operators may be insufficient, for example, the number of UEs available to the participating operators is insufficient, the number of connected resources is insufficient, or the available bandwidth resources are insufficient, and the resource usage of the participating operators in the congested cells is congested.
  • the resource usage of the participating operators corresponding to the operator identifier may be, for example, a user equipment number resource, a connection number resource, or a bandwidth resource.
  • the core network device is the MME/SGSN.
  • the MME/SGSN receives a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested.
  • the congestion notification message includes the participating operator identity in which congestion occurs.
  • the MME/SGSN records a congestion notification message, and sends a congestion notification response message to the RAN device.
  • S102 is specifically:
  • the S102a, the MME/SGSN receives the access request sent by the user equipment UE through the RAN device, and the access request includes the participating operator information to be accessed.
  • the MME/SGSN sends an access reject message to the UE according to the participating operator information and the congestion notification message included in the access request.
  • the access request is an attach request in the 4G network; or the access request is a service request initiated by the UE; or the access request is a tracking area update request; or the access request is a routing area update request.
  • the access request is a Packet Data Protocol (PDP) context establishment or modification request initiated by the UE.
  • PDP Packet Data Protocol
  • the access reject message may further include: an access reject reason and an idle cell indication information, where the U E selects an idle cell indicated by the access idle cell indication information.
  • the core network device includes an MME/SGSN, an S-GW, a P-GW/GGSN, and a Policy and Charging Rules Function (hereinafter referred to as PCRF).
  • PCRF Policy and Charging Rules Function
  • the MME/SGSN receives a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested.
  • the MME/SGSN records the congestion notification message, and sends a congestion notification response message to the RAN device.
  • S102 is specifically:
  • IP-Accessive Network IP-CAN
  • the P-GW/GGSN initiates a bearer setup/modification request to the MME/SGSN through the S-GW according to the IP-CAN session modification request, where the bearer setup/modification request includes the IMSI information of the UE/the participating operator identifier of the UE.
  • the MME/SGSN rejects the bearer setup/modification request according to the IMSI information/participating operator identity and the congestion notification message.
  • the MME/SGSN initiates a bearer establishment/modification rejection response to the P-GW/GGSN through the S-GW, and the bearer establishment/modification rejection response includes the rejection reason;
  • the P-GW/GGSN sends an IP-CAN session modification response message to the PCRF, and the IP-CAN session modification response message includes the rejection reason.
  • the method may further include:
  • the MME/SGSN receives a congestion mitigation notification message sent by the RAN device when the participating operator congestion condition mitigation occurs in the RAN device;
  • the MME/SGSN sends a congestion mitigation response message to the RAN device.
  • the core network device includes an MME/SGSN, an S-GW, a P-GW/GGSN, and a PCRF.
  • the S101 is specifically:
  • the MME/SGSN receives a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested.
  • the MME/SGSN sends a bearer update request message to the P-GW/GGSN through the S-GW, where the bearer update request message includes the content of the congestion notification message.
  • the P-GW/GGSN receives the bearer update request message.
  • the P-GW/GGSN records a bearer update request message, and sends a congestion notification response message to the RAN device through the S-GW and the MME/SGSN.
  • S102 is specifically:
  • S102f and PCRF send an IP connection access network IP-CAN session modification request to the P-GW/GGSN.
  • the S102g, the P-GW/GGSN rejects the IP-CAN session modification request according to the type of the congestion notification message and the IP-CAN session modification request.
  • the P-GW/GGSN sends an IP-CAN session modification response message to the PCRF, and the IP-CAN session modification response message includes the rejection reason.
  • the MME/SGSN receives a congestion mitigation notification message sent when the RAN device detects that the participating operator congestion condition has subsided within the RAN device.
  • the MME/SGSN sends a congestion mitigation notification message to the P-GW/GGSN through the S-GW.
  • the P-GW/GGSN sends a congestion mitigation response message to the RAN device through the S-GW and the MME/SGSN.
  • the core network equipment includes S-GW, P-GW/GGSN, and
  • the S101i and the P-GW/GGSN receive, by the S-GW, a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested.
  • S101j the P-GW/GGSN records a congestion notification message, and sends a congestion notification response message to the RAN device through the S-GW.
  • S102 is specifically:
  • PCRF sends an IP-CAN session modification request to the P-GW/GGSN.
  • the S102i the P-GW/GGSN rejects the IP-CAN session modification request according to the type of the congestion notification message and the IP-CAN session modification request.
  • the P-GW/GGSN sends an IP-CAN session modification response message to the PCRF, and the IP-CAN session modification response message includes the rejection reason.
  • the P-GW/GGSN receives, by the S-GW, a congestion mitigation notification message sent by the RAN device when the participating operator congestion condition is reduced in the RAN device.
  • the P-GW/GGSN sends a congestion mitigation response message to the RAN device through the S-GW.
  • the congestion control method provided by the embodiment of the present invention receives, by the core network device, a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested, and the congestion notification message includes the participating operator identifier that is congested. Then, according to the congestion notification message, congestion control is performed on the participating operators corresponding to the participating operator identifiers. Therefore, it is possible to distinguish between different participating operators for congestion control, and to implement accurate and efficient congestion control for specific congestion objects and congestion causes, and to protect the number of connection resources and bandwidth resources of participating operators that are not congested.
  • the RAN device is used as an execution entity as an example. As shown in FIG. 2, the method in this embodiment may include: S201.
  • the resource usage of the quotient detects the occurrence of congestion. Specifically, in the case that an operator shares its network to one or more operators or virtual operators, each virtual operator needs to negotiate RAN resource usage with the operator, for example, assigning a corresponding RAN to each virtual operator. Resource usage ratio, and set the congestion threshold for resource control.
  • the RAN device collects the resource usage of each MVNO in real time.
  • the virtual carrier is determined to be the virtual carrier. Congestion occurs on the RAN device.
  • the cause of the congestion may be that the number of user equipments available to the MVNO in the RAN device is insufficient, or the number of available resources of the MVNO user in the RAN device is insufficient, or the bandwidth resource available to the MVNO in the RAN device may be insufficient.
  • Insufficient number of user equipment resources is simultaneously on the RAN device
  • the virtual carrier user equipment that is connected to the network meets or exceeds the set threshold.
  • the insufficient number of available connections is the bearer of the virtual carrier's user equipment that is connected to the RAN device at the same time.
  • Exceeding the threshold value set for the MVNO; insufficient bandwidth resources means that the bandwidth usage (such as throughput) of all MVNO user equipments on the RAN device meets or exceeds the setting for the virtual operator at the same time. Threshold.
  • the RAN device detects that one or more participating operators are congested, sending a congestion notification message to the core network device related to the participating participating carrier, where the congestion notification message includes the participating operator identifier that is congested.
  • the core network device performs congestion control on the participating operators corresponding to the participating operator identifiers.
  • the congestion notification message further includes any one or combination of the following:
  • Congestion causes of congested participating operators, resource usage of participating operators in congested cells where congestion occurs, other available cell information of neighboring RAN devices of RAN equipment or RAN equipment, and neighboring RANs of RAN equipment or RAN equipment
  • the congestion of the participating operators may be insufficient, for example, the number of UEs available to the participating operators is insufficient, the number of connected resources is insufficient, or the available bandwidth resources are insufficient, and the resource usage of the participating operators in the congested cells is congested.
  • the resource usage of the participating operators corresponding to the operator identifier may be, for example, a user equipment number resource, a connection number resource, or a bandwidth resource.
  • the core network device is the MME/SGSN, and the S202 is specifically:
  • the RAN device When detecting that one or more participating operators are congested, the RAN device sends a congestion notification message to the MME/SGSN related to the participating operator that is involved in the congestion, and the MME/SGSN records the congestion notification message, and according to the congestion notification. The message is used to control the congestion of the participating operators corresponding to the operator identifier.
  • the method further includes:
  • the RAN device receives the congestion notification response message sent by the MME/SGSN.
  • the core network device includes an MME/SGSN, an S-GW, P-GW/ GGSN and PCRF, at this time S202 is specifically:
  • the method at this time further includes: the RAN device receives the congestion notification response message sent by the MME/SGSN.
  • the method further includes:
  • the RAN/SSN When the RAN device detects the congestion of the participating operators in the RAN device, the RAN/SSN sends a congestion mitigation notification message to the MME/SGSN.
  • the RAN device receives the congestion mitigation response message sent by the MME/SGSN.
  • the core network device includes an MME/SGSN, an S-GW, a P-GW/GGSN, and a PCRF.
  • the S202 is specifically:
  • S202c When the RAN device detects that one or more participating operators are congested, sends a congestion notification message to the MME/SGSN related to the participating operator that is congested, and the MME/SGSN uses the S-GW to the P-GW.
  • the /GGSN sends a bearer update request message, and the bearer update request message includes the content of the congestion notification message.
  • the method further includes:
  • the RAN device receives the congestion notification response message sent by the P-GW/GGSN through the S-GW and the MME/SGSN.
  • the MME/SGSN When the RAN device detects the congestion of the participating operators in the RAN device, the MME/SGSN sends a congestion mitigation notification message to the MME/SGSN to send a congestion mitigation notification message to the P-GW/GGSN through the S-GW.
  • the RAN device receives the congestion mitigation response message sent by the P-GW/GGSN through the S-GW and the MME/SGSN.
  • the core network device includes an S-GW, a P-GW/GGSN, and a PCRF.
  • the S202 is specifically:
  • S202d When the RAN device detects that one or more participating operators are congested, sending a congestion notification message to the S-GW related to the participating participating carrier, where the S-GW sends congestion to the P-GW/GGSN. Notification message. At this time, the method further includes:
  • the RAN device receives the congestion notification response message sent by the P-GW/GGSN through the S-GW. Further, it also includes:
  • the RAN device When the RAN device detects the congestion of the participating operators in the RAN device, the RAN device sends a congestion mitigation notification message to the S-GW, and the S-GW sends a congestion mitigation notification message to the P-GW/GGSN.
  • the RAN device receives the congestion mitigation response message sent by the P-GW/GGSN through the S-GW.
  • the congestion control method provided by the embodiment of the present invention detects the occurrence of congestion according to the resource usage of the participating operators by the RAN device.
  • the RAN device detects that one or more participating operators are congested, the RAN device participates in the participation operation with congestion.
  • the Provider-related core network device sends a congestion notification message, and the congestion notification message includes the participating operator identifier for the congestion, and is used by the core network device to perform congestion control on the participating operators corresponding to the participating operator identifier. Therefore, it is possible to distinguish between different participating operators for congestion control, and to implement accurate and efficient congestion control for specific congestion objects and congestion reasons, and to protect the number of connection resources and bandwidth resources of participating operators that are not congested.
  • Embodiment 3 is a signaling interaction diagram of Embodiment 3 of a congestion control method according to the present invention.
  • the core network device in this embodiment is an MME/SGSN, and the method in this embodiment may include:
  • the RAN device detects the occurrence of congestion according to resource usage of the participating operators. Specifically, for example, the RAN device collects the resource usage of each participating operator MVNO in real time, and when a virtual operator increases the resource usage on the RAN device to meet or exceed the preset congestion threshold of the MVNO, It is determined that the virtual operator is congested on the RAN device.
  • S302 When the RAN device detects that one or more participating operators are congested, sending a congestion notification message to the MME/SGSN related to the participating operator that is congested, and the congestion notification message includes the participating operator identifier that is congested.
  • the RAN device selects a corresponding MME/SGSN to send a congestion notification according to the identifier of the MVNO in which congestion occurs (such as MVNO ID, IMSI number segment, Public Land Mobile Network (PLMN) ID, etc.) Message.
  • RAN may also send a congestion notification message to all MMEs/SGSNs connected to it.
  • the congestion notification message also includes any one or combination of the following:
  • Congestion causes of congested participating operators, resource usage of participating operators in congested cells where congestion occurs, other available cell information of neighboring RAN devices of RAN equipment or RAN equipment, and neighboring RANs of RAN equipment or RAN equipment The resource usage of participating operators corresponding to the operator identifier in other available cells of the device.
  • the MME/SGSN receives the congestion notification message, and records the congestion notification message.
  • the MME/SGSN sends a congestion notification response message to the RAN device.
  • the UE sends an access request to the RAN device, where the access request includes the participating operator information to be accessed.
  • the RAN device forwards the received access request to the MME/SGSN.
  • the MME/SGSN sends an access reject message to the UE according to the participating operator information and the congestion notification message included in the access request.
  • the access request is an attach request in the 4G network; or the access request is a service request initiated by the UE; or the access request is a tracking area update request; or the access request is a routing area update request.
  • the access request is a primary/secondary packet data protocol PDP context establishment or modification request initiated by the UE.
  • the MME/SGSN determines that the user equipment belongs to congestion according to the MVNO information included in the access request message. In the case of the virtual operator, the MME/SGSN rejects the access request of the user equipment according to the above information.
  • the congestion type included in the congestion notification message sent by the RAN device to the MME is the congestion caused by the connection resource exceeding the preset value.
  • the MVNO information included in the incoming request message determines that the user equipment belongs to the virtual operator in which the congestion occurs, and the access type of the user is attached, and the MME rejects the attach request of the user equipment.
  • the access reject message may further include: an access reject reason and an idle cell indication information, where the UE selects an idle cell indicated by the access idle cell indication information.
  • the access rejection reason is that the virtual operator generates a user equipment number resource or a connection resource resource in the RAN device. Congestion caused by the restriction, and other available cells of the user equipment may be indicated to indicate that the user equipment is accessing from the idle cell. The user equipment is instructed to access from the idle cell, and the idle cell information may be sent to the user equipment through a non-access stratum (NAS) message, and the user equipment selects a suitable cell to access.
  • NAS non-access stratum
  • the idle cell information may also be sent to the RAN device through the system message (S1) access point (AP) message, and the RAN device instructs the user equipment to select an appropriate cell access.
  • S1 system message
  • AP access point
  • the idle cell information may also be sent to the RAN device through the RAN AP message, and the RAN device instructs the user equipment to select an appropriate cell access.
  • the idle cell information may also be sent to the RAN device through the base station subsystem (BSS) AP message, and the RAN device instructs the user equipment to select an appropriate cell access.
  • BSS base station subsystem
  • the RAN device determines that the congestion status of the MVNO is obtained, for example, when the occupied resource (connection number resource/bandwidth resource) of the MVNO in the RAN device that is congested is gradually reduced to reach or lower than the congestion mitigation threshold preset by the MVNO. ease.
  • the RAN device may send a congestion mitigation notification message to all MMEs/SGSNs connected thereto; or may only send a congestion mitigation notification message to the MME/SGSN related to the MVNO in which congestion occurs, for example, the RAN device identifies the MVNO according to the congestion ( The MME/SGSN is selected to send a congestion mitigation notification message, such as MVNO ID, IMSI number segment, PLMN ID, and the like.
  • the MME/SGSN sends a congestion mitigation response message to the RAN device.
  • Embodiment 4 is a signaling interaction diagram of Embodiment 4 of a congestion control method according to the present invention.
  • the core network device in this embodiment includes an MME/SGSN, an S-GW, a P-GW/GGSN, and a PCRF.
  • the implementation is as shown in FIG. 4, the implementation is as shown in FIG.
  • the method of the example may include:
  • S401 to S404 in this embodiment are the same as those in steps S301 to S304 in the third embodiment shown in FIG. 3, and details are not described herein again.
  • the PCRF sends an IP-CAN session modification request to the P-GW/GGSN.
  • the P-GW/GGSN initiates a bearer setup/modification request to the MME/SGSN by using the S-GW according to the IP-CAN session modification request, where the bearer setup/modification request includes the IMSI information of the UE/the participating operator identifier of the UE.
  • the MME/SGSN rejects the bearer setup/modification request according to the IMSI information/participating operator identifier and the congestion notification message.
  • the congestion cause included in the congestion notification message sent by the RAN device to the MME/SGSN is that the connection resource and/or the bandwidth resource exceeds the preset value, and the MME/SGSN participates in the carrier according to the IMSI information or
  • the identifier determines that the UE belongs to the participating operator that has generated the above congestion. Perform the following actions according to different situations:
  • the MME/SGSN rejects the bearer setup request.
  • the MME/SGSN When the congestion cause is insufficient for the bandwidth, the MME/SGSN receives the request message type as the bearer update request, and the bearer update needs to increase the bandwidth of the bearer; or the MME/SGSN receives the request message type as the bearer new request, then the MME /SGSN rejects the bearer update request.
  • the MME/SGSN initiates a bearer setup/modification rejection response to the P-GW/GGSN through the S-GW, and the bearer setup/modification rejection response includes a reject reason.
  • the P-GW/GGSN sends an IP-CAN session modification response message to the PCRF, and the IP-CAN session modification response message includes the rejection reason.
  • the MME/SGSN initiates a bearer setup/modification rejection response to the P-GW/GGSN through the S-GW according to the decision made in the foregoing process.
  • the response may include the reject cause as the MVNO, the congestion type is the connection number resource, and/or The bandwidth resource exceeds the preset congestion.
  • the P-GW/GGSN sends an IP-CAN session modification response message to the PCRF, and the message may include a rejection.
  • the reason is that the congestion type of the MVNO is the connection number resource and/or the bandwidth resource exceeds the preset value.
  • S410 Send a congestion mitigation notification message to the MME/SGSN when the RAN device detects that the participating operator congestion condition is congested in the RAN device.
  • the RAN device determines that the congestion status of the MVNO is obtained, for example, when the occupied resource (connection number resource/bandwidth resource) of the MVNO in the RAN device that is congested is gradually reduced to reach or lower than the congestion mitigation threshold preset by the MVNO. ease.
  • the RAN device may send a congestion mitigation notification message to all MMEs/SGSNs connected thereto; or may only send a congestion mitigation notification message to the MME/SGSN related to the MVNO in which congestion occurs, for example, the RAN device identifies the MVNO according to the congestion ( The MME/SGSN is selected to send a congestion mitigation notification message, such as MVNO ID, IMSI number segment, PLMN ID, and the like.
  • the MME/SGSN sends a congestion mitigation response message to the RAN device.
  • FIG. 5 is a signaling interaction diagram of Embodiment 5 of a congestion control method according to the present invention.
  • the core in this embodiment The network device includes an MME/SGSN, an S-GW, a P-GW/GGSN, and a PCRF. As shown in FIG. 5, the method in this embodiment may include:
  • the RAN device detects the occurrence of congestion according to the resource usage of the participating operators. Specifically, for example, the RAN device collects the resource usage of each participating operator MVNO in real time, and when a virtual operator increases the resource usage on the RAN device to meet or exceed the preset congestion threshold of the MVNO, It is determined that the virtual operator is congested on the RAN device.
  • the RAN device detects that one or more participating operators are congested, sending a congestion notification message to the MME/SGSN related to the participating operator that is congested, and the congestion notification message includes the participating operator identifier that is congested.
  • the RAN device selects the corresponding MME/SGSN to send a congestion notification message according to the identifier of the MVNO in which the congestion occurs (e.g., MVNO ID, IMSI number segment, PLMN ID, etc.).
  • the RAN device can also send a congestion notification message to all MMEs/SGSNs connected to it.
  • the congestion notification message also includes any one or combination of the following:
  • Congestion causes of congested participating operators, resource usage of participating operators in congested cells where congestion occurs, other available cell information of neighboring RAN devices of RAN equipment or RAN equipment, and neighboring RANs of RAN equipment or RAN equipment The resource usage of participating operators corresponding to the operator identifier in other available cells of the device.
  • the MME/SGSN sends a bearer update request message to the P-GW/GGSN through the S-GW, where the bearer update request message includes the content of the congestion notification message.
  • the P-GW/GGSN receives and records a bearer update request message.
  • the P-GW/GGSN sends a congestion notification response message to the RAN device by using the S-GW and the MME/SGSN.
  • the PCRF sends an IP-CAN session modification request to the P-GW/GGSN.
  • the P-GW/GGSN rejects the IP-CAN session modification request according to the type of the congestion notification message and the IP-CAN session modification request.
  • the P-GW/GGSN sends an IP-CAN session modification response message to the PCRF, where the IP-CAN session modification response message includes a rejection reason.
  • the RAN device determines that the congestion status of the MVNO is obtained, for example, when the occupied resource (connection number resource/bandwidth resource) of the MVNO in the RAN device that is congested is gradually reduced to reach or lower than the congestion mitigation threshold preset by the MVNO. ease.
  • the RAN device may send a congestion mitigation notification message to all MMEs/SGSNs connected thereto; or may only send a congestion mitigation notification message to the MME/SGSN related to the MVNO in which congestion occurs, for example, the RAN device identifies the MVNO according to the congestion ( The MME/SGSN is selected to send a congestion mitigation notification message, such as MVNO ID, IMSI number segment, PLMN ID, and the like.
  • the MME/SGSN sends a congestion mitigation notification message to the P-GW/GGSN through the S-GW.
  • the P-GW/GGSN sends a congestion mitigation response message to the RAN device by using the S-GW and the MME/SGSN.
  • FIG. 6 is a signaling interaction diagram of Embodiment 6 of the congestion control method of the present invention.
  • the core network device in this embodiment includes an S-GW, a P-GW/GGSN, and a PCRF.
  • the method in this embodiment may be Includes:
  • the RAN device detects the occurrence of congestion according to the resource usage of the participating operators. Specifically, for example, the RAN device collects the resource usage of each participating operator MVNO in real time, and when a virtual operator increases the resource usage on the RAN device to meet or exceed the preset congestion threshold of the MVNO, It is determined that the virtual operator is congested on the RAN device.
  • the RAN device detects that one or more participating operators are congested, sending a congestion notification message to the S-GW related to the participating operator that is congested, where the congestion notification message includes the participating operator identifier that is congested.
  • the RAN device selects the corresponding MME/SGSN to send a congestion notification message according to the identifier of the MVNO in which the congestion occurs (e.g., MVNO ID, IMSI number segment, PLMN ID, etc.).
  • the RAN device can also send a congestion notification message to all MMEs/SGSNs connected to it.
  • the congestion notification message also includes any one or combination of the following:
  • Congestion causes of congested participating operators, resource usage of participating operators in congested cells where congestion occurs, other available RAN equipment of RAN equipment or RAN equipment
  • the cell information and the resource usage of the participating operators corresponding to the operator identity in the other available cells of the RAN device or the neighboring RAN device of the RAN device.
  • S603 The S-GW forwards the congestion notification message to the P-GW/GGSN.
  • the P-GW/GGSN receives and records the congestion notification message.
  • the P-GW/GGSN sends a congestion notification response message to the RAN device through the S-GW.
  • the PCRF sends an IP-CAN session modification request to the P-GW/GGSN.
  • the P-GW/GGSN rejects the IP-CAN session modification request according to the type of the congestion notification message and the IP-CAN session modification request.
  • the P-GW/GGSN sends an IP-CAN session modification response message to the PCRF, where the IP-CAN session modification response message includes a rejection reason.
  • the RAN device sends a congestion mitigation notification message to the P-GW/GGSN through the S-GW when the RAN device detects congestion of the participating operators in the RAN device.
  • the P-GW/GGSN sends a congestion mitigation response message to the RAN device by using the S-GW.
  • the congestion mitigation notification message includes at least one of the following information: 1) an MVNO identifier for which the congestion condition is mitigated (for example, one or more MVNOs for identifying congestion, which may be an MVNO identifier, or The IMSI number segment corresponding to the MVNO, etc.; 2) The congestion cause of the MVNO in which the congestion condition is alleviated.
  • FIG. 7 is a schematic structural diagram of Embodiment 1 of a core network device according to the present invention.
  • the apparatus in this embodiment may include: a receiving module 11 and a processing module 12, where the receiving module 11 is configured to receive the RAN device to detect a certain A congestion notification message sent when one or more participating operators are congested, and the congestion notification message includes the participating operator identifier in which congestion occurs.
  • the processing module 12 is configured to perform congestion control on the participating operators corresponding to the participating operator identifiers according to the congestion notification message.
  • the congestion notification message also includes any one or combination of the following:
  • Congestion causes of congested participating operators, resource usage of participating operators in congested cells where congestion occurs, other available cell information of neighboring RAN devices of RAN equipment or RAN equipment, and neighboring RANs of RAN equipment or RAN equipment The resource usage of participating operators corresponding to the operator identifier in other available cells of the device.
  • the MME/SGSN includes: a receiving module, a first sending module, and a first processing module, where the first receiving module is configured to receive
  • the RAN device detects a congestion notification message sent when one or more participating operators experience congestion.
  • the first sending module is configured to record a congestion notification message and send a congestion notification response message to the RAN device.
  • the first receiving module is further configured to receive an access request sent by the user equipment UE by using the RAN device, where the access request includes the participating operator information to be accessed.
  • the first processing module is configured to send an access reject message to the UE according to the participating operator information and the congestion notification message included in the access request.
  • the access request is an attach request, or the access request is a service request initiated by the UE; or the access request is a tracking area update request; or the access request is a routing area update request.
  • the access request is a primary/secondary PDP context establishment or modification request initiated by the UE.
  • the access reject message further includes: an access reject reason and an idle cell indication information, where the UE selects an idle cell indicated by the access idle cell indication information.
  • the core network device includes an MME/SGSN and an S-GW.
  • the MME/SGSN includes: a second receiving module and a second sending module, where the second receiving module is configured to receive a congestion notification sent by the RAN device when detecting that one or more participating operators are congested. Message.
  • the second sending module is configured to record a congestion notification message and send a congestion notification response message to the RAN device.
  • the PCRF includes a third sending module, and the third sending module is configured to send an IP connection access network IP-CAN session modification request to the P-GW/GGSN.
  • the P-GW/GGSN includes a fourth sending module, and the fourth sending module is configured to initiate a bearer setup/modification request to the MME/SGSN by using the S-GW according to the IP-CAN session modification request, where the bearer setup/modification request includes the international mobile of the UE
  • the user identifies the IMSI information/the participating operator identity of the UE.
  • the MME/SGSN further includes: a second processing module, configured to reject the bearer setup/modification request according to the IMSI information/participating operator identity and the congestion notification message.
  • the second sending module is further configured to: initiate, by the S-GW, a bearer setup/modification rejection response to the P-GW/GGSN, and the bearer setup/modification reject response includes a reject reason.
  • the fourth sending module is further configured to: send an IP-CAN session modification response message to the PCRF, The reason for rejection is included in the IP-CAN session modification response message.
  • the second receiving module is further configured to: receive, by the RAN device, a congestion mitigation notification message sent when the participating operator congestion condition mitigation occurs in the RAN device.
  • the second sending module is further configured to send a congestion mitigation response message to the RAN device.
  • the MME/SGSN when the core network device includes the MME/SGSN, the S-GW, the P-GW/GGSN, and the PCRF, the MME/SGSN includes: a third receiving module and a fifth sending module, where the third receiving module is used.
  • the fifth sending module is configured to send a bearer update request message to the P-GW/GGSN by using the S-GW, where the bearer update request message includes the content of the congestion notification message.
  • the P-GW/GGSN includes: a fourth receiving module and a sixth sending module, where the fourth receiving module is configured to receive a bearer update request message.
  • the sixth sending module is configured to record the bearer update request message, and send a congestion notification response message to the RAN device by using the S-GW and the MME/SGSN.
  • the PCRF includes a seventh sending module, and the seventh sending module is configured to send an IP connection access network IP-CAN session modification request to the P-GW/GGSN.
  • the P-GW/GGSN further includes: a third processing module, configured to reject the IP-CAN session modification request according to the type judgment of the congestion notification message and the IP-CAN session modification request.
  • the sixth sending module is further configured to: send an IP-CAN session modification response message to the PCRF, where the IP-CAN session modification response message includes a rejection reason.
  • the third receiving module is further configured to receive a congestion mitigation notification message sent when the RAN device detects that the participating operator congestion condition is relieved within the RAN device.
  • the fifth sending module is further configured to send a congestion mitigation notification blank E to the P-GW/GGSN through the S-GW.
  • the sixth sending module is further configured to send a congestion mitigation response message to the RAN device by using the S-GW and the MME/SGSN.
  • the P-GW/GGSN when the core network device includes the S-GW, the P-GW/GGSN, and the PCRF, the P-GW/GGSN includes: a fifth receiving module and a seventh sending module, where the fifth receiving module is configured to pass
  • the S-GW receives a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested.
  • the seventh sending module is configured to record a congestion notification message, and A congestion notification response message is sent to the RAN device through the S-GW.
  • the PCRF includes: an eighth sending module, and the eighth sending module is configured to send an IP-CAN session modification request to the P-GW/GGSN.
  • the P-GW/GGSN includes: a fourth processing module, where the fourth processing module is configured to reject the IP-CAN session modification request according to the type of the congestion notification message and the IP-CAN session modification request.
  • the seventh sending module is further configured to: send an IP-CAN session modification response message to the PCRF, where the IP-CAN session modification response message includes a rejection reason.
  • the fifth receiving module is further configured to: receive, by the S-GW, a congestion mitigation notification message sent by the RAN device when the participating operator congestion condition is reduced in the RAN device.
  • the seventh sending module is further configured to: send a congestion mitigation response message to the RAN device by using the S-GW.
  • the device in this embodiment may be used to implement the technical solution of the method embodiment shown in FIG. 1.
  • the implementation principle is similar, and details are not described herein again.
  • the core network device receives, by the receiving module, a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested, and the congestion notification message includes the participating operator identifier that is congested.
  • the processing module then performs congestion control on the participating operators corresponding to the participating operator identifiers according to the congestion notification message. Therefore, it is possible to distinguish between different participating operators for congestion control, and to implement accurate and efficient congestion control for specific congestion objects and congestion causes, and to protect the number of connection resources and bandwidth resources of participating operators that do not have congestion.
  • FIG. 8 is a schematic structural diagram of Embodiment 1 of a RAN device according to the present invention.
  • the device in this embodiment may include: a detecting module 21 and a sending module 22, where the detecting module 21 is configured to use resources according to participating operators. The situation detects the occurrence of congestion.
  • the sending module 22 is configured to: when the detecting module 21 detects that one or more participating operators are congested, send a congestion notification message to the core network device related to the participating participating carrier, where the congestion notification message includes the participating operation in which congestion occurs.
  • the quotient identifier is used by the core network device to perform congestion control on the participating operators corresponding to the operator identifier.
  • the congestion notification message also includes any one or combination of the following:
  • Congestion causes of congested participating operators, resource usage of participating operators in congested cells where congestion occurs, other available RAN equipment of RAN equipment or RAN equipment
  • the cell information and the resource usage of the participating operators corresponding to the operator identity in the other available cells of the RAN device or the neighboring RAN device of the RAN device.
  • the sending module 22 is configured to:
  • the detecting module 21 When the detecting module 21 detects that one or more participating operators are congested, sending a congestion notification message to the MME/SGSN related to the participating operator that is causing the congestion, for the MME/SGSN to record the congestion notification message, and according to the congestion notification The message is used to control the congestion of the participating operators corresponding to the operator identifier.
  • the RAN device further includes: a first receiving module, where the first receiving module is configured to receive a congestion notification response message sent by the MME/SGSN.
  • the sending module 22 is configured to:
  • the detecting module 21 When the detecting module 21 detects that one or more participating operators are congested, it sends a congestion notification message to the MME/SGSN related to the participating participating carrier for the MME/SGSN to record the congestion notification message.
  • the RAN device further includes: a second receiving module, where the second receiving module is configured to receive a congestion notification response message sent by the MME/SGSN.
  • the sending module 22 is further configured to:
  • the congestion mitigation notification message is sent to the MME/SGSN.
  • the first receiving module or the second receiving module is further configured to: receive a congestion mitigation response message sent by the MME/SGSN.
  • the sending module 22 is configured to:
  • the detecting module 21 detects that one or more participating operators are congested, sending a congestion notification message to the MME/SGSN related to the participating participating carrier for the MME/SGSN to the P-GW through the S-GW.
  • the GGSN sends a bearer update request message, where the bearer update request message includes the content of the congestion notification message;
  • the RAN device further includes: a third receiving module, configured to receive a congestion notification response message sent by the P-GW/GGSN through the S-GW and the MME/SGSN. Further, the sending module 22 is also used to:
  • the congestion mitigation notification message is sent to the MME/SGSN, and the MME/SGSN sends a congestion mitigation notification message to the P-GW/GGSN through the S-GW. .
  • the third receiving module is further configured to receive a congestion mitigation response message sent by the P-GW/GGSN through the S-GW and the MME/SGSN.
  • the sending module 22 is configured to:
  • the detecting module 21 When the detecting module 21 detects that one or more participating operators are congested, it sends a congestion notification message to the S-GW related to the participating participating carrier, and the S-GW sends a congestion notification to the P-GW/GGSN. Message.
  • the RAN device also includes:
  • the fourth receiving module is configured to receive a congestion notification response message sent by the P-GW/GGSN through the S-GW.
  • sending module 22 is also used to:
  • the congestion mitigation notification message is sent to the S-GW, and the S-GW sends a congestion mitigation notification message to the P-GW/GGSN.
  • the fourth receiving module is further configured to receive a congestion mitigation response message sent by the P-GW/GGSN through the S-GW.
  • the device in this embodiment may be used to implement the technical solution of the method embodiment shown in FIG. 2, and the implementation principle and the technical effect are similar, and details are not described herein again.
  • the RAN device provided by the embodiment of the present invention detects the occurrence of congestion according to the resource usage of the participating operators by the detecting module.
  • the sending module participates in the congestion.
  • the carrier-related core network device sends a congestion notification message, and the congestion notification message includes the participating operator identifier that is congested, and is used by the core network device to perform congestion control on the participating operators corresponding to the participating operator identifier. Therefore, it is possible to distinguish between different participating operators for congestion control, and to implement accurate and efficient congestion control for specific congestion objects and congestion causes, and to protect the connection resources and bandwidth resources of the participating operators that do not have congestion.
  • the communication system provided by the embodiment of the present invention includes the core network device shown in FIG. 7 and the RAN device shown in FIG. 8.
  • FIG. 9 is a schematic structural diagram of Embodiment 2 of a core network device according to the present invention.
  • the apparatus in this embodiment may include: a receiver 31 and a processor 32, where the receiver 31 is configured to receive a RAN device to detect a certain A congestion notification message sent when one or more participating operators are congested, and the congestion notification message includes a participating operator identifier in which congestion occurs.
  • the processor 32 is configured to perform congestion control on the participating operators corresponding to the participating operator identifiers according to the congestion notification message.
  • the congestion notification message also includes any one or combination of the following:
  • Congestion causes of congested participating operators, resource usage of participating operators in congested cells where congestion occurs, other available cell information of neighboring RAN devices of RAN equipment or RAN equipment, and neighboring RANs of RAN equipment or RAN equipment The resource usage of participating operators corresponding to the operator identifier in other available cells of the device.
  • the MME/SGSN when the core network device is the MME/SGSN, the MME/SGSN includes: a first receiver, a first sending And the first processor, where the first receiver is configured to receive a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested.
  • the first transmitter is configured to record a congestion notification message and send a congestion notification response message to the RAN device.
  • the first receiver is further configured to receive an access request sent by the user equipment UE by using the RAN device, where the access request includes the participating operator information to be accessed.
  • the first processor is configured to send an access reject message to the UE according to the participating operator information and the congestion notification message included in the access request.
  • the access request is an attach request, or the access request is a service request initiated by the UE; or the access request is a tracking area update request; or the access request is a routing area update request.
  • the access request is a primary/secondary PDP context establishment or modification request initiated by the UE.
  • the access reject message further includes: an access reject reason and an idle cell indication information, where the UE selects an idle cell indicated by the access idle cell indication information.
  • the MME/SGSN when the core network device includes an MME/SGSN, an S-GW, a P-GW/GGSN, and a PCRF, the MME/SGSN includes: a second receiver and a second transmitter, where the second receiver is configured to: The receiving RAN device detects that one or more participating operators are congested Congestion notification message sent at the time. The second transmitter is configured to record a congestion notification message and send a congestion notification response message to the RAN device.
  • the PCRF includes a third transmitter for transmitting an IP connection access network IP-CAN session modification request to the P-GW/GGSN.
  • the P-GW/GGSN includes a fourth transmitter, and the fourth transmitter is configured to initiate a bearer setup/modification request to the MME/SGSN through the S-GW according to the IP-CAN session modification request, where the bearer setup/modification request includes the UE's international mobile subscriber Identify the participating operator identification of the IMSI information/UE.
  • the MME/SGSN further includes: a second processor, the second processor is configured to reject the bearer setup/modification request according to the IMSI information/participating operator identity and the congestion notification message.
  • the second transmitter is further configured to: initiate, by the S-GW, a bearer setup/modification rejection response to the P-GW/GGSN, and the bearer setup/modification rejection response includes a reject reason.
  • the fourth transmitter is further configured to: send an IP-CAN session modification response message to the PCRF, where the IP-CAN session modification response message includes a rejection reason.
  • the second receiver is further configured to: receive, by the RAN device, a congestion mitigation notification message sent when the participating operator congestion condition mitigation occurs in the RAN device.
  • the second transmitter is further configured to send a congestion mitigation response message to the RAN device.
  • the MME/SGSN when the core network device includes an MME/SGSN, an S-GW, a P-GW/GGSN, and a PCRF, the MME/SGSN includes: a third receiver and a fifth transmitter, where the third receiver is configured to: The receiving RAN device detects a congestion notification message sent when one or more participating operators are congested.
  • the fifth transmitter is configured to send a bearer update request message to the P-GW/GGSN by using the S-GW, where the bearer update request message includes the content of the congestion notification message.
  • the P-GW/GGSN includes: a fourth receiver and a sixth transmitter, wherein the fourth receiver is configured to receive a bearer update request message.
  • the sixth transmitter is configured to record a bearer update request message, and send a congestion notification response message to the RAN device through the S-GW and the MME/SGSN.
  • the PCRF includes a seventh transmitter for transmitting an IP connection access network IP-CAN session modification request to the P-GW/GGSN.
  • the P-GW/GGSN further includes: a third processor, the third processor configured to reject the IP-CAN session modification request according to the type judgment of the congestion notification message and the IP-CAN session modification request.
  • the sixth transmitter is further configured to: send an IP-CAN session modification response message to the PCRF, where the IP-CAN session modification response message includes a rejection reason.
  • the third receiver is further configured to receive a congestion mitigation notification message sent when the RAN device detects that the participating operator congestion condition in the RAN device is relieved.
  • the fifth transmitter is further configured to send a congestion mitigation notification message to the P-GW/GGSN through the S-GW.
  • the sixth transmitter is further configured to send a congestion mitigation response message to the RAN device by using the S-GW and the MME/SGSN.
  • the P-GW/GGSN when the core network device includes the S-GW, the P-GW/GGSN, and the PCRF, the P-GW/GGSN includes: a fifth receiver and a seventh transmitter, and the fifth receiver is configured to pass the S
  • the GW receives the congestion notification message sent by the RAN device when it detects that one or more participating operators are congested.
  • the seventh transmitter is configured to record a congestion notification message, and send a congestion notification response message to the RAN device through the S-GW.
  • the PCRF includes an eighth transmitter for transmitting an IP-CAN session modification request to the P-GW/GGSN.
  • the P-GW/GGSN includes: a fourth processor, the fourth processor configured to reject the IP-CAN session modification request according to the type of the congestion notification message and the IP-CAN session modification request.
  • the seventh transmitter is further configured to: send an IP-CAN session modification response message to the PCRF, and the IP-CAN session modification response message includes a rejection reason.
  • the fifth receiver is further configured to: receive, by the S-GW, a congestion mitigation notification message sent by the RAN device when the participating operator congestion condition mitigation occurs in the RAN device.
  • the seventh transmitter is further configured to: send a congestion mitigation response message to the RAN device by using the S-GW.
  • the device in this embodiment may be used to implement the technical solution of the method embodiment shown in FIG. 1.
  • the implementation principle is similar, and details are not described herein again.
  • the core network device receives, by the receiver, a congestion notification message that is sent when the RAN device detects that one or more participating operators are congested, and the congestion notification message includes the participating operator identifier that is congested.
  • the processor then performs congestion control on the participating operators corresponding to the participating operator identifiers according to the congestion notification message. Therefore, it is possible to distinguish between different participating operators for congestion control, and to implement accurate and efficient congestion control for specific congestion objects and congestion causes, and to protect the number of connection resources and bandwidth resources of participating operators that are not congested.
  • the apparatus of the embodiment may include: a processor 41 and a transmitter 42, wherein the processor 41 is configured to detect the occurrence of congestion according to resource usage of the participating operators.
  • the transmitter 42 is configured to: when the processor 41 detects that one or more participating operators are congested, send a congestion notification message to the core network device related to the participating participating carrier, where the congestion notification message includes the participating operation in which congestion occurs.
  • the quotient identifier is used by the core network device to perform congestion control on the participating operators corresponding to the operator identifier.
  • the congestion notification message also includes any one or combination of the following:
  • Congestion causes of congested participating operators, resource usage of participating operators in congested cells where congestion occurs, other available cell information of neighboring RAN devices of RAN equipment or RAN equipment, and neighboring RANs of RAN equipment or RAN equipment The resource usage of participating operators corresponding to the operator identifier in other available cells of the device.
  • the transmitter 42 is configured to:
  • the processor 41 When the processor 41 detects that one or more participating operators are congested, it sends a congestion notification message to the MME/SGSN related to the participating operator that is congested, and the MME/SGSN records the congestion notification message, and according to the congestion notification. The message is used to control the congestion of the participating operators corresponding to the operator identifier.
  • the RAN device further includes: a first receiver, the first receiver configured to receive a congestion notification response message sent by the MME/SGSN.
  • the core network device includes an MME/SGSN, an S-GW,
  • the transmitter 42 is used to:
  • the processor 41 When the processor 41 detects that one or more participating operators are congested, it sends a congestion notification message to the MME/SGSN related to the participating participating carrier for the MME/SGSN to record the congestion notification message.
  • the RAN device further includes: a second receiver, the second receiver is configured to receive a congestion notification response message sent by the MME/SGSN.
  • the transmitter 42 is further configured to:
  • the processor 41 When the processor 41 detects the participating operator congestion condition mitigation in which the RAN device is congested, it sends a congestion mitigation notification message to the MME/SGSN.
  • the first receiver or the second receiver is further configured to: receive congestion mitigation sent by the MME/SGSN Response message.
  • the transmitter 42 is configured to:
  • the processor 41 When the processor 41 detects that one or more participating operators are congested, it sends a congestion notification message to the MME/SGSN related to the participating participating carrier for the MME/SGSN to pass the S-GW to the P-GW/
  • the GGSN sends a bearer update request message, where the bearer update request message includes the content of the congestion notification message;
  • the RAN device further includes: a third receiver, configured to receive a congestion notification response message sent by the P-GW/GGSN through the S-GW and the MME/SGSN.
  • transmitter 42 is also used to:
  • the MME/SGSN When the processor 41 detects that the participating operator congestion condition mitigation occurs in the RAN device, the MME/SGSN sends a congestion mitigation notification message for the MME/SGSN to send a congestion mitigation notification message to the P-GW/GGSN through the S-GW. .
  • the third receiver is further configured to receive a congestion mitigation response message sent by the P-GW/GGSN through the S-GW and the MME/SGSN.
  • the transmitter 42 is configured to:
  • the processor 41 When the processor 41 detects that one or more participating operators are congested, it sends a congestion notification message to the S-GW related to the participating participating carrier, and the S-GW sends a congestion notification to the P-GW/GGSN. Message.
  • the RAN device also includes:
  • a fourth receiver configured to receive a congestion notification response message sent by the P-GW/GGSN through the S-GW.
  • transmitter 42 is also used to:
  • the processor 41 When the processor 41 detects that the participating operator congestion condition mitigation occurs in the RAN device, it sends a congestion mitigation notification message to the S-GW for the S-GW to send a congestion mitigation notification message to the P-GW/GGSN.
  • the fourth receiver is further configured to receive a congestion mitigation response message sent by the P-GW/GGSN through the S-GW.
  • the device of this embodiment may be used to implement the technical solution of the method embodiment shown in FIG. 2,
  • the implementation principle is similar to the technical effect, and will not be described here.
  • the RAN device detects the occurrence of congestion according to the resource usage of the participating operators by the processor.
  • the sender participates in the congestion.
  • the carrier-related core network device sends a congestion notification message, and the congestion notification message includes the participating operator identifier that is congested, and is used by the core network device to perform congestion control on the participating operators corresponding to the participating operator identifier. Therefore, it is possible to distinguish between different participating operators for congestion control, and to implement accurate and efficient congestion control for specific congestion objects and congestion reasons, and to protect the number of connection resources and bandwidth resources of participating operators that are not congested.
  • the communication system provided by the embodiment of the present invention includes the core network device shown in FIG. 9 and the RAN device shown in FIG.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, i.e., may be located in one place, or may be distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a hardware plus software functional unit.
  • the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
  • the software functional unit is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform the method of various embodiments of the present invention. Partially Step.
  • the foregoing storage medium includes: a U disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明提供一种拥塞控制方法、装置及系统。该方法包括:核心网设备接收无线接入网(RAN)设备检测到某一个或多个参与运营商发生拥塞时发送的拥塞通知消息,拥塞通知消息包括发生拥塞的参与运营商标识(S101),参与运营商为移动虚拟网络运营商(MVNO)或共享运营商网络的运营商。然后,核心网设备根据拥塞通知消息,对参与运营商标识对应的参与运营商进行拥塞控制(S102)。采用该方法,可以区分不同的参与运营商进行拥塞控制,实现了针对特定的拥塞对象以及拥塞原因进行精确高效的拥塞控制,同时保护了未发生拥塞的参与运营商的连接数资源以及带宽资源。

Description

拥塞控制方法、 装置及系统
技术领域
本发明实施例涉及通信技术领域, 尤其涉及一种拥塞控制方法、 装置 及系统。 背景技术
随着全球电信市场开放格局的形成, 运营商竞争的焦点集中在对用户 的争夺上, 因此, 更优质的服务、 更多彩的业务成为运营商竞争的砝码。 网络投资是运营商最主要的支出, 尤其是在移动网络流量激增的当下, 传 统移动网络运营商要投入巨额的资金来建设、 升级网络, 相比之下, 租用 网络即可推出业务的模式具有节约成本投入的优势, 移动虚拟网络运营商 ( Mobile Virtual Network Operator, 以下简称: MVNO) 的出现, 给网络 的运营提供了新的模式, MVNO通常指本身没有运营牌照或者发展规模受 到限制, 需要利用已有的基础移动运营商(Mobile Network Operator, 以下 简称: MNO) 的网络发展自己的用户, 并向用户提供业务的运营者。 对于 本身具有运营牌照的移动网络运营商也可以通过租用其他移动网络运营 商的网络 (一般也称之为网络共享) 来发展自己的用户和提供业务, 这也 可以看作是 MVNO。在成熟的电信市场上, 越来越多的 MVNO涌现出来。
随着 MVNO的引入, 一个 MNO的网络可能为多个 MVNO服务, 该 MNO需要针对不同的 MVNO做好网络资源的管理,例如为不同的 MVNO 分配不同的无线接入资源、 最大用户数、 最大承载 (Bearer) /分组数据协 议(Packet Data Protocol, 以下简称: PDP ) 资源、 可用的业务等。 网络资 源可以通过数量来表示, 例如某 MVNO的最大用户数 1000; 也可以采用 资源占用比来表示, 例如某 MVNO可使用 40%的移动网络的无线接入资 源等。 MNO根据上述的网络资源管理的方法, 对不同 MVNO的网络资源 进行管理和控制, 以确保服务的所有 MVNO都有足够的网络资源可用。 然而, 当某个 MVNO 的资源使用达到预设值 (最大数据, 或最大百分比 等) , 就会导致该 MVNO 的网络资源使用发生拥塞。 该拥塞可能是某一 个或多个 MVNO的接入用户设备 (User Equipment, 以下简称: UE) 过 多, 导致占用了过多的资源, 而其他 MVNO 的资源使用正常; 该拥塞也 可能是所有 MVNO的 UE占用资源过多, 导致网络设备发生设备拥塞。如 何针对不同的 MVNO进行相应的拥塞控制, 是一个需要解决的问题。
现有的一种解决方案是: 无线接入网 (Radio access network, 以下简 称: RAN) 节点上报小区拥塞信息给核心网设备, 拥塞信息可以包括拥 塞的小区标识 (cell ID) , 核心网设备接收到该拥塞信息后, 针对整个小 区进行统一拥塞控制, 如指示策略和计费规则功能实体 (Policy and Charging Rule Function, 以下简称: PCRF )或者业务服务器减少数据包发 送, 或者降低业务服务质量 (QoS ) , 降低拥塞小区中 UE资源的占用。 但是上述方法会导致误伤资源占用少的 MVNO或者提供服务的 MNO, 使 得资源占用少的 MVNO或者提供服务的 MNO的 UE无法充分使用资源, 对于拥塞控制的效率低。 发明内容 本发明实施例提供一种拥塞控制方法、 装置及系统, 可区分不同的参 与运营商进行拥塞控制, 实现了针对特定的拥塞对象以及拥塞原因进行精 确高效的拥塞控制。
第一方面, 本发明实施例提供一种拥塞控制方法, 包括:
核心网设备接收无线接入网 RAN设备检测到某一个或多个参与运营 商发生拥塞时发送的拥塞通知消息, 所述拥塞通知消息包括发生拥塞的参 与运营商标识, 所述参与运营商为移动虚拟网络运营商 MVNO或共享运 营商网络的运营商;
所述核心网设备根据所述拥塞通知消息, 对所述参与运营商标识对应 的参与运营商进行拥塞控制。
在第一方面的第一种可能的实施方式中, 所述拥塞通知消息还包括下 述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 所述 RAN设备或所述 RAN设备的相邻 RAN设备的 其他可用的小区信息和所述 RAN设备或所述 RAN设备的相邻 RAN设备 的其他可用的小区中所述参与运营商标识对应的参与运营商的资源使用 情况。
结合第一方面的第一种可能的实施方式中, 在第一方面的第二种可能 的实施方式中, 所述核心网设备为移动管理实体 MME/服务 GPRS支持节 点 SGSN, 所述核心网设备接收无线接入网 RAN设备检测到某一个或多 个参与运营商发生拥塞时发送的拥塞通知消息, 包括:
所述 MME/ SGSN接收 RAN设备检测到某一个或多个参与运营商发 生拥塞时发送的拥塞通知消息;
所述 MME/ SGSN记录所述拥塞通知消息, 并向所述 RAN设备发送 拥塞通知响应消息;
所述核心网设备根据所述拥塞通知消息, 对所述参与运营商标识对应 的参与运营商进行拥塞控制, 包括:
所述 MME/ SGSN接收用户设备 UE通过所述 RAN设备发送的接入请 求, 所述接入请求包含所要接入的参与运营商信息;
所述 MME/ SGSN根据所述接入请求包含的所述参与运营商信息和拥 塞通知消息, 向所述 UE发送接入拒绝消息。
结合第一方面的第二种可能的实施方式, 在第一方面的第三种可能的 实施方式中, 在 4G网络下, 所述接入请求为附着请求; 或者,
所述接入请求为 UE发起的服务请求; 或者,
所述接入请求为跟踪区更新请求; 或者,
所述接入请求为路由区更新请求; 或者,
在 2G/3G网络下, 所述接入请求为 UE发起的一次 /二次 PDP上下文 建立或修改请求;
所述接入拒绝消息还包括: 接入拒绝原因和空闲小区指示信息, 用于 所述 UE选择接入所述空闲小区指示信息指示的空闲小区。
结合第一方面的第一种可能的实施方式中, 在第一方面的第四种可能 的实施方式中, 所述核心网设备包括 MME/ SGSN, 服务网关 S-GW、 分 组数据网络网关 P-G W/网关 GPRS支持节点 GGSN和策略与计费规则功能 实体 PCRF,所述核心网设备接收无线接入网 RAN设备检测到某一个或多 个参与运营商发生拥塞时发送的拥塞通知消息, 包括: MME/ SGSN接收 RAN设备检测到某一个或多个参与运营商发生拥 塞时发送的拥塞通知消息;
所述 MME/ SGSN记录所述拥塞通知消息, 并向所述 RAN设备发送 拥塞通知响应消息;
所述核心网设备根据所述拥塞通知消息, 对所述参与运营商标识对应 的参与运营商进行拥塞控制, 包括:
PCRF向 P-GW/GGSN发送 IP连接接入网络 IP-CAN会话修改请求; 所述 P-GW/GGSN根据所述 IP-CAN会话修改请求通过 S-GW向所述 MME/ SGSN发起承载建立 /修改请求, 所述承载建立 /修改请求中包含 UE 的国际移动用户标识 IMSI信息 /UE的参与运营商标识;
所述 MME/ SGSN根据所述 IMSI信息 /参与运营商标识和所述拥塞通 知消息, 拒绝所述承载建立 /修改请求。
结合第一方面的第四种可能的实施方式中, 在第一方面的第五种可能 的实施方式中, 还包括:
所述 MME/ SGSN通过 S-GW向所述 P-GW/GGSN发起承载建立 /修改 拒绝响应, 所述承载建立 /修改拒绝响应包括拒绝原因;
所述 P-GW/GGSN向所述 PCRF发送 IP-CAN会话修改响应消息, 所 述 I P - C AN会话修改响应消息中包含所述拒绝原因。
结合第一方面的第一种可能的实施方式至第一方面的第五种可能的 实施方式中任一项所述的方法, 在第一方面的第六种可能的实施方式中, 还包括:
所述 MME/ SGSN接收所述 RAN设备检测到所述 RAN设备内发生拥 塞的参与运营商拥塞状况缓解时发送的拥塞缓解通知消息;
所述 MME/ SGSN向所述 RAN设备发送拥塞缓解响应消息。
结合第一方面的第一种可能的实施方式, 在第一方面的第七种可能的 实施方式中, 所述核心网设备包括 MME/ SGSN, S-GW, P-GW/ GGSN和 PCRF, 所述核心网设备接收无线接入网 RAN设备检测到某一个或多个参 与运营商发生拥塞时发送的拥塞通知消息, 包括:
所述 MME/ SGSN接收 RAN设备检测到某一个或多个参与运营商发 生拥塞时发送的拥塞通知消息; 所述 MME/ SGSN通过所述 S-GW向所述 P-GW/GGSN发送承载更新 请求消息, 所述承载更新请求消息包括所述拥塞通知消息的内容;
所述 P-GW/GGSN接收所述承载更新请求消息;
所述 P-GW/GGSN记录所述承载更新请求消息, 并通过所述 S-GW和 所述 MME/ SGSN向所述 RAN设备发送拥塞通知响应消息;
所述核心网设备根据所述拥塞通知消息, 对所述参与运营商标识对应 的参与运营商进行拥塞控制, 包括:
PCRF向所述 P-GW/GGSN发送 IP连接接入网络 IP-CAN会话修改请 求;
所述 P-GW/GGSN根据所述拥塞通知消息和所述 IP-CAN会话修改请 求的类型判断, 拒绝所述 IP-CAN会话修改请求。
结合第一方面的第七种可能的实施方式, 在第一方面的第八种可能的 实施方式中, 还包括:
所述 P-GW/GGSN向所述 PCRF发送 IP-CAN会话修改响应消息, 所 述 IP-CAN会话修改响应消息中包含拒绝原因。
结合第一方面的第七种可能的实施方式或第一方面的第八种可能的 实施方式, 在第一方面的第九种可能的实施方式中, 还包括:
所述 MME/ SGSN接收所述 RAN设备检测到所述 RAN设备内发生拥 塞的参与运营商拥塞状况缓解时发送的拥塞缓解通知消息;
所述 MME/ SGSN通过所述 S-GW向所述 P-GW/GGSN发送所述拥塞 缓解通知消息;
所述 P-GW/GGSN通过所述 S-GW和所述 MME/ SGSN向所述 RAN 设备发送拥塞缓解响应消息。
结合第一方面的第一种可能的实施方式, 在第一方面的第十种可能的 实施方式中, 所述核心网设备包括 S-GW、 P-GW/ GGSN和 PCRF, 所述 核心网设备接收无线接入网 RAN设备检测到某一个或多个参与运营商发 生拥塞时发送的拥塞通知消息, 包括:
所述 P-GW/ GGSN通过所述 S-GW接收 RAN设备检测到某一个或多 个参与运营商发生拥塞时发送的拥塞通知消息;
所述 P-GW/ GGSN记录所述拥塞通知消息,并通过所述 S-GW向所述 RAN设备发送拥塞通知响应消息;
所述核心网设备根据所述拥塞通知消息, 对所述参与运营商标识对应 的参与运营商进行拥塞控制, 包括:
PCRF向所述 P-GW/GGSN发送 IP-CAN会话修改请求;
所述 P-GW/GGSN根据所述拥塞通知消息和所述 IP-CAN会话修改请 求的类型判断, 拒绝所述 IP-CAN会话修改请求。
结合第一方面的第十种可能的实施方式, 在第一方面的第十一种可能 的实施方式中, 还包括:
所述 P-GW/GGSN向所述 PCRF发送 IP-CAN会话修改响应消息, 所 述 IP-CAN会话修改响应消息中包含拒绝原因。
结合第一方面的第十种可能的实施方式或第一方面的第十一种可能 的实施方式, 在第一方面的第十二种可能的实施方式中, 还包括:
所述 P-GW/GGSN通过所述 S-GW接收所述 RAN设备检测到所述 RAN 设备内发生拥塞的参与运营商拥塞状况缓解时发送的拥塞缓解通知 消息;
所述 P-GW/GGSN通过所述 S-GW向所述 RAN设备发送拥塞缓解响 应消息。
第二方面, 本发明实施例提供一种拥塞控制方法, 包括:
无线接入网 RAN设备根据参与运营商的资源使用情况检测拥塞的发 生, 所述参与运营商为移动虚拟网络运营商 MVNO或共享运营商网络的 运营商;
当所述 RAN设备检测到某一个或多个所述参与运营商发生拥塞时, 向与发生拥塞的所述参与运营商相关的核心网设备发送拥塞通知消息, 所 述拥塞通知消息包括发生拥塞的参与运营商标识, 用于所述核心网设备对 所述参与运营商标识对应的参与运营商进行拥塞控制。
在第二方面的第一种可能的实施方式中, 所述拥塞通知消息还包括下 述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 所述 RAN设备或所述 RAN设备的相邻 RAN设备的 其他可用的小区信息和所述 RAN设备或所述 RAN设备的相邻 RAN设备 的其他可用的小区中所述参与运营商标识对应的参与运营商的资源使用 情况。
结合第二方面的第一种可能的实施方式, 在第二方面的第二种可能的 实施方式中, 所述核心网设备为 MME/ SGSN, 当所述 RAN设备检测到某 一个或多个所述参与运营商发生拥塞时, 向与发生拥塞的所述参与运营商 相关的核心网设备发送拥塞通知消息, 包括:
所述 RAN设备检测到某一个或多个所述参与运营商发生拥塞时, 向 与发生拥塞的所述参与运营商相关的 MME/ SGSN发送拥塞通知消息, 用 于所述 MME/ SGSN记录所述拥塞通知消息, 并根据所述拥塞通知消息, 对所述参与运营商标识对应的参与运营商进行拥塞控制;
所述方法还包括: 所述 RAN设备接收所述 MME/ SGSN发送的拥塞 通知响应消息。
结合第二方面的第二种可能的实施方式, 在第二方面的第三种可能的 实施方式中, 所述核心网设备包括 MME/ SGSN, S-GW、 P-GW/ GGSN和 PCRF,当所述 RAN设备检测到某一个或多个所述参与运营商发生拥塞时, 向与发生拥塞的所述参与运营商相关的核心网设备发送拥塞通知消息, 包 括:
当所述 RAN设备检测到某一个或多个所述参与运营商发生拥塞时, 向与发生拥塞的所述参与运营商相关的 MME/ SGSN发送拥塞通知消息, 用于所述 MME/ SGSN记录所述拥塞通知消息;
所述方法还包括: 所述 RAN设备接收所述 MME/ SGSN发送的拥塞 通知响应消息。
结合第二方面的第一种可能的实施方式至第二方面的第三种可能的 实施方式中任一项所述的方法, 在第二方面的第四种可能的实施方式中, 还包括:
所述 RAN设备检测到所述 RAN设备内发生拥塞的参与运营商拥塞状 况缓解时, 向所述 MME/ SGSN发送拥塞缓解通知消息;
所述 RAN设备接收所述 MME/ SGSN发送的拥塞缓解响应消息。 结合第二方面的第一种可能的实施方式, 在第二方面的第五种可能的 实施方式中, 所述核心网设备包括 MME/ SGSN, S-GW、 P-GW/ GGSN和 PCRF,当所述 RAN设备检测到某一个或多个所述参与运营商发生拥塞时, 向与发生拥塞的所述参与运营商相关的核心网设备发送拥塞通知消息, 包 括:
当所述 RAN设备检测到某一个或多个所述参与运营商发生拥塞时, 向与发生拥塞的所述参与运营商相关的 MME/ SGSN发送拥塞通知消息, 用于所述 MME/ SGSN通过所述 S-GW向所述 P-GW/GGSN发送承载更新 请求消息, 所述承载更新请求消息包括所述拥塞通知消息的内容;
所述方法还包括:
所述 RAN设备接收所述 P-GW/GGSN通过所述 S-GW和所述 MME/ SGSN发送的拥塞通知响应消息。
结合第二方面的第五种可能的实施方式, 在第二方面的第六种可能的 实施方式中, 还包括:
所述 RAN设备检测到所述 RAN设备内发生拥塞的参与运营商拥塞状 况缓解时, 向所述 MME/ SGSN发送拥塞缓解通知消息, 用于所述 MME/ SGSN通过所述 S-GW向所述 P-GW/GGSN发送所述拥塞缓解通知消息; 所述 RAN设备接收所述 P-GW/GGSN通过所述 S-GW和所述 MME/ SGSN发送的拥塞缓解响应消息。
结合第二方面的第一种可能的实施方式, 在第二方面的第七种可能的 实施方式中, 所述核心网设备包括 S-GW、 P-GW/ GGSN和 PCRF, 当所 述 RAN设备检测到某一个或多个所述参与运营商发生拥塞时, 向与发生 拥塞的所述参与运营商相关的核心网设备发送拥塞通知消息, 包括:
当所述 RAN设备检测到某一个或多个所述参与运营商发生拥塞时, 向与发生拥塞的所述参与运营商相关的 S-GW发送拥塞通知消息, 用于所 述 S-GW向所述 P-GW/GGSN发送所述拥塞通知消息;
所述方法还包括:
所述 RAN设备接收所述 P-GW/GGSN通过所述 S-GW发送的拥塞通 知响应消息。
结合第二方面的第七种可能的实施方式, 在第二方面的第八种可能的 实施方式中, 还包括:
所述 RAN设备检测到所述 RAN设备内发生拥塞的参与运营商拥塞状 况缓解时, 向所述 S-GW发送拥塞缓解通知消息, 用于所述 S-GW向所述 P-GW/GGSN发送所述拥塞缓解通知消息;
所述 RAN设备接收所述 P-GW/GGSN通过所述 S-GW发送的拥塞缓 解响应消息。
第三方面, 本发明实施例提供一种核心网设备, 包括:
接收模块, 用于接收无线接入网 RAN设备检测到某一个或多个参与 运营商发生拥塞时发送的拥塞通知消息, 所述拥塞通知消息包括发生拥塞 的参与运营商标识, 所述参与运营商为移动虚拟网络运营商 MVNO或共 享运营商网络的运营商;
处理模块, 用于根据所述拥塞通知消息, 对所述参与运营商标识对应 的参与运营商进行拥塞控制。
在第三方面的第一种可能的实施方式中, 所述拥塞通知消息还包括下 述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 所述 RAN设备或所述 RAN设备的相邻 RAN设备的 其他可用的小区信息和所述 RAN设备或所述 RAN设备的相邻 RAN设备 的其他可用的小区中所述参与运营商标识对应的参与运营商的资源使用 情况。
结合第三方面的第一种可能的实施方式, 在第三方面的第二种可能的 实施方式中, 所述核心网设备为移动管理实体 MME/服务 GPRS支持节点 SGSN, 所述 MME/SGSN包括:
第一接收模块, 用于接收 RAN设备检测到某一个或多个参与运营商 发生拥塞时发送的拥塞通知消息;
第一发送模块, 用于记录所述拥塞通知消息, 并向所述 RAN设备发 送拥塞通知响应消息;
所述第一接收模块还用于接收用户设备 UE通过所述 RAN设备发送 的接入请求, 所述接入请求包含所要接入的参与运营商信息;
第一处理模块, 用于根据所述接入请求包含的所述参与运营商信息和 拥塞通知消息, 向所述 UE发送接入拒绝消息。
结合第三方面的第二种可能的实施方式, 在第三方面的第三种可能的 实施方式中, 在 4G网络下, 所述接入请求为附着请求; 或者,
所述接入请求为 UE发起的服务请求; 或者,
所述接入请求为跟踪区更新请求; 或者,
所述接入请求为路由区更新请求; 或者,
在 2G/3G网络下, 所述接入请求为 UE发起的一次 /二次 PDP上下文 建立或修改请求;
所述接入拒绝消息还包括: 接入拒绝原因和空闲小区指示信息, 用于 所述 UE选择接入所述空闲小区指示信息指示的空闲小区。
结合第三方面的第一种可能的实施方式, 在第三方面的第四种可能的 实施方式中, 所述核心网设备包括 MME/ SGSN、 服务网关 S-GW、 分组 数据网络网关 P-G W/网关 GPRS支持节点 GGSN和策略与计费规则功能实 体 PCRF, 所述 MME/ SGSN包括:
第二接收模块, 用于接收 RAN设备检测到某一个或多个参与运营商 发生拥塞时发送的拥塞通知消息;
第二发送模块, 用于记录所述拥塞通知消息, 并向所述 RAN设备发 送拥塞通知响应消息;
所述 PCRF包括:
第三发送模块,用于向 P-GW/GGSN发送 IP连接接入网络 IP-CAN会 话修改请求;
所述 P-GW/GGSN包括:
第四发送模块, 用于根据所述 IP-CAN会话修改请求通过 S-GW向所 述 MME/ SGSN发起承载建立 /修改请求, 所述承载建立 /修改请求中包含 UE的国际移动用户标识 IMSI信息 /UE的参与运营商标识;
所述 MME/ SGSN还包括:
第二处理模块, 用于根据所述 IMSI信息 /参与运营商标识和所述拥塞 通知消息, 拒绝所述承载建立 /修改请求。
结合第三方面的第四种可能的实施方式, 在第三方面的第五种可能的 实施方式中, 所述第二发送模块还用于:
通过 S-GW向所述 P-GW/GGSN发起承载建立 /修改拒绝响应,所述承 载建立 /修改拒绝响应包括拒绝原因; 所述第四发送模块还用于: 向所述 PCRF发送 IP-CAN会话修改响应 消息, 所述 IP-CAN会话修改响应消息中包含所述拒绝原因。
结合第三方面的第一种可能的实施方式至第三方面的第五种可能的 实施方式中任一项所述的核心网设备, 在第一方面的第六种可能的实施方 式中, 所述第二接收模块还用于:
接收所述 RAN设备检测到所述 RAN设备内发生拥塞的参与运营商拥 塞状况缓解时发送的拥塞缓解通知消息;
所述第二发送模块还用于向所述 RAN设备发送拥塞缓解响应消息。 结合第三方面的第一种可能的实施方式, 在第一方面的第七种可能的 实施方式中, 所述核心网设备包括 MME/ SGSN、 S-GW, P-GW/ GGSN和 PCRF, 所述 MME/SGSN包括:
第三接收模块, 用于接收 RAN设备检测到某一个或多个参与运营商 发生拥塞时发送的拥塞通知消息;
第五发送模块, 用于通过所述 S-GW向所述 P-GW/GGSN发送承载更 新请求消息, 所述承载更新请求消息包括所述拥塞通知消息的内容; 所述 P-GW/GGSN包括:
第四接收模块, 用于接收所述承载更新请求消息;
第六发送模块, 用于记录所述承载更新请求消息, 并通过所述 S-GW 和所述 MME/ SGSN向所述 RAN设备发送拥塞通知响应消息;
所述 PCRF包括:
第七发送模块, 用于向所述 P-GW/GGSN 发送 IP 连接接入网络 IP-CAN会话修改请求;
所述 P-GW/GGSN还包括:
第三处理模块, 用于根据所述拥塞通知消息和所述 IP-CAN会话修改 请求的类型判断, 拒绝所述 IP-CAN会话修改请求。
结合第三方面的第七种可能的实施方式, 在第一方面的第八种可能的 实施方式中, 所述第六发送模块还用于: 向所述 PCRF发送 IP-CAN会话 修改响应消息, 所述 IP-CAN会话修改响应消息中包含拒绝原因。
结合第三方面的第七种可能的实施方式或第一方面的第八种可能的 实施方式, 在第一方面的第九种可能的实施方式中, 所述第三接收模块还 用于:接收所述 RAN设备检测到所述 RAN设备内发生拥塞的参与运营商 拥塞状况缓解时发送的拥塞缓解通知消息;
所述第五发送模块还用于: 通过所述 S-GW向所述 P-GW/GGSN发送 所述拥塞缓解通知消息;
所述第六发送模块还用于: 通过所述 S-GW和所述 MME/ SGSN向所 述 RAN设备发送拥塞缓解响应消息。
结合第三方面的第一种可能的实施方式, 在第三方面的第十种可能的 实施方式中, 所述核心网设备包括 S-GW、 P-GW/ GGSN和 PCRF, 所述 P-GW/ GGSN包括:
第五接收模块, 用于通过所述 S-GW接收 RAN设备检测到某一个或 多个参与运营商发生拥塞时发送的拥塞通知消息;
第七发送模块, 用于记录所述拥塞通知消息, 并通过所述 S-GW向所 述 RAN设备发送拥塞通知响应消息;
所述 PCRF包括:
第八发送模块,用于向所述 P-GW/GGSN发送 IP-CAN会话修改请求; 所述 P-GW/GGSN包括:
第四处理模块, 用于根据所述拥塞通知消息和所述 IP-CAN会话修改 请求的类型判断, 拒绝所述 IP-CAN会话修改请求。
结合第三方面的第十种可能的实施方式, 在第三方面的第十一种可能 的实施方式中, 所述第七发送模块还用于:
向所述 PCRF发送 IP-CAN会话修改响应消息, 所述 IP-CAN会话修 改响应消息中包含拒绝原因。
结合第三方面的第十种可能的实施方式或第三方面的第十一种可能 的实施方式, 在第三方面的第十二种可能的实施方式中, 所述第五接收模 块还用于:通过所述 S-GW接收所述 RAN设备检测到所述 RAN设备内发 生拥塞的参与运营商拥塞状况缓解时发送的拥塞缓解通知消息;
所述第七发送模块还用于: 通过所述 S-GW向所述 RAN设备发送拥 塞缓解响应消息。
第四方面, 本发明实施例提供一种无线接入网设备, 包括:
检测模块, 用于根据参与运营商的资源使用情况检测拥塞的发生, 所 述参与运营商为移动虚拟网络运营商 MVNO或共享运营商网络的运营商; 发送模块, 用于当所述检测模块检测到某一个或多个所述参与运营商 发生拥塞时, 向与发生拥塞的所述参与运营商相关的核心网设备发送拥塞 通知消息, 所述拥塞通知消息包括发生拥塞的参与运营商标识, 用于所述 核心网设备对所述参与运营商标识对应的参与运营商进行拥塞控制。
在第四方面的第一种可能的实施方式中, 所述拥塞通知消息还包括下 述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 所述 RAN设备或所述 RAN设备的相邻 RAN设备的 其他可用的小区信息和所述 RAN设备或所述 RAN设备的相邻 RAN设备 的其他可用的小区中所述参与运营商标识对应的参与运营商的资源使用 情况。
结合第四方面的第一种可能的实施方式, 在第四方面的第二种可能的 实施方式中, 所述核心网设备为 MME/ SGSN, 所述发送模块用于:
当所述检测模块检测到某一个或多个所述参与运营商发生拥塞时, 向 与发生拥塞的所述参与运营商相关的 MME/ SGSN发送拥塞通知消息, 用 于所述 MME/ SGSN记录所述拥塞通知消息, 并根据所述拥塞通知消息, 对所述参与运营商标识对应的参与运营商进行拥塞控制;
所述无线接入网设备还包括:
第一接收模块,用于接收所述 MME/ SGSN发送的拥塞通知响应消息。 结合第四方面的第一种可能的实施方式, 在第四方面的第三种可能的 实施方式中, 所述核心网设备包括 MME/ SGSN, S-GW、 P-GW/ GGSN和 PCRF, 所述发送模块用于:
当所述检测模块检测到某一个或多个所述参与运营商发生拥塞时, 向 与发生拥塞的所述参与运营商相关的 MME/ SGSN发送拥塞通知消息, 用 于所述 MME/ SGSN记录所述拥塞通知消息;
所述无线接入网设备还包括:
第二接收模块,用于接收所述 MME/ SGSN发送的拥塞通知响应消息。 结合第四方面的第一种可能的实施方式至第四方面的第三种可能的 实施方式中任一项所述的无线接入网设备, 在第四方面的第四种可能的实 施方式中, 所述发送模块还用于:
当所述检测模块检测到所述 RAN设备内发生拥塞的参与运营商拥塞 状况缓解时, 向所述 MME/ SGSN发送拥塞缓解通知消息;
所述第一接收模块或所述第二接收模块还用于:
接收所述 MME/ SGSN发送的拥塞缓解响应消息。
结合第四方面的第一种可能的实施方式, 在第四方面的第五种可能的 实施方式中, 所述核心网设备包括 MME/ SGSN, S-GW, P-GW/ GGSN和 PCRF, 所述发送模块用于:
当所述检测模块检测到某一个或多个所述参与运营商发生拥塞时, 向 与发生拥塞的所述参与运营商相关的 MME/ SGSN发送拥塞通知消息, 用 于所述 MME/ SGSN通过所述 S-GW向所述 P-GW/GGSN发送承载更新请 求消息, 所述承载更新请求消息包括所述拥塞通知消息的内容;
所述无线接入网设备还包括:
第三接收模块, 用于接收所述 P-GW/GGSN通过所述 S-GW和所述 MME/ SGSN发送的拥塞通知响应消息。
结合第四方面的第五种可能的实施方式, 在第四方面的第六种可能的 实施方式中, 所述发送模块还用于:
当所述检测模块检测到所述 RAN设备内发生拥塞的参与运营商拥塞 状况缓解时,向所述 MME/ SGSN发送拥塞缓解通知消息,用于所述 MME/ SGSN通过所述 S-GW向所述 P-GW/GGSN发送所述拥塞缓解通知消息; 所述第三接收模块还用于接收所述 P-GW/GGSN通过所述 S-GW和所 述 MME/ SGSN发送的拥塞缓解响应消息。
结合第四方面的第一种可能的实施方式, 在第四方面的第七种可能的 实施方式中, 所述核心网设备包括 S-GW、 P-GW/ GGSN和 PCRF, 所述 发送模块用于:
当所述检测模块检测到某一个或多个所述参与运营商发生拥塞时, 向 与发生拥塞的所述参与运营商相关的 S-GW发送拥塞通知消息, 用于所述 S-GW向所述 P-GW/GGSN发送所述拥塞通知消息;
所述无线接入网设备还包括:
第四接收模块, 用于接收所述 P-GW/GGSN通过所述 S-GW发送的拥 塞通知响应消息。
结合第四方面的第七种可能的实施方式, 在第四方面的第八种可能的 实施方式中, 所述发送模块还用于:
当所述检测模块检测到所述 RAN设备内发生拥塞的参与运营商拥塞 状况缓解时, 向所述 S-GW发送拥塞缓解通知消息, 用于所述 S-GW向所 述 P-GW/GGSN发送所述拥塞缓解通知消息;
所述第四接收模块还用于接收所述 P-GW/GGSN通过所述 S-GW发送 的拥塞缓解响应消息。
第五方面, 本发明实施例提供一种通信系统, 包括上述第三方面至第 三方面的第十二种可能的实施方式中任一项所述的核心网设备和第四方 面至第四方面的第第八种可能的实施方式中任一项所述的 RAN设备。
本发明实施例提供的拥塞控制方法、 装置及系统, 通过核心网设备接 收 RAN设备检测到某一个或多个参与运营商发生拥塞时发送的拥塞通知 消息, 拥塞通知消息包括发生拥塞的参与运营商标识。 然后根据拥塞通知 消息, 对参与运营商标识对应的参与运营商进行拥塞控制。 因此可区分不 同的参与运营商进行拥塞控制, 实现了针对特定的拥塞对象以及拥塞原因 进行精确高效的拥塞控制, 同时保护了未发生拥塞的参与运营商的连接数 资源以及带宽资源。 附图说明 为了更清楚地说明本发明实施例或现有技术中的技术方案, 下面将对 实施例或现有技术描述中所需要使用的附图作一简单地介绍, 显而易见 地, 下面描述中的附图是本发明的一些实施例, 对于本领域普通技术人员 来讲, 在不付出创造性劳动性的前提下, 还可以根据这些附图获得其他的 附图。
图 1为本发明拥塞控制方法实施例一的流程图;
图 2为本发明拥塞控制方法实施例二的流程图;
图 3为本发明拥塞控制方法实施例三的信令交互图;
图 4为本发明拥塞控制方法实施例四的信令交互图;
图 5为本发明拥塞控制方法实施例五的信令交互图; 图 6为本发明拥塞控制方法实施例六的信令交互图;
图 7为本发明核心网设备实施例一的结构示意图;
图 8为本发明 RAN设备实施例一的结构示意图;
图 9为本发明核心网设备实施例二的结构示意图;
图 10为本发明 RAN设备实施例二的结构示意图。 具体实施方式 为使本发明实施例的目的、 技术方案和优点更加清楚, 下面将结合本 发明实施例中的附图, 对本发明实施例中的技术方案进行清楚、 完整地描 述, 显然,所描述的实施例是本发明一部分实施例, 而不是全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有做出创造性劳动前提 下所获得的所有其他实施例, 都属于本发明保护的范围。
本发明实施例提供一种拥塞控制方法, 可实现在运营商与多家虚拟运 营商签约且无线接入网 (Radio access network, 以下简称: RAN) 设备发 生拥塞的场景下, 根据不同的拥塞类型对不同 MVNO进行拥塞状况解除, 而对未发生拥塞的 MVNO 的连接数资源以及带宽资源进行保护, 同时也 实现了在多 MVNO状态下的资源精细化控制。
图 1为本发明拥塞控制方法实施例一的流程图, 本实施例以核心网设 备作为执行主体为例进行说明,本实施例中的核心网设备包括 3GPP网络中 支持不同接入技术的设备, 包括移动性管理设备, 如支持 2G/3G网络接入 的 /服务 GPRS支持节点(Serving GPRS Support Node, 以下简称: SGSN), 支持 4G网络接入的移动管理实体(Mobility Management Entity, 以下简称: MME), 4G-SGSN等,以及网关设备,如网关 GPRS支持节点(Gateway GPRS Support Node, 以下简称: GGSN) 、 服务网关 ( Serving Gateway, 以下简 称: S-GW) 、 分组数据网络网关 (Packet Data Network Gateway , 以下 简称: P-GW) 等。
如图 1所示, 本实施例的方法可以包括:
S101、 核心网设备接收 RAN设备检测到某一个或多个参与运营商发 生拥塞时发送的拥塞通知消息, 拥塞通知消息包括发生拥塞的参与运营商 标识。 其中, 参与运营商是指共享运营商网络的运营商或者 MVNO。例如为 MVNO时,参与运营商标识例如可以为 MVNO标识或者 MVNO对应的国 际移动用户标识(International Mobile Subscriber Identity,以下简称: IMSI) 号段等。
S102、 核心网设备根据拥塞通知消息, 对参与运营商标识对应的参与 运营商进行拥塞控制。
进一歩地, 拥塞通知消息还包括下述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 RAN设备或 RAN设备的相邻 RAN设备的其他可用 的小区信息和 RAN设备或 RAN设备的相邻 RAN设备的其他可用的小区 中参与运营商标识对应的参与运营商的资源使用情况。 其中, 发生拥塞的 参与运营商的拥塞原因, 例如可以是参与运营商可用的 UE数资源不足, 连接数资源不足或者可用的带宽资源不足等; 发生拥塞的参与运营商在拥 塞小区的资源使用情况例如可以是参与运营商在拥塞小区所占接入用户 设备数资源,承载连接数资源和 /或带宽资源的百分比、高中低等类型信息, 或者拥塞程度; RAN设备或 RAN设备的相邻 RAN设备的其他可用的小 区中参与运营商标识对应的参与运营商的资源使用情况, 例如可以是用户 设备数资源、 连接数资源或带宽资源等。
针对核心网设备的不同, 本实施例中有四种可实施的方式, 作为第一 种可实施的方式, 核心网设备为 MME/ SGSN, 此时 S101具体为:
S101a、 MME/ SGSN接收 RAN设备检测到某一个或多个参与运营商 发生拥塞时发送的拥塞通知消息。拥塞通知消息包括发生拥塞的参与运营 商标识。
S101b、 MME/ SGSN记录拥塞通知消息, 并向 RAN设备发送拥塞通 知响应消息。
S102具体为:
S102a、 MME/ SGSN接收用户设备 UE通过 RAN设备发送的接入请 求, 接入请求包含所要接入的参与运营商信息。
S102b、MME/ SGSN根据接入请求包含的参与运营商信息和拥塞通知 消息, 向 UE发送接入拒绝消息。 其中, 在 4G 网络下, 接入请求为附着请求; 或者, 接入请求为 UE 发起的服务请求; 或者, 接入请求为跟踪区更新请求; 或者, 接入请求为 路由区更新请求。
在 2G/3G 网络下, 接入请求为 UE 发起的一次 /二次分组数据协议 ( Packet Data Protocol, 以下简称: PDP ) 上下文建立或修改请求。
接入拒绝消息还可以包括: 接入拒绝原因和空闲小区指示信息, 用于 U E选择接入空闲小区指示信息指示的空闲小区。
作为第二种可实施的方式, 核心网设备包括 MME/ SGSN、 S-GW、 P-GW/ GGSN 和策略与计费规则功能实体 (Policy and Charging Rules Function, 以下简称: PCRF ) , 此时 S101具体为:
S101c、 MME/ SGSN接收 RAN设备检测到某一个或多个参与运营商 发生拥塞时发送的拥塞通知消息。
S101d、 MME/ SGSN记录拥塞通知消息, 并向 RAN设备发送拥塞通 知响应消息。
S102具体为:
S102c、 PCRF向 P-GW/GGSN发送 IP连接接入网络 (IP Connectivity Access Network , 简称: IP-CAN) 会话修改请求。
S102d、 P-GW/GGSN根据 IP-CAN会话修改请求通过 S-GW向 MME/ SGSN发起承载建立 /修改请求, 承载建立 /修改请求中包含 UE的 IMSI信 息 /UE的参与运营商标识。
S 102e、 MME/ SGSN根据 IMSI信息 /参与运营商标识和拥塞通知消息, 拒绝承载建立 /修改请求。
进一歩地, 还包括:
MME/ SGSN通过 S-GW向 P-GW/GGSN发起承载建立 /修改拒绝响 应, 承载建立 /修改拒绝响应包括拒绝原因;
P-GW/GGSN向 PCRF发送 IP-CAN会话修改响应消息, IP-CAN会话 修改响应消息中包含拒绝原因。
在上述两种可能的实施方式中, 还可以包括:
MME/ SGSN接收 RAN设备检测到 RAN设备内发生拥塞的参与运营 商拥塞状况缓解时发送的拥塞缓解通知消息; MME/ SGSN向 RAN设备发送拥塞缓解响应消息。
作为第三种可实施的方式, 核心网设备包括 MME/ SGSN, S-GW, P-GW/ GGSN和 PCRF, 此时 S101具体为:
S101e、 MME/ SGSN接收 RAN设备检测到某一个或多个参与运营商 发生拥塞时发送的拥塞通知消息。
S101f、 MME/ SGSN通过 S-GW向 P-GW/GGSN发送承载更新请求消 息, 承载更新请求消息包括拥塞通知消息的内容。
S101g、 P-GW/GGSN接收承载更新请求消息。
S101h、 P-GW/GGSN记录承载更新请求消息, 并通过 S-GW和 MME/ SGSN向 RAN设备发送拥塞通知响应消息。
S102具体为:
S102f、PCRF向 P-GW/GGSN发送 IP连接接入网络 IP-CAN会话修改 请求。
S102g、 P-GW/GGSN根据拥塞通知消息和 IP-CAN会话修改请求的类 型判断, 拒绝 IP-CAN会话修改请求。
进一歩地, 还包括:
P-GW/GGSN向 PCRF发送 IP-CAN会话修改响应消息, IP-CAN会话 修改响应消息中包含拒绝原因。
进一歩地, 还包括:
MME/ SGSN接收 RAN设备检测到 RAN设备内发生拥塞的参与运营 商拥塞状况缓解时发送的拥塞缓解通知消息。
MME/ SGSN通过 S-GW向 P-GW/GGSN发送拥塞缓解通知消息。 P-GW/GGSN通过 S-GW和 MME/ SGSN向 RAN设备发送拥塞缓解响 应消息。
作为第四种可实施的方式, 核心网设备包括 S-GW、 P-GW/ GGSN和
PCRF, 此时 S101具体为:
S101i、 P-GW/ GGSN通过 S-GW接收 RAN设备检测到某一个或多个 参与运营商发生拥塞时发送的拥塞通知消息。
S101j、 P-GW/ GGSN记录拥塞通知消息, 并通过 S-GW向 RAN设备 发送拥塞通知响应消息。 S102具体为:
S102h、 PCRF向 P-GW/GGSN发送 IP-CAN会话修改请求。
S102i、 P-GW/GGSN根据拥塞通知消息和 IP-CAN会话修改请求的类 型判断, 拒绝 IP-CAN会话修改请求。
进一歩地, 还包括:
P-GW/GGSN向 PCRF发送 IP-CAN会话修改响应消息, IP-CAN会话 修改响应消息中包含拒绝原因。
进一歩地, 还包括:
P-GW/GGSN通过 S-GW接收 RAN设备检测到 RAN设备内发生拥塞 的参与运营商拥塞状况缓解时发送的拥塞缓解通知消息。
P-GW/GGSN通过 S-GW向 RAN设备发送拥塞缓解响应消息。
本发明实施例提供的拥塞控制方法, 通过核心网设备接收 RAN设备 检测到某一个或多个参与运营商发生拥塞时发送的拥塞通知消息, 拥塞通 知消息包括发生拥塞的参与运营商标识。 然后根据拥塞通知消息, 对参与 运营商标识对应的参与运营商进行拥塞控制。 因此可区分不同的参与运营 商进行拥塞控制, 实现了针对特定的拥塞对象以及拥塞原因进行精确高效 的拥塞控制, 同时保护了未发生拥塞的参与运营商的连接数资源以及带宽 资源。
图 2为本发明拥塞控制方法实施例二的流程图, 本实施例以 RAN设 备作为执行主体为例进行说明, 如图 2所示, 本实施例的方法可以包括: S201、 RAN设备根据参与运营商的资源使用情况检测拥塞的发生。 具体来说, 在运营商共享其网络给一个或多个运营商或虚拟运营商的 情况下, 各个虚拟运营商需要与运营商协商 RAN资源使用情况, 例如, 为 各个虚拟运营商分配相应的 RAN资源使用比例, 并设置资源控制的拥塞门 限。 RAN设备实时统计各个 MVNO的资源使用情况, 当某虚拟运营商在该 RAN设备上的资源使用量不断增加以至达到或超过之前预设的该 MVNO 的拥塞门限值时, 判定为该虚拟运营商在 RAN设备发生拥塞。 引起拥塞的 原因可能是由于 RAN设备中该 MVNO可用的用户设备数资源不足, 或者 RAN设备中该 MVNO用户可用的连接数资源不足,也可能是由于 RAN设备 中该 MVNO可用的带宽资源不足。用户设备数资源不足是 RAN设备上同时 连接过多的该虚拟运营商用户设备, 达到或超出了所设定的门限值; 可用 的连接数资源不足是 RAN设备上同时连接过多的属于该虚拟运营商用户 设备的承载, 达到或超过了为该 MVNO所设定的门限值; 带宽资源不足是 指在同一时刻 RAN设备上该 MVNO所有用户设备的带宽占用 (如吞吐量 等) 达到或超过了为该虚拟运营商所设定的门限值。
S202、 当 RAN设备检测到某一个或多个参与运营商发生拥塞时, 向 与发生拥塞的参与运营商相关的核心网设备发送拥塞通知消息, 拥塞通知 消息包括发生拥塞的参与运营商标识, 用于核心网设备对参与运营商标识 对应的参与运营商进行拥塞控制。
其中, 拥塞通知消息还包括下述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 RAN设备或 RAN设备的相邻 RAN设备的其他可用 的小区信息和 RAN设备或 RAN设备的相邻 RAN设备的其他可用的小区 中参与运营商标识对应的参与运营商的资源使用情况。 其中, 发生拥塞的 参与运营商的拥塞原因, 例如可以是参与运营商可用的 UE数资源不足, 连接数资源不足或者可用的带宽资源不足等; 发生拥塞的参与运营商在拥 塞小区的资源使用情况例如可以是参与运营商在拥塞小区所占接入用户 设备数资源,承载连接数资源和 /或带宽资源的百分比、高中低等类型信息, 或者拥塞程度; RAN设备或 RAN设备的相邻 RAN设备的其他可用的小 区中参与运营商标识对应的参与运营商的资源使用情况, 例如可以是用户 设备数资源、 连接数资源或带宽资源等。
针对核心网设备的不同, 本实施例中有四种可实施的方式, 作为第一 种可实施的方式, 核心网设备为 MME/ SGSN, 此时 S202具体为:
S202a、 RAN设备检测到某一个或多个参与运营商发生拥塞时, 向与 发生拥塞的参与运营商相关的 MME/ SGSN 发送拥塞通知消息, 用于 MME/ SGSN记录拥塞通知消息, 并根据拥塞通知消息, 对参与运营商标 识对应的参与运营商进行拥塞控制。
此时该方法还包括:
RAN设备接收 MME/ SGSN发送的拥塞通知响应消息。
作为第二种可实施的方式, 核心网设备包括 MME/ SGSN, S-GW、 P-GW/ GGSN和 PCRF, 此时 S202具体为:
S202b、 当 RAN设备检测到某一个或多个参与运营商发生拥塞时, 向 与发生拥塞的参与运营商相关的 MME/ SGSN 发送拥塞通知消息, 用于 MME/ SGSN记录拥塞通知消息;
此时该方法还包括: RAN设备接收 MME/ SGSN发送的拥塞通知响应 消息。
在上述两种实施方式中, 进一歩地, 还包括:
RAN 设备检测到 RAN 设备内发生拥塞的参与运营商拥塞状况缓解 时, 向 MME/ SGSN发送拥塞缓解通知消息。
RAN设备接收 MME/ SGSN发送的拥塞缓解响应消息。
作为第三种可实施的方式, 核心网设备为包括 MME/ SGSN、 S-GW, P-GW/ GGSN和 PCRF, 此时 S202具体为:
S202c、 当 RAN设备检测到某一个或多个参与运营商发生拥塞时, 向 与发生拥塞的参与运营商相关的 MME/ SGSN 发送拥塞通知消息, 用于 MME/ SGSN通过 S-GW向 P-GW/GGSN发送承载更新请求消息, 承载更 新请求消息包括拥塞通知消息的内容。
此时该方法还包括:
RAN设备接收 P-GW/GGSN通过 S-GW和 MME/ SGSN发送的拥塞通 知响应消息。
进一歩地, 还包括:
RAN 设备检测到 RAN 设备内发生拥塞的参与运营商拥塞状况缓解 时,向 MME/ SGSN发送拥塞缓解通知消息,用于 MME/ SGSN通过 S-GW 向 P-GW/GGSN发送拥塞缓解通知消息。
RAN设备接收 P-GW/GGSN通过 S-GW和 MME/ SGSN发送的拥塞缓 解响应消息。
作为第四种可实施的方式, 核心网设备为包括 S-GW、 P-GW/ GGSN 和 PCRF, 此时 S202具体为:
S202d、 当 RAN设备检测到某一个或多个参与运营商发生拥塞时, 向 与发生拥塞的参与运营商相关的 S-GW发送拥塞通知消息,用于 S-GW向 P-GW/GGSN发送拥塞通知消息。 此时该方法还包括:
RAN设备接收 P-GW/GGSN通过 S-GW发送的拥塞通知响应消息。 进一歩地, 还包括:
RAN 设备检测到 RAN 设备内发生拥塞的参与运营商拥塞状况缓解 时, 向 S-GW发送拥塞缓解通知消息, 用于 S-GW向 P-GW/GGSN发送拥 塞缓解通知消息。
RAN设备接收 P-GW/GGSN通过 S-GW发送的拥塞缓解响应消息。 本发明实施例提供的拥塞控制方法, 通过 RAN设备根据参与运营商 的资源使用情况检测拥塞的发生, 当 RAN设备检测到某一个或多个参与 运营商发生拥塞时, 向与发生拥塞的参与运营商相关的核心网设备发送拥 塞通知消息, 拥塞通知消息包括发生拥塞的参与运营商标识, 用于核心网 设备对参与运营商标识对应的参与运营商进行拥塞控制。 因此可区分不同 的参与运营商进行拥塞控制, 实现了针对特定的拥塞对象以及拥塞原因进 行精确高效的拥塞控制, 同时保护了未发生拥塞的参与运营商的连接数资 源以及带宽资源。
下面采用四个具体的实施例, 对上述所示方法实施例的技术方案进行 详细说明。
图 3为本发明拥塞控制方法实施例三的信令交互图, 如图 3所示, 本 实施例中的核心网设备为 MME/ SGSN, 本实施例的方法可以包括:
S301、 RAN设备根据参与运营商的资源使用情况检测拥塞的发生。 具体为例如 RAN设备实时统计各个参与运营商 MVNO的资源使用情 况, 当某虚拟运营商在该 RAN设备上的资源使用量不断增加以至达到或 超过之前预设的该 MVNO的拥塞门限值时, 判定为该虚拟运营商在 RAN 设备发生拥塞。
S302、 当 RAN设备检测到某一个或多个参与运营商发生拥塞时, 向 与发生拥塞的参与运营商相关的 MME/ SGSN发送拥塞通知消息, 拥塞通 知消息包括发生拥塞的参与运营商标识。
具体地, 例如, RAN设备根据发生拥塞的 MVNO的标识(如 MVNO ID, IMSI号段, 公用陆地移动通信网 (Public Land Mobile Network , 简 称: PLMN) ID等) 选择相应的 MME/SGSN发送拥塞通知消息。 RAN 设备也可以向与之连接的所有的 MME/ SGSN发送拥塞通知消息。
拥塞通知消息还包括下述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 RAN设备或 RAN设备的相邻 RAN设备的其他可用 的小区信息和 RAN设备或 RAN设备的相邻 RAN设备的其他可用的小区 中参与运营商标识对应的参与运营商的资源使用情况。
5303、 MME/ SGSN接收拥塞通知消息, 并记录拥塞通知消息。
5304、 MME/ SGSN向 RAN设备发送拥塞通知响应消息。
5305、 UE向 RAN设备发送接入请求, 接入请求包含所要接入的参与 运营商信息。
5306、 RAN设备将接收到的接入请求转发给 MME/ SGSN。
5307、 MME/ SGSN根据接入请求包含的参与运营商信息和拥塞通知 消息, 向 UE发送接入拒绝消息。
其中, 在 4G 网络下, 接入请求为附着请求; 或者, 接入请求为 UE 发起的服务请求; 或者, 接入请求为跟踪区更新请求; 或者, 接入请求为 路由区更新请求。
在 2G/3G网络下,接入请求为 UE发起的一次 /二次分组数据协议 PDP 上下文建立或修改请求。
例如,当 RAN设备向 MME/SGSN发送的拥塞通知消息中包含的拥塞原 因是用户设备数资源超出预设值导致的拥塞, MME/SGSN根据接入请求消 息包含的 MVNO信息判断用户设备属于发生拥塞状况的虚拟运营商, 则 MME/SGSN根据上述信息, 拒绝用户设备的接入请求。
在 4G中用户设备附着过程中需要建立缺省承载, 因此在 4G场景中, 当 RAN设备向 MME发送的拥塞通知消息中包含的拥塞类型是连接数资 源超出预设值导致的拥塞, MME根据接入请求消息包含的 MVNO信息判 断用户设备属于发生拥塞状况的虚拟运营商, 且用户的接入类型为附着, 则 MME拒绝用户设备的附着请求。
进一歩地, 接入拒绝消息还可以包括: 接入拒绝原因和空闲小区指示 信息, 用于 UE选择接入空闲小区指示信息指示的空闲小区。 例如接入拒 绝原因为该虚拟运营商在 RAN设备发生用户设备数资源或连接数资源超 出限制而引起的拥塞, 并可以进一歩指示用户设备其他可用小区, 以指示 用户设备从空闲小区接入。 指示用户设备从空闲小区接入, 可以将空闲小 区信息通过非接入层 (NAS ) 消息发送给用户设备, 由用户设备选择合适 的小区进行接入。 在 4G中, 也可以将空闲小区信息通过系统消息 (S1 ) 接入点 (AP ) 消息头发送给 RAN设备, 由 RAN设备指示用户设备选择 合适的小区接入。 在 3G中, 也可以将空闲小区信息通过 RAN AP消息头 发送给 RAN设备, 由 RAN设备指示用户设备选择合适的小区接入。 在 2G中, 也可以将空闲小区信息通过基站子系统(BSS ) AP消息头发送给 RAN设备, 由 RAN设备指示用户设备选择合适的小区接入。
S308、当 RAN设备检测到 RAN设备内发生拥塞的参与运营商拥塞状 况缓解时, 向 MME/SGSN发送拥塞缓解通知消息。
其中, 例如当发生拥塞的 RAN设备中 MVNO的所占资源(连接数资 源 /带宽资源) 逐渐减少, 达到或低于该 MVNO预设的拥塞缓解门限值, RAN设备判断此 MVNO的拥塞状况得到缓解。 RAN设备可以向与之连接 的所有 MME/SGSN 发送拥塞缓解通知消息; 也可以仅向与发生拥塞的 MVNO相关的 MME/SGSN发送拥塞缓解通知消息, 例如, RAN设备根据 发生拥塞的 MVNO的标识(如 MVNO ID, IMSI号段, PLMN ID等)选 择相应的 MME/SGSN发送拥塞缓解通知消息。
S309、 MME/ SGSN向 RAN设备发送拥塞缓解响应消息。
图 4为本发明拥塞控制方法实施例四的信令交互图, 本实施例中的核 心网设备包括 MME/ SGSN、 S-GW、 P-GW/ GGSN和 PCRF, 如图 4所示, 本实施例的方法可以包括:
本实施例中 S401〜S404与图 3所示实施例三中歩骤 S301〜S304中相 同, 此处不再赘述。
S405、 PCRF向 P-GW/GGSN发送 IP-CAN会话修改请求。
5406、 P-GW/GGSN根据 IP-CAN会话修改请求通过 S-GW向 MME/ SGSN发起承载建立 /修改请求, 承载建立 /修改请求中包含 UE的 IMSI信 息 /UE的参与运营商标识。
5407、 MME/ SGSN根据 IMSI信息 /参与运营商标识和拥塞通知消息, 拒绝承载建立 /修改请求。 具体例如为,当 RAN设备向 MME/SGSN发送的拥塞通知消息中包含的 拥塞原因是连接数资源和 /或带宽资源超出预设值导致的拥塞, 且 MME/SGSN根据 IMSI信息或 /参与运营商标识判断 UE属于发生上述拥塞 的参与运营商。 根据不同情况分别执行下列动作:
当拥塞原因为连接数资源不足, 且 MME/SGSN收到的请求消息类型 为承载建立请求, 则 MME/SGSN拒绝该承载建立请求。
当拥塞原因为带宽资源不足, MME/SGSN 收到的请求消息类型为承 载更新请求, 且承载更新需要增大该承载的带宽; 或 MME/SGSN收到的 请求消息类型为承载新建请求, 则 MME/SGSN拒绝该承载更新请求。
S408、 MME/ SGSN通过 S-GW向 P-GW/GGSN发起承载建立 /修改拒 绝响应, 承载建立 /修改拒绝响应包括拒绝原因。
S409.P-GW/GGSN向 PCRF发送 IP-CAN会话修改响应消息, IP-CAN 会话修改响应消息中包含拒绝原因。
具体地, MME/SGSN根据上述流程中所作的决策通过 S-GW向 P-GW/GGSN发起承载建立 /修改拒绝响应, 例如响应中可以包含拒绝原因 为 MVNO发生拥塞类型是连接数资源和 /或带宽资源超出预设值的拥塞。 P-GW/GGSN向 PCRF发送 IP-CAN会话修改响应消息,消息中可以包含拒绝 原因为 MVNO发生拥塞类型是连接数资源和 /或带宽资源超出预设值的拥 塞。
S410、当 RAN设备检测到 RAN设备内发生拥塞的参与运营商拥塞状 况缓解时, 向 MME/SGSN发送拥塞缓解通知消息。
其中, 例如当发生拥塞的 RAN设备中 MVNO的所占资源(连接数资 源 /带宽资源) 逐渐减少, 达到或低于该 MVNO预设的拥塞缓解门限值, RAN设备判断此 MVNO的拥塞状况得到缓解。 RAN设备可以向与之连接 的所有 MME/SGSN 发送拥塞缓解通知消息; 也可以仅向与发生拥塞的 MVNO相关的 MME/SGSN发送拥塞缓解通知消息, 例如, RAN设备根据 发生拥塞的 MVNO的标识(如 MVNO ID, IMSI号段, PLMN ID等)选 择相应的 MME/SGSN发送拥塞缓解通知消息。
S411、 MME/ SGSN向 RAN设备发送拥塞缓解响应消息。
图 5为本发明拥塞控制方法实施例五的信令交互图, 本实施例中的核 心网设备包括 MME/ SGSN、 S-GW、 P-GW/ GGSN和 PCRF, 如图 5所示, 本实施例的方法可以包括:
5501、 RAN设备根据参与运营商的资源使用情况检测拥塞的发生。 具体为例如 RAN设备实时统计各个参与运营商 MVNO的资源使用情 况, 当某虚拟运营商在该 RAN设备上的资源使用量不断增加以至达到或 超过之前预设的该 MVNO的拥塞门限值时, 判定为该虚拟运营商在 RAN 设备发生拥塞。
5502、 当 RAN设备检测到某一个或多个参与运营商发生拥塞时, 向 与发生拥塞的参与运营商相关的 MME/ SGSN发送拥塞通知消息, 拥塞通 知消息包括发生拥塞的参与运营商标识。
具体地, 例如, RAN设备根据发生拥塞的 MVNO的标识(如 MVNO ID, IMSI号段, PLMN ID等) 选择相应的 MME/SGSN发送拥塞通知消 息。 RAN设备也可以向与之连接的所有的 MME/ SGSN发送拥塞通知消 息。
拥塞通知消息还包括下述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 RAN设备或 RAN设备的相邻 RAN设备的其他可用 的小区信息和 RAN设备或 RAN设备的相邻 RAN设备的其他可用的小区 中参与运营商标识对应的参与运营商的资源使用情况。
S503、 MME/ SGSN通过 S-GW向 P-GW/GGSN发送承载更新请求消息, 承载更新请求消息包括拥塞通知消息的内容。
5504、 P-GW/GGSN接收并记录承载更新请求消息。
5505, P-GW/GGSN通过 S-GW和 MME/ SGSN向 RAN设备发送拥 塞通知响应消息。
S506、 PCRF向 P-GW/GGSN发送 IP-CAN会话修改请求。
5507、 P-GW/GGSN根据拥塞通知消息和 IP-CAN会话修改请求的类 型判断, 拒绝 IP-CAN会话修改请求。
5508, P-GW/GGSN向 PCRF发送 IP-CAN会话修改响应消息, IP-CAN 会话修改响应消息中包含拒绝原因。
S509、当 RAN设备检测到 RAN设备内发生拥塞的参与运营商拥塞状 况缓解时, 向 MME/SGSN发送拥塞缓解通知消息。
其中, 例如当发生拥塞的 RAN设备中 MVNO的所占资源(连接数资 源 /带宽资源) 逐渐减少, 达到或低于该 MVNO预设的拥塞缓解门限值, RAN设备判断此 MVNO的拥塞状况得到缓解。 RAN设备可以向与之连接 的所有 MME/SGSN 发送拥塞缓解通知消息; 也可以仅向与发生拥塞的 MVNO相关的 MME/SGSN发送拥塞缓解通知消息, 例如, RAN设备根据 发生拥塞的 MVNO的标识(如 MVNO ID, IMSI号段, PLMN ID等)选 择相应的 MME/SGSN发送拥塞缓解通知消息。
5510、 MME/ SGSN通过 S-GW向 P-GW/GGSN发送拥塞缓解通知消 息。
5511、 P-GW/GGSN通过 S-GW和 MME/ SGSN向 RAN设备发送拥 塞缓解响应消息。
图 6为本发明拥塞控制方法实施例六的信令交互图, 本实施例中的核 心网设备包括 S-GW、 P-GW/ GGSN和 PCRF, 如图 6所示, 本实施例的 方法可以包括:
5601、 RAN设备根据参与运营商的资源使用情况检测拥塞的发生。 具体为例如 RAN设备实时统计各个参与运营商 MVNO的资源使用情 况, 当某虚拟运营商在该 RAN设备上的资源使用量不断增加以至达到或 超过之前预设的该 MVNO的拥塞门限值时, 判定为该虚拟运营商在 RAN 设备发生拥塞。
5602、 当 RAN设备检测到某一个或多个参与运营商发生拥塞时, 向 与发生拥塞的参与运营商相关的 S-GW发送拥塞通知消息, 拥塞通知消息 包括发生拥塞的参与运营商标识。
具体地, 例如, RAN设备根据发生拥塞的 MVNO的标识(如 MVNO ID, IMSI号段, PLMN ID等) 选择相应的 MME/SGSN发送拥塞通知消 息。 RAN设备也可以向与之连接的所有的 MME/ SGSN发送拥塞通知消 息。
拥塞通知消息还包括下述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 RAN设备或 RAN设备的相邻 RAN设备的其他可用 的小区信息和 RAN设备或 RAN设备的相邻 RAN设备的其他可用的小区 中参与运营商标识对应的参与运营商的资源使用情况。
5603、 S-GW将拥塞通知消息转发给 P-GW/ GGSN。
5604、 P-GW/ GGSN接收并记录拥塞通知消息。
S605、 P-GW/ GGSN通过 S-GW向 RAN设备发送拥塞通知响应消息。
5606、 PCRF向 P-GW/GGSN发送 IP-CAN会话修改请求。
5607、 P-GW/GGSN根据拥塞通知消息和 IP-CAN会话修改请求的类 型判断, 拒绝 IP-CAN会话修改请求。
5608、 P-GW/GGSN向 PCRF发送 IP-CAN会话修改响应消息, IP-CAN 会话修改响应消息中包含拒绝原因。
5609、 RAN设备检测到 RAN设备内发生拥塞的参与运营商拥塞状况 缓解时, 通过 S-GW向 P-GW/GGSN发送拥塞缓解通知消息。
5610、 P-GW/GGSN通过 S-GW向 RAN设备发送拥塞缓解响应消息。 其中, 拥塞缓解通知消息中包含如下信息的至少一项: 1 ) 拥塞状况 得到缓解的 MVNO 标识 (例如可以是用以标识发生拥塞的一个或多个 MVNO, 可以是 MVNO标识 (MVNO ID ) , 或者 MVNO对应的 IMSI号 段等; 2 ) 拥塞状况得到缓解的 MVNO的拥塞原因。
图 7为本发明核心网设备实施例一的结构示意图, 如图 7所示, 本实 施例的装置可以包括: 接收模块 11 和处理模块 12, 其中, 接收模块 11 用于接收 RAN设备检测到某一个或多个参与运营商发生拥塞时发送的拥 塞通知消息,拥塞通知消息包括发生拥塞的参与运营商标识。处理模块 12 用于根据拥塞通知消息, 对参与运营商标识对应的参与运营商进行拥塞控 制。
进一歩地, 拥塞通知消息还包括下述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 RAN设备或 RAN设备的相邻 RAN设备的其他可用 的小区信息和 RAN设备或 RAN设备的相邻 RAN设备的其他可用的小区 中参与运营商标识对应的参与运营商的资源使用情况。
针对核心网设备的不同, 本实施例中有四种可实施的方式, 作为第一 种可实施的方式, 核心网设备为 MME/SGSN时, MME/SGSN包括: 第一 接收模块、 第一发送模块和第一处理模块, 其中, 第一接收模块用于接收
RAN 设备检测到某一个或多个参与运营商发生拥塞时发送的拥塞通知消 息。 第一发送模块用于记录拥塞通知消息, 并向 RAN设备发送拥塞通知 响应消息。 第一接收模块还用于接收用户设备 UE通过 RAN设备发送的 接入请求, 接入请求包含所要接入的参与运营商信息。 第一处理模块用于 根据接入请求包含的参与运营商信息和拥塞通知消息, 向 UE发送接入拒 绝消息。
其中, 在 4G 网络下, 接入请求为附着请求, 或者, 接入请求为 UE 发起的服务请求; 或者, 接入请求为跟踪区更新请求; 或者, 接入请求为 路由区更新请求。
在 2G/3G网络下, 接入请求为 UE发起的一次 /二次 PDP上下文建立 或修改请求。
接入拒绝消息还包括: 接入拒绝原因和空闲小区指示信息, 用于 UE 选择接入空闲小区指示信息指示的空闲小区。
作为第二种可能的实施方式, 核心网设备包括 MME/ SGSN、 S-GW,
P-GW/ GGSN和 PCRF时, MME/SGSN包括: 第二接收模块和第二发送 模块, 第二接收模块用于接收 RAN设备检测到某一个或多个参与运营商 发生拥塞时发送的拥塞通知消息。 第二发送模块用于记录拥塞通知消息, 并向 RAN设备发送拥塞通知响应消息。
PCRF包括第三发送模块, 第三发送模块用于向 P-GW/GGSN发送 IP 连接接入网络 IP-CAN会话修改请求。
P-GW/GGSN包括第四发送模块, 第四发送模块用于根据 IP-CAN会 话修改请求通过 S-GW向 MME/ SGSN发起承载建立 /修改请求,承载建立 /修改请求中包含 UE的国际移动用户标识 IMSI信息 /UE的参与运营商标 识。
MME/ SGSN 还包括: 第二处理模块, 第二处理模块用于根据 IMSI 信息 /参与运营商标识和拥塞通知消息, 拒绝承载建立 /修改请求。
进一歩地, 第二发送模块还用于: 通过 S-GW向 P-GW/GGSN发起承 载建立 /修改拒绝响应, 承载建立 /修改拒绝响应包括拒绝原因。
第四发送模块还用于: 向 PCRF 发送 IP-CAN 会话修改响应消息, IP-CAN会话修改响应消息中包含拒绝原因。
在上述两种实施方式中, 进一歩地, 第二接收模块还用于: 接收 RAN 设备检测到 RAN设备内发生拥塞的参与运营商拥塞状况缓解时发送的拥 塞缓解通知消息。 第二发送模块还用于向 RAN设备发送拥塞缓解响应消 息。
作为第三种可能的实施方式, 核心网设备包括 MME/ SGSN、 S-GW、 P-GW/ GGSN和 PCRF时, MME/SGSN包括: 第三接收模块和第五发送 模块, 第三接收模块用于接收 RAN设备检测到某一个或多个参与运营商 发生拥塞时发送的拥塞通知消息。 第五发送模块用于通过 S-GW 向 P-GW/GGSN发送承载更新请求消息, 承载更新请求消息包括拥塞通知消 息的内容。
P-GW/GGSN包括: 第四接收模块和第六发送模块, 其中, 第四接收 模块用于接收承载更新请求消息。第六发送模块用于记录承载更新请求消 息, 并通过 S-GW和 MME/ SGSN向 RAN设备发送拥塞通知响应消息。
PCRF包括第七发送模块, 第七发送模块用于向 P-GW/GGSN发送 IP 连接接入网络 IP-CAN会话修改请求。
P-GW/GGSN还包括: 第三处理模块, 第三处理模块用于根据拥塞通 知消息和 IP-CAN会话修改请求的类型判断,拒绝 IP-CAN会话修改请求。
进一歩地, 第六发送模块还用于: 向 PCRF发送 IP-CAN会话修改响 应消息, IP-CAN会话修改响应消息中包含拒绝原因。
进一歩地,第三接收模块还用于接收 RAN设备检测到 RAN设备内发 生拥塞的参与运营商拥塞状况缓解时发送的拥塞缓解通知消息。
第五发送模块还用于通过 S-GW向 P-GW/GGSN发送拥塞缓解通知消 白E、。
第六发送模块还用于通过 S-GW和 MME/ SGSN向 RAN设备发送拥 塞缓解响应消息。
作为第四种可能的实施方式, 核心网设备包括 S-GW、 P-GW/ GGSN 和 PCRF时, P-GW/ GGSN包括: 第五接收模块和第七发送模块, 第五接 收模块用于通过 S-GW接收 RAN设备检测到某一个或多个参与运营商发 生拥塞时发送的拥塞通知消息。 第七发送模块用于记录拥塞通知消息, 并 通过 S-GW向 RAN设备发送拥塞通知响应消息。
PCRF包括: 第八发送模块, 第八发送模块用于向 P-GW/GGSN发送 IP-CAN会话修改请求。
P-GW/GGSN包括: 第四处理模块, 第四处理模块用于根据拥塞通知 消息和 IP-CAN会话修改请求的类型判断, 拒绝 IP-CAN会话修改请求。
进一歩地, 第七发送模块还用于: 向 PCRF发送 IP-CAN会话修改响 应消息, IP-CAN会话修改响应消息中包含拒绝原因。
进一歩地, 第五接收模块还用于: 通过 S-GW接收 RAN设备检测到 RAN 设备内发生拥塞的参与运营商拥塞状况缓解时发送的拥塞缓解通知 消息。 第七发送模块还用于: 通过 S-GW向 RAN设备发送拥塞缓解响应 消息。
本实施例的装置, 可以用于执行图 1所示方法实施例的技术方案, 其 实现原理类似, 此处不再赘述。
本发明实施例提供的核心网设备, 通过接收模块接收 RAN设备检测 到某一个或多个参与运营商发生拥塞时发送的拥塞通知消息, 拥塞通知消 息包括发生拥塞的参与运营商标识。 然后处理模块根据拥塞通知消息, 对 参与运营商标识对应的参与运营商进行拥塞控制。 因此可区分不同的参与 运营商进行拥塞控制, 实现了针对特定的拥塞对象以及拥塞原因进行精确 高效的拥塞控制, 同时保护了未发生拥塞的参与运营商的连接数资源以及 带宽资源。
图 8为本发明 RAN设备实施例一的结构示意图, 如图 8所示, 本实 施例的装置可以包括: 检测模块 21 和发送模块 22, 其中, 检测模块 21 用于根据参与运营商的资源使用情况检测拥塞的发生。 发送模块 22用于 当检测模块 21 检测到某一个或多个参与运营商发生拥塞时, 向与发生拥 塞的参与运营商相关的核心网设备发送拥塞通知消息, 拥塞通知消息包括 发生拥塞的参与运营商标识, 用于核心网设备对参与运营商标识对应的参 与运营商进行拥塞控制。
进一歩地, 拥塞通知消息还包括下述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 RAN设备或 RAN设备的相邻 RAN设备的其他可用 的小区信息和 RAN设备或 RAN设备的相邻 RAN设备的其他可用的小区 中参与运营商标识对应的参与运营商的资源使用情况。
针对核心网设备的不同, 本实施例中有四种可实施的方式, 作为第一 种可实施的方式, 核心网设备为 MME/SGSN时, 发送模块 22用于:
当检测模块 21 检测到某一个或多个参与运营商发生拥塞时, 向与发 生拥塞的参与运营商相关的 MME/ SGSN发送拥塞通知消息, 用于 MME/ SGSN记录拥塞通知消息, 并根据拥塞通知消息, 对参与运营商标识对应 的参与运营商进行拥塞控制。
RAN设备还包括:第一接收模块,第一接收模块用于接收 MME/ SGSN 发送的拥塞通知响应消息。
作为第二种可实施的方式, 核心网设备包括 MME/ SGSN, S-GW、 P-GW/ GGSN和 PCRF时, 发送模块 22用于:
当检测模块 21 检测到某一个或多个参与运营商发生拥塞时, 向与发 生拥塞的参与运营商相关的 MME/ SGSN发送拥塞通知消息, 用于 MME/ SGSN记录拥塞通知消息。
RAN设备还包括:第二接收模块,第二接收模块用于接收 MME/ SGSN 发送的拥塞通知响应消息。
在上述两种实施方式中, 发送模块 22还用于:
当检测模块 21检测到 RAN设备内发生拥塞的参与运营商拥塞状况缓 解时, 向 MME/ SGSN发送拥塞缓解通知消息。
第一接收模块或第二接收模块还用于: 接收 MME/ SGSN发送的拥塞 缓解响应消息。
作为第三种可实施的方式, 核心网设备包括 MME/ SGSN, S-GW、 P-GW/ GGSN和 PCRF时, 发送模块 22用于:
当检测模块 21 检测到某一个或多个参与运营商发生拥塞时, 向与发 生拥塞的参与运营商相关的 MME/ SGSN发送拥塞通知消息, 用于 MME/ SGSN通过 S-GW向 P-GW/GGSN发送承载更新请求消息, 承载更新请求 消息包括拥塞通知消息的内容;
RAN 设备还包括: 第三接收模块, 第三接收模块用于接收 P-GW/GGSN通过 S-GW和 MME/ SGSN发送的拥塞通知响应消息。 进一歩地, 发送模块 22还用于:
当检测模块 21检测到 RAN设备内发生拥塞的参与运营商拥塞状况缓 解时, 向 MME/ SGSN发送拥塞缓解通知消息, 用于 MME/ SGSN通过 S-GW向 P-GW/GGSN发送拥塞缓解通知消息。
第三接收模块还用于接收 P-GW/GGSN通过 S-GW和 MME/ SGSN发 送的拥塞缓解响应消息。
作为第四种可实施的方式, 核心网设备包括 S-GW、 P-GW/ GGSN和 PCRF时, 发送模块 22用于:
当检测模块 21 检测到某一个或多个参与运营商发生拥塞时, 向与发 生拥塞的参与运营商相关的 S-GW 发送拥塞通知消息, 用于 S-GW 向 P-GW/GGSN发送拥塞通知消息。
RAN设备还包括:
第四接收模块, 用于接收 P-GW/GGSN通过 S-GW发送的拥塞通知响 应消息。
进一歩地, 发送模块 22还用于:
当检测模块 21检测到 RAN设备内发生拥塞的参与运营商拥塞状况缓 解时, 向 S-GW发送拥塞缓解通知消息, 用于 S-GW向 P-GW/GGSN发送 拥塞缓解通知消息。
第四接收模块还用于接收 P-GW/GGSN通过 S-GW发送的拥塞缓解响 应消息。
本实施例的装置, 可以用于执行图 2所示方法实施例的技术方案, 其 实现原理和技术效果类似, 此处不再赘述。
本发明实施例提供的 RAN设备, 通过检测模块根据参与运营商的资 源使用情况检测拥塞的发生, 当 RAN设备检测到某一个或多个参与运营 商发生拥塞时, 发送模块向与发生拥塞的参与运营商相关的核心网设备发 送拥塞通知消息, 拥塞通知消息包括发生拥塞的参与运营商标识, 用于核 心网设备对参与运营商标识对应的参与运营商进行拥塞控制。 因此可区分 不同的参与运营商进行拥塞控制, 实现了针对特定的拥塞对象以及拥塞原 因进行精确高效的拥塞控制, 同时保护了未发生拥塞的参与运营商的连接 数资源以及带宽资源。 本发明实施例提供的通信系统, 包括图 7所示的核心网设备和图 8所 示的 RAN设备。
图 9为本发明核心网设备实施例二的结构示意图, 如图 9所示, 本实 施例的装置可以包括: 接收器 31和处理器 32, 其中, 接收器 31用于接收 RAN 设备检测到某一个或多个参与运营商发生拥塞时发送的拥塞通知消 息, 拥塞通知消息包括发生拥塞的参与运营商标识。 处理器 32用于根据 拥塞通知消息, 对参与运营商标识对应的参与运营商进行拥塞控制。
进一歩地, 拥塞通知消息还包括下述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 RAN设备或 RAN设备的相邻 RAN设备的其他可用 的小区信息和 RAN设备或 RAN设备的相邻 RAN设备的其他可用的小区 中参与运营商标识对应的参与运营商的资源使用情况。
针对核心网设备的不同, 本实施例中有四种可实施的方式, 作为第一 种可实施的方式, 核心网设备为 MME/SGSN时, MME/SGSN包括: 第一 接收器、 第一发送器和第一处理器, 其中, 第一接收器用于接收 RAN设 备检测到某一个或多个参与运营商发生拥塞时发送的拥塞通知消息。第一 发送器用于记录拥塞通知消息, 并向 RAN设备发送拥塞通知响应消息。 第一接收器还用于接收用户设备 UE通过 RAN设备发送的接入请求, 接 入请求包含所要接入的参与运营商信息。第一处理器用于根据接入请求包 含的参与运营商信息和拥塞通知消息, 向 UE发送接入拒绝消息。
其中, 在 4G 网络下, 接入请求为附着请求, 或者, 接入请求为 UE 发起的服务请求; 或者, 接入请求为跟踪区更新请求; 或者, 接入请求为 路由区更新请求。
在 2G/3G网络下, 接入请求为 UE发起的一次 /二次 PDP上下文建立 或修改请求。
接入拒绝消息还包括: 接入拒绝原因和空闲小区指示信息, 用于 UE 选择接入空闲小区指示信息指示的空闲小区。
作为第二种可能的实施方式, 核心网设备包括 MME/ SGSN、 S-GW、 P-GW/ GGSN和 PCRF时, MME/SGSN包括: 第二接收器和第二发送器, 第二接收器用于接收 RAN设备检测到某一个或多个参与运营商发生拥塞 时发送的拥塞通知消息。 第二发送器用于记录拥塞通知消息, 并向 RAN 设备发送拥塞通知响应消息。
PCRF包括第三发送器,第三发送器用于向 P-GW/GGSN发送 IP连接 接入网络 IP-CAN会话修改请求。
P-GW/GGSN包括第四发送器, 第四发送器用于根据 IP-CAN会话修 改请求通过 S-GW向 MME/ SGSN发起承载建立 /修改请求, 承载建立 /修 改请求中包含 UE的国际移动用户标识 IMSI信息 /UE的参与运营商标识。
MME/ SGSN还包括: 第二处理器, 第二处理器用于根据 IMSI信息 / 参与运营商标识和拥塞通知消息, 拒绝承载建立 /修改请求。
进一歩地, 第二发送器还用于: 通过 S-GW向 P-GW/GGSN发起承载 建立 /修改拒绝响应, 承载建立 /修改拒绝响应包括拒绝原因。
第四发送器还用于:向 PCRF发送 IP-CAN会话修改响应消息, IP-CAN 会话修改响应消息中包含拒绝原因。
在上述两种实施方式中, 进一歩地, 第二接收器还用于: 接收 RAN 设备检测到 RAN设备内发生拥塞的参与运营商拥塞状况缓解时发送的拥 塞缓解通知消息。第二发送器还用于向 RAN设备发送拥塞缓解响应消息。
作为第三种可能的实施方式, 核心网设备包括 MME/ SGSN、 S-GW, P-GW/ GGSN和 PCRF时, MME/SGSN包括: 第三接收器和第五发送器, 第三接收器用于接收 RAN设备检测到某一个或多个参与运营商发生拥塞 时发送的拥塞通知消息。第五发送器用于通过 S-GW向 P-GW/GGSN发送 承载更新请求消息, 承载更新请求消息包括拥塞通知消息的内容。
P-GW/GGSN包括: 第四接收器和第六发送器, 其中, 第四接收器用 于接收承载更新请求消息。 第六发送器用于记录承载更新请求消息, 并通 过 S-GW和 MME/ SGSN向 RAN设备发送拥塞通知响应消息。
PCRF包括第七发送器,第七发送器用于向 P-GW/GGSN发送 IP连接 接入网络 IP-CAN会话修改请求。
P-GW/GGSN还包括: 第三处理器, 第三处理器用于根据拥塞通知消 息和 IP-CAN会话修改请求的类型判断, 拒绝 IP-CAN会话修改请求。
进一歩地, 第六发送器还用于: 向 PCRF发送 IP-CAN会话修改响应 消息, IP-CAN会话修改响应消息中包含拒绝原因。 进一歩地,第三接收器还用于接收 RAN设备检测到 RAN设备内发生 拥塞的参与运营商拥塞状况缓解时发送的拥塞缓解通知消息。
第五发送器还用于通过 S-GW 向 P-GW/GGSN发送拥塞缓解通知消 息。
第六发送器还用于通过 S-GW和 MME/ SGSN向 RAN设备发送拥塞 缓解响应消息。
作为第四种可能的实施方式, 核心网设备包括 S-GW、 P-GW/ GGSN 和 PCRF时, P-GW/ GGSN包括: 第五接收器和第七发送器, 第五接收器 用于通过 S-GW接收 RAN设备检测到某一个或多个参与运营商发生拥塞 时发送的拥塞通知消息。第七发送器用于记录拥塞通知消息,并通过 S-GW 向 RAN设备发送拥塞通知响应消息。
PCRF包括:第八发送器,第八发送器用于向 P-GW/GGSN发送 IP-CAN 会话修改请求。
P-GW/GGSN包括: 第四处理器, 第四处理器用于根据拥塞通知消息 和 IP-CAN会话修改请求的类型判断, 拒绝 IP-CAN会话修改请求。
进一歩地, 第七发送器还用于: 向 PCRF发送 IP-CAN会话修改响应 消息, IP - CAN会话修改响应消息中包含拒绝原因。
进一歩地,第五接收器还用于:通过 S-GW接收 RAN设备检测到 RAN 设备内发生拥塞的参与运营商拥塞状况缓解时发送的拥塞缓解通知消息。 第七发送器还用于: 通过 S-GW向 RAN设备发送拥塞缓解响应消息。
本实施例的装置, 可以用于执行图 1所示方法实施例的技术方案, 其 实现原理类似, 此处不再赘述。
本发明实施例提供的核心网设备, 通过接收器接收 RAN设备检测到 某一个或多个参与运营商发生拥塞时发送的拥塞通知消息, 拥塞通知消息 包括发生拥塞的参与运营商标识。 然后处理器根据拥塞通知消息, 对参与 运营商标识对应的参与运营商进行拥塞控制。 因此可区分不同的参与运营 商进行拥塞控制, 实现了针对特定的拥塞对象以及拥塞原因进行精确高效 的拥塞控制, 同时保护了未发生拥塞的参与运营商的连接数资源以及带宽 资源。
图 10为本发明 RAN设备实施例二的结构示意图, 如图 10所示, 本 实施例的装置可以包括: 处理器 41和发送器 42, 其中, 处理器 41用于根 据参与运营商的资源使用情况检测拥塞的发生。 发送器 42用于当处理器 41检测到某一个或多个参与运营商发生拥塞时,向与发生拥塞的参与运营 商相关的核心网设备发送拥塞通知消息, 拥塞通知消息包括发生拥塞的参 与运营商标识, 用于核心网设备对参与运营商标识对应的参与运营商进行 拥塞控制。
进一歩地, 拥塞通知消息还包括下述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 RAN设备或 RAN设备的相邻 RAN设备的其他可用 的小区信息和 RAN设备或 RAN设备的相邻 RAN设备的其他可用的小区 中参与运营商标识对应的参与运营商的资源使用情况。
针对核心网设备的不同, 本实施例中有四种可实施的方式, 作为第一 种可实施的方式, 核心网设备为 MME/SGSN时, 发送器 42用于:
当处理器 41 检测到某一个或多个参与运营商发生拥塞时, 向与发生 拥塞的参与运营商相关的 MME/ SGSN 发送拥塞通知消息, 用于 MME/ SGSN记录拥塞通知消息, 并根据拥塞通知消息, 对参与运营商标识对应 的参与运营商进行拥塞控制。
RAN设备还包括: 第一接收器, 第一接收器用于接收 MME/ SGSN发 送的拥塞通知响应消息。
作为第二种可实施的方式, 核心网设备包括 MME/ SGSN, S-GW、
P-GW/ GGSN和 PCRF时, 发送器 42用于:
当处理器 41 检测到某一个或多个参与运营商发生拥塞时, 向与发生 拥塞的参与运营商相关的 MME/ SGSN 发送拥塞通知消息, 用于 MME/ SGSN记录拥塞通知消息。
RAN设备还包括: 第二接收器, 第二接收器用于接收 MME/ SGSN发 送的拥塞通知响应消息。
在上述两种实施方式中, 发送器 42还用于:
当处理器 41检测到 RAN设备内发生拥塞的参与运营商拥塞状况缓解 时, 向 MME/ SGSN发送拥塞缓解通知消息。
第一接收器或第二接收器还用于: 接收 MME/ SGSN发送的拥塞缓解 响应消息。
作为第三种可实施的方式, 核心网设备包括 MME/ SGSN、 S-GW, P-GW/ GGSN和 PCRF时, 发送器 42用于:
当处理器 41 检测到某一个或多个参与运营商发生拥塞时, 向与发生 拥塞的参与运营商相关的 MME/ SGSN 发送拥塞通知消息, 用于 MME/ SGSN通过 S-GW向 P-GW/GGSN发送承载更新请求消息, 承载更新请求 消息包括拥塞通知消息的内容;
RAN 设备还包括: 第三接收器, 第三接收器用于接收 P-GW/GGSN 通过 S-GW和 MME/ SGSN发送的拥塞通知响应消息。
进一歩地, 发送器 42还用于:
当处理器 41检测到 RAN设备内发生拥塞的参与运营商拥塞状况缓解 时,向 MME/ SGSN发送拥塞缓解通知消息,用于 MME/ SGSN通过 S-GW 向 P-GW/GGSN发送拥塞缓解通知消息。
第三接收器还用于接收 P-GW/GGSN通过 S-GW和 MME/ SGSN发送 的拥塞缓解响应消息。
作为第四种可实施的方式, 核心网设备包括 S-GW、 P-GW/ GGSN和 PCRF时, 发送器 42用于:
当处理器 41 检测到某一个或多个参与运营商发生拥塞时, 向与发生 拥塞的参与运营商相关的 S-GW 发送拥塞通知消息, 用于 S-GW 向 P-GW/GGSN发送拥塞通知消息。
RAN设备还包括:
第四接收器, 用于接收 P-GW/GGSN通过 S-GW发送的拥塞通知响应 消息。
进一歩地, 发送器 42还用于:
当处理器 41检测到 RAN设备内发生拥塞的参与运营商拥塞状况缓解 时, 向 S-GW发送拥塞缓解通知消息, 用于 S-GW向 P-GW/GGSN发送拥 塞缓解通知消息。
第四接收器还用于接收 P-GW/GGSN通过 S-GW发送的拥塞缓解响应 消息。
本实施例的装置, 可以用于执行图 2所示方法实施例的技术方案, 其 实现原理和技术效果类似, 此处不再赘述。
本发明实施例提供的 RAN设备, 通过处理器根据参与运营商的资源 使用情况检测拥塞的发生, 当 RAN设备检测到某一个或多个参与运营商 发生拥塞时, 发送器向与发生拥塞的参与运营商相关的核心网设备发送拥 塞通知消息, 拥塞通知消息包括发生拥塞的参与运营商标识, 用于核心网 设备对参与运营商标识对应的参与运营商进行拥塞控制。 因此可区分不同 的参与运营商进行拥塞控制, 实现了针对特定的拥塞对象以及拥塞原因进 行精确高效的拥塞控制, 同时保护了未发生拥塞的参与运营商的连接数资 源以及带宽资源。
本发明实施例提供的通信系统, 包括图 9所示的核心网设备和图 10 所示的 RAN设备。
在本发明所提供的几个实施例中,应该理解到,所揭露的装置和方法, 可以通过其它的方式实现。 例如, 以上所描述的装置实施例仅仅是示意性 的, 例如, 所述单元的划分, 仅仅为一种逻辑功能划分, 实际实现时可以 有另外的划分方式, 例如多个单元或组件可以结合或者可以集成到另一个 系统, 或一些特征可以忽略, 或不执行。 另一点, 所显示或讨论的相互之 间的耦合或直接耦合或通信连接可以是通过一些接口, 装置或单元的间接 耦合或通信连接, 可以是电性, 机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的, 作为单元显示的部件可以是或者也可以不是物理单元, 即可以位于一个地 方, 或者也可以分布到多个网络单元上。 可以根据实际的需要选择其中的 部分或者全部单元来实现本实施例方案的目的。
另外, 在本发明各个实施例中的各功能单元可以集成在一个处理单元 中, 也可以是各个单元单独物理存在, 也可以两个或两个以上单元集成在 —个单元中。 上述集成的单元既可以采用硬件的形式实现, 也可以采用硬 件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元, 可以存储在一个计算 机可读取存储介质中。 上述软件功能单元存储在一个存储介质中, 包括若 干指令用以使得一台计算机设备 (可以是个人计算机, 服务器, 或者网络 设备等) 或处理器 (processor) 执行本发明各个实施例所述方法的部分歩 骤。 而前述的存储介质包括: U 盘、 移动硬盘、 只读存储器 (Read-Only Memory, ROM) 、 随机存取存储器 ( Random Access Memory, RAM ) 、 磁碟或者光盘等各种可以存储程序代码的介质。
本领域技术人员可以清楚地了解到, 为描述的方便和简洁, 仅以上述 各功能模块的划分进行举例说明, 实际应用中, 可以根据需要而将上述功 能分配由不同的功能模块完成, 即将装置的内部结构划分成不同的功能模 块, 以完成以上描述的全部或者部分功能。 上述描述的装置的具体工作过 程, 可以参考前述方法实施例中的对应过程, 在此不再赘述。
最后应说明的是: 以上各实施例仅用以说明本发明的技术方案, 而非 对其限制; 尽管参照前述各实施例对本发明进行了详细的说明, 本领域的 普通技术人员应当理解: 其依然可以对前述各实施例所记载的技术方案进 行修改, 或者对其中部分或者全部技术特征进行等同替换; 而这些修改或 者替换, 并不使相应技术方案的本质脱离本发明各实施例技术方案的范 围。

Claims

权 利 要 求 书
1、 一种拥塞控制方法, 其特征在于, 包括:
核心网设备接收无线接入网 RAN设备检测到某一个或多个参与运营 商发生拥塞时发送的拥塞通知消息, 所述拥塞通知消息包括发生拥塞的参 与运营商标识, 所述参与运营商为移动虚拟网络运营商 MVNO或共享运 营商网络的运营商;
所述核心网设备根据所述拥塞通知消息, 对所述参与运营商标识对应 的参与运营商进行拥塞控制。
2、 根据权利要求 1 所述的方法, 其特征在于, 所述拥塞通知消息还 包括下述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 所述 RAN设备或所述 RAN设备的相邻 RAN设备的 其他可用的小区信息和所述 RAN设备或所述 RAN设备的相邻 RAN设备 的其他可用的小区中所述参与运营商标识对应的参与运营商的资源使用 情况。
3、 根据权利要求 2所述的方法, 其特征在于, 所述核心网设备为移 动管理实体 MME/服务 GPRS支持节点 SGSN, 所述核心网设备接收无线 接入网 RAN设备检测到某一个或多个参与运营商发生拥塞时发送的拥塞 通知消息, 包括:
所述 MME/ SGSN接收 RAN设备检测到某一个或多个参与运营商发 生拥塞时发送的拥塞通知消息;
所述 MME/ SGSN记录所述拥塞通知消息, 并向所述 RAN设备发送 拥塞通知响应消息;
所述核心网设备根据所述拥塞通知消息, 对所述参与运营商标识对应 的参与运营商进行拥塞控制, 包括:
所述 MME/ SGSN接收用户设备 UE通过所述 RAN设备发送的接入请 求, 所述接入请求包含所要接入的参与运营商信息;
所述 MME/ SGSN根据所述接入请求包含的所述参与运营商信息和拥 塞通知消息, 向所述 UE发送接入拒绝消息。
4、 根据权利要求 3所述的方法, 其特征在于, 在 4G网络下, 所述接 入请求为附着请求; 或者,
所述接入请求为 UE发起的服务请求; 或者,
所述接入请求为跟踪区更新请求; 或者,
所述接入请求为路由区更新请求;
在 2G/3G网络下, 所述接入请求为 UE发起的一次 /二次 PDP上下文 建立或修改请求;
所述接入拒绝消息还包括: 接入拒绝原因和空闲小区指示信息, 用于 所述 UE选择接入所述空闲小区指示信息指示的空闲小区。
5、 根据权利要求 2所述的方法, 其特征在于, 所述核心网设备包括 MME/ SGSN、服务网关 S-GW、分组数据网络网关 P-GW/网关 GPRS支持 节点 GGSN和策略与计费规则功能实体 PCRF, 所述核心网设备接收无线 接入网 RAN设备检测到某一个或多个参与运营商发生拥塞时发送的拥塞 通知消息, 包括:
MME/ SGSN接收 RAN设备检测到某一个或多个参与运营商发生拥 塞时发送的拥塞通知消息;
所述 MME/ SGSN记录所述拥塞通知消息, 并向所述 RAN设备发送 拥塞通知响应消息;
所述核心网设备根据所述拥塞通知消息, 对所述参与运营商标识对应 的参与运营商进行拥塞控制, 包括:
PCRF向 P-GW/GGSN发送 IP连接接入网络 IP-CAN会话修改请求; 所述 P-GW/GGSN根据所述 IP-CAN会话修改请求通过 S-GW向所述 MME/ SGSN发起承载建立 /修改请求, 所述承载建立 /修改请求中包含 UE 的国际移动用户标识 IMSI信息 /UE的参与运营商标识;
所述 MME/ SGSN根据所述 IMSI信息 /参与运营商标识和所述拥塞通 知消息, 拒绝所述承载建立 /修改请求。
6、 根据权利要求 5所述的方法, 其特征在于, 还包括:
所述 MME/ SGSN通过 S-GW向所述 P-GW/GGSN发起承载建立 /修改 拒绝响应, 所述承载建立 /修改拒绝响应包括拒绝原因;
所述 P-GW/GGSN向所述 PCRF发送 IP-CAN会话修改响应消息, 所 述 I P - C AN会话修改响应消息中包含所述拒绝原因。
7、 根据权利要求 3〜6任一项所述的方法, 其特征在于, 还包括: 所述 MME/ SGSN接收所述 RAN设备检测到所述 RAN设备内发生拥 塞的参与运营商拥塞状况缓解时发送的拥塞缓解通知消息;
所述 MME/ SGSN向所述 RAN设备发送拥塞缓解响应消息。
8、 根据权利要求 2所述的方法, 其特征在于, 所述核心网设备包括
MME/ SGSN、 S-GW, P-GW/ GGSN和 PCRF, 所述核心网设备接收无线 接入网 RAN设备检测到某一个或多个参与运营商发生拥塞时发送的拥塞 通知消息, 包括:
所述 MME/ SGSN接收 RAN设备检测到某一个或多个参与运营商发 生拥塞时发送的拥塞通知消息;
所述 MME/ SGSN通过所述 S-GW向所述 P-GW/GGSN发送承载更新 请求消息, 所述承载更新请求消息包括所述拥塞通知消息的内容;
所述 P-GW/GGSN接收所述承载更新请求消息;
所述 P-GW/GGSN记录所述承载更新请求消息, 并通过所述 S-GW和 所述 MME/ SGSN向所述 RAN设备发送拥塞通知响应消息;
所述核心网设备根据所述拥塞通知消息, 对所述参与运营商标识对应 的参与运营商进行拥塞控制, 包括:
PCRF向所述 P-GW/GGSN发送 IP连接接入网络 IP-CAN会话修改请 求;
所述 P-GW/GGSN根据所述拥塞通知消息和所述 IP-CAN会话修改请 求的类型判断, 拒绝所述 IP-CAN会话修改请求。
9、 根据权利要求 8所述的方法, 其特征在于, 还包括:
所述 P-GW/GGSN向所述 PCRF发送 IP-CAN会话修改响应消息, 所 述 IP-CAN会话修改响应消息中包含拒绝原因。
10、 根据权利要求 8或 9所述的方法, 其特征在于, 还包括: 所述 MME/ SGSN接收所述 RAN设备检测到所述 RAN设备内发生拥 塞的参与运营商拥塞状况缓解时发送的拥塞缓解通知消息;
所述 MME/ SGSN通过所述 S-GW向所述 P-GW/GGSN发送所述拥塞 缓解通知消息;
所述 P-GW/GGSN通过所述 S-GW和所述 MME/ SGSN向所述 RAN 设备发送拥塞缓解响应消息。
11、 根据权利要求 2所述的方法, 其特征在于, 所述核心网设备包括 S-GW、 P-GW/ GGSN和 PCRF, 所述核心网设备接收无线接入网 RAN设 备检测到某一个或多个参与运营商发生拥塞时发送的拥塞通知消息, 包 括:
所述 P-GW/ GGSN通过所述 S-GW接收 RAN设备检测到某一个或多 个参与运营商发生拥塞时发送的拥塞通知消息;
所述 P-GW/ GGSN记录所述拥塞通知消息,并通过所述 S-GW向所述 RAN设备发送拥塞通知响应消息;
所述核心网设备根据所述拥塞通知消息, 对所述参与运营商标识对应 的参与运营商进行拥塞控制, 包括:
PCRF向所述 P-GW/GGSN发送 IP-CAN会话修改请求;
所述 P-GW/GGSN根据所述拥塞通知消息和所述 IP-CAN会话修改请 求的类型判断, 拒绝所述 IP-CAN会话修改请求。
12、 根据权利要求 11所述的方法, 其特征在于, 还包括:
所述 P-GW/GGSN向所述 PCRF发送 IP-CAN会话修改响应消息, 所 述 IP-CAN会话修改响应消息中包含拒绝原因。
13、 根据权利要求 11或 12所述的方法, 其特征在于, 还包括: 所述 P-GW/GGSN通过所述 S-GW接收所述 RAN设备检测到所述 RAN 设备内发生拥塞的参与运营商拥塞状况缓解时发送的拥塞缓解通知 消息;
所述 P-GW/GGSN通过所述 S-GW向所述 RAN设备发送拥塞缓解响 应消息。
14、 一种拥塞控制方法, 其特征在于, 包括:
无线接入网 RAN设备根据参与运营商的资源使用情况检测拥塞的发 生, 所述参与运营商为移动虚拟网络运营商 MVNO或共享运营商网络的 运营商;
当所述 RAN设备检测到某一个或多个所述参与运营商发生拥塞时, 向与发生拥塞的所述参与运营商相关的核心网设备发送拥塞通知消息, 所 述拥塞通知消息包括发生拥塞的参与运营商标识, 用于所述核心网设备对 所述参与运营商标识对应的参与运营商进行拥塞控制。
15、 根据权利要求 14所述的方法, 其特征在于, 所述拥塞通知消息 还包括下述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 所述 RAN设备或所述 RAN设备的相邻 RAN设备的 其他可用的小区信息和所述 RAN设备或所述 RAN设备的相邻 RAN设备 的其他可用的小区中所述参与运营商标识对应的参与运营商的资源使用 情况。
16、 根据权利要求 15 所述的方法, 其特征在于, 所述核心网设备为 MME/ SGSN, 当所述 RAN设备检测到某一个或多个所述参与运营商发生 拥塞时, 向与发生拥塞的所述参与运营商相关的核心网设备发送拥塞通知 消息, 包括:
所述 RAN设备检测到某一个或多个所述参与运营商发生拥塞时, 向 与发生拥塞的所述参与运营商相关的 MME/ SGSN发送拥塞通知消息, 用 于所述 MME/ SGSN记录所述拥塞通知消息, 并根据所述拥塞通知消息, 对所述参与运营商标识对应的参与运营商进行拥塞控制;
所述方法还包括: 所述 RAN设备接收所述 MME/ SGSN发送的拥塞 通知响应消息。
17、 根据权利要求 15 所述的方法, 其特征在于, 所述核心网设备包 括 MME/ SGSN、 S-GW、 P-GW/ GGSN和 PCRF, 当所述 RAN设备检测 到某一个或多个所述参与运营商发生拥塞时, 向与发生拥塞的所述参与运 营商相关的核心网设备发送拥塞通知消息, 包括:
当所述 RAN设备检测到某一个或多个所述参与运营商发生拥塞时, 向与发生拥塞的所述参与运营商相关的 MME/ SGSN发送拥塞通知消息, 用于所述 MME/ SGSN记录所述拥塞通知消息;
所述方法还包括: 所述 RAN设备接收所述 MME/ SGSN发送的拥塞 通知响应消息。
18、 根据权利要求 15〜17任一项所述的方法, 其特征在于, 还包括: 所述 RAN设备检测到所述 RAN设备内发生拥塞的参与运营商拥塞状 况缓解时, 向所述 MME/ SGSN发送拥塞缓解通知消息; 所述 RAN设备接收所述 MME/ SGSN发送的拥塞缓解响应消息。
19、 根据权利要求 15 所述的方法, 其特征在于, 所述核心网设备包 括 MME/ SGSN, S-GW, P-GW/ GGSN和 PCRF, 当所述 RAN设备检测 到某一个或多个所述参与运营商发生拥塞时, 向与发生拥塞的所述参与运 营商相关的核心网设备发送拥塞通知消息, 包括:
当所述 RAN设备检测到某一个或多个所述参与运营商发生拥塞时, 向与发生拥塞的所述参与运营商相关的 MME/ SGSN发送拥塞通知消息, 用于所述 MME/ SGSN通过所述 S-GW向所述 P-GW/GGSN发送承载更新 请求消息, 所述承载更新请求消息包括所述拥塞通知消息的内容;
所述方法还包括:
所述 RAN设备接收所述 P-GW/GGSN通过所述 S-GW和所述 MME/ SGSN发送的拥塞通知响应消息。
20、 根据权利要求 19所述的方法, 其特征在于, 还包括:
所述 RAN设备检测到所述 RAN设备内发生拥塞的参与运营商拥塞状 况缓解时, 向所述 MME/ SGSN发送拥塞缓解通知消息, 用于所述 MME/ SGSN通过所述 S-GW向所述 P-GW/GGSN发送所述拥塞缓解通知消息; 所述 RAN设备接收所述 P-GW/GGSN通过所述 S-GW和所述 MME/ SGSN发送的拥塞缓解响应消息。
21、 根据权利要求 15 所述的方法, 其特征在于, 所述核心网设备包 括 S-GW、 P-GW/ GGSN和 PCRF, 当所述 RAN设备检测到某一个或多个 所述参与运营商发生拥塞时, 向与发生拥塞的所述参与运营商相关的核心 网设备发送拥塞通知消息, 包括:
当所述 RAN设备检测到某一个或多个所述参与运营商发生拥塞时, 向与发生拥塞的所述参与运营商相关的 S-GW发送拥塞通知消息, 用于所 述 S-GW向所述 P-GW/GGSN发送所述拥塞通知消息;
所述方法还包括:
所述 RAN设备接收所述 P-GW/GGSN通过所述 S-GW发送的拥塞通 知响应消息。
22、 根据权利要求 21所述的方法, 其特征在于, 还包括:
所述 RAN设备检测到所述 RAN设备内发生拥塞的参与运营商拥塞状 况缓解时, 向所述 S-GW发送拥塞缓解通知消息, 用于所述 S-GW向所述 P-GW/GGSN发送所述拥塞缓解通知消息;
所述 RAN设备接收所述 P-GW/GGSN通过所述 S-GW发送的拥塞缓 解响应消息。
23、 一种核心网设备, 其特征在于, 包括:
接收模块, 用于接收无线接入网 RAN设备检测到某一个或多个参与 运营商发生拥塞时发送的拥塞通知消息, 所述拥塞通知消息包括发生拥塞 的参与运营商标识, 所述参与运营商为移动虚拟网络运营商 MVNO或共 享运营商网络的运营商;
处理模块, 用于根据所述拥塞通知消息, 对所述参与运营商标识对应 的参与运营商进行拥塞控制。
24、 根据权利要求 23 所述的核心网设备, 其特征在于, 所述拥塞通 知消息还包括下述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 所述 RAN设备或所述 RAN设备的相邻 RAN设备的 其他可用的小区信息和所述 RAN设备或所述 RAN设备的相邻 RAN设备 的其他可用的小区中所述参与运营商标识对应的参与运营商的资源使用 情况。
25、 根据权利要求 24所述的核心网设备, 其特征在于, 所述核心网 设备为移动管理实体 MME/服务 GPRS支持节点 SGSN,所述 MME/SGSN 包括:
第一接收模块, 用于接收 RAN设备检测到某一个或多个参与运营商 发生拥塞时发送的拥塞通知消息;
第一发送模块, 用于记录所述拥塞通知消息, 并向所述 RAN设备发 送拥塞通知响应消息;
所述第一接收模块还用于接收用户设备 UE通过所述 RAN设备发送 的接入请求, 所述接入请求包含所要接入的参与运营商信息;
第一处理模块, 用于根据所述接入请求包含的所述参与运营商信息和 拥塞通知消息, 向所述 UE发送接入拒绝消息。
26、根据权利要求 25所述的核心网设备,其特征在于,在 4G网络下, 所述接入请求为附着请求; 或者,
所述接入请求为 UE发起的服务请求; 或者,
所述接入请求为跟踪区更新请求; 或者,
所述接入请求为路由区更新请求; 或者,
在 2G/3G网络下, 所述接入请求为 UE发起的一次 /二次 PDP上下文 建立或修改请求;
所述接入拒绝消息还包括: 接入拒绝原因和空闲小区指示信息, 用于 所述 UE选择接入所述空闲小区指示信息指示的空闲小区。
27、 根据权利要求 24所述的核心网设备, 其特征在于, 所述核心网 设备包括 MME/ SGSN、 服务网关 S-GW、 分组数据网络网关 P-GW/网关
GPRS 支持节点 GGSN 和策略与计费规则功能实体 PCRF , 所述 MME/ SGSN包括:
第二接收模块, 用于接收 RAN设备检测到某一个或多个参与运营商 发生拥塞时发送的拥塞通知消息;
第二发送模块, 用于记录所述拥塞通知消息, 并向所述 RAN设备发 送拥塞通知响应消息;
所述 PCRF包括:
第三发送模块,用于向 P-GW/GGSN发送 IP连接接入网络 IP-CAN会 话修改请求;
所述 P-GW/GGSN包括:
第四发送模块, 用于根据所述 IP-CAN会话修改请求通过 S-GW向所 述 MME/ SGSN发起承载建立 /修改请求, 所述承载建立 /修改请求中包含 UE的国际移动用户标识 IMSI信息 /UE的参与运营商标识;
所述 MME/ SGSN还包括:
第二处理模块, 用于根据所述 IMSI信息 /参与运营商标识和所述拥塞 通知消息, 拒绝所述承载建立 /修改请求。
28、 根据权利要求 27所述的核心网设备, 其特征在于, 所述第二发 送模块还用于:
通过 S-GW向所述 P-GW/GGSN发起承载建立 /修改拒绝响应,所述承 载建立 /修改拒绝响应包括拒绝原因; 所述第四发送模块还用于: 向所述 PCRF发送 IP-CAN会话修改响应 消息, 所述 IP-CAN会话修改响应消息中包含所述拒绝原因。
29、 根据权利要求 24〜28任一项所述的核心网设备, 其特征在于, 所 述第二接收模块还用于:
接收所述 RAN设备检测到所述 RAN设备内发生拥塞的参与运营商拥 塞状况缓解时发送的拥塞缓解通知消息;
所述第二发送模块还用于向所述 RAN设备发送拥塞缓解响应消息。
30、 根据权利要求 24所述的核心网设备, 其特征在于, 所述核心网 设备包括 MME/ SGSN、 S-GW、 P-GW/ GGSN和 PCRF, 所述 MME/SGSN 包括:
第三接收模块, 用于接收 RAN设备检测到某一个或多个参与运营商 发生拥塞时发送的拥塞通知消息;
第五发送模块, 用于通过所述 S-GW向所述 P-GW/GGSN发送承载更 新请求消息, 所述承载更新请求消息包括所述拥塞通知消息的内容;
所述 P-GW/GGSN包括:
第四接收模块, 用于接收所述承载更新请求消息;
第六发送模块, 用于记录所述承载更新请求消息, 并通过所述 S-GW 和所述 MME/ SGSN向所述 RAN设备发送拥塞通知响应消息;
所述 PCRF包括:
第七发送模块, 用于向所述 P-GW/GGSN 发送 IP 连接接入网络
IP-CAN会话修改请求;
所述 P-GW/GGSN还包括:
第三处理模块, 用于根据所述拥塞通知消息和所述 IP-CAN会话修改 请求的类型判断, 拒绝所述 IP-CAN会话修改请求。
31、 根据权利要求 30所述的核心网设备, 其特征在于, 所述第六发 送模块还用于:向所述 PCRF发送 IP-CAN会话修改响应消息,所述 IP-CAN 会话修改响应消息中包含拒绝原因。
32、 根据权利要求 30或 31所述的核心网设备, 其特征在于, 所述第 三接收模块还用于:接收所述 RAN设备检测到所述 RAN设备内发生拥塞 的参与运营商拥塞状况缓解时发送的拥塞缓解通知消息; 所述第五发送模块还用于: 通过所述 S-GW向所述 P-GW/GGSN发送 所述拥塞缓解通知消息;
所述第六发送模块还用于: 通过所述 S-GW和所述 MME/ SGSN向所 述 RAN设备发送拥塞缓解响应消息。
33、 根据权利要求 24所述的核心网设备, 其特征在于, 所述核心网 设备包括 S-GW、 P-GW/ GGSN和 PCRF, 所述 P-GW/ GGSN包括:
第五接收模块, 用于通过所述 S-GW接收 RAN设备检测到某一个或 多个参与运营商发生拥塞时发送的拥塞通知消息;
第七发送模块, 用于记录所述拥塞通知消息, 并通过所述 S-GW向所 述 RAN设备发送拥塞通知响应消息;
所述 PCRF包括:
第八发送模块,用于向所述 P-GW/GGSN发送 IP-CAN会话修改请求; 所述 P-GW/GGSN包括:
第四处理模块, 用于根据所述拥塞通知消息和所述 IP-CAN会话修改 请求的类型判断, 拒绝所述 IP-CAN会话修改请求。
34、 根据权利要求 33 所述的核心网设备, 其特征在于, 所述第七发 送模块还用于:
向所述 PCRF发送 IP-CAN会话修改响应消息, 所述 IP-CAN会话修 改响应消息中包含拒绝原因。
35、 根据权利要求 33或 34所述的核心网设备, 其特征在于, 所述第 五接收模块还用于: 通过所述 S-GW接收所述 RAN设备检测到所述 RAN 设备内发生拥塞的参与运营商拥塞状况缓解时发送的拥塞缓解通知消息; 所述第七发送模块还用于: 通过所述 S-GW向所述 RAN设备发送拥 塞缓解响应消息。
36、 一种无线接入网设备, 其特征在于, 包括:
检测模块, 用于根据参与运营商的资源使用情况检测拥塞的发生, 所 述参与运营商为移动虚拟网络运营商 MVNO或共享运营商网络的运营商; 发送模块, 用于当所述检测模块检测到某一个或多个所述参与运营商 发生拥塞时, 向与发生拥塞的所述参与运营商相关的核心网设备发送拥塞 通知消息, 所述拥塞通知消息包括发生拥塞的参与运营商标识, 用于所述 核心网设备对所述参与运营商标识对应的参与运营商进行拥塞控制。
37、 根据权利要求 36所述的无线接入网设备, 其特征在于, 所述拥 塞通知消息还包括下述任一项或组合:
发生拥塞的参与运营商的拥塞原因、 发生拥塞的参与运营商在拥塞小 区的资源使用情况、 所述 RAN设备或所述 RAN设备的相邻 RAN设备的 其他可用的小区信息和所述 RAN设备或所述 RAN设备的相邻 RAN设备 的其他可用的小区中所述参与运营商标识对应的参与运营商的资源使用 情况。
38、 根据权利要求 37所述的无线接入网设备, 其特征在于, 所述核 心网设备为 MME/ SGSN, 所述发送模块用于:
当所述检测模块检测到某一个或多个所述参与运营商发生拥塞时, 向 与发生拥塞的所述参与运营商相关的 MME/ SGSN发送拥塞通知消息, 用 于所述 MME/ SGSN记录所述拥塞通知消息, 并根据所述拥塞通知消息, 对所述参与运营商标识对应的参与运营商进行拥塞控制;
所述无线接入网设备还包括:
第一接收模块,用于接收所述 MME/ SGSN发送的拥塞通知响应消息。
39、 根据权利要求 37所述的无线接入网设备, 其特征在于, 所述核 心网设备包括 MME/ SGSN、 S-GW、 P-GW/ GGSN和 PCRF, 所述发送模 块用于:
当所述检测模块检测到某一个或多个所述参与运营商发生拥塞时, 向 与发生拥塞的所述参与运营商相关的 MME/ SGSN发送拥塞通知消息, 用 于所述 MME/ SGSN记录所述拥塞通知消息;
所述无线接入网设备还包括:
第二接收模块,用于接收所述 MME/ SGSN发送的拥塞通知响应消息。
40、根据权利要求 37〜39任一项所述的无线接入网设备,其特征在于, 所述发送模块还用于:
当所述检测模块检测到所述 RAN设备内发生拥塞的参与运营商拥塞 状况缓解时, 向所述 MME/ SGSN发送拥塞缓解通知消息;
所述第一接收模块或所述第二接收模块还用于:
接收所述 MME/ SGSN发送的拥塞缓解响应消息。
41、 根据权利要求 37所述的无线接入网设备, 其特征在于, 所述核 心网设备包括 MME/ SGSN、 S-GW, P-GW/ GGSN和 PCRF, 所述发送模 块用于:
当所述检测模块检测到某一个或多个所述参与运营商发生拥塞时, 向 与发生拥塞的所述参与运营商相关的 MME/ SGSN发送拥塞通知消息, 用 于所述 MME/ SGSN通过所述 S-GW向所述 P-GW/GGSN发送承载更新请 求消息, 所述承载更新请求消息包括所述拥塞通知消息的内容;
所述无线接入网设备还包括:
第三接收模块, 用于接收所述 P-GW/GGSN通过所述 S-GW和所述 MME/ SGSN发送的拥塞通知响应消息。
42、 根据权利要求 41 所述的无线接入网设备, 其特征在于, 所述发 送模块还用于:
当所述检测模块检测到所述 RAN设备内发生拥塞的参与运营商拥塞 状况缓解时,向所述 MME/ SGSN发送拥塞缓解通知消息,用于所述 MME/ SGSN通过所述 S-GW向所述 P-GW/GGSN发送所述拥塞缓解通知消息; 所述第三接收模块还用于接收所述 P-GW/GGSN通过所述 S-GW和所 述 MME/ SGSN发送的拥塞缓解响应消息。
43、 根据权利要求 37所述的无线接入网设备, 其特征在于, 所述核 心网设备包括 S-GW、 P-GW/ GGSN和 PCRF, 所述发送模块用于:
当所述检测模块检测到某一个或多个所述参与运营商发生拥塞时, 向 与发生拥塞的所述参与运营商相关的 S-GW发送拥塞通知消息, 用于所述 S-GW向所述 P-GW/GGSN发送所述拥塞通知消息;
所述无线接入网设备还包括:
第四接收模块, 用于接收所述 P-GW/GGSN通过所述 S-GW发送的拥 塞通知响应消息。
44、 根据权利要求 43 所述的无线接入网设备, 其特征在于, 所述发 送模块还用于:
当所述检测模块检测到所述 RAN设备内发生拥塞的参与运营商拥塞 状况缓解时, 向所述 S-GW发送拥塞缓解通知消息, 用于所述 S-GW向所 述 P-GW/GGSN发送所述拥塞缓解通知消息; 所述第四接收模块还用于接收所述 P-GW/GGSN通过所述 S-GW发送 的拥塞缓解响应消息。
45、 一种通信系统, 包括上述权利要求 23〜35任一项所述的核心网设 备和权利要求 36〜44任一项所述的 RAN设备。
PCT/CN2013/087124 2013-11-14 2013-11-14 拥塞控制方法、装置及系统 WO2015070414A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2013/087124 WO2015070414A1 (zh) 2013-11-14 2013-11-14 拥塞控制方法、装置及系统
CN201380004566.5A CN104969621B (zh) 2013-11-14 2013-11-14 拥塞控制方法、装置及系统
EP18152260.8A EP3376795B1 (en) 2013-11-14 2013-11-14 Congestion control method, apparatus, and system
EP13897406.8A EP3062560B1 (en) 2013-11-14 2013-11-14 Congestion control method, device, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/087124 WO2015070414A1 (zh) 2013-11-14 2013-11-14 拥塞控制方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2015070414A1 true WO2015070414A1 (zh) 2015-05-21

Family

ID=53056635

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/087124 WO2015070414A1 (zh) 2013-11-14 2013-11-14 拥塞控制方法、装置及系统

Country Status (3)

Country Link
EP (2) EP3376795B1 (zh)
CN (1) CN104969621B (zh)
WO (1) WO2015070414A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210352618A1 (en) * 2019-01-18 2021-11-11 Vivo Mobile Communication Co., Ltd. Paging transmission method and device

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102380619B1 (ko) * 2017-08-11 2022-03-30 삼성전자 주식회사 이동 통신 시스템 망에서 혼잡 제어를 효율적으로 수행하는 방법 및 장치

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101977416A (zh) * 2010-05-19 2011-02-16 中兴通讯股份有限公司 一种mtc设备的过载控制方法和系统
CN102696269A (zh) * 2010-01-15 2012-09-26 瑞典爱立信有限公司 用于lte和第三代无线网络之间互工作的拥塞控制

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4920564B2 (ja) * 2007-11-29 2012-04-18 株式会社日立製作所 パケット通信網およびユーザ関連情報配信制御装置
US8165091B2 (en) * 2008-06-27 2012-04-24 Nix John A Efficient handover of media communications in heterogeneous IP networks using LAN profiles and network handover rules
CN101594617A (zh) * 2009-06-19 2009-12-02 电子科技大学 一种分级频谱共享网络的控制信道建立方法
CN102638864B (zh) * 2011-02-14 2017-05-03 中兴通讯股份有限公司 一种共享网络的接入控制方法和系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102696269A (zh) * 2010-01-15 2012-09-26 瑞典爱立信有限公司 用于lte和第三代无线网络之间互工作的拥塞控制
CN101977416A (zh) * 2010-05-19 2011-02-16 中兴通讯股份有限公司 一种mtc设备的过载控制方法和系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210352618A1 (en) * 2019-01-18 2021-11-11 Vivo Mobile Communication Co., Ltd. Paging transmission method and device

Also Published As

Publication number Publication date
EP3062560B1 (en) 2018-03-14
EP3376795A1 (en) 2018-09-19
EP3062560A4 (en) 2016-10-26
CN104969621B (zh) 2019-06-21
CN104969621A (zh) 2015-10-07
EP3062560A1 (en) 2016-08-31
EP3376795B1 (en) 2020-01-08

Similar Documents

Publication Publication Date Title
KR101973462B1 (ko) 접속 해제를 수행하는 방법 및 그 단말
US9560514B2 (en) Method for establishing connection by HNB
CN104471975B (zh) 用于检测和管理用户平面拥塞的方法和装置
US10412771B2 (en) Method for controlling connection between user equipment and network, and mobility management entity
US8761107B2 (en) Method and apparatus for maintaining traffic continuity
US9473971B2 (en) Method and apparatus for managing QoS group in wireless communication system
EP2193632B1 (en) Methods for establishing connection of a home node b, hnb
US9860783B2 (en) Congestion state reporting method and access network device
CN106658601B (zh) 数据传输的处理方法及装置
CN101959252B (zh) 服务质量控制、策略配置方法和装置
JP5718484B2 (ja) 共有ネットワークのアクセス制御方法、アクセスネットワークノード及びコアネットワークノード
CN101969635A (zh) 一种机器通信的接入控制方法及系统和系统
CN102056265A (zh) 限制mtc设备接入和通信的方法、移动管理单元及网关单元
WO2015061978A1 (zh) 网络共享的管理方法及装置
CN104919829A (zh) 用于发送mtc设备的数据的方法
CN102948203B (zh) 负载控制方法和设备及通信系统
CN102905388B (zh) 接入控制的方法及系统、网络侧网元
WO2009046670A1 (fr) Procédé, système, station de base et nœud de gestion pour accéder à un nœud de réseau d'infrastructure
US20150237495A1 (en) Method and system for differentiating between subscribers
CN101990321A (zh) 一种本地ip访问接入控制的方法及系统
WO2015070414A1 (zh) 拥塞控制方法、装置及系统
US10524163B2 (en) Base station, communication terminal, communication method, communication system, and storage medium
US20200107188A1 (en) Communication device, communication method, communication system, and storage medium
EP2871885B1 (en) Method and device for processing service data packet
WO2014056444A1 (zh) 资源授权的方法、装置以及系统

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

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

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2013897406

Country of ref document: EP