WO2017148256A1 - 一种流量控制方法、装置和系统 - Google Patents

一种流量控制方法、装置和系统 Download PDF

Info

Publication number
WO2017148256A1
WO2017148256A1 PCT/CN2017/073451 CN2017073451W WO2017148256A1 WO 2017148256 A1 WO2017148256 A1 WO 2017148256A1 CN 2017073451 W CN2017073451 W CN 2017073451W WO 2017148256 A1 WO2017148256 A1 WO 2017148256A1
Authority
WO
WIPO (PCT)
Prior art keywords
traffic
guaranteed bandwidth
flow control
bandwidth
switching device
Prior art date
Application number
PCT/CN2017/073451
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 JP2017564623A priority Critical patent/JP6541117B2/ja
Priority to KR1020177034371A priority patent/KR102039384B1/ko
Priority to EP17759107.0A priority patent/EP3297323B1/en
Publication of WO2017148256A1 publication Critical patent/WO2017148256A1/zh
Priority to US15/909,565 priority patent/US10523589B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/805—QOS or priority aware
    • 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/20—Traffic policing
    • 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/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
    • 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/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
    • 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/31—Flow control; Congestion control by tagging of packets, e.g. using discard eligibility [DE] bits
    • 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/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
    • 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/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
    • H04L47/323—Discarding or blocking control packets, e.g. ACK packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
    • H04L47/762—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/808—User-type aware
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a flow control method, apparatus, and system.
  • EPS bearer In the Evolved Packet System (EPS), the basic granularity of Quality of Service (QoS) control is EPS bearer. All data flows on the same bearer will receive the same QoS guarantee, and different QoS guarantees need to be provided by different EPS bearers. According to different QoS, EPS bearers can be classified into two categories: Guaranteed Bit Rate (GBR) bearer and Non-Guaranteed Bit Rate (Non-GBR) bearer.
  • GBR Guaranteed Bit Rate
  • Non-GBR Non-Guaranteed Bit Rate
  • the GBR bearer is mainly used for voice, video, real-time games and other services, and is carried by a dedicated bearer.
  • the parameter GBR represents the bit rate that is expected to be provided by the GBR bearer; the parameter Maximum Bit Rate (MBR) limits the bit rate that the GBR bearer can provide, which indicates that the GBR bearer provides the upper limit of the desired data rate.
  • MBR Maximum Bit Rate
  • the MBR must be greater than or equal to GBR. In the case of resource shortages, traffic exceeding GBR will be discarded, but traffic within the GBR needs to be guaranteed.
  • Non-GBR bearers are mainly used for carrying various data services.
  • a Non-GBR bearer can be simply understood as a bearer that provides an Internet Protocol (IP) connection that tries to interconnect as a network, and is established with the establishment of a Public Data Network (PDN) link. Destroyed as the PDN link was removed. In the case of network congestion, the Non-GBR service (or bearer) needs to withstand the requirement of a reduced rate.
  • IP Internet Protocol
  • PDN Public Data Network
  • the backbone network is a network that forms the core connection of the Internet.
  • the user service data can flow from the user equipment (User Equipment, UE) to the carrier network, such as the core network (for example, EPS, or Circuit Switching, CS)) after the transmission network.
  • the backbone network aggregates a large number of data streams. Different from the QoS control according to the data flow in the EPS network, if the control is performed according to the granularity of the data flow, a large amount of resource overhead is required. Therefore, under the existing network architecture, the backbone network is deployed based on redundancy, and the network resources are considered to be It is sufficient.
  • the backbone network transmits the data flow of the corresponding QoS requirements into the pipeline (such as the GBR pipeline and the non-GBR pipeline) by establishing a pipe that satisfies different QoS.
  • an EPS bearer that meets the contracted QoS requirement is established according to the user and the service information.
  • the data stream is matched to the corresponding EPS bearer for transmission according to the IP quintuple of the data stream transmission and the receiver in the EPS system.
  • the data stream is sent out to the backbone network, it is aggregated to the same pipeline for transmission, and transmitted to the peer end or the corresponding service platform through the backbone network.
  • the IP quintuple based on the data stream can be matched to the established pipeline for transmission through static configuration.
  • the backbone network may be congested. Based on the existing transmission mode, the backbone network does not identify the specific data flow. Therefore, the user cannot guarantee the bandwidth traffic. For example, the traffic in the GBR cannot be guaranteed. This will result in end-to-end QoS for the service not being guaranteed.
  • SDN Software Defined Network
  • the embodiment of the invention provides a flow control method, device and system, which are used to ensure the bandwidth of the user to ensure bandwidth.
  • an embodiment of the present invention provides a method for flow control, including:
  • the network device adds the traffic control label to the traffic control label or increases the bandwidth traffic to the flow control label; and sends the data flow carrying the flow control label to the backbone network switching device; the backbone network switching device discards the excess according to the flow control label. Bandwidth traffic.
  • the network device may be a gateway or an eNodeB.
  • the network device before the network device increases the traffic exceeding the guaranteed bandwidth by adding the flow control label or increasing the traffic of the guaranteed bandwidth to the flow control label, the network device detects the received Guaranteed bandwidth traffic in the data stream and traffic exceeding the guaranteed bandwidth.
  • the increasing the traffic exceeding the guaranteed bandwidth by the flow control label comprises: exceeding the guaranteed bandwidth
  • the traffic is divided into at least two levels, and the corresponding flow control labels are respectively added.
  • the backbone network switching device discarding the traffic exceeding the guaranteed bandwidth according to the flow control label comprises: the backbone network switching device discarding the traffic exceeding the guaranteed bandwidth according to the flow control label and the congestion degree. In this way, the data stream can be finely controlled to use network resources more efficiently.
  • the backbone network switching device reports that the discarding exceeds the guaranteed bandwidth traffic
  • the event and the degree of congestion are given to the policy center, so that the policy center determines the user who needs to reduce the bandwidth according to the event, and the event carries the identifier of the discarded data flow exceeding the guaranteed bandwidth traffic.
  • the policy center can know the status of the backbone network in time and dynamically determine the users who need to reduce the bandwidth.
  • the network device receives an adjustment policy for reducing user bandwidth from the policy center; the network device sends the adjustment policy to The user, in order to reduce the bandwidth when the user sends a service.
  • the network device can know the bandwidth policy of the user in time, and feedback the policy to the user in time, so that the user can dynamically adjust the bandwidth of the sent data stream according to the congestion condition of the backbone network.
  • the adjusting the policy specifically includes: the service usage bandwidth of the user does not exceed the allowed bandwidth of the backbone network.
  • the backbone network switching device further discards the traffic of the guaranteed bandwidth.
  • the backbone network switching device After the backbone network switching device discards the traffic of the guaranteed bandwidth, it also reports the event of discarding the user's guaranteed bandwidth traffic to the policy center, so that the policy center determines the user's adjustment policy according to the event to remove the bearer corresponding to the bandwidth of the user; The event carries an identifier of the discarded data stream. In this way, the policy center can reversely adjust the user resources according to the processing of the traffic on the backbone network, so that the network resources can be more rationally utilized.
  • the network device receives a policy for removing a bearer corresponding to the guaranteed bandwidth of the user from the policy center; Corresponding bearer.
  • the detecting step further includes: the network device receiving the policy center
  • the delivered message is used to instruct the network device to detect guaranteed bandwidth traffic and traffic exceeding the guaranteed bandwidth in the data flow. In this way, the policy center can control whether the network device detects the guaranteed bandwidth traffic.
  • the backbone network switching device reports a congestion situation to the policy center.
  • the policy center can notify the network device to detect the guaranteed bandwidth traffic in the case of network congestion, thereby performing flow control.
  • the functionality of the network device is optimized.
  • an embodiment of the present invention provides another method for flow control, including:
  • the network device increases the traffic label exceeding the guaranteed bandwidth or increases the traffic of the guaranteed bandwidth to the flow control label
  • the data flow carrying the flow control label is sent to the backbone switching device, so that the backbone switching device discards the traffic exceeding the guaranteed bandwidth according to the flow control label.
  • an embodiment of the present invention provides another method for flow control, including:
  • the backbone network switching device receives the data flow carrying the flow control label sent by the network device, where the flow control label includes a flow control label carried in the traffic exceeding the guaranteed bandwidth, or a flow control label carried in the guaranteed bandwidth traffic;
  • the backbone network switching device discards traffic exceeding the guaranteed bandwidth according to the flow control label.
  • an embodiment of the present invention provides a network device that implements flow control, and the network device has a function of implementing network device behavior in the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the embodiment of the present invention provides a backbone network switching device that implements flow control, and the backbone network switching device has the function of implementing the behavior of the backbone network switching device in the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • an embodiment of the present invention provides a network device, where the network device includes a processor and a memory, where the memory is used to store application code that supports the network device to perform the foregoing method, where the processor is configured. Is used to execute an application stored in the memory.
  • the network device can also include a communication interface for the network device to communicate with other devices or communication networks.
  • an embodiment of the present invention provides a backbone network switching device, where the network device includes a processor and a memory, where the memory is used to store an application code that supports a backbone switching device to perform the foregoing method, where The processor is configured to execute an application stored in the memory.
  • the backbone network switching device may also include a communication interface for the network device to communicate with other devices or communication networks.
  • an embodiment of the present invention provides a computer storage medium, which is used for storing the foregoing network device.
  • Computer software instructions comprising a program designed to perform the above aspects for a network device.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for the backbone switching device, which includes a program designed to perform the foregoing aspects for a backbone switching device.
  • the tenth aspect of the present invention provides a system for implementing flow control, including the foregoing network device and a backbone network switching device. Further, the system may further include the above policy center.
  • the names of the network devices and the backbone network switching devices are not limited to the devices themselves. In actual implementation, these devices may appear under other names. As long as the functions of the respective devices are similar to the present invention, they are within the scope of the claims and the equivalents thereof.
  • the solution provided by the embodiment of the present invention can ensure that the bandwidth of the user is guaranteed.
  • FIG. 1 is a schematic diagram of a possible system according to an embodiment of the present invention.
  • FIG. 2 is a schematic diagram of a computer device according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a method for controlling flow according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a method for controlling flow according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a method for flow control according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a backbone network switching device according to an embodiment of the present invention.
  • the network architecture and the service scenario described in the embodiments of the present invention are used to more clearly illustrate the technical solutions of the embodiments of the present invention, and do not constitute a limitation of the technical solutions provided by the embodiments of the present invention.
  • the technical solutions provided by the embodiments of the present invention are equally applicable to similar technical problems.
  • FIG. 1 is a schematic diagram of a simple system provided by an embodiment of the present invention.
  • the network device 11 is included, and the network device 11 may have one or more in the system.
  • the network device 11 may be a gateway of a different carrier network (such as an EPS network, a CS network, etc.) for interworking between the carrier network and the backbone network; the network device 11 may also be an eNodeB (ie, an evolved Node B), of course. Not limited to these two devices.
  • the system also includes a backbone network and a backbone network switching device 12.
  • the data streams sent by different user terminals (UEs) are aggregated to the backbone network through different network devices 11, and transmitted in the backbone network, and transmitted to the peer end or corresponding through the backbone network. business platform.
  • the user equipment UE involved in the present application may include various handheld devices with wireless communication functions, in-vehicle devices, wearable devices, computing devices or other processing devices connected to the wireless modem, and various forms of user equipment (User Equipment) , UE), mobile station (MS), terminal, terminal equipment, soft terminal, and the like.
  • User Equipment User Equipment
  • UE User Equipment
  • MS mobile station
  • terminal terminal equipment
  • soft terminal soft terminal
  • the system may further include a policy center 13 that can control the transmission control of data flows in the carrier network (such as an EPS network, a CS network, etc.), and can also implement control of the backbone network transmission to achieve end-to-end (for example: Unified control of QoS from the sender of the data stream to the receiver of the data stream.
  • the policy center can be directly controlled or controlled by the SDN controller 14.
  • the SDN controller 14 can have one (SDN controller A) or multiple (SDN controller A and SDN controllers) in the system. B).
  • the policy center controls the network device 11 through the SDN controller A, and controls the backbone network switching device 12 through the SDN controller B.
  • the SDN controllers that control different network devices 11 can also be different SDN controllers.
  • the SDN controllers that control different network devices 11 and control backbone switching devices can also be the same SDN controller.
  • Figure 1 is just an example.
  • the guaranteed bandwidth traffic of the UE1 bearer is 4 Mbps, and the traffic exceeding the guaranteed bandwidth is 4 Mbps-6 Mbps; the guaranteed bandwidth traffic of the UE2 bearer is 2 Mbps, and the traffic exceeding the guaranteed bandwidth is 2 Mbps-3 Mbps; The guaranteed bandwidth traffic is 8 Mbps, and the traffic exceeding the guaranteed bandwidth is 8 Mbps - 10 Mbps.
  • the data flows of UE1, UE2, and UE3 are aggregated into the backbone network via gateway A, gateway B, and gateway C, respectively.
  • the data stream transmitted by the EPS network to the backbone network also transmits the traffic exceeding the guaranteed bandwidth when the traffic of the guaranteed bandwidth is satisfied.
  • the backbone network is congested after a large number of data streams of multiple gateways are aggregated. Since the backbone network does not recognize the specific data stream, it cannot distinguish between the bandwidth guaranteed traffic and the traffic exceeding the guaranteed bandwidth. After the traffic control (referred to as flow control), the backbone network may transmit the traffic exceeding the guaranteed bandwidth of UE2, and discard the traffic of the guaranteed bandwidth of UE3, thus causing the end of the data stream of UE3. End-to-end QoS cannot be guaranteed.
  • the traffic of the guaranteed bandwidth may be the traffic within the GBR; the traffic exceeding the guaranteed bandwidth may be the traffic between the GBR and the MBR.
  • the traffic of the guaranteed bandwidth and the traffic exceeding the guaranteed bandwidth may not be expressed as the traffic between the GBR and the traffic between the GBR and the MBR, and may be expressed in other manners, which is not limited herein.
  • the traffic in the guaranteed bandwidth is the traffic in the GBR; the traffic exceeding the guaranteed bandwidth is the traffic between the GBR and the MBR as an example.
  • the GBR and the MBR of the UE1 are 4 Mbps and 6 Mbps respectively; the GBR and MBR of the UE2 are 2 Mbps and 3 Mbps respectively; and the GBR and MBR of the UE3 are 8 Mbps and 10 Mbps, respectively.
  • the data flows of UE1, UE2, and UE3 are aggregated into the backbone network via gateway A, gateway B, and gateway C, respectively.
  • the EPS network resources are sufficient, the data flow transmitted by the EPS network to the backbone network also transmits the traffic between the GBR-MBRs when the traffic within the GBR is satisfied.
  • the backbone network is congested after a large number of data streams of multiple gateways are aggregated.
  • the backbone network cannot distinguish between GBR and MBR because it does not recognize specific data streams.
  • the traffic between the GBR and the MBR of the UE2 may be transmitted, and the traffic in the GBR of the UE3 may be discarded. As a result, the end-to-end QoS of the data stream of the UE3 cannot be obtained. Guarantee.
  • the EPS network cannot obtain the congestion of the backbone network, the EPS network cannot reduce the bandwidth by adjusting the bandwidth at the source end of the data stream (such as the sender of the transmitted data stream, which may be the UE or other senders). Congestion of the backbone network and avoiding the impact of data stream loss on service quality.
  • the method, device and system provided by the embodiments of the present invention can ensure the traffic of the data stream to ensure bandwidth (for example: within the GBR) Traffic).
  • the policy center can be determined by the backbone network switching device reporting the degree of congestion and reporting the event and congestion level exceeding the guaranteed bandwidth traffic, so that the policy center determines, according to the event, the user that needs to reduce the bandwidth, where the event is carried.
  • the identifier of the data flow that exceeds the guaranteed bandwidth traffic is discarded, and the adjustment policy for reducing the user bandwidth is sent to the network device, and the adjustment policy is sent to the user by the network device, so that the user reduces the bandwidth when sending the data flow. Therefore, bandwidth adjustment is performed at the source end of the data stream to reduce the congestion of the backbone network.
  • the network device such as a gateway, eNodeB, etc.
  • the backbone switching device in FIG. 1 can be implemented in the manner of the computer device (or system) in FIG. 2.
  • FIG. 2 is a schematic diagram of a computer device according to an embodiment of the present invention.
  • the computer device 200 includes at least one processor 201, a communication bus 202, a memory 203, and at least one communication interface 204.
  • the processor 201 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 202 can include a path for communicating information between the components described above.
  • the communication interface 204 uses devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), and the like.
  • RAN Radio Access Network
  • WLAN Wireless Local Area Networks
  • the memory 203 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 203 is used to store application code for executing the solution of the present invention, and is controlled by the processor 201 for execution.
  • the processor 201 is configured to execute application code stored in the memory 203.
  • processor 201 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • computer device 200 can include multiple processors, such as processor 201 and processor 208 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • computer device 200 may also include output device 202 and input device 206 as an embodiment.
  • Output device 205 is in communication with processor 201 and can display information in a variety of ways.
  • the output device 205 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector.
  • Input device 206 is in communication with processor 201 and can accept user input in a variety of ways.
  • input device 206 can be a mouse, keyboard, touch screen device or sensing device, and the like.
  • the computer device 200 described above can be a general purpose computer device or a special purpose computer device.
  • the computer device 200 can be a desktop computer, a portable computer, a network server, or a palmtop computer (Personal Digital Assistant, PDA), mobile handset, tablet, wireless terminal, communication device, embedded device or device with similar structure in Figure 2.
  • PDA Personal Digital Assistant
  • Embodiments of the invention do not limit the type of computer device 200.
  • the network device 11 in FIG. 1 may be the device shown in FIG. 2, and one or more software modules (for example, a first interaction module and a first execution module, etc.) are stored in the memory of the network device 11.
  • the backbone network switching device 12 of FIG. 1 may be the device shown in FIG. 2, and one or more software modules (for example, a second interaction module and a second execution module, etc.) are stored in the memory of the backbone network switching device 12.
  • the network device 11 or the backbone network switching device 12 can implement the flow control by implementing the software module through the processor and the program code in the memory.
  • the network device 11 is used as a gateway as an example for description.
  • FIG. 3 is a schematic flowchart diagram of a method for flow control according to an embodiment of the present invention.
  • the user equipment UE sends a data stream to the gateway.
  • the gateway receives the data stream.
  • the data stream is transmitted to the gateway through the EPS bearer.
  • the GBR of the UE corresponding to the EPS bearer is, for example, 4 Mbps
  • the MBR is, for example, 6 Mbps
  • the actual used bandwidth is 6 Mbps.
  • S303 The gateway increases the flow rate of the traffic exceeding the guaranteed bandwidth or increases the traffic of the guaranteed bandwidth by the flow control label.
  • the tag category can be GBRin or GBRout.
  • GBRin GBRin
  • GBRout GBRout
  • the traffic with the guaranteed bandwidth is the traffic of the GBR
  • the traffic exceeding the guaranteed bandwidth is the traffic between the GBR and the MBR.
  • adding a flow control label to a data stream may be as follows:
  • the first type can increase the traffic of the UE by more than 4 Mbps to the flow control label, and the traffic within 4 Mbps does not play the flow control label.
  • the traffic within 4 Mbps is added to the flow control tag, and the traffic exceeding 4 Mbps does not hit the flow control tag.
  • different flow control tags are added to traffic within 4 Mbps and traffic exceeding 4 Mbps.
  • the meaning of the flow control label and the label added by the gateway to the data stream may be pre-configured on the gateway, or may be delivered by other network elements (for example, a policy center).
  • the meaning of the label may be configured in the backbone network switching device in advance, or may be delivered by other network elements (for example, a policy center).
  • the first mode will be described as an example.
  • the gateway may also detect the guaranteed bandwidth traffic and the traffic exceeding the guaranteed bandwidth in the received data flow.
  • the gateway sends the data flow carrying the flow control label to the backbone switching device.
  • the backbone network switching device receives the data stream that is sent by the gateway and carries the flow control label.
  • the gateway sends the traffic to the backbone switching device within 4 Mbps without the flow control label, and the traffic with the flow control label exceeding 4 Mbps (ie: 4 Mbps). Traffic to 6Mbps).
  • the backbone network switching device discards the traffic exceeding the guaranteed bandwidth according to the flow control label.
  • the backbone network switching device determines the traffic exceeding the guaranteed bandwidth according to the flow control label carried in the data flow of the UE, discards the traffic exceeding the guaranteed bandwidth, and reserves the traffic of the guaranteed bandwidth. Specifically, in the first manner of adding a flow control label, the backbone switching device discards the traffic carrying the flow control label of the UE, that is, the traffic exceeding the GBR from 4 Mbps to 6 Mbps; and retaining the GBR of the UE without the flow control label The traffic within, that is, the traffic within 4Mbps.
  • the backbone network switching device after the data stream of the UE is transmitted to the backbone network, the backbone network switching device according to the set congestion threshold (may It is determined that the backbone network is congested by pre-configuration on the backbone network or by the policy center. Therefore, the flow of data flowing through the backbone network needs to be controlled.
  • the flow control here includes discarding traffic exceeding the guaranteed bandwidth, and may further include discarding the traffic of the guaranteed bandwidth.
  • the congestion threshold here can be the pipe usage threshold.
  • a flow control processing policy may be configured in advance in a backbone network switching device, or a flow control processing policy may be sent to a backbone network switching device by another device.
  • the flow control processing policy may be: when the backbone network is congested, the backbone network switching device discards the traffic exceeding the guaranteed bandwidth.
  • the actions of the above gateway may be performed by the gateway in accordance with the software modules in the memory mentioned above.
  • the actions of the gateways in S301 and S305 can be performed according to the first interaction module in FIG. 2.
  • the action of the gateway in S303 can be performed according to the first execution module in FIG. 2.
  • the actions of the backbone switching device described above may be performed by the backbone switching device in accordance with the software modules in the memory mentioned above.
  • the action of the backbone switching device in S305 can be performed according to the second interaction module in FIG. 2.
  • the action of the backbone switching device in S307 can be performed according to the second execution module in FIG.
  • the traffic in the data stream GBR can be ensured, for example, in the case where the backbone network is congested. Avoid discarding traffic within certain traffic streams GBR while preserving traffic that exceeds GBR for certain traffic.
  • the gateway increases the traffic exceeding the guaranteed bandwidth by the flow control label, and specifically, the traffic exceeding the guaranteed bandwidth is divided into two levels or more, Add the corresponding flow control label to each level.
  • the gateway and the backbone network switching device may pre-configure the level corresponding to the flow control label; or the other network element may send the level corresponding to the flow control label to the gateway and the backbone network switching device; or the gateway may also increase the flow. After the label is controlled, it is negotiated with the backbone switching device.
  • the specific method is not limited here.
  • the backbone network switching device discards traffic exceeding the guaranteed bandwidth according to the congestion degree of the backbone network and the flow control label, or hierarchical flow control.
  • the gateway can classify the traffic between 4 Mbps and 6 Mbps, for example, divide the traffic between 4 Mbps and 5 Mbps into the first level, increase the flow control label A; and divide the traffic between 5 Mbps and 6 Mbps into the second level. Increase the flow control label B.
  • the tag category field and the tag index field may be added in the metadata of the data stream.
  • the label category may be GBRout; the label index may be a data identifier, such as A or B, where A represents a traffic between 4 Mbps and 5 Mbps, and B represents a traffic between 5 Mbps and 6 Mbps.
  • A represents a traffic between 4 Mbps and 5 Mbps
  • B represents a traffic between 5 Mbps and 6 Mbps.
  • A represents a traffic between 4 Mbps and 5 Mbps
  • B represents a traffic between 5 Mbps and 6 Mbps
  • the backbone network switching device controls the traffic according to the corresponding relationship between the pipeline usage threshold and the flow control label that reflect the congestion degree of the backbone network. For example, when the pipeline usage rate is 60%, the flow control label is discarded as B traffic; when the pipeline usage rate is 80%, the flow control label is discarded as the traffic of A, and so on.
  • 60% or 80% is just an example, the specific value can be set as needed.
  • the pipeline expansion process can be started to increase the bandwidth resource corresponding to the pipeline. If the capacity expansion fails or the capacity expansion succeeds, the traffic without the flow control identifier (the traffic within the GBR) can be discarded. It is also possible to continue to discard the traffic without the flow control identifier when the traffic with the flow control identifier is still not able to make the pipeline usage lower than the set maximum threshold.
  • the gateway may further receive the cancellation sent by the policy center.
  • the message is used to instruct the gateway to detect the guaranteed bandwidth traffic in the data stream and the traffic exceeding the guaranteed bandwidth, and add a label, and then the gateway performs step S303.
  • the policy center sends the message to the gateway because the policy center receives the event that the backbone switching device reports congestion. In this way, the policy center can notify the gateway to detect the guaranteed bandwidth traffic when the network is congested, thereby performing flow control, thereby reducing the burden on the gateway and optimizing the functions of the gateway and the entire system.
  • the action of the gateway may be performed according to the first interaction module in FIG. 2.
  • FIG. 4 is a schematic flowchart diagram of another method for flow control according to an embodiment of the present invention.
  • the traffic of the backbone network switching device discarding the traffic exceeding the guaranteed bandwidth is taken as an example in the flow control mode.
  • the policy center may send a flow control processing policy to the backbone network switching device.
  • the flow control processing strategy includes the congestion degree of the backbone network and the corresponding processing manner.
  • the congestion degree of the backbone network can be represented by the pipeline usage rate of the backbone network; the corresponding processing manner can be represented by the excess guaranteed bandwidth traffic of the discarded user, or by a certain percentage of the discarded user exceeding the guaranteed bandwidth traffic.
  • the congestion degree of the backbone network can be represented by the pipeline usage rate of the backbone network; the corresponding processing manner can be represented by the excess guaranteed bandwidth traffic of the discarded user, or by a certain percentage of the discarded user exceeding the guaranteed bandwidth traffic.
  • the backbone network switching device reports the event that exceeds the guaranteed bandwidth traffic and the congestion degree of the backbone network to the policy center.
  • the policy center receives the event that the backbone switching device reports the discarding of excess bandwidth traffic and the congestion of the backbone network.
  • the event includes an identifier of the discarded data stream that exceeds the guaranteed bandwidth.
  • the policy center controls the backbone network switching device through the SDN controller, the backbone network switching device needs to discard the event exceeding the guaranteed bandwidth traffic and the backbone network congestion degree through the SDN controller. Give the strategy center.
  • the event that exceeds the guaranteed bandwidth traffic and the congestion degree of the backbone network are reported to the policy center without going through the SDN controller.
  • the policy center determines an adjustment policy according to the event that the discarding exceeds the guaranteed bandwidth traffic.
  • the policy center may determine an adjustment policy of the corresponding user according to the identifier of the discarded data flow that exceeds the guaranteed bandwidth included in the event, that is, reduce the bandwidth of the user (such as lowering the MBR).
  • the policy center can dynamically determine the users who need to reduce the bandwidth in order to adjust the bandwidth of the user.
  • the policy center sends an adjustment policy for reducing user bandwidth to the gateway.
  • the gateway receives the adjustment policy of reducing user bandwidth sent by the policy center.
  • the adjustment strategy is as follows: the bandwidth used by the user does not exceed the bandwidth allowed by the backbone network.
  • the gateway sends the adjustment policy to the user, so that the user reduces the bandwidth when sending the data stream.
  • the gateway can know the bandwidth policy of the user in time, and feedback the policy to the user in time, so that the user equipment can dynamically adjust the bandwidth of the sent data stream according to the congestion of the backbone network.
  • the actions of the backbone switching device described above may be performed by the backbone switching device in accordance with the software modules in the memory mentioned above.
  • the action of the backbone switching device in S409 can be performed according to the second interaction module in FIG. 2.
  • the actions of the above gateway may be performed by the gateway in accordance with the software modules in the memory mentioned above.
  • the actions of the gateways in S413 and S415 can be performed in accordance with the first interaction module in FIG.
  • FIG. 5 is a schematic flowchart diagram of another method for flow control according to an embodiment of the present invention.
  • the flow of the guaranteed bandwidth is discarded by the backbone switching device in the flow control mode.
  • S509 The backbone network switching device reports the event of discarding the guaranteed bandwidth of the user to the policy center.
  • Strategy center An event that receives the traffic of the guaranteed bandwidth of the discarded user reported by the backbone switching device.
  • the event carries an identifier of the discarded data stream.
  • the policy center controls the backbone network switching device through the SDN controller, the backbone network switching device needs to discard the event exceeding the guaranteed bandwidth traffic and the backbone network congestion degree through the SDN controller. Give the strategy center.
  • the backbone switching device reports the event that exceeds the guaranteed bandwidth traffic and the congestion degree of the backbone network to the policy center without passing through the SDN controller.
  • the policy center determines, according to the event that the traffic of the user's guaranteed bandwidth is discarded, that the user's adjustment policy is to remove the bearer corresponding to the guaranteed bandwidth of the user (here, the bearer corresponding to the guaranteed bandwidth is a GBR bearer).
  • the policy center may determine an adjustment policy of the corresponding user according to the identifier of the data flow included in the event.
  • the policy center sends an adjustment policy to the gateway.
  • the gateway receives the adjustment policy sent by the policy center.
  • the gateway removes the GBR bearer of the user.
  • the gateway removes the GBR bearer from the user, and the gateway receives the indication of the bearer that is sent by the policy center, and initiates the deletion of the bearer request corresponding to the GBR to remove (or delete) the GBR bearer.
  • the bearer request may be sent to the eNodeB and the UE used by the user via a Serving Gateway (SGW) to a Mobility Management Entity (MME).
  • SGW Serving Gateway
  • MME Mobility Management Entity
  • the backbone network switching device discards the guaranteed bandwidth traffic and the S509-S515 can be implemented in combination with the flow control method of FIG. That is to say, after the traffic exceeding the guaranteed bandwidth is discarded as shown in FIG. 4, the traffic of the guaranteed bandwidth can continue to be discarded. For example, after the traffic that exceeds the guaranteed bandwidth is discarded and the backbone network is still congested, the traffic with guaranteed bandwidth can continue to be discarded.
  • the actions of the backbone switching device described above may be performed by the backbone switching device in accordance with the software modules in the memory mentioned above.
  • the action of the backbone switching device in S509 can be performed according to the second interaction module in FIG. 2.
  • the actions of the above gateway may be performed by the gateway in accordance with the software modules in the memory mentioned above.
  • the actions of the gateways in S513 and S515 can be performed in accordance with the first interaction module of FIG.
  • the embodiment of the present invention further provides a schematic structural diagram of a network device.
  • the network device 600 includes an add label unit 601 and a sending unit 603.
  • the labeling unit 601 is configured to: add a traffic label that exceeds the guaranteed bandwidth to the flow control label or increase the bandwidth traffic to the flow control label;
  • the sending unit 603 is configured to send the data stream that carries the flow control label to the backbone network switching device.
  • the backbone switching device discards traffic exceeding the guaranteed bandwidth according to the flow control label.
  • the detecting unit 605 is further configured to detect the guaranteed bandwidth of the received data stream and the traffic exceeding the guaranteed bandwidth.
  • network device 600 is presented in the form of a functional unit.
  • a "unit” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • the detecting unit 605, the adding label unit 601 and the sending unit 603 can be implemented by the processor and the memory of FIG. 2.
  • the sending unit 603 can be implemented by executing a first interaction module by the processor, the detecting unit 605 and adding a label.
  • Unit 603 can be implemented by executing a first execution module by a processor.
  • the embodiment of the present invention further provides a schematic structural diagram of a backbone network switching device.
  • the changing device 700 includes a receiving unit 701 and a flow control unit 703.
  • the receiving unit 701 is configured to receive a data flow that is sent by the network device and that carries the flow control label.
  • the flow control label includes a flow control label that is carried in a traffic exceeding the guaranteed bandwidth, or a flow that is carried in the guaranteed bandwidth traffic.
  • the control label 703 is configured to discard the traffic exceeding the guaranteed bandwidth according to the flow control label.
  • the backbone switching device 700 is presented in the form of a functional unit.
  • a "unit” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • the backbone switching device 700 can take the form shown in FIG.
  • the receiving unit 701 and the flow control unit 703 can be implemented by the processor and the memory of FIG. 2. Specifically, the receiving unit 701 can be implemented by executing a second interaction module by the processor, and the flow control unit 703 can be configured by the processor. Implement the second execution module to implement.
  • the embodiment of the present invention further provides a computer storage medium for storing the computer software instructions used by the network device shown in FIG. 6 or the backbone network switching device shown in FIG. 7, which includes an embodiment for performing the foregoing method.
  • embodiments of the present invention can be provided as a method, apparatus (device), or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program is stored/distributed in a suitable medium, provided with other hardware or as part of the hardware, or in other distributed forms, such as over the Internet or other wired or wireless telecommunication systems.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions are provided for implementing one or more processes and/or block diagrams in the flowchart The steps of the function specified in the box or in multiple boxes.

Abstract

本发明实施例提供了一种流量控制方法，网络设备将超过保证带宽的流量增加流控标签或将保证带宽的流量增加流控标签；将携带流控标签的数据流发送给骨干网交换设备；所述骨干网交换设备根据所述流控标签丢弃超过保证带宽的流量。通过上述方案，使用户保证带宽的流量得到了保证。

Description

一种流量控制方法、装置和系统
本申请要求于2016年2月29日提交中国专利局、申请号为201610112450.9、发明名称为“一种流量控制方法、装置和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，尤其涉及一种流量控制方法、装置和系统。
背景技术
在演进分组系统(Evolved Packet System，EPS)中，服务质量(Quality of Service，QoS)控制的基本粒度是EPS承载。相同承载上的所有数据流将获得相同的QoS保障，不同的QoS保障需要不同的EPS承载来提供。根据QoS的不同，EPS承载可以划分为两大类：保证比特速率(Guaranteed Bit Rate，GBR)承载和非保证比特速率(Non-Guaranteed Bit Rate，Non-GBR)承载。
GBR承载主要用于语音、视频、实时游戏等业务，采用专用承载的方式进行承载。参数GBR代表了预期能够由GBR承载提供的比特速率；参数最大比特速率(Maximum Bit Rate，MBR)则限制了GBR承载能提供的比特速率，它表示了GBR承载提供期望数据速率的上限。MBR必须大于等于GBR。在资源紧张的情况下，超过GBR的流量会被丢弃，但GBR内的流量需要保证。
Non-GBR承载则主要用于各种数据业务的承载。Non-GBR承载可简单地理解为一种提供尽力而为网络之间互连的协议(Internet Protocol，IP)连接的承载，随着公用数据网(Public Data Network，PDN)链接的建立而建立，随着PDN的链接的拆除而销毁。在网络拥塞的情况下，Non-GBR业务(或承载)需要承受降低速率的要求。
骨干网(Backbone Network)是构成互联网核心连接的一个网络，可以是用户业务数据从用户设备(User Equipment，UE)流出运营商网络，比如核心网(比如可以是EPS，或电路交换(Circuit Switching，CS))后的传输网络。骨干网汇聚了大量的数据流。与EPS网络中按数据流来进行QoS控制不同，如果按数据流的粒度来进行控制需要增加大量的资源开销，因此在现有网络架构下，骨干网是基于冗余部署的，认为网络资源都是够用的，骨干网通过建立满足不同QoS的管道(Pipe)，把相应QoS需求的数据流放入管道(如建立GBR的管道和非GBR的管道)中进行传输。
当UE接入网络时，根据用户和业务信息建立满足签约QoS要求的EPS承载。UE进行业务时，在EPS系统中根据数据流的发送和接收方的IP五元组，将数据流匹配到对应的EPS承载中进行传输。数据流在出EPS网络后到骨干网后汇聚到同一个管道进行传输，经骨干网传输到对端或者对应的业务平台。在骨干网中可以通过静态配置，基于数据流的IP五元组匹配到建立的管道中进行传输。通过上述方式，可以实现从EPS网络到骨干网整个业务流程满足QoS需求的控制。
在5G网络，随着终端用户数和业务量的增加，同时基于件定义网络(Software Defined  Network，SDN)架构对网络的控制，对网络资源利用率也提出更高的要求。骨干网在汇聚了大量业务后，将可能出现拥塞情况，而基于现有的传输方式，骨干网不识别具体的数据流，因此也无法保证用户保证带宽的流量，例如无法保证GBR内的流量。这样将导致业务的端到端QoS无法得到保障。
发明内容
本发明实施例提供一种流量控制方法、装置及系统，用以保证用户保证带宽的流量。
第一方面，本发明实施例提供了一种流量控制的方法，包括：
网络设备将超过保证带宽的流量增加流控标签或将保证带宽流量增加流控标签；将携带流控标签的数据流发送给骨干网交换设备；所述骨干网交换设备根据流控标签丢弃超过保证带宽的流量。
通过该方法，可以保证用户保证带宽的流量，避免丢弃某些保证带宽的流量，而保留了某些超过保证带宽的流量。比如：避免丢弃某些数据流GBR内的流量而保留了某些数据流超过GBR的流量。
比如，在骨干网拥塞情况下，可以保证用户保证带宽的流量。其中，网络设备可以为网关，也可以为eNodeB。
结合第一方面，在第一方面的第一种可能的实现方式中，所述网络设备将超过保证带宽的流量增加流控标签或将保证带宽的流量增加流控标签之前，网络设备检测接收的数据流中的保证带宽的流量和超过保证带宽的流量。
结合第一方面或第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，所述将超过保证带宽的流量增加流控标签具体包括：将超过保证带宽的流量分成至少两级，分别增加相应的流控标签。相应的，所述骨干网交换设备根据流控标签丢弃超过保证带宽的流量具体包括：所述骨干网交换设备根据流控标签和拥塞程度分级丢弃超过保证带宽的流量。这样，可以对数据流进行精细化控制，更有效的使用网络资源。
结合第一方面或第一方面的第一种至第二种任一可能的实现方式，在第一方面的第三种可能的实现方式中，所述骨干网交换设备上报丢弃超过保证带宽流量的事件和拥塞程度给策略中心，以使策略中心根据所述事件确定需要降低带宽的用户，所述事件中携带丢弃的超过保证带宽流量的数据流的标识。这样，策略中心可以及时的获知骨干网的状态，动态确定需要降低带宽的用户。
结合第一方面的第三种可能的实现方式，在第一方面的第四种可能的实现方式中，网络设备接收来自策略中心的降低用户带宽的调整策略；网络设备将所述调整策略发给所述用户，以使用户发送业务时降低带宽。这样，网络设备可以及时的获知用户的带宽策略，并将策略及时的反馈给用户，以使用户可以根据骨干网的拥塞情况动态调整发送数据流的带宽。
结合第一方面的第四种可能的实现方式，在第一方面的第五种可能的实现方式中，所述调整策略具体包括：用户的业务使用带宽不超过骨干网允许带宽。
结合第一方面或第一方面的第一种至第五种任一可能的实现方式，在第一方面的第六种可能的实现方式中，所述骨干网交换设备还丢弃保证带宽的流量。
结合第一方面的第六种可能的实现方式，在第一方面的第七种可能的实现方式中，所 述骨干网交换设备丢弃保证带宽的流量后，还上报丢弃用户的保证带宽的流量的事件给策略中心，以使策略中心根据所述事件确定用户的调整策略为拆除用户保证带宽对应的承载；其中，所述事件中携带丢弃的数据流的标识。这样，策略中心可以根据骨干网对流量的处理情况来反向调整用户的资源，使网络资源得到更合理的利用。
结合第一方面的第七种可能的实现方式，在第一方面的第八种可能的实现方式中，网络设备接收来自策略中心的拆除用户保证带宽对应的承载的策略；网络设备拆除用户保证带宽对应的承载。
结合第一方面或第一方面的第一种至第八种任一可能的实现方式，在第一方面的第九种可能的实现方式中，所述检测步骤之前进一步包括：网络设备接收策略中心下发的消息，所述消息用于指示网络设备检测所述数据流中的保证带宽流量和超过保证带宽的流量。这样，策略中心可以对网络设备是否来检测保证带宽的流量进行控制。
结合第一方面的第九种可能的实现方式，在第一方面的第十种可能的实现方式中，当所述骨干网出现拥塞的情况下，骨干网交换设备上报拥塞情况给策略中心。这样，可以使策略中心在网络拥塞的情况下，再通知网络设备来检测保证带宽的流量，以此进行流控。网络设备的功能得到了优化。
第二方面，本发明实施例提供了另一种流量控制的方法，包括：
网络设备将超过保证带宽的流量增加流控标签或将保证带宽的流量增加流控标签；
将携带流控标签的数据流发送给骨干网交换设备，以使骨干网交换设备根据流控标签丢弃超过保证带宽的流量。
第三方面，本发明实施例提供了另一种流量控制的方法，包括：
骨干网交换设备接收网络设备发送的携带流控标签的数据流；其中，所述流控标签包括携带在超过保证带宽流量中的流控标签，或携带在保证带宽流量中的流控标签；
所述骨干网交换设备根据所述流控标签丢弃超过保证带宽的流量。
第四方面，本发明实施例提供了一种实现流量控制的网络设备，该网络设备具有实现上述方法中实现网络设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
第五方面，本发明实施例提供了一种实现流量控制的骨干网交换设备，该骨干网交换设备具有实现上述方法中实现骨干网交换设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
第六方面，本发明实施例提供了一种网络设备，该网络设备的结构中包括处理器和存储器，所述存储器用于存储支持网络设备执行上述方法的应用程序代码，所述处理器被配置为用于执行所述存储器中存储的应用程序。所述网络设备还可以包括通信接口，用于网络设备与其他设备或通信网络通信。
第七方面，本发明实施例提供了一种骨干网交换设备，该网络设备的结构中包括处理器和存储器，所述存储器用于存储支持骨干网交换设备执行上述方法的应用程序代码，所述处理器被配置为用于执行所述存储器中存储的应用程序。所述骨干网交换设备还可以包括通信接口，用于网络设备与其他设备或通信网络通信。
第八方面，本发明实施例提供了一种计算机存储介质，用于储存为上述网络设备所用 的计算机软件指令，其包含用于执行上述方面为网络设备所设计的程序。
第九方面，本发明实施例提供了一种计算机存储介质，用于储存为上述骨干网交换设备所用的计算机软件指令，其包含用于执行上述方面为骨干网交换设备所设计的程序。
第十方面，本发明实施例提供了一种实现流量控制的系统，包括上述的网络设备和骨干网交换设备。进一步的，该系统还可以包括上述策略中心。
本发明中，网络设备和骨干网交换设备的名字对设备本身不构成限定，在实际实现中，这些设备可以以其他名称出现。只要各个设备的功能和本发明类似，属于本发明权利要求及其等同技术的范围之内。
相较于现有技术，本发明实施例提供的方案可以使用户保证带宽的流量得到保证。
本发明的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简要介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域的普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1所示为本发明实施例的一种可能的系统示意图；
图2所示为本发明实施例提供的计算机设备示意图；
图3所示为本发明实施例提供的流量控制的方法流程示意图；
图4所示为本发明实施例提供的流量控制的方法流程示意图；
图5所示为本发明实施例提供的流量控制的方法流程示意图；
图6所示为本发明实施例提供的网络设备的结构示意图；
图7所示为本发明实施例提供的骨干网交换设备的结构示意图。
具体实施方式
为了使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明作进一步地详细描述。而且，方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。
本发明实施例描述的网络架构以及业务场景是为了更加清楚的说明本发明实施例的技术方案，并不构成对于本发明实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本发明实施例提供的技术方案对于类似的技术问题，同样适用。
如图1所示，是本发明实施例提供的一种简单的系统示意图。该系统中，包括网络设备11，网络设备11在系统中可以有一个，也可以有多个。网络设备11可以为不同运营商网络(比如EPS网络，CS网络等)的网关，用于实现运营商网络到骨干网的互通；网络设备11也可以为eNodeB(即：演进型Node B)，当然也不限于这两种设备。
该系统还包括骨干网以及骨干网交换设备12。不同用户终端(UE)发送的数据流经过不同的网络设备11汇聚到骨干网，在骨干网中进行传输，经骨干网传输到对端或者对应的 业务平台。
本申请所涉及到的用户设备UE可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的用户设备(User Equipment，UE)，移动台(Mobile station，MS)，终端(terminal)，终端设备(Terminal Equipment)，软终端等等。为方便描述，本申请中，上面提到的设备统称为用户设备或UE。
该系统还可以包括策略中心13，策略中心13可以控制运营商网络(比如EPS网络，CS网络等)中数据流的传输控制，还可以实现对骨干网传输的控制，实现端到端(比如：数据流发送方到数据流接收方)QoS的统一控制。策略中心可以直接进行控制，也可以通过SDN控制器14来进行控制，SDN控制器14在系统中可以有1个(SDN控制器A)，也可以有多个(SDN控制器A和SDN控制器B)。比如，策略中心通过SDN控制器A对网络设备11进行控制，通过SDN控制器B对骨干网交换设备12进行控制。当然控制不同网络设备11的SDN控制器也可以为不同的SDN控制器，控制不同网络设备11和控制骨干网交换设备的SDN控制器也可以为相同的SDN控制器。图1只是一个示例。
如图1所示，比如UE1对应承载的保证带宽流量为4Mbps，超过保证带宽的流量为4Mbps-6Mbps；UE2对应承载的保证带宽流量为2Mbps，超过保证带宽的流量为2Mbps-3Mbps；UE3对应承载的保证带宽流量为8Mbps，超过保证带宽的流量为8Mbps-10Mbps。UE1，UE2和UE3的数据流分别经由网关A，网关B和网关C汇聚到骨干网中。在EPS网络资源充足的情况下，EPS网络传送到骨干网的数据流在满足即保证带宽的流量时，也传送了超过保证带宽的流量。而骨干网在汇聚了多个网关的大量数据流后出现了拥塞，骨干网由于不识别具体的数据流，也就无法区分保证带宽的流量和超过保证带宽的流量。骨干网在进行流量控制(简称：流控)后，可能存在把UE2的超过保证带宽的流量进行了传输，而把UE3的保证带宽的流量进行了丢弃的情况，这样导致UE3的数据流的端到端QoS无法得到保障。
在具体实现中，保证带宽的流量可以为GBR内的流量；超过保证带宽的流量可以为GBR-MBR间的流量。当然，保证带宽的流量和超过保证带宽的流量也可以不是表现为GBR内的流量和GBR-MBR间的流量，可以是以其他方式来表现，这里不做限定。
下面以保证带宽的流量为GBR内的流量；超过保证带宽的流量为GBR-MBR间的流量为例来说明。比如UE1对应承载的GBR和MBR分别为4Mbps和6Mbps；UE2对应承载的GBR和MBR分别为2Mbps和3Mbps；UE3对应承载的GBR和MBR分别为8Mbps和10Mbps。UE1，UE2和UE3的数据流分别经由网关A，网关B和网关C汇聚到骨干网中。在EPS网络资源充足的情况下，EPS网络传送到骨干网的数据流在满足GBR内的流量时，也传送了GBR-MBR间的流量。而骨干网在汇聚了多个网关的大量数据流后出现了拥塞，骨干网由于不识别具体的数据流，也就无法区分GBR和MBR。骨干网在进行流量控制后，可能存在把UE2的GBR-MBR间的流量进行了传输，而把UE3的GBR内的流量进行了丢弃的情况，这样导致UE3的数据流的端到端QoS无法得到保障。
进一步的，由于EPS网络无法获取到骨干网的拥塞情况，EPS网络无法通过在数据流的源端(比如发送数据流的发送方，可以是UE，也可以是其他发送方)进行带宽调节来降低骨干网的拥塞情况，并避免数据流的丢失对业务质量的影响。
本发明实施例提供的方法、装置和系统可以保证数据流保证带宽的流量(比如：GBR内 的流量)。进一步，还可以通过由骨干网交换设备上报自身拥塞程度以及上报丢弃超过保证带宽流量的事件和拥塞程度给策略中心，以使策略中心根据所述事件确定需要降低带宽的用户，所述事件中携带丢弃的超过保证带宽流量的数据流的标识，并将降低用户带宽的调整策略下发给网络设备，通过网络设备将所述调整策略发送给所述用户，以使用户发送数据流时降低带宽。从而，在数据流的源端进行带宽调节来降低骨干网的拥塞情况。
如图2所示，图1中的网络设备(比如网关，eNodeB等)和骨干网交换设备可以以图2中的计算机设备(或系统)的方式来实现。
图2所示为本发明实施例提供的计算机设备示意图。计算机设备200包括至少一个处理器201，通信总线202，存储器203以及至少一个通信接口204。
处理器201可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线202可包括一通路，在上述组件之间传送信息。所述通信接口204，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(RAN)，无线局域网(Wireless Local Area Networks，WLAN)等。
存储器203可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，所述存储器203用于存储执行本发明方案的应用程序代码，并由处理器201来控制执行。所述处理器201用于执行所述存储器203中存储的应用程序代码。
在具体实现中，作为一种实施例，处理器201可以包括一个或多个CPU，例如图2中的CPU0和CPU1。
在具体实现中，作为一种实施例，计算机设备200可以包括多个处理器，例如图2中的处理器201和处理器208。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，计算机设备200还可以包括输出设备202和输入设备206。输出设备205和处理器201通信，可以以多种方式来显示信息。例如，输出设备205可以是液晶显示器(liquid crystal display，LCD)，发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备206和处理器201通信，可以以多种方式接受用户的输入。例如，输入设备206可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的计算机设备200可以是一个通用计算机设备或者是一个专用计算机设备。在具体实现中，计算机设备200可以是台式机、便携式电脑、网络服务器、掌上电脑(Personal  Digital Assistant，PDA)、移动手机、平板电脑、无线终端设备、通信设备、嵌入式设备或有图2中类似结构的设备。本发明实施例不限定计算机设备200的类型。
如图1中的网络设备11可以为图2所示的设备，网络设备11的存储器中存储了一个或多个软件模块(例如：第一交互模块和第一执行模块等)。如图1的骨干网交换设备12可以为图2所示的设备，骨干网交换设备12的存储器中存储了一个或多个软件模块(例如：第二交互模块和第二执行模块等)。网络设备11或骨干网交换设备12可以通过处理器以及存储器中的程序代码来实现软件模块，实现流量控制。
下面的实施例中，以网络设备11为网关为例来进行说明。
如图3所示，为本发明实施例提供的一种流量控制的方法流程示意图。
S301，用户设备UE发送数据流给网关。网关接收数据流。
其中，数据流经过EPS承载传输到网关。UE对应EPS承载的GBR比如为4Mbps，MBR比如为6Mbps，实际使用带宽为6Mbps。
S303，网关将超过保证带宽的流量增加流控标签或将保证带宽的流量增加流控标签。
在具体实现中，增加流控标签的方式有多种。比如，可以在数据流的metadata中增加字段：标签类别。标签类别可以为GBRin or GBRout。当然也可以采用其他手段，这里不做限定。
本实施例中，以保证带宽的流量为GBR的流量，超过保证带宽的流量为GBR-MBR间的流量为例来进行说明。
具体实现中，给数据流增加流控标签可以有如下几种方式：
第一种，可以将UE的超过4Mbps的流量增加流控标签，4Mbps内的流量不打流控标签。第二种，将4Mbps内的流量增加流控标签，超过4Mbps的流量不打流控标签。第三种，将4Mbps内的流量和超过4Mbps的流量增加不同的流控标签。
在具体实现中，网关对数据流增加流控标签以及标签的意义可以在网关上预先配置，也可以由其他网元(比如：策略中心)来下发。另外，还可以预先在骨干网交换设备配置标签的意义，也可以由其他网元(比如：策略中心)来下发。
本实施例中，以第一种方式为例来进行说明。
在具体实现中，网关将超过保证带宽的流量增加流控标签或将保证带宽的流量增加流控标签之前，还可以检测接收的数据流中的保证带宽的流量和超过保证带宽的流量。
S305，网关将携带流控标签的数据流发送给骨干网交换设备。骨干网交换设备接收网关发送的携带流控标签的数据流。
具体到本实施例中UE的GBR为4Mbps这个例子来说，网关发送给骨干网交换设备的是不带流控标签的4Mbps内的流量，和带流控标签的超过4Mbps的流量(即：4Mbps到6Mbps间的流量)。
S307，骨干网交换设备根据流控标签丢弃超过保证带宽的流量。
具体来说，骨干网交换设备根据UE的数据流中携带的流控标签确定超过保证带宽的流量，丢弃超过保证带宽的流量，保留保证带宽的流量。具体到第一种增加流控标签的方式来说，骨干网交换设备丢弃UE的携带流控标签的流量，即超过GBR的从4Mbps到6Mbps间的流量；保留UE的不带流控标签的GBR内的流量，即4Mbps内的流量。
具体实现中，在UE的数据流传输到骨干网后，骨干网交换设备根据设置的拥塞阈值(可 以在骨干网预配置，也可以由策略中心下发)确定骨干网发生了拥塞，因此需要对流经骨干网的数据流进行流控。这里的流控包括丢弃超过保证带宽的流量，进一步还可以包括丢弃保证带宽的流量。这里的拥塞阈值可以是管道使用率阈值。
具体实现中，作为一种实施例，骨干网交换设备中可以预先配置流控处理策略，也可以由其他设备下发流控处理策略给骨干网交换设备。该流控处理策略可以为：骨干网发生拥塞的情况下，骨干网交换设备丢弃超过保证带宽的流量。
上述网关的动作可以由网关根据上述提及的存储器中的软件模块来执行。例如，S301和S305中网关的动作可以根据图2中的第一交互模块来执行。S303中网关的动作可以根据图2中的第一执行模块来执行。
上述骨干网交换设备的动作可以由骨干网交换设备根据上述提及的存储器中的软件模块来执行。例如，S305中骨干网交换设备的动作可以根据图2中第二交互模块来执行。S307中骨干网交换设备的动作可以根据图2中第二执行模块来执行。
通过上述方法，可以保证数据流GBR内的流量，比如在骨干网出现拥塞的情况下。避免丢弃某些数据流GBR内的流量而保留了某些数据流超过GBR的流量。
在具体实现中，作为一种实施例，在上述方法中，在S303中，网关将超过保证带宽的流量增加流控标签，具体可以是：将超过保证带宽的流量分成两级或两级以上，将每一级增加相应的流控标签。
具体实现中，网关和骨干网交换设备可以预先配置流控标签对应的级别；也可以由其他网元将流控标签对应的级别下发给网关和骨干网交换设备；或者，网关也可以增加流控标签后，再和骨干网交换设备进行协商。具体方法这里不做限定。
相应的，所述骨干网交换设备根据骨干网拥塞程度和流控标签分级丢弃超过保证带宽的流量，或者说分级流控。
关于分级丢弃超过保证带宽的流量，下面以UE对应EPS承载的GBR为4Mbps，MBR为6Mbps，并且将超过GBR的流量分成两级为例来介绍。具体的，网关可以将4Mbps-6Mbps之间的流量分级，比如将4Mbps-5Mbps之间的流量分为第一级，增加流控标签A；将5Mbps-6Mbps之间的流量分为第二级，增加流控标签B。关于流控标签，具体实现中，可以在数据流的metadata中增加标签类别字段和标签索引字段。其中，标签类别可以为GBRout；标签索引可以为数据标识，比如A或B，其中A代表4Mbps-5Mbps之间的流量，B代表5Mbps-6Mbps之间的流量。当然，也可以采用其他方式，这里不做限定。
当数据流传输到骨干网后，骨干网交换设备根据设置的反映骨干网拥塞程度的管道使用率阈值和流控标签的对应关系来对流量进行控制。比如当管道使用率为60％时，丢弃流控标签为B的流量；管道使用率为80％时，丢弃流控标签为A的流量，等等。这里的60％或80％只是一个示例，具体数值可以根据需要设定。
进一步的，如果丢弃所有的带流控标识的流量(GBR-MBR间的流量)仍然无法使管道使用率小于设定的最高阈值时，可以启动管道扩容流程，来增加管道对应的带宽资源。当扩容失败或在扩容成功前，可以丢弃不带流控标识的流量(GBR内的流量)。当然也可以在丢弃所有的带流控标识的流量仍然无法使管道使用率小于设定的最高阈值时，继续丢弃不带流控标识的流量。
在具体实现中，作为另一种实施例，在S303之前，网关还可以接收策略中心下发的消 息，该消息用于指示网关检测所述数据流中的保证带宽流量和超过保证带宽的流量，增加标签，之后网关执行步骤S303。可选的，策略中心之所以给网关下发该消息，是因为策略中心接收到了骨干网交换设备上报拥塞情况的事件。这样，可以使策略中心在网络拥塞的时候，再通知网关来检测保证带宽的流量，以此进行流控，这样可以减轻网关的负担，使网关以及整个系统的功能得到了优化。该实施例中，网关的动作可以根据图2中的第一交互模块来执行。
如图4所示，为本发明实施例提供的另一种流量控制的方法流程示意图。
S401-S407，同S301-S307，这里不再赘述。本实施例中，以流控方式为骨干网交换设备丢弃超过保证带宽的流量为例。
具体实现中，步骤401之前，策略中心可以下发流控处理策略给骨干网交换设备。其中，流控处理策略包括骨干网拥塞程度和对应的处理方式。比如：骨干网拥塞程度可以用骨干网的管道使用率来表示；对应的处理方式可以用丢弃用户的超过保证带宽流量来表示，或者用丢弃用户一定比例的超过保证带宽流量来表示。当然，也不限于这些方式。
S409，骨干网交换设备上报丢弃超过保证带宽流量的事件和骨干网拥塞程度给策略中心。策略中心接收骨干网交换设备上报的丢弃超过保证带宽流量的事件和骨干网拥塞程度。所述事件中包括被丢弃的超过保证带宽的数据流的标识。
在具体实现中，作为一种实现方式，如果策略中心通过SDN控制器对骨干网交换设备进行控制，那么骨干网交换设备需要经由SDN控制器将丢弃超过保证带宽流量的事件和骨干网拥塞程度上报给策略中心。
在具体实现中，作为一种实现方式，不经过SDN控制器将丢弃超过保证带宽流量的事件和骨干网拥塞程度上报给策略中心。
S411，策略中心根据所述丢弃超过保证带宽流量的事件确定调整策略。
在具体实现中，策略中心可以根据所述事件中包括的被丢弃的超过保证带宽的数据流的标识确定对应的用户的调整策略，即：降低用户的带宽(如降低MBR)。
这样，策略中心可以动态确定需要降低带宽的用户，以便对用户的带宽进行调整。
S413，策略中心发送降低用户带宽的调整策略给网关。网关接收策略中心发送的降低用户带宽的调整策略。
其中，调整策略为：用户的业务使用带宽不超过骨干网允许带宽。
S415，网关将所述调整策略发给所述用户，以使所述用户发送数据流时降低带宽。
这样，网关可以及时的获知用户的带宽策略，并将策略及时的反馈给用户，以使用户设备可以根据骨干网的拥塞情况动态调整发送数据流的带宽。
上述骨干网交换设备的动作可以由骨干网交换设备根据上述提及的存储器中的软件模块来执行。例如，S409中骨干网交换设备的动作可以根据图2中第二交互模块来执行。
上述网关的动作可以由网关根据上述提及的存储器中的软件模块来执行。例如，S413和S415中网关的动作可以根据图2中第一交互模块来执行。
如图5所示，为本发明实施例提供的另一种流量控制的方法流程示意图。
S501-S507，同S301-S307，这里不再赘述。
本实施例中，以流控方式为骨干网交换设备丢弃保证带宽的流量为例。
S509，骨干网交换设备上报丢弃用户的保证带宽的流量的事件给策略中心。策略中心 接收骨干网交换设备上报的丢弃用户的保证带宽的流量的事件。其中，所述事件中携带丢弃的数据流的标识。
在具体实现中，作为一种实现方式，如果策略中心通过SDN控制器对骨干网交换设备进行控制，那么骨干网交换设备需要经由SDN控制器将丢弃超过保证带宽流量的事件和骨干网拥塞程度上报给策略中心。
在具体实现中，作为一种实现方式，骨干网交换设备不经由SDN控制器而将丢弃超过保证带宽流量的事件和骨干网拥塞程度上报给策略中心。
S511，策略中心根据所述丢弃用户的保证带宽的流量的事件确定用户的调整策略为拆除用户保证带宽对应的承载(这里以保证带宽对应的承载为GBR承载为例)。
在具体实现中，策略中心可以根据所述事件中包括的数据流的标识确定对应的用户的调整策略。
S513，策略中心发送调整策略给网关。网关接收策略中心发送的调整策略。
S515，网关拆除用户的GBR承载。
具体实现中，网关拆除用户的GBR承载可以通过网关接收到策略中心下发的拆除承载的指示，发起删除该GBR对应的承载请求来拆除(或删除)该GBR承载。上述承载请求可以经服务网关(Serving Gateway，SGW)到移动性管理实体(Mobility Management Entity，MME)再发给eNodeB和用户使用的UE。
在具体实现中骨干网交换设备丢弃保证带宽的流量以及S509-S515可以和图4的流控方法结合起来执行。也就是说，在图4所示的丢弃超过保证带宽的流量后，那么可以继续丢弃保证带宽的流量。比如，丢弃超过保证带宽的流量后，骨干网还是拥塞，那么就可以继续丢弃保证带宽的流量。
上述骨干网交换设备的动作可以由骨干网交换设备根据上述提及的存储器中的软件模块来执行。例如，S509中骨干网交换设备的动作可以根据图2中第二交互模块来执行。
上述网关的动作可以由网关根据上述提及的存储器中的软件模块来执行。例如，S513和S515中网关的动作可以根据图2中第一交互模块来执行。
如图6所示，本发明实施例还提供了一种网络设备的结构示意图。该网络设备600包括，增加标签单元601和发送单元603。其中，增加标签单元601，用于将超过保证带宽的流量增加流控标签或将保证带宽流量增加流控标签；发送单元603，用于将携带流控标签的数据流发送给骨干网交换设备，以使骨干网交换设备根据流控标签丢弃超过保证带宽的流量。进一步的，还可以包括检测单元605，用于检测接收的数据流中的保证带宽的流量和超过保证带宽的流量。
在本实施例中，网络设备600是以功能单元的形式来呈现。这里的“单元”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到网络设备600可以采用图2所示的形式。检测单元605，增加标签单元601和发送单元603可以通过图2的处理器和存储器来实现，具体的，发送单元603可以通过由处理器来执行第一交互模块来实现，检测单元605和增加标签单元603可以通过由处理器来执行第一执行模块来实现。
如图7所示，本发明实施例还提供了一种骨干网交换设备的结构示意图。该骨干网交 换设备700包括，接收单元701和流控单元703。
其中，接收单元701，用于接收网络设备发送的携带流控标签的数据流；其中，所述流控标签包括携带在超过保证带宽流量中的流控标签，或携带在保证带宽流量中的流控标签；流控单元703，用于根据所述流控标签丢弃超过保证带宽的流量。
在本实施例中，骨干网交换设备700是以功能单元的形式来呈现。这里的“单元”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到骨干网交换设备700可以采用图2所示的形式。接收单元701和流控单元703可以通过图2的处理器和存储器来实现，具体的，接收单元701可以通过由处理器来执行第二交互模块来实现，流控单元703可以通过由处理器来执行第二执行模块来实现。
本发明实施例还提供了一种计算机存储介质，用于储存为上述图6所示的网络设备或图7所示的骨干网交换设备所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。通过执行存储的程序，可以使用户保证带宽的流量得到保证。
尽管在此结合各实施例对本发明进行了描述，然而，在实施所要求保护的本发明过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
本领域技术人员应明白，本发明的实施例可提供为方法、装置(设备)、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。计算机程序存储/分布在合适的介质中，与其它硬件一起提供或作为硬件的一部分，也可以采用其他分布形式，如通过Internet或其它有线或无线电信系统。
本发明是参照本发明实施例的方法、装置(设备)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方 框或多个方框中指定的功能的步骤。
尽管结合具体特征及其实施例对本发明进行了描述，显而易见的，在不脱离本发明的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本发明的示例性说明，且视为已覆盖本发明范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (31)

  1. 一种流量控制方法，其特征在于，包括：
    网络设备将超过保证带宽的流量增加流控标签或将保证带宽的流量增加流控标签；
    将携带流控标签的数据流发送给骨干网交换设备；
    所述骨干网交换设备根据所述流控标签丢弃超过保证带宽的流量。
  2. 如权利要求1所述的方法，其特征在于，所述网络设备将超过保证带宽的流量增加流控标签或将保证带宽的流量增加流控标签之前，还包括：
    网络设备检测接收的数据流中的保证带宽的流量和超过保证带宽的流量。
  3. 如权利要求1或2所述的方法，其特征在于，所述将超过保证带宽的流量增加流控标签包括：
    将超过保证带宽的流量分成至少两级，分别增加相应的流控标签；
    相应的，所述骨干网交换设备根据流控标签丢弃超过保证带宽的流量具体包括：所述骨干网交换设备根据流控标签和骨干网拥塞程度分级丢弃超过保证带宽的流量。
  4. 如权利要求1至3任一所述的方法，还包括：
    所述骨干网交换设备上报丢弃超过保证带宽流量的事件和骨干网拥塞程度给策略中心，以使所述策略中心根据所述事件确定需要降低带宽的用户，所述事件中携带丢弃的超过保证带宽流量的数据流的标识。
  5. 如权利要求4所述的方法，还包括：
    网络设备接收来自策略中心的降低用户带宽的调整策略；
    网络设备将所述调整策略发给所述用户，以使所述用户发送数据流时降低带宽。
  6. 如权利要求5所述的方法，所述调整策略具体包括：用户的业务使用带宽不超过骨干网允许带宽。
  7. 如权利要求1至6任一所述的方法，还包括，所述骨干网交换设备还丢弃保证带宽的流量。
  8. 如权利要求7所述的方法，还包括，
    所述骨干网交换设备上报丢弃用户的保证带宽的流量的事件给策略中心，以使策略中心根据所述事件确定用户的调整策略为拆除用户保证带宽对应的承载；其中，所述事件中携带丢弃的保证带宽流量的数据流的标识。
  9. 如权利要求8所述的方法，还包括：
    网络设备接收来自策略中心的拆除用户保证带宽对应的承载的策略；
    网络设备拆除用户的保证带宽对应的承载。
  10. 如权利要求2至9任一所述的方法，所述网络设备检测接收的数据流中的保证带宽的流量和超过保证带宽的流量之前还包括：
    网络设备接收策略中心下发的消息，所述消息用于指示网络设备检测所述数据流中的保证带宽流量和超过保证带宽的流量。
  11. 如权利要求10所述的方法，还包括：
    当所述骨干网发生拥塞情况下，骨干网交换设备上报拥塞情况给策略中心。
  12. 一种流量控制的方法，其特征在于，包括：
    网络设备将超过保证带宽的流量增加流控标签或将保证带宽的流量增加流控标签；
    将携带流控标签的数据流发送给骨干网交换设备，以使骨干网交换设备根据流控标签丢弃超过保证带宽的流量。
  13. 如权利要求12所述的方法，其特征在于，所述网络设备将超过保证带宽的流量增加流控标签或将保证带宽的流量增加流控标签之前，还包括：
    网络设备检测接收的数据流中的保证带宽的流量和超过保证带宽的流量。
  14. 如权利要求12或13所述的方法，其特征在于，所述将超过保证带宽的流量增加流控标签具体包括：将超过保证带宽的流量分成至少两级，分别增加相应的流控标签；
    相应的，根据流控标签丢弃超过保证带宽的流量具体包括：所述骨干网交换设备根据流控标签和骨干网拥塞程度分级丢弃超过保证带宽的流量。
  15. 如权利要求12至14任一所述的方法，其特征在于，还包括：
    所述网络设备接收来自策略中心的降低用户带宽的调整策略；
    所述网络设备将所述调整策略发给所述用户，以使所述用户发送数据流时降低带宽。
  16. 如权利要求13至15任一所述的方法，其特征在于，所述网络设备检测接收的数据流中的保证带宽的流量和超过保证带宽的流量之前还包括：
    网络设备接收策略中心下发的消息，所述消息用于指示所述网络设备检测所述数据流中的保证带宽流量和超过保证带宽的流量。
  17. 一种流量控制的方法，其特征在于，包括：
    骨干网交换设备接收网络设备发送的携带流控标签的数据流；其中，所述流控标签包括携带在超过保证带宽流量中的流控标签，或携带在保证带宽流量中的流控标签；
    所述骨干网交换设备根据所述流控标签丢弃超过保证带宽的流量。
  18. 如权利要求17所述的方法，其特征在于，所述携带在超过保证带宽流量中的流控标签包括：至少两级流控标签，
    相应的，所述骨干网交换设备根据所述流控标签丢弃超过保证带宽的流量具体包括：
    所述骨干网交换设备根据流控标签和骨干网拥塞程度分级丢弃超过保证带宽的流量。
  19. 如权利要求17或18所述的方法，还包括：
    所述骨干网交换设备上报丢弃超过保证带宽流量的事件和骨干网拥塞程度给策略中心，以使所述策略中心根据所述事件确定需要降低带宽的用户，所述事件中携带丢弃的超过保证带宽流量的数据流的标识。
  20. 如权利要求19所述的方法，还包括，所述骨干网交换设备还丢弃保证带宽的流量。
  21. 如权利要求20所述的方法，还包括，
    所述骨干网交换设备上报丢弃用户的保证带宽的流量的事件和丢弃数据流的流标识给策略中心，以使策略中心根据所述事件确定用户的调整策略为拆除用户保证带宽对应的承载；其中，所述事件中携带丢弃的保证带宽流量的数据流的标识。
  22. 一种实现流量控制的网络设备，其特征在于，包括：
    增加标签单元，用于将超过保证带宽的流量增加流控标签或将保证带宽流量增加流控标签；
    发送单元，用于将携带流控标签的数据流发送给骨干网交换设备，以使骨干网交换设备根据流控标签丢弃超过保证带宽的流量。
  23. 如权利要求22所述的网络设备，其特征在于，还包括：
    检测单元，用于检测接收的数据流中的保证带宽的流量和超过保证带宽的流量。
  24. 如权利要求22或23所述的网络设备，其特征在于，
    所述增加标签单元，用于将超过保证带宽的流量增加流控标签，包括：
    所述增加标签单元，具体用于将超过保证带宽的流量分成至少两级，分别增加相应的流控标签。
  25. 如权利要求22至24任一所述的网络设备，其特征在于，还包括：
    接收单元，用于接收来自策略中心的降低用户带宽的调整策略；
    则发送单元，还用于将所述调整策略发给所述用户，以使所述用户发送数据流时降低带宽。
  26. 如权利要求22至25任一所述的网络设备，其特征在于，
    所述接收单元，还用于接收策略中心下发的消息，所述消息用于指示所述网络设备检测所述数据流中的保证带宽流量和超过保证带宽的流量。
  27. 一种实现流量控制的骨干网交换设备，其特征在于，包括：
    接收单元，用于接收网络设备发送的携带流控标签的数据流；其中，所述流控标签包括携带在超过保证带宽流量中的流控标签，或携带在保证带宽流量中的流控标签；
    流控单元，用于根据所述流控标签丢弃超过保证带宽的流量。
  28. 如权利要求27所述的骨干网交换设备，其特征在于，所述携带在超过保证带宽流量中的流控标签包括：至少两级流控标签，
    相应的，所述流控单元，具体用于根据流控标签和骨干网拥塞程度分级丢弃超过保证带宽的流量。
  29. 如权利要求27或28所述的骨干网交换设备，其特征在于，还包括：
    上报单元，用于上报丢弃超过保证带宽流量的事件和骨干网拥塞程度给策略中心，以使所述策略中心根据所述事件确定需要降低带宽的用户，所述事件中携带丢弃的超过保证带宽流量的数据流的标识。
  30. 权利要求27至29任一所述的骨干网交换设备，还包括，所述骨干网交换设备还丢弃保证带宽的流量。
  31. 如权利要求30所述的骨干网交换设备，其特征在于，
    上报单元，还用于上报丢弃用户的保证带宽的流量的事件和丢弃数据流的流标识给策略中心，以使策略中心根据所述事件确定用户的调整策略为拆除用户保证带宽对应的承载；其中，所述事件中携带丢弃的数据流的标识。
PCT/CN2017/073451 2016-02-29 2017-02-14 一种流量控制方法、装置和系统 WO2017148256A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2017564623A JP6541117B2 (ja) 2016-02-29 2017-02-14 トラフィック制御方法、装置、及びシステム
KR1020177034371A KR102039384B1 (ko) 2016-02-29 2017-02-14 트래픽 제어 방법, 장치 및 시스템
EP17759107.0A EP3297323B1 (en) 2016-02-29 2017-02-14 Traffic control method, apparatus and system
US15/909,565 US10523589B2 (en) 2016-02-29 2018-03-01 Traffic control method, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610112450.9 2016-02-29
CN201610112450.9A CN107135521B (zh) 2016-02-29 2016-02-29 一种流量控制方法、装置和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/909,565 Continuation US10523589B2 (en) 2016-02-29 2018-03-01 Traffic control method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2017148256A1 true WO2017148256A1 (zh) 2017-09-08

Family

ID=59721639

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/073451 WO2017148256A1 (zh) 2016-02-29 2017-02-14 一种流量控制方法、装置和系统

Country Status (6)

Country Link
US (1) US10523589B2 (zh)
EP (1) EP3297323B1 (zh)
JP (1) JP6541117B2 (zh)
KR (1) KR102039384B1 (zh)
CN (1) CN107135521B (zh)
WO (1) WO2017148256A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10893437B2 (en) * 2018-02-27 2021-01-12 Verizon Patent And Licensing Inc. Out-of-order packet handling in 5G/new radio
US10743211B2 (en) * 2018-09-25 2020-08-11 Verizon Patent And Licensing, Inc. Diversified ran architecture with congestion control based on spectrum re-allocation
US11190488B1 (en) * 2019-03-07 2021-11-30 NortonLifeLock Inc. Adaptive security filtering on a client device
CN110351357B (zh) * 2019-07-08 2023-07-25 中国平安人寿保险股份有限公司 服务器限流方法、装置、计算机设备以及存储介质
US11411823B2 (en) * 2019-09-20 2022-08-09 Sonatus, Inc. System, method, and apparatus to support mixed network communications on a vehicle
US11538287B2 (en) 2019-09-20 2022-12-27 Sonatus, Inc. System, method, and apparatus for managing vehicle data collection
US11772583B2 (en) 2020-03-06 2023-10-03 Sonatus, Inc. System, method, and apparatus for managing vehicle automation

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080037552A1 (en) * 2006-08-11 2008-02-14 Latitude Broadband, Inc. Methods And Systems For Providing Quality Of Service In Packet-Based Core Transport Networks
CN102195819A (zh) * 2011-05-30 2011-09-21 中兴通讯股份有限公司 一种网络设备及其业务流量监管方法
CN103441943A (zh) * 2013-08-28 2013-12-11 迈普通信技术股份有限公司 一种流量报文控制方法及装置
CN104601488A (zh) * 2015-01-22 2015-05-06 杭州华三通信技术有限公司 一种软件定义网络中流量控制方法和装置

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003218923A (ja) * 2001-11-19 2003-07-31 Matsushita Electric Ind Co Ltd パケット送信装置及びパケット送信処理方法
JP4238150B2 (ja) * 2004-01-30 2009-03-11 日本電信電話株式会社 通信網におけるレート制御方法およびレート制御システム
US9143406B2 (en) * 2007-10-17 2015-09-22 Verizon Patent And Licensing Inc. Apparatus, method and computer-readable storage medium for calculating throughput requirements of a network
US8284665B1 (en) * 2008-01-28 2012-10-09 Juniper Networks, Inc. Flow-based rate limiting
US8730812B2 (en) * 2009-01-09 2014-05-20 Brocade Communications Systems, Inc. Hierarchical rate color marker
US8335161B2 (en) * 2010-02-03 2012-12-18 Bridgewater Systems Corp. Systems and methods for network congestion management using radio access network congestion indicators
KR20130064519A (ko) * 2011-12-08 2013-06-18 삼성전자주식회사 무선 통신 시스템 및 그의 트래픽 제어 방법
EP2704380A1 (en) * 2012-09-03 2014-03-05 Telefonaktiebolaget L M Ericsson (publ) Congestion signalling in a communications network
WO2014142971A1 (en) * 2013-03-15 2014-09-18 Hewlett-Packard Development Company , L. P. Traffic control across a layer 2 - layer 3 boundary in a software defined network
US20140293796A1 (en) * 2013-03-29 2014-10-02 Samsung Electronics Co., Ltd. Method and apparatus for controlling congestion in wireless communication system
CN104254106A (zh) * 2013-06-29 2014-12-31 华为终端有限公司 无线接入网络ran拥塞处理方法及装置
CN105579991A (zh) * 2013-07-23 2016-05-11 慧与发展有限责任合伙企业 使用优先级进行工作保持的带宽保证
WO2015043662A1 (en) * 2013-09-27 2015-04-02 Telefonaktiebolaget L M Ericsson (Publ) Methods, devices and computer programs for providing a service or service component requiring a specific packet-forwarding treatment
CN104333882A (zh) * 2014-10-27 2015-02-04 浪潮电子信息产业股份有限公司 一种无线网络流量控制的方法
CN105245466A (zh) * 2015-10-14 2016-01-13 北京锐安科技有限公司 流量控制方法、装置及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080037552A1 (en) * 2006-08-11 2008-02-14 Latitude Broadband, Inc. Methods And Systems For Providing Quality Of Service In Packet-Based Core Transport Networks
CN102195819A (zh) * 2011-05-30 2011-09-21 中兴通讯股份有限公司 一种网络设备及其业务流量监管方法
CN103441943A (zh) * 2013-08-28 2013-12-11 迈普通信技术股份有限公司 一种流量报文控制方法及装置
CN104601488A (zh) * 2015-01-22 2015-05-06 杭州华三通信技术有限公司 一种软件定义网络中流量控制方法和装置

Also Published As

Publication number Publication date
JP2018525865A (ja) 2018-09-06
US10523589B2 (en) 2019-12-31
EP3297323A4 (en) 2018-08-01
US20180191636A1 (en) 2018-07-05
KR20170140811A (ko) 2017-12-21
KR102039384B1 (ko) 2019-11-04
CN107135521B (zh) 2020-12-25
JP6541117B2 (ja) 2019-07-10
EP3297323B1 (en) 2020-04-08
CN107135521A (zh) 2017-09-05
EP3297323A1 (en) 2018-03-21

Similar Documents

Publication Publication Date Title
WO2017148256A1 (zh) 一种流量控制方法、装置和系统
WO2018082602A1 (zh) 切换方法及装置
EP3471355B1 (en) Communication network congestion control using allocation and retention priority
CA3112926A1 (en) Slice information processing method and apparatus
AU2019323009B2 (en) Quality of service monitoring method and system, and device
WO2013117126A1 (zh) 业务速率控制方法和系统以及设备
WO2013010462A1 (zh) 保证上行服务质量的方法、基站及用户设备
US20150271087A1 (en) Evolved node-b and mobility management entity and user equipment and methods for supporting attended and unattended services
WO2019029581A1 (zh) 一种业务质量流的控制方法及相关设备
WO2019149106A1 (zh) 一种服务质量QoS控制方法及相关设备
TWI721333B (zh) 在無線通訊系統中建立承載的方法和裝置
WO2018082597A1 (zh) 拥塞控制方法及装置、基站
EP3518580B1 (en) Data transmission method and apparatus therefor
WO2018120183A1 (zh) 数据传输的方法及装置
WO2018141278A1 (zh) 无线通信方法、用户设备、接入网设备和网络系统
US11647419B2 (en) Adjusting window size based on quality of experience
CN103139843B (zh) 一种优先级扩展队列实现方法及系统
WO2017101121A1 (zh) 传输信令、传输数据和建立gtp隧道的方法及设备
CN110740472B (zh) 一种下行数据传输的控制方法和系统
JP2016046669A (ja) パケット処理装置、プログラム及び方法
WO2014067075A1 (zh) 缓解网络拥塞的方法、核心网设备和接入网设备
WO2018171639A1 (zh) 无线通信方法、终端、接入网设备和网络系统
CN103716894B (zh) Lte中承载抢占时业务数据处理的方法及装置
WO2024032603A1 (zh) 一种通信方法及装置
EP4040845B1 (en) Communication method, apparatus and system

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2017759107

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20177034371

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017564623

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE