WO2011009257A1 - 一种承载绑定和事件报告功能的重选系统及方法 - Google Patents

一种承载绑定和事件报告功能的重选系统及方法 Download PDF

Info

Publication number
WO2011009257A1
WO2011009257A1 PCT/CN2009/075373 CN2009075373W WO2011009257A1 WO 2011009257 A1 WO2011009257 A1 WO 2011009257A1 CN 2009075373 W CN2009075373 W CN 2009075373W WO 2011009257 A1 WO2011009257 A1 WO 2011009257A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
pcrf
policy
message
indication message
Prior art date
Application number
PCT/CN2009/075373
Other languages
English (en)
French (fr)
Inventor
周晓云
宗在峰
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US13/258,893 priority Critical patent/US9277592B2/en
Priority to EP09847492.7A priority patent/EP2458913B1/en
Publication of WO2011009257A1 publication Critical patent/WO2011009257A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/24—Interfaces between hierarchically similar devices between backbone network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8038—Roaming or handoff
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H04W36/125—Reselecting a serving backbone network switching or routing node involving different types of service backbones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • the present invention relates to the field of communications, and in particular, to a reselection system and method for bearer binding and event reporting.
  • EPS Evolved Packet System of 3GPP (3rd Generation Partnership Project) by E-UTRAN (Evolved Universal Terrestrial Radio Access Network), MME (Evolved Universal Terrestrial Radio Access Network) Mobility Management Entity, Mobile Management Unit, S-GW (Serving Gateway), P-GW (Packet Data Network Gateway), HSS (Home Subscriber Server), 3GPP AAA Server ( 3GPP authentication and authorization accounting server), PCRF (Policy and Charging Rules Function) and other supporting nodes.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • MME Evolved Universal Terrestrial Radio Access Network
  • Mobility Management Entity Mobile Management Unit
  • S-GW Server
  • P-GW Packet Data Network Gateway
  • HSS Home Subscriber Server
  • 3GPP AAA Server 3GPP authentication and authorization accounting server
  • PCRF Policy and Charging Rules Function
  • FIG. 1 is a schematic diagram of a system architecture of an EPS in the related art.
  • 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 is connected to the E-UTRAN.
  • Incoming gateway device for forwarding data between E-UTRAN and P-GW, and for buffering paging waiting data;
  • P-GW is boundary between EPS and Packet Data Network (PDN)
  • PDN Packet Data Network
  • Non-3GPP networks include trusted non-3GPP networks and untrusted non-3GPP networks.
  • the IP (Internet Protocol) access of the trusted non-3GPP network can be directly connected to the P-GW through the S2a interface; the IP access of the untrusted non-3GPP network needs to pass the ePDG (Evolved Packet Data Gateway). ) Connected to the P-GW, the ePDG and the P-GW are connected through the S2b interface.
  • IP Internet Protocol
  • the policy and charging rules are formulated by the PCRF.
  • the PCRF is connected to the IP service network of the operator through the receiving interface Rx to obtain service information.
  • the PCRF is connected to the gateway device in the network through the Gx/Gxa/Gxc interface, and is responsible for initiating the establishment of the IP bearer, guaranteeing the QoS (Quality of Service) of the service data, and performing charging control.
  • the PCEF Policy and Charging Enforcement Function
  • the PCRF exchanges information with the P-GW through the Gx interface.
  • the interface between the P-GW and the S-GW is based on PMIP (Proxy Mobile IP)
  • PMIP Proxy Mobile IP
  • BBERF Bit Binding and Event Report Function
  • the BBERF is also resident in the trusted non-3GPP access gateway, and the access gateway between the trusted non-3GPP network and the PCRF exchanges information through the Gxa interface.
  • the interface between the home PCRF and the visited PCRF is the S9 interface
  • the AF Application Function
  • the service network is sent to the PCRF through the Rx interface.
  • the protocol used in the PCC architecture is in the Diameter base protocol (Dimeter)
  • Diameter application protocol Based on the Base Protocol (base Protocol) developed Diameter application protocol. For example, the application protocol applied to the Gx interface, the application protocol applied to the Rx interface, the application protocol applied to the Gxx interface (including the Gxa and Gxc interfaces), and the application protocol applied to the roaming interface S9. Messages, commands, and AVPs (Attribute Value Pairs) for PCC are defined in these application protocols. Diameter sessions established with these protocols can be referred to as Gx sessions, Gxx sessions, Rx sessions, and S9 sessions, respectively. Through these sessions, each functional entity of the PCC performs policy charging control on the PDN connection established for the UE to access the network.
  • IP-Connected Network IP Connectivity Access Network
  • Gx sessions Gx sessions
  • Gxx sessions gateway control sessions
  • S9 sessions S9 sessions for policy control of the same IP-CAN session.
  • the association operation takes place during the establishment and modification of the IP-CAN session.
  • the above Diameter session is called a policy charging control session.
  • FIG. 2 is a schematic diagram of an initial attach procedure of a UE accessing an EPS through an E-UTRAN and establishing a PDN connection (ie, an IP-CAN session); wherein the PM-IPv6 protocol is used between the S-GW and the P-GW.
  • the process shown mainly includes the following steps:
  • Step S201 The UE sends an attach request message to the eNodeB (evolved Node B, ie, the base station, referred to as the eNB), requesting access to the EPS;
  • eNodeB evolved Node B, ie, the base station, referred to as the eNB
  • Step S202 The eNodeB sends an attach request message to the MME.
  • Step S203 The network authenticates the UE and starts NAS (Non-Access stratum) security encryption protection
  • Step S204 After the UE is authenticated, the MME interacts with the HSS to perform a location update process.
  • Step S206 The BBERF located in the S-GW sends a gateway control to the PCRF a session establishment indication message, where the message carries a user identifier NAI (Network Access Identifier), a PDN identifier, and a bearer attribute of the current access network; the message requests the established gateway control session (Gxx session), Expressed as Gxx session 1;
  • NAI Network Access Identifier
  • the access network bearer attributes include: an IP-CAN type, a BBERF address; and the access network bearer attribute may further include a RAT (Radio Access Technology) type; Step S207: The PCRF is based on the user identifier NAI and the PDN. Identifying the APN to obtain the subscription information of the user, according to the subscription information of the user, the network policy, and the bearer attributes of the current access network (including
  • the IP-CAN type, or IP-CAN type and RAT type) formulate a policy.
  • the policy formulated by the PCRF is the default policy for the user to access the APN, including PCC rules, QoS rules, and event-triggered crying.
  • the PCRF returns a gateway control session establishment confirmation message to the BBERF, and sends the formulated QoS rule and event trigger to the BBERF; the BBERF installs and executes the QoS rule and the event trigger; Step S208:
  • the S-GW selects the P selected by the MME in step S205.
  • - GW sends a proxy binding update message, which carries the user identity NAI, the PDN identity APN, and the access network bearer attributes (including the IP-CAN type, or the IP-CAN type and the RAT type);
  • Step S209 The P-GW allocates an IP address, which is indicated as IP Address 1 , for the PDN connection requested by the UE to access.
  • the PCEF located at the P-GW sends an IP-CAN session establishment indication message to the PCRF, where the message carries the user identity NAI, the PDN identity APN, the IP Address 1, and the access network bearer attributes (including the IP-CAN type, or the IP-CAN type). And the RAT type), etc.; the access network bearer attribute in the message is obtained in step S208; the Gx session requested by the message is represented as Gx session 1;
  • Step S210 The PCRF associates the Gxx session 1 with the Gx session 1 according to the NAI and the APN, that is, the Gxx session 1 and the Gx session 1 are used for policy charging control of the PDN connection (ie, IP-CAN session) requested by the UE;
  • the PDN connection ie, IP-CAN session
  • Step S211 The PCRF returns an IP-CAN session establishment confirmation message to the PCEF, and sends the PCC rule and event trigger specified in step S207 to the PCEF; the PCEF installs and executes the PCC rule and the event trigger;
  • the PCRF may modify the PCC rule and the QoS rule according to the bearer attribute of the access network reported in step S209. At this time, the PCRF sends the modified PCC rule and the QoS rule to the PCEF and the BBERF for update;
  • Step S212 The P-GW returns a proxy binding acknowledgement message to the S-GW, where the message carries IP Address 1;
  • Step S213 The S-GW returns a default bearer response message to the MME, where the message carries IP Address 1;
  • Step S214 The MME returns an attach accept message to the eNodeB, where the message carries IP Address 1;
  • Step S215 The eNodeB returns an attach accept message to the UE, where the message carries IP Address1; Step S216: The UE sends an attach complete message to the eNodeB;
  • Step S217 The eNodeB sends an attach complete message to the MME.
  • Step S218 The MME and the S-GW perform an interaction process of updating the bearer.
  • Step S219 The MME learns that the UE can access the non-3GPP according to the subscription information of the user, and therefore sends the address of the P-GW selected by the UE to establish a PDN connection (ie, an IP-CAN session) to the HSS, and the HSS saves the P-GW address. Then return a reply message.
  • a PDN connection ie, an IP-CAN session
  • the UE establishes a PDN connection to the default APN (ie, an IP-CAN session); thereafter, the UE can access the proprietary service through the connection, and the PCRF will be based on the service characteristics, PCC rules and QoS rules are formulated for information such as user subscription information, network policies, and access network bearer attributes. Since the association is made in step S210, the PCRF can transmit the PCC rule to the PCEF through the Gx session 1 and the QoS rule to the BBERF through the Gxx session 1.
  • the PCRF can transmit the PCC rule to the PCEF through the Gx session 1 and the QoS rule to the BBERF through the Gxx session 1.
  • the PCRF When the BBERF requests a new QoS rule or modifies the QoS rule through the Gxx session 1, the PCRF also formulates the corresponding PCC rule or modifies the corresponding PCC rule and sends it to the PCEF through the Gx session 1; and vice versa.
  • FIG. 3 is a schematic diagram of a process for a UE to switch from an E-UTRAN to a trusted non-3GPP access system after accessing the EPS by using the process shown in FIG. 2; wherein, when the non-3GPP access is performed, the non-3GPP access gateway is trusted.
  • the PMIPv6 protocol is used between the P-GWs.
  • the process shown in FIG. 3 mainly includes the following steps: Step S301: The UE establishes a PDN connection (ie, an IP-CAN session) through the 3GPP access, and a ⁇ tunnel exists between the S-GW and the P-GW.
  • a PDN connection ie, an IP-CAN session
  • Step S302 The UE finds a trusted non-3GPP access system and decides to switch the current session from the 3GPP access to the trusted non-3GPP access system.
  • Step S303 The UE, the trusted non-3GPP access gateway, and the HSS/AAA perform an EAP (Extensible Authentication Protocol) authentication process; in the authentication process, the HSS/AAA selects the P selected by the UE during 3GPP access. - The address of the GW is returned to the trusted non-3GPP access gateway; Step S304: After the authentication authorization is successful, the non-3GPP access specific layer 3 attach procedure is triggered; in the process, the UE indicates to the network that it has the IP address retention capability ;
  • EAP Extensible Authentication Protocol
  • Step S305 The BBERF located in the trusted non-3GPP access gateway sends a gateway control session establishment indication message to the PCRF, where the message carries the user identifier NAI, the PDN identifier APN, and the current access network bearer attribute (including the new IP-CAN). Type, or new IP-CAN type and new RAT type), etc.; the gateway control session (Gxx session) requested by the message is represented as Gxx session 2;
  • Step S306 The PCRF associates the Gxx session 2 with the Gx session 1 established in the process shown in FIG. 2 according to the NAI and the APN;
  • Step S307 The PCRF is based on the user subscription information, the network policy, and the bearer of the current access network.
  • the QoS rules and event triggers are set by the UE through non-3GPP access, and include the proprietary policies formulated by the PCRF when the UE accesses the proprietary service after accessing the 3GPP;
  • the PCRF sends the above QoS rules and event triggers to the BBERF through the gateway control session establishment confirmation message; the BBERF installs and executes the QoS rules and event triggers; the trusted non-3GPP access gateway performs a specific non-3GPP access procedure for resource reservation ;
  • Step S308 The trusted non-3GPP access gateway sends a proxy binding update message to the corresponding P-GW according to the P-GW address obtained in step S303, where the message carries the user identifier NAI, the PDN identifier APN, and the current access network.
  • Bearer attributes including IP-CAN type, or IP-CAN type and RAT type);
  • Step S309 The P-GW allocates the IP address (ie, IP Address 1) used by the 3GPP to the UE according to the NAI and the APN to keep the IP address unchanged, thereby ensuring continuity of the service; and the PCEF direction of the P-GW
  • the PCRF sends an IP-CAN session modification indication message, where the message carries the new access network bearer attribute obtained in step S308; the message modifies the Gx session 1 established in the process shown in FIG. 2;
  • Step S310 The PCRF determines that the tunnel of the PDN connection established by the UE (ie, the IP-CAN session) has been handed over (ie, switched from 3GPP to non-3GPP), so the PCRF performs the reconstructed PDN connection according to the new access network bearer attribute (ie, IP). -CAN session) modify the PCC rule, and return the modified PCC rule to the PCEF for update via the IP-CAN session modification confirmation message;
  • Step S311 The P-GW returns a proxy binding acknowledgement message to the trusted non-3GPP access gateway, where the message carries IP Address1;
  • Step S312 The trusted non-3GPP access gateway returns a layer 3 attach complete message to the UE, where the message carries IP Address1;
  • Step S313 The UE switches the PDN connection from the 3GPP access to the trusted non-3GPP access, and the PMIPv6 tunnel exists between the trusted non-3GPP access gateway and the P-GW (the PMIPv6 tunnel is established through steps S308 and S311); The services accessed by the UE when accessing through 3GPP can continue to be accessed.
  • step S306 the PCRF associates a new Gxx session to an established PDN connection (IP-CAN session) according to the NAI and the APN, and the PCRF can After the UE is accessed through the 3GPP system, the PCRF is updated according to the new access network bearer attribute, and then sent to the new BBERF through the new gateway control session (Gxx session), thereby ensuring the PMIPv6.
  • the non-3GPP access system Before the handover of the tunnel has not occurred (ie, before step S308), the non-3GPP access system has reserved resources for the services previously accessed by the UE, speeding up the handover speed and improving the user experience.
  • the P-GW makes this decision after receiving the proxy binding update message sent by the trusted non-3GPP access gateway.
  • the PCRF has made a decision to associate a new gateway control session (Gxx session) to an existing PDN connection (ie, the PCRF has made a switch). If the P-GW decides to establish a new PDN connection without switching, the policy issued by the PCRF will inevitably be inconsistent with the P-GW decision, resulting in an error.
  • the methods for solving this problem in the prior art are as follows:
  • the gateway control session establishment indication message sent by the BBERF located in the access gateway to the PCRF carries a delay association indication, and after the PCRF receives the delay association indication, Immediately associate the built gateway control session (Gxx session) (ie Gxx session 2 in Figure 3) with the existing PDN connection (IP-CAN session);
  • the PCEF located in the P-GW sends an IP-CAN session modification indication message to the PCRF, and modifies the established Gx session (ie, Gx session 1 in FIG. 3), at this time, the PCRF Associating a newly established gateway control session (Gxx session) (ie Gxx session 2) with an established PDN connection (IP-CAN session) (ie, associating Gxx session 2 with Gx session 1);
  • the P-GW allocates a new IP address (represented as IP Address2) to the UE; PCEF located at the P-GW Sending an IP-CAN session establishment indication message to the PCRF, requesting to establish a new Gx session (represented as Gx session 2), the message carrying the user identifier NAI, the PDN identifier APN, and the IP Address2; at this time, the PCRF decides to control the newly created gateway.
  • the session (Gxx session) is associated with the newly created Gx session (ie, Gxx Session 2 is associated with Gx Session 2). under these circumstances, The proprietary service that the UE accesses before accessing through the 3GPP is interrupted, and the UE needs to re-initiate the service request, and the PCRF re-strategizes it.
  • IP-CAN session The above method of not immediately associating a gateway control session with an existing PDN connection (IP-CAN session) is called Defered linking.
  • FIG. 4 is an EPS roaming architecture diagram of the home router in the prior art.
  • the P-GW is in the home network, and the IP service is provided by the home network operator (ie, the AF home network).
  • FIG. 5 is a schematic diagram of an EPS roaming architecture for local grooming in the prior art.
  • the P-GW may provide IP services (ie, AF home network) by the home network operator, or may be visited by the home network operator.
  • the network operator provides IP services (ie, AF is on the visited network).
  • the PCC process is different, and the functions performed by the PCC network element are also different.
  • the Visiting PCRF terminates all G-sessions and gateway control sessions (Gxx sessions) in the visited network.
  • Home PCRF Home PCRF
  • hPCRF home PCRF
  • the vPCRF gateway control session Gxx session
  • IP-CAN sessions IP-CAN sessions
  • S9 subsessions There may be multiple sub-sessions (called S9 subsessions) in an S9 session, each of which is used to transmit information on a Gx, gateway control session (Gxx session) of an IP-CAN session.
  • the technical problem to be solved by the present invention is to overcome the deficiencies of the prior art, and provide a system and method for implementing re-selection of bearer binding and event reporting functions in an EPS roaming scenario, so as to implement a policy charging control session in a roaming scenario. Delay association.
  • the present invention first provides a reselection method for bearer binding and event reporting, and establishes a first IP connection access network IP-CAN session for the user equipment UE in the evolved packet system EPS, and establishes the same.
  • the BBERF reselection process is performed in the bearer binding and event reporting function.
  • the visited local policy and charging rule function PCRF establishes a second sub-session of the S9 session with the home PCRF, and associates the second gateway control session established between the destination BBERF and the visited PCRF with the second sub-session; Receiving the IP-CAN session modification indication message sent by the policy and charging execution function PCEF, the home PCRF requests the IP-CAN session modification indication message according to the session identification information included in the IP-CAN session modification indication message.
  • the modified first Gx session is associated with the second subsession; or
  • the home PCRF requests the second establishment of the IP-CAN session establishment indication message according to the session identification information included in the IP-CAN session establishment indication message.
  • a Gx session is associated with the second subsession.
  • the visited PCRF after receiving the gateway control session establishment indication message sent by the destination BBERF, the visited PCRF establishes the second subsession with the home PCRF according to the delay association indication and the session identification information carried in the message, and controls the gateway.
  • the second gateway control session that the session establishment indication message requests to establish is associated with the second subsession.
  • the visited PCRF establishes the second sub-session by sending an S9 session modification indication message to the home PCRF, where the message carries the delay association indication and the session identification information;
  • the home PCRF After receiving the S9 session modification indication message, the home PCRF sends the default quality of service QoS policy defined for the user to the visited PCRF in the S9 session modification confirmation message according to the delay association indication and the session identification information; After receiving the S9 session modification confirmation message, the visited PCRF sends the default QoS policy to the destination BBERF in the gateway control session establishment confirmation message.
  • the home PCRF sends a policy charging control PCC policy defined by the user to the PCEF through the first Gx session, and passes the The two sub-sessions are sent to the visited PCRF by the user-defined QoS policy, and the QoS policy is sent by the visited PCRF to the destination BBERF through the second gateway control session; or
  • the home PCRF sends the PCC policy defined by the user to the PCEF through the second Gx session, and the user is the user through the second sub-session.
  • the QoS policy is sent to the visited PCRF, and the QoS policy is sent by the visited PCRF to the destination BBERF through the second gateway control session.
  • the session identification information includes a user identifier, a packet data network identifier.
  • the present invention also provides a reselection method for bearer binding and event reporting, establishing a first IP-CAN session for the UE in the EPS, and establishing a first gateway control for policy control of the first IP-CAN session. After the first subsession of the session, the first Gx session, the S9 session, and the S9 session, during the BBERF reselection:
  • a second gateway control session is established between the BBERF and the visited PCRF;
  • the visited PCRF associates the modified first Gx session with the second gateway control session according to the session identification information in the message, and associates with the home
  • the PCRF establishes a second subsession of the S9 session, and obtains, by the second subsession, a policy that the home PCRF is modified for the user; or
  • the visited PCRF associates the second Gx session established by the message request with the second gateway control session according to the session identification information in the message, and associates with the home
  • the PCRF establishes a second sub-session of the S9 session, and the home PCRF is obtained by the second sub-session to newly create a policy for the user.
  • the home PCRF modified or newly formulated policy includes a PCC rule and a QoS rule; after the home PCRF modification or the newly formulated policy is acquired by the second subsession, the visited PCRF passes the first The Gx session delivers the PCC rule in the policy to the PCEF. And sending, by the second gateway control session, the QoS rule in the policy to the destination BBERF.
  • the home PCRF modified or newly formulated policy includes a PCC rule;
  • the visited PCRF After obtaining the home PCRF modification or the newly created PCC rule by using the second sub-session, the visited PCRF sends the PCC rule to the PCEF through the first Gx session, and formulates a corresponding according to the PCC rule.
  • the QoS rule is used to deliver the QoS rule to the destination BBERF through the second gateway control session.
  • the visited PCRF after receiving the IP-CAN session modification indication message, the visited PCRF establishes the second sub-session by sending an S9 session modification indication message carrying an execution indication to the home PCRF, where the execution indication is used to indicate the attribution.
  • the PCRF is a user modification policy; after receiving the S9 session modification indication message, the home PCRF sends the policy modified for the user according to the execution indication to the PCR message in the S9 session modification confirmation message; or
  • the visited PCRF After receiving the IP-CAN session establishment indication message, the visited PCRF establishes the second subsession by sending an S9 session modification indication message carrying an execution indication to the home PCRF, where the execution indication is used to indicate the home PCRF After the S9 session modification indication message is received, the home PCRF sends the default policy defined for the user to the visited PCRF in the S9 session modification confirmation message according to the execution indication.
  • the destination BBERF establishes the second gateway control session by sending a gateway control session establishment indication message to the visited PCRF, where the message carries a delay association indication, an access network bearer attribute, and session identifier information;
  • the visited PCRF After receiving the gateway control session establishment indication message, the visited PCRF searches for a default QoS rule corresponding to the session identification information according to the delay association indication, and performs the default QoS rule according to the access network bearer attribute. After the modification, the gateway control session establishment confirmation message is sent to the destination BBERF.
  • the session identification information includes a user identifier, a packet data network identifier.
  • the present invention provides a reselection system for bearer binding and event reporting functions, including a visited location policy and a charging rule function PCRF, a home PCRF, and a policy and charging execution function PCEF, which are users in the evolved packet system EPS.
  • the device UE establishes a first IP connection access network IP-CAN session, and establishes a first gateway control session for performing policy control on the first IP-CAN session, the first Gx After the first subsession of the session, S9 session and S9 session, during the BBERF reselection of the bearer binding and event reporting functions:
  • the visited PCRF is configured to establish a second sub-session of the S9 session with the home PCRF, establish a second gateway control session with the destination BBERF, and control the second gateway control session with the second sub-session Session association;
  • the PCEF is configured to send an IP-CAN session modification indication message or an IP-CAN session establishment indication message to the home PCRF;
  • the home PCRF is configured to perform, according to the session identifier information included in the IP-CAN session modification indication message, the first Gx session requested to be modified by the IP-CAN session modification indication message, and the second subsession Correlating; associating the second Gx session that is requested by the IP-CAN session establishment indication message with the second sub-session according to the session identification information included in the IP-CAN session establishment indication message.
  • Another reselection system for carrying binding and event reporting functions including a visited policy and a charging rule function PCRF, a home PCRF, and a policy and charging execution function PCEF, in the evolved packet system EPS
  • the user equipment UE establishes a first IP connection access network IP-CAN session, and establishes a first gateway control session, a first Gx session, an S9 session, and a first S9 session for policy control of the first IP-CAN session.
  • the PCEF is configured to send an IP-CAN session modification indication message or an IP-CAN session establishment indication message to the visited PCRF;
  • the visited PCRF is set to establish a second gateway control session with the destination BBERF; the first request for modification of the IP-CAN session modification indication message according to the session identification information in the IP-CAN session modification indication message
  • the Gx session is associated with the second gateway control session, and establishes a second subsession of the S9 session with the home PCRF, and obtains, by the second subsession, the policy that the home PCRF is modified by the user;
  • - the session identification information in the CAN session establishment indication message associates the second Gx session requested by the IP-CAN session establishment indication message with the second gateway control session, and establishes an S9 session with the home PCRF a second sub-session, obtaining, by the second sub-session, the home PCRF as a newly-defined policy of the user;
  • the home PCRF is configured to newly formulate the policy for the user, and establish a second subsession of the S9 session with the visited PCRF.
  • the present invention establishes a sub-session of a new S9 session between the visited PCRF and the home PCRF in the process of BBERF reselection, and controls the session with the destination BBERF and the visited PCRF.
  • the Gxx session is associated with the corresponding Gx session, and the delayed association of the policy charging control session is implemented in the home routing and local grooming roaming scenarios.
  • FIG. 1 is a schematic diagram of a system architecture of an EPS in a related art
  • FIG. 2 is a schematic diagram of an initial attach process of a UE accessing an EPS through an E-UTRAN and establishing a PDN connection;
  • FIG. 3 is a schematic diagram of a process for a UE to switch from an E-UTRAN to a trusted non-3GPP access system after accessing the EPS by using the process shown in FIG. 2;
  • FIG. 5 is a schematic diagram of an EPS roaming architecture for local grooming in the prior art
  • FIG. 6 is a schematic flowchart of performing initial attaching by E-UTRAN in a roaming scenario of a home-routed route of the UE according to the first embodiment of the present invention
  • FIG. 7a is a schematic diagram of a process for a UE with network mobility capability to switch from E-UTRAN access to trusted non-3GPP access after accessing the EPS by using the process shown in FIG. 6 according to the first embodiment of the present invention
  • FIG. 7b is a schematic diagram of a process for a UE that does not have network mobility capability to switch from E-UTRAN access to trusted non-3GPP access after accessing the EPS by using the process shown in FIG. 6 according to the first embodiment of the present invention
  • FIG. 8 is a schematic flowchart of performing initial attaching by E-UTRAN in a localized roaming scenario of a UE according to a second embodiment of the present invention
  • FIG. 9a is a schematic diagram of a process for a UE with network mobility capability to switch from E-UTRAN access to trusted non-3GPP access after accessing the EPS by using the process shown in FIG. 8 according to the second embodiment of the present invention.
  • FIG. 9b is a schematic diagram of a process for a UE that does not have network mobility capability to switch from E-UTRAN access to trusted non-3GPP access after accessing the EPS by using the process shown in FIG. 8 according to the second embodiment of the present invention.
  • the core idea of the present invention is that, in the process of BBERF reselection, a new S9 session subsession is established between the visited PCRF and the home PCRF, and the gateway control session (Gxx session) established by the destination BBERF and the visited PCRF is The sub-session is associated, and the Gx session requested by the IP-CAN session establishment indication message sent by the PCEF or the Gx session of the IP-CAN session modification indication message is modified according to the session identification information (including the user identifier, the PDN identifier, etc.) This newly created S9 session subsession.
  • FIG. 6 is a schematic flowchart of performing initial attach by E-UTRAN in a roaming scenario in which a UE is in a home-routed manner according to the first embodiment of the present invention; wherein the PM-IPv6 protocol is used between the S-GW and the P-GW.
  • the process shown in Figure 6 mainly includes the following steps:
  • Step S601 The UE sends an attach request message to the eNodeB to request access to the EPS.
  • Step S602 The eNodeB sends an attach request message to the MME.
  • Step S603 The network authenticates the UE and starts NAS security encryption protection.
  • Step S604 After the authentication is passed, the MME interacts with the HSS to perform a location update procedure.
  • Default bearer request message
  • Step S606 The BBERF located in the S-GW sends a gateway control session establishment indication message to the vPCRF, where the message carries the user identifier NAI, the PDN identifier APN, and the bearer attributes of the current access network (including the IP-CAN type, the RAT type, and the BBERF). Address), etc.; the message requests the establishment of a gateway control session (Gxx session), denoted as Gxx session 1;
  • Step S607 The vPCRF determines that the corresponding user is a roaming user according to the NAI, and has not established an S9 session for the user. Therefore, the vPCRF sends an S9 session establishment indication message to the hPCRF, requesting to establish a subsession Subsession1 of the S9 session, and the vPCRF maintains the Gxx session 1.
  • the association relationship with Subsession1, and the bearer attributes of the NAI, the APN, and the current access network are included in the Subsession1 and sent to the hPCRF;
  • Step S608 The hPCRF obtains the subscription information of the user according to the NAI and the APN, and formulates a policy according to the subscription information of the user, the network policy, and the bearer attribute of the current access network.
  • the policy formulated by the hPCRF is a default policy for the user to access the APN. , including PCC rules, QoS rules, and event triggers;
  • the hPCRF returns an S9 session establishment confirmation message to the vPCRF, and the QoS rule and the event trigger are included in the Subsession1 and sent to the vPCRF;
  • Step S609 The vPCRF returns a gateway control session establishment confirmation message of the Gxx session 1 to the BBERF, and sends the QoS rule and the event trigger in the Subsession1 to the BBERF; the BBERF installs and executes the QoS rule and the event trigger;
  • Step S610 The S-GW sends a proxy binding to the P-GW selected by the MME in step S605. a new message, the message carrying the user identity NAI, the PDN identity APN, and the access network bearer attributes (including the IP-CAN type, or the IP-CAN type and the RAT type);
  • Step S611 The P-GW allocates an IP address for the PDN connection (ie, IP-CAN session) that the P-GW requests to establish, which is represented as IP Address 1.
  • IP-CAN session an IP address for the PDN connection (ie, IP-CAN session) that the P-GW requests to establish
  • IP Address 1 IP Address 1
  • the P-GW is located in the home network, located in the P-
  • the PCEF of the GW sends an IP-CAN session establishment indication message to the hPCRF, where the message carries the user identifier NAI, the PDN identifier APN, the IP Address 1, and the access network bearer attribute, etc.; the Gx session requested by the message is represented as Gx session 1;
  • Step S612 The hPCRF associates the Gx session 1 with the Subsession1 in the S9 session according to the NAI and the APN;
  • Step S613 The hPCRF returns an IP-CAN session establishment confirmation message of the Gx session 1 to the PCEF, and sends the PCC rule and the event trigger specified in step S608 to the PCEF; the PCEF installs and executes the PCC rule and the event trigger;
  • the hPCRF may modify the PCC rule and the QoS rule according to the access network bearer attribute reported in step S611. At this time, the hPCRF sends the modified PCC rule and the QoS rule to the PCEF and the BBERF for update;
  • Step S614 The P-GW returns a proxy binding acknowledgement message to the S-GW, where the message carries IP Address 1;
  • Step S615 The S-GW returns a default bearer response message to the MME, where the message carries IP Address 1;
  • Step S616 The MME returns an attach accept message to the eNodeB, where the message carries the IP
  • Step S617 The eNodeB returns an attach accept message to the UE, where the message carries IP Address1; Step S618: The UE sends an attach complete message to the eNodeB;
  • Step S619 The eNodeB sends an attach complete message to the MME.
  • Step S620 The MME and the S-GW perform an interaction process of updating the bearer.
  • Step S621 The MME learns that the UE can access the non-3GPP according to the user subscription information, and therefore sends the address of the P-GW selected by the UE to establish the PDN connection to the HSS, and the HSS returns the response message after saving the P-GW address.
  • FIG. 7a is a schematic diagram of a flow of a UE switching from an E-UTRAN access to a trusted non-3GPP access after accessing the EPS by using the process shown in FIG. 6 according to the first embodiment of the present invention;
  • the PMIPv6 protocol is used between the trusted non-3GPP access gateway and the P-GW.
  • the UE has network mobility capability (ie, IP address retention capability).
  • the process shown in Figure 7a mainly includes the following steps:
  • Step S701 The UE establishes a PDN connection through the 3GPP access, and a PMIPv6 tunnel exists between the S-GW and the P-GW.
  • Step S702 The UE finds a trusted non-3GPP access system and decides to switch the current session from the 3GPP access to the trusted non-3GPP access system.
  • Step S703 The UE, the trusted non-3GPP access gateway, and the HSS/AAA perform an EAP authentication process. In the authentication process, the HSS/AAA returns the address of the P-GW selected by the UE during 3GPP access to the trusted non-3GPP. Access gateway
  • Step S704 After the authentication and authorization succeeds, the non-3GPP access specific layer 3 attach procedure is triggered.
  • Step S705 Since the trusted non-3GPP access gateway is uncertain whether the UE has network mobility capability (ie, IP address retention capability), The BBERF located in the trusted non-3GPP access gateway sends a gateway control session establishment indication message to the vPCRF, where the message carries the user identifier NAI, the PDN identifier APN, and the new access network bearer attribute (including the IP-CAN type, or IP- CAN type and RAT type) and delay association indication; the message requests the established gateway control session (Gxx session), denoted as Gxx session 2;
  • Step S706 Since the gateway control session establishment indication message carries the delay association indication, the vPCRF does not associate the Gxx session 2 with the Subsession1 established in the process of FIG. 6 according to the NAI and the APN; the vPCRF determines to create a new S9 session subsession, and therefore the vPCRF is sent to the hPCRF. Sending an S9 session modification indication message, requesting to establish a new sub-session Subsession2, the vPCRF maintains the association relationship between Gxx2 and Subsession2, and includes the new access network bearer attribute, NAI and APN in Subsession2 and sends it to the hPCRF, which also carries Delay association indication;
  • Step S707 The hPCRF does not associate the Subsession2 with the Gx session 1 established in the process of FIG. 6 because the S9 session modification indication message carries the delay association indication; the hPCRF is contracted according to the user.
  • the information, the network policy, the new access network bearer attribute, etc. are used by the UE to formulate QoS rules and event triggers through non-3GPP access. These rules are the default policies of the user, and do not include the policy for the user to access the proprietary service before; hPCRF will use the above QoS.
  • the rule, the event trigger is sent to the vPCRF through the S9 session modification confirmation message in Subsession2;
  • Step S708 The vPCRF sends the foregoing QoS rule and event trigger to the BBERF in the trusted non-3GPP access gateway through the gateway control session establishment confirmation message of the Gxx session 2; the BBERF installs and executes the QoS rule and the event trigger; the trusted non The 3GPP access gateway performs a specific non-3GPP access procedure for resource reservation;
  • Step S709 The trusted non-3GPP access gateway sends a proxy binding update message to the corresponding P-GW according to the P-GW address obtained in step S703, where the message carries the user identifier NAI, the PDN identifier APN, and the current access network.
  • Bearer attributes including IP-CAN type, or IP-CAN type and RAT type);
  • Step S710 If the P-GW determines that the UE has the network mobility capability (ie, the IP address retention capability), the handover process of the UE is performed:
  • the P-GW allocates the IP address (IP) used by the PGPP to the UE through 3GPP access according to the NAI and the APN.
  • IP IP address
  • the PCEF located in the P-GW sends an IP-CAN session modification indication message to the hPCRF, where the message carries a new access network bearer attribute (including IP-CAN type, or IP-CAN type and RAT type), and can also carry the user identifier.
  • the NAI and the PDN identify the APN, etc.; the message modifies the Gx session 1 established in FIG. 6;
  • Step S711 The hPCRF determines that the UE can perform the handover procedure according to the IP-CAN session modification indication message sent by the PCEF. Therefore, the Gx session 1 and the Subsession2 are associated according to the NAI and the APN. Meanwhile, the hPCRF can continue to maintain the association relationship between the Gx session 1 and the Subsession1.
  • the hPCRF returns the modified PCC rule and the event trigger to the PCEF for updating by the IP-CAN session modification confirmation message of the Gx session 1;
  • the P-GW returns the proxy binding to the trusted non-3GPP access gateway. Confirmation message, The message carries IP Address 1;
  • Step S714 The trusted non-3GPP access gateway returns a layer 3 attach complete message to the UE, where the message carries IP Address1;
  • Step S715 The hPCRF sends the QoS rule and event trigger defined in step S712 to the S9 session and the rule providing message of the Subsession2 and sends the message to the vPCRF.
  • Step S716 The vPCRF sends the QoS rule and the event trigger to the BBERF in the trusted non-3GPP access gateway through the gateway control and QoS rule providing message of the Gxx session 2;
  • Step S717 After the BBERF installs the QoS rule and the event trigger, the gateway control and the QoS rule are provided to provide an acknowledgement message; the trusted non-3GPP access gateway performs a specific non-3GPP access procedure to perform resource reservation;
  • Step S718 The vPCRF returns an S9 session and rule providing confirmation message to the hPCRF.
  • the P-GW determines that the UE does not have the network mobility capability, the P-GW will establish a new PDN connection (ie, an IP-CAN session) for the UE, and the specific execution steps are as shown in FIG. 7b:
  • Steps S701, ⁇ S709, are the same as steps S701 to S709, respectively;
  • Step S710' If the P-GW determines that the UE does not have network mobility capability (ie, does not have IP address retention capability), the P-GW decides to establish a new PDN connection:
  • the P-GW allocates a new IP address to the UE (referred to as IP Address2);
  • the PCEF located at the P-GW sends an IP-CAN session establishment indication message to the hPCRF, which carries the user identity NALPDN identifier APN, IP Address2, and new access network bearer attributes (including IP-CAN type, or IP-CAN type and RAT type); the message requests to establish a new Gx session, denoted as Gx session 2; Step S711, the hPCRF determines that the UE cannot perform the handover procedure according to the IP-CAN session establishment indication message sent by the PCEF, but creates a new PDN connection in the trusted non-3GPP access gateway, so the Subsession2 and the Gx session are performed according to the NAI and the APN. Make an association;
  • Step S712' The hPCRF formulates a default policy (including PCC rules, QoS rules, and event triggers) for the newly established PDN connection (ie, IP-CAN session) according to the new access network bearer characteristics, network policy, user subscription information, and the like. And returning the PCC rules and event triggers to the PCEF through the IP-CAN session establishment confirmation message of the Gx session 2, and the PCEF installs and executes the PCC rules and event triggers;
  • a default policy including PCC rules, QoS rules, and event triggers
  • Step S713' The P-GW returns a proxy binding acknowledgement message to the trusted non-3GPP access gateway, where the message carries IP Address2;
  • Step S714 The trusted non-3GPP access gateway returns a layer 3 attach complete message to the UE, where the message carries IP Address2;
  • Step S715' If the QoS rule and event trigger formulated in step S712' are different from the QoS rule and event trigger formulated in step S707', the hPCRF includes the QoS rule and event trigger formulated in step 712' in the S9 session of Subsession2. And sending a message to the vPCRF in the rule providing message; Step S716': the vPCRF sends the QoS rule and the event trigger to the BBERF in the trusted non-3GPP access gateway through the gateway control and QoS rule providing message of the Gxx session 2;
  • Step S717' The BBERF installation performs QoS rules and event triggers, and returns a gateway control and QoS rule providing confirmation message to the vPCRF; the trusted non-3GPP access gateway performs a specific non-3GPP access procedure for resource reservation;
  • Step S718, The vPCRF returns an S9 session and rule provision confirmation message to the hPCRF;
  • Step S719' The UE newly establishes a PDN connection (ie, an IP-CAN session) through the trusted non-3GPP access network, in the trusted non-3GPP access.
  • a PMIPv6 tunnel between the gateway and the P-GW (the PMIPv6 tunnel is established through steps S709' and S713'); the UE accesses the service accessed through the 3GPP access cannot continue to access, and the UE needs to re-initiate the service access request.
  • the reselection system that carries the binding and event reporting functions in this embodiment mainly includes a visited location policy and a charging rule function PCRF, a home PCRF, and a policy and charging execution function PCEF, which are user equipments in the evolved packet system EPS.
  • the UE establishes a first IP connection access network IP-CAN session, And establishing a first gateway control session, a first Gx session, an S9 session, and a first subsession of the S9 session for policy control of the first IP-CAN session, and the BBERF reselection in the bearer binding and event reporting function
  • a visited location policy and a charging rule function PCRF a home PCRF
  • PCEF policy and charging execution function
  • the visited PCRF is set to establish a second sub-session of the S9 session with the home PCRF, establish a second gateway control session with the destination BBERF, and associate the second gateway control session with the second sub-session;
  • the PCEF is configured to send an IP-CAN session modification indication message or an IP-CAN session establishment indication message to the home PCRF;
  • the home PCRF is configured to associate the first Gx session requested by the IP-CAN session modification indication message with the second sub-session according to the session identification information included in the IP-CAN session modification indication message; according to the IP-CAN session establishment indication
  • the session identification information included in the message associates the second Gx session established by the IP-CAN session establishment indication message with the second subsession.
  • This embodiment is equally applicable to a UE switching from one trusted non-3GPP access network to another trusted non-3GPP access network. Wherein, when two non-3GPP accesses are used, the PMIPv6 protocol is used between the trusted non-3GPP access gateway and the P-GW.
  • FIG. 8 is a schematic flowchart of performing initial attach by E-UTRAN in a localized roaming scenario of a UE according to a second embodiment of the present invention; wherein a PMIPv6 protocol is used between the S-GW and the P-GW.
  • the process shown in Figure 8 mainly includes the following steps:
  • Step S801 The UE sends an attach request message to the eNodeB to request access to the EPS.
  • Step S802 The eNodeB sends an attach request message to the MME.
  • Step S803 The network authenticates the UE and starts NAS security encryption protection.
  • Step S804 After the authentication is passed, the MME interacts with the HSS to perform a location update process.
  • the MME sends a default bearer request message to the selected S-GW;
  • Step S806 The BBERF located in the S-GW sends a gateway control session establishment finger to the vPCRF.
  • the message carries the user identifier NAI, the PDN identifier APN, and the bearer attributes of the current access network (including the IP-CAN type, the RAT type, and the BBERF address), etc.; the message requests the established gateway control session (Gxx session), Expressed as Gxx session 1;
  • Step S807 The vPCRF determines that the corresponding user is a roaming user according to the NAI, and has not established an S9 session for the user. Therefore, the vPCRF sends an S9 session establishment indication message to the hPCRF, requesting to establish a sub-session Subsession1 of the S9 session, and the vPCRF maintains the Gxx session 1.
  • the association relationship with Subsession1, and the bearer attributes of the NAI, the APN, and the current access network are included in the Subsession1 and sent to the hPCRF;
  • Step S808 The hPCRF obtains the subscription information of the user according to the NAI and the APN, and then formulates a policy according to the subscription information of the user, the network policy, and the bearer attribute of the current access network.
  • the policy formulated by the hPCRF is a default policy for the user to access the APN. , including PCC rules, QoS rules, and event triggers;
  • the hPCRF returns an S9 session establishment confirmation message to the vPCRF, and the QoS rule and the event trigger are included in the Subsession1 and sent to the vPCRF;
  • Step S809 The vPCRF returns a gateway control session establishment confirmation message of the Gxx session 1 to the BBERF, and sends the QoS rule and the event trigger in the Subsession1 to the BBERF; the BBERF installs and executes the QoS rule and the event trigger;
  • Step S810 The S-GW sends a proxy binding update message to the P-GW selected by the MME in step S805, where the message carries the user identifier NAI, the PDN identifier APN, and the access network bearer attribute (including the IP-CAN type, or IP). -CAN type and RAT type);
  • Step S811 The P-GW allocates an IP address to the PDN connection that the UE requests to establish, and indicates that it is an IP address.
  • the PCEF located in the P-GW sends an IP-CAN session establishment indication message to the vPCRF, where the message carries the user identifier NAI.
  • the PDN identifies the APN, the IP Address 1, and the access network bearer attributes (including the IP-CAN type, or the IP-CAN type, and the RAT type), and the like; the Gx session requested by the message is represented as Gx session 1;
  • Step S812 The vPCRF associates the Gx session 1 with the Gxx session 1 and the Subsesion1 in the S9 session according to the NAI and the APN;
  • Step S813 The vPCRF sends an S9 session modification indication message to the hPCRF, and the IP Address1 is Included in Subsession1 sent to hPCRF;
  • Step S814 The hPCRF returns an S9 session modification confirmation message to the vPCRF, and the PCC rules and event triggers specified in step S808 are included in the Subsession1 and sent to the vPCRF;
  • the hPCRF may modify the PCC rules, QoS rules, and event triggers. At this time, the hPCRF sends the modified PCC rules and QoS rules to the PCEF and the BBERF for updating respectively.
  • Step S816 The P-GW returns a proxy binding acknowledgement message to the S-GW, where the message carries IP Address 1;
  • Step S817 The S-GW returns a default bearer response message to the MME, where the message carries IP Address 1;
  • Step S818 The MME returns an attach accept message to the eNodeB, where the message carries IP Address 1;
  • Step S819 The eNodeB returns an attach accept message to the UE, where the message carries IP Address1; Step S820: The UE sends an attach complete message to the eNodeB;
  • Step S821 The eNodeB sends an attach complete message to the MME.
  • Step S822 The MME and the S-GW perform an interaction process of updating the bearer.
  • Step S823 The MME learns that the UE can access the non-3GPP according to the user subscription information, and therefore sends the address of the P-GW selected by the UE to establish the PDN connection to the HSS, and the HSS returns the response message after saving the P-GW address.
  • FIG. 9 is a schematic diagram of a flow of a UE switching from an E-UTRAN access to a trusted non-3GPP access after accessing the EPS by using the process shown in FIG. 8 according to the second embodiment of the present invention; wherein, when the non-3GPP access is used, The PMIPv6 protocol is used between the trusted non-3GPP access gateway and the P-GW.
  • the UE has network mobility capability (ie, IP address retention capability).
  • the process shown in Figure 9a mainly includes the following steps: Step S901: The UE establishes a PDN connection through the 3GPP access, and a PMIPv6 tunnel exists between the S-GW and the P-GW.
  • Step S902 The UE finds a trusted non-3GPP access system and decides to switch the current session from the 3GPP access to the trusted non-3GPP access system.
  • Step S903 The UE, the trusted non-3GPP access gateway, and the HSS/AAA perform an EAP authentication process. In the authentication process, the HSS/AAA returns the address of the P-GW selected by the UE during 3GPP access to the trusted non-3GPP. Access gateway
  • Step S904 After the authentication authorization is successful, the non-3GPP access specific layer 3 attach procedure is triggered.
  • Step S906 The vPCRF does not associate the Gxx session 2 with the sub-session of any S9 session according to the NAI and the APN because the gateway control session establishment indication message carries the delay association indication.
  • the vPCRF searches according to the NAI and the APN because the roaming mode of the UE is local grooming.
  • the default QoS rules and event triggers sent by the hPCRF in Figure 8 and the corresponding default QoS rules and event triggers sent by the hPCRF in Figure 8 are modified according to the new access network bearer attributes, and will be modified.
  • the QoS rules and event triggers are sent to the BBERF in the trusted non-3GPP access gateway in the gateway control session establishment confirmation message of the Gxx session 2; the BBERF installs and executes the QoS rules and event triggers; the trusted non-3GPP interface
  • the ingress gateway performs a specific non-3GPP access procedure for resource reservation; Step S907: The trusted non-3GPP access gateway sends a proxy binding update message to the corresponding P-GW according to the P-GW address obtained in step S903, the message Carrying the user identity NAI, the PDN identity APN, and the current access network bearer attributes (including IP-CAN type, or IP-CAN type, and RAT class) );
  • Step S908 If the P-GW determines that the UE has the network mobility capability (ie, the IP address retention capability), the P-GW performs the handover process of the UE: The P-GW allocates an IP address (IP Addressl) used by the 3GPP to the UE according to the NAI and the APN to keep the IP address unchanged, thereby ensuring continuity of the service;
  • IP Addressl IP Addressl
  • the PCEF located at the P-GW sends an IP-CAN session modification indication message to the vPCRF, where the message carries the current access network bearer attributes (including IP-CAN type, or IP-CAN type and RAT type); the message is modified.
  • Figure 8 establishes Gx session 1;
  • Step S909 The vPCRF determines, according to the received IP-CAN session modification indication message, that the UE can perform the handover procedure, and therefore associates the Gxx session 2 and the Gx session 1 established in step S905 according to the NAI and the APN;
  • Step S910 The vPCRF sends an S9 session modification indication message to the hPCRF, requesting to establish a new sub-session Subsession2, and including the NAI, the APN, and the new access network bearer attribute in the Subsession2 and sending the information to the hPCRF; the message also carries Performing an indication to notify the hPCRF to perform a handover process of the UE;
  • Step S911 The hPCRF determines, according to the execution indication, that the UE can perform the handover procedure, and therefore modifies the PCC rules, QoS rules, and event triggers of the PDN connection established before the UE handover according to the new access network bearer attribute, where the user includes the 3GPP.
  • the policy of accessing the proprietary service during access the hPCRF includes the modified PCC rule, the QoS rule, and the event trigger in the Subsession2, and sends the confirmation message to the vPCRF through the S9 session modification confirmation message;
  • Step S912 The vPCRF sends the PCC rule and the event trigger to the PCEF through the IP-CAN session modification confirmation message of the Gx session 1, and the PCEF updates the PCC rule and the event trigger.
  • Step S913 The P-GW returns a proxy binding acknowledgement message to the trusted non-3GPP access gateway, where the message carries an IP Address1;
  • Step S914 The trusted non-3GPP access gateway returns a layer 3 attach complete message to the UE, where the message carries IP Address1;
  • Step S915 The vPCRF sends the QoS rule and the event trigger to the BBERF in the trusted non-3GPP access gateway by using the gateway control and QoS rule providing message of the Gxx session 2;
  • Step S916 The BBERF installs and executes the QoS rule and the event trigger, and returns a gateway control and QoS rule providing confirmation message to the vPCRF; the trusted non-3GPP access gateway performs a specific non-3GPP access procedure for resource reservation; Step S917: The UE switches the PDN connection from the 3GPP access to the trusted non-3GPP access, and the PMIPv6 tunnel exists between the trusted non-3GPP access gateway and the P-GW (the PMIPv6 tunnel is established through steps S907 and S913); The proprietary services that the UE accesses when accessing through 3GPP can continue to access.
  • the hPCRF only formulates/modifies PCC rules without making/modifying
  • the corresponding QoS rules are formulated by the vPCRF based on the PCC rules issued by the hPCRF and sent to the corresponding BBERF.
  • the hPCRF formulates a PCC rule for the PDN connection established by the UE through the trusted non-3GPP access, and sends the PCC rule to the vPCRF.
  • the vPCRF formulates the QoS rule according to the PCC rule, and sends the QoS rule to the trusted non-3GPP access. BBERF in the gateway.
  • the P-GW determines that the UE does not have the network mobility capability, the P-GW will establish a new PDN connection (ie, an IP-CAN session) for the UE, and the specific execution steps are as shown in FIG. 9b:
  • Steps S901 ' ⁇ S907' are the same as steps S901 to S907, respectively;
  • Step S908' If the P-GW determines that the UE does not have network mobility capability (ie, does not have IP address retention capability), the P-GW establishes a new PDN connection:
  • the P-GW allocates a new IP address to the UE (referred to as IP Address2);
  • the PCEF located at the P-GW sends an IP-CAN session establishment indication message to the vPCRF, which carries the user identity NAL PDN identifier APN, IP Address2, and new access network bearer attributes (including IP-CAN type, or IP-CAN type). And RAT type); the message requests to establish a new Gx session, denoted as Gx session 2;
  • Step S909 the vPCRF determines, according to the received IP-CAN session establishment indication message, that the UE cannot perform the handover procedure, but creates a new PDN connection in the trusted non-3GPP access gateway, so the Gxx session 2 and the Gx are according to the NAI and the APN. Session 2 is associated;
  • Step S910' The vPCRF sends an S9 session modification indication message to the hPCRF, requesting to establish a new subsession Subsession2, and including the NAI, APN, and the new access network bearer attribute, IP Address2, in the Subsession2, and sending the message to the hPCRF; Carrying an execution instruction, Know that hPCRF performs a new PDN connection (ie IP-CAN session) process;
  • Step S911 the hPCRF determines, according to the execution indication, that the UE initiates establishment of a new PDN connection (ie, an IP-CAN session), so the hPCRF establishes a new PDN connection according to the new access network bearer attribute, network policy, and user subscription information (ie, IP).
  • -CAN session Develop PCC rules, QoS rules, and event triggers. These rules are default rules and do not include the policy for the UE to access proprietary services when accessing through 3GPP; hPCRF includes the above PCC rules, QoS rules, and event triggers.
  • the S9 session modification confirmation message is sent to the vPCRF;
  • Step S912' The vPCRF sends the PCC rule and the event trigger to the PCEF through the IP-CAN session establishment confirmation message of the Gx session 2, and the PCEF installs and executes the PCC rule and the event trigger;
  • Step S913' P-GW to the trusted non The 3GPP access gateway returns a proxy binding acknowledgement message, where the message carries an IP Address2;
  • Step S914' the trusted non-3GPP access gateway returns a layer 3 attach complete message to the UE, where the message carries IP Address2;
  • Step S915' The vPCRF sends the QoS rule and the event trigger to the BBERF in the trusted non-3GPP access gateway through the gateway control and QoS rule providing message of the Gxx session 2;
  • Step S916' The BBERF installation performs QoS rules and event triggers, and returns a gateway control and QoS rule providing confirmation message to the vPCRF; the trusted non-3GPP access gateway performs a specific non-3GPP access procedure for resource reservation;
  • Step S917' The UE newly establishes a PDN connection (ie, an IP-CAN session) through the trusted non-3GPP access network, and a PMIPv6 tunnel exists between the trusted non-3GPP access gateway and the P-GW (the PMIPv6 tunnel passes the step S907' and S913' are established); the service accessed by the UE when accessing through the 3GPP cannot continue to access, and the UE needs to re-initiate the service access request.
  • a PDN connection ie, an IP-CAN session
  • P-GW the PMIPv6 tunnel passes the step S907' and S913' are established
  • This embodiment is equally applicable to a UE switching from one trusted non-3GPP access network to another trusted non-3GPP access network. Wherein, when two non-3GPP accesses are used, the PMIPv6 protocol is used between the trusted non-3GPP access gateway and the P-GW.
  • the hPCRF only formulates PCC rules without formulating QoS rules. Then, send it to the corresponding BBERF.
  • hPCRF is for UEs through trusted non-3GPP A PDN connection (ie, an IP-CAN session) is established to establish a PCC rule, and the PCC rule is sent to the vPCRF.
  • the vPCRF formulates a QoS rule according to the PCC rule, and delivers the QoS rule to the trusted non-3GPP access gateway. BBERF.
  • the reselection system that carries the binding and event reporting functions in this embodiment mainly includes a visited location policy and a charging rule function PCRF, a home PCRF, and a policy and charging execution function PCEF, which are user equipments in the evolved packet system EPS.
  • the UE establishes a first IP connection access network IP-CAN session, and establishes a first gateway control session, a first Gx session, an S9 session, and a first subsession of the S9 session for policy control of the first IP-CAN session.
  • the PCEF is configured to send an IP-CAN session modification indication message or an IP-CAN session establishment indication message to the visited PCRF;
  • the visited PCRF is set to establish a second gateway control session with the destination BBERF; and the first Gx session and the second gateway requested to be modified by the IP-CAN session modification indication message according to the session identification information in the IP-CAN session modification indication message Controlling the session to be associated, and establishing a second subsession of the S9 session with the home PCRF, obtaining a policy modified by the home PCRF for the user through the second subsession; and setting the IP address according to the session identification information in the IP-CAN session establishment indication message
  • the second Gx session that the CAN session establishment indication message requests to establish is associated with the second gateway control session, and establishes a second subsession of the S9 session with the home PCRF, and acquires a home PCRF for the user by the second subsession. ;
  • the home PCRF is set to newly create a policy for the user and establish a second subsession of the S9 session with the visited PCRF.
  • 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, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software. While the embodiments of the present invention have been described above, the described embodiments are merely for the purpose of understanding the invention and are not intended to limit the invention. Any modification and variation of the form and details of the invention may be made by those skilled in the art without departing from the spirit and scope of the invention. It is still subject to the scope defined by the appended claims.

Landscapes

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

Description

一种承载绑定和事件报告功能的重选系统及方法
技术领域
本发明涉及通信领域， 尤其涉及一种承载绑定和事件报告功能的重选系 统及方法。
背景技术
3GPP ( 3rd Generation Partnership Project, 第三代合作伙伴计划） 的 EPS ( Evolved Packet System, 演进的分组系统） 由 E-UTRAN ( Evolved Universal Terrestrial Radio Access Network , 演进的通用地面无线接入网） 、 MME ( Mobility Management Entity, 移动管理单元） 、 S-GW ( Serving Gateway, 服务网关） 、 P-GW ( Packet Data Network Gateway, 分组数据网络网关） 、 HSS ( Home Subscriber Server, 归属用户服务器）、 3GPP AAA服务器（ 3GPP 认证授权计费服务器） 、 PCRF ( Policy and Charging Rules Function, 策略和 计费规则功能）及其他支撑节点组成。
图 1为相关技术中的 EPS的系统架构示意图。 如图 1所示， 该架构示意 中， MME负责移动性管理、非接入层信令的处理和用户移动管理上下文的管 理等控制面的相关工作； S-GW是与 E-UTRAN相连的接入网关设备，用于在 E-UTRAN和 P-GW之间转发数据，并且负责对寻呼等待数据进行緩存； P-GW 则是 EPS与分组数据网络（Packet Data Network, 简称为 PDN )的边界网关， 负责 PDN的接入以及在 EPS与 PDN间转发数据等功能。
EPS支持与非 3GPP网络的互通， 其通过 S2a/b/c接口实现与非 3GPP网 络的互通。 非 3GPP网络包括可信任非 3GPP网络和不可信任非 3GPP网络。 可信任非 3GPP网络的 IP ( Internet Protocol, 网络协议 )接入可直接通过 S2a 接口与 P-GW相连；不可信任非 3GPP网络的 IP接入需要经过 ePDG( Evolved Packet Data Gateway, 演进的分组数据网关）与 P-GW相连， ePDG与 P-GW 间通过 S2b接口相连。
若 EPS系统支持 PCC ( Policy and Charging Control, 策略计费控制） ， 则由 PCRF进行策略和计费规则的制定。 PCRF通过接收接口 Rx和运营商的 IP业务网络相连， 获取业务信息。 此外， PCRF通过 Gx/Gxa/Gxc接口与网络 中的网关设备相连， 负责发起 IP承载的建立， 保证业务数据的 QoS ( Quality of Service, 服务质量） ， 并进行计费控制。 其中， PCEF ( Policy and Charging Enforcement Function, 策略和计费执行功能）位于 P-GW中， PCRF与 P-GW 间通过 Gx接口交换信息。当 P-GW与 S-GW间的接口基于 PMIP( Proxy Mobile IP, 代理移动 IP )时， S-GW中存在 BBERF ( Bearer Binding and Event Report Function, 承载绑定和事件报告功能） ， 并且 S-GW与 PCRF之间通过 Gxc 接口交换信息。 当通过可信任非 3GPP网络接入时，可信任非 3GPP接入网关 中也驻留 BBERF , 可信任非 3GPP网络的接入网关与 PCRF之间通过 Gxa接 口交换信息。 UE ( User Equipment, 用户设备 )漫游时， 归属地 PCRF和拜访 地 PCRF的接口为 S9接口，同时，为 UE提供业务的 AF( Application Function, 应用功能）位于业务网络中， 通过 Rx接口向 PCRF发送用于生成 PCC策略 的业务信息。
在现有技术中， PCC架构中釆用的协议是在 Diameter基础协议（ Diameter
Base Protocol )基础上发展的 Diameter应用协议。 例如， 应用于 Gx接口的应 用协议， 应用于 Rx接口的应用协议、 应用于 Gxx接口 （包括 Gxa和 Gxc接 口）的应用协议和应用于漫游接口 S9的应用协议等。在这些应用协议中定义 了用于 PCC的消息、 命令以及 AVP ( Attribute Value Pairs, 属性值对）等。 用这些协议建立的 Diameter会话可以分别被称为 Gx会话、 Gxx会话、 Rx会 话和 S9会话。 PCC各功能实体通过这些会话对为 UE接入网络而建立的 PDN 连接进行策略计费控制。 通常将 UE到 PDN网络的一个 IP连接称为一个 IP 连接接入网 （ IP Connectivity Access Network, 简称为 IP-CAN )会话。 PCRF 要执行的一个重要操作就是将用于对同一个 IP-CAN会话进行策略控制的 Gx 会话、 网关控制会话（Gxx会话）和 S9会话进行关联。 关联操作在 IP-CAN 会话的建立以及修改的过程中进行。 本文中， 将以上 Diameter会话称为策略 计费控制会话。
图 2为 UE通过 E-UTRAN接入 EPS并建立 PDN连接（即 IP-CAN会话 ) 的初始附着流程示意图； 其中， S-GW与 P-GW之间釆用 PMIPv6协议。 图 2 所示流程主要包括如下步骤：
步骤 S201 : UE向 eNodeB (演进的节点 B, 即基站， 简称为 eNB )发送 附着请求消息， 请求接入 EPS；
步骤 S202： eNodeB向 MME发送附着请求消息；
步骤 S203： 网络对 UE进行认证并启动 NAS ( Non Access stratum, 非接 入层）安全加密保护；
步骤 S204: 对 UE认证通过后， MME与 HSS交互， 执行位置更新流程； 步骤 S205： MME根据用户签约的默认 APN ( Access Point Name , 接入 点名称）为 UE选择 P-GW, 并选择 S-GW, MME向选定的 S-GW发送建立 默认承载请求消息；以下在不出现歧义的情况下用 'ΑΡΝ'表示 '默认 ΑΡΝ' ； 步骤 S206: 位于 S-GW中的 BBERF向 PCRF发送网关控制会话建立指 示消息， 该消息中携带用户标识 NAI ( Network Access Identifier , 网络接入标 识符） 、 PDN标识 ΑΡΝ以及当前接入网的承载属性等； 该消息请求建立的 网关控制会话（Gxx会话） ， 表示为 Gxx会话 1 ;
其中， 接入网承载属性包括： IP-CAN类型、 BBERF地址； 此外， 接入 网承载属性还可以包括 RAT ( Radio Access Technology,无线接入技术）类型； 步骤 S207: PCRF根据用户标识 NAI和 PDN标识 APN获取用户的签约 信息， 从而根据用户的签约信息、 网络策略和当前接入网的承载属性（包括
IP-CAN类型、 或 IP-CAN类型和 RAT类型 )制定策略， 这时 PCRF制定的 策略为用户接入该 APN的默认策略， 包括 PCC规则、 QoS规则和事件触发 哭口.？
PCRF向 BBERF返回网关控制会话建立确认消息，将制定的 QoS规则和 事件触发器发送给 BBERF; BBERF安装并执行 QoS规则和事件触发器； 步骤 S208: S-GW向步骤 S205中 MME所选择的 P-GW发送代理绑定更 新消息， 该消息中携带用户标识 NAI、 PDN标识 APN和接入网承载属性（包 括 IP-CAN类型、 或 IP-CAN类型和 RAT类型） ；
步骤 S209: P-GW为 UE接入而请求建立的 PDN连接分配 IP地址， 表 示为 IP Address 1 ; 位于 P-GW的 PCEF向 PCRF发送 IP-CAN会话建立指示消息，该消息中 携带用户标识 NAI、 PDN标识 APN、 IP Address 1和接入网承载属性（包括 IP-CAN类型、 或 IP-CAN类型和 RAT类型 )等； 该消息中的接入网承载属 性为步骤 S208中获得； 该消息请求建立的 Gx会话表示为 Gx会话 1 ;
步骤 S210： PCRF根据 NAI和 APN将 Gxx会话 1和 Gx会话 1进行关联， 即 Gxx会话 1和 Gx会话 1用于对 UE请求建立的 PDN连接 (即 IP-CAN会 话）进行策略计费控制；
步骤 S211 : PCRF向 PCEF返回 IP-CAN会话建立确认消息，将步骤 S207 中制定的 PCC规则和事件触发器发送给 PCEF; PCEF安装并执行 PCC规则 和事件触发器；
PCRF可能会根据步骤 S209中上报的接入网承载属性修改 PCC规则和 QoS规则，此时 PCRF会将修改的 PCC规则和 QoS规则分别发送给 PCEF和 BBERF进行更新；
步骤 S212: P-GW向 S-GW返回代理绑定确认消息， 该消息中携带 IP Address 1 ;
步骤 S213: S-GW向 MME返回建立默认承载应答消息， 该消息中携带 IP Address 1 ;
步骤 S214 : MME 向 eNodeB 返回附着接受消息， 该消息中携带 IP Address 1 ;
步骤 S215: eNodeB向 UE返回附着接受消息，该消息中携带 IP Addressl ; 步骤 S216: UE向 eNodeB发送附着完成消息；
步骤 S217: eNodeB向 MME发送附着完成消息；
步骤 S218： MME与 S-GW进行更新承载的交互流程；
步骤 S219: MME根据用户的签约信息获知 UE可以通过非 3GPP接入， 因此将 UE建立 PDN连接 (即 IP-CAN会话 )所选择的 P-GW的地址发送给 HSS, HSS保存该 P-GW地址后返回应答消息。
通过图 2所示的流程， UE建立了到默认 APN的 PDN连接 (即 IP-CAN 会话）； 此后， UE可以通过该连接访问专有的业务， PCRF将根据业务特性、 用户签约信息、网络策略和接入网承载属性等信息制定 PCC规则和 QoS规则。 由于在步骤 S210中进行了关联，因此 PCRF可以通过 Gx会话 1将 PCC规则 发送给 PCEF而通过 Gxx会话 1将 QoS规则发送给 BBERF。 当 BBERF通过 Gxx会话 1请求新的 QoS规则或修改 QoS规则时， PCRF也会制定相应的 PCC 规则或修改相应的 PCC规则， 并通过 Gx会话 1发送给 PCEF; 反之亦然。
当 UE发生跨系统切换或跨 S-GW的切换（即 BBERF重选 ) 时， PCRF 需要执行新的关联操作。
图 3为 UE釆用图 2所示流程接入 EPS后， 从 E-UTRAN切换到可信任 非 3GPP接入系统的流程示意图；其中，通过非 3GPP接入时，可信任非 3GPP 接入网关与 P-GW之间釆用 PMIPv6协议。 图 3所示流程主要包括如下步骤： 步骤 S301： UE通过 3GPP接入建立 PDN连接 (即 IP-CAN会话 ) , S-GW 和 P-GW之间存在 ΡΜΙΡνό隧道；
步骤 S302: UE发现可信任非 3GPP接入系统并决定将当前的会话从 3GPP 接入切换到该可信任非 3GPP接入系统；
步骤 S303: UE、可信任非 3GPP接入网关和 HSS/AAA执行 EAP( Extensible Authentication Protocol,可扩展认证协议）认证过程；在认证过程中， HSS/AAA 将 UE在 3GPP接入时所选择的 P-GW的地址返回给可信任非 3GPP接入网关； 步骤 S304: 认证授权成功后， 非 3GPP接入特定的层 3附着流程被触发； 在此过程中， UE向网络指示其具有 IP地址保持能力；
步骤 S305:位于可信任非 3GPP接入网关中的 BBERF向 PCRF发送网关 控制会话建立指示消息， 该消息中携带用户标识 NAI、 PDN标识 APN以及 当前的接入网承载属性（包括新的 IP-CAN类型、或新的 IP-CAN类型和新的 RAT类型）等； 该消息请求建立的网关控制会话（Gxx会话）表示为 Gxx会 话 2;
步骤 S306: PCRF根据 NAI和 APN将 Gxx会话 2和图 2所示流程中建 立的 Gx会话 1进行关联；
步骤 S307: PCRF根据用户签约信息、 网络策略、 当前接入网的承载属 性等为 UE通过非 3GPP接入制定 QoS规则和事件触发器，其中包含 UE通过 3GPP接入后访问专有业务时 PCRF为其制定的专有策略；
PCRF将上述 QoS规则和事件触发器通过网关控制会话建立确认消息发 送给 BBERF; BBERF安装并执行 QoS规则和事件触发器； 可信任非 3GPP 接入网关执行特定的非 3GPP接入流程进行资源预留；
步骤 S308:可信任非 3GPP接入网关根据步骤 S303中获得的 P-GW地址 向对应的 P-GW发送代理绑定更新消息， 该消息中携带用户标识 NAI、 PDN 标识 APN和当前的接入网承载属性（包括 IP-CAN类型、 或 IP-CAN类型和 RAT类型） ；
步骤 S309: P-GW根据 NAI和 APN为 UE分配其通过 3GPP接入时使用 的 IP地址（即 IP Address 1 ) 以保持 IP地址不变， 进而保证业务的连续性； 位于 P-GW的 PCEF向 PCRF发送 IP-CAN会话修改指示消息，该消息中 携带步骤 S308中获得的新的接入网承载属性；该消息修改的是图 2所示流程 中建立的 Gx会话 1 ;
步骤 S310： PCRF判定 UE建立的 PDN连接 (即 IP-CAN会话 ) 的隧道 发生了切换（即从 3GPP切换到了非 3GPP ) ， 因此 PCRF根据新的接入网承 载属性为重建的 PDN连接 (即 IP-CAN会话 )修改 PCC规则， 并将修改的 PCC规则通过 IP-CAN会话修改确认消息返回给 PCEF进行更新；
步骤 S311 : P-GW向可信任非 3GPP接入网关返回代理绑定确认消息， 该消息中携带 IP Addressl；
步骤 S312: 可信任非 3GPP接入网关向 UE返回层 3附着完成消息， 该 消息中携带 IP Addressl ;
步骤 S313: UE将 PDN连接从 3GPP接入切换到了从可信任非 3GPP接 入， 在可信任非 3GPP接入网关和 P-GW之间存在 PMIPv6隧道（该 PMIPv6 隧道通过步骤 S308和 S311建立 )； UE在通过 3GPP接入时访问的业务都能 继续访问。
由图 3所示流程可知， 在步骤 S306中， PCRF根据 NAI和 APN将新的 Gxx会话关联到已建立的一个 PDN连接 ( IP-CAN会话 )上， 进而 PCRF可 以将 UE通过 3GPP系统接入时 PCRF为其制定的策略根据新的接入网承载属 性进行更新后，通过这个新的网关控制会话 ( Gxx会话 )下发给新的 BBERF, 从而保证了在 PMIPv6隧道还没有发生切换前（即在步骤 S308之前 ),非 3GPP 接入系统已经为 UE之前访问的业务进行了资源预留， 加快了切换速度， 改 善了用户体验。
然而， 并不是所有的 UE都能执行切换流程 (即保持 IP地址不变 ) 。 当 网络不确定 UE是否具有网络移动性能力（即 IP地址保持能力）时，将由 P-GW 决定是否为 UE分配一个新的 IP地址（即建立一个新的 PDN连接 )或保持 IP地址不变（即切换已建立的 PDN连接）。 然而 P-GW做出这个决定是在收 到可信任非 3GPP接入网关发送的代理绑定更新消息后。 此时， PCRF已经做 出了将新的网关控制会话 ( Gxx会话 ) 关联到已有的 PDN连接上（即 PCRF 已经做出了切换的决定）。 若此时 P-GW决定建立一个的新的 PDN连接而不 进行切换， 那么必然导致 PCRF下发的策略与 P-GW的决定不一致， 导致了 错误的发生。 现有技术中解决这个问题的方法如下：
( 1 ) 当接入网关无法确定 UE是否具有网络移动性能力时， 位于接入网 关中的 BBERF向 PCRF发送的网关控制会话建立指示消息中携带延迟关联指 示， PCRF收到延迟关联指示后， 不立即将所建的网关控制会话（Gxx会话） (即图 3中的 Gxx会话 2 )与已存在的 PDN连接 ( IP-CAN会话 )进行关联；
( 2 )若 P-GW决定进行切换， 则位于 P-GW中的 PCEF向 PCRF发送 IP-CAN会话修改指示消息，修改已建立的 Gx会话（即图 3中的 Gx会话 1 ) , 此时 PCRF将新建立的网关控制会话 ( Gxx会话 ) (即 Gxx会话 2 )与已建 立的 PDN连接 ( IP-CAN会话 )进行关联（即将 Gxx会话 2与 Gx会话 1进 行关联） ；
( 3 )若 P-GW决定不进行切换，而是新建一个 PDN连接（ IP-CAN会话 ), 那么 P-GW为 UE分配一个新的 IP地址（表示为 IP Address2 ) ； 位于 P-GW 的 PCEF向 PCRF发送 IP-CAN会话建立指示消息， 请求建立一个新的 Gx会 话（表示为 Gx会话 2 ) , 该消息中携带用户标识 NAI、 PDN标识 APN和 IP Address2; 此时 PCRF决定将新建的网关控制会话 ( Gxx会话 )与新建的 Gx 会话进行关联（即将 Gxx会话 2与 Gx会话 2进行关联） 。 在这种情况下， UE之前通过 3GPP接入时访问的专有业务会中断， UE需要重新发起业务请 求， PCRF重新为其制定策略。
上述不立即将网关控制会话与已存在的 PDN连接 ( IP-CAN会话 )进行 关联的方法称为延迟关联 ( Defered linking ) 。
现有技术中仅仅讨论了非漫游场景下实现策略计费控制会话延迟关联的 方法。 对于漫游场景， 现有技术还没有涉及。
EPS存在两种漫游架构， 第一种为家乡路由， 第二种为本地疏导。 图 4 是现有技术中家乡路由的 EPS漫游架构图， 如图 4所示， P-GW在家乡网络， 并由家乡网络运营商提供 IP业务（即 AF在家乡网络） 。 图 5是现有技术中 本地疏导的 EPS漫游架构图， 如图 5所示， P-GW在拜访网络， 可以由家乡 网络运营商提供 IP业务（即 AF在家乡网络） ， 也可以由拜访地网络运营商 提供 IP业务（即 AF在拜访网络）。 对于不同的漫游场景， PCC的流程不同， PCC网元执行的功能也不相同。
目前， 实现 S9漫游接口的方案中， 拜访地 PCRF ( Visit PCRF, 简称为 vPCRF )终结 UE建立的所有 IP-CAN会话在拜访地网络存在的 Gx会话、 网 关控制会话 ( Gxx会话 ) , 即不会将网关控制会话 ( Gxx会话 )和 Gx会话发 送给归属地 PCRF ( Home PCRF, 简称为 hPCRF ) , 而是在 vPCRF和 hPCRF 网关控制会话 ( Gxx会话）上的信息， 但不终结所有 IP-CAN会话在拜访地 网络中的 Rx会话， 只是将 Rx会话的消息转发给归属地 PCRF, 将 vPCRF作 为一个代理 （Proxy ) 。 在一个 S9 会话中可能存在多个子会话 （称为 S9 subsession ) , 每一个子会话用来传送一个 IP-CAN会话的 Gx、 网关控制会话 ( Gxx会话）上的信息。
综上所述， 由于 EPS漫游场景的复杂性， 以及在漫游场景下策略计费控 制会话延迟关联自身的复杂性， 使得在漫游场景下实现策略计费控制会话延 迟关联的方法以及对其的策略计费控制存在难度， 现有技术中还没有相应的 解决方案。 发明内容
本发明所要解决的技术问题是， 克服现有技术的不足， 提供一种 EPS漫 游场景下实现承载绑定和事件报告功能的重选的系统及方法， 以便在漫游场 景下实现策略计费控制会话的延迟关联。
为了解决上述问题， 本发明首先提供一种承载绑定和事件报告功能的重 选方法， 在演进的分组系统 EPS中为用户设备 UE建立第一 IP连接接入网 IP-CAN会话， 并建立用于对第一 IP-CAN会话进行策略控制的第一网关控制 会话、 第一 Gx会话、 S9会话和 S9会话的第一子会话后， 在承载绑定和事件 才艮告功能 BBERF重选的过程中：
拜访地策略和计费规则功能 PCRF与归属地 PCRF建立 S9会话的第二子 会话，并将目的 BBERF与拜访地 PCRF之间建立的第二网关控制会话与所述 第二子会话进行关联； 如果接收到策略和计费执行功能 PCEF发送的 IP-CAN会话修改指示消 息， 则归属地 PCRF根据所述 IP-CAN会话修改指示消息中包含的会话标识 信息将所述 IP-CAN会话修改指示消息请求修改的第一 Gx会话与所述第二子 会话进行关联； 或
如果接收到 PCEF发送的 IP-CAN会话建立指示消息，则归属地 PCRF根 据所述 IP-CAN会话建立指示消息中包含的会话标识信息，将所述 IP-CAN会 话建立指示消息请求建立的第二 Gx会话与所述第二子会话进行关联。
此外，拜访地 PCRF接收到目的 BBERF发送的网关控制会话建立指示消 息后， 根据该消息中携带的延迟关联指示和会话标识信息与归属地 PCRF建 立所述第二子会话， 并将所述网关控制会话建立指示消息请求建立的所述第 二网关控制会话与所述第二子会话进行关联。
此外，拜访地 PCRF通过向归属地 PCRF发送 S9会话修改指示消息来建 立所述第二子会话， 该消息中携带延迟关联指示和会话标识信息；
接收到所述 S9会话修改指示消息后，归属地 PCRF根据所述延迟关联指 示和会话标识信息将为用户制定的默认服务质量 QoS策略包含在 S9会话修 改确认消息中发送给拜访地 PCRF; 接收到所述 S9会话修改确认消息后， 拜访地 PCRF将所述默认 QoS策 略包含在网关控制会话建立确认消息中发送给目的 BBERF。
此外， 将所述第一 Gx会话与所述第二子会话进行关联后， 归属地 PCRF 通过所述第一 Gx会话向 PCEF下发为用户制定的策略计费控制 PCC策略， 并通过所述第二子会话将为用户制定的 QoS策略发送给拜访地 PCRF, 由拜 访地 PCRF将所述 QoS策略通过所述第二网关控制会话下发给目的 BBERF; 或
将所述第二 Gx会话与所述第二子会话进行关联后，归属地 PCRF通过所 述第二 Gx会话向 PCEF下发为用户制定的 PCC策略， 并通过所述第二子会 话将为用户制定的 QoS策略发送给拜访地 PCRF,由拜访地 PCRF将所述 QoS 策略通过所述第二网关控制会话下发给目的 BBERF。
此外， 所述会话标识信息包括用户标识、 分组数据网络标识。
本发明还提供一种承载绑定和事件报告功能的重选方法，在 EPS中为 UE 建立第一 IP-CAN会话，并建立用于对第一 IP-CAN会话进行策略控制的第一 网关控制会话、第一 Gx会话、 S9会话和 S9会话的第一子会话后，在 BBERF 重选的过程中：
目的 BBERF与拜访地 PCRF之间建立第二网关控制会话；
如果接收到 PCEF发送的 IP-CAN会话修改指示消息，则拜访地 PCRF根 据该消息中的会话标识信息将该消息请求修改的第一 Gx会话与所述第二网 关控制会话进行关联， 并与归属地 PCRF建立 S9会话的第二子会话， 通过所 述第二子会话获取归属地 PCRF为用户修改的策略； 或
如果接收到 PCEF发送的 IP-CAN会话建立指示消息，则拜访地 PCRF根 据该消息中的会话标识信息将该消息请求建立的第二 Gx会话与所述第二网 关控制会话进行关联， 并与归属地 PCRF建立 S9会话的第二子会话， 通过所 述第二子会话获取归属地 PCRF为用户新制定的策略。
此外，归属地 PCRF修改或新制定的所述策略包含 PCC规则和 QoS规则； 通过所述第二子会话获取到归属地 PCRF修改或新制定的所述策略后， 拜访地 PCRF通过所述第一 Gx会话向 PCEF下发所述策略中的 PCC规则， 并通过所述第二网关控制会话向目的 BBERF下发所述策略中的 QoS规则。 此外， 归属地 PCRF修改或新制定的所述策略包含 PCC规则；
通过所述第二子会话获取到归属地 PCRF修改或新制定的所述 PCC规则 后， 拜访地 PCRF通过所述第一 Gx会话向 PCEF下发所述 PCC规则， 并根 据所述 PCC规则制定相应的 QoS规则， 通过所述第二网关控制会话向目的 BBERF下发所述 QoS规则。
此外， 接收到所述 IP-CAN会话修改指示消息后， 拜访地 PCRF通过向 归属地 PCRF发送携带执行指示的 S9会话修改指示消息来建立所述第二子会 话， 所述执行指示用于指示归属地 PCRF为用户修改策略； 接收到所述 S9会 话修改指示消息后， 归属地 PCRF根据所述执行指示将为用户修改的策略包 含在 S9会话修改确认消息中发送给拜访地 PCRF; 或
接收到所述 IP-CAN会话建立指示消息后， 拜访地 PCRF通过向归属地 PCRF发送携带执行指示的 S9会话修改指示消息来建立所述第二子会话， 所 述执行指示用于指示归属地 PCRF为用户制定默认策略；接收到所述 S9会话 修改指示消息后， 归属地 PCRF根据所述执行指示将为用户制定的默认策略 包含在 S9会话修改确认消息中发送给拜访地 PCRF。
此外， 目的 BBERF通过向拜访地 PCRF发送网关控制会话建立指示消息 建立所述第二网关控制会话， 该消息中携带延迟关联指示、 接入网承载属性 和会话标识信息；
接收到所述网关控制会话建立指示消息后， 拜访地 PCRF根据所述延迟 关联指示查找与所述会话标识信息对应的默认 QoS规则， 并根据所述接入网 承载属性对所述默认 QoS规则进行修改后通过网关控制会话建立确认消息发 送给目的 BBERF。
此外， 所述会话标识信息包括用户标识、 分组数据网络标识。
本发明提供的一种承载绑定和事件报告功能的重选系统， 包括拜访地策 略和计费规则功能 PCRF、 归属地 PCRF以及策略和计费执行功能 PCEF, 在 演进的分组系统 EPS中为用户设备 UE建立第一 IP连接接入网 IP-CAN会话， 并建立用于对第一 IP-CAN会话进行策略控制的第一网关控制会话、 第一 Gx 会话、 S9会话和 S9会话的第一子会话后，在承载绑定和事件报告功能 BBERF 重选的过程中：
所述拜访地 PCRF, 设置为与所述归属地 PCRF建立 S9会话的第二子会 话， 与目的 BBERF之间建立第二网关控制会话， 并将所述第二网关控制会话 与所述第二子会话进行关联；
所述 PCEF, 设置为向所述归属地 PCRF发送 IP-CAN会话修改指示消息 或者 IP-CAN会话建立指示消息；
所述归属地 PCRF,设置为根据所述 IP-CAN会话修改指示消息中包含的 会话标识信息，将所述 IP-CAN会话修改指示消息请求修改的第一 Gx会话与 所述第二子会话进行关联； 根据所述 IP-CAN会话建立指示消息中包含的会 话标识信息，将所述 IP-CAN会话建立指示消息请求建立的第二 Gx会话与所 述第二子会话进行关联。 本发明提供的另一种承载绑定和事件报告功能的重选系统， 包括拜访地 策略和计费规则功能 PCRF、 归属地 PCRF以及策略和计费执行功能 PCEF, 在演进的分组系统 EPS中为用户设备 UE建立第一 IP连接接入网 IP-CAN会 话， 并建立用于对第一 IP-CAN会话进行策略控制的第一网关控制会话、 第 一 Gx会话、 S9会话和 S9会话的第一子会话后， 在承载绑定和事件报告功能 BBERF重选的过程中：
所述 PCEF , 设置为向所述拜访地 PCRF发送 IP-CAN会话修改指示消息 或者 IP-CAN会话建立指示消息；
所述拜访地 PCRF , 设置为与目的 BBERF之间建立第二网关控制会话； 根据所述 IP-CAN会话修改指示消息中的会话标识信息将所述 IP-CAN会话修 改指示消息请求修改的第一 Gx会话与所述第二网关控制会话进行关联，并与 归属地 PCRF建立 S9会话的第二子会话，通过所述第二子会话获取所述归属 地 PCRF为用户修改的策略； 根据所述 IP-CAN会话建立指示消息中的会话 标识信息将所述 IP-CAN会话建立指示消息请求建立的第二 Gx会话与所述第 二网关控制会话进行关联，并与所述归属地 PCRF建立 S9会话的第二子会话， 通过所述第二子会话获取所述归属地 PCRF为用户新制定的策略； 所述归属地 PCRF,设置为为用户新制定所述策略，并与所述拜访地 PCRF 建立所述 S9会话的第二子会话。
综上所述，本发明通过在 BBERF重选的过程中在拜访地 PCRF与归属地 PCRF之间建立新的 S9会话的子会话，并将其与目的 BBERF与拜访地 PCRF 建立的网关控制会话（Gxx会话）以及相应的 Gx会话相关联， 在家乡路由和 本地疏导的漫游场景下实现了策略计费控制会话的延迟关联。
本发明的其它特征和优点将在随后的说明书中阐述， 并且， 部分地从说 明书中变得显而易见， 或者通过实施本发明而了解。 本发明的目的和其他优 点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图概述
附图用来提供对本发明的进一步理解， 并且构成说明书的一部分， 与本 发明的实施例一起用于解释本发明， 并不构成对本发明的限制。 在附图中： 图 1为相关技术中的 EPS的系统架构示意图；
图 2为 UE通过 E-UTRAN接入 EPS并建立 PDN连接的初始附着流程示 意图；
图 3为 UE釆用图 2所示流程接入 EPS后， 从 E-UTRAN切换到可信任 非 3GPP接入系统的流程示意图；
图 4为现有技术中家乡路由的 EPS漫游架构图；
图 5为现有技术中本地疏导的 EPS漫游架构图；
图 6为本发明第一实施例 UE在家乡路由的漫游场景下，通过 E-UTRAN 执行初始附着的流程示意图；
图 7a为本发明第一实施例具有网络移动性能力的 UE釆用图 6所示流程 接入 EPS后， 从通过 E-UTRAN接入切换到通过可信任非 3GPP接入的流程 示意图；
图 7b为本发明第一实施例不具有网络移动性能力的 UE釆用图 6所示流 程接入 EPS后， 从通过 E-UTRAN接入切换到通过可信任非 3GPP接入的流 程示意图； 图 8为本发明第二实施例 UE在本地疏导的漫游场景下，通过 E-UTRAN 执行初始附着的流程示意图；
图 9a为本发明第二实施例具有网络移动性能力的 UE釆用图 8所示流程 接入 EPS后， 从通过 E-UTRAN接入切换到通过可信任非 3GPP接入的流程 示意图；
图 9b为本发明第二实施例不具有网络移动性能力的 UE釆用图 8所示流 程接入 EPS后， 从通过 E-UTRAN接入切换到通过可信任非 3GPP接入的流 程示意图。
本发明的较佳实施方式
以下将结合附图及实施例来详细说明本发明的实施方式， 借此对本发明 如何应用技术手段来解决技术问题， 并达成技术效果的实现过程能充分理解 并据以实施。
需要说明的是， 如果不冲突， 本发明实施例以及实施例中的各个特征可 以相互结合， 均在本发明的保护范围之内。 另外， 在附图的流程示意图示出 的步骤可以在诸如一组计算机可执行指令的计算机系统中执行， 并且， 虽然 在流程示意图中示出了逻辑顺序， 但是在某些情况下， 可以以不同于此处的 顺序执行所示出或描述的步骤。
本发明的核心思想是， 在 BBERF重选的过程， 拜访地 PCRF和归属地 PCRF之间建立一个新的 S9会话子会话， 并将目的 BBERF与拜访地 PCRF 建立的网关控制会话 ( Gxx会话 )与子会话关联， 同时根据会话标识信息（包 括用户标识、 PDN标识等 )将 PCEF发送的 IP-CAN会话建立指示消息请求 建立的 Gx会话或 IP-CAN会话修改指示消息的请求修改的 Gx会话关联到这 个新建立的 S9会话子会话。
下面将结合附图和实施例对本发明在不同漫游场景下实现策略计费控制 会话延迟关联的方法进行详细描述。
第一实施例 图 6为本发明第一实施例 UE在家乡路由的漫游场景下，通过 E-UTRAN 执行初始附着的流程示意图； 其中， S-GW与 P-GW之间釆用 PMIPv6协议。 图 6所示流程主要包括如下步骤：
步骤 S601： UE向 eNodeB发送附着请求消息， 请求接入 EPS;
步骤 S602: eNodeB向 MME发送附着请求消息；
步骤 S603： 网络对 UE进行认证并启动 NAS安全加密保护；
步骤 S604: 认证通过后， MME与 HSS交互， 执行位置更新流程； 步骤 S605： MME根据用户签约的默认 APN为 UE选择 P-GW, 并选择 S-GW, MME向选定的 S-GW发送建立默认承载请求消息；
步骤 S606: 位于 S-GW中的 BBERF向 vPCRF发送网关控制会话建立指 示消息， 该消息中携带用户标识 NAI、 PDN标识 APN以及当前接入网的承 载属性 (包括 IP-CAN类型、 RAT类型和 BBERF地址）等； 该消息请求建立 的网关控制会话（Gxx会话） ， 表示为 Gxx会话 1 ;
步骤 S607: vPCRF根据 NAI判定对应的用户为漫游用户， 并且还没有 为该用户建立 S9会话， 因此 vPCRF向 hPCRF发送 S9会话建立指示消息， 请求建立一个 S9会话的子会话 Subsessionl , vPCRF保持 Gxx会话 1 和 Subsessionl的关联关系， 并将 NAI、 APN以及当前接入网的承载属性包含在 Subsessionl中发送给 hPCRF;
步骤 S608: hPCRF根据 NAI和 APN获取用户的签约信息， 从而根据用 户的签约信息、 网络策略和当前接入网的承载属性制定策略， 这时 hPCRF制 定的策略为用户接入该 APN的一些默认策略， 包括 PCC规则、 QoS规则和 事件触发器；
hPCRF向 vPCRF返回 S9会话建立确认消息， 将 QoS规则和事件触发器 包含在 Subsessionl中发送给 vPCRF;
步骤 S609: vPCRF向 BBERF返回 Gxx会话 1的网关控制会话建立确认 消息， 将 Subsessionl中的 QoS规则和事件触发器发送给 BBERF; BBERF安 装并执行 QoS规则和事件触发器；
步骤 S610: S-GW向步骤 S605中 MME所选择的 P-GW发送代理绑定更 新消息 , 该消息中携带用户标识 NAI、 PDN标识 APN和接入网承载属性（包 括 IP-CAN类型、 或 IP-CAN类型和 RAT类型） ；
步骤 S611： P-GW为 UE接入而请求建立的 PDN连接 (即 IP-CAN会话 ) 分配 IP地址， 表示为 IP Address 1 ; 在家乡路由场景下， P-GW位于归属地网 络， 位于 P-GW的 PCEF向 hPCRF发送 IP-CAN会话建立指示消息， 该消息 中携带用户标识 NAI、 PDN标识 APN、 IP Address 1和接入网承载属性等； 该 消息请求建立的 Gx会话表示为 Gx会话 1 ;
步骤 S612: hPCRF根据 NAI和 APN将 Gx会话 1 和 S9会话中的 Subsessionl进行关联；
步骤 S613 : hPCRF向 PCEF返回 Gx会话 1的 IP-CAN会话建立确认消 息， 将步骤 S608制定的 PCC规则和事件触发器发送给 PCEF; PCEF安装并 执行 PCC规则和事件触发器；
hPCRF有可能会根据步骤 S611上报的接入网承载属性修改 PCC规则和 QoS规则， 此时 hPCRF会将修改的 PCC规则和 QoS规则分别发送给 PCEF 和 BBERF进行更新；
步骤 S614: P-GW向 S-GW返回代理绑定确认消息， 该消息中携带 IP Address 1 ;
步骤 S615: S-GW向 MME返回建立默认承载应答消息， 该消息中携带 IP Address 1 ;
步骤 S616 : MME 向 eNodeB 返回附着接受消息， 该消息中携带 IP
Address 1 ;
步骤 S617: eNodeB向 UE返回附着接受消息，该消息中携带 IP Addressl ; 步骤 S618: UE向 eNodeB发送附着完成消息；
步骤 S619: eNodeB向 MME发送附着完成消息；
步骤 S620： MME与 S-GW进行更新承载的交互流程；
步骤 S621： MME根据用户签约信息获知 UE可以通过非 3GPP接入， 因 此将 UE建立 PDN连接所选择的 P-GW的地址发送给 HSS , HSS保存该 P-GW 地址后返回应答消息。 图 7a为本发明第一实施例 UE釆用图 6所示流程接入 EPS后， 从通过 E-UTRAN接入切换到通过可信任非 3GPP接入的流程示意图； 其中， 通过非 3GPP接入时， 可信任非 3GPP接入网关与 P-GW之间釆用 PMIPv6协议； 本 流程中， UE具有网络移动性能力 （即 IP地址保持能力） 。 图 7a所示流程主 要包括如下步骤：
步骤 S701 : UE通过 3GPP接入建立 PDN连接， S-GW和 P-GW之间存 在 PMIPv6隧道；
步骤 S702: UE发现可信任非 3GPP接入系统并决定将当前的会话从 3GPP 接入切换到该可信任非 3GPP接入系统；
步骤 S703: UE、 可信任非 3GPP接入网关和 HSS/AAA执行 EAP认证过 程； 在认证过程中， HSS/AAA将 UE在 3GPP接入时所选择的 P-GW的地址 返回给可信任非 3GPP接入网关；
步骤 S704: 认证授权成功后， 非 3GPP接入特定的层 3附着流程被触发； 步骤 S705: 由于可信任非 3GPP接入网关不确定 UE是否具有网络移动 性能力（即 IP地址保持能力 ),所以位于可信任非 3GPP接入网关中的 BBERF 向 vPCRF发送网关控制会话建立指示消息，该消息中携带用户标识 NAI、 PDN 标识 APN、新的接入网承载属性（包括 IP-CAN类型、或 IP-CAN类型和 RAT 类型）和延迟关联指示； 该消息请求建立的网关控制会话 ( Gxx会话） ， 表 示为 Gxx会话 2;
步骤 S706:由于网关控制会话建立指示消息中携带延迟关联指示， vPCRF 不根据 NAI和 APN将 Gxx会话 2和图 6流程中建立的 Subsessionl进行关联； vPCRF决定新建一个 S9会话子会话， 因此 vPCRF向 hPCRF发送 S9会话修 改指示消息， 请求建立新的子会话 Subsession2 , vPCRF 保持 Gxx2 和 Subsession2 的关联关系， 并将新的接入网承载属性、 NAI和 APN 包含在 Subsession2中发送给 hPCRF, 该消息中还携带延迟关联指示；
步骤 S707: 由于 S9会话修改指示消息中携带延迟关联指示， hPCRF不 将 Subsession2和图 6流程建立的 Gx会话 1进行关联； hPCRF根据用户签约 信息、 网络策略、 新接入网承载属性等为 UE通过非 3GPP接入制定 QoS规 则和事件触发器， 这些规则为用户的默认策略， 不包括用户之前访问专有业 务的策略； hPCRF将上述 QoS规则、 事件触发器包含在 Subsession2中通过 S9会话修改确认消息发送给 vPCRF;
步骤 S708: vPCRF将上述 QoS规则和事件触发器通过 Gxx会话 2的网 关控制会话建立确认消息发送给可信任非 3GPP接入网关中的 BBERF; BBERF安装并执行 QoS规则和事件触发器； 可信任非 3GPP接入网关执行特 定的非 3GPP接入流程进行资源预留；
步骤 S709:可信任非 3GPP接入网关根据步骤 S703中获得的 P-GW地址 向对应的 P-GW发送代理绑定更新消息， 该消息中携带用户标识 NAI、 PDN 标识 APN和当前的接入网承载属性（包括 IP-CAN类型、 或 IP-CAN类型和 RAT类型） ；
步骤 S710: 如果 P-GW判定 UE具有网络移动性能力（即 IP地址保持能 力） ， 则执行 UE的切换流程：
P-GW根据 NAI和 APN为 UE分配其通过 3GPP接入时使用的 IP地址（ IP
Addressl ) 以保持 IP地址不变， 进而保证业务的连续性；
位于 P-GW的 PCEF向 hPCRF发送 IP-CAN会话修改指示消息， 该消息 中携带新的接入网承载属性 (包括 IP-CAN类型、 或 IP-CAN类型和 RAT类 型） ， 还可以携带用户标识 NAI和 PDN标识 APN等； 该消息修改的是图 6 建立的 Gx会话 1 ;
步骤 S711 : hPCRF根据 PCEF发送的 IP-CAN会话修改指示消息判定 UE 可以执行切换流程， 因此根据 NAI和 APN将 Gx会话 1与 Subsession2进行 关联； 同时， hPCRF可以继续保持 Gx会话 1和 Subsessionl的关联关系； 步骤 S712: hPCRF可能会根据新的接入网承载属性修改 UE切换前所建 立的 PDN连接的 PCC规则、 QoS规则和事件触发器； 这些规则包括 UE在通 过 3GPP接入时访问的专有业务的策略； hPCRF通过 Gx会话 1的 IP-CAN会 话修改确认消息将修改后的 PCC规则和事件触发器返回给 PCEF进行更新； 步骤 S713: P-GW向可信任非 3GPP接入网关返回代理绑定确认消息， 该消息中携带 IP Address 1；
步骤 S714: 可信任非 3GPP接入网关向 UE返回层 3附着完成消息， 该 消息中携带 IP Addressl ;
步骤 S715: hPCRF将步骤 S712制定的 QoS规则和事件触发器包含在 Subsession2的 S9会话和规则提供消息中发送给 vPCRF;
步骤 S716: vPCRF将 QoS规则和事件触发器通过 Gxx会话 2的网关控 制和 QoS规则提供消息发送给可信任非 3GPP接入网关中的 BBERF;
步骤 S717: BBERF安装 QoS规则和事件触发器后返回网关控制和 QoS 规则提供确认消息；可信任非 3GPP接入网关执行特定的非 3GPP接入流程进 行资源预留；
步骤 S718： vPCRF向 hPCRF返回 S9会话和规则提供确认消息； 步骤 S719: UE将 PDN连接从 3GPP接入切换到了从可信任非 3GPP接 入， 在可信任非 3GPP接入网关和 P-GW之间存在 PMIPv6隧道（该 PMIPv6 隧道通过步骤 S709和 S713建立 )； UE在通过 3GPP接入时访问的业务都能 继续访问。
在上述流程中， 如果 P-GW判定 UE不具有网络移动性能力， 则 P-GW 将为 UE建立一个新的 PDN连接 (即 IP-CAN会话 ) , 具体执行步骤如图 7b 所示：
步骤 S701，~ S709，： 分别与步骤 S701 ~ S709相同；
步骤 S710': 如果 P-GW判定 UE不具有网络移动性能力 （即不具有 IP 地址保持能力 ) , 则 P-GW决定建立新的 PDN连接：
P-GW为 UE分配新的 IP地址（记作 IP Address2 ) ；
位于 P-GW的 PCEF向 hPCRF发送 IP-CAN会话建立指示消息， 该消息 中携带用户标识 NALPDN标识 APN、IP Address2和新的接入网承载属性（包 括 IP-CAN类型、 或 IP-CAN类型和 RAT类型 ) ； 该消息请求建立一个新的 Gx会话， 表示为 Gx会话 2; 步骤 S711，： hPCRF根据 PCEF发送的 IP-CAN会话建立指示消息判定 UE不能执行切换流程， 而是在可信任非 3GPP接入网关中新建一个 PDN连 接， 因此根据 NAI和 APN将 Subsession2与 Gx会话 2进行关联；
步骤 S712' : hPCRF根据新的接入网承载特性、 网络策略、 用户签约信 息等为新建立的 PDN连接 (即 IP-CAN会话 )制定默认策略（包括 PCC规则、 QoS规则和事件触发器 ) , 并通过 Gx会话 2的 IP-CAN会话建立确认消息将 PCC规则和事件触发器返回给 PCEF, PCEF安装并执行 PCC规则和事件触 发器；
步骤 S713' : P-GW向可信任非 3GPP接入网关返回代理绑定确认消息， 该消息中携带 IP Address2；
步骤 S714，： 可信任非 3GPP接入网关向 UE返回层 3附着完成消息， 该 消息中携带 IP Address2;
步骤 S715' : 若步骤 S712'制定的 QoS规则和事件触发器与步骤 S707'制 定的 QoS规则和事件触发器不同， 则 hPCRF将步骤 712'制定的 QoS规则和 事件触发器包含在 Subsession2的 S9会话和规则提供消息中发送给 vPCRF; 步骤 S716' : vPCRF将 QoS规则和事件触发器通过 Gxx会话 2的网关控 制和 QoS规则提供消息发送给可信任非 3GPP接入网关中的 BBERF;
步骤 S717' : BBERF安装执行 QoS规则和事件触发器，并向 vPCRF返回 网关控制和 QoS规则提供确认消息； 可信任非 3GPP接入网关执行特定的非 3GPP接入流程进行资源预留；
步骤 S718，： vPCRF向 hPCRF返回 S9会话和规则提供确认消息； 步骤 S719' : UE通过可信任非 3GPP接入网新建立了一个 PDN连接 (即 IP-CAN会话 ) , 在可信任非 3GPP接入网关和 P-GW之间存在 PMIPv6隧道 (该 PMIPv6隧道通过步骤 S709'和 S713'建立 )； UE在通过 3GPP接入时访 问的业务不能继续访问， UE需要重新发起业务访问请求。
本实施例中承载绑定和事件报告功能的重选系统， 主要包括拜访地策略 和计费规则功能 PCRF、 归属地 PCRF以及策略和计费执行功能 PCEF, 在演 进的分组系统 EPS中为用户设备 UE建立第一 IP连接接入网 IP-CAN会话， 并建立用于对第一 IP-CAN会话进行策略控制的第一网关控制会话、 第一 Gx 会话、 S9会话和 S9会话的第一子会话后，在承载绑定和事件报告功能 BBERF 重选的过程中：
拜访地 PCRF设置为与归属地 PCRF建立 S9会话的第二子会话， 与目的 BBERF之间建立第二网关控制会话， 并将第二网关控制会话与第二子会话进 行关联；
PCEF设置为向归属地 PCRF发送 IP-CAN会话修改指示消息或者 IP-CAN 会话建立指示消息；
归属地 PCRF设置为根据 IP-CAN会话修改指示消息中包含的会话标识 信息，将 IP-CAN会话修改指示消息请求修改的第一 Gx会话与第二子会话进 行关联； 根据 IP-CAN会话建立指示消息中包含的会话标识信息， 将 IP-CAN 会话建立指示消息请求建立的第二 Gx会话与第二子会话进行关联。
本实施例同样适用于 UE从一个可信任非 3GPP接入网切换到另一个可信 任非 3GPP接入网。 其中， 通过两个非 3GPP接入时， 可信任非 3GPP接入网 关与 P-GW之间釆用 PMIPv6协议。
第二实施例
图 8为本发明第二实施例 UE在本地疏导的漫游场景下，通过 E-UTRAN 执行初始附着的流程示意图； 其中， S-GW与 P-GW之间釆用 PMIPv6协议。 图 8所示流程主要包括如下步骤：
步骤 S801： UE向 eNodeB发送附着请求消息， 请求接入 EPS;
步骤 S802： eNodeB向 MME发送附着请求消息；
步骤 S803： 网络对 UE进行认证并启动 NAS安全加密保护；
步骤 S804: 认证通过后， MME与 HSS交互， 执行位置更新流程； 步骤 S805： MME根据用户签约的默认 APN为 UE选择 P-GW, 并选择
S-GW, MME向选定的 S-GW发送建立默认承载请求消息；
步骤 S806: 位于 S-GW中的 BBERF向 vPCRF发送网关控制会话建立指 示消息， 该消息中携带用户标识 NAI、 PDN标识 APN以及当前接入网的承 载属性 (包括 IP-CAN类型、 RAT类型和 BBERF地址）等； 该消息请求建立 的网关控制会话（Gxx会话） ， 表示为 Gxx会话 1 ;
步骤 S807: vPCRF根据 NAI判定对应的用户为漫游用户， 并且还没有 为该用户建立 S9会话， 因此 vPCRF向 hPCRF发送 S9会话建立指示消息， 请求建立一个 S9会话的子会话 Subsessionl , vPCRF保持 Gxx会话 1 和 Subsessionl的关联关系， 并将 NAI、 APN以及当前接入网的承载属性包含在 Subsessionl中发送给 hPCRF;
步骤 S808: hPCRF根据 NAI和 APN获取用户的签约信息， 从而根据用 户的签约信息、 网络策略和当前接入网的承载属性制定策略， 这时 hPCRF制 定的策略为用户接入该 APN的一些默认策略， 包括 PCC规则、 QoS规则和 事件触发器；
hPCRF向 vPCRF返回 S9会话建立确认消息， 将 QoS规则和事件触发器 包含在 Subsessionl中发送给 vPCRF;
步骤 S809: vPCRF向 BBERF返回 Gxx会话 1的网关控制会话建立确认 消息， 将 Subsessionl中的 QoS规则和事件触发器发送给 BBERF; BBERF安 装并执行 QoS规则和事件触发器；
步骤 S810: S-GW向步骤 S805中 MME所选择的 P-GW发送代理绑定更 新消息， 该消息中携带用户标识 NAI、 PDN标识 APN和接入网承载属性（包 括 IP-CAN类型、 或 IP-CAN类型和 RAT类型） ；
步骤 S811 : P-GW为 UE接入而请求建立的 PDN连接分配 IP地址， 表 示为 IP Address 1； 位于 P-GW的 PCEF向 vPCRF发送 IP-CAN会话建立指示 消息， 该消息中携带用户标识 NAI、 PDN标识 APN、 IP Address 1和接入网承 载属性（包括 IP-CAN类型、 或 IP-CAN类型和 RAT类型）等； 该消息请求 建立的 Gx会话表示为 Gx会话 1；
步骤 S812: vPCRF根据 NAI和 APN将 Gx会话 1和 Gxx会话 1以及 S9 会话中的 Subsesionl进行关联；
步骤 S813: vPCRF向 hPCRF发送 S9会话修改指示消息， 将 IP Addressl 包含在 Subsessionl中发送给 hPCRF;
步骤 S814: hPCRF向 vPCRF返回 S9会话修改确认消息， 将步骤 S808 制定的 PCC规则和事件触发器包含在 Subsessionl中发送给 vPCRF;
hPCRF有可能会修改 PCC规则、 QoS规则和事件触发器， 此时 hPCRF 会将修改的 PCC规则和 QoS规则分别发送给 PCEF和 BBERF进行更新； 步骤 S815: vPCRF向 PCEF发送 Gx会话 1的 IP-CAN会话建立确认消 息， 将 PCC规则和事件触发器发送给 PCEF; PCEF安装并执行 PCC规则和 事件触发器；
步骤 S816: P-GW向 S-GW返回代理绑定确认消息， 该消息中携带 IP Address 1 ;
步骤 S817: S-GW向 MME返回建立默认承载应答消息， 该消息中携带 IP Address 1 ;
步骤 S818: MME 向 eNodeB 返回附着接受消息， 该消息中携带 IP Address 1 ;
步骤 S819: eNodeB向 UE返回附着接受消息，该消息中携带 IP Addressl ; 步骤 S820: UE向 eNodeB发送附着完成消息；
步骤 S821 : eNodeB向 MME发送附着完成消息；
步骤 S822： MME与 S-GW进行更新承载的交互流程；
步骤 S823: MME根据用户签约信息获知 UE可以通过非 3GPP接入， 因 此将 UE建立 PDN连接所选择的 P-GW的地址发送给 HSS , HSS保存该 P-GW 地址后返回应答消息。
图 9a为本发明第二实施例 UE釆用图 8所示流程接入 EPS后， 从通过 E-UTRAN接入切换到通过可信任非 3GPP接入的流程示意图； 其中， 通过非 3GPP接入时， 可信任非 3GPP接入网关与 P-GW之间釆用 PMIPv6协议。 本 流程中， UE具有网络移动性能力 （即 IP地址保持能力） 。 图 9a所示流程主 要包括如下步骤： 步骤 S901 : UE通过 3GPP接入建立 PDN连接， S-GW和 P-GW之间存 在 PMIPv6隧道；
步骤 S902: UE发现可信任非 3GPP接入系统并决定将当前的会话从 3GPP 接入切换到该可信任非 3GPP接入系统；
步骤 S903: UE、 可信任非 3GPP接入网关和 HSS/AAA执行 EAP认证过 程； 在认证过程中， HSS/AAA将 UE在 3GPP接入时所选择的 P-GW的地址 返回给可信任非 3GPP接入网关；
步骤 S904: 认证授权成功后， 非 3GPP接入特定的层 3附着流程被触发； 步骤 S905: 由于可信任非 3GPP接入网关不确定 UE是否具有网络移动 性能力（即 IP地址保持能力 ),所以位于可信任非 3GPP接入网关中的 BBERF 向 vPCRF发送网关控制会话建立指示消息，该消息中携带用户标识 NAI、 PDN 标识 APN、新的接入网承载属性（包括 IP-CAN类型、或 IP-CAN类型和 RAT 类型 )和延迟关联指示； 该消息请求建立的网关控制会话 ( Gxx会话）表示 为 Gxx会话 2;
步骤 S906:由于网关控制会话建立指示消息中携带延迟关联指示， vPCRF 不根据 NAI和 APN将 Gxx会话 2关联到任何 S9会话的子会话； 由于 UE的 漫游方式为本地疏导， vPCRF根据 NAI和 APN查找图 8中由 hPCRF下发的 默认 QoS规则和事件触发器， 并根据新的接入网承载属性对图 8中由 hPCRF 下发的默认 QoS规则和事件触发器进行相应的修改，并将修改后的 QoS规则 和事件触发器包含在 Gxx会话 2的网关控制会话建立确认消息中下发给可信 任非 3GPP接入网关中的 BBERF; BBERF安装并执行 QoS规则和事件触发 器； 可信任非 3GPP接入网关执行特定的非 3GPP接入流程进行资源预留； 步骤 S907:可信任非 3GPP接入网关根据在步骤 S903获得的 P-GW地址 向对应的 P-GW发送代理绑定更新消息， 该消息中携带用户标识 NAI、 PDN 标识 APN和当前的接入网承载属性（包括 IP-CAN类型、 或 IP-CAN类型和 RAT类型） ；
步骤 S908: 如果 P-GW判定 UE具有网络移动性能力（即 IP地址保持能 力） ， 则 P-GW执行 UE的切换流程： P-GW根据 NAI和 APN为 UE分配其通过 3GPP接入时使用的 IP地址（ IP Addressl ) 以保持 IP地址不变， 进而保证业务的连续性；
位于 P-GW的 PCEF向 vPCRF发送 IP-CAN会话修改指示消息， 该消息 中携带当前的接入网承载属性（包括 IP-CAN类型、 或 IP-CAN类型和 RAT 类型） ； 该消息修改的是图 8建立的 Gx会话 1 ;
步骤 S909: vPCRF根据收到的 IP-CAN会话修改指示消息判定 UE可以 执行切换流程， 因此根据 NAI和 APN将步骤 S905建立的 Gxx会话 2和 Gx 会话 1进行关联；
步骤 S910: vPCRF向 hPCRF发送 S9会话修改指示消息， 请求建立一个 新的子会话 Subsession2, 并将 NAI、 APN, 以及新的接入网承载属性等包含 在 Subsession2中发送给 hPCRF; 该消息中还携带执行指示， 通知 hPCRF执 行 UE的切换流程；
步骤 S911 : hPCRF根据执行指示判断 UE可以执行切换流程， 因此根据 新的接入网承载属性对 UE切换前所建立的 PDN连接的 PCC规则、 QoS规则 和事件触发器进行修改， 其中包含用户在 3GPP接入时访问专有业务的策略； hPCRF将修改后的 PCC规则、 QoS规则和事件触发器包含在 Subsession2中 通过 S9会话修改确认消息发送给 vPCRF;
步骤 S912: vPCRF将 PCC规则和事件触发器通过 Gx会话 1的 IP-CAN 会话修改确认消息发送给 PCEF, PCEF更新 PCC规则和事件触发器；
步骤 S913： P-GW向可信任非 3GPP接入网关返回代理绑定确认消息， 该消息中携带 IP Addressl；
步骤 S914: 可信任非 3GPP接入网关向 UE返回层 3附着完成消息， 该 消息中携带 IP Addressl ;
步骤 S915: vPCRF将 QoS规则和事件触发器通过 Gxx会话 2的网关控 制和 QoS规则提供消息发送可信任非 3GPP接入网关中的 BBERF;
步骤 S916: BBERF安装执行 QoS规则和事件触发器， 并返回网关控制 和 QoS规则提供确认消息给 vPCRF; 可信任非 3GPP接入网关执行特定的非 3GPP接入流程进行资源预留； 步骤 S917: UE将 PDN连接从 3GPP接入切换到了从可信任非 3GPP接 入， 在可信任非 3GPP接入网关和 P-GW之间存在 PMIPv6隧道（该 PMIPv6 隧道通过步骤 S907和 S913建立 )； UE在通过 3GPP接入时访问的专有业务 都能继续访问。
在本发明的其它实施例中， hPCRF仅制定 /修改 PCC规则而不制定 /修改
QoS规则； 在这种情况下， 将由 vPCRF根据 hPCRF下发的 PCC规则制定相 应的 QoS规则 , 并将其下发给相应的 BBERF。 例如， hPCRF为 UE通过可信 任非 3GPP接入建立的 PDN连接制定 PCC规则，并将 PCC规则下发给 vPCRF, vPCRF根据 PCC规则制定 QoS规则， 并将 QoS规则下发给可信任非 3GPP 接入网关中的 BBERF。
在上述流程中， 如果 P-GW判定 UE不具有网络移动性能力， 则 P-GW 将为 UE建立一个新的 PDN连接 (即 IP-CAN会话 ) , 具体执行步骤如图 9b 所示：
步骤 S901 ' ~ S907' : 分别与步骤 S901 ~ S907相同；
步骤 S908' : 如果 P-GW判定 UE不具有网络移动性能力 （即不具有 IP 地址保持能力 ) , 则 P-GW建立新的 PDN连接：
P-GW为 UE分配新的 IP地址（记作 IP Address2 ) ；
位于 P-GW的 PCEF向 vPCRF发送 IP-CAN会话建立指示消息， 该消息 中携带用户标识 NAL PDN标识 APN、IP Address2和新的接入网承载属性（包 括 IP-CAN类型、 或 IP-CAN类型和 RAT类型 ) ； 该消息请求建立一个新的 Gx会话， 表示为 Gx会话 2;
步骤 S909，： vPCRF根据收到的 IP-CAN会话建立指示消息判定 UE不能 执行切换流程， 而是在可信任非 3GPP接入网关中新建一个 PDN连接， 因此 根据 NAI和 APN将 Gxx会话 2与 Gx会话 2进行关联；
步骤 S910' : vPCRF向 hPCRF发送 S9会话修改指示消息， 请求建立一 个新的子会话 Subsession2 , 并将 NAI、 APN, 以及新的接入网承载属性、 IP Address2包含在 Subsession2中发送给 hPCRF; 该消息中还携带执行指示，通 知 hPCRF执行新建 PDN连接 (即 IP-CAN会话 ) 流程；
步骤 S911，： hPCRF根据执行指示判定 UE发起建立新的 PDN连接 (即 IP-CAN会话） ， 因此 hPCRF根据新的接入网承载属性、 网络策略和用户签 约信息等为新建的 PDN连接 (即 IP-CAN会话 )制定 PCC规则、 QoS规则和 事件触发器，这些规则均为默认规则， 不包含 UE通过 3GPP接入时访问专有 业务的策略； hPCRF 将上述 PCC 规则、 QoS 规则和事件触发器包含在 Subsession2中， 通过 S9会话修改确认消息发送给 vPCRF;
步骤 S912' : vPCRF通过 Gx会话 2的 IP-CAN会话建立确认消息将 PCC 规则和事件触发器发送给 PCEF, PCEF安装并执行 PCC规则和事件触发器； 步骤 S913 '： P-GW向可信任非 3GPP接入网关返回代理绑定确认消息， 该消息中携带 IP Address2；
步骤 S914' : 可信任非 3GPP接入网关向 UE返回层 3附着完成消息， 该 消息中携带 IP Address2;
步骤 S915' : vPCRF将 QoS规则和事件触发器通过 Gxx会话 2的网关控 制和 QoS规则提供消息发送给可信任非 3GPP接入网关中的 BBERF;
步骤 S916' : BBERF安装执行 QoS规则和事件触发器，并向 vPCRF返回 网关控制和 QoS规则提供确认消息； 可信任非 3GPP接入网关执行特定的非 3GPP接入流程进行资源预留；
步骤 S917' : UE通过可信任非 3GPP接入网新建立了一个 PDN连接 (即 IP-CAN会话） ， 在可信任非 3GPP接入网关和 P-GW之间存在 PMIPv6隧道 (该 PMIPv6隧道通过步骤 S907'和 S913'建立 )； UE在通过 3GPP接入时访 问的业务不能继续访问， UE需要重新发起业务访问请求。
本实施例同样适用于 UE从一个可信任非 3GPP接入网切换到另一个可信 任非 3GPP接入网。 其中， 通过两个非 3GPP接入时， 可信任非 3GPP接入网 关与 P-GW之间釆用 PMIPv6协议。
在本发明的其它实施例中， hPCRF仅制定 PCC规则而不制定 QoS规则。 则， 并将其下发给相应的 BBERF。 例如， hPCRF为 UE通过可信任非 3GPP 接入建立的 PDN连接 (即 IP-CAN会话 )制定 PCC规则， 并将 PCC规则下 发给 vPCRF, vPCRF根据 PCC规则制定 QoS规则， 并将 QoS规则下发给可 信任非 3GPP接入网关中的 BBERF。
本实施例中承载绑定和事件报告功能的重选系统， 主要包括拜访地策略 和计费规则功能 PCRF、 归属地 PCRF以及策略和计费执行功能 PCEF, 在演 进的分组系统 EPS中为用户设备 UE建立第一 IP连接接入网 IP-CAN会话， 并建立用于对第一 IP-CAN会话进行策略控制的第一网关控制会话、 第一 Gx 会话、 S9会话和 S9会话的第一子会话后，在承载绑定和事件报告功能 BBERF 重选的过程中：
PCEF设置为向拜访地 PCRF发送 IP-CAN会话修改指示消息或者 IP-CAN 会话建立指示消息；
拜访地 PCRF设置为与目的 BBERF之间建立第二网关控制会话；并根据 IP-CAN会话修改指示消息中的会话标识信息将 IP-CAN会话修改指示消息请 求修改的第一 Gx会话与第二网关控制会话进行关联，并与归属地 PCRF建立 S9会话的第二子会话，通过第二子会话获取归属地 PCRF为用户修改的策略； 根据 IP-CAN会话建立指示消息中的会话标识信息将 IP-CAN会话建立指示消 息请求建立的第二 Gx会话与第二网关控制会话进行关联， 并与归属地 PCRF 建立 S9会话的第二子会话，通过第二子会话获取归属地 PCRF为用户新制定 的策略；
归属地 PCRF设置为为用户新制定策略， 并与拜访地 PCRF建立 S9会话 的第二子会话。
显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布 在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程 序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 或 者将它们分别制作成各个集成电路模块， 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样， 本发明不限制于任何特定的硬件和软 件结合。 虽然本发明所揭露的实施方式如上， 但所述的内容只是为了便于理解本 发明而釆用的实施方式， 并非用以限定本发明。 任何本发明所属技术领域内 的技术人员， 在不脱离本发明所揭露的精神和范围的前提下， 可以在实施的 形式上及细节上作任何的修改与变化， 但本发明的专利保护范围， 仍须以所 附的权利要求书所界定的范围为准。

Claims

权 利 要 求 书
1、 一种承载绑定和事件报告功能的重选方法，其中，在演进的分组系统 EPS中为用户设备 UE建立第一 IP连接接入网 IP-CAN会话， 并建立用于对 第一 IP-CAN会话进行策略控制的第一网关控制会话、 第一 Gx会话、 S9会 话和 S9会话的第一子会话后， 在承载绑定和事件报告功能 BBERF重选的过 程中：
拜访地策略和计费规则功能 PCRF与归属地 PCRF建立 S9会话的第二子 会话，并将目的 BBERF与拜访地 PCRF之间建立的第二网关控制会话与所述 第二子会话进行关联； 如果接收到策略和计费执行功能 PCEF发送的 IP-CAN会话修改指示消 息， 则归属地 PCRF根据所述 IP-CAN会话修改指示消息中包含的会话标识 信息将所述 IP-CAN会话修改指示消息请求修改的第一 Gx会话与所述第二子 会话进行关联； 或
如果接收到 PCEF发送的 IP-CAN会话建立指示消息，则归属地 PCRF根 据所述 IP-CAN会话建立指示消息中包含的会话标识信息，将所述 IP-CAN会 话建立指示消息请求建立的第二 Gx会话与所述第二子会话进行关联。
2、 如权利要求 1所述的方法， 其中：
拜访地 PCRF接收到目的 BBERF发送的网关控制会话建立指示消息后， 根据该消息中携带的延迟关联指示和会话标识信息与归属地 PCRF建立所述 第二子会话， 并将所述网关控制会话建立指示消息请求建立的所述第二网关 控制会话与所述第二子会话进行关联。
3、 如权利要求 2所述的方法， 其中：
拜访地 PCRF通过向归属地 PCRF发送 S9会话修改指示消息来建立所述 第二子会话， 该消息中携带延迟关联指示和会话标识信息；
接收到所述 S9会话修改指示消息后，归属地 PCRF根据所述延迟关联指 示和会话标识信息将为用户制定的默认服务质量 QoS策略包含在 S9会话修 改确认消息中发送给拜访地 PCRF; 接收到所述 S9会话修改确认消息后， 拜访地 PCRF将所述默认 QoS策 略包含在网关控制会话建立确认消息中发送给目的 BBERF。
4、 如权利要求 1所述的方法， 其中：
将所述第一 Gx会话与所述第二子会话进行关联后，归属地 PCRF通过所 述第一 Gx会话向 PCEF下发为用户制定的策略计费控制 PCC策略， 并通过 所述第二子会话将为用户制定的 QoS 策略发送给拜访地 PCRF, 由拜访地 PCRF将所述 QoS策略通过所述第二网关控制会话下发给目的 BBERF; 或 将所述第二 Gx会话与所述第二子会话进行关联后，归属地 PCRF通过所 述第二 Gx会话向 PCEF下发为用户制定的 PCC策略， 并通过所述第二子会 话将为用户制定的 QoS策略发送给拜访地 PCRF,由拜访地 PCRF将所述 QoS 策略通过所述第二网关控制会话会话下发给目的 BBERF。
5、 如权利要求 1至 4中任一权利要求所述的方法， 其中：
所述会话标识信息包括用户标识、 分组数据网络标识。
6、 一种承载绑定和事件报告功能的重选方法，其中，在演进的分组系统 EPS中为用户设备 UE建立第一 IP连接接入网 IP-CAN会话， 并建立用于对 第一 IP-CAN会话进行策略控制的第一网关控制会话、 第一 Gx会话、 S9会 话和 S9会话的第一子会话后， 在承载绑定和事件报告功能 BBERF重选的过 程中：
目的 BBERF与拜访地策略和计费规则功能 PCRF之间建立第二网关控制 会话；
如果接收到策略和计费执行功能 PCEF发送的 IP-CAN会话修改指示消 息， 则拜访地 PCRF根据该消息中的会话标识信息将该消息请求修改的第一 Gx会话与所述第二网关控制会话进行关联， 并与归属地 PCRF建立 S9会话 的第二子会话， 通过所述第二子会话获取归属地 PCRF为用户修改的策略； 或
如果接收到 PCEF发送的 IP-CAN会话建立指示消息，则拜访地 PCRF根 据该消息中的会话标识信息将该消息请求建立的第二 Gx会话与所述第二网 关控制会话进行关联， 并与归属地 PCRF建立 S9会话的第二子会话， 通过所 述第二子会话获取归属地 PCRF为用户新制定的策略。
7、 如权利要求 6所述的方法， 其中：
归属地 PCRF修改或新制定的所述策略包含策略计费控制 PCC规则和服 务质量 QoS规则；
通过所述第二子会话获取到归属地 PCRF修改或新制定的所述策略后， 拜访地 PCRF通过所述第一 Gx会话向 PCEF下发所述策略中的 PCC规则， 并通过所述第二网关控制会话向目的 BBERF下发所述策略中的 QoS规则。
8、 如权利要求 6所述的方法， 其中：
归属地 PCRF修改或新制定的所述策略包含策略计费控制 PCC规则； 通过所述第二子会话获取到归属地 PCRF修改或新制定的所述 PCC规则 后， 拜访地 PCRF通过所述第一 Gx会话向 PCEF下发所述 PCC规则， 并根 据所述 PCC规则制定相应的服务质量 QoS规则，通过所述第二网关控制会话 向目的 BBERF下发所述 QoS规则。
9、 如权利要求 6所述的方法， 其中：
接收到所述 IP-CAN会话修改指示消息后， 拜访地 PCRF通过向归属地 PCRF发送携带执行指示的 S9会话修改指示消息来建立所述第二子会话， 所 述执行指示用于指示归属地 PCRF为用户修改策略；接收到所述 S9会话修改 指示消息后， 归属地 PCRF根据所述执行指示将为用户修改的策略包含在 S9 会话修改确认消息中发送给拜访地 PCRF; 或
接收到所述 IP-CAN会话建立指示消息后， 拜访地 PCRF通过向归属地 PCRF发送携带执行指示的 S9会话修改指示消息来建立所述第二子会话， 所 述执行指示用于指示归属地 PCRF为用户制定默认策略；接收到所述 S9会话 修改指示消息后， 归属地 PCRF根据所述执行指示将为用户制定的默认策略 包含在 S9会话修改确认消息中发送给拜访地 PCRF。
10、 如权利要求 6所述的方法， 其中: 目的 BBERF通过向拜访地 PCRF发送网关控制会话建立指示消息建立所 述第二网关控制会话， 该消息中携带延迟关联指示、 接入网承载属性和会话 标识信息；
接收到所述网关控制会话建立指示消息后， 拜访地 PCRF根据所述延迟 关联指示查找与所述会话标识信息对应的默认服务质量 QoS规则， 并根据所 述接入网承载属性对所述默认服务质量 QoS规则进行修改后通过网关控制会 话建立确认消息发送给目的 BBERF。
11、 如权利要求 6至 10中任一权利要求所述的方法， 其中：
所述会话标识信息包括用户标识、 分组数据网络标识。
12、 一种承载绑定和事件报告功能的重选系统， 包括拜访地策略和计费 规则功能 PCRF、 归属地 PCRF以及策略和计费执行功能 PCEF, 在演进的分 组系统 EPS中为用户设备 UE建立第一 IP连接接入网 IP-CAN会话， 并建立 用于对第一 IP-CAN会话进行策略控制的第一网关控制会话、 第一 Gx会话、 S9会话和 S9会话的第一子会话后，在承载绑定和事件报告功能 BBERF重选 的过程中：
所述拜访地 PCRF, 设置为与所述归属地 PCRF建立 S9会话的第二子会 话， 与目的 BBERF之间建立第二网关控制会话， 并将所述第二网关控制会话 与所述第二子会话进行关联；
所述 PCEF, 设置为向所述归属地 PCRF发送 IP-CAN会话修改指示消息 或者 IP-CAN会话建立指示消息；
所述归属地 PCRF,设置为根据所述 IP-CAN会话修改指示消息中包含的 会话标识信息，将所述 IP-CAN会话修改指示消息请求修改的第一 Gx会话与 所述第二子会话进行关联； 根据所述 IP-CAN会话建立指示消息中包含的会 话标识信息，将所述 IP-CAN会话建立指示消息请求建立的第二 Gx会话与所 述第二子会话进行关联。
13、 一种承载绑定和事件报告功能的重选系统， 包括拜访地策略和计费 规则功能 PCRF、 归属地 PCRF以及策略和计费执行功能 PCEF, 在演进的分 组系统 EPS中为用户设备 UE建立第一 IP连接接入网 IP-CAN会话， 并建立 用于对第一 IP-CAN会话进行策略控制的第一网关控制会话、 第一 Gx会话、 S9会话和 S9会话的第一子会话后，在承载绑定和事件报告功能 BBERF重选 的过程中：
所述 PCEF , 设置为向所述拜访地 PCRF发送 IP-CAN会话修改指示消息 或者 IP-CAN会话建立指示消息；
所述拜访地 PCRF , 设置为与目的 BBERF之间建立第二网关控制会话； 根据所述 IP-CAN会话修改指示消息中的会话标识信息将所述 IP-CAN会话修 改指示消息请求修改的第一 Gx会话与所述第二网关控制会话进行关联，并与 归属地 PCRF建立 S9会话的第二子会话，通过所述第二子会话获取所述归属 地 PCRF为用户修改的策略； 根据所述 IP-CAN会话建立指示消息中的会话 标识信息将所述 IP-CAN会话建立指示消息请求建立的第二 Gx会话与所述第 二网关控制会话进行关联，并与所述归属地 PCRF建立 S9会话的第二子会话， 通过所述第二子会话获取所述归属地 PCRF为用户新制定的策略；
所述归属地 PCRF,设置为为用户新制定所述策略，并与所述拜访地 PCRF 建立所述 S9会话的第二子会话。
PCT/CN2009/075373 2009-07-20 2009-12-07 一种承载绑定和事件报告功能的重选系统及方法 WO2011009257A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US13/258,893 US9277592B2 (en) 2009-07-20 2009-12-07 System for bearer binding and event reporting function relocation and method thereof
EP09847492.7A EP2458913B1 (en) 2009-07-20 2009-12-07 Reselection system for bearer binding and event reporting function and method thereof

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910158597.1 2009-07-20
CN2009101585971A CN101959257B (zh) 2009-07-20 2009-07-20 一种承载绑定和事件报告功能的重选方法

Publications (1)

Publication Number Publication Date
WO2011009257A1 true WO2011009257A1 (zh) 2011-01-27

Family

ID=43486277

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/075373 WO2011009257A1 (zh) 2009-07-20 2009-12-07 一种承载绑定和事件报告功能的重选系统及方法

Country Status (4)

Country Link
US (1) US9277592B2 (zh)
EP (1) EP2458913B1 (zh)
CN (1) CN101959257B (zh)
WO (1) WO2011009257A1 (zh)

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931928B (zh) * 2009-06-19 2014-08-13 中兴通讯股份有限公司 漫游场景下单apn多pdn连接的策略计费控制的方法及系统
CN101969673B (zh) * 2009-07-27 2013-08-07 中兴通讯股份有限公司 一种承载绑定和事件报告功能的重选方法
CN101969632B (zh) * 2009-07-28 2013-06-05 中兴通讯股份有限公司 一种漫游场景下的策略计费控制实现方法
US20110182206A1 (en) * 2010-01-25 2011-07-28 Qualcomm Incorporated Apparatus and method for associating a gateway control session with an internet protocol connectivity access network (ip-can) session
US8560708B2 (en) * 2010-06-29 2013-10-15 Alcatel Lucent Method and apparatus for allocating bundles of sessions in a network element
US8959222B2 (en) * 2011-05-19 2015-02-17 International Business Machines Corporation Load balancing system for workload groups
CN102917355A (zh) * 2011-08-03 2013-02-06 中兴通讯股份有限公司 一种接入方法、系统及移动智能接入点
EP2843887A4 (en) * 2012-04-27 2015-12-23 Nec Corp COMMUNICATION SYSTEM AND METHOD FOR CONTROLLING TRANSMISSION PATH
US9596621B2 (en) 2012-08-10 2017-03-14 Ibasis, Inc. Signaling traffic reduction in mobile communication systems
US9788188B2 (en) 2012-12-14 2017-10-10 Ibasis, Inc. Method and system for hub breakout roaming
CN103229538B (zh) * 2012-12-28 2018-03-06 华为技术有限公司 通信系统间的消息处理方法及设备
KR102096503B1 (ko) * 2013-03-07 2020-04-02 삼성전자주식회사 무선통신 시스템에서 트래픽 제어 방법 및 장치
CN103402192A (zh) * 2013-04-25 2013-11-20 南京邮电大学 一种epc网络中实现hss与aaa融合的方法
CN105101176B (zh) * 2014-05-05 2019-06-11 华为技术有限公司 一种漫游场景下的会话绑定方法、装置和系统
US9629060B2 (en) * 2014-06-06 2017-04-18 Oracle International Corporation Flexible routing policy for Wi-Fi offloaded cellular data
JP7046487B2 (ja) 2014-09-25 2022-04-04 シャープ株式会社 Ｕｅ、コアネットワーク装置及びｕｅの通信制御方法
CN105530666B (zh) * 2014-09-29 2019-01-08 中国电信股份有限公司 会话绑定方法与系统
WO2016155011A1 (zh) * 2015-04-03 2016-10-06 华为技术有限公司 一种分组数据网关的选择方法、相关装置及系统
CN106664614B (zh) * 2015-06-26 2019-06-21 华为技术有限公司 承载绑定的方法和相关设备
US10470031B2 (en) 2016-05-20 2019-11-05 Ibasis, Inc. Voice over IMS roaming gateway
CN109429272B (zh) * 2017-08-31 2022-02-11 华为技术有限公司 一种漫游场景下的分流方法及相关设备
US11115330B2 (en) * 2018-03-14 2021-09-07 Juniper Networks, Inc. Assisted replication with multi-homing and local bias
CN114785626B (zh) 2018-06-26 2024-01-30 华为技术有限公司 数据管理的方法和装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1321047A (zh) * 2000-04-25 2001-11-07 阿尔卡塔尔公司 在主机和移动终端之间建立会话的方法及其设备

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1770915A1 (en) * 2005-09-29 2007-04-04 Matsushita Electric Industrial Co., Ltd. Policy control in the evolved system architecture
CN101286915B (zh) * 2008-06-11 2012-05-09 中兴通讯股份有限公司 分组数据网络的接入控制方法和系统、pcrf实体
US8832208B2 (en) * 2008-08-18 2014-09-09 Telefonaktiebolaget L M Ericsson (Publ) Handling of aggregate maximum bit rate by policy and charge control
CN101677437B (zh) 2008-09-18 2012-02-29 华为技术有限公司 多分组数据网场景下实现策略和计费控制的方法和系统
CN101931928B (zh) 2009-06-19 2014-08-13 中兴通讯股份有限公司 漫游场景下单apn多pdn连接的策略计费控制的方法及系统
CN101969673B (zh) * 2009-07-27 2013-08-07 中兴通讯股份有限公司 一种承载绑定和事件报告功能的重选方法
CN102014517A (zh) * 2009-09-08 2011-04-13 中兴通讯股份有限公司 漫游场景下承载控制模式的发送方法和系统

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1321047A (zh) * 2000-04-25 2001-11-07 阿尔卡塔尔公司 在主机和移动终端之间建立会话的方法及其设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Policy and Charging Control (PCC) over S9 reference point (stage 3) release 8", 3GPP TS 29.215 V8.0.2, 31 January 2009 (2009-01-31), pages 11, XP050372423, Retrieved from the Internet <URL:www.3gpp.org> *
"Policy and Charging Control signalling flows and QoS parameter mapping", 3GPP TS 29.213 V8.4.0, 31 May 2009 (2009-05-31), XP050372378, Retrieved from the Internet <URL:www.3gpp.org> *

Also Published As

Publication number Publication date
US9277592B2 (en) 2016-03-01
CN101959257B (zh) 2013-06-12
EP2458913B1 (en) 2019-02-20
EP2458913A1 (en) 2012-05-30
US20120110193A1 (en) 2012-05-03
EP2458913A4 (en) 2015-07-01
CN101959257A (zh) 2011-01-26

Similar Documents

Publication Publication Date Title
EP2458914B1 (en) Method for reselecting bearer binding and event report function
WO2011009257A1 (zh) 一种承载绑定和事件报告功能的重选系统及方法
US9137652B2 (en) Method for implementing policy and charging control in a roaming scene
US9351325B2 (en) Policy control method and system for converged network
US8799440B2 (en) Policy and charging control method and system for multi-PDN connections of single APN
WO2014056445A1 (zh) 一种路由转发的方法、系统及控制器
WO2009094837A1 (en) A method for selecting a policy and charging rules function server on a non-roaming scene
WO2009149642A1 (zh) 分组数据网络的接入控制方法和系统、pcrf实体
WO2010081329A1 (zh) 业务流迁移过程中对网络资源进行控制的方法和系统
WO2008101392A1 (fr) Procédé de transmission de qualité de service lors de transfert entre systèmes et système de réseau et réseau de destination correspondants
WO2010034195A1 (zh) 用户设备ip地址提供方法、diameter 路由代理
EP2557729A1 (en) Method and system for information transmission
WO2011006317A1 (zh) 删除家乡策略和计费规则功能冗余信息的方法及系统
WO2012006909A1 (zh) 一种上报固网接入信息的方法及系统
WO2011029289A1 (zh) 漫游场景下承载控制模式的发送方法和系统
WO2009046598A1 (fr) Procédé pour établir une porteuse dédiée pour un terminal utilisateur
WO2019225326A1 (ja) ユーザ装置、制御装置、及び通信制御方法
WO2010111944A1 (zh) 释放接入连接的方法、装置、策略控制实体及系统
WO2010054560A1 (zh) 一种实现多接入的方法及系统
WO2014056374A1 (zh) 会话建立方法、装置及系统
WO2011072438A1 (zh) 一种iwp场景下lbo处理方法、装置及系统
WO2012146092A1 (zh) 一种ip流迁移的策略控制方法及系统
WO2011134315A1 (zh) 业务授权方法、装置及系统
WO2011029349A1 (zh) 多承载绑定和事件报告功能的处理方法及系统
WO2016155011A1 (zh) 一种分组数据网关的选择方法、相关装置及系统

Legal Events

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

Ref document number: 09847492

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 13258893

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2009847492

Country of ref document: EP