WO2010121460A1 - 一种实现有限策略计费控制的方法及系统 - Google Patents

一种实现有限策略计费控制的方法及系统 Download PDF

Info

Publication number
WO2010121460A1
WO2010121460A1 PCT/CN2009/073835 CN2009073835W WO2010121460A1 WO 2010121460 A1 WO2010121460 A1 WO 2010121460A1 CN 2009073835 W CN2009073835 W CN 2009073835W WO 2010121460 A1 WO2010121460 A1 WO 2010121460A1
Authority
WO
WIPO (PCT)
Prior art keywords
pcrf
pcc
message
network
event
Prior art date
Application number
PCT/CN2009/073835
Other languages
English (en)
French (fr)
Inventor
周晓云
宗在峰
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US13/259,957 priority Critical patent/US8817612B2/en
Priority to EP09843564.7A priority patent/EP2424160B1/en
Publication of WO2010121460A1 publication Critical patent/WO2010121460A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • 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

Definitions

  • the present invention relates to a method and system for implementing limited policy charging control. Background technique
  • Evolved Packet System consists of Evolved Universal Terrestrial Radio Access (Evolved Universal Terrestrial Radio Access) Network, referred to as E-UTRAN), Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (PDN GW or P-GW) , Home Subscriber Server (HSS), 3GPP's Authentication, Authorization and Accounting (AAA) server, Policy and Charging Rules Function (PCRF) and Other support nodes are composed.
  • E-UTRAN Evolved Universal Terrestrial Radio Access
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • PDN GW or P-GW Packet Data Network Gateway
  • HSS Home Subscriber Server
  • AAA Authentication, Authorization and Accounting
  • PCRF Policy and Charging Rules Function
  • the MME is used for control plane related operations 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, in the E-UTRAN and The data is forwarded between the P-GWs and used to buffer the paging waiting data.
  • the P-GW is a border gateway between the EPS and the PDN, and is used for PDN access and forwarding data between the EPS and the PDN.
  • EPS supports interworking with non-3GPP systems.
  • the interworking with the non-3GPP system is implemented through the S2a, S2b, and S2c interfaces, and the P-GW serves as an anchor point between the 3GPP system and the non-3GPP system.
  • the non-3GPP system is divided into a trusted non-3GPP access system and an untrusted non-3GPP access system.
  • the trusted non-3GPP access system can be directly connected to the P-GW through the S2a interface; the untrusted non-3GPP access system needs to be connected to the P-GW through an Evolved Packet Data Gateway (ePDG), ePDG and P -
  • ePDG Evolved Packet Data Gateway
  • ePDG Evolved Packet Data Gateway
  • the S2c interface provides user plane-related control and mobility support between the User Equipment (UE) and the P-GW.
  • the supported mobility management protocol is dual-stack mobile IPv6 (Moblie IPv6 support for dual stack Hosts). And Routers, referred to as DSMIPv6).
  • the EPS system introduces the Policy and Charging Control (PCC) function framework to perform dynamic policy charging control for user service access.
  • PCC Policy and Charging Control
  • AF Application Function
  • PCRF Policy control and charging rule function entity
  • the PCRF is the core of the PCC and is responsible for policy decision making and billing rules.
  • the PCRF provides network control rules based on service data flows, including traffic data flow detection, Gating Control, Quality of Service (QoS) control, and data flow based charging rules.
  • the PCRF sends its policy and charging rules to the Policy and Control Enforcement Function (PCEF).
  • PCEF Policy and Control Enforcement Function
  • the basis for formulating policies and charging rules by the PCRF includes: obtaining information related to the service from the AF, obtaining subscription information related to the user policy charging control from the Subscription Profile Repository (SPR), and obtaining the subscription information from the PCEF through the Gx interface. Information about the bearer-related network.
  • SPR Subscription Profile Repository
  • the PCEF is usually located in the Gate-Way (GW) and performs the policy and charging rules defined by the PCRF on the bearer plane.
  • the PCEF detects the service data flow according to the service data flow filter in the rule sent by the PCRF, and then executes the policy and charging rules formulated by the PCRF for these service data flows.
  • the PCEF performs QoS authorization according to the rules sent by the PCRF, and performs gate control according to the execution of the AF.
  • the PCEF triggers reporting of events occurring on the bearer network according to events subscribed by the PCRF.
  • the PCEF performs a corresponding service data flow charging operation, and the charging can be either online charging or offline charging.
  • the PCEF In the case of online charging, the PCEF needs to perform credit management together with the Online Charging System (OCS). In the case of offline charging, the PCEF and the Offline Charging System (OFCS) exchange relevant charging information.
  • the interface between the PCEF and the PCRF is a Gx interface
  • the interface between the OCE and the OCS is a Gy interface
  • the interface between the OFCS and the OFCS is a Gz interface.
  • the PCEF is generally located on the gateway of the network, such as the Packet Data Network Gateway (PDN-GW) of the EPS, the GPRS Gateway Support Node (GGSN) in the GPRS (General Packet Radio Service), and the I-WLAN (Interworking WLAN).
  • Packet Data Gateway (PDG) in the Internet (Internet Protocol).
  • BBERF Bit Binding and Event Reporting Function
  • the S-GW exists.
  • BBERF When the user equipment accesses through a trusted non-3GPP access network, BBERF also exists in the trusted non-3GPP access gateway.
  • MIP Mobile Internet Protocol
  • the PCEF cannot perform the establishment, modification, and deletion of the bearer according to the PCC rules, and may also fail to report the trigger. event. At this time, the establishment, modification and deletion of the bearer and the event reporting function are completed by BBERF.
  • the PCRF interacts with the BBERF via the Gxx interface.
  • the User Contracted Database stores user policy charging control subscription information related to policy control and charging.
  • the interface between SPR and PCRF is the Sp interface.
  • the online charging system (OCS) and PCEF are used to control and manage user credits in the online charging mode.
  • the offline charging system (OFCS) and the PCEF complete the charging operation in the offline charging mode.
  • the AF needs to subscribe to the PCRF for the AF signaling transmission path status notification.
  • the PCRF subscribes to the corresponding event to the PCEF.
  • the PCEF detects the corresponding event (for example, the bearer of the transmission AF signaling is lost or released)
  • the PCEF reports the transmission AF signal bearer loss or release to the PCRF, so that the PCRF notifies the AF of the event (or state).
  • the PMIPv6 protocol is used, or when the user equipment accesses through the trusted non-3GPP access gateway and uses DSMIPv6 (Dual Stack Mobile Internet Protocol version 6, double stack mobile IP protocol version 6) or MIPv4 protocol, it is located at P.
  • DSMIPv6 Dual Stack Mobile Internet Protocol version 6, double stack mobile IP protocol version 6
  • MIPv4 protocol MIPv4 protocol
  • AF may also subscribe to the IP-CAN (IP-Connectivity Access Network) type change notification to the PCRF.
  • the PCRF subscribes to the AF subscription and then subscribes to the BBERF for the event.
  • the BBERF detects the packet and reports it to the PCRF.
  • the PCRF reports the IP-CAN type and the specific RAT of the IP-CAN type (Radio Access Technology, Wireless Access Technology). The type changes, so that the PCRF reports the information to the AF.
  • IP-CAN IP-Connectivity Access Network
  • the PCEF located in the P-GW cannot accurately detect the IP.
  • - Change in RAT type in the CAN type the PCRF can only subscribe to the BBERF for the IP-CAN type change notification. The BBERF detects the event and reports the event to the PCRF. The PCRF reports the result to the AF.
  • the AF may also subscribe to the PCRF for notification of whether the resource requested for the service is successfully assigned.
  • the PCRF subscribes to the AF subscription and then subscribes the event to the BBERF. After the BBERF assignment succeeds or fails, the BBERF reports the success or failure to the PCRF, and the PCRF reports the indication to the AF.
  • the P-GW is located in the home network
  • the S-GW or the trusted non-3GPP access gateway is located in the visited network. If the home network is deployed with the PCC and the visited network does not deploy the PCC, The visited network was unable to subscribe to the event on the PCRF, so the PCRF could not be uploaded to the AF.
  • the UE when the UE is connected to the PCRF and the non-3GPP access network and the 3GPP network belong to different operators, if the PCC is deployed on the 3GPP network instead of the 3GPP network, the non-3GPP network cannot report to the PCRF. The event is subscribed, so the PCRF is also unable to report to the AF.
  • the AF determines whether the visited network of the UE is deployed with the PCC according to its own configuration information (such as the roaming protocol) (that is, whether the current deployment is a limited PCC deployment scenario).
  • the AF does not subscribe to certain events to the PCRF (such as transmitting AF signaling). Path status notification, IP-CAN type change notification, and request to assign resource success or failure notifications).
  • the main problem of the method is that the configuration information is relatively complicated, especially when the AF is a third party providing services, the update of the configuration information is difficult, and when visiting the network or a part of the S-GW or the trusted non-3GPP access gateway in the non-3GPP network
  • AF cannot simply decide whether to subscribe to an event based on the visited network where the UE is located.
  • the technical problem to be solved by the present invention is to overcome the deficiencies of the prior art and provide a method and system for implementing limited policy charging control, so as to make it easier for AF to know whether it is currently a limited policy charging control deployment (ie, visiting a network). No PCC is deployed, dynamic PCC is not supported).
  • the present invention provides a method for implementing limited policy charging control, the method comprising:
  • the policy and charging rule function entity PCRF determines whether the visited network of the user equipment UE roaming supports the policy charging control PCC. If the visited network does not support the PCC, the application function AF is notified that the subscribed event cannot be reported.
  • the PCRF may send a message to the application function AF, and the message may carry an identifier indicating the limited policy charging control deployment.
  • the AF does not subscribe to the event, and/or subscribe to the cancellation event according to the identifier.
  • the PCRF determines whether the visited network supports the PCC in the following manner:
  • the PCRF receives the IP bearer network connection access network IP-CAN session establishment indication message, or the IP-CAN session modification indication message, determines whether the visited network supports the PCC, when the IP-CAN session establishment indication message, or the IP-CAN session modification indication
  • the mobility management protocol carried in the message indicates that the MPT identifier indicates that the protocol used by the access is not the general wireless packet service GPRS tunneling protocol, and the PCRF does not receive the gateway control session establishment indication message, and determines that the visited network does not support the PCC.
  • the PCRF determines whether the visited network supports the PCC in the following manner:
  • the PCRF determines whether the visited network supports the PCC according to the local configuration information and the IP address of the access gateway of the visited network, and/or the care-of address of the UE, and/or the IP address of the serving gateway. In addition, the PCRF determines whether the visited network supports the PCC in the following manner:
  • the policy and charging execution function entity PCEF determines whether the visited network supports the PCC according to the local configuration information and: the IP address of the access gateway of the visited network, and/or the care-of address of the UE, and/or the IP address of the monthly service gateway. And notifying the PCRF of the judgment result, and the PCRF determines whether the visited network supports the PCC according to the judgment result.
  • the PCRF after receiving the application/service information message or the event subscription message sent by the AF, the PCRF includes the identifier for indicating the limited policy control deployment in the corresponding response message and sends it to the AF.
  • the PCRF includes the identifier for indicating the limited policy control deployment to be sent to the AF in the event notification message.
  • the PCRF when the UE switches to an access gateway that does not support the BBERF function, the PCRF notifies the AF that its subscribed event cannot be reported.
  • the PCRF After the PCRF detects that the UE moves to the trusted non-3GPP access network supporting the PCC, the visited 3GPP access network, or the home network, the PCRF sends a limited policy charging control deployment recovery indication identifier to the AF.
  • the present invention further provides a policy and charging rule function entity PCRF, which supports implementing limited policy charging control, and the PCRF is configured to determine whether the visited network of the user equipment UE roaming supports the policy charging control PCC, if the visited network If it is not supported, the application function AF is notified that its subscribed event cannot be reported.
  • PCRF policy and charging rule function entity
  • the PCRF is configured to send a message to the AF, where the message carries an identifier for indicating a limited policy charging control deployment, so that the AF does not perform event subscription, and/or cancel event according to the identifier. subscription.
  • the PCRF is configured to determine whether the visited network supports the PCC in the following manner:
  • the PCRF After receiving the IP bearer network connection access network IP-CAN session establishment indication message or the IP-CAN session modification indication message, the PCRF determines whether the visited network supports the PCC, when the IP-CAN session is established.
  • the indication message, or the mobility management protocol carried in the IP-CAN session modification indication message indicates that the MPT identifier indicates that the protocol used for the access is not a general wireless packet.
  • the service GPRS tunneling protocol does not receive the gateway control session establishment indication message, it is determined that the visited network does not support the PCC.
  • the PCRF is configured to determine whether the visited network supports the PCC in the following manner:
  • the PCRF is configured to determine whether the visited network supports the PCC in the following manner:
  • the policy and charging execution function entity PCEF determines the visit according to the configuration information of the PCRF and the IP address of the access gateway of the visited network, and/or the care-of address of the UE, and/or the IP address of the serving gateway. Whether the network supports the PCC, and notifying the PCRF of the determination result, and the PCRF determines, according to the determination result, whether the visited network supports the PCC.
  • the PCRF is configured to send the unreportable event indication to the AF in the corresponding response message after receiving the application/service information message or the event subscription message sent by the AF.
  • the PCRF is further configured to include an unreportable event indication in the event notification message and send to the AF.
  • the PCRF is further configured to notify the AF that the subscribed event cannot be reported when the UE switches to the access gateway that does not support the BBERF function.
  • the PCRF is further configured to send a limited policy charging to the AF after the PCRF detects that the UE moves to a trusted non-3GPP access network, a visited 3GPP access network, or a home network that supports the PCC. Control the deployment recovery indication ID.
  • the present invention also provides a system for implementing limited policy charging control, including a policy and charging rule functional entity PCRF and an application function AF as described above.
  • a system for implementing limited policy charging control according to the present invention may include: UE, PCRF,
  • the PCRF is configured to determine whether the visited network supports the PCC. If yes, the UE sends a message to the AF, where the message carries an identifier for indicating limited policy charging control deployment.
  • the AF is configured to: after receiving the message carrying the identifier, perform subscription of the event, and/or subscription of the cancellation event according to the identifier.
  • the method and system of the present invention can more conveniently and accurately notify the current policy charging control deployment of the AF when the limited policy charging control is implemented (that is, when the visited network does not support the PCC).
  • the AF can perform corresponding operations according to the current policy charging control deployment situation, for example, no event subscription or cancellation event subscription, so as to save system resources.
  • Figure 1 is a diagram of an existing EPS system architecture
  • FIG. 2 is a schematic diagram of a conventional Rel-8 PCC non-roaming scenario
  • FIG. 3 is a schematic diagram of an application scenario of the first embodiment and the second embodiment of the present invention.
  • FIG. 4 is a flow chart of a method according to a first embodiment of the present invention.
  • Figure 5 is a flow chart of a method of the second embodiment of the present invention.
  • FIG. 6 is a schematic diagram of an application scenario according to a third embodiment of the present invention.
  • Figure 7 is a flow chart of a method of a third embodiment of the present invention.
  • Figure 8 is a flow chart of a method of the fourth embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a limited policy charging control system of the present invention. Preferred embodiment of the invention
  • FIG. 3 is a schematic diagram of an application scenario according to the first embodiment of the present invention.
  • the UE accesses the EPS through the trusted non-3GPP access network and the PMIPv6 protocol; the 3GPP network supports the dynamic PCC, and the trusted non- The 3GPP access network does not support dynamic PCC, and the trusted non-3GPP network and the 3GPP network belong to different operators.
  • the method of the first embodiment of the present invention is shown in Figure 4, and the specific steps are as follows: 401: The UE accesses a trusted non-3GPP access network.
  • the UE After accessing the trusted non-3GPP access network, the UE requests the HSS/AAA to perform EPS access authentication. After receiving the EPS access authentication request, the HSS/AAA authenticates the requesting UE. The HSS/AAA is completed. After the UE is authenticated, the P-GW selection information subscribed by the UE is sent to the trusted non-3GPP access gateway.
  • the layer 3 attach procedure of the UE is triggered.
  • the trusted non-3GPP access gateway selects the P-GW according to the P-GW selection information, and sends a proxy binding update message to the selected P-GW, where the proxy binding update message carries the NAI of the UE (Network Access Identifier, network access identifier) and APN (Access Point Name).
  • NAI Network Access Identifier, network access identifier
  • APN Access Point Name
  • the P-GW After receiving the proxy binding update message, the P-GW sends an IP-CAN session establishment indication to the PCRF, where the IP-CAN session establishment indication carries the NAI of the UE, the IP address and the APN allocated by the P-GW for the UE, and the mobile A Mobility Protocol Type (MPT) identifier; the MPT identifier is used to indicate to the PCRF that the UE is accessed by the PMIPv6 protocol.
  • MPT Mobile A Mobility Protocol Type
  • the MPT identifier can also notify the PCRF that the protocol used by the current access protocol is non-GTP by not carrying the GTP (GPRS Tunneling Protocol) specific parameters. If the message does not carry the Default-EPS-Bearer-QoS, PCRF It can be judged that the current access does not use the GTP protocol.
  • GTP GPRS Tunneling Protocol
  • the PCRF interacts with the SPR to obtain subscription data related to the user access service.
  • the PCRF Since the MPT indicates that the protocol used by the current access is PMIPv6 or other non-GTP protocols, and the PCRF does not receive the gateway control session establishment indication message sent by the trusted non-3GPP access gateway, the PCRF determines that the trusted non- The 3GPP access gateway does not support dynamic PCC. In order to ensure the consistency of policy control on the trusted non-3GPP access network and the P-GW, and to correctly charge the UE, the PCRF decides not to start the dynamic PCC, and the PCRF returns the IP-CAN to the P-GW.
  • the session establishment confirmation message carries an indication that the dynamic PCC is not activated; or the PCRF can customize some special dynamic PCC rules for the special scenario (ie, the limited policy charging control deployment scenario), but these special dynamic PCC rules must ensure that The UE is billed correctly.
  • the P-GW interacts with the HSS and sends its own IP address to the HSS.
  • the P-GW After receiving the indication that the dynamic PCC is not started, the P-GW uses the pre-configured policy charging rule, or installs a special dynamic PCC rule customized by the PCRF for this special scenario; the P-GW connects to the trusted non-3GPP. The gateway returns a proxy binding acknowledgement message.
  • the UE interacts with the AF, and after the QoS and other parameters are negotiated for the accessed service, the AF sends an application/service information message to the PCRF to provide service information required for accessing the service.
  • the PCRF saves the service information, and returns a response message, where the response message carries an indication that the bearer layer event cannot be detected, and the message may also carry a specific reason that the bearer layer event cannot be detected, that is, the non-3GPP network does not support the dynamic PCC (currently For the limited policy charging control deployment scenario), the cause value may also be referred to as a limited policy charging control deployment indication identifier.
  • the AF does not subscribe to the transmission AF signaling path status notification, the IP-CAN type change notification, and/or the request resource allocation success or failure notification.
  • step 412 returns an indication carrying the undetectable bearer layer event.
  • the response message can carry the specific reason why the bearer layer event cannot be detected. After receiving the message, the AF cancels the subscription.
  • the PCRF can also determine that the trusted non-3GPP network does not support the dynamic PCC by other methods. For example, the PCEF firstly according to the IP address of the trusted non-3GPP access gateway and the configuration information of the PCEF carried in the proxy binding update message (which IPs are recorded therein) The trusted non-3GPP access gateway corresponding to the address supports, and/or does not support the dynamic PCC. It is determined that the trusted non-3GPP access gateway does not support the dynamic PCC, so that the PCEF reports to the PCRF (for example, in the IP-CAN session establishment indication message) Medium-to-upup) Trusted non-3GPP access gateways do not support dynamic PCC.
  • the PCRF detects that the trusted non-3GPP network supports dynamic PCC.
  • the PCRF will send a limited policy charging deployment recovery indication to the AF (this indication is used to indicate that the policy charging deployment has been restored to normal by the limited policy charging deployment), and the notification AF can subscribe to the transmission AF signaling path status notification, IP. -CAN type change notification And/or request resource allocation success or failure notifications, etc. After that, the AF can then subscribe to the bearer layer event.
  • the 3GPP network supports the dynamic PCC
  • the trusted non-3GPP access network does not support the dynamic PCC
  • the trusted non-3GPP access network and the 3GPP network belong to different
  • the process of the AF policy for the limited policy charging control is similar to that of the embodiment, and details are not described herein again.
  • the UE accesses the EPS through the trusted non-3GPP access network and the DSMIPv6 protocol in the application scenario shown in FIG. 3, and the 3GPP network supports dynamic PCC, and the trusted non-3GPP access network does not support. Dynamic PCC (trusted non-3GPP access networks and 3GPP networks belong to different operators).
  • FIG. 5 A flowchart of a method according to a second embodiment of the present invention is shown in FIG. 5, and the specific steps are as follows:
  • the UE accesses the trusted non-3GPP access network, the HSS/AAA performs mutual authentication with the UE, and the HSS/AAA authorizes the UE.
  • the UE negotiates with the trusted non-3GPP access gateway, determines to use the DSMIPv6 protocol for access, and the UE performs a layer 3 attach procedure, and the trusted non-3GPP access gateway allocates a CoA (care-of address) to the UE.
  • the trusted non-3GPP access gateway allocates a CoA (care-of address) to the UE.
  • the UE obtains an IP address of the P-GW to be accessed by performing a DNS (Domain Name System) query according to the APN.
  • the P-GW is located in the home network of the UE, and the UE establishes with the P-GW to be accessed.
  • Security Alliance get the home address (HoA).
  • the UE After establishing a security association with the P-GW, the UE sends a binding update request message to the P-GW, where the binding update request message carries the HoA and the CoA.
  • the P-GW After receiving the binding update request message, the P-GW sends an IP-CAN session establishment indication to the PCRF, where the IP-CAN session establishment indication carries the NAI of the UE, the IP address assigned by the P-GW to the UE, and the APN and the MPT.
  • the MPT identifier is used to indicate that the UE accesses by using the DSMIPv6 protocol.
  • the MPT identifier can also notify the PCRF that the protocol used by the current access protocol is non-GTP by not carrying the GTP-specific parameters. If the message does not carry the Default-EPS-Bearer-QoS, the PCRF can determine that the current access is not available. Use the GTP protocol.
  • the PCRF interacts with the SPR to obtain subscription data of the user access service.
  • 507 Since the MPT indicates that the protocol used by the current access is DSMIPv6 or other non-GTP protocols, and the PCRF does not receive the gateway control session establishment indication message sent by the trusted non-3GPP access gateway, the PCRF determines that the trusted non-3GPP is trusted.
  • the access gateway does not support dynamic PCC. In order to ensure the consistency of policy control on the trusted non-3GPP access network and the P-GW, and to correctly charge the UE, the PCRF decides not to start the dynamic PCC.
  • the PCRF carries an indication that the dynamic PCC is not started in the IP-CAN session establishment confirmation message returned to the P-GW; or the PCRF can customize some special dynamic PCC rules for this special scenario, but these special dynamic PCC rules must be guaranteed.
  • the UE can be charged correctly.
  • the P-GW receives the indication that the dynamic PCC is not started, and uses the pre-configured policy charging rule or the special dynamic PCC rule that the PCRF is customized for the special scenario, and the P-GW returns a binding acknowledgement message to the UE. .
  • the UE interacts with the AF, and after the QoS and other parameters are negotiated for the accessed service, the AF sends an application/service information message to the PCRF to provide service information required for accessing the service.
  • the non--3GPP network does not support the dynamic PCC (currently For the limited policy charging control deployment scenario), the cause value may also be referred to as a limited policy charging control deployment indication identifier.
  • the AF After receiving the response message, the AF will not subscribe to the transmission AF signaling path status notification, the IP-CAN type change notification, and/or the request resource allocation success or failure notification.
  • step 509 the AF subscribes to the PCRF to subscribe to the AF signaling path status notification
  • the step 510 returns a response message carrying an indication that the bearer layer event cannot be detected, and may carry a specific reason that the subscription event cannot be detected; after the AF receives the message, , unsubscribe.
  • the PCRF may also determine that the trusted non-3GPP network does not support the dynamic PCC by other methods. For example, the PCEF firstly according to the care-of address (CoA) carried in the binding update message and the configuration information of the PCEF (where the trusted addresses corresponding to the care-of addresses are recorded) The 3GPP network supports, and/or does not support dynamic PCC. It is determined that the trusted non-3GPP access gateway does not support dynamic PCC, so that the PCEF reports to the PCRF that the trusted non-3GPP access gateway does not support dynamic PCC.
  • CoA care-of address
  • the PCRF detects that the trusted non-3GPP network supports the dynamic PCC, and the PCRF sends a limited policy charging deployment recovery indication to the AF (the indication is used to indicate Currently, the limited policy charging deployment has been restored to the normal policy charging deployment.
  • the notification AF can subscribe to the transmission AF signaling path status notification, the IP-CAN type change notification, and/or the request resource allocation success and/or failure notification. After that, AF can subscribe to the bearer layer event again.
  • FIG. 6 is a schematic diagram of an application scenario according to a third embodiment of the present invention.
  • the UE accesses the E-UTRAN, and the S-GW and the P-GW access the PMIPv6 protocol.
  • EPS where the UE home network supports dynamic PCC, and the visited network does not support dynamic PCC.
  • FIG. 7 A flowchart of a method according to a third embodiment of the present invention is shown in FIG. 7, and the specific steps are as follows:
  • the UE sends an attach request message to the MME.
  • the HSS authenticates and authorizes the UE. After the authentication succeeds, the MME initiates a location update process, and the HSS sends the subscription data of the UE to the MME.
  • the HSS sends the P-GW selection information subscribed by the UE to the MME, and the MME selects the P-GW according to the P-GW selection information, and the MME also selects the S-GW.
  • the MME After selecting the P-GW and the S-GW, the MME sends a default bearer request to the selected S-GW.
  • the S-GW After receiving the default bearer request, the S-GW sends a proxy binding update message to the P-GW.
  • the P-GW After receiving the proxy binding update message, the P-GW sends an IP-CAN session establishment indication to the PCRF (referred to as hPCRF) of the UE home network, and carries the NAI and P-GW of the UE in the IP-CAN session establishment indication.
  • the IP address assigned to the UE, the APN of the UE, and the MPT, the MPT is used to indicate to the PCRF that the UE accesses through the E-UTRAN, and the PMIPv6 protocol is used between the S-GW and the P-GW.
  • the MPT identifier can also notify the PCRF that the protocol used for the current access is non-GTP by not carrying the GTP-specific parameters. If the message does not carry the Default-EPS-Bearer-QoS, the PCRF can determine that the current access is not available. Use the GTP protocol. 705: The hPCRF interacts with the SPR to obtain subscription data of the user access service.
  • the MPF indicates that the protocol used by the current access is PMIPv6 or other non-GTP protocol, and the PCRF does not receive the gateway control session establishment indication message sent by the S-GW, so the PCRF determines that the network where the S-GW is located does not support dynamic PCC.
  • the PCRF decides not to start the dynamic PCC.
  • the PCRF carries an indication that the dynamic PCC is not started in the return message to the P-GW, or the PCRF can customize some special dynamic PCC rules for the special scenario, but these special dynamic PCC rules must ensure that the UE can be correctly performed. Billing.
  • the P-GW After receiving the indication that the dynamic PCC is not started, the P-GW uses the pre-configured policy charging rule, or installs a special dynamic PCC rule customized by the PCRF for the special scenario; the P-GW returns the proxy to the S-GW. Bind the confirmation message.
  • the S-GW After receiving the proxy binding acknowledgement message, the S-GW returns a default bearer response to the MME.
  • the MME After receiving the default bearer response, the MME initiates establishment of a radio bearer, and notifies the UE that the attach is successful.
  • the MME After the MME notifies the UE that the connection is successful, the MME initiates a bearer update, and sends the radio bearer information to the S-GW.
  • the UE interacts with the AF, and after the QoS and other parameters are negotiated for the accessed service, the AF sends an application/service information message to the PCRF to provide service information required for accessing the service.
  • the PCRF saves the service information, and returns a response message, where the response message carries an indication that the bearer layer event cannot be detected, and the message may also carry a specific reason that the bearer layer event cannot be detected, that is, the network where the S-GW is located (ie, the UE).
  • the visited network does not support dynamic PCC (currently a limited policy charging control deployment scenario), and the cause value may also be referred to as a limited policy charging control deployment indication identifier.
  • the AF does not subscribe to the transmission AF signaling path status notification, the IP-CAN type change notification, and/or the request resource allocation success or failure notification.
  • step 712 returns an indication carrying the failure to detect the bearer layer event. Answer the message and carry the specific reason, AF receives the message After that, unsubscribe.
  • the PCRF can also detect the network where the S-GW is located (that is, the visited network of the UE) does not support the dynamic PCC. For example, the PCEF firstly sets the IP address of the S-GW and the configuration information of the PCEF carried in the proxy binding update message. Recording which IP addresses correspond to the visited network support, and/or not supporting the dynamic PCC) determining that the visited network or the S-GW does not support the dynamic PCC, so that the PCEF reports to the PCRF the network where the S-GW is located (ie, the visited place of the UE) Network) does not support dynamic PCC.
  • the PCRF detects the trusted non-3GPP network or the visited place.
  • the 3GPP access network supports dynamic PCC, and the PCRF will send a limited policy charging deployment recovery indication to the AF (this indication is used to indicate that the current policy has been restored to the normal policy charging deployment by the limited policy charging deployment), and the notification AF can subscribe to the transmission AF. Signaling path status notification, IP-CAN type change notification, and/or request resource allocation success or failure notification, etc. Thereafter, the AF can then subscribe to the bearer layer event.
  • This embodiment describes a method for the AF to learn the limited policy charging control deployment in the process of the UE switching from E-UTRAN access to trusted non-3GPP access.
  • the PMIPv6 protocol is used between the S-GW and the P-GW, and the 3GPP network supports the dynamic PCC
  • the trusted non-3GPP access gateway does not support the dynamic PCC
  • the trusted non-3GPP network It belongs to different operators from 3GPP networks.
  • the AF subscribes to the transmission AF signaling path status notification, the IP-CAN type change notification, and/or the request resource allocation success or failure notification, and the like. As shown in FIG. 8, the method includes the following steps:
  • a radio access bearer is established between the UE and the S-GW, and a ⁇ tunnel is established between the S-GW and the P-GW, and the UE sends and receives data through the 3GPP network.
  • the QoS rule delivered by the PCRF is installed on the S-GW.
  • the PCC rules issued by the PCRF are installed on the GW.
  • the UE discovers a trusted non-3GPP access system and initiates a handover.
  • 803 The UE performs access authentication and authorization in the trusted non-3GPP access system; the 3GPP AAA server authenticates the non-3GPP access of the UE, and the HSS returns the P connected to the UE in the 3GPP system to the trusted non-3GPP access gateway. -GW's address. 804: The layer 3 attach procedure of the UE is triggered.
  • the trusted non-3GPP access gateway sends a proxy binding update request to the P-GW.
  • the P-GW sends an IP-CAN session modification indication message to the PCRF, where the message carries the NAI of the UE, the IP address allocated by the P-GW for the UE, the APN of the UE, and the MPT identifier, where the MPT identifier is used to indicate the UE to the PCRF. ⁇ Access using the PMIPv6 protocol.
  • the MPT identifier can also notify the PCRF that the protocol used for the current access is non-GTP by not carrying the GTP-specific parameters. If the message does not carry the Default-EPS-Bearer-QoS, the PCRF can determine that the current access is not available. Use the GTP protocol.
  • the PCRF Since the MPT indicates that the protocol used by the current access is PMIPv6 or other non-GTP protocols, and the PCRF knows that the UE has switched from the 3GPP network to the non-3GPP network, the PCRF does not receive the trusted non-3GPP access gateway to send. The incoming gateway controls the session establishment indication message, so the PCRF determines that the trusted non-3GPP access gateway does not support dynamic PCC. In order to ensure the consistency of policy control on the trusted non-3GPP access gateway and the P-GW, and to correctly charge the UE, the PCRF decides not to start the dynamic PCC, and the PCRF returns the IP-CAN to the P-GW.
  • the session modification confirmation message carries an indication that the dynamic PCC is not started; or the PCRF can customize some special dynamic PCC rules for the special scenario, but these special dynamic PCC rules must ensure that the UE can be correctly charged.
  • the P-GW deletes the PCC rules sent by the PCRF in the 3GPP access according to the indication that the dynamic PCC is not started, uses a pre-configured policy charging rule, or uses a special dynamic PCC customized by the PCRF for this special scenario.
  • the rule update originally uses the PCC rule delivered by the PCRF when the 3GPP access is used, and returns a proxy binding acknowledgement message to the trusted non-3GPP access gateway.
  • the AF subscribes to the transmission AF signaling path status notification, the IP-CAN type change notification, and/or the request resource allocation success or failure notification, etc., when the UE accesses through the 3GPP, but when the UE switches to the trusted non-3GPP connection On the entry, the trusted non-3GPP access network does not support the dynamic PCC, so that the bearer layer event that the AF subscribes to in the source network cannot be detected. Therefore, the PCRF sends an event report message to the AF, where the message carries an indication that the bearer layer event cannot be detected.
  • the message may also carry a specific reason that the bearer layer event cannot be detected, that is, the non-3GPP network does not support dynamic PCC (currently The limited policy charging control deployment scenario), the cause value may also be referred to as a limited policy charging control deployment indication identifier.
  • the AF After receiving the event report message, the AF returns a confirmation message and cancels the subscription.
  • the PCRF can also detect that the trusted non-3GPP network does not support the dynamic PCC by other methods. For example, the PCEF first determines the trusted non-3GPP according to the IP address of the trusted non-3GPP access gateway and the configuration information of the PCEF carried in the proxy binding update message. The access gateway does not support dynamic PCC, so that the PCEF reports to the PCRF that the trusted non-3GPP access gateway does not support dynamic PCC.
  • the PCRF detects the trusted non-3GPP network or the visited place.
  • the 3GPP access network supports dynamic PCC, and the PCRF will send a limited policy charging deployment recovery indication to the AF (this indication is used to indicate that the current policy has been restored to the normal policy charging deployment by the limited policy charging deployment), and the notification AF can subscribe to the transmission AF. Signaling path status notification, IP-CAN type change notification, and/or request resource allocation success or failure notification, etc. Thereafter, the AF can then subscribe to the bearer layer event.
  • the UE switches from 3GPP access to trusted non-3GPP access, and between the S-GW and the P-GW.
  • the UE performs handover within 3GPP, the source network supports dynamic PCC and the target network does not support dynamic PCC, and the flow when the PMIPv6 protocol is used between the S-GW and the P-GW in the target network is similar.
  • the non-3GPP access network is switched to the 3GPP network, where the 3GPP access is the roaming mode of the home route, the PMIPv6 protocol is used between the S-GW and the P-GW, the home network supports the dynamic PCC, and the visited network does not.
  • the flow when supporting dynamic PCC can also be implemented according to the inventive concept.
  • the foregoing embodiment may also have multiple transformation modes, for example: (1)
  • the PCRF may also be based on the IP address of the trusted non-3GPP access gateway and the configuration information of the PCRF, and/or the care-of address of the UE. And the configuration information of the PCRF, and/or the IP address of the S-GW and the configuration information of the PCRF to determine whether the visited network supports dynamic PCC (that is, whether the current policy is a limited policy charging control scenario).
  • the PCRF may also notify the AF that the AF is currently a limited policy control deployment scenario in the corresponding response message.
  • the present invention further provides a policy and charging rule function entity PCRF, which supports implementing limited policy charging control, and the PCRF is configured to determine whether the visited network of the user equipment UE roaming is The policy charging control PCC is supported. If the visited network does not support, the application function AF is notified that the subscribed event cannot be reported.
  • PCRF policy and charging rule function entity
  • the PCRF is configured to send a message to the AF, where the message carries an identifier for indicating a limited policy charging control deployment, so that the AF does not perform event subscription, and/or cancel event according to the identifier. subscription.
  • the PCRF is configured to determine whether the visited network supports the
  • the PCRF After receiving the IP bearer network connection access network IP-CAN session establishment indication message or the IP-CAN session modification indication message, the PCRF determines whether the visited network supports the PCC, when the IP-CAN session is established.
  • the indication message, or the mobility management protocol carried in the IP-CAN session modification indication message indicates that the MPT identifier indicates that the protocol used for the access is not the general wireless packet service GPRS tunneling protocol, and the PCRF does not receive the gateway control session.
  • the indication message is established, it is determined that the visited network does not support the PCC.
  • the PCRF is configured to determine whether the visited network supports the PCC in the following manner:
  • the PCRF is configured to determine whether the visited network supports the PCC in the following manner:
  • the policy and charging execution function entity PCEF determines the visit according to the configuration information of the PCRF and the IP address of the access gateway of the visited network, and/or the care-of address of the UE, and/or the IP address of the serving gateway. Whether the network supports the PCC, and notifying the PCRF of the determination result, and the PCRF determines, according to the determination result, whether the visited network supports the PCC.
  • the PCRF is configured to include the unreportable event indication in the corresponding response message and send the AF to the AF after receiving the application/service information message or the event subscription message sent by the AF.
  • the PCRF is further configured to include an unreportable event indication in the event notification message and send to the AF.
  • the PCRF is further configured to notify the AF that the subscribed event cannot be reported when the UE switches to the access gateway that does not support the BBERF function.
  • the PCRF is further configured to send a limited policy charging to the AF after the PCRF detects that the UE moves to a trusted non-3GPP access network, a visited 3GPP access network, or a home network that supports the PCC. Control the deployment recovery indication ID.
  • the present invention also provides a system for implementing limited policy charging control, as shown in FIG. 9, including the policy and charging rule function entity PCRF and the application function AF as described above.
  • the current policy charging control deployment of the AF can be more conveniently and accurately notified, and the AF can be based on the current Policy charging controls the deployment situation to perform corresponding operations, such as not subscribing to events or subscribing to events, in order to save system resources.

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)

Description

一种实现有限策略计费控制的方法及系统
技术领域
本发明涉及一种实现有限策略计费控制的方法及系统。 背景技术
如图 1所示， 3 GPP ( 3rd Generation Partnership Project, 第三代合作伙伴 计划）演进分组系统（ Evolved Packet System, 简称 EPS ) 由演进的通用移动 通信系统陆地无线接入网 （ Evolved Universal Terrestrial Radio Access Network, 简称 E-UTRAN )、 移动管理单元（ Mobility Management Entity, 简 称 MME ) 、 服务网关（ Serving Gateway, 简称 S-GW ) 、 分组数据网络网关 ( Packet Data Network Gateway, 简称 PDN GW或 P-GW )、 归属用户服务器 ( Home Subscriber Server,简称 HSS )、 3 GPP的认证授权计费（ Authentication, Authorization and Accounting , 简称 AAA )服务器、 策略和计费规则功能实体 ( Policy and Charging Rules Function, 简称 PCRF )及其它支撑节点组成。
其中， MME用于移动性管理、非接入层信令的处理和用户移动管理上下 文的管理等控制面相关工作； S-GW是与 E-UTRAN相连的接入网关设备，在 E-UTRAN与 P-GW之间转发数据，并且用于对寻呼等待数据进行緩存； P-GW 则是 EPS与 PDN的边界网关， 用于 PDN的接入及在 EPS与 PDN间转发数 据等功能。
EPS支持与非 3GPP系统的互通。 与非 3GPP系统的互通通过 S2a、 S2b、 S2c接口实现， P-GW作为 3GPP系统与非 3GPP系统之间的锚点。 其中， 非 3GPP系统被分为可信任非 3GPP接入系统和不可信任非 3GPP接入系统。 可 信任非 3GPP接入系统可以直接通过 S2a接口与 P-GW连接；不可信任非 3GPP 接入系统需经过演进的分组数据网关 （ Evolved Packet Data Gateway , 简称 ePDG )与 P-GW相连， ePDG与 P-GW之间为 S2b接口。 S2c接口提供了用 户设备 ( User Equipment, 简称 UE )与 P-GW之间用户面相关的控制和移动 性支持， 支持的移动性管理协议为支持双栈的移动 IPv6 ( Moblie IPv6 support for dual stack Hosts and Routers , 简称 DSMIPv6 ) 。 EPS系统引入策略计费控制（Policy and Charging Control, 简称 PCC )功 能框架对用户的业务访问进行动态的策略计费控制。以下对图 2所示的 Rel-8 PCC非漫游场景架构中的各个逻辑功能实体及其接口功能进行描述。
AF ( Application Function, 应用功能）用于提供业务应用的接入点， 这些 业务应用所使用的网络资源需要进行动态的策略控制。 在业务面进行参数协 商时， AF将相关业务信息传递给策略控制与计费规则功能实体 PCRF。 如果 这些业务信息与 PCRF的策略相一致， 则 PCRF接受该协商； 否则， PCRF拒 绝该协商， 并在反馈时给出 PCRF可接受的业务参数。 随后， AF可将这些参 数返回给用户设备 UE。 其中， AF和 PCRF之间的接口是 Rx接口。
PCRF是 PCC的核心， 负责策略决策和计费规则的制定。 PCRF提供了 基于业务数据流的网络控制规则， 这些网络控制包括业务数据流的检测、 门 控（ Gating Control ) 、 服务质量（ Quality of Service, 简称 QoS )控制以及基 于数据流的计费规则等。 PCRF将其制定的策略和计费规则发送给策略和计费 执行功能实体 ( Policy and Control Enforcement Function, 简称 PCEF )执行； 同时， PCRF还需要保证这些规则和用户的签约信息一致。 PCRF制定策略和 计费规则的依据包括： 从 AF 获取与业务相关的信息、 从用户签约数据库 ( Subscription Profile Repository, 简称 SPR )获取与用户策略计费控制相关的 签约信息、 通过 Gx接口从 PCEF获取的与承载相关网络的信息。
PCEF通常位于网关（ Gate-Way, 简称 GW ) 内， 在承载面执行 PCRF所 制定的策略和计费规则。 PCEF按照 PCRF所发送的规则中的业务数据流过滤 器对业务数据流进行检测， 进而对这些业务数据流执行 PCRF所制定的策略 和计费规则。 在承载建立时， PCEF按照 PCRF发送的规则进行 QoS授权， 并根据 AF的执行进行门控控制。 同时， PCEF根据 PCRF订阅的事件触发上 报承载网络上发生的事件。根据 PCRF发送的计费规则， PCEF执行相应的业 务数据流计费操作， 计费既可以是在线计费， 也可以是离线计费。 如果是在 线计费， 则 PCEF需要和在线计费系统（ Online Charging System, 简称 OCS ) 一起进行信用管理。 离线计费时， PCEF 和离线计费系统（Offline Charging System, 简称 OFCS )之间交换相关的计费信息。 PCEF与 PCRF之间的接口 是 Gx接口，与 OCS之间的接口是 Gy接口，与 OFCS之间的接口是 Gz接口。 PCEF一般都位于网络的网关上， 如 EPS的分组数据网络网关（ PDN-GW ) 、 GPRS ( General Packet Radio Service, 通用无线分组业务）中的 GPRS网关支 持节点 （GGSN ) 以及 I-WLAN ( Interworking WLAN, 互联无线网局域网 ) 中的分组数据网关 （Packet Data Gateway, 简称 PDG ) 。
BBERF ( Bearer Binding and Event Reporting Function, 载绑定和事件才艮 告功能实体）通常位于接入网网关（ Access Network Gateway ) 内。 如当用户 设备通过 E-UTRAN接入 EPS、 服务网关 S-GW与 P-GW之间釆用 PMIPv6 ( Proxy Mobile Internet Protocol version 6 , 代理移动互联网协议版本 6 )协议 时， S-GW中就存在 BBERF。 当用户设备通过可信任非 3GPP接入网接入时， 可信任非 3GPP接入网关中也存在 BBERF。 引入 BBERF的目的是， 当接入 网关与 P-GW之间釆用 MIP ( Mobile Internet Protocol, 移动互联网协议 )时， PCEF无法根据 PCC规则执行承载的建立、 修改和删除， 同时也可能无法上 报触发事件。 这时， 承载的建立、 修改和删除以及事件上报功能就由 BBERF 来完成。 PCRF通过 Gxx接口与 BBERF进行交互。
用户签约数据库 （SPR )存储了与策略控制和计费相关的用户策略计费 控制签约信息。 SPR和 PCRF之间的接口是 Sp接口。
在线计费系统（OCS )和 PCEF—起进行在线计费方式下用户信用的控 制和管理。
离线计费系统（OFCS )与 PCEF—起完成离线计费方式下的计费操作。 AF需要向 PCRF订阅 AF信令传输路径状态通知。 PCRF收到 AF的订阅 后， 就向 PCEF订阅对应的事件。 当 PCEF检测到对应的事件（例如， 传输 AF信令的承载丟失或释放 ) 时， PCEF向 PCRF上报传输 AF信令承载丟失 或释放， 从而 PCRF再向 AF通知该事件（或称状态 ) 。
当用户设备通过 E-UTRAN接入 EPS且 S-GW与 P-GW之间釆用 PMIPv6 协议、或当用户设备通过可信任非 3GPP接入网接入且可信任非 3GPP接入网 关与 P-GW之间釆用 PMIPv6协议、或当用户设备通过可信任非 3GPP接入网 关且釆用 DSMIPv6 ( Dual Stack Mobile Internet Protocol version 6, 双栈移动 IP协议版本 6 )或 MIPv4协议接入时， 位于 P-GW的 PCEF无法检测到传输 AF信令的承载丟失或释放， 此时 PCRF只能向 BBERF订阅传输 AF信令的 承载丟失或释放事件 , 由 BBERF进行检测并向 PCRF上报该事件 , PCRF再 向 AF进行上报。
此外， AF还可能向 PCRF订阅 IP-CAN ( IP-Connectivity Access Network, IP承载网络连接接入网络） 类型变化通知。 PCRF 收到 AF 的订阅后再向 BBERF订阅该事件， 由 BBERF进行检测并向 PCRF上报， 向 PCRF上报 IP-CAN类型以及该 IP-CAN类型中特定的 RAT ( Radio Access Technoledge, 无线接入技术）类型变化， 从而 PCRF再向 AF上报该信息。
同样， 当用户设备通过 E-UTRAN接入 EPS且 S-GW与 P-GW之间釆用 ΡΜΙΡνό协议、或当用户设备通过可信任非 3GPP接入网接入且可信任非 3GPP 接入网关与 P-GW之间釆用 ΡΜΙΡν6协议、 或用户设备通过可信任非 3GPP 接入网关并釆用 DSMIPv6或 MIPv4协议接入时，在某些情况下，位于 P-GW 的 PCEF无法准确地检测到 IP-CAN类型中的 RAT类型的变化。 此时 PCRF 只能向 BBERF订阅 IP-CAN类型变化通知， 由 BBERF进行检测并向 PCRF 上报该事件， PCRF再向 AF进行上报。
此外，当用户设备釆用上述接入场景接入时， AF为特定业务请求资源时，
AF还可能向 PCRF订阅为该业务请求的资源是否分配成功的通知。 PCRF收 到 AF的订阅后再向 BBERF订阅该事件， 当 BBERF分配成功或失败后， 由 BBERF向 PCRF上报成功或失败的指示， 从而 PCRF再向 AF上报该指示。
然而，对于 UE处于家乡路由的漫游场景，即 P-GW位于家乡网络、 S-GW 或可信任非 3GPP接入网关位于拜访网络， 若此时家乡网络部署了 PCC而拜 访网络没有部署 PCC, 由于拜访网络无法向 PCRF上 "^所订阅的事件， 因此 PCRF也无法向 AF进行上才艮。
同样， 当 UE通过非 3GPP接入并且非 3GPP接入网与 3GPP网络属于不 同的运营商时，若此时 3GPP网络部署了 PCC而非 3GPP网络没有部署 PCC, 由于非 3GPP网络无法向 PCRF上报所订阅的事件， 因此 PCRF也无法向 AF 进行上报。
现有技术中， AF将根据自身的配置信息 (如漫游协议 )判断 UE所在的 拜访网络是否部署了 PCC (即判断当前是否为有限 PCC部署场景 )。 当拜访 网络不支持 PCC时， AF不会向 PCRF进行某些事件的订阅（如传输 AF信令 路径状况通知、 IP-CAN类型变化通知和请求分配资源成功或失败通知）。 该 方法的主要问题是， 配置信息相对复杂， 特别当 AF是第三方提供业务时， 配置信息的更新比较困难， 并且当拜访网络或非 3GPP网络中部分 S-GW或 可信任非 3GPP接入网关支持 BBERF功能时， AF将无法简单地根据 UE所 在的拜访网络来决定是否订阅事件。
发明内容
本发明所要解决的技术问题是， 克服现有技术的不足， 提供一种实现有 限策略计费控制的方法及系统， 以便更方便地使 AF获知当前是否为有限策 略计费控制部署（即拜访网络没有部署 PCC, 不支持动态 PCC ) 。
为了解决上述问题， 本发明提供一种实现有限策略计费控制的方法， 该 方法包括：
策略和计费规则功能实体 PCRF判断用户设备 UE漫游的拜访地网络是 否支持策略计费控制 PCC, 如果拜访地网络不支持 PCC, 通知应用功能 AF 其订阅的事件无法上报。
PCRF可以向应用功能 AF发送消息， 而该消息中可以携带用于指示有限 策略计费控制部署的标识。 此外， 接收到 PCRF的携带所述标识的消息后， AF根据所述标识不进行 事件的订阅、 和 /或取消事件的订阅。
此外， 所述 PCRF釆用如下方式判断拜访地网络是否支持 PCC:
PCRF接收到 IP承载网络连接接入网络 IP-CAN会话建立指示消息、 或 IP-CAN会话修改指示消息， 判断拜访网络是否支持 PCC, 当 IP-CAN会话建 立指示消息、 或 IP-CAN会话修改指示消息中携带的移动性管理协议指示 MPT标识表明接入所釆用的协议不是通用无线分组业务 GPRS隧道协议、 且 PCRF未接收到网关控制会话建立指示消息时， 判定拜访网络不支持 PCC。
此外， 所述 PCRF釆用如下方式判断拜访地网络是否支持 PCC:
PCRF根据本地的配置信息以及： 拜访地网络的接入网关的 IP地址、 和 / 或 UE的转交地址、 和 /或服务网关的 IP地址判断拜访网络是否支持 PCC。 此外， 所述 PCRF釆用如下方式判断拜访地网络是否支持 PCC:
策略和计费执行功能实体 PCEF根据本地的配置信息以及： 拜访地网络 的接入网关的 IP地址、 和 /或 UE的转交地址、 和 /或月良务网关的 IP地址判断 拜访网络是否支持 PCC, 并将判断结果通知给 PCRF, PCRF根据所述判断结 果判断拜访网络是否支持 PCC。
此外，在接收到 AF发送的应用 /业务信息消息、或事件订阅消息后， PCRF 将所述用于指示有限策略控制部署的标识包含在相应的应答消息中发送给 AF。
此外， PCRF将所述用于指示有限策略控制部署的标识包含在事件通知消 息中发送给 AF。
此外， 当 UE切换到不支持 BBERF功能的接入网关时， PCRF通知 AF 其订阅的事件无法上报。
此外， 当 PCRF检测到 UE移动到支持 PCC的可信任非 3GPP接入网、 拜访地 3GPP接入网或家乡网络后， PCRF向 AF发送有限策略计费控制部署 恢复指示标识。
本发明还提供一种策略和计费规则功能实体 PCRF,其支持实现有限策略 计费控制， PCRF设置为判断用户设备 UE漫游的拜访地网络是否支持策略计 费控制 PCC, 如果所述拜访地网络不支持， 则通知应用功能 AF其订阅的事 件无法上报。
此外， PCRF设置为向所述 AF发送消息， 所述消息中携带用于指示有限 策略计费控制部署的标识， 以使所述 AF根据所述标识不进行事件的订阅、 和 /或取消事件的订阅。
此外， PCRF设置为釆用如下方式判断所述拜访地网络是否支持所述 PCC:
所述 PCRF接收到 IP承载网络连接接入网络 IP-CAN会话建立指示消息、 或 IP-CAN会话修改指示消息后， 判断所述拜访地网络是否支持所述 PCC, 当所述 IP-CAN会话建立指示消息、或所述 IP-CAN会话修改指示消息中携带 的移动性管理协议指示 MPT标识表明接入所釆用的协议不是通用无线分组 业务 GPRS隧道协议、且所述 PCRF未接收到网关控制会话建立指示消息时， 判定所述拜访网络不支持所述 PCC。
此外， PCRF设置为釆用如下方式判断所述拜访地网络是否支持所述 PCC:
所述 PCRF根据所述 PCRF的配置信息以及： 所述拜访地网络的接入网 关的 IP地址、 和 /或所述 UE的转交地址、 和 /或服务网关的 IP地址判断所述 拜访地网络是否支持所述 PCC。
此外， PCRF设置为釆用如下方式判断所述拜访地网络是否支持所述 PCC:
策略和计费执行功能实体 PCEF根据所述 PCRF的配置信息以及： 所述 拜访地网络的接入网关的 IP地址、 和 /或 UE的转交地址、 和 /或服务网关的 IP 地址判断所述拜访网络是否支持所述 PCC , 并将判断结果通知给所述 PCRF, 所述 PCRF根据所述判断结果判断所述拜访网络是否支持所述 PCC。
此外， PCRF设置为在接收到所述 AF发送的应用 /业务信息消息、或事件 订阅消息后， 将无法上报事件指示包含在相应的应答消息中发送给所述 AF。
此外， PCRF还设置为将无法上报事件指示包含在事件通知消息中发送给 所述 AF。
此外， PCRF还设置为当所述 UE切换到不支持 BBERF功能的接入网关 时， 通知所述 AF其订阅的事件无法上报。
此外， PCRF还设置为当所述 PCRF检测到所述 UE移动到支持所述 PCC 的可信任非 3GPP接入网、 拜访地 3GPP接入网或家乡网络后， 向所述 AF发 送有限策略计费控制部署恢复指示标识。
本发明还提供一种实现有限策略计费控制的系统， 包括如上面所述的策 略和计费规则功能实体 PCRF和应用功能 AF。
本发明的一种实现有限策略计费控制的系统， 可以包含： UE、 PCRF,
AF和所述 UE漫游的拜访地网络；
所述 PCRF用于判断所述拜访地网络是否支持 PCC, 如果支持， 则向所 述 AF发送消息， 该消息中携带用于指示有限策略计费控制部署的标识。 此外， 所述 AF用于在接收到携带所述标识的消息后， 根据所述标识不 进行事件的订阅、 和 /或取消事件的订阅。
综上所述， 釆用本发明的方法及系统， 在实现有限策略计费控制时（即 拜访网络不支持 PCC时） ， 可以更方便、 更准确地通知 AF当前的策略计费 控制部署情况， AF可以根据当前的策略计费控制部署情况进行相应的操作， 例如不进行事件的订阅或取消事件的订阅， 以达到节省系统资源的目的。 附图概述
图 1是现有的 EPS系统架构图；
图 2是现有的 Rel-8 PCC非漫游场景架构图；
图 3是本发明第一实施例和第二实施例的应用场景示意图；
图 4是本发明第一实施例的方法流程图；
图 5是本发明第二实施例的方法流程图；
图 6所示为本发明第三实施例的应用场景示意图；
图 7是本发明第三实施例的方法流程图；
图 8是本发明第四实施例的方法流程图； 以及
图 9是本发明有限策略计费控制系统示意图。 本发明的较佳实施方式
下面将结合附图和实施例对本发明的方法、 以及实现本发明方法的系统 进行详细描述。
第一实施例
图 3所示为本发明第一实施例的应用场景示意图； 在该应用场景中， UE 通过可信任非 3GPP接入网、 釆用 PMIPv6协议接入 EPS; 3GPP网络支持动 态 PCC, 而可信任非 3GPP接入网不支持动态 PCC, 可信任非 3GPP网络与 3GPP网络属于不同的运营商。
本发明第一实施例的方法流程图如图 4所示， 具体步骤如下： 401 : UE接入可信任非 3GPP接入网。
402: UE接入到可信任非 3GPP接入网后， 向 HSS/AAA请求进行 EPS 接入认证； HSS/AAA接收到 EPS接入认证请求后， 对发出请求的 UE进行认 证； HSS/AAA完成对 UE的认证后， 向可信任非 3GPP接入网关发送 UE签 约的 P-GW选择信息。
403: UE的层 3附着过程被触发。
404: 可信任非 3GPP接入网关根据 P-GW选择信息选定 P-GW, 并向所 选定的 P-GW发送代理绑定更新消息， 代理绑定更新消息中携带 UE的 NAI ( Network Access Identifier, 网络接入标识 )和 APN ( Access Point Name, 接 入点名称） 。
405: P-GW接收到代理绑定更新消息后， 向 PCRF发送 IP-CAN会话建 立指示， 在 IP-CAN会话建立指示中携带 UE的 NAI、 P-GW为 UE分配的 IP 地址和 APN以及移动性管理协议指示（Mobility Protocol Type, MPT )标识； 该 MPT标识用于向 PCRF指示 UE是釆用 PMIPv6协议接入。
MPT标识也可以通过不携带 GTP ( GPRS Tunneling Protocol , GPRS隧道 协议）特定的参数来通知 PCRF当前接入所釆用的协议为非 GTP, 如该消息 中没有携带 Default— EPS— Bearer— QoS , PCRF就可判断当前接入没有釆用 GTP 协议。
406: PCRF与 SPR交互获得用户访问业务相关的签约数据。
407: 由于 MPT指示当前接入所釆用的协议为 PMIPv6或其它非 GTP协 议， 并且 PCRF并没有接收到可信任非 3GPP接入网关发送来的网关控制会 话建立指示消息， 所以 PCRF判断可信任非 3GPP接入网关不支持动态 PCC。 为了保证在可信任非 3GPP接入网和 P-GW上的策略控制的一致性， 以及能 对 UE进行正确的计费， PCRF决定不启动动态 PCC, PCRF在向 P-GW返回 的 IP-CAN会话建立确认消息中携带不启动动态 PCC的指示； 或者 PCRF可 以为这种特殊的场景 （即有限策略计费控制部署场景）定制一些特殊的动态 PCC规则， 但是这些特殊的动态 PCC规则必须保证能够正确地对 UE进行计 费。 408: P-GW与 HSS交互， 将其自身的 IP地址发送到 HSS。
409: P-GW接收到不启动动态 PCC的指示后，使用预先配置的策略计费 规则，或者安装 PCRF为这种特殊的场景定制的特殊的动态 PCC规则； P-GW 向可信任非 3GPP接入网关返回代理绑定确认消息。
410: 层 3附着过程完成。
411 : UE与 AF进行交互， 对访问的业务进行 QoS等参数的协商后， AF 向 PCRF发送应用 /业务信息消息， 提供访问业务所需的业务信息。
412: PCRF保存业务信息， 返回应答消息， 在该应答消息中携带无法检 测承载层事件的指示， 该消息中还可携带无法检测承载层事件的具体原因， 即非 3GPP网络不支持动态 PCC (当前为有限策略计费控制部署场景 ) , 该 原因值也可以称为有限策略计费控制部署指示标识。 AF收到该应答消息后， 不订阅传输 AF信令路径状况通知、 IP-CAN类型变化通知和 /或请求资源分配 成功或失败通知等。
此外， 若在步骤 411中， AF向 PCRF订阅传输 AF信令路径状况通知、 IP-CAN类型变化通知和 /或请求资源分配成功或失败通知等， 则步骤 412返 回携带无法检测承载层事件的指示的应答消息并可以携带无法检测承载层事 件的具体原因， AF收到该消息后， 取消订阅。
PCRF也可以通过其它方法判定可信任非 3GPP网络不支持动态 PCC,如 PCEF首先根据代理绑定更新消息中携带的可信任非 3GPP接入网关的 IP地 址和 PCEF的配置信息 （其中记录了哪些 IP地址对应的可信任非 3GPP接入 网关支持、 和 /或不支持动态 PCC )判定该可信任非 3GPP接入网关不支持动 态 PCC,从而 PCEF向 PCRF上报（例如， 在 IP-CAN会话建立指示消息中上 报 )可信任非 3GPP接入网关不支持动态 PCC。
若 UE通过上述实施例接入之后发生移动， 移动到支持动态 PCC的可信 任非 3GPP接入网中、 拜访地 3GPP接入网或回到家乡网络， PCRF检测到可 信任非 3GPP网络支持动态 PCC, PCRF将向 AF发送有限策略计费部署恢复 指示 （该指示用于表示当前已由有限策略计费部署恢复到正常的策略计费部 署） ， 通知 AF可以订阅传输 AF信令路径状况通知、 IP-CAN类型变化通知 和 /或请求资源分配成功或失败通知等。 此后， AF 又可以进行承载层事件订 阅了。
当 UE通过可信任非 3GPP接入网、 釆用 MIPv4协议接入 EPS, 3GPP网 络支持动态 PCC, 可信任非 3GPP接入网不支持动态 PCC, 可信任非 3GPP 接入网和 3GPP网络属于不同的运营商的情况下， AF获知有限策略计费控制 部署的流程与本实施例的方法类似， 在此不再赘述。
第二实施例
在本实施例中， UE在图 3所示的应用场景下， 通过可信任非 3GPP接入 网、釆用 DSMIPv6协议接入 EPS, 3GPP网络支持动态 PCC,而可信任非 3GPP 接入网不支持动态 PCC (可信任非 3GPP接入网和 3GPP网络属于不同的运 营商） 。 本发明第二实施例的方法流程图如图 5所示， 具体步骤如下：
501 : UE接入可信任非 3GPP接入网， HSS/AAA与 UE进行相互认证 , HSS/AAA对 UE进行授权。
502: 认证成功后， UE与可信任非 3GPP接入网关进行协商， 决定釆用 DSMIPv6协议进行接入， UE进行层 3附着过程，可信任非 3GPP接入网关为 UE分配 CoA (转交地址 ) 。
503: UE根据 APN进行 DNS ( Domain Name System, 域名系统）查询 获得要接入的 P-GW的 IP地址， 该 P-GW位于 UE的家乡网络中， UE与该 要接入的 P-GW建立安全联盟， 获得家乡地址（HoA ) 。
504: UE与 P-GW建立安全联盟后， 向 P-GW发送绑定更新请求消息， 在该绑定更新请求消息中携带 HoA和 CoA。
505: P-GW接收到绑定更新请求消息后， 向 PCRF发送 IP-CAN会话建 立指示， 在 IP-CAN会话建立指示中携带 UE的 NAI、 P-GW为 UE分配的 IP 地址和 APN以及 MPT, 该 MPT标识用于指示 UE釆用 DSMIPv6协议接入。
MPT标识也可以通过不携带 GTP协议特定的参数来通知 PCRF当前接入 所釆用的协议为非 GTP ,如该消息中没有携带 Default— EPS— Bearer— QoS , PCRF 就可判断当前接入没有釆用 GTP协议。
506: PCRF与 SPR交互获取用户访问业务的签约数据。 507: 由于 MPT指示当前接入所釆用的协议为 DSMIPv6或其它非 GTP 协议， 并且 PCRF没有接收到可信任非 3GPP接入网关发送来的网关控制会 话建立指示消息， 所以 PCRF判断可信任非 3GPP接入网关不支持动态 PCC。 为了保证在可信任非 3GPP接入网和 P-GW上的策略控制的一致性， 以及能 对 UE进行正确的计费， PCRF决定不启动动态 PCC。 PCRF在向 P-GW返回 的 IP-CAN会话建立确认消息中携带不启动动态 PCC的指示； 或者 PCRF可 以为这种特殊的场景定制一些特殊的动态 PCC规则， 但是这些特殊的动态 PCC规则必须保证能够正确地对 UE进行计费。
508: P-GW接收到不启动动态 PCC的指示，将使用预先配置的策略计费 规则或者安装 PCRF为这种特殊的场景定制的特殊的动态 PCC规则， P-GW 向 UE返回绑定确认消息。
509: UE与 AF进行交互， 对访问的业务进行 QoS等参数的协商后， AF 向 PCRF发送应用 /业务信息消息， 提供访问业务所需的业务信息。
510: PCRF保存业务信息， 返回应答消息， 在该应答消息中携带无法检 测承载层事件的指示， 该消息中还可携带无法检测承载层事件的具体原因， 即非 3GPP网络不支持动态 PCC (当前为有限策略计费控制部署场景 ) , 该 原因值也可以称为有限策略计费控制部署指示标识。 AF收到该应答消息后， 将不订阅传输 AF信令路径状况通知、 IP-CAN类型变化通知和 /或请求资源分 配成功或失败通知等。
此外， 若在步骤 509中， AF向 PCRF订阅传输 AF信令路径状况通知、
IP-CAN类型变化通知和 /或请求资源分配成功或失败通知等， 则步骤 510返 回携带无法检测承载层事件的指示的应答消息并可以携带无法检测订阅事件 的具体原因； AF收到该消息后， 取消订阅。
PCRF也可以通过其它方法判定可信任非 3GPP网络不支持动态 PCC,如 PCEF首先根据绑定更新消息中携带的转交地址（CoA )和 PCEF的配置信息 (其中记录有哪些转交地址对应的可信任非 3GPP网络支持、 和 /或不支持动 态 PCC )判定该可信任非 3GPP接入网关不支持动态 PCC,从而 PCEF向 PCRF 上报可信任非 3GPP接入网关不支持动态 PCC。
若 UE通过上述实施例接入之后发生移动， 移动到支持动态 PCC的可信 任非 3GPP接入网、 拜访地 3GPP接入网或回到家乡网络中， PCRF检测到可 信任非 3GPP网络支持动态 PCC, PCRF将向 AF发送有限策略计费部署恢复 指示 （该指示用于表示当前已由有限策略计费部署恢复到正常的策略计费部 署） ， 通知 AF可以订阅传输 AF信令路径状况通知、 IP-CAN类型变化通知 和 /或请求资源分配成功和 /或失败通知等。 此后， AF又可以进行承载层事件 订阅了。
第三实施例
图 6所示为本发明第三实施例的应用场景示意图； 当 UE在家乡路由的 漫游场景下，通过拜访地的 E-UTRAN、并且 S-GW与 P-GW之间釆用 PMIPv6 协议接入 EPS, 其中 UE归属地网络支持动态 PCC, 而拜访地网络不支持动 态 PCC。
本发明第三实施例的方法流程图如图 7所示， 具体步骤如下：
701 : UE向 MME发送附着请求消息； HSS对 UE进行认证和授权， 认 证成功后， MME发起位置更新流程， HSS将 UE的签约数据发送给 MME。 在认证过程中， HSS将 UE签约的 P-GW选择信息发送给 MME, MME根据 P-GW选择信息选择 P-GW, 同时 MME也会选择 S-GW。
702： MME选定 P-GW和 S-GW后， 向选定的 S-GW发送建立默认承载 请求。
703: S-GW接收到建立默认承载请求后， 向 P-GW发送代理绑定更新消 息。
704: P-GW接收到代理绑定更新消息后， 向 UE归属地网络的 PCRF (记 作 hPCRF )发送 IP-CAN会话建立指示， 在 IP-CAN会话建立指示中携带 UE 的 NAI、 P-GW为 UE分配的 IP地址、 UE的 APN以及 MPT, 该 MPT用于 向 PCRF指示 UE通过 E-UTRAN接入、并且 S-GW和 P-GW之间釆用 PMIPv6 协议。
MPT标识也可以通过不携带 GTP协议特定的参数来通知 PCRF当前接入 所釆用的协议为非 GTP协议，如该消息中没有携带 Default— EPS— Bearer— QoS , PCRF就可判断当前接入没有釆用 GTP协议。 705: hPCRF与 SPR交互获取用户访问业务的签约数据。
706: 由于 MPT指示当前接入所釆用的协议为 PMIPv6或其它非 GTP协 议， 并且 PCRF没有接收到 S-GW发送来的网关控制会话建立指示消息， 所 以 PCRF判断 S-GW所在网络不支持动态 PCC。 为了保证在 S-GW和 P-GW 上的策略控制的一致性， 以及能对 UE进行正确的计费， PCRF决定不启动动 态 PCC。 PCRF在向 P-GW的返回消息中携带不启动动态 PCC的指示， 或者 PCRF可以为这种特殊的场景定制一些特殊的动态 PCC规则， 但是这些特殊 的动态 PCC规则必须保证能够正确的对 UE进行计费。
707: P-GW接收到不启动动态 PCC的指示后，使用预先配置的策略计费 规则，或者安装 PCRF为这种特殊的场景定制的特殊的动态 PCC规则； P-GW 向 S-GW返回代理绑定确认消息。
708: S-GW接收到代理绑定确认消息后， 向 MME返回建立默认承载应 答。
709: MME接收到建立默认承载应答后， 发起建立无线承载， 并且通知 UE附着成功。
710: MME通知 UE附着成功后， 发起承载更新， 将无线承载信息发送 给 S-GW。
711 : UE与 AF进行交互， 对访问的业务进行 QoS等参数的协商后， AF 向 PCRF发送应用 /业务信息消息， 提供访问业务所需的业务信息。
712: PCRF保存业务信息， 返回应答消息， 在该应答消息中携带无法检 测承载层事件的指示， 该消息中还可携带无法检测承载层事件的具体原因， 即 S-GW所在网络（即 UE的拜访地网络） 不支持动态 PCC (当前为有限策 略计费控制部署场景） ， 该原因值也可以称为有限策略计费控制部署指示标 识。 AF收到该应答消息后， 不订阅传输 AF信令路径状况通知、 IP-CAN类 型变化通知和 /或请求资源分配成功或失败通知等。
此外，若步骤 711中， AF向 PCRF订阅传输 AF信令路径状况通知、 IP-CAN 类型变化通知和 /或请求资源分配成功或失败通知等， 则步骤 712返回携带无 法检测承载层事件的指示的应答消息并可以携带具体原因， AF 收到该消息 后， 取消订阅。
PCRF也可以通过其它方法检测 S-GW所在网络（即 UE的拜访地网络 ) 不支持动态 PCC, 如 PCEF首先根据代理绑定更新消息中携带的 S-GW的 IP 地址和 PCEF的配置信息 (其中记录了哪些 IP地址对应的拜访地网络支持、 和 /或不支持动态 PCC )判定该拜访地网络或 S-GW不支持动态 PCC, 从而 PCEF向 PCRF上报 S-GW所在网络（即 UE的拜访地网络）不支持动态 PCC。
若 UE通过上述实施例接入之后发生移动， 移动到支持动态 PCC的可信 任非 3GPP接入网、 拜访地 3GPP接入网或回到家乡网络中， PCRF检测到可 信任非 3GPP网络或拜访地 3GPP接入网支持动态 PCC, PCRF将向 AF发送 有限策略计费部署恢复指示 （该指示用于表示当前已由有限策略计费部署恢 复到正常的策略计费部署） ， 通知 AF可以订阅传输 AF信令路径状况通知、 IP-CAN类型变化通知和 /或请求资源分配成功或失败通知等。 此后， AF又可 以进行承载层事件订阅了。
第四实施例
本实施例描述的是 UE从 E-UTRAN接入切换到可信任非 3GPP接入的过 程中 AF获知有限策略计费控制部署的方法。其中， UE从 E-UTRAN接入时， S-GW和 P-GW之间釆用 PMIPv6协议， 并且 3GPP网络支持动态 PCC, 而可 信任非 3GPP接入网关不支持动态 PCC,可信任非 3GPP网络和 3GPP网络属 于不同的运营商。 其中， 当 UE通过 E-UTRAN接入时 , AF订阅了传输 AF 信令路径状况通知、 IP-CAN类型变化通知和 /或请求资源分配成功或失败通 知等。 如图 8所示， 该方法包括如下步骤：
801 : UE与 S-GW之间建立无线接入承载， S-GW与 P-GW之间建立 ΡΜΙΡνό隧道， UE通过 3GPP网络收发数据； 其中， S-GW上安装 PCRF下发 的 QoS规则， P-GW上安装了 PCRF下发的 PCC规则。
802: UE发现可信任非 3GPP接入系统并发起切换。
803： UE在可信任非 3GPP接入系统中执行接入认证和授权； 3GPP AAA 服务器鉴权 UE的非 3GPP接入， 同时 HSS向可信任非 3GPP接入网关返回 在 3GPP系统中 UE连接的 P-GW的地址。 804: UE的层 3附着过程被触发。
805: 可信任非 3GPP接入网关向 P-GW发送代理绑定更新请求。
806： P-GW向 PCRF发送 IP-CAN会话修改指示消息， 该消息中携带 UE 的 NAI、 P-GW为 UE分配的 IP地址、 UE的 APN以及 MPT标识， 该 MPT 标识用于向 PCRF指示 UE釆用 PMIPv6协议接入。
MPT标识也可以通过不携带 GTP协议特定的参数来通知 PCRF当前接入 所釆用的协议为非 GTP协议，如该消息中没有携带 Default— EPS— Bearer— QoS , PCRF就可判断当前接入没有釆用 GTP协议。
807: 由于 MPT指示当前接入所釆用的协议为 PMIPv6或其它非 GTP协 议，并且 PCRF知道 UE发生了从 3GPP网络到非 3GPP网络的切换，但 PCRF 没有接收到可信任非 3GPP接入网关发送来的网关控制会话建立指示消息， 所以 PCRF判断可信任非 3GPP接入网关不支持动态 PCC。 为了保证在可信 任非 3GPP接入网关和 P-GW上的策略控制的一致性，以及能对 UE进行正确 的计费， PCRF决定不启动动态 PCC, PCRF在向 P-GW返回的 IP-CAN会话 修改确认消息中携带不启动动态 PCC的指示； 或者 PCRF可以为这种特殊的 场景定制一些特殊的动态 PCC规则， 但是这些特殊的动态 PCC规则必须保 证能够正确的对 UE进行计费。
808: P-GW根据不启动动态 PCC的指示， 删除在 3GPP接入时 PCRF下 发的 PCC规则， 使用预先配置的策略计费规则、 或者根据 PCRF为这种特殊 的场景定制的特殊的动态 PCC规则更新原来釆用 3GPP接入时 PCRF下发的 PCC规则， 并向可信任非 3GPP接入网关返回代理绑定确认消息。
809: 层 3附着过程完成。
810: 由于 UE在通过 3GPP接入时， AF订阅了传输 AF信令路径状况通 知、 IP-CAN类型变化通知和 /或请求资源分配成功或失败通知等， 但当 UE 切换到可信任非 3GPP接入时， 可信任非 3GPP接入网不支持动态 PCC, 从 而无法检测 AF在源网络中订阅的承载层事件， 因此， PCRF向 AF发送事件 报告消息， 该消息中携带无法检测承载层事件的指示， 该消息中还可以携带 无法检测承载层事件的具体原因， 即非 3GPP网络不支持动态 PCC (当前为 有限策略计费控制部署场景） ， 该原因值也可以称为有限策略计费控制部署 指示标识。
811 : AF收到事件报告消息后， 返回确认消息， 取消订阅。
PCRF也可以通过其它方法检测可信任非 3GPP网络不支持动态 PCC,如 PCEF首先根据代理绑定更新消息中携带的可信任非 3GPP接入网关的 IP地 址和 PCEF的配置信息判定该可信任非 3GPP接入网关不支持动态 PCC, 从 而 PCEF向 PCRF上报可信任非 3GPP接入网关不支持动态 PCC。
若 UE通过上述实施例切换之后又发生移动， 切换到支持动态 PCC的可 信任非 3GPP接入网、 拜访地 3GPP接入网或回到家乡网络中， PCRF检测到 可信任非 3GPP网络或拜访地 3GPP接入网支持动态 PCC, PCRF将向 AF发 送有限策略计费部署恢复指示 （该指示用于表示当前已由有限策略计费部署 恢复到正常的策略计费部署） ,通知 AF可以订阅传输 AF信令路径状况通知、 IP-CAN类型变化通知和 /或请求资源分配成功或失败通知等。 此后， AF又可 以进行承载层事件订阅了。
UE从 3GPP接入切换到可信任非 3GPP接入， S-GW与 P-GW之间釆用
GTP协议， 3GPP网络支持动态 PCC而非 3GPP网络不支持动态 PCC的流程 与此类似。
此外， UE在 3GPP内部发生切换， 源网络支持动态 PCC而目标网络不 支持动态 PCC, 并且目标网络中的 S-GW与 P-GW之间釆用 PMIPv6协议时 的流程与此类似。
相应地， 从非 3GPP接入网络切换到 3GPP网络， 其中 3GPP接入为家乡 路由的漫游方式， 在 S-GW与 P-GW之间釆用 PMIPv6协议， 家乡网络支持 动态 PCC,拜访地网络不支持动态 PCC时的流程，亦可按照本发明思想实现。
根据本发明的基本原理， 上述实施例还可以有多种变换方式， 例如： (一） PCRF也可以根据可信任非 3GPP接入网关的 IP地址和 PCRF的 配置信息、和 /或 UE的转交地址和 PCRF的配置信息、和 /或 S-GW的 IP地址 和 PCRF的配置信息来判断拜访地网络是否支持动态 PCC (即判断当前是否 为有限策略计费控制场景） 。 (二） PCRF也可以在接收到 AF发送的事件订阅请求后， 在相应的应答 消息中通知 AF当前为有限策略控制部署场景。
为了实现实施例中的所述方法， 本发明还提供了一种策略和计费规则功 能实体 PCRF,其支持实现有限策略计费控制， 所述 PCRF设置为判断用户设 备 UE漫游的拜访地网络是否支持策略计费控制 PCC, 如果所述拜访地网络 不支持， 则通知应用功能 AF其订阅的事件无法上报。
此外， PCRF设置为向所述 AF发送消息， 所述消息中携带用于指示有限 策略计费控制部署的标识， 以使所述 AF根据所述标识不进行事件的订阅、 和 /或取消事件的订阅。
此外， PCRF设置为釆用如下方式判断所述拜访地网络是否支持所述
PCC:
所述 PCRF接收到 IP承载网络连接接入网络 IP-CAN会话建立指示消息、 或 IP-CAN会话修改指示消息后， 判断所述拜访地网络是否支持所述 PCC, 当所述 IP-CAN会话建立指示消息、或所述 IP-CAN会话修改指示消息中携带 的移动性管理协议指示 MPT标识表明接入所釆用的协议不是通用无线分组 业务 GPRS隧道协议、且所述 PCRF未接收到网关控制会话建立指示消息时， 判定所述拜访网络不支持所述 PCC。
此外， PCRF设置为釆用如下方式判断所述拜访地网络是否支持所述 PCC:
所述 PCRF根据所述 PCRF的配置信息以及： 所述拜访地网络的接入网 关的 IP地址、 和 /或所述 UE的转交地址、 和 /或服务网关的 IP地址判断所述 拜访地网络是否支持所述 PCC。
此外， PCRF设置为釆用如下方式判断所述拜访地网络是否支持所述 PCC:
策略和计费执行功能实体 PCEF根据所述 PCRF的配置信息以及： 所述 拜访地网络的接入网关的 IP地址、 和 /或 UE的转交地址、 和 /或服务网关的 IP 地址判断所述拜访网络是否支持所述 PCC , 并将判断结果通知给所述 PCRF, 所述 PCRF根据所述判断结果判断所述拜访网络是否支持所述 PCC。 此外， PCRF设置为在接收到所述 AF发送的应用 /业务信息消息、或事件 订阅消息后， 将无法上报事件指示包含在相应的应答消息中发送给所述 AF。
此外， PCRF还设置为将无法上报事件指示包含在事件通知消息中发送给 所述 AF。
此外， PCRF还设置为当所述 UE切换到不支持 BBERF功能的接入网关 时， 通知所述 AF其订阅的事件无法上报。
此外， PCRF还设置为当所述 PCRF检测到所述 UE移动到支持所述 PCC 的可信任非 3GPP接入网、 拜访地 3GPP接入网或家乡网络后， 向所述 AF发 送有限策略计费控制部署恢复指示标识。
为了实现实施例中的所述方法， 本发明还提供一种实现有限策略计费控 制的系统， 如图 9所示， 包括如上面所述的策略和计费规则功能实体 PCRF 和应用功能 AF。
工业实用性
釆用本发明的方法及系统， 在实现有限策略计费控制时（即拜访网络不 支持 PCC时） ， 可以更方便、 更准确地通知 AF当前的策略计费控制部署情 况， AF可以根据当前的策略计费控制部署情况进行相应的操作， 例如不进行 事件的订阅或取消事件的订阅， 以达到节省系统资源的目的。

Claims

权 利 要 求 书
1、 一种实现有限策略计费控制的方法， 所述方法包括：
策略和计费规则功能实体 PCRF判断用户设备 UE漫游的拜访地网络是 否支持策略计费控制 PCC, 如果所述拜访地网络不支持所述 PCC, 则通知应 用功能 AF其订阅的事件无法上报。
2、 如权利要求 1所述的方法， 其还包括：
接收到所述通知后， 所述 AF不进行事件的订阅、 和 /或取消事件的订阅。
3、 如权利要求 1所述的方法， 其中， 所述通知步骤包括向所述 AF发送 消息， 所述消息中携带用于指示有限策略计费控制部署的标识；
接收到所述 PCRF的携带所述标识的消息后 ,所述 AF根据所述标识不进 行事件的订阅、 和 /或取消事件的订阅。
4、 如权利要求 1所述的方法， 其中， 所述 PCRF釆用如下方式之一判断 所述拜访地网络是否支持所述 PCC:
所述 PCRF接收到 IP承载网络连接接入网络 IP-CAN会话建立指示消息、 或 IP-CAN会话修改指示消息后， 判断所述拜访地网络是否支持所述 PCC, 当所述 IP-CAN会话建立指示消息、或所述 IP-CAN会话修改指示消息中携带 的移动性管理协议指示 MPT标识表明接入所釆用的协议不是通用无线分组 业务 GPRS隧道协议、且所述 PCRF未接收到网关控制会话建立指示消息时， 判定所述拜访网络不支持所述 PCC; 或
所述 PCRF根据所述 PCRF的配置信息以及： 所述拜访地网络的接入网 关的 IP地址、 和 /或所述 UE的转交地址、 和 /或服务网关的 IP地址判断所述 拜访地网络是否支持所述 PCC; 或
策略和计费执行功能实体 PCEF根据所述 PCRF的配置信息以及： 所述 拜访地网络的接入网关的 IP地址、 和 /或 UE的转交地址、 和 /或服务网关的 IP地址判断所述拜访地网络是否支持所述 PCC, 并将判断结果通知给所述
PCRF ,所述 PCRF根据所述判断结果判断所述拜访地网络是否支持所述 PCC。
5、 如权利要求 1至 4中任一权利要求所述的方法， 其中， 在接收到所述 AF发送的应用 /业务信息消息、 或事件订阅消息后， 所述 PCRF将无法上报事件指示包含在相应的应答消息中发送给所述 AF。
6、 如权利要求 1至 4中任一权利要求所述的方法， 其中，
所述 PCRF将无法上报事件指示包含在事件通知消息中发送给所述 AF。
7、 如权利要求 1所述的方法， 其还包括：
当所述 UE切换到不支持 BBERF功能的接入网关时， 所述 PCRF通知所 述 AF其订阅的事件无法上报。
8、 如权利要求 1所述的方法， 其还包括：
当所述 PCRF检测到所述 UE移动到支持所述 PCC的可信任非 3GPP接 入网、拜访地 3GPP接入网或家乡网络后， 所述 PCRF向所述 AF发送有限策 略计费控制部署恢复指示标识。
9、 一种策略和计费规则功能实体 PCRF,其支持实现有限策略计费控制， 所述 PCRF设置为判断用户设备 UE漫游的拜访地网络是否支持策略计 费控制 PCC, 如果所述拜访地网络不支持， 则通知应用功能 AF其订阅的事 件无法上报。
10、 如权利要求 9所述的 PCRF, 其中，
所述 PCRF设置为向所述 AF发送消息，所述消息中携带用于指示有限策 略计费控制部署的标识， 以使所述 AF根据所述标识不进行事件的订阅、 和 / 或取消事件的订阅。
11、 如权利要求 9所述的 PCRF， 其中， 所述 PCRF设置为釆用如下方式 之一判断所述拜访地网络是否支持所述 PCC:
所述 PCRF接收到 IP承载网络连接接入网络 IP-CAN会话建立指示消息、 或 IP-CAN会话修改指示消息后， 判断所述拜访地网络是否支持所述 PCC, 当所述 IP-CAN会话建立指示消息、或所述 IP-CAN会话修改指示消息中携带 的移动性管理协议指示 MPT标识表明接入所釆用的协议不是通用无线分组 业务 GPRS隧道协议、且所述 PCRF未接收到网关控制会话建立指示消息时， 判定所述拜访网络不支持所述 PCC; 或 所述 PCRF根据所述 PCRF的配置信息以及： 所述拜访地网络的接入网 关的 IP地址、 和 /或所述 UE的转交地址、 和 /或服务网关的 IP地址判断所述 拜访地网络是否支持所述 PCC; 或
策略和计费执行功能实体 PCEF根据所述 PCRF的配置信息以及： 所述 拜访地网络的接入网关的 IP地址、 和 /或 UE的转交地址、 和 /或服务网关的 IP 地址判断所述拜访网络是否支持所述 PCC , 并将判断结果通知给所述 PCRF, 所述 PCRF根据所述判断结果判断所述拜访网络是否支持所述 PCC。
12、如权利要求 9至 11中任一权利要求所述的 PCRF,其中， 所述 PCRF 还设置为：
在接收到所述 AF发送的应用 /业务信息消息、 或事件订阅消息后， 将无 法上报事件指示包含在相应的应答消息中发送给所述 AF。
13、如权利要求 9至 11中任一权利要求所述的 PCRF,其中， 所述 PCRF 还设置为将无法上报事件指示包含在事件通知消息中发送给所述 AF。
14、 如权利要求 9所述的 PCRF, 其中， 所述 PCRF还设置为： 当所述 UE切换到不支持 BBERF功能的接入网关时， 通知所述 AF其订 阅的事件无法上报。
15、 如权利要求 9所述的 PCRF, 其中， 所述 PCRF还设置为： 当所述 PCRF检测到所述 UE移动到支持所述 PCC的可信任非 3GPP接 入网、拜访地 3GPP接入网或家乡网络后， 向所述 AF发送有限策略计费控制 部署恢复指示标识。
16、 一种实现有限策略计费控制的系统， 其包括如权利要求 9-15中任一 项所述的 PCRF和所述 AF。
PCT/CN2009/073835 2009-04-20 2009-09-09 一种实现有限策略计费控制的方法及系统 WO2010121460A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US13/259,957 US8817612B2 (en) 2009-04-20 2009-09-09 Method for implementing limited policy and charging control and system thereof
EP09843564.7A EP2424160B1 (en) 2009-04-20 2009-09-09 Method for implementing limited policy and charging control and system thereof

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910134979.0A CN101867909B (zh) 2009-04-20 2009-04-20 一种实现有限策略计费控制的方法及系统
CN200910134979.0 2009-04-20

Publications (1)

Publication Number Publication Date
WO2010121460A1 true WO2010121460A1 (zh) 2010-10-28

Family

ID=42959417

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/073835 WO2010121460A1 (zh) 2009-04-20 2009-09-09 一种实现有限策略计费控制的方法及系统

Country Status (4)

Country Link
US (1) US8817612B2 (zh)
EP (1) EP2424160B1 (zh)
CN (1) CN101867909B (zh)
WO (1) WO2010121460A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111726234A (zh) * 2013-07-24 2020-09-29 康维达无线有限责任公司 服务域收费系统和方法

Families Citing this family (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013016189A1 (en) * 2011-07-22 2013-01-31 Interdigital Patent Holdings, Inc. Managing multicast traffic
CN102917355A (zh) * 2011-08-03 2013-02-06 中兴通讯股份有限公司 一种接入方法、系统及移动智能接入点
KR101923487B1 (ko) 2011-09-29 2018-11-30 삼성전자 주식회사 통신 연결 서비스 제공 방법 및 장치
CN103313317B (zh) * 2012-03-07 2016-09-28 华为技术有限公司 一种WiFi终端接入分组数据PS业务域的方法和可信网关
WO2014022984A1 (zh) 2012-08-08 2014-02-13 华为技术有限公司 信息处理方法和装置
EP2728813B1 (en) * 2012-11-02 2017-01-04 Telefonaktiebolaget LM Ericsson (publ) Application function dependent policy control
CN103929787A (zh) * 2013-01-11 2014-07-16 电信科学技术研究院 一种异构网络切换方法、装置及系统
US9220118B1 (en) 2013-08-07 2015-12-22 Sprint Spectrum L.P. Method and system for establishing a default bearer in accordance with a substitute packet data policy
CN104519472B (zh) * 2013-09-30 2019-06-18 中兴通讯股份有限公司 终端ue的接入网信息处理方法、装置及pcrf
US9350734B1 (en) 2013-11-01 2016-05-24 Sprint Spectrum L.P. Method and system for managing a flood of data-connection requests
US9924434B1 (en) 2013-11-07 2018-03-20 Sprint Spectrum L.P. Method and system for diverting WCDs based on unavailability of authentication procedure
FR3021836A1 (fr) * 2014-05-28 2015-12-04 Orange Procede pour informer une entite d' un reseau ip du type de reseau d' acces utilise par un terminal
CN105553923A (zh) * 2014-11-04 2016-05-04 中兴通讯股份有限公司 一种获取用户标识的方法及网络侧设备
CN105682068A (zh) * 2014-11-17 2016-06-15 中兴通讯股份有限公司 一种启用策略和计费控制的方法、装置和系统
US9763130B1 (en) * 2014-11-26 2017-09-12 Sprint Spectrum L.P. Systems and methods for managing congestion in a wireless communication network
CN107135084B (zh) * 2016-02-29 2020-03-31 华为技术有限公司 一种策略配置方法和装置
BR112021001605A2 (pt) * 2018-08-13 2021-04-27 Telefonaktiebolaget Lm Ericsson (Publ) métodos em uma função de exposição de rede e em uma função de controle de política, aparelhos de função de exposição de rede e de função de controle de política, e, mídia legível por computador não transitória
WO2020103662A1 (en) * 2018-11-19 2020-05-28 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for event monitoring
US11632472B2 (en) * 2019-06-18 2023-04-18 Nokia Technologies Oy Event subscription notification
US11025783B2 (en) * 2019-08-20 2021-06-01 Oracle International Corporation Methods, systems, and computer readable media for extending new radio (NR) usage indications to application function (AF)
US11468425B1 (en) * 2020-03-30 2022-10-11 Cisco Technology, Inc. Asynchronously initiating online charging triggers in mobile networks
CN112752231B (zh) * 2020-12-29 2022-07-22 中国联合网络通信集团有限公司 漫游业务接入控制方法、智能卡、终端及网关设备

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101047874A (zh) * 2006-03-31 2007-10-03 华为技术有限公司 移动通信网络中业务信息决策方法

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7436766B2 (en) * 2005-04-04 2008-10-14 Lucent Technologies Inc. Telecommunication network support for service based policy in roaming configurations
WO2007026268A1 (en) * 2005-08-31 2007-03-08 Nokia Corporation Inter-access mobility and service control
GB2436665A (en) * 2006-03-31 2007-10-03 Fujitsu Ltd Efficient call routing while roaming
US8489096B2 (en) * 2006-06-01 2013-07-16 Nokia Corporation Inter-access handover with access specific policy control functions
US8856860B2 (en) * 2006-08-18 2014-10-07 Cisco Technology, Inc. System and method for implementing policy server based application interaction manager
US8086216B2 (en) * 2007-01-31 2011-12-27 Alcatel Lucent Mobility aware policy and charging control in a wireless communication network
CN101110766B (zh) * 2007-03-23 2010-04-21 华为技术有限公司 一种信令ip流承载事件上报的控制方法和功能实体
US8155020B2 (en) * 2008-01-14 2012-04-10 Qualcomm Incorporated Policy control and charging (PCC) rules based on mobility protocol
CN101267319B (zh) * 2008-04-30 2011-07-13 中兴通讯股份有限公司 一种下发策略计费控制规则的方法
US8249551B2 (en) * 2008-06-05 2012-08-21 Bridgewater Systems Corp. Long-term evolution (LTE) policy control and charging rules function (PCRF) selection
US8521775B1 (en) * 2008-08-20 2013-08-27 At&T Mobility Ii Llc Systems and methods for implementing a master policy repository in a policy realization framework
US8537822B2 (en) * 2008-11-10 2013-09-17 Research In Motion Limited Methods and apparatus for providing alternative paths to obtain session policy
US7957314B2 (en) * 2008-12-12 2011-06-07 Cisco Technology, Inc. System and method for provisioning charging and policy control in a network environment

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101047874A (zh) * 2006-03-31 2007-10-03 华为技术有限公司 移动通信网络中业务信息决策方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111726234A (zh) * 2013-07-24 2020-09-29 康维达无线有限责任公司 服务域收费系统和方法
CN111726234B (zh) * 2013-07-24 2023-03-24 康维达无线有限责任公司 服务域收费系统和方法

Also Published As

Publication number Publication date
US8817612B2 (en) 2014-08-26
EP2424160B1 (en) 2016-03-09
US20120020345A1 (en) 2012-01-26
EP2424160A4 (en) 2013-04-10
CN101867909B (zh) 2013-10-16
CN101867909A (zh) 2010-10-20
EP2424160A1 (en) 2012-02-29

Similar Documents

Publication Publication Date Title
WO2010121460A1 (zh) 一种实现有限策略计费控制的方法及系统
EP2351345B1 (en) Detection and report of limited policy and charging control capabilities
US8874715B2 (en) Charging method, system and reporting method for terminal accessing through multiple access networks
US9137652B2 (en) Method for implementing policy and charging control in a roaming scene
US8621555B2 (en) Access control method and system for packet data network, PCRF entity
EP2302842B1 (en) Method for sending down and installing event trigger
CN101267319B (zh) 一种下发策略计费控制规则的方法
US8849273B2 (en) Method and system for reporting fixed network access information
US8811342B2 (en) Method and system for deleting redundant information of home policy and charging rules function
EP2790455A1 (en) Policy control method and system for converged network
WO2009124436A1 (zh) 一种承载绑定和事件报告功能策略控制的方法及系统
WO2011029289A1 (zh) 漫游场景下承载控制模式的发送方法和系统
WO2013060170A1 (zh) 一种提供基于lipa承载的计费支持的方法及装置
WO2014107985A1 (zh) 漫游本地业务的在线计费方法、h-ocs及v-ocs
WO2011018020A1 (zh) 控制pcrf负载均衡的方法、系统及重定向dra
WO2012129992A1 (zh) 被赞助数据连接的处理方法及策略与计费规则功能实体
WO2010118673A1 (zh) 策略和计费控制的处理方法、系统及设备
WO2012155774A1 (zh) S9子会话建立方法、系统及pcrf
WO2013113263A1 (zh) 一种应用检测控制功能模式的识别方法及系统
WO2011029349A1 (zh) 多承载绑定和事件报告功能的处理方法及系统
WO2014079323A1 (zh) 一种漫游本地业务功能实现方法、装置和系统
WO2012126311A1 (zh) 创建和删除Diameter路由代理中绑定信息的方法及系统、H-PCRF
WO2013020451A1 (zh) 一种建立会话的方法及系统
WO2012022218A1 (zh) 一种建立会话、策略下发的方法和系统
WO2010025627A1 (zh) 会话信息的标识方法及装置

Legal Events

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

Ref document number: 09843564

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 13259957

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2009843564

Country of ref document: EP