WO2016206071A1 - Procédé de liaison de porteuse et équipement associé - Google Patents

Procédé de liaison de porteuse et équipement associé Download PDF

Info

Publication number
WO2016206071A1
WO2016206071A1 PCT/CN2015/082443 CN2015082443W WO2016206071A1 WO 2016206071 A1 WO2016206071 A1 WO 2016206071A1 CN 2015082443 W CN2015082443 W CN 2015082443W WO 2016206071 A1 WO2016206071 A1 WO 2016206071A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
bearer
identifier
dynamic rule
pcef
Prior art date
Application number
PCT/CN2015/082443
Other languages
English (en)
Chinese (zh)
Inventor
何光伟
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201580030965.8A priority Critical patent/CN106664614B/zh
Priority to PCT/CN2015/082443 priority patent/WO2016206071A1/fr
Publication of WO2016206071A1 publication Critical patent/WO2016206071A1/fr

Links

Images

Classifications

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

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and related device for bearer binding.
  • 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.
  • PCRF Policy and Charging Rules Function
  • PCEF Policy and Charging Enforcement Function
  • the PCEF installs the control policy on the default bearer.
  • 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.
  • QCI QoS Class Identifier
  • ARP Allocation Retention Priority
  • the application detection and control (ADC) scenario is currently controlled by sending traffic detection related events.
  • ADC application detection and control
  • the allocation and bearer of dynamic rules in an ADC scenario The way to bind is:
  • 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.
  • APP ID application identifier
  • the PCEF performs bearer binding, and the dynamic rule is installed on the default bearer.
  • 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;
  • 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.
  • 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.
  • 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;
  • 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;
  • 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 dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier.
  • 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.
  • 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;
  • 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. ;
  • 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.
  • the dynamic rule further includes a charging and policy control parameter for the service plan corresponding to the service identifier.
  • the service identifier is an application identifier, or a flow information.
  • the service identifier is an application identifier
  • 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.
  • the dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier.
  • 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.
  • 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.
  • the dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier.
  • the service identifier is an application identifier, or a flow information.
  • 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:
  • 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 bearer binding is not performed temporarily, and the service corresponding to the service identifier is detected in the session scope;
  • 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.
  • 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 dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier.
  • the service identifier is an application identifier, and the service corresponding to the service identifier Identify the corresponding application for the application;
  • Application detection is performed on the application corresponding to the application identifier in the session scope.
  • 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:
  • 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;
  • the processor 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:
  • 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:
  • 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 dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier.
  • the service identifier is an application identifier, or a flow information.
  • 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 present invention has the following advantages:
  • 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.
  • 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.
  • 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.
  • FIG. 1 is a schematic diagram of a PCC scenario according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of signaling interaction of a method for bearer binding in an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a method for bearer binding in an embodiment of the present invention.
  • FIG. 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.
  • 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.
  • 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:
  • ADC application detection and control
  • 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.
  • the service identifier is an application identifier (APP ID);
  • the PCEF does not report the detection event to the PCRF.
  • 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.
  • the dedicated bearer still survives and occupies network resources.
  • the service identifier in the normal PCC scenario is Flow Information.
  • QCI is an abbreviation of QoS Class Identifier, indicating a QoS class identifier
  • ARP Allocation Retention Priority
  • an embodiment of a method for bearer binding in an 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, 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.
  • 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.
  • 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.
  • the UE may first send a session creation message to the PCEF initiation session (IP-CAN Session) creation process, requesting to establish a session.
  • 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.
  • 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.
  • 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.
  • the dynamic rules and the delay bearer binding indications may be carried in other messages in the actual application, which is not limited herein.
  • 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.
  • 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.
  • 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.
  • the PCEF 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.
  • 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.
  • the PCEF may first save the dynamic rule based on the session before performing service detection on the service corresponding to the service identifier.
  • 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.
  • the PCEF 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.
  • 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.
  • the message received by the PCEF includes a delay bearer binding indication and a dynamic rule carrying the service identifier.
  • 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.
  • Another embodiment of the method for carrying the binding in the embodiment of the present invention includes:
  • 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;
  • step 201 Similar to step 201, it will not be described here.
  • 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;
  • Steps 302 to 304 are similar to steps 202 to 204, and are not described herein.
  • the message received by the PCEF includes a delay bearer binding indication and a dynamic rule carrying the service identifier.
  • 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 message includes a dynamic rule carrying a service identifier.
  • the service identifier is different according to the application 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.
  • 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. ;
  • the service identifier is the application identifier at this time. Specifically:
  • 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;
  • 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.
  • the message further includes a mute command.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • the message is CCA-U
  • 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.
  • 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.
  • 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.
  • the message includes a dynamic rule carrying a service identifier.
  • the service identifier is different according to the application 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.
  • 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 message further includes a mute command.
  • 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.
  • 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 message received by the receiving module 401 includes a delay bearer binding indication and a dynamic rule carrying a service identifier.
  • the PCEF does not perform bearer binding temporarily
  • 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.
  • 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.
  • the dynamic rule further includes a charging and policy control parameter for the service plan corresponding to the service identifier.
  • the service identifier is an application identifier
  • 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.
  • 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.
  • the message further includes a mute instruction, where the mute instruction is used to indicate a service detection related event without generating a message.
  • 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 message further includes a mute command.
  • 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.
  • PCRF in the embodiment of the present invention is described below.
  • One embodiment of the PCRF in the embodiment of the present invention includes:
  • 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 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.
  • the message includes a dynamic rule carrying a service identifier.
  • the service identifier is different according to the application 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.
  • 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.
  • the message further includes a mute command.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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;
  • the bearer binding is not performed temporarily, and the service corresponding to the service identifier is detected in the session scope;
  • 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.
  • the dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier
  • the service identifier is an application identifier
  • the service corresponding to the service identifier is an application corresponding to the application identifier
  • Application detection is performed on the application corresponding to the application identifier in the session scope.
  • 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 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;
  • 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:
  • the PCRF application end event is not notified, and the dedicated bearer is deleted.
  • the processor 503 is configured to perform the following steps by calling an operation instruction stored in the memory 502:
  • 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 dynamic rule further includes a charging and policy control parameter for a service plan corresponding to the service identifier
  • the service identifier is an application identifier, or a flow information
  • 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 disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner 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.
  • 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.
  • 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.
  • 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.

Landscapes

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

Abstract

La présente invention porte sur un procédé de liaison de porteuse et sur un équipement associé, allouant de façon dynamique une ressource réseau et augmentant un taux d'utilisation de la ressource réseau tout en diminuant les interactions de signalisation dans une interface Gx, réduisant la charge de signalisation et augmentant l'efficacité des interactions. Selon un mode de réalisation de l'invention, le procédé consiste à : recevoir, au moyen d'une fonction d'application de politique et de facturation (PCEF pour Policy and Charging Enforcement Function), un message comprenant une indication de latence de liaison de porteuse et une règle dynamique comportant un identifiant de service ; différer, au moyen de la fonction PCEF et en fonction de l'indication de latence de liaison de porteuse, un procédé de liaison de porteuse ; surveiller, au moyen de la fonction PCEF, un service correspondant à l'identifiant de service dans une session ; lors de la détection d'un démarrage du service correspondant à l'identifiant de service, exécuter, au moyen de la fonction PCEF et en fonction d'un identifiant de classe (QCI) de qualité de service (QoS pour Quality of Service) et d'une priorité de conservation d'attribution (ARP pour Allocation Retention Priority) indiqués dans la règle dynamique différente d'une porteuse par défaut, le procédé de liaison de porteuse et déclencher, au moyen de la fonction PCEF, l'établissement d'une porteuse dédiée de sorte à lier directement la règle dynamique à la porteuse dédiée récemment établie ; supprimer, à la fin du service correspondant à l'identifiant de service et au moyen de la fonction PCEF, la porteuse dédiée de sorte à annuler la liaison de porteuse associée à la règle dynamique ; et déclencher à nouveau, au moyen de la fonction PCEF, une détection de service du service correspondant à l'identifiant de service dans la session.
PCT/CN2015/082443 2015-06-26 2015-06-26 Procédé de liaison de porteuse et équipement associé WO2016206071A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201580030965.8A CN106664614B (zh) 2015-06-26 2015-06-26 承载绑定的方法和相关设备
PCT/CN2015/082443 WO2016206071A1 (fr) 2015-06-26 2015-06-26 Procédé de liaison de porteuse et équipement associé

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/082443 WO2016206071A1 (fr) 2015-06-26 2015-06-26 Procédé de liaison de porteuse et équipement associé

Publications (1)

Publication Number Publication Date
WO2016206071A1 true WO2016206071A1 (fr) 2016-12-29

Family

ID=57584562

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/082443 WO2016206071A1 (fr) 2015-06-26 2015-06-26 Procédé de liaison de porteuse et équipement associé

Country Status (2)

Country Link
CN (1) CN106664614B (fr)
WO (1) WO2016206071A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101778434A (zh) * 2009-01-12 2010-07-14 华为技术有限公司 一种统一控制的方法、网络设备及系统
CN102340889A (zh) * 2010-07-26 2012-02-01 中兴通讯股份有限公司 一种网络侧发起ims信令承载建立的方法及系统
WO2012175123A1 (fr) * 2011-06-22 2012-12-27 Telefonaktiebolaget L M Ericsson (Publ) Procédé de gestion de politique et procédé de commande du support ainsi que serveurs, systèmes et programmes d'ordinateur correspondants
US20130003566A1 (en) * 2011-07-01 2013-01-03 Telefonaktiebolaget Lm Ericsson (Publ) Method and Node for Controlling Bearer Related Resources as well as a Corresponding System and Computer Program
WO2013044959A1 (fr) * 2011-09-29 2013-04-04 Telefonaktiebolaget L M Ericsson (Publ) Procédés et nœuds de réseau pour commandes des ressources d'une session de service, ainsi que système et programme d'ordinateur correspondants

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101877894B (zh) * 2009-04-28 2014-12-24 电信科学技术研究院 承载绑定与事件报告功能实体重定位方法、系统及其装置
CN101959257B (zh) * 2009-07-20 2013-06-12 中兴通讯股份有限公司 一种承载绑定和事件报告功能的重选方法
CN101969673B (zh) * 2009-07-27 2013-08-07 中兴通讯股份有限公司 一种承载绑定和事件报告功能的重选方法
CN104010332B (zh) * 2013-02-21 2019-03-15 中兴通讯股份有限公司 承载绑定方法及系统
US10021038B2 (en) * 2013-05-17 2018-07-10 Telefonaktiebolaget Lm Ericsson (Publ) Sharing resource reservation
CN104509140B (zh) * 2013-07-02 2018-10-30 华为技术有限公司 应用流检测方法、实体及系统
CN103686648A (zh) * 2013-12-17 2014-03-26 中国联合网络通信集团有限公司 一种策略计费控制规则信息的请求方法、装置及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101778434A (zh) * 2009-01-12 2010-07-14 华为技术有限公司 一种统一控制的方法、网络设备及系统
CN102340889A (zh) * 2010-07-26 2012-02-01 中兴通讯股份有限公司 一种网络侧发起ims信令承载建立的方法及系统
WO2012175123A1 (fr) * 2011-06-22 2012-12-27 Telefonaktiebolaget L M Ericsson (Publ) Procédé de gestion de politique et procédé de commande du support ainsi que serveurs, systèmes et programmes d'ordinateur correspondants
US20130003566A1 (en) * 2011-07-01 2013-01-03 Telefonaktiebolaget Lm Ericsson (Publ) Method and Node for Controlling Bearer Related Resources as well as a Corresponding System and Computer Program
WO2013044959A1 (fr) * 2011-09-29 2013-04-04 Telefonaktiebolaget L M Ericsson (Publ) Procédés et nœuds de réseau pour commandes des ressources d'une session de service, ainsi que système et programme d'ordinateur correspondants

Also Published As

Publication number Publication date
CN106664614B (zh) 2019-06-21
CN106664614A (zh) 2017-05-10

Similar Documents

Publication Publication Date Title
JP5622933B2 (ja) インターネットプロトコルコネクティビティアクセスネットワークセッションの管理
EP2499858B1 (fr) Déclencheur d'événement de service
US10623584B2 (en) Charging session management method and apparatus
US9949191B2 (en) Methods, devices and computer programs for providing a service or service component requiring a specific packet-forwarding treatment
WO2019228214A1 (fr) Procédé et appareil pour établir une porteuse radio et surveiller un flux de services
EP2521305B1 (fr) Procédé, dispositif et système destinés à commander une police de séance d'utilisateur
KR101425327B1 (ko) 다이어미터 세션 검사
JP5830185B2 (ja) ネットワークリソースを管理するための方法及びノード並びに対応するシステム及びコンピュータプログラム
WO2014000260A1 (fr) Procédé de traitement de qos, serveur d'application, élément de réseau de commande de qos et réseau mobile
JP2015526041A (ja) 課金セッションを終了すべきことを判定するデバイスおよびそのシステム
EP2139280A1 (fr) Procédé pour le traitement du relèvement et dispositif de gestion mobile
WO2011110021A1 (fr) Procédé et système de commande de politique et dispositif de commande de politique
KR20220133250A (ko) QoS 통지를 위한 방법 및 네트워크 노드
WO2017128819A1 (fr) Procédé et appareil de contrôle de politique et de facturation basés sur une application, et support de stockage
WO2009056046A1 (fr) Procédé de fin de session
US10205659B2 (en) Information transmission using direct HPCRF communications
JP2022524738A (ja) 課金方法および装置
WO2016206071A1 (fr) Procédé de liaison de porteuse et équipement associé
WO2022200839A1 (fr) Commande de charge de fonction de plan utilisateur (upf)
CN108781475B (zh) 一种事件上报的方法及装置
WO2024055815A1 (fr) Procédé de gestion de psa de périphérie, dispositif électronique et support lisible par ordinateur
WO2013116978A1 (fr) Procédé, dispositif et système permettant de traiter une demande de ressource utilisateur
KR100974659B1 (ko) 이동통신 시스템에서 보존모드의 세션 관리 방법
US20140050098A1 (en) Handling session linking status in gxx update

Legal Events

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

Ref document number: 15895971

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15895971

Country of ref document: EP

Kind code of ref document: A1