WO2013159617A1 - 一种网络拥塞的处理方法、系统和控制网元 - Google Patents

一种网络拥塞的处理方法、系统和控制网元 Download PDF

Info

Publication number
WO2013159617A1
WO2013159617A1 PCT/CN2013/072977 CN2013072977W WO2013159617A1 WO 2013159617 A1 WO2013159617 A1 WO 2013159617A1 CN 2013072977 W CN2013072977 W CN 2013072977W WO 2013159617 A1 WO2013159617 A1 WO 2013159617A1
Authority
WO
WIPO (PCT)
Prior art keywords
traffic compression
network element
traffic
user
compression
Prior art date
Application number
PCT/CN2013/072977
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 中兴通讯股份有限公司
Publication of WO2013159617A1 publication Critical patent/WO2013159617A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/38—Flow control; Congestion control by adapting coding or compression rate

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, system, and control network element for processing network congestion.
  • FIG 1 is the Policy and Charging Control (PCC) defined by the 3rd Generation Partnership Project (3GPP).
  • PCC Policy and Charging Control
  • Application Function is used to provide the service information required for the control policy of the service.
  • IP Internet Protocol
  • port number used for service development are required for service development.
  • Information such as bandwidth and quality of service.
  • the Policy and Charging Rules Function is used to formulate QoS and charging policies for network resources.
  • the PCRF formulates the control policy, and needs to combine the service information received from the AF, the user subscription information received from the User Profile Repository (SPR), the policy configured by the operator, and the like.
  • the PCRF sends the control policy for the service to the Policy and Charging Enforcement Function (PCEF) or the Bearer Binding and Event Report Function (BBERF).
  • PCEF Policy and Charging Enforcement Function
  • BBERF Bearer Binding and Event Report Function
  • the PCRF can subscribe to the bearer layer related events to the PCEF and/or BBERF to be aware of the event when the bearer layer occurs, and to change the control strategy.
  • the PCEF is configured to execute a PCC rule delivered by the PCRF or preconfigured on the PCEF, and bind the rule to the matching bearer.
  • the PCEF detects the IP address transmitted on the network according to the quintuple information contained in the PCC rule. When the IP address is matched with the quintuple of a certain rule, the IP packet is corresponding according to the rule. QoS and billing control.
  • the PCRF subscribes to the PCEF for the relevant bearer layer event, and when the event occurs, the PCEF needs to go to the PCRF. Report the incident in a timely manner.
  • the BBERF mainly receives the QoS rules delivered by the PCRF and binds the rules to the matching bearers.
  • the BBERF detects the IP ⁇ message transmitted on the network according to the quintuple information contained in the rule.
  • the QoS control policy defined by the rule is executed on the IP packet.
  • the PCRF subscribes to the relevant bearer layer event to the BBERF, and after the event occurs, the BBERF needs to report the event to the PCRF in time.
  • SPR is used to save user subscription information and provide necessary user subscription information for PCF rules for PCRF.
  • OCS Online Charging System
  • OFCS Offline Charging System
  • the PCRF interacts with PCEF and BBERF through the Gx and Gxa interfaces respectively.
  • the PCRF needs to establish a gateway control session and an IP-CAN session with the BBERF and the PCEF before the user officially conducts the specific service, and establish a gateway control session and an IP-CAN session association to ensure that the specific service data flow is in the BBERF. Consistency with the implementation of the control strategy on the PCEF.
  • the PCRF formulates a corresponding policy for the service data flow included in the service according to the service layer negotiation service information, the user subscription information, and the operator policy, and includes the information of the quintuple information and the authorized bandwidth of the identifier flow.
  • the policy is sent to the BBERF in the form of a QoS rule and sent to the PCEF in the form of a PCC rule.
  • the IP packet arrives at the PCEF or BBERF, the IP packet is matched according to the quintuple information in the rule, and the matched IP packet is transmitted using the corresponding bearer, and corresponding charging is performed to implement the service. Effective control.
  • changes in business information occur, for example, a certain service data flow is terminated, and the network resources occupied by the service can be released in real time through the PCC to achieve dynamic QoS control for the service.
  • RFC2616 has defined a variety of headers for terminal devices.
  • the Accept-Encoding field defines the encoding mechanism that the client can understand and supports traffic compression. If you need to install the appropriate browser software for the terminal device that cannot support the traffic compression, you can enable the compression function for the terminal device that does not support the compression mechanism.
  • the Content-Encoding field needs to be included in the HTTP packet returned to the terminal device to indicate that the compressed content is returned to the client browser, and the client can compress the data accordingly. The content is decompressed to get the required data.
  • the HTTP 1.1 web content can be compressed into a gzip format for transmission, or a 16 bit TIFF image can be re-encoded into an 8-bit TIFF image transmission.
  • traffic compression mechanism can also be seen for terminal capabilities and networks. There is a dependency on capabilities, and not all terminals and networks support this mechanism. At the same time, traffic compression will also cause some data loss and affect the user experience. Therefore, the traffic compression mechanism is not a mandatory function of the network, but the operator needs to selectively use the user and the network.
  • the embodiments of the present invention provide a method, a system, and a control network element for processing network congestion, which implement network congestion processing, thereby reducing network congestion and ensuring user service experience.
  • the processing method of the network congestion includes: Controlling whether the network element initiates traffic compression, and if it is started, sending a traffic compression indication to the network element supporting the traffic compression;
  • the network element supporting the traffic compression starts traffic compression according to the traffic compression indication.
  • the foregoing method may further have the following feature: the controlling the network element deciding whether to initiate traffic compression comprises: the controlling network element determining whether to initiate traffic compression according to one or a combination of the following information: user information, user equipment information, application service information, Access network type, location information, time, network congestion.
  • the above method may also have the following features: the user information includes a user level; the user equipment information includes a capability of the user equipment to support traffic compression and/or a screen size of the user equipment; and the application service information includes a service type.
  • the location information includes the location where the user is currently located.
  • the traffic compression indication includes: an indication of starting traffic compression, and/or a traffic compression mode.
  • control network element is a policy and charging rule function PCRF.
  • the foregoing method may also have the following features:
  • the network element supporting the traffic compression is one of the following: a policy and a charging execution function, a PCEF, a bearer binding, and an event reporting function, a BBERF, a transmission detection function, a TDF, and an application function AF.
  • the control network element includes: a decision unit and a sending unit, where:
  • the decision unit is configured to: determine whether to initiate traffic compression
  • the sending unit is configured to: after the decision unit initiates the traffic compression, send a traffic compression indication to the network element that supports the traffic compression.
  • the control network element may further have the following feature, the determining unit is configured to decide whether to initiate traffic compression according to one or a combination of the following information: user information, user equipment information, application service information, access network type, location information, Time, network congestion.
  • the foregoing control network element may also have the following features: the user information includes a user level; the user equipment information includes a capability of the user equipment to support traffic compression and/or a screen size of the user equipment; and the application service information includes a service. Type, the location information includes the user currently located s position.
  • the control network element may also have the following features: the traffic compression indication includes an indication to initiate traffic compression, and/or a traffic compression mode.
  • control network element may also have the following features: the control network element is a policy and charging rule function PCRF.
  • the network congestion processing system includes the foregoing control network element and a network element supporting traffic compression, where:
  • the network element supporting the traffic compression is configured to: after receiving the traffic compression indication sent by the control network element, start traffic compression according to the traffic compression indication.
  • the above system may also have the following features:
  • the network element supporting the traffic compression is one of the following: policy and charging execution function PCEF, bearer binding and event reporting function BBERF, transmission detection function TDF, application function AF.
  • the embodiments of the present invention provide a congestion processing method and system, so that the network can perform traffic startup compression based on the capabilities of the user equipment, network congestion, and the like, thereby reducing network congestion and reducing network load.
  • FIG. 2 is a flow chart of Embodiment 1 of the present invention.
  • Embodiment 2 of the present invention is a flow chart of Embodiment 2 of the present invention.
  • FIG. 5 is a flow chart of Embodiment 4 of the present invention.
  • FIG. 6 is a block diagram of a control network element in an embodiment of the present invention. Preferred embodiment of the invention
  • An embodiment of the present invention provides a method for processing network congestion, including:
  • the control network element determines whether the traffic compression is started. If the traffic is compressed, the network element that supports the traffic compression sends the traffic compression indication, and the network element supporting the traffic compression starts the traffic compression according to the traffic compression indication.
  • control network element determines whether to initiate traffic compression, including: controlling the network element according to user information, user equipment information, application service information, access network type, location information, time, network congestion, or one or more Any combination of decisions to initiate traffic compression.
  • the present invention is not limited to the above information, and may also decide whether to initiate traffic compression based on other information.
  • the user information includes a user level
  • the user equipment information includes whether the user equipment supports traffic compression
  • the device screen size includes whether the user equipment supports traffic compression
  • the application service information includes a service type
  • the location information indicates a current location of the user.
  • the traffic compression indication comprises: an indication of starting traffic compression, and/or a traffic compression mode.
  • the control network element may be a policy and charging rule function PCRF.
  • the network element supporting the traffic compression may be one of the following: a policy and a charging execution function.
  • PCEF bearer binding and event reporting functions BBERF, transmission detection function TDF, application function AF. It can also be other network elements that support traffic compression.
  • the PCRF determines whether the capability of the user equipment is compressed for the traffic carried by the user according to the current network congestion. The process is described as follows:
  • the user terminal device is attached to the network, initiates an attach procedure, and sends the capability of the user equipment to the network, where the user equipment capability is used to describe whether to support traffic compression, the screen size of the user equipment, and the like;
  • the PCEF After receiving the attach request, the PCEF initiates an IP-CAN session establishment request to the PCRF, and sends the user equipment capability to the PCRF;
  • the PCRF obtains user subscription information, such as a user level, a bandwidth allocated to the user, and a service that the user is allowed to access, according to the user identifier carried in the request message. 204. The PCRF returns a successful response to the IP-CAN session establishment to the PCEF;
  • the terminal device conducts a service, and completes service negotiation with the application server;
  • the AF sends the service negotiation information to the PCRF.
  • the service negotiation information includes a media type included in the service, a bandwidth described by the service flow, and a codec mode used;
  • the PCRF After receiving the service negotiation information, the PCRF obtains the network congestion status from the network management center.
  • the network management center is used to calculate network traffic status and analyze network congestion status.
  • the network management center is used to manage the network congestion state.
  • other network elements that are aware of the network congestion status may also be used to report the network congestion status to the PCRF.
  • the implementation of the network congestion state may be performed by the PCRF.
  • the network management center may periodically report to the PCRF; or the network management center may report to the PCRF according to the PCRF request; or set a traffic threshold, when the traffic in the network exceeds the When the threshold is stated, the network management center reports to the PCRF;
  • the PCRF uses the network QoS resources for the service to make policy decisions. Since the network is in a congested state at step 207, and the user equipment capability information indicates that the terminal device supports traffic compression, and the terminal screen is small, even if the service data compression has less impact on the user experience, the PCRF decision is as described.
  • Service start traffic compression
  • the PCRF returns an indication of traffic compression to the AF, indicating that the traffic compression transmission is initiated;
  • the renegotiation of the service between the application server and the terminal including the negotiation of the re-used coding, etc.;
  • the AF re-delivers the service information after negotiation to the PCRF;
  • the PCRF makes policy decisions for the service again according to service information and the like;
  • the PCRF sends the authorized QoS policy to the PCEF for execution
  • the terminal device and the application server initiate traffic compression transmission to the service data flow in a negotiated manner.
  • Embodiment 2 The second embodiment describes that a gateway dedicated to traffic compression is deployed in the network, and data exchanged between the user and the network passes through the compression gateway.
  • the PCRF can decide to send a compression indication to the compression gateway as needed to implement traffic compression. The process is described as follows:
  • the user terminal device is attached to the network, initiates an attach procedure, and sends the capability of the user equipment to the network, where the user equipment capability is used to describe whether to support traffic compression, the screen size of the user equipment, and the like;
  • the PCEF After receiving the attach request, the PCEF initiates an IP-CAN session establishment request to the PCRF, and sends the user equipment capability to the PCRF;
  • the PCRF obtains the user subscription information, such as the user level, the bandwidth allocated to the user, and the service that the user is allowed to access, from the SPR;
  • the PCRF returns a successful response to the IP-CAN session establishment to the PCEF;
  • the terminal device conducts a service, and completes service negotiation with the application server;
  • the AF sends the service negotiation information to the PCRF;
  • the PCRF After receiving the service negotiation information, the PCRF obtains the network congestion status from the network management center.
  • the implementation process is the same as step 207;
  • the PCRF uses the network QoS resources for the service to make policy decisions. Since the network is in a congested state at step 307, the PCRF decision initiates traffic compression for the service;
  • the PCRF sends the authorized QoS policy to the PCEF for execution
  • the PCRF sends an indication of starting traffic compression to the compression gateway device
  • the compression gateway initiates traffic compression on the service data flow
  • the service data of the interaction between the terminal device and the application server is compressed and transmitted.
  • the bearer network element may be PCEF, BBERF, TDF (Traffic) Detection Function, transmission detection function).
  • PCEF Traffic
  • BBERF Bit Rate Average
  • TDF Traffic Detection Function
  • transmission detection function transmission detection function
  • PCRF PCRF for initiating the traffic compression of the decision network determines whether to start the traffic compression mechanism according to the capabilities of the user equipment, the user level, and the network congestion, and sends a startup traffic compression indication to the PCEF. The process is described as follows:
  • the terminal device is attached to the network, and the user equipment capability is sent to the network;
  • the PCEF When the user is attached to the network, the PCEF initiates an IP-CAN session establishment request to the PCRF, and reports the user equipment capability and the user information to the PCRF through the request, for example, whether the user equipment supports traffic compression, and the user equipment Screen size, etc.
  • the PCRF receives the IP-CAN session establishment request, and obtains subscription information of the corresponding user from the SPR according to the user information, such as a user level, a subscription service of the user, and a subscription QoS of the user.
  • the PCRF saves the above information received from the PCEF, SPR, and returns a successful response to the IP-CAN session establishment to the PCEF, and the PCRF subscribes to the PCEF for network congestion, requiring the PCEF to congest the congestion when the bearer network is congested. The status is reported to the PCRF;
  • the PCRF acquires a network congestion state from the PCEF. If the bearer network element (for example, PCEF) can sense the network congestion status, the PCRF can obtain the network congestion status by subscribing to the PCEF by the network congestion status event.
  • the bearer network element for example, PCEF
  • the PCEF reports the congestion status to the PCRF. This step is optional. If there is no congestion on the network, this step will not occur;
  • the user conducts business negotiations between the business and the AF;
  • the AF sends the service negotiation information to the PCRF, where the service information includes a service identifier, a service QoS requirement, and the like;
  • the PCRF After receiving the service information, the PCRF combines user information, user equipment information, network congestion, and the like to determine whether to initiate traffic compression for the service decision; for example:
  • the user equipment uses a small-size screen device, and the user is a bronze user.
  • the network is in a congested state, and the PCRF determines the traffic compression of the service initiated by the user.
  • the PCRF makes policy decisions on the QoS used by the service according to the service information and the user subscription information.
  • the PCRF sends the control policy to the PCEF, and sends the service to the PCEF.
  • An indication of traffic compression
  • the PCEF After receiving the control policy, the PCEF installs the policy, and starts the traffic compression of the service initiated by the user according to the indication of the startup traffic compression delivered by the PCRF.
  • the PCEF supports the traffic compression function. If the PCEF does not support the traffic compression function, the PCEF needs to provide the indication to the network element supporting the compression function after receiving the indication of the start traffic compression delivered by the PCRF.
  • This embodiment describes whether the PCRF determines whether to initiate traffic compression for the service detected by the TDF according to service information, network congestion, and the like. For example, the user initiates a video download through the smart terminal. Since the download service will occupy a large amount of network resources, it may even affect other services transmitted on the network. If the smart terminal used by the user to download the video is a small screen terminal, the compression of the download service is started in combination with the size of the smart terminal, and even if some data is lost (for example, the high definition is compressed into a normal), the user experience is not experienced.
  • This example describes the combination of the capabilities of the terminal device and the start of traffic compression for the video download service. The process is described as follows:
  • the terminal device is attached to the network, and the user equipment capability is sent to the network;
  • the PCEF initiates an IP-CAN session establishment request to the PCRF, and reports the user equipment capability and the user information to the PCRF through the request, for example, whether the user equipment supports traffic compression, and the user equipment Screen size, etc.
  • the PCRF receives the IP-CAN session establishment request, and obtains subscription information of the corresponding user from the SPR according to the user information, such as a user level, a subscription service of the user, and a subscription QoS of the user.
  • the PCRF saves the above information received from the PCEF, SPR, and returns a successful response to the IP-CAN session establishment to the PCEF, and the PCRF subscribes to the PCEF for network congestion, requiring the PCEF to congest the congestion when the bearer network is congested. The status is reported to the PCRF;
  • a TDF session is established between the PCRF and the TDF, and the ADC is sent (Application Detection And control, application detection and control) rules, requiring TDF to report P2P download services when reporting;
  • the TDF detects the download application
  • the TDF reports the detected service information to the PCRF
  • the PCRF obtains network congestion status from the network management center
  • the capabilities of the user equipment eg, whether to support traffic compression, the screen size of the terminal device, etc.
  • the PCRF decision initiates traffic compression for the service
  • the PCRF sends a control policy to the TDF, and sends a traffic compression indication.
  • the indication of initiating traffic compression may indicate a specific traffic compression mode. If the gateway that performs traffic compression can support multiple traffic compression modes, the PCRF should specify the specific traffic compression mode when issuing the control policy.
  • the PCRF sends a control policy for the service to the PCEF, and sends an indication of starting traffic compression. ;
  • the PCEF starts to perform traffic compression on the download service according to the startup traffic compression indication sent by the PCRF.
  • the embodiment of the present invention further provides a control network element.
  • the method includes: a decision unit and a sending unit, where:
  • the decision unit is configured to: determine whether to initiate traffic compression
  • the sending unit is configured to: after the decision unit initiates the traffic compression, send a traffic compression indication to the network element that supports the traffic compression.
  • the determining, by the determining unit, whether to initiate traffic compression includes:
  • the decision unit decides whether to initiate traffic compression according to one of the following information or a combination thereof: user information, user equipment information, application service information, access network type, location information, time, network congestion.
  • the user information includes a user level; the user equipment information includes a capability of the user equipment to support traffic compression and/or a screen size of the user equipment; the application service information includes a service type, and the location information includes a user.
  • the current location includes a user level; the user equipment information includes a capability of the user equipment to support traffic compression and/or a screen size of the user equipment; the application service information includes a service type, and the location information includes a user.
  • the current location includes a user level; the user equipment information includes a capability of the user equipment to support traffic compression and/or a screen size of the user equipment; the application service information includes a service type, and the location information includes a user.
  • the current location includes a user level; the user equipment information includes a capability of the user equipment to support traffic compression and/or a screen size of the user equipment; the application service information includes a service type, and the location information includes a user.
  • the current location includes a user level; the user equipment information includes a capability of the user equipment to
  • the traffic compression indication includes an indication to initiate traffic compression, and/or a traffic compression mode.
  • the control network element is a policy and charging rule function PCRF.
  • the embodiment of the present invention further provides a network congestion processing system, including: the foregoing control network element and a network element supporting traffic compression, where:
  • the network element supporting the traffic compression is configured to: after receiving the traffic compression indication sent by the control network element, start traffic compression according to the traffic compression indication.
  • the present invention can also support the PCRF to initiate traffic compression based on the geographic location, time, and the like of the user equipment. For example, for some hotspot areas, such as stations, during the peak of the traffic flow, the network automatically starts the traffic compression mechanism.
  • the implementation is: When the user attaches to the network, the PCEF will user equipment capability, user location information (cell information, base station information). And reported to the PCRF.
  • the PCRF makes a policy decision for the user to conduct the service, it is determined according to the user location information whether the user is located in the feature area, and whether the current time is the peak time of the work. If the time is the peak time and the user is in the hotspot area, the PCRF decides to start traffic compression for the service, and delivers an indication of starting traffic compression to the network element supporting the traffic compression. Accordingly, traffic compression is initiated for the service.
  • the PCRF is used to determine whether the service is initiated by the user to initiate traffic compression, and may also be replaced by other network elements that support the function.
  • modules or steps of the present invention described above can be implemented with a general purpose computing device, which can be centralized on a single computing device, or distributed. Alternatively, on a network of computing devices, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, The steps shown or described may be performed in an order different than that herein, or they may be separately fabricated into individual integrated circuit modules, or a plurality of the modules or steps may be implemented as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.
  • the embodiments of the present invention provide a congestion processing method and system, so that the network can perform traffic startup compression based on the capabilities of the user equipment, network congestion, and the like, thereby reducing network congestion and reducing network load. .

Abstract

本发明实施例公开了一种网络拥塞的处理方法、系统及控制网元，所述方法包括控制网元决策是否启动流量压缩，如果启动，则向支持流量压缩的网元下发流量压缩指示；所述支持流量压缩的网元根据所述流量压缩指示，启动流量压缩。

Description

一种网络拥塞的处理方法、 系统和控制网元
技术领域
本发明涉及通信领域， 具体的， 涉及一种网络拥塞的处理方法、 系统和 控制网元。
背景技术
图 1是第三代合作伙伴计划 （ 3rd Generation Partnership Project, 简称为 3GPP ) 定义的策略和计费控制架构 （Policy and Charging Control, 简称为 PCC ) 。
应用功能（Application Function, 简称为 AF )用于提供为业务制定控制 策略所需的业务信息， 例如业务开展所使用的因特网协议（Internet Protocol, 简称为 IP )地址、 端口号， 业务开展所需要的带宽、 服务质量（Quality of Service )等信息。
策略和计费规则功能 （Policy and Charging Rules Function , 简称为 PCRF ) 为业务使用网络资源进行 QoS和计费策略的制订。 PCRF制定所述控制策略 需要结合从 AF接收的业务信息， 从用户签约数据库 （Subscription Profile Repository, 简称为 SPR )接收的用户签约信息， 运营商配置的策略等。 PCRF 将为业务制定的控制策略下发给策略和计费执行功能 （Policy and Charging Enforcement Function, 简称为 PCEF )或者承载绑定和事件上报功能（ Bearer Binding and Event Report Function , 简称为 BBERF )执行。 同时 PCRF可以向 PCEF和 /或 BBERF订阅承载层相关事件，以便当承载层发生所述事件时及时 感知， 并更改控制策略。
PCEF用于执行 PCRF下发的或者 PCEF上预配置的 PCC规则， 并将所 述规则绑定到与之匹配的承载上。 PCEF根据 PCC规则中包含五元组信息对 网络上传输的 IP ^艮文进行检测， 当 IP ^艮文和某一个规则的五元组匹配的时 候，则按照规则对所述 IP报文进行相应的 QoS和计费控制。同时如果当 PCRF 向 PCEF订阅了相关承载层事件，并且当所述事件发生后， PCEF需要向 PCRF 及时上报所述事件。
当网络釆用代理移动性 IP( Proxy Mobility Internet Protocol,简称为 PMIP ) 协议的时候，网络需要配置 BBERF功能。 BBERF主要接收 PCRF下发的 QoS 规则， 并将所述规则绑定到与之匹配的承载上。 BBERF根据规则中包含的五 元组信息对网络上传输的 IP ^艮文进行检测， 当 IP ^艮文与五元组匹配的时候， 对所述 IP报文执行规则定义的 QoS控制策略。 同时如果当 PCRF向 BBERF 订阅了相关承载层事件， 并且当所述事件发生后， BBERF需要向 PCRF及时 上报所述事件。
SPR用于保存用户签约信息， 为 PCRF制订 PCC规则提供必须的用户签 约信息。 在线计费系统 （Online Charging System, 简称为 OCS)和离线计费系 统（ Offline Charging System, 简称为 OFCS )分别用于离线和在线计费。
PCRF分别通过 Gx、 Gxa接口实现和 PCEF、 BBERF的交互。
PCC架构对承载网络上传输的业务实施策略控制的原理如下：
首先 PCRF在用户正式开展具体业务之前， 需要和 BBERF、 PCEF之间 分别建立网关控制会话、 IP-CAN会话， 并要建立网关控制会话和 IP-CAN会 话关联，以保证针对特定业务数据流在 BBERF和 PCEF上实施控制策略的一 致性。
此后在业务开展过程中， 由 PCRF根据应用层协商业务信息、 用户签约 信息、 运营商策略等为业务包含的业务数据流制订相应的策略， 包含标识流 的五元组信息、 授权带宽等信息。 并将策略以 QoS规则形式下发给 BBERF, 以 PCC规则形式下发给 PCEF。 当 IP报文到达 PCEF、 BBERF时， 首先根据 规则中的五元组信息匹配 IP报文， 并将匹配上的 IP报文使用对应的承载进 行传输， 并进行相应的计费， 以实现对业务的有效控制。 另外当业务开展过 程中， 发生业务信息的更改， 例如终止了某一业务数据流， 通过 PCC也可以 实时的释放业务所占的网络资源， 达到对业务进行动态 QoS控制的目的。
随着网络和终端设备的发展，大量用户通过智能终端接入 Internet网络访 问各种数据业务， 一方面网络上的数据业务还在不断的丰富， 例如各种视频 服务， 游戏服务等， 另一方面使用智能终端的上网用户还在爆发式的增长。 这对运营商的网络运营带来了冲击和挑战。大量的数据业务增加了网络负荷， 甚至造成了网络拥塞（例如在车站、 码头等热点区域） 。 大量的数据业务甚 至侵占了语音服务的资源， 使得传统的语音服务都得不到可靠的 QoS保证。 因此如何调整网络流量， 减轻网络负荷， 减少网络拥塞是运营商需要面临的 问题。
当然运营商可以通过增加投资， 扩充网络容量的方式来解决上述问题， 这将增加投资成本。 另一种方式是用压缩流量的方式减少网络负荷或拥塞。
RFC2616已经为终端设备定义了多种头标，其中 Accept-Encoding字段定 义了客户端可以理解的编码机制， 支持流量压缩。 如果对于不能支持流量压 缩的终端设备， 需要加装合适的浏览器软件， 可以使原本不支持压缩机制的 终端设备开启压缩功能。 而对于网络设备， 如果需要对流量进行压缩， 则需 要在返回给终端设备的 HTTP包中包含 Content-Encoding字段，以表明给客户 端浏览器返回了被压缩的内容， 客户端据此可以对压缩内容进行解压得到所 需的数据。 通过上述机制可以减少网络的数据流量， 例如可以将 HTTP 1.1的 web内容压缩成 gzip格式进行传送， 或者将一个 16 bit的 TIFF图像经过重新 编码压缩成一个只有 8 bit的 TIFF图像传送。
通过这种流量压缩机制使得运营商可以在网络不扩容的情况下解决网络 拥塞问题， 有助于运营商节省硬件投资， 但是从上述流量压缩的介绍也可以 看出流量压缩机制对终端能力和网络能力存在依赖， 并非所有终端和网络都 支持这种机制。 同时流量压缩也会造成部分数据丟失， 影响用户体验。 因此 流量压缩机制并非网络必选功能， 而是运营商需要根据用户和网络情况有选 择性的运用。
发明内容
本发明实施例提供一种网络拥塞的处理方法、 系统和控制网元， 实现网 络拥塞处理， 达到减少网络拥塞， 保证用户业务体验的目的。
所述网络拥塞的处理方法， 包括： 控制网元决策是否启动流量压缩， 如果启动， 则向支持流量压缩的网元 下发流量压缩指示；
所述支持流量压缩的网元根据所述流量压缩指示， 启动流量压缩。
上述方法还可具有以下特点，所述控制网元决策是否启动流量压缩包括： 所述控制网元根据如下信息之一或其组合决策是否启动流量压缩： 用户 信息， 用户设备信息， 应用服务信息， 接入网络类型， 位置信息， 时间， 网 络拥塞情况。
上述方法还可具有以下特点， 所述用户信息包括用户等级； 所述用户设 备信息包括用户设备是否支持流量压缩的能力和 /或所述用户设备的屏幕尺 寸； 所述应用服务信息包括服务类型， 所述位置信息包括用户当前所处的位 置。
上述方法还可具有以下特点， 所述流量压缩指示包括： 启动流量压缩的 指示， 和 /或， 流量压缩方式。
上述方法还可具有以下特点， 所述控制网元为策略和计费规则功能 PCRF。
上述方法还可具有以下特点， 所述支持流量压缩的网元为如下之一： 策 略和计费执行功能 PCEF、 承载绑定和事件上报功能 BBERF、 传输检测功能 TDF、 应用功能 AF。
所述控制网元， 包括： 决策单元和发送单元， 其中：
所述决策单元设置为， 决策是否启动流量压缩；
所述发送单元设置为， 所述决策单元决策启动流量压缩后， 向支持流量 压缩的网元下发流量压缩指示。
上述控制网元还可具有以下特点， 所述决策单元是设置为根据如下信息 之一或其组合决策是否启动流量压缩： 用户信息， 用户设备信息， 应用服务 信息， 接入网络类型， 位置信息， 时间， 网络拥塞情况。
上述控制网元还可具有以下特点， 所述用户信息包括用户等级； 所述用 户设备信息包括用户设备是否支持流量压缩的能力和 /或所述用户设备的屏 幕尺寸； 所述应用服务信息包括服务类型， 所述位置信息包括用户当前所处 的位置。
上述控制网元还可具有以下特点， 所述流量压缩指示包括启动流量压缩 的指示， 和 /或， 流量压缩方式。
上述控制网元还可具有以下特点， 所述控制网元为策略和计费规则功能 PCRF。
所述网络拥塞的处理系统， 包括上述控制网元和支持流量压缩的网元， 其中：
所述支持流量压缩的网元设置为， 收到所述控制网元发送的流量压缩指 示后， 4艮据所述流量压缩指示， 启动流量压缩。
上述系统还可具有以下特点， 所述支持流量压缩的网元为如下之一： 策 略和计费执行功能 PCEF、 承载绑定和事件上报功能 BBERF、 传输检测功能 TDF、 应用功能 AF。
本发明实施例提供了一种拥塞处理方法和系统， 使得网络可以根据用户 设备的能力， 网络拥塞情况等决策是否为用户开展的业务启动流量压缩， 从 而可以达到减少网络拥塞， 减轻网络负荷的目的。 附图概述
图 1是相关技术的 PCC架构图；
图 2是本发明实施例一的流程图；
图 3是本发明实施例二的流程图；
图 4是本发明实施例三的流程图；
图 5是本发明实施例四的流程图；
图 6是本发明实施例控制网元框图。 本发明的较佳实施方式
下文中将结合附图对本发明的实施例进行详细说明。 需要说明的是， 在 不冲突的情况下， 本申请中的实施例及实施例中的特征可以相互任意组合。 本发明实施例提供一种网络拥塞的处理方法， 包括：
控制网元决策是否启动流量压缩， 如果启动， 向支持流量压缩的网元下 发流量压缩指示， 所述支持流量压缩的网元根据所述流量压缩指示， 启动流 量压缩。
较佳的， 所述控制网元决策是否启动流量压缩， 包括： 控制网元根据用 户信息， 用户设备信息， 应用服务信息， 接入网络类型， 位置信息， 时间， 网络拥塞情况的一种或几种的任意组合决策是否启动流量压缩。 本发明不限 于上述信息， 也可根据其他信息决策是否启动流量压缩。
所述用户信息包括用户等级， 用户设备信息包括用户设备是否支持流量 压缩的能力， 设备屏幕尺寸， 应用服务信息包括服务类型， 位置信息表示用 户当前所处的位置。
较佳的， 所述流量压缩指示包括： 启动流量压缩的指示， 和 /或， 流量压 缩方式。
其中， 所述控制网元可以为策略和计费规则功能 PCRF。
其中， 所述支持流量压缩的网元可以为如下之一： 策略和计费执行功能
PCEF、承载绑定和事件上报功能 BBERF、传输检测功能 TDF、应用功能 AF。 也可以是其他支持流量压缩的网元。
实施例一
本实施例描述的是 PCRF根据当前网络拥塞情况， 用户终端设备的能力 决策是否为用户开展的业务进行流量压缩传输， 其流程描述如下：
201. 用户终端设备附着到网络， 发起附着流程， 并将用户设备的能力发 送给网络， 所述用户设备能力用于描述是否支持流量压缩， 用户设备的屏幕 尺寸等；
202. PCEF收到附着请求后， 向 PCRF发起 IP-CAN会话建立请求， 并将 所述用户设备能力发送给 PCRF;
203. PCRF根据请求消息中携带的用户标识， 从 SPR中获取用户签约信 息， 例如用户等级， 分配给用户的带宽， 允许用户访问的业务等信息； 204. PCRF向 PCEF返回 IP-CAN会话建立成功的响应；
205.终端设备开展业务， 完成和应用服务器之间的业务协商；
206. AF将业务协商信息下发给 PCRF。 所述业务协商信息包括业务包含 的媒体类型， 业务流所述的带宽， 以及釆用的编解码方式等；
207. PCRF收到所述业务协商信息之后， 从网管中心获取网络拥塞状况。 所述网管中心用于统计网络流量状况并分析网络拥塞状态。 本实施例中釆用 所述网管中心管理网络拥塞状态， 实际运营中， 具备感知网络拥塞状态的其 他网元也可以应用于向 PCRF报告网络拥塞状态；
所述 PCRF获取网络拥塞状态的实现可以有多种， 例如可以由网管中心 定时主动向 PCRF报告； 或者应 PCRF请求， 网管中心向 PCRF报告； 或者 设置一个流量阔值， 当网络中的流量超出所述阔值时，所述网管中心向 PCRF 报告；
208. 根据业务协商信息， 网络拥塞状态， 用户设备能力信息， 用户签约 信息以及运营策略， PCRF为所述业务使用网络 QoS资源进行策略决策。 由 于从 207步获取此时网络处于拥塞状态， 并且用户设备能力信息指示所述终 端设备支持流量压缩， 且终端屏幕较小， 即使业务数据压缩也对用户体验影 响较小， 因此 PCRF决策为所述业务启动流量压缩；
209. PCRF向 AF返回流量压缩的指示， 指示启动流量压缩传输；
210. 根据所述指示， 应用服务器和终端之间进行业务的重协商， 包括重 新使用的编码等方式的协商；
211. AF将协商之后的业务信息重新下发给 PCRF;
212. PCRF根据业务信息等再次对所述业务进行策略决策；
213. PCRF将授权 QoS策略下发给 PCEF执行；
214. 终端设备和应用服务器之间按照协商的方式对业务数据流启动流 量压缩传输。
实施例二 本实施例二描述的是网络中部署有专门支持流量压缩的网关， 用户和网 络交互的数据都经过所述压缩网关。根据需要， PCRF可以决策向压缩网关发 送压缩指示， 以此实现流量压缩。 其流程实现如下描述：
301. 用户终端设备附着到网络， 发起附着流程， 并将用户设备的能力发 送给网络， 所述用户设备能力用于描述是否支持流量压缩， 用户设备的屏幕 尺寸等；
302. PCEF收到附着请求后， 向 PCRF发起 IP-CAN会话建立请求， 并将 所述用户设备能力发送给 PCRF;
303. 根据请求消息中携带的用户标识， PCRF从 SPR中获取用户签约信 息， 例如用户等级， 分配给用户的带宽， 允许用户访问的业务等信息；
304. PCRF向 PCEF返回 IP-CAN会话建立成功的响应；
305.终端设备开展业务， 完成和应用服务器之间的业务协商；
306. AF将业务协商信息下发给 PCRF;
307. PCRF收到所述业务协商信息之后， 从网管中心获取网络拥塞状况。 其实现过程和步骤 207相同；
308. 根据业务协商信息， 网络拥塞状态， 用户设备能力信息， 用户签约 信息以及运营策略， PCRF为所述业务使用网络 QoS资源进行策略决策。 由 于从 307步获取此时网络处于拥塞状态， 因此 PCRF决策为所述业务启动流 量压缩；
309. PCRF将授权 QoS策略下发给 PCEF执行；
310. 同时 PCRF向所述压缩网关设备下发启动流量压缩的指示；
311. 4艮据所述指示， 压缩网关对所述业务数据流启动流量压缩；
312. 终端设备和应用服务器之间的交互的所述业务数据进行压缩传送。
实施例三
本实施例描述的是现有承载网络网元如果支持流量压缩功能， 则釆用所 述网元实现流量压缩。 所述承载网络网元可以是 PCEF, BBERF, TDF(Traffic Detection Function,传输检测功能)。为了描述方便，本实施例仅以 PCEF为例。 用于决策网络启动流量压缩的 PCRF根据用户设备的能力， 用户等级以及网 络拥塞情况来决定是否启动流量压缩机制， 并向 PCEF下发启动流量压缩指 示， 其流程描述如下：
401. 终端设备附着到网络， 将用户设备能力发送给网络；
402. 当用户附着到网络的时候， PCEF向 PCRF发起 IP-CAN会话建立请 求， 通过所述请求将用户设备能力， 以及用户信息上报给 PCRF, 例如用户设 备是否支持流量压缩， 所述用户设备的屏幕尺寸等；
403. PCRF接收到所述 IP-CAN会话建立请求， 根据用户信息从 SPR获 取对应用户的签约信息， 例如用户等级， 用户的签约业务， 用户的签约 QoS 等；
404. PCRF保存从 PCEF, SPR收到的上述信息 ,并向 PCEF返回 IP-CAN 会话建立成功的响应， 同时 PCRF向 PCEF订阅网络拥塞情况， 要求当承载 网络发生拥塞的时候， PCEF将所述拥塞状态上报给 PCRF;
本实施例描述的是 PCRF从 PCEF获取网络拥塞状态。 如果承载网络网 元（以 PCEF为例 )能够感知网络拥塞状况， 则 PCRF可以通过向 PCEF订阅 网络拥塞状态事件来获取网络拥塞状态；
405. —旦网络发生拥塞， PCEF向 PCRF上报拥塞状态。 该步骤为可选， 如果网络没有发生拥塞， 则不会发生该步骤；
406. 用户开展业务和 AF之间完成业务协商；
407. AF将业务协商信息下发给 PCRF, 所述业务信息中包含业务标识、 业务对 QoS的要求等；
408. PCRF接收到所述业务信息之后， 结合用户信息， 用户设备信息， 网络拥塞情况等为所述业务决策是否启动流量压缩； 例如：
用户设备使用的是小尺寸屏幕设备， 用户为铜牌用户， 且此时网络处于 拥塞状态， 则 PCRF决策对用户开展的所述业务启动流量压缩。 同时 PCRF 根据业务信息以及用户签约信息等对所述业务使用的 QoS进行策略决策。
409. PCRF将控制策略下发给 PCEF, 同时向 PCEF下发对所述业务启动 流量压缩的指示；
410. PCEF收到所述控制策略之后，安装所述策略， 同时根据 PCRF下发 的启动流量压缩的指示， 对用户开展的所述业务启动流量压缩；
411. 当 PCEF检测到所述业务对应的 IP报文之后， 对所述 IP报文启动 流量压缩。 当用户设备接收到所述压缩报文之后， 对所述报文启动解压。
上述实施例描述的是 PCEF支持流量压缩功能。 如果 PCEF不支持流量 压缩功能， 则当 PCEF收到 PCRF下发的启动流量压缩的指示后， 需要将所 述指示提供给支持所述压缩功能的网元。
实施例四
本实施例描述的是 PCRF根据业务信息，网络拥塞情况等决策是否对 TDF 检测的业务启动流量压缩。 例如对于用户通过智能终端启动视频下载。 由于 所述下载业务将会占用大量网络资源， 甚至可能影响到网络上传输的其他业 务。 而如果用户下载视频所使用的智能终端是小屏幕终端， 那么结合所述智 能终端的尺寸对所述下载业务启动压缩， 即使损失了部分数据（例如将高清 压缩成普通）也不会对用户体验造成重大影响， 本实施例描述的是结合终端 设备能力对视频下载业务启动流量压缩， 其流程描述如下：
500. 终端设备附着到网络， 将用户设备能力发送给网络；
501. 当用户附着到网络的时候， PCEF向 PCRF发起 IP-CAN会话建立请 求， 通过所述请求将用户设备能力， 以及用户信息上报给 PCRF, 例如用户设 备是否支持流量压缩， 所述用户设备的屏幕尺寸等；
502. PCRF接收到所述 IP-CAN会话建立请求， 根据用户信息从 SPR获 取对应用户的签约信息， 例如用户等级， 用户的签约业务， 用户的签约 QoS 等；
503. PCRF保存从 PCEF, SPR收到的上述信息，并向 PCEF返回 IP-CAN 会话建立成功的响应， 同时 PCRF向 PCEF订阅网络拥塞情况， 要求当承载 网络发生拥塞的时候， PCEF将所述拥塞状态上报给 PCRF;
504. PCRF与 TDF之间建立 TDF会话，并下发 ADC( Application Detection and Control, 应用检测和控制）规则， 要求 TDF检测到 P2P下载业务时上报；
505. 此时所述用户启动视频下载；
506. 根据 ADC规则， TDF检测到所述下载应用；
507. TDF将检测到的业务信息上报给 PCRF;
508. PCRF从网管中心获取网络拥塞状况；
509.根据网络拥塞状况， 用户设备的能力 （例如是否支持流量压缩， 终 端设备的屏幕尺寸等） PCRF决策为所述业务启动流量压缩；
情况 A:
510a. 如果 TDF支持流量压缩， 则 PCRF向 TDF下发控制策略， 并下发 流量压缩指示；
所述启动流量压缩的指示可以指明具体釆用的流量压缩方式。 如果执行 流量压缩的网关可以支持多种流量压缩方式， 则 PCRF下发控制策略时应指 明具体的流量压缩方式；
511a. 根据指示 TDF对所述业务数据流启动流量压缩；
情况 B:
510b. 如果 PCEF支持流量压缩， 且 507步中 TDF上报的业务信息中包 含有业务流的五元组信息， 则 PCRF向 PCEF下发针对所述业务的控制策略， 同时下发启动流量压缩的指示；
511b. PCEF按照 PCRF下发的启动流量压缩指示说明对所述下载业务启 动流量压缩；
512. 对所述用户的下载业务启动压缩方式的传输。
本发明实施例还提供一种控制网元， 如图 6所示， 包括： 决策单元和发 送单元， 其中：
所述决策单元设置为， 决策是否启动流量压缩；
所述发送单元设置为， 所述决策单元决策启动流量压缩后， 向支持流量 压缩的网元下发流量压缩指示。 其中， 所述决策单元决策是否启动流量压缩包括：
所述决策单元根据如下信息之一或其组合决策是否启动流量压缩： 用户 信息， 用户设备信息， 应用服务信息， 接入网络类型， 位置信息， 时间， 网 络拥塞情况。
其中， 所述用户信息包括用户等级； 所述用户设备信息包括用户设备是 否支持流量压缩的能力和 /或所述用户设备的屏幕尺寸； 所述应用服务信息包 括服务类型， 所述位置信息包括用户当前所处的位置。
其中， 所述流量压缩指示包括启动流量压缩的指示， 和 /或， 流量压缩方 式。
其中， 所述控制网元为策略和计费规则功能 PCRF。
本发明实施例还提供一种网络拥塞的处理系统， 包括： 上述控制网元和 支持流量压缩的网元， 其中：
所述支持流量压缩的网元设置为， 收到所述控制网元发送的流量压缩指 示后， 4艮据所述流量压缩指示， 启动流量压缩。
另外， 本发明还可以支持 PCRF根据用户设备的地理位置， 时间等决策 是否为用户开展的业务启动流量压缩。 例如对于一些热点区域， 比如车站等， 在人流高峰期间， 网络自动启动流量压缩机制， 其实现是： 当用户附着到网 络的时候， PCEF将用户设备能力， 用户位置信息（小区信息， 基站信息）等 上报给 PCRF。 当 PCRF为用户开展业务进行策略决策的时候，根据用户位置 信息判断所述用户是否位于特点区域， 同时判断当前时间是否为上班高峰时 间。 如果此时是高峰时间， 并且用户位于热点区域， 则 PCRF决策为所述业 务启动流量压缩， 并向支持流量压缩的网元下发启动流量压缩的指示。据此， 对所述业务启动流量压缩。
本发明实施例中使用 PCRF为用户开展业务是否启动流量压缩进行决策， 同样也可以被其他支持所述功能的网元替代。
显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布 在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程 序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 并 且在某些情况下， 可以以不同于此处的顺序执行所示出或描述的步骤， 或者 将它们分别制作成各个集成电路模块， 或者将它们中的多个模块或步骤制作 成单个集成电路模块来实现。 这样， 本发明不限制于任何特定的硬件和软件 结合。
以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本 领域的技术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和 原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护 范围之内。
工业实用性
本发明实施例提供了一种拥塞处理方法和系统， 使得网络可以根据用户 设备的能力， 网络拥塞情况等决策是否为用户开展的业务启动流量压缩， 从 而可以达到减少网络拥塞， 减轻网络负荷的目的。

Claims

权 利 要 求 书
1、 一种网络拥塞的处理方法， 其包括：
控制网元决策是否启动流量压缩， 如果启动， 则向支持流量压缩的网元 下发流量压缩指示；
所述支持流量压缩的网元根据所述流量压缩指示， 启动流量压缩。
2、 如权利要求 1所述的方法， 其中， 所述控制网元决策是否启动流量压 缩包括：
所述控制网元根据如下信息之一或其组合决策是否启动流量压缩： 用户 信息， 用户设备信息， 应用服务信息， 接入网络类型， 位置信息， 时间， 网 络拥塞情况。
3、 如权利要求 2所述的方法， 其中， 所述用户信息包括用户等级； 所述 用户设备信息包括用户设备是否支持流量压缩的能力和 /或所述用户设备的 屏幕尺寸； 所述应用服务信息包括服务类型， 所述位置信息包括用户当前所 处的位置。
4、 如权利要求 1所述的方法， 其中， 所述流量压缩指示包括： 启动流量 压缩的指示， 和 /或， 流量压缩方式。
5、 如权利要求 1至 4任一所述的方法， 其中， 所述控制网元为策略和计 费规则功能 PCRF。
6、 如权利要求 1至 4任一所述的方法， 其中， 所述支持流量压缩的网元 为如下之一： 策略和计费执行功能 PCEF、承载绑定和事件上报功能 BBERF、 传输检测功能 TDF、 应用功能 AF。
7、 一种控制网元， 包括： 决策单元和发送单元， 其中：
所述决策单元设置为， 决策是否启动流量压缩；
所述发送单元设置为， 所述决策单元决策启动流量压缩后， 向支持流量 压缩的网元下发流量压缩指示。
8、 如权利要求 7所述的控制网元， 其中，
所述决策单元是设置为根据如下信息之一或其组合决策是否启动流量压 缩： 用户信息， 用户设备信息， 应用服务信息， 接入网络类型， 位置信息， 时间， 网络拥塞情况。
9、 如权利要求 8所述的控制网元， 其中， 所述用户信息包括用户等级； 所述用户设备信息包括用户设备是否支持流量压缩的能力和 /或所述用户设 备的屏幕尺寸； 所述应用服务信息包括服务类型， 所述位置信息包括用户当 前所处的位置。
10、 如权利要求 7所述的控制网元， 其中， 所述流量压缩指示包括启动 流量压缩的指示， 和 /或， 流量压缩方式。
11、 如权利要求 7所述的控制网元， 其中， 所述控制网元为策略和计费 规则功能 PCRF。
12、 一种网络拥塞的处理系统， 其包括如权利要求 7至 11任一所述的控 制网元和支持流量压缩的网元， 其中：
所述支持流量压缩的网元设置为， 收到所述控制网元发送的流量压缩指 示后， 4艮据所述流量压缩指示， 启动流量压缩。
13、 如权利要求 12所述的系统， 其中， 所述支持流量压缩的网元为如下 之一： 策略和计费执行功能 PCEF、 承载绑定和事件上报功能 BBERF、 传输 检测功能 TDF、 应用功能 AF。
PCT/CN2013/072977 2012-04-28 2013-03-21 一种网络拥塞的处理方法、系统和控制网元 WO2013159617A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2012101323082A CN103379043A (zh) 2012-04-28 2012-04-28 一种网络拥塞的处理方法、系统和控制网元
CN201210132308.2 2012-04-28

Publications (1)

Publication Number Publication Date
WO2013159617A1 true WO2013159617A1 (zh) 2013-10-31

Family

ID=49463614

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/072977 WO2013159617A1 (zh) 2012-04-28 2013-03-21 一种网络拥塞的处理方法、系统和控制网元

Country Status (2)

Country Link
CN (1) CN103379043A (zh)
WO (1) WO2013159617A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104640150A (zh) * 2013-11-11 2015-05-20 华为技术有限公司 一种通信优化方法、设备及系统
WO2015100667A1 (zh) * 2013-12-31 2015-07-09 华为技术有限公司 一种通知接入网拥塞状态的方法和装置
CN106937323B (zh) * 2015-12-30 2021-03-30 华为技术有限公司 一种用户终端数量的监控方法及相关设备
US10374964B2 (en) * 2016-03-07 2019-08-06 Huawei Technologies Co., Ltd. Control channel compression upon congestion detection
CN107592979B (zh) 2016-05-10 2021-01-29 华为技术有限公司 QoS资源分配方法和装置
CN112637886B (zh) * 2019-09-24 2022-05-17 深圳市万普拉斯科技有限公司 基站与终端的通信资源共享方法及系统
CN112311686B (zh) * 2020-09-27 2022-09-30 长沙市到家悠享网络科技有限公司 一种数据处理方法、装置、电子设备及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101026566A (zh) * 2007-02-13 2007-08-29 华为技术有限公司 一种提高接入设备服务带宽的方法、系统及其装置
CN101094180A (zh) * 2007-07-20 2007-12-26 杭州华三通信技术有限公司 一种对压缩后流量进行监管的方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101394291A (zh) * 2007-09-17 2009-03-25 华为技术有限公司 一种处理业务的方法、装置及系统
CN101472295B (zh) * 2007-12-27 2011-02-09 中国移动通信集团公司 一种拥塞控制方法和装置
CN102215155B (zh) * 2010-04-02 2016-06-08 中兴通讯股份有限公司 一种家庭网络的资源接纳控制方法及系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101026566A (zh) * 2007-02-13 2007-08-29 华为技术有限公司 一种提高接入设备服务带宽的方法、系统及其装置
CN101094180A (zh) * 2007-07-20 2007-12-26 杭州华三通信技术有限公司 一种对压缩后流量进行监管的方法及装置

Also Published As

Publication number Publication date
CN103379043A (zh) 2013-10-30

Similar Documents

Publication Publication Date Title
RU2513711C2 (ru) Триггер события услуги
WO2013159617A1 (zh) 一种网络拥塞的处理方法、系统和控制网元
CN101325780B (zh) 策略控制实现方法和系统、及策略和计费执行实体
JP5113254B2 (ja) マルチメディア通信ネットワークにおけるリソース制限の通知
CN103828476B (zh) 控制服务会话的资源的方法和网络节点以及对应的系统和计算机程序
RU2577333C2 (ru) Поддержка множества однонаправленных каналов при ситуациях перегрузки
EP2938131B1 (en) Capability exposure system, gateway, proxy, and method of wireless network
EP2521305B1 (en) Method, device and system for controlling user session policy
JP2012507223A (ja) ポリシー及び課金制御方法、サーバ、及びコンピュータプログラム
US20100186064A1 (en) Method and device for obtaining capabilities of policy and charging enforcement function
RU2435205C2 (ru) Способ законного перехвата информации и устройство для этого
WO2010069170A1 (zh) 一种实现策略和计费控制的方法
KR20090054528A (ko) 사용자를 위한 서비스 품질 관리 방법 및 이를 수행하기위한 시스템
WO2009024050A1 (fr) Procédé, système et dispositif de commande de politique
US9544201B2 (en) Quality of experience in communication networks
WO2015033580A1 (ja) 通信装置、制御装置、通信方法、制御方法およびプログラム
WO2013007142A1 (zh) 一种用量监控方法及系统
WO2007112657A1 (fr) Procédé et système de décision concernant l'information sur les services dans un système de communication mobile
WO2013091410A1 (zh) 网络接入方法、系统及设备
EP2630823A1 (en) Multi-bearer rate control for transporting user plane data
WO2011085614A1 (zh) 在全业务融合网络中控制资源的方法和系统
WO2014026545A1 (zh) 一种固定宽带网络的资源分配方法、装置及系统
WO2014032289A1 (zh) 带宽控制方法、装置及系统
WO2014180210A1 (zh) 一种控制网络拥塞的方法和负荷感知功能
WO2014146502A1 (zh) 无线接入网络拥塞管理方法及装置、拥塞策略管理方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13782617

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

Country of ref document: EP

Kind code of ref document: A1