WO2014067075A1 - 缓解网络拥塞的方法、核心网设备和接入网设备 - Google Patents
缓解网络拥塞的方法、核心网设备和接入网设备 Download PDFInfo
- Publication number
- WO2014067075A1 WO2014067075A1 PCT/CN2012/083777 CN2012083777W WO2014067075A1 WO 2014067075 A1 WO2014067075 A1 WO 2014067075A1 CN 2012083777 W CN2012083777 W CN 2012083777W WO 2014067075 A1 WO2014067075 A1 WO 2014067075A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data flow
- network device
- core network
- congestion
- flow identifier
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 67
- 238000001514 detection method Methods 0.000 claims description 43
- 230000011664 signaling Effects 0.000 claims description 17
- 230000004913 activation Effects 0.000 claims description 12
- 230000004048 modification Effects 0.000 claims description 4
- 238000012986 modification Methods 0.000 claims description 4
- 230000000116 mitigating effect Effects 0.000 description 12
- 238000010586 diagram Methods 0.000 description 10
- 230000005540 biological transmission Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 3
- 230000003213 activating effect Effects 0.000 description 2
- 230000007420 reactivation Effects 0.000 description 2
- 150000001768 cations Chemical class 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000000523 sample Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/122—Avoiding congestion; Recovering from congestion by diverting traffic away from congested entities
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a method for mitigating network congestion, a core network device, and an access network device.
- the network side can modify the PCC rule (Policy and Charging Control rule) or ADC rule (Application Detection and Control).
- QoS Quality of Service
- MBR Maximum Bit Rate
- GBR Guard Bit Rate
- the QoS parameters may include: QCI (QoS Class Identifier), ARP (Allocation and Retention Priority), MBR, GBR, and Up/Down maximum bit rate (UL/DL maximum bit rate) )Wait.
- the method for modifying the PCC rule and the ADC rule/QoS parameter may include: activating or modifying a specified data stream by a PCRF (Policy and Charging Rules Function) entity (hereinafter referred to as a PCRF) Corresponding PCC rule/QoS parameters, or activated or modified by TDF (Taffic detection function) entity (hereinafter referred to as TDF), such as reducing the ADC rule (Application Detection and Control) corresponding to the specified data stream.
- PCRF Policy and Charging Rules Function
- TDF Taffic detection function
- the current UL/DL maximum bit rate in the probe for example, reduces application services that are currently considered to occupy excessive network resources, such as P 2 P (peer-to-peer) services (such as Skype).
- the specified data flow configured on the network side is usually an application service data flow that excessively occupies network resources, and the network side modifies the application service data flow.
- the specified data flow configured on the network side is usually an application service data flow that excessively occupies network resources, and the network side modifies the application service data flow.
- the network side modifies the application service data flow.
- Corresponding PCC rule/QOS but with the diversification of application services, each business has a variety of impacts on the network, it is difficult to estimate the current network.
- the congestion is caused by which application service data flow, so this method may not alleviate network congestion in a timely and effective manner.
- Embodiments of the present invention provide a method for mitigating network congestion, a core network device, and an access network device, which solves the problem that network congestion cannot be alleviated in a timely and effective manner.
- a method for mitigating network congestion including:
- the core network device obtains congestion state information and a data flow identifier for indicating congestion of the access network, and reduces service quality QoS of the data flow corresponding to the data flow identifier according to the congestion state information.
- the access network device determines a data flow that is congested by the access network
- a core network device including:
- a receiver configured to obtain congestion state information and a data flow identifier for indicating congestion of the access network
- a processor configured to reduce a quality of service QoS of the data flow corresponding to the data flow identifier according to the congestion state information.
- an access network device including:
- a processor configured to determine a data flow used to indicate congestion of the access network
- a transmitter configured to send, to the core network device, congestion state information and a data flow identifier for indicating congestion of the access network, so that the core network device reduces the data flow according to the congestion state information and the data flow identifier Quality of Service QoS.
- a system for mitigating network congestion including:
- the core network device and the access network device provided in the above content.
- the method for mitigating network congestion and the core network device provided by the embodiments of the present invention adopt the foregoing solution
- the access network device determines the data flow that causes the access network to be congested, it sends congestion state information and data flow identifiers for indicating the congestion of the access network to the core network device, and the core network device receives the congestion state information and data.
- the QoS of the data flow corresponding to the data flow identifier is reduced according to the congestion state information, so as to alleviate network congestion.
- FIG. 1 is a flowchart of a method for relieving network congestion according to an embodiment of the present disclosure
- FIG. 2 is a flowchart of a method for relieving network congestion according to the embodiment
- FIG. 3 is a schematic diagram of information transmission between a PCEF and a PCRF in the method shown in FIG. 2;
- FIG. 4a is a schematic diagram of data transmission between an access network device and a core network device in the method shown in FIG. 2;
- FIG. 4b is a schematic diagram of data transmission of an access network device and a core network device in the method shown in FIG. 2;
- FIG. 5 is a flowchart of a method for mitigating network congestion according to the embodiment.
- FIG. 6 is a schematic diagram of a method for sending a report indication message to an access network device according to an embodiment of the present invention
- FIG. 7 is a flowchart of a method for relieving network congestion according to an embodiment of the present disclosure.
- FIG. 8 is a flowchart of a method for relieving network congestion according to an embodiment of the present disclosure
- FIG. 9 is a schematic flowchart of a method for alleviating network congestion according to an embodiment of the present disclosure.
- FIG. 10 is a schematic structural diagram of a core network device according to an embodiment of the present disclosure.
- FIG. 11 is a schematic structural diagram of another core network device according to the embodiment.
- FIG. 12 is a schematic structural diagram of an access network device according to an embodiment of the present disclosure.
- FIG. 13 is a schematic structural diagram of another access network device according to the embodiment.
- FIG. 14 is a schematic structural diagram of a system for alleviating network congestion according to an embodiment of the present disclosure.
- the network side solves the problem of network congestion by modifying the PCC rule/QoS parameter corresponding to the corresponding data stream.
- it may not be able to effectively alleviate network congestion in a timely and effective manner.
- the access network device first determines the data flow that causes the network to be congested, and then notifies the core network device of the data flow in a corresponding manner, so that the core network device determines the policy corresponding to the data flow that causes the network to be congested. And the charging control rule and/or the application detection control rule, so that the core network device modifies the corresponding data flow and the QoS parameter of the bearer according to the determined policy and charging control rule and/or the application detection control rule,
- the bearer may be a bearer where the data flow causing network congestion is located.
- the core network device may include, but is not limited to: a PCRF, a gateway device/PCEF (Poly cy and Charging Enforcement Funneling) entity (hereinafter referred to as a PCEF) MME (Mobi Li ty Management Entity, Mobility Management Network Element).
- PCEF Policy cy and Charging Enforcement Funneling
- MME Mobility Management Network Element
- the embodiment provides a method for mitigating network congestion.
- the executor of the method may be a core network device. As shown in FIG. 1, the method may include:
- the core network device obtains congestion state information and a data flow identifier for indicating congestion of the access network.
- the congested data stream may be a data stream that excessively occupies network resources, and specifically, which data stream may be determined by the access network device according to bandwidth resources occupied by various data streams.
- some data streams occupy large bandwidth resources, and these data streams can be considered as data flows that cause network congestion.
- How to define a large bandwidth resource which can be defined by the network according to the actual situation, for example, but not limited to, when a service flow occupies more than 50% of the bandwidth resources, the data flow can be considered as excessively occupying network resources.
- the data stream is either referred to as the data stream that causes congestion.
- the data flow that causes network congestion in the following full text is all this.
- the access network device sends the congestion state information and the data flow identifier indicating the congestion of the access network to the core network device after determining the data flow that causes the access network to be congested, and the core network device receives the congestion state. After the information and the data flow are identified, the QoS of the data flow corresponding to the data flow identifier is reduced according to the congestion state information, so as to alleviate network congestion.
- This embodiment provides another method for alleviating network congestion.
- the method is a further extension of the method shown in FIG. 1.
- the method may include:
- the core network device acquires congestion state information and a data flow identifier for indicating congestion of the access network.
- the access network device When network congestion occurs, the access network device sends congestion state information and data flow identifiers for indicating congestion of the access network to the core network device after determining the data stream that excessively occupies the network resources or causes the network to be congested.
- congestion status information and the data flow identifier used by the core network device to indicate the congestion of the access network may include, but are not limited to:
- the core network device receives the control plane signaling including the data flow identifier and the congestion state information, and the core network device obtains the data flow identifier and the congestion state information from the control plane signaling; or
- the core network device receives the user plane data packet including the data flow identifier and the congestion state information; or the core network device receives the user plane data packet of the data flow that includes the congestion state information, and the core network device acquires the data flow identifier corresponding to the data flow, and Obtain congestion status information from the user plane packet.
- the method for obtaining the congestion state information and the data flow identifier of the core network device is not limited in this embodiment, and may be set according to actual needs, and details are not described herein again.
- the core network device determines whether there is a policy and charging control rule corresponding to the data flow identifier.
- step 203 if it exists, go to step 203, if not, go to step 205.
- the core network device may be a gateway device/PCEF.
- the step may be: the gateway device/PCEF determines whether there is a policy and charging control rule corresponding to the data flow identifier and/or application detection. Control rules.
- the step may be: determining whether the policy and the charging control rule corresponding to the data flow identifier exist; or When the network device reduces the QoS of the data flow corresponding to the data flow identifier in the application detection control rule, this step may be used to determine whether the application detection control rule corresponding to the data flow identifier exists; or when the core network device reduces the application detection control rule and policy.
- this step may be used to determine whether there is an application detection control rule and a policy and charging control rule corresponding to the data flow identifier.
- the method for determining the step 202 is not limited in this embodiment, and may be set according to actual needs, and details are not described herein again.
- the core network device may, but is not limited to, reduce the QoS of the data flow corresponding to the data flow identifier by modifying the QoS parameters in the at least one rule.
- the core network device may further reduce the QoS of the data flow corresponding to the data flow identifier by re-activating at least one rule and deleting the at least one rule, so that at least one rule after the reactivation is performed.
- the QoS corresponding to the QoS parameter is lower than the QoS corresponding to the QoS parameter of the data stream before activation.
- the policy and charging control rule are reduced.
- the QoS of the data stream corresponding to the data stream identifier may include, but is not limited to, congested after the gateway device/PCEF receives the congestion state information and the data flow identifier and determines that the policy and the charging control rule corresponding to the data flow identifier exist.
- the policy and charging control rules corresponding to the status information and the data flow identifier are sent to the PCRF, and the PCRF modifies the policy and the charging control rule corresponding to the data flow identifier according to the congestion state information, and the PCRF can include the policy and the charging control rule.
- the QoS parameters are modified (ie, reduced QoS), for example, can be tampered with but not limited to QCI, ARP, MBR, GBR, and the like.
- the PCRF may reactivate the policy and charging control rules corresponding to the data flow identifier according to the data flow identifier and the congestion state information.
- 4a is a schematic diagram of data transmission between an access network device and a core network device (which may include: gateway device/PCEF, PCRF, etc.).
- a core network device which may include: gateway device/PCEF, PCRF, etc.
- reducing the QoS of the data flow corresponding to the data flow identifier in the application detection control rule may further include: if the PCRF determines that the application detection control rule corresponding to the data flow identifier exists, the PCRF may further The received data flow identifier sends the indication information to the TDF, where the indication information is used to indicate that the TDF modifies the application detection control rule corresponding to the data flow identifier.
- the TDF can modify the QoS parameters in the ADC ru l e, for example, the maximum bit rate (UL/DL max imum b i t ra te ) in the ADC Ru l e can be reduced.
- the indication information may be used to indicate that the TDF re-activates the application detection control rule corresponding to the data flow identifier and deletes the original application detection control rule, and the TDF sends an acknowledgement message to the PCRF, where the acknowledgement message may include, but is not limited to, after reactivation.
- the application detection control rule is such that the QoS corresponding to the QoS parameter in the re-activated application detection control rule is lower than the QoS corresponding to the QoS parameter of the data stream before activation.
- the ADC ru l e in Figure 4b is the application detection control rule.
- the core network device can also reduce the QoS of the data flow corresponding to the data flow identifier in the policy and the charging control rule and the application detection control rule.
- the specific implementation manner of the method is not described here.
- the QoS parameters are not limited in this embodiment, and are well-known in the art, and can be set according to actual needs, and details are not described herein again.
- the method for sending the congestion state information and the data stream identifier to the PCRF by the gateway device/PCEF is not limited, and is a technology well known to those skilled in the art, and can be set according to actual needs, for example, but not limited to PCEF direction.
- the PCRF sends an IP-CAN (IP-Connec ti ty Acces s Network, IP ⁇ Internet Protoco l, Inter-Network Interconnection Protocol> connection access network) message containing the congestion status information and the data flow identifier, and details are not described herein.
- the gateway device/PCEF determines that there is no policy and charging control rule corresponding to the data flow identifier and/or applies the detection control rule
- the data flow identifier needs to be sent to the PCRF for PCRF.
- the QoS corresponding to the QoS parameter in the at least one of the activated policy and the charging control rule is lower than the QoS corresponding to the QoS parameter of the data stream before the activation.
- the activated policy and the charging control rule are sent to the gateway device/PCEF, so that the gateway device/PCEF receives the The policy and the charging control rule perform subsequent operations, for example, limiting the Q0S parameters of the current service flow, thereby reducing the bandwidth occupied by the bearer corresponding to the data flow.
- the PCRF activation data flow identifier corresponding to the application detection control rule may include: after receiving the data flow identifier, the PCRF sends indication information to the TDF, where the indication information may be used to indicate the TDF activation data flow.
- the corresponding application detection control rule is identified; the TDF will send an acknowledgement message to the PCRF, which may include, but is not limited to, an activated application detection control rule.
- the application detection control rule may be sent to the TDF device, so that the TDF device performs subsequent operations according to the received application detection control rule, for example, modifying the Q0S parameter of the application service, for example, The maximum bit rate of the uplink and the downlink, etc., can further reduce the resources occupied by the data stream.
- the method for the activation of the policy and the charging control rule of the PCRF, and the method for the application of the detection control rule by the TDF are not limited, and are well-known to those skilled in the art, and can be set according to actual needs. Narration.
- the PCRF may send an IP-CAN message to the gateway device/PCEF, and the IP-CAN message may include, but is not limited to, modified or activated policy and charging control rules and modified or activated. After the application detects at least one rule in the control rule.
- the method for sending at least one of the modified or activated policy and charging control rules and the modified or activated application detection control rules to the gateway device/PCEF is not limited, and may be set according to actual needs. , will not repeat them here.
- the PCRF can send a Diame ter to the TDF device.
- This embodiment is not limited to the method for modifying or determining the QoS parameters in the detection control rule by the TDF device, and is a technology well known to those skilled in the art, and details are not described herein again.
- step 205 may be directly executed without performing the determining step of step 202.
- the QoS of the data flow corresponding to the data flow identifier may be reduced: after the core network device obtains the congestion state information and the data flow identifier of the access network congestion, the policy corresponding to the data flow identifier is reactivated. And at least one of the charging control rule and the application detection control rule, and deleting the original policy and charging control rule and/or applying the detection control rule, wherein the activated policy and charging control rule and charging control rule.
- the QoS corresponding to the QoS parameter in at least one of the rules of the application detection control rule is lower than the QoS corresponding to the QoS parameter of the data stream before activation.
- step 206 is an optional step, and is not necessarily performed after step 205 during execution, and may be performed before or after any step of the embodiment, which is not limited herein.
- the access network device sends the congestion state information and the data flow identifier indicating the congestion of the access network to the core network device after determining the data flow that causes the access network to be congested, and the core network device receives the congestion state. After the information and the data flow are identified, the QoS of the data flow corresponding to the data flow identifier is reduced according to the congestion state information, so as to alleviate network congestion.
- the core network device may determine, according to the reporting indication message, whether to send the congestion state information and the data flow identifier to the core network device.
- This embodiment provides another method for mitigating network congestion.
- the method is mainly used to describe a process for determining, by the access network device, whether to send congestion state information and a data flow identifier to a core network device according to the report indication message, as shown in FIG. Can include:
- the terminal sends an attach request to the access network device.
- the access network device forwards the attach request to the E.
- the MME sends an activation session request to the gateway device/PCEF according to the attach request.
- the gateway device/PCEF sends an IP-CAN session establishment request to the PCRF.
- the PCRF sends an IP-CAN session establishment response to the gateway device/PCEF.
- the PCRF determines that the access network device reports the data flow information that causes congestion to the core network device when the access network is congested, the PCRF sends a report indication message to the gateway device/PCEF, that is, the report indication message is used to indicate the access network.
- the access network device reports the congestion status information and the data flow identifier used to indicate the congestion of the access network to the core network device, and the report indication message may be included in the IP-CAN session establishment response and sent to the gateway device/PCEF.
- the gateway device/PCEF sends an activation session response to the ⁇ E, where the response may include a reporting indication message.
- the E sends an initial context setup request/attach accept message to the access network device, where the message may include a report indication message.
- the ⁇ E may also send an indication message to the access network device by using other methods, which may include:
- the terminal sends a service request to the access network device.
- the access network device sends a service request to the MME
- ⁇ E sends an initial context setup request to the access network device, in the initial context setup request. May include, but is not limited to, reporting an indication message;
- the method for sending the report indication message to the access network device is not limited, and may be set according to actual needs, and details are not described herein again.
- the access network sends an RRC (Radio Resource Control Protocol) connection reconfiguration process to the terminal.
- RRC Radio Resource Control Protocol
- This embodiment is not limited to the RRC connection reconfiguration method, the function of the attach request, and the function of the service request, and is not known to those skilled in the art.
- the access network device sends the congestion state information and the data flow identifier indicating the congestion of the access network to the core network device after determining the data flow that causes the access network to be congested, and the core network device receives the congestion state. After the information and the data flow are identified, the QoS of the data flow corresponding to the data flow identifier is reduced according to the congestion state information, so as to alleviate network congestion.
- the executor of the method may be an access network device. As shown in FIG. 7, the method may include:
- the access network device determines a data flow used to indicate that the access network is congested.
- the access network device sends the congestion state information and the data flow identifier indicating the congestion of the access network to the core network device after determining the data flow that causes the access network to be congested, and the core network device receives the congestion state. After the information and the data flow are identified, the QoS of the data flow corresponding to the data flow identifier is reduced according to the congestion state information, so as to alleviate network congestion.
- This embodiment provides a method for alleviating network congestion.
- the method is further extended to the method shown in FIG. 7.
- the method may include:
- the reporting indication message may be used to indicate that the access network device sends the congestion state information and the data flow identifier to the core network device. This step is optional. 802.
- the access network device determines a data flow used to indicate congestion of the access network.
- the access network device determines that the data flow that causes the network to be congested may include:
- the access network device can learn the packet filter information corresponding to the data stream that currently over-occupies the network resource (that is, causes network congestion), that is, the data.
- DPI Deep Packet Inspection
- the packet filter information and the service identifier are both referred to as data stream identifiers.
- the method for obtaining the packet filter information and the service identifier of the access network device is not limited in this embodiment, and is a technology well known to those skilled in the art, and details are not described herein again.
- the method for determining the data flow that causes the network to be congested by the access network device is not limited, and may be set according to actual needs, and details are not described herein again.
- the sending the access network congestion information to the core network device may be: sending a user plane data packet of the data flow including the congestion state information to the core network device, so that the core network device acquires the data flow identifier corresponding to the data flow, and the user Obtaining congestion status information in the face packet;
- control plane signaling that includes the data flow identifier and the congestion state information, so that the core network device obtains the data flow identifier and the congestion state information from the control plane signaling; further, as shown in FIG.
- the network access device can send control plane signaling including congestion status information to ⁇ E, It is then sent by the MME to the gateway device/PCEF, or a third party device.
- the sending the access network congestion information to the core network device may be: when there is no uplink data packet between the access network device and the core network device, the access network device cannot send the data including the congestion state information to the core network device.
- the packet may also include the congestion status information in the header of the uplink data packet and be sent to the core network device, but the uplink data packet is an uplink data packet of the other terminal that is configured by the current gateway device and includes the uplink data packet.
- the uplink data packet may further include an identifier of the terminal.
- the third-party device is not limited, and may be configured according to actual needs.
- it may be, but is not limited to, a network management device, a detection network device, and the like, and details are not described herein again.
- the access network device sends the congestion state information and the data flow identifier indicating the congestion of the access network to the core network device after determining the data flow that causes the access network to be congested, and the core network device receives the congestion state. After the information and the data flow are identified, the QoS of the data flow corresponding to the data flow identifier is reduced according to the congestion state information, so as to alleviate network congestion.
- This embodiment provides a core network device, as shown in FIG. 10, which may include:
- the receiver 101 is configured to acquire congestion state information and a data flow identifier for indicating congestion of the access network.
- the processor 102 is configured to reduce the quality of service QoS of the data stream corresponding to the data flow identifier according to the congestion state information.
- the access network device After the foregoing solution is adopted, after determining the data flow that causes the access network to be congested, the access network device sends, to the receiver, congestion state information and a data flow identifier for indicating congestion of the access network, and the processor receives the congestion state at the receiver. After the information and the data flow are identified, the QoS of the data flow corresponding to the data flow identifier is reduced according to the congestion state information, so as to alleviate network congestion.
- This embodiment provides another core network device, which is a further extension of the core network device shown in FIG. 10, as shown in FIG.
- the receiver 111 is configured to acquire congestion state information and a data flow indicator for indicating congestion of the access network.
- the processor 112 is configured to reduce the quality of service QoS of the data stream corresponding to the data flow identifier according to the congestion state information.
- the transmitter 113 is configured to send a report indication message to the access network device, where the report indication message is used to indicate that the access network device sends the congestion state information and the data flow identifier to the core network device.
- the processor 112 is configured to obtain at least one of an existing policy and charging control rule and an application detection control rule corresponding to the data flow identifier, and modify the QoS parameter in the at least one rule to modify the QoS.
- the QoS corresponding to the parameter is lower than the QoS corresponding to the QoS parameter of the data stream before modification.
- the processor 112 is configured to activate at least one of a policy and a charging control rule and an application detection control rule corresponding to the data flow identifier, where the QoS corresponding to the QoS parameter in the at least one rule is lower than that before the activation.
- the QoS corresponding to the QoS parameters of the data stream is configured to activate at least one of a policy and a charging control rule and an application detection control rule corresponding to the data flow identifier, where the QoS corresponding to the QoS parameter in the at least one rule is lower than that before the activation.
- the QoS corresponding to the QoS parameters of the data stream is configured to activate at least one of a policy and a charging control rule and an application detection control rule corresponding to the data flow identifier, where the QoS corresponding to the QoS parameter in the at least one rule is lower than that before the activation.
- the QoS corresponding to the QoS parameters of the data stream is configured to activate at least one of a policy and
- the receiver 111 is configured to receive control plane signaling that includes the data flow identifier and the congestion state information, and obtain the data flow identifier and the congestion state information from the control plane signaling; or
- the receiver 111 may be, but not limited to, a gateway device/PCEF, or a third-party device, or a device E; the processor 112 may be, but not limited to, a policy and charging control function entity; 113 may be, but is not limited to, ⁇ E, or a third party device.
- the access network device After the foregoing solution is adopted, after determining the data flow that causes the access network to be congested, the access network device sends, to the receiver, congestion state information and a data flow identifier for indicating congestion of the access network, and the processor receives the congestion state at the receiver. After the information and the data flow are identified, the QoS of the data flow corresponding to the data flow identifier is reduced according to the congestion state information, so as to alleviate network congestion.
- the embodiment provides an access network device, as shown in FIG. 12, which may include:
- the processor 121 is configured to determine a data flow used to indicate that the access network is congested
- the transmitter 122 is configured to send, to the core network device, congestion state information used to indicate congestion of the access network. And the data flow identifier, so that the core network device reduces the quality of service QoS of the data flow according to the congestion state information and the data flow identifier.
- the access network device After the foregoing solution is adopted, after determining the data flow that causes the access network to be congested, the access network device sends, to the receiver, congestion state information and a data flow identifier for indicating congestion of the access network, and the processor receives the congestion state at the receiver. After the information and the data flow are identified, the QoS of the data flow corresponding to the data flow identifier is reduced according to the congestion state information, so as to alleviate network congestion.
- the present embodiment provides an access network device, which is a further extension of the access network device shown in FIG. 12, as shown in FIG.
- the processor 1 31 is configured to determine a data flow used to indicate congestion of the access network.
- the transmitter 1 32 is configured to send, to the core network device, congestion state information and a data flow identifier for indicating congestion of the access network, so that the core network device reduces the quality of service QoS of the data flow according to the congestion state information and the data flow identifier.
- the receiver 1 33 is configured to receive a report indication message sent by the core network device, where the report indication message is used to instruct the access network device to send the congestion state information and the data flow identifier to the core network device.
- the sender 1 31 is configured to send a user plane data packet of the data flow including the congestion state information to the core network device, so that the core network device acquires the data flow identifier corresponding to the data flow, and obtains the congestion from the user plane data packet.
- Status information or,
- the control plane signaling is configured to send the data flow identifier and the congestion state information to the core network device, so that the core network device obtains the data flow identifier and the congestion state information from the control plane signaling; or is configured to send the information to the core network device.
- User plane packet for data flow identification and congestion status information.
- the transmitter sends the congestion state information and the data flow identifier for indicating the congestion of the access network to the core network device, and the core network device receives the congestion state.
- the QoS of the data flow corresponding to the data flow identifier is reduced according to the congestion state information, so as to alleviate network congestion.
- the embodiment provides a system for mitigating network congestion.
- the core network device 141 and the access network device 142 provided in the foregoing device embodiments may be included.
- the implementations of the core network device 141 and the access network device 142 are the same as those of the core network device and the access network device provided in this embodiment, and are not described here.
- the access network device sends the congestion state information and the data flow identifier indicating the congestion of the access network to the core network device after determining the data flow that causes the access network to be congested, and the core network device receives the congestion state. After the information and the data flow are identified, the QoS of the data flow corresponding to the data flow identifier is reduced according to the congestion state information, so as to alleviate network congestion.
- the present invention can be implemented by means of software plus necessary general hardware, and of course, by hardware, but in many cases, the former is a better implementation. .
- the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a readable storage medium, such as a floppy disk of a computer.
- a hard disk or optical disk or the like includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本实施例提供一种缓解网络拥塞的方法、核心网设备和接入网设备。涉及通信技术领域。解决了不能及时有效地缓解网络拥塞的问题。具体可以包括:核心网设备获取用于指示接入网拥塞的拥塞状态信息和数据流标识;根据拥塞状态信息,降低数据流标识所对应的数据流的服务质量QoS。可应用于缓解网络拥塞中。
Description
緩解网络拥塞的方法、 核心网设备和接入网设备 技术领域
本发明涉及通信技术领域, 尤其涉及緩解网络拥塞的方法、 核心网设备 和接入网设备。
背景技术
由于无线网络部署的 cell (信元)容量有限, 当过量的终端接入网络中 时, 可能会导致网络拥塞。
为了緩解网络拥塞, 网络侧 (通常的, 可以为核心网设备)可以修改承 载的 PCC rule (Policy and Charging Control rule, 策略与计费控制规则) 或者, ADC rule (Application Detection and Control, 应用探测) 中的 QoS ( Quality of Service,月良务质量)参数(例: ¾口, 减小 MBR ( Maximum Bi t Rate, 最大比特率)、 GBR (Guaranteed Bit Rate,保证最大比特率) 的数值)、 去激 活部分承载、 分离部分终端等。 其中, QoS 参数可以包括: QCI (QoS Class Identifier, QoS类标识 )、 ARP (Allocation and Retention Priority, 分 配与抢占优先级)、 MBR, GBR, 以及上 /下行最大比特率(UL/DL maximum bit rate)等。 现有技术中, 修改 PCC rule、 ADC rule/QoS参数的方法可以包括: 由 PCRF (Policy and Charging Rules Function, 策略与计费控制功能) 实 体(以下筒称为 PCRF)激活或修改指定的数据流对应的 PCC rule/QoS参数, 或者, 由 TDF (Taffic detection function, 流探测功能) 实体(以下筒称 为 TDF)激活或修改, 比如降低指定的数据流对应的 ADC rule (Application Detection and Control, 应用探测 ) 中的当前的 UL/DL maximum bit rate (上 /下行最大比特率), 例如, 降低目前认为占用过多网络资源的应用业务, 比如 P2P (点对点)类业务(如 Skype等)。
在实现上述緩解网络拥塞的过程中, 发明人发现现有技术中至少存在如 下问题: 网络侧配置的指定的数据流通常为过度占用网络资源的应用业务数 据流, 网络侧修改该应用业务数据流对应的 PCC rule/QOS, 但是随着应用业 务的多样化, 每种业务对网络带来的沖击更是多种多样, 很难预估当前网络
的拥塞是由哪种应用业务数据流导致的, 因此, 这种方式可能不能及时有效 地緩解网络拥塞。
发明内容
本发明的实施例提供一种緩解网络拥塞的方法、 核心网设备和接入网设 备, 解决了不能及时有效地緩解网络拥塞的问题。
为达到上述目的, 本发明的实施例采用如下技术方案:
一方面, 提供一种緩解网络拥塞的方法, 包括:
核心网设备获取用于指示接入网拥塞的拥塞状态信息和数据流标识; 根据所述拥塞状态信息, 降低所述数据流标识所对应的数据流的服务质 量 QoS。
另外, 还提供另一种緩解网络拥塞的方法, 包括:
接入网设备确定接入网拥塞的数据流;
向核心网设备发送用于指示接入网拥塞的拥塞状态信息和数据流标识, 以便所述核心网设备根据所述拥塞状态信息和所述数据流标识降低所述数据 流的服务质量 QoS。
另一方面, 提供一种核心网设备, 包括:
接收器, 用于获取用于指示接入网拥塞的拥塞状态信息和数据流标识; 处理器, 用于根据所述拥塞状态信息, 降低所述数据流标识所对应的数 据流的服务质量 QoS。
另外, 还提供一种接入网设备, 包括:
处理器, 用于确定用于指示接入网拥塞的数据流;
发送器, 用于向核心网设备发送用于指示接入网拥塞的拥塞状态信息和 数据流标识, 以便所述核心网设备根据所述拥塞状态信息和所述数据流标识 降低所述数据流的服务质量 QoS。
再一方面, 提供一种緩解网络拥塞的系统, 包括:
上述内容中提供的核心网设备和接入网设备。
本发明实施例提供的緩解网络拥塞的方法和核心网设备, 采用上述方案
后, 接入网设备在确定导致接入网拥塞的数据流后, 向核心网设备发送用于 指示接入网拥塞的拥塞状态信息和数据流标识, 核心网设备在接收到拥塞状 态信息和数据流标识后, 根据拥塞状态信息, 降低数据流标识所对应的数据 流的 QoS , 以便于緩解网络拥塞。
附图说明
为了更清楚地说明本发明实施例中的技术方案, 下面将对实施例描述中 所需要使用的附图作筒单地介绍, 显而易见地, 下面描述中的附图仅仅是本 发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动的 前提下, 还可以根据这些附图获得其他的附图。
图 1为本实施例提供的緩解网络拥塞的方法流程图;
图 2为本实施例提供的緩解网络拥塞的方法流程图;
图 3为图 2所示的方法中 PCEF与 PCRF之间信息传递的示意图; 图 4a为图 2所示的方法中, 接入网络设备和核心网设备的数据传输示意 图;
图 4b 为图 2 所示的方法中接入网络设备和核心网设备的数据传输示意 图;
图 5为本实施例提供的緩解网络拥塞的方法流程图;
图 6为本实施例提供的一种匪 E向接入网设备发送上报指示消息的方法 示意图;
图 7为本实施例提供的緩解网络拥塞的方法流程图;
图 8为本实施例提供的緩解网络拥塞的方法流程图;
图 9为本实施例提供的緩解网络拥塞的方法流程示意图;
图 10为本实施例提供的一种核心网设备结构示意图;
图 11为本实施例提供的另一种核心网设备结构示意图;
图 12为本实施例提供的一种接入网设备结构示意图;
图 1 3为本实施例提供的另一种接入网设备结构示意图;
图 14为本实施例提供的一种緩解网络拥塞的系统结构示意图。
具体实施方式
下面将结合本发明实施例中的附图, 对本发明实施例中的技术方案进行 清楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而 不是全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有作 出创造性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范围。
现有技术中, 由网络侧通过修改相应数据流对应的 PCC rule/QoS参数来 解决网络拥塞的问题。 但是, 由于艮难预估当前网络的拥塞是由哪种应用业 务数据流导致的, 因此, 可能不能及时有效地緩解网络拥塞。
为了解决上述问题, 本方案中, 接入网设备首先确定导致网络拥塞的数 据流, 然后, 通过相应方式将该数据流通知核心网设备, 使核心网设备确定 导致网络拥塞的数据流对应的策略与计费控制规则和 /或应用探测控制规则, 进而使得核心网设备根据确定的策略与计费控制规则和 /或应用探测控制规 则对相应的数据流以及其所在的承载的 QoS 参数进行修改, 该承载可以为导 致网络拥塞的数据流所在的承载。
作为本实施例的一种实施方式, 核心网设备可以包括但不限于: PCRF、 网关设备 /PCEF ( Pol i cy and Charging Enforcement Func t ion, 策略和计费 执行) 实体(以下筒称为 PCEF )、 MME ( Mobi l i ty Management Ent i ty, 移动 性管理网元)等。
本实施例对 PCRF、 网关设备 /PCEF、 匪 E的功能不作细致描述, 为本领域 技术人员熟知的技术, 在此不再赘述。
为了使本领域技术人员能够更清楚地理解本实施例提供的技术方案, 下 面通过具体的实施例对本发明实施例提供的緩解网络拥塞的方法进行详细说 明。
本实施例提供一种緩解网络拥塞的方法, 该方法的执行主体可以为核心 网设备, 如图 1所示, 可以包括:
101、 核心网设备获取用于指示接入网拥塞的拥塞状态信息和数据流标 识。
作为本实施例的一种实施方式, 用于指示接入网拥塞的 (即导致接入网
拥塞的)数据流可以是过度占用网络资源的数据流, 具体是哪种数据流, 可 以由接入网设备根据各种数据流占用的带宽资源决定。
比如当网络拥塞时, 某些数据流占用了较大带宽资源, 便可以认为这些 数据流为导致网络拥塞的数据流。 占用了较大带宽资源具体如何定义, 可以 由网络根据实际情况自定义, 比如可以为但不限于, 当某业务流占用了 50% 以上的带宽资源, 则可以认为该数据流为过度占用网络资源的数据流或者被 称为是导致拥塞的数据流。 以下全文中导致网络拥塞的数据流均为此意。
1 02、 根据拥塞状态信息, 降低数据流标识所对应的数据流的服务质量
QoS。
采用上述方案后, 接入网设备在确定导致接入网拥塞的数据流后, 向核 心网设备发送用于指示接入网拥塞的拥塞状态信息和数据流标识, 核心网设 备在接收到拥塞状态信息和数据流标识后, 根据拥塞状态信息, 降低数据流 标识所对应的数据流的 QoS , 以便于緩解网络拥塞。
本实施例提供另一种緩解网络拥塞的方法, 该方法是对图 1 所示的方法 的进一步扩展, 如图 2所示, 可以包括:
201、 核心网设备获取用于指示接入网拥塞的拥塞状态信息和数据流标 识。
在发生网络拥塞时, 接入网设备在确定过度占用网络资源或者导致网络 拥塞的数据流后, 向核心网设备发送用于指示接入网拥塞的拥塞状态信息和 数据流标识。
进一步的, 核心网设备获取用于指示接入网拥塞的拥塞状态信息和数据 流标识可以包括但不限于:
核心网设备接收包含数据流标识和拥塞状态信息的控制面信令, 核心网 设备从控制面信令中获取数据流标识和拥塞状态信息; 或者,
核心网设备接收包含数据流标识和拥塞状态信息的用户面数据包; 或者, 核心网设备接收包含拥塞状态信息的数据流的用户面数据包, 核心网设 备获取数据流对应的数据流标识, 并从用户面数据包中获取拥塞状态信息。
本实施例对核心网设备获取拥塞状态信息和数据流标识的方法不作限 定, 可以根据实际需要进行设定, 在此不再赘述。
202、 核心网设备判断是否存在数据流标识对应的策略与计费控制规则和
/或应用探测控制规则;若存在,则执行步骤 203 ,若不存在,则执行步骤 205。
作为本实施例的一种实施方式,核心网设备可以为网关设备 /PCEF ,这样, 本步骤可以为: 网关设备 /PCEF判断是否存在数据流标识对应的策略与计费控 制规则和 /或应用探测控制规则。
具体的, 当核心网设备降低策略与计费控制规则中数据流标识所对应的 数据流的 QoS 时, 本步骤可以为判断是否存在数据流标识对应的策略与计费 控制规则; 或者, 当核心网设备降低应用探测控制规则中数据流标识所对应 的数据流的 QoS 时, 本步骤可以为判断是否存在数据流标识对应的应用探测 控制规则; 或者, 当核心网设备降低应用探测控制规则和策略与计费控制规 则中数据流标识所对应的数据流的 QoS 时, 本步骤可以为判断是否存在数据 流标识对应的应用探测控制规则和策略与计费控制规则。
本实施例对步骤 202的判断方法不作限定, 可以根据实际需要进行设定, 在此不再赘述。
20 3、 获取数据流标识对应的已有的策略与计费控制规则和应用探测控制 规则中至少一项规则。
204、修改至少一项规则中的 QoS参数,使得修改后的 QoS参数对应的 QoS 低于修改前的数据流的 QoS参数对应的 QoS。
作为本实施例的一种实施方式, 核心网设备可以但不限于通过修改至少 一项规则中的 QoS参数来降低数据流标识所对应的数据流的 QoS。
进一步可选的, 核心网设备还可以通过重新激活至少一项规则并删除原 有至少一项规则的方式来降低数据流标识所对应的数据流的 QoS , 使得, 重新 激活后的至少一项规则中的 QoS参数对应的 QoS低于激活前的数据流的 QoS 参数对应的 QoS。
作为本实施例的一种实施方式, 如图 3 所示, 降低策略与计费控制规则
中数据流标识所对应的数据流的 QoS可以包括但不限于:在网关设备 /PCEF接 收到拥塞状态信息和数据流标识并判断出存在数据流标识对应的策略与计费 控制规则后, 将拥塞状态信息和数据流标识对应的策略与计费控制规则发送 至 PCRF , PCRF根据拥塞状态信息对数据流标识对应的策略与计费控制规则进 行修改, PCRF可以对策略与计费控制规则中包含的 QoS参数进行修改(即降 氐 QoS ), 例如, 可以爹改但不限于 QCI、 ARP、 MBR、 GBR等。
或者, PCRF还可以根据数据流标识和拥塞状态信息重新激活数据流标识 对应的策略与计费控制规则。
其中, 图 4a为接入网络设备和核心网设备(可以包括: 网关设备 /PCEF、 PCRF等 )之间的数据传输示意图。
进一步可选的, 如图 4b所示, 降低应用探测控制规则中数据流标识对应 的数据流的 QoS还可以包括: 若 PCRF判断出存在数据流标识对应的应用探测 控制规则, 则 PCRF还可以根据接收到的数据流标识向 TDF发送指示信息, 该 指示信息用于指示 TDF修改数据流标识对应的应用探测控制规则。 TDF可以修 改 ADC ru l e中的 QoS参数, 例如, 可以降低 ADC Ru l e中的上下行的最大比 特率 ( UL/DL max imum b i t ra te )等。
或者, 该指示信息还可以用于指示 TDF 重新激活数据流标识对应的应用 探测控制规则并删除原有的应用探测控制规则, TDF向 PCRF发送确认消息, 该确认消息可以包含但不限于重新激活后的应用探测控制规则, 使得重新激 活后的应用探测控制规则中的 QoS参数对应的 QoS低于激活前的数据流的 QoS 参数对应的 QoS
其中, 图 4b中的 ADC ru l e为应用探测控制规则。
值得说明的是, 核心网设备还可以同时降低策略与计费控制规则和应用 探测控制规则中的数据流标识所对应的数据流的 QoS ,该方法具体实施方式在 此不再赘述。
本实施例对 QoS参数不作限定, 为本领域技术人员熟知的技术, 并可以 根据实际需要进行设定, 在此不再赘述。
本实施例对网关设备 /PCEF向 PCRF发送拥塞状态信息和数据流标识的方 法不作限定, 为本领域技术人员熟知的技术, 并可以根据实际需要进行设定, 例如, 可以是但不限于 PCEF向 PCRF发送包含有拥塞状态信息和数据流标识 的 IP-CAN ( IP-Connec t i v i ty Acces s Network , IP< Internet Protoco l , 网 络间互联协议〉连接访问网络)消息, 在此不再赘述。
执行步骤 206。
205、 激活数据流标识对应的策略与计费控制规则和应用探测控制规则中 至少一项规则。
作为本实施例的一种实施方式,当网关设备 /PCEF判断出不存在数据流标 识对应的策略与计费控制规则和 /或应用探测控制规则时, 则需要向 PCRF发 送数据流标识, 以便 PCRF激活数据流标识对应的策略与计费控制规则和应用 探测控制规则中至少一项规则。
其中, 激活的策略与计费控制规则和应用探测控制规则中至少一项规则 中的 QoS参数对应的 QoS低于激活前的数据流的 QoS参数对应的 QoS。
作为本实施例的一种实施方式, 当 PCRF激活数据流标识对应的策略与计 费控制规则后, 将激活的策略与计费控制规则发送至网关设备 /PCEF , 以便网 关设备 /PCEF根据接收到的策略与计费控制规则执行后续操作, 比如, 限制当 前业务流的 Q0S参数等, 进而可以减小数据流对应的承载占用的带宽等。
作为本实施例的一种实施方式, PCRF激活数据流标识对应的应用探测控 制规则可以包括: PCRF在接收到数据流标识后, 向 TDF发送指示信息, 该指 示信息可以用于指示 TDF激活数据流标识对应的应用探测控制规则; TDF将向 PCRF发送确认消息, 该确认消息可以包含但不限于激活后的应用探测控制规 则。
当 PCRF激活数据流标识对应的应用探测控制规则后, 可以将该应用探测 控制规则发送到 TDF设备, 以便 TDF设备根据接收到的应用探测控制规则执 行后续操作, 比如修改应用业务的 Q0S 参数, 比如上下行最大比特率等, 进 而可以减小数据流占用的资源。
本实施例对 PCRF激活策略与计费控制规则的方法, 和 TDF激活应用探测 控制规则中的方法不作限定, 为本领域技术人员熟知的技术, 并可以根据实 际需要进行设定, 在此不再赘述。
作为本实施例的一种实施方式, PCRF可以向网关设备 /PCEF发送 IP-CAN 消息, 该 IP-CAN消息可以包含但不限于修改后或激活后的策略与计费控制规 则和修改后或激活后的应用探测控制规则中至少一项规则。
本实施例对向网关设备 /PCEF 发送修改后或激活后的策略与计费控制规 则和修改后或激活后的应用探测控制规则中至少一项规则的方法不作限定, 可以根据实际需要进行设定, 在此不再赘述。
作为本实施例的一种实施方式, PCRF可以通过向 TDF设备发送 Diame ter
(直径)会话消息, 以将包含有确定的应用的带宽参数(上下行最大比特率) 的 ADC ru l e发送到 TDF设备。 在此不再赘述。
本实施例对 TDF设备根据修改或确定应用探测控制规则中的 QoS参数的 方法不作限定, 为本领域技术人员熟知的技术, 在此不再赘述。
值得说明的是, 本实施例还可以不执行步骤 202 的判断步骤, 而直接执 行步骤 205。
即根据拥塞状态信息, 降低数据流标识所对应的数据流的服务质量 QoS 可以为: 在核心网设备获取到接入网拥塞的拥塞状态信息和数据流标识后, 重新激活数据流标识对应的策略与计费控制规则和应用探测控制规则中至少 一项规则,并删除原有的策略与计费控制规则和 /或应用探测控制规则,其中, 激活的策略与计费控制规则与计费控制规则和应用探测控制规则中至少一项 规则中的 QoS参数对应的 QoS低于激活前的数据流的 QoS参数对应的 QoS。
206、 向接入网设备发送上报指示消息, 上报指示消息用于指示接入网设 备向核心网设备发送拥塞状态信息和数据流标识。
值得说明的是, 步骤 206 是可选步骤, 而且在执行时也不一定执行于步 骤 205之后, 还可以执行与本实施例的任意步骤之前或之后, 在此不作限定
采用上述方案后, 接入网设备在确定导致接入网拥塞的数据流后, 向核 心网设备发送用于指示接入网拥塞的拥塞状态信息和数据流标识, 核心网设 备在接收到拥塞状态信息和数据流标识后, 根据拥塞状态信息, 降低数据流 标识所对应的数据流的 QoS , 以便于緩解网络拥塞。
进一步可选的, 在网络发生拥塞时, 核心网设备可以根据上报指示消息 确定是否向核心网设备发送拥塞状态信息和数据流标识。
本实施例提供另一种緩解网络拥塞的方法, 该方法主要用于描述接入网 设备根据上报指示消息确定是否向核心网设备发送拥塞状态信息和数据流标 识的过程, 如图 5所示, 可以包括:
501、 终端向接入网设备发送附着请求;
502、 接入网设备向 E转发附着请求;
503、 MME根据附着请求向网关设备 /PCEF发送激活会话请求;
504、 网关设备 /PCEF向 PCRF发送 IP-CAN会话建立请求;
505、 PCRF向网关设备 /PCEF发送 IP-CAN会话建立响应。
如果 PCRF决定在接入网拥塞时, 使接入网设备向核心网设备上报导致拥 塞的数据流信息, 则 PCRF向网关设备 /PCEF发送上报指示消息, 即上报指示 消息用于指示在接入网拥塞时, 接入网设备向核心网设备上报用于指示接入 网拥塞的拥塞状态信息和数据流标识, 上报指示消息可以包含于 IP-CAN会话 建立响应中并被发送至网关设备 /PCEF。
506、 网关设备 /PCEF向匪 E发送激活会话响应,该响应中可以包含有上报 指示消息;
507、 E向接入网设备发送初始上下文建立请求 /附着接受消息, 该消息 中可以包含有上报指示消息;
进一步可选的, 如图 6所示, 匪 E还可以通过其他方式向接入网设备发 送上 指示消息, 具体的可以包括:
1、 终端向接入网设备发送服务请求;
2、 接入网设备向 MME发送服务请求;
3、 匪 E 向接入网设备发送初始上下文建立请求, 初始上下文建立请求中
可以包含但不限于上报指示消息;
4、 无线 7 载建立。
本实施例对 E 向接入网设备发送上报指示消息的方法不作限定, 可以 根据实际需要进行设定, 在此不再赘述。
508、 接入网向终端发送 RRC ( Rad io Resource Cont ro l , 无线资源控制协 议)连接重配置过程。
本实施例对 RRC连接重配置的方法、 和附着请求的功能、 和服务请求的 功能不作限定, 为本领域技术人员熟知的技术, 在此不再赘述。
采用上述方案后, 接入网设备在确定导致接入网拥塞的数据流后, 向核 心网设备发送用于指示接入网拥塞的拥塞状态信息和数据流标识, 核心网设 备在接收到拥塞状态信息和数据流标识后, 根据拥塞状态信息, 降低数据流 标识所对应的数据流的 QoS , 以便于緩解网络拥塞。
本实施例提供另一种緩解网络拥塞的方法, 该方法的执行主体可以为接 入网设备, 如图 7所示, 可以包括:
701、 接入网设备确定用于指示接入网拥塞的数据流;
702、 向核心网设备发送用于指示接入网拥塞的拥塞状态信息和数据流标 识, 以便核心网设备根据拥塞状态信息和数据流标识降低数据流的服务质量 QoS。
采用上述方案后, 接入网设备在确定导致接入网拥塞的数据流后, 向核 心网设备发送用于指示接入网拥塞的拥塞状态信息和数据流标识, 核心网设 备在接收到拥塞状态信息和数据流标识后, 根据拥塞状态信息, 降低数据流 标识所对应的数据流的 QoS , 以便于緩解网络拥塞。
本实施例提供一种緩解网络拥塞的方法, 该方法是对图 7 所示的方法的 进一步扩展, 如图 8所示, 可以包括:
801、 接收核心网设备发送的上报指示消息。
上报指示消息可以用于指示接入网设备向核心网设备发送拥塞状态信息 和数据流标识。 本步骤是可选的。
802、 接入网设备确定用于指示接入网拥塞的数据流。
作为本实施例的一种是实施方式, 接入网设备确定导致网络拥塞的数据 流可以包括:
当接入网设备不具有 DPI ( Deep Packet Inspect ion, 深度包检测)功能 时, 接入网设备可以获知当前过度占用网络资源 (即导致网络拥塞) 的数据 流对应的包过滤器信息, 即数据流的 IP五元组信息; 或者, 当接入网设备具 有 DPI 功能时, 接入网设备可以获知导致网络拥塞的数据流对应的业务标识 (Appl i cat ion Id) , 该标识是在接入网侧与网络侧均统一配置, 所以当接入 网将该标识通知网络侧数据流时, 网络侧能够识别该数据流。 因此, 可以根 据包过滤器信息或业务标识、 和拥塞状态信息确定导致网络拥塞的数据流。
值得说明的是, 本实施例中将包过滤器信息、 和业务标识均称为数据流 标识。
本实施例对接入网设备获取包过滤器信息、 和业务标识的方法不作限定, 为本领域技术人员熟知的技术, 在此不再赘述。
本实施例对接入网设备确定导致网络拥塞的数据流的方法不作限定, 可 以根据实际需要进行设定, 在此不再赘述。
803、 向核心网设备发送用于指示接入网拥塞的拥塞状态信息和数据流标 识, 以便核心网设备根据拥塞状态信息和数据流标识降低数据流的服务质量 QoS。
进一步的, 向核心网设备发送接入网拥塞信息可以为: 向核心网设备发 送包含拥塞状态信息的数据流的用户面数据包, 以便核心网设备获取数据流 对应的数据流标识, 并从用户面数据包中获取拥塞状态信息;
或者, 向核心网设备发送包含数据流标识和拥塞状态信息的用户面数据 包;
或者, 向核心网设备发送包含数据流标识和拥塞状态信息的控制面信令, 以便核心网设备从控制面信令中获取数据流标识和拥塞状态信息; 进一步的, 如图 9所示,接入网设备可以将包含有拥塞状态信息的控制面信令发送至匪 E,
再由 MME发送至网关设备 /PCEF、 或第三方设备。
或者, 向核心网设备发送接入网拥塞信息还可以为: 当接入网设备与核 心网设备之间不存在上行数据包时, 接入网设备无法向核心网设备发送包含 拥塞状态信息的数据包, 则还可以将拥塞状态信息包含于上行数据包的消息 头中并被发送至核心网设备, 但是, 该上行数据包是当前网关设备管理的其 它包含有上行数据包的终端的上行数据包, 此时, 该上行数据包中还可以包 括该终端的标识。
本实施例对第三方设备不作限定, 可以根据实际需要进行设定, 例如, 可以为但不限于网管设备、 探测网络设备等, 在此不再赘述。
采用上述方案后, 接入网设备在确定导致接入网拥塞的数据流后, 向核 心网设备发送用于指示接入网拥塞的拥塞状态信息和数据流标识, 核心网设 备在接收到拥塞状态信息和数据流标识后, 根据拥塞状态信息, 降低数据流 标识所对应的数据流的 QoS , 以便于緩解网络拥塞。
下面提供一些装置实施例, 该装置实施例与上述提供的相应的方法实施 例对应。
本实施例提供一种核心网设备, 如图 10所示, 可以包括:
接收器 101 , 用于获取用于指示接入网拥塞的拥塞状态信息和数据流标 识;
处理器 102 , 用于根据拥塞状态信息, 降低数据流标识所对应的数据流的 服务质量 QoS。
采用上述方案后, 接入网设备在确定导致接入网拥塞的数据流后, 向接 收器发送用于指示接入网拥塞的拥塞状态信息和数据流标识, 处理器在接收 器接收到拥塞状态信息和数据流标识后, 根据拥塞状态信息, 降低数据流标 识所对应的数据流的 QoS , 以便于緩解网络拥塞。
本实施例提供另一种核心网设备, 该核心网设备是对图 10所示的核心网 设备的进一步扩展, 如图 1 1所示, 可以包括:
接收器 111 , 用于获取用于指示接入网拥塞的拥塞状态信息和数据流标
处理器 112, 用于根据拥塞状态信息, 降低数据流标识所对应的数据流的 服务质量 QoS。
发送器 113, 用于向接入网设备发送上报指示消息, 上报指示消息用于指 示接入网设备向核心网设备发送拥塞状态信息和数据流标识。
进一步的, 处理器 112, 用于获取数据流标识对应的已有的策略与计费控 制规则和应用探测控制规则中至少一项规则; 修改至少一项规则中的 QoS 参 数, 使得修改后的 QoS参数对应的 QoS低于修改前的数据流的 QoS参数对应 的 QoS。
进一步的, 处理器 112, 用于激活数据流标识对应的策略与计费控制规则 和应用探测控制规则中至少一项规则, 其中, 至少一项规则中的 QoS参数对 应的 QoS低于激活前的数据流的 QoS参数对应的 QoS。
进一步的,接收器 111, 用于接收包含数据流标识和拥塞状态信息的控制 面信令, 从控制面信令中获取数据流标识和拥塞状态信息; 或者,
用于接收包含数据流标识和拥塞状态信息的用户面数据包; 或者, 用于接收包含拥塞状态信息的数据流的用户面数据包, 获取数据流对应 的数据流标识, 并从用户面数据包中获取拥塞状态信息。
作为本实施例的一种实施方式, 接收器 111 可以为但不限于网关设备 /PCEF、 或第三方设备、 或匪 E; 处理器 112可以为但不限于策略与计费控制 功能实体; 发送器 113可以为但不限于匪 E、 或第三方设备。
采用上述方案后, 接入网设备在确定导致接入网拥塞的数据流后, 向接 收器发送用于指示接入网拥塞的拥塞状态信息和数据流标识, 处理器在接收 器接收到拥塞状态信息和数据流标识后, 根据拥塞状态信息, 降低数据流标 识所对应的数据流的 QoS, 以便于緩解网络拥塞。
本实施例提供一种接入网设备, 如图 12所示, 可以包括:
处理器 121, 用于确定用于指示接入网拥塞的数据流;
发送器 122,用于向核心网设备发送用于指示接入网拥塞的拥塞状态信息
和数据流标识, 以便核心网设备根据拥塞状态信息和数据流标识降低数据流 的服务质量 QoS。
采用上述方案后, 接入网设备在确定导致接入网拥塞的数据流后, 向接 收器发送用于指示接入网拥塞的拥塞状态信息和数据流标识, 处理器在接收 器接收到拥塞状态信息和数据流标识后, 根据拥塞状态信息, 降低数据流标 识所对应的数据流的 QoS , 以便于緩解网络拥塞。
本实施例提供一种接入网设备, 该接入网设备是对图 12所示的接入网设 备的进一步扩展, 如图 1 3所示, 可以包括:
处理器 1 31 , 用于确定用于指示接入网拥塞的数据流。
发送器 1 32 ,用于向核心网设备发送用于指示接入网拥塞的拥塞状态信息 和数据流标识, 以便核心网设备根据拥塞状态信息和数据流标识降低数据流 的服务质量 QoS。
接收器 1 33 , 用于接收核心网设备发送的上报指示消息, 上报指示消息用 于指示接入网设备向核心网设备发送拥塞状态信息和数据流标识。
进一步的,发送器 1 31 , 用于向核心网设备发送包含拥塞状态信息的数据 流的用户面数据包, 以便核心网设备获取数据流对应的数据流标识, 并从用 户面数据包中获取拥塞状态信息; 或者,
用于向核心网设备发送包含数据流标识和拥塞状态信息的控制面信令, 以便核心网设备从控制面信令中获取数据流标识和拥塞状态信息; 或者, 用于向核心网设备发送包含数据流标识和拥塞状态信息的用户面数据 包。
采用上述方案后, 发送器在处理器确定导致接入网拥塞的数据流后, 向 核心网设备发送用于指示接入网拥塞的拥塞状态信息和数据流标识, 核心网 设备在接收到拥塞状态信息和数据流标识后, 根据拥塞状态信息, 降低数据 流标识所对应的数据流的 QoS , 以便于緩解网络拥塞。
本实施例提供一种緩解网络拥塞的系统, 如图 14所示, 可以包括: 上述 装置实施例中提供的核心网设备 141和接入网设备 142。
本实施例提供的核心网设备 141和接入网设备 142的实施方式与装置实 施例提供的核心网设备和接入网设备的实施方式相同, 在此不再赘述。
采用上述方案后, 接入网设备在确定导致接入网拥塞的数据流后, 向核 心网设备发送用于指示接入网拥塞的拥塞状态信息和数据流标识, 核心网设 备在接收到拥塞状态信息和数据流标识后, 根据拥塞状态信息, 降低数据流 标识所对应的数据流的 QoS , 以便于緩解网络拥塞。
通过以上的实施方式的描述, 所属领域的技术人员可以清楚地了解到本 发明可借助软件加必需的通用硬件的方式来实现, 当然也可以通过硬件, 但 很多情况下前者是更佳的实施方式。 基于这样的理解, 本发明的技术方案本 质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来, 该 计算机软件产品存储在可读取的存储介质中, 如计算机的软盘, 硬盘或光盘 等, 包括若干指令用以使得一台计算机设备(可以是个人计算机, 服务器, 或者网络设备等)执行本发明各个实施例所述的方法。
以上所述, 仅为本发明的具体实施方式, 但本发明的保护范围并不局限 于此, 任何熟悉本技术领域的技术人员在本发明揭露的技术范围内, 可轻易 想到变化或替换, 都应涵盖在本发明的保护范围之内。 因此, 本发明的保护 范围应所述以权利要求的保护范围为准。
Claims
1、 一种緩解网络拥塞的方法, 其特征在于, 包括:
核心网设备获取用于指示接入网拥塞的拥塞状态信息和数据流标识; 根据所述拥塞状态信息, 降低所述数据流标识所对应的数据流的服务质量
QoS。
2、 根据权利要求 1所述的方法, 其特征在于, 所述降低所述数据流标识所 对应的数据流的服务质量 QoS , 包括:
获取所述数据流标识对应的已有的策略与计费控制规则和应用探测控制规 则中至少一项规则;
修改所述至少一项规则中的 QoS参数, 使得修改后的 QoS参数对应的 QoS 低于修改前的所述数据流的 QoS参数对应的 QoS。
3、 根据权利要求 1所述的方法, 其特征在于, 所述降低所述数据流标识所 对应的数据流的服务质量 QoS , 包括:
激活所述数据流标识对应的策略与计费控制规则和应用探测控制规则中至 少一项规则, 其中, 所述至少一项规则中的 QoS参数对应的 QoS低于激活前的 所述数据流的 QoS。
4、 根据权利要求 1至 3中任意一项所述的方法, 其特征在于, 所述核心网 设备获取用于指示接入网拥塞的拥塞状态信息和数据流标识, 包括:
所述核心网设备接收包含所述数据流标识和所述拥塞状态信息的控制面信 令, 所述核心网设备从所述控制面信令中获取所述数据流标识和所述拥塞状态 信息; 或者,
所述核心网设备接收包含所述数据流标识和所述拥塞状态信息的用户面数 据包; 或者,
所述核心网设备接收包含所述拥塞状态信息的所述数据流的用户面数据 包, 所述核心网设备获取所述数据流对应的所述数据流标识, 并从所述用户面 数据包中获取所述拥塞状态信息。
5、 根据权利要求 1至 4中任意一项所述的方法, 其特征在于, 所述方法还
包括:
向接入网设备发送上报指示消息, 所述上报指示消息用于指示所述接入网 设备向所述核心网设备发送所述拥塞状态信息和所述数据流标识。
6、 一种緩解网络拥塞的方法, 其特征在于, 包括:
接入网设备确定用于指示接入网拥塞的数据流;
向核心网设备发送用于指示接入网拥塞的拥塞状态信息和数据流标识, 以 便所述核心网设备根据所述拥塞状态信息和所述数据流标识降低所述数据流的 服务质量 QoS。
7、 根据权利要求 6所述的方法, 其特征在于, 所述向核心网设备发送用于 指示接入网拥塞的拥塞状态信息和数据流标识为:
向核心网设备发送包含所述拥塞状态信息的所述数据流的用户面数据包, 以便所述核心网设备获取所述数据流对应的所述数据流标识, 并从所述用户面 数据包中获取所述拥塞状态信息; 或者,
向核心网设备发送包含所述数据流标识和所述拥塞状态信息的控制面信 令, 以便所述核心网设备从所述控制面信令中获取所述数据流标识和所述拥塞 状态信息; 或者,
向核心网设备发送包含所述数据流标识和所述拥塞状态信息的用户面数据 包。
8、 根据权利要求 6或 7所述的方法, 其特征在于, 在所述向核心网设备发 送用于指示接入网拥塞的拥塞状态信息和数据流标识之前, 所述方法还包括: 接收所述核心网设备发送的上报指示消息, 所述上报指示消息用于指示所 述接入网设备向所述核心网设备发送所述拥塞状态信息和所述数据流标识。
9、 一种核心网设备, 其特征在于, 包括:
接收器, 用于获取用于指示接入网拥塞的拥塞状态信息和数据流标识; 处理器, 用于根据所述拥塞状态信息, 降低所述数据流标识所对应的数据 流的服务质量 QoS。
10、 根据权利要求 9 所述的核心网设备, 其特征在于, 所述处理器, 用于
获取所述数据流标识对应的已有的策略与计费控制规则和应用探测控制规则中 至少一项规则; 修改所述至少一项规则中的 QoS参数, 使得修改后的 QoS参数 对应的 QoS低于修改前的所述数据流的 QoS参数对应的 QoS。
1 1、 根据权利要求 9 所述的核心网设备, 其特征在于, 所述处理器, 用于 激活所述数据流标识对应的策略与计费控制规则和应用探测控制规则中至少一 项规则, 其中, 所述至少一项规则中的 QoS参数对应的 QoS低于激活前的所述 数据流的 QoS参数对应的 QoS。
12、 根据权利要求 9至 1 1中任意一项所述的核心网设备, 其特征在于, 所 述接收器, 用于接收包含所述数据流标识和所述拥塞状态信息的控制面信令, 从所述控制面信令中获取所述数据流标识和所述拥塞状态信息; 或者,
用于接收包含所述数据流标识和所述拥塞状态信息的用户面数据包; 或者, 用于接收包含所述拥塞状态信息的所述数据流的用户面数据包, 获取所述 数据流对应的所述数据流标识, 并从所述用户面数据包中获取所述拥塞状态信 息。
1 3、 根据权利要求 9至 1 2中任意一项所述的核心网设备, 其特征在于, 所 述核心网设备还包括:
发送器, 用于向接入网设备发送上报指示消息, 所述上报指示消息用于指 示所述接入网设备向所述核心网设备发送所述拥塞状态信息和所述数据流标 识。
14、 一种接入网设备, 其特征在于, 包括:
处理器, 用于确定用于指示接入网拥塞的数据流;
发送器, 用于向核心网设备发送用于指示接入网拥塞的拥塞状态信息和数 据流标识, 以便所述核心网设备根据所述拥塞状态信息和所述数据流标识降低 所述数据流的服务质量 QoS。
15、 根据权利要求 14所述的接入网设备, 其特征在于, 所述发送器, 用于 向核心网设备发送包含所述拥塞状态信息的所述数据流的用户面数据包, 以便 所述核心网设备获取所述数据流对应的所述数据流标识, 并从所述用户面数据
包中获取所述拥塞状态信息; 或者,
用于向核心网设备发送包含所述数据流标识和所述拥塞状态信息的控制面 信令, 以便所述核心网设备从所述控制面信令中获取所述数据流标识和所述拥 塞状态信息; 或者,
用于向核心网设备发送包含所述数据流标识和所述拥塞状态信息的用户面 数据包。
16、 根据权利要求 14或 15所述的接入网设备, 其特征在于, 所述接入网 设备还包括:
接收器, 用于接收所述核心网设备发送的上报指示消息, 所述上报指示消 息用于指示所述接入网设备向所述核心网设备发送所述拥塞状态信息和所述数 据流标识。
17、 一种緩解网络拥塞的系统, 其特征在于, 包括: 权利要求 9至 1 3任意 一项所述的核心网设备和权利要求 14至 16任意一项所述的接入网设备。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201280001693.5A CN103907323A (zh) | 2012-10-30 | 2012-10-30 | 缓解网络拥塞的方法、核心网设备和接入网设备 |
PCT/CN2012/083777 WO2014067075A1 (zh) | 2012-10-30 | 2012-10-30 | 缓解网络拥塞的方法、核心网设备和接入网设备 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2012/083777 WO2014067075A1 (zh) | 2012-10-30 | 2012-10-30 | 缓解网络拥塞的方法、核心网设备和接入网设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014067075A1 true WO2014067075A1 (zh) | 2014-05-08 |
Family
ID=50626309
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2012/083777 WO2014067075A1 (zh) | 2012-10-30 | 2012-10-30 | 缓解网络拥塞的方法、核心网设备和接入网设备 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN103907323A (zh) |
WO (1) | WO2014067075A1 (zh) |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108886531B (zh) * | 2015-03-02 | 2021-04-20 | 康维达无线有限责任公司 | 使用服务层能力进行网络和应用管理 |
CN107493238A (zh) * | 2016-06-13 | 2017-12-19 | 华为技术有限公司 | 一种网络拥塞控制方法、设备及系统 |
CN108347746B (zh) * | 2017-01-23 | 2024-05-03 | 中兴通讯股份有限公司 | 接入控制方法、接入网网元及用户设备 |
WO2021012902A1 (zh) | 2019-07-24 | 2021-01-28 | 华为技术有限公司 | 一种处理网络拥塞的方法以及相关装置 |
CN113141311A (zh) | 2020-01-19 | 2021-07-20 | 华为技术有限公司 | 一种用于获取转发信息的方法及装置 |
CN118785242A (zh) * | 2023-04-04 | 2024-10-15 | 维沃移动通信有限公司 | 拥塞信息的操作方法、装置及通信设备 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1983845A (zh) * | 2006-04-16 | 2007-06-20 | 华为技术有限公司 | 一种上行链路速率调整的方法 |
CN101789880A (zh) * | 2010-01-22 | 2010-07-28 | 中国电信股份有限公司 | 基于IP接入网实现上行QoS的方法和多业务接入网关 |
CN102075898A (zh) * | 2010-12-21 | 2011-05-25 | 华为技术有限公司 | 业务控制方法、装置及系统 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101009631A (zh) * | 2006-01-24 | 2007-08-01 | 华为技术有限公司 | 一种QoS控制方法和系统 |
CN101075963B (zh) * | 2007-07-02 | 2012-05-23 | 中兴通讯股份有限公司 | 一种基于网络QoS的动态控制装置及其方法 |
EP2219331B1 (en) * | 2009-02-02 | 2011-06-15 | Alcatel Lucent | Telecommunication method and apparatus thereof |
CN101720075A (zh) * | 2009-02-10 | 2010-06-02 | 中兴通讯股份有限公司 | 一种上报业务信息的方法和装置 |
CN102215469B (zh) * | 2010-04-09 | 2015-01-28 | 中兴通讯股份有限公司 | 一种基于网络负荷的策略计费控制方法和系统 |
-
2012
- 2012-10-30 WO PCT/CN2012/083777 patent/WO2014067075A1/zh active Application Filing
- 2012-10-30 CN CN201280001693.5A patent/CN103907323A/zh active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1983845A (zh) * | 2006-04-16 | 2007-06-20 | 华为技术有限公司 | 一种上行链路速率调整的方法 |
CN101789880A (zh) * | 2010-01-22 | 2010-07-28 | 中国电信股份有限公司 | 基于IP接入网实现上行QoS的方法和多业务接入网关 |
CN102075898A (zh) * | 2010-12-21 | 2011-05-25 | 华为技术有限公司 | 业务控制方法、装置及系统 |
Also Published As
Publication number | Publication date |
---|---|
CN103907323A (zh) | 2014-07-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN109314710B (zh) | 用于通信网络中的服务质量监测、策略执行和计费的系统和方法 | |
WO2019228214A1 (zh) | 一种无线承载建立、业务流的监测方法及装置 | |
CN104115543B (zh) | 蜂窝式网络中触发以及上报多样业务信息的方法及装置 | |
US10523589B2 (en) | Traffic control method, apparatus, and system | |
CN103650573B (zh) | 拥塞状态上报方法及接入网设备 | |
US9497128B2 (en) | Service rate control method, system and device | |
US9867076B2 (en) | PCRF apparatus and traffic handling method for use in PCRF | |
WO2014067075A1 (zh) | 缓解网络拥塞的方法、核心网设备和接入网设备 | |
WO2011110000A1 (zh) | 无线承载丢失信息的上报方法和装置 | |
CN108259434B (zh) | 一种用户侧QoS保障能力的开放方法及服务器 | |
US20150003246A1 (en) | Radio access network triggered bearer modification procedure | |
WO2013082789A1 (zh) | 一种拥塞控制方法及装置 | |
CN108271219B (zh) | 无线网络资源的控制方法及装置 | |
WO2018082597A1 (zh) | 拥塞控制方法及装置、基站 | |
CN113747479B (zh) | 获取网络资源的方法、设备及系统 | |
CN110139360B (zh) | 一种寻呼策略确定方法、装置、ran网元及核心网网元 | |
JP5736072B2 (ja) | 輻輳緩和の方法及び装置 | |
EP4040845B1 (en) | Communication method, apparatus and system | |
US20210360486A1 (en) | Traffic Availability in a Cellular Communication Network | |
CN103152794A (zh) | 业务接入方法及接入控制器 | |
WO2014166438A1 (zh) | 一种基于拥塞控制的策略控制方法、装置和系统 | |
CN103501513B (zh) | 一种处理信令消息的方法及系统 | |
WO2013097251A1 (zh) | Pcc架构下对报文的处理方法和设备 | |
CN110876160B (zh) | 基于多模基站下的资源传输控制方法及装置 | |
CN103139849B (zh) | 一种多网协同下的QoS业务执行方法和AF、PCRF |
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: 12887785 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 12887785 Country of ref document: EP Kind code of ref document: A1 |