WO2013075580A1 - Method and system for resource control of local unload data - Google Patents

Abstract

Disclosed are a method and system for resource control of local unload data. The method comprises: a local gateway (L-GW) sending an admission control request to a broadband policy control function (BPCF) after receiving a trigger message; the BPCF performing the admission control, returning to the L-GW an admission control result, and in the case of the admission control result being accepted, issuing to a broadband network gateway/broadband remote access server (BNG/BRAS) a control policy in which a CPE IP address and authorization quality of service (QoS) information are at least included; the L-GW performing a bearing operation according to the admission control result; and the BNG/BRAS performing resource control on a data message encapsulated using the CPE IP address in accordance with the authorization quality of service (QoS) information. The present invention resolves a resource control problem in developing a local unload service through UE accessing via an HeNB, so that the local unload service developed by the UE may also be guaranteed in terms of QoS.

Description

 Method and system for resource control of local unloading data

 The present invention relates to the field of wireless communication technologies, and in particular, to a method and system for resource control of local offload data. Background technique

 The Evolved Packet Core network (EPC) developed by the 3rd Generation Partnership Project (3GPP) is composed of Mobility Management Entity (MME) and Serving Gateway (S-GW). The packet data network gateway (P-GW, Packet Data Network Gateway), the home subscriber server (HSS, Home Subscriber Server) and other network elements, as shown in Figure 1.

 The MME is responsible for the control planes such as mobility management, non-access stratum signaling processing, and user mobility management context management; the S-GW forwards data between the user access and the P-GW, and is responsible for paging waiting. The data is buffered; the P-GW is a border gateway of an Evolved Packet System (EPS) and a Packet Data Network (PDN), which is responsible for PDN access and forwarding data between the EPS and the PDN.

If the EPC supports Policy and Charging Control (PCC), the Policy and Charging Rules Function (PCRF, Policy and Charging Rules Function) is used to formulate policies and charging rules through the interface Rx and the carrier network protocol. (IP, Internet Protocol) The application function (AF, Application Function) in the service network is connected to obtain service information, which is used to generate service information of the PCC policy. When the S5 interface between the S-GW and the P-GW adopts the General Packet Radio Service Tunneling Protocol (GTP, GPRS Tunnelling Protocol), the P-GW resides in the Policy and Charging Enforcement Function (PCEF, Policy and Charging Enforcement Function). ), the PCRF and the P-GW exchange information through the Gx interface, which is responsible for sending The bearer is established, modified, and released, guarantees the quality of service (QoS) of the service data transmission, and performs charging control. When the S5 interface of the S-GW and the P-GW adopts Proxy Mobile IP (PMIP), the S-GW hosts the bearer binding and event reporting function (BBERF, Bearer Binding and Event Report Function), and S - The GW and the PCRF exchange information through the Gxc interface, and the BBERF is responsible for initiating the establishment, modification, and release of the bearer, ensuring the service quality of the service data, and performing charging control by the PCEF.

 Users can access the EPC network through the Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

 In addition, the user can access the EPC network through a Home NodeB subsystem (referred to as a ΗΝΒ subsystem) or an evolved Home Node System (HeNB subsystem), as shown in FIG. 1 . The HeNB/HNB is a small, low-power base station deployed in indoor locations such as homes and offices. The HeNB/HNB usually enters the EPC by renting a fixed line ί3⁄4. To ensure access security, a security gateway (SeGW, Security Gateway) needs to be deployed on the EPC network. After the HeNB/HNB is powered on, a network security (IPSec, IP Security) tunnel is established with the SeGW, and the user accesses the HeNB/HNB. The data exchanged between the device (UE) and the EPC network is encapsulated by IPSec, so that the devices on the line cannot perceive the data and ensure the security of data transmission. When the HeNB system is used, the HeNB GW is an optional network element. If not deployed, the HeNB directly connects to the MME. If the HNB system is used, the HNB GW must be deployed with the NE and the HNB connected to the HNB GW. In addition to the HeNB system, the HNB system also supports circuit switched (CS) services, that is, the connection between the HNB GW and the Mobile Switching Center (MSC). In order to implement policy control of the CS service in the HNB system, an S15 interface is established between the HNB GW and the PCRF.

The HeNB/HNB system shown in Figure 1 accesses the EPC through the fixed network, and the data packets of the UE access service/application accessing the HeNB/HNB are routed through the EPC network. However, considering that a large number of access users access the service through the EPC network will not only increase the data traffic load of the EPC network, but The preemption of network resources by multiple services may result in failure to provide service quality assurance for services with high QoS requirements. Therefore, the 3GPP R-11 standard specification defines the offload (local offload) function of the HeNB system, that is, the service/application data accessed by the user accessing the HeNB system is not routed through the EPC network, but is directly used by the HeNB system and the HeNB system. The fixed line is routed, and this part of the data is called offload data.

 As shown in Figure 2, 3GPP R-11 introduces a separate local gateway (L-GW, Local Gate Way) network element for the HeNB system to support the offload function. The L-GW is deployed on the local network and functions like a P-GW. When the L-GW and the HeNB are powered on, the local IP address is obtained from the local network, which is called the L-GW local IP address and the HeNB local IP address. The L-GW and the HeNB respectively perform IKEv2 negotiation with the SeGW by using the local IP address to establish an IPSec tunnel for transmitting data that passes through the HeNB system and is routed back to the EPC network. In addition, the HeNB and the L-GW need to exchange local IP addresses with each other to establish an Sxx tunnel for transmitting data that is unloaded through the HeNB system and from the local network. After the HeNB and the L-GW establish an IPSec tunnel with the SeGW, the SeGW also allocates a core network IP address, which is called the core network IP address of the HeNB and the core network IP address of the L-GW.

FIG. 3 is a schematic diagram of offlaod data routing when the HeNB system accessing the EPC core network through the BBF network supports the offload function. The HeNB and the L-GW are deployed under the Residental Gateway (RG), that is, the RG allocates the local private network IP address to the HeNB and the L-GW respectively. When the UE accessing the HeNB system accesses the offload service, the offload data is routed through the HeNB system (ie, the HeNB and the L-GW in the figure) and the fixed network access line used by the HeNB system (ie, RG, BNG/ in the figure). BRAS) _0, where BNG is a Broadband Network Gateway and BRAS is a Broadband Remote Access Server.

When the UE accessing the HeNB system needs to perform the offload service, first, a PDN connection (for example, a SIPTO connection) for accessing the offload service needs to be established, as shown in FIG. Only established After the PDN is connected, the UE can perform the offload service through the HeNB system. It should be noted that the prior art process described in FIG. 4 is a scenario in which the RG is not deployed on the fixed network. The local IP address of the HeNB and the L-GW can be allocated by the BNG/BRAS. If the RG is deployed in the network, that is, when the HeNB system accesses the fixed network through the RG, the RG can allocate the local IP address for the HeNB and the L-GW. The process shown in Figure 4 mainly includes:

 Step 401: After the HeNB is powered on to complete the access authentication of the fixed network, the fixed network device (BNG/BRAS/RG) allocates the HeNB local IP address (HeNB@LN address;), and the HeNB uses the HeNB@LN address to complete. The IKEv2 negotiation with the SeGW establishes an IPSec tunnel, and the SeGW allocates a HeNB core network IP address (HeNB@CN address) to the HeNB.

 Step 402: The process of powering up the L-GW is similar to that of the HeNB. After the power-on process is complete, an IPSec tunnel is established between the L-GW and the SeGW, and the L-GW obtains the local IP address of the L-GW (L-GW@LN address). And the L-GW core network IP address (L-GW@CN address).

 Step 403: The L-GW initiates an update to the domain name server (ie, the DNS server), and the L-GW@LN address, the L-GW@CN address, the full-name domain name (FQDN, Fully Qualified Domain Name), and the access point name (APN, The Access Point Name and Local HeNB Network Identity (LHN-ID, Local HeNB Network Identity) information is sent to the DNS server for storage.

 Step 404: The DNS server returns a response that the update is successful.

 Step 405: The access UE initiates a SIPTO (Selected IP Traffic Offload) connection request, and the request message includes APN information. When the message passes through the HeNB, the HeNB carries the LHN-ID to the MME.

 Step 406: When the MME receives the request, first determine, according to the APN information, whether the UE can perform SIPTO. If yes, initiate a DNS query according to the LHN-ID, and select a corresponding L-GW.

Step 407: After the DNS server selects the L-GW for the access of the UE, the information of the selected L-GW (including the L-GW@LN address, the L-GW@CN address, the FQDN, and the like) Return to the MME to save.

 Step 408: The MME sends a session establishment request to the S-GW.

 Step 409: The S-GW sends a session establishment request to the selected L-GW.

 Step 410: After receiving the session establishment request, the L-GW returns a session establishment response to the S-GW, where the response message includes the tunnel end identifier (TEID, Tunnel Endpoint) generated by the L-GW.

Identifier ) and the IP address assigned to the UE.

 Step 411: The corresponding S-GW returns a session establishment response to the MME.

 Step 412: After receiving the session establishment response, the MME sends a bearer setup request to the HeNB, where the request message includes the L-GW@LN address, the FQDN, the TEID, and the IP address information of the UE.

 Step 413: An RRC connection is established between the HeNB and the UE, and the HeNB sends the IP address of the UE to the UE.

 Step 414: The HeNB returns a bearer setup response to the MME, where the response message includes the TEID generated by the HeNB, and the HeNB@LN address information.

 Step 415: The HeNB returns PDN connection establishment completion information to the MME.

 Step 416: After receiving the message that the PDN connection is established, the MME sends the message to the S-GW.

The L-GW initiates a bearer modification request, and brings the TEID and HeNB@LN address information of the HeNB to the L-GWo.

 Alternatively, after receiving the PDN connection establishment, the MME sends the TEID of the HeNB and the HeNB@LN address information to the L-GW through the S-GW.

 So far, an Sxx tunnel for carrying offload data is established between the HeNB and the L-GW. After the UE completes the above PDN connection (referred to as SIPTO connection in the figure) establishment process, the UE can perform the offload service by using the L-GW for its assigned IP address.

3 and 4 illustrate the PDN connection establishment process and data routing in the case where the HeNB system supports offload. As can be seen from FIG. 3, the data of the offload service carried out by the UE accessing the HeNB system needs to be routed through the fixed network line (backhaul) used by the HeNB to access, and Fixed-line resources can be resource-intensive because they are used by a large number of users, including mobile users and fixed-line users. If the offload service is a service that needs to provide QoS guarantee, then QoS guarantee for offload will not be provided in this case. Therefore, how to provide resource control for the offload data in the above scenario is an urgent problem to be solved.

 In addition, the following describes the routing process of the offload data in the prior art in the HeNB system and the fixed network backhaul (ie, between the UE and the BNG/BRAS) used by the HeNB/L-GW access.

In conjunction with the scenario in which the HeNB system is connected to the BBF network through the RG, after the HeNB/L-GW is powered on, the RG allocates a local private network IP address (local private network IP address-1 and local private network IP). Address-2) ₀ When the HeNB/L-GW establishes an IPSec tunnel with the SeGW for IKEv2 negotiation with the local private network IP address, the local private IP address-1 of the HeNB performs network address translation on the RG (NAT, Network). Address Translation ), converted to public network IP address (called CPE IP address) and port (set) -1; L-GW local private network IP address-2 performs NAT translation on the RG to CPE IP address and port (set ) -2. The CPE is Customer Premise Equipment.

 As shown in Figure 4, the PDN connection needs to be established before the UE accessing the HeNB system performs the offload service. In this process, the RG allocates a local private network IP address -3 to the UE. The UE can use the IP address to carry out the offload service. The above-mentioned offload data is used as an example (downstream offload data, only need to change the source and destination IP addresses of the uplink data packet, and the port number can be changed), and the IP layer data encapsulation format of the data routing is shown in FIG. 5.

The offload data sent by the UE to the HeNB, the source address of the data encapsulation is the UE local private network IP address-3, and the destination address is the CN IP address (that is, the communication peer IP address;). After the HeNB arrives at the HeNB, the Sxx tunnel encapsulation is performed, the source address is the HeNB local private network IP address -1, and the destination address is the L-GW local private network IP address -2, and is sent to the L-GW. After receiving the packet, the L-GW performs decapsulation of the Sxx tunnel and sends the decapsulated data packet to the RG. The RG performs NAT translation on the source IP address of the data, that is, the local private IP address of the UE-3. It is converted to CPE IP address and port number -3 before being sent to BNG/BRAS.

 Figure 6 shows the NAT conversion performed by the local private network IP address assigned by the RG to the device it accesses. That is, the RG allocates a local private network IP address -1, a local private network IP address -2, and a local private network IP address -3 to the HeNB, the L-GW, and the UE, respectively. When the device sends the information through the RG by using the local private network IP address assigned by the RG (for example, the HeNB and the L-GW initiate IKEv2 negotiation to the SeGW through the RG, or the UE initiates the offload service through the RG), the RG needs to perform N: 1 for it. NAT conversion, that is, the RG converts the HeNB's local private network IP address -1 to NAT to CPE IP address + port (set) 1; converts the L-GW's local private network IP address -2 to NAT to convert to CPE IP address + Port (set) 2; Convert the UE's local private IP address-3 to NAT to CPE IP address + port (set) 3. The CPE IP address is a public network IP address after the RG performs NAT conversion on the private network IP address of the device connected to it. Summary of the invention

 In view of the above, the main purpose of the embodiments of the present invention is to provide a method and a system for performing resource control on a local offloading data, so as to solve the problem of resource control of an offload service performed by a UE accessed by a HeNB, so that the offload service performed by the UE can be Get QoS guarantee.

 To achieve the above objective, the technical solution of the embodiment of the present invention is implemented as follows:

 A method for performing resource control on local offload data includes: after receiving a trigger message, the local gateway L-GW sends an admission control request to the broadband policy control function BPCF; the BPCF performs admission control, and returns to the L-GW. Accepting the control result, and when the admission control result is accepted, transmitting a control policy to the broadband network gateway/broadband remote access server BNG/BRAS, where the control policy includes at least a customer premises equipment network protocol CPE IP address and authorization Quality of Service QoS information.

 After returning the admission control result to the L-GW, the method further includes: the L-GW performing a bearer operation according to the admission control result.

After issuing the control policy to the BNG/BRAS, the method further includes: the BNG/BRAS And filtering the data packet according to the CPE IP address, and performing resource control on the data packet encapsulated by the CPE IP address according to the authorized QoS information.

 The trigger message is a resource allocation request, a service request, or a bearer operation request from the network from the UE side of the user equipment.

 The carrying operation performed by the L-GW according to the admission control result is specifically:

 If the admission control result is a rejection, the L-GW rejects the bearer setup or modification operation;

 If the admission control result is accepted, the L-GW initiates a bearer setup or modification operation.

 Before the L-GW receives the trigger message, the method further includes: the BPCF and the L-GW establish a first policy control session, and the BPCF acquires the CPE IP address; the BPCF discovers the location according to the CPE IP address. The BNG/BRAS establishes a second policy control session with the BNG/BRAS.

 The first policy control session is a policy control session directly established between the BPCF and the L-GW; correspondingly, the L-GW discovers the BPCF according to the CPE IP address, and establishes the first policy. Control the session.

 The first policy control session is composed of a policy control session established between the L-GW and the policy and charging rule function PCRF, and a policy control session established between the PCRF and the BPCF; correspondingly, the L-GW is based on the LHN - the ID or CPE IP address discovers the PCRF and establishes a policy control session with the PCRF; the PCRF discovers the BPCF according to the CPE IP address and establishes a policy control session with the BPCF .

 A system for resource control of local offload data, comprising: a local gateway L-GW, a broadband policy control function BPCF, a broadband network gateway/broadband remote access server BNG/BRAS, wherein

The L-GW is configured to send an admission control request to the BPCF after receiving the trigger message; The BPCF is configured to perform admission control, and return an admission control result to the L-GW, and send a control policy to the BNG/BRAS when the admission control result is accepted, where the control policy includes at least Customer premises equipment network protocol CPE IP address and authorized quality of service QoS information;

 The BNG/BRAS is configured to receive a control policy delivered by the BPCF.

 The L-GW is further configured to perform a bearer operation according to the admission control result.

 The BNG/BRAS is further configured to: filter the data packet according to the CPE IP address, and perform resource control on the data packet encapsulated by the CPE IP address according to the authorized QoS information.

 The trigger message is a resource allocation request, a service request, or a bearer operation request from the network from the UE side of the user equipment.

 The L-GW is further configured to reject the bearer setup or modify operation when the admission control result is rejected; and initiate a bearer setup or modify operation when the admission control result is accepted.

 The BPCF is further configured to: before the L-GW receives the trigger message, the BPCF establishes a first policy control session with the L-GW, and the BPCF acquires the CPE IP address; the BPCF according to the CPE IP address The BNG/BRAS is found to establish a second policy control session with the BNG/BRAS.

 The first policy control session is a policy control session directly established between the BPCF and the L-GW; correspondingly, the L-GW discovers the BPCF according to the CPE IP address, and establishes the first policy. Control the session.

The first policy control session is composed of a policy control session established between the L-GW and the policy and charging rule function PCRF, and a policy control session established between the PCRF and the BPCF; correspondingly, the L-GW is based on the LHN - the ID or CPE IP address discovers the PCRF and establishes a policy control session with the PCRF; the PCRF discovers the BPCF according to the CPE IP address and establishes a policy control session with the BPCF . A method and system for performing resource control on local offload data provided by an embodiment of the present invention, after receiving the trigger message, the L-GW sends an admission control request to the BPCF; the BPCF performs admission control, and returns an admission control result to the L-GW. And when the admission control result is accepted, the control policy is sent to the BNG/BRAS, where the control policy includes at least the CPE IP address and the authorized QoS information; the L-GW performs the bearer operation according to the admission control result; the BNG/BRAS is based on the CPE IP address. The data packet is filtered, and the data packet encapsulated by the CPE IP address is used for resource control according to the authorized QoS information.

 The present invention solves the problem of resource control of the local offloading service performed by the UE accessed by the HeNB, so that the local offloading service carried out by the UE can also obtain QoS guarantee. The solution of the invention is equally applicable to HNB systems. DRAWINGS

 1 is a schematic structural diagram of a HeNB accessing an EPC in the prior art;

 2 is a schematic diagram of a HeNB system deployed with an independent L-GW in the prior art; FIG. 3 is a schematic diagram of a route for accessing offload data through a HeNB in the prior art; FIG. 4 is a schematic diagram of establishing a SIPTO connection in the prior art. Flow chart

 FIG. 5 is a schematic diagram of encapsulation of offload data routing in a HeNB access scenario in the prior art;

 6 is a schematic diagram of NAT conversion performed by the RG in the N:1 mode on the private network IP address of the device accessed by the RG in the prior art;

 7 is a flow chart of a method for resource control of local offload data according to an embodiment of the present invention;

 8 is a flowchart of establishing a policy control session according to Embodiment 1 of the present invention;

 9 is a flowchart of establishing a policy control session according to Embodiment 2 of the present invention;

FIG. 10 is a flowchart of establishing a policy control session according to Embodiment 3 of the present invention. detailed description

 The technical solutions of the present invention are further elaborated below in conjunction with the accompanying drawings and specific embodiments. The data packet of the offload service carried out by the UE accessed by the HeNB system needs to perform the conversion of the private network IP address and the CPE IP address of the UE after passing through the RG, that is, the offload datagram routed between the RG and the BNG/BRAS. The text is encapsulated using the CPE IP address. Therefore, the present invention establishes a policy control session on the BNG/BRAS before the offload service is launched, and sends the CPE IP address to the BNG/BRAS and the policy control device. After the offload service is performed, the BNG/BRAS can determine whether it is an offload data packet according to whether the data packet contains the CPE IP address. If so, the BNG/BRAS can request resource control for the offload data message to the policy control device.

 Based on the above idea, a method for performing resource control on local unloading data according to an embodiment of the present invention, as shown in FIG. 7, mainly includes:

 Step 701: After receiving the trigger message, the L-GW sends an admission control request to a Broadband Policy Control Function (BPCF).

 The trigger message may be a resource allocation request from the UE side, a service request, or a bearer operation request from the network.

 Step 702: The BPCF performs the admission control, returns the admission control result to the L-GW, and sends a control policy to the BNG/BRAS when the admission control result is accepted. The control policy includes at least the CPE IP address and the authorized QoS information.

 Step 703: The L-GW performs a bearer operation according to the admission control result. The BNG/BRAS filters the data packet according to the CPE IP address, and performs resource control on the data packet encapsulated by the CPE IP address according to the authorized QoS information.

The L-GW performs the bearer operation according to the admission control result, specifically: if the admission control result is a rejection, the L-GW rejects the bearer setup or modification operation; if the admission control result is accepted, the L-GW initiates the bearer setup or modification operation. . In addition, before the L-GW receives the trigger message, the method further includes: the BPCF and the L-GW establish a first policy control session, and the BPCF obtains the CPE IP address; the BPCF discovers the BNG/BRAS according to the CPE IP address, and establishes and A second policy control session between BNG/BRAS.

 The first policy control session may be a policy control session directly established between the BPCF and the L-GW; correspondingly, the L-GW discovers the BPCF according to the CPE IP address, and establishes a first policy control session.

 The first policy control session may also be composed of a policy control session established between the L-GW and the PCRF, and a policy control session established between the PCRF and the BPCF;

 Correspondingly, the L-GW discovers the PCRF according to the LHN-ID or CPE IP address, and establishes a policy control session with the PCRF; the PCRF discovers the BPCF according to the CPE IP address, and establishes a policy control session with the BPCF.

 Corresponding to the foregoing method for performing resource control on local unloading data, an embodiment of the present invention further provides a system for performing resource control on local unloading data, which mainly includes: L-GW, BPCF, BNG/BRAS, wherein L-GW is used. After receiving the trigger message, sending an admission control request to the BPCF; performing a bearer operation according to the admission control result. The BPCF is used for admission control, and returns the admission control result to the L-GW. When the admission control result is accepted, the control policy is sent to the BNG/BRAS, and the control policy includes at least the CPE IP address and the authorized QoS information. The BNG/BRAS is used to filter data packets according to the CPE IP address and perform resource control on the data packets encapsulated by the CPE IP address according to the authorized QoS information.

 Preferably, the L-GW is further configured to: when the admission control result is rejected, reject the bearer establishment or modification operation; when the admission control result is accepted, initiate a bearer setup or modification operation.

 Preferably, the BPCF may be further configured to: before the L-GW receives the trigger message, the BPCF establishes a first policy control session with the L-GW, and the BPCF obtains the CPE IP address; the BPCF discovers the BNG/BRAS according to the CPE IP address, and establishes A second policy control session with BNG/BRAS.

The first policy control session may be directly established between the BPCF and the L-GW. The policy controls the session; correspondingly, the L-GW discovers the BPCF according to the CPE IP address and establishes a first policy control session.

 The first policy control session may also be composed of a policy control session established between the L-GW and the PCRF, and a policy control session established between the PCRF and the BPCF;

 Correspondingly, the L-GW discovers the PCRF according to the LHN-ID or CPE IP address, and establishes a policy control session with the PCRF; the PCRF discovers the BPCF according to the CPE IP address, and establishes a policy control session with the BPCF.

 The above method and system for resource control of local offload data will be further described in detail below with reference to specific embodiments.

 The scenario described in Embodiment 1 of the present invention is that the HeNB system accesses the EPC through the RG and BBF networks. The RG allocates a private network IP address for the device accessed through it. The process of implementing resource control for the offload service carried out by the UE accessed by the HeNB system, as shown in FIG. 8, the process mainly includes:

 Step 801: The L-GW is powered on, and performs access authentication to the fixed network. The RG and the fixed network AAA server participate in the access authentication process when the L-GW is powered on.

 Step 802: When the L-GW performs the access authentication to the fixed network, the RG allocates the local private network IP address -1 to the L-GW.

 Step 803: The L-GW completes the IKEv2 negotiation with the SeGW by using the private network IP address allocated by the RG to establish an IPSec tunnel. When the IKEv2 message sent by the L-GW passes the RG, the RG converts the local private IP address -1 of the L-GW into a CPE IP address and a port (set) -1.

 Step 804: The SeGW allocates the core network IP address of the L-GW to the L-GW, and sends the IP address to the L-GW. At the same time, by extending the IKEv2 message, the SeGW sends the NAT-converted CPE IP address to the L-GW.

Step 805: The L-GW uses the CPE IP address information and/or the FQDN to discover the BPCF that controls the L-GW to access the fixed line resource used, and initiates a first policy control session establishment request. The request message includes the CPE IP address information and/or FQDN.

 Step 806: After receiving the first policy control session establishment request, the BPCF discovers the BNG/BRAS on the fixed network line used by the L-GW access according to the CPE IP address information and/or the FQDN, and establishes a second policy control session. . At the same time, the BPCF obtains the subscription QoS information of the fixed line used by the L-GW access, and this information serves as a basis for subsequent admission control of the resource request of the offload service.

 Step 807: The BPCF returns a response that the first policy control is successfully established to the L-GW.

 Step 808: In a similar manner, the HeNB obtains the local private network IP address -2, and negotiates with the SeGW to establish an IPSec tunnel.

 Step 809 is a process in which the UE accesses the HeNB network to establish a PDN connection for offloading services. For the process, refer to the process shown in FIG. 4.

 Step 810: After establishing the PDN connection, the UE may perform the offload service by using the local private network IP address -3 allocated by the RG. The UE sends a service request to the L-GW, and the request message is sent to the L-GW through the HeNB, or sent to the L-GW through the HeNB, the MME, and the S-GW.

 Step 811: After receiving the service request, the L-GW initiates an admission control request to the BPCF, where the admission control request message includes QoS information related to the service.

 Step 812: The BPCF performs admission control on the service, and if the L-GW accesses the resources on the fixed line used to meet the QoS requirement of the service, the request is accepted.

 Step 813: The BPCF returns a successful response to the L-GW.

 Step 814, the L-GW initiates an operation of bearer establishment/modification according to this.

 Step 815: The BPCF sends a control policy to the BNG/BRAS, including the CPE IP address and the authorized QoS information. When the data packet passes the BNG/BRAS, if the BNG/BRAS filters the corresponding data packet according to the CPE IP address, it indicates that the data packet is the offload service, and the offload data is controlled according to the authorized QoS information.

The scenario described in the second embodiment of the present invention is the same as that in the first embodiment, and the difference lies in the first policy control. The establishment of the session is established by the L-GW through the PCRF and BPCF. The process is shown in Figure 9, which mainly includes:

 Step 901: The L-GW performs the access authentication to the fixed network, and obtains the local private network IP address. The process of establishing the IPSec tunnel and obtaining the CPE IP address is the same as that in the first embodiment. See steps 801-804.

 Step 902: The L-GW discovers the PCRF according to the LHN-ID or the CPE IP address, and initiates a policy control session A establishment request to the PCRF, where the request message includes the LHN-ID, the CPE IP address, and/or the FQDNo.

 Step 903: After receiving the policy control session A establishment request, the PCRF discovers the BPCF that controls the L-GW access to the fixed line resource according to the CPE IP address information and/or the FQDN information, and initiates the policy control session B. A request is established, and the request message contains a CPE IP address and/or FQDN.

 Step 904: After receiving the establishment request of the policy control session B, the BPCF discovers the BNG/BRAS on the fixed network line used by the L-GW access according to the CPE IP address and/or the FQDN information, and establishes a second policy control session. . At the same time, the BPCF obtains the subscription QoS information of the fixed line used by the L-GW access, and this information serves as a basis for subsequent admission control of the offload service.

 Step 905: The BPCF returns a policy control session B to the PCRF to establish a successful response.

 Step 906: The PCRF returns a policy control session A to the L-GW to establish a successful response.

 Step 907: In the same manner, an IPSec tunnel is established between the HeNB and the SeGW. Step 908 is a process in which the UE accesses the HeNB network to establish a PDN connection in order to perform an offload service. For the process, refer to the process shown in FIG. 4.

 Step 909: After establishing the PDN connection, the UE can perform the offload service by using the local private network IP address -3 allocated by the RG. The UE sends a service request to the L-GW, and the request message is sent to the L-GW through the HeNB, or sent to the L-GW through the HeNB, the MME, and the S-GW.

Step 910: After receiving the service request, the L-GW initiates an admission control request to the PCRF. The request message contains QoS information related to the service.

 Step 911, the PCRF initiates an admission control request to the BPCF.

 Step 912: The BPCF performs admission control on the service, and if the resource on the fixed line used by the L-GW access can meet the requirement of the service to perform QoS, the request is accepted.

 In step 913, the BPCF returns a successful response to the PCRF.

 Step 914, the PCRF returns a successful response to the L-GW.

 Step 915: The L-GW initiates an operation of establishing/modifying the bearer according to this.

 Step 916: The BPCF sends a control policy to the BNG/BRAS, including the CPE IP address and the authorized QoS information. When the data packet passes the BNG/BRAS, if the BNG/BRAS filters the corresponding data packet according to the CPE IP address, it indicates that the data packet is the offload service, and the offload data is controlled according to the authorized QoS information.

 It should be noted that, in this embodiment, the L-GW and the PCRF establish a policy control session A. When the UE performs the offload service, the PCRF does not make policy decision and admission control, but forwards the admission control request from the L-GW. BPCF, and forwards the admission control result of the BPCF to the L-GW. However, if the PCRF is a network element deployed in the HeNB system, that is, the network resource inside the HeNB system is specifically managed, when the PCRF receives the resource authorization request from the L-GW in step 910, the PCRF may perform resource authorization on the request, and The authorization QoS information is sent to the BPCF for admission control. According to the admission control result of the BPCF, the PCRF can decide to send the authorization QoS information to the L-GW.

 The scenario described in the third embodiment of the present invention is the same as that in the first embodiment, except that the process of establishing a policy control session occurs when the UE accessing the HeNB establishes a PDN connection. The process is shown in Figure 10, which mainly includes:

 For the process of powering up the L-GW, see steps 801-804 in Figure 8.

1002. The L-GW sends a DNS update to the DNS server located in the core network, and sends information such as the L-GW core network IP address, the LHN-ID, and the APN to the DNS server. 1003. The HeNB is powered on and the IPSec tunnel of the SeGW is established.

 1004. The UE initiates a PDN connection establishment request, where the request message includes information such as a UE-ID and an APN. The APN information indicates that the UE requests to establish a PDN connection for offload. When the request message arrives at the HeNB, the HeNB includes the LHN-ID of the HeNB network to which it belongs, in the request message, and sends it to the MME.

 1005. After receiving the connection establishment request message, the MME first determines, according to the APN information, whether the UE is allowed to establish a PDN connection, and if allowed, queries the DNS server for the L-GW serving the UE according to the LHN-ID.

 1006. The DNS queries the corresponding L-GW according to the LHN-ID, and returns information of the L-GW (including information such as the L-GW core network IP address) to the MME.

 1007. The MME then sends a session establishment request to the S-GW, where the request message includes an L-GW core network IP address.

 1008. The S-GW initiates a session establishment request to the L-GW according to the IP address of the L-GW core network.

1009. After receiving the session establishment request, the L-GW discovers the BPCF according to the CPE IP address and/or the FQDN, and initiates a first policy control session establishment request, where the request message includes the CPE IP address.

 1010. After receiving the first policy control session establishment request, the BPCF discovers the BNG/BRAS on the fixed network line used by the L-GW access according to the CPE IP address and/or the FQDN, and establishes a second policy control session. At the same time, the BPCF obtains the subscription QoS information of the fixed line used by the L-GW access, and this information serves as a basis for subsequent admission control of the resource request of the offload service.

 1011. The BPCF returns a response to the L-GW that the first policy control is successfully established.

 1012. The L-GW returns a session establishment response to the S-GW. The response message includes information such as the TEID generated by the L-GW, the UE IP address, and the L-GW local private network IP address -1.

1013, the subsequent steps of establishing the PDN connection, including the Sxx connection establishment process request, refer to the description of steps 411-416 in FIG. 1014. After the UE establishes a PDN connection, the offload service can be performed. Refer to steps 810-815 in Figure 8 for the process of performing admission control by the BPCF during the business process and other processes.

 It should be noted that, in the first embodiment to the third embodiment of the present invention, the CPE IP address is sent to the BNG/BRAS, and the BNG/BRAS filters the data packet according to the CPE IP address, and the data packet is encapsulated by using the CPE IP address. It is considered to be an offload data message. However, if the RG is connected to the HeNB system, it can also be accessed by other users (such as fixed network users). When the data sent by the other users passes through the RG, the local private network IP address is also converted into a CPE IP address. At this time, the resource control provided by the BNG/BRAS according to the CPE IP address is RG-level resource control, that is, includes resource control for other user access under the RG. To avoid this situation, the RG may be configured to be dedicated. The HeNB system is used for access.

 In another solution, when the L-GW is powered on to perform the access authentication to the fixed network, the RG acts as the authenticator, and assigns the private network IP address to the L-GW, and the RG will correspond to the CPE IP address after the NAT is transferred. And the port number set is sent to BNG/BRAS. When the port number set is used by the UE accessed by the HeNB system to perform the offload service, the data packet is used after NAT conversion by the RG. At this time, the BNG/BRAS filters the packet according to the CPE IP address and the port number set. If the data packet is encapsulated by the CPE IP address, and the used port number also belongs to the range of the port number set, the The packet is an offload data packet, so that resource control is performed. If the data packet is encapsulated by the CPE IP address, but the port number used does not belong to the range of the port number set, the data packet is not offload data. For the message, BNG/BRAS will not perform resource control on the data message. This enables resource control at the L-GW level.

 It should be noted that the solution and all the embodiments of the present invention only describe the policy control implementation of the UE accessing the HeNB system to perform the offload service, and all implementations thereof can also be used in the HNB system.

In summary, the resource control problem of the offload service performed by the UE accessed by the HeNB is solved by the foregoing embodiment of the present invention, so that the offload service carried out by the UE can also be obtained. QoS guarantee.

 Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

 The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim  A method for resource control of local offload data, the method comprising: after receiving a trigger message, the local gateway L-GW sends an admission control request to the broadband policy control function BPCF;  The BPCF performs admission control, returns an admission control result to the L-GW, and sends a control policy to the broadband network gateway/broadband remote access server BNG/BRAS when the admission control result is accepted, the control The policy includes at least a customer premises equipment network protocol CPE IP address and authorized quality of service QoS information.  The method of claim 1, wherein the method further comprises: after returning the admission control result to the L-GW, the method further comprises:  The L-GW performs a bearer operation according to the admission control result.  The method for performing resource control on the local unloading data according to claim 1, wherein after the issuing the control policy to the BNG/BRAS, the method further includes:  The BNG/BRAS filters the data packet according to the CPE IP address, and performs resource control on the data packet encapsulated by the CPE IP address according to the authorized QoS information.  The method for performing resource control on local offload data according to claim 1, wherein the trigger message is a resource allocation request, a service request, or a bearer operation request from a network from a UE side of the user equipment.  The method for performing resource control on the local unloading data according to claim 2, wherein the L-GW performs the bearer operation according to the admission control result:  If the admission control result is a rejection, the L-GW rejects the bearer setup or modification operation;  If the admission control result is accepted, the L-GW initiates a bearer setup or modification operation. 6. Resource control of local offload data according to any one of claims 1 to 5. The method further includes: before the L-GW receives the trigger message, the method further includes: the BPCF and the L-GW establish a first policy control session, and the BPCF acquires the CPE IP address; A second policy control session between BNG/BRAS.  The method for performing resource control on local unloading data according to claim 6, wherein the first policy control session is a policy control session directly established between the BPCF and the L-GW;  Correspondingly, the L-GW discovers the BPCF according to the CPE IP address, and establishes the first policy control session.  8. The method for resource control of local offload data according to claim 6, wherein the first policy control session is a policy control session established between the L-GW and the policy and charging rule function PCRF, and a PCRF and The policy control session is established between the BPCFs; correspondingly, the L-GW discovers the PCRF according to the LHN-ID or the CPE IP address, and establishes a policy control session with the PCRF; The CPE IP address discovers the BPCF and establishes a policy control session with the BPCF.  9. A system for resource control of local offload data, the system comprising: a local gateway L-GW, a broadband policy control function BPCF, a broadband network gateway/broadband remote access server BNG/BRAS, wherein  The L-GW is configured to send an admission control request to the BPCF after receiving the trigger message; The BPCF is configured to perform admission control, and return an admission control result to the L-GW, and send a control policy to the BNG/BRAS when the admission control result is accepted, where the control policy includes at least Customer premises equipment network protocol CPE IP address and authorized quality of service QoS information; The BNG/BRAS is configured to receive a control policy delivered by the BPCF.  10. The system for performing resource control on local offload data according to claim 9, wherein the L-GW is further configured to perform a bearer operation according to the admission control result.  The system for performing resource control on the local unloading data according to claim 9, wherein the BNG/BRAS is further configured to: filter the data packet according to the CPE IP address, and encapsulate the data encapsulated by the CPE IP address. The message is resource controlled according to the authorized QoS information.  The system for performing resource control on the local offload data according to claim 9, wherein the trigger message is a resource allocation request, a service request, or a bearer operation request from the network from the UE side of the user equipment.  The system for performing resource control on the local unloading data according to claim 10, wherein the L-GW is further configured to: when the admission control result is rejected, reject the bearer establishment or modification operation; When the control result is accepted, a bearer setup or modification operation is initiated.  The system for performing resource control on the local offload data according to any one of claims 9 to 13, wherein the BPCF is further configured to: before the L-GW receives the trigger message, the BPCF and the L- The GW establishes a first policy control session, and the BPCF acquires the CPE IP address A second policy control session between BNG/BRAS.  The system for performing resource control on the local offload data according to claim 14, wherein the first policy control session is a policy control session directly established between the BPCF and the L-GW;  Correspondingly, the L-GW discovers the BPCF according to the CPE IP address, and establishes the first policy control session. 16. The system for resource control of local offload data according to claim 14, wherein The first policy control session is composed of a policy control session established between the L-GW and the policy and charging rule function PCRF, and a policy control session established between the PCRF and the BPCF; correspondingly, the L-GW Discovering the PCRF according to an LHN-ID or CPE IP address, and establishing a policy control session with the PCRF; the PCRF discovers the BPCF according to the CPE IP address, and establishes a policy with the BPCF Control the session.