WO2018014740A1

WO2018014740A1 - Policy control method, apparatus and system

Info

Publication number: WO2018014740A1
Application number: PCT/CN2017/092081
Authority: WO
Inventors: 周晓云; 梁爽
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-07-18
Filing date: 2017-07-06
Publication date: 2018-01-25

Abstract

Published are a policy control method, apparatus and system. The method comprises: receiving a first message for indicating a resource allocation result, and according to a first example identifier in the first message, determining a corresponding second example identifier, wherein the first example identifier is an example identifier corresponding to a policy rule example executing resource allocation, and the second example identifier is a media component example for making the policy rule example or an example identifier corresponding to a media sub-component example; and sending a second message for indicating a resource allocation result to an application function (AF) entity, wherein the second message carries the second example identifier.

Description

Strategy control method, device and system

Technical field

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.

Background technique

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). As shown in Figure 1, 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). At the same time, 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. In addition, the PCEF and the Traffic Detection Function (TDF) can perform application detection and control functions according to the PCC rules (PCEF) or the Application and Detection Control (ADC) issued by the PCRF. Including, the online charging system (Online Charging System, OCS for short), the offline charging system (Offline Charging System, referred to as OFCS), the Rx, Nt, Sp, Gxx, etc. between the modules are the communication interfaces between the modules.

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);

Authentication and authorization request sent by the AF to the PCRF to provide service information (Authentication and The format of the authorization request (AAR) message is as follows: one AAR message can have zero, one or more media description components:

The format of the Media-Component-Description AVP is as follows. A Media-Component-Description AVP can carry zero, one or more Media-Sub-Component AVPs. Where 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. In this process, 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:

The format of Flows AVP is as follows. Where Media-Component-Number is used to represent an IP stream:

Step 217: The AF returns an acknowledgement message to the PCRF.

In the above process, 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. Similarly, 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. When the resource reservation corresponding to one of the service information updates fails, the AF will not know which resource information update corresponding to the resource reservation fails.

Correspondingly, the AF is also unable to prepare to know which resource information update corresponding resource reservation is successful.

Summary of invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the invention provides a policy control method, device and system, so that the AF correctly knows the resource reservation result.

According to an embodiment of the present invention, a policy control method is provided, 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, and 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. Transmitting, to the application function AF entity, a second message indicating a resource allocation result, where the second message carries the second instance identifier.

In an embodiment, 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.

In an embodiment, 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.

In an embodiment, the indication information is an identifier bit or a specific value interval in the value of the first instance identifier.

In an embodiment, before determining the second instance identifier according to the first instance identifier in the first message, the method further includes one of the following:

Receiving the second instance identifier assigned by the AF entity;

Assigning the second instance identification to the media component instance or the media subcomponent instance.

In an embodiment, 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.

In an embodiment, 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.

In an embodiment, 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.

In an embodiment, 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.

In an embodiment, 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.

In an embodiment, the first message further carries a rule identifier of the policy rule instance, and 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.

In an embodiment, after assigning the second instance identifier to the media component 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.

According to another embodiment of the present invention, a policy control apparatus is provided, 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.

In an embodiment, 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.

In an embodiment, 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.

In an embodiment, 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.

In an embodiment, 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.

In an embodiment, 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.

According to still another embodiment of the present invention, a policy control system is provided, 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 media component instance or the media sub-component instance corresponding to the instance identifier; the sending module, configured to send, to the application function AF entity, a second message for indicating a resource allocation result, where the second message carries the second instance identifier; The AF entity is set to: receive the second message.

In an embodiment, 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.

According to still another embodiment of the present invention, a storage medium is also provided. The storage medium is arranged to store program code for performing the following steps:

Receiving a first message for indicating a resource allocation result, and determining 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 An instance identifier, where 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;

Sending, to the application function AF entity, a second message indicating a resource allocation result, where the second message carries the second instance identifier.

According to the embodiment of the present invention, 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. An instance identifier corresponding to the assigned policy rule instance, where 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 instance, and is sent to the application function AF entity to indicate resource allocation The second message of the second message carries the second instance identifier. The AF can be made to know the resource reservation result correctly.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

1 is a schematic diagram of a PCC architecture defined by 3GPP;

2 is a flow chart of AF request network QoS guarantee;

3 is a flowchart of a policy control method according to an embodiment of the present invention;

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;

7 is a schematic flowchart of policy control according to Embodiment 2 of the present invention;

FIG. 8 is a schematic flowchart of a third policy control according to Embodiment 3 of the present invention; FIG.

FIG. 9 is a schematic flowchart of a policy control according to Embodiment 4 of the present invention.

Detailed

The present application will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

It should be noted that the terms "first", "second" and the like in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or order.

Example 1

In this embodiment, a policy control method running in the network architecture shown in FIG. 1 is provided. 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. An instance identifier, where 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;

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.

In this embodiment, 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.

And 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.

In an embodiment of the present invention, an Instance Identifier may also be referred to as an Update Counter, a sequence number, a Reference Number, or an Update Instance identifier.

In an embodiment, the execution body of the above steps may be a PCRF or the like, but is not limited thereto.

In an embodiment, 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.

In an embodiment, 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.

In an embodiment, before determining the second instance identifier according to the first instance identifier in the first message, the second instance identifier may also be allocated by using the external node or itself, including:

Receiving a second instance identifier assigned by the AF entity; or

Assign a second instance ID to the media component instance or media subcomponent.

In the embodiment according to the embodiment, when receiving the second instance identifier allocated by the AF entity, the method may further include:

S11. Receive a second instance identifier that is allocated by the AF entity to the media component instance.

S12. Create one or more instances of the PCC rule according to the media component instance, where the first instance identifier corresponding to the second instance identifier is carried in the one or more PCC rule instances.

In an embodiment, 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.

In an embodiment according to this embodiment, 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. In an embodiment, after the second instance identifier is assigned to the media component 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.

In an 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.

In an embodiment, in the embodiment, 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.

In an embodiment, the first message further carries a rule identifier of the policy rule instance, and 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.

Through the description of the above embodiments, those skilled in the art can clearly understand that 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. Based on this rationale 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. The method of various embodiments of the present invention (which may be a cell phone, a computer, a server, or a network device, etc.).

Example 2

In the embodiment, a policy control device and a system are provided to implement the foregoing embodiments and implementation manners, which have not been described again. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although 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.

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. An instance identifier corresponding to the policy rule instance, where 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 instance;

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.

In an embodiment, 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.

In an embodiment, 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.

In an embodiment, 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.

In an embodiment, 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.

In an embodiment, 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.

In an embodiment, the first message further carries a rule identifier of the policy rule instance, and 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:

Including the policy and charging rule function PCRF entity 50 and AF entity 52,

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. An instance identifier corresponding to the policy rule instance, where the second instance identifier is an instance identifier corresponding to the media component instance or the media subcomponent instance update used to formulate the policy rule instance;

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.

In an embodiment, 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.

It should be noted that each of the above modules may be implemented by software or hardware. For the latter, 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.

Example 3

This embodiment provides a method for policy control, so that the AF can correctly learn the resource reservation result.

The method for policy and charging control provided in this embodiment includes:

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.

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.

The second instance identifier is assigned by an application function or by a PCRF.

When the second instance identifier is allocated by an application function, 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.

When the second instance identifier is allocated by the PCRF, the PCRF is a second instance identifier for assigning the same value to the media subcomponent instance for formulating the same PCC rule instance.

The following is a detailed description of the present embodiment in conjunction with the actual scenario, including the following four embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

Embodiment 1

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. In this process, the PCRF may need to interact with the SPR to obtain the user's subscription information. In the process of formulating PCC rules by the PCRF, 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. If 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). At the same time, 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. Similarly, 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). 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 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. 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.

In an embodiment, after the PCRF allocates the Rx instance identifier to the Media-Sub-Component AVP, 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). Usually 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. If the existing Sub Component is modified and the previous PCC rule is updated, 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. Similarly, 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). 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 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. 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.

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). When the indication information is actually implemented, 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. The Gx instance identifier 'identifies the second update of this PCC rule (can be considered to be the first update instance identifying this PCC rule)

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). If 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); In step 617, 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). The Reference-Number AVP is carried in the Charging-Rule-Report 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). If, in step 614, the PCRF receives the Gx instance identifier a, 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. For each service update, the PCRF is allocated according to the allocation principle of the Rx instance identifier and the Gx instance identifier.

In the foregoing embodiment, when the AF initially provides the service information, 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. In other embodiments, 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.

In the foregoing embodiment, 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. Of course, 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.

Embodiment 2

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. In this process, the PCRF may need to interact with the SPR to obtain the user's subscription information. In the process of formulating PCC rules by the PCRF, 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. If 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). At the same time, 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. And 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). 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 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. 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.

In an embodiment, after the PCRF allocates the Rx instance identifier to the 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). Usually 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. Identifying b, and assigning a new Rx instance identifier b to all Sub Components corresponding to the PCC/QoS rule; if modifying the existing Sub Component and updating the previous PCC/QoS rule, the PCRF assigns a new Gx to the PCC/QoS rule. Referring to the back number b/Gxx instance identifier b, 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). 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. 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. And 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). 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). If the failure indication received by the BBERF is the response of the resource reservation procedure initiated by the BBERF in step 422, 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. If the PCRF receives the Gxx instance identifier b, the Flows AVP carries the corresponding Rx instance identifier b. . In this way, according to the Rx instance identifier a and the 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.

In the foregoing embodiment, when the AF initially provides the service information, the Rx instance identifier and the Gx instance identifier/Gxx instance identifier allocated by the PCRF, and after the resource allocation failure of the initial provision of the service information fails, the corresponding Rx instance identifier is reported and Gx instance ID / Gxx instance ID. In other embodiments, 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.

Embodiment 3

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. In this process, the PCRF may need to interact with the SPR to obtain the user's subscription information. In the process of formulating PCC rules by the PCRF, 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. At the same time, 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. Similarly, 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). 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 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. Similarly, if the PCRF formulates multiple PCC rules according to the updated media component, 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. Similarly, 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). 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). When the indication information is actually implemented, 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). If 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); In step 517, 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). The Reference-Number AVP is carried in the Charging-Rule-Report 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. 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 fails to be allocated;

Step 521: The AF returns an acknowledgement message to the PCRF.

In the foregoing embodiment, 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. Of course, 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.

Embodiment 4

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. In this process, the PCRF may need to interact with the SPR to obtain the user's subscription information. In the process of formulating PCC rules by the PCRF, 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. That is, the Gx/Gxx instance identifier and the Rx instance identifier are in one-to-one correspondence. And 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). 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 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 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. 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). When the indication information is 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/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. And 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). 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). If the failure indication received by the BBERF is the response of the resource reservation process initiated by the BBERF in step 622, 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. If the PCRF receives the Gxx instance identifier b, the Flows AVP carries the corresponding Rx instance identifier b. . In this way, according to the Rx instance identifier a and the 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.

In all of the above embodiments, 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. 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.

In all of the above embodiments, 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, and the Gx/Gxx reference number is the PCC/QoS rule instance identifier.

In the above example, only the flow of the Gx/Gxx interface (ie, the interaction between the PCRF and the PCEF or the PCRF and the BBERF) can implement the PCRF to obtain information on which PCC/QoS rule instance fails to execute. It can be applied to the scenario where the PCC/QoS rule is not triggered by the service information and the scenario triggered by the service information.

In all of the above examples, 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.

Correspondingly, if the AF subscribes to the PCRF for a special action of the successful resource allocation indication, the PCRF triggers the event for the successful resource allocation to the PCEF/BBERF. Then, after the PCC/QoS rule instance is successfully executed, 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.

In summary, after 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 second instance ID of the media component instance or media subcomponent instance of the rule instance. 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.

In the several embodiments provided by the present invention, it should be understood that the disclosed method and smart device may be implemented in other manners. The device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, 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. In addition, 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.

In addition, 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.

Example 4

Embodiments of the present invention also provide a storage medium. In this embodiment, 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;

S2. Send a second message to the application function AF entity to indicate a resource allocation result, where the second message carries the second instance identifier.

In this embodiment, 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. A variety of media that can store program code.

In an embodiment, in this embodiment, 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;

In an embodiment, in the embodiment, 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. .

For examples in this embodiment, reference may be made to the examples described in the foregoing embodiments and implementation manners, and details are not described herein again.

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. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.

The above description is only for the embodiments of the present invention, and is not intended to limit the present application, and various changes and modifications may be made by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this application are intended to be included within the scope of the present application.

Industrial applicability

According to the embodiment of the present invention, 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. An instance identifier corresponding to the assigned policy rule instance, where 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 instance, and is sent to the application function AF entity to indicate resource allocation The second message of the second message carries the second instance identifier. Through the embodiment of the present invention, the AF can correctly learn the resource reservation result.

Claims

A policy control method, including:

Receiving a first message for indicating a resource allocation result, and determining 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 An instance identifier, where 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;

Sending, to the application function AF entity, a second message indicating a resource allocation result, where the second message carries the second instance identifier.
The method of claim 1, wherein the receiving the first message for indicating a resource allocation result comprises:

Receiving a first message sent by the PCEF entity for indicating a resource allocation result by the policy and charging execution function; or

Receiving a first message sent by the BBERF entity sent by the bearer binding and event reporting function to indicate the resource allocation result.
The method according to claim 1, wherein the first instance identifier carries indication information of a service information triggering policy decision or indication information of the second instance identifier corresponding to the first instance identifier.
The method according to claim 3, wherein the indication information is an identifier bit or a specific value interval in the value of the first instance identifier.
The method of claim 1, wherein the method further comprises one of: before determining the second instance identification according to the first instance identifier in the first message:

Receiving the second instance identifier assigned by the AF entity;

Assigning the second instance identification to the media component instance or the media subcomponent instance.
The method of claim 5, wherein the receiving the second instance identifier assigned by the AF entity comprises:

Receiving, by the AF entity, the second instance identifier allocated by the media component instance;

The method further includes:

Forming one or more policy and charging control 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 method of claim 6 wherein said formulating one or more PCC rules based on said media component instance comprises:

When the PCC rule instance is configured according to the media component instance, when the media component instance carries multiple media subcomponents, the multiple media subcomponents are aggregated to formulate a PCC rule instance; or

The first instance identifier is carried in each PCC rule instance when the plurality of PCC rule instances are defined by the media component instance.
The method of claim 5, wherein the assigning the second instance identifier to the media component instance or the media subcomponent instance comprises:

Assigning the second instance identifier to the media component instance if the PCC rule instance is defined 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 identifier is assigned to the media subcomponent instance.
The method of claim 1, wherein before receiving the first message indicating the resource allocation result, the method further comprises:

Assigning a first instance identifier to the PCC rule instance, wherein the first instance identifier is determined according to the second instance identifier.
The method according to any one of claims 1 to 9, wherein the relationship between the second instance identifier and the first instance identifier satisfies 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 method according to claim 1, wherein the first message further carries a rule identifier of the policy rule instance, and the second message further carries an identifier of the media component instance or an identifier of the media subcomponent instance The rule identifier is used to determine the media component instance or the media subcomponent instance.
The method of claim 8, wherein after the assigning the second instance identifier to the media component instance, the method further comprises:

Returning the second instance identification to the AF and providing an identification of the media component instance or media subcomponent instance.
A policy control device comprising:

The first receiving module 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 performed An instance identifier corresponding to the policy rule instance of the resource allocation, where 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 instance;

And a sending module, 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 apparatus of claim 13, wherein the first receiving module comprises:

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 apparatus of claim 13 further comprising:

The second receiving module is configured to receive, before the first receiving module determines the second instance identifier according to the first instance identifier in the first message, the second instance identifier that is allocated by the AF entity; or,

An allocation module configured to assign the second instance identification to the media component instance or the media subcomponent instance.
The apparatus of claim 15, wherein the second receiving module is configured to: receive The second instance identifier assigned by the AF entity to the media component instance;

The device also includes:

a rule module, configured to: create one or more PCC rule instances according to the media component instance, where the one or more PCC rule instances carry the first instance identifier corresponding to the second instance identifier .
The apparatus according to claim 15, wherein said allocating module is configured to: assign a second instance identifier to said media component instance if said PCC rule instance is formulated according to a media component instance; or, if according to one or The plurality of media subcomponent instances formulate a PCC rule instance, and the second instance identifier is assigned to the media subcomponent instance.
The device according to claim 13, wherein the first instance identifier carries indication information of a service information triggering policy decision or indication information of the second instance identifier corresponding to the first instance identifier.
The apparatus according to claim 18, wherein the indication information is an identifier bit or a specific value interval in the value of the first instance identifier.
The apparatus according to claim 13, wherein the first message further carries a rule identifier of the policy rule instance, and the second message further carries an identifier of the media component instance or an identifier of the media subcomponent instance The rule identifier is used to determine the media component instance or the media subcomponent instance.
The apparatus according to claim 17, wherein the sending module is further configured to: after the assigning module assigns the second instance identifier to the media component instance, return the second instance to the AF Identify and provide an identification of the media component instance or media subcomponent instance.
A policy control system includes a policy and charging rule function PCRF entity and an AF entity, wherein

The PCRF entity includes:

The first receiving module 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 performed The instance identifier corresponding to the policy rule instance of the resource allocation, and the second instance identifier An instance identifier corresponding to a media component instance or a media subcomponent instance used to formulate the policy rule instance;

a sending module, 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 is arranged to receive the second message.
The system of claim 22 wherein

The AF entity is further configured to assign the second instance identifier; or

The PCRF entity is further configured to assign the second instance identification to the media component instance or the media subcomponent instance.