WO2011029349A1 - Procédé et système de traitement de multiples fonctions d'association de support et de rapport d'événement - Google Patents

Procédé et système de traitement de multiples fonctions d'association de support et de rapport d'événement Download PDF

Info

Publication number
WO2011029349A1
WO2011029349A1 PCT/CN2010/075388 CN2010075388W WO2011029349A1 WO 2011029349 A1 WO2011029349 A1 WO 2011029349A1 CN 2010075388 W CN2010075388 W CN 2010075388W WO 2011029349 A1 WO2011029349 A1 WO 2011029349A1
Authority
WO
WIPO (PCT)
Prior art keywords
bberf
session
vpcrf
pcrf
primary
Prior art date
Application number
PCT/CN2010/075388
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 WO2011029349A1 publication Critical patent/WO2011029349A1/fr

Links

Classifications

    • 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
    • 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
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the present invention relates to an IP-Connected Network (IP-Access) network technology, and more particularly to a method and system for processing a multi-bearer binding and event reporting function.
  • IP-Access IP-Connected Network
  • the EPS of the 3rd Generation Partnership Project includes: E-UTRAN (Evolved Universal Terrestrial Radio Access Network), Mobility Management Entity (MME), S-GW (Serving Gateway), Packet Data Network Gateway (P-GW) , Packet Data Network Gateway), Home Subscriber Server (HSS), 3GPP Authentication and Authorization Accounting (AAA) server, Policy and Charging Rules Function (PCRF) and other supporting nodes.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • Packet Data Network Gateway Packet Data Network Gateway
  • HSS Home Subscriber Server
  • AAA 3GPP Authentication and Authorization Accounting
  • PCRF Policy and Charging Rules Function
  • the MME is used for control planes such as mobility management, non-access stratum signaling processing, and user mobility management context management.
  • the S-GW is an access gateway device connected to the E-UTRAN.
  • the E-UTRAN and the P-GW forward data, and are responsible for buffering the paging waiting data;
  • the P-GW is a border gateway of the EPS and the Packet Data Network (PDN), and is used for the PDN access and Forward data and other functions between EPS and PDN.
  • PDN Packet Data 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 S2a;
  • the IP address of the untrusted non-3GPP network needs to be connected to the P-GW by the Evolved Packet Data Gateway (ePDG).
  • ePDG Evolved Packet Data Gateway
  • the interface between the ePDG and the P-GW is S2b.
  • the user equipment UE, User Equipment
  • the EPS system supports the policy and charging rules of the PCRF of the Policy and Charging Control (PCC)
  • the EPS system is connected to the service network of the operator's Internet Protocol (IP) through the receiving interface Rx. Obtaining the service information;
  • the EPS system is connected to the gateway device in the network through the Gx/Gxa/Gxc interface, and is responsible for initiating the establishment of the IP bearer, guaranteeing the quality of service (QoS) of the service data, and performing charging. control.
  • IP Internet Protocol
  • PCEF Policy and Charging Enforcement Function M
  • PCRF Policy and Charging Enforcement Function M
  • Gx Gx interface
  • PMIP Proxy Mobile IP
  • BBERF Bearer Binding and Event Report Function
  • the trusted non-3GPP access gateway also has a BBERF, and the trusted non-3GPP network access gateway exchanges information with the PCRF through the Gxa interface.
  • the home PCRF hPCRF
  • the interface of the visited PCRF vPCRF
  • the application function AF, Application Function
  • the service information for generating the PCC policy is sent to the PCRF through the Rx interface.
  • the protocol used in the PCC architecture is the Diameter application protocol developed on the basis of the Diameter Base Protocol.
  • Example 3 ⁇ 4 port application protocol applied to Gx interface, application protocol applied to Rx interface, application protocol of Gxx interface (including Gxa and Gxc interface), and application protocol applied to roaming interface S9.
  • Messages, commands, and attribute value pairs (AVP, Attribute Value Pairs) for PCC are defined in these application protocols. Wait.
  • Diameter sessions established with these protocols can be Gx sessions, Gxx sessions, Rx sessions, and S9 sessions, respectively.
  • the PCC functional entities perform policy charging control on the PDN connection established by the UE accessing the network through these sessions.
  • the PCC architecture has defined the Diameter application protocol used in the non-roaming scenario, for example, an application protocol applied to the Gx interface, an application protocol applied to the Rx interface, and an application protocol of the Gxx interface (including the Gxa and Gxc interfaces). Messages, commands, AVPs, etc. for the PCC are defined in these application protocols.
  • an IP-CAN session involves multiple network elements.
  • each network element will establish a Diameter session with the PCRF.
  • an IP-CAN session will be associated with multiple Diameter sessions, which are created, maintained, and deleted using the Diameter protocol.
  • the PCRF When reselection occurs in the BBERF, for example, when the UE cross-system handover or the UE performs pre-registration across systems, the PCRF needs to control two or more BBERFs located in different systems or network elements simultaneously, one of which is called the primary BBERF (Primary BBERF), the other is called Non-Primary BBERF.
  • the PCRF saves its QoS rules and status for each BBERF at the same time, and the operation of these BBERFs is also different. For example: When the PCRF wants to update the QoS rules, the PCRF will send the updated QoS rules to these BBERFs. If the Primary BBERF fails to install the QoS rules, the Primary BBERF reports the situation to the PCRF.
  • the PCRF will delete the same in Non-Primary. QoS rules, and delete the corresponding PCC rules in the PCEF. If the Non-Primary BBERF fails to install the QoS rules, the Non-Primary BBERF reports the situation to the PCRF. The PCRF only updates the QoS rules and their status saved in the Non-Primary BBERF in the PCRF without performing other operations. Of course, hPCRF has other different operations for Primary BBERF and Non-Primary BBERF, and will not be described here.
  • FIG. 2 is a flow chart of establishing an IP-CAN session for accessing an EPS through an E-UTRAN or a trusted non-3GPP access gateway in a non-roaming scenario in the prior art, assuming that When the E-UTRAN is accessed, the PMIPv6 protocol is used between the S-GW and the P-GW. When accessing through the trusted non-3GPP access gateway, the PMIPv6 protocol is used between the access gateway and the P-GW. As shown in Figure 2, the following steps are included:
  • Step 201 The BBERF receives the establishment of the IP-CAN session request message, and the BBERF obtains the user identifier, such as a Network Access Identity (NAI), a PDN identifier, and access information used to formulate a policy.
  • the access information includes the network identifier of the network where the BBERF is located, the current location information of the UE, the address of the BBERF, and the IP-CAN type or RAT type.
  • the BBERF can be located in the S-GW or a trusted non-3GPP access gateway.
  • Step 202 The BBERF sends a gateway control session establishment indication message to the PCRF, where the gateway control session establishment indication message carries the user identifier, the PDN identifier, and the access information used to formulate the policy.
  • Gxx session (Gxx session, also called the gateway control session) established by the gateway control session establishment indication message is called Gxx session 1.
  • Step 203 The PCRF saves the reported access information.
  • the SPR Subscribescription Profile Repository
  • the PCRF sends a gateway control session establishment confirmation message to the BBERF, and the message carries QoS rules and event triggers for the BBERF to install QoS rules and event triggers.
  • Step 204 The gateway where the BBERF is located sends an IP-CAN session request message to the P-GW, where the message carries the NAI identifier of the UE, the PDN identifier, and the IP-CAN type or RAT type of the access network.
  • the establishment of the IP-CAN session request message is an agent binding update message when implemented.
  • step 204 can be performed simultaneously with step 202 without waiting for step 203 to return. Message.
  • Step 205 The P-GW allocates an IP address to the UE, and the PCEF that resides in the P-GW sends an IP-CAN session establishment indication message to the PCRF, where the message carries the user identifier, the IP address assigned to the UE, the PDN identifier, and the Develop policy access information.
  • the access information used to formulate the policy is: the IP-CAN type or the RAT type reported in step 204.
  • the Gx session established by the IP-CAN session setup indication message is called Gx Session 1.
  • Step 206 The PCRF associates the Gx session 1 with the Gxx session established in step 202 (the Gxx session is also referred to as a gateway control session) according to the user identity.
  • the PCRF sends the previously established PCC rules and event triggers to the PCEF via an IP-CAN session setup confirmation message. Since there is currently only one BBERF, the BBERF can be considered a Primary BBERF. Of course, the PCRF can also determine that the BBERF is Primary BBERF according to the IP-CAN type reported in step 205 and the IP-CAN type reported in step 202.
  • the PCEF After receiving the acknowledgment message, the PCEF installs the issued PCC rules and event triggers, and the PCRF can also modify the established PCC rules according to the access information provided by the PCEF for formulating policies. Then, the PCRF sends the modified PCF rules. PCC rules.
  • Step 207 The P-GW returns an IP-CAN session response to the gateway where the BBERF is located.
  • the IP-CAN session response is established as a proxy binding update acknowledgement message.
  • the establishment of the IP-CAN Session Reply message can be initiated without waiting for the acknowledgment message of step 206.
  • Step 208 The gateway where the BBERF is located returns to establish an IP-CAN session response.
  • FIG. 3 is a flow chart of an IP-CAN session modification of an existing UE accessing an EPS through an E-UTRAN or a trusted non-3GPP access gateway. It is assumed that after accessing the EPS to establish an IP-CAN session as shown in FIG. 2, due to BBERF A reselection occurs, such as an IP-CAN session modification caused by a handover of the UE or a cross-system pre-registration by the UE. It is assumed that when accessing through E-UTRAN, the PMIPv6 protocol is used between the S-GW and the P-GW, and when accessing through a trusted non-3GPP access gateway, the PMIPv6 protocol is used between the access gateway and the P-GW.
  • Step 301 The new BBERF (New BBERF) receives the setup gateway control session request message, and the new BBERF obtains the user identifier, the PDN identifier, and the access information used to formulate the policy, and the access information includes the network identifier of the New BBERF, and the UE Current location information, IP-CAN type or IP-CAN type and RAT type of the access network.
  • the new BBERF receives the setup gateway control session request message, and the new BBERF obtains the user identifier, the PDN identifier, and the access information used to formulate the policy, and the access information includes the network identifier of the New BBERF, and the UE Current location information, IP-CAN type or IP-CAN type and RAT type of the access network.
  • Step 302 The new BBERF sends a gateway control session establishment indication message to the PCRF, where the gateway control session establishment indication message carries the user identifier, the PDN identifier, and the access information used for formulating the policy, and the access information includes the location of the New BBERF.
  • a Gxx session established by a gateway control session establishment indication message (a Gxx session is also referred to as a gateway control session) is represented as a Gxx session 2.
  • Step 303 The PCRF associates the Gxx session 2 with the Subsession1 according to the user ID and the PDN identifier.
  • the PCRF sends a Gateway Control Session Establishment Confirmation message to the New BBERF, which carries QoS rules and event triggers.
  • the PCRF re-defines the QoS rules based on the UE's new access information.
  • the PCRF will determine which BBERF is Primary BBERF and which is Non-primary BBERF. If the new access network IP-CAN type reported by the New BBERF in step 302 is inconsistent with the IP-CAN type of the access network on the PCEF in step 205 of FIG. 2, the PCRF determines that the New BBERF is a Non-Primary BBERF. Old BBERF is still Primary BBERF.
  • the PCRF will perform different operations for Primary BBERF and Non-Primary BBERF.
  • the process of the UE performing cross-system pre-registration ends here, and the process of UE handover continues with the following steps.
  • Step 304 The gateway where the new BBERF is located sends an IP-CAN session signaling message to the P-GW, where the message carries the user identifier and the PDN identifier.
  • the message is implemented as a proxy binding update message for PMIPv6.
  • the message carries the new access network IP-CAN type or IP-CAN type and RAT type.
  • the IP-CAN session modification indication message is sent to the PCRF, where the message carries the UE-switched access information, including the new access network IP-CAN type or IP-CAN type and RAT type.
  • Step 306 The PCRF determines, according to the access information reported by the Gx session 1 and the access network information reported by the Gxx session 1 and the Gxx session 2, that the New BBERF is Primary BBERF and the Old BBERF is Non-Primary BBERF.
  • the new access network IP-CAN type on the PCEF in step 306 is the same as the new access network IP-CAN type reported by New BBERF in step 302. Therefore, the PCRF determines that the New BBERF is Primary BBERF, Old BBERF. For Non-Primary BBERF.
  • the PCRF re-forms the PCC rules, QoS rules, and event triggers based on the access information reported by the New BBERF, user subscription data, and network policies.
  • the PCRF returns an IP-CAN Session Modification Confirmation message to the PCEF carrying the updated PCC rules and event triggers.
  • Step 307 The P-GW returns an IP-CAN session signaling message to the gateway where the New BBERF is located, and the message is implemented as a proxy binding update acknowledgement message.
  • Step 308 The gateway where the New BBERF is located returns a gateway control session response message.
  • Step 309 The PCRF passes the updated QoS rule and event trigger through the Gxx session 2, and carries it in the gateway control and QoS rule providing message to the New BBERF.
  • Step 310 New BBERF installs and executes QoS rules and event triggers, and returns a confirmation message to the PCRF to return the gateway control and QoS rules.
  • the PCRF also sends updated QoS rules and event triggers to the Old BBERF.
  • the PCRF sends QoS rules and event triggers to the Old BBERF via Gxx Session 1 for the Qos rules and event triggers.
  • BBERF In the process of BBERF reselection, PCRF controls 2 simultaneously. BBERF, and based on BBERF categories, such as Primary and Non-Primary for policy control.
  • BBERF and based on BBERF categories, such as Primary and Non-Primary for policy control.
  • the prior art only discloses a processing flow for establishing a gateway control session request in a scenario where the PCRF simultaneously controls two BBERFs, and the processing flow for the gateway control session termination indication message sent by one of the BBERFs is not disclosed.
  • the PCRF simultaneously controls more than two BBERFs
  • after the PCRF receives the gateway control session termination indication message sent by one of the BBERFs how to deal with it is still an unsolved problem. Summary of the invention
  • the main purpose of the present invention is to provide a processing method and system for multi-bearing binding and event reporting, and implement gateway control for BBERF transmission in a scenario where two or more BBERFs are simultaneously controlled by a PCRF.
  • the processing of the session termination indication message fills the technical gap in this processing area.
  • a method for processing a multi-bearer binding and event reporting function comprising: a policy and charging rule function (PCRF) receiving a bearer binding and event reporting function (BBERF) gateway control session termination indication message, when When the PCRF determines that the category of the BBERF is the primary BBERF, the PCRF will initiate a gateway control session termination request for terminating all non-primary BBERFs.
  • PCRF policy and charging rule function
  • BBERF bearer binding and event reporting function
  • the method further includes:
  • the PCRF receives the gateway control session termination indication message of the first BBERF.
  • the PCRF determines that the first BBERF is the primary BBERF and the second BBERF is the non-primary BBERF, the PCRF initiates a gateway control session termination request for terminating the second BBERF.
  • the method further includes:
  • the second BBERF deletes its own related policy control information, and sends a gateway control session termination indication message to the PCRF; the PCRF deletes the second BBERF related policy control information.
  • the method further includes: The vPCRF receives the gateway control session termination indication message of the first BBERF.
  • the vPCRF determines that the first BBERF is the primary BBERF and the second BBERF is the non-primary BBERF, the vPCRF initiates a gateway control session termination request for terminating the second BBERF.
  • the vPCRF After the vPCRF initiates a gateway control session termination request to the second BBERF, the vPCRF further includes:
  • the second BBERF deletes its own related policy control information, and sends a gateway control session termination indication message to the vPCRF; the vPCRF deletes the second BBERF related policy control information.
  • the method further includes:
  • the vPCRF receives the gateway control session termination indication message of the first BBERF, and the vPCRF sends an S9 session modification indication message to the hPCRF.
  • the hPCRF determines that the first BBERF is the primary BBERF and the second BBERF is the non-primary BBERF, the hPCRF will initiate the termination of the second
  • the gateway of the BBERF controls the session termination request message, the S9 subsession or the S9 session corresponding to the initiation of the termination.
  • the hPCRF further determines that the current S9 sub-session corresponding to the first BBERF or the second BBERF is the last sub-session of the S9 session; the hPCRF initiates a gateway control session termination request message that terminates the second BBERF, and initiates the termination. After the corresponding S9 session, it also includes:
  • the hPCRF sends an S9 session termination request message to the vPCRF, and carries the session termination indication. After the vPCRF deletes all the policy control information related to the S9 session, the vPCRF sends an S9 session termination indication message to the hPCRF. The hPCRF deletes all the policy control information related to the S9 session.
  • the vPCRF sends a gateway control session termination request message to the second BBERF; the second BBERF deletes its own associated policy control information, and sends a gateway control session termination indication message to the vPCRF; the vPCRF deletes the second BBERF related policy control information.
  • the hPCRF When the hPCRF further determines that the current S9 sub-session corresponding to the first BBERF or the second BBERF is not the last sub-session of the S9 session, the hPCRF initiates a gateway control session termination request message for terminating the second BBERF, and initiates termination.
  • S9 subsession Includes:
  • the hPCRF sends an S9 session modification request message to the vPCRF, and carries a session termination indication; the vPCRF deletes all policy control information related to the S9 subsession;
  • the vPCRF sends a gateway control session termination request message to the second BBERF; the second BBERF deletes its own associated policy control information, and sends a gateway control session termination indication message to the vPCRF; the vPCRF deletes the second BBERF related policy control information.
  • a processing system for multi-bearing binding and event reporting comprising: a determining unit, configured to: the PCRF receives a BBERF gateway control session termination indication message, when the PCRF determines that the BBERF category is a primary BBERF The PCRF will initiate a gateway control session termination request that terminates all non-primary BBERFs.
  • the determining unit is further configured to: when the PCRF determines that the first BBERF is the primary BBERF and the second BBERF is the non-primary BBERF, the PCRF initiates a gateway control session termination request for terminating the second BBERF.
  • the determining unit is further configured to: when the vPCRF determines that the first BBERF is the primary BBERF, and the second BBERF is the non-primary BBERF, the vPCRF initiates the termination of the second BBERF gateway control session. request.
  • the judging unit is further configured to: when the hPCRF determines that the first BBERF is the primary BBERF and the second BBERF is the non-primary BBERF, the hPCRF initiates the termination of the second BBERF gateway control session. Request a message, initiate a corresponding S9 subsession or an S9 session.
  • the PCRF of the present invention receives the gateway control session termination indication message of the BBERF.
  • the PCRF determines that the BBERF class is Primary BBERF, the PCRF will initiate a gateway control session termination request for terminating all other Non-Primary BBERFs.
  • the processing of the gateway control session termination indication message sent by the BBERF is implemented, thereby The PCRF is able to respond correctly to any of the BBERF's gateway control session termination indication messages.
  • Figure 1 is a schematic diagram showing the composition of a system architecture of an existing EPS
  • FIG. 2 is a flow chart of establishing an IP-CAN session for an existing UE to access an EPS through an E-UTRAN or a trusted non-3GPP access gateway;
  • FIG. 3 is a flow chart of tampering of an IP-CAN session in which an existing UE accesses an EPS through an E-UTRAN or a trusted non-3GPP access gateway;
  • Embodiment 4 is a flow chart of Embodiment 1 of a method for processing a multi-bearing binding and event reporting function according to the present invention
  • FIG. 5 is a flowchart of Embodiment 3 of a method for processing a multi-bearer binding and event reporting function. detailed description
  • the basic idea of the present invention is: When the PCRF responds to any of the BBERF gateways to control the session termination indication message, when the PCRF determines that the BBERF class is Primary BBERF, the PCRF will initiate termination of all other Non-Primary BBERF gateway control sessions. request.
  • a method for processing a multi-bearer binding and event reporting function includes: the PCRF receives a BBERF gateway control session termination indication message, and when the PCRF determines that the BBERF category is a primary BBERF, the PCRF initiates termination of all other non-primary The BBERF gateway controls the session termination request.
  • the PCRF receives the gateway control session termination indication message of any one of the BBERFs of the two or more BBERFs.
  • the PCRF determines the BBERF.
  • the category is Primary BBERF, and the PCRF will initiate a gateway control session for all other Non-Primary BBERFs. End the request.
  • the method further includes: after receiving the BBERF gateway control session termination indication message, the PCRF deletes the BBERF related policy control information.
  • the first scenario In a non-roaming scenario, one PCRF controls two BBERFs simultaneously.
  • the method further includes the steps of:
  • Step 321 After receiving the gateway control session termination indication message of the first BBERF, the PCRF deletes the policy control information related to the first BBERF.
  • Step 322 When the PCRF determines that the first BBERF is Primary BBERF and the second BBERF is Non-Primary BBERF, the PCRF initiates a gateway control session termination request for terminating the second BBERF.
  • the method further includes: after the PCRF sends the gateway control session termination request message to the second BBERF, the second BBERF deletes the related policy control information, and sends a gateway control session termination indication message to the PCRF; the PCRF deletes the second BBERF related Policy control information.
  • the second scenario The UE controls the two BBERFs simultaneously in the local grooming roaming scenario.
  • the vPCRF initiates a gateway to control the session termination request.
  • the method further includes the following steps:
  • Step 331 After receiving the gateway control session termination indication message of the first BBERF, the vPCRF deletes the policy control information related to the first BBERF.
  • Step 332 When the vPCRF determines that the first BBERF is Primary BBERF, the second BBERF For Non-Primary BBERF, the vPCRF will initiate a gateway control session termination request that terminates the second BBERF.
  • the method further includes: after the vPCRF sends the gateway control session termination request message to the second BBERF, the second BBERF deletes the related policy control information, and sends a gateway control session termination indication message to the vPCRF; the vPCRF deletes the second BBERF related Policy control information.
  • the third scenario In the roaming scenario of the home route, the two PCRFs control the two BBERFs at the same time.
  • the two PCRFs are the hPCRF and the vPCRF respectively.
  • the hPCRF initiates the gateway to control the session termination request.
  • the method further includes the following steps:
  • Step 341 After receiving the gateway control session termination indication message of the first BBERF, the vPCRF sends an S9 session modification indication message to the hPCRF. The hPCRF deletes the first BBERF address and the session termination indication carried in the S9 session modification indication message. BBERF related policy control information.
  • Step 342 When the hPCRF determines that the first BBERF is Primary BBERF and the second BBERF is Non-Primary BBERF, the hPCRF initiates a gateway control session termination request message for terminating the second BBERF, and initiates an S9 subsession or S9 session corresponding to the termination.
  • the step 342 further includes:
  • Step 3421 the hPCRF sends an S9 session termination request message to the vPCRF, and carries the session termination indication.
  • the SPCR session sends the S9 session termination indication message to the hPCRF.
  • the hPCRF deletes all the policy control information related to the S9 session. .
  • Step 3421b The vPCRF sends a gateway control session termination request message to the second BBERF.
  • the second BBERF deletes the related policy control information, and sends a gateway control session termination indication message to the vPCRF.
  • the vPCRF deletes the second BBERF related policy control information.
  • the step 332 further includes:
  • Step 3422a The hPCRF sends an S9 session modification request message to the vPCRF, and carries a session termination indication.
  • the vPCRF deletes all policy control information related to the S9 subsession.
  • Step 3422b The vPCRF sends a gateway control session termination request message to the second BBERF.
  • the second BBERF deletes the related policy control information, and sends a gateway control session termination indication message to the vPCRF.
  • the vPCRF deletes the second BBERF related policy control information.
  • the present invention mainly includes the following contents:
  • the PCRF receives the BBERF gateway control session termination indication message and deletes the BBERF related policy control.
  • the PCRF determines the type of the BBERF. If the BBERF is Primary BBERF, the PCRF initiates a gateway control session for terminating all other Non-Primary BBERFs.
  • the invention is illustrated by way of example below.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • a UE may perform a BBERF reselection process and a UE pre-registration across a system in a non-roaming scenario. It is assumed that the PCRF simultaneously controls two BBERFs, as shown by BBERF 1 and BBERF2 in Figure 4; and assumes that the UE uses the PMIPv6 protocol when accessing the EPS through the access network where BBERF 1 and BBERF2 are located.
  • Step 401 Upon receiving the trigger, BBERF1 decides to terminate its gateway control session with the PCRF.
  • the triggering of the gateway control session of terminating BBERF1 and PCRF may come from the UE, or the P-GW, or BBERF1 itself.
  • Step 402 BBERF 1 sends a gateway control session termination indication message to the PCRF.
  • Step 403 The PCRF deletes the BBERF1 related policy control information, including the QoS rule, Event triggers, etc.
  • Step 404 The PCRF returns a gateway control session termination confirmation message to the BBERF1.
  • Step 405 If the PCRF determines that BBERF1 is Primary BBERF, the PCRF decides to initiate a gateway control session that terminates other Non-Primary BBERFs. Thus, the PCRF sends a PCRF-initiated gateway control session termination request message to BBERF2.
  • Step 406 After receiving the gateway control session termination request message, the BBERF2 returns an acknowledgement message to the PCRF.
  • Step 407 After deleting the related policy control information, the BBERF2 sends a gateway control session termination indication message to the PCRF.
  • Step 408 After the PCRF deletes the BBERF2 related policy control information, the PCR message returns a confirmation message to the BBERF2.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the gateway control session termination process is similar to the non-roaming scenario, except that the embodiment is First, the PCRF initiates a gateway to control the session termination request.
  • the vPCRF initiates a gateway to control the session termination request.
  • the PCRF in FIG. 4 serves as a vPCRF.
  • the vPCRF When the vPCRF receives the gateway control session termination indication message sent by the BBERF1, if the vPCRF determines that the BBERF1 is the Primary BBERF, the vPCRF decides to initiate a gateway control session for terminating the other Non-Primary BBERF. Thus, the vPCRF sends a PCRF initiated gateway control session termination request message to BBERF2.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • FIG. 5 is a flowchart of a method for processing a multi-bearing binding and event reporting function according to the present invention.
  • the UE may perform the BBERF re-selection process and the UE cross-system pre-registration after the home routing roaming scenario. It is assumed that the hPCRF controls two BBERFs simultaneously, such as BBERF1 and BBERF2 in Figure 5; and the UE accesses through the access network where BBERF1 and BBERF2 are located.
  • the EPS is used in the PMIPv6 protocol.
  • Step 501 The BBERF1 receives the trigger and decides to terminate its gateway control session with the vPCRF. Among them, BEERF 1 is the visited place BBERF.
  • the triggering of the gateway control session of terminating BBERF1 and vPCRF may come from
  • UE or P-GW, or BBERFl itself.
  • Step 502 The BBERF1 sends a gateway control session termination indication message to the vPCRF.
  • Step 503 The vPCRF finds an S9 session corresponding to the gateway control session and a subsession (Subsession1) of the corresponding S9 session.
  • the vPCRF sends an S9 session modification indication message to the hPCRF, and carries the BBERF1 address and the session termination indication in the Subsessinl.
  • the BBERFl address and session termination indication are carried at the S9 subsession level.
  • the session termination indication indicates that the visited gateway control session is terminated.
  • Step 504 The hPCRF deletes the BBERF1 related policy control information, including the QoS rule, the event trigger, and the like according to the BBERF1 address and the session termination indication.
  • Step 505 The hPCRF returns an S9 session modification confirmation message to the vPCRF.
  • Step 506 The vPCRF deletes the BBERF1 related policy control information and returns a gateway control session termination confirmation message to the BBERF1.
  • the hPCRFPCRF decides to initiate a gateway control session for terminating other Non-Primary BBERFs and a corresponding S9 subsession or S9 session. If Subsession1 corresponding to BBERF 1 or BBERF2 is the last subsession of the S9 session, go to Step 507 to Step 510. Otherwise, go to Step 511 to Step 512.
  • Step 507 The hPCRF sends an S9 session termination request initiated by the hPCRF to the vPCRF, and carries a session termination indication at the command level.
  • Step 508 The vPCRF returns an acknowledgement message to the hPCRF.
  • Step 509 After the vPCRF deletes all policy control information related to the S9 session, the hPCRF is sent to the hPCRF. Send an S9 session termination indication message.
  • Step 510 The hPCRF deletes all related policy control information and returns an acknowledgement message.
  • Step 512 After the vPCRF deletes the policy control information related to Subsession1, the vPCRF returns an acknowledgement message to the hPCRF.
  • Step 513 The vPCRF decides to initiate a gateway control session that terminates other Non-Primary BBERFs. Thus, the vPCRF sends a PCRF initiated gateway control session termination request message to BBERF2.
  • Step 514 After receiving the request message, the BBERF2 returns a gateway control session termination confirmation message to the vPCRF.
  • Step 515 After deleting the related policy control information, the BBERF2 sends a gateway control session termination indication message to the vPCRF.
  • Step 516 After the vPCRF deletes the BBERF2 related policy control information, it returns a confirmation message to BBERF2.
  • a processing system for multi-bearing binding and event reporting comprising a judging unit, a judging unit, configured to send a BBERF gateway control session termination indication message by the PCRF, and when the PCRF determines that the BBERF category is a Primary BBERF, the PCRF A gateway control session termination request that terminates all other Non-Primary BBERFs will be initiated.
  • the system further includes a deleting unit, and the deleting unit is configured to receive the BBERF gateway control session termination indication message by the PCRF, and delete the BBERF related policy control information.
  • the first scenario In a non-roaming scenario.
  • the deleting unit is further configured to delete the first BBERF-related policy control information after the PCRF receives the gateway control session termination indication message of the first BBERF.
  • the judging unit is further configured to: when the PCRF determines that the first BBERF is a Primary BBERF, and the second BBERF is a Non-Primary BBERF, the PCRF initiates a gateway control session termination request for terminating the second BBERF.
  • the second scenario in a localized roaming scenario.
  • the deleting unit is further configured to: after the vPCRF receives the gateway control session termination indication message of the first BBERF, delete the first BBERF related policy control information.
  • the judging unit is further configured to: when the vPCRF determines that the first BBERF is Primary BBERF, and the second BBERF is Non-Primary BBERF, the vPCRF initiates a gateway control session termination request for terminating the second BBERF.
  • the third scenario Under the roaming scenario of home routing.
  • the deleting unit is further configured to: after the vPCRF receives the gateway control session termination indication message of the first BBERF, the vPCRF sends an S9 session modification indication message to the hPCRF; the hPCRF receives the first BBERF address and the session termination carried in the S9 session modification indication message. Instruct to delete the first BBERF related policy control information.
  • the judging unit is further configured to: when the hPCRF determines that the first BBERF is a Primary BBERF, and the second BBERF is a Non-Primary BBERF, the hPCRF initiates a gateway control session termination request message for terminating the second BBERF, and initiates an S9 subsession corresponding to the termination or S9. Conversation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention porte sur un procédé de traitement de multiples fonctions d'association de support et de rapport d'événement (BBERF). Le procédé comprend les opérations suivantes : une fonction de règles de politique et de facturation (PCRF) reçoit un message d'indication de terminaison de session de commande de passerelle provenant d'une BBERF; et lorsqu'elle détermine que le type de la BBERF est la BBERF primaire, la PCRF envoie une requête de terminaison de session de commande de passerelle afin de terminer toutes les BBERF non primaires. La présente invention porte également sur un système de traitement de multiples BBERF. Dans le système, une unité de détermination est utilisée pour recevoir un message d'indication de terminaison de session de commande de passerelle provenant d'une BBERF et déterminer que le type de la BBERF est une BBERF primaire, et une PCRF enverra une requête de terminaison de session de commande de passerelle afin de terminer toutes les BBERF non primaires. Le procédé et le système de la présente invention mettent en œuvre le traitement de messages d'indication de terminaison de session de commande de passerelle envoyés par des BBERF.
PCT/CN2010/075388 2009-09-11 2010-07-22 Procédé et système de traitement de multiples fonctions d'association de support et de rapport d'événement WO2011029349A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2009100929318A CN102026296A (zh) 2009-09-11 2009-09-11 多承载绑定和事件报告功能的处理方法及系统
CN200910092931.8 2009-09-11

Publications (1)

Publication Number Publication Date
WO2011029349A1 true WO2011029349A1 (fr) 2011-03-17

Family

ID=43731988

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/075388 WO2011029349A1 (fr) 2009-09-11 2010-07-22 Procédé et système de traitement de multiples fonctions d'association de support et de rapport d'événement

Country Status (2)

Country Link
CN (1) CN102026296A (fr)
WO (1) WO2011029349A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8768295B2 (en) 2010-02-18 2014-07-01 Alcatel Lucent Method of handling a change to bearer control mode
WO2013049587A2 (fr) 2011-09-29 2013-04-04 Interdigital Patent Holdings Inc. Procédé et appareil pour permettre l'accès à des applications intégrées à un réseau visité
CN110035424B (zh) * 2018-01-12 2021-10-19 华为技术有限公司 策略相关的通信方法、装置和系统

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101355806A (zh) * 2008-08-29 2009-01-28 中兴通讯股份有限公司 网络会话释放方法、装置及系统

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101355806A (zh) * 2008-08-29 2009-01-28 中兴通讯股份有限公司 网络会话释放方法、装置及系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3GPP TSG-CT WG3 Meeting #54, C3-090904,24-28 Aug. 2009(24-28.08.2009)", article ALCATEL-LUCENT: "Non-Primary BBERF GW Control Session Termination", pages: 6 *
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control signalling flows and QoS parameter mapping; (Release 8)", 3GPP TS 29.213 V8.4.0, May 2009 (2009-05-01) *

Also Published As

Publication number Publication date
CN102026296A (zh) 2011-04-20

Similar Documents

Publication Publication Date Title
US9137652B2 (en) Method for implementing policy and charging control in a roaming scene
US8811342B2 (en) Method and system for deleting redundant information of home policy and charging rules function
EP2424160B1 (fr) Procédé pour mettre en uvre une commande de politique et de facturation limitée et système associé
US9351325B2 (en) Policy control method and system for converged network
US8621555B2 (en) Access control method and system for packet data network, PCRF entity
US8874715B2 (en) Charging method, system and reporting method for terminal accessing through multiple access networks
EP2302842B1 (fr) Procédé d envoi et d installation d un déclencheur d évènement
US20110161504A1 (en) Method and apparatus for identifying session information
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
WO2009135362A1 (fr) Procédé de commande de politique et de facturation pour cacher la topologie d'un réseau visité
WO2011011943A1 (fr) Procédé pour la ré-sélection de fonction de liaison de support et de rapport d’événements
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
WO2011029289A1 (fr) Procédé et système de transmission d'un mode de commande de support dans des scénarios d'itinérance
WO2012006909A1 (fr) Procédé et système de rapport d'informations d'accès à un réseau fixe
WO2009124436A1 (fr) Procédé et système de contrôle de politique bberf
WO2014094488A1 (fr) Procédé et dispositif de gestion de politique de facturation destinés à un service local d'itinérance
WO2014107985A1 (fr) Procédé de facturation en ligne de services d'itinérance locale, h-ocs et v-ocs
WO2011018020A1 (fr) Procede et systeme de commande d'equilibre de charge de pcrf et dra de redirection
WO2012129992A1 (fr) Procédé de traitement de connectivité de données sponsorisées, et fonction d'imputation et de règles
WO2011029349A1 (fr) Procédé et système de traitement de multiples fonctions d'association de support et de rapport d'événement
WO2012155774A1 (fr) Procédé, système d'établissement d'une sous-session s9, et fonction "règles de politique et de facturation"
WO2013113263A1 (fr) Procédé et système d'identification de mode fonction de commande de détection d'application
WO2013023515A1 (fr) Procédé et système permettant de résoudre un conflit de contrôle de la politique de qualité de service
WO2014079323A1 (fr) Procédé, dispositif, et système, pour exécuter une fonction de service local d'itinérance
WO2012126311A1 (fr) Procédé et système de création et de suppression d'informations d'association dans un agent de routage diameter, h-pcrf

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

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

Country of ref document: EP

Kind code of ref document: A1