WO2013082987A1

WO2013082987A1 - Method and system for performing resource control on local offload data

Info

Publication number: WO2013082987A1
Application number: PCT/CN2012/084330
Authority: WO
Inventors: 毛玉欣; 周晓云; 宗在峰; 毕以峰
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-12-05
Filing date: 2012-11-08
Publication date: 2013-06-13
Also published as: CN103139914A

Abstract

Disclosed is a method for performing resource control on local offload data, comprising: a PCRF obtaining a customer premise equipment Internet protocol (CPE IP) address from an S-GW, and according to the CPE IP address, determining a broadband policy control function (BPCF); and after receiving a bearer operation request of an L-GW, the S-GW requesting, through the PCRF, the BPCF to perform resource allocation for local offload data. Further correspondingly disclosed is a system for performing resource control on local offload data. Through the present invention, the policy control problem occurring when a UE accessed through an HeNB/HNB launches an offload service may be solved, so that the QoS of the offload service launched by the UE accessed through the HeNB/HNB obtains is guaranteed.

Description

Method and system for resource control of local unloading data

The present invention relates to the field of wireless communications, and in particular, to a method and system for resource control of locally offloading data. Background technique

FIG. 1 is a schematic diagram of a structure of a HeNB accessing an EPC in the prior art. As shown in FIG. 1 , an Evolved Packet Core network (EPC) developed by a 3rd Generation Partnership Project (3GPP) Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW), Home Subscriber Server (HSS) The network element is composed of a network element, where the MME is responsible for control planes such as mobility management, non-access stratum signaling processing, and user mobility management context management; and the S-GW forwards data between the user access and the P-GW. And is responsible for buffering paging waiting data; P-GW is a border gateway between EPS and Packet Data Network (PDN), which is responsible for PDN access and forwarding data between EPS and PDN.

If the EPC supports Policy and Charging Control (PCC), the Policy and Charging Rules Function (PCRF) performs policy and charging rules. It uses the interface Rx and the carrier network protocol. The application function (AF) of the service network (the Internet Protocol, IP) 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 GTP protocol, the P-GW resides in the Policy and Charging Enforcement Function (PCEF), and the PCRF and the P-GW pass the Gx interface. Exchange information, responsible for initiating bearer establishment, modification, and release, ensuring quality of service data transmission (Quality of Service, QoS), and charge control. When the S5 interface of the S-GW and the P-GW adopts Proxy Mobile IP (PMIP), the S-GW hosts Bearer Binding and Event Report Function (BBERF), 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 (HNB subsystem) or an evolved Home Node Node (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 accesses the EPC through a leased fixed line. In order to ensure the security of the access, the EPC network needs to deploy a security gateway (SeGW). After the HeNB/HNB is powered on, an IPSec tunnel is established with the SeGW. The UE accessed by the HeNB/HNB interacts with the EPC network. The data is encapsulated in 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 deployment network element. If not deployed, the HeNB is directly connected 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, unlike the HeNB system, the HNB system also supports the CS service, 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 also preempting network resources by multiple services may result in failure to provide quality of service for services with high QoS requirements. Guarantee. Therefore, the 3GPP R1 standard specification defines the 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 directly through the fixed network line used by the HeNB system and the HeNB system. Routing, we call this part of the data as offload data.

2 is a schematic diagram of a HeNB system in which an independent local gateway (L-GW) is deployed in the prior art. As shown in FIG. 2, the 3GPP R-11 introduces an independent L-GW network element for the HeNB system to support the offload function. The L-GW is deployed on the local network and functions like the PDN 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 HeNB local IP address and the L-GW 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 assigns 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.

3 is a schematic diagram of a route of the offload data accessed by the HeNB in the prior art. As shown in FIG. 3, the HeNB and the L-GW are deployed under the 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 ).

When a UE accessing the HeNB system needs to perform an offload service, a PDN connection (for example, a SIPTO connection) for accessing the offload service needs to be established. FIG. 4 is a flowchart of establishing a SIPTO connection in the prior art, and only after establishing the PDN connection. The UE can perform an 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, and 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, the HeNB system accesses through the RG. In the case of the fixed network, the local IP address can be assigned by the RG to the HeNB and the L-GW. FIG. 4 specifically includes the following steps:

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 sum. The IKEv2 negotiation between the SeGWs establishes an IPSec tunnel, and the SeGW allocates the 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 completed, 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 DNS server, and sends the L-GW@LN address, the L-GW@CN address, the FQDN, and the APN information to the DNS server for storage.

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

Step 405. The access UE initiates a SIPTO 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, it first determines whether the UE can perform SIPTO according to the APN information. If yes, initiates a DNS query according to the LHN-ID, and selects a corresponding step 407. When the DNS server selects the access for the UE. After the L-GW, the information of the selected L-GW (including L-GW@LN address, L-GW@CN address, FQDN, etc.) is returned to the MME for storage.

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 TEID generated by the L-GW and the IP address allocated for 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 complete, the MME initiates a bearer modification request to the L-GW through the S-GW, and brings the TEID and HeNB@LN address information of the HeNB to the L-GW. Or, after receiving the PDN connection establishment, the MME sends the HID TEID and the HeNB@LN address information to the L-GW through the S-GW by using a new message.

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.

Figure 3 and Figure 4 illustrate the PDN connection establishment process and data routing of the HeNB system supporting 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 access, and the fixed network resources are used by a large number of users (including mobile users and fixed networks). User) may cause resource shortage. If the offload service is a service that needs to provide QoS guarantee, then the QoS guarantee for the offload will not be provided in this case. Therefore, how to provide resource control for the offload data in the above scenario is a problem that needs to be solved. Summary of the invention

In view of the above, the main object of the present invention is to provide a method and system for resource control of local offload data, which is used to solve the problem of policy control for offloading services of a UE accessed by a HeNB/HNB, so that the HeNB/HNB is connected. The offload service carried out by the incoming UE can also be To get QoS guarantee.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A method for resource control of local offload data, including:

The policy and charging rule function PCRF obtains the CPE IP address of the customer premises equipment Internet protocol from the serving gateway S-GW, and determines the broadband policy control function BPCF according to the CPE IP address;

After receiving the bearer operation request of the local gateway L-GW, the S-GW requests the BPCF to perform resource allocation for the local offload data by using the PCRF.

The PCRF obtains a CPE IP address from the S-GW, and determines a BPCF according to the CPE IP address, including:

The PCRF and the S-GW establish a first policy control session, and the S-GW sends the CPE IP address to the PCRF;

The PCRF discovers a BPCF according to the CPE IP address, establishes a second policy control session with the BPCF, and notifies the BPCF of the CPE IP address.

After the PCRF determines the BPCF according to the CPE IP address, the method further includes: the BPCF discovering the broadband network gateway/broadband remote access server BNG/BRAS according to the CPE IP address, and establishing the first with the BNG/BRAS Three policy control sessions.

After receiving the bearer operation request of the L-GW, the S-GW requests the BPCF to allocate resources for the local offload data by using the PCRF, including:

After receiving the bearer operation request, the S-GW sends an admission control request to the PCRF through the first policy control session, and the PCRF sends an admission control request to the BPCF through the second policy control session;

The BPCF performs an admission control decision and generates an admission control result;

The BPCF returns an admission control result to the PCRF through the second policy control session, and the PCRF returns an admission control result to the S-GW through the first policy control session. After receiving the bearer operation request of the L-GW, the S-GW requests the BPCF to perform resource allocation for the local uninstall data by using the PCRF, including:

And the BPCF sends the control policy to the BNG/BRAS by using the third policy control session, where the control policy includes at least the CPE IP address and authorized QoS information;

The BNG/BRAS filters data packets and performs resource control on the local uninstall data.

The BNG/BRAS filter data packet, and the resource control of the local unloading data is: if the data packet is encapsulated by a CPE IP address, the data packet is a local unloading data packet, and the BNG/BRAS pair is The data packet is resource controlled according to the authorized QoS information in the control policy.

A system for resource control of local offload data, including: PCRF, S-GW, BPCF, and L-GW;

The PCRF is configured to acquire a CPE IP address from the S-GW, and determine a BPCF according to the CPE IP address;

The S-GW is configured to, after receiving the bearer operation request of the L-GW, request the BPCF to perform resource allocation for the local offload data by using the PCRF;

The BPCF is set to perform resource allocation according to a request from the PCRF;

The L-GW is configured to initiate a bearer operation request to the S-GW.

The system also includes BNG/BRAS,

The BPCF is further configured to determine BPCF according to the CPE IP address at the PCRF Thereafter, the BNG/BRAS is discovered according to the CPE IP address, and a third policy control session is established with the BNG/BRAS.

The BPCF returns an admission control result to the PCRF through the second policy control session, and the PCRF returns an admission control result to the S-GW through the first policy control session.

The method and system for resource control of local offload data, the PCRF obtains a customer premises equipment Internet Protocol (CPE IP) address from the S-GW, and determines a broadband policy control function (BPCF) according to the CPE IP address; After receiving the bearer operation request of the L-GW, the GW requests the BPCF to perform resource allocation for the local offload data by using the PCRF. The present invention can solve the problem of the policy control of the offload service performed by the UE accessed by the HeNB/HNB, so that The offload service carried out by the UE accessed by the HeNB/HNB is guaranteed by QoS. 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 in which an independent L-GW is deployed in the prior art;

3 is a schematic diagram of a route for accessing offload data by a HeNB in the prior art; FIG. 4 is a flowchart of establishing a SIPTO connection in the prior art;

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:l mode on the private network IP address of the device accessed by the RG in the prior art;

FIG. 7 is a schematic flowchart of a method for resource control of local unloading data according to the present invention; FIG. 8 is a schematic flowchart of a policy control session establishment process according to Embodiment 1 of the present invention; FIG. 9 is a schematic flowchart of implementation of admission control according to Embodiment 2 of the present invention; . detailed description

The basic idea of the present invention is: the PCRF obtains the CPE IP address from the S-GW, and determines the BPCF according to the CPE IP address; after receiving the bearer operation request of the L-GW, the S-GW requests the PCRF through the BPCF allocates resources for local offload data.

In order to find a solution to solve the policy control problem of the offload service of the UE accessed by the HeNB/HNB, first describe the fixed network backhaul (ie UE and BNG/BRAS) used by the offload data in the HeNB system and the HeNB/L-GW access. Between the routing process.

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 through IKEv2 negotiation with the SeGW using its local private IP address, the local private IP address of the HeNB Address-1 performs NAT translation to the public network IP address (called CPE IP address) and port (set) -1 on the RG. The local private network IP address-2 of the L-GW performs NAT translation to the CPE IP address on the RG. And port (set) - 2.

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 line of offload data is used as an example. The source and destination IP addresses of the uplink data packets need to be exchanged for the downlink data. The IP layer data encapsulation format is used for data routing. The package diagram of the offload data routing is shown in Figure 5.

The UE sends offload data to the HeNB, where 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 packet arrives at the HeNB, the Sxx tunnel is encapsulated, 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 decapsulates the Sxx tunnel and sends the decapsulated data packet to the RG. The RG performs NAT conversion on the source IP address of the data (ie, the local private IP address of the UE -3), converts it into a CPE IP address and a port number of -3, and then sends it to the BNG/BRAS.

FIG. 6 is a schematic diagram of a NAT conversion performed by the RG in the N:1 mode on the private network IP address of the device accessed by the RG. As shown in FIG. 6, the RG is a HeNB, and the L-GW and the UE allocate a local private network. IP address -1, local private network IP address -2 and local private network IP address -3. When the device sends the information through the RG by using the local private network IP address allocated by the RG (for example, the HeNB and the L-GW initiate IKEv2 negotiation through the RG to the SeGW, or the UE initiates the offload service through the RG), the RG needs to perform N: l NAT conversion, that is, the RG converts the HeNB's local private network IP address-1 to perform NAT to CPE IP address + port (set) 1; converts the L-GW's local private network IP address-2 to perform NAT 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 RG The public IP address of the device connected to the device is used to perform the NAT translation of the public IP address.

The data packets of the offload service carried out by the UE accessed by the HeNB system need to perform the conversion of the private network IP address and the CPE IP address of the UE 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, if the offload service is started, a policy control session is established on the BNG/BRAS. After the offload service is performed, the policy control device sends a control policy to the BNG/BRAS, where the control policy includes at least a CPE IP address and authorized QoS information. The BNG/BRAS filters the data packet according to the CPE IP address in the delivered control policy. If the packet is encapsulated by the CPE IP address, the packet is an offload data packet, and is included in the control policy that is delivered according to the policy. Authorize QoS information for resource control.

Based on the above, the present invention provides a method for resource control of local offload data. FIG. 7 is a schematic flowchart of a method for resource control of local offload data according to the present invention. As shown in FIG. 7, the process includes:

Step 701: The PCRF obtains the CPE IP address from the S-GW.

Specifically, the PCRF and the S-GW establish a first policy control session, and the S-GW sends the CPE IP address to the PCRF.

Here, the first policy control session is used by the PCRF to receive an admission control request from the S-GW, and is used by the PCRF to return an admission control result to the S-GW, where the admission control result is to accept the request or reject the request. Instructions.

The IP address of the CPE is the public IP address of the local private network IP address of the device accessed by the RG after NAT transformation.

Step 702: The PCRF determines a BPCF according to the CPE IP address.

Specifically, the PCRF finds a BPCF according to the CPE IP address, establishes a second policy control session with the BPCF, and notifies the BPCF of the CPE IP address.

Here, since the CPE IP address is an IP address information allocated by the fixed network device, the fixed network passes In the IP address planning or configuration mode, BPCF and BNG/BRAS corresponding to the address segment where the CPE IP address is located can be specified. Therefore, the BPCF can be found according to the CPE IP address.

The BPCF is used to control QoS resources of the fixed line used by the L-GW access, and the second policy control session is used by the PCRF to send an admission control request to the BPCF and to receive the admission control result from the BPCF.

It is to be noted that after the PCRF determines the BPCF according to the CPE IP address, the method further includes: the BPCF discovering, according to the CPE IP address, a broadband network gateway/broadband remote access server BNG/BRAS, and the The BNG/BRAS establishes a third policy control session. Here, the BNG/BRAS is a device on the fixed line line used by the L-GW to access. The third policy control session is used by the L-GW to receive a control policy delivered by the BPCF, where the control policy includes at least the CPE IP address and the authorized QoS information.

Step 703: After receiving the bearer operation request of the L-GW, the S-GW requests the BPCF to perform resource allocation for the local offload data by using the PCRF.

The step specifically includes: after receiving the bearer operation request, the S-GW sends an admission control request to the PCRF by using a first policy control session, where the PCRF sends an admission control request to the BPCF by using a second policy control session. The BPCF performs an admission control decision and generates an admission control result; the BPCF returns an admission control result to the PCRF through the second policy control session, and the PCRF controls the session to the S through the first policy -GW returns the admission control result.

The step of the method further includes: the BPCF sending the control policy to the BNG/BRAS by using the third policy control session, where the control policy includes at least the CPE IP address and authorized QoS information; The BRAS filters data packets and performs resource control on the local unloaded data.

Preferably, the present invention is applicable to a scenario in which the UE performs resource control on the offload data when the UE accesses and performs an offload service. The present invention also correspondingly proposes a system for resource control of local offload data, the system comprising: PCRF, S-GW, BPCF and L-GW;

The L-GW is configured to initiate a bearer operation request to the S-GW.

The system also includes BNG/BRAS,

The BPCF is further configured to: after the PCRF determines the BPCF according to the CPE IP address, discover the BNG/BRAS according to the CPE IP address, and establish a third policy control session with the BNG/BRAS.

The BPCF returns an admission control node to the PCRF through the second policy control session The PCRF returns an admission control result to the S-GW through the first policy control session.

It should be noted that, in the present invention, the CPE IP address is the local IP address of the L-GW when the network is not deployed with the NAT, and the NAT is deployed in the network (for example, the RG accessing the L-GW exists in the NAT). In the case of the public network IP address after the LAN conversion of the local IP address of the L-GW.

The technical solution of the present invention will be further described in detail below with reference to specific embodiments. Example 1

The scenario described in this embodiment is that the HeNB system accesses the EPC through the RG and the BBF network, and the RG allocates the private network IP address for the device accessed by the RG, and the UE accesses the network to establish a PDN connection establishment process for performing the offload service. FIG. 8 is a schematic flowchart of a policy control session establishment process according to Embodiment 1 of the present invention. As shown in FIG. 8, the process includes:

Step 801. The L-GW is powered on, and the access authentication to the fixed network is completed, and the RG allocates a local private network IP address. The L-GW uses the local private network IP address and the SeGW to complete the IKEv2 negotiation and establish an IPSec tunnel. The SeGW allocates a core network IP address to the L-GW. During the IKE negotiation process, the RG performs NAT translation on the L-GW local private network IP address into a CPE IP address. So SeGW Sending the CPE IP address and the L-GW core network IP address to the step 802 by extending the IKEv2 message. The L-GW initiates a DNS update to the DNS server located in the core network, and sets the L-GW core network IP address, LHN-ID, Information such as APN is sent to the DNS server.

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

Step 804. After receiving the request message, the MME first determines whether to allow the UE to establish the PDN connection according to the APN information, and if possible, queries the DNS server for the L-GW serving the UE according to the LHN-ID. The DNS server determines the L-GW and returns the L-GW information (e.g., the L-GW core network IP address) to the MME.

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

Step 806. The S-GW utilizes a session establishment request to the L-GW.

Step 807. The L-GW returns a session establishment response to the S-GW. At the same time, the L-GW obtains the local private network IP address allocated by the RG to the UE. The L-GW includes the TEID generated by the L-GW, the UE local private network IP address, the L-GW local private network IP address, and the CPE IP address in the response message.

Step 808. After receiving the session establishment response, the S-GW discovers the PCRF according to the UE-ID, and initiates a first policy control session establishment to the PCRF, and the S-GW sends the CPE IP address to the PCRF.

It should be noted that the S-GW selects the PCRF according to the UE-ID, and the first policy control session established by the S-GW and the PCRF is the UE level, that is, the UE accessed by the HeNB system is found according to the UE-ID. Different PCRFs establish different first policy control sessions.

It should be noted that the session establishment request (step 805) / response message received at the S-GW (Step 807) carries the LHN-ID, and the S-GW may also discover the PCRF according to the LHN-ID and establish a first policy control session. The first policy control session at this time is an L-GW level, that is, all UEs accessed by the HeNB system share the first policy control session. The first policy control session is created when the first UE accessing the HeNB system is accessed, and the other UEs do not need to be created when accessing.

Step 809. After receiving the request, the PCRF discovers the BPCF that controls the L-GW to access the fixed line resource according to the CPE IP address, and initiates a second policy control session establishment, and sends the CPE IP address to the BPCF. ₀

Step 810. The BPCF discovers the BNG/BRAS on the fixed network line used by the L-GW access according to the CPE IP address, and establishes a third policy control session. The BPCF obtains the subscription QoS information of the fixed network line used by the L-GW access, and this information serves as a basis for the subsequent BPCF decision on the QoS policy of the service data flow using the fixed line.

Step 811. The S-GW returns a session establishment response to the MME, where the response message includes the UE local private network IP address and the L-GW local private network IP address.

Step 812. After receiving the session establishment response, the MME sends a bearer setup request to the HeNB, where the request message includes the L-GW local private network IP address, the FQDN, the TEID, and the local private network IP address information of the UE.

Step 813. An RRC connection is established between the HeNB and the UE, and the HeNB sends the UE local private network IP address to the UE.

Step 814. The HeNB returns a bearer setup response to the MME, where the response message includes the TEID generated by the HeNB and the local private network IP address information of the HeNB.

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

Step 816. After receiving the message that the PDN connection is complete, the MME initiates a modification request to the L-GW through the S-GW, and brings the TEID of the HeNB and the local private network IP address information of the HeNB to the L-GW. Or, after the MME receives the establishment of the PDN connection, the new MME adds The TID of the HeNB and the HeNB local private network IP address information are sent to the S-GW through the S-GW, and 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 RG for its assigned IP address.

It should be noted that the S-GW obtains the L-GW local private network IP address, which can also be obtained from the MME in step 804. The premise is that the L-GW must update its local private IP address to the core network DNS server. Since the MME determines the L-GW serving the UE through the DNS query, the L-GW local private network IP address can be obtained. Then step 807 does not require the L-GW to transmit the L-GW local private network IP address to the S-GW.

It should be noted that, if the S-GW obtains the L-GW local private network IP address from the MME, the establishment of the policy control session may also occur after step 805. Example 2

The present embodiment describes a resource control process when the UE accessing the HeNB system performs the offload service. FIG. 9 is a schematic flowchart of the admission control implementation in the first embodiment of the present invention. As shown in FIG. 9, the process includes:

Step 901: If the UE accessing the HeNB system needs to perform offload service, the UE initiates a bearer resource request to the MME, where the request message includes the requested QoS.

Step 902. The MME forwards the bearer resource request to the S-GW.

Step 903. When the S-GW receives the request, it initiates an admission control request to the PCRF. Step 904. The PCRF forwards the admission control request to the BPCF.

Step 905. The BPCF combines the QoS resources of the fixed network line used by the L-GW to perform admission control on the request, and if the resources on the fixed network line used by the L-GW access can satisfy the service, the QoS is performed. The request accepts the request and returns an admission control result to the PCRF. Step 906. If the BPCF accepts the request, the BPCF sends a control policy to the BNG/BRAS, where the control policy includes the CPE IP address and the authorized QoS.

Step 907. When the PCRF receives the admission control result returned by the BPCF, it returns an admission control result to the S-GW.

Step 908. If the admission control result is to accept the request, the S-GW continues to send a bearer resource request to the L-GW.

Step 909. According to the request, the L-GW initiates a bearer operation request to the S-GW, for example, initiates bearer setup or bearer modification.

It should be noted that the S-GW sends a process of accepting the control request to the PCRF, that is, steps 903 - 905 may also occur after step 909.

Step 910. The S-GW initiates a bearer operation request to the MME.

Step 911. The MME initiates a bearer operation request to the HeNB.

Step 912. The HeNB initiates an RRC connection reconfiguration with the UE.

Step 913. The HeNB returns a response of the bearer operation to the MME.

Step 914. The MME returns a response to the operation to the S-GW.

Step 915. The S-GW returns a response of the bearer operation to the L-GW.

After the corresponding bearer resources are reserved for the offload service carried out by the UE, the offload service can be started. The BNG/BRAS filters the traversed data packets according to the CPE IP address. If the data packet is encapsulated by using the CPE IP address, the BNG/BRAS will perform the QoS QoS for the data packet according to the BPCF. Data messages are used for resource control.

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 implement the SIPTO service, and all the method implementation solutions can also be used in the HNB system.

It can be seen that, by using the foregoing embodiment of the present invention, the policy control problem of the offload service performed by the UE accessed by the HeNB is solved, so that the offload service initiated by the user 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 present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. within the spirit and scope of the invention are intended to be included within the scope of the invention.

Claims

Claim

A method for resource control of local offload data, wherein the method includes: a policy and charging rule function PCRF obtains a customer premises equipment Internet Protocol CPE IP address from a serving gateway S-GW, and according to the CPE IP address Determining the broadband policy control function BPCF;

2. The method according to claim 1, wherein the PCRF obtains a CPE IP address from the S-GW, and determines a BPCF according to the CPE IP address, including:

The method according to claim 1 or 2, wherein after the PCRF determines the BPCF according to the CPE IP address, the method further includes:

The BPCF discovers a broadband network gateway/broadband remote access server BNG/BRAS according to the CPE IP address, and establishes a third policy control session with the BNG/BRAS.

The method according to claim 1, wherein, after receiving the bearer operation request of the L-GW, the S-GW requests the BPCF to perform resource allocation for local unloading data by using the PCRF, including:

The BPCF returns an admission control result to the PCRF through the second policy control session, and the PCRF returns an admission control node to the S-GW through the first policy control session. fruit.

The method according to claim 5, wherein the BNG/BRAS filters the data message and performs resource control on the local unloading data as:

If the data packet is encapsulated by the CPE IP address, the data packet is a local unloaded data packet, and the BNG/BRAS performs resource control on the data packet according to the authorized QoS information in the control policy.

7. A system for resource control of local offload data, wherein the system comprises: a PCRF, an S-GW, a BPCF, and an L-GW; wherein

The L-GW is configured to initiate a bearer operation request to the S-GW.

8. The system according to claim 7, wherein the PCRF obtains a CPE IP address from the S-GW, and determines a BPCF according to the CPE IP address, including:

The PCRF discovers a BPCF according to the CPE IP address, and establishes a second with the BPCF. The policy control session notifies the BPCF of the CPE IP address.

The system according to claim 7 or 8, wherein the system further comprises a BNG/BRAS, the BPCF being further configured to: after the PCRF determines the BPCF according to the CPE IP address, according to the CPE IP address The BNG/BRAS is discovered and a third policy control session is established with the BNG/BRAS.

The system of claim 7, wherein the S-GW requests the BPCF to perform resource allocation for the local offload data by using the PCRF after receiving the bearer operation request of the L-GW, including:

The system according to claim 7, wherein the S-GW requests the BPCF to perform resource allocation for the local offload data by using the PCRF after receiving the bearer operation request of the L-GW, including:

12. The system according to claim 11, wherein the BNG/BRAS filter data packet, and the resource control of the local uninstall data is: