WO2009124436A1 - Procédé et système de contrôle de politique bberf - Google Patents

Procédé et système de contrôle de politique bberf Download PDF

Info

Publication number
WO2009124436A1
WO2009124436A1 PCT/CN2008/071720 CN2008071720W WO2009124436A1 WO 2009124436 A1 WO2009124436 A1 WO 2009124436A1 CN 2008071720 W CN2008071720 W CN 2008071720W WO 2009124436 A1 WO2009124436 A1 WO 2009124436A1
Authority
WO
WIPO (PCT)
Prior art keywords
control information
identifier
policy control
session
access network
Prior art date
Application number
PCT/CN2008/071720
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 中兴通讯股份有限公司
Publication of WO2009124436A1 publication Critical patent/WO2009124436A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/20—Traffic policing

Definitions

  • EPS Evolved Packet System
  • the 3GPP EPS is composed of E-UTRAN (Evolved Universal Terrestrial Radio Access Network), MME (Mobility Management Entity), and S-GW (Serving Gateway, service). Gateway), P-GW (Packet Data Network Gateway), HSS (Home Subscriber Server, Home Subscriber Server), 3GPP AAA Server (3GPP Authentication and Authorization Accounting Server), PCRF (Policy and Charging Rules Function) And the charging rule function) entity and other supporting nodes.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • MME Mobility Management Entity
  • S-GW Serving Gateway, service.
  • P-GW Packet Data Network Gateway
  • HSS Home Subscriber Server, Home Subscriber Server
  • 3GPP AAA Server 3GPP Authentication and Authorization Accounting Server
  • PCRF Policy and Charging Rules Function
  • the S-GW is an access gateway device connected to the E-UTRAN, and forwards data between the E-UTRAN and the P-GW, and is responsible for buffering paging waiting data;
  • the P-GW is EPS and PDN (Packet)
  • the border gateway of the Data Network (Packet Data Network) is responsible for accessing the PDN and forwarding data between the EPS and the PDN.
  • the PCRF accesses the service network of the carrier IP (Internet Protocol) through the Rx interface to obtain service information.
  • the gateway device in the 3GPP network is connected to the gateway device in the 3GPP network through the S7/S7a/S7b/S7c 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 gateway device in the 3GPP network through the S7/S7a/S7b/S7c 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.
  • QoS Quality of Service
  • EPS supports interworking with non-3GPP networks. Interworking with non-3GPP networks is implemented through the S2a/b/c interface, and the P-GW acts as an anchor between the 3GPP network and the non-3GPP network.
  • Non-3GPP networks include trusted non-3GPP networks and untrusted non-3GPP networks. The IP access of the trusted non-3GPP network can be directly connected to the P-GW through the S2a; the IP access of the untrusted non-3GPP network needs to be connected to the P-GW through the EPDG (Evolved Packet Data Gateway), ePDG and The interface between the P-GWs is S2b.
  • EPDG Evolved Packet Data Gateway
  • the UE User Equipment
  • the P-GW can also directly connect to the P-GW through the S2c interface using the DSMIPv6 ( Dual Stack Mobile IPv6) protocol.
  • the PCEF Policy and Charging Enforcement Function
  • the PCRF exchanges information with the P-GW through the S7 interface.
  • the S-GW also has a policy control function, which is called BBERF (Bearer Binding and Event Reporting Function), S-GW.
  • BBERF Bit Binding and Event Reporting Function
  • the BBERF When the user equipment accesses through the trusted non-3GPP network, the BBERF is also present in the trusted non-3GPP access network, and the trusted non-3GPP network access gateway exchanges information with the PCRF through the S7a interface.
  • the BBERF exists in the ePDG, and the ePDG exchanges information with the PCRF through the S7b interface.
  • the S9 interface acts as an interface between the home PCRF and the visited PCRF.
  • the AF Application Function
  • the AF Application Function
  • the AF Application Function
  • MIPv6 (Moblie IPv6) supports the accessibility and continuity of the session when the MN moves in the network by binding the IPv6 care-of address of the mobile node MN (Mobile Node) to the IPv6 home address HoA.
  • IPv6 MNs tend to move to networks that do not support IPv6, so MIPv6 must be extended.
  • DSMIPv6 is an effective solution. It is a client-based MIP protocol that requires both the mobile node MN and the home agent Home Agent to support DSMIPv6. MNs that support DSMIPv6 are handed over through their IPv4/IPv6
  • the EPS system supports multiple PDN access, that is, the UE can access multiple PDNs simultaneously through multiple P-GWs or one P-GW.
  • FIG. 2 is a scenario diagram of a UE accessing two PDNs through two P-GWs at the same time and using a DSMIPv6 protocol by the UE.
  • FIG. 3 is a flow chart of the initial attachment of the UE based on the scenario in FIG. 2, and the specific steps are as follows:
  • Step 301 The user equipment accesses the trusted non-3GPP access network through the layer 2, and the HSS/AAA performs access authentication and authorization on the UE.
  • Step 302 After the authentication succeeds, establish a layer 3 connection between the UE and the trusted non-3GPP access system; the access system allocates an IP address to the UE as the care-of address CoA of the UE;
  • Step 303 The trusted non-3GPP access network sends a "gateway control session establishment" to the PCRF.
  • the message carries the NAI (Network Access Identifier) and the care-of address CoA of the UE;
  • Step 304 The PCRF formulates a control policy, that is, a QoS rule, based on the network policy and the subscription information of the UE, and sends the message to the trusted non-3GPP access network through a "Gateway Control Session Establishment Confirmation" message, where the control policy and the UE are to be accessed.
  • a control policy that is, a QoS rule, based on the network policy and the subscription information of the UE, and sends the message to the trusted non-3GPP access network through a "Gateway Control Session Establishment Confirmation" message, where the control policy and the UE are to be accessed.
  • Business has nothing to do;
  • Step 305 The UE performs a DNS (Domain Name Server) query according to the APN (Access Point Name) to obtain an IP address of the P-GW1 that provides the access service network 1, and establishes an IP address between the UE and the P-GW1.
  • APN Access Point Name
  • P-GW1 assigns the home address HoAl to the UE;
  • Step 306 The UE sends a "Binding Update" request message to the P-GW1, where the message carries CoA and HoAl;
  • Step 307 The P-GW1 sends an "IP-CAN Session Establishment Indication" message to the PCRF, where the message carries CoA, HoAl, NAI, and APN1, and the PCRF associates the session with the gateway control session according to the CoA;
  • Step 308 The PCRF formulates corresponding PCC rules and event triggers according to the network policy, the user subscription, and the information of the service network 1 to be accessed, and sends the message to the P-GW1 through the "IP-CAN session establishment confirmation" message;
  • Step 309 P-GW1 returns a "Binding Confirmation" message to the UE;
  • Step 310 The PCRF modifies the previous QoS rule according to the network policy, the user subscription, and the information of the service network 1 to be accessed, and formulates an event trigger, and sends the message to the trusted non-"through the "gateway control and QoS rule provision” message.
  • 3GPP access network
  • Step 311 The trusted non-3GPP access network returns a "gateway control and QoS rule provision confirmation" message to the P-GW1;
  • Step 312 When the UE determines to access the service network 2, perform a DNS query according to the APN2, and obtain an IP address of the P-GW2 that provides the access service network 2.
  • Step 313 A security association is established between the UE and the P-GW2.
  • the P-GW2 is The UE allocates the home address HoA2;
  • Step 314 The UE sends a "Binding Update" request message to the P-GW2, where the message carries CoA and HoA2;
  • Step 315 The P-GW2 sends a ' ⁇ -CAN session establishment indication' message to the PCRF, where the message carries CoA, HoA2, NAI, and APN2, and the PCRF associates the session with the gateway control session according to the CoA;
  • Step 316 The PCRF formulates corresponding PCC rules and event triggers according to the network policy, the user subscription, and the information of the service network 2 to be accessed, and sends the message to the P-GW2 through the "IP-CAN session establishment confirmation" message;
  • Step 317 P-GW2 returns a "binding confirmation" message to the UE;
  • Step 318 The PCRF formulates QoS rules and event triggers according to the network policy, the user subscription, and the information of the service network 2 to be accessed, and sends the message to the trusted non-3GPP access network through the "gateway control and QoS rule provisioning" message.
  • Step 319 The trusted non-3GPP access network returns a "Gateway Control and QoS Rule Provide Confirmation" message to the P-GW2.
  • the QoS rule is modified in step 310, and the PCRF already has the information of the service network 2 at step 318, so the QoS rule can be directly specified.
  • the UE establishes two IP connections to the service network 1 and the service network 2, respectively.
  • This IP connection from the UE to the service network is called an IP-CAN (IP Connectivity Access Network) session.
  • IP-CAN IP Connectivity Access Network
  • the PCRF establishes a Diameter session with the trusted non-3GPP access network (in the prior art, the Diameter protocol is used to establish this connection, and the context of the Diameter session is saved in the PCRF and the trusted non-3GPP access network), P-GW1.
  • P-GW2 establishes a Diameter session with the PCRF, respectively.
  • the PCRF delivers the PCC or QoS rules and event triggers for policy charging control of the IP-CAN session 1 through the Diameter session between the trusted non-3GPP access network and the PCRF and the Diameter session between the P-GW1 and the PCRF. Give the relevant gateway.
  • the same PCRF passes the trusted non The Diameter session between the 3GPP access network and the PCRF and the Diameter session between the P-GW2 and the PCRF deliver the PCC or QoS rules and triggers for policy charging control of the IP-CAN session 2 to the associated gateway. It is not difficult to see from the above analysis that the Diamter session between the P-GW and the PCRF is one-to-one with the IP-CAN session.
  • the P-GW can determine Which policy information is related to which IP-CAN session.
  • the Diamter session and the IP-CAN session between the trusted non-3GPP access network and the PCRF are one-to-many.
  • the PCRF sends the policy information to the trusted non-3GPP access network through the Diameter session the trusted non- The 3GPP access network is unable to determine which IP-CAN session these policy information is associated with. This can lead to errors in policy control.
  • the PCRF issues a QoS rule for policy control of IP-CAN session 1 to a trusted non-3GPP access network, and the trusted non-3GPP access network controls the service data flow after installing the QoS rule;
  • a QoS rule for controlling the IP-CAN session 2 is sent to the trusted non-3GPP access network.
  • the trusted non-3GPP access network considers the update of the previously issued QoS rule, resulting in an error in the policy control. . Of course, this kind of error will also occur when the event trigger is updated.
  • the PCRF When the UE decides to disconnect from the service network 1, the PCRF must inform the BBERF to delete or deactivate all policy control information associated with the IP-CAN Session 1, while retaining the policy control information associated with the IP-CAN Session 2. BBERF does not know which IP-CAN session-related policy control information to delete or deactivate. Summary of the invention
  • the technical problem to be solved by the present invention is to provide a method and system for carrying out bearer binding and event reporting function policy control.
  • the bearer binding and event reporting functions can be Differentiate the policy control information of each IP-CAN session to perform correct policy control on the service data flow.
  • the present invention provides a method for controlling bearer binding and event reporting function, including:
  • the policy and charging rule function entity PCRF sends the policy control information and the identifier to the bearer binding and event reporting function entity BBERF.
  • the identifier is used to indicate the policy control letter
  • the IP-related access network session, where the policy control information is used to indicate an operation of the IP connection access network session indicated by the identifier and an operation object;
  • the BBERF After receiving the policy control information and the identifier, the BBERF binds the policy control information to a corresponding IP connection access network session according to the identifier, and performs a corresponding operation according to the policy control information.
  • the operation indicated by the policy control information refers to one or more of the following operations: installing, activating, updating, deleting, deactivating;
  • the operation object indicated by the policy control information is a quality of service rule and/or an event trigger.
  • the binding of the policy control information to the corresponding IP connection access network session according to the identifier means that the BBERF is associated with the IP connection access session to be performed according to the identifier; the BBERF is IP
  • the connection access session operates as one or more of the following: Install Quality of Service Rules, Activate Quality of Service Rules, Install Event Triggers, Update Quality of Service Rules, Update Event Triggers, Delete Quality of Service Rules, Delete Event Triggers, Deactivate the quality of service rules.
  • the PCRF sends the policy control information and the identifier to the BBERF through a gateway control and a QoS rule providing message.
  • the IP connection access network session identifier of the same user equipment in the same PCRF is unique.
  • the identifier is a home address of a user equipment related to the IP connection access network session, or an access point name of a user equipment related to the IP connection access network session, or The identifier assigned by the PCRF to the IP connection access network session.
  • the method includes:
  • the PCRF re-defines the policy control information and sends it to the BBERF with an identifier for indicating an IP connection access network session related to the re-established policy control information; the BBERF is received according to the The identifier binds the re-established policy control information to a corresponding IP connection access network session, and performs corresponding operations according to the re-established policy control information.
  • the method includes:
  • the non-3rd generation partner program network After receiving the resource allocation or release request sent by the user equipment, the non-3rd generation partner program network sends a request to the PCRF, and the PCRF re-defines the policy control information, and sends the re-established policy control information and identifier.
  • the identifier is used to indicate an IP connection access network session related to the re-established policy control information; after the BBERF receives the re-formulated policy control information and the identifier, The identifier binds the re-established policy control information to the corresponding IP connection access network session, and performs corresponding operations according to the re-established policy control information.
  • the BBERF in the non-third-generation partner plan network stores the identifier of the IP-connected access network session, after receiving the resource allocation or release request sent by the user equipment, the BBERF is carried in the request sent by the PCRF. The identification.
  • the IP connection access network session has a service quality rule and/or an event trigger installed.
  • the method includes:
  • the IP-connected access network session termination indication message is sent to the PCRF by the packet data network gateway; the PCRF sends policy control information and an identifier to the BBERF, where the identifier is used for Instructing an IP connection access network session related to the policy control information, the operation indicated by the policy control information is deleting and/or deactivating, and the indicated operation object is all quality of service rules and/or event triggers; After receiving the policy control information and the identifier, the BBERF performs one or more of the following operations according to the re-established policy control information: deleting the quality of service rule, deleting the event trigger, and deactivating the quality of service rule.
  • the invention also discloses a system for carrying out binding and event reporting function policy control, comprising: a policy and charging rule function entity PCRF, when the user equipment accesses the service network through the gateway device or the user equipment passes the gateway device After accessing the service network, the policy control information is set for the IP connection access network session, and the policy control information and the identifier are sent to the bearer binding and event reporting function entity BBERF, where the identifier is used to indicate the policy control The information-related IP connection is connected to the network session, and the policy control information is used to indicate that the IP connection to be represented by the identifier is connected to the network.
  • the BBERF is configured to, after receiving the policy control information and the identifier sent by the PCRF, bind the policy control information to a corresponding IP connection access network session according to the identifier, and according to the The policy control information performs the corresponding operations.
  • the operation indicated by the policy control information refers to one or more of the following operations: installing, activating, updating, deleting, deactivating;
  • the operation object indicated by the policy control information is a quality of service rule and/or an event trigger.
  • the PCRF is further configured to: when the service information of the service network involved in the IP connection access network session changes, the evolved packet system network policy changes, or the subscription information of the user changes, Transmitting, by the IP connection, the policy control information related to the access network session, and sending the re-established policy control information and an identifier to the BBERF, where the identifier is used to indicate the policy control information with the re-established policy
  • the associated IP connection is connected to the network session.
  • the BBERF is further configured to send, after receiving the resource allocation or release request sent by the user equipment, the gateway control and the QoS policy rule request message to the PCRF;
  • the PCRF is further configured to: after receiving the gateway control and quality of service policy rule request message sent by the BBERF, re-establish policy control information related to the IP connection access network session, and The formulated policy control information and the identification are sent to the BBERF.
  • the gateway control and the QoS policy rule request message sent to the PCRF carries the logo.
  • the PCRF is further configured to send the policy control information and the identifier to the BBERF after the received IP-connected access network session termination indication message sent by the packet data network gateway, where the identifier is used to indicate The policy control information related IP connection access network session, the operation indicated by the policy control information is deletion and/or deactivation, and the indicated operation object is all quality of service rules and/or event triggers;
  • the BBERF is further configured to: after receiving the policy control information and the identifier, perform one or more of the following operations according to the re-established policy control information: deleting a service quality rule, deleting an event trigger, Deactivate the quality of service rule and return a session termination confirmation to the PCRF Message.
  • the identifier is a home address of the user equipment related to the IP connection access network session, or an access point name of the user equipment related to the IP connection access network session, or the PCRF is the IP address.
  • the identity of the connection to the access network session is a home address of the user equipment related to the IP connection access network session, or an access point name of the user equipment related to the IP connection access network session, or the PCRF is the IP address.
  • the invention has the beneficial effects that when the user equipment establishes an IP connection with multiple services at the same time and uses the DSMIPv6 protocol, although there are multiple IP-CAN (IP connection access) sessions in the network, the BBERF (bearing binding and The event reporting function can correctly bind the policy control information delivered by the PCRF (Policy and Charging Rules Function) to the corresponding IP-CAN session by using the identifier in the message. Similarly, the PCRF can correctly bind the relevant information sent by the BBERF to the corresponding IP-CAN session by using the identifier in the message.
  • PCRF Policy and Charging Rules Function
  • FIG. 1 is an architectural diagram of an EPS of a 3GPP network in a non-roaming state
  • FIG. 2 is a schematic diagram of a UE accessing different service networks through different P-GWs
  • FIG. 3 is an attached flow diagram of a UE accessing different service networks through different P-GWs in the prior art
  • FIG. 4 is an attached flowchart of an embodiment of the UE of the present invention accessing different service networks through different P-GWs;
  • FIG. 5 is a flowchart of an embodiment of performing policy control change when the service information of the service network 1 changes after the UE establishes an IP connection with the service network 1 and the service network 2;
  • FIG. 6 is a UE of the present invention; After establishing an IP connection with the service network 1 and the service network 2, the UE initiates a flowchart of an embodiment of performing a policy control change when a new resource allocation request is made using the service network 1;
  • FIG. 7 is a flow chart of the UE disconnecting from the service network 2 and performing policy deletion and deactivation after the UE of the present invention establishes an IP connection with the service network 1 and the service network 2;
  • FIG. 8 is an attached flowchart of an embodiment of a UE of the present invention accessing different service networks through an untrusted non-3GPP access network; 9 is a schematic diagram of an embodiment of a system for bearer binding and event reporting function policy control of the present invention.
  • the BBERF or the PCRF can The identity in the message correctly binds it to the IP-CAN session.
  • This identifier is unique to each IP-CAN session of the same UE under the same PCRF.
  • the identifier may be specifically allocated by the PCRF for each IP-CAN session, or may use existing parameters, such as the home address of the UE (user equipment) associated with an IP-CAN session or an APN (access) Point name) as the identifier of the IP-CAN session.
  • the policy control information includes an operation indicating that the BBERF is to be performed and an object corresponding to the operation.
  • the PCRF sends policy control information and an IP-CAN session identifier to the BBERF, the identifier being associated with the policy control information, that is, the policy control information is policy control information for the session indicated by the identifier.
  • the BBERF After receiving the policy control information and the IP-CAN session identifier, the BBERF binds the policy control information to the corresponding IP connection access network session according to the identifier, that is, the BBERF learns which session to operate according to the identifier, and learns through the policy control information. What the operation of the session is and the object of the operation.
  • the operations performed on the session include installation, activation, update, deletion, or deactivation, and the objects of the operation are quality of service rules and/or event triggers.
  • the policy control operation performed by using the policy control information may be one or more of the following: installing a quality of service rule; activating a quality of service rule; installing an event trigger; updating a quality of service rule; updating an event trigger ; delete the quality of service rules; delete event triggers; deactivate the quality of service rules.
  • the following embodiments are based on the scenario in which the UE accesses different service networks through different P-GWs as shown in FIG. 2 .
  • FIG. 4 it is an attaching flowchart of an embodiment in which a UE of the present invention accesses different service networks through different P-GWs. The steps are described as follows:
  • Step 401 The user equipment accesses the trusted non-3GPP access network through the layer 2, and the HSS/AAA performs access authentication and authorization on the UE.
  • Step 402 After the authentication is successful, establish a layer 3 connection between the UE and the trusted non-3GPP access system, and the access system allocates an IP address to the UE as the care-of address CoA of the UE;
  • Step 403 The trusted non-3GPP access network that has the BBERF (bearer binding and event reporting function) sends a "gateway control session establishment" request to the PCRF, where the message carries the identity of the UE and the CoA;
  • BBERF bearer binding and event reporting function
  • Step 404 The PCRF formulates a control policy, that is, a QoS rule, based on the network policy and the subscription information of the UE, and sends the message to the trusted non-3GPP access network through a "Gateway Control Session Establishment Confirmation" message, where the control policy and the UE are to be accessed.
  • a control policy that is, a QoS rule, based on the network policy and the subscription information of the UE, and sends the message to the trusted non-3GPP access network through a "Gateway Control Session Establishment Confirmation" message, where the control policy and the UE are to be accessed.
  • Business has nothing to do;
  • Step 405 The UE performs a DNS query according to the APN1, and obtains an IP address of the P-GW1 that provides the access service 1 network.
  • the UE establishes a security association with the P-GW1.
  • the P-GW1 allocates the home address HoAl to the UE.
  • Step 406 The UE sends a "Binding Update" request message to the P-GW1, where the message carries CoA and HoAl;
  • Step 407 The P-GW1 sends an "IP-CAN Session Establishment Indication" message to the PCRF, where the message carries CoA, HoAl, NAI, and APN1; and the PCRF associates the session with the gateway control session according to the CoA;
  • Step 408 The PCRF formulates corresponding PCC rules and event triggers according to the network policy, the user subscription, and the information of the service network 1 to be accessed, and sends the message to the P-GW1 through the "IP-CAN session establishment confirmation"message;
  • Step 410 The PCRF modifies the previously formulated QoS rule according to the network policy, the user subscription, and the information of the service network 1 to be accessed, and formulates an event trigger, and the PCRF allocates an identifier IP-CAN session identifier for the IP-CAN session. 1. Transmitting the modified QoS rule, event trigger, and IP-CAN session identifier 1 to the trusted non-3GPP access network through a "gateway control and QoS rule provisioning" message;
  • Step 411 The trusted non-3GPP access network determines, according to the IP-CAN session identifier 1, that it is a new IP-CAN session related policy control information, so save the IP-CAN session identifier 1 and install a QoS rule for the IP-CAN session. And event trigger, and return "gateway control and QoS rule provision confirmation" message to P-GW1;
  • the policy control information indicates that the operation to be performed is installation, and the object of the operation is a QoS rule and an event trigger.
  • the trusted non-3GPP access network queries the IP-CAN session according to the identifier, and learns according to the policy control information. Actions to install QoS rules and event triggers need to be performed.
  • Step 412 When the UE determines to access the service network 2, perform a DNS query according to the APN2, and obtain an IP address of the P-GW2 that provides the access service network 2.
  • Step 413 A security association is established between the UE and the P-GW2.
  • the P-GW2 allocates the home address HoA2 to the UE.
  • Step 414 The UE sends a "Binding Update" request message to the P-GW2, where the message carries CoA and HoA2;
  • Step 415 The P-GW2 sends an "IP-CAN Session Establishment Indication" message to the PCRF, where the message carries CoA, HoA2, NAI, and APN2, and the PCRF associates the session with the gateway control session according to the CoA;
  • Step 416 The PCRF formulates corresponding PCC rules and event triggers according to the network policy, the user subscription, and the information of the service network 2 to be accessed, and sends the message to the P-GW2 through the "IP-CAN session establishment confirmation" message;
  • Step 417 P-GW1 returns a "Binding Confirmation" message to the UE;
  • Step 418 The PCRF formulates a QoS rule and an event trigger according to the network policy, the user subscription, and the information of the service network 2 to be accessed, and the PCRF allocates the identifier IP-CAN for the IP-CAN session. Session ID 2, sent to the trusted non-3GPP access network through a "gateway control and QoS rule provisioning"message;
  • Step 419 The trusted non-3GPP access network determines, according to the IP-CAN session identifier 2, that this is a new IP-CAN session related policy control information, so save the IP-CAN session identifier 2, and install QoS for the IP-CAN session.
  • the rules and event triggers return a "gateway control and QoS rule provision confirmation" message to P-GW2.
  • the PCRF may not allocate the IP-CAN session identifier 1 but carry the home address HoAl of the UE or the access point name APN1 in the "Gateway Control and QoS Rule Provisioning" message, and send it to the Trusting the non-3GPP access network to identify that the message is associated with IP-CAN session 1; in step 411, the trusted non-3GPP access network determines that a new IP-CAN session is associated with the policy based on HoAl or APN1 Control information, so save HoAl or APN1, install QoS rules and event triggers for this IP-CAN session, and return "Gateway Control and QoS Rule Provide Confirmation" message to P-GW1.
  • the PCRF may also not allocate the IP-CAN session identifier 2, but instead use the UE's home address HoA2 or the access point name APN2 instead.
  • the QoS rule can be a dynamic rule defined by the PCRF or a BBERF predefined QoS rule
  • the BBERF performs the QoS rule after receiving the QoS rule delivered by the PCRF, as shown in the above process. If the PCRF decides to activate the BBERF predefined QoS rule, the PCRF can use the identifier of the predefined rule to notify the BBERF, and the BBERF activates the predefined QoS rule.
  • the PCRF may also only send QoS rules to the BBERF or only send event triggers.
  • the PCRF is triggered to be restarted.
  • the PCC and QoS rules are formulated so that the PCRF needs to change the PCC rules in P-GW1 and the QoS rules related to IP-CAN Session 1 in the trusted non-3GPP access network.
  • Step 501 The PCRF receives the changed information, and the changed information includes the changed service information delivered by the service network 1, the information of the policy change of the EPS network, or the information of the change of the UE subscription information, and the PCRF is re-established with the IP-CAN. Session 1 related PCC rules, QoS rules; Step 502: The PCRF sends the re-established QoS rules through the "Gateway Control and QoS Policy Rule Provisioning" message to the trusted BBERF (bearer binding and event reporting function) In the non-3GPP access network, the message carries an IP-CAN session identifier 1 to indicate that the delivered QoS rule is related to the IP-CAN session 1;
  • Step 503 The UE and the trusted non-3GPP IP access network specific mechanism perform the newly delivered policy.
  • CAN session 1 changes the QoS rules related to IP-CAN session 1, and returns a "gateway control and QoS policy rule provision confirmation" message to the PCRF;
  • the change to the QoS rule includes: installing and/or activating a QoS rule that is not installed or inactivated and requiring installation and/or activation, and the operation indicated by the policy control information is installation and/or activation, operation
  • the object is a Qos rule; the QoS rule that has been previously installed or activated and requested to be deleted and/or deactivated is deleted and/or deactivated, and the operation indicated by the policy control information is deleted and/or deactivated.
  • the object is a Qos rule; the PCC rule that has been installed and issued to require an update is updated. At this time, the operation indicated by the policy control information is an update, and the object of the operation is a Qos rule.
  • Step 505 The PCRF sends a newly formulated PCC rule to the P-GW1 through the "Policy Charging Rule Provisioning" message;
  • Step 506 The P-GW1 changes the PCC rule, and returns a "Policy Charging Rule Provide Confirmation" message to the PCRF.
  • Changes to the PCC rules include: installing and/or activating PCC rules that were previously installed or inactive and requiring installation and/or activation, and requesting deletion and/or deactivation for previously installed or activated
  • the PCC rules are deleted and/or deactivated, and the PCC rules that have been previously installed and issued with the required updates are updated.
  • step 502 When the PCRF sends the re-established QoS rule to the trusted non-3GPP access network through the "Gateway Control and QoS Policy Rule" message, the message carries the home address HoAl of the UE to indicate that the QoS rule is delivered.
  • the trusted non-3GPP access network binds the delivered QoS rule to the IP-CAN session 1 according to the home address HoAl of the UE, and the IP-CAN session 1
  • the access point names APN1 and APN2 may be used instead of the IP-CAN session identifier 1 and the IP-CAN session identifier 2 as the identifiers indicating the relevant IP-CAN sessions.
  • the PCRF is also triggered to reform the PCC and QoS rules, so that the PCRF needs to associate the PCC rules in the P-GW2 with the IP-CAN session 2 in the trusted non-3GPP access network.
  • the rules are changed.
  • the process is similar to the above process.
  • the PCRF when the service network 1 information changes, the EPS network policy changes, or the user's subscription data changes, the PCRF is triggered to re-establish the PCC and QoS rules, and the PCRF is also triggered to re-define the event trigger.
  • the PCRF needs to change the PCC rules, event triggers, and QoS rules and event triggers associated with IP-CAN Session 1 in the trusted non-3GPP access network in P-GW1.
  • step 502 the QoS rule and the event trigger need to be delivered, and in step 504, the non-3GPP access network can change the QoS rule and the event trigger; in step 505, the PCC rule and the event trigger are sent, and accordingly, 506
  • the step P-GW changes the PCC rules and event triggers.
  • the PCRF may also only change event triggers (including event triggers in P-GW1 and event triggers associated with IP-CAN Session 1 in a trusted non-3GPP access network).
  • step 502 only the event trigger is issued, and in step 504, the non-3GPP access network only changes the event trigger; in step 505, only the event trigger is issued, and in step 506, the P-GW only changes the event trigger.
  • the UE does not necessarily access the service network 2 after accessing the service network 1. Therefore, in other embodiments, the UE can access the service network 1 according to the existing process, that is, the PCRF does not allocate or Indicating the identity, and when the QoS rule and/or the event trigger of the session in the service network 1 on the BBERF is required to be operated, the PCRF allocates or indicates the identifier for the session, and after receiving the identifier, the BBERF according to the identifier
  • the policy control information is bound to the corresponding IP connection access network session, and the corresponding operation is performed according to the policy control information.
  • the UE When it is required to operate the QoS rules and/or event triggers of the session in the service network 1 on the BBERF, the UE may be not yet connected to the service network 2 (the IP-CAN session 2 does not exist), or has access to the service network. 2. If already When accessing the service network 2, the session should have been assigned or indicated the session identifier, so as to ensure that the BBERF can distinguish the policy control information of each session.
  • Step 601 The non-3GPP access gateway receives the resource allocation request initiated by the UE for the IP-CAN session 1.
  • Step 602 The trusted non-3GPP access network camping on the BBERF (bearer binding and event reporting function) sends a "Gateway Control and QoS Policy Rule Request" message to the PCRF, where the message carries the requested Q 0 S, service filtering.
  • BBERF bearer binding and event reporting function
  • Step 603 The PCRF binds the foregoing request information to the IP-CAN session 1 according to the IP-CAN session identifier 1, and makes a decision for each QoS request, and formulates a PCC and a QoS rule.
  • Step 604 The PCRF sends a "Policy and Charging Rule Provisioning" message to the P-GW1, where the message carries the PCC rule to be changed.
  • Step 605 P-GW1 changes the PCC rule, and returns a "policy and charging rule providing confirmation" message;
  • Changes to the PCC rules include: installing and/or activating PCC rules that were previously installed or inactive and requiring installation and/or activation, and requesting deletion and/or deactivation for previously installed or activated
  • the PCC rules are deleted and/or deactivated, and the PCC rules that have been previously installed and issued with the required updates are updated.
  • Step 606 The PCRF sends a "Gateway Control and QoS Policy Rule Provisioning" message to the trusted non-3GPP access network, where the message carries the QoS rule to be changed and the IP-CAN session identifier 1 to indicate the QoS rule delivered here. Changes to the IP-CAN session lQoS rules;
  • Step 607 The trusted non-3GPP access network binds the QoS rule to the IP-CAN session 1 according to the IP-CAN session identifier 1, and changes its QoS rule to trust the non-3GPP access network specific. Mechanism execution strategy.
  • Changes to the QoS rules include: installing and/or activating QoS rules that are not previously installed or inactive and requiring installation and/or activation, and requesting deletion and/or deactivation for previously installed or activated
  • the QoS rules are deleted and/or deactivated, and the QoS rules that have been previously installed and required to be updated are updated.
  • the non-3GPP access can be trusted.
  • the "Gateway Control and QoS Policy Rule Request" message sent by the network to the PCRF carries the requested QoS, the service filter template, and the home address HoAl of the UE; accordingly, in step 603, the PCRF is based on the UE's home address HoAl. Bind the above request information to IP-CAN Session 1.
  • step 606 the "Facilization Control and QoS Policy Rule Provisioning" message sent by the PCRF to the trusted non-3GPP access network carries the QoS rule to be changed and the home address HoAl of the UE to indicate the QoS rule delivered here.
  • the trusted non-3GPP access network binds the QoS rule to IP-CAN Session 1 according to the UE's home address HoAl.
  • the access point names APN1 and APN2 can also be used instead of the IP-CAN session identifier 1 and the IP-CAN session identifier 2 as indicators for indicating the relevant IP-CAN session.
  • the PCRF is also required to reformulate the PCC and QoS rules, so that the PCRF will have a PCC rule in the P-GW2 and an IP-CAN session in the trusted non-3GPP access network.
  • the relevant QoS rules are changed.
  • the process of change is similar to the above process.
  • the UE initiates a resource release request for the service network 1, and in step 601, the UE initiates the release of the resource of the IP-CAN session 1 to the trusted non-3GPP access network, and the message in step 602 carries the request resource.
  • the message in step 602 carries the request resource.
  • the PCRF binds the request information to the IP-CAN session 1 according to the IP-CAN session identifier 1, and performs the request for the released QoS. Decision making, re-engineering PCC and QoS rules; other steps are similar.
  • the PCRF can also change event triggers while changing PCC rules and QoS rules, or only event triggers, as needed.
  • the UE may access the service network 1 according to an existing procedure, and when initiating a resource allocation or resource release request, the PCRF allocates or indicates an identifier for the session, so that the BBERF operates. For example, in step 602, the message sent by the trusted non-3GPP access network to the PCRF does not carry the IP-CAN session identifier, and the PCRF sends the assigned identifier to the BBERF when the new policy control information is sent. After the end of this process, the UE accesses the service network 2.
  • the PCRF sends a message to notify the trusted non-3GPP that resides with the BBERF.
  • the access gateway deletes and deactivates the QoS rules associated with IP-CAN Session 2. The process is shown in Figure 7, and the steps are described as follows:
  • Step 701 The UE decides to disconnect from the service network 2, and sends a registration update update message to the P-GW2, where the message carries HoA2, and the lifetime parameter value is 0;
  • Step 702 P-GW2 sends an IP-CAN session termination indication message to the PCRF, and deletes the PCC rule related to the IP-CAN session 2 at the same time;
  • P-GW2 deactivates the predefined PCC rule.
  • Step 703 The PCRF deletes the IP-CAN session 2 related PCC rule, and returns an IP-CAN session termination confirmation message to the P-GW2.
  • the PCRF deactivates the predefined PCC rule.
  • Step 704 The P-GW2 notifies the AAA and the HSS to delete the IP address of the P-GW2 for the UE.
  • Step 705 The P-GW2 returns a binding acknowledgement message to the UE.
  • Step 706 The PCRF deletes the QoS rule related to the IP-CAN session 2, and sends a message of "Gateway Control and QoS Rule Provisioning" to the trusted non-3GPP access gateway that hosts the BBERF.
  • the message carries policy control information (for indicating deletion). And/or the session termination indication of the deactivation operation) and the IP-CAN session identifier 2, notifying the trusted non-3GPP access gateway to delete the QoS rule associated with the IP-CAN session 2;
  • Step 707 After receiving the "Gateway Control and QoS Rule Provisioning" message, the trusted non-3GPP access gateway binds the policy control information in the message to the corresponding IP connection access network session according to the identifier carried therein
  • the policy control information (the policy control information refers to the Qos rule) of the IP connection access network session is found according to the identifier, all QoS rules related to the IP-CAN session 2 are deleted, and the gateway control is returned to the PCRF.
  • the QoS rule provides an acknowledgment message; if the PCRF notifies the BBERF to activate the predefined QoS rule in step 706, then in this step, the trusted non-3GPP access gateway deactivates the predefined QoS rule;
  • the PCRF sends the "gateway control and QoS rules" to the trusted non-3GPP access network.
  • the home address HoA of the UE is carried; the access point name APN can also be used instead of the IP-CAN session identifier as the identifier indicating the relevant IP-CAN session.
  • the PCRF can also delete event triggers or delete event triggers while deleting or deactivating PCC rules and QoS rules, as needed.
  • the following embodiment is an attach procedure of a UE accessing different service networks through different P-GWs through an untrusted non-3GPP IP access network. As shown in FIG. 8, the method includes:
  • Step 801 The UE initiates an IKEv2 (Internet Key Exchange Version 2) tunnel establishment process, and the HSS/AAA performs tunnel authentication and authorization on the UE.
  • IKEv2 Internet Key Exchange Version 2
  • Step 802 The ePDG sends a last IKEv2 message to the UE, where the message is configured with the UE's care-of address CoA;
  • Step 803 The ePDG residing with the BBERF (bearer binding and event reporting function) sends a "Gateway Control Session Establishment" request message to the PCRF, where the message carries the identifiers of the UE and the CoA;
  • Step 805 The UE performs a DNS query according to APN1, and obtains a network that provides access service 1
  • the IP address of the P-GW1 the UE establishes a security association with the P-GW1, and in this process, the P-GW1 allocates the home address HoAl to the UE;
  • Step 806 The UE sends a "Binding Update" request message to the P-GW1, where the message carries CoA and HoAl;
  • Step 807 The P-GW1 sends an "IP-CAN Session Establishment Indication" message to the PCRF, where the message carries CoA, HoAl, NAI, and APN1; and the PCRF associates the session with the gateway control session according to the CoA;
  • Step 808 The PCRF formulates corresponding PCC rules and event triggers according to the network policy, the user subscription, and the information of the service network 1 to be accessed, and sends the message to the P-GW1 through the "IP-CAN session establishment confirmation" message;
  • Step 809 P-GW1 returns a "binding acknowledgement" message to the UE;
  • Step 810 The PCRF modifies the previously formulated QoS rule according to the network policy, the user subscription, and the information of the service network 1 to be accessed, and formulates an event trigger, and the PCRF allocates an identifier IP-CAN session identifier for the IP-CAN session. 1. Send the modified QoS rule, event trigger and IP-CAN session identifier 1 to the ePDG through the "Gateway Control and QoS Rule Provisioning" message; Step 811: The ePDG judges to be a new IP based on the IP-CAN session identifier 1.
  • the policy control information related to the CAN session so the IP-CAN session identifier 1 is saved, the QoS rules and event triggers are installed for the IP-CAN session, and the "gateway control and QoS rule provision confirmation, message" is returned to the P-GW1;
  • Step 812 When the UE determines to access the service network 2, perform a DNS query according to the APN2, and obtain an IP address of the P-GW2 that provides the access service network 2.
  • Step 813 A security association is established between the UE and the P-GW2.
  • the P-GW2 allocates the home address HoA2 to the UE.
  • Step 815 The P-GW2 sends a ' ⁇ -CAN session establishment indication' message to the PCRF, where the message carries CoA, HoA2, NAI, and APN2, and the PCRF associates the session with the gateway control session according to the CoA;
  • Step 817 P-GW1 returns a "Binding Confirmation" message to the UE;
  • Step 818 The PCRF formulates a QoS rule and an event trigger according to the network policy, the user subscription, and the information of the service network 2 to be accessed, and the PCRF allocates the identifier IP-CAN session identifier 2 to the IP-CAN session, and passes the gateway control.
  • QoS rules provide "messages sent to ePDG;
  • Step 819 The ePDG determines, according to the IP-CAN session identifier 2, that this is a new IP-CAN session related policy control information, so save the IP-CAN session identifier 2, and install QoS rules and event triggers for the IP-CAN session. Return to the P-GW2 "Gateway Control and QoS Rule Provide Confirmation, Message.
  • the event trigger triggers and/or PCC rules initiated by the PCRF to the P-GW, event triggers and/or QoS rules initiated to the ePDG, And the resource request and the resource release process initiated by the UE are similar to those when the UE accesses the network through the trusted non-3GPP IP access network, and details are not described herein again.
  • Figure 9 An embodiment of the system for bearer binding and event reporting function policy control of the present invention is shown in Figure 9, which includes:
  • a policy and charging rule function (PCRF) 901 configured to establish a control policy for each IP connection access network session when the user equipment accesses the service network through the gateway device or after the UE accesses the service network through the gateway device, and The established control policy is sent to the bearer binding and event reporting function 902 by a message, the message including an identifier for indicating an IP-CAN session associated with the message, the policy control information is used to indicate that the policy will be The operation of the IP connection access network session indicated by the identifier and the object of the operation;
  • PCRF policy and charging rule function
  • a bearer binding and event reporting function (BBERF) 902 is configured to bind the message to the corresponding IP-CAN session according to the identifier in the message after receiving the message sent by the policy and charging rule function 901. And performing corresponding operations according to the policy control information.
  • the PCRF is further used for service of a service network involved in the IP connection access network session
  • the information or the evolved packet system network policy or the subscription information of the user changes, re-deact policy control information related to the IP connection access network session, and send the re-formulated policy control information and identifier to the a BBERF, where the identifier is used to indicate an IP connection access network session related to the re-established policy control information;
  • the PCRF sends a gateway control and a QoS policy rule request message, where the request message includes the requested policy control information and the identifier (if the PCRF is previously assigned an identifier, otherwise not carried), the identifier is used to identify the policy control with the request.
  • the network access session is bound, and the corresponding operation is performed according to the re-established policy control information, that is, one or several of the following operations are performed: installing the service quality rule, activating the service quality rule, updating the service quality rule, installing the event trigger, Update event triggers, delete quality of service rules, delete event triggers, and deactivate quality of service rules;
  • the PCRF is further configured to: after receiving the gateway control and QoS policy rule request message sent by the BBERF, if there is an identifier, connect the requested policy control information to the corresponding IP according to the identifier Binding the session to the network, otherwise re-establishing the policy control information related to the IP connection network session, and sending the re-established policy control information and the identifier to the BBERF, where the identifier is used for An IP connection access network session associated with the redefined policy control information is indicated.
  • the PCRF is further configured to send policy control information and an identifier to the BBERF according to the IP connection access network session termination indication message sent by the received packet data network gateway, where the identifier is used to indicate The policy control information related IP connection access network session, the operation indicated by the policy control information is deletion and/or deactivation, and the indicated operation object is all quality of service rules and/or event triggers;
  • the BBERF is further configured to: after receiving the policy control information and the identifier, perform one or more of the following operations according to the re-established policy control information: deleting a service quality rule, deleting an event trigger, Deactivate the quality of service rules and return a session termination confirmation message to the PCRF.
  • the identifier may be allocated by the policy and charging rule function 901, and the identifier of each IP-CAN session of the same UE under each policy and charging rule function 901 is unique; the identifier in the message may also be used. There are parameters, such as the home address or access point name of the UE associated with an IP-CAN session as the identity of the IP-CAN session.
  • the reporting function can correctly bind the policy control information delivered by the PCRF (policy and charging rule function) to the corresponding IP-CAN session through the identifier in the message.
  • the PCRF can correctly bind the relevant information sent by the BBERF to the corresponding IP-CAN session through the identity in the message.

Landscapes

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

Abstract

L'invention concerne un procédé et un système de contrôle de politique BBERF (fonction de rapport d'événements et de liaison de porteuse) dans un EPS (système paquet évolué) de 3GPP. Le procédé consiste en ce que: lorsqu'un EU accède au réseau de service par l'intermédiaire d'un dispositif de passerelle ou après que l'EU accède au réseau de service par l'intermédiaire du dispositif de passerelle, une PCRF (fonction règles de politiques et de facturation) envoie les informations de contrôle de politique et un identificateur au BBERF, l'identificateur indiquant une session de réseau d'accès de connexion IP associée aux informations de contrôle de politique, les informations de contrôle de politique indiquent l'opération mise en oeuvre par une session de réseau d'accès de connexion IP par l'identificateur et l'objet de l'opération; après que le BBERF reçoit les informations de contrôle de politique et l'identificateur, le BBERF lie les informations de contrôle de politique et la session de réseau d'accès de connexion IP correspondante en fonction de l'identificateur, et met en oeuvre l'opération correspondante en fonction des informations de contrôle de politique. La présente invention permet à la BBERF de lier correctement les informations de contrôle de politique envoyées par une PCRF à la session IP-CAN par l'intermédiaire de l'identificateur contenu dans le message.
PCT/CN2008/071720 2008-04-11 2008-07-22 Procédé et système de contrôle de politique bberf WO2009124436A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810089963.8 2008-04-11
CN2008100899638A CN101459951B (zh) 2008-04-11 2008-04-11 一种承载绑定和事件报告功能策略控制的方法及系统

Publications (1)

Publication Number Publication Date
WO2009124436A1 true WO2009124436A1 (fr) 2009-10-15

Family

ID=40770513

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/071720 WO2009124436A1 (fr) 2008-04-11 2008-07-22 Procédé et système de contrôle de politique bberf

Country Status (2)

Country Link
CN (1) CN101459951B (fr)
WO (1) WO2009124436A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013030659A1 (fr) 2011-09-02 2013-03-07 Alcatel Lucent Procédé et appareil de commande d'accès à un réseau sans fil par un terminal

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101841798B (zh) * 2009-03-20 2014-01-01 中兴通讯股份有限公司 计费标识的关联方法和装置
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 中兴通讯股份有限公司 漫游场景下承载控制模式的发送方法和系统
CN101801038B (zh) * 2009-12-28 2014-04-02 华为技术有限公司 用户会话策略控制方法、装置及系统
CN102238690B (zh) * 2010-04-26 2014-04-09 中兴通讯股份有限公司 Cdma网络的策略和计费控制中的会话关联方法
CN102316444B (zh) * 2010-07-06 2016-06-29 中兴通讯股份有限公司 一种对用户设备进行服务质量控制的系统及方法
CN102611586B (zh) * 2011-01-18 2017-06-13 中兴通讯股份有限公司 支持双栈的ip‑can会话实现应用检测和控制的方法及系统
CN102098651B (zh) * 2011-01-21 2013-08-14 北京邮电大学 利用用户服务标识usid实施策略标识与控制的方法
CN103209497B (zh) * 2012-01-11 2018-05-11 中兴通讯股份有限公司 一种策略会话建立方法及装置
CN103458390B (zh) * 2012-06-04 2016-12-14 电信科学技术研究院 一种ip地址传输方法及装置
CN106161375B (zh) * 2015-04-13 2019-10-29 中国移动通信集团公司 业务链标识的分配方法、装置、策略控制器及分类器
CN109246173B (zh) * 2017-06-16 2023-02-17 北京三星通信技术研究有限公司 会话操作的控制方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101141412A (zh) * 2007-10-12 2008-03-12 中兴通讯股份有限公司 一种为用户终端建立专有承载的方法
CN101159563A (zh) * 2007-11-02 2008-04-09 中兴通讯股份有限公司 一种策略计费控制服务器的选择方法及系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101141412A (zh) * 2007-10-12 2008-03-12 中兴通讯股份有限公司 一种为用户终端建立专有承载的方法
CN101159563A (zh) * 2007-11-02 2008-04-09 中兴通讯股份有限公司 一种策略计费控制服务器的选择方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3GPP TS 23. 203 v8. 1. 1 3rd Generation Partnership Project", 31 March 2008, article "Technical Specification Group Services and System Aspects; Policy and charging control architecture", pages: 15 - 53 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013030659A1 (fr) 2011-09-02 2013-03-07 Alcatel Lucent Procédé et appareil de commande d'accès à un réseau sans fil par un terminal
EP2752054A1 (fr) * 2011-09-02 2014-07-09 Alcatel-Lucent Procédé et appareil de commande d'accès à un réseau sans fil par un terminal
EP2752054A4 (fr) * 2011-09-02 2015-03-11 Alcatel Lucent Procédé et appareil de commande d'accès à un réseau sans fil par un terminal
US9407512B2 (en) 2011-09-02 2016-08-02 Alcatel Lucent Method and apparatus for controlling terminal's access to a wireless network

Also Published As

Publication number Publication date
CN101459951B (zh) 2011-08-24
CN101459951A (zh) 2009-06-17

Similar Documents

Publication Publication Date Title
WO2009124436A1 (fr) Procédé et système de contrôle de politique bberf
US8621555B2 (en) Access control method and system for packet data network, PCRF entity
US8463889B2 (en) Method for provisioning and installing event triggers
US8874715B2 (en) Charging method, system and reporting method for terminal accessing through multiple access networks
US8811342B2 (en) Method and system for deleting redundant information of home policy and charging rules function
WO2009135362A1 (fr) Procédé de commande de politique et de facturation pour cacher la topologie d'un réseau visité
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
WO2009086734A1 (fr) Procédé pour sélectionner une entité à fonction de règles de politique et de facturation dans le scénario sans itinérance
US20110161504A1 (en) Method and apparatus for identifying session information
WO2010121460A1 (fr) Procédé pour mettre en oeuvre une commande de politique et de facturation limitée et système associé
WO2010015133A1 (fr) Procédé de suppression de l'information de session contenue dans le dra
WO2012006909A1 (fr) Procédé et système de rapport d'informations d'accès à un réseau fixe
WO2012058998A1 (fr) Procédé de commande de politique et de facturation soutenant une mobilité de flux ip dans un scénario d'itinérance
WO2010121511A1 (fr) Procédé de commande de multiples accès réseau, système de communication et dispositifs apparentés
WO2013104234A1 (fr) Procédé et système de contrôle de règles pour un réseau convergé
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
WO2013189217A1 (fr) Procédé pour mettre à jour des informations d'identité au sujet d'une passerelle de paquets, serveur aaa et passerelle de paquets
WO2011015140A1 (fr) Procédé, système et appareil pour radiomessagerie de télécommunication mobile
WO2010124551A1 (fr) Procédé et système pour préserver un identifiant de passerelle de réseau par paquets dans un scénario d'accès multiples
WO2011134327A1 (fr) Procédé et système permettant de déterminer une fonction de règles de politique et de facturation
WO2012022222A1 (fr) Procédé et système permettant une association de sessions de contrôle de politique
WO2011018020A1 (fr) Procede et systeme de commande d'equilibre de charge de pcrf et dra de redirection
US20120008523A1 (en) Methods and Apparatuses for Associating Charging Identifiers
WO2012013103A1 (fr) Procédé et système de rapport d'identité de passerelle
WO2012010036A1 (fr) Procédé et système de contrôle de politique

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08873802

Country of ref document: EP

Kind code of ref document: A1