WO2016206071A1

WO2016206071A1 - Bearer binding method and associated equipment

Info

Publication number: WO2016206071A1
Application number: PCT/CN2015/082443
Authority: WO
Inventors: 何光伟
Original assignee: 华为技术有限公司
Priority date: 2015-06-26
Filing date: 2015-06-26
Publication date: 2016-12-29
Also published as: CN106664614A; CN106664614B

Abstract

The present invention discloses a bearer binding method and associated equipment, dynamically allocating a network resource and increasing a utilization rate of the network resource, while decreasing signaling interactions in a Gx interface, reducing signaling load, and increasing interaction efficiency. In one embodiment of the invention, the method comprises: receiving, by a policy and charging enforcement function (PCEF), a message including a bearer binding latency indication and a dynamic rule carrying a service identifier; postponing, by the PCEF and according to the bearer binding latency indication, a bearer binding process; monitoring, by the PCEF, for a service corresponding to the service identifier in a session; upon detecting startup of the service corresponding to the service identifier, performing, by the PCEF and according to a quality of service (QoS) class identifier (QCI) and allocation retention priority (ARP) indicated in the dynamic rule different from a default bearer, the bear binding process and triggering, by the PCEF, establishment of a dedicated bearer so as to directly bind the dynamic rule with the newly established dedicated bearer; deleting, upon termination of the service corresponding to the service identifier and by the PCEF, the dedicated bearer so as to cancel bearer binding associated with the dynamic rule; and re-triggering, by the PCEF, service detection of the service corresponding to the service identifier in the session.

Description

Bearer binding method and related equipment

Technical field

The present invention relates to the field of communications, and in particular, to a method and related device for bearer binding.

Background technique

With the development of the mobile Internet, more and more users of mobile data services, traffic is getting larger and larger, and many new topics have emerged. For example, how to protect the user experience of VIP customers and provide differentiated services; how to properly control the long-term occupation of wireless resources by timely messaging services (such as QQ, Fetion, etc.); how to effectively control the unlimited bandwidth users in the monthly subscription, which does not significantly affect Its user experience further reduces the impact on other users' experience during a specific period of time; how to protect high-value users such as streaming media; how to control low-value businesses such as P2P, and so on. Policy Control and Charging (PCC) in the 3rd Generation Partnership Project (3GPP) can be used to solve these problems.

The PCC architecture is mainly composed of a Policy and Charging Rules Function (PCRF), a Policy and Charging Enforcement Function (PCEF), and a service policy providing function entity (in conjunction with its own service platform). Set) These three parts are composed. During the work, the PCRF makes a decision based on the user's subscription information, service information, or user status, generates a control policy, and then sends the control policy to the PCEF. The PCEF installs the control policy on the default bearer. In order to make the policy control more flexible, the PCRF can also generate dynamic rules based on the service state to generate a QoS Class Identifier (QCI) and/or an Allocation Retention Priority (ARP) different from the default bearer. Proprietary bearer.

To implement the binding of dynamic rules, the application detection and control (ADC) scenario is currently controlled by sending traffic detection related events. For example, at present, the allocation and bearer of dynamic rules in an ADC scenario The way to bind is:

1. The PCRF initially sends a dynamic rule carrying an application identifier (APP ID), and the QCI and ARP of the rule are the same as the default bearer.

2. The PCEF performs bearer binding, and the dynamic rule is installed on the default bearer.

3. After the PCRF detects the APPLICATION START event reported by the PCEF, Update the QCI and ARP of the dynamic rule carrying the application identifier, and the updated QCI and/or ARP are different from the default bearer;

4. The PCEF performs bearer binding based on the updated QCI and ARP, triggering the creation of a dedicated bearer, and the updated dynamic rules are bound to the dedicated bearer to provide a dedicated bearer guarantee for the ongoing service;

After the PCRF detects the service STOP event reported by the PCEF, the QCI and the ARP carrying the dynamic rule of the application identifier are updated, and the updated QCI and/or ARP are the same as the default bearer.

The PCEF performs bearer binding based on the updated QCI and ARP. The rule is re-bound to the default bearer. The proprietary bearer is deleted because there is no valid rule. After the service is stopped, the private bearer does not need to be reserved.

However, the binding and unbinding of the dynamic rules are controlled by the service detection related events, and the Gx interface needs to perform multiple signaling interactions to achieve the purpose of dynamically allocating network resources, thereby increasing the signaling burden and reducing the interaction efficiency.

Summary of the invention

The embodiments of the present invention provide a bearer binding method and related equipment, which are used to dynamically allocate network resources, improve network resource utilization, reduce signaling interaction of Gx interfaces, reduce signaling load, and improve interaction efficiency.

A first aspect of the embodiments of the present invention provides a method for bearer binding, including:

The policy and charging enforcement function entity PCEF receives the message that is sent by the policy and charging rule function entity PCRF and includes a delay bearer binding indication and a dynamic rule, where the dynamic rule carries a service identifier, and the QCI in the dynamic rule And the ARP is different from the default bearer, and the delayed bearer binding indication is used to indicate that the PCEF performs bearer binding on the dynamic rule only when the service corresponding to the service identifier is detected;

The PCEF performs bearer binding according to the delay bearer binding indication, and performs service detection on the service corresponding to the service identifier in the session scope;

When the PCEF detects that the service corresponding to the service identifier starts, the bearer binding is performed based on the QCI and the ARP in the dynamic rule, and the creation of the dedicated bearer is triggered, so that the dynamic rule is bound to the newly created special Have a bearing;

When the PCEF detects that the service corresponding to the service identifier ends, the dedicated bearer is deleted, the bearer binding of the dynamic rule is revoked, and the service identifier corresponding to the service identifier is retriggered in the session scope. The steps of the business to conduct business inspection.

With reference to the first aspect of the embodiments of the present invention, in a first implementation manner of the first aspect of the embodiments, the dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier.

With reference to the first aspect of the embodiment of the present invention or the first implementation manner of the first aspect, in the second implementation manner of the first aspect of the embodiment, the service identifier is an application identifier, and the service corresponding to the service identifier Identify the corresponding application for the application;

The performing service detection on the service corresponding to the service identifier in the session scope includes:

Application detection is performed on the application corresponding to the application identifier in the session scope.

With reference to the second implementation manner of the first aspect of the embodiments of the present disclosure, in a third implementation manner of the first aspect of the embodiments, the message further includes a mute instruction, where the mute instruction is used to indicate service detection related The event does not need to generate signaling interactions;

And when the PCEF detects that the service corresponding to the service identifier starts, performing bearer binding and triggering to create a dedicated bearer based on the QCI and the ARP in the dynamic rule, specifically:

When the PCEF detects that the application corresponding to the application identifier starts, according to the muting indication, the PCRF application start event is not notified, and the bearer binding is performed based on the QCI and the ARP in the dynamic rule, and the creation of the dedicated bearer is triggered. ;

And deleting, when the PCEF detects that the service corresponding to the service identifier ends, deleting the dedicated bearer, specifically:

When the PCEF detects that the application corresponding to the application identifier ends, according to the mute indication, the PCRF application end event is not notified, and the dedicated bearer is deleted.

A second aspect of the embodiments of the present invention provides a method for bearer binding, including:

The PCRF sends a message including a delayed bearer binding indication and a dynamic rule to the PCEF, where the dynamic rule carries a service identifier, and the QCI and/or ARP in the dynamic rule is different from the default bearer, and the delay bearer The binding indication is used to indicate that the PCEF performs bearer binding on the dynamic rule only when the service corresponding to the service identifier is detected.

With reference to the second aspect of the embodiments of the present invention, the first implementation manner of the second aspect of the embodiment of the present invention The dynamic rule further includes a charging and policy control parameter for the service plan corresponding to the service identifier.

With reference to the second aspect of the embodiment of the present invention or the first implementation manner of the second aspect, in the second implementation manner of the second aspect of the embodiment, the service identifier is an application identifier, or a flow information.

With reference to the second aspect of the embodiment of the present invention or the first implementation manner of the second aspect, in a third implementation manner of the second aspect of the embodiment, the service identifier is an application identifier, and the message further includes The instruction, the mute instruction is used to indicate that the service detection related event does not need to generate a signaling interaction.

A third aspect of the embodiments of the present invention provides a PCEF, including:

a receiving module, configured to receive, by the PCRF, a message that includes a delayed bearer binding indication and a dynamic rule, where the dynamic rule carries a service identifier, where the QCI and/or the ARP in the dynamic rule are different from the default bearer. The delay bearer binding indication is used to indicate that the PCEF performs bearer binding on the dynamic rule only when the service corresponding to the service identifier is detected;

The detecting module is configured to perform the service detection on the service corresponding to the service identifier in the session scope according to the delay bearer binding indication in the message received by the receiving module;

a bearer binding module, configured to: when the detecting module detects that the service corresponding to the service identifier starts, perform bearer binding based on QCI and ARP in the dynamic rule, and trigger to create a dedicated bearer, so that the dynamic The rules are bound to the newly created private bearer;

The binding revocation module is configured to delete the dedicated bearer when the service corresponding to the service identifier is detected, cancel the bearer binding of the dynamic rule, and re-trigger the detection module.

With reference to the third aspect of the embodiments of the present invention, in a first implementation manner of the third aspect, the dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier.

With reference to the third aspect of the embodiment of the present invention or the first implementation manner of the third aspect, in the second implementation manner of the third aspect of the embodiment, the service identifier is an application identifier, and the service corresponding to the service identifier Identify the corresponding application for the application;

The detecting module is configured to perform the application detection on the application corresponding to the application identifier in the session scope according to the delay bearer binding indication in the message received by the receiving module.

With reference to the second implementation manner of the third aspect of the embodiments of the present invention, In a third implementation manner, the message further includes a mute instruction, where the mute instruction is used to indicate that the service detection related event does not need to generate a signaling interaction;

The bearer binding module is specifically configured to: when the detecting module detects that the application corresponding to the application identifier starts, according to the mute indication, does not notify the PCRF application start event, based on the QCI and the dynamic rule ARP performs bearer binding and triggers creation of a dedicated bearer, so that the dynamic rule is bound to the newly created private bearer;

The binding revocation module is specifically configured to: when the end of the application corresponding to the application identifier is detected, not to notify the PCRF application end event according to the mute indication, delete the dedicated bearer, and the dynamic rule is The bearer binding is revoked and the detection module is re-triggered.

A fourth aspect of the embodiments of the present invention provides a PCRF, including:

a sending module, configured to send a message that includes a delayed bearer binding indication and a dynamic rule, where the dynamic rule carries a service identifier, where the QCI and/or ARP in the dynamic rule is different from the default bearer. The delay bearer binding indication is used to indicate that the PCEF performs bearer binding on the dynamic rule only when the service corresponding to the service identifier is detected.

With reference to the fourth aspect of the embodiments of the present invention, in a first implementation manner of the fourth aspect, the dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier.

With reference to the fourth aspect of the embodiments of the present invention and the first implementation manner of the fourth aspect, in the second implementation manner of the fourth aspect of the embodiments, the service identifier is an application identifier, or a flow information.

With reference to any one of the implementation manners of the fourth to fourth aspects of the embodiments of the present invention, in a third implementation manner of the fourth aspect of the embodiments, the message further includes a mute command. The mute command is used to indicate that the service detection related event does not need to generate a signaling interaction.

A fifth aspect of the embodiments of the present invention provides a PCEF, including:

Transceiver, processor and memory;

The processor is configured to perform the following steps by using the operation instruction stored in the memory:

Controlling, by the transceiver, a message that is sent by the PCRF and includes a delay bearer binding indication and a dynamic rule, where the dynamic rule carries a service identifier, where the QCI and/or ARP in the dynamic rule is different from the default bearer. The delay bearer binding indication is used to indicate that the PCEF performs bearer binding on the dynamic rule only when the service corresponding to the service identifier is detected;

According to the delay bearer binding indication, the bearer binding is not performed temporarily, and the service corresponding to the service identifier is detected in the session scope;

When the service corresponding to the service identifier is detected, the bearer binding is performed based on the QCI and the ARP in the dynamic rule, and the creation of the dedicated bearer is triggered, so that the dynamic rule is bound to the newly created dedicated bearer. ;

When the service corresponding to the service identifier is detected, the dedicated bearer is deleted, the bearer binding of the dynamic rule is revoked, and the service corresponding to the service identifier is re-triggered in the session scope. The steps of business detection.

With reference to the fifth aspect of the embodiments of the present invention, in a first implementation manner of the fifth aspect, the dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier.

With reference to the fifth aspect of the embodiment of the present invention or the first implementation manner of the fifth aspect, in a second implementation manner of the fifth aspect of the embodiment, the service identifier is an application identifier, and the service corresponding to the service identifier Identify the corresponding application for the application;

When the processor performs the step of performing service detection on the service corresponding to the service identifier in the session scope, the following steps are specifically performed:

With reference to the second implementation manner of the fifth aspect of the embodiments of the present invention, in a third implementation manner of the fifth aspect of the embodiments, the message further includes a mute command, where the mute command is used to indicate service detection related The event does not need to generate signaling interactions;

The processor performs the following steps when performing the step of performing bearer binding and triggering the creation of a dedicated bearer based on the QCI and the ARP in the dynamic rule when the service corresponding to the service identifier is started:

When it is detected that the application corresponding to the application identifier is started, according to the mute indication, the PCRF application start event is not notified, and the bearer binding is performed based on the QCI and the ARP in the dynamic rule, and the creation of the dedicated bearer is triggered;

When the processor performs the step of deleting the dedicated bearer when detecting the end of the service corresponding to the service identifier, the processor performs the following steps:

When it is detected that the application corresponding to the application identifier ends, according to the mute indication, no notification is received. The PCRF application end event deletes the dedicated bearer.

A sixth aspect of the embodiments of the present invention provides a PCRF, including:

Transceiver, processor and memory;

The processor is configured to perform the following steps by invoking an operation instruction stored by the memory:

Controlling, by the transceiver, a message that includes a delay bearer binding indication and a dynamic rule, where the dynamic rule carries a service identifier, where the QCI and/or ARP in the dynamic rule is different from the default bearer. The delay bearer binding indication is used to indicate that the PCEF performs bearer binding on the dynamic rule only when the service corresponding to the service identifier is detected.

With reference to the sixth aspect of the embodiments of the present invention, in a first implementation manner of the sixth aspect, the dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier.

With reference to the sixth aspect of the embodiment of the present invention or the first implementation manner of the sixth aspect, in the second implementation manner of the sixth aspect of the embodiment, the service identifier is an application identifier, or a flow information.

With reference to the second implementation of the sixth to sixth aspects of the embodiments of the present invention, in a third implementation manner of the sixth aspect of the embodiments, the message further includes a mute instruction, where the mute instruction is used There is no need to generate signaling interactions to indicate events related to service detection.

As can be seen from the foregoing technical solutions, the embodiment of the present invention has the following advantages: In the embodiment of the present invention, the message received by the PCEF includes a delay bearer binding indication and a dynamic rule carrying the service identifier, and is bound according to the delay bearer. The PCEF does not carry the bearer binding, and performs service detection on the service corresponding to the service identifier in the session scope. When the service corresponding to the service identifier is detected, the dynamic rule is different from the default bearer. The QCI and the ARP perform bearer binding and trigger the creation of a dedicated bearer, and directly bind the dynamic rule to the newly created dedicated bearer. When the service corresponding to the service identifier ends, the dedicated bearer is deleted. The bearer binding of the rule is revoked, and the service detection of the service corresponding to the service identifier is performed in the session scope. Therefore, the service detection related event sent by the Gx interface is not required to control the binding and unbinding of the dynamic rule. While dynamically allocating network resources and improving network resource utilization, the signaling interaction of the Gx interface is reduced, and the signaling load is reduced. High interaction efficiency.

DRAWINGS

FIG. 1 is a schematic diagram of a PCC scenario according to an embodiment of the present invention;

2 is a schematic diagram of signaling interaction of a method for bearer binding in an embodiment of the present invention;

3 is a schematic flowchart of a method for bearer binding in an embodiment of the present invention;

4 is a schematic structural diagram of a PCEF according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a network device according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The present invention provides a bearer binding method and related device, which is used to dynamically allocate network resources, improve network resource utilization, reduce signaling interaction of Gx interfaces, reduce signaling load, and improve interaction efficiency.

The present invention is applicable to an application scenario in which a dedicated bearer guarantee service experience needs to be created under the PCC architecture. The method of the present invention is applicable to the Gx interface. The Gx interface is an interface between the PCEF device and the PCRF device in the LTE or EPC network. The Gx interface is located between the PCEF functional entity and the PCRF functional entity for charging control and policy control. The Gx interface is used to provide or remove PCC rules for the PCRF to and from the PCEF, and to communicate relevant events from the PCEF to the PCRF.

As shown in FIG. 1 , a schematic diagram of a PCC scenario in the embodiment of the present invention, wherein the PCRF can send a dynamic rule carrying a service identifier to a PCEF, and the PCEF can access the user equipment accessed through the access network according to the service identifier ( The user data stream of the user equipment (UE) performs service identification, and the PCEF can establish a dedicated bearer according to the delivered dynamic rules to ensure the user experience when accessing the wide area network.

The PCC scenario can be divided into an application detection and control (ADC) scenario and an ordinary PCC scenario according to different service identifiers:

Specifically, the ADC feature is introduced in the 3GPP standard, and the PCEF performs detection and reporting of the application according to the indication of the PCRF, and the PCRF dynamically performs policy decision according to the reported detection result. The ADC feature enables the PCRF to sense the service status of the user, provide richer input for the policy decision of the PCRF, facilitate dynamic resource allocation based on the service status, and implement PCC more flexibly (strategy, full). More business scenarios are being carried out. Then, in the ADC scenario, the service identifier is an application identifier (APP ID);

In the normal PCC scenario, the PCEF does not report the detection event to the PCRF. After the PCEF sends the dynamic rule to the PCEF, the PCEF binds the dynamic rule to the dedicated bearer when it receives the dynamic rule. After the service ends, the dedicated bearer still survives and occupies network resources. The service identifier in the normal PCC scenario is Flow Information.

In the present invention, the term "QCI" is an abbreviation of QoS Class Identifier, indicating a QoS class identifier;

The term "ARP" is an abbreviation for Allocation Retention Priority, which indicates the allocation reservation priority.

The method for bearer binding in the embodiment of the present invention is described below in conjunction with the signaling interaction process between the PCEF and the PCRF in the embodiment of the present invention:

Referring to FIG. 2, an embodiment of a method for bearer binding in an embodiment of the present invention includes:

201, the PCRF sends a message including a delayed bearer binding indication and a dynamic rule to the PCEF;

The dynamic rule carries a service identifier, where the QCI and/or the ARP in the dynamic rule is different from the default bearer, and the delayed bearer binding indication is used to indicate the PCEF: only when the service identifier is The dynamic rule is bearered and bound when the corresponding service is detected.

It should be noted that the delay bearer binding indication may be dynamic rule granularity or message granularity. If the delayed bearer binding indication is dynamic rule granularity, it is included in the dynamic rule. The sub-parameter of the rule, the delay bearer binding indication is only valid for the dynamic rule that includes the delay bearer binding indication; if the delayed bearer binding indication is message granularity, the delayed bearer binding indication pair The dynamic rules contained in this message are valid and are not limited here.

It can be understood that the message may be an improvement of the CCA-I response message, the CCA-U response message, or the RAR update message in the 3GPP protocol, and the sending process and the sending timing may be the same as those specified in the protocol. limited.

Specifically, for example, if the message is a CCA-I response message, before step 201, the UE may first send a session creation message to the PCEF initiation session (IP-CAN Session) creation process, requesting to establish a session. After receiving the session creation message, the PCEF may send a CCR-I request message to the PCRF, where the CCR-I request message is used to request the PCRF to send policy information, and the CCR-I request is cancelled. The user information of the UE is carried in the interest. After receiving the CCR-I request message, the PCRF sends a CCA-I response message to the PCEF. The user information may be a unique identifier of the UE in the network system, such as an International Mobile Subscriber Identification Number (IMSI), and the calling user is required to dial a mobile subscriber in the GSM PLMN. MSISDN and the like are not limited herein. The PCRF can obtain the service identifier corresponding to the user information according to the user subscription data.

Similarly, if the message is a CCA-U response message, before the step 201, the PCRF may receive a CCR-U request message sent by the PCEF for requesting the PCRF update policy information; if the message is a RAR update message, the message is The updated policy information that is actively pushed by the PCRF can be understood. In addition to these types of messages, the dynamic rules and the delay bearer binding indications may be carried in other messages in the actual application, which is not limited herein.

It can be understood that, in practical applications, the dynamic rule carries the QCI and ARP parameters different from the default bearer, and may also carry the charging and policy control parameters for the service plan corresponding to the service identifier, for example, Rate (Rating Group, RG), Quality of Service (QoS), etc., are not limited herein.

It should be noted that any parameter in the QCI and the ARP in the dynamic rule is different from the default bearer, and indicates that the QCI and/or the ARP in the dynamic rule are different from the default bearer.

202. The PCEF performs bearer binding according to the delay bearer binding indication, and performs service detection on the service corresponding to the service identifier in the session scope.

After receiving the message that is sent by the PCRF and carrying the dynamic rule and the delay bearer binding indication, the PCEF performs the bearer binding according to the delay bearer binding indication, and performs the service corresponding to the service identifier in the session scope. Business testing.

Alternatively, in step 204, the PCEF deletes the dedicated bearer, and after the bearer binding of the dynamic rule is revoked, the service corresponding to the service identifier may be re-inspected in the session scope.

It can be understood that the PCEF may first save the dynamic rule based on the session before performing service detection on the service corresponding to the service identifier.

203. When the PCEF detects that the service corresponding to the service identifier starts, perform bearer binding based on the QCI and the ARP in the dynamic rule, and trigger to create a dedicated bearer, so that the dynamic rule is bound to the newly created. On a proprietary bearer;

During the session, when the PCEF detects the start of the service corresponding to the service identifier, the PCEF performs bearer binding based on the QCI and the ARP that are different from the default bearer in the dynamic rule, and triggers the creation of a dedicated bearer. , then bind the dynamic rule to the newly created private bearer.

204. When the PCEF detects that the service corresponding to the service identifier ends, delete the dedicated bearer, cancel the bearer binding of the dynamic rule, and re-trigger step 202.

When the PCEF detects that the service corresponding to the service identifier is terminated, the PCEF rolls back the bearer binding result, that is, deletes the created dedicated bearer, cancels the bearer binding of the dynamic rule, and re-triggers step 202 to continue The service detection is performed on the service corresponding to the service identifier in the session scope.

It can be understood that the PCEF detects the end of the service corresponding to the service identifier, and can be detected by the session level or by the bearer layer, which is not limited herein.

In the embodiment of the present invention, the message received by the PCEF includes a delay bearer binding indication and a dynamic rule carrying the service identifier. According to the delay bearer binding indication, the PCEF does not perform bearer binding temporarily, and is in the session scope. The service corresponding to the service identifier performs service detection, and when the service corresponding to the service identifier is started, the bearer binding is performed according to the QCI and the ARP in the dynamic rule different from the default bearer, and the creation of the dedicated bearer is directly triggered. The dynamic rule is bound to the newly created dedicated bearer, and when the service corresponding to the service identifier ends, the dedicated bearer is deleted, the bearer binding of the dynamic rule is revoked, and the trigger is re-triggered in the session scope. The service corresponding to the service identifier performs service detection. Therefore, the service detection related events sent by the Gx interface are not required to control the binding and unbinding of the dynamic rules, and the network resources are dynamically allocated, and the network resource utilization rate is improved. The signaling interaction of the Gx interface reduces the signaling load and improves the interaction efficiency.

The following describes the method for carrying the binding in the embodiment of the present invention from the perspective of the PCEF. Referring to FIG. 3, another embodiment of the method for carrying the binding in the embodiment of the present invention includes:

301. The PCEF receives a message that is sent by the PCRF and includes a delayed bearer binding indication and a dynamic rule.

The dynamic rule carries a service identifier, and the QCI and/or the ARP in the dynamic rule are different from the default bearer, where the delayed bearer binding indication is used to indicate that the PCEF only corresponds to the service identifier. The dynamic rule is bearered and bound when the service is detected;

Similar to step 201, it will not be described here.

302. The PCEF performs the bearer binding according to the delay bearer binding indication. Performing service detection on the service corresponding to the service identifier in the range of the voice;

303. When the PCEF detects that the service corresponding to the service identifier starts, perform bearer binding based on the QCI and the ARP in the dynamic rule, and trigger to create a dedicated bearer, so that the dynamic rule is bound to the newly created. On a proprietary bearer;

304. When the PCEF detects that the service corresponding to the service identifier ends, delete the dedicated bearer, cancel the bearer binding of the dynamic rule, and re-trigger step 302.

Steps 302 to 304 are similar to steps 202 to 204, and are not described herein.

In the above embodiment, the message includes a dynamic rule carrying a service identifier. In an actual application, the service identifier is different according to the application scenario. Specifically, in the ADC scenario, the service identifier is an application identifier. The service corresponding to the service identifier is: the application corresponding to the application identifier; in the normal PCC scenario, the service identifier is the flow information, and the service corresponding to the service identifier is: the service corresponding to the flow information.

It can be understood that, in the ADC scenario, when the PCEF detects that the service corresponding to the service identifier starts, it will notify the PCRF service start event, and when the PCEF detects that the service corresponding to the service identifier ends, it will notify the PCRF service end event. In an actual application, in an ADC scenario, as another embodiment of the method for carrying a binding in the embodiment of the present invention, the message further includes a mute instruction, where the mute instruction is used to indicate that the service detection related event does not need to generate signaling interaction. ;

Because it is an ADC scenario, the service identifier is the application identifier at this time. Specifically:

When the PCEF detects that the service corresponding to the service identifier starts, based on the dynamic rule The QCI and the ARP perform the bearer binding and trigger the creation of the dedicated bearer. Specifically, when the PCEF detects that the application corresponding to the application identifier starts, according to the mute indication, the PCRF application start event is not notified. Performing bearer binding based on QCI and ARP in the dynamic rule and triggering creation of a dedicated bearer;

When the PCEF detects that the service corresponding to the service identifier ends, deleting the dedicated bearer may be: when the PCEF detects that the application corresponding to the application identifier ends, according to the mute indication. The PCRF application end event is not notified, and the dedicated bearer is deleted.

In the embodiment of the present invention, the message further includes a mute command. In the ADC scenario, the PCEF is prevented from notifying the related event to the PCRF when the service starts and ends, saving the signaling required for transmitting the related event, and further reducing the Gx interface. The signaling interaction reduces the signaling load and achieves the purpose of improving the interaction efficiency.

It can be understood that, in the embodiment of the present invention, the message includes the delay bearer binding indication, and the service detection related event is no longer required to control the binding and unbinding of the dynamic rule. Therefore, the service can be no longer sent in the ADC scenario. The related event is detected, so as to save the signaling interaction of the Gx interface. However, the embodiment of the present invention does not limit the service detection related event on the Gx interface, that is, the message in the embodiment of the present invention carries the delayed bearer binding. The indication provides a basis for not transmitting the service detection related event, and whether the specific transmission is performed may be selected according to the actual situation, which is not limited herein.

The following describes the method for carrying the binding in the embodiment of the present invention from the perspective of the PCRF. Another embodiment of the method for carrying the binding in the embodiment of the present invention includes:

The PCRF sends a message including a delayed bearer binding indication and a dynamic rule to the PCEF;

The dynamic rule carries a service identifier, and the QCI and/or the ARP in the dynamic rule are different from the default bearer, where the delayed bearer binding indication is used to indicate that the PCEF only corresponds to the service identifier. The dynamic rules are bearered and bound when the service is detected.

Specifically, for example, if the message is a CCA-I response message, the message is triggered by a CCR-I request message received by the PCRF for requesting the PCRF to send policy information; if the message is CCA-U In response to the message, the message is received by the PCRF for requesting a PCRF update policy letter. The message is triggered by the CCR-U request message; the message may also be a policy update message actively pushed by the PCRF. It can be understood that, in addition to these kinds of messages, in actual applications, dynamic rules can also be carried in other messages. And the delay bearer binding indication, correspondingly, the triggering condition that the PCRF sends the message to the PCEF may also have other conditions, which is not limited herein.

In the embodiment of the present invention, the message sent by the PCRF to the PCEF carries the delay bearer binding indication, so that the PCEF binds the dynamic rule only when the service corresponding to the service identifier is detected, so that The service detection related events sent by the Gx interface are used to control the binding and unbinding of dynamic rules. When dynamically allocating network resources and improving network resource utilization, the signaling interaction of the Gx interface is reduced, and the signaling load is reduced. Improve the efficiency of interaction.

Optionally, as another embodiment of the method for carrying a binding in the embodiment of the present invention, in an actual application, in an ADC scenario, the message may further include a mute instruction, where the mute instruction is used to indicate a service detection related event. There is no need to generate signaling interaction, which is not limited herein.

The following describes the PCEF in the embodiment of the present invention. Referring to FIG. 4, an embodiment of the PCEF in the embodiment of the present invention includes:

The receiving module 401 is configured to receive, by the PCRF, a message that includes a delayed bearer binding indication and a dynamic rule, where the dynamic rule carries a service identifier, where the QCI and/or the ARP in the dynamic rule are different from the default bearer. The delay bearer binding indication is used to indicate that the PCEF performs bearer binding on the dynamic rule only when the service corresponding to the service identifier is detected;

The detecting module 402 is configured to perform the bearer binding according to the delayed bearer binding indication in the message received by the receiving module 401, and perform the service corresponding to the service identifier in the session scope. Inspection

The bearer binding module 403 is configured to: when the detecting module 402 detects that the service corresponding to the service identifier starts, perform bearer binding based on the QCI and the ARP in the dynamic rule, and trigger to create a dedicated bearer, so that the The dynamic rules are bound to the newly created private bearer;

The binding revocation module 404 is configured to delete the dedicated bearer created by the bearer binding module 403, and undo the bearer binding of the dynamic rule, and re-trigger when the service corresponding to the service identifier is detected. The detecting module 402.

In the embodiment of the present invention, the message received by the receiving module 401 includes a delay bearer binding indication and a dynamic rule carrying a service identifier. According to the delay bearer binding indication, the PCEF does not perform bearer binding temporarily, and the detecting module 402 When the service corresponding to the service identifier is detected in the session, and the service corresponding to the service identifier is started, the bearer binding module 403 binds the bearer according to the QCI and the ARP in the dynamic rule different from the default bearer. Determining and triggering the creation of a dedicated bearer, directly binding the dynamic rule to the newly created dedicated bearer, and when the service corresponding to the service identifier ends, the binding revocation module 404 deletes the private bearer, and the dynamic rule is deleted. The bearer binding is revoked, and the retries detection module 402 performs service detection on the service corresponding to the service identifier in the session scope, so that the service detection related event sent by the Gx interface is not needed to control the binding and solution of the dynamic rule. Tied, while dynamically allocating network resources and improving network resource utilization, reducing signaling interaction on Gx interfaces and reducing signaling Load and improve the efficiency of interaction.

Optionally, in the foregoing embodiment, the dynamic rule further includes a charging and policy control parameter for the service plan corresponding to the service identifier.

Optionally, as another embodiment of the PCEF in the embodiment of the present invention, in the foregoing embodiment, the service identifier is an application identifier, and the service corresponding to the service identifier is an application corresponding to the application identifier;

The detecting module 402 is configured to perform the application detection on the application corresponding to the application identifier in the session scope according to the delay bearer binding indication in the message received by the receiving module 401.

In this embodiment, the PCEF can be applied to the ADC scenario, so that the delay bearer binding mechanism can be applied to the dynamic rule carrying the application identifier in the ADC scenario, and the adaptation range of the PCEF is improved.

Optionally, as another embodiment of the PCEF in the embodiment of the present invention, in the foregoing embodiment, the message further includes a mute instruction, where the mute instruction is used to indicate a service detection related event without generating a message. Make interaction

The bearer binding module 403 is specifically configured to: when the detecting module 402 detects that the application corresponding to the application identifier starts, according to the mute indication, does not notify the PCRF application start event, based on the QCI in the dynamic rule. Carrying a bearer binding with the ARP and triggering the creation of a dedicated bearer, so that the dynamic rule is bound to the newly created private bearer;

The binding revocation module 404 is specifically configured to: when the end of the application corresponding to the application identifier is detected, not to notify the PCRF application end event according to the mute indication, and delete the proprietary created by the bearer binding module 403. The bearer binds the bearer binding of the dynamic rule and re-triggers the detecting module 402.

The PCRF in the embodiment of the present invention is described below. One embodiment of the PCRF in the embodiment of the present invention includes:

In the embodiment of the present invention, the message sent by the sending module to the PCEF carries the delay bearer binding indication, so that the PCEF performs bearer binding on the dynamic rule only when the service corresponding to the service identifier is detected, so that The service detection related events sent by the Gx interface are not required to control the binding and unbinding of the dynamic rules, and the network resources are dynamically allocated, the network resource utilization is improved, the signaling interaction of the Gx interface is reduced, and the signaling is reduced. Load, improve the efficiency of interaction.

Optionally, as another embodiment of the PCRF in the embodiment of the present invention, in an actual application, in an ADC scenario, the message may further include a mute instruction, where the mute instruction is used to indicate that the service detection related event does not need to generate signaling. Interaction, not limited here.

FIG. 5 is a schematic structural diagram of a network device 500 according to an embodiment of the present invention, including:

The transceiver 501, the memory 502, and the processor 503 (wherein the number of processors 503 in the network device 500 may be one or more, and one processor 503 is taken as an example in FIG. 5). In some embodiments of the present invention, the transceiver 501, the memory 502, and the processor 503 may be connected by a bus or other means, wherein the bus connection is taken as an example in FIG.

It can be understood that the network device may represent the PCEF in the embodiment of the present invention, and may also represent the PCRF in the embodiment of the present invention, according to the operation instruction stored in the memory 502 and the processing step of the processor 503.

When the network device represents the PCEF in the embodiment of the present invention, the processor 503 is configured to perform the following steps by calling an operation instruction stored in the memory 504:

The transceiver 501 is configured to receive a message that is sent by the PCRF and includes a delayed bearer binding indication and a dynamic rule, where the dynamic rule carries a service identifier, where the QCI and/or the ARP in the dynamic rule are different from the default bearer. The delay bearer binding indication is used to indicate that the PCEF performs bearer binding on the dynamic rule only when the service corresponding to the service identifier is detected;

When the service corresponding to the service identifier is detected, the dedicated bearer is deleted, the bearer binding of the dynamic rule is revoked, and the service corresponding to the service identifier is re-triggered in the session scope. Business detection steps;

In some embodiments of the present invention, the dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier;

In some embodiments of the present invention, the service identifier is an application identifier, and the service corresponding to the service identifier is an application corresponding to the application identifier;

When the processor 503 performs the step of performing service detection on the service corresponding to the service identifier in the session scope, the following steps are specifically performed:

In some embodiments of the present invention, the message further includes a mute instruction, where the mute instruction is used to indicate that the service detection related event does not need to generate a signaling interaction;

The processor 503 performs the following steps when performing the step of performing bearer binding and triggering the creation of a dedicated bearer based on the QCI and the ARP in the dynamic rule when the service corresponding to the service identifier is started. :

The processor 503, when performing the step of deleting the dedicated bearer when detecting the end of the service corresponding to the service identifier, performing the following steps:

When it is detected that the application corresponding to the application identifier ends, according to the mute indication, the PCRF application end event is not notified, and the dedicated bearer is deleted.

When the network device indicates the PCRF in the embodiment of the present invention, the processor 503 is configured to perform the following steps by calling an operation instruction stored in the memory 502:

Controlling the transceiver 501 to send a message including a delayed bearer binding indication and a dynamic rule to the PCEF, where the dynamic rule carries a service identifier, and the QCI and/or ARP in the dynamic rule is different from the default bearer. The delay bearer binding indication is used to indicate that the PCEF performs bearer binding on the dynamic rule only when the service corresponding to the service identifier is detected.

In some embodiments of the present invention, the service identifier is an application identifier, or a flow information;

In some embodiments of the present invention, the message further includes a mute instruction, where the mute instruction is used There is no need to generate signaling interactions to indicate events related to service detection.

The embodiment of the invention further provides a bearer binding system, including:

The PCEF shown in any of the above embodiments, and the PCRF shown in any of the above embodiments.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, 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, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be 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 processing unit, or each unit may exist physically separately, 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 a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. The medium in which the program code is stored.

The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that The technical solutions described in the embodiments are modified, or the equivalents of the technical features are replaced by the equivalents of the technical solutions of the embodiments of the present invention.

Claims

A method for bearer binding, comprising:

The policy and charging enforcement function entity PCEF receives the message that is sent by the policy and charging rule function entity PCRF and includes a delay bearer binding indication and a dynamic rule, where the dynamic rule carries a service identifier, and the QCI in the dynamic rule And the ARP is different from the default bearer, and the delayed bearer binding indication is used to indicate that the PCEF performs bearer binding on the dynamic rule only when the service corresponding to the service identifier is detected;

The PCEF performs bearer binding according to the delay bearer binding indication, and performs service detection on the service corresponding to the service identifier in the session scope;

When the PCEF detects that the service corresponding to the service identifier starts, the bearer binding is performed based on the QCI and the ARP in the dynamic rule, and the creation of the dedicated bearer is triggered, so that the dynamic rule is bound to the newly created special Have a bearing;

When the PCEF detects that the service corresponding to the service identifier ends, the dedicated bearer is deleted, the bearer binding of the dynamic rule is revoked, and the service identifier corresponding to the service identifier is retriggered in the session scope. The steps of the business to conduct business inspection.
The method according to claim 1, wherein the dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier.
The method according to claim 1 or 2, wherein the service identifier is an application identifier, and the service corresponding to the service identifier is an application corresponding to the application identifier;

The performing service detection on the service corresponding to the service identifier in the session scope includes:

Application detection is performed on the application corresponding to the application identifier in the session scope.
The method according to claim 3, wherein the message further includes a mute instruction, the mute instruction is used to indicate that the service detection related event does not need to generate a signaling interaction;

And when the PCEF detects that the service corresponding to the service identifier starts, performing bearer binding and triggering to create a dedicated bearer based on the QCI and the ARP in the dynamic rule, specifically:

When the PCEF detects that the application corresponding to the application identifier starts, according to the muting indication, the PCRF application start event is not notified, and the bearer binding is performed based on the QCI and the ARP in the dynamic rule, and the creation of the dedicated bearer is triggered. ;

When the PCEF detects that the service corresponding to the service identifier ends, deleting the special There are bearers, including:

When the PCEF detects that the application corresponding to the application identifier ends, according to the mute indication, the PCRF application end event is not notified, and the dedicated bearer is deleted.
A method for bearer binding, comprising:

The PCRF sends a message including a delayed bearer binding indication and a dynamic rule to the PCEF, where the dynamic rule carries a service identifier, and the QCI and/or ARP in the dynamic rule is different from the default bearer, and the delay bearer The binding indication is used to indicate that the PCEF performs bearer binding on the dynamic rule only when the service corresponding to the service identifier is detected.
The method according to claim 5, wherein the dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier.
The method according to claim 5 or 6, wherein the service identifier is an application identifier, or stream information.
The method according to any one of claims 5 to 6, wherein the service identifier is an application identifier, and the message further includes a mute instruction, where the mute command is used to indicate that the service detection related event does not need to be generated. Signaling interaction.
A PCEF, comprising:

a receiving module, configured to receive, by the PCRF, a message that includes a delayed bearer binding indication and a dynamic rule, where the dynamic rule carries a service identifier, where the QCI and/or the ARP in the dynamic rule are different from the default bearer. The delay bearer binding indication is used to indicate that the PCEF performs bearer binding on the dynamic rule only when the service corresponding to the service identifier is detected;

The detecting module is configured to perform the service detection on the service corresponding to the service identifier in the session scope according to the delay bearer binding indication in the message received by the receiving module;

a bearer binding module, configured to: when the detecting module detects that the service corresponding to the service identifier starts, perform bearer binding based on QCI and ARP in the dynamic rule, and trigger to create a dedicated bearer, so that the dynamic The rules are bound to the newly created private bearer;

The binding revocation module is configured to delete the dedicated bearer when the service corresponding to the service identifier is detected, cancel the bearer binding of the dynamic rule, and re-trigger the detection module.
The PCEF according to claim 9, wherein the dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier.
The PCEF according to claim 9 or 10, wherein the service identifier is an application identifier, and the service corresponding to the service identifier is an application corresponding to the application identifier;

The detecting module is configured to perform the application detection on the application corresponding to the application identifier in the session scope according to the delay bearer binding indication in the message received by the receiving module.
The PCEF according to claim 11, wherein the message further includes a mute instruction, where the mute instruction is used to indicate that the service detection related event does not need to generate a signaling interaction;

The bearer binding module is specifically configured to: when the detecting module detects that the application corresponding to the application identifier starts, according to the mute indication, does not notify the PCRF application start event, based on the QCI and the dynamic rule ARP performs bearer binding and triggers creation of a dedicated bearer, so that the dynamic rule is bound to the newly created private bearer;

The binding revocation module is specifically configured to: when the end of the application corresponding to the application identifier is detected, not to notify the PCRF application end event according to the mute indication, delete the dedicated bearer, and the dynamic rule is The bearer binding is revoked and the detection module is re-triggered.
A PCRF, comprising:

a sending module, configured to send a message that includes a delayed bearer binding indication and a dynamic rule, where the dynamic rule carries a service identifier, where the QCI and/or ARP in the dynamic rule is different from the default bearer. The delay bearer binding indication is used to indicate that the PCEF performs bearer binding on the dynamic rule only when the service corresponding to the service identifier is detected.
The PCRF according to claim 13, wherein the dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier.
The PCRF according to claim 13 or 14, wherein the service identifier is an application identifier, or stream information.
The PCRF according to any one of claims 13 to 15, wherein the message further includes a mute instruction, the mute instruction is used to indicate that the service detection related event does not need to generate a signaling interaction.
A PCEF, comprising:

Transceiver, processor and memory;

The processor is configured to perform the following steps by using the operation instruction stored in the memory:

Controlling, by the transceiver, a message that is sent by the PCRF and includes a delay bearer binding indication and a dynamic rule, where the dynamic rule carries a service identifier, where the QCI and/or ARP in the dynamic rule is different from the default bearer. The delay bearer binding indication is used to indicate that the PCEF performs bearer binding on the dynamic rule only when the service corresponding to the service identifier is detected;

According to the delay bearer binding indication, the bearer binding is not performed temporarily, and the service corresponding to the service identifier is detected in the session scope;

When the service corresponding to the service identifier is detected, the bearer binding is performed based on the QCI and the ARP in the dynamic rule, and the creation of the dedicated bearer is triggered, so that the dynamic rule is bound to the newly created dedicated bearer. ;

When the service corresponding to the service identifier is detected, the dedicated bearer is deleted, the bearer binding of the dynamic rule is revoked, and the service corresponding to the service identifier is re-triggered in the session scope. The steps of business detection.
The PCEF according to claim 17, wherein the dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier.
The PCEF according to claim 17 or 18, wherein the service identifier is an application identifier, and the service corresponding to the service identifier is an application corresponding to the application identifier;

When the processor performs the step of performing service detection on the service corresponding to the service identifier in the session scope, the following steps are specifically performed:

Application detection is performed on the application corresponding to the application identifier in the session scope.
The PCEF according to claim 19, wherein the message further includes a mute instruction, where the mute instruction is used to indicate that the service detection related event does not need to generate a signaling interaction;

The processor performs the following steps when performing the step of performing bearer binding and triggering the creation of a dedicated bearer based on the QCI and the ARP in the dynamic rule when the service corresponding to the service identifier is started:

When it is detected that the application corresponding to the application identifier is started, according to the mute indication, the PCRF application start event is not notified, and the bearer binding is performed based on the QCI and the ARP in the dynamic rule, and the creation of the dedicated bearer is triggered;

When the processor performs the step of deleting the dedicated bearer when detecting the end of the service corresponding to the service identifier, the processor performs the following steps:

When it is detected that the application corresponding to the application identifier ends, according to the mute indication, the PCRF application end event is not notified, and the dedicated bearer is deleted.
A PCRF, comprising:

Transceiver, processor and memory;

The processor is configured to perform the following steps by invoking an operation instruction stored by the memory:

Controlling, by the transceiver, a message that includes a delay bearer binding indication and a dynamic rule, where the dynamic rule carries a service identifier, where the QCI and/or ARP in the dynamic rule is different from the default bearer. The delay bearer binding indication is used to indicate that the PCEF performs bearer binding on the dynamic rule only when the service corresponding to the service identifier is detected.
The PCRF according to claim 21, wherein the dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier.
The PCRF according to claim 21 or 22, wherein the service identifier is an application identifier, or stream information.
The PCRF according to any one of claims 21 to 23, wherein the message further includes a mute instruction, the mute instruction is used to indicate that the service detection related event does not need to generate a signaling interaction.