WO2012100606A1 - Procédé et système pour gérer des ressources - Google Patents

Procédé et système pour gérer des ressources Download PDF

Info

Publication number
WO2012100606A1
WO2012100606A1 PCT/CN2011/084064 CN2011084064W WO2012100606A1 WO 2012100606 A1 WO2012100606 A1 WO 2012100606A1 CN 2011084064 W CN2011084064 W CN 2011084064W WO 2012100606 A1 WO2012100606 A1 WO 2012100606A1
Authority
WO
WIPO (PCT)
Prior art keywords
wlan
handover
fixed network
resource management
pcrf
Prior art date
Application number
PCT/CN2011/084064
Other languages
English (en)
Chinese (zh)
Inventor
毕以峰
刘国燕
周晓云
宗在峰
霍玉臻
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012100606A1 publication Critical patent/WO2012100606A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1446—Reselecting a network or an air interface over a different radio air interface technology wherein at least one of the networks is unlicensed

Definitions

  • the present invention relates to the field of communications, and in particular, to a resource management method and system. Background technique
  • the Policy and Charging Rules Function Entity (PCRF) is the core of the PCC and is responsible for policy decision making and billing rules.
  • the PCRF provides network control rules based on service data flows, including traffic data flow detection, Gating Control, Quality of Service (QoS) control, and data flow based charging rules.
  • the PCRF sends its established policies and accounting rules to the PCEF for execution. At the same time, the PCRF also needs to ensure that these rules are consistent with the user's subscription information.
  • the basis for formulating the policy and charging rules by the PCRF includes: obtaining information related to the service from the AF; obtaining the subscription information with the user policy charging control from the Subscription Profile Repository (SPR); and obtaining the information related to the bearer related network from the PCEF .
  • SPR Subscription Profile Repository
  • EPS supports interworking with non-3GPP systems. Interworking with non-3GPP systems is implemented through the S2a/b/c interface, which acts as an anchor between 3GPP and non-3GPP systems.
  • the system architecture diagram of EPS is shown in Figure 1. The non-3GPP system is divided into trusted non-3GPP IP access and untrusted non 3GPP IP access.
  • Trusted non-3GPP IP access can be directly connected to the P-GW through the S2a interface, which uses PMIPv6 (Proxy Mobile IP version 6, Proxy Mobile IP Version 6) protocol; untrusted non-3GPP IP access needs to pass ePDG (Evolved Packet)
  • PMIPv6 Proxy Mobile IP version 6, Proxy Mobile IP Version 6
  • ePDG Evolved Packet
  • the Data Gateway, the evolved packet data gateway, is connected to the P-GW, and the interface between the ePDG and the P-GW is S2b, using a 5 ⁇ or GTP (General Packet Radio Service Tunnel Protocol) protocol, and the UE IPSec (Internet Protocol security) commands and data are encrypted and protected between User Equipment (User Equipment) and ePDG.
  • S2c provides user plane related control and mobility support between the UE and the P-GW.
  • the supported mobility management protocol is DSMIPv6 (Mobile IPv6 Support for Lo Dual Stack Hosts and Router
  • the access network is generally referred to as a fixed network, and specifically refers to a wireless local area network (WLAN) access.
  • WLAN wireless local area network
  • EPC Evolved Packet Core
  • H(e)NB home base station
  • H(e)NB occupies a fixed line.
  • the UE accesses the mobile core network EPC through the WLAN access network (fixed network), and the scenario belongs to the non-
  • 3GPP WLAN access network / fixed network access to EPC technology.
  • the basic criteria for accessing the requirements of the above EPS support and non-3GPP systems are specifically divided into S2a, S2b and
  • the 5 EPS supports access to the home base station (HeNB), which is a small, low-power base. Station, deployed in indoor places such as homes, offices and corporate buildings.
  • HeNB home base station
  • the Closed Subscriber Group (CSG) is a concept introduced after the introduction of a home base station. Usually a family or a user inside an enterprise forms a closed user group, which is identified by a CSG ID. The home base station serving the users in this closed subscriber group has the same CSG ID. When a closed subscriber group is served by only one home base station, the closed subscriber group can also be directly identified by the home base station identity (e.g., BS ID).
  • BS ID home base station identity
  • the CSG user and/or the non-CSG user can distinguish different levels, and the service priority, the service quality, and the service category that are enjoyed by the different priorities may be different.
  • the user can access the home base station corresponding to multiple closed user groups, for example, the user's office, home, and the like.
  • the concept of allowing a closed user group list to be introduced is therefore introduced. This list is stored in the user's UE and the user data server on the network side.
  • home base stations There are three usage modes for home base stations: closed mode, mixed mode, and open mode.
  • closed mode only the CSG subscription user to which the home base station belongs can access the base station and enjoy the service provided by the base station; when the home base station is in the open mode, any operator subscription user can access the base station, The home base station is equivalent to the macro base station; when the home base station is in the hybrid mode, it also allows any operator to sign up the user or the roaming user to access the use, but to distinguish the different levels according to whether the user subscribes to the CSG information, that is, sign the CSG. Users have higher service priorities when using hybrid home base stations, enjoying better quality of service and service categories.
  • the HeNB usually enters the EPS core network through the leased fixed network line, as shown in Figure 2.
  • the security gateway (SeGW) is shielded in the core network.
  • the data between the HeNB and the SeGW is encapsulated by IPSec (IP Security).
  • IPSec IP Security
  • the HeNB can directly connect to the MME and the S-GW of the core network through the IPSec tunnel established with the SeGW, and can also connect to the MME and the S-GW through the HeNB GW, that is, the HeNB GW is an optional network element.
  • the Home eNodeB Management System (HeMS) is not shown in the architecture diagram because it has little to do with the present invention.
  • the Universal Mobile Telecommunications System supports access to the home base station HNB (Home NodeB). Similar to Figure 2 and its description. The difference is that the Serving General Packet Radio Service Support Node (SGSN) is used instead of the S-GW, and the Gateway General Packet Radio Service Support Node (GGSN) is replaced by a Gateway General Packet Radio Service Support Node (GGSN). P-GW.
  • SGSN Serving General Packet Radio Service Support Node
  • GGSN Gateway General Packet Radio Service Support Node
  • P-GW Gateway General Packet Radio Service Support Node
  • the QoS of the fixed line that is accessed by the H(e)NB is usually limited by the contract between the owner of the HeNB/HNB and the fixed network operator. Therefore, when the 3GPP UE accesses the 3GPP core network through the HeNB/HNB, the required QoS cannot exceed the contracted QoS of the fixed line provided by the fixed network operator. Otherwise, the QoS of the UE access service will not be guaranteed, especially for the Guaranteed Bit Rate (GBR) service. Therefore, for 3GPP networks and fixed networks, a unified management mechanism is needed to implement user/connection/service admission control. For example: When a new service is initiated, the service can only be accepted if the fixed network has sufficient resources/bandwidth and the mobile network resources are sufficient. Otherwise, the service should be rejected. .
  • Step 401 The H(e)NB is powered on, establishes an IPsec tunnel to the SeGW, and registers with the H(e)NB GW/MME to establish a Sl/Iuh session.
  • Step 402 The UE accesses through the H(e)NB to complete an air interface access operation, an authentication and authorization operation, and the like.
  • Step 403, ⁇ is triggered, sending a create session request to the S-GW, and the S-GW sends a create session request to the P-GW to request to establish a segmented GTP tunnel;
  • Step B The P-GW initiates an IP-CAN session establishment request to the PCRF.
  • Step 404 The P-GW allocates an IP address to the UE, and transmits the session response message to the S-GW and the MME at one time.
  • Step 405 The MME establishes an air interface connection and an access network bearer by using a subsequent operation, and sends an IP address allocated by the P-GW to the UE to the UE.
  • Step A triggered by step B, the PCRF initiates a policy session establishment in reverse, and the PCRF establishes an S9* session to the BPCF (Broadband Forum Policy Control Function/Framework), and the BPCF establishes/refreshes to the BNG. /BRAS fixed network policy session.
  • BPCF Broadband Forum Policy Control Function/Framework
  • the session established in step A and step B has an association relationship in the PCRF. Therefore, the policy information can communicate between the corresponding network elements of the fixed network and the mobile network through the policy session and the association relationship.
  • the H(e)NB is powered on, and an IPsec tunnel is established to the SeGW.
  • Step A The SeGW is triggered to initiate an S16/T1 interface session establishment operation to the H(e)NB PF (Policy Function).
  • H(e)NB PF Policy Function
  • H(e)NB to H(e)NB GW/MME registration, establishing a Sl/Iuh session.
  • Step B.1 Policy session establishment.
  • the H(e)NB GW or the MME is triggered to establish an SI 5 interface session to the H(e)NB PF, and the H(e)NB PF is triggered to establish an S9* session to the BPCF, and the BPCF is triggered to establish to the BNG/ BRAS policy session.
  • Step B.2 H(e)NB initiates a policy session establishment (T2 interface session) to the H(e)NB PF,
  • the H(e)NB PF is triggered to initiate an S9* session establishment to the BPCF, and the BPCF establishes/refreshes the fixed network policy session to the BNG/BRAS.
  • the UE After completing the foregoing operations, if the UE accesses the H(e)NB, the UE uses the established policy session to exchange policy information between the fixed network and the mobile network.
  • the policy session has a corresponding relationship at each network element node. Therefore, the policy information can communicate with the corresponding network elements of the fixed network and the mobile network through the policy session and the association relationship.
  • Steps B.1 and B.2 are two-choice, and step A and scheme A are respectively composed of scheme 2 and scheme 2. Introduction of WLAN access scenarios
  • Step 301 The UE accesses the fixed network.
  • the fixed network supports 3GPP-based authentication, and the UE completes the authentication and authorization by using the BNG/BRAS and the AAA of the fixed network as a proxy to the HSS/AAA of the EPC network.
  • the 3GPP-based authentication mode is optional. If the 3GPP-based authentication mode is not supported, the UE only performs access authentication to the AAA of the fixed network.
  • Step 302 The UE acquires a local IP address assigned by the fixed network (generally BNG/BRAS).
  • Step 302 and step 301 are interactions of multiple messages, and it is not necessarily that step 302 must occur after step 301.
  • the UE completes obtaining the local IP address and completing the authentication authorization in steps 301 and 302.
  • Step A.1 Policy session establishment.
  • BNG/BRAS initiates a fixed network policy session establishment to BPCF, and BPCF receives the trigger After that, establish an S9* session with the PCRF.
  • PCRF which may pass visited PCRF (VPCRF) 0 or more sessions are part of the policy session BPCF and home PCRF (H-PCRF) to establish a session.
  • VPCRF visited PCRF
  • H-PCRF home PCRF
  • Step 303 The UE establishes an IPsec tunnel with the ePDG, and completes the authentication to the 3GPP HSS/AAA.
  • Step A.2 Policy session establishment.
  • the ePDG is triggered to initiate a policy session establishment operation (Gxb* session) to the PCRF.
  • the PCRF (or VPCRF if roaming) initiates a policy session (S9* session) establishment to the BPCF.
  • Step 304 The ePDG sends a PBU (Proxy Binding Update) message to the P-GW to request to establish a binding relationship.
  • PBU Proxy Binding Update
  • Step B the PCRF initiates a policy session establishment operation (IP-CAN session) to the PCRF.
  • IP-CAN session IP-CAN session
  • the P-GW directly establishes a policy session with the home PCRF (HPCRF); if it is the local grooming scenario of the roaming mode, the P-GW establishes a policy session with the VPCRF.
  • the VPCRF is in the HPCRF interaction strategy information.
  • the PCRF performs session association with the IP-CAN session established in this step and the S9* session established in step A.1 or the Gxb* established in step A.2. .
  • the S9* session or the Gxb* session will be connected to the hPCRF via the S9 session, ie the hPCRF is associated with the S9 session and the IP-CAN session.
  • Step 305 the P-GW allocates an IP address to the UE, and transmits the message to the ePDG through a PBA (Proxy Binding Ack) message;
  • PBA Proxy Binding Ack
  • Step 306 An IPsec tunnel is established between the ePDG and the UE, and the address is transmitted to the UE by using an IKEv2 message.
  • Step A.3 After being triggered by the IP-CAN session establishment, the V/HPCRF initiates a policy session (S9* session) to the BPCF in reverse;
  • the BPCF is triggered by the establishment operation of the S9* session, and reversely establishes/refreshes the fixed network policy session between the BNG/BRAS and the BPCF.
  • steps A.1, A.2, A.3 and step B are used to establish a policy session, and step B is a mandatory step.
  • Steps A.1, A.2, and A.3 are three choices. The relationship of one represents three different schemes.
  • the policy session established by A.l, A.2, or A.3 and the policy session established by step B establish an association relationship at the PCRF. Therefore, the policy information can communicate between the fixed network and the mobile network of the fixed network through the policy session and the association relationship.
  • step 304 and step 305 are respectively PIPv and PBA messages of PMIPv6, and in addition, another alternative protocol may be adopted: GTP protocol.
  • GTP protocol the GTP protocol is adopted, the ePDG sends a session request message to the P-GW, and the P-GW responds to the ePDG by creating a session response message.
  • the S2c access scenario exists in addition to the scenario in which the UE accesses the EPC through the S2b-PMIP mode.
  • the S2c scenario is divided into two cases: trusted access and untrusted access.
  • the main difference between the trusted S2c access scenario and the S2b scenario is that the step 304 and step 305 messages are no longer from ePDG to P-.
  • the GW sends a binding request, but the UE sends a BU request directly to the P-GW. After the P-GW allocates an address, it sends the message to the UE through the BA message.
  • the main difference between the untrusted S2c access scenario and the S2b scenario is that, in addition to the steps 304 and 305, the message is sent by the UE directly to the P-GW, and the P-GW allocates the address and sends the message to the UE through the BA message.
  • the IPsec tunnel establishment step of steps 303 and 306 and the policy session step of A.2 need not be performed again.
  • the interworking of S2b and S2c (trusted/untrusted) scenarios is mainly reflected in mobility management. There is basically no difference in policy session establishment and policy interworking.
  • UEs may access through H(e)NB and WLAN at the same time or at different times. Because H(e)NB and WLAN belong to the same enterprise or home, the occupied line is the same fixed-line link/backhaul network. a specific fixed network The bandwidth owned by the link/backhaul network is fixed by subscription, that is, the combined bandwidth of the sum of the H(e)NB and the WLAN.
  • the various access scenarios shown above mainly have the following problems.
  • the UE accesses from the H(e)NB, and some other devices access from the WLAN.
  • the contracted bandwidth of the fixed network link/backhaul network is running low.
  • the UE switches from the H(e)NB to the WLAN access, it needs to apply for resources from the WLAN access first.
  • the system finds that the fixed network/backhaul network has insufficient resources, so the handover fails.
  • the H(e)NB and the WLAN accessed by the UE are in the same fixed network link, and the UE will naturally release the resources occupied by the H(e)NB after switching to the WLAN, so that Lead to insufficient resources.
  • the same problem occurs when the UE is switched from the WLAN to the H(e)NB.
  • the UE is dual-mode dual-standby, can access from both H(e)NB and WLAN, and can migrate data streams back and forth in different access systems.
  • H(e)NB and the WLAN that the UE accesses at the same time are on the same fixed network link, and the subscription bandwidth of the fixed network link is almost left, if the UE migrates from the H(e)NB to the WLAN access
  • the IP data stream needs to be applied for resources from the WLAN.
  • the system finds that the fixed network link has insufficient resources and the data stream fails to be migrated, resulting in service interruption.
  • the H(e)NB and the WLAN that the UE accesses are on the same fixed network link.
  • the resources occupied by the H(e)NB are naturally released. This will not lead to insufficient resources. Conversely, the same problem exists when the UE has a WLAN to migrate data streams to the H(e)NB.
  • the main objective of the present invention is to provide a resource management method and system, which are avoided when a UE switches or migrates between an H(e)NB and a WLAN under the same fixed network link. The handover failed due to insufficient transient resources.
  • a resource management method including:
  • the UE When the UE performs flow migration or handover between the H(e)NB and the WLAN, it is determined according to the fixed network tunnel information whether the UE accesses from the H(e)NB and the WLAN under the same fixed network link;
  • the method for accepting the handover or the flow migration is:
  • the (agent) admission control by the decision entity includes: accepting or rejecting resource allocation, modification, reconfiguration, preemption, or bearer setup/modification/update; or accepting or rejecting handover or flow migration.
  • the UE Before the UE performs the flow migration, the UE has been simultaneously accessed by the WLAN and the H(e)NB, and the WLAN and the H(e)NB are both under the same fixed network link;
  • the UE before the UE performs the handover, the UE has accessed through the H(e)NB or through the WLAN, and the WLAN and the H(e)NB belong to the same fixed network link;
  • the method for determining is: confirming that the tunnel information of the UE from the WLAN access and the access from the H(e)NB is the same or that the tunnel information identifies the same fixed network link, and accordingly, determining whether the flow or handover of the UE is Performed under the same fixed network link;
  • the method of accepting the handover or the flow migration is: admission control by the P-GW.
  • the tunnel information is aggregated at the BPCF; the method of accepting the handover or the flow migration is: performing admission control by the BPCF;
  • H(e)NB PF and PCRF are combined, and H(e)NB PF/PCRF is a convergence point; the method of accepting the handover or flow migration is: H(e)NB PF/PCRF for admission control;
  • the PCRF is a unified convergence point; the method of accepting the handover or flow migration is: admission control by the PCRF.
  • the method for judging is: querying from the BPCF to the fixed network to determine whether the two tunnel information identifies the same fixed network link, and confirming that the UE is from the same fixed network link when the determination result is yes. H(e)NB and WLAN access;
  • the method of accepting the handover or stream migration is as follows: Other network elements are entrusted by BPCF or BPCF for admission control.
  • a resource management system comprising: a resource management decision unit and a resource management execution unit; wherein, when the UE performs flow migration or handover between the H(e)NB and the WLAN;
  • the resource management decision unit is configured to determine, according to the fixed network tunnel information, whether the UE accesses the HeNB and the WLAN under the same fixed network fixed network link, and notifies the resource management execution unit of the determination result;
  • the resource management execution unit is configured to accept the handover or the flow migration when the determination result is yes.
  • the resource management execution unit when accepting the handover or the flow migration, is configured to: control the decision entity to perform (proxy) admission control, including: accepting or rejecting resource allocation, modification, reconfiguration, preemption, or bearer establishment/modification/ Update; or, accept or reject the switch or stream migration.
  • the UE Before the UE performs the flow migration, the UE has been simultaneously accessed by the WLAN and the H(e)NB, and the WLAN and the H(e)NB are both under the same fixed network link;
  • the UE before the UE performs the handover, the UE has accessed through the H(e)NB or through the WLAN, and the WLAN and the H(e)NB belong to the same fixed network link;
  • the resource management decision unit When the resource management decision unit performs the determining, it is used to: confirm that the tunnel information of the UE when accessing from the WLAN and the access from the H(e)NB is the same or the tunnel information identifies the same fixed network link, according to the It is determined that the flow migration or handover of the UE is performed under the same fixed network link; when the resource management execution unit accepts the handover or the flow migration, the resource management execution unit is configured to: control the P-GW to perform admission control.
  • the tunnel information is aggregated at the BPCF; when the resource management execution unit accepts the handover or the flow migration, the method is used to: control the BPCF to accept the control;
  • H(e)NB PF and PCRF are combined, and H(e)NB PF/PCRF is a convergence point; when the resource management execution unit accepts the handover or flow migration, it is used to: control H(e)NB PF /PCRF for admission control;
  • the PCRF is a unified convergence point; when the resource management execution unit accepts the handover or the flow migration, it is used to: control the PCRF to accept the control.
  • the H(e)NB and the WLAN are in the same one of the fixed network links, but the two reported tunnel information are different.
  • the resource management decision unit performs the determining, the method is used to: control the BPCF to the fixed network query, Determining whether the two tunnel information identifies the same fixed network link, and confirming that the UE is accessed from the H(e)NB and the WLAN under the same fixed network link when the determination result is yes;
  • the resource management execution unit When the resource management execution unit accepts the handover or the flow migration, it is used to: control the BPCF or the BPCF to entrust other network elements to perform admission control.
  • the method and system of the present invention ensure that when the UE switches or migrates between the H(e)NB and the WLAN under the same fixed network link, the handover failure caused by the shortage of instantaneous resources can be effectively avoided.
  • FIG. 1 is a schematic diagram of an architecture of a non-3GPP access to an EPS
  • FIG. 2 is a schematic diagram of a UE accessing an H(e)NB and a WLAN under the same fixed network link;
  • FIG. 3 is a flow chart of the prior art UE accessing the EPC through the WLAN;
  • FIG. 4 is a flowchart of one of the schemes for a UE in the prior art to access an EPC through an H(e)NB;
  • FIG. 5 is a second and a third scheme of a UE of the prior art accessing an EPC through an H(e)NB;
  • FIG. 6 is a flowchart of resource management according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of resource management according to another embodiment of the present invention.
  • FIG. 8 is a flowchart of resource management according to still another embodiment of the present invention.
  • FIG. 9 is a flowchart of resource management according to still another embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a resource management process of the present invention.
  • FIG 11 is a diagram of a resource management system of the present invention. detailed description
  • the P-GW or (V-) PCRF or BPCF can determine whether the UE is from the same one according to the fixed network tunnel information.
  • the HeNB and the WLAN under the fixed network link access, and accept the handover or flow migration request when the determination result is yes.
  • the proxy admission control can be performed by the P-GW or the (V-) PCRF or BPCF.
  • Embodiments of the present invention are based on a variety of scenarios in which a WLAN accesses an EPC as a trusted or untrusted network, accessed through a PMIP, GTP protocol, or DSPMIP protocol.
  • the strategy of H(e)NB is controlled by three methods: PCRF control or H(e)NB PF control.
  • PCRF control or H(e)NB PF control.
  • a policy control entity such as BPCF or PCRF
  • P-GW proxy network element
  • the admission control refers to: accepting or rejecting resource allocation, modification, reconfiguration, preemption, or bearer setup/modification/update (H(e)NB PF/BPCF/PCRF/P-GW functions) , or, accept or reject the switch or stream migration (the function of the P-GW).
  • the scenario on which the embodiment of the present invention is based is: when the H(e)NB accesses the fixed network, the RG (Residential Gateway) functions as a bridging function or a routing function, and the UE applies the mobile network user identity when accessing the fixed network, and The fixed network can recognize the identity.
  • the RG Residential Gateway
  • the backhual and the fixed network backhaul network refer to a fixed network link.
  • the fixed network link may be identified by tunnel information, and the tunnel information includes one or more of the following: The IP address assigned by the terminal, the IP address assigned by the SeGW to the terminal, the SeGW address, the address and port number after the NAT translation of the network address translation, and the identifier of the HeNB.
  • the PCRF when used as the convergence point of the tunnel information, it may be the PCRF at the home, which is called HPCRF or PCRF, or may be called the PCRF, which is called VPCRF.
  • the UE has been simultaneously accessed through the WLAN and the H(e)NB, and the WLAN and the H(e)NB are both under the same backhaul, and the flow migration may occur at any time.
  • the trusted S2c mode is adopted, and the policy session is established by the mode A.1 or the mode A.3 in FIG. 3.
  • the tunnel information is already sent through the BU message. To the P-GW.
  • the tunnel information is also sent to the P-GW.
  • the strategy control method is the one shown in Figure 4.
  • the P-GW can determine that the handover of the UE is performed under the same backhaul, and confirm that the UE is from the The HeNB and the WLAN are connected under the same fixed network link; at this time, the P-GW proxy accepts control, allowing resource allocation/modification at the time of handover. See Figure 6 for the implementation process.
  • the UE has access through the H(e)NB, and the WLAN and the H(e)NB are both under the same backhaul, and the UE switching between the two access modes (from H(e)NB to WLAN) may occur at any time.
  • the WLAN accesses the EPC in the S2c mode, and the policy session is established through the mode A.1 or the mode A.3 in FIG. 3.
  • the tunnel information is sent to the P- through the BU message.
  • the H(e)NB accesses the EPC, the tunnel information is also sent to the P-GW.
  • the strategy control method is the one shown in Figure 4.
  • the P-GW can determine that the handover of the UE is performed under the same backhaul; - GW proxy admission control, allowing resource allocation/modification at handover.
  • the resource control mode adopted by the UE is the two modes shown in FIG. 5, so the UE reports from the WLAN and the H(e)NB.
  • the tunnel information can be aggregated at the BPCF before it can be judged whether it is under the same backhaul; therefore, the BPCF performs admission control, allowing resource allocation/modification. See flowchart 9.
  • H(e)NB and VPCRF are combined into one, so H(e)NB PF/VPCRF becomes a convergence point, and then it can be judged whether it is under the same backhaul; therefore, by BPCF Admission control, allowing resource allocation/modification. See flowchart 8.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • the difference between this embodiment and the embodiments 1 and 2 is that when the UE accesses from the WLAN, the access mode of the S2b is adopted.
  • the resource control of H(e)NB is still based on A.1 and A.2 shown in Figure 3.
  • the resource control mode of H(e)NB is still in the mode shown in Figure 4.
  • proxy admission control is performed by the P-GW. See implementation flow chart 6.
  • the difference between this embodiment and the embodiment 3 is that when the UE accesses from the WLAN, the access mode of the S2b is adopted.
  • H(e)NB In the resource control mode, the resource control of H(e)NB still adopts A.1 and A.2, H(e)NB resource control mode is still in the way shown in Figure 5.
  • proxy admission control is performed by the P-GW. See flowcharts 9 and 8.
  • the H(e)NB access mode is as shown in FIG. 4, and the WLAN access adopts the A.2 mode of FIG. 3, where the VPCRF is a unified convergence point, and the VPCRF performs admission control, allowing resources. Assign/modify. See Figure 6 and Figure 7.
  • the H(e)NB is in the same backhual as the WLAN, but the reported tunnel information is different.
  • the BPCF to the fixed network query to determine whether the two tunnel information identifies the same backhual, and when the judgment result is yes, the BPCF or BPCF entrusts other network elements to accept control, allowing resource allocation/modification. . See implementation flow chart 9.
  • Step 601 The UE accesses.
  • Case 1 The UE accesses the EPC system in dual mode dual standby mode through H(e)NB and WLAN, and establishes multiple connections to the same P-GW.
  • Case 2 The UE accesses through one of the H(e)NB or WLAN radio access technologies, and currently switches from H(e)NB or WLAN to WLAN or H(e)NB.
  • Step 602 The UE sends a binding request message to the P-GW to request flow migration/switching.
  • the UE If it is the flow migration described in Case 1, the UE carries the flow description information for advertising that the P-GW needs to migrate the IP flow; if it is the handover introduced in Case 2, the UE carries the handover indication to the P-GW for request handover.
  • Step 603 The P-GW initiates an IP-CAN session modification request operation to the PCRF to request resource authorization.
  • Step 604 the PCRF responds to the P-GW with an IP-CAN session modification response, and authorizes the resource It is notified to the P-GW.
  • the P-GW determines whether the system is in the same backhual according to the tunnel information or whether the system before and after the handover is under the same backhual. If it is under the same backhual, the P-GW directly performs proxy admission control to allow resource allocation/modification.
  • the P-GW After receiving the flow migration or handover request, the P-GW requests the PCRF through the IP-CAN session, and the PCRF requests the resource authorization from the BPCF. If the fixed network resources are sufficient, the resource authorization is returned by the BPCF until the P-GW is notified, and the P-GW allows the flow migration/switching. Otherwise, the stream migration or the switch fails.
  • the tunnel information is already communicated to the P-GW in the prior art.
  • the tunnel information may include the following information: a CPE address and a port number, an H(e)NB identifier, an SSID (Service Set Identifier), and the like.
  • Step 605 If it is a roaming scenario, and the P-GW is in the visited place, the message interaction between step 603 and step 604 is actually to the VPCRF, and the VPCRF interacts with the HPCRF through the S9 interface. If it is a non-roaming scenario or a home routing method of a roaming scenario, the P-GW directly interacts with the HPCRF and no longer passes through the VPCRF.
  • Step 606 The P-GW sends a binding acknowledgement to the UE.
  • Step 607 triggered by the modification of the IP-CAN session, the V/HPCRF interacts with the BPCF through the S9* interface to request resource authorization.
  • the BPCF After the BPCF receives the information, the BPCF performs admission control or proxy admission control in the fixed domain according to the resources of the fixed network.
  • Step 701 The UE accesses.
  • Case 1 The UE accesses the EPC system through the H(e)NB and the WLAN, and establishes multiple connections to the same P-GW.
  • Case 2 The UE accesses through one of the H(e)NB or WLAN, and currently switches from the H(e)NB or WLAN to the WLAN or H(e)NB.
  • Step 702 The UE establishes an IPsec tunnel with the ePDG to request access authentication.
  • the UE authentication operation may be omitted, and the UE only carries the flow description information to the ePDG; if it is the handover introduced in case 2, the UE carries the handover indication to the ePDG for requesting handover.
  • Step 703 The ePDG sends a proxy binding request message to the P-GW.
  • the ePDG only carries the flow description information to the P-GW; if it is the handover introduced in Case 2, the ePDG carries a handover indication to the P-GW for requesting handover.
  • Step 704 The P-GW initiates an IP-CAN session modification request operation to the PCRF to request resource authorization.
  • Step 705 The PCRF responds to the P-GW with an IP-CAN session modification response, and advertises the resource authorization result to the P-GW.
  • the P-GW determines whether the system is in the same backhual according to the tunnel information or whether the system before and after the handover is under the same backhual. If it is under the same backhual, the P-GW directly performs proxy admission control to allow resource allocation/modification.
  • the P-GW After receiving the flow migration or handover request, the P-GW requests the PCRF through the IP-CAN session, and the PCRF requests the resource authorization from the BPCF. If the fixed network resources are sufficient, the resource authorization is returned by the BPCF until the P-GW is notified, and the P-GW allows the flow migration/switching. Otherwise, the stream migration or the switch fails.
  • the tunnel information is already communicated to the P-GW in the prior art.
  • the tunnel information may include the following information: a CPE address and port number, an H(e)NB identifier, an SSID, and the like.
  • Step 706 if it is a roaming scenario, and the P-GW is in the visited place, the message interaction of step 704 and step 705 is actually to the VPCRF, and the VPCRF interacts with the HPCRF through the S9 interface. If it is a non-roaming scenario or a home routing method of a roaming scenario, the P-GW directly interacts with the HPCRF and no longer passes through the VPCRF. Step 707: The P-GW sends a proxy binding acknowledgement to the ePDG.
  • Step 708 The ePDG completes IPsec tunnel establishment with the UE.
  • Step 709 triggered by the modification of the IP-CAN session, the V/HPCRF interacts with the BPCF through the S9* interface to request resource authorization. After the BPCF receives the information, the BPCF performs admission control or proxy admission control in the fixed domain according to the resources of the fixed network.
  • Case 1 The UE accesses the EPC system through the H(e)NB and the WLAN, and establishes multiple connections to the same P-GW.
  • Case 2 The UE accesses through one of the H(e)NB or WLAN radio access technologies, and currently switches from the WLAN to the H(e)NB.
  • the network side sends a dedicated bearer setup/modification request message to the H(e)NB GW/MME, and carries the requested resource information.
  • the H(e)NB GW/MME sends a bearer authorization request message to the H(e)NB PF, requesting resource authorization.
  • H(e)NB PF determines whether the system is in the same backhual according to the tunnel information or whether the system before and after the handover is under the same backhual. If the same backhual is used, the proxy admission control is directly performed by the H(e)NB PF, and the resource allocation is allowed. /modify.
  • the tunnel information is already able to be communicated to the P-GW in the prior art.
  • the tunnel information may include the following information: a CPE address and port number, an H(e)NB identifier, an SSID, and the like.
  • the H(e)NB PF may have a policy update message with the fixed network policy control entity (such as BPCF). 806.
  • the H(e)NB PF responds to the H(e)NB GW/MME with an authorization response message.
  • the H(e)NB GW/MME sends a bearer setup/modification request/session management request message to the H(e)NB.
  • the H(e)NB sends a resource allocation request message to the H(e)NB PF, where the resource is requested;
  • the H(e)NB PF determines whether the system before or after the handover is in the same backhual according to the tunnel information. If the system is in the same backhual, the proxy admission control is directly performed by the H(e)NB PF, and the resource allocation is allowed. /modify.
  • the tunnel information is already able to be communicated to the P-GW in the prior art.
  • the tunnel information may include the following information: a CPE address and port number, an H(e)NB identifier, an SSID, and the like.
  • the H(e)NB PF may have a policy update message with the fixed network policy control entity (such as BPCF).
  • the fixed network policy control entity such as BPCF
  • the H(e)NB PF responds to the H(e)NB with a resource allocation response message.
  • the UE accesses.
  • Case 1 The UE accesses the EPC system through the H(e)NB and the WLAN, and establishes multiple connections to the same P-GW.
  • Case 2 The UE accesses through one of the H(e)NB or WLAN radio access technologies, and currently switches from the WLAN to the H(e)NB.
  • the network side triggers H(e)NB PF/ or PCRF due to handover or flow migration operation, and H(e)NB PF/ or PCRF sends resource allocation request/resource authorization request/S9*
  • the call modification request to the BPCF carries the requested resource information.
  • the BPCF determines, according to the tunnel information, whether the system before or after the handover is under the same backhual. If it is under the same backhual, the BPCF performs admission control to allow resource allocation/modification. This is the content of the invention.
  • the tunnel information is already able to be communicated to the P-GW in the prior art.
  • the tunnel information may include the following information: a CPE address and port number, an H(e)NB identifier, an SSID, and the like.
  • the H(e)NB PF may have a policy update message with the fixed network policy control entity (such as BPCF).
  • the fixed network policy control entity such as BPCF
  • the BPCF responds to the H(e)NB PF/PCRF with a resource allocation response resource authorization response/S9* session modification response.
  • the operation of the resource management of the present invention can represent the process shown in FIG. 10, and the process includes the following steps:
  • Step 1001 When the UE performs flow migration or handover between the H(e)NB and the WLAN, it is determined according to the fixed network tunnel information whether the UE accesses from the H(e)NB and the WLAN under the same fixed network link.
  • Step 1002 When the judgment result is yes, accept the switching or stream migration.
  • FIG. 11 is a diagram of a resource management system according to the present invention, where the system includes a connected resource management decision unit and a resource management execution unit.
  • the resource management decision unit can determine, according to the fixed network tunnel information, whether the UE is from the H(e)NB under the same fixed network link. And the WLAN access, and notifying the resource management execution unit of the determination result; and, when the determination result is YES, the resource management execution unit can accept the handover or the flow migration.
  • a functional entity such as a policy control entity or a proxy network element capable of doing (proxy) admission control may be referred to as a decision entity. In practical applications, the decision entity may be
  • P-GW Packet Control Function
  • PCRF Packet Control Function
  • PF Packet Control Function
  • BPCF Packet Control Function
  • the method is used to: control the decision entity to perform (proxy) admission control, including: accepting or rejecting resource allocation, modification, reconfiguration, preemption, or bearer establishment/modification/ Update; or, accept or reject the switch or stream migration.
  • the UE Before the UE performs the flow migration, the UE has been simultaneously accessed through the WLAN and the H(e)NB, and the WLAN and the H(e)NB are both under the same fixed network link;
  • the UE has accessed through the H(e)NB or through the WLAN, and the WLAN and the H(e)NB belong to the same fixed network link;
  • the resource management decision unit When the resource management decision unit performs the determining, it is used to: confirm that the tunnel information of the UE when accessing from the WLAN and the access from the H(e)NB is the same or the tunnel information identifies the same fixed network link, according to the It is determined that the flow migration or handover of the UE is performed under the same fixed network link; when the resource management execution unit accepts the handover or the flow migration, the resource management execution unit is configured to: control the P-GW to perform admission control.
  • the tunnel information is aggregated at the BPCF; when the resource management execution unit accepts the handover or the flow migration, the method is used to: control the BPCF to accept the control;
  • H(e)NB PF and PCRF are combined, and H(e)NB PF/PCRF is a convergence point; when the resource management execution unit accepts the handover or flow migration, it is used to: control H(e)NB PF /PCRF for admission control;
  • the PCRF is a unified convergence point; when the resource management execution unit accepts the handover or the flow migration, it is used to: control the PCRF to perform admission control.
  • the H(e)NB and the WLAN are in the same fixed network link, but the two reported tunnel information are different.
  • the resource management decision unit performs the judgment, it is used to: control the BPCF to the fixed network check. Inquiring, to determine whether the two tunnel information identifies the same fixed network link, and confirm that the UE is accessed from the H(e)NB and the WLAN under the same fixed network link when the determination result is yes;
  • the resource management execution unit When the resource management execution unit accepts the handover or the flow migration, it is used to: control the BPCF or the BPCF to entrust other network elements to perform admission control.
  • the resource management technology of the present invention can effectively avoid the moment when the UE switches or migrates between the H(e)NB and the WLAN under the same fixed network link, whether it is a method or a system.

Landscapes

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

Abstract

La présente invention se rapporte à un procédé et à un système adaptés pour gérer des ressources. Dans le procédé et le système selon l'invention, quand une migration de flux ou une commutation de flux est mise en œuvre par un équipement d'utilisateur (UE, User Equipment) entre une station de base formant nœud B domestique évolué (H(e)NB) et un réseau local sans fil (WLAN), sur la base de données de tunnel de réseau fixe, il est déterminé si l'UE tente ou non un accès à partir du H(e)NB et du WLAN de la même liaison de réseau fixe ; quand le résultat de la détermination correspond à oui, la commutation de flux ou la migration de flux est acceptée. Le procédé et le système selon la présente invention garantissent que, quand la commutation de flux ou la migration de flux de l'UE est mise en œuvre entre le H(e)NB et le WLAN de la même liaison de réseau fixe, une défaillance de la commutation occasionnée par une insuffisance momentanée de ressources est effectivement empêchée.
PCT/CN2011/084064 2011-01-27 2011-12-15 Procédé et système pour gérer des ressources WO2012100606A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110030406.0 2011-01-27
CN201110030406.0A CN102625396B (zh) 2011-01-27 2011-01-27 一种资源管理方法和系统

Publications (1)

Publication Number Publication Date
WO2012100606A1 true WO2012100606A1 (fr) 2012-08-02

Family

ID=46565032

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/084064 WO2012100606A1 (fr) 2011-01-27 2011-12-15 Procédé et système pour gérer des ressources

Country Status (2)

Country Link
CN (1) CN102625396B (fr)
WO (1) WO2012100606A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103857048B (zh) * 2012-11-30 2017-08-29 华为技术有限公司 一种资源调度方法及装置
CN107529182A (zh) * 2016-06-22 2017-12-29 中兴通讯股份有限公司 数据调度方法和系统
CN107959918B (zh) * 2016-10-14 2020-02-07 电信科学技术研究院 一种会话管理方法、移动性管理功能以及会话管理功能

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101083610A (zh) * 2006-05-30 2007-12-05 西门子（中国）有限公司 提高移动节点在无线局域网中切换速度的方法及移动节点
CN101478796A (zh) * 2009-01-20 2009-07-08 中国科学院计算技术研究所 一种异构网络分级切换控制信令系统及其切换方法
CN101801055A (zh) * 2010-02-05 2010-08-11 上海顶竹通讯技术有限公司 不同网络之间的通信切换方法及其终端设备
EP2259631A1 (fr) * 2008-03-24 2010-12-08 Panasonic Corporation Système de communication, dispositif d'amélioration de rendement de canal de communication et terminal de communication radio

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101083610A (zh) * 2006-05-30 2007-12-05 西门子（中国）有限公司 提高移动节点在无线局域网中切换速度的方法及移动节点
EP2259631A1 (fr) * 2008-03-24 2010-12-08 Panasonic Corporation Système de communication, dispositif d'amélioration de rendement de canal de communication et terminal de communication radio
CN101478796A (zh) * 2009-01-20 2009-07-08 中国科学院计算技术研究所 一种异构网络分级切换控制信令系统及其切换方法
CN101801055A (zh) * 2010-02-05 2010-08-11 上海顶竹通讯技术有限公司 不同网络之间的通信切换方法及其终端设备

Also Published As

Publication number Publication date
CN102625396A (zh) 2012-08-01
CN102625396B (zh) 2017-09-12

Similar Documents

Publication Publication Date Title
US8849273B2 (en) Method and system for reporting fixed network access information
US9271220B2 (en) Policy control method and system
WO2013064070A1 (fr) Procédé, système et pcrf pour réaliser un mécanisme qos à réflexion
CN102378280B (zh) 一种实现bbf接入的策略控制方法及系统
WO2012065499A1 (fr) Procédé et système d'établissement d'un contrôle de qualité de service
WO2012041073A1 (fr) Procédé et système adaptés pour exécuter un transfert de flux
EP2884802B1 (fr) Procédé et système de notification d'informations de position dans un réseau d'accès
WO2012003770A1 (fr) Système, dispositif et procédé permettant à un équipement utilisateur d'accéder à un réseau mobile
WO2011095025A1 (fr) Procédé et système de commande de politique pour accès local d'utilisateur mobile
CN102131240B (zh) 一种实现服务质量控制的方法及系统
CN102098653A (zh) 一种实现服务质量控制的方法及系统
US8874079B2 (en) Control method for home base station access and home base station gateway
Ahmed et al. Multi access data network connectivity and IP flow mobility in Evolved Packet System (EPS)
WO2012100606A1 (fr) Procédé et système pour gérer des ressources
WO2012028044A1 (fr) Procédé et système pour traiter une erreur ifom
Ahmed et al. Inter-system mobility in evolved packet system (EPS): Connecting non-3GPP accesses
WO2014071790A1 (fr) Procédé, dispositif et système destinés à un contrôle de politique d'une convergence fixe-mobile
WO2013152651A1 (fr) Procédé et système de gestion de ressources, et élément de réseau de gestion de ressources
WO2012152198A1 (fr) Procédé et système de suppression de session de politique
WO2012146092A1 (fr) Procédé et système de contrôle de politique pour mesurer la mobilité d'un flux ip
WO2012019506A1 (fr) Procédé et système adaptés pour mettre en œuvre un contrôle de ressources dans un scénario d'intégration d'un réseau fixe et d'un réseau mobile
WO2011131064A1 (fr) Procédé et système de contrôle d'accès à un nœud b domestique (hnb)
CN102547884B (zh) 一种基站间切换资源控制的方法
WO2012059043A1 (fr) Procédé et système de contrôle d'admission à un service
CN102572771B (zh) 一种切换过程中实现资源管理控制的方法和系统

Legal Events

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

Ref document number: 11856810

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11856810

Country of ref document: EP

Kind code of ref document: A1