WO2011018030A1 - 策略和计费控制规则授权方法、装置及系统 - Google Patents

策略和计费控制规则授权方法、装置及系统 Download PDF

Info

Publication number
WO2011018030A1
WO2011018030A1 PCT/CN2010/075870 CN2010075870W WO2011018030A1 WO 2011018030 A1 WO2011018030 A1 WO 2011018030A1 CN 2010075870 W CN2010075870 W CN 2010075870W WO 2011018030 A1 WO2011018030 A1 WO 2011018030A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
policy
arp
rule
resource allocation
Prior art date
Application number
PCT/CN2010/075870
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 EP10807975.7A priority Critical patent/EP2458809B1/en
Publication of WO2011018030A1 publication Critical patent/WO2011018030A1/zh
Priority to US13/370,798 priority patent/US8958322B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/781—Centralised allocation of resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/805—QOS or priority aware
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/53—Allocation or scheduling criteria for wireless resources based on regulatory allocation policies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a policy, a charging control rule authorization method, apparatus, and system.
  • the allocation and retention priority (Allocation and Retention Priority, ARP) parameters are introduced.
  • the bearer binding is performed by using the QoS Class Identification (QCI) and the ARP parameters, that is, the QCI and ARP parameters of all PCC rules on the same bearer are the same.
  • QCI QoS Class Identification
  • the UE When the user equipment (User Equipment, UE) is connected to the 2G/3G and supports the hybrid control mode, the UE may perform a traffic flow template (Traffic Flow Template) on the secondary context initiated by the network side. Add operation and corresponding Quality of Service (QoS) operation; General Packet Radio Service (GPRS): Service GPRS Support Node (SGSN)
  • QoS Quality of Service
  • GPRS General Packet Radio Service
  • SGSN Service GPRS Support Node
  • the resource allocation request message is sent to the service gateway (Service Gateway, SGW for short), and the resource allocation request message carries the TFT and QoS information, and also carries a bearer ID (Bearer ID), which is used to indicate that the resource needs to be in the specified bearer.
  • SGW Service Gateway
  • the SGW forwards the resource allocation request message to the Packet Data Network Gateway (PGW); the PGW initiates an Internet protocol to the Policy Control and Charging Rules Function (PCRF) Internet Access Connectivity Network (IP) -CAN) session tampering message; after receiving the IP-CAN session tampering message, the PCRF generates a new PCC rule and generates ARP parameters and QCI corresponding to the new PCC rule. Since the PCRF cannot know the bearer ID, it cannot be known. The ARP parameter generated on the bearer corresponding to the bearer ID may be different from the ARP parameter of other PCC rules on the bearer corresponding to the bearer ID.
  • PCRF Policy Control and Charging Rules Function
  • IP Internet Access Connectivity Network
  • the embodiments of the present invention provide a method, a device, and a system for authorizing a policy and a charging control rule, which enable a UE to successfully allocate resources to a specified bearer.
  • An embodiment of the present invention provides a policy and a charging control rule authorization method, including: receiving a resource allocation request message, where the resource allocation request message indicates that resources are allocated on a designated bearer;
  • An embodiment of the present invention provides a policy and charging rule execution apparatus, including:
  • a first receiving module configured to receive a resource allocation request message, where the resource allocation request message indicates that resources are allocated on the designated bearer
  • a sending module configured to send, to the policy and charging rule function entity PCRF, the allocation of the designated bearer indicated by the resource allocation request message received by the first receiving module, and the retention priority ARP information, where the second receiving module is configured to receive the
  • the PCRF controls the quality of service QoS of the PCC rule according to the policy and charging control of the ARP information of the specified bearer sent by the sending module;
  • a binding module configured to perform bearer binding according to the QoS of the authorized PCC rule received by the second receiving module.
  • the embodiment of the invention provides a policy and charging rule authorization device, including:
  • a receiving module configured to receive, by the policy and charging enforcement entity, the PCEF, according to the received resource allocation request message, the allocation of the specified bearer and the retention priority ARP information, where the resource allocation request message indicates that the resource is allocated on the designated bearer;
  • a first sending module configured to send, to the PCEF, a policy and a charging control PCC rule quality of service QoS according to the ARP information authorization of the specified bearer received by the receiving module.
  • the embodiment of the invention provides a policy and charging control rule authorization system, which comprises the above policy and charging rule execution device and a policy and charging rule authorization device.
  • the ARP information of the specified bearer is sent to the PCRF, and the bearer binding is performed according to the QoS of the PCC rule authorized by the PCRF according to the ARP information of the specified bearer.
  • the PCRF can learn the ARP information of the specified bearer, so that the embodiment of the present invention can bind the PCC rule authorized by the PCRF to the designated bearer, so that the UE successfully allocates the resource on the designated bearer.
  • FIG. 1 is a flowchart of Embodiment 1 of a policy and charging control rule authorization method provided by the present invention
  • FIG. 2 is a flowchart of Embodiment 2 of a policy and charging control rule authorization method provided by the present invention
  • FIG. 4 is a flowchart of Embodiment 4 of a policy and charging control rule authorization method provided by the present invention
  • FIG. 5 is a flowchart of the policy and charging control provided by the present invention
  • FIG. 6 is a flowchart of Embodiment 6 of a policy and charging control rule authorization method provided by the present invention
  • FIG. 7 is a flowchart of a policy and charging rule execution apparatus according to an embodiment of the present invention
  • FIG. 8 is a schematic structural diagram of an embodiment of a policy and charging rule authorization apparatus according to the present invention
  • FIG. 9 is a schematic structural diagram of an embodiment of a policy and charging control rule authorization system provided by the present invention.
  • FIG. 1 is a flowchart of Embodiment 1 of a policy and charging control rule authorization method provided by the present invention. As shown in FIG. 1, the embodiment specifically includes the following steps:
  • Step 101 Receive a resource allocation request message, where the resource allocation request message indicates that resources are allocated on a designated bearer.
  • the designated bearer is an established bearer, and the hybrid mode UE initiates a resource allocation request message on the established bearer, and the policy and charging execution function entity (Policy and Charging Enforcement) Function, abbreviated as: PCEF) receives the resource allocation request message, which indicates that resources are allocated on the designated bearer.
  • policy and charging execution function entity Policy and Charging Enforcement Function
  • Step 102 Send, to the PC F, the A P information of the designated bearer.
  • the PCEF When the PCEF learns that the operation needs to be performed on the designated bearer according to the resource allocation request message, the PCEF sends the ARP information of the specified bearer to the PCRF.
  • the ARP information of the specified bearer is related to the ARP parameter of the specified bearer. It can be specific to the A P parameter of the specified bearer or the existing PCC rule in the specified bearer.
  • Step 103 The receiving PCRF performs bearer binding according to the QoS of the PCC rule authorized by the ARP information of the specified bearer according to the QoS of the authorized PCC rule.
  • the PCRF authorizes the PCC rule according to the ARP information of the specified bearer, and the authorized PCC rule
  • the QoS is sent to the PCEF, and the PCEF performs bearer binding according to the QoS of the authorized PCC rule.
  • the PCEF after receiving the resource allocation request message, the PCEF sends the ARP information of the specified bearer to the PCRF.
  • the PCRF authorizes the PCC rule according to the ARP information of the specified bearer, and the PCEF performs bearer binding according to the QoS of the authorized PCC rule.
  • the PCRF can learn the ARP information of the specified bearer, so that the PCEF can bind the PCC rule authorized by the PCRF to the specified bearer, so that the UE successfully allocates the resource on the designated bearer.
  • FIG. 2 is a flowchart of Embodiment 2 of a policy and charging control rule authorization method provided by the present invention.
  • the present embodiment is applicable to a System Architecture Evolution (SAE) network of the 3GPP R8, where the UE is a hybrid mode terminal capable of supporting both 2G and 3G, and the PCEF is specifically a PGW, and the UE is connected to the 3GPP anchor point.
  • SAE System Architecture Evolution
  • the SGSN (S4-SGSN) of the S4 is connected to the SGW and the PGW, and the S5 interface is the S5 interface.
  • the protocol of the S5 interface is the GPRS Tunneling Protocol (GTP).
  • GTP GPRS Tunneling Protocol
  • This embodiment is specifically a processing flow for initiating a TFT addition operation on a packet data protocol (PDP) connection established by the UE on the network side.
  • PDP packet data protocol
  • the embodiment specifically includes the following steps:
  • Step 201 The UE sends a modify PDP context request message to the S4-SGSN, where the purpose is to add a TFT and perform a corresponding QoS operation on the PDP connection established on the network side.
  • Step 202 The S4-SGSN converts the modified PDP context request message into a resource allocation request message, specifically a Bearer Resource Command, and sends the message to the SGW.
  • the bearer resource command carries the information such as the TFT, the QoS, and the bearer ID.
  • the bearer ID is the identifier of the PDP connection established on the network side.
  • Step 203 The SGW forwards the bearer resource command to the PGW.
  • Step 204 The PGW receives the bearer resource command, and according to the bearer ID carried in the bearer resource command, learns that the resource needs to be allocated on the designated bearer corresponding to the bearer ID.
  • the PGW sends an IP-CAN session modification message to the PCRF, where the IP-CAN session modification message is sent. It carries the ARP parameters of the specified bearer.
  • the designated bearer in this embodiment is a PDP connection established on the network side.
  • the IP-CAN session modification message can carry information such as TFT and QoS.
  • Step 205 The PCRF determines whether the ARP parameter of the specified bearer can be used for resource allocation. If yes, step 206 is performed; otherwise, step 210 is performed.
  • the PCRF determines whether the ARP parameter of the specified bearer is applicable to the resource allocation according to the TFT information carried in the IP-CAN session modification message according to the TFT information carried in the IP-CAN session modification message.
  • Step 206 The PCRF authorizes the PCC rule according to the ARP parameter of the specified bearer.
  • the ARP parameter of the authorized PCC rule is the same as the ARP parameter of the specified bearer, and the QoS of the authorized PCC rule is sent to the PGW.
  • Step 207 The PGW performs bearer binding according to the QoS of the authorized PCC rule.
  • the PGW binds the authorized PCC rules and other PCC rules in the specified bearer to the specified bearer.
  • Step 209 The S4-SGSN returns a Modify PDP Context Response message to the UE, and ends.
  • Step 210 The PCRF returns a failure information to the PGW, where the failure information is used to indicate that the UE initiates a resource allocation request on the new bearer.
  • the failure information may carry a cause value.
  • Step 211 The PGW returns the failure information to the S4-SGSN through the SGW, and the S4-SGSN returns a modified PDP context failure message carrying the failure information to the UE, and ends.
  • the PGW after receiving the resource allocation request message, the PGW sends the ARP parameter of the specified bearer to the PCRF.
  • the PCRF determines that the ARP parameter of the specified bearer can be used for resource allocation
  • the PCRF authorizes the PCC rule according to the ARP parameter of the specified bearer.
  • the PGW performs bearer binding according to the QoS of the authorized PCC rule.
  • the PCRF can know the ARP information of the specified bearer, so that the PGW can The PCC rules authorized by the PCRF are bound to the specified bearer, so that the UE successfully allocates resources to the specified bearer.
  • the PCRF may return a failure information for indicating that the UE initiates a resource allocation request on the new bearer.
  • FIG. 3 is a flowchart of Embodiment 3 of a policy and charging control rule authorization method provided by the present invention.
  • the scenario in this embodiment is the same as that in the foregoing embodiment. The difference is that: in this embodiment, the PGW needs to send the existing PCC rule in the specified bearer to the PCRF when the resource needs to be allocated on the designated bearer.
  • the PGW needs to send the existing PCC rule in the specified bearer to the PCRF when the resource needs to be allocated on the designated bearer.
  • the specific instructions are as follows.
  • the embodiment specifically includes the following steps:
  • Step 301 The UE sends a modify PDP context request message to the S4-SGSN, where the purpose is to add a TFT and perform a corresponding QoS operation on the PDP established on the network side.
  • Step 302 The S4-SGSN converts the modified PDP context request message into a resource allocation request message, which is specifically a bearer resource command, and sends the message to the SGW.
  • the bearer resource command carries the information such as the TFT, the QoS, and the bearer ID.
  • the bearer ID is the identifier of the PDP connection established on the network side.
  • Step 303 The SGW forwards the bearer resource command to the PGW.
  • step 304 the PGW receives the bearer resource command, and according to the bearer ID carried in the bearer resource command, it is learned that the resource needs to be allocated on the designated bearer corresponding to the bearer ID; the PGW sends an IP-CAN session modification message to the PCRF, and the IP-CAN session modification message is sent. It carries the existing PCC rules in the specified bearer.
  • the designated bearer in this embodiment is a PDP connection established on the network side.
  • the IP-CAN session modification message can carry information such as TFT and QoS.
  • Step 305 The PCRF obtains an ARP parameter of the existing PCC rule, and determines whether the ARP parameter can be used for resource allocation. If yes, step 306 is performed; otherwise, step 310 is performed.
  • the PCRF determines whether the APC parameter of the existing PCC rule is applicable to the PCC rule that is required to be authorized according to the TFT information carried in the IP-CAN session modification message, that is, whether the ARP parameter of the existing PCC rule can be determined. Used for resource allocation.
  • Step 306 The PCR authorizes the PCC rule according to the ARP parameter of the existing PCC rule, and the ARP parameter of the authorized PCC rule is the same as the ARP parameter of the existing PCC rule, and the authorized PCC is authorized.
  • the QoS of the rule is sent to the PGW.
  • Step 307 The PGW performs bearer binding according to the QoS of the authorized PCC rule.
  • the PGW binds the authorized PCC rules and existing PCC rules in the specified bearer to the specified bearer.
  • Step 308 The PGW, the SGW, and the S4-SGSN perform a proprietary tampering operation because the ARP parameters of the authorized PCC rule are the same as the ARP parameters of the existing designated bearer.
  • Step 309 The S4-SGSN returns a Modify PDP Context Response message to the UE, and ends.
  • Step 310 The PCRF returns a failure information to the PGW, where the failure information is used to indicate that the UE initiates a resource allocation request on the new bearer.
  • the failure information may carry a cause value.
  • Step 311 The PGW returns the failure information to the S4-SGSN through the SGW, and the S4-SGSN returns a modified PDP context failure message carrying the failure information to the UE, and ends.
  • the PGW after receiving the resource allocation request message, the PGW sends the existing PCC rule in the specified bearer to the PCRF.
  • the PCRF determines that the ARP parameter of the specified bearer can be used for resource allocation, the PCRF is based on the existing PCC rule.
  • the ARP parameter authorizes the PCC rule, and the PGW performs bearer binding according to the QoS of the authorized PCC rule.
  • the PCRF can learn the ARP information of the specified bearer, so that the PGW can bind the PCC rule authorized by the PCRF to the designated bearer, so that the UE successfully allocates the resource on the designated bearer.
  • the PCRF may return a failure information indicating that the UE initiates a resource allocation request on the new bearer.
  • FIG. 4 is a flowchart of Embodiment 4 of a policy and charging control rule authorization method provided by the present invention.
  • This embodiment is applicable to the GPRS network of the 3GPP R8, where the UE is a hybrid mode terminal capable of supporting both 2G and 3G, and the PCEF is specifically a GPRS gateway support node (Gateway GPRS Support Node, GGSN), and the UE is connected through the SGSN. To the GGSN.
  • the embodiment is specifically a process of initiating a TFT adding operation on the PDP connection established by the UE on the network side, and modifying the context request message is specifically modifying the PDP context request message.
  • the embodiment specifically includes the following steps:
  • Step 401 The UE sends a modify PDP context request message to the SGSN, where the purpose is to add a TFT and perform a corresponding QoS operation on the PDP established on the network side.
  • Step 402 The SGSN sends a modify PDP context request message to the GGSN.
  • the modified PDP context request message carries information such as a TFT, a QoS, and a PDP Context ID, where the PDP context ID is an identifier of a PDP connection established by the network side, and the PDP context ID indicates the tampering PDP context.
  • the request message request allocates resources on the specified 7
  • Step 403 After receiving the modify PDP context request message, the GGSN sends an IP-CAN session setup message to the PCRF, where the IP-CAN session setup message carries the ARP parameter of the designated bearer.
  • the GGSN performs an IP-CAN bearer setup operation, and the GGSN reassigns the bearer ID.
  • the designated bearer in this embodiment is a PDP connection established on the network side.
  • the IP-CAN session setup message may carry information such as TFT, QoS, and reassigned bearer ID.
  • Step 404 The PCRF determines whether the ARP parameter of the specified bearer can be used for resource allocation. If yes, step 405 is performed; otherwise, step 409 is performed.
  • the PCRF determines whether the ARP parameter of the specified bearer is applicable to the resource allocation according to the TFT information carried in the IP-CAN session establishment message, and whether the ARP parameter of the specified bearer is applicable to the resource allocation.
  • the GGSN has not previously reported the bearer ID to the PCRF. According to the re-assigned bearer ID, the PCRF still does not know that the resource needs to be allocated on the specified bearer, but the ARP parameter of the specified bearer needs to be allocated on the specified bearer.
  • Step 405 The PCRF authorizes the PCC rule according to the ARP parameter of the specified bearer.
  • the ARP parameter of the authorized PCC rule is the same as the ARP parameter of the specified bearer, and the QoS of the authorized PCC rule is sent to the GGSN.
  • Step 406 The GGSN performs bearer binding according to the QoS of the authorized PCC rule.
  • the GGSN binds the authorized PCC rules and other PCC rules in the specified bearer to the specified bearer.
  • Step 407 The GGSN and the SGSN perform a secondary context tampering operation because the ARP parameter of the authorized PCC rule is the same as the ARP parameter of the existing designated bearer.
  • Step 408 The SGSN returns a Modify PDP Context Response message to the UE, and ends.
  • the failure information may carry a cause value.
  • Step 410 The GGSN returns the failure information to the SGSN, and the SGSN returns a ⁇ ⁇ tampering PDP context failure message carrying the failure information to the UE, and ends.
  • the GGSN receives the resource allocation request message (specifically, the tampering in this embodiment)
  • the ARP parameter is specified to be sent to the PCRF.
  • the PCRF determines that the ARP parameter of the specified bearer can be used for resource allocation, the PCRF authorizes the PCC rule according to the ARP parameter of the specified bearer, and the GGSN according to the authorized The QoS of the PCC rule carries the bearer binding.
  • the PCRF can learn the ARP information of the specified bearer, so that the GGSN can bind the PCC rules authorized by the PCRF to the designated bearer, so that the UE successfully allocates resources to the designated bearer.
  • the PCRF may return a failure information, indicating that the UE initiates a resource allocation request on the new bearer.
  • FIG. 5 is a flowchart of Embodiment 5 of a policy and charging control rule authorization method provided by the present invention.
  • the scenario in this embodiment is the same as that in the foregoing embodiment 4, except that: in this embodiment, when the GGSN needs to allocate resources on the designated bearer, the PGSN needs to send the existing PCC rule in the specified bearer to the PCRF.
  • the PGSN needs to send the existing PCC rule in the specified bearer to the PCRF.
  • the specific instructions are as follows.
  • Step 501 The UE sends a modify PDP context request message to the SGSN, where the purpose is to add a TFT and perform a corresponding QoS operation on the PDP established on the network side.
  • Step 502 The SGSN sends a modify PDP context request message to the GGSN.
  • the modified PDP context request message carries information such as the TFT, the QoS, and the PDP context ID, where the PDP context ID is an identifier of the PDP connection established by the network side, and the PDP context ID indicates that the modified PDP context request message is requested in the specified bearer. Allocate resources on.
  • Step 503 After receiving the modify PDP context request message, the GGSN sends an IP-CAN session establishment message to the PCRF, where the IP-CAN session setup message carries the existing PCC rule in the specified bearer.
  • This embodiment is applicable to the case where the GGSN does not upload the ID to the PCRF.
  • the GGSN performs an IP-CAN bearer setup operation, and the GGSN reassigns the bearer ID.
  • the designated bearer in this embodiment is a PDP connection established on the network side.
  • IP-CAN session setup message In addition to carrying existing PCC rules, it can also carry information such as TFT, QoS, and reassigned bearer ID.
  • Step 504 The PC F obtains an A P parameter of the existing PCC rule, and determines whether the AP parameter can be used for resource allocation. If yes, step 505 is performed; otherwise, step 509 is performed.
  • the PCRF determines whether the PCC rule to be authorized is applicable to the AP parameter of the existing PCC rule according to the TFT information carried in the IP-CAN session establishment message, that is, whether the ARP parameter of the existing PCC rule can be determined. Used for resource allocation.
  • the GGSN has not previously reported the bearer ID to the PCRF. According to the re-assigned bearer ID, the PCRF still does not know that the resource needs to be allocated on the specified bearer, but the ARP parameter of the specified bearer needs to be allocated on the specified bearer.
  • Step 505 The PCRF authorizes the PCC rule according to the ARP parameter of the existing PCC rule, and the QoS of the granted rule is sent to the GGSN.
  • Step 506 The GGSN performs bearer binding according to the QoS of the authorized PCC rule.
  • the GGSN binds the authorized PCC rules and other PCC rules in the specified bearer to the specified bearer.
  • Step 507 The GGSN and the SGSN perform a secondary context tampering operation because the ARP parameter of the authorized PCC rule is the same as the ARP parameter of the existing designated bearer.
  • Step 508 The SGSN returns a Modify PDP Context Response message to the UE, and ends.
  • Step 509 The PCRF returns a failure information to the GGSN, where the failure information is used to indicate that the UE initiates a resource allocation request on the new bearer.
  • the failure information may carry the cause value.
  • Step 510 The GGSN returns the failure information to the SGSN, and the SGSN returns a ⁇ ⁇ tampering PDP context failure message carrying the failure information to the UE, and ends.
  • the GGSN after receiving the resource allocation request message (specifically, the tampering PDP context request message in this embodiment), the GGSN sends the existing PCC rule in the specified bearer to the PCRF, and the PCRP determines that the ARP parameter of the specified bearer can be For resource allocation, the PCRF authorizes the PCC rule according to the ARP parameters of the existing PCC rule, and the GGSN performs bearer binding according to the QoS of the authorized PCC rule.
  • the PCR can be used to obtain the ARP information of the specified bearer, so that the GGSN can bind the PCR-authorized PCC rule to the specified bearer, so that the UE successfully allocates the resource on the designated bearer. Source.
  • the PCRF may return a failure information for indicating that the UE initiates a resource allocation request on the new bearer.
  • FIG. 6 is a flowchart of Embodiment 6 of a policy and charging control rule authorization method provided by the present invention.
  • This embodiment is applicable to the SAE network of 3GPP R8, where the UE is a hybrid mode terminal capable of supporting both 2G and 3G, and the UE connects to the SGW and the PGW through the interface between the 3GPP anchor and the S4 SGSN (S4-SGSN).
  • the interface between the SGW and the PGW is S5, and the protocol of the S5 interface is Proxy Mobile Internet Protocol (PMIP).
  • the PCEF is specifically an SGW.
  • This embodiment is specifically a processing procedure for initiating a TFT adding operation on a PDP connection established by the UE on the network side.
  • the embodiment specifically includes the following steps:
  • Step 601 The UE sends a modify PDP context request message to the S4-SGSN, where the purpose is to add a TFT and perform a corresponding QoS operation on the PDP connection established on the network side.
  • Step 602 The S4-SGSN converts the modified PDP context request message into a resource allocation request message, which is specifically a bearer resource command, and sends the message to the SGW.
  • the bearer resource command carries the information such as the TFT, the QoS, and the bearer ID.
  • the bearer ID is the identifier of the PDP connection established on the network side.
  • Step 603 The SGW receives the bearer resource command, and according to the bearer ID carried in the bearer resource command, learns that the resource needs to be allocated on the designated bearer corresponding to the bearer ID.
  • the SGW sends a gateway control and QoS policy rule request message to the PCRF, where the gateway control and QoS are performed.
  • the policy rule request message carries the ARP parameters of the specified bearer.
  • the designated bearer in this embodiment is a PDP connection established on the network side.
  • Step 604 The PCRF determines whether the ARP parameter of the specified bearer can be used for resource allocation. If yes, step 605 is performed; otherwise, step 609 is performed.
  • the PCRF determines whether the ARP parameter of the specified bearer is applicable to the PCC rule that needs to be authorized, that is, whether the ARP parameter of the specified bearer can be used for resource allocation.
  • Step 605 The PCRF authorizes the PCC rule according to the ARP parameter of the specified bearer.
  • the ARP parameter of the authorized PCC rule is the same as the ARP parameter of the specified bearer, and the QoS of the authorized PCC rule is sent to the SGW.
  • Step 606 The SGW performs bearer binding according to the QoS of the authorized PCC rule.
  • the SGW binds the authorized PCC rules and other PCC rules in the specified bearer to the specified bearer.
  • Step 607 The AGW parameter of the authorized PCC rule is the same as the ARP parameter of the existing designated bearer, so the SGW and the S4-SGSN perform a dedicated bearer modification operation.
  • Step 608 The S4-SGSN returns a Modify PDP Context Response message to the UE, and ends.
  • Step 609 The PCRF returns a failure information to the SGW, where the failure information is used to indicate that the UE initiates a resource allocation request on the new bearer.
  • the failure information may carry a cause value.
  • Step 610 The SGW returns the failure information to the S4-SGSN, and the S4-SGSN returns a tampering PDP context failure message carrying the failure information to the UE, and ends.
  • the gateway control and QoS policy rule request message in the foregoing step 603 may also carry the existing PCC rule in the specified bearer.
  • Step 604 may be: The PCRF obtains the ARP parameter of the existing PCC rule, and determines The ARP parameter can be used for resource allocation.
  • Step 605 can be: The PCRF authorizes the PCC rule according to the ARP parameter of the existing PCC rule, and the ARP parameter of the authorized PCC rule is the same as the ARP parameter of the existing PCC rule, and the authorization is authorized.
  • the QoS of the PCC rules is sent to the SGW.
  • the SGW after receiving the resource allocation request message, the SGW sends an ARP message of the specified bearer to the PCRF.
  • the PCRF determines that the ARP parameter of the specified bearer can be used for resource allocation
  • the PCRF authorizes the PCC rule according to the ARP parameter
  • the SGW The QoS of the authorized PCC rule carries the bearer binding.
  • the PCRF can learn the ARP information of the specified bearer, so that the SGW can bind the PCC rule authorized by the PCRF to the designated bearer, so that the UE successfully allocates the resource on the designated bearer.
  • the PCRF may return a failure information, indicating that the UE initiates a resource allocation request on the new bearer.
  • FIG. 7 is a schematic structural diagram of an embodiment of a policy and charging rule execution apparatus according to the present invention. This embodiment may be specifically a PCEF.
  • the embodiment specifically includes: a first receiving module 11, a sending module 12, a second receiving module 13, and a binding module 14.
  • the first receiving module 11 is configured to receive a resource allocation request message, where the resource allocation request message indicates that the resource is allocated on the designated bearer, and the sending module 12 is configured to send, by the PCRF, the resource allocation request message received by the first receiving module 11 Specifying the ARP information of the bearer;
  • the second receiving module 13 is configured to receive the QoS of the PCC rule authorized by the PCR according to the ARP information of the specified bearer sent by the sending module 12;
  • the binding module 14 is configured to use the second receiving module according to the second receiving module 13 receives the QoS of the authorized PCC rule for bearer binding.
  • the ARP information of the specified bearer may be specifically the ARP parameter of the specified bearer or the existing PCC rule in the specified bearer.
  • the second receiving module 13 is configured to: when the PCRF determines that the ARP parameter of the specified bearer sent by the sending module 12 or the ARP parameter of the existing PCC rule can be used for resource allocation, the receiving PCRF receives the ARP information according to the specified bearer. QoS for authorized PCC rules.
  • the embodiment may further include a third receiving module 15 configured to receive, when the PCRF determines that the ARP parameter of the specified bearer sent by the sending module 12 or the ARP parameter of the existing PCC rule cannot be used for resource allocation.
  • the returned failure information is used to indicate that the UE initiates a resource allocation request on the new bearer.
  • the PCEF provided by the embodiment After receiving the resource allocation request message, the PCEF provided by the embodiment sends the specified ARP information to the PCRF.
  • the PCRF authorizes the PCC rule according to the ARP information of the specified bearer, and the PCEF performs bearer binding according to the QoS of the authorized PCC rule.
  • the PCRF can learn the ARP information of the specified bearer, so that the PCEF can bind the PCC rule authorized by the PCRF to the designated bearer, so that the UE successfully allocates the resource on the designated bearer.
  • FIG. 8 is a schematic structural diagram of an embodiment of a policy and charging rule authorization apparatus according to the present invention. This embodiment may be specifically a PCRF.
  • the embodiment specifically includes a receiving module 21 and a first sending module 22.
  • the receiving module 21 is configured to receive ARP information of the specified bearer sent by the PCEF according to the received resource allocation request message, where the resource allocation request message indicates that the resource is allocated on the designated bearer, and the first sending module 22 is configured to send the The QoS of the PCC rule authorized by the ARP information of the specified bearer received by the receiving module 21.
  • the ARP information of the specified bearer may be specifically the ARP parameter of the specified bearer or the existing PCC rule in the specified bearer.
  • the embodiment may further include a determining module 23, configured to determine whether the ARP parameter of the specified bearer received by the receiving module 21 or the ARP parameter of the existing PCC rule can be used for resource allocation.
  • the first sending module 22 is specifically configured to: when the determining module 23 determines that the ARP parameter of the specified bearer or the ARP parameter of the existing PCC rule can be used for resource allocation, send the ARP information authorization according to the specified bearer received by the receiving module 21 to the PCEF.
  • QoS for PCC rules for The PCEF performs bearer binding according to the QoS of the authorized PCC rule.
  • the embodiment may further include a second sending module 24, where the second sending module 24 is configured to determine that the ARP parameter of the specified bearer received by the receiving module 21 or the ARP parameter of the existing PCC rule cannot be used for the resource.
  • a failure message is sent to the PCEF, which is used to indicate that the UE initiates a resource allocation request on the new bearer.
  • the PC F receives the ARP information of the specified bearer sent by the PCEF according to the received resource allocation request message, and sends the QoS of the PCC rule authorized according to the ARP information of the specified bearer to the PCEF, so that the PCEF can be based on the authorized PCC rule.
  • the QoS carries the bearer binding.
  • the PCRF can learn the ARP information of the specified bearer, so that the PCEF can bind the PCC rule authorized by the PCRF to the designated bearer, so that the UE successfully allocates the resource on the designated bearer.
  • FIG. 9 is a schematic structural diagram of an embodiment of a policy and charging control rule authorization system according to the present invention. As shown in FIG. 9, the embodiment specifically includes a policy and charging rule execution device 31 and a policy and charging rule authorizing device 32.
  • the policy and charging rule execution apparatus 31 is configured to receive a resource allocation request message, where the resource allocation request message indicates that the resource is allocated on the designated bearer, and sends the ARP information of the specified bearer to the policy and charging rule authorizing device 32;
  • the receiving policy and charging rule authorizing means 32 performs bearer binding according to the QoS of the PCC rule authorized by the ARP information of the specified bearer according to the QoS of the authorized PCC rule.
  • the policy and charging rule authorization device 32 is configured to receive ARP information of the specified bearer sent by the policy and charging executing device 31 according to the received resource allocation request message, where the resource allocation request message indicates that resources are allocated on the designated bearer;
  • the QoS of the PCC rule authorized according to the ARP information of the specified bearer is transmitted to the policy and charging executing device 31 for the policy and charging executing device 31 to perform bearer binding according to the QoS of the authorized PCC rule.
  • the policy and charging rule execution device after receiving the resource allocation request message, sends the ARP information of the specified bearer to the policy and charging rule authorizing device, and the policy and charging rule authorizing device authorizes the PCC according to the ARP information of the specified bearer.
  • the rule, policy, and charging rule execution device performs bearer binding according to the QoS of the authorized PCC rule.
  • Policy and charging rules authorizing devices are able to learn to specify The bearer ARP information enables the policy and charging rule execution device to bind the PCC rule authorized by the policy and charging rule authorization device to the designated bearer, so that the UE successfully allocates the resource on the designated bearer.
  • the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed.
  • the steps of the foregoing method embodiments are included, and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

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

Description

策略和计费控制规则授权方法、 装置及系统
本申请要求于 2009 年 8 月 11 日提交中国专利局、 申请号为 200910091177.6, 发明名称为 "策略和计费控制规则授权方法、 装置及系统" 的中国专利申请的优先权， 其全部内容通过引用结合在本申请中。
技术领域
本发明实施例涉及通信技术领域，尤其涉及一种策略和计费控制规则授权 方法、 装置及系统。
背景技术
在第三代合作伙伴计划（ 3GPP )R8的策略和计费控制（ Policy and Charging Control, 简称： PCC )技术中， 引入了分配以及保留优先级（ Allocation and Retention Priority , 筒称： ARP ) 参数， 并使用服务质量类标 （QoS Class Identification, 简称： QCI )和 ARP参数进行承载绑定， 即保证同一个承载上 的所有 PCC规则的 QCI和 ARP参数相同。
当用户设备（User Equipment, 筒称： UE )在 2G/3G接入， 并支持混合控 制模式时，UE可以在网络侧发起的二次上下文上进行业务流模板（ Traffic Flow Template, 简称： TFT )添加操作以及对应的服务质量（ Quality of Service, 简 称： QoS )操作；通用分组无线业务（ General Packet Radio Service,筒称： GPRS ) 月良务支持节点 （Service GPRS Support Node, 简称： SGSN )将其转化成资源 分配请求消息发送给服务网关（Service Gateway, 简称： SGW ), 该资源分配 请求消息中携带 TFT和 QoS信息， 同时还携带承载标识（Bearer ID ), 用于指 明该资源需要在指定承载上建立； SGW将资源分配请求消息转发给分组数据 网络网关（ Packet Data Network Gateway, 简称 PGW ); PGW向策略和计费规 则功能实体（ Policy Control and Charging Rules Function, 筒称： PCRF )发起 因特网协议连接接入网络（ Internet Protocol Connectivity Access Network,简称： IP-CAN )会话爹改消息； PCRF接收到 IP-CAN会话爹改消息后， 生成新的 PCC规则， 同时生成与新的 PCC规则对应的 ARP参数和 QCI, 由于 PCRF不 能获知承载 ID, 也不能获知承载 ID对应的承载上现有的 PCC规则， 所以生 成的 ARP参数可能和承载 ID对应的承载上其他 PCC规则的 ARP参数不同。 如果 PCRF下发的 PCC规则的 ARP参数和现有承载上的 ARP参数不一致， 根据 R8中关于 PCC的规定， PGW无法将 ARP参数不同的 PCC规则绑定到 同一个承载上， 导致 UE在指定承载上资源分配请求失败。 发明内容
本发明实施例提供了一种策略和计费控制规则授权方法、 装置及系统 , 能使 UE在指定承载上成功分配到资源。
本发明实施例提供了一种策略和计费控制规则授权方法 , 包括： 接收资源分配请求消息，所述资源分配请求消息指明了在指定承载上分配 资源；
向策略和计费规则功能实体 PCRF发送所述指定承载的分配以及保留优 先级 ARP信息；
接收所述 PCRF根据所述指定承载的 ARP信息授权的策略和计费控制 PCC规则的服务质量 QoS, 根据所述授权的 PCC规则的 QoS进行承载绑定。
本发明实施例提供了一种策略和计费规则执行装置 , 包括：
第一接收模块， 用于接收资源分配请求消息， 所述资源分配请求消息指明 了在指定承载上分配资源；
发送模块，用于向策略和计费规则功能实体 PCRF发送所述第一接收模块 接收的资源分配请求消息指明的指定承载的分配以及保留优先级 ARP信息； 第二接收模块，用于接收所述 PCRF根据所述发送模块发送的指定承载的 ARP信息授权的策略和计费控制 PCC规则的服务质量 QoS;
绑定模块，用于根据所述第二接收模块接收的所述授权的 PCC规则的 QoS 进行承载绑定。
本发明实施例提供了一种策略和计费规则授权装置， 包括：
接收模块，用于接收策略和计费执行实体 PCEF根据接收到的资源分配请 求消息发送的指定承载的分配以及保留优先级 ARP信息， 所述资源分配请求 消息指明了在指定承载上分配资源；
第一发送模块，用于向所述 PCEF发送根据所述接收模块接收的指定承载 的 ARP信息授权的策略和计费控制 PCC规则的服务质量 QoS。
本发明实施例提供了一种策略和计费控制规则授权系统， 包括上述策略 和计费规则执行装置和策略和计费规则授权装置。 本发明实施例中，接收到资源分配请求消息后， 向 PCRF发送指定承载的 ARP信息， 并根据 PCRF根据指定承载的 ARP信息授权的 PCC规则的 QoS 进行承载绑定。 PCRF能够获知指定承载的 ARP信息， 使得本发明实施例能 够将 PCRF授权的 PCC规则绑定到指定承载上， 从而使得 UE在指定承载上 成功分配到资源。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施 例或现有技术描述中所需要使用的附图作筒单地介绍， 显而易见地， 下面描述 中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付 出创造性劳动的前提下， 还可以根据这些附图获得其他的实施方式。
图 1为本发明提供的策略和计费控制规则授权方法实施例一的流程图； 图 2为本发明提供的策略和计费控制规则授权方法实施例二的流程图； 图 3为本发明提供的策略和计费控制规则授权方法实施例三的流程图； 图 4为本发明提供的策略和计费控制规则授权方法实施例四的流程图； 图 5为本发明提供的策略和计费控制规则授权方法实施例五的流程图； 图 6为本发明提供的策略和计费控制规则授权方法实施例六的流程图； 图 7为本发明提供的策略和计费规则执行装置一实施例的结构示意图； 图 8为本发明提供的策略和计费规则授权装置一实施例的结构示意图； 图 9 为本发明提供的策略和计费控制规则授权系统一实施例的结构示意 图。
具体实施方式
下面通过附图和实施例， 对本发明实施例的技术方案做进一步的详细描 述。
图 1为本发明提供的策略和计费控制规则授权方法实施例一的流程图。如 图 1所示， 本实施例具体包括如下步驟：
步骤 101、 接收资源分配请求消息， 该资源分配请求消息指明了在指定承 载上分配资源；
其中， 指定承载为一已建立承载， 混合模式 UE在已建立承载上发起资源 分配请求消息， 策略和计费执行功能实体（Policy and Charging Enforcement Function, 简称： PCEF )接收该资源分配请求消息， 该资源分配请求消息指明 了在指定承载上分配资源。
步骤 102、 向 PC F发送指定承载的 A P信息；
PCEF根据资源分配请求消息获知需要在指定承载上进行操作，则向 PCRF 发送指定承载的 ARP信息。 该指定承载的 ARP信息为与指定承载的 ARP参 数相关的信息， 它可以具体为指定承载的 A P参数本身， 也可以为指定承载 中现有的 PCC规则。
步驟 103、接收 PCRF根据指定承载的 ARP信息授权的 PCC规则的 QoS, 根据授权的 PCC规则的 QoS进行承载绑定。
PCRF根据指定承载的 ARP信息授权 PCC规则 ,将该授权的 PCC规则的
QoS发送给 PCEF, PCEF根据授权的 PCC规则的 QoS进行承载绑定。
本实施例中， PCEF接收到资源分配请求消息后， 向 PCRF发送指定承载 的 ARP信息 , PCRF根据指定承载的 ARP信息授权 PCC规则 , PCEF根据该 授权的 PCC规则的 QoS进行承载绑定。 PCRF能够获知指定承载的 ARP信息， 使得 PCEF能够将 PCRF授权的 PCC规则绑定到指定承载上， 从而使得 UE 在指定承载上成功分配到资源。
图 2为本发明提供的策略和计费控制规则授权方法实施例二的流程图。本 实施例适用于 3GPP R8的系统架构演进 ( System Architecture Evolution, 简称： SAE ) 网络， 其中 UE为既能支持 2G又能支持 3G的混合模式终端， PCEF具 体为 PGW, UE通过与 3GPP锚点间的接口为 S4的 SGSN ( S4-SGSN )连接 到 SGW和 PGW, SGW和 PGW之间为 S5接口， S5接口的协议为 GPRS隧 道协议 ( GPRS Tunneling Protocol , 简称： GTP )。 本实施例具体为 UE在网络 侧建立的分组数据协议（Packet Data Protocol, 筒称： PDP )连接上发起 TFT 添加操作的处理流程。
如图 2所示， 本实施例具体包括如下步驟：
步驟 201、 UE向 S4-SGSN发送修改 PDP上下文请求消息，其目的为在网 络侧建立的 PDP连接上添加 TFT及执行对应 QoS操作。
步驟 202、 S4-SGSN将修改 PDP上下文请求消息转化为资源分配请求消 息， 具体为承载资源命令（Bearer Resource Command ), 发送给 SGW。 该承载资源命令中携带了 TFT、 QoS和承载 ID等信息， 其中承载 ID即 为网络侧建立的 PDP连接的标识。
步骤 203、 SGW将承载资源命令转发给 PGW。
步驟 204、 PGW接收到承载资源命令， 根据承载资源命令中携带的承载 ID获知需要在承载 ID对应的指定承载上分配资源； PGW向 PCRF发送 IP-CAN 会话修改消息， 该 IP-CAN会话修改消息中携带了指定承载的 ARP参数。
本实施例的指定承载即为网络侧建立的 PDP连接。 IP-CAN会话修改消息 中除了携带指定承载的 ARP参数， 还可以携带 TFT和 QoS等信息。
步驟 205、 PCRF判断指定承载的 ARP参数是否能够用于资源分配，若是， 则执行步驟 206; 否则执行步驟 210。
具体地， PCRF结合业务情况， 根据 IP-CAN会话修改消息中携带的 TFT 信息判断需要授权的 PCC规则是否适用该指定承载的 ARP参数，即判断 ARP 参数是否能够用于资源分配。
步驟 206、 PCRF根据指定承载的 ARP参数授权 PCC规则 ,该授权的 PCC 规则的 ARP参数与指定承载的 ARP参数相同 , 将授权的 PCC规则的 QoS发 送给 PGW。
步驟 207、 PGW根据授权的 PCC规则的 QoS进行承载绑定。
PGW将授权的 PCC规则和指定承载中其他 PCC规则绑定到指定承载上。 步驟 208、 由于授权的 PCC规则的 ARP参数与现有的指定承载的 ARP 参数相同， 所以 PGW、 SGW和 S4-SGSN进行专有承载修改操作。
步驟 209、 S4-SGSN向 UE返回修改 PDP上下文响应消息， 结束。
步驟 210、 PCRF向 PGW返回失败信息， 该失败信息用于指明 UE在新的 承载上发起资源分配请求， 可选地， 该失败信息中可以携带原因值。
步驟 211、 PGW通过 SGW将失败信息返回给 S4-SGSN, S4-SGSN向 UE 返回携带该失败信息的修改 PDP上下文失败消息， 结束。
本实施例中， PGW接收到资源分配请求消息后， 向 PCRF发送指定承载 的 ARP参数，当 PCRF判断出指定承载的 ARP参数能够用于资源分配时 , PCRF 根据指定承载的 ARP参数授权 PCC规则， PGW根据该授权的 PCC规则的 QoS进行承载绑定。 PCRF能够获知指定承载的 ARP信息， 使得 PGW能够将 PCRF授权的 PCC规则绑定到指定承载上，从而使得 UE在指定承载上成功分 配到资源。当 PCRF判断出指定承载的 ARP参数不能够用于资源分配时， PCRF 可以返回失败信息， 用于指明 UE在新的承载上发起资源分配请求。
图 3为本发明提供的策略和计费控制规则授权方法实施例三的流程图。本 实施例所适用的场景与上述实施例二相同， 不同之处在于： 本实施例中 PGW 获知需要在指定承载上分配资源时， 向 PCRF发送指定承载中现有的 PCC规 贝' J , PCRF在授权 PCC规则时， 考虑现有的 PCC规则的 ARP参数。 具体说明 如下。
如图 3所示， 本实施例具体包括如下步驟：
步驟 301、 UE向 S4-SGSN发送修改 PDP上下文请求消息，其目的为在网 络侧建立的 PDP上添加 TFT及执行对应 QoS操作。
步驟 302、 S4-SGSN将修改 PDP上下文请求消息转化为资源分配请求消 息， 具体为承载资源命令， 发送给 SGW。
该承载资源命令中携带了 TFT、 QoS和承载 ID等信息， 其中承载 ID即 为网络侧建立的 PDP连接的标识。
步驟 303、 SGW将承载资源命令转发给 PGW。
步驟 304、 PGW接收到承载资源命令， 根据承载资源命令中携带的承载 ID获知需要在承载 ID对应的指定承载上分配资源； PGW向 PCRF发送 IP-CAN 会话修改消息 , 该 IP-CAN会话修改消息中携带了指定承载中现有的 PCC规 则。
本实施例的指定承载即为网络侧建立的 PDP连接。 IP-CAN会话修改消息 中除了携带现有的 PCC规则 , 还可以携带 TFT和 QoS等信息。
步驟 305、 PCRF获取现有的 PCC规则的 ARP参数， 判断该 ARP参数是 否能够用于资源分配， 若是， 则执行步驟 306; 否则执行步驟 310。
具体地， PCRF结合业务情况， 根据 IP-CAN会话修改消息中携带的 TFT 信息判断需要授权的 PCC规则是否适用该现有的 PCC规则的 ARP参数， 即 判断现有的 PCC规则的 ARP参数是否能够用于资源分配。
步驟 306、 PCR 根据现有的 PCC规则的 ARP参数授权 PCC规则， 该授 权的 PCC规则的 ARP参数与现有的 PCC规则的 ARP参数相同，将授权的 PCC 规则的 QoS发送给 PGW。
步驟 307、 PGW根据授权的 PCC规则的 QoS进行承载绑定。
PGW将授权的 PCC规则和指定承载中现有的 PCC规则绑定到指定承载 上。
步驟 308、 由于授权的 PCC规则的 ARP参数与现有的指定承载的 ARP 参数相同， 所以 PGW、 SGW和 S4-SGSN进行专有 载爹改操作。
步驟 309、 S4-SGSN向 UE返回修改 PDP上下文响应消息， 结束。
步驟 310、 PCRF向 PGW返回失败信息， 该失败信息用于指明 UE在新的 承载上发起资源分配请求， 可选地， 该失败信息中可以携带原因值。
步驟 311、 PGW通过 SGW将失败信息返回给 S4-SGSN, S4-SGSN向 UE 返回携带该失败信息的修改 PDP上下文失败消息， 结束。
本实施例中， PGW接收到资源分配请求消息后， 向 PCRF发送指定承载 中现有的 PCC规则 , 当 PCRF判断出指定承载的 ARP参数能够用于资源分配 时， PCRF根据现有的 PCC规则的 ARP参数授权 PCC规则， PGW根据该授 权的 PCC规则的 QoS进行承载绑定。 PCRF能够获知指定承载的 ARP信息， 使得 PGW能够将 PCRF授权的 PCC规则绑定到指定承载上，从而使得 UE在 指定承载上成功分配到资源。 当 PCRF判断出指定承载的 ARP参数不能够用 于资源分配时， PCRF可以返回失败信息， 用于指明 UE在新的承载上发起资 源分配请求。
图 4为本发明提供的策略和计费控制规则授权方法实施例四的流程图。本 实施例适用于 3GPP R8的 GPRS网络， 其中 UE为既能支持 2G又能支持 3G 的混合模式终端， PCEF具体为 GPRS网关支持节点 （Gateway GPRS Support Node, 筒称： GGSN ), UE通过 SGSN连接到 GGSN。 本实施例具体为 UE在 网络侧建立的 PDP连接上发起 TFT添加操作的处理流程 , 修改上下文请求消 息具体为修改 PDP上下文请求消息。
如图 4所示， 本实施例具体包括如下步骤：
步驟 401、 UE向 SGSN发送修改 PDP上下文请求消息， 其目的为在网络 侧建立的 PDP上添加 TFT及执行对应 QoS操作。
步驟 402、 SGSN将修改 PDP上下文请求消息发送给 GGSN。 该修改 PDP上下文请求消息中携带了 TFT 、 QoS和 PDP上下文 ID ( PDP Context ID )等信息，其中 PDP上下文 ID即为网络侧建立的 PDP连接的标识， 该 PDP上下文 ID指明了该爹改 PDP上下文请求消息请求在指定 7|载上分配 资源。
步驟 403、 GGSN接收到修改 PDP上下文请求消息后 , GGSN向 PCRF发 送 IP-CAN会话建立消息，该 IP-CAN会话建立消息中携带了指定承载的 ARP 参数。 中， GGSN会执行一个 IP-CAN承载建立的操作， GGSN重新分配承载 ID。
本实施例的指定承载即为网络侧建立的 PDP连接。 IP-CAN会话建立消息 中除了携带指定承载的 ARP参数， 还可以携带 TFT、 QoS和重新分配的承载 ID等信息。
步驟 404、 PCRF判断指定承载的 ARP参数是否能够用于资源分配，若是， 则执行步驟 405; 否则执行步驟 409。
具体地， PCRF结合业务情况， 根据 IP-CAN会话建立消息中携带的 TFT 信息判断需要授权的 PCC规则是否适用该指定承载的 ARP参数， 即判断指定 承载的 ARP参数是否能够用于资源分配。
由于 GGSN之前没有向 PCRF上报过承载 ID,根据该重新分配的承载 ID, PCRF仍然不知道需要在指定承载上分配资源， 而是根据指定承载的 ARP参 数获知需要在指定承载上分配资源。
步驟 405、 PCRF根据指定承载的 ARP参数授权 PCC规则 ,该授权的 PCC 规则的 ARP参数与指定承载的 ARP参数相同 , 将授权的 PCC规则的 QoS发 送给 GGSN。
步驟 406、 GGSN根据授权的 PCC规则的 QoS进行承载绑定。
GGSN将授权的 PCC规则和指定承载中其他 PCC规则绑定到指定承载 上。
步驟 407、 由于授权的 PCC规则的 ARP参数与现有的指定承载的 ARP 参数相同 , 所以 GGSN和 SGSN进行二次上下文爹改操作。
步驟 408、 SGSN向 UE返回修改 PDP上下文响应消息， 结束。 步驟 409、 PCRF向 GGSN返回失败信息， 该失败信息用于指明 UE在新 的承载上发起资源分配请求， 可选地， 该失败信息中可以携带原因值。
步骤 410、 GGSN将失败信息返回给 SGSN, SGSN向 UE返回携带该失 败信息的^ ί'爹改 PDP上下文失败消息， 结束。
本实施例中 , GGSN接收到资源分配请求消息 （本实施例中具体为爹改
PDP上下文请求消息）后， 向 PCRF发送指定 7|载的 ARP参数， 当 PCRF判 断出指定承载的 ARP参数能够用于资源分配时， PCRF根据指定承载的 ARP 参数授权 PCC规则 , GGSN根据该授权的 PCC规则的 QoS进行承载绑定。 PCRF 能够获知指定承载的 ARP信息，使得 GGSN能够将 PCRF授权的 PCC规则绑 定到指定承载上， 从而使得 UE在指定承载上成功分配到资源。 当 PCRF判断 出指定承载的 ARP参数不能够用于资源分配时， PCRF可以返回失败信息， 用于指明 UE在新的承载上发起资源分配请求。
图 5为本发明提供的策略和计费控制规则授权方法实施例五的流程图。本 实施例所适用的场景与上述实施例四相同， 不同之处在于： 本实施例中 GGSN 获知需要在指定承载上分配资源时， 向 PCRF发送指定承载中现有的 PCC规 贝' J , PCRF在授权 PCC规则时， 考虑现有的 PCC规则的 ARP参数。 具体说明 如下。
步驟 501、 UE向 SGSN发送修改 PDP上下文请求消息， 其目的为在网络 侧建立的 PDP上添加 TFT及执行对应 QoS操作。
步驟 502、 SGSN将修改 PDP上下文请求消息发送给 GGSN。
该修改 PDP上下文请求消息中携带了 TFT、 QoS和 PDP上下文 ID等信 息， 其中 PDP上下文 ID即为网络侧建立的 PDP连接的标识， 该 PDP上下文 ID指明了该修改 PDP上下文请求消息请求在指定承载上分配资源。
步驟 503、 GGSN接收到修改 PDP上下文请求消息后， GGSN向 PCRF发 送 IP-CAN会话建立消息， 该 IP-CAN会话建立消息中携带了指定承载中现有 的 PCC规则。
本实施例适用于 GGSN之前没有向 PCRF上 ^艮过 载 ID的情况， 本步驟 中 , GGSN会执行一个 IP-CAN承载建立的操作 , GGSN重新分配承载 ID。
本实施例的指定承载即为网络侧建立的 PDP连接。 IP-CAN会话建立消息 中除了携带现有的 PCC规则，还可以携带 TFT、 QoS和重新分配的承载 ID等 信息。
步骤 504、 PC F获取现有的 PCC规则的 A P参数， 判断该 A P参数是 否能够用于资源分配， 若是， 则执行步驟 505; 否则执行步驟 509。
具体地， PCRF结合业务情况， 根据 IP-CAN会话建立消息中携带的 TFT 信息判断需要授权的 PCC规则是否适用该现有的 PCC规则的 A P参数， 即 判断现有的 PCC规则的 ARP参数是否能够用于资源分配。
由于 GGSN之前没有向 PCRF上报过承载 ID,根据该重新分配的承载 ID, PCRF仍然不知道需要在指定承载上分配资源， 而是根据指定承载的 ARP参 数获知需要在指定承载上分配资源。
步驟 505、 PCRF根据现有的 PCC规则的 ARP参数授权 PCC规则， 该授 规则的 QoS发送给 GGSN。
步驟 506、 GGSN根据授权的 PCC规则的 QoS进行承载绑定。
GGSN将授权的 PCC规则和指定承载中其他 PCC规则绑定到指定承载 上。
步驟 507、 由于授权的 PCC规则的 ARP参数与现有的指定承载的 ARP 参数相同， 所以 GGSN和 SGSN进行二次上下文爹改操作。
步驟 508、 SGSN向 UE返回修改 PDP上下文响应消息 , 结束。
步驟 509、 PCRF向 GGSN返回失败信息， 该失败信息用于指明 UE在新 的承载上发起资源分配请求， 可选地， 该失败信息中可以携带原因值。
步驟 510、 GGSN将失败信息返回给 SGSN, SGSN向 UE返回携带该失 败信息的^ ί'爹改 PDP上下文失败消息， 结束。
本实施例中， GGSN接收到资源分配请求消息 （本实施例中具体为爹改 PDP上下文请求消息）后，向 PCRF发送指定承载中现有的 PCC规则 ,当 PCRP 判断出指定承载的 ARP参数能够用于资源分配时， PCRF根据现有的 PCC规 则的 ARP参数授权 PCC规则， GGSN根据该授权的 PCC规则的 QoS进行承 载绑定。 PCR 能够获知指定承载的 ARP信息， 使得 GGSN能够将 PCR 授 权的 PCC规则绑定到指定承载上， 从而使得 UE在指定承载上成功分配到资 源。 当 PCRF判断出指定承载的 ARP参数不能够用于资源分配时， PCRF可以 返回失败信息， 用于指明 UE在新的承载上发起资源分配请求。
图 6为本发明提供的策略和计费控制规则授权方法实施例六的流程图。本 实施例适用于 3GPP R8的 SAE网络，其中 UE为既能支持 2G又能支持 3G的 混合模式终端 , UE通过与 3GPP锚点间的接口为 S4的 SGSN ( S4-SGSN )连 接到 SGW和 PGW, SGW和 PGW之间的接口为 S5 , S5接口的协议为代理移 动因特网协议（ Proxy Mobile Internet Protocol,简称： PMIP )。本实施例中 PCEF 具体为 SGW。本实施例具体为 UE在网络侧建立的 PDP连接上发起 TFT添加 操作的处理流程。
如图 6所示， 本实施例具体包括如下步驟：
步驟 601、 UE向 S4-SGSN发送修改 PDP上下文请求消息，其目的为在网 络侧建立的 PDP连接上添加 TFT及执行对应 QoS操作。
步驟 602、 S4-SGSN将修改 PDP上下文请求消息转化为资源分配请求消 息， 具体为承载资源命令， 发送给 SGW。
该承载资源命令中携带了 TFT、 QoS和承载 ID等信息， 其中承载 ID即 为网络侧建立的 PDP连接的标识。
步驟 603、 SGW接收到承载资源命令， 根据承载资源命令中携带的承载 ID获知需要在承载 ID对应的指定承载上分配资源； SGW向 PCRF发送网关 控制和 QoS策略规则请求消息， 该网关控制和 QoS策略规则请求消息中携带 了指定承载的 ARP参数。
本实施例的指定承载即为网络侧建立的 PDP连接。
步驟 604、 PCRF判断指定承载的 ARP参数是否能够用于资源分配，若是， 则执行步驟 605; 否则执行步驟 609。
具体地， PCRF结合业务情况，判断需要授权的 PCC规则是否适用该指定 承载的 ARP参数， 即判断指定承载的 ARP参数是否能够用于资源分配。
步驟 605、 PCRF根据指定承载的 ARP参数授权 PCC规则 ,该授权的 PCC 规则的 ARP参数与指定承载的 ARP参数相同 , 将授权的 PCC规则的 QoS发 送给 SGW。
步驟 606、 SGW根据授权的 PCC规则的 QoS进行承载绑定。 SGW将授权的 PCC规则和指定承载中其他 PCC规则绑定到指定承载上。 步驟 607、 由于授权的 PCC规则的 ARP参数与现有的指定承载的 ARP 参数相同， 所以 SGW和 S4-SGSN进行专有承载修改操作。
步驟 608、 S4-SGSN向 UE返回修改 PDP上下文响应消息， 结束。
步驟 609、 PCRF向 SGW返回失败信息 , 该失败信息用于指明 UE在新的 承载上发起资源分配请求， 可选地， 该失败信息中可以携带原因值。
步驟 610、 SGW将失败信息返回给 S4-SGSN, S4-SGSN向 UE返回携带 该失败信息的爹改 PDP上下文失败消息， 结束。
作为另外一种实施方式， 上述步驟 603中网关控制和 QoS策略规则请求 消息中也可以携带指定承载中现有的 PCC规则； 则步驟 604可以为： PCRF 获取现有的 PCC规则的 ARP参数， 判断该 ARP参数是否能够用于资源分配； 步驟 605可以为： PCRF根据现有的 PCC规则的 ARP参数授权 PCC规则， 该 授权的 PCC规则的 ARP参数与现有的 PCC规则的 ARP参数相同 , 将授权的 PCC规则的 QoS发送给 SGW。
本实施例中， SGW接收到资源分配请求消息后， 向 PCRF发送指定承载 的 ARP消息，当 PCRF判断出指定承载的 ARP参数能够用于资源分配时， PCRF 根据该 ARP参数授权 PCC规则， SGW根据该授权的 PCC规则的 QoS进行承 载绑定。 PCRF能够获知指定承载的 ARP信息， 使得 SGW能够将 PCRF授权 的 PCC规则绑定到指定承载上， 从而使得 UE在指定承载上成功分配到资源。 当 PCRF判断出指定承载的 ARP参数不能够用于资源分配时， PCRF可以返回 失败信息， 用于指明 UE在新的承载上发起资源分配请求。
图 7为本发明提供的策略和计费规则执行装置一实施例的结构示意图。本 实施例可以具体为 PCEF。
如图 7所示， 本实施例具体包括： 第一接收模块 11、 发送模块 12、 第二 接收模块 13和绑定模块 14。 其中， 第一接收模块 11用于接收资源分配请求 消息， 该资源分配请求消息指明了在指定承载上分配资源； 发送模块 12用于 向 PCRF 发送第一接收模块 11 接收的资源分配请求消息指明的指定承载的 ARP信息； 第二接收模块 13用于接收 PCR 根据发送模块 12发送的指定承 载的 ARP信息授权的 PCC规则的 QoS; 绑定模块 14用于根据第二接收模块 13接收的授权的 PCC规则的 QoS进行承载绑定。
上述指定承载的 ARP信息可以具体为指定承载的 ARP参数或指定承载中 现有的 PCC规则。
进一步的，上述第二接收模块 13是在 PCRF判断出发送模块 12发送的指 定承载的 ARP参数或现有的 PCC规则的 ARP参数能够用于资源分配的情况 下， 接收 PCRF根据指定承载的 ARP信息授权的 PCC规则的 QoS。 本实施例 还可以包括第三接收模块 15， 该第三接收模块 15用于接收 PCRF判断出发送 模块 12发送的指定承载的 ARP参数或现有的 PCC规则的 ARP参数不能够用 于资源分配时返回的失败信息，该失败信息用于指明 UE在新的承载上发起资 源分配请求。
本实施例提供的 PCEF接收到资源分配请求消息后， 向 PCRF发送指定承 载的 ARP信息， PCRF根据指定承载的 ARP信息授权 PCC规则 , PCEF根据 该授权的 PCC规则的 QoS进行承载绑定。 PCRF能够获知指定承载的 ARP信 息， 使得 PCEF能够将 PCRF授权的 PCC规则绑定到指定承载上， 从而使得 UE在指定承载上成功分配到资源。
图 8为本发明提供的策略和计费规则授权装置一实施例的结构示意图。本 实施例可以具体为 PCRF。
如图 8所示， 本实施例具体包括接收模块 21和第一发送模块 22。 其中， 接收模块 21用于接收 PCEF根据接收到的资源分配请求消息发送的指定承载 的 ARP信息， 该资源分配请求消息指明了在指定承载上分配资源； 第一发送 模块 22用于向 PCEF发送根据接收模块 21接收的指定承载的 ARP信息授权 的 PCC规则的 QoS。
上述指定承载的 ARP信息可以具体为指定承载的 ARP参数或指定承载中 现有的 PCC规则。
进一步的， 本实施例还可以包括判断模块 23 , 该判断模块 23用于判断接 收模块 21接收的指定承载的 ARP参数或现有的 PCC规则的 ARP参数是否能 够用于资源分配。第一发送模块 22具体用于当判断模块 23判断出指定承载的 ARP参数或现有的 PCC规则的 ARP参数能够用于资源分配时，向 PCEF发送 根据接收模块 21接收的指定承载的 ARP信息授权的 PCC规则的 QoS, 以供 PCEF根据授权的 PCC规则的 QoS进行承载绑定。
本实施例还可以包括第二发送模块 24, 该第二发送模块 24用于当判断模 块 23判断出接收模块 21接收的指定承载的 ARP参数或现有的 PCC规则的 ARP参数不能够用于资源分配时， 向 PCEF发送失败信息，该失败信息用于指 明 UE在新的承载上发起资源分配请求。
本实施例提供的 PC F接收 PCEF根据接收到的资源分配请求消息发送的 指定承载的 ARP信息，并向 PCEF发送根据指定承载的 ARP信息授权的 PCC 规则的 QoS, 以供 PCEF根据授权的 PCC规则的 QoS进行承载绑定。 PCRF 能够获知指定承载的 ARP信息， 使得 PCEF能够将 PCRF授权的 PCC规则绑 定到指定承载上， 从而使得 UE在指定承载上成功分配到资源。
图 9 为本发明提供的策略和计费控制规则授权系统一实施例的结构示意 图。 如图 9所示， 本实施例具体包括策略和计费规则执行装置 31与策略和计 费规则授权装置 32。
其中， 策略和计费规则执行装置 31用于接收资源分配请求消息， 该资源 分配请求消息指明了在指定承载上分配资源； 向策略和计费规则授权装置 32 发送指定承载的 ARP信息； 以及，接收策略和计费规则授权装置 32根据指定 承载的 ARP信息授权的 PCC规则的 QoS, 根据授权的 PCC规则的 QoS进行 承载绑定。
策略和计费规则授权装置 32用于接收策略和计费执行装置 31根据接收到 的资源分配请求消息发送的指定承载的 ARP信息， 该资源分配请求消息指明 了在指定承载上分配资源； 以及， 向策略和计费执行装置 31发送根据指定承 载的 ARP信息授权的 PCC规则的 QoS, 以供策略和计费执行装置 31根据授 权的 PCC规则的 QoS进行承载绑定。
本实施例中策略和计费规则执行装置 31 与策略和计费规则授权装置 32 的具体结构可以参见装置实施例， 在此不再赘述。
本实施例中， 策略和计费规则执行装置接收到资源分配请求消息后， 向策 略和计费规则授权装置发送指定承载的 ARP信息， 策略和计费规则授权装置 根据指定承载的 ARP信息授权 PCC规则 ,策略和计费规则执行装置根据该授 权的 PCC规则的 QoS进行承载绑定。 策略和计费规则授权装置能够获知指定 承载的 ARP信息， 使得策略和计费规则执行装置能够将策略和计费规则授权 装置授权的 PCC规则绑定到指定承载上， 从而使得 UE在指定承载上成功分 配到资源。
本领域普通技术人员可以理解：实现上述方法实施例的全部或部分步驟可 以通过程序指令相关的硬件来完成，前述的程序可以存储于一计算机可读取存 储介质中， 该程序在执行时， 执行包括上述方法实施例的步骤， 而前述的存储 介质包括： ROM、 RAM, 磁碟或者光盘等各种可以存储程序代码的介质。 对其限制； 尽管参照前述实施例对本发明实施例进行了详细的说明， 本领域的 普通技术人员应当理解： 其依然可以对前述各实施例所记载的技术方案进行修 改， 或者对其中部分技术特征进行等同替换； 而这些修改或者替换， 并不使相 应技术方案的本质脱离本发明实施例各实施例技术方案的精神和范围。

Claims

OP080844 WO 2011/018030 PCT/CN2010/075870 - 16- 权 利 要 求
1、 一种策略和计费控制规则授权方法， 其特征在于包括：
接收资源分配请求消息，所述资源分配请求消息指明了在指定承载上分配 资源；
向策略和计费规则功能实体 PCRF发送所述指定承载的分配以及保留优 先级 A P信息；
接收所述 PCRF根据所述指定承载的 ARP信息授权的策略和计费控制 PCC规则的服务质量 QoS, 根据所述授权的 PCC规则的 QoS进行承载绑定。
2、 根据权利要求 1所述的策略和计费控制规则授权方法， 其特征在于， 所述指定承载的 ARP信息具体为所述指定承载的 ARP参数或所述指定承载中 现有的 PCC规则。
3、 根据权利要求 2所述的策略和计费控制规则授权方法， 其特征在于， 所述接收 PCRF根据指定承载的 ARP信息授权的 PCC规则的 QoS包括：接收 PCRF判断出所述指定承载的 ARP参数能够用于资源分配时授权的 PCC规则 的 QoS , 所述授权的 PCC规则的 ARP参数与所述指定承载的 ARP参数相同。
4、 根据权利要求 2所述的策略和计费控制规则授权方法， 其特征在于还 包括： 接收 PCRF判断出所述指定承载的 ARP参数不能够用于资源分配时返 回的失败信息 ,所述失败信息用于指明用户终端在新的承载上发起资源分配请 求。
5、 根据权利要求 2所述的策略和计费控制规则授权方法， 其特征在于， 所述接收 PCRF根据指定承载的 ARP信息授权的 PCC规则的 QoS包括：接收 PCRF判断出所述现有的 PCC规则的 ARP参数能够用于资源分配时授权的 PCC规则的 QoS, 所述授权的 PCC规则的 ARP参数与所述现有的 PCC规则 的 ARP参数相同。
6、 根据权利要求 5所述的策略和计费控制规则授权方法， 其特征在于还 包括： 接收 PCRF判断出所述现有的 PCC规则的 ARP参数不能够用于资源分 配时返回的失败信息 ,所述失败信息用于指明用户终端在新的承载上发起资源 分配请求。
7、 根据权利要求 1所述的策略和计费控制规则授权方法， 其特征在于， OP080844
WO 2011/018030 PCT/CN2010/075870
- 17- 在系统架构演进 SAE网络中， 所述资源分配请求消息具体为承载资源命令； 在通用分组无线业务 GPRS网络中，所述资源分配请求消息具体为修改上下文 请求消息。
8、 一种策略和计费规则执行装置， 其特征在于包括：
第一接收模块， 用于接收资源分配请求消息， 所述资源分配请求消息指明 了在指定^^载上分配资源；
发送模块，用于向策略和计费规则功能实体 PCRF发送所述第一接收模块 接收的资源分配请求消息指明的指定承载的分配以及保留优先级 ARP信息； 第二接收模块，用于接收所述 PCRF根据所述发送模块发送的指定承载的 ARP信息授权的策略和计费控制 PCC规则的服务质量 QoS;
绑定模块，用于根据所述第二接收模块接收的所述授权的 PCC规则的 QoS 进行承载绑定。
9、 根据权利要求 8所述的策略和计费规则执行装置， 其特征在于， 所述 指定承载的 ARP信息具体为所述指定承载的 ARP参数或所述指定承载中现有 的 PCC规则。
10、根据权利要求 9所述的策略和计费规则执行装置，其特征在于还包括： 第三接收模块， 用于接收所述 PCRF 判断出所述发送模块发送的指定承载的 ARP参数或所述现有的 PCC规则的 ARP参数不能够用于资源分配时返回的失 败信息， 所述失败信息用于指明用户终端在新的承载上发起资源分配请求。
11、 一种策略和计费规则授权装置， 其特征在于包括：
接收模块，用于接收策略和计费执行实体 PCEF根据接收到的资源分配请 求消息发送的指定承载的分配以及保留优先级 ARP信息， 所述资源分配请求 消息指明了在指定承载上分配资源；
第一发送模块，用于向所述 PCEF发送根据所述接收模块接收的指定承载 的 ARP信息授权的策略和计费控制 PCC规则的服务质量 QoS。
12、 根据权利要求 11所述的策略和计费规则授权装置， 其特征在于， 所 述指定承载的 ARP信息具体为所述指定承载的 ARP参数或所述指定承载中现 有的 PCC规则。
13、 根据权利要求 12所述的策略和计费规则授权装置， 其特征在于还包 OP080844
WO 2011/018030 PCT/CN2010/075870
- 18- 括： 判断模块， 用于判断所述接收模块接收的指定承载的 ARP参数或所述现 有的 PCC规则的 ARP参数是否能够用于资源分配；
所述第一发送模块具体用于当所述判断模块判断出所述指定承载的 A P 参数或所述现有的 PCC规则的 ARP参数能够用于资源分配时， 向所述 PCEF 发送根据所述接收模块接收的指定承载的 ARP信息授权的策略和计费控制 PCC规则的 QoS。
14、 根据权利要求 13所述的策略和计费规则授权装置， 其特征在于还包 括： 第二发送模块， 用于当所述判断模块判断出所述指定承载的 ARP参数或 所述现有的 PCC规则的 ARP参数不能够用于资源分配时， 向所述 PCEF发送 失败信息， 所述失败信息用于指明用户终端在新的承载上发起资源分配请求。
15、 一种策略和计费控制规则授权系统， 其特征在于包括： 权利要求 8 或 9或 10所述的策略和计费规则执行装置与权利要求 11至 14任一权利要求 所述的策略和计费规则授权装置。
PCT/CN2010/075870 2009-08-11 2010-08-11 策略和计费控制规则授权方法、装置及系统 WO2011018030A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP10807975.7A EP2458809B1 (en) 2009-08-11 2010-08-11 Method, apparatus and system for authorizing policy and charging control rules
US13/370,798 US8958322B2 (en) 2009-08-11 2012-02-10 Method, apparatus and system for authorizing policy and charging control rule

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910091177.6 2009-08-11
CN2009100911776A CN101998531B (zh) 2009-08-11 2009-08-11 策略和计费控制规则授权方法、装置及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/370,798 Continuation US8958322B2 (en) 2009-08-11 2012-02-10 Method, apparatus and system for authorizing policy and charging control rule

Publications (1)

Publication Number Publication Date
WO2011018030A1 true WO2011018030A1 (zh) 2011-02-17

Family

ID=43585961

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/075870 WO2011018030A1 (zh) 2009-08-11 2010-08-11 策略和计费控制规则授权方法、装置及系统

Country Status (4)

Country Link
US (1) US8958322B2 (zh)
EP (1) EP2458809B1 (zh)
CN (1) CN101998531B (zh)
WO (1) WO2011018030A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8958322B2 (en) 2009-08-11 2015-02-17 Huawei Technologies Co., Ltd. Method, apparatus and system for authorizing policy and charging control rule

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110282981A1 (en) * 2010-05-11 2011-11-17 Alcatel-Lucent Canada Inc. Behavioral rule results
WO2012167546A1 (zh) * 2011-11-11 2012-12-13 华为技术有限公司 业务分发控制方法和设备
CN103248451B (zh) 2012-02-09 2016-12-07 华为技术有限公司 业务速率控制方法和系统以及设备
JP6163204B2 (ja) 2012-06-14 2017-07-12 テケレック・インコーポレイテッドＴｅｋｅｌｅｃ， Ｉｎｃ． ポリシーおよび課金ルール機能（ｐｃｒｆ）に統合型オープンフローコントローラを提供するための方法、システム、およびコンピュータ読取可能媒体
EP2904749A1 (en) * 2012-10-04 2015-08-12 Telefonaktiebolaget L M Ericsson (Publ) Network resource modification
KR20140045215A (ko) * 2012-10-08 2014-04-16 삼성전자주식회사 그룹 기반 연결 설정 방법 및 장치
US9537904B2 (en) * 2013-01-24 2017-01-03 Tekelec, Inc. Methods, systems, and computer readable media for using policy knowledge of or obtained by a policy and charging rules function (PCRF) for needs based forwarding of bearer session traffic to network nodes
WO2014127347A1 (en) 2013-02-18 2014-08-21 Tekelec, Inc. Methods, systems, and computer readable media for providing a virtualized diameter network architecture and for routing traffic to dynamically instantiated diameter resource instances
US9369390B2 (en) 2013-02-18 2016-06-14 Tekelec, Inc. Methods, systems, and computer readable media for providing a thinking diameter network architecture
WO2014190517A1 (zh) * 2013-05-30 2014-12-04 华为技术有限公司 基于无线通信网络的数据传输控制方法及装置
US9391897B2 (en) 2013-07-31 2016-07-12 Oracle International Corporation Methods, systems, and computer readable media for mitigating traffic storms
US10206137B2 (en) * 2013-09-05 2019-02-12 Nec Corporation Communication apparatus, control apparatus, communication system, communication method, control method, and program
US11388082B2 (en) 2013-11-27 2022-07-12 Oracle International Corporation Methods, systems, and computer readable media for diameter routing using software defined network (SDN) functionality
CN104754657A (zh) * 2013-12-30 2015-07-01 中兴通讯股份有限公司 策略控制方法、策略执行以及下发装置
US9191265B1 (en) * 2014-02-07 2015-11-17 Sprint Communications Company L.P. Internet multimedia subsystem (IMS) bypass of a long term evolution (LTE) policy, charging, and rules function (PCRF)
US10148509B2 (en) 2015-05-13 2018-12-04 Oracle International Corporation Methods, systems, and computer readable media for session based software defined networking (SDN) management
CN107634838A (zh) * 2016-07-18 2018-01-26 中兴通讯股份有限公司 策略控制方法、装置及系统
CN106454201B (zh) * 2016-09-13 2020-04-24 国网天津市电力公司 一种基于ims网络的视频会议接入服务质量保证方法
CN110972198B (zh) * 2018-09-30 2023-10-10 中兴通讯股份有限公司 业务控制方法、网络设备、及存储介质
US11139852B2 (en) * 2019-07-04 2021-10-05 Nortac Defence Limited Situational awareness over a low bandwidth short burst data satellite system
US11133945B2 (en) * 2019-07-16 2021-09-28 T-Mobile Usa, Inc. Online charging of ro fail-open sessions

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101188504A (zh) * 2006-11-20 2008-05-28 华为技术有限公司 一种网络融合策略计费控制架构的系统及处理方法
CN101222413A (zh) * 2007-01-09 2008-07-16 华为技术有限公司 业务流程中的处理方法及系统
CN101272256A (zh) * 2007-03-23 2008-09-24 华为技术有限公司 业务处理方法和系统、策略控制和计费规则功能实体
CN101374260A (zh) * 2007-08-22 2009-02-25 华为技术有限公司 Pcc规则和承载关联的实现方法、装置和系统

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7263087B2 (en) * 2002-01-25 2007-08-28 Nokia Corporation Method and system for adding IP routes to a routing mobile terminal with 3G messages
EP2005661B1 (en) * 2006-04-06 2009-12-02 Telefonaktiebolaget LM Ericsson (publ) System, arrangements and method relating to access handling
US7787426B2 (en) * 2006-11-10 2010-08-31 Powerwave Cognition, Inc. Adaptive control channel initialization operations for autonomous dynamic spectrum access systems
WO2008061477A1 (fr) 2006-11-20 2008-05-29 Huawei Technologies Co., Ltd. Système et procédé de commande de facturation d'une structure de commande de facturation de politique de fusion de réseau
CN101094236B (zh) 2007-07-20 2011-08-10 华为技术有限公司 地址解析协议报文处理方法及通讯系统及转发平面处理器
US8422373B2 (en) * 2008-01-17 2013-04-16 Nokia Corporation Adaptive multi-rate codec bit rate control in a wireless system
WO2009128755A1 (en) * 2008-04-18 2009-10-22 Telefonaktiebolaget L M Ericsson (Publ) Optimizing the usage of radio resources by cross-layer reading of information from higher level control plane protocol layer
ES2422590T3 (es) * 2008-11-03 2013-09-12 Nokia Siemens Networks Oy Control de cobro que proporciona corrección de información de control de cobro
WO2010145717A1 (en) * 2009-06-19 2010-12-23 Telefonaktiebolaget Lm Ericsson (Publ) Establishing a communication session
CN101998531B (zh) 2009-08-11 2013-04-24 华为技术有限公司 策略和计费控制规则授权方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101188504A (zh) * 2006-11-20 2008-05-28 华为技术有限公司 一种网络融合策略计费控制架构的系统及处理方法
CN101222413A (zh) * 2007-01-09 2008-07-16 华为技术有限公司 业务流程中的处理方法及系统
CN101272256A (zh) * 2007-03-23 2008-09-24 华为技术有限公司 业务处理方法和系统、策略控制和计费规则功能实体
CN101374260A (zh) * 2007-08-22 2009-02-25 华为技术有限公司 Pcc规则和承载关联的实现方法、装置和系统

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8958322B2 (en) 2009-08-11 2015-02-17 Huawei Technologies Co., Ltd. Method, apparatus and system for authorizing policy and charging control rule

Also Published As

Publication number Publication date
US20120140665A1 (en) 2012-06-07
US8958322B2 (en) 2015-02-17
EP2458809B1 (en) 2016-10-05
CN101998531A (zh) 2011-03-30
CN101998531B (zh) 2013-04-24
EP2458809A1 (en) 2012-05-30
EP2458809A4 (en) 2012-07-04

Similar Documents

Publication Publication Date Title
WO2011018030A1 (zh) 策略和计费控制规则授权方法、装置及系统
US20230262530A1 (en) Method and apparatus for controlling quality of service
US8621555B2 (en) Access control method and system for packet data network, PCRF entity
US9288790B2 (en) Method and apparatus for bearer processing
EP2154842A1 (en) Method and network element device for acquiring the policy control information of ip access session
WO2013082984A1 (zh) 一种附着到e-utran的方法及移动性管理实体
WO2007143940A1 (fr) procédé, système et équipement de contrôle des conditions d'utilisation et de la facturation lorsque l'utilisateur est mobile
TW200803370A (en) Wireless communication method and system for activating multiple service bearers via efficient packet data protocol context activation procedures
WO2010081329A1 (zh) 业务流迁移过程中对网络资源进行控制的方法和系统
WO2011140895A1 (zh) 签约业务合并场景下对qos参数进行处理的方法及设备
WO2009018777A1 (fr) Procédé et appareil de distribution et de transfert d'une identité de support dans un réseau évolué
JP2010535449A (ja) メディアフローの選択方法
WO2009132536A1 (zh) 一种策略授权方法、系统及设备
WO2008092346A1 (fr) Procédé, système et appareil pour l'établissement d'un support de signalisation
WO2011134102A1 (zh) 关联会话的方法、装置及系统
US20180324087A1 (en) Method and system for routing rule transmission, and device
WO2010075735A1 (zh) 基于轻量级双栈的业务流管理方法、装置及系统
WO2011035665A1 (zh) 一种通知终端承载建立失败的方法及系统
WO2011140707A1 (zh) 业务流旁路方法、系统和策略与计费规则功能实体
WO2010006493A1 (zh) 动态业务流的处理方法及系统
JP6271719B2 (ja) データ接続のためのオンデマンドＱｏＳ
WO2012155774A1 (zh) S9子会话建立方法、系统及pcrf
WO2011120235A1 (zh) Sae架构下实现业务数据流旁路的方法、装置及系统
WO2009036694A1 (fr) Procédé, dispositif et système pour établir de multiples connexions pdn
WO2011085578A1 (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: 10807975

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2010807975

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2010807975

Country of ref document: EP