WO2018014740A1 - Procédé, appareil et système de commande de politiques - Google Patents

Procédé, appareil et système de commande de politiques Download PDF

Info

Publication number
WO2018014740A1
WO2018014740A1 PCT/CN2017/092081 CN2017092081W WO2018014740A1 WO 2018014740 A1 WO2018014740 A1 WO 2018014740A1 CN 2017092081 W CN2017092081 W CN 2017092081W WO 2018014740 A1 WO2018014740 A1 WO 2018014740A1
Authority
WO
WIPO (PCT)
Prior art keywords
instance
identifier
instance identifier
media
message
Prior art date
Application number
PCT/CN2017/092081
Other languages
English (en)
Chinese (zh)
Inventor
周晓云
梁爽
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN201610884609.9A external-priority patent/CN107634838A/zh
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP17830374.9A priority Critical patent/EP3487257A4/fr
Priority to US16/318,274 priority patent/US10630495B2/en
Publication of WO2018014740A1 publication Critical patent/WO2018014740A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Definitions

  • the present application relates to, but is not limited to, the field of communications, and more particularly to a policy control method, apparatus and system.
  • FIG. 1 is a schematic diagram of an architecture of a Policy and Charging Control (PCC) defined according to the 3rd Generation Partnership Project (3GPP).
  • the Policy and Charging Rules Function (PCRF) is used to determine the quality of service (QoS) and charging policy for the service using network resources.
  • the PCRF needs to combine the service information received from the application function (AF, Application Function), the user subscription information received from the SPR (Subscription Profile Repository), and the policy configured by the operator.
  • the PCRF sends the control policy for the service to the Policy and Charging Enforcement Function (PCEF) or the Bearer Binding and Event Report Function (BBERF).
  • PCEF Policy and Charging Enforcement Function
  • BBERF Bearer Binding and Event Report Function
  • the PCRF can subscribe to the bearer layer related events to the PCEF and/or the BBERF, so that when the above events occur in the bearer layer, it can be perceived in time and change the control strategy.
  • the PCEF and the Traffic Detection Function can perform application detection and control functions according to the PCC rules (PCEF) or the Application and Detection Control (ADC) issued by the PCRF.
  • PCEF PCC rules
  • ADC Application and Detection Control
  • the AF requests the QoS authorization of the network to allocate resources for the application at the network layer by providing service information to the PCRF.
  • 2 is a flow chart of network QoS guarantee according to AF request, including:
  • Step 201 The AF provides service information to the PCRF, where the message carries service information, including a media description component (carried by the Media-Component-Description AVP);
  • AAR authorization request sent by the AF to the PCRF to provide service information
  • AAR authorization request
  • the format of the authorization request (AAR) message is as follows: one AAR message can have zero, one or more media description components:
  • a Media-Component-Description AVP can carry zero, one or more Media-Sub-Component AVPs.
  • Media-Component-Number is used to identify a Media-Component-Description:
  • the format of the Media-Sub-Component AVP is as follows, where Flow-Number is used to identify a Media-Sub-Component:
  • Step 202 The PCRF returns a confirmation message after saving the information.
  • Step 203 The PCRF makes a policy decision according to the network policy, service information, and user subscription information, and formulates a PCC rule.
  • the PCRF may need to interact with the SPR to obtain the user's subscription information;
  • Step 204 The PCRF provides the PCC rule formulated after the policy decision to the PCEF.
  • Step 205 After the PCEF installs the PCC rule, the PCEF returns an acknowledgement message.
  • Step 206 The PCEF initiates a resource reservation process according to the PCC rule.
  • Step 207 After the PCRF provides the PCEF to the PCC rule (ie, after step S204), the PCRF receives the updated service information again, and carries the updated media description component.
  • Step 208 The PCRF returns an acknowledgement message after saving the updated service information.
  • Step 209 The PCRF performs policy decision according to the network policy, service information, and user subscription information, and updates the previous PCC rule.
  • Step 210 The PCRF provides the updated PCC rule to the PCEF.
  • Step 211 After the PCEF installs the PCC rule, the PCEF returns an acknowledgement message.
  • Step 212 The PCRF initiates a resource reservation process according to the installed PCC rules.
  • Step 213 After that, the PCEF receives the response message of the resource reservation process initiated by step 206, indicating that the resource reservation fails.
  • Step 214 The PCEF sends an event notification to the PCRF, carrying a resource reservation failure indication and a corresponding PCC rule name.
  • Step 215 The PCRF returns an acknowledgement message to the PCEF.
  • Step 216 The PCRF sends an event notification to the AF, and carries a resource reservation failure indication and a flow identifier.
  • the format of the RAR message that the PCEF sends an event notification to the PCRF is as follows.
  • the Specific-Action AVP is used to carry the resource reservation failure indication, and the Flows AVP is used to carry the flow identifier:
  • Step 217 The AF returns an acknowledgement message to the PCRF.
  • the AF since the AF reserves the failure feedback after the AF sends the updated service information to the PCRF, the AF cannot determine whether the resource reservation of the initially provided service information fails or the resource of the updated service information. The reservation failed.
  • the PCRF since the PCRF is the resource reservation failure feedback received after the PCC rule is updated to the PCEF, the PCRF cannot determine whether the initially provided PCC rule resource reservation failure or the updated PCC rule resource reservation failure.
  • the above problem also exists after the initial resource reservation is successful, and the AF continuously updates the service information.
  • the AF will not know which resource information update corresponding to the resource reservation fails.
  • the AF is also unable to prepare to know which resource information update corresponding resource reservation is successful.
  • the embodiment of the invention provides a policy control method, device and system, so that the AF correctly knows the resource reservation result.
  • a policy control method including: receiving a first message indicating a resource allocation result, and determining a corresponding second instance identifier according to the first instance identifier in the first message
  • the first instance identifier is an instance identifier corresponding to a policy rule instance that performs resource allocation
  • the second instance identifier is an instance identifier corresponding to a media component instance or a media subcomponent instance used to formulate the policy rule instance.
  • receiving the first message for indicating a resource allocation result includes: receiving, by the policy and charging execution function, a first message sent by the PCEF entity to indicate a resource allocation result; or receiving the bearer binding and The event reporting function sends a first message sent by the BBERF entity to indicate the result of the resource allocation.
  • the first instance identifier carries the indication information of the service information triggering policy decision or the indication information of the second instance identifier corresponding to the first instance identifier.
  • the indication information is an identifier bit or a specific value interval in the value of the first instance identifier.
  • the method before determining the second instance identifier according to the first instance identifier in the first message, the method further includes one of the following:
  • the receiving, by the AF entity, the second instance identifier includes: receiving the second instance identifier that is allocated by the AF entity to the media component instance; the method further includes: Determining one or more PCC rule instances according to the media component instance, wherein the first instance identifier corresponding to the second instance identifier is carried in the one or more PCC rule instances.
  • the formulating one or more PCC rule instances according to the media component instance includes: when the PCC rule instance is formulated according to the media component instance, when the media component instance carries multiple media subcomponents, The PCC rule instance is generated by aggregating the plurality of media sub-components; or, when the PCC rule instance is configured according to the media component instance, each PCC rule instance carries the first instance identifier.
  • the allocating the second instance identifier to the media component instance or the media subcomponent instance includes: if the PCC rule instance is formulated according to the media component instance, assigning the The second instance identifier is allocated to the media subcomponent instance if the PCC rule instance is formulated according to one or more media subcomponent instances.
  • the method before receiving the first message for indicating the resource allocation result, the method further includes: allocating a first instance identifier to the PCC rule instance, wherein the first instance identifier is determined according to the second instance identifier.
  • the relationship between the second instance identifier and the first instance identifier meets one of the following:
  • the value of the second instance identifier is the same as the value of the first instance identifier
  • the value of the second instance identifier is calculated according to the value of the first instance identifier according to the configuration
  • the value of the second instance identifier is obtained according to the correspondence between the first instance identifier and the second instance identifier saved by the PCRF.
  • the first message further carries a rule identifier of the policy rule instance
  • the second message further carries an identifier of the media component instance or an identifier of the media subcomponent instance, where the The rule identification is used to determine the media component instance or the media subcomponent instance.
  • the method further comprises: returning the second instance identifier to the AF, and providing the media component instance or media sub The identity of the component.
  • a policy control apparatus including: a first receiving module, configured to receive a first message for indicating a resource allocation result, and according to a first instance in the first message The identifier determines a corresponding second instance identifier, where the first instance identifier is an instance identifier corresponding to a policy rule instance that performs resource allocation, and the second instance identifier is a media component instance used to formulate the policy rule instance or An instance identifier corresponding to the media sub-component instance; the sending module is configured to send, to the application function AF entity, a second message that is used to indicate a resource allocation result, where the second message carries the second instance identifier.
  • the first receiving module includes: a first receiving unit, configured to receive a first message sent by a PCEF entity for indicating a resource allocation result by a policy and charging execution function; or a second receiving unit And being configured to receive the first message sent by the BBERF entity sent by the bearer binding and event reporting function to indicate a resource allocation result.
  • the apparatus further includes: a second receiving module, configured to receive, before the first receiving module determines the second instance identifier according to the first instance identifier in the first message, Said second instance identifier assigned by the AF entity; or an allocation module configured to allocate the second instance identifier for the media component instance or the media subcomponent instance.
  • the second receiving module is configured to: receive the second instance identifier that is allocated by the AF entity for the media component instance; and the device further includes: formulating a rule module, configured to be according to the media component The instance formulates one or more instances of the PCC rule, wherein the first instance identifier corresponding to the second instance identifier is carried in the one or more PCC rule instances.
  • the allocating module is configured to: assign a second instance identifier to the media component instance if a PCC rule instance is formulated according to the media component instance; or if according to one or more media subcomponents The instance formulates a PCC rule instance, and then assigns the second instance identifier to the media subcomponent instance.
  • the first instance identifier carries the indication information of the service information triggering policy decision or the indication information of the second instance identifier corresponding to the first instance identifier.
  • the indication information is an identifier bit or a specific value interval in the value of the first instance identifier.
  • the first message further carries a rule identifier of the policy rule instance
  • the second message further carries an identifier of the media component instance or an identifier of the media subcomponent instance, where the The rule identification is used to determine the media component instance or the media subcomponent instance.
  • the sending module is further configured to: after the assigning module allocates the second instance identifier to the media component instance, return the second instance identifier to the AF, and provide the The identity of the media component instance or media subcomponent instance.
  • a policy control system including: a policy and charging rule function PCRF entity and an AF entity, where the PCRF entity includes: a first receiving module, configured to receive for indicating resource allocation The first message of the result, and according to the first message
  • the first instance identifier determines a corresponding second instance identifier, where the first instance identifier is an instance identifier corresponding to a policy rule instance that performs resource allocation, and the second instance identifier is used to formulate the policy rule instance
  • the AF entity is set to: receive the second message.
  • the AF entity is further configured to allocate the second instance identifier; or the PCRF entity is further configured to assign the second instance identifier to the media component instance or the media subcomponent.
  • a storage medium is also provided.
  • the storage medium is arranged to store program code for performing the following steps:
  • first instance identifier is a policy rule instance corresponding to performing resource allocation
  • second instance identifier is an instance identifier corresponding to a media component instance or a media subcomponent instance used to formulate the policy rule instance
  • a first message for indicating a resource allocation result is received, and a corresponding second instance identifier is determined according to the first instance identifier in the first message, where the first instance identifier is an execution resource.
  • the second message of the second message carries the second instance identifier. The AF can be made to know the resource reservation result correctly.
  • 1 is a schematic diagram of a PCC architecture defined by 3GPP;
  • FIG. 3 is a flowchart of a policy control method according to an embodiment of the present invention.
  • FIG. 4 is a structural block diagram of a policy control apparatus according to an embodiment of the present invention.
  • FIG. 5 is a structural block diagram of a policy control system according to an embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of a policy control according to an embodiment of the present invention.
  • FIG. 8 is a schematic flowchart of a third policy control according to Embodiment 3 of the present invention.
  • FIG. 9 is a schematic flowchart of a policy control according to Embodiment 4 of the present invention.
  • FIG. 3 is a flowchart of a policy control method according to an embodiment of the present invention. As shown in FIG. 3, the process includes the following steps. step:
  • Step S302 Receive a first message for indicating a resource allocation result, and determine a corresponding second instance identifier according to the first instance identifier in the first message, where the first instance identifier is a policy rule instance corresponding to performing resource allocation.
  • Step S304 Send a second message for indicating a resource allocation result to the application function AF entity, where the second message carries the second instance identifier.
  • the policy rule instance refers to the initial provision of the policy rule or a certain time.
  • New; media component instance or media subcomponent instance refers to the initial or some update of a media component or media subcomponent.
  • the first message that is used to indicate the resource allocation result is received, and the corresponding second instance identifier is determined according to the first instance identifier in the first message, where the first instance identifier is a policy rule instance corresponding to performing resource allocation.
  • An instance identifier, the second instance identifier is an instance identifier corresponding to the media component instance or the media subcomponent instance used to formulate the policy rule, and the second function is sent to the application function AF entity to indicate the resource allocation result.
  • the second instance identifier The AF can be made to know the resource reservation result correctly.
  • an Instance Identifier may also be referred to as an Update Counter, a sequence number, a Reference Number, or an Update Instance identifier.
  • the execution body of the above steps may be a PCRF or the like, but is not limited thereto.
  • the receiving the first message for indicating the resource allocation result includes the following two methods: receiving the first message sent by the PCEF entity for indicating the resource allocation result by the policy and charging execution function; or receiving The first message sent by the BBERF entity to the bearer binding and event reporting function to indicate the resource allocation result.
  • the first instance identifier carries the indication information of the service information triggering policy decision or the indication information of the second instance identifier corresponding to the first instance identifier.
  • the indication information is one or more identifier bits or a specific one or more value intervals in the first instance identifier value.
  • the second instance identifier may also be allocated by using the external node or itself, including:
  • the method when receiving the second instance identifier allocated by the AF entity, the method may further include:
  • formulating one or more PCC rule instances according to the media component instance includes: when a PCC rule instance is formulated according to the media component instance, when the media component carries multiple media subcomponents, the multiple media subcomponents are aggregated After the PCC rule instance is created, each PCC rule instance carries the first instance identifier.
  • the method when assigning the second instance identifier to the media component instance or the media subcomponent instance, the method further includes: assigning a second to the media component instance if the PCC rule instance is formulated according to the media component instance An instance identifier; or, if a PCC rule instance is formulated based on one or more media subcomponent instances, assign a second instance identifier to the media subcomponent instance.
  • the method may further perform: returning the second instance identifier to the AF, and providing the identifier of the media component instance or the media subcomponent instance.
  • the embodiment before receiving the first message for indicating the resource allocation result, the embodiment further includes: allocating a first instance identifier to the PCC rule, wherein the first instance identifier is determined according to the second instance identifier.
  • the relationship between the second instance identifier and the first instance identifier meets one of the following: the value of the second instance identifier is the same as the value of the first instance identifier; The value is obtained according to the configuration of the first instance identifier. The value of the second instance identifier is obtained according to the correspondence between the first instance identifier and the second instance identifier saved by the PCRF.
  • the first message further carries a rule identifier of the policy rule instance
  • the second message further carries an identifier of the media component instance or an identifier of the media subcomponent instance, wherein the rule identifier is used to determine the media component instance or the media subcomponent Example.
  • the rule identifier may be a rule name.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the embodiment of the present invention may be embodied in the form of a software product stored in a storage medium (such as a ROM/RAM, a magnetic disk, an optical disk), and includes a plurality of instructions for making a terminal device.
  • a storage medium such as a ROM/RAM, a magnetic disk, an optical disk
  • the method of various embodiments of the present invention (which may be a cell phone, a computer, a server, or a network device, etc.).
  • a policy control device and a system are provided to implement the foregoing embodiments and implementation manners, which have not been described again.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the devices described in the following embodiments may be implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 4 is a structural block diagram of a policy control apparatus according to an embodiment of the present invention. As shown in FIG. 4, the apparatus includes:
  • the first receiving module 40 is configured to receive a first message for indicating a resource allocation result, and determine a corresponding second instance identifier according to the first instance identifier in the first message, where the first instance identifier is used to perform resource allocation.
  • the sending module 42 is configured to send a second message for indicating a resource allocation result to the application function AF entity, where the second message carries the second instance identifier.
  • the first receiving module 40 further includes: a first receiving unit, configured to receive a first message sent by the PCEF entity for indicating a resource allocation result by the policy and charging execution function; or
  • the second receiving unit is configured to receive a first message sent by the BBERF entity sent by the bearer binding and event reporting function to indicate a resource allocation result.
  • the device further includes: a second receiving module, configured to receive the second instance identifier allocated by the AF entity before the first receiving module determines the second instance identifier according to the first instance identifier in the first message; Or, an allocation module, configured to assign a second instance ID to a media component instance or a media subcomponent instance.
  • the second receiving module is configured to: the device further includes: a formulating module, configured to receive a second instance identifier allocated by the AF entity for the media component instance; and one or more according to the media component instance The PCC rule instance, wherein the first instance identifier corresponding to the second instance identifier is carried in one or more PCC rule instances.
  • the allocation module is configured to: assign a second instance identifier to the media component instance if the PCC rule instance is formulated according to the media component instance; or if the PCC rule instance is formulated according to one or more media subcomponent instances , the second instance ID is assigned to the media subcomponent instance.
  • the sending module is further configured to: after the assigning module allocates the second instance identifier to the media component instance, return a second instance identifier to the AF, and provide an identifier of the media component instance or the media subcomponent instance.
  • the first instance identifier carries the indication information of the service information triggering policy decision or the indication information of the second instance identifier corresponding to the first instance identifier.
  • the indication information is an identifier bit or a specific value interval in the value of the first instance identifier.
  • the first message further carries a rule identifier of the policy rule instance
  • the second message further carries an identifier of the media component instance or an identifier of the media subcomponent, wherein the rule identifier is used to determine the media component instance or the media subcomponent instance .
  • FIG. 5 is a structural block diagram of a policy control system according to an embodiment of the present invention. As shown in FIG. 5, the method includes:
  • the PCRF entity 50 includes:
  • the first receiving module 502 is configured to receive a first message for indicating a resource allocation result, and determine a corresponding second instance identifier according to the first instance identifier in the first message, where the first instance identifier is configured to perform resource allocation.
  • the sending module 504 is configured to send, to the application function AF entity, a second message that is used to indicate a resource allocation result, where the second message carries the second instance identifier.
  • the AF entity 52 is arranged to receive the second message.
  • the AF entity 52 is further configured to assign the second instance identification; or the PCRF entity 50 is further configured to assign a second instance identification to the media component instance or the media subcomponent instance. That is, the second instance identification can be obtained by the AF entity 52 and the PCRF entity 50.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • This embodiment provides a method for policy control, so that the AF can correctly learn the resource reservation result.
  • the PCRF allocates a first instance identifier to the PCC rule, where the first instance identifier carries a second instance identifier corresponding to the first instance identifier, and the second instance identifier is a corresponding service information used to customize the PCC rule. Instance ID.
  • the PCRF After receiving the message of the resource allocation result sent by the bearer binding function (BBERF/PCEF), the PCRF sends a message of the resource allocation result to the AF after determining the second instance identifier according to the first instance identifier in the message, and carries the message The second instance identifier.
  • BBERF/PCEF bearer binding function
  • the second instance identifier is assigned by an application function or by a PCRF.
  • the application function allocates one of the second instance identifiers for each media component instance in the service information, and the PCRF formulates one or more according to the media component instance.
  • the PCC rule instance carries the first instance identifier of the same value in the PCC rule instance.
  • the PCRF is a second instance identifier for assigning the same value to the media subcomponent instance for formulating the same PCC rule instance.
  • FIG. 6 is a schematic flowchart of a policy control according to an embodiment of the present invention, in which an Rx instance identifier is allocated by a PCRF, and the Rx instance identifier and the Gx instance identifier are in one-to-one correspondence. Includes the following steps:
  • Step 601 The AF provides service information to the PCRF, where the message carries service information, including one or more media components (carried in the Media-Component-Description AVP);
  • Step 602 The PCRF makes a policy decision according to the network policy, service information, and user subscription information, and formulates a PCC rule.
  • the PCRF may need to interact with the SPR to obtain the user's subscription information.
  • the PCRF may formulate a PCC rule according to a media subcomponent (carrying in the Media-Sub-Component AVP) (ie, if a Media-Component-Description AVP carries 2 Media-Sub-Component AVPs)
  • the PCRF will formulate two PCC rules.
  • the PCRF may also aggregate multiple Media Sub Components in a Media Component to generate a PCC rule.
  • the PCRF formulates a PCC rule based on a Media Sub Component
  • the PCRF will assign an Rx instance identifier (Reference number) to the Media Sub Component (here denoted as the Rx instance identifier a); if the PCRF is 2 or more Media Subs
  • the Component has a PCC rule, and the PCRF will assign one Rx instance identifier (Reference number) to the two or more Media Sub Components (here denoted as the Rx instance identifier a); if the PCRF has a PCC rule for the Media Component, then The PCRF will assign an Rx instance number to the Media Component (ie, the same as assigning the same Reference number to all Media Sub Components in the Media Component).
  • the Rx instance identifier a identifies the initial provision of the Media Component or Media Sub Component (which may be considered to be the initial provisioning instance identifying the Media Component or Media Sub Component).
  • the Gc instance identifier is carried in the PCC rule, here denoted as the Gx instance identifier a.
  • the value of the Gx instance identifier can be the same as the value of the Rx instance identifier, or the value of the Gx instance identifier can be derived based on the value of the Rx instance identifier. That is, the Gx instance identifier and the Rx instance identifier are in one-to-one correspondence.
  • the Gx instance identifier carries the indication information indicating the policy decision triggered by the service information (that is, the Gx instance identifier corresponds to one Rx instance identifier).
  • the indication information may be that an identifier bit is set in the value of the Gx instance identifier, or a specific value interval is allocated.
  • the Gx instance identifier a identifies the initial provision of a PCC rule (which may be considered to be the initial provisioning instance that identifies this PCC rule).
  • Step 603 The PCRF returns an acknowledgement message, and the message carries the flow identifier (carried by the Flows AVP) and carries the corresponding Rx instance identifier (here, the Rx instance identifier a), and is carried by the Reference-Number AVP. If the PCRF assigns the same Reference Number to a Media Component, the Flow only needs to carry the Media Component Number of the Media Component (using Media-Component-Number AVP) and the corresponding Rx instance identifier; if the PCRF is different in a Media Component The Media Sub Component is assigned a different Reference Number.
  • the Flow AVP In addition to the Media Component Number carrying the Media component, the Flow AVP also carries the Flow Number of the Sub Sub Component (carryed by the Flow-Number AVP) and the corresponding Reference Number. Through this message, the AF knows the Reference Number of each Media Sub Component.
  • the PCRF may return a response message carrying the Rx instance identifier to the AF, and then formulate a PCC rule.
  • Step 604 The PCRF provides the PCC rule formulated after the policy decision to the PCEF.
  • Step 605 After the PCEF installs the PCC rule, the PCEF returns an acknowledgement message.
  • Step 606 The PCEF initiates a resource reservation process according to the PCC rule.
  • Step 607 After the PCRF provides the PCEF to the PCC rule (ie, after step S604), the PCRF receives the updated service information, and carries the updated media component (ie, a new instance of the previously provided media component).
  • the updated media component ie, a new instance of the previously provided media component.
  • AF only sends media components that need to be updated. AF can also Provide complete business information (including updated media components and unupdated media components)
  • Step 608 The PCRF performs policy decision according to the network policy, service information, and user subscription information, and updates the previous PCC rule. If the updated media component is carried, the following steps are also performed: if a new Sub Component is added and a new PCC rule is created for it, the PCRF assigns a Gx instance identifier b to the PCC rule, and assigns an Rx instance identifier b to the Sub Component; The Sub-Component is added and the previous PCC rule is updated according to the newly added Sub Component. The PCRF allocates a new Gx instance identifier b to the PCC rule, and assigns a new Rx instance identifier b to all Sub Components corresponding to the PCC rule.
  • the PCRF allocates a new Gx reference post number b to the PCC rule, and assigns a new Rx instance identifier b to all Sub Components corresponding to the PCC rule.
  • the value of the Gx instance identifier b may be the same as the value of the Rx instance identifier b, or the value of the Gx instance identifier b and the value of the Rx instance identifier b may be derived from each other. That is, the Gx instance identifier b and the Rx instance identifier b are one-to-one correspondence.
  • the Gx instance identifier carries the indication information indicating the policy decision triggered by the service information (that is, the Gx instance identifier corresponds to one Rx instance identifier).
  • the indication information may be that an identifier bit is set in the value of the Gx instance identifier, or a specific value interval is allocated.
  • the Rx instance identifier b identifies the first update of this Media Component or Media Sub Component (which can be thought of as the first update instance identifying this Media Component or Media Sub Component).
  • the Gx instance identifier b identifies the first update of this PCC rule (which may be considered to be the first update instance identifying this PCC rule).
  • Step 609 The PCRF returns an acknowledgement message, and the message carries the flow identifier (carried by the Flows AVP) and carries the corresponding Rx instance identifier b therein, and is carried by the Reference-Number AVP. If the PCRF allocates the same Reference Number to a Media Component, Flow only needs to carry the Media Component Number of the Media Component (with Media-Component-Number AVP) and the corresponding Rx instance to identify b; if the PCRF is a Media Component Different Media SubComponents are assigned different Rx instance identifiers a.
  • the Flows AVP In addition to the Media Component Number carrying the Media component, the Flows AVP also carries the Flow Number of the Sub Sub Component ( carried by the Flow-Number AVP) and the corresponding Rx instance identifier. b. Through this message, AF knows each Media Sub The instance ID of the Component.
  • the PCRF may return a response message carrying the Rx instance identifier to the AF, and then formulate a PCC rule.
  • Step 610 The PCRF provides the updated PCC rule to the PCEF, and the PCC rule carries the Gx instance identifier b.
  • Step 611 After the PCEF installs the PCC rule, the PCEF returns an acknowledgement message.
  • Step 612 The PCRF initiates a resource reservation process according to the installed PCC rule.
  • Step 613 After step 610, the PCRF may need to further update the PCC rules for some reason (for example, the network policy changes, the user subscription changes, the access network changes, etc.), the PCRF makes policy decisions, updates the PCC rules, and
  • the PCC rule carries a new Gx instance identifier (here denoted as a Gx instance identifier ').
  • the Gx instance identifier indicates that the policy decision triggered by the non-service information is carried out (that is, the Gx instance identifier does not correspond to an Rx instance identifier).
  • the identifier may be set in the value of the Gx instance identifier, or a specific value interval may be allocated (that is, the Gx instance identifier corresponding to the Rx instance identifier and the Gx corresponding to the Rx instance identifier).
  • the instance IDs belong to different value ranges.
  • Step 614 The PCRF provides the updated PCC rule to the PCEF, and the PCC rule carries the Gx. Instance identification’;
  • Step 615 After the PCEF installs the PCC rule, the PCEF returns a confirmation message.
  • Step 616 The PCRF initiates a resource reservation process according to the installed PCC rule.
  • Step 617 After this, the PCEF receives the response message of the resource reservation process, indicating that the resource reservation fails.
  • Step 618 The PCEF sends an event notification to the PCRF, carrying a resource reservation failure indication (carried by the Event-Trigger AVP), and a corresponding PCC rule (carried by the Charging-Rule-Report AVP).
  • the failure indication received by the PCEF is the response of the resource reservation process initiated by the PCEF in step 606
  • the message sent by the PCEF to the PCRF further carries the Gx instance identifier a (using the Reference-Number AVP)
  • the failure indication received by the PCEF is the response of the resource reservation process initiated by the PCEF in step 612, and the message sent by the PCEF to the PCRF further carries the Gx instance identifier b (using the Reference-Number AVP);
  • the failure indication received by the PCEF is the response of the resource reservation procedure initiated by the PCEF in step 616, and the message sent by the PCEF to the PCRF further carries the Gx instance identifier '(with Reference-Number AVP).
  • Step 619 The PCRF returns an acknowledgement message to the PCEF.
  • Step 620 If the PCEF reports that the Gx instance identifier is the Gx instance identifier a or the Gx instance identifier b, the PCRF determines the Rx instance identifier a or the Rx instance identifier b according to the Gx instance identifier a or the Gx instance identifier b. (The PCRF can derive the Rx instance ID from the Gx instance identifier according to the configuration). The PCRF sends an event notification to the AF, carrying a resource reservation failure indication (carried by the Specific-Action AVP), and a flow identifier (carried by the Flows AVP).
  • a resource reservation failure indication carried by the Specific-Action AVP
  • a flow identifier carried by the Flows AVP
  • the Flows AVP carries the corresponding Rx instance identifier a. If the PCRF receives the Gx instance identifier b, the Flows AVP carries the corresponding Rx instance identifier b. . In this way, according to the Rx instance identifier a or the Rx instance identifier b, the AF can determine which resource information of the provided service information has failed to be allocated; (here, the allocation result is an allocation failure)
  • Step 621 The AF returns an acknowledgement message to the PCRF.
  • the last embodiment only describes a scenario in which the AF continuously provides 2 times of service information, and the scenario is similar for the case where the AF continuously provides 3 or more scenes.
  • the PCRF is allocated according to the allocation principle of the Rx instance identifier and the Gx instance identifier.
  • the Rx instance identifier and the Gx instance identifier are allocated by the PCRF, and after the resource allocation of the initial service information is failed, the corresponding Rx instance identifier and the Gx instance identifier are reported.
  • the instance identifier may not be assigned when the service information is initially provided. In this way, as long as the instance identifier is not carried in the reported information, it indicates that the resource allocation of the initially provided service information fails.
  • the PCRF is not required to save the actual correspondence between the Gx instance identifier and the Rx instance identifier, but the PCRF may derive the Rx instance identifier according to the Gx instance identifier according to the configured method.
  • the PCRF can also save the correspondence between the Gx reference number and the Rx reference number to implement mapping between each other.
  • the PCRF updates the established PCC rules based on new instances of media components or media subcomponents that may be considered to be new instances of PCC rules based on new instances of media components or media subcomponents.
  • FIG. 7 is a schematic flowchart of policy control according to Embodiment 2 of the present invention, including the following steps:
  • Step 401 The AF provides service information to the PCRF, where the message carries service information, including one or more media components (carried in the Media-Component-Description AVP);
  • Step 402 The PCRF performs policy decision according to the network policy, service information, and user subscription information, and formulates a PCC rule.
  • the PCRF may need to interact with the SPR to obtain the user's subscription information.
  • the PCRF may formulate a PCC rule according to a media subcomponent (carrying in the Media-Sub-Component AVP) (ie, if a Media-Component-Description AVP carries 2 Media-Sub-Component AVPs)
  • the PCRF will formulate two PCC rules.
  • the PCRF may also aggregate multiple Media Sub Components in a Media Component to generate a PCC rule.
  • the PCRF formulates a PCC rule based on a Media Sub Component
  • the PCRF will assign an Rx instance identifier (Reference number) to the Media Sub Component (here denoted as the Rx instance identifier a); if the PCRF is 2 or more Media Subs
  • the Component has a PCC rule, and the PCRF will assign one Rx instance identifier (Reference number) to the two or more Media Sub Components (here denoted as the Rx instance identifier a); if the PCRF has a PCC rule for the Media Component, then The PCRF will assign an Rx instance number to the Media Component (ie, the same as assigning the same Reference number to all Media Sub Components in the Media Component).
  • the Gx instance identifier is carried in the PCC rule, which is represented as the Gx instance identifier a, and carries the Gxx instance identifier in the QoS rule, which is represented as the Gxx instance identifier a.
  • the Gx instance ID and the Gxx instance ID have the same value.
  • the value of the Gx/Gxx instance identifier may be the same as the value of the Rx instance identifier, or the value of the Gx/Gxx instance identifier may be derived according to the value of the Rx instance identifier. That is, the Gx/Gxx instance identifier and the Rx instance identifier are in one-to-one correspondence.
  • the Gx/Gxx instance identifier carries the indication information indicating the policy decision triggered by the service information (that is, the Gx/Gxx instance identifier corresponds to one Rx instance identifier).
  • the indication information may be that an identifier bit is set in the value of the Gx instance identifier, or a specific value interval is allocated.
  • the Rx instance identifier a identifies the initial provision of this Media Component or Media Sub Component (which can be considered as the initial mention of identifying this Media Component or Media Sub Component). For example).
  • the Gx/Gxx instance identification a identifies the initial provision of this PCC/QoS rule (which can be considered as an initial provisioning instance identifying this PCC/QoS rule).
  • Step 403 The PCRF returns an acknowledgement message, and the message carries the flow identifier (carried by the Flows AVP) and carries the corresponding Rx instance identifier therein, and is carried by the Reference-Number AVP. If the PCRF assigns the same Reference Number to a Media Component, the Flow only needs to carry the Media Component Number of the Media Component (using Media-Component-Number AVP) and the corresponding Rx instance identifier; if the PCRF is different in a Media Component The Media Sub Component is assigned a different Reference Number.
  • the Flow AVP In addition to the Media Component Number carrying the Media component, the Flow AVP also carries the Flow Number of the Sub Sub Component (carryed by the Flow-Number AVP) and the corresponding Reference Number. Through this message, the AF knows the Reference Number of each Media Sub Component.
  • the PCRF may return a response message carrying the Rx instance identifier to the AF, and then formulate a PCC/QoS rule.
  • Step 404 The PCRF provides the PCC rule formulated after the policy decision to the PCEF.
  • Step 405 After the PCEF installs the PCC rule, the PCEF returns an acknowledgement message.
  • Step 406 The PCRF provides a QoS rule to the BBERF.
  • Step 407 The BBERF returns an acknowledgement message.
  • Step 408 The PCEF initiates a resource reservation process according to the QoS rule.
  • Step 409 After the PCRF provides the BBERF to the QoS rule (ie, after step S406), the PCRF receives the updated service information, and carries the updated media component (ie, a new instance of the previously provided media component).
  • the updated media component ie, a new instance of the previously provided media component.
  • AF only sends media description components that need to be updated. AF can also provide complete business information (including updated media components and unupdated media components).
  • Step 410 The PCRF performs policy decision according to the network policy, service information, and user subscription information, and updates the previous PCC rule. If the updated media component is carried, the following steps are also performed: if a new Sub Component is added and a new PCC/QoS rule is created for it, the PCRF assigns a Gx instance identifier b to the PCC rule, and assigns a Gxx instance identifier b to the QoS rule. And assigning the Rx instance identifier b to the Sub Component; if the Sub Component is added and the previous PCC/QoS rule is updated according to the newly added Sub Component, the PCRF allocates a new Gx instance identifier b/Gxx instance for the PCC/QoS rule.
  • a new Rx instance identifier b is assigned to all Sub Components corresponding to the PCC/QoS rule.
  • the value of the Gx instance identifier b/Gxx instance identifier b may be the same as the value of the Rx instance identifier b, or the value of the Gx instance identifier b/Gxx instance identifier b and the value of the Rx instance identifier b may be deduced from each other. That is, the Gx instance identifier b/Gxx instance identifier b and the Rx instance identifier b are one-to-one correspondence. Similarly, the Gx instance identifier b/Gxx instance identifier b carries the indication information indicating the policy decision triggered by the service information (that is, the Gx instance identifier corresponds to one Rx instance identifier).
  • the indication information when the indication information is actually implemented, it may be that an identifier bit is set in the value of the Gx instance identifier, or a specific value interval is allocated.
  • the Rx instance identifier b identifies the first update of this Media Component or Media Sub Component (which can be thought of as the first update instance identifying this Media Component or Media Sub Component).
  • the Gx/Gxx instance identification b identifies the first update of this PCC/QoS rule (which can be considered as the first update instance identifying this PCC/QoS rule).
  • Step 411 The PCRF returns an acknowledgement message, and the message carries the flow identifier (using Flows AVP). Carrying and carrying the corresponding Rx instance identifier a, carried by the Reference-Number AVP. If the PCRF allocates the same Reference Number to a Media Component, Flow only needs to carry the Media Component Number of the Media Component (with Media-Component-Number AVP) and the corresponding Rx instance to identify b; if the PCRF is a Media Component Different Media Sub Components are assigned different Rx instance identifiers b.
  • the Flow AVP In addition to the Media Component Number carrying the Media component, the Flow AVP also carries the Flow Number of the Sub Sub Component ( carried by the Flow-Number AVP) and the corresponding Rx instance identifier. b. Through this message, the AF knows the instance ID of each Media Sub Component.
  • Step 412 The PCRF provides the updated PCC rule to the PCEF, and the PCC rule carries the Gx instance identifier a;
  • Step 413 After the PCEF installs the PCC rule, the PCEF returns a confirmation message.
  • Step 414 The PCRF provides a QoS rule to the BBERF.
  • Step 415 After installing the QoS rule, the BBERF returns an acknowledgement message to the PCRF.
  • Step 416 The PCRF initiates a resource reservation process according to the installed QoS rule.
  • Step 417 After step 414, the PCRF may need to further update the PCC rules for some reason (such as a change in the network policy, a change in the subscription of the user, a change in the access network, etc.), and the PCRF makes policy decisions and updates the PCC/QoS rules.
  • the new Gx instance identifier (here denoted as Gx instance identifier ') is carried in the PCC rule, and the QoS rule carries a new Gxx instance identifier (here denoted as Gxx instance identifier ').
  • the Gx/Gxx instance identifier indicates that the policy decision triggered by the non-service information is triggered (that is, the Gx/Gxx instance identifier does not correspond to an Rx instance identifier).
  • the indication information when the indication information is actually implemented, it may be that an identifier bit is set in the value of the Gx/Gxx instance identifier, or a specific value interval is allocated (that is, the Gx/Gxx instance identifier corresponding to the Rx instance identifier and the Rx instance are not associated with the Rx instance identifier.
  • the corresponding Gx/Gxx instance identifiers belong to different value ranges.
  • the Gx/Gxx instance identifies 'identifies the second update of this PCC/QoS rule (which can be considered as the second update instance identifying this PCC/QoS rule).
  • Step 418 The PCRF provides the updated PCC rule to the PCEF, and the PCC rule carries the Gx instance identifier ';
  • Step 419 After the PCEF installs the PCC rule, the PCEF returns a confirmation message.
  • Step 420 The PCRF provides a QoS rule to the BBERF.
  • Step 421 After installing the QoS rule, the BBERF returns an acknowledgement message to the PCRF.
  • Step 422 The PCRF initiates a resource reservation process according to the installed BBERF rule.
  • Step 423 After that, the BBERF receives the response message of the resource reservation process, indicating that the resource reservation fails.
  • Step 424 The BBERF sends an event notification to the PCRF, carrying a resource reservation failure indication (carried by the Event-Trigger AVP), and a corresponding QoS rule (carried by the QoS-Rule-Report AVP). If the failure indication received by the BBERF is the response of the resource reservation procedure initiated by the BBERF in step 408, the message sent by the BBERF to the PCRF further carries the Gxx instance identifier a (using the Reference-Number AVP); In step 423, the failure indication received by the BBERF is the response of the resource reservation procedure initiated by the BBERF in step 416, and the message sent by the BBERF to the PCRF further carries the Gxx instance identifier b (using the Reference-Number AVP).
  • the message sent by the BBERF to the PCRF further carries the Gx instance identifier '(with Reference-Number AVP) where Reference- The Number AVP is carried in the QoS-Rule-Report AVP.
  • Step 425 The PCRF returns an acknowledgement message to the BBERF.
  • Step 426 If the BBERF reports that the Gxx instance identifier is the Gxx instance identifier a or the Gxx instance identifier b, the PCRF determines the Rx instance identifier a or the Rx instance identifier b according to the Gxx instance identifier a or the Gxx instance identifier b. The PCRF sends an event notification to the AF, carrying a resource reservation failure indication (carried by the Specific-Action AVP), and a flow identifier (carried by the Flows AVP). If the PCRF receives the Gxx instance identifier a in step 424, the Flows AVP carries the corresponding Rx instance identifier a.
  • the Flows AVP carries the corresponding Rx instance identifier b. .
  • the AF can determine which resource information of the provided service information fails to be allocated;
  • Step 427 The AF returns an acknowledgement message to the PCRF.
  • the last embodiment only describes a scenario in which the AF continuously provides 2 times of service information, and the scenario is similar for the case where the AF continuously provides 3 or more scenes.
  • the PCRF is allocated according to the allocation principle of the Rx instance identifier and the Gx instance identifier.
  • the instance identifier may not be assigned when the service information is initially provided. In this way, as long as the instance identifier is not carried in the reported information, it indicates that the resource allocation of the initially provided service information fails.
  • the PCRF updates the established PCC/QoS rules based on new instances of media components or media subcomponents that may be considered to be new instances of PCC/QoS rules based on new instances of media components or media subcomponents.
  • FIG. 8 is a schematic flowchart of a third policy control according to an embodiment of the present invention, where an AF assigns an Rx instance identifier, including the following steps:
  • Step 501 The AF provides service information to the PCRF, where the message carries service information, including one or more media components (carried in the Media-Component-Description AVP).
  • the AF can assign a Rx instance identifier to a media component, which is represented here as an Rx instance identifier a;
  • Step 502 The PCRF returns a confirmation message after saving the service information.
  • Step 503 The PCRF makes a policy decision according to the network policy, service information, and user subscription information, and formulates a PCC rule.
  • the PCRF may need to interact with the SPR to obtain the user's subscription information.
  • the PCRF may formulate a PCC rule according to a media subcomponent (carrying in the Media-Sub-Component AVP) (ie, if a Media-Component-Description AVP carries 2 Media-Sub-Component AVPs)
  • the PCRF will formulate two PCC rules.
  • the PCRF may also aggregate multiple Media Sub Components in a Media Component to generate a PCC rule.
  • the Gx instance identifier is carried in the PCC rule, which is represented as the Gx instance identifier a. If the PCRF formulates multiple PCC rules according to one media component, the PCRF carries the same Gx instance identifier in each PCC rule.
  • the value of the Gx instance identifier can be the same as the value of the Rx instance identifier, or the value of the Gx instance identifier can be derived based on the value of the Rx instance identifier. That is, the Gx instance identifier and the Rx instance identifier are in one-to-one correspondence.
  • the Gx instance identifier carries the indication information indicating the policy decision triggered by the service information (that is, the Gx instance identifier corresponds to one Rx instance identifier).
  • the indication information may be that an identifier bit is set in the value of the Gx instance identifier, or a specific value interval is allocated.
  • the Rx instance identifier a identifies the initial offer of this Media Component (which can be thought of as identifying the initial provider of this Media Component).
  • the Gx instance identifier a identifies the initial provision of this PCC rule (which can be considered to be the initial provisioning instance that identifies this PCC rule).
  • Step 504 The PCRF provides the PCC rule formulated after the policy decision to the PCEF.
  • Step 505 After the PCEF installs the PCC rule, the PCEF returns a confirmation message.
  • Step 506 The PCEF initiates a resource reservation process according to the PCC rule.
  • Step 507 After the PCRF provides the PCEF to the PCC rule (ie, after step S504), the PCRF receives the updated service information and carries the updated media component. (ie a new instance of the media component provided previously). Usually AF only sends media components that need to be updated. The AF can assign a new Rx instance identifier to the updated media component, denoted here as the Rx instance identifier b. AF can also provide complete business information (including updated media components and unupdated media components).
  • Step 508 After the PCRF saves the service information, it returns an acknowledgement message.
  • Step 509 The PCRF performs policy decision according to the network policy, service information, and user subscription information, and updates the previous PCC rule. If the updated media component is carried, the following steps are also performed: if a new Sub Component is added and a new PCC rule is created for it, the PCRF assigns a Gx instance identifier b to the PCC rule; if a new Sub Component is added and The Sub Component updates the previous PCC rule, and the PCRF assigns a new Gx instance identifier b to the PCC rule; if the existing Sub Component is modified and the previous PCC rule is updated, the PCRF assigns a new Gx reference to the PCC rule. b.
  • the PCC rules carry the same Gx instance identifier.
  • the value of the Gx instance identifier b may be the same as the value of the Rx instance identifier b, or the value of the Gx instance identifier b and the value of the Rx instance identifier b may be derived from each other. That is, the Gx instance identifier b and the Rx instance identifier b are one-to-one correspondence.
  • the Gx instance identifier carries the indication information indicating the policy decision triggered by the service information (that is, the Gx instance identifier corresponds to one Rx instance identifier).
  • the indication information when the indication information is actually implemented, it may be that an identifier bit is set in the value of the Gx instance identifier, or a specific value interval is allocated.
  • the Rx instance identifier b identifies the first update of this Media Component (which can be thought of as identifying the first update instance of this Media Component).
  • the Gx/Gxx instance identifier b identifies the first update of this PCC rule (which can be considered to be the first update instance identifying this PCC).
  • Step 510 The PCRF provides the updated PCC rule to the PCEF, and the PCC rule carries the Gx instance identifier b.
  • Step 511 After the PCEF installs the PCC rule, the PCEF returns a confirmation message.
  • Step 512 The PCRF initiates a resource reservation process according to the installed PCC rule.
  • Step 513 After step 510, the PCRF may need to further update the PCC rules for some reason (for example, the network policy changes, the user subscription changes, the access network changes, etc.), the PCRF makes policy decisions, updates the PCC rules, and
  • the PCC rule carries a new Gx instance identifier (here denoted as a Gx instance identifier ').
  • the Gx instance identifier indicates that the policy decision triggered by the non-service information is carried out (that is, the Gx instance identifier does not correspond to an Rx instance identifier).
  • the identifier may be set in the value of the Gx instance identifier, or a specific value interval may be allocated (that is, the Gx instance identifier corresponding to the Rx instance identifier and the Gx corresponding to the Rx instance identifier).
  • the instance IDs belong to different value ranges.
  • Gx The instance identification ' identifies the second update of this PCC rule (which can be considered as the second update instance identifying this PCC rule).
  • Step 514 The PCRF provides the updated PCC rule to the PCEF, and the PCC rule carries the Gx instance identifier ';
  • Step 515 After the PCEF installs the PCC rule, the PCEF returns a confirmation message.
  • Step 516 The PCRF initiates a resource reservation process according to the installed PCC rules.
  • Step 517 After that, the PCEF receives the response message of the resource reservation process, indicating that the resource reservation fails.
  • Step 518 The PCEF sends an event notification to the PCRF, carrying a resource reservation failure indication (carried by the Event-Trigger AVP), and a corresponding PCC rule (carried by the Charging-Rule-Report AVP).
  • the failure indication received by the PCEF is the response of the resource reservation process initiated by the PCEF in step 506
  • the message sent by the PCEF to the PCRF further carries the Gx instance identifier a (using the Reference-Number AVP)
  • the failure indication received by the PCEF is the response of the resource reservation process initiated by the PCEF in step 512, and the message sent by the PCEF to the PCRF further carries the Gx instance identifier b (using the Reference-Number AVP);
  • the failure indication received by the PCEF is the response of the resource reservation process initiated by the PCEF in step 516, and the message sent by the PCEF to the PCRF further carries the Gx instance identifier '(with Reference-Number AVP).
  • Step 519 The PCRF returns an acknowledgement message to the PCEF.
  • Step 520 If the PCEF reports that the Gx instance identifier is the Gx instance identifier a or the Gx instance identifier b, the PCRF determines the Rx instance identifier a or the Rx instance identifier b according to the Gx instance identifier a or the Gx instance identifier b. The PCRF sends an event notification to the AF, carrying a resource reservation failure indication (carried by the Specific-Action AVP), and a flow identifier (carried by the Flows AVP). If, in step 514, the PCRF receives the Gx instance identifier a, the Flows AVP carries the corresponding Rx instance identifier a.
  • the Flows AVP carries the corresponding Rx instance identifier b. .
  • the AF can determine which resource information of the provided service information fails to be allocated;
  • Step 521 The AF returns an acknowledgement message to the PCRF.
  • the last embodiment only describes a scenario in which the AF continuously provides 2 times of service information, and the scenario is similar for the case where the AF continuously provides 3 or more scenes.
  • the PCRF is allocated according to the allocation principle of the Rx instance identifier and the Gx instance identifier.
  • the Rx instance identifier and the Gx instance identifier are allocated by the PCRF, and after the resource allocation of the initial service information is failed, the corresponding Rx instance identifier and the Gx instance identifier are reported.
  • the instance identifier may not be assigned when the service information is initially provided. In this way, as long as the instance identifier is not carried in the reported information, it indicates that the resource allocation of the initially provided service information fails.
  • the PCRF is not required to save the actual correspondence between the Gx instance identifier and the Rx instance identifier, but the PCRF may derive the Rx instance identifier according to the Gx instance identifier according to the configured method.
  • the PCRF can also save the correspondence between the Gx reference number and the Rx reference number to implement mapping between each other.
  • the PCRF updates the established PCC rules based on new instances of media components or media subcomponents that may be considered to be new instances of PCC rules based on new instances of media components or media subcomponents.
  • FIG. 9 is a schematic flowchart of a fourth policy control according to Embodiment 4 of the present invention, including the following steps:
  • Step 601 The AF provides service information to the PCRF, where the message carries service information, including one or more media components (carried in the Media-Component-Description AVP).
  • the AF can assign a Rx instance identifier to a media component, which is represented here as an Rx instance identifier a;
  • Step 602 The PCRF returns a confirmation message after saving the service information.
  • Step 603 The PCRF makes a policy decision according to the network policy, service information, and user subscription information, and formulates a PCC rule.
  • the PCRF may need to interact with the SPR to obtain the user's subscription information.
  • the PCRF may formulate a PCC rule according to a media subcomponent (carrying in the Media-Sub-Component AVP) (ie, if a Media-Component-Description AVP carries 2 Media-Sub-Component AVPs)
  • the PCRF will formulate two PCC rules.
  • the PCRF may also aggregate multiple Media Sub Components in a Media Component to generate a PCC rule.
  • the Gx instance identifier is carried in the PCC rule, which is represented by the Gx instance identifier a, and carries the Gxx instance identifier in the QoS rule, which is represented as the Gxx instance identifier a.
  • the Gx instance ID and the Gxx instance ID have the same value. If the PCRF has multiple PCC rules according to a media component, the PCRF carries the same Gx instance identifier in each PCC rule, and the QoS rule carries the same Gxx instance identifier.
  • the value of the Gx/Gxx instance identifier may be the same as the value of the Rx instance identifier, or the value of the Gx/Gxx instance identifier may be derived according to the value of the Rx instance identifier.
  • the Gx/Gxx instance identifier and the Rx instance identifier are in one-to-one correspondence.
  • the Gx/Gxx instance identifier carries the indication information indicating the policy decision triggered by the service information (that is, the Gx/Gxx instance identifier corresponds to one Rx instance identifier).
  • the indication information may be that an identifier bit is set in the value of the Gx instance identifier, or a specific value interval is allocated.
  • the Rx instance identifier a identifies the initial offer of this Media Component (which can be thought of as identifying the initial provider of this Media Component).
  • the Gx/Gxx instance identification a identifies the initial provision of this PCC/QoS rule (which can be considered as an initial provisioning instance identifying this PCC/QoS rule).
  • Step 604 The PCRF provides the PCC rule formulated after the policy decision to the PCEF.
  • Step 605 After the PCEF installs the PCC rule, the PCEF returns an acknowledgement message.
  • Step 606 The PCRF provides a QoS rule to the BBERF.
  • Step 607 The BBERF returns a confirmation message.
  • Step 608 The PCEF initiates a resource reservation process according to the QoS rule.
  • Step 609 After the PCRF provides the BBERF to the QoS rule (ie, after step S606), the PCRF receives the updated service information and carries the updated media component. (ie a new instance of the media component provided previously). Usually AF only sends media description components that need to be updated. AF assigns an Rx instance identifier to a media component, denoted here as the Rx instance identifier b. AF can also provide complete business information (including updated media components and unupdated media components).
  • Step 610 The PCRF returns a confirmation message after saving the service information.
  • Step 611 The PCRF performs policy decision according to the network policy, service information, and user subscription information, and updates the previous PCC rule. If the updated media component is carried, the following steps are performed: if a new Sub Component is added and a new PCC/QoS rule is created for it, the PCRF allocates a Gx instance identifier b for the PCC rule and a Gxx instance identifier b for the QoS rule; If the Sub Component is added and the previous PCC/QoS rules are updated according to the newly added Sub Component, the PCRF assigns a new Gx instance identifier b/Gxx instance identifier b to the PCC/QoS rule; if the existing Sub Component is modified and After updating the previous PCC/QoS rules, the PCRF assigns a new Gx reference to the PCC/QoS rule.
  • the b/Gxx instance identifier b The value of the Gx instance identifier b/Gxx instance identifier b can be taken with the Rx instance identifier b. The value is the same, or the value of the Gx instance identifier b/Gxx instance identifier b and the value of the Rx instance identifier b are mutually derivable. If the PCRF has multiple PCC rules according to a media component, the PCRF carries the same Gx instance identifier in each PCC rule, and the QoS rule carries the same Gxx instance identifier. That is, the Gx instance identifier b/Gxx instance identifier b and the Rx instance identifier b are one-to-one correspondence.
  • the Gx instance identifier b/Gxx instance identifier b carries the indication information indicating the policy decision triggered by the service information (that is, the Gx instance identifier corresponds to one Rx instance identifier).
  • the indication information it may be that an identifier bit is set in the value of the Gx instance identifier, or a specific value interval is allocated.
  • the Rx instance identifier b identifies the first update of this Media Component (which can be thought of as identifying the first update instance of this Media Component).
  • the Gx/Gxx instance identifier b identifies the first update of this PCC/QoS rule (can be considered the first time to identify this PCC/QoS rule) Update the instance).
  • Step 612 The PCRF provides the updated PCC rule to the PCEF, and the PCC rule carries the Gx instance identifier a;
  • Step 613 After the PCEF installs the PCC rule, the PCEF returns a confirmation message.
  • Step 614 The PCRF provides a QoS rule to the BBERF.
  • Step 615 After installing the QoS rule, the BBERF returns an acknowledgement message to the PCRF.
  • Step 616 The PCRF initiates a resource reservation process according to the installed QoS rule.
  • Step 617 After step 614, the PCRF may need to further update the PCC rules for some reason (for example, the network policy changes, the user subscription changes, the access network changes, etc.), and the PCRF makes policy decisions and updates the PCC/QoS rules.
  • the new Gx instance identifier (here denoted as Gx instance identifier ') is carried in the PCC rule, and the QoS rule carries a new Gxx instance identifier (here denoted as Gxx instance identifier ').
  • the Gx/Gxx instance identifier indicates that the policy decision triggered by the non-service information is triggered (that is, the Gx/Gxx instance identifier does not correspond to an Rx instance identifier).
  • the indication information when the indication information is actually implemented, it may be that an identifier bit is set in the value of the Gx/Gxx instance identifier, or a specific value interval is allocated (that is, the Gx/Gxx instance identifier corresponding to the Rx instance identifier and the Rx instance are not associated with the Rx instance identifier.
  • the corresponding Gx/Gxx instance identifiers belong to different value ranges.
  • the Gx/Gxx instance identifies 'identifies the second update of this PCC/QoS rule (which can be considered as the second update instance identifying this PCC/QoS rule).
  • Step 618 The PCRF provides the updated PCC rule to the PCEF, and the PCC rule carries the Gx instance identifier ';
  • Step 619 After the PCEF installs the PCC rule, the PCEF returns a confirmation message.
  • Step 620 The PCRF provides a QoS rule to the BBERF.
  • Step 621 After the BBERF installs the QoS rule, it returns an acknowledgement message to the PCRF.
  • Step 622 The PCRF initiates a resource reservation process according to the installed BBERF rule.
  • Step 623 After that, the BBERF receives the response message of the resource reservation process, indicating that the resource reservation fails.
  • Step 624 The BBERF sends an event notification to the PCRF, carrying a resource reservation failure indication. (carried with the Event-Trigger AVP) and the corresponding QoS rules (carried with the QoS-Rule-Report AVP). If the failure indication received by the BBERF is the response of the resource reservation process initiated by the BBERF in step 623, the message sent by the BBERF to the PCRF further carries the Gxx instance identifier a (using the Reference-Number AVP); In step 623, the failure indication received by the BBERF is the response of the resource reservation procedure initiated by the BBERF in step 616, and the message sent by the BBERF to the PCRF further carries the Gxx instance identifier b (using the Reference-Number AVP).
  • the message sent by the BBERF to the PCRF further carries the Gx instance identifier '(with Reference-Number AVP) where Reference- The Number AVP is carried in the QoS-Rule-Report AVP.
  • Step 625 The PCRF returns an acknowledgement message to the BBERF.
  • Step 626 If the BBERF reports that the Gxx instance identifier is the Gxx instance identifier a or the Gxx instance identifier b, the PCRF determines the Rx instance identifier a or the Rx instance identifier b according to the Gxx instance identifier a or the Gxx instance identifier b. The PCRF sends an event notification to the AF, carrying a resource reservation failure indication (carried by the Specific-Action AVP), and a flow identifier (carried by the Flows AVP). If the PCRF receives the Gxx instance identifier a in step 424, the Flows AVP carries the corresponding Rx instance identifier a.
  • the Flows AVP carries the corresponding Rx instance identifier b. .
  • the AF can determine which resource information of the provided service information fails to be allocated;
  • Step 627 The AF returns an acknowledgement message to the PCRF.
  • the last embodiment only describes a scenario in which the AF continuously provides 2 times of service information, and the scenario is similar for the case where the AF continuously provides 3 or more scenes.
  • the PCRF is allocated according to the allocation principle of the Rx instance identifier and the Gx instance identifier.
  • the instance identifier may not be assigned when the service information is initially provided. In this way, as long as the instance identifier is not carried in the reported information, it indicates that the resource allocation of the initially provided service information fails.
  • the PCRF updates the established PCC rules based on new instances of media components or media subcomponents that may be considered to be new instances of PCC rules based on new instances of media components or media subcomponents.
  • the Gx/Gxx instance identifier since the Gx/Gxx instance identifier carries the indication information for triggering the policy decision by the service information or the indication information of the Rx instance identifier corresponding to the Gx/Gxx instance identifier, these Gx/Gxx instance identifiers and other The Gx/Gxx instance ID of the PCC/QoS rule that is determined by the policy decision triggered by the non-service information is differentiated (different identifiers are used for distinguishing or different value intervals are used), so the policy decision is triggered by the service information.
  • the policy or algorithm that carries the Gx/Gxx instance identifier in the PCC/QoS rule that can be configured by the PCRF is determined by the Rx instance identifier.
  • the PCRF After the PCRF receives the Gx/Gxx instance identifiers reported by the PCEF/BBERF, the PCRF can also be based on the same Configure to determine the corresponding Rx instance ID. In this way, the PCRF does not need to save a correspondence between the Rx instance identifier and the Gx/Gxx instance identifier.
  • the media component or media subcomponent that is initially provided or subsequently updated may be considered as a media component instance or a media subcomponent instance;
  • the PCC rules or QoS rules initially provided or subsequently updated may be considered to be A PCC rule instance or QoS rule instance.
  • the Rx reference number is the media component instance identifier or the media subcomponent instance identifier
  • the Gx/Gxx reference number is the PCC/QoS rule instance identifier.
  • the PCRF after the PCRF receives the first indication message indicating that the PCC/QoS rule instance fails to execute (ie, the resource allocation fails), and determines, according to the first instance identifier in the first message, the corresponding A second instance identification of a media component instance or a media subcomponent instance of a PCC/QoS rule instance.
  • the PCRF sends a second indication message to the AF, and is used to indicate that the service instance resource corresponding to the media component instance or the media sub-component instance fails to be allocated to the AF, where the second message carries the second instance identifier.
  • the PCRF triggers the event for the successful resource allocation to the PCEF/BBERF.
  • the BBERF/PCEF also sends a first message to the PCRF by using a similar process, indicating that the PCC/QoS rule instance is successfully executed (ie, the resource allocation is successful), and according to the first in the first message.
  • the instance identification determines a corresponding second instance identification of the media component instance or media subcomponent instance used to formulate the PCC/QoS rule instance.
  • the PCRF sends a second indication message to the AF, and is used to indicate that the service instance resource corresponding to the media component instance or the media sub-component instance is successfully assigned to the AF, where the second message carries the second instance identifier.
  • the PCRF receives the first indication message indicating the execution result (resource allocation result) of the PCC/QoS rule instance, and determines the corresponding PCC/QoS according to the first instance identifier in the first message.
  • the PCRF sends a second indication message to the AF, and is used to indicate to the AF the service instance resource allocation result corresponding to the media component instance or the media sub-component instance, where the second message carries the second instance identifier.
  • the disclosed method and smart device may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner such as: multiple units or components may be combined, or Can be integrated into another The system, or some features can be ignored or not executed.
  • the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.
  • the units described above as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units, that is, may be located in one place or distributed to multiple network units; Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one second processing unit, or each unit may be separately used as one unit, or two or more units may be integrated into one unit;
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • Embodiments of the present invention also provide a storage medium.
  • the above storage medium may be configured to store program code for performing the following steps:
  • S1 Receive a first message for indicating a resource allocation result, and determine a corresponding second instance identifier according to the first instance identifier in the first message, where the first instance identifier is an instance corresponding to the policy rule update for performing resource allocation. And the second instance identifier is an instance identifier corresponding to the media component instance or the media subcomponent instance used to formulate the policy rule;
  • the foregoing storage medium may include, but not limited to, a U disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • mobile hard disk a magnetic disk
  • magnetic disk a magnetic disk
  • optical disk a variety of media that can store program code.
  • the processor performs, according to the stored program code in the storage medium, receiving a first message for indicating a resource allocation result, and determining, according to the first instance identifier in the first message, the corresponding message.
  • a second instance identifier where the first instance identifier is an instance identifier corresponding to a policy rule that performs resource allocation, and the second instance identifier is an instance identifier corresponding to the media component instance or the media subcomponent instance used to formulate the policy rule;
  • the processor sends a second message for indicating a resource allocation result to the application function AF entity according to the stored program code in the storage medium, where the second message carries the second instance identifier.
  • the modules or steps of the above embodiments of the present invention may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices, which may be implemented by computing devices.
  • the executed program code is implemented such that they can be stored in a storage device by a computing device, and in some cases, the steps shown or described can be performed in a different order than here, or they can be
  • Each of the integrated circuit modules is fabricated separately, or a plurality of modules or steps thereof are fabricated into a single integrated circuit module.
  • embodiments of the invention are not limited to any specific combination of hardware and software.
  • a first message for indicating a resource allocation result is received, and a corresponding second instance identifier is determined according to the first instance identifier in the first message, where the first instance identifier is an execution resource.
  • the second message of the second message carries the second instance identifier.

Landscapes

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

Abstract

L'invention concerne un procédé, un appareil et un système de commande de politiques. Le procédé comporte les étapes consistant à: recevoir un premier message servant à indiquer un résultat d'attribution de ressources, et d'après un premier exemple d'identifiant figurant dans le premier message, déterminer un deuxième exemple correspondant d'identifiant, le premier exemple d'identifiant étant un exemple d'identifiant correspondant à un exemple de règle de politique exécutant une attribution de ressources, et le deuxième exemple d'identifiant étant un exemple de composant de média servant à créer l'exemple de règle de politique ou un exemple d'identifiant correspondant à un exemple de sous-composant de média; et envoyer un deuxième message servant à indiquer un résultat d'attribution de ressources à une entité de fonction d'application (AF), le deuxième message transportant le deuxième exemple d'identifiant.
PCT/CN2017/092081 2016-07-18 2017-07-06 Procédé, appareil et système de commande de politiques WO2018014740A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17830374.9A EP3487257A4 (fr) 2016-07-18 2017-07-06 Procédé, appareil et système de commande de politiques
US16/318,274 US10630495B2 (en) 2016-07-18 2017-07-06 Policy control method, apparatus and system

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201610566487 2016-07-18
CN201610566487.9 2016-07-18
CN201610884609.9A CN107634838A (zh) 2016-07-18 2016-10-10 策略控制方法、装置及系统
CN201610884609.9 2016-10-10

Publications (1)

Publication Number Publication Date
WO2018014740A1 true WO2018014740A1 (fr) 2018-01-25

Family

ID=60992947

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/092081 WO2018014740A1 (fr) 2016-07-18 2017-07-06 Procédé, appareil et système de commande de politiques

Country Status (1)

Country Link
WO (1) WO2018014740A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101720112A (zh) * 2009-04-28 2010-06-02 中兴通讯股份有限公司 一种无线资源管理方法与装置
CN102131296A (zh) * 2010-01-15 2011-07-20 中兴通讯股份有限公司 在全业务融合网络中控制资源的方法和系统
CN102136983A (zh) * 2010-01-25 2011-07-27 中兴通讯股份有限公司 在全业务融合网络中控制资源的方法和系统
CN102404319A (zh) * 2011-11-09 2012-04-04 大唐移动通信设备有限公司 一种af会话的处理方法及装置
CN104620536A (zh) * 2012-09-17 2015-05-13 瑞典爱立信有限公司 高可用性、可扩展策略和计费控制系统及用于其的方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101720112A (zh) * 2009-04-28 2010-06-02 中兴通讯股份有限公司 一种无线资源管理方法与装置
CN102131296A (zh) * 2010-01-15 2011-07-20 中兴通讯股份有限公司 在全业务融合网络中控制资源的方法和系统
CN102136983A (zh) * 2010-01-25 2011-07-27 中兴通讯股份有限公司 在全业务融合网络中控制资源的方法和系统
CN102404319A (zh) * 2011-11-09 2012-04-04 大唐移动通信设备有限公司 一种af会话的处理方法及装置
CN104620536A (zh) * 2012-09-17 2015-05-13 瑞典爱立信有限公司 高可用性、可扩展策略和计费控制系统及用于其的方法

Non-Patent Citations (1)

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

Similar Documents

Publication Publication Date Title
EP3664370B1 (fr) Procédé de gestion d'informations de fonction de réseau et dispositif associé
EP3800926B1 (fr) Procédé et dispositif d'alarme
US10481953B2 (en) Management system, virtual communication-function management node, and management method for managing virtualization resources in a mobile communication network
CN108370328B (zh) 一种nfv mano策略描述符的管理方法及装置
CN112468338B (zh) 通信方法、装置和系统
US10609225B2 (en) Charging method, apparatus, and system
US20150215228A1 (en) Methods, systems, and computer readable media for a cloud-based virtualization orchestrator
CN105765921A (zh) 用于利用软件定义网络(sdn)功能进行diameter路由的方法、系统和计算机可读介质
JP2017503421A (ja) ネットワーク機能仮想化ｎｆｖ障害管理の装置、デバイス、および方法
WO2019174000A1 (fr) Procédé et appareil de gestion de service
US11470202B2 (en) Charging method, apparatus, and system
CN109417501B (zh) 网络资源的编排方法和设备
WO2016127612A1 (fr) Procédé et dispositif de gestion de surveillance
US9801229B2 (en) Method for processing service connection in a communication network and device thereof
EP3308500B1 (fr) Procédé et appareil de gestion d'abonnement à des compteurs de politiques
US10630495B2 (en) Policy control method, apparatus and system
CN109547222A (zh) 网络请求的流量统计方法及装置
EP3101926A1 (fr) Procédé de gestion de facturation, noeud de commande de réseau centralisé, noeud de fonction, et système
WO2017107563A1 (fr) Procédé et dispositif de traitement de contrôle de zone d'accès
WO2018014740A1 (fr) Procédé, appareil et système de commande de politiques
CN111512594B (zh) 虚拟网络功能管理方法和装置
EP3266152A1 (fr) Procédé, appareil et système de facturation d'un flux de données dans un réseau sdn
US10412772B2 (en) Methods, systems, and computer readable media for using access point name (APN) independent subscriber bindings
EP3272065B1 (fr) Procédé et appareil pour gérer un abonnement à un compteur de politique
JP6460743B2 (ja) 設定情報生成システム及び設定情報生成方法

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017830374

Country of ref document: EP

Effective date: 20190218