WO2011011943A1 - Procédé pour la ré-sélection de fonction de liaison de support et de rapport d’événements - Google Patents

Procédé pour la ré-sélection de fonction de liaison de support et de rapport d’événements Download PDF

Info

Publication number
WO2011011943A1
WO2011011943A1 PCT/CN2009/075297 CN2009075297W WO2011011943A1 WO 2011011943 A1 WO2011011943 A1 WO 2011011943A1 CN 2009075297 W CN2009075297 W CN 2009075297W WO 2011011943 A1 WO2011011943 A1 WO 2011011943A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
pcrf
message
policy
gateway control
Prior art date
Application number
PCT/CN2009/075297
Other languages
English (en)
Chinese (zh)
Inventor
周晓云
宗在峰
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US13/258,184 priority Critical patent/US8943165B2/en
Priority to EP09847729.2A priority patent/EP2458914B1/fr
Publication of WO2011011943A1 publication Critical patent/WO2011011943A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0019—Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]

Definitions

  • the present invention relates to the field of communications, and in particular, to a method for reselecting bearer binding and event reporting functions.
  • 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 a related art; wherein, the MME is responsible for control planes such as mobility management, processing of non-access stratum signaling, and management of user mobility management context; S-GW is with E- UTRAN-connected access gateway device, used to forward data between E-UTRAN and P-GW, and is responsible for buffering paging waiting data; P-GW is EPS and packet data network (Packet Data Network, referred to as PDN) The border gateway of the network, responsible for PDN access and forwarding data between EPS and PDN.
  • PDN Packet Data Network
  • the EPS supports interworking with non-3GPP networks and implements interworking with non-3GPP networks through the S2a/b/c interface.
  • 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.
  • ePDG Evolved Packet Data Gateway
  • the PCRF performs policy and charging rules.
  • the PCRF connects to the operator's IP service network 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.
  • the establishment of an IP bearer guarantees the QoS (Quality of Service) of the service data and performs 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
  • S-GW S- The GW and the PCRF exchange information through the Gxc interface.
  • 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)
  • the Diameter application protocol is developed; for example, an application protocol applied to the Gx interface, an application protocol applied to the Rx interface, an application protocol applied to the Gxx interface (including the Gxa and Gxc interfaces), and an application protocol applied to the roaming interface S9.
  • Application protocols, etc. 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, gateway control 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-CAN IP Connectivity Access Network
  • Gx sessions Gx sessions
  • Gxx sessions gateway control sessions
  • S9 sessions S9 sessions for policy charging control of the same IP-CAN session.
  • the association operation is performed 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 flow chart of initial attachment 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 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 gateway control session (Gxx session) indicated by the message request is established. For Gxx session 1;
  • NAI Network Access Identifier
  • the access network bearer attributes include: an IP-CAN type and a BBERF address; and the access network bearer attribute may further include a RAT (Radio Access Technology) type.
  • RAT Radio Access Technology
  • Step S207 The PCRF obtains the subscription information of the user according to the user identifier NAI and the PDN identifier APN, so according to the subscription information of the user, the network policy, and the bearer attribute 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 setup confirmation message to the BBERF, and sends the formulated QoS rules and event triggers to the BBERF; the BBERF installs and executes the QoS rules and event triggers.
  • Step S208 The S-GW sends a proxy binding update message to the P-GW selected by the MME in step S205, 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 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 to be established 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 updating.
  • 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 flow chart of a UE switching 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 Figure 3 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 bearer attribute of the current access network (including the new IP-CAN). Type, new RAT type and new BBERF address), etc.; the gateway control session (Gxx session) requested by the message is represented as Gxx session 2;
  • Step S306 PCRF identifies GPN session 2 and map according to user identification NAI and PDN identification APN The Gx session 1 established in the process shown in 2 is associated;
  • Step S307 The PCRF formulates QoS rules and event triggers for the UE through non-3GPP access according to the user subscription information, the network policy, the bearer attribute of the current access network, and the like, where the UE includes the UE.
  • 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 user identifier NAI and the PDN identifier APN to keep the IP address unchanged, thereby ensuring continuity of the service;
  • IP Address 1 IP Address 1
  • the PCEF located in the P-GW sends an IP-CAN session modification indication message to the PCRF, where the message carries the new access network bearer attribute obtained in step S308; the message is modified by the Gx session 1 established in the process shown in FIG. .
  • 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 gateway control session (Gxx session) to an established PDN connection according to the user identity NAI and the PDN identity APN. (IP-CAN session), and then the PCRF can be used to transmit the UE through the 3GPP system, and the policy developed by the PCRF is updated according to the new access network bearer attribute, and then sent through the new gateway control session (Gxx session).
  • the new BBERF is given, so that before the handover of the PMIPv6 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 established 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).
  • the proprietary service accessed by the UE before the 3GPP access is interrupted, and the UE needs to re-initiate the service request.
  • the PCRF re-strategized 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 a home route 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 the existing The EPS roaming architecture diagram of the local grooming in the technology, as shown in Figure 5, the P-GW can provide IP services (that is, the AF home network) by the home network operator or the IP service of the visited network operator. (ie AF is visiting the network).
  • IP services that is, the AF home network
  • the PCC process is different, and the functions performed by the PCC network element are also different.
  • the Visiting PCRF terminates the Gx session and the gateway control session (Gxx session:) in the visited network of all IP-CAN sessions established by the UE.
  • the gateway control session (Gxx session:) and the Gx session are sent to the Home PCRF (Home PCRF, abbreviated as hPCRF), but an S9 session is established between the vPCRF and the hPCRF, and all IP-CANs are transmitted using this S9 session.
  • Session Gx session, gateway control session (Gxx session) information but does not terminate all IP-CAN sessions in the visited network Rx session, just forward the Rx session message to the home PCRF, the vPCRF as a proxy (Proxy).
  • the method for implementing the policy charging control session delay association in the roaming scenario and the method thereof are Policy charging control is difficult, and there is no corresponding solution in the prior art.
  • the technical problem to be solved by the present invention is to overcome the deficiencies of the prior art and provide an EPS diffuser.
  • the present invention provides a reselection method for a bearer binding and event reporting function, where the reselection method establishes a first network protocol IP connection access network IP for a user equipment UE in an evolved packet system EPS.
  • CAN session and after establishing the first gateway control session, the first Gx session, the S9 session, and the first subsession of the S9 session for policy control of the first IP-CAN session, for bearer binding and event reporting
  • the method includes:
  • a second gateway control session is established between the BBERF and the visited local policy and the charging rule function PCRF;
  • the home PCRF requests the modified first Gx session and the first subsession according to the session identification information. If the IP-CAN session establishment indication message sent by the PCEF is received, the home PCRF requests the IP-CAN session establishment indication message to be used for the second IP according to the session identification information included in the message. A second Gx session in which the CAN session performs policy control is associated with the first subsession;
  • the visited PCRF After establishing the second gateway control session, the visited PCRF associates the second gateway control session with the first subsession.
  • the step of establishing a second gateway control session between the destination BBERF and the visited PCRF includes:
  • the BBERF sends a gateway control session establishment indication message to the visited PCRF.
  • the visited PCRF After receiving the gateway control session establishment indication message, the visited PCRF includes the delay association indication, the session identification information, and the access network bearer attribute carried in the gateway control session establishment indication message in the S9 session modification indication message of the S9 session. Transmitted to the home PCRF;
  • the home PCRF After receiving the S9 session modification indication message, the home PCRF establishes a default quality of service QoS rule for the user according to the delay association indication, the session identification information, and the access network bearer attribute, and includes the S9 in the S9 session. Sending to the visited PCRF in the session modification confirmation message;
  • the visited PCRF After receiving the S9 session modification confirmation message, the visited PCRF is modified according to the S9 session.
  • the destination BBERF address included in the acknowledgement message is sent to the destination BBERF in the gateway control session setup acknowledgement message.
  • the method further includes:
  • the home PCRF sends the S9 session and the rule providing message of the first sub-session to the visited PCRF to indicate that the visited PCRF maintains the association relationship between the first sub-session and the first gateway control session;
  • the method further includes:
  • the home PCRF sends the S9 session and the rule providing message of the first sub-session to the visited PCRF to instruct the visited PCRF to release the association relationship between the first sub-session and the first gateway control session.
  • the method further includes:
  • the home location PCRF modifies the policy charging control PCC rules and QoS rules for the user
  • the PCC rule is sent to the PCEF through the IP-CAN session modification confirmation message of the first Gx session, and the QoS rule is sent to the visited PCRF through the S9 session and rule providing message, and the visited PCRF according to the S9 session And sending, by the destination BBERF address carried in the rule providing message, the QoS rule to the destination BBERF in the gateway control and QoS rule providing message of the second gateway control session; or
  • the method further includes:
  • the home PCRF sets a default PCC rule and a QoS rule for the user, sends the PCC rule to the PCEF through the IP-CAN session modification confirmation message of the second Gx session, and passes the QoS rule through the S9 session and rule.
  • the providing message is sent to the visited PCRF, and the visited PCRF sends the QoS rule to the destination BBERF in the gateway control and QoS rule providing message of 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, the reselection method establishing a first network protocol IP connection access network IP-CAN session for the user equipment UE in the evolved packet system EPS, and After 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, in a process for BBERF reselection, the method includes :
  • a second gateway control session is established between the BBERF and the visited local policy and charging rule function PCRF;
  • the visited PCRF controls the first Gx session and the second gateway that are modified by the IP-CAN session modification indication message according to the session identification information.
  • the session is associated with the first sub-session; or if the IP-CAN session establishment indication message sent by the PCEF is received, the visited PCRF requests the second Gx session established by the IP-CAN session establishment indication message according to the session identification information.
  • the second gateway control session is associated with the first subsession.
  • the method further includes:
  • the visited PCRF also obtains a policy that the home PCRF is modified for the user by using the first sub-session, and delivers the policy charging control PCC rule in the policy to the PCEF through the first Gx session, and passes the second
  • the gateway control session delivers the quality of service QoS rule in the policy to the destination BBERF; or
  • the method further includes:
  • the visited PCRF also obtains a default policy that is newly defined by the home PCRF through the first sub-session, and delivers the policy charging control PCC rule in the default policy to the PCEF through the second Gx session, and passes the The second gateway control session delivers the quality of service QoS rule in the default policy to the destination BBERF.
  • the method further includes:
  • the visited PCRF also obtains the policy that the home PCRF is modified by the user through the first subsession.
  • the policy charging control PCC rule in the policy is delivered to the PCEF through the first Gx session, and the corresponding quality of service QoS rule is determined according to the PCC rule, and the session is controlled to the destination BBERF by using the second gateway. Issuing the QoS rule; or
  • the method further includes:
  • the visited PCRF also obtains a default policy that is newly defined by the home PCRF through the first sub-session, and delivers the policy charging control PCC rule in the default policy to the PCEF through the second Gx session, and according to the The PCC rule sets a corresponding quality of service QoS rule, and the QoS rule is delivered to the destination BBERF through the second gateway control session.
  • the step of the visited PCRF acquiring the policy that the home PCRF is modified by the user includes: :
  • the visited PCRF sends an S9 session modification indication message carrying an execution indication to the home PCRF, where the execution indication is used to indicate that the home PCRF is a user modification policy; after receiving the S9 session modification indication message, the home PCRF is configured according to the location
  • the policy indicating that the execution instruction will be modified for the user is included in the S9 session modification confirmation message and sent to the visited PCRF; or
  • the step of the visited PCRF acquiring the home PCRF as the user's newly created default policy includes: :
  • the visited PCRF sends an S9 session modification indication message carrying an execution indication to the home PCRF, where the execution indication is used to indicate that the home PCRF establishes a default policy for the user; after receiving the S9 session modification indication message, the home PCRF is configured according to the The execution indication is to be sent to the visited PCRF in the S9 session modification confirmation message.
  • the step of establishing a second gateway control session between the destination BBERF and the visited PCRF includes:
  • the destination BBERF sends a gateway control session to the visited PCRF, where the gateway control session establishment indication 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 quality of service QoS rule corresponding to the session identification information according to the delay association indication, and performs the default QoS according to the access network bearer attribute.
  • 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 establishes a sub-session of the S9 session established before the UE handover and the destination BBERF and the visited PCRF according to the session identification information (including the user identifier, the PDN identifier, and the like) in the process of the BBERF reselection.
  • the gateway control session and the corresponding Gx session are associated, and the delayed association of the policy charging control session is implemented in the home routing and the local grooming roaming scenario.
  • FIG. 1 is a schematic diagram of a system architecture of an EPS in the related art
  • FIG. 2 is a flow chart of initial attachment of a UE to access an EPS through an E-UTRAN and establish a PDN connection
  • FIG. 3 is a diagram of a UE switching from an E-UTRAN to a trusted non-3GPP access system after accessing the EPS by using the procedure shown in FIG. Flow chart
  • FIG. 5 is a schematic diagram of an EPS roaming architecture for local grooming in the prior art
  • FIG. 6 is a flowchart of performing initial attach by E-UTRAN in a roaming scenario of a home-routed UE in a first embodiment of the present invention
  • FIG. 7a is a flowchart of a UE with network mobility capability according to the first embodiment of the present invention, after accessing the EPS by using the process shown in FIG. 6, and switching from accessing E-UTRAN access to accessing through trusted non-3GPP;
  • FIG. 7b is a flow diagram of a UE that does not have network mobility capability according to the first embodiment of the present invention, after accessing the EPS by using the process shown in FIG. 6, switching from accessing through E-UTRAN access to accessing through trusted non-3GPP;
  • FIG. 8 is a flowchart of performing initial attach by E-UTRAN in a local grooming roaming scenario according to a second embodiment of the present invention
  • FIG. 9a is a flowchart of a UE having network mobility capability according to a second embodiment of the present invention, after accessing an EPS by using the process shown in FIG. 8, switching from accessing through E-UTRAN access to accessing through trusted non-3GPP; and
  • FIG. 9b is a flow diagram of a UE that does not have network mobility capability according to the second embodiment of the present invention, after accessing the EPS by using the process shown in FIG. 8, switching from accessing through E-UTRAN access to accessing through trusted non-3GPP.
  • the core idea of the present invention is: In the process of BBERF reselection, the sub-session of the S9 session established before the UE handover and the destination BBERF and the visited PCRF are established according to the session identification information (including the user identifier, the PDN identifier, and the like).
  • the Gxx session is associated with the corresponding Gx session to enable a delayed association of the policy charging control session in the home routing and local grooming roaming scenarios.
  • FIG. 6 is a 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; Including 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 is requested to be established Gateway control session (Gxx session) is represented as Gxx session 1;
  • Step S607 The vPCRF determines that the corresponding user is a roaming user according to the user identifier 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. Relationship between session 1 and Subsession1, and including the user identifier NAI, the PDN identifier APN, and the bearer attribute of the current access network in Subsession1 and sent to the hPCRF;
  • Step S608 The hPCRF obtains the subscription information of the user according to the user identifier NAI and the PDN identifier 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, and the policy formulated by the hPCRF is the user accessing the APN.
  • Some default policies including PCC rules, QoS rules, and event triggers;
  • the hPCRF returns an S9 session setup confirmation message to the vPCRF, and the QoS rules and event triggers 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 update message to the P-GW selected by the MME in step S605, 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 S611 The P-GW allocates an IP address for the PDN connection (ie, IP-CAN session) that the UE requests to establish, which is represented as IP Address1.
  • IP-CAN session an IP address for the PDN connection
  • the P-GW is located in the home network, located at the P-GW.
  • the PCEF 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 user identifier NAI and the PDN identifier 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 updating.
  • 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 IP Address 1;
  • 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 interaction process between the MME and the S-GW to update 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 flowchart of a UE switching 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; wherein, when accessing through non-3GPP access 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 FIG. 7a 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 identity NAI, the PDN identity APN, and the new access network bearer attributes (IP-CAN type, RAT type, and BBERF). Address) and delay association indication;
  • the gateway control session (Gxx session) that the message requests to establish is represented as Gxx session 2;
  • Step S706 The vPCRF associates the Gxx session 2 with the subsession Subsession1 of the S9 session established in the process shown in FIG. 6 according to the user identifier NAI and the PDN identifier.
  • the vPCRF may also control the delay association indication included in the session establishment indication message according to the gateway. , the Gxx session 2 is not associated with the subsession Subsession1 of the S9 session established in the process shown in FIG. 6;
  • the vPCRF sends an S9 session modification indication message to the hPCRF according to the user identification NAI and the PDN identity APN, and sends a S9 session modification indication message to the hPCRF. If the vPCRF associates the Gxx session 2 with the Subsession1, the vPCRF carries the new access network bearer attribute and The delay association indication is sent to the hPCRF in the Subsession1; if there is no association, the vPCRF sends the new access network bearer attribute and the delay association indication to the hPCRF at the S9 session level; the S9 session modification indication message may also carry the user identifier NAI and The PDN identifies the APN.
  • Step S707 After receiving the S9 session modification indication message, the hPCRF cancels the association relationship between the Subsession1 and the Gx session 1 established in the process shown in FIG. 6 according to the delay association indication; the hPCRF is based on the user subscription information, the network policy, and the new access network bearer.
  • the attributes are such that the UE formulates QoS rules and event triggers through non-3GPP access. These rules are the default policies of the user, and do not include the policies of the proprietary services previously accessed by the user; hPCRF sets the QoS rules, event triggers, and new BBERF addresses.
  • Step S708 After receiving the S9 session modification confirmation message, the vPCRF determines, according to the address of the new BBERF, that the QoS rule and the event trigger in the message are sent to the BBERF in the trusted non-3GPP access gateway, so the vPCRF passes the Gxx session 2
  • the gateway control session establishment acknowledgement message sends the above QoS rules and event triggers to the BBERF in the trusted non-3GPP access gateway; the BBERF installs and executes the QoS rules and event triggers; the trusted non-3GPP access network Performing 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 Address 1) used by the 3GPP to the UE according to the user identifier NAI and the PDN identity APN to keep the IP address unchanged, thereby ensuring continuity of the service; PCEF direction at the P-GW
  • IP Address 1 IP Address 1
  • the hPCRF sends an IP-CAN session modification indication message, where the message carries a new access network bearer attribute (including IP-CAN type, or IP-CAN type and RAT type); in addition, the message may also carry the user identifier NAI and The PDN identifies information such as APN; this message modifies the Gx session 1 established in FIG. 6.
  • Step S711 The hPCRF determines, according to the IP-CAN session modification indication message sent by the PCEF, that the UE can perform the handover procedure, and then re-associates the Subsession1 with the Gx session 1; the access network bearer attributes (including the IP-CAN type carried in the message) , or the IP-CAN type and the RAT type) are consistent with the reported information in step S706;
  • Step S712 The hPCRF may modify 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. These rules include the proprietary services that the UE accesses when accessing through the 3GPP.
  • 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;
  • 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 includes the QoS rule and the event trigger defined in step S712 in the Subsession1, and sends the message to the vPCRF through the S9 session and the rule providing message; the Subsession1 also includes the address of the new BBERF to indicate the QoS rule and the event trigger. Is sent to Trusting the BBERF in the non-3GPP access gateway; at the same time, the hPCRF also sends an execution indication to the vPCRF to notify the vPCRF to perform the handover procedure;
  • the execution indication may not be carried in this message.
  • Step S716 The vPCRF learns to perform the handover procedure (indicating the handover according to the issued execution indication or the default non-delivery execution indication). If the Gxx session 2 and the Subsession1 established in the step S705 are not associated in step S706, the vPCRF will perform the Gxx session. 2 Associate with Subsession1; vPCRF sends QoS rules and event triggers to the BBERF in the trusted non-3GPP access gateway through the gateway control and QoS rule provisioning message of Gxx session 2 according to the address of the new BBERF; The relationship between Gxx session 1, Gxx session 2 and Subsessionl;
  • Step S717 The BBERF in the trusted non-3GPP access gateway returns a gateway control and QoS rule providing acknowledgement message after installing the QoS rule and the event trigger; 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 providing acknowledgement message to the hPCRF; and step S719: the UE switches the PDN connection from the 3GPP access to the trusted non-3GPP access, in the trusted non-3GPP access gateway and the P-GW There is a PMIPv6 tunnel (the PMIPv6 tunnel is established through steps S709 and S713); the services accessed by the UE when accessing through the 3GPP can continue to access.
  • 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:
  • Step S701 '-S709' same as steps S701 to S709;
  • 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, where the message carries the user identity NAL PDN identifier APN, IP Address2, and new access network bearer attributes (package) Including IP-CAN type, or IP-CAN type and RAT type); This 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 Subsessionl is identified according to the user identifier NAI and the PDN identifier APN. Associated with Gx Session 2;
  • 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 the hPCRF sends an S9 session and a rule providing message carrying the Subsession1 of the execution indication to the vPCRF, and the execution indication is used to notify the vPCRF to perform the new PDN connection process; if the QoS rule and the event trigger established in step S712' are formulated with the step S707' The difference between the hPCRF and the QoS rules and event triggers specified in step 712' are sent to the vPCRF in Subsession1;
  • Step S716' After receiving the S9 session and the rule providing message, if the step S706' does not associate the Gxx session 2 and the Subsession1 established in the step S705', the vPCRF associates the Gxx session 2 with the Subsession1; the vPCRF is in accordance with the execution indication. Dissolving the association between Gxx session 1 and Subsession1; the vPCRF sends the QoS rule to the BBERF in the trusted non-3GPP access gateway through the gateway control and QoS rule provisioning message of the Gxx session 2;
  • Step S717' The BBERF installation in the trusted non-3GPP access gateway performs QoS rules and event triggers, and returns a gateway control and QoS rule providing acknowledgement message to the vPCRF; the trusted non-3GPP access gateway performs specific non-3GPP access The process performs resource reservation; Step S718,: the vPCRF returns an S9 session and rule providing confirmation message to the hPCRF; and step S719': the UE newly establishes a PDN connection (ie, an IP-CAN session) through the trusted non-3GPP access network, and the trusted non-3GPP connection There is a PMIPv6 tunnel between the ingress 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.
  • a PDN connection ie, an IP-CAN session
  • This embodiment is equally applicable to a UE switching from one trusted non-3GPP access network to another trusted non-3GPP access network.
  • the PMIPv6 protocol is used between the trusted non-3GPP access gateway and the P-GW.
  • FIG. 8 is a flowchart of performing initial attach by E-UTRAN in a local grooming roaming scenario according to a second embodiment of the present invention; wherein the PM-IPv6 protocol is used between the S-GW and the P-GW; Including 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 procedure.
  • Default bearer request message
  • Step S806 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 gateway control session (Gxx session) requested by the message is represented as Gxx session 1;
  • Step S807 The vPCRF determines that the corresponding user is a roaming user according to the user identifier 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.
  • the relationship between session 1 and Subsession1, and the bearer attributes of the NAI, APN, and the current access network are included in Subsession1 and sent to the hPCRF;
  • Step S808 The hPCRF acquires the user's subscription according to the user identifier NAI and the PDN identifier APN.
  • the information is used to formulate a policy according to the user's subscription information, the network policy, and the bearer attribute of the current access network.
  • the hPCRF policy 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 setup confirmation message to the vPCRF, and the QoS rules and event triggers 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 the Subsession1 and sent to the 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 BBERF for update.
  • Step S815 The vPCRF sends an IP-CAN session establishment confirmation message of the Gx session 1 to the PCEF, and sends the PCC rule and the event trigger to the PCEF; the PCEF installs and executes the PCC rule and the event trigger;
  • Step S816 The P-GW returns a proxy binding acknowledgement message to the S-GW, where the message carries the 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 interaction process between the MME and the S-GW to update 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. 9a is a flowchart of a UE switching 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; wherein, when accessing through non-3GPP access 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 FIG. 9a 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.
  • the established gateway control session (Gxx session) is represented as Gxx session 2;
  • Step S906 The vPCRF associates the Gxx session 2 to the Subsession1 according to the NAI and the APN; the vPCRF may also carry the delay association indication according to the gateway control session establishment indication message, and does not associate the Gxx session 2 with the subsession of any S9 session; the vPCRF is associated according to the delay Instructing to release the association relationship between Subsession1 and Gx session 1; since the roaming mode of the UE is local grooming, the vPCRF searches for the default QoS rule and event trigger sent by the hPCRF in the process described in FIG. 8 according to the NAI and the APN, according to the new access.
  • the network bearer attribute is modified correspondingly to the default QoS rule and the event trigger sent by the hPCRF in FIG. 8, and the modified QoS rule and the event trigger are included in the gateway control session establishment confirmation message of the Gxx session 2.
  • 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, 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 S908 If the P-GW determines that the UE has network mobility capability (ie, IP address retention capability), the P-GW performs a handover process of the UE:
  • the P-GW allocates the IP address (IP Address 1) used by the 3GPP to the UE according to the user identifier NAI and the PDN identity APN to keep the IP address unchanged, thereby ensuring continuity of the service; PCEF direction at the P-GW
  • IP Address 1 IP Address 1
  • NAI user identifier
  • PDN identity APN IP address 1
  • the vPCRF sends an IP-CAN session modification indication message, where the message carries the current access network bearer attribute (including IP-CAN type, or IP-CAN type and RAT type); the message is modified by the Gx session 1 established in FIG. .
  • Step S909 The vPCRF determines, according to the received IP-CAN session modification indication message, that the UE can perform the handover procedure, and the vPCRF associates the Gxx session 2 and the Gx session 1 established in step S905 according to the user identifier NAI and the PDN identifier APN, while maintaining the Gxx session. 1 and Gx session 1 association; if the Gxx session 2 is not associated with the S9 session subsession in step S906, vPCRF associates Gxx Session 2 with Subsession1;
  • Step S910 The vPCRF sends an S9 session modification indication message including Subsession1 to the hPCRF, and the new access network bearer attributes (IP-CAN type, RAT type, and BBERF address) are included in the Subsession1 and sent to the hPCRF; Carrying an execution indication, configured to notify the hPCRF to perform a handover process;
  • IP-CAN type, RAT type, and BBERF address the new access network bearer attributes
  • the execution indication may not be carried in this message.
  • Step S911 The hPCRF learns to perform the handover procedure (indicating the handover according to the delivered execution indication or the default non-delivery execution indication), and therefore the PCC rule and the QoS rule of the PDN connection established before the UE handover according to the new access network bearer attribute. And the event trigger is modified.
  • These policies include the policy that the user accesses the proprietary service in the 3GPP access; the hPCRF includes the modified PCC rule, the QoS rule, and the event trigger in the Subsession1 and sends the confirmation message to the vPCRF through the S9 session modification.
  • Subsessionl also includes a new BBERF address to indicate that the QoS rules and event triggers are sent to the BBERF in the trusted non-3GPP access gateway;
  • 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 IP Address 1;
  • 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 according to the address of the new BBERF;
  • Step S916 The BBERF installation in the trusted non-3GPP access gateway performs QoS rules and event triggers, and returns a gateway control and QoS rule provision confirmation message to the vPCRF; the trusted non-3GPP access gateway performs a specific non-3GPP access procedure. Make resource reservations; and
  • 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) The tunnel is established through steps S907 and S913); the UE can continue to access the proprietary services accessed when accessing through the 3GPP.
  • the hPCRF only formulates/modifies the PCC rules without formulating/modifying the QoS rules; in this case, the corresponding QoS rules are formulated by the vPCRF according to the PCC rules delivered by the hPCRF, and are issued. Give 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:
  • Step S90 ⁇ ⁇ S907 ' is the same as steps S901 to S907;
  • 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 that the UE cannot perform the handover procedure according to the received IP-CAN session establishment indication message, but creates a new PDN connection in the trusted non-3GPP access gateway, and the vPCRF identifies the APN according to the user identifier NAI, PDN.
  • Session 2 is associated with Gx Session 2, and vPCRF releases the association relationship between Subsession1 and Gxx Session 1, Gx Session 1; if Step S906' does not associate Gxx Session 2 with S9 Session Subsession, then vPCRF will Gxx Session 2 and Subsessionl Make an association;
  • Step S910' The vPCRF sends an S9 session modification indication message to the hPCRF, and the new access network bearer attribute and the IP address2 are included in the Subsession1 and sent to the hPCRF.
  • the message further carries an execution indication, and is used to notify the hPCRF to perform a new PDN connection.
  • 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 in the trusted non-3GPP access gateway performs QoS rules and event triggers, and returns a gateway control and QoS rule providing acknowledgement message to the vPCRF; the trusted non-3GPP access gateway performs specific non-3GPP access The process performs 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.
  • 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, it is sent 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 invention controls the gateway control session established between the sub-session of the S9 session established before the UE handover and the destination BBERF and the visited PCRF according to the session identification information (including the user identifier, the PDN identifier, and the like) in the process of the BBERF reselection.
  • the corresponding Gx session is associated, and the delayed association of the policy charging control session is implemented in the home routing and local grooming roaming scenarios.

Landscapes

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

Abstract

La présente invention concerne un procédé pour la ré-sélection de fonction de liaison de support et de rapport d’événements (BBERF). Le procédé est utilisé dans un système de paquets évolué (EPS) suite à l’établissement de la première session de réseau d’accès de connectivité (IP-CAN) de protocole Internet (IP) pour un équipement utilisateur (UE) et à l’établissement de la première session de commande de passerelle, de la première session Gx, de la session s9 et de la première sous-session de la session s9, qui effectuent la commande de règle sur la première session IP-CAN. Lors de la ré-sélection de la fonction BBERF, sur la base de l’information d’identifiant de session, la présente invention peut associer la sous-session de la session s9 établie avant la commutation de l’équipement utilisateur à une session de commande de passerelle établie entre une fonction BBERF de destination et une fonction de politiques et de règles de facturation de visite (PCRF) et une session Gx correspondante, permettant ainsi la réalisation d’une liaison différée dans un scénario d’itinérance de route locale et d’acheminement local.
PCT/CN2009/075297 2009-07-27 2009-12-03 Procédé pour la ré-sélection de fonction de liaison de support et de rapport d’événements WO2011011943A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US13/258,184 US8943165B2 (en) 2009-07-27 2009-12-03 Method for reselecting bearer binding and event report function
EP09847729.2A EP2458914B1 (fr) 2009-07-27 2009-12-03 Procédé pour la ré-sélection de fonction de liaison de support et de rapport d événements

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910150199.5 2009-07-27
CN2009101501995A CN101969673B (zh) 2009-07-27 2009-07-27 一种承载绑定和事件报告功能的重选方法

Publications (1)

Publication Number Publication Date
WO2011011943A1 true WO2011011943A1 (fr) 2011-02-03

Family

ID=43528707

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/075297 WO2011011943A1 (fr) 2009-07-27 2009-12-03 Procédé pour la ré-sélection de fonction de liaison de support et de rapport d’événements

Country Status (4)

Country Link
US (1) US8943165B2 (fr)
EP (1) EP2458914B1 (fr)
CN (1) CN101969673B (fr)
WO (1) WO2011011943A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103718504A (zh) * 2012-06-30 2014-04-09 华为技术有限公司 一种网关计费处理方法及网关

Families Citing this family (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2782388B1 (fr) * 2009-03-23 2016-05-18 Telefonaktiebolaget LM Ericsson (publ) Mèthode et appareils pour retarder leg linking dans PCRF en cours de transfert intercellulaire
CN101931928B (zh) * 2009-06-19 2014-08-13 中兴通讯股份有限公司 漫游场景下单apn多pdn连接的策略计费控制的方法及系统
CN101959257B (zh) 2009-07-20 2013-06-12 中兴通讯股份有限公司 一种承载绑定和事件报告功能的重选方法
US8768295B2 (en) 2010-02-18 2014-07-01 Alcatel Lucent Method of handling a change to bearer control mode
CN102769933B (zh) * 2011-05-06 2017-05-17 中兴通讯股份有限公司 一种策略会话删除方法及其系统
CN104247343A (zh) * 2012-04-27 2014-12-24 日本电气株式会社 通信系统以及用于路径控制的方法
US9439118B2 (en) * 2012-07-23 2016-09-06 Qualcomm Incorporated Systems and methods supporting WLAN-WWAN mobility in devices
CN103582163B (zh) * 2012-08-01 2018-10-23 中兴通讯股份有限公司 承载处理方法、承载释放方法、装置及系统
US9596621B2 (en) 2012-08-10 2017-03-14 Ibasis, Inc. Signaling traffic reduction in mobile communication systems
US20140050098A1 (en) * 2012-08-14 2014-02-20 Alcatel-Lucent Canada, Inc. Handling session linking status in gxx update
US9735971B2 (en) * 2012-09-17 2017-08-15 Telefonaktiebolaget Lm Ericsson (Publ) High-availability, scalable policy and charging control systems, and methods therefor
WO2014054014A1 (fr) * 2012-10-02 2014-04-10 Telefonaktiebolaget L M Ericsson (Publ) Procédé et dispositif pour la prise en charge de plusieurs connexions pdn
US9788188B2 (en) 2012-12-14 2017-10-10 Ibasis, Inc. Method and system for hub breakout roaming
CN104956762B (zh) * 2013-02-01 2019-10-08 瑞典爱立信有限公司 使用pcrf节点与移动性管理节点之间的直接连接的移动网关选择
CN103701597B (zh) * 2013-11-29 2016-11-16 中国电子科技集团公司第三十研究所 一种可信分组验证的控制方法
EP3117686B1 (fr) 2014-03-12 2017-12-20 British Telecommunications Public Limited Company Passerelle d'accès sans fil
WO2016206071A1 (fr) * 2015-06-26 2016-12-29 华为技术有限公司 Procédé de liaison de porteuse et équipement associé
US10470031B2 (en) 2016-05-20 2019-11-05 Ibasis, Inc. Voice over IMS roaming gateway
JP6777451B2 (ja) * 2016-08-10 2020-10-28 株式会社Ｎｔｔドコモ 基地局
CN110073694B (zh) * 2016-12-16 2022-04-01 诺基亚技术有限公司 向ran提供切换阈值
US10104604B2 (en) * 2016-12-30 2018-10-16 Alcatel Lucent S9 roaming session destination selection
US11082881B2 (en) * 2018-04-05 2021-08-03 At&T Intellectual Property I, L.P. Dynamic quality of service setting system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008096258A1 (fr) * 2007-02-09 2008-08-14 Telefonaktiebolaget Lm Ericsson (Publ) Système et procédé pour une allocation de porteuse dynamique
CN101286915A (zh) * 2008-06-11 2008-10-15 中兴通讯股份有限公司 分组数据网络的接入控制方法和系统、pcrf实体
CN101459951A (zh) * 2008-04-11 2009-06-17 中兴通讯股份有限公司 一种承载绑定和事件报告功能策略控制的方法及系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1150521A1 (fr) * 2000-04-25 2001-10-31 Alcatel Méthode pour l'établissement d'une session entre un serveur d'un réseau de données et un terminal mobile d'un réseau mobile ainsi que dispositif pour la mise en oeuvre de cette méthode
CN101394449B (zh) * 2007-09-19 2011-01-19 华为技术有限公司 一种会话修改方法及系统
CN101646149B (zh) * 2008-08-07 2012-09-05 中兴通讯股份有限公司 一种删除dra中会话信息的方法
CN101583112B (zh) * 2008-08-12 2011-09-21 中兴通讯股份有限公司 会话信息的标识方法及装置
CN101931928B (zh) * 2009-06-19 2014-08-13 中兴通讯股份有限公司 漫游场景下单apn多pdn连接的策略计费控制的方法及系统
CN101959257B (zh) * 2009-07-20 2013-06-12 中兴通讯股份有限公司 一种承载绑定和事件报告功能的重选方法
CN101969632B (zh) * 2009-07-28 2013-06-05 中兴通讯股份有限公司 一种漫游场景下的策略计费控制实现方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008096258A1 (fr) * 2007-02-09 2008-08-14 Telefonaktiebolaget Lm Ericsson (Publ) Système et procédé pour une allocation de porteuse dynamique
CN101459951A (zh) * 2008-04-11 2009-06-17 中兴通讯股份有限公司 一种承载绑定和事件报告功能策略控制的方法及系统
CN101286915A (zh) * 2008-06-11 2008-10-15 中兴通讯股份有限公司 分组数据网络的接入控制方法和系统、pcrf实体

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2458914A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103718504A (zh) * 2012-06-30 2014-04-09 华为技术有限公司 一种网关计费处理方法及网关
US9319536B2 (en) 2012-06-30 2016-04-19 Huawei Technologies Co., Ltd. Processing method of gateway charging and gateway
CN103718504B (zh) * 2012-06-30 2016-11-09 华为技术有限公司 一种网关计费处理方法及网关

Also Published As

Publication number Publication date
CN101969673B (zh) 2013-08-07
US20120117251A1 (en) 2012-05-10
EP2458914A4 (fr) 2014-09-10
EP2458914B1 (fr) 2017-11-01
EP2458914A1 (fr) 2012-05-30
US8943165B2 (en) 2015-01-27
CN101969673A (zh) 2011-02-09

Similar Documents

Publication Publication Date Title
WO2011011943A1 (fr) Procédé pour la ré-sélection de fonction de liaison de support et de rapport d’événements
EP2458913B1 (fr) Système de resélection pour fonction de liaison de porteuse et de rapport d'événement et procédé associé
US9137652B2 (en) Method for implementing policy and charging control in a roaming scene
US9351325B2 (en) Policy control method and system for converged network
US8849273B2 (en) Method and system for reporting fixed network access information
WO2014056445A1 (fr) Procédé, système et contrôleur pour transfert de routage
WO2009094837A1 (fr) Procédé de sélection d'un serveur à fonction de règles de politiques et de facturation dans une situation sans itinérance
WO2011006317A1 (fr) Procédé et système permettant d'effacer des informations redondantes d'une fonction d’imputation et de règles domestique
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
WO2010081329A1 (fr) Procédé et système pour réguler des ressources de réseau pendant une procédure de migration de flux de services
EP2557729A1 (fr) Procédé et système de transmission d'informations
WO2010034195A1 (fr) Procédé pour obtenir l'adresse ip d'un équipement d'utilisateur, d'un agent de routage diameter
WO2011029289A1 (fr) Procédé et système de transmission d'un mode de commande de support dans des scénarios d'itinérance
WO2014173340A1 (fr) Procédé et dispositif de politique de facturation d'autorisation d'abonnement interréseau
WO2009046598A1 (fr) Procédé pour établir une porteuse dédiée pour un terminal utilisateur
WO2012003770A1 (fr) Système, dispositif et procédé permettant à un équipement utilisateur d'accéder à un réseau mobile
EP2884802A1 (fr) Procédé et système de notification d'informations de position dans un réseau d'accès
WO2010111944A1 (fr) Procédé, appareil, fonction de commande de politique et système destinés à libérer des connexions d'accès
WO2011072438A1 (fr) Procédé, dispositif et système de traitement de sortie de zone locale dans un scénario de serveur proxy d'interfonctionnement
WO2012146092A1 (fr) Procédé et système de contrôle de politique pour mesurer la mobilité d'un flux ip
WO2011029349A1 (fr) Procédé et système de traitement de multiples fonctions d'association de support et de rapport d'événement
WO2011134315A1 (fr) Procédé, dispositif et système pour une autorisation de service
WO2013152655A1 (fr) Procédé et système de contrôle de politique dans un réseau de convergence
WO2012171425A1 (fr) Procédé et dispositif de traitement de service
WO2013023515A1 (fr) Procédé et système permettant de résoudre un conflit de contrôle de la politique de qualité de service

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: 09847729

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 13258184

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2009847729

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2009847729

Country of ref document: EP