WO2016148494A1 - Congestion control method and apparatus based on lte network - Google Patents

Congestion control method and apparatus based on lte network Download PDF

Info

Publication number
WO2016148494A1
WO2016148494A1 PCT/KR2016/002621 KR2016002621W WO2016148494A1 WO 2016148494 A1 WO2016148494 A1 WO 2016148494A1 KR 2016002621 W KR2016002621 W KR 2016002621W WO 2016148494 A1 WO2016148494 A1 WO 2016148494A1
Authority
WO
WIPO (PCT)
Prior art keywords
functional entity
bearer
air interface
user
information
Prior art date
Application number
PCT/KR2016/002621
Other languages
English (en)
French (fr)
Inventor
Jun Wang
Xiaoning MA
Lixiang Xu
Xiaowan KE
Yu Qiu
Hong Wang
Original Assignee
Samsung Electronics Co., Ltd.
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 Samsung Electronics Co., Ltd. filed Critical Samsung Electronics Co., Ltd.
Publication of WO2016148494A1 publication Critical patent/WO2016148494A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • H04W28/0236—Traffic management, e.g. flow control or congestion control based on communication conditions radio quality, e.g. interference, losses or delay
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0284—Traffic management, e.g. flow control or congestion control detecting congestion or overload during communication

Definitions

  • the present disclosure relates to radio communication techniques, and more particularly, to a congestion control method and apparatus based on an LTE network.
  • FIG. 1 shows a system structure of System Architecture Evolution (SAE) according to the prior art, in which:
  • Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 102 is a radio access network, including an eNodeB/NodeB which provides an interface for the UE to access the radio network.
  • Mobility Management Entity (MME) 103 is responsible for managing mobility context, session context and security information of the UE.
  • Serving Gateway (SGW) 104 is mainly used for providing a user plane function.
  • the MME 103 and the SGW 104 may be in a same physical entity.
  • Packet data network Gateway (PGW) 105 is responsible for charging, legal listening and other functions.
  • the PGW 105 may also be in the same physical entity with the SGW 104.
  • PCRF Policy and Charging Rule Function
  • Operator service network 107 includes service servers for providing data service source services for the UE.
  • Serving GPRS Support Node (SGSN) 108 is a network device for providing route for data transmission in a Universal Mobile Telecommunications System (UMTS).
  • Home Subscriber Server (HSS) 109 is a home sub-system of the UE, and is responsible for protecting user information such as current location, serving node location, user security information and packet data context of the user device.
  • RAN congestion Apperceive Function (RCAF) is proposed in 3GPP Rel-13. As shown in FIG. 2, the RCAF collects RAN information from an Operation Administration and Maintenance (OAM) entity and performs a congestion detection. The RCAF obtains a ⁇ IMSI, APN> list of UEs served by a congestion base station or a congestion cell from the MME via an Nq interface, so as to determine the PCRF serving these UEs.
  • OFAM Operation Administration and Maintenance
  • the RCAF reports RAN User Congestion Information (RUCI) containing a ⁇ eNBId, IMSI, APN, Congestion Level> list to the PCRF through an Np interface.
  • the PCRF performs a Packet Data Network (PDN) link level congestion control policy decision according to the RUCI.
  • PDN Packet Data Network
  • OTT Over The Top
  • radio resources are limited, how to perform timely and accurate congestion control at the RAN side, how to obtain the QoE indicator in time, including recognizing the service type, especially Mobile Video services accounting for more than 70% of the service amount in the LTE network and user experience brought by the Mobile Video services, how to utilize the resources reasonably and effectively, how to implement accurate congestion control at the bearer level and the service data flow level, including necessary scheduling priority or QoS adjustment to a particular bearer and necessary rate limiting or gating to a particular service data flow, how to utilize the LTE network resources more intelligently, sufficiently and effectively, reduce congestion and thereby improve user experiences, these are still under research.
  • a congestion control method based on a Long-Term Evolution (LTE) network including:
  • CC Congestion Control
  • UE User Equipment
  • MME Mobility Management Entity
  • PI Packet Inspection
  • QoE Quality of Experience
  • the air interface status report includes air interface resource usage status and air interface channel quality information.
  • the determining the adjusting manner of the user data transmission includes: determining a bearer congestion status according to the air interface resource usage status and the air interface channel quality information, and determining a scheduling priority or a Quality of Service (QoS) of a user bearer needs to be adjusted according to the congestion status and the QoE indicator.
  • QoS Quality of Service
  • the air interface resource usage status is a Physical Resource Block (PRB) usage of a user bearer
  • the air interface channel quality information is a Modulation Product code Rate (MPR) of the user
  • the determining the adjusting manner of the user data transmission comprises: for a user bearer with a PRB usage higher than a predefined PRB threshold, an MPR lower than a predefined MPR threshold and a QoE indicator lower than a predefined QoE threshold, decreasing a processing priority of the user bearer.
  • the performing the corresponding adjustment includes:
  • PCRF Policy and Charging Rule Function
  • the CC functional entity is independent from the MME
  • the CC functional entity receiving the air interface status report transmitted by each base station includes: receiving, by the CC functional entity, the air interface status report from the base station directly via an interface between the CC functional entity and the base station; or, the base station transmitting the air interface status report to the MME via an S1-MME interface, and the CC functional entity receiving the air interface status report forwarded by the MME.
  • the method when a bearer is to be deleted, the method further includes: transmitting, by the MME, a UE context release indication to the CC functional entity to indicate a bearer to be released and an International Mobile Subscriber Identity (IMSI) of the user, deleting, by the CC functional entity, context information of a corresponding bearer according to the UE context release indication received, and informing the PI functional entity to release the detection information corresponding to the deleted bearer.
  • IMSI International Mobile Subscriber Identity
  • the method further includes: transmitting, by the MME, a UE context update indication to the CC functional entity and indicating modification information of a service data flow, a bearer identifier and the IMSI of the user; updating, by the CC functional entity, context of the corresponding bearer and the service data flow according to the UE context update indication, and informing the PI functional entity to modify the corresponding bearer and update the context of the corresponding service data flow.
  • TFT Traffic Flow Template
  • the CC functional entity is located in the MME
  • the CC functional entity receiving the air interface status report transmitted by each base station includes: receiving, by the CC functional entity, the air interface status report transmitted by the base station via an S1-MME interface.
  • a congestion control method based on an LTE network including:
  • the PI functional entity reporting the QoE indicator to the CC functional entity includes:
  • the PI functional entity is located independently from a PGW, or the PI functional entity is located in the PGW.
  • a CC functional entity includes: an MME interface unit, a PI interface unit, an air interface report receiving unit and a congestion control unit;
  • the MME interface unit is adapted to receive UE context indication information transmitted by an MME;
  • the PI interface unit is adapted to configure detection information for a PI functional entity according to the UE context indication information, and receive a data characteristic and a QoE indicator transmitted by the PI functional entity obtained after detection and analysis to service data according to user and bearer information included in the detection information;
  • the air interface report receiving unit is adapted to receive an air interface status report transmitted by each base station, wherein the air interface status report includes an air interface resource usage status and air interface channel quality information;
  • the congestion control unit is adapted to determine a user data transmission adjusting manner according to the air interface status report and the QoE indicator and perform a corresponding adjustment.
  • a PI functional entity including: a receiving unit, a detecting unit and a transmitting unit;
  • the receiving unit is adapted to receive detection information configured by a CC functional entity
  • the detecting unit is adapted to detect and analyze service data of a user according to user and bearer information included in the detection information, obtain a data characteristic and a QoE indicator of the service data;
  • the transmitting unit is adapted to report the QoE indicator to the CC functional entity, such that the CC functional entity performs a congestion control.
  • the CC functional entity receives the air interface status report from the base station, obtains the air interface resource usage status and the air interface channel quality information, so as to detect the congestion status of the RAN timely and accurately.
  • the PI functional entity is able to obtain the QoE indicator in time and report it to the CC functional entity.
  • the QoE indicator may be utilized by the CC functional entity reasonably and effectively, thereby realizes accurate user bearer level and service data flow level congestion control.
  • detailed congestion control may include necessary adjustment to the scheduling priority or QoS of a particular bearer, and necessary rate limiting or gating to a particular service data flow.
  • the LTE network resources are utilized more intelligently, sufficiently and effectively. Congestion is reduced and user experience is improved.
  • Embodiments of the present disclosure provide a congestion control method and apparatus based on an LTE network, so as to realize effective and accurate congestion control.
  • FIG. 1 is a schematic diagram illustrating a system architecture of SAE according to the prior art.
  • FIG. 2 is a schematic diagram illustrating a 3GPP Rel-13 congestion control architecture.
  • FIG. 3 is a schematic diagram illustrating a new congestion control architecture according to an embodiment of the present disclosure.
  • FIG. 4 is a flowchart illustrating a congestion control method according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram illustrating a bearer level congestion control procedure with independently deployed CC/PI functional entities according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram illustrating a service data flow level congestion control procedure with independently deployed CC/PI functional entities according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram illustrating a bearer level congestion control procedure with combined MME and CC functional entity according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic diagram illustrating a bearer delete procedure with independently deployed CC/PI functional entities according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic diagram illustrating a bearer modification procedure with TFT update and independently deployed CC/PI functional entities according to an embodiment of the present disclosure.
  • CC Congestion Control
  • PI Packet Inspection
  • the system architecture after the above two functional entities are introduced is as shown in FIG. 3.
  • the base station (eNodeB) implements detection and report of user air interface status;
  • the PI functional entity detects and analyzes service data to obtain a Quality of Experience (QoE) indicator and reports the QoE indicator;
  • the CC functional entity has the function of the RCAF in Rel-13 for collecting RAN side congestion information, but the information is from timely and accurate congestion detection of the base station to the air interface but not from the OAM, i.e., the CC functional entity performs necessary judgment and control to the bearer and Service Data Flow (SDF) according to the information reported by the eNodeB and the PI functional entity.
  • SDF Service Data Flow
  • the CC functional entity and the PI functional entity are shown independently in FIG. 3.
  • the CC functional entity and the PI functional entity may be independent entities or functional modules configured in other physical entities.
  • the CC functional entity may be an independent physical entity or a functional module configured in the MME or in other physical entities.
  • the PI functional entity may be an independent entity, or a functional module configured in the PGW or in other physical entities.
  • FIG. 4 shows a basic procedure of a congestion control method based on the LTE network according to an embodiment of the present disclosure. As shown in FIG 4, the method includes the following.
  • the CC functional entity receives UE context indication information transmitted by the MME.
  • the CC functional entity configures detection information to the PI functional entity according to the UE context indication information.
  • the PI functional entity receives and saves the detection information transmitted by the CC functional entity.
  • the PI functional entity detects and analyzes service data according to user and bearer information contained in the detection information, obtains a data characteristic and a QoE indicator and reports to the CC functional entity.
  • the CC functional entity receives an air interface status report transmitted by each base station.
  • the air interface status report may include air interface resource usage status and air interface quality information.
  • the CC functional entity determines an adjusting manner for the user data transmission according to the air interface status report and the QoE indicator and performs a corresponding adjustment.
  • the operations in block 405 and operations in blocks 402 ⁇ 404 may be performed in parallel, or in any order.
  • the PI functional entity obtains the QoE indicator through analyzing the service data according to the detection information configured by the CC functional entity and reports the QoE indicator.
  • the CC functional entity obtains the air interface status report from the base station, obtains the QoE indicator from the PI functional entity, and performs accurate congestion detection according to the air interface status report and the QoE indicator obtained, so as to realize corresponding congestion control.
  • the overall method procedure is described from the point of interactions between multiple entities.
  • the processing in blocks 401, 402, 405 and 406 forms the congestion control method of the CC functional entity.
  • the processing in blocks 403 and 404 forms the congestion control method of the PI functional entity.
  • the two entities cooperate with each other to realize a more accurate congestion control.
  • the CC functional entity and the PI functional entity may be independent entities or combined with other entities.
  • the congestion control of the system includes a bearer level congestion control and a data flow level congestion control.
  • the method of the present disclosure is described in detail with regard to different positions of the CC/PI functional entities and different types of the congestion control, wherein the description is still given in form of interactions between multiple entities.
  • FIG. 5 shows a bearer level congestion control procedure with independently deployed CC/PI functional entities according to an embodiment of the present disclosure.
  • an Nq interface may be used between the CC functional entity and the MME
  • an Np interface based on Diameter protocol may be used between the CC functional entity and the PCRF.
  • a Pi interface based on the GTP may be used between the CC functional entity and the PI functional entity, the CC functional entity and the base station may communicate with each other directly via a Ce interface based on GTP or communicate with each other indirectly via the MME.
  • the procedure as shown in FIG. 5 includes the following.
  • a bearer is set up following an existing bearer setup procedure.
  • the MME transmits a newly-added UE context indication message to the CC functional entity via the Nq interface.
  • the UE context indication message may include but is not limited to, ⁇ Message_Type, Global_eNB_ID, eNB_UE_S1AP_ID, IMSI, Bearer_Id, UEIP, QoS>.
  • the CC functional entity saves a mapping relationship between the UE identifier IMSI and ⁇ Global_eNB_ID, eNB_UE_S1AP_ID> and the UE relevant context information.
  • the CC functional entity saves the mapping relationship between the UE identifier IMSI and the ⁇ Global_eNB_ID, eNB_UE_S1AP_ID>.
  • the CC functional entity transmits detection information configuration information carrying ⁇ Message_Type, IMSI, Bearer_Id, UEIP> to the PI functional entity via the Pi interface.
  • the PI functional entity detects and analyzes the service data according to relevant user and bearer information, and obtains a data characteristic and a QoE indicator on the basis of recognizing the service type.
  • the PI functional entity reports the QoE indicator to the CC functional entity.
  • the QoE indicator reported by the PI functional entity may be configured according to a congestion control requirement, or it is possible to report all obtained QoE indicators to the CC functional entity and the CC functional entity selects a corresponding indicator according to a congestion control requirement.
  • the relevant QoE indicator may include information such as born service type, encode rate of a video service and buffer level of the UE.
  • the PI functional entity may report the QoE indicator to the CC functional entity via the newly-added Pi interface.
  • the report manner includes but is not limited to:
  • the PI functional entity performs an in-depth analysis to a specific user bearer or service data flow and obtains the QoE indicator. If the value of the indicator reaches a configured threshold, the PI functional entity is triggered to report the QoE indicator to the CC functional entity.
  • the PI functional entity performs an in-depth analysis to a specific user bearer or service data flow and obtains the QoE indicator, and reports it to the CC functional entity according to a configured period.
  • the base station collects a bearer level PRB usage in each Transmission Time Interval (TTI), and performs a smoothing/averaging calculation to the PRB usage according to the configured period, and determines a Modulation Product code Rate(MPR) according to a Channel Quality Indicator (CQI) reported by the UE.
  • TTI Transmission Time Interval
  • MPR Modulation Product code Rate
  • the air interface status report includes the air interface resource usage status and the air interface channel quality information.
  • the PRB usage of the user bearer is used to denote the air interface resource usage status and the MPR of the user is used as the air interface channel quality information. Therefore, in this block, the base station determines the PRB usage and the MPR for preparing to transmit the air interface status report.
  • the air interface resource usage status and the air interface channel quality information may also be denoted by information in other forms, which is not restricted in the present disclosure, if only they can denote the air interface resource usage status and the air interface channel quality.
  • the CC functional entity receives an air interface status report from each base station.
  • the base station reports a relevant UE level MPR and bearer level PRB usage information to the CC functional entity.
  • the CC functional entity may adopt one of the following two manners to receive the air interface status report.
  • block 508 includes operations of block 508a:
  • the base station transmits an air interface status report message to the CC functional entity, carrying information including but is not limited to ⁇ Message_Type, Global_eNB_ID, eNB_UE_S1AP_ID, MPR, Bearer_Id, PRB_Usage> list information.
  • block 508 includes operations of following blocks 508b and 509b:
  • the base station transmits a newly-added air interface status report message to the MME via the S1-MME interface, carrying information including but is not limited to: ⁇ Message_Type, Global_eNB_ID, eNB_UE_S1AP_ID, MPR, Bearer_Id, PRB_Usage> list information.
  • the MME forward the relevant information to the CC functional entity via a newly-added UE resource status report message through the Nq interface.
  • the method may further include the following.
  • the CC functional entity determines a scheduling priority or QoS of a user bearer which requires adjustment, i.e., ⁇ Global_eNB_ID, eNB_UE_S1AP_ID/IMSI, Bearer_Id, Priority_Level/QoS>, according to the air interface status and QoE indicator of each base station, each user and each bearer.
  • the CC functional entity determines the congestion status of the user bearer according to the air interface resource usage and the air interface channel quality information (such as the PRB usage of the user bearer and the MPR of the user) and determines the scheduling priority or QoS of the user bearer which requires adjustment according to the congestion status and the QoE indicator. For example, for the user bearer with high PRB usage, low MPR and low QoE indicator, it is possible to decrease its processing priority. In particular, for a user bearer whose PRB usage is higher than a predefined PRB threshold, MPR is lower than a predefined MPR threshold and QoE indicator is lower than a predefined QoE threshold, the processing priority may be decreased.
  • the CC functional entity adjusts the data transmission of the user bearer which requires adjustment.
  • the adjustment to the data transmission may be performed via the following two manners.
  • block 511 includes the following.
  • the CC functional entity transmits the scheduling indication message to the base station, carrying information including but is not limited to: ⁇ Message_Type, Global_eNB_ID, eNB_UE_S1AP_ID, Bearer_Id, Priority_Level> list information.
  • block 511 includes the following.
  • the CC functional entity transmits a newly-added scheduling indication message to the MME via the Nq interface, carrying information including but is not limited to: ⁇ Message_Type, Global_eNB_ID, eNB_UE_S1AP_ID, Bearer_Id, Priority_Level> list information.
  • the MME forwards relevant information to the base station via a newly-added scheduling indication message through the S1-MME interface.
  • the base station After receiving the scheduling indication message through block 511 or blocks 511b ⁇ 512b, the base station proceeds with block 513 to schedule a particular user bearer using the indicated priority according to the scheduling indication message, and ends the procedure.
  • block 511 may be implemented via following blocks 514 ⁇ 519.
  • an existing Np interface message Aggregated RUCI Report is enhanced to include ⁇ IMSI, Bearer_Id, QoS> list information, the CC functional entity transmits the ARR message to the PCRF.
  • the PCRF refers to the user bearer and QoS carried in the ARR message transmitted by the CC functional entity, performs a policy decision and transmits an existing Re-Auth-Request (RAR) message carrying QoS-Information to the PGW (PCEF).
  • RAR Re-Auth-Request
  • the PCRF returns an Aggregated RUCI ACK (ARA) message to the CC functional entity.
  • ARA Aggregated RUCI ACK
  • the PGW (PCEF) returns a Re-Auth-Answer (RAA) message to the PCRF.
  • RAA Re-Auth-Answer
  • the PGW initiates a bearer modification procedure with QoS update.
  • downlink data transmission is implemented under the control of the new bearer QoS policy and the procedure ends.
  • FIG. 6 is a schematic diagram illustrating a service data flow level congestion control procedure with independently deployed CC/PI functional entities according to an embodiment of the present disclosure.
  • the procedure includes the following.
  • Block 601 is similar as blocks 501 ⁇ 504.
  • the PI functional entity detects and analyzes service data after receiving the detection information configuration message, and obtains a data characteristic and a QoE indicator on the basis of recognizing a service type.
  • the PI functional entity reports the QoE indicator to the CC functional entity.
  • the QoE indicator reported by the PI functional entity may be configured according to a congestion control requirement, or it is possible to report all obtained QoE indicators to the CC functional entity and the CC functional entity selects a corresponding indicator according to a congestion control requirement.
  • the data flow level congestion control is performed. Therefore, the relevant QoE indicator includes a service data flow identifier (SdfId, consists of data source IP address, source port number, destination IP address, destination port number), and service type such as encode rate of a video service and buffer level of the UE, etc.
  • SdfId service data flow identifier
  • Block 604 is similar as blocks 507 ⁇ 509.
  • the CC functional entity determines a detailed adjustment indicator of the user bearer to be adjusted according to the air interface status and QoE indicator of each base station, each user and each bearer.
  • the CC functional entity determines the congestion status of the user bearer according to the air interface resource usage status and the air interface channel quality information (such as the PRB usage of the user bearer and the MPR of the user), and determines the scheduling priority and QoS of the user bearer to be adjusted according to the congestion status and the QoE indicator, and, determines a rate limit and gating of the service data flow level, e.g., determine ⁇ Global_eNB_ID, eNB_UE_S1AP_ID/IMSI, Bearer_Id, Priority_Level, QoS, SdfId, MBR(Maximum Bit Rate)/Gating>.
  • a rate limiting or gating method may be adopted for a Service Data Flow (SDF) with high PRB usage, low MPR and low QoE indicator.
  • SDF Service Data Flow
  • a rate limiting or gating method may be adopted for an SDF with PRB usage higher than a PRB threshold, MPR lower than a predefined MPR threshold and QoE indicator lower than a predefined QoE threshold.
  • Block 606 is similar as blocks 511 ⁇ 513.
  • existing Np interface message Aggregated RUCI Report is enhanced to include ⁇ IMSI, Bearer_Id, QoS, SdfId, MBR/Gating> list information, the CC functional entity transmits the ARR message to the PCRF.
  • the PCRF refers to the information carried in the ARR message from the CC functional entity, transmits an existing Re-Auth-Request (RAR) carrying Flow-Information, Flow-Status, QoS-Information to the PGW (PCEF) after policy decision.
  • RAR Re-Auth-Request
  • PCEF PGW
  • Block 609 is similar to blocks 516 ⁇ 518.
  • FIG. 7 is a schematic diagram illustrating a bearer level congestion control procedure with combined CC and MME entity and independently deployed PI entity according to an embodiment of the present disclosure.
  • the difference mainly includes the CC functional entity and the MME implement internal communication, and the MME/CC combination and the base station communicate via the S1-MME interface.
  • the procedure includes the following.
  • a bearer is set up according to an existing bearer setup procedure.
  • the MME/CC combination saves a UE identifier mapping relationship and UE context information, including but is not limited to ⁇ Message_Type, Global_eNB_ID, eNB_UE_S1AP_ID, IMSI, Bearer_Id, UEIP, QoS>.
  • Block 703 is similar to blocks 504 ⁇ 507.
  • the base station transmits a newly-added air interface status report message to the MME/CC combination, wherein the air interface status report message includes but is not limited to ⁇ Message_Type, Global_eNB_ID, eNB_UE_S1AP_ID, MPR, Bearer_Id, PRB_Usage> list information.
  • Block 705 is similar to block 510.
  • the MME/CC combination entity transmits a newly-added scheduling indication message containing but is not limited to ⁇ Message_Type, Global_eNB_ID, eNB_UE_S1AP_ID, Bearer_Id, Priority_Level> list information to the base station via the S1-MME interface.
  • Block 707 is similar to blocks 513 ⁇ 519.
  • FIG. 8 is a schematic diagram illustrating a bearer deletion procedure with independently deployed CC/PI functional entities according to an embodiment of the present disclosure.
  • the procedure includes the following.
  • bearer release of an existing entity is implemented according to an existing bearer release procedure.
  • the MME transmits a newly-added UE context release indication message carrying but not limited to ⁇ Message_Type, IMSI, Bearer_Id> to the CC functional entity via the Nq interface; the CC functional entity deletes context information of a corresponding bearer.
  • the CC functional entity transmits a newly-added detection configuration information release message carrying but is not limited to ⁇ Message_Type, IMSI, Bearer_Id> to the PI functional entity via the Np interface; the PI functional entity deletes detection configuration context information of the corresponding bearer.
  • the bearer release in a scenario that the CC and the PI functional entities are independently deployed is implemented. If the CC functional entity is combined with the MME, or the PI functional entity is combined with the PGW, the bearer release is implemented by the MME/CC combination entity or the PGW/PI combination entity.
  • FIG. 9 is a schematic diagram illustrating a bearer modification procedure with TFT update and independently deployed CC/PI functional entities according to an embodiment of the present disclosure.
  • the procedure includes the following.
  • bearer update of an existing entity is implemented according to an existing bearer modification procedure.
  • the MME transmits a newly-added UE context update message carrying but is not limited to ⁇ Message_Type, IMSI, Bearer_Id, Sdf-Info> to the CC functional entity via the Nq interface, wherein the Sdf-Info is modification information of the service data flow obtained by the MME through analyzing based on the updated TFT, the modification information includes addition, replacement, deletion of the service data flow information corresponding to the bearer; the CC functional entity updates the corresponding bearer and the service data flow context according to the Sdf-Info.
  • Sdf-Info is modification information of the service data flow obtained by the MME through analyzing based on the updated TFT
  • the modification information includes addition, replacement, deletion of the service data flow information corresponding to the bearer
  • the CC functional entity updates the corresponding bearer and the service data flow context according to the Sdf-Info.
  • the CC functional entity transmits a newly-added detection configuration information update message carrying but is not limited to ⁇ Message_Type, IMSI, Bearer_Id, Sdf-Info> to the PI functional entity via the Np interface; the PI functional entity updates the corresponding bearer and the service data flow context according to the Sdf-Info.
  • the bearer modification with TFT update and independently deployed CC and PI functional entities is implemented, the modification includes addition, replacement and deletion of the service data flow information corresponding to the bearer. If the CC functional entity is combined with the MME, or the PI functional entity is combined with the PGW, the bearer modification is implemented by the MME/CC combination entity or the PGW/PI combination entity.
  • FIG. 5 ⁇ FIG. 9 for relevant procedures of bearer level and service data flow level congestion control in the following several scenarios.
  • the main difference includes the following.
  • the CC functional entity is located independently from the MME, and the PI functional entity is combined with the PGW
  • communication may be implemented directly with the PGW/PI combination entity; the PGW/PI combination entity has the functions of both the PGW and the PI functional entity; the PI functional entity and the PGW interact via internal communication.
  • the CC functional entity is combined with the MME, and the PI functional entity and the PGW are combined.
  • interaction is implemented directly with the MME/CC combination entity; the MME/CC functional entity has the functions of both the MME and the CC functional entity; the CC functional entity and the MME interact via internal communication.
  • communication may be implemented directly with the PGW/PI combination entity; the PGW/PI combination entity has the functions of both the PGW and the PI functional entity; the PI functional entity and the PGW interact via internal communication.
  • the above describes the implementation of the method provided by the embodiments of the present disclosure.
  • the present disclosure further provides a CC functional entity and a PI functional entity, applicable for implementing the above method.
  • the CC functional entity provided by an embodiment of the present disclosure includes: an MME interface unit, a PI interface unit, an air interface report receiving unit and a congestion control unit.
  • the MME interface unit is adapted to receive UE context indication information transmitted by an MME.
  • the PI interface unit is adapted to configure detection information for a PI functional entity according to the UE context indication information, and receive a data characteristic and a QoE indicator transmitted by the PI functional entity obtained after detection and analysis to service data according to user and bearer information included in the detection information.
  • the air interface report receiving unit is adapted to receive an air interface status report transmitted by each base station, wherein the air interface status report includes an air interface resource usage status and air interface channel quality information.
  • the congestion control unit is adapted to determine a user data transmission adjusting manner according to the air interface status report and the QoE indicator and perform a corresponding adjustment.
  • the PI functional entity provided by an embodiment of the present disclosure includes: a receiving unit, a detecting unit and a transmitting unit.
  • the receiving unit is adapted to receive detection information configured by a CC functional entity.
  • the detecting unit is adapted to detect and analyze service data of a user according to user and bearer information included in the detection information, obtain a data characteristic and a QoE indicator of the service data.
  • the transmitting unit is adapted to report the QoE indicator to the CC functional entity, such that the CC functional entity performs a congestion control.
  • congestion status of the RAN may be detected timely and accurately and QoE indicator may be obtained in time, so as to be utilized reasonably and effectively, and achieve the objective of accurate congestion control of the user bearer level and the service data flow level, including necessary scheduling priority or QoS adjustment to a particular bearer, and necessary rate limiting and gating to a particular service data flow, such that the LTE network resources are utilized more intelligent, sufficient and effective, reduce congestion and improve user experience.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/KR2016/002621 2015-03-16 2016-03-16 Congestion control method and apparatus based on lte network WO2016148494A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510113201.7 2015-03-16
CN201510113201.7A CN106034327A (zh) 2015-03-16 2015-03-16 一种基于lte网络的拥塞控制方法和设备

Publications (1)

Publication Number Publication Date
WO2016148494A1 true WO2016148494A1 (en) 2016-09-22

Family

ID=56919249

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2016/002621 WO2016148494A1 (en) 2015-03-16 2016-03-16 Congestion control method and apparatus based on lte network

Country Status (2)

Country Link
CN (1) CN106034327A (zh)
WO (1) WO2016148494A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111343666A (zh) * 2018-12-19 2020-06-26 中国移动通信集团四川有限公司 基于lte网络的拥塞调整方法、装置、设备和介质
CN110225512B (zh) * 2019-06-04 2021-01-08 浙江大学 一种蜂窝物联网的无线资源控制方法及系统
CN113891388B (zh) * 2021-10-15 2024-04-02 中国联合网络通信集团有限公司 一种体验质量QoE上报的控制方法、装置、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014058369A1 (en) * 2012-10-12 2014-04-17 Telefonaktiebolaget L M Ericsson (Publ) Bearer management in the ran based on quality of service
US20140126502A1 (en) * 2011-04-14 2014-05-08 Telefonaktiebolaget Lm Ericsson (Publ) Qoe-aware traffic delivery in cellular networks
US20140198637A1 (en) * 2013-01-14 2014-07-17 Intel IP Corporation Handling User Plane Congestion
WO2014163346A1 (en) * 2013-04-01 2014-10-09 Samsung Electronics Co., Ltd. Scheme for congestion control in a mobile communication system
US20150009826A1 (en) * 2012-02-17 2015-01-08 Vid Scale, Inc Hierarchical traffic differentiation to handle congestion and/or manage user quality of experience

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140126502A1 (en) * 2011-04-14 2014-05-08 Telefonaktiebolaget Lm Ericsson (Publ) Qoe-aware traffic delivery in cellular networks
US20150009826A1 (en) * 2012-02-17 2015-01-08 Vid Scale, Inc Hierarchical traffic differentiation to handle congestion and/or manage user quality of experience
WO2014058369A1 (en) * 2012-10-12 2014-04-17 Telefonaktiebolaget L M Ericsson (Publ) Bearer management in the ran based on quality of service
US20140198637A1 (en) * 2013-01-14 2014-07-17 Intel IP Corporation Handling User Plane Congestion
WO2014163346A1 (en) * 2013-04-01 2014-10-09 Samsung Electronics Co., Ltd. Scheme for congestion control in a mobile communication system

Also Published As

Publication number Publication date
CN106034327A (zh) 2016-10-19

Similar Documents

Publication Publication Date Title
WO2014112844A1 (en) Method and apparatus for controlling traffic in wireless communication system
WO2014142524A1 (en) Method and apparatus for controlling congestion status of mobile communication network
WO2013103271A1 (en) Method of mdt continuous measurement and reporting under multiple plmns
WO2015199411A1 (en) Method and apparatus for assigning data to split bearers in dual connectivity
WO2013119021A1 (ko) 단말의 휴면 모드 동작 방법 및 장치
WO2017188787A2 (ko) 무선 통신 시스템에서 기지국에 의해 수행되는 데이터 전달 방법 및 상기 방법을 이용하는 장치
WO2015152678A1 (en) Method and apparatus for processing charging in wireless communication system and method and apparatus for providing policy service using the same
WO2015037947A1 (en) Method and device for setting up local breakout bearers
WO2014061911A1 (ko) Mtc 모니터링 관련 정보 제공 방법
WO2013133663A1 (ko) 무선 통신 시스템에서 서비스를 제어하기 위한 방법
WO2013141662A1 (en) Method and system for selecting pcef and pcrf in a wireless communication system
WO2015020366A1 (en) Methods, systems and devices for supporting local breakout in small cell architecture
WO2014051392A1 (ko) 패킷 처리 방법 및 장치
WO2014137098A1 (ko) 근접 서비스 범위 조정 방법 및 필터링 방법
WO2016159674A2 (en) Method and apparatus of caching service data in lte networks
WO2019054841A1 (en) METHOD FOR IMPLEMENTING REFLECTIVE SERVICE QUALITY IN WIRELESS COMMUNICATION SYSTEM, AND DEVICE THEREOF
WO2009107950A2 (en) Method for supporting ue mobility between macro cell and hnb cell
WO2013109082A1 (ko) 데이터 전송의 우선권 설정 방법 및 장치
EP2428059A2 (en) Server for control plane at mobile communication network and method for controlling establishment of connection thereof
WO2014065492A1 (ko) Mtc 모니터링 방법 및 네트워크 노드
WO2011087298A2 (ko) 이동통신시스템에서 이동성이 낮은 아이들모드 디바이스의 통신을 위한 메저먼트 장치 및 방법
WO2013141552A1 (ko) 로밍 시스템에서 메시지 송수신 방법 및 장치
WO2018143709A1 (ko) Rrc 상태를 결정하는 방법 및 장치
WO2015126160A1 (en) Video telephony service quality enhancement method and apparatus
WO2018131892A1 (en) Apparatus and method for controlling traffic in wireless communication system

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

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

Country of ref document: EP

Kind code of ref document: A1