WO2013082789A1 - Procédé et dispositif de contrôle de congestion de réseau - Google Patents

Procédé et dispositif de contrôle de congestion de réseau Download PDF

Info

Publication number
WO2013082789A1
WO2013082789A1 PCT/CN2011/083712 CN2011083712W WO2013082789A1 WO 2013082789 A1 WO2013082789 A1 WO 2013082789A1 CN 2011083712 W CN2011083712 W CN 2011083712W WO 2013082789 A1 WO2013082789 A1 WO 2013082789A1
Authority
WO
WIPO (PCT)
Prior art keywords
congestion
level
service flow
user priority
control policy
Prior art date
Application number
PCT/CN2011/083712
Other languages
English (en)
Chinese (zh)
Inventor
王磊
李岩
魏凯
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2011/083712 priority Critical patent/WO2013082789A1/fr
Priority to CN201180003285.9A priority patent/CN103548381B/zh
Publication of WO2013082789A1 publication Critical patent/WO2013082789A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/11—Identifying congestion

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a congestion control method and apparatus. Background technique
  • the PCRF Policy and Charging Rules Function
  • QoS Quality of Service
  • An object of the embodiments of the present invention is to provide a congestion control method and apparatus, and to ensure user priority according to network congestion.
  • the purpose of the embodiment of the present invention is achieved by the following technical solutions:
  • an embodiment of the present invention provides a congestion control method, including:
  • an embodiment of the present invention provides a congestion control apparatus, including:
  • a detecting unit configured to detect a congestion identifier carried by the service flow
  • a determining unit configured to determine a corresponding congestion level according to the detection result and a user priority of the user equipment UE that receives the service flow, and obtain a corresponding congestion control policy according to the congestion level and the user priority;
  • control unit configured to perform congestion control on the service flow according to the obtained congestion control policy.
  • the current traffic congestion is measured by the congestion level and the user priority to perform corresponding service flow control, thereby ensuring the user priority according to the network congestion.
  • FIG. 1 is a schematic flowchart of a congestion control method according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of a congestion control apparatus according to an embodiment of the present invention.
  • 3 is a schematic flowchart 1 of an application flow of a congestion control method according to an embodiment of the present invention
  • 4 is a second schematic diagram of an application flow of a congestion control method according to an embodiment of the present invention
  • FIG. 5 is a second schematic diagram of an application flow of a congestion control method according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram 4 of an application flow of a congestion control method according to an embodiment of the present invention. detailed description
  • an embodiment of the present invention provides a congestion control method, including:
  • the execution entity of the congestion control method in the embodiment of the present invention may be a PGW (Packet Data Network Gateway), and specifically, may be a PCEF (Policy and Charging Execution Function) entity, or a TDF. (Traffic Detection Function) An entity, etc., where the TDF entity includes two types: a built-in TDF and an external TDF.
  • PGW Packet Data Network Gateway
  • PCEF Policy and Charging Execution Function
  • TDF Traffic Detection Function
  • the current traffic congestion is measured by the congestion level and the user priority to perform corresponding service flow control, thereby ensuring the user priority according to the network congestion.
  • the method for detecting the congestion identifier carried by the service flow in the foregoing step 11 may include:
  • the number of data packets carrying the congestion identifier in the service flow is detected.
  • the congestion identifier may include a ConEx (Congestion Exposure) identifier.
  • ConEx Congestion Exposure
  • the ConEx logo can be understood by reference to the prior art and will not be described here.
  • the data packet may include an uplink data packet or a downlink data packet.
  • the specific implementation manner of detecting the data packet carrying the congestion identifier may be: when the first ConEx marked downlink packet is detected, the recording is started, and the statistics are detected within a certain period of time. The number of downstream packets of the ConEx tag.
  • the foregoing step 11 is configured to detect a congestion identifier carried by the service flow, and the method may include:
  • the congestion identifier carried by all service flows of the UE is detected.
  • the congestion control method in the embodiment of the present invention can detect the service flow granularity or the user granularity.
  • the foregoing step 12 determines a corresponding congestion level according to the detection result and the user priority of the UE that receives the data packet.
  • the congestion threshold is composed of the number of data packets
  • the corresponding congestion level is determined according to the number of data packets of the detection result and the user priority
  • the congestion threshold is composed of a congestion ratio
  • the corresponding congestion level is determined based on the congestion ratio of the detection result and the user priority.
  • each congestion level different user priorities correspond to different congestion thresholds.
  • the congestion threshold corresponding to the high user priority is greater than the congestion threshold corresponding to the lower user priority, and the same user takes precedence.
  • Level F the congestion threshold of the high congestion level is greater than the congestion threshold of the low congestion level.
  • the congestion level has different metrics, reflecting the two dimensions of user priority and congestion level.
  • the metric of the congestion level may be configured on the PCEF entity or the TDF entity, or may be sent by the PCRF entity to the PCEF entity or the TDF entity.
  • the PCEF entity or the TDF entity may determine the identity characteristics of the user to which the service flow belongs according to the IP-CAN (IP-Connectivity Access Network) session information, such as IMSI (International Mobile Subscriber Identification Number, International Mobile User). The identification code) or MSISDN (Mobile Station Integrated Services Digital Number), etc., and then use the IMSI or MSISDN as the index to query the subscription information database, and the user priority can be obtained.
  • IP-CAN IP-Connectivity Access Network
  • IMSI International Mobile Subscriber Identification Number, International Mobile User
  • MSISDN Mobile Station Integrated Services Digital Number
  • the congestion control policy in step 13 above may include:
  • the traffic congestion control degree for high user priority is lower than the traffic flow congestion control degree for low user priority
  • the traffic congestion control degree for the low congestion level is lower than the traffic flow congestion control level for the high congestion level.
  • a congestion control strategy metric is comprehensively considered from the two dimensions of user priority and congestion level. Moreover, multiple combinations can be implemented by user priority and congestion level, so that the traffic of high priority users or low congestion users can be guaranteed.
  • the congestion control policy can be formulated according to the operator policy.
  • the congestion control policy may be configured on the PCEF entity or the TDF entity, or may be sent by the PCRF entity to the PCEF entity or the TDF entity, or may be sent to the PCEF entity or the TDF entity by the PCRF entity.
  • the congestion control policy delivered by the PCRF entity affects the bearer parameters, such as QoS (Quality of Service)
  • the PCRF entity can send the congestion control policy to the PCEF entity through the Gx reference point, or through the Gxx reference. The point is sent to the BBERF (Bearing Binding and Event Report Function) entity for execution.
  • the PCC Policy and Charging Control
  • the QoS rule is used to deliver the QoS-BBERF function
  • the ADC Application Detection and Control
  • TDF Transmission Detection and Control
  • the foregoing step 13 is based on The congestion level and the priority of the household acquire the corresponding congestion control policies, which may include:
  • the congestion level is sent to the PCRF entity, so that the PCRF entity determines the corresponding congestion control policy according to the user priority and the congestion level; and receives the congestion control policy sent by the PCRF entity.
  • the congestion level is sent to the PCRF entity; and the congestion control policy corresponding to the user priority of each congestion level sent by the PCRF entity is received.
  • the PCRF entity may determine the identity characteristics of the user to which the service flow belongs according to the IP-CAN session information, such as IMSI or MSISDN, and then use IMSI or MSISDN as an index to query the subscription information database, and the user priority may be obtained.
  • IP-CAN session information such as IMSI or MSISDN
  • the PCRF entity can deliver a set of congestion control policies or a specific congestion control policy according to the report.
  • the PCRF entity is actively sent to the PCEF entity or the TDF entity or the BBERF entity, and the corresponding congestion control policy is obtained according to the congestion level and the user priority in the foregoing step 13, which may include:
  • the congestion control policy corresponding to the user priority sent by the PCRF entity is received, and the congestion control policy corresponding to the user priority is the same under each congestion level; and the matched congestion control policy is obtained according to the congestion level.
  • the PCRF entity can actively deliver a set of congestion control policies or a specific congestion control policy.
  • the congestion control policy may be configured on the PCEF entity or the TDF entity, and the corresponding congestion control policy may be obtained according to the congestion level and the user priority in the foregoing step 13, which may include:
  • the congestion control policy corresponding to the priority of each user in each congestion level is pre-configured, and the corresponding congestion control policy is obtained according to the congestion level and the user priority.
  • the congestion control mode in the foregoing step 13 may include:
  • Loss of data packets in the service flow or block data packets in the service flow, or switch service flows, or modify QoS parameters of data packets in the service flow.
  • the congestion control performed by the PCEF entity or the TDF entity may include performing packet loss processing on the data packet in the service flow, or blocking the data packet in the service flow, or switching the service flow, or modifying the QoS of the data packet in the service flow. parameter.
  • the congestion control performed by the BBERF entity includes modifying the QoS parameters of the data packets in the traffic flow.
  • the congestion control policy for performing packet loss processing on the data packet may include:
  • the packet loss rate corresponding to the service flow of the high user priority is smaller than the packet loss rate corresponding to the service flow of the low user priority;
  • an embodiment of the present invention provides a congestion control apparatus, including: The detecting unit 21 is configured to detect a congestion identifier carried by the service flow.
  • the determining unit 22 determines a corresponding congestion level according to the detection result and the W-home priority of the user equipment UE that receives the service flow, and acquires a corresponding congestion control policy according to the congestion level and the user priority.
  • the control unit 23 is configured to perform congestion control on the service flow according to the acquired congestion control policy.
  • the executor of the congestion control method in the embodiment of the present invention may be a PGW, and specifically, may be a PCEF entity, or a TDF entity, etc., where the TDF entity includes two types: a built-in TDF and an external TDF.
  • the current traffic congestion is measured by the congestion level and the user priority to perform corresponding service flow control, thereby ensuring the W household priority according to the network congestion.
  • the detecting unit 21 is specifically configured to:
  • the congestion identifier may include a ConEx identifier.
  • the detecting unit 21 is further configured to:
  • a congestion identifier carried by all service flows of the UE is detected.
  • the determining unit 22 is specifically configured to:
  • the congestion threshold is composed of the number of data packets
  • the corresponding congestion level is determined according to the number of data packets of the detection result and the user priority
  • the congestion threshold is composed of a congestion ratio
  • the corresponding congestion level is determined based on the congestion ratio of the detection result and the user priority.
  • each congestion level different user priorities correspond to different congestion thresholds.
  • the congestion threshold corresponding to the high user priority is greater than the congestion threshold corresponding to the lower user priority, and the same user takes precedence.
  • the congestion threshold of the high congestion level is greater than the congestion threshold of the low congestion level.
  • the congestion control strategy may include:
  • the traffic congestion control degree for high user priority is lower than the traffic flow congestion control degree for low user priority
  • the traffic congestion control degree for the low congestion level is lower than the traffic flow congestion control level for the high congestion level.
  • control unit 23 may be specifically configured to:
  • Loss of data packets in the service flow or block data packets in the service flow, or switch service flows, or modify the quality of service QoS parameters of data packets in the service flow.
  • the congestion control policy for performing packet loss processing on the data packet may include:
  • the packet loss rate corresponding to the service flow of the high user priority is smaller than the packet loss rate corresponding to the service flow of the low user priority; and/or, Under the same Sichuan household priority, the packet loss rate corresponding to the traffic flow with low congestion level is small, and the packet loss rate corresponding to the traffic flow with high congestion level.
  • the determining unit 22, the body can be used D:-:
  • the congestion level is sent to the PCRF entity, and receives a congestion control policy corresponding to the user priority under each congestion level sent by the PCRF entity.
  • the determining unit 22 is specifically configured to:
  • the congestion control policy corresponding to the user priority is the same under each congestion level, and a matching congestion control policy is obtained according to the congestion level.
  • the determining unit 22 is specifically configured to:
  • a congestion control policy corresponding to each user priority in each congestion level is pre-configured, and a corresponding congestion control policy is obtained according to the congestion level and the user priority.
  • Embodiment 1 The congestion control apparatus and its configuration of the embodiment of the present invention can be understood in accordance with the execution action of the execution subject of the congestion control method of the above embodiment.
  • Embodiment 1
  • the application scenario of the congestion control method in this embodiment is: the PCEF entity performs the service flow granularity level detection, and reports the congestion level to the PCRF entity; the PCRF entity performs the congestion control policy decision and sends it to the PCEF entity for execution, and the PCEF entity receives the congestion control. After the policy, flow control is performed at the granularity of the service flow.
  • the PCEF entity detects the ConEx identifier information carried in the data packet sent by the sending end, such as an application function (such as an application function), and the identifier may reflect a network bottleneck in the packet forwarding path, such as an eNodeB (Evolved Node B, Current congestion of evolved Node B).
  • an eNodeB evolved Node B, Current congestion of evolved Node B
  • the PCEF can obtain the degree of congestion of the eNodeB indirectly without interacting with the eNodeB, which can reduce the interaction process.
  • the PCEF entity performs the service flow granularity level detection, including: when the PCEF entity detects the first packet carrying the ConEx identification information, the recording starts, and the number of the packets carrying the ConEx identification information is detected in a certain period of time, and the ConEx identifier is carried. The greater the number of messages, the higher the congestion.
  • the corresponding congestion level has different metrics.
  • the metric can be configured on the PCEF entity or the PCRF entity.
  • the congestion level of the eNodeB is defined as four levels of ABCD, A to D, and the congestion level is lowered in turn.
  • the user has certain identity characteristics when signing the contract, such as gold, silver, and copper users, and the user priority is lowered from gold to copper. .
  • the metrics can be divided into two types. The first one is the same user. The larger the number of packets carrying ConEx identification information, the higher the congestion level. For the traffic flow of gold users, the congestion levels A and B are detected respectively. 80 and 60 ConEx tagged messages.
  • the second type is that at the same congestion level, the number of low-priority users can be less than that of high-priority users.
  • For a congestion level A 80 ConEx messages are detected in the gold service flow for a period of time, and the silver medal is The user's service flow detected 70 ConEx messages.
  • the congestion control standard can It can be configured on the PCEF entity to be configured in the subscription data.
  • the congestion control standard is set according to the operator's policy. Different combinations of W-priority and congestion levels can be used to achieve multiple combinations. For example, even if the low-priority W-type packet congestion is low, it is considered that congestion control is required. High-priority users do not perform congestion control even if the packet congestion is high.
  • Table 1 below can be used to reflect the congestion level.
  • the known in Table 1 is the user level such as gold, silver and copper and the number of packets M (only the threshold values of different congestion levels are indicated). Get an unknown ABCD rating.
  • the gold medal user has 60 ConEx-marked messages within a certain period of time, it indicates that the current congestion level has reached the B level.
  • the congestion level D can be used for recovery after congestion control. If the PCEF entity detects that a service flow does not have a ConEx marked packet, the congestion level D can cancel the congestion control of the service flow.
  • the PCEF detects the ratio of the number of ConEx tokens in the traffic flow message to the number of packets of the service flow. This requires the PCEF entity to record the number of ConEx-tagged packets and the number of unmarked packets in the traffic stream when detecting the ConEx-tagged packets, calculate the proportion of the ConEx-tagged packets, and measure the congestion level based on the ratio.
  • the PCEF entity After the PCEF entity obtains the congestion level, the PCEF entity reports the congestion level to the PCRF entity, and the PCRF entity receives the congestion level and makes a congestion control policy decision.
  • the PCEF entity reports the congestion level by using the existing PCEF to request the PCC rule flow, for example, by setting a new reporting cause value and embodying the congestion level in the cause value.
  • the congestion level reaches a certain level, the PCEF entity reports the cause value and carries a specific congestion level.
  • the PCRF entity obtains the cause value and the congestion level information therein to make a policy decision. That is, the PCRF entity delivers a targeted policy for the current congestion level.
  • the PCEF entity executes the policy after receiving the congestion control policy.
  • the specific actions may include the following: Performing different levels of packet loss, blocking the service flow, performing service flow switching, and modifying the service flow according to the user category and the congestion level. QoS parameters, etc.
  • the congestion control policy is used as an example to perform different levels of packet loss in the service flow granularity.
  • the PCRF entity formulates a packet loss decision based on the user priority and congestion level, and distinguishes different policies by the proportion of the number of lost packets, as shown in Table 2.
  • the packet loss rate of the service flow message of the gold card user should be lower than that of the silver card user at the same level of congestion.
  • the traffic rate corresponding to the user with the lower congestion level is lower. Packet loss rate for different congestion levels and ffl household priorities Different from Table 1,
  • the PCEF entity reports that the user's congestion level is B, and the PCRF entity queries the subscription information database to obtain the identity of the user as a silver card user, then the traffic flow of the congestion level B is generated for the silver card user, and 30% of the traffic is executed. package.
  • the congestion level of the current network eNodeB is D.
  • the PCEF entity reports the congestion level to the PCRF entity, and the PCRF entity modification policy returns to the control mode when there is no congestion.
  • the congestion control policy is used as an example to block the service flow.
  • the file transfer protocol (FTP) of the Bronze user is congested, and the PCEF entity or the TDF entity corresponds to the corresponding congestion information on the application ID reported by the service flow.
  • the UE sends a policy to the UE, and the UE performs the received policy, and the FTP is generated from the 3GPP (3rd) that generates congestion.
  • Generation Partnership Project) Network such as UMTS (Universal Mobile Telecommunications System) network or LTE (Long Term Evolution)
  • non-3GPP non-3GPP access network
  • WLAN Wireless
  • the congestion control policy is used as an example to block the service flow.
  • the corresponding MBR Maximum Bit Rate
  • the gate corresponding to the modified service flow is turned off.
  • the congestion control policy is used as an example to modify the QoS parameters of the service flow, and the description is as follows:
  • the PCEF entity detects the congestion information
  • the Diameter CCR (Credit Control Request) message is reported, and the PCRF entity decides to modify the QoS parameter according to the congestion information, and passes the Diameter CCA (Credit Control Answer).
  • the message is sent by the policy.
  • the PCEF entity executes the policy and modifies QoS parameters, such as reducing the MBR or APN-AMBR (Access Point Name-Aggregate Maximum Bit Rate).
  • the PCRF entity may carry a time parameter when indicating the congestion control policy, and is used to indicate the effective time of the congestion control policy. During this period of time, the congestion control policy is valid, and the PCEF entity performs the corresponding action; after the time arrives, the congestion control policy is deactivated, and the PCEF entity no longer performs the corresponding action. After this point in time, the PCEF entity can perform a new congestion level detection.
  • the UE After the IP-CAN session is established, the UE performs the service, and the downlink data packet is sent to the eNodeB. eNodeB performs packet forwarding Yes, it detects whether the current queue is congested as a congestion warning. When the congestion congestion warning occurs, the ECT (ECN-capable transport, ECM, Explicit Congestion Notification) indicator is marked in the forwarded downlink data packet.
  • ECM ECM
  • the eNodeB sends the data packet to the UE by using the air interface resource, where the data packet carries the ECT identifier.
  • the UE receives the downlink data packet, and detects the ECT flag in the downlink data packet.
  • the UE simultaneously detects packet loss during the forwarding process of the downlink data packet.
  • the UE feeds back the ECT identification information of the eNodeB to the AF.
  • AF marks Re-echo-ECN in the data packet according to the ECT identification information, and marks Re-echo-Loss according to the retransmission information of the message, and estimates that the appropriate Credit AF uses these two types of information as the ConEx identifier.
  • Information marked in the downstream data message.
  • the line data packet is sent to the UE through the intermediate routing device.
  • the PCEF entity performs the service flow level detection on the downlink data packet.
  • the number of the ConEx identifier information is counted to measure the current congestion level.
  • the PCEF detects that there is 50 ConEx-labeled packets in a certain service flow for a period of time, indicating that the congestion level is B.
  • the PCEF entity reports the congestion level information to the PCRF entity. If the PCEF entity reuses the existing CCR/CCA process, the congestion level is reported as B.
  • the PCRF entity receives the congestion information reported by the PCEF entity, and the PCRF entity determines the identity feature of the user to which the service flow belongs according to the IP-CAN session information.
  • the PCRF entity formulates a congestion control policy based on the identity characteristics and congestion information. For example, the PCRF entity determines that the service flow belongs to a silver card user according to the session information in the CCR. According to Table 2, a congestion of 30% is performed by the congestion level B and the identity characteristics of the silver card user.
  • the PCRF entity sends the congestion control policy to the PCEF entity.
  • the PCEF entity performs a congestion control policy. For example, according to Table 2, the PCEF entity performs 30% packet loss on the service flow. Steps 31 to 35 describe the existing processes of ECN (Explicit Congestion Notification) and ConEx in the prior art, and therefore no description is made.
  • ECN Exlicit Congestion Notification
  • Steps 39 to 310 can refer to the corresponding processes of the prior art.
  • the V-PCRF is a functional entity in a roaming scenario, and is not described here.
  • Embodiment 2 is a functional entity in a roaming scenario, and is not described here.
  • the PCEF entity when performing the congestion level detection, the PCEF entity detects the user granularity, that is, detects the service flow corresponding to all the rules in the IP-CAN session, and the PCEF entity counts the multiple users. Congestion caused by traffic flow over a period of time, measuring the level of congestion at that user level. The PCEF entity then reports the congestion level to the PCRF entity, and the PCRF entity makes user-level policy decisions.
  • the PCEF entity when performing the congestion level detection, the PCEF entity detects the user granularity, that is, detects the service flow corresponding to all the rules in the IP-CAN session, and the PCEF entity counts the multiple users. Congestion caused by traffic flow over a period of time, measuring the level of congestion at that user level. The PCEF entity then reports the congestion level to the PCRF entity, and the PCRF entity makes user-level policy decisions.
  • Embodiment 3 when performing the congestion level detection, the PCEF entity detects the user granularity, that is, detects the service flow corresponding to all the rules in
  • the application scenario of the congestion control method in this embodiment is: the PCRF entity performs policy decision according to the operator policy and the pre-configured congestion level, and actively sends a congestion control policy; the PCEF entity performs service flow granularity congestion detection, and matches the corresponding policy. carried out The corresponding action.
  • the UE After the IP-CAN session is established, the UE performs the service, and the downlink data packet is sent to the eNodeB.
  • the eNodeB performs packet forwarding to detect whether the current queue is congested as a congestion warning. When a congestion congestion warning occurs, the ECT is marked in the forwarded downlink data message.
  • the eNodeB sends the data packet to the UE by using the air interface resource, where the data packet carries the ECT identifier.
  • the UE receives the downlink data packet, and detects the ECT flag in the downlink data packet.
  • the UE simultaneously detects packet loss during the forwarding process of the downlink data packet.
  • the UE feeds back the ECT identification information of the eNodeB to the AF.
  • the AF marks the Re-echo-ECN in the downlink data packet according to the ECT identification information, and marks the packet according to the retransmission information of the packet.
  • the downlink data packet is sent to the UE through the intermediate routing device.
  • the PCRF entity actively performs policy decision according to the operator policy and the user identity and a predefined set of congestion levels, and obtains a set of congestion control policies corresponding to a congestion level of a certain service flow. For example, for a certain service flow, when the PCC rule is delivered, the PCRF entity simultaneously delivers a congestion control policy for the service flow. As shown in Table 3, for the service flow of the gold card user, the PCRF entity sets a corresponding packet loss rate for each of the four congestion levels of the ABCD.
  • the metric of the congestion level can be statically configured on the PCEF entity, or can be actively sent by the PCRF entity while the policy is being sent.
  • the metrics for different levels of congestion can also be used as a set of information, as shown in Table 4, which only shows the threshold values for different congestion levels.
  • the PCRF entity sends a congestion control policy to the PCEF entity.
  • the PCRF entity can reuse the RAR (Re-Authorization-Request) procedure to send the congestion control policy to the PCEF entity.
  • the PCEF entity sends a RAA (Re- Authorization-Answer) response message to the PCRF entity.
  • the PCEF entity performs the service flow level detection on the data packet.
  • the number of the ConEx identifier information is counted to measure the current congestion level. Assume that at this time, the PCEF detects that there is 50 ConEx-tagged packets in a certain service flow for a period of time, and the inquiry table 4 can obtain the congestion level at the C level.
  • the PCEF entity obtains the congestion level C according to the calculation, performs policy matching in Table 3, and performs policy control according to the matched result, that is, discards 10% of the current service flow.
  • Steps 41 ⁇ 45 describe the existing processes of ECN and ConEx in the current technology.
  • Steps 47 to 48 describe the existing flow of the active delivery strategy of the PCRF entity in the prior art.
  • V-PCRF in Figure 4 is a functional entity in a roaming scenario, and is not described here.
  • the PCEF entity performs the detection of the user granularity when performing the congestion level detection, calculates the congestion degree of all the packets in the user granularity, reports the congestion level, and executes the corresponding policy.
  • Embodiment 5 the PCEF entity performs the detection of the user granularity when performing the congestion level detection, calculates the congestion degree of all the packets in the user granularity, reports the congestion level, and executes the corresponding policy.
  • the application scenario of the congestion control method in this embodiment is as follows:
  • the external TDF entity performs the service flow granularity level detection, and reports the congestion level to the PCRF entity.
  • the PCRF entity performs policy decision and sends it to the external TDF entity for execution.
  • the external TDF entity After receiving the congestion control policy, the external TDF entity performs flow control at the service flow granularity.
  • the PCRF entity sends the congestion control policy F to the PCEF entity through the Gx reference point (GTP-based S5/S8) or through the Gxx reference.
  • GTP-based S5/S8 Gx reference point
  • the point congestion control policy is implemented for the BBERF (Bearing Binding and Event Report Function) entity (PM IP-based S5/S8).
  • the congestion control method in this embodiment is described in detail, including:
  • the UE After the IP-CAN session is established, the UE performs the service, and the downlink data packet is sent to the eNodeB.
  • the eNodeB performs packet forwarding to detect whether the current queue is congested or congestion. When a congestion or congestion warning occurs, the ECT is marked in the forwarded downlink data packet.
  • the eNodeB sends the downlink data packet to the UE by using the air interface resource, where the downlink data packet carries the ECT identifier.
  • the UE receives the downlink data packet, and detects the ECT flag in the downlink data packet.
  • the UE simultaneously detects packet loss during the forwarding process of the downlink data packet.
  • the UE feeds back the ECT identification information of the eNodeB to the AF.
  • the AF marks the Re-echo-ECN in the downlink data packet according to the ECT identification information, and marks the Re-echo-Loss according to the retransmission information of the packet, and estimates that the appropriate Credit AF uses the three types of information as the ConEx identification information. Mark in the downlink data message.
  • the downlink data packet is sent to the UE through the intermediate routing device.
  • the external TDF entity performs the service flow level detection on the line data packet.
  • the number of the ConEx identifier information is counted to measure the current congestion level.
  • the external TDF entity reports congestion level information to the PCRF entity. If the ffiTDF entity reuses the existing CCR/CCA process, it reports the congestion level B.
  • a similar reporting method can be used to detect the traffic level of the current service flow/user and report it to the policy control network element.
  • the PCRF entity receives the congestion information reported by the external TDF, and the PCRF entity determines the identity feature of the user to which the service flow belongs according to the session information.
  • the PCRF entity formulates a congestion control policy based on the identity characteristics and congestion information. For example, the PCRF entity determines that the service flow belongs to the silver card user according to the session information in the CCR, and according to Table 2, through the congestion level B and the identity characteristics of the silver card user, a 30% packet loss action is determined.
  • the PCRF entity sends the congestion control policy to the external TDF entity.
  • the external TDF entity performs a congestion control policy, that is, the external TDF entity performs 30% packet loss on the service flow.
  • the PCRF formulates the corresponding PCC policy or QoS policy according to the level, and the PCRF entity sends the rule to the PCEF entity through the RAR message. Or BBERF (not shown) entity execution.
  • the PCRF entity decides to reduce the bandwidth parameter of the service flow, and the PCRF entity sends the congestion control policy to the PCEF entity through the Gx session or to the BBERF entity through the Gxx session.
  • the PCEF entity or the BBERF entity replies with a corresponding message, indicating that the congestion control policy is executed.
  • the PCEF entity receives the updated PCC rule, and modifies the bearer according to the congestion control policy.
  • the maximum bandwidth of the packet is reduced by controlling the bearer.
  • the BBERF entity receives an updated QoS rule (RAR QoS rule), and modifies the bearer according to the congestion control policy.
  • RAR QoS rule updated QoS rule
  • Steps 51 to 55 can refer to the corresponding processes of the prior art.
  • Steps 59 to 513 can refer to the corresponding processes of the prior art.
  • V-PCRF in Figure 5 is a functional entity in a roaming scenario, and is not described here.
  • the difference between the embodiment and the foregoing embodiment 5 is that the external TDF entity performs the congestion level detection of the user granularity, collects the packet congestion degree of all service flow granularities in the user granularity, and reports the congestion level to the PCRF entity.
  • Example 7 the external TDF entity performs the congestion level detection of the user granularity, collects the packet congestion degree of all service flow granularities in the user granularity, and reports the congestion level to the PCRF entity.
  • the scenario described in this embodiment is:
  • the PCRF performs policy decision according to the definition of the operator policy and the congestion level, and actively sends a congestion control policy;
  • the external TDF entity performs traffic flow granularity congestion detection, matches the corresponding congestion control policy, and executes The corresponding action.
  • the PCRF entity sends the congestion control policy to the PCEF entity through the Gx reference point (GTP-based S5/S8) or through the Gxx reference point.
  • the congestion control policy is enforced for the BBERF entity (PM IP-based S5/S8).
  • the congestion control method in this embodiment is described in detail, including: 61.
  • the UE After the IP-CAN session is established, the UE performs the service, and the downlink data packet is sent to the eNodeB.
  • the eNodeB performs packet forwarding to detect whether the current queue is congested as a congestion warning. When a congestion congestion warning occurs, the ECT is marked in the forwarded line data message.
  • the eNodeB sends the data packet to the UE by using the air interface resource, where the data packet carries the ECT identifier.
  • the UE receives the downlink data packet, and detects the ECT flag in the downlink data packet.
  • the UE simultaneously detects packet loss during the forwarding process of the downlink data packet.
  • the UE feeds back the ECT identification information of the eNodeB to the AF.
  • the AF marks the Re-echo-ECN in the downlink data packet according to the ECT identification information, and marks the Re-echo-Loss according to the retransmission information of the packet, and estimates that the appropriate Credit AF is used as the ConEx identification information. , marked in the downlink data message.
  • the downlink data packet is sent to the UE through the intermediate routing device.
  • the PCRF entity actively performs policy decision according to the operator policy and the user identity and a predefined set of congestion levels, and obtains a set of congestion control policies corresponding to a congestion level of a certain service flow. For example, for a certain service flow, when the ADC rule is sent, the PCRF entity simultaneously delivers a congestion control policy for the service flow. For the business flow of the Ding-the gold card user, the PCRF entity separately sets the corresponding packet loss rate for the four congestion levels of the ABCD. See Table 3.
  • the metric of the congestion level can be statically configured on the external TDF, or can be actively sent by the PCRF while the policy is being issued. Metrics for different levels of congestion can also be used as a set of information, as shown in Table 4.
  • the PCRF entity sends out a congestion control policy to the TDF entity.
  • the PCRF entity can use the TSR (TDF-Session-Request) message or the RAR message to actively send the congestion control policy to the external TDF entity, which is a set of policies with different congestion levels.
  • TSR TDF-Session-Request
  • the external TDF entity sends a response message to the PCRF.
  • the external TDF entity performs the service flow level detection on the line data packet.
  • the number of the ConEx identifier information is counted to measure the current congestion level. Assume that at this time, the external TDF entity detects that there is 50 ConEx-tagged packets in a certain service flow for a period of time, and the query table 4 can obtain the congestion level of C at this time.
  • the external TDF entity performs policy matching according to the calculated congestion level C, and performs policy control according to the matched result, that is, discards 10% of the current service flow.
  • the PCRF requires the TDF to report the congestion level.
  • the PCRF formulates a corresponding PCC policy or a QoS policy according to the level.
  • the PCRF entity delivers the rule to the PCEF entity or the BBERF (not shown) entity through the RAR message. For example, the PCRF entity decides to reduce the bandwidth parameter of the service flow, and the PCRF entity sends the policy to the PCEF entity through the Gx session or to the BBERF entity through the Gxx session.
  • the PCEF entity or the BBERF entity replies with a corresponding message, indicating that the policy execution is completed.
  • the PCEF entity receives the updated PCC rule
  • the BBERF entity receives the updated QoS rule, and modifies the bearer according to the policy.
  • the maximum bandwidth of the packet is reduced by controlling the bearer.
  • Steps 61 to 65 can refer to the corresponding processes of the prior art.
  • Steps 67 to 68, and steps 61 to 614, refer to the corresponding processes of the prior art.
  • the V-PCRF in Figure 6 is a functional entity in a roaming scenario, and is not described here.
  • the PCRF performs policy decision according to the definition of the operator policy and the congestion level, and actively issues the policy
  • the external TDF entity performs the user level congestion level detection, and matches Corresponding strategies and perform the corresponding actions. It can be seen from the technical solution provided by the foregoing embodiments of the present invention that the current traffic congestion is measured by the congestion level and the user priority to perform corresponding service flow control, and the user priority can be ensured according to the network congestion.
  • the storage medium may be a magnetic disk, an optical disk, or a read-only storage memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Abstract

La présente invention se rapporte à un procédé et à un dispositif de contrôle de congestion de réseau. Le procédé de contrôle de congestion de réseau selon l'invention consiste : à détecter un identifiant de congestion de réseau contenu dans un flux de trafic en circulation ; sur la base d'un résultat de la détection et de la priorité d'utilisation d'un équipement d'utilisateur (UE) qui reçoit le flux de trafic, à déterminer un niveau de congestion de réseau correspondant ; sur la base du niveau de congestion de réseau et de la priorité d'utilisation, à obtenir une stratégie de contrôle de congestion de réseau correspondante dans le but d'exécuter un contrôle de congestion de réseau sur le flux de trafic. Dans le procédé et le dispositif de contrôle de congestion de réseau décrits dans les modes de réalisation de la présente invention, le degré de congestion de réseau actuel est mesuré sur la base du niveau de congestion de réseau et de la priorité d'utilisation. Cela permet d'exécuter un contrôle correspondant sur le flux de trafic et de garantir ainsi la priorité d'utilisation en fonction de la condition de congestion du réseau.
PCT/CN2011/083712 2011-12-08 2011-12-08 Procédé et dispositif de contrôle de congestion de réseau WO2013082789A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2011/083712 WO2013082789A1 (fr) 2011-12-08 2011-12-08 Procédé et dispositif de contrôle de congestion de réseau
CN201180003285.9A CN103548381B (zh) 2011-12-08 2011-12-08 一种拥塞控制方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/083712 WO2013082789A1 (fr) 2011-12-08 2011-12-08 Procédé et dispositif de contrôle de congestion de réseau

Publications (1)

Publication Number Publication Date
WO2013082789A1 true WO2013082789A1 (fr) 2013-06-13

Family

ID=48573507

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/083712 WO2013082789A1 (fr) 2011-12-08 2011-12-08 Procédé et dispositif de contrôle de congestion de réseau

Country Status (2)

Country Link
CN (1) CN103548381B (fr)
WO (1) WO2013082789A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105208547A (zh) * 2014-06-26 2015-12-30 中兴通讯股份有限公司 拥塞处理方法、装置、ran rcaf及pcrf
CN105847168A (zh) * 2015-01-12 2016-08-10 华为技术有限公司 一种数据传输的方法、网络服务器、用户终端及系统
CN105992282A (zh) * 2015-03-02 2016-10-05 中国移动通信集团广东有限公司 一种调整服务质量参数的方法和装置
WO2018108093A1 (fr) * 2016-12-13 2018-06-21 中国移动通信有限公司研究院 Procédé et appareil de contrôle de congestion, et support de stockage informatique
CN111278055A (zh) * 2015-03-05 2020-06-12 思科技术公司 针对漫游用户的拥塞缓解
CN112383450A (zh) * 2020-11-30 2021-02-19 盛科网络（苏州）有限公司 一种网络拥塞检测方法及装置
WO2022057131A1 (fr) * 2020-09-18 2022-03-24 京信网络系统股份有限公司 Procédé et appareil de traitement d'encombrement de données, dispositif informatique, et support de stockage

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ES2745570T3 (es) * 2014-11-10 2020-03-02 Huawei Tech Co Ltd Método de notificación de congestión, sistema y dispositivo relacionados
CN105991468B (zh) * 2015-02-03 2019-06-25 中国移动通信集团公司 一种Diameter拥塞响应的处理方法及装置
CN110868357A (zh) * 2018-08-27 2020-03-06 中兴通讯股份有限公司 网络流量控制方法、vtep设备和存储介质
CN111385223B (zh) * 2018-12-28 2023-08-15 阿里巴巴集团控股有限公司 流控方法、设备、系统及存储介质
CN113141628B (zh) * 2020-01-20 2023-12-12 中国移动通信集团辽宁有限公司 小区拥塞处理方法、系统、上报装置及处理装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101110753A (zh) * 2006-07-20 2008-01-23 华为技术有限公司 基于拥塞预警的端到端的质量保证方法及系统
CN101188611A (zh) * 2007-11-21 2008-05-28 华为技术有限公司 拥塞通知方法、系统和节点设备
CN101965007A (zh) * 2009-07-21 2011-02-02 中兴通讯股份有限公司 用于基站的拥塞控制的方法和装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101272563B (zh) * 2008-05-04 2014-12-10 中兴通讯股份有限公司 建立集群通信的移动终端及利用其建立集群通信的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101110753A (zh) * 2006-07-20 2008-01-23 华为技术有限公司 基于拥塞预警的端到端的质量保证方法及系统
CN101188611A (zh) * 2007-11-21 2008-05-28 华为技术有限公司 拥塞通知方法、系统和节点设备
CN101965007A (zh) * 2009-07-21 2011-02-02 中兴通讯股份有限公司 用于基站的拥塞控制的方法和装置

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105208547A (zh) * 2014-06-26 2015-12-30 中兴通讯股份有限公司 拥塞处理方法、装置、ran rcaf及pcrf
CN105847168A (zh) * 2015-01-12 2016-08-10 华为技术有限公司 一种数据传输的方法、网络服务器、用户终端及系统
CN105992282A (zh) * 2015-03-02 2016-10-05 中国移动通信集团广东有限公司 一种调整服务质量参数的方法和装置
CN111278055A (zh) * 2015-03-05 2020-06-12 思科技术公司 针对漫游用户的拥塞缓解
CN111278055B (zh) * 2015-03-05 2023-12-19 思科技术公司 针对漫游用户的拥塞缓解
WO2018108093A1 (fr) * 2016-12-13 2018-06-21 中国移动通信有限公司研究院 Procédé et appareil de contrôle de congestion, et support de stockage informatique
CN108449279A (zh) * 2016-12-13 2018-08-24 中国移动通信有限公司研究院 拥塞控制方法及装置
WO2022057131A1 (fr) * 2020-09-18 2022-03-24 京信网络系统股份有限公司 Procédé et appareil de traitement d'encombrement de données, dispositif informatique, et support de stockage
CN112383450A (zh) * 2020-11-30 2021-02-19 盛科网络（苏州）有限公司 一种网络拥塞检测方法及装置

Also Published As

Publication number Publication date
CN103548381B (zh) 2016-12-28
CN103548381A (zh) 2014-01-29

Similar Documents

Publication Publication Date Title
WO2013082789A1 (fr) Procédé et dispositif de contrôle de congestion de réseau
EP3446464B1 (fr) Systèmes et procédé destinés à la surveillance de qualité de service, l'application de politique et la facturation dans un réseau de communication
JP6025926B2 (ja) サービスを制御する方法、装置及びシステム
US9509575B2 (en) Method, apparatus and system for marking service data packet
RU2654488C2 (ru) Объект mtc-iwf, объект pcrf и способ связи
JP5727091B2 (ja) インテリジェントな輻輳存在通知サービス
KR20130121166A (ko) 일시적인 제한 및 롤백
WO2012095402A1 (fr) Prise en charge par porteuses multiples en situation d'encombrement de trafic
US20150003246A1 (en) Radio access network triggered bearer modification procedure
EP3047672B1 (fr) Mesure d'encombrement et transmission pour des applications temps réel sensibles au retard
US20180213445A1 (en) Data transmission control method and apparatus based on wireless communications network
US10149186B2 (en) Node and method for monitoring an ability of a wireless device to receive downlink data
WO2014146502A1 (fr) Procédé et appareil de gestion de congestion de réseau d'accès radio, et procédé et système de gestion de stratégie de congestion
WO2014187227A1 (fr) Procédé et appareil de commande de transmission d'un flux de données
US11477691B2 (en) Dedicated bearer management
WO2012129992A1 (fr) Procédé de traitement de connectivité de données sponsorisées, et fonction d'imputation et de règles
WO2014176987A1 (fr) Procédé de commande de politique et élément de réseau
WO2013071860A1 (fr) Procédé de décision de règles et dispositif de réseau
WO2013151468A1 (fr) Procédé et système de gestion de file d'attente
WO2014110923A1 (fr) Procédé, appareil et système de traitement d'informations de réseau
WO2014180949A1 (fr) Procede d'exploitation d'un reseau et reseau associe
US20150257034A1 (en) Method and Apparatus for Combined Sequence Numbers for Drop Precedence Support
GB2572443A (en) Dedicated bearer management

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

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

Country of ref document: EP

Kind code of ref document: A1