CN105472635A - Access network congestion status reporting method and device and congestion information update processing method and device - Google Patents

Access network congestion status reporting method and device and congestion information update processing method and device Download PDF

Info

Publication number
CN105472635A
CN105472635A CN201410425740.XA CN201410425740A CN105472635A CN 105472635 A CN105472635 A CN 105472635A CN 201410425740 A CN201410425740 A CN 201410425740A CN 105472635 A CN105472635 A CN 105472635A
Authority
CN
China
Prior art keywords
congestion
ruci
information
rcaf
entity
Prior art date
Legal status (The legal status 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 status listed.)
Withdrawn
Application number
CN201410425740.XA
Other languages
Chinese (zh)
Inventor
周晓云
朱进国
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN201410425740.XA priority Critical patent/CN105472635A/en
Priority to PCT/CN2015/073802 priority patent/WO2016029673A1/en
Publication of CN105472635A publication Critical patent/CN105472635A/en
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The invention is mainly to provide an access network congestion status reporting method and device and a congestion information update processing method and device. The access network congestion status reporting method comprises: an RCAF entity obtains a network area managed thereby; and the RCAF entity reports RUCI carrying congestion status indication information to a PCRF entity, wherein the congestion status indication information is used for indicating that the congestion status of UE is uncongested, in one of the following situations: the network area is a congested area and the RCAF entity determines that the UE has moved out of the congested area; and the network area is an uncongested area and the RCAF entity determines that the UE is located in the network area. The problem that the PCRF cannot know the true congestion status of the area in which the UE is located and the like is solved, so that the PCRF is allowed to know the true status of the PCRF.

Description

The update process method of Access Network congestion state reporting, congestion information and device
Technical field
The present invention relates to the communications field, in particular to update process method and the device of a kind of Access Network congestion state reporting, congestion information.
Background technology
Fig. 1 is third generation partner program (3rdGenerationPartnershipProject in correlation technique, referred to as 3GPP) strategy that defines and charging control architecture (PolicyandChargingControl, referred to as PCC) schematic diagram, as shown in Figure 1, the core of "Policy and Charging Rules Function (PolicyandChargingRulesFunction, referred to as PCRF) whole PCC framework.PCRF formulates described control strategy to be needed to combine from application function (ApplicationFunction, referred to as AF) business information that receives, from user-subscribed database (SubscriptionProfileRepository, referred to as SPR) user signing contract information that receives, the strategy etc. of operator's configuration.The control strategy formulated for business is handed down to strategy and charge execution function (PolicyandChargingEnforcementFunction by PCRF, referred to as PCEF) or bearing binding and reporting events function (BearerBindingandEventReportFunction, referred to as BBERF) perform.Simultaneously PCRF can subscribe to bearing bed dependent event to PCEF and/or BBERF, timely perception when there is described event with convenient bearing bed, and changes control strategy.PCEF also can support application detection control function.The PCC rule comprising application identities that PCEF can issue according to this locality configuration or PCRF is carried out application and is detected and carry out strategy execution (as gate, being redirected and bandwidth restriction).PCEF is generally positioned on the gateway of network, as the grouped data network gateway (PacketDataNetworkGateway, referred to as P-GW) of the grouping domain system (EvolvedPacketSystem, referred to as EPS) of evolution.In addition, network can also realize applying detection control by disposing separate traffic measuring ability (TrafficDetectionFunction, referred to as TDF).TDF and PCRF is connected by Sd interface, and application detection control (ApplicationDetectionandControl, referred to as the ADC) rule that TDF can issue according to pre-configured or PCRF is carried out application and detected and strategy execution.
The principle of PCC framework to the service implementation policy control that bearer network transmits is as follows: along with the development of network and terminal equipment, a large number of users accesses various data service by intelligent terminal access Internet network, data service on the one hand on network is also constantly abundant, such as, various Video service, game services etc., use the Internet user of intelligent terminal also in the growth of explosion type on the other hand.This brings charge and challenge to the network operation of operator.A large amount of data services adds network load, even causes network congestion (such as, AT STATION, the hot spot region such as harbour).The resource of voice service been has even has been occupied in a large amount of data services, makes traditional voice service all can not get reliable QoS and ensures.Therefore, how to adjust network traffics, alleviate network load, reducing network congestion is that operator needs problems faced.
Fig. 2 is the Organization Chart of PCRF cognitive radio Access Network information on load in correlation technique.Wireless access network congestion aware function (RadioAccessNetworkCongestionAwarenessFunction, referred to as RCAF) by Np interface, unlimited user of access network face congestion information (RANUserPlaneCongestionInformation, referred to as RUCI) is reported to PCRF and carries out strategic decision-making to alleviate network load for PCRF.RCAF is from RAN operation management maintain (OperationAdministrationMaintenance, referred to as OAM) systematic collection user face congestion information.For E-UTRAN, RCAF obtains Node B (EvolvedNodeB in specific evolution by Nq interface from MME, referred to as eNB) UE (IMSI) list for each activation APN under the cellular global identity (EvolvedCellGlobalIdentifier, referred to as ECGI) of/evolution.For UTRAN access, RCAF directly can obtain the IMSI list specific NB/CGI from RAN, and passes through the IMSI list of Nq ' acquisition for each activation APN.Such RCAF just can obtain the IMSI list for each activation APN under each congested base station (eNB/NB)/community (ECGI/CGI).These information reportings are given correct PCRF by RCAF, and PCRF just to these UE Developing Tactics, can alleviate the load of congested base station or community.
Under normal circumstances, there is one or more RCAF in one network, do not have RCAF to be in charge of a network area (such as the corresponding cell list of each RCAF or station list).Like this, UE will being there is when being moved, in the range of management of a RCAF, moving to the range of management of another RCAF.Under scene below, the existing mechanism that reports there will be mistake.
If UE moves to congested cell (CellY, RCAFB are in charge of) from congested cell (CellX, RCAFA are in charge of).Because CellY is congested, so RCAFB reports congestion information to PCRF.And in the IMSI list of RCAFA under the CellX received, there is no UE, therefore the state of notice PCRF now UE is non-congested by RCAFA.Mistake is thought that UE is in the community of non-congested by such PCRF.
If UE moves to another congested cell (CellY, RCAFB are in charge of) from congested cell (CellX, RCAFA are in charge of) and is getting back to congested cell CellX.Because CellY is congested, so RCAFB reports congestion information to PCRF.When UE gets back to CellX, because the congestion state of CellX does not change, so RCAF can not notify PCRF.Therefore PCRF can think UE also under CellY.After this, PCAFB detects UE not under cellY, so RCAFB notify PCRF now UE be in non-congested state.Like this, PCRF can think that UE is in the community of non-congested.
For the problems of the prior art, at present effective solution is not yet proposed.
Summary of the invention
Main purpose of the present invention is the update process method and the device that provide a kind of Access Network congestion state reporting, congestion information, and to solve in correlation technique, PCRF cannot know the problems such as the true congestion state of UE region.
To achieve these goals, according to an aspect of the present invention, provide the Access Network congestion state reporting method of a kind of UE, comprising: RCAF entity obtains the network area of its management; In one of following situation, described RCAF entity reports the RUCI carrying congestion state indication information to PCRF entity, wherein, described congestion state indication information be used to indicate described UE congestion state for not congested: described network area is areas of congestion and described RCAF entity is determined UE and shifted out described areas of congestion; Described network area is not areas of congestion and described RCAF entity determines that UE is in described network area.
Preferably, described RCAF entity determines that UE shifts out described areas of congestion in the following manner: described RCAF entity obtains the user ID list under the described network area of its management, and wherein, the described network area that described RCAF entity obtains is areas of congestion; The local keeping records of described RCAF entity indicates described UE to be positioned at areas of congestion, and when there is not the user ID of described UE in described user ID list, then determines that described UE shifts out described areas of congestion.
Preferably, described RCAF entity, to after described PCRF entity reports described RUCI, also comprises: whether described PCRF entity determines whether to upgrade the congestion information of UE described in described local keeping records from same RCAF entity according to the congestion information of UE described in described RUCI and local keeping records.
Preferably, whether described PCRF entity determines from same RCAF entity the congestion information whether upgrading UE described in described local keeping records according to the congestion information of UE described in described RUCI and local keeping records, comprise: if the congestion information of UE described in described local keeping records and described RUCI are from same RCAF entity, then described PCRF entity upgrades the congestion information of UE described in described local keeping records according to described RUCI; And/or, if the congestion information of UE described in described local keeping records and described RUCI are from different RCAF entities and described PCRF receives the RUCI carrying described congestion state indication information, then described PCRF entity does not upgrade the congestion information of UE described in described local keeping records.
Preferably, the very first time stamp information generating described RUCI is carried in described RUCI.
Preferably, described RCAF entity is to after described PCRF entity reports described RUCI, comprise: if the second timestamp of the congestion information of UE stabbed early than the described very first time described in the local keeping records of PCRF, and when the congestion information of UE described in described local keeping records and described RUCI are from same RCAF entity, described PCRF entity upgrades the congestion information of UE described in described local keeping records according to described RUCI; And/or, if the second timestamp of the described congestion information of UE stabbed early than the described very first time described in described local keeping records, and the congestion information of UE described in described local keeping records and described RUCI are from different RCAF entities and described PCRF receives the RUCI carrying described congestion state indication information, then described PCRF entity does not upgrade the congestion information of UE described in described local keeping records.
According to another aspect of the present invention, provide a kind of update process method of UE congestion information, comprise: PCRF entity receives the wireless access network users face congestion information RUCI from wireless access network congestion aware function RCAF entity, wherein, congestion state indication information is carried in described RUCI, wherein, described congestion state indication information is used to indicate the congestion state of described UE for not congested; Described PCRF entity is according to described congestion state indication information, and in local keeping records, the congestion information of UE and described RUCI, whether from same RCAF entity, judge whether the congestion information upgrading UE described in local keeping records.
Preferably, described PCRF entity is according to described congestion state indication information, and in local keeping records the congestion information of UE and described RUCI whether from same RCAF entity, judge whether the congestion information upgrading UE described in local keeping records, comprise: if the congestion information of UE described in the local keeping records of PCRF entity and described RUCI are from same RCAF entity, then described PCRF entity upgrades the congestion information of UE described in local keeping records according to described congestion state indication information.
Preferably, described PCRF entity is according to described congestion state indication information, and in local keeping records the congestion information of UE and described RUCI whether from same RCAF entity, judge whether the congestion information upgrading UE described in local keeping records, comprise: if the congestion information of UE described in the local keeping records of PCRF from described RUCI from different RCAF entities, and the state of the congestion information of UE described in described local keeping records instruction is that congested and described RUCI carries described congestion state indication information, then described PCRF entity does not upgrade the congestion information of UE described in described local keeping records.
Preferably, described RUCI also carries the very first time stamp of RUCI described in described RCAF solid generation.
Preferably, described PCRF entity is according to described congestion state indication information, and in local keeping records the congestion information of UE and described RUCI whether from same RCAF entity, judge whether the congestion information upgrading UE described in local keeping records, comprise: if the second timestamp of the described congestion information of UE stabbed early than the described very first time described in the local keeping records of PCRF, and the congestion information of UE described in described local keeping records and described RUCI are from same RCAF entity, then described PCRF entity upgrades the congestion information of UE described in described local keeping records according to described RUCI, and/or, if the second timestamp of the congestion information of UE stabbed early than the described very first time described in described local keeping records, and the congestion information of UE described in described local keeping records and described RUCI are from different RCAF entities and described PCRF receives the RUCI carrying described congestion state indication information, then described PCRF entity does not upgrade the congestion information of UE described in described local keeping records.
According to a further aspect of the invention, provide the Access Network congestion state reporting device of a kind of UE, be applied to RCAF entity, comprise: acquisition module, for obtaining the network area of described RCAF entity management; Reporting module, for in one of following situation, described RCAF entity reports to "Policy and Charging Rules Function PCRF entity the RUCI carrying congestion state indication information, wherein, described congestion state indication information be used to indicate described UE congestion state for not congested: described network area is areas of congestion and described RCAF entity is determined UE and shifted out described areas of congestion; Described network area is not areas of congestion and described RCAF entity determines that UE is in described network area.
Preferably, described reporting module is used for when described RCAF entity determines that UE shifts out described areas of congestion in the following manner, report described RUCI: described RCAF entity obtains the user ID list under the described network area of its management, wherein, the described network area that described RCAF entity obtains is areas of congestion; The local keeping records of described RCAF entity indicates described UE to be positioned at areas of congestion, and when there is not the user ID of described UE in described user ID list, then determines that described UE shifts out described areas of congestion.
Preferably, described reporting module, also for reporting the described RUCI carrying the timestamp generating described RUCI.
According to a further aspect of the invention, provide a kind of update process device of UE congestion information, be applied to PCRF entity, comprise: receiver module, for receiving the wireless access network users face congestion information RUCI from wireless access network congestion aware function RCAF entity, wherein, in described RUCI, carry congestion state indication information, wherein, described congestion state indication information is used to indicate the congestion state of described UE for not congested; Judge module, for according to described congestion state indication information, and in local keeping records, the congestion information of UE and described RUCI, whether from same RCAF entity, judge whether the congestion information upgrading UE described in local keeping records.
Preferably, described judge module, for when the congestion information of UE described in the local keeping records of PCRF entity and described RUCI are from same RCAF entity, judges the congestion information upgrading UE described in local keeping records according to described congestion state indication information.
Preferably, described judge module, for the congestion information of UE described in the local keeping records of PCRF from described RUCI from different RCAF entities, and the state of the congestion information of UE described in described local keeping records instruction is congested and described RUCI when carrying described congestion state indication information, judges the congestion information not upgrading UE described in described local keeping records.
Preferably, described receiver module, for receiving the very first time stamp that the described RUCI carrying following information: described RCAF generates described RUCI.
Preferably, described judge module, for: described in described local keeping records, the second timestamp of the described congestion information of UE stabbed early than the described very first time, and the congestion information of UE described in described local keeping records and described RUCI are from same RCAF entity, judge the congestion information upgrading UE described in described local keeping records according to described RUCI; And/or, if the second timestamp of the described congestion information of UE stabbed early than the described very first time described in described local keeping records, and the congestion information of UE described in described local keeping records and described RUCI from different RCAF entities and described PCRF receive and carry described congestion state indication information RUCI, then judge the congestion information not upgrading UE described in described local keeping records.
Pass through the present invention, adopt in one of following situation, described RCAF entity reports the wireless access network users face congestion information RUCI carrying congestion state indication information to "Policy and Charging Rules Function PCRF entity, wherein, described congestion state indication information be used to indicate described UE congestion state for not congested: described network area is areas of congestion and described RCAF entity is determined UE and shifted out described areas of congestion; Described network area is not areas of congestion and described RCAF entity determines that UE is in the technological means of described network area, solves PCRF and cannot know the problems such as the true congestion state of UE region, make PCRF can know the time of day of PCRF.
Accompanying drawing explanation
Accompanying drawing described herein is used to provide a further understanding of the present invention, and form a application's part, schematic description and description of the present invention, for explaining the present invention, does not form inappropriate limitation of the present invention.In the accompanying drawings:
Fig. 1 is the strategy and charging control architecture PCC schematic diagram that in correlation technique, third generation partner program 3GPP defines;
Fig. 2 is the Organization Chart of PCRF cognitive radio Access Network information on load in correlation technique;
Fig. 3 is the flow chart of the Access Network congestion state reporting method according to the embodiment of the present invention;
Fig. 4 is the structured flowchart of the Access Network congestion state reporting device according to the embodiment of the present invention;
Fig. 5 is the flow chart of the update process method of congestion information according to the embodiment of the present invention;
Fig. 6 is the structured flowchart of the update process device of congestion information according to the embodiment of the present invention;
Fig. 7 is the Access Network congestion information report method flow chart of the UE according to the embodiment of the present invention 1;
Fig. 8 is the Access Network congestion information report method flow chart of the UE according to the embodiment of the present invention 2;
Fig. 9 is the Access Network congestion information report method flow chart of the UE according to the embodiment of the present invention 3;
Figure 10 is the Access Network congestion information report method flow chart of the UE according to the embodiment of the present invention 4;
Figure 11 is the Access Network congestion information report method flow chart of the UE according to the embodiment of the present invention 5;
Figure 12 is the Access Network congestion information report method flow chart of the UE according to the embodiment of the present invention 6;
Figure 13 is the Access Network congestion information report method flow chart of the UE according to the embodiment of the present invention 7.
Embodiment
Hereinafter also describe the present invention in detail with reference to accompanying drawing in conjunction with the embodiments.It should be noted that, when not conflicting, the embodiment in the application and the feature in embodiment can combine mutually.
Fig. 3 is the flow chart of the Access Network congestion state reporting method according to the embodiment of the present invention.As shown in Figure 3, the method comprises:
Step S302, RCAF entity obtains the network area of its management;
Step S304, in one of following situation, above-mentioned RCAF entity reports the RUCI carrying congestion state indication information to PCRF entity, wherein, above-mentioned congestion state indication information be used to indicate above-mentioned UE congestion state for not congested: (1) above-mentioned network area is areas of congestion and above-mentioned RCAF entity is determined UE and shifted out above-mentioned areas of congestion; (2) above-mentioned network area is not areas of congestion and above-mentioned RCAF entity determines that UE is in above-mentioned network area.
By each treatment step above-mentioned, PCRF entity can be made to obtain the true congestion state (congested or not congested) of network area residing for UE.
In a preferred embodiment, can determine that UE shifts out above-mentioned areas of congestion in the following manner: RCAF entity obtains the user ID list under the above-mentioned network area of its management, wherein, the above-mentioned network area that above-mentioned RCAF entity obtains is areas of congestion; The local keeping records of above-mentioned RCAF entity indicates above-mentioned UE to be positioned at areas of congestion, and when there is not the user ID of above-mentioned UE in above-mentioned user ID list, then determines that above-mentioned UE shifts out above-mentioned areas of congestion.
At above-mentioned RCAF entity to after above-mentioned PCRF entity reports above-mentioned RUCI, PCRF can perform following processing procedure: whether PCRF entity determines from same RCAF entity the congestion information whether upgrading above-mentioned UE in above-mentioned local keeping records according to the congestion information of above-mentioned UE in above-mentioned RUCI and local keeping records.In a preferred implementation process, above-mentioned processing procedure can show as following way of realization, but be not limited thereto: if the congestion information of above-mentioned UE and above-mentioned RUCI are from same RCAF entity in above-mentioned local keeping records, then above-mentioned PCRF entity upgrades the congestion information of above-mentioned UE in above-mentioned local keeping records according to above-mentioned RUCI; If congestion information and the above-mentioned RUCI of above-mentioned UE are from different RCAF entities and PCRF receives the RUCI carrying above-mentioned congestion state indication information in above-mentioned local keeping records, then above-mentioned PCRF entity does not upgrade the congestion information of above-mentioned UE in above-mentioned local keeping records.
In a preferred embodiment, the very first time stamp information generating above-mentioned RUCI is carried in above-mentioned RUCI.Now, above-mentioned RCAF entity is to after above-mentioned PCRF entity reports above-mentioned RUCI:
If the second timestamp of the congestion information of above-mentioned UE stabbed early than the above-mentioned very first time in the local keeping records of PCRF, and when in above-mentioned local keeping records, the congestion information of above-mentioned UE and above-mentioned RUCI are from same RCAF entity, above-mentioned PCRF entity upgrades the congestion information of above-mentioned UE in above-mentioned local keeping records according to above-mentioned RUCI; And/or,
If the second timestamp of the above-mentioned congestion information of above-mentioned UE stabbed early than the above-mentioned very first time in above-mentioned local keeping records, and in above-mentioned local keeping records, congestion information and the above-mentioned RUCI of above-mentioned UE are from different RCAF entities and above-mentioned PCRF receives the RUCI carrying described congestion state indication information, then above-mentioned PCRF entity does not upgrade the congestion information of above-mentioned UE in above-mentioned local keeping records.
In the present embodiment, also provide the Access Network congestion state reporting device of a kind of UE, be applied to RCAF entity, as shown in Figure 4, this device comprises:
Acquisition module 40, for obtaining the network area of described RCAF entity management;
Reporting module 42, for in one of following situation, the RUCI carrying congestion state indication information is reported to "Policy and Charging Rules Function PCRF entity, wherein, above-mentioned congestion state indication information be used to indicate above-mentioned UE congestion state for not congested: above-mentioned network area is areas of congestion and above-mentioned RCAF entity is determined UE and shifted out above-mentioned areas of congestion; Above-mentioned network area is not areas of congestion and above-mentioned RCAF entity determines that UE is in above-mentioned network area.
Reporting module 42 is for when above-mentioned RCAF entity determines that UE shifts out above-mentioned areas of congestion in the following manner, report above-mentioned RUCI: above-mentioned RCAF entity obtains the user ID list under the above-mentioned network area of its management, wherein, the above-mentioned network area that above-mentioned RCAF entity obtains is areas of congestion; The local keeping records of above-mentioned RCAF entity indicates above-mentioned UE to be positioned at areas of congestion, and when there is not the user ID of above-mentioned UE in above-mentioned user ID list, then determines that above-mentioned UE shifts out above-mentioned areas of congestion.
Alternatively, in a preferred implementation of the present embodiment, reporting module 42, for reporting the above-mentioned RUCI carrying the timestamp generating above-mentioned RUCI.
In the present embodiment, a kind of update process method of UE congestion information is also provided, as shown in Figure 5, comprises:
Step S502, PCRF entity receives the RUCI from RCAF entity, wherein, carries congestion state indication information in above-mentioned RUCI, and above-mentioned congestion state indication information is used to indicate the congestion state of described UE for not congested;
Step S504, PCRF entity is according to above-mentioned congestion state indication information, and in local keeping records, the congestion information of UE and above-mentioned RUCI, whether from same RCAF entity, judge whether the congestion information upgrading above-mentioned UE in local keeping records.
In a preferred embodiment, step S504 specifically can realize in the following manner, but is not limited thereto:
(1) if the congestion information of above-mentioned UE and above-mentioned RUCI are from same RCAF entity in the local keeping records of PCRF entity, then above-mentioned PCRF entity upgrades the congestion information of above-mentioned UE in local keeping records according to above-mentioned congestion state indication information;
(2) if in the local keeping records of PCRF the congestion information of above-mentioned UE from above-mentioned RUCI from different RCAF entities, and the state of the congestion information instruction of above-mentioned UE is that congested and above-mentioned RUCI carries above-mentioned congestion state indication information in above-mentioned local keeping records, then above-mentioned PCRF entity does not upgrade the congestion information of above-mentioned UE in above-mentioned local keeping records.
Above-mentioned RUCI also carries the very first time stamp of the above-mentioned RUCI of above-mentioned RCAF solid generation.Now, step S504 can show as following way of realization, but is not limited thereto:
If the second timestamp of the above-mentioned congestion information of above-mentioned UE stabbed early than the above-mentioned very first time in the local keeping records of PCRF, and the congestion information of above-mentioned UE and above-mentioned RUCI are from same RCAF entity in above-mentioned local keeping records, then above-mentioned PCRF entity upgrades the congestion information of above-mentioned UE in above-mentioned local keeping records according to above-mentioned RUCI; And/or,
If the second timestamp of the congestion information of above-mentioned UE stabbed early than the above-mentioned very first time in above-mentioned local keeping records, and in above-mentioned local keeping records, congestion information and the above-mentioned RUCI of above-mentioned UE are from different RCAF entities and above-mentioned PCRF receives the RUCI carrying above-mentioned congestion state indication information, then above-mentioned PCRF entity does not upgrade the congestion information of above-mentioned UE in above-mentioned local keeping records.
In the present embodiment, also provide a kind of update process device of UE congestion information, be applied to PCRF entity, as shown in Figure 6, this device comprises:
Receiver module 60, for receiving the wireless access network users face congestion information RUCI from wireless access network congestion aware function RCAF entity, wherein, congestion state indication information is carried in above-mentioned RUCI, wherein, above-mentioned congestion state indication information is used to indicate the congestion state of above-mentioned UE for not congested;
Judge module 62, for according to above-mentioned congestion state indication information, and in local keeping records, the congestion information of UE and above-mentioned RUCI, whether from same RCAF entity, judge whether the congestion information upgrading above-mentioned UE in local keeping records.
Preferably, judge module 62, during for the congestion information of above-mentioned UE in the local keeping records of PCRF entity and above-mentioned RUCI from same RCAF entity, judges the congestion information upgrading above-mentioned UE in local keeping records according to above-mentioned congestion state indication information.
Preferably, judge module 62, for the congestion information of above-mentioned UE in the local keeping records of PCRF from above-mentioned RUCI from different RCAF entities, and in above-mentioned local keeping records, the state of the congestion information instruction of above-mentioned UE is congested and above-mentioned RUCI when carrying above-mentioned congestion state indication information, judges the congestion information not upgrading above-mentioned UE in above-mentioned local keeping records.
Preferably, receiver module 60, for receiving the very first time stamp that the above-mentioned RUCI carrying following information: above-mentioned RCAF generates above-mentioned RUCI.
Preferably, judge module 62, for: in above-mentioned local keeping records, the second timestamp of the above-mentioned congestion information of above-mentioned UE stabbed early than the above-mentioned very first time, and the congestion information of above-mentioned UE and above-mentioned RUCI are from same RCAF entity in above-mentioned local keeping records, judge the congestion information upgrading above-mentioned UE in above-mentioned local keeping records according to above-mentioned RUCI; And/or,
If the second timestamp of the above-mentioned congestion information of above-mentioned UE stabbed early than the above-mentioned very first time in above-mentioned local keeping records, and in above-mentioned local keeping records congestion information and the above-mentioned RUCI of above-mentioned UE from different RCAF entities and above-mentioned PCRF receive and carry above-mentioned congestion state indication information RUCI, then judge the congestion information not upgrading above-mentioned UE in above-mentioned local keeping records.
In order to understand above-described embodiment better, describe in detail below in conjunction with preferred embodiment.
The main design idea of following examples is:
RCAF reports angle:
RCAF receives from RANOAM jam state information, if upper once report in the region at UE place still keep congestion state, and RCAF judges that UE moves out areas of congestion, then RCAF indicates the state of UE not congested at RUCI; PCRF makes the following judgment after receiving RUCI:
1) if PCRF preserves the congested RCAF reported with the RCAF newly to report from same RCAF, and the state that PCRF preserves be congested and state in the RUCI that newly reports for not congested, then the state updating of UE is not congested according to RUCI by PCRF;
2) if PCRF preserves the congested RCAF reported from the RCAF newly reported from different RCAF, and the state that PCRF preserves is congested and state in the RUCI that newly reports is not congested, then PCRF does not do and upgrades.
RCAF receives from RANOAM jam state information, if upper once report in the region at UE place become not congested by congested, and RCAF judges that UE is still in this region, then RCAF indicates the state of UE to be not congested at RUCI; The state of UE is set to not congested according to RUCI by PCRF.
RCAF at RUCI in the mark of also carrying timestamp and RCAF self.According to timestamp, PCRF judges which is up-to-date RUCI, on the above basis judged, new RUCI can cover old RUCI.
PCRF receiving angle:
PCRF receives the RUCI report of RCAF:
If RUCI comes from the identical RCAF of congestion information that PCRF preserves, then PCRF upgrades the congestion information of the UE of PCRF preservation according to the RUCI newly reported;
If RUCI comes from the different RCAF of congestion information that PCRF preserves, then PCRF upgrades according to following principle:
If the state that PCRF preserves be congested and state in the RUCI that newly reports for not congested, then PCRF does not do and upgrades.
If the state that PCRF preserves is not congested and state in the RUCI that newly reports is congested, then PCRF is updated to congested.
PCRF needs to judge which RUCI is up-to-date according to timestamp.
Embodiment 1
The present embodiment describe when E-UTRAN accesses, the report method of network load information.Wherein UE1 moves to CellY (congested) from CellX (not congested).Fig. 7 is the flow chart according to the embodiment of the present invention 1, and as shown in Figure 7, this flow process comprises the steps:
701.RCAF1 obtains congested relevant OAM information and involved area from RANOAM.Because CellX is not now in congestion state, and hypothesis RCAF1 to receive also be not in congestion state from CellX in OAM information last time, did not therefore comprise CellX in involved area.
702.RCAF1 determines the MME be correlated with according to the involved area that step 701 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).
703.RCAF1 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.Wherein do not comprise IMSI1.In addition RCAF1 can also carry the mark (RCAFId1) of timestamp (Timestamp1) and RCAF.
704.RCAF1 reports RCUI to PCRF;
705:PCRF carries out strategic decision-making according to RUCI.If IMSI1 is in charge of by PCRF1, PCRF1 can not be subject to the relevant congestion information of UE1 that RCAF1 reports.Before supposing, IMSI1 does not have congestion information in PCRF1 information, and therefore PCRF1 thinks that IMSI1 is in non-congested state.
706.RCAF2 obtains congested relevant OAM information and involved area from RANOAM, is in congestion state (ECGIId2) comprising CellY.
707.RCAF2 determines the MME be correlated with according to the involved area that step 706 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).Comprising the IMSI (IMSI1) of UE1 under CellY (ECGIId2) and the APN (APN1 and APN2) of activation.
708.RCAF2 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.Comprising IMSI1.In addition RCAF2 can also carry the mark (RCAFId2) of timestamp (Timestamp2) and RCAF2.
Table 3-1
709.RCAF1 reports RUCI to PCRF;
310. are in charge of by PCRF1 due to IMSI1, so the congestion information that will receive about IMIS1 of PCRF1.Do not have congestion information due in the context of IMSI1 on PCRF1 before, therefore PCRF1 upgrades the context of IMSI1 according to the congestion information reported.PCRF1 formulates corresponding strategy according to congestion information.The relevant congested context of the IMSI1 now preserved on PCRF1 is as follows
Table 3-2
Embodiment 2
The present embodiment describe when E-UTRAN accesses, the report method of network load information.Wherein UE1 moves to CellY (congested) from CellX (congested).Fig. 8 is the flow chart according to the embodiment of the present invention 2, and as shown in Figure 8, this flow process comprises the steps:
801.RCAF1 obtains congested relevant OAM information and involved area from RANOAM.Because CellX is now in congestion state, so involved area comprises areas of congestion CellX (ECGIId1).
802.RCAF1 determines the MME be correlated with according to the involved area that step 801 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).Comprising the IMSI (IMSI1) of UE1 under CellX and the APN (APN1 and APN2) of activation.
803.RCAF1 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.Comprising IMSI1.In addition RCAF1 can also carry the mark of timestamp (Timestamp1) and RCAF1.
804.RCAF1 reports RCUI to PCRF;
Table 4-1
805:PCRF1 carries out strategic decision-making according to RUCI.If IMSI1 is in charge of by PCRF1, before supposing, IMSI1 does not have congestion information in the context of PCRF1, and therefore PCRF1 upgrades the context of IMSI1 according to the congestion information reported.PCRF1 formulates corresponding strategy according to congestion information.The relevant congested context of the IMSI1 now preserved on PCRF1 is as follows
Table 4-2
806.RCAF2 obtains congested relevant OAM information and involved area from RANOAM, is in congestion state comprising CellY.
807.RCAF2 determines the MME be correlated with according to the involved area that step 806 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF2.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).Comprising the IMSI (IMSI1) of UE1 under CellY and the APN (APN1 and APN2) of activation.
808.RCAF2 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.Comprising IMSI1.
Table 4-3
809.RCAF2 reports RUCI to PCRF.
810. are in charge of by PCRF1 due to IMSI1, and so PCRF1 will receive the congestion information of the relevant IMSI1 that RCAF2 provides.According to RCAFId2, PCR1F judges that UE1 is moved to new RCAF (congestion information originally preserved is reported by RCAF1).Then PCRF1 is the context that UE1 preserves according to the information updating PCRF1 that RCAF2 reports.As shown in the table.PCRF1 can alleviate strategy according to the formulation of new congestion information is congested.In addition PCRF1 additionally can also consider that timestamp judges which RUCI determines whether upgrading for the up-to-date congestion situation of UE1 further, only has when Timestamp1 just performs above-mentioned decision logic early than Timestamp2, PCRF1.
Table 4-4
811.RCAF1 obtains congested relevant OAM information and involved area from RANOAM again.And CellX is now in congestion state, so areas of congestion comprises the ECGI (ECGIId1) of CellX.
812.RCAF1 determines the MME be correlated with according to the involved area that step 811 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).Because UE1 has been moved to below CellY, in the user list therefore under CellX, do not comprise the IMSI1. of UE1
813.RCAF1 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.In addition RCAF1 can also carry the mark of timestamp (TimeStampe3) and RCAF1.RCAF1 does not comprise IMSI according in the IMSI list received, and therefore judges that UE1 have left CellX.Obvious UE1 is not also in the affected community that any RCAF1 is in charge of.Therefore RCAF1 judges that UE1 is not as congested.
Table 4-5
814.RCAF1 reports RUCI to PCRF;
815:PCRF1 carries out strategic decision-making according to RUCI.PCRF1 receives the RUCI reported.The RCAF that reports preserved in context due to IMSI1 in PCRF1 is RCAF2, and the state that in the RUCI that reports of RCAF1, IMSI1 is corresponding is not for congested, then PCRF1 does not do any renewal for IMSI1.Therefore PCRF1 thinks that UE1 is still in congestion state.In addition PCRF1 additionally can also consider that timestamp judges which RUCI determines whether upgrading for the up-to-date congestion situation of UE1 further, only has when Timestamp2 just performs above-mentioned decision logic early than Timestamp3, PCRF1.
Embodiment 3
The present embodiment describe when E-UTRAN accesses, the report method of network load information.Wherein UE1 moves to CellY (not congested) from CellX (congested).Fig. 9 is the flow chart according to the embodiment of the present invention 3, and as shown in Figure 9, this flow process comprises the steps:
901.RCAF1 obtains congested relevant OAM information and involved area from RANOAM.Because CellX is now in congestion state, so involved area comprises areas of congestion CellX (ECGIId1).
902.RCAF1 determines the MME be correlated with according to the involved area that step 901 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).Comprising the IMSI (IMSI1) of UE1 under CellX and the APN (APN1 and APN2) of activation.
903.RCAF1 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.Comprising IMSI1.In addition RCAF1 can also carry the mark of timestamp (Timestamp1) and RCAF1.
904.RCAF1 reports RCUI to PCRF;
Table 5-1
905:PCRF1 carries out strategic decision-making according to RUCI.If IMSI1 is in charge of by PCRF1, before supposing, IMSI1 does not have congestion information in the context of PCRF1, and therefore PCRF1 upgrades the context of IMSI1 according to the congestion information reported.PCRF1 formulates corresponding strategy according to congestion information.The relevant congested context of the IMSI1 now preserved on PCRF1 is as follows
Table 5-2
906.RCAF2 obtains congested relevant OAM information and involved area from RANOAM, because CellY is in not congestion state, and RCAF2 upper once report in obtain information CellY and be also in not congestion state, so do not comprise CellY in involved area.
907.RCAF2 determines the MME be correlated with according to the involved area that step 906 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF2.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).
908.RCAF2 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.Wherein do not comprise IMSI1.
909.RCAF2 reports RUCI to PCRF.
910. owing to not comprising IMSI1 in RUCI, and therefore PCRF1 can not receive the relevant RUCI of IMSI1.PCRF1 also can not do for IMSI1 and upgrade.
911.RCAF1 obtains congested relevant OAM information and involved area from RANOAM again.And CellX is now in congestion state, so areas of congestion comprises the ECGI (ECGIId1) of CellX.
912.RCAF1 determines the MME be correlated with according to the involved area that step 911 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).Because UE1 has been moved to below CellY, in the user list therefore under CellX, do not comprise the IMSI1. of UE1
913.RCAF1 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.In addition RCAF1 can also carry the mark of timestamp (Timestampe3) and RCAF1.According to the IMSI list received, RCAF1 judges that UE1 have left CellX.Obvious UE1 is not also in the affected community that any RCAF1 is in charge of.Therefore the congestion state of UE1 is not congested by RCAF1.
Table 5-3
914.RCAF1 reports RUCI to PCRF;
915:PCRF1 carries out strategic decision-making according to RUCI.PCRF1 receives the RUCI reported.The RCAF that reports preserved in context due to IMSI1 in PCRF1 is RCAF1, and new RUCI to report also be from RCAF1, and the state that in the new RUCI reported at RCAF1, IMSI1 is corresponding is not congested.Therefore PCRF1 to do for IMSI1 according to the RUCI newly reported and upgrades.According to network strategy, the relevant following PCRF of congested context of the IMSI1 now preserved on PCRF1 can think that UE1 is in non-congested state, can take corresponding strategy.In addition PCRF1 additionally can also consider that timestamp judges which RUCI determines whether upgrading for the up-to-date congestion situation of UE1 further, only has when Timestamp1 just performs above-mentioned decision logic early than Timestamp3, PCRF1.
Table 5-5
Embodiment 4
The present embodiment describe when E-UTRAN accesses, the report method of network load information.Wherein UE1 moves to again CellX (congested) after CellX (congested) moves to CellY (congested).Figure 10 is the flow chart according to the embodiment of the present invention 4, and as shown in Figure 10, this flow process comprises the steps:
1001.RCAF1 obtains congested relevant OAM information and involved area from RANOAM.Because CellX is now in congestion state, so areas of congestion comprises the ECGI (ECGIId1) of CellX.
1002.RCAF1 determines the MME be correlated with according to the involved area that step 1001 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).Comprising the IMSI (IMSI1) of UE1 under CellX and the APN (APN1 and APN2) of activation.
1003.RCAF1 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.Comprising IMSI1.In addition RCAF1 can also carry the mark of timestamp and RCAF1.
1004.RCAF1 reports RCUI to PCRF;
Table 6-1
1005:PCRF1 carries out strategic decision-making according to RUCI.If IMSI1 is in charge of by PCRF1, before supposing, IMSI1 does not have congestion information in the context of PCRF1, and therefore PCRF1 upgrades the context of IMSI1 according to the congestion information reported.PCRF1 formulates corresponding strategy according to congestion information.The relevant congested context of the IMSI1 now preserved on PCRF1 is as follows.
Table 6-2
1006.RCAF2 obtains congested relevant OAM information and involved area from RANOAM, is in congestion state comprising CellY.
1007.RCAF2 determines the MME be correlated with according to the involved area that step 1006 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF2.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).Comprising the IMSI (IMSI1) of UE1 under CellY and the APN (APN1 and APN2) of activation.
1008.RCAF2 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.Comprising IMSI1.
Table 6-3
1009.RCAF2 reports RUCI to PCRF.
1010. are in charge of by PCRF1 due to IMSI1, and so PCRF1 will receive the congestion information of the relevant IMSI1 that RCAF2 provides.According to RCAFId2, the RUCI that PCRF1 reports according to RCAF2, PCR1F judge that UE1 is moved to new RCAF.Then PCRF1 is the context that UE1 preserves according to the information updating PCRF1 that RCAF2 reports.As shown in the table.PCRF1 can alleviate strategy according to the formulation of new congestion information is congested.In addition PCRF1 additionally can also consider that timestamp judges which RUCI determines whether upgrading for the up-to-date congestion situation of UE1 further, only has when Timestamp1 just performs above-mentioned decision logic early than Timestamp2, PCRF1.
Table 6-4
1011.RCAF1 obtains congested relevant OAM information and involved area from RANOAM again.And CellX is now in congestion state, so areas of congestion comprises the ECGI (ECGIId1) of CellX.
1012.RCAF1 determines the MME be correlated with according to the involved area that step 1011 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).If now UE1 again CellY moved back to CellX, still comprise the IMSI1. (because other UE may move out CellX, therefore may not comprise the IMSI of some UE in user list) of UE1 in the user list therefore under CellX
1013.RCAF1 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.In addition RCAF1 can also carry the mark of timestamp (Timestamp3) and RCAF1.
Table 6-5
1014.RCAF1 reports RUCI to PCRF;
1015:PCRF1 carries out strategic decision-making according to RUCI.PCRF1 receives the RUCI reported.Because the middle up and down RCAF that reports preserved of IMSI1 in PCRF1 is according to RCAFId1, RCAF2, PCR1F judge that UE1 is moved to again new RCAF.Then PCRF1 is the context that UE1 preserves according to the information updating PCRF1 that RCAF1 reports.As shown in the table.PCRF1 can alleviate strategy according to the formulation of new congestion information is congested.In addition PCRF1 additionally can also consider that timestamp judges which RUCI determines whether upgrading for the up-to-date congestion situation of UE1 further, only has when Timestamp2 just performs above-mentioned decision logic early than Timestamp3, PCRF1.
Table 6-6
1016.RCAF2 obtains congested relevant OAM information and involved area from RANOAM again.And CellY is now in congestion state, so areas of congestion comprises the ECGI (ECGIId2) of CellY.
1017.RCAF2 determines the MME be correlated with according to the involved area that step 1016 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).Because UE1 has been moved to below CellX, in the user list therefore under CellY, do not comprise the IMSI1. of UE1
1018.RCAF2 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.In addition RCAF2 can also carry the mark of timestamp (Timestamp4) and RCAF2.According to the IMSI list received, RCAF2 judges that UE1 have left CellY.Obvious UE1 is not also in the affected community that any RCAF2 is in charge of.Therefore RCAF2 arranges the congestion state of UE1 for not congested.
Table 6-7
1019.RCAF2 reports RUCI to PCRF;
1020:PCRF1 carries out strategic decision-making according to RUCI.PCRF1 receives the RUCI reported.Due to IMSI1 in PCRF1 up and down in the RCAF that reports that preserves be RCAF1, and new RUCI is from RCAF2, and the state that in the RUCI reported at RCAF2, IMSI1 is corresponding is not for congested, then PCRF1 does not do any renewal for IMSI1.Therefore PCRF1 thinks that UE1 is still in congestion state.In addition PCRF1 additionally can also consider that timestamp judges which RUCI determines whether upgrading for the up-to-date congestion situation of UE1 further, only has when Timestamp3 just performs above-mentioned decision logic early than Timestamp4, PCRF1.
Embodiment 5
The present embodiment describe when E-UTRAN accesses, the report method of network load information.Wherein UE1 moves to again CellX (congested) after CellX (congested) moves to CellY (not congested).Figure 11 is the flow chart according to the embodiment of the present invention 5, and as shown in figure 11, this flow process comprises the steps:
1101.RCAF1 obtains congested relevant OAM information and involved area from RANOAM.Because CellX is now in congestion state, so areas of congestion comprises the ECGI (ECGIId1) of CellX.
1102.RCAF1 determines the MME be correlated with according to the involved area that step 1101 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).Comprising the IMSI (IMSI1) of UE1 under CellX and the APN (APN1 and APN2) of activation.
1103.RCAF1 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.Comprising IMSI1.In addition RCAF1 can also carry the mark of timestamp and RCAF1.
1104.RCAF1 reports RCUI to PCRF;
Table 7-1
1105:PCRF1 carries out strategic decision-making according to RUCI.If IMSI1 is in charge of by PCRF1, before supposing, IMSI1 does not have congestion information in the context of PCRF1, and therefore PCRF1 upgrades the context of IMSI1 according to the congestion information reported.PCRF1 formulates corresponding strategy according to congestion information.The relevant congested context of the IMSI1 now preserved on PCRF1 is as follows
Table 7-2
1106.RCAF2 obtains congested relevant OAM information and involved area from RANOAM, because CellY is in not congestion state, suppose that in the information that the RCAF2 last time obtains from OAM, CellY is also in not congestion state, so do not comprise CellY in involved area
1107.RCAF2 determines the MME be correlated with according to the involved area that step 1106 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF2.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).
1108.RCAF2 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.Wherein do not comprise IMSI1.
1109.RCAF2 reports RUCI to PCRF.
1110. owing to not comprising IMSI1 in RUCI, and therefore PCRF1 can not receive the relevant RUCI of IMSI1.
PCRF1 also can not do for IMSI1 and upgrade.
(if RCAF2 does not receive reporting of any involved area in step 1106, then step 1107-step 1110 does not perform)
1111.RCAF1 obtains congested relevant OAM information and involved area from RANOAM again.And CellX is now in congestion state, so areas of congestion comprises the ECGI (ECGIId1) of CellX.
1112.RCAF1 determines the MME be correlated with according to the involved area that step 1111 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).If now UE1 again CellY moved back to CellX, still comprise the IMSI1. (because other UE may move out CellX, therefore may not comprise the IMSI of some UE in user list) of UE1 in the user list therefore under CellX
1113.RCAF1 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.In addition RCAF1 can also carry the mark of timestamp and RCAF1.
Table 7-3
1114.RCAF1 reports RUCI to PCRF;
1115:PCRF1 carries out strategic decision-making according to RUCI.PCRF1 receives the RUCI reported.Because the middle up and down RCAF that reports preserved of IMSI1 in PCRF1 is according to RCAFid1, RCAF2, PCR1F judge that UE1 is moved to again new RCAF.Then PCRF1 is the context that UE1 preserves according to the information updating PCRF1 that RCAF1 reports.As shown in the table.PCRF1 can alleviate strategy according to the formulation of new congestion information is congested.In addition PCRF1 additionally can also consider that timestamp judges which RUCI determines whether upgrading for the up-to-date congestion situation of UE1 further, only has when Timestamp1 just performs above-mentioned decision logic early than Timestamp3, PCRF1.
Table 7-4
1116.RCAF2 obtains congested relevant OAM information and involved area, because CellY is in not congestion state, so do not comprise CellY in involved area from RANOAM
1117.RCAF2 determines the MME be correlated with according to the involved area that step 1106 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF2.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).
1118.RCAF2 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.Wherein do not comprise IMSI1.
1119.RCAF2 reports RUCI to PCRF.
1120. owing to not comprising IMSI1 in RUCI, and therefore PCRF1 can not receive the relevant RUCI of IMSI1.PCRF1 also can not do for IMSI1 and upgrade.
Embodiment 6
The present embodiment describe when E-UTRAN accesses, the report method of network load information.Wherein UE1 is from CellX resident period, and CellX is from congested to not congested.Figure 12 is the flow chart according to the embodiment of the present invention 6, and as shown in figure 12, this flow process comprises the steps:
1201.RCAF1 obtains congested relevant OAM information and involved area from RANOAM.Because CellX is now in congestion state, so areas of congestion comprises the ECGI (ECGIId1) of CellX.
1202.RCAF1 determines the MME be correlated with according to the involved area that step 1201 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).Comprising the IMSI (IMSI1) of UE1 under CellX and the APN (APN1 and APN2) of activation.
1203.RCAF1 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.Comprising IMSI1.In addition RCAF1 can also carry the mark of timestamp (Timestamp1) and RCAF1.
1204.RCAF1 reports RCUI to PCRF;
Table 8-1
1205:PCRF1 carries out strategic decision-making according to RUCI.If IMSI1 is in charge of by PCRF1, before supposing, IMSI1 does not have congestion information in the context of PCRF1, and therefore PCRF1 upgrades the context of IMSI1 according to the congestion information reported.PCRF1 formulates corresponding strategy according to congestion information.The relevant congested context of the IMSI1 now preserved on PCRF1 is as follows
Table 8-2
1206.RCAF1 obtains congested relevant OAM information and involved area from RANOAM, and now CellX has congestion state to arrive not congestion state, so involved area comprises areas of congestion CellX.
1207.RCAF1 determines the MME be correlated with according to the involved area that step 1206 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF1.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).Comprising the IMSI (IMSI1) of UE1 under CellX and the APN (APN1 and APN2) of activation.
1208.RCAF2 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.Comprising IMSI1.
Table 8-3
1209.RCAF1 reports RUCI to PCRF.
1210:PCRF1 carries out strategic decision-making according to RUCI.PCRF1 receives the RUCI reported.Because the middle up and down RCAF that reports preserved of IMSI1 in PCRF1 is that RCAF1, PCRF1 judge UE1 still at RCAF1 according to RCAFid1, but change over not congestion state from congestion state.Then PCRF1 is the context that UE1 preserves according to the information updating PCRF1 that RCAF1 reports.In addition PCRF1 additionally can also consider that timestamp judges which RUCI determines whether upgrading for the up-to-date congestion situation of UE1 further, only has when Timestamp1 just performs above-mentioned decision logic early than Timestamp2, PCRF1.As shown in the table.PCRF1 can alleviate strategy according to the formulation of new congestion information is congested.
Table 8-4
Embodiment 7
The present embodiment describe when E-UTRAN accesses, the report method of network load information.Wherein UE1 is from CellX resident period, and CellX is never congested to congested.Figure 13 is the flow chart according to the embodiment of the present invention 7, and as shown in figure 13, this flow process comprises the steps:
1301.RCAF1 obtains congested relevant OAM information and involved area from RANOAM.Because CellX is now in not congestion state, so do not comprise the ECGI (ECGIId1) of CellX in areas of congestion.
1302.RCAF1 determines the MME be correlated with according to the involved area that step 1301 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).
1303.RCAF1 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.Wherein do not comprise IMSI1.In addition RCAF1 can also carry the mark of timestamp (Timestamp1) and RCAF1.
1304.RCAF1 reports RCUI to PCRF;
1305:PCRF1 carries out strategic decision-making according to RUCI.If IMSI1 is in charge of by PCRF1, PCRF1 can not receive the congestion information about UE1.Before supposing, IMSI1 does not have congestion information in the context of PCRF1, and therefore PCRF1 upgrades the context of IMSI1 according to the congestion information reported.
1306.RCAF1 obtains congested relevant OAM information and involved area from RANOAM, now CellX by not congestion state to congestion state, so involved area comprises congested CellX.
1307.RCAF1 determines the MME be correlated with according to the involved area that step 1306 receives, and subscribes to the IMSI list of involved area to relevant MME.Each MME provides the APN of UE (i.e. IMSI) list of involved area and the activation of correspondence to RCAF1.Involved area (i.e. areas of congestion) can be base station (identifying with eNBID), also can be community (identifying with ECGI).Comprising the IMSI (IMSI1) of UE1 under CellX and the APN (APN1 and APN2) of activation.
1308.RCAF1 generates RUCI according to receiving information, the IMSI list of congested RAN congestion state, activation APN.Comprising IMSI1.
Table 9-1
1309.RCAF1 reports RUCI to PCRF.
1310:PCRF1 carries out strategic decision-making according to RUCI.PCRF1 receives the RUCI reported.Due to IMSI1 in PCRF1 up and down in the RCAF that reports that preserves be that RCAF1, PCRF1 judge UE1 still at RCAF1 according to RCAFid1, but never congestion state changed over congestion state.Then PCRF1 is the context that UE1 preserves according to the information updating PCRF1 that RCAF1 reports.In addition PCRF1 additionally can also consider that timestamp judges which RUCI determines whether upgrading for the up-to-date congestion situation of UE1 further, only has when Timestamp1 just performs above-mentioned decision logic early than Timestamp2, PCRF1.As shown in the table.PCRF1 can alleviate strategy according to the formulation of new congestion information is congested.
Table 9-2
In the flow process of embodiment 1 to embodiment 7, involved area is community, be base station this method is also similar for involved area, and namely at RUCI affected area domain information is Base Station Identification.
In the flow process of embodiment 1 to embodiment 7, network is that each UE selects a PCRF, and be that each APN of each UE selects a PCRF to be also similar for networking, the RUCI namely for same IMSI may need to report different PCRF according to different APN.
For the scene that UE accesses from UTRAN, because SGSN directly can obtain the IMSI list of involved area from OAM, be therefore that SGSN obtains the little IMSI list of involved area and this region from OAM with above-described embodiment 1 to embodiment 7 difference.RCAF based on logical construct RUCI similar in above-described embodiment, and can report corresponding PCRF.PCRF also can based on logical construct similar in above-described embodiment according to congestion information in user's context
In another embodiment, additionally provide a kind of software, this software is for performing the technical scheme described in above-described embodiment and preferred implementation.
In another embodiment, additionally provide a kind of storage medium, store above-mentioned software in this storage medium, this storage medium includes but not limited to: CD, floppy disk, hard disk, scratch pad memory etc.
Obviously, those skilled in the art should be understood that, above-mentioned of the present invention each module or each step can realize with general calculation element, they can concentrate on single calculation element, or be distributed on network that multiple calculation element forms, alternatively, they can realize with the executable program code of calculation element, thus, they can be stored and be performed by calculation element in the storage device, and in some cases, step shown or described by can performing with the order be different from herein, or they are made into each integrated circuit modules respectively, or the multiple module in them or step are made into single integrated circuit module to realize.Like this, the present invention is not restricted to any specific hardware and software combination.
These are only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.

Claims (19)

1. an Access Network congestion state reporting method for user equipment (UE), is characterized in that, comprising:
Wireless access network congestion aware function RCAF entity obtains the network area of its management;
In one of following situation, described RCAF entity reports the wireless access network users face congestion information RUCI carrying congestion state indication information to "Policy and Charging Rules Function PCRF entity, wherein, described congestion state indication information is used to indicate the congestion state of described UE for not congested:
Described network area is areas of congestion and described RCAF entity determines that UE shifts out described areas of congestion; Described network area is not areas of congestion and described RCAF entity determines that UE is in described network area.
2. method according to claim 1, is characterized in that, described RCAF entity determines that UE shifts out described areas of congestion in the following manner:
Described RCAF entity obtains the user ID list under the described network area of its management, and wherein, the described network area that described RCAF entity obtains is areas of congestion;
The local keeping records of described RCAF entity indicates described UE to be positioned at areas of congestion, and when there is not the user ID of described UE in described user ID list, then determines that described UE shifts out described areas of congestion.
3. method according to claim 1, is characterized in that, described RCAF entity, to after described PCRF entity reports described RUCI, also comprises:
Whether described PCRF entity determines from same RCAF entity the congestion information whether upgrading UE described in described local keeping records according to the congestion information of UE described in described RUCI and local keeping records.
4. method according to claim 3, it is characterized in that, whether described PCRF entity determines from same RCAF entity the congestion information whether upgrading UE described in described local keeping records according to the congestion information of UE described in described RUCI and local keeping records, comprising:
If the congestion information of UE described in described local keeping records and described RUCI are from same RCAF entity, then described PCRF entity upgrades the congestion information of UE described in described local keeping records according to described RUCI; And/or,
If the congestion information of UE described in described local keeping records and described RUCI are from different RCAF entities and described PCRF receives the RUCI carrying described congestion state indication information, then described PCRF entity does not upgrade the congestion information of UE described in described local keeping records.
5. method according to claim 1, is characterized in that, carries the very first time stamp information generating described RUCI in described RUCI.
6. method according to claim 5, is characterized in that, described RCAF entity, to after described PCRF entity reports described RUCI, comprising:
If the second timestamp of the congestion information of UE stabbed early than the described very first time described in the local keeping records of PCRF, and when the congestion information of UE described in described local keeping records and described RUCI are from same RCAF entity, described PCRF entity upgrades the congestion information of UE described in described local keeping records according to described RUCI; And/or,
If the second timestamp of the described congestion information of UE stabbed early than the described very first time described in described local keeping records, and the congestion information of UE described in described local keeping records and described RUCI are from different RCAF entities and described PCRF receives the RUCI carrying described congestion state indication information, then described PCRF entity does not upgrade the congestion information of UE described in described local keeping records.
7. a update process method for user equipment (UE) congestion information, is characterized in that, comprising:
"Policy and Charging Rules Function PCRF entity receives the wireless access network users face congestion information RUCI from wireless access network congestion aware function RCAF entity, wherein, congestion state indication information is carried in described RUCI, wherein, described congestion state indication information is used to indicate the congestion state of described UE for not congested;
Described PCRF entity is according to described congestion state indication information, and in local keeping records, the congestion information of UE and described RUCI, whether from same RCAF entity, judge whether the congestion information upgrading UE described in local keeping records.
8. method according to claim 7, it is characterized in that, described PCRF entity is according to described congestion state indication information, and in local keeping records the congestion information of UE and described RUCI whether from same RCAF entity, judge whether the congestion information upgrading UE described in local keeping records, comprising:
If the congestion information of UE described in the local keeping records of PCRF entity and described RUCI are from same RCAF entity, then described PCRF entity upgrades the congestion information of UE described in local keeping records according to described congestion state indication information.
9. method according to claim 7, it is characterized in that, described PCRF entity is according to described congestion state indication information, and in local keeping records the congestion information of UE and described RUCI whether from same RCAF entity, judge whether the congestion information upgrading UE described in local keeping records, comprising:
If the congestion information of UE described in the local keeping records of PCRF from described RUCI from different RCAF entities, and the state of the congestion information of UE described in described local keeping records instruction is that congested and described RUCI carries described congestion state indication information, then described PCRF entity does not upgrade the congestion information of UE described in described local keeping records.
10. method according to claim 7, is characterized in that, described RUCI also carries the very first time stamp of RUCI described in described RCAF solid generation.
11. methods according to claim 10, it is characterized in that, described PCRF entity is according to described congestion state indication information, and in local keeping records the congestion information of UE and described RUCI whether from same RCAF entity, judge whether the congestion information upgrading UE described in local keeping records, comprising:
If the second timestamp of the described congestion information of UE stabbed early than the described very first time described in the local keeping records of PCRF, and the congestion information of UE described in described local keeping records and described RUCI are from same RCAF entity, then described PCRF entity upgrades the congestion information of UE described in described local keeping records according to described RUCI; And/or,
If the second timestamp of the congestion information of UE stabbed early than the described very first time described in described local keeping records, and the congestion information of UE described in described local keeping records and described RUCI are from different RCAF entities and described PCRF receives the RUCI carrying described congestion state indication information, then described PCRF entity does not upgrade the congestion information of UE described in described local keeping records.
The Access Network congestion state reporting device of 12. 1 kinds of UE, is applied to wireless access network congestion aware function RCAF entity, it is characterized in that, comprising:
Acquisition module, for obtaining the network area of described RCAF entity management;
Reporting module, for in one of following situation, described RCAF entity reports the wireless access network users face congestion information RUCI carrying congestion state indication information to "Policy and Charging Rules Function PCRF entity, wherein, described congestion state indication information is used to indicate the congestion state of described UE for not congested:
Described network area is areas of congestion and described RCAF entity determines that UE shifts out described areas of congestion; Described network area is not areas of congestion and described RCAF entity determines that UE is in described network area.
13. devices according to claim 12, is characterized in that, described reporting module is used for when described RCAF entity determines that UE shifts out described areas of congestion in the following manner, reports described RUCI:
Described RCAF entity obtains the user ID list under the described network area of its management, and wherein, the described network area that described RCAF entity obtains is areas of congestion;
The local keeping records of described RCAF entity indicates described UE to be positioned at areas of congestion, and when there is not the user ID of described UE in described user ID list, then determines that described UE shifts out described areas of congestion.
14. devices according to claim 12, is characterized in that, described reporting module, also for reporting the described RUCI carrying the timestamp generating described RUCI.
The update process device of 15. 1 kinds of user equipment (UE) congestion informations, is applied to "Policy and Charging Rules Function PCRF entity, it is characterized in that, comprising:
Receiver module, for receiving the wireless access network users face congestion information RUCI from wireless access network congestion aware function RCAF entity, wherein, in described RUCI, carry congestion state indication information, wherein, described congestion state indication information is used to indicate the congestion state of described UE for not congested;
Judge module, for according to described congestion state indication information, and in local keeping records, the congestion information of UE and described RUCI, whether from same RCAF entity, judge whether the congestion information upgrading UE described in local keeping records.
16. devices according to claim 15, it is characterized in that, described judge module, for when the congestion information of UE described in the local keeping records of PCRF entity and described RUCI are from same RCAF entity, judge the congestion information upgrading UE described in local keeping records according to described congestion state indication information.
17. devices according to claim 15, it is characterized in that, described judge module, for the congestion information of UE described in the local keeping records of PCRF from described RUCI from different RCAF entities, and the state of the congestion information of UE described in described local keeping records instruction is congested and described RUCI when carrying described congestion state indication information, judges the congestion information not upgrading UE described in described local keeping records.
18. devices according to claim 15, is characterized in that, described receiver module, for receiving the very first time stamp that the described RUCI carrying following information: described RCAF generates described RUCI.
19. devices according to claim 18, is characterized in that, described judge module, for:
Described in described local keeping records, the second timestamp of the described congestion information of UE stabbed early than the described very first time, and the congestion information of UE described in described local keeping records and described RUCI are from same RCAF entity, judge the congestion information upgrading UE described in described local keeping records according to described RUCI; And/or,
If the second timestamp of the described congestion information of UE stabbed early than the described very first time described in described local keeping records, and the congestion information of UE described in described local keeping records and described RUCI from different RCAF entities and described PCRF receive and carry described congestion state indication information RUCI, then judge the congestion information not upgrading UE described in described local keeping records.
CN201410425740.XA 2014-08-26 2014-08-26 Access network congestion status reporting method and device and congestion information update processing method and device Withdrawn CN105472635A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201410425740.XA CN105472635A (en) 2014-08-26 2014-08-26 Access network congestion status reporting method and device and congestion information update processing method and device
PCT/CN2015/073802 WO2016029673A1 (en) 2014-08-26 2015-03-06 Access network congestion status reporting method, congestion information update processing method, and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201410425740.XA CN105472635A (en) 2014-08-26 2014-08-26 Access network congestion status reporting method and device and congestion information update processing method and device

Publications (1)

Publication Number Publication Date
CN105472635A true CN105472635A (en) 2016-04-06

Family

ID=55398715

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201410425740.XA Withdrawn CN105472635A (en) 2014-08-26 2014-08-26 Access network congestion status reporting method and device and congestion information update processing method and device

Country Status (2)

Country Link
CN (1) CN105472635A (en)
WO (1) WO2016029673A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107734544A (en) * 2016-08-11 2018-02-23 上海诺基亚贝尔股份有限公司 method and apparatus for congestion control

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090305701A1 (en) * 2008-06-09 2009-12-10 Qualcomm Incorporated Method and apparatus for pcc enhancement for flow based mobility
CN101711041A (en) * 2009-12-09 2010-05-19 华为技术有限公司 Congestion control method, operation-maintenance center equipment and base station
CN102075898A (en) * 2010-12-21 2011-05-25 华为技术有限公司 Service control method, device and system
US20110252123A1 (en) * 2010-04-08 2011-10-13 Kamakshi Sridhar Policy And Charging Rules Function In An Extended Self Optimizing Network
CN102223663A (en) * 2010-04-15 2011-10-19 中兴通讯股份有限公司 Method and system for obtaining network load
CN102742318A (en) * 2012-03-06 2012-10-17 华为技术有限公司 Congestion control method, device, and system
CN102763365A (en) * 2010-02-18 2012-10-31 阿尔卡特朗讯公司 Method for PCRF to autonomously respond to cell capacity shortage
CN102802239A (en) * 2011-05-25 2012-11-28 中兴通讯股份有限公司 Method and system for providing access network selection strategy based on network state
US20140022897A1 (en) * 2012-07-14 2014-01-23 Tekelec, Inc. Methods, systems, and computer readable media for dynamically controlling congestion in a radio access network
US8724467B2 (en) * 2011-02-04 2014-05-13 Cisco Technology, Inc. System and method for managing congestion in a network environment
EP2731373A1 (en) * 2012-11-13 2014-05-14 NTT DoCoMo, Inc. Method and apparatus for congestion notification

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090305701A1 (en) * 2008-06-09 2009-12-10 Qualcomm Incorporated Method and apparatus for pcc enhancement for flow based mobility
CN101711041A (en) * 2009-12-09 2010-05-19 华为技术有限公司 Congestion control method, operation-maintenance center equipment and base station
CN102763365A (en) * 2010-02-18 2012-10-31 阿尔卡特朗讯公司 Method for PCRF to autonomously respond to cell capacity shortage
US20110252123A1 (en) * 2010-04-08 2011-10-13 Kamakshi Sridhar Policy And Charging Rules Function In An Extended Self Optimizing Network
CN102223663A (en) * 2010-04-15 2011-10-19 中兴通讯股份有限公司 Method and system for obtaining network load
CN102075898A (en) * 2010-12-21 2011-05-25 华为技术有限公司 Service control method, device and system
US8724467B2 (en) * 2011-02-04 2014-05-13 Cisco Technology, Inc. System and method for managing congestion in a network environment
CN102802239A (en) * 2011-05-25 2012-11-28 中兴通讯股份有限公司 Method and system for providing access network selection strategy based on network state
CN102742318A (en) * 2012-03-06 2012-10-17 华为技术有限公司 Congestion control method, device, and system
US20140022897A1 (en) * 2012-07-14 2014-01-23 Tekelec, Inc. Methods, systems, and computer readable media for dynamically controlling congestion in a radio access network
EP2731373A1 (en) * 2012-11-13 2014-05-14 NTT DoCoMo, Inc. Method and apparatus for congestion notification

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107734544A (en) * 2016-08-11 2018-02-23 上海诺基亚贝尔股份有限公司 method and apparatus for congestion control
CN107734544B (en) * 2016-08-11 2021-05-07 上海诺基亚贝尔股份有限公司 Method and apparatus for congestion control

Also Published As

Publication number Publication date
WO2016029673A1 (en) 2016-03-03

Similar Documents

Publication Publication Date Title
US11172435B2 (en) Network entity, user equipment and method for the control and use of network slices
CN112188533B (en) Method and device for reporting network performance
CN105580459B (en) Service request method and user equipment
CN105532043B (en) For reselecting the method for being responsible for the network node of control plane
CN104521257A (en) Method for reporting mobility information in wireless communication system and apparatus for supporting same
CN106664730B (en) Management method and related device of wireless communication system
US20170374604A1 (en) Method and nodes for handling a user equipment's access to a mobile communications network
US20150181494A1 (en) Methods, Computer Program Products and Apparatuses Enabling to Improve Handovers in Mobile Communication Networks
WO2010077190A1 (en) Emergency call support during roaming
US11785480B2 (en) Method and apparatus to support RACH optimization and delay measurements for 5G networks
CN109314718A (en) A kind of service control method and equipment based on the band of position
CN106538002B (en) Method and device for reporting user equipment location information
EP2989822B1 (en) Reducing location update signaling between network nodes of a mobile communication network
KR20140131676A (en) Apparatus and method for policy and charging control in flat networks
CN105472635A (en) Access network congestion status reporting method and device and congestion information update processing method and device
CN105376796A (en) Method and device for reporting congestion state of access network, and updating congestion information of access network
EP3240249B1 (en) Congestion information management method and apparatus
CN106304023B (en) Business access control and neighboring BS relationship querying method, device and system
CN103249067A (en) Link processing method and device, data flow reporting method and device
CN105897607A (en) Management method of congestion information, device and system
KR20150024689A (en) Method and apparatus for acquiring location information of user equipment based on event
CN103929756A (en) Network information processing method, device and system
CN102868976A (en) Method, device and system for processing businesses of machinery communication equipment
CN107567091A (en) Location area updating method and mobile station
CN105208547A (en) Congestion processing method, device, RAN RCAF (RAN Congestion Awareness Function) entity and PCRF (Policy and Charging Rules Function) entity

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
WW01 Invention patent application withdrawn after publication
WW01 Invention patent application withdrawn after publication

Application publication date: 20160406