WO2011072438A1

WO2011072438A1 - Local breakout processing method, device and system in interworking proxy scenario

Info

Publication number: WO2011072438A1
Application number: PCT/CN2009/075561
Authority: WO
Inventors: 王珊珊; 戚彩霞; 胡颖
Original assignee: 华为技术有限公司
Priority date: 2009-12-14
Filing date: 2009-12-14
Publication date: 2011-06-23
Also published as: CN102763486A; CN102763486B

Abstract

The embodiments of the present invention provide a Local Breakout (LBO) processing method in Interworking Proxy (IWP) scenario. The method includes: judging whether the roaming scenario is LBO or not; if the roaming scenario is LBO, sending a Policy Control and Charging (PCC) request to a home Policy Charging Rule Function (hPCRF); receiving a PCC response message returned by the hPCRF, and forwarding the PCC response message. Correspondingly, the embodiments of the present invention also provide a network entity and communication system.

Description

LBO processing method, device and system in IWP scenario

Technical field

The present invention relates to the field of communications technologies, and in particular, to a LB0 processing method, apparatus, and system in an IWP scenario. Background of the invention

The core network of the wireless evolution network mainly includes three logical functions: a mobility management entity (MME, Mobility Management Entity), a service gateway (S-GW, a Serving Gateway), and a packet data gateway (P_GW, Packet Data Network Gateway), among which The MME is responsible for encrypting NAS signaling and NAS signaling with the user equipment (UE, User Equipment), assigning temporary identity to the UE, and selecting core network elements such as S-GW and P-GW to provide roaming, tracking, and security. And so on, it corresponds to the control plane part of the SGSN inside the current UMTS system. The S-GW is a mobility anchor that switches between local E-UTRAN base stations (eNBs, E-UTRAN Nodes) and provides lawful interception related functions; the P-GW is responsible for user address allocation, policy control, and enforcement of charging rules. And legal listening related functions. The Home Subscriber Server (HSS) is used to store subscription information of users. The Policy Charging Rule Function (PCRF) provides policy and charging control rules.

In the above system architecture, the S-GW and the P-GW are UEs via a core network and a packet data network (PDN, Packet Data).

Network) The necessary gateway for data exchange between. In the scenario of local route (LB0, Local Breakout), the S-GW and the P-GW belong to the same public land mobile communication network (PLMN), and they are connected by the S5 reference point; In the home network routing scenario, the S-GW is located in the visited Public Land Mobile Network (VPLMN), and the P-GW is located in the home public land mobile network (HPLMN). The connection is made by the S8 reference point. Two protocols can be used at the S5 or S8 reference point: GPRS Tunneling Protocol (GTP) and Mobile Agent IP (ΡΜΙΡ, Proxy Mobile IP). When the GTP protocol is used, the P-GW and the PCRF are connected through the Gx reference point. The PCRF passes the UE's Policy Control and Charging (PCC) policy and the Quality of Service (QoS) through the Gx interface. The P-GW delivers the QoS information to the S-GW/MME through the GTP message for the MME to allocate the radio resources. When the PMIP protocol is used, because the PMIP protocol cannot transmit QoS information, the S-GW obtains QoS information through the Gxc reference point with the PCRF, and the S-GW transmits the QoS information to the MME for the MME to allocate the radio resources. In the case of LB0, the P_GW and the S_GW are in the VPLMN, and the SPCR reference point is connected between the home hPCRF and the vPCRF of the visited place. The vPCRF obtains the QoS and PCC information of the hPCRF and generates the final QoS and PCC information.

In the current 3GPP protocol, in order to solve the problem of GTP and PMIP network interworking, the gateway needs to support both GTP and PMIP. A protocol, such as a gateway in a PMIP network, needs to support GTP at the same time to interwork with the GTP network. In order to reduce the requirement of protocol support for network devices, NTT proposes to use the interworking proxy (IWP) interworking gateway for GTP-PMIP protocol conversion.

The prior art does not give a processing method of LB0 in the case where the IWP is used as a protocol conversion node. Summary of the invention

An embodiment of the present invention provides a system architecture and a process solution solution for using an IWP as a protocol conversion point in an LBO scenario, where the method includes:

Determine whether the roaming scene is LBO;

If the roaming scenario is an LBO, the PCC request is directly sent to the home policy charging rule function hPCRF; the response message returned by the hPCRF is received, and the response message is forwarded.

The embodiment of the present invention further provides a network entity, configured to locally route an LBO scenario, including:

a determining unit, configured to determine whether the roaming scene is an LBO;

a first sending unit, configured to send a PCC request to the home policy charging rule function hPCRF directly according to the judgment result of the determining unit, if it is an LBO;

a receiving unit, configured to receive a PCC response message returned by the hPCRF;

a forwarding unit, configured to forward the PCC response message.

The embodiment of the present invention further provides a local routing LBO system in an inter-network proxy IWP scenario, including: a network entity, configured to determine whether a roaming scenario is an LBO, and if so, directly send a PCC request to the hPCRF, and receive and forward the hPCRF transmission. PCC response message;

The hPCRF is configured to receive a PCC request and send a PCC response message to the network entity.

The method, the network entity and the communication system provided by the embodiments of the present invention effectively implement the processing of the LBO in the scenario where the IWP is used as a protocol conversion point. The IWP or the vPCRF distinguishes whether the current service scenario is an LBO and routes the correct PCC message in the LBO scenario to ensure that the service process can be executed correctly. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic flow chart 1 of a method provided by the prior art;

2 is a schematic flowchart 2 of a method provided by the prior art;

3 is a schematic flowchart of a method according to Embodiment 1 of the present invention; 4 is a schematic flowchart of a method provided by Embodiment 2 of the present invention;

FIG. 5 is a schematic flowchart of a method according to Embodiment 3 of the present invention; FIG.

6 is a schematic flowchart of a method according to Embodiment 4 of the present invention;

7 is a schematic flowchart of a method according to Embodiment 5 of the present invention;

FIG. 8 is a schematic structural diagram of a network entity according to an embodiment of the present disclosure;

FIG. 9 is a schematic diagram of a communication system according to an embodiment of the present invention. The embodiments of the present invention will be described clearly and completely in conjunction with the drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, instead of All embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

In the case that the roaming scenario is the home route, the P-GW is located in the HPLMN, the S-GW is located in the VPLMN, the S8 interface between the IWP and the S-GW adopts the PMIP protocol, and the S8 interface between the IWP and the P-GW adopts the GTP protocol. When the processing flow is shown in Figure 1, it is specifically as follows:

5101. The UE sends a PDN connection request PDN Connectivity Request message to the MME;

5102. The MME sends a Create Session Request message to the S-GW, including the UE ID, the APN, the IWP address, and the default bearer QoS.

5103. The S-GW sends a gateway control session to establish a Gateway Control Session Establishment message to the vPCRF, requesting to obtain corresponding QoS information, where the message carries the APN and the UE ID;

5104. The vPCRF forwards the Gateway Control Session Establishment message to the IWP;

5105. The IWP sends the pre-configured temporary QoS information in the gateway control session establishment response Acknowledge Gateway Control Session Establishment message to the vPCRF, where the QoS rule is included;

5106. The vPCRF forwards the temporary QoS information in step S105 to the S-GW.

S107. The S-GW sends a proxy binding update Proxy Binding Update message to the IWP, where the UE ID is included.

APN;

5108. The IWP sends a Create Session Request message to the P-GW, including the UE ID, the address of the IWP, and the tunnel endpoint identifier, APN;

5109. The P-GW will send an IP-CAN session establishment request message to the hPCRF, which carries the UE ID, APN, IP-CAN type;

SI 10. hPCRF sends IP-CAN session establishment confirmation Acknowledge IP-CAN Session Establishment message to P-GW, including PCC rule information and real QoS information;

5111. The P-GW sends a Create Session Response message to the IWP, including the address of the P-GW and the tunnel endpoint identifier, the PDN address, the EPS bearer ID, and the real QoS.

5112. IWP sending proxy binding confirmation Proxy Binding Acknowledgemen message to the S-GW, including the identity and address information of the UE, and the Charging ID.

5113. After the real QoS information received by the IWP, the gateway control QoS rule is provided to provide a Gateway Control and QoS Rules Provision message, and the vPCRF forwards the real QoS information received from the IWP to the S-GW.

SI 14. The S-GW sends the Gateway Control and QoS Rules Provision Ack to the IJ1WP via the vPCRF; SI 15. The S-GW sends a Create Session Response message to the MME;

S116. The MME sends a PDN Connectivity Accept message to the UE. Similarly, in the case where the roaming scenario is the home route, the S8 interface between the IWP and the S-GW adopts the GTP protocol, and when the S8 interface between the IWP and the P-GW adopts the PMIP protocol, the processing flow is as shown in FIG. 2 .

5201. The UE sends a PDN Connectivity Request message to the MME.

5202. The MME sends a Create Session Request message to the S-GW, where the UE ID, the APN, the IWP address, and the default bearer QoS are included.

S203. The S-GW sends a Create Session Request message to the IWP, where the UE ID, the address of the S-GW, and the TEID, APN are sent.

5204. The IWP sends a Gateway Control Session Establishment request message to the hPCRF, where the message carries the APN and the UE ID, and the default bearer QoS;

5205. The hPCRF sends a response message Acknowledge Gateway Control Session Establishment to the IWP, including the QoS rule;

5206. The IWP sending proxy binding updates the Proxy Binding Update request message to the PGW, including the UE ID, APN;

5207. The P-GW sends an IP-CAN session establishment request message to the hPCRF, where the UE ID, APN, and IP-CAN types are carried; 5208. The hPCRF sends an IP-CAN session establishment confirmation Acknowledge IP-CAN Session Establishment message to the P-GW, including PCC rule information, updated QoS information;

5209. The P-GW sending proxy binds the corresponding Proxy Binding Acknowledgement message to the IWP, including the identifier and address information of the UE, the Charging ID, and the like;

S210. If the QoS rule is changed, the hPCRF will initialize the GW Control Session Modification process. The hPCRF sends a Gateway Control and QoS Rules Pro vision request to the IWP. Which includes QoS rules;

5211. The IWP sends a Gateway Control and QoS Rules Provision response to the hPCRF.

5212. The IWP creates a session response Create Session Response message to the S-GW, which includes the address and tunnel endpoint identifier of the IWP, and QoS information;

S213. The S-GW sends a Create Session Response message to the MME.

S214. The MME sends a PDN Connectivity Accept message to the UE. Embodiment 1 of the present invention provides an LBO processing method in the case of an IWP as a protocol conversion point, as shown in FIG. 3, including:

S301. Determine whether the roaming scenario is an LBO.

The IWP or vPCRF can determine whether the roaming scene is LBO by using the UE ID and the APN.

5302. If yes, sending a PCC request directly to the home policy charging rule function hPCRF;

If not, the roaming scenario is a home route, which can be processed according to the method in the prior art. For details, refer to FIG. 1 and 2.

When GTP is used between the S-GW and the P-GW, the PCC request is an IP-CAN Session Establishment request message; if PMIP is used between the S-GW and the P-GW, the PCC request message between the S-GW and the IWP is The Gateway Control Session Establishment request message, and the message between the P-GW and the IWP is an IP-CAN Session Establishment request message.

S303: Receive a PCC response message returned by the hPCRF, and forward the PCC response message.

The forwarding of the PCC response message may be that the IWP sends the PCC response message to the vPCRF, or the vPCRF may directly send the PCC response message to the S-GW or the P-GW.

When GTP is used between the S-GW and the P-GW, the PCC response message is an IP-CAN Session Establishment response message; if a PMIP, a PCC response message between the S-GW and the IWP is used between the S-GW and the P-GW It is a Gateway Control Session Establishment response message, and the PCC response message between the P-GW and the IWP is an IP-CAN Session Establishment response message. The method provided by the embodiment of the present invention effectively implements the LBO processing method in the scenario where the IWP is used as a protocol conversion point. The IWP distinguishes whether the current service scenario is an LBO and performs routing of the correct PCC message in the LBO scenario to ensure that the service process can be executed correctly. The forwarding response message may be different according to the protocol adopted by the S5 interface. For details, refer to the following embodiments.

Embodiment 2

In this embodiment, the IWP is used to determine whether it is an LBO scenario, and the S5 interface between the S-GW and the P-GW adopts the GTP protocol. The specific steps are as follows, see Figure 4:

5401. The UE initiates a request PDN connection process, and sends a PDN Connectivity Request message to the MME;

5402. The MME sends a Create Session Request to the S-GW, where the UE ID, the APN, the P-GW address, and the default bearer QoS are carried.

5403. The S-GW creates an entry in its EPS bearer table, and sends a Create Session Request to the P-GW, including the UE ID, the address of the S-GW, and the TEID, APN information.

5404. The P-GW will send an IP-CAN Session Establishment request message to the vPCRF, including the UE ID, APN, and IP-CAN types. The vPCRF forwards this message to the IWP;

S405. The IWP determines, according to the identifier of the UE and the APN, that the current LBO scenario is sent to the hPCRF directly.

CAN session establishment request message;

The specific judgment can be:

The user identification international mobile subscriber identity IMSI and APN are used to determine the roaming scenario, if the operator identifier of the APN is in the Operator Identifier part and the Mobility Country Code (MCC) and the Mobility Network Code (MNC) in the IMSI. The common PLMNs are the same, indicating that the current local network routing scenario; if not, the current LBO scenario.

5406. The hPCRF establishes an IP-CAN session record and returns an Acknowledge IP-CAN Session Establishment to the IWP, including PCC rule information;

5407. The IWP forwards the Acknowledge IP-CAN Session Establishment message to the P-GW via the vPCRF. The IWP sends a response message to the vPCRF, that is, an Acknowledge IP-CAN Session Establishment message, and the vPCRF forwards the response message to the P-GW.

5408. The P-GW returns a Create session response message to the S-GW, where the service flow information is included, where the service flow is from the PCC rule information in S407.

5409. The S-GW sends a Create Session Response message to the MME. S410. The MME sends a PDN Connectivity Accept message to the UE.

It should be noted that, in the foregoing step S405, if the IWP determines that the routing mode of the system is the home route, the IP CAN session establishment request message is not sent to the hPCRF, that is, the above steps S406-S410 are not performed, but the existing steps are adopted. In the method of the technique, steps S204 to S214 in Fig. 2 are performed.

The embodiment of the present invention can effectively solve the processing method of the GTP protocol on the S5 interface in the IWP scenario LB0. The IWP distinguishes whether the current service scenario is LB0 and routes the correct PCC message in the LB0 scenario to ensure that the service process can be executed correctly.

Embodiment 3

In this embodiment, the IWP is used to determine whether it is an LBO scenario, and the S5 interface between the S-GW and the P-GW adopts the PMIP protocol. The specific steps are as follows, see Figure 5:

5501. The UE initiates a request PDN connection process, and sends a PDN Connectivity Request message to the MME;

5502. The MME sends a Create Session Request to the S-GW, including the UE ID, the APN, the P-GW address, and the default bearer QoS;

5503. The S-GW sends a Gateway Control Session Establishment, which is forwarded to the IWP via the vPCRF, including the IP-CAN Type, the UE ID, so that the vPCRF can identify the IP-CAN session to be established in step 8, and also forward the received from the MME. Default bearer QoS;

After receiving the message, the IWP, according to the identifier of the UE and the APN, determines that the current LBO scenario is sent, and the Gateway Control Session Establishment message is directly sent to the hPCRF;

The specific judgment can be:

The user identification of the International Mobile Subscriber Identity (IMSI) and the APN is used to determine the roaming scenario. If the Operator Identifier part of the APN is the same as the PLMN represented by the MCC and the MNC in the IMSI, the current local network routing scenario; if not, The description is currently an LBO scenario.

5505. hPCRF sends a response message Acknowledge Gateway Control Session Establishment to IWP;

S506. The IWP is forwarded via the vPCRF to the Acknowledge Gateway Control Session Establishment.

S-GW. Which includes QoS rules;

The IWP sends a response message to the vPCRF, that is, an Acknowledge IP-CAN Session Establishment message, and the vPCRF forwards the response message to the P-GW.

S507. The S-GW sends a Proxy Binding Update to the P-GW, where the UE identifier, the APN, is included; 5508. The P-GW sends an IP-CAN session establishment request to the IWP via the vPCRF, including the UE ID, APN, IP-CAN type;

5509. The IWP forwards the IP-CAN session establishment request to the hPCRF;

5510. The hPCRF sends an Acknowledge IP-CAN Session Establishment to the IWP, including PCC rule information;

5511. The IWP forwards the received acknowledgement to the PGW via the vPCRF;

5512. The P-GW sends a proxy binding acknowledgement to the S-GW, including the identifier and address information of the UE, a Charging ID, and the like;

5513. If the QoS rule changes, the hPCRF will initiate the GW Control Session Modification process, sending the Gateway Control and QoS Rules Provision to the IWP, including the QoS rules;

5514. The IWP forwards the Gateway Control and QoS Rules Provision to the S-GW via the vPCRF;

5515. The S-GW sends the Gateway Control and QoS Rules Provision Ack to the IJlWP via the vPCRF;

5516. The IWP forwards the confirmation message in step 15 to the hPCRF;

5517. The S-GW sends a Create Session Response message to the MME.

S518. The MME sends a PDN Connectivity Accept message to the UE.

It should be noted that, in the foregoing step S504, if the IWP determines that the routing mode of the system in which the system is located is the home route, steps S105-S116 in FIG. 1 are performed.

The embodiment of the present invention can effectively solve the processing method of the PMIP protocol on the S5 interface of the IBO scenario. The IWP distinguishes whether the current service scenario is an LBO and routes the correct PCC message in the LBO scenario to ensure that the service process can be executed correctly. Embodiment 4

In this embodiment, the vPCRF is used to determine whether it is an LBO scenario, and the S5 interface between the S-GW and the P-GW adopts the GTP protocol. The specific steps are as follows, see Figure 6:

S601. The UE initiates a request PDN connection process, and sends a PDN Connectivity Request message to the MME.

5602. The MME sends a Create Session Bearer Request to the S-GW, including the UE ID, APN, P-GW address, and default bearer QoS;

5603. The S-GW creates an entry in its EPS bearer table, and sends a Create Session Request to the P-GW, including the UE ID, the address of the S-GW, and the TEID, APN; 5604. The P-GW will initialize the IP-CAN Session Establishment process, and send an IP-CAN session establishment request message to the vPCRF, including the UE identity, APN, IP-CAN type;

After receiving the message, the vPCRF determines that the current LBO scenario is based on the APN and the UE identifier, and directly sends the message to the hPCRF.

The specific judgment method is the same as the above embodiment.

5606. The hPCRF sends a response message Acknowledge IP-CAN Session Establishment to the vPCRF, including PCC rule information;

5607. The vPCRF forwards the Acknowledge IP-CAN Session Establishment to the PGW;

5608. The P-GW creates a new entry in its EPS bearer context table and sends a Create Session Response to the S-GW, including the address and TEID of the P-GW, the EPS bearer ID and the QoS and service flow information, the service Flowing PCC rule information from S606;

5609. The S-GW sends a Create Session Response message to the MME.

5610. The MME sends a PDN Connectivity Accept message to the UE.

In this embodiment, after determining that the current LBO scenario is present, the vPCRF directly sends a PCC request message to the hPCRF without the IWP. When the GTP protocol is used on the S5 interface of the LBO, the vPCRF distinguishes whether the current service scenario is LBO. The correct PCC message is routed in the LBO scenario to ensure that the service process can be executed correctly.

Embodiment 4

In this embodiment, the vPCRF is used to determine whether it is an LBO scenario, and the S5 interface between the S-GW and the P-GW adopts the PMIP protocol. The specific steps are as follows, see Figure 7:

S701. The UE initiates a request PDN connection process, and sends a PDN Connectivity Request message to the MME.

5702. The MME sends a Create Session Request to the S-GW, including the UE ID, the APN, the P-GW address, and the default bearer QoS;

5703. The S-GW sends the Gateway Control Session Establishment to the vPCRF, including the IP-CAN Type, the UE ID, and also forwards the default bearer QoS received from the MME;

S704. After receiving the message, the vPCRF, according to the APN and the UE identifier, determines that the current LBO scenario is sent to the hPCRF directly.

The specific judgment method is the same as the above embodiment.

S705. The hPCRF sends a response Acknowledge Gateway Control Session Establishment message to the vPCRF; 5706. The vPCRF forwards the acknowledgement message to the S-GW;

5707. The S-GW sends a Proxy Binding Update to the PGW, where the UE identifier, the APN, is included;

5708. The P-GW sends an IP-CAN session establishment request to the vPCRF via the vPCRF, including the identity of the UE, APN, and IP-CAN type;

S709. After receiving the message, the VPCRF, according to the APN and the UE identifier, determines that the current LBO scenario is sent to the hPCRF directly.

5710. The hPCRF establishes an IP CAN session record, and returns a response message carrying the PCC rule information to the vPCRF;

10. The hPCRF sends an Acknowledge IP-CAN Session Establishment to the vPCRF, including PCC rule information;

5711. The vPCRF forwards the received acknowledgement to the PGW;

5712. The P-GW confirms to the S-GW, and sends a Binding Acknowledgement, which includes the identity and address information of the UE, Charging ID;

5713. If the QoS rule changes, the hPCRF will initialize the GW Control Session Modification process and send the Gateway Control and QoS Rules Provision to the vPCRF;

5714. The vPCRF forwards this message to the SGW;

5715. The S-GW sends the Gateway Control and QoS Rules Provision Ack to the IJvPCRF;

5716. The vPCRF forwards the acknowledgment message in step 15 to the hPCRF;

5717. The S-GW sends a Create Session Response message to the MME.

S718. The MME sends a PDN Connectivity Accept message to the UE.

In this embodiment, after determining that the current LBO scenario is present, the vPCRF directly sends a PCC request message to the hPCRF without the IWP. IWP Scenarios When the S5 interface uses the PMIP protocol, the vPCRF distinguishes the current service scenario from the LBO and performs the correct PCC message routing in the LBO scenario to ensure that the service process can be executed correctly. Corresponding to the method embodiment, the embodiment of the present invention further provides a network entity, which is used in the LBO in the IWP scenario, as shown in FIG. 8, and includes:

The determining unit 801 is configured to determine whether the roaming scene is an LBO;

The first sending unit 802 is configured to send, according to the determination result of the determining unit, a PCC request to the home policy charging rule function hPCRF, if it is an LBO; The receiving unit 803 is configured to receive a PCC response message returned by the hPCRF.

The forwarding unit 804 is configured to forward the PCC response message.

The network entity of the embodiment of the present invention may be an IWP. Correspondingly, the receiving unit 803 is further configured to receive a PCC request from the vPCRF before the determining unit determines whether the roaming scenario is an LBO.

The determining unit 801 is configured to determine, according to the UE identifier and the APN, whether the roaming scenario is an LBO;

The forwarding unit 804 is configured to send the PCC response message to the vPCRF.

The network entity of the embodiment of the present invention may be a vPCRF, and correspondingly, if the protocol between the S-GW and the P-GW is a GTP protocol, the forwarding unit 804 is configured to forward the response message to the P-GW;

If the protocol between the S-GW and the P-GW is the PMIP protocol, the forwarding unit is configured to send the PCC response message to the S-GW or the P-GW.

When GTP is used between the S-GW and the P-GW, the PCC request is an IP-CAN Session Establishment request message, and the PCC response message is an IP-CAN Session Establishment response message; if PMIP is used between the S-GW and the P-GW, The PCC request message between the S-GW and the IWP is a Gateway Control Session Establishment request message, and the PCC response message between the S-GW and the IWP is a Gateway Control Session Establishment response message; and the PCC request message between the P-GW and the IWP It is an IP-CAN Session Establishment request message, and the PCC response message is an IP-CAN Session Establishment response message.

The network entity provided by the embodiment of the present invention can distinguish whether the current service scenario is an LBO, and perform routing of the correct PCC message in the LBO scenario, so as to ensure that the service process can be correctly executed. The embodiment of the present invention further provides a local routing LBO communication system in an IWP scenario. As shown in FIG. 9, the network entity 901 is configured to determine whether the roaming scenario is LBO. If yes, the PCC request is directly sent to the hPCRF to receive and forward. a PCC response message sent by the hPCRF;

The hPCRF 902 is configured to receive the PCC request, and send a PCC response message to the network entity.

The network entity 901 in the communication system may be an IWP, and the IWP receives the PCC request message from the vPCRF, and sends the PCC request message to the PCRF directly after determining the LBO scenario, and determines whether the roaming scenario is determined according to the UE identifier and the APN. LBO.

The network entity in the communication system may be a vPCRF. If the protocol between the S-GW and the P-GW is a GTP protocol, the vPCRF sends a response message to the P-GW, and the P-GW sends the response message to The S-GW.

If the protocol between the S-GW and the P-GW is the PMIP protocol, the vPCRF sends the response message directly to the Said S-GW or said P-GW.

The communication system provided by the embodiment of the present invention can distinguish whether the current service scenario is an LBO, and perform routing of the correct PCC message in the LBO scenario, so as to ensure that the service process can be correctly executed.

The above description is only a preferred embodiment of the present invention, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present invention. It should be considered as the scope of protection of the present invention.

Claims

Rights request

An inter-network proxy LPU processing method in the IWP scenario, the method includes the following steps: determining whether the roaming scenario is an LBO;

And if the roaming scenario is an LBO, sending a PCC request to the home policy charging rule function hPCRF; receiving a PCC response message returned by the hPCRF, and forwarding the response message.

The method according to claim 1, wherein the determining whether the roaming scene is an LBO comprises: determining whether the roaming scene is an LBO according to the user equipment UE identifier and the access point name APN.

The method according to claim 2, wherein the IWP determines whether the roaming scene is an LBO, and includes:

According to the mobile country code MCC and the mobile network number MNC identified by the UE, and the APN, it is determined whether the roaming scene is LBO.

The method according to any one of claims 1-3, wherein the method is specifically: the IWP determines whether the roaming scenario is an LBO;

If the roaming scenario is LBO, the IWP sends a PCC request to the home policy charging rule function hPCRF;

The IWP receives the PCC response message returned by the hPCRF and forwards the response message.

The method according to claim 4, wherein if the protocol between the S-GW and the P-GW is the GTP protocol, the IWP determining whether the roaming scenario is an LBO includes: receiving a PCC request message from the vPCRF ;

And the transmitting, by the IWP, the PCC response message includes: sending the PCC response message to a vPCRF, where the vPCRF sends the PCC response message to the P-GW.

The method according to claim 4, wherein if the protocol between the S-GW and the P-GW is a PMIP protocol, the IWP determining whether the roaming scenario is an LBO comprises: receiving a PCC request message from the vPCRF ;

The forwarding, by the IWP, the PCC response message includes: sending the PCC response message to a vPCRF, where the vPCRF sends the PCC response message to an S-GW or a P-GW.

The method according to claim 6, wherein the method further comprises:

The IWP receives the gateway sent by the hPCRF to control the QoS rule providing message, and forwards the message to the S-GW;

Receiving a gateway control QoS rule providing response message sent by the S-GW, and forwarding the message to the hPCRF.

The method according to any one of claims 1 to 3, wherein the method is specifically: The vPCRF determines whether the roaming scenario is LBO.

9. The method according to claim 8, wherein if the protocol between the S-GW and the P-GW is

The GTP protocol, the forwarding the response message includes:

The vPCRF sends the PCC response message to the P-GW.

The method according to claim 8, wherein if the protocol between the S-GW and the P-GW is a PMIP protocol, the forwarding the PCC response message includes:

The vPCRF sends the PCC response message to the S-GW or the P-GW.

A network entity, configured to locally route an LBO scenario, and includes:

And a forwarding unit, configured to forward the PCC response message.

The entity according to claim 10, wherein the entity is an IWP, and the receiving unit is further configured to: receive, after the determining unit determines whether the roaming scenario is LBO, receive a PCC request from the vPCRF; The determining unit is configured to determine, according to the UE identifier and the APN, whether the roaming scenario is an LBO;

The forwarding unit is configured to send the PCC response message to the vPCRF.

The entity according to claim 10, wherein the entity is a v-PCRF, and if the protocol between the S-GW and the P-GW is a GTP protocol, the forwarding unit is configured to respond to the PCC. The message is forwarded to the P-GW; if the protocol between the S-GW and the P-GW is the PMIP protocol, the forwarding unit is configured to send the PCC response message to the S-GW or the P-GW.

A local routing LBO system in an inter-network proxy IWP scenario, comprising: a network entity, configured to determine whether a roaming scenario is an LBO, and if so, directly sending a PCC request to the hPCRF, receiving and forwarding the hPCRF transmission PCC response message;

An hPCRF, configured to receive the PCC request, and send a PCC response message to the network entity.

The system according to claim 14, wherein the network entity is an IWP or a vPCRF.

16. The system according to claim 14, wherein the network entity is based on a UE identity and The APN determines whether the roaming scene is LBO.