WO2017128817A1

WO2017128817A1 - Third-party application access method and apparatus

Info

Publication number: WO2017128817A1
Application number: PCT/CN2016/106361
Authority: WO
Inventors: 周晓云; 郭文洁
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-01-25
Filing date: 2016-11-18
Publication date: 2017-08-03
Also published as: CN106998543A

Abstract

Disclosed are a third-party application access method and apparatus. The method comprises: formulating a flow-oriented policy and a charging policy corresponding to the flow-oriented policy when a UE accesses a third-party application, wherein the flow-oriented policy comprises a downlink flow-oriented policy and/or an uplink flow-oriented policy; and notifying a flow-oriented policy execution function entity of the flow-oriented policy and the charging policy.

Description

Third party application access method and device

Technical field

The present invention relates to the field of communications, and in particular to a third party application access method and apparatus.

Background technique

FIG. 1 is a schematic diagram of a Policy and Charging Control (PCC) architecture defined by a 3rd Generation Partnership Project (3GPP) in the related art, as shown in FIG. The Policy and Charging Rules Function (PCRF) is used to define the Quality of Service (QoS) and the charging policy for the service using network resources. The PCRF needs to combine the service information received from the Application Function (AF), the user subscription information received from the Subscription Profile Repository (SPR), and the policy configured by the operator. The PCRF sends the control policy for the service to the Policy and Charging Enforcement Function (PCEF) or the Bearer Binding and Event Report Function (BBERF). At the same time, the PCRF can subscribe to the bearer layer related events to the PCEF and/or the BBERF to sense in time when the bearer layer occurs, and change the control strategy. In addition, the PCEF and the Traffic Detection Function (TDF) can perform application detection according to the PCC rules (PCEF) or Application Detection and Control (ADC) rules (TDF) delivered by the PCRF. control function. The Traffic Steering Supporting Function (TSSF) is used to obtain the service routing control policy from the PCRF and perform pre-configuration actions.

In the related art, the PCEF can be used according to the charging policy in the PCC rule delivered by the PCRF. Statistics such as the traffic and duration generated by the user's service access are collected and reported to the accounting system for accounting.

Currently, operators deploy mobile service value-added networks to improve the Quality of Experience (QoE), reduce network bandwidth pressure, and provide value-added services. The industry proposes a dynamic service chain scheme of the local area network SGi-LAN as shown in FIG. 2 to adapt to flexible and rapid service deployment changes, and at the same time reduce capital expenditure (CAPital eXpenditure, referred to as CAPX), and FIG. 2 is related technology. Schematic diagram of the architecture supporting dynamic business chains.

The PCRF can be used as a service chain selection decision entity. The PCRF has the following two functions:

Receiving the service chain description delivered by the configuration management system, and the user attribute/access type/service type/service chain weight corresponding to the service chain, thereby obtaining a static policy corresponding to the service chain;

Obtain the user's subscription information from the SPR, obtain the user dynamic access information from the BBERF/PCEF, and combine the static policy corresponding to the service chain obtained above to establish a Traffic Steering Control (TSC) policy in the access process. The traffic classifier function (TCF) is notified. The TSC policy usually includes a description of the service data flow and a corresponding service chain identity. The service data flow description may be an application identifier or a service data flow filter;

Traffic Steering Control Enforcement Function (TSCEF) (TSCEF can be integrated on PCEF, TDF, or it can be separate, that is, Traffic Steering Support Function (TSSF) has the following functions: The TSC policy sent by the PCRF performs the TSC policy according to the pre-configured action after detecting the service data. The data packet of the service data stream can be dynamically routed to the corresponding service function (Service Function), also called the enabler. (Enabler).

In order to introduce new business functions faster and to effectively deploy special business functions that are not familiar to mobile operators, mobile operators allow third-party application providers to apply their own services to third parties on (S)Gi-LAN. Features. The network needs to be able to be based on third-party applications Request to develop a corresponding business chain strategy to route data to application functions deployed by third-party applications. The operator also needs to perform statistical accounting on the application data of the application function that is routed to the third-party application deployment. However, there is currently no mechanism to support this need.

For the problem that the application data in the related art cannot be statistically charged for the application data of the application function that is routed to the third-party application deployment, an effective solution has not been proposed yet.

Summary of the invention

The embodiments of the present invention provide a third-party application access method and device, so as to solve at least the problem that the application data in the network that cannot be applied to the third-party application can be statistically charged.

According to an aspect of the embodiments of the present invention, a third-party application access method is provided, including: formulating a traffic-oriented policy for a user equipment (UE) to access a third-party application, and a charging policy corresponding to the traffic-oriented policy The traffic steering policy includes a downlink traffic steering policy and/or an uplink traffic steering policy; and the traffic steering policy and the charging policy are notified to the traffic steering policy enforcement function entity.

In an embodiment of the present invention, the notifying the traffic steering policy and the charging policy to the traffic steering policy execution function entity includes: carrying the identifier of the traffic steering policy and the charging policy And in the predetermined rule; sending the predetermined rule to the traffic steering policy execution function entity.

In an embodiment of the present invention, the formulating the charging policy includes: if the traffic steering policy indicates that the data of the UE accessing the third-party application is directed to a service function deployed by the third-party application, And formulating the corresponding charging policy for the traffic steering policy.

In an embodiment of the present invention, the traffic steering policy execution function entity includes one of the following: a policy and charging execution function PCEF, a service checking function TDF, and a traffic steering support function TSSF.

According to another aspect of an embodiment of the present invention, a third party application access method is provided, The traffic guidance policy for the user equipment UE accessing the third party application and the charging policy corresponding to the traffic steering policy determined by the receiving policy and the charging rule function PCRF, wherein the traffic steering policy includes downlink traffic steering a policy and/or an upstream traffic steering policy; performing the traffic steering policy and the charging policy.

In an embodiment of the present invention, the receiving, by the PCRF, the traffic steering policy that is used by the UE to access the third-party application, and the charging policy that is corresponding to the traffic-oriented policy, includes: Receiving a predetermined rule from the PCRF, where the predetermined rule carries an identifier of the traffic steering policy and the charging policy.

In an embodiment of the present invention, the performing the traffic steering policy and the charging policy includes: charging, according to the charging policy, data of the third party application accessed by the UE, and generating the The charging information is reported to the charging system, where the charging information carries the identifier of the traffic steering policy.

In an embodiment of the present invention, the downlink data of the third-party application of the UE is charged according to the charging policy corresponding to the downlink traffic-directed policy, and the generated first charging information is reported to the The charging system, wherein the first charging information carries an identifier of the downlink traffic steering policy, and/or the third party accesses the third party according to a charging policy corresponding to the uplink traffic guiding policy The uplink data of the application is used for charging, and the generated second charging information is reported to the charging system, where the second charging information carries the identifier of the uplink traffic guiding policy.

According to another aspect of the present invention, a third-party application access apparatus is provided, including: a setting module configured to formulate a traffic-oriented policy for a user equipment UE to access a third-party application, and corresponding to the traffic-oriented policy The charging policy, wherein the traffic steering policy includes a downlink traffic steering policy and/or an uplink traffic steering policy; the notification module is configured to notify the traffic steering policy and the charging policy to the traffic steering policy execution function entity .

In an embodiment of the present invention, the formulating module includes: formulating a unit, and configuring When the data indicating that the UE accesses the third-party application is directed to the service function deployed by the third-party application, the corresponding traffic policy is formulated for the traffic-oriented policy.

The formulating module, the notification module, and the formulating module may use a central processing unit (CPU), a digital signal processor (DSP, Digital Singnal Processor), or a programmable logic array (FPGA) when performing processing. , Field-Programmable Gate Array) implementation.

According to another aspect of an embodiment of the present invention, a policy and charging rule function PCRF is provided, including the above-described third party application access device.

According to another aspect of the present invention, another third-party application access device is provided, including: a receiving module configured to learn, when the user equipment UE accesses a third-party application, determined by the policy and charging rule function PCRF And a traffic policy corresponding to the traffic policy: the traffic policy includes a downlink traffic policy and/or an uplink traffic policy; and an execution module configured to execute the traffic policy and the Fee strategy.

In an embodiment of the present invention, the execution module includes: a charging unit, configured to perform charging on the data of the third-party application accessed by the UE according to the charging policy, and generate the charging The information is reported to the charging system, where the charging information carries the identifier of the traffic steering policy.

The receiving module, the executing module, and the charging unit may use a central processing unit (CPU), a digital signal processor (DSP), or a programmable logic array when performing processing. FPGA, Field-Programmable Gate Array) implementation.

According to another aspect of an embodiment of the present invention, a traffic steering policy enforcement function entity is provided, including another third party application access device described above.

In an embodiment of the present invention, the traffic steering policy execution function entity includes One of the following: the policy and accounting execution function PCEF, the service check function TDF, and the traffic steering support function TSSF.

According to the embodiment of the present invention, a traffic-oriented policy for a UE to access a third-party application and a charging policy corresponding to the traffic-oriented policy are adopted, where the traffic-directed policy includes a downlink traffic-directed policy and/or an uplink traffic. Orienting a policy; notifying the traffic steering policy and the charging policy to the traffic steering policy enforcement function entity. The problem that the application data of the application function that is routed to the third-party application cannot be statistically charged is solved in the network in the related art, and the application data of the application function for routing to the third-party application deployment is calculated. The effect of the fee.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

1 is a PCC architecture diagram defined by 3GPP in the related art;

2 is a schematic diagram of an architecture supporting a dynamic service chain in the related art;

3 is a flowchart of a first method for accessing a third party application according to an embodiment of the present invention;

4 is a flowchart of a second method for accessing a third party application according to an embodiment of the present invention;

5 is a flowchart of a PCEF performing a TSC policy and performing charging according to an embodiment of the present invention;

6 is a flow chart of a TDF or TSSF performing a TSC policy and performing charging according to an embodiment of the present invention;

7 is a structural block diagram of a first type of third party application access device according to an embodiment of the present invention;

FIG. 8 is a structural block diagram of a policy and charging rule function PCRF according to an embodiment of the present invention; FIG.

9 is a structural block diagram of a second type of third party application access device according to an embodiment of the present invention;

FIG. 10 is a structural block diagram of a traffic steering policy execution function entity according to an embodiment of the present invention.

detailed description

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

It is to be understood that the terms "first", "second" and the like in the specification and claims of the present invention are used to distinguish similar objects, and are not necessarily used to describe a particular order or order.

A third-party application access method is provided in this embodiment. FIG. 3 is a flowchart of a first third-party application access method according to an embodiment of the present invention. As shown in FIG. 3, the process includes the following steps:

Step S302, a traffic-oriented policy for a user equipment (User Equipment, UE for short) to access a third-party application, and a charging policy corresponding to the traffic-oriented policy, where the traffic-oriented policy includes a downlink traffic-oriented policy and/or Or an upstream traffic steering strategy;

In step S304, the traffic steering policy and the charging policy are notified to the traffic steering policy execution function entity.

Wherein, the above operation may be performed by a PCRF.

Through the foregoing steps, the PCRF may formulate a downlink traffic steering policy and/or an uplink traffic steering policy of the UE, and a charging policy corresponding to the downlink traffic steering policy and/or a charging policy corresponding to the uplink traffic steering policy, thereby implementing The UE accesses the third-party application to formulate a corresponding service chain policy, so as to route the data to the application function of the third-party application deployment, and implement the purpose of statistical accounting for the application data of the application function that is routed to the third-party application deployment. The problem that the application data of the application function that is routed to the third-party application cannot be statistically charged in the network in the related art, and the application data of the application function that is routed to the third-party application deployment is statistically charged. Effect.

In an optional embodiment, notifying the traffic steering policy and the charging policy to the traffic steering policy execution function entity includes: carrying the identifier of the traffic steering policy and the charging policy In the predetermined rule; the predetermined rule is sent to the traffic steering policy execution function entity. The traffic-oriented policy execution function entity may be configured to correspond to different predetermined rules. For example, when the traffic-oriented policy execution function entity is a PCEF, the corresponding predetermined rule is a PCC rule; and when the traffic-oriented policy execution function entity is a TDF, Or the traffic steering support function TSSF, the corresponding predetermined rule is the ADC rule. In an optional embodiment, the carrying the foregoing traffic-oriented policy identifier and the charging policy in the predetermined rule includes: adding a traffic-oriented policy attribute value pair and a charging policy attribute value pair in the predetermined rule; The charging policy for charging the provider of the third-party application in the identifier of the traffic-oriented policy and the charging policy is carried in the traffic-oriented policy attribute value pair, and the charging policy is used to charge the UE. The charging policy is carried in the charging policy attribute value pair; or the charging policy used to charge the UE in the identifier of the traffic steering policy and the charging policy is carried in the traffic steering policy attribute value pair, and The charging policy used for charging the provider of the third-party application in the foregoing charging policy is carried in the charging policy attribute value pair. Therefore, in this embodiment, the charging policy includes two charging policies, one is a charging policy for the UE, and the other is a charging policy for the operator of the third-party application. Therefore, the UE and the third-party application operator can be separately charged, and the two charging policies can be the same or different, and a more reasonable charging is achieved.

In an optional embodiment, when the foregoing charging policy is formulated, the foregoing charging policy may be formulated if a predetermined condition is met, for example, if the traffic steering policy indicates that the UE accesses the third-party application. The service function that is directed to the third-party application deployment formulates a corresponding charging policy for the traffic-oriented policy.

In an optional embodiment, the foregoing traffic-oriented policy enforcement function entity may include one of the following: a policy and charging execution function PCEF, a service check function TDF, and a traffic steering support function TSSF.

A third-party application access method is also provided in this embodiment. FIG. 4 is a flowchart of a second third-party application access method according to an embodiment of the present invention. As shown in FIG. 4, the process includes The following steps:

Step S402, the traffic steering policy for the user equipment UE accessing the third party application and the charging policy corresponding to the traffic steering policy determined by the policy and charging rule function PCRF, wherein the traffic steering policy includes a downlink traffic steering policy And/or upstream traffic-oriented strategies;

Step S404, executing the foregoing traffic steering policy and charging policy.

The following operations may be performed by one of the following traffic-oriented policy enforcement functional entities: PCEF, TDF, and TSSF.

Through the above steps, the PCRF can formulate a downlink traffic steering policy and/or an uplink traffic steering policy of the UE, and a corresponding charging policy, thereby implementing a corresponding service chain policy for the UE to access the third-party application, so as to route the data to the first The application function of the three-party application deployment, and the purpose of performing statistical accounting for the application data of the application function that is routed to the third-party application deployment, and solving the application in the related technology that cannot be deployed to the third-party application in the network. The application data of the function performs the problem of statistical accounting, thereby achieving the effect of performing statistical accounting on the application data of the application function that is routed to the third-party application deployment.

In an optional embodiment, the receiving, by the PCRF, the traffic steering policy for the UE to access the third-party application and the charging policy corresponding to the traffic-directed policy include: receiving a predetermined rule from the PCRF, where The predetermined rule carries the identifier and charging policy of the above traffic steering policy. The traffic-oriented policy execution function entity may be configured to correspond to different predetermined rules. For example, when the traffic-oriented policy execution function entity is a PCEF, the corresponding predetermined rule is a PCC rule; and when the traffic-oriented policy execution function entity is a TDF, Or the traffic steering support function TSSF, the corresponding predetermined rule is the ADC rule. In an optional embodiment, the manner in which the foregoing predetermined rule carries the identifier and the charging policy of the traffic steering policy includes: the identifier of the traffic steering policy attribute value added in the predetermined rule carries the identifier of the traffic steering policy, And a charging policy for charging a provider of the third-party application in the foregoing charging policy; and carrying the charging policy attribute value pair added in the foregoing predetermined rule The charging policy used to charge the UE in the charging policy; or the traffic-oriented policy attribute value pair added in the foregoing predetermined rule carries the identifier of the traffic-directed policy, and is used in the charging policy The charging policy for charging the UE; and the charging policy attribute value pair added in the foregoing predetermined rule carries the charging policy for charging the provider of the third-party application in the charging policy. Therefore, in this embodiment, the charging policy includes two charging policies, one is a charging policy for the UE, and the other is a charging policy for the operator of the third-party application. Therefore, the UE and the third-party application operator can be separately charged, and the two charging policies can be the same or different, and a more reasonable charging is achieved. In an optional embodiment, the UE may be configured to access the third-party application according to the foregoing traffic-directed policy and the charging policy: routing the service data of the UE to the application function of the third-party application deployment according to the foregoing traffic-oriented policy; The charging policy for charging the provider of the third-party application in the charging control policy charges the foregoing provider, and according to the charging policy pair used for charging the UE in the charging control policy The UE performs charging; wherein, when there is no charging policy for charging the provider of the third-party application in the charging control policy, the charging policy to the provider for charging the UE according to the foregoing Performing charging; and/or, when there is no charging policy for charging the UE in the foregoing charging control policy, the charging policy for charging the provider of the third-party application to the UE Billing. In this embodiment, it is ensured that the reasonable charging can be achieved even if there is no charging policy for charging the UE, or if there is no charging policy for charging the operator of the third-party application. .

In an optional embodiment, the performing the traffic-oriented policy and the charging policy includes: charging the data of the third-party application by the UE according to the charging policy, and reporting the generated charging information to the charging system. The charging information carries the identifier of the traffic steering policy.

In an optional embodiment, the method includes: charging, according to the charging policy corresponding to the downlink traffic steering policy, the downlink data of the third-party application, and reporting the generated first charging information to the charging system. Where the first charging information carries a downstream traffic guide The identifier of the policy, and/or, according to the charging policy corresponding to the uplink traffic-directed policy, the uplink data of the UE accessing the third-party application is charged, and the generated second charging information is reported to the charging system, where the second The charging information carries the identifier of the uplink traffic steering policy.

The invention is exemplified below in connection with PCEF and TDF/TSSF, respectively.

Example 1

This embodiment describes a related processing procedure when the TCEEF is located on the PCEF, and FIG. 5 is a flowchart of the PCEF performing the TSC policy and performing charging according to an embodiment of the present invention. As shown in FIG. 5, the process includes the following steps:

Step S501: The user equipment UE is attached to the network, initiates an attach procedure, or the UE initiates another packet data network (Packet Data Network, PDN for short) connection establishment process. The gateway where the PCEF is located receives the above request message.

Step S502: After receiving the attach request or the PDN connection establishment request, the PCEF initiates an Internet Protocol Connectivity Access Network (IP-CAN) session establishment request to the PCRF, and provides the user identifier and the PDN identifier to the PCRF. Information such as IP address.

Step S503: If there is no defined user subscription information, the PCRF obtains user subscription information, such as user level, bandwidth allocated to the user, service that allows the user to access (ie, allows the UE to access), service chain, and the like. The PCRF makes policy decisions and formulates PCC rules. The TPC policy is carried in the PCC rule, which carries the traffic steering policy identifier and the corresponding charging policy. The PCRF may issue one or more PCC rules at the same time in this step.

If the uplink data of the third-party application accessed by the UE is routed to the service function of the third-party application, the PCRF carries the Downlink Traffic Steering Policy Id and the corresponding charging policy in the PCC rule; The downlink data of the third-party application is routed to the Service Function of the third-party application deployment, then the PCRF is in the PCC. The rule carries the upstream traffic steering policy to identify the Downlink Traffic Steering Policy Id and the corresponding charging policy. The foregoing charging policy includes indication information using online charging or offline charging, and measurement methods adopted, such as traffic and/or time. In a specific implementation, the charging rule defines an attribute value pair Charging-Rule-Definition AVP (corresponding to the foregoing predetermined rule), and carries a newly defined group type AVP (Attribute Value Pair), that is, a traffic-oriented policy attribute. Value vs. Traffic-Steering-Policy AVP. A Traffic-Steering-Policy-Policy AVP instance carries either a Traffic-Steering-Policy-Identifier-DL AVP or a Traffic-Steering-Policy-Identifier-UL AVP. If the downlink data of the third-party application accessed by the UE is routed to the service function of the third-party application deployment, the PCRF carries the Traffic-Steering-Policy-Identifier-DL AVP in the Traffic-Steering-Policy AVP, and sets the corresponding value. The AVP that carries the other charging policies is set to the corresponding value. If the uplink data of the third-party application accessed by the UE is routed to the service function deployed by the third-party application, the PCRF carries Traffic-Steering in the Traffic-Steering-Policy AVP. Policy-Identifier-UL AVP, and set the corresponding value. In addition, it carries other accounting policies AVP and sets the corresponding values. If the Traffic-Steering-Policy ACP does not carry the rating group attribute value pair Rating-Group AVP, the online attribute value pair Online AVP, the offline attribute value pair Offline AVP and the measurement method attribute value to the Metering-Method AVP, etc. Or multiple, the PCFE will perform the charging policy according to the corresponding value carried in the Charging-Rule-Definition AVP level. A Charging-Rule-Definition AVP instance may contain one or two Traffic-Steering-Policy AVP instances (ie, carrying a Traffic-Steering-Policy AVP instance containing Traffic-Steering-Policy-Identifier-DL AVP or containing Traffic-Steering -Policy-Identifier-UL AVP's Traffic-Steering-Policy AVP instance or a Traffic-Steering-Policy AVP instance with a Traffic-Steering-Policy-Identifier-DL AVP and one containing Traffic-Steering-Policy-Identifier-UL AVP's Traffic-Steering-Policy AVP instance).

among them,

Step S504: The PCEF installs the delivered PCC rule.

Step S505: The gateway where the PCEF is located returns an attach request or a response message for establishing a PDN connection request to the UE.

Step S506: The UE initiates access to the third-party application.

Step S507: The PCEF performs application detection or service data flow identification according to the PCC rule, and detects data of the application. The PCEF performs a TSC policy on the application data, that is, performs a specific operation corresponding to the Traffic Steering Policy Id configured in the PCEF. At the same time, the PCEF needs to charge the application data according to the charging policy corresponding to the Traffic Steering Policy Id.

Step S508: The PCEF is based on the charging policy of the Charging-Rule-Definition AVP level (that is, the charging policy carried outside the Traffic-Steering-Policy AVP, such as Rating-Group AVP, Online AVP, Offline AVP, and/or Metering- Method AVP) Third party to UE access The data of the application is used for statistics, and the PCEF collects data of the third-party application accessed by the UE according to the charging policy carried by the Traffic-Steering-Policy AVP (the data is directed to the service function of the third-party application deployed in the carrier network) Perform statistics.

Step S509: When the condition for reporting the charging information is met (the condition of the reporting CDR is the PCEF local configuration or the online charging system (OCS) or the offline charging system (Offline Charging System, referred to as OFCS). Subscribe), PCEF generates billing information (such as Call Detail Record (CDR)) and reports it to OCS or OFCS. The billing information includes the Traffic Steering Policy Id and corresponding statistics. Specifically, if the Traffic-Steering-Policy-Policy AVP carries the Traffic-Steering-Policy-Identifier-DL AVP, the accounting information includes the Downlink Traffic Steering Policy Id and the corresponding statistics information, if the Traffic-Steering-Policy AVP is carried in the Traffic-Steering-Policy AVP. The Traffic-Steering-Policy-Identifier-UL AVP carries the Uplink Traffic Steering Policy Id and corresponding statistics. The statistical information is the traffic and/or duration (ie, the data traffic and/or duration of the business function directed to the third party application). In addition, the charging information may further include a user identifier, a PDN identifier, a sponsor Sponsor Id, and/or an Application Service Provider (ASP) Id.

In step S510, the OCS or OFCS returns an acknowledgement message to the PCEF.

Example 2

This embodiment describes a related processing procedure when the TCEEF is located on the TDF or the TSSF, and FIG. 6 is a flowchart of the TSF or TSSF performing the TSC policy and performing charging according to an embodiment of the present invention. In this embodiment, a charging related interface exists between the TDF or the TSSF and the OCS or the OFCS. As shown in FIG. 6, the process includes the following steps:

Step S601: The user equipment UE attaches to the network, initiates an attach procedure, or the UE initiates another PDN connection establishment procedure. The gateway where the PCEF is located receives the above request message.

Step S602: After receiving the attach request or the PDN connection establishment request, the PCEF sends the request to the PCRF. The IP-CAN session establishment request is provided, and the PCRF is provided with information such as a user identifier, a PDN identifier, and an IP address.

Step S603: If there is no defined user subscription information, the PCRF obtains user subscription information, such as user level, bandwidth allocated to the user, service allowed to access the user, service chain, and the like, from the SPR. The PCRF performs a policy decision, and the PCRF sends a TDF session establishment request message to the TDF or a TSSF session establishment request message to the TSSF. The message carries an ADC rule, where the established ADC rule carries the TSC policy, that is, carries the traffic steering policy identifier Traffic Steering Policy Id. And the corresponding billing strategy. The PCRF may also provide a User Identity, PDN Identity, Sponsor Id, and/or ASP Id to the TDF or TSSF. The PCRF may issue one or more ADC rules simultaneously at this step. In a specific implementation, a newly defined group type AVP, that is, a Traffic-Steering-Policy AVP, is carried in the ADC-Rule-Definition AVP. A Traffic-Steering-Policy-Policy AVP instance carries either a Traffic-Steering-Policy-Identifier-DL AVP or a Traffic-Steering-Policy-Identifier-UL AVP. If the downlink data of the third-party application accessed by the UE is routed to the service function of the third-party application deployment, the PCRF carries the Traffic-Steering-Policy-Identifier-DL AVP in the Traffic-Steering-Policy AVP, and sets the corresponding value. The AVP that carries the other charging policies is set to the corresponding value. If the uplink data of the third-party application accessed by the UE is routed to the service function deployed by the third-party application, the PCRF carries Traffic-Steering in the Traffic-Steering-Policy AVP. Policy-Identifier-UL AVP, and set the corresponding value. In addition, it carries other accounting policies AVP and sets the corresponding values. If the Traffic-Steering-Policy AVP does not carry any one or more of the Rating-Group AVP, Online AVP, Offline AVP, and Metering-Method AVP, the TDF or TSSF will be carried according to the ADC-Rule-Definition AVP level. The value is used to perform the accounting policy. An ADC-Rule-Definition AVP instance can contain 1 or 2 Traffic-Steering-Policy AVP instances (ie carrying one) Traffic-Steering-Policy-Identifier-DL AVP Traffic-Steering-Policy AVP instance or Traffic-Steering-Identifier-Policy AVP instance containing Traffic-Steering-Policy-Identifier-UL AVP or both carrying a Traffic-Steering-Policy-Identifier - Traffic-Steering-Policy AVP instance of DL AVP and a Traffic-Steering-Policy AVP instance with Traffic-Steering-Policy-Identifier-UL AVP).

among them,

Step S604: The TDF or the TSSF installs and executes the delivered ADC rule.

Step S605: The TDF or the TSSF returns an acknowledgement message to the PCRF.

Step S606: The PCRF returns a response to the PCEF that the IP-CAN session is successfully established, and carries the PCC rule.

Step S607: The gateway where the PCEF is located returns an attach request or a response message for establishing a PDN connection request to the UE.

Step S608: The UE initiates access to the application, performs signaling interaction with the application server, and the UE accesses the service by using an ordinary user identity.

Step S609: The TDF or the TSSF performs application detection or service data flow identification according to the ADC rule, and detects data of the application. The TDF or TSSF performs a TSC policy on the application data, that is, performs a specific operation corresponding to the Traffic Steering Policy Id configured in the TDF or TSSF. At the same time, the TDF or the TSSF needs to charge the application data according to the charging policy corresponding to the Traffic Steering Policy Id.

Step S610: The TDF or the TSSF is based on the charging policy of the ADC-Rule-Definition AVP level (that is, the charging policy carried outside the Traffic-Steering-Policy AVP, such as Rating-Group AVP, Online AVP, Offline AVP, and/or Metering). - Method AVP) Statistics of the data of the third-party application accessed by the UE, and the TDF or the TSSF collects statistics on the data of the third-party application accessed by the UE according to the charging policy carried by the Traffic-Steering-Policy AVP.

Step S611: When the condition for reporting the charging information is satisfied, the TDF or the TSSF generates charging information (such as a CDR), and reports the charging information to the OCS or the OFCS. The billing information includes the Traffic Steering Policy Id and corresponding statistics. Specifically, if the Traffic-Steering-Policy-Policy AVP carries the Traffic-Steering-Policy-Identifier-DL AVP, the accounting information includes the Downlink Traffic Steering Policy Id and the corresponding statistics information, if the Traffic-Steering-Policy AVP is carried in the Traffic-Steering-Policy AVP. The Traffic-Steering-Policy-Identifier-UL AVP carries the Uplink Traffic Steering Policy Id and the corresponding statistics. The statistical information is the traffic and/or duration (ie, the data traffic and/or duration of the business function directed to the third party application). In addition, the charging information may further include a user identifier, a PDN identifier, a Sponsor Id, and/or an ASP Id.

Step S612: The OCS or OFCS returns an acknowledgement message to the TDF or TSSF.

In the above embodiment, the PCC or ADC rules are respectively provided to the PCEF or TDF/TSSF during the IP-CAN session establishment process, and in other embodiments, the IPC CAN session modification process may also be used to modify the PCC or ADC rules. Provided separately to PCEF or TDF/TSSF.

In the above embodiment, the Traffic-Steer-Policy AVP is carried in the dynamic PCC or ADC rules provided to the PCEF or TDF/TSSF. In other embodiments, the Traffic-Steer-Policy AVP is also configured with only predefined PCC rules or ADCs. rule. The PCRF can activate the charging policy as long as the predefined PCC rules or ADC rules are activated.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a plurality of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the embodiments of the present invention. Methods.

In the embodiment, a third-party application access device is also provided, which is used to implement the foregoing embodiments and preferred embodiments, and is not described again. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 7 is a structural block diagram of a first type of third party application access device according to an embodiment of the present invention. As shown in FIG. 7, the device includes a formulation module 72 and a notification module 74, which will be described below.

The formulating module 72 is configured to formulate a traffic-oriented policy for the UE to access the third-party application and a charging policy corresponding to the traffic-oriented policy, where the traffic-directed policy includes a downlink traffic-oriented policy and/or an uplink traffic-oriented policy; The notification module 74 is connected to the foregoing setting module 72, and configured to notify the traffic steering policy execution function entity to the traffic steering policy and the charging policy.

In an optional embodiment, the notification module 74 may notify the traffic steering policy execution function entity to the traffic steering policy execution function entity by: carrying the identifier of the traffic steering policy and the charging policy in a predetermined rule. And sending the predetermined rule to the traffic steering policy execution function entity. The different traffic-oriented policy enforcement function entities may correspond to different predetermined rules. For example, when the predetermined function entity is a PCEF, the corresponding predetermined rule is a PCC rule; when the predetermined function entity is a TDF or a traffic-oriented support function TSSF The corresponding predetermined rule is the ADC rule. In an optional embodiment, the notification module 74 may carry the identifier and charging policy of the traffic steering policy in a predetermined rule by adding a traffic steering policy attribute value pair and charging in the predetermined rule. The policy attribute value pair; the charging policy for charging the third-party application provider in the identifier of the traffic-directed policy and the charging policy is carried in the traffic-oriented policy attribute value pair, and The charging policy used for charging the UE in the charging policy is carried in the charging policy attribute value pair; or the charging of the traffic steering policy and the charging policy used to charge the UE The policy is carried in the traffic-oriented policy attribute value pair, and the charging policy used for charging the provider of the third-party application in the foregoing charging policy is carried in the charging policy attribute value pair. Therefore, in this embodiment, the charging policy includes two charging policies, one is a charging policy for the UE, and the other is a charging policy for the operator of the third-party application. Therefore, the UE and the third-party application operator can be separately charged, and the two charging policies can be the same or different, and a more reasonable charging is achieved.

In an optional embodiment, the foregoing formulating module 72 includes a determining unit configured to formulate the foregoing charging policy when the foregoing charging policy is formulated, for example, if the foregoing traffic is used. When the directed policy indicates that the data of the third-party application is directed to the service function deployed by the third-party application, the corresponding charging policy is formulated for the traffic-oriented policy.

FIG. 8 is a structural block diagram of a policy and charging rule function PCRF according to an embodiment of the present invention. As shown in FIG. 8, the PCRF 82 includes the first type of third party application access device 84 described above.

FIG. 9 is a structural block diagram of a second type of third party application access device according to an embodiment of the present invention. As shown in FIG. 9, the device includes a receiving module 92 and an executing module 94, which will be described below.

The receiving module 92 is configured to learn the traffic steering policy and the charging policy corresponding to the traffic steering policy, where the user equipment UE accesses the third party application determined by the policy and charging rule function PCRF, where the traffic steering policy includes the downlink policy. a traffic steering policy and/or an upstream traffic steering policy; an execution module 94, coupled to the receiving module 92, configured to perform the traffic steering Policy and billing strategy.

In an optional embodiment, the receiving module 92 may receive the traffic steering policy and the charging policy corresponding to the traffic steering policy by receiving a predetermined rule from the PCRF, where the predetermined rule carries the foregoing The identification and charging policy of the traffic-oriented policy. The traffic-oriented policy execution function entity may be configured to correspond to different predetermined rules. For example, when the traffic-oriented policy execution function entity is a PCEF, the corresponding predetermined rule is a PCC rule; and when the traffic-oriented policy execution function entity is a TDF, Or the traffic steering support function TSSF, the corresponding predetermined rule is the ADC rule. In an optional embodiment, the manner in which the foregoing predetermined rule carries the identifier and the charging policy of the traffic steering policy includes: the identifier of the traffic steering policy attribute value added in the predetermined rule carries the identifier of the traffic steering policy, And a charging policy for charging a provider of the third-party application in the foregoing charging policy; and the charging policy attribute value pair added in the foregoing predetermined rule carries the charging policy for the UE The charging policy for performing charging; or the traffic-oriented policy attribute value pair added in the foregoing predetermined rule carries the identifier of the traffic-directed policy, and the charging policy used for charging the UE in the charging policy. And the charging policy attribute value pair added in the foregoing predetermined rule carries the charging policy used for charging the provider of the third-party application in the foregoing charging policy. Therefore, in this embodiment, the charging policy includes two charging policies, one is a charging policy for the UE, and the other is a charging policy for the operator of the third-party application. Therefore, the UE and the third-party application operator can be separately charged, and the two charging policies can be the same or different, and a more reasonable charging is achieved. In an optional embodiment, the execution module 94 may further control the UE to access the third-party application by: routing the service data of the UE to the application function of the third-party application deployment according to the foregoing traffic-oriented policy; The charging policy for charging the provider of the third-party application in the fee control policy charges the foregoing provider, and according to the charging policy used for charging the UE in the charging control policy Performing charging; wherein, when the above charging control policy does not exist When charging a charging policy for a provider of a third-party application, charging the provider according to the foregoing charging policy for charging the UE; and/or, when the charging control policy is not When there is a charging policy for charging the UE, the UE is charged according to the foregoing charging policy for charging the provider of the third-party application. In this embodiment, it is ensured that the reasonable charging can be achieved even if there is no charging policy for charging the UE, or if there is no charging policy for charging the operator of the third-party application. .

In an optional embodiment, the foregoing execution module 94 may include a charging unit, and the charging unit may perform charging on the data of the third-party application accessed by the UE according to the charging policy, and report the generated charging information to the accounting information. The charging system, wherein the charging information carries the identifier of the traffic steering policy.

In an optional embodiment, the executing module 94 may perform charging on the downlink data of the third-party application, and report the generated first charging information to the charging according to the charging policy corresponding to the downlink traffic steering policy. The system, wherein the first charging information carries an identifier of a downlink traffic steering policy, and/or, according to a charging policy corresponding to the uplink traffic steering policy, performs charging on the uplink data of the UE accessing the third-party application, and generates the The second charging information is reported to the charging system, where the second charging information carries the identifier of the uplink traffic steering policy.

FIG. 10 is a structural block diagram of a traffic steering policy execution function entity according to an embodiment of the present invention. As shown in FIG. 10, the traffic steering policy enforcement function entity 102 includes the second third-party application access device 104 described above.

In an optional embodiment, the traffic steering policy enforcement function entity 102 may include one of the following: a policy and charging execution function PCEF, a service checking function TDF, and a traffic steering support function TSSF.

It should be noted that each of the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.

Embodiments of the present invention also provide a storage medium. Optionally, in the embodiment, the foregoing storage medium may be configured to store program code for performing the following steps:

S11, a traffic-oriented policy for the UE to access the third-party application, and a charging policy corresponding to the traffic-oriented policy, where the traffic-oriented policy includes a downlink traffic-oriented policy and/or an uplink traffic-oriented policy;

S12. Notify the traffic steering policy and the charging policy to the traffic steering policy execution function entity.

Optionally, the storage medium is further arranged to store program code for performing the following steps:

S21. The traffic policy and the charging policy corresponding to the traffic steering policy, where the user equipment UE accesses the third-party application, and the traffic-oriented policy includes a downlink traffic-oriented policy and / or upstream traffic-oriented strategy;

S22. Perform the foregoing traffic steering policy and charging policy.

Optionally, in the embodiment, the foregoing storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (RAM). A variety of media that can store program code, such as a hard disk, a disk, or an optical disk.

Optionally, in this embodiment, the processor executes the steps in the foregoing method embodiments according to the stored program code in the storage medium.

For example, the specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. Execution shown or described The steps are either made into individual integrated circuit modules, or a plurality of modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

The embodiment of the present invention adopts a traffic-oriented policy for the UE to access a third-party application and a charging policy corresponding to the traffic-oriented policy, where the traffic-oriented policy includes a downlink traffic-oriented policy and/or an upstream traffic-oriented policy. The policy: notifying the traffic steering policy and the charging policy to the traffic steering policy enforcement function entity. The problem that the application data of the application function that is routed to the third-party application cannot be statistically charged is solved in the network in the related art, and the application data of the application function for routing to the third-party application deployment is calculated. The effect of the fee.

Claims

A third-party application access method, including:

a traffic-oriented policy for the user equipment UE to access the third-party application and a charging policy corresponding to the traffic-oriented policy, where the traffic-oriented policy includes a downlink traffic-directed policy and/or an upstream traffic-oriented policy;

Notifying the traffic steering policy and the charging policy to the traffic steering policy enforcement function entity.
The method according to claim 1, wherein the notifying the traffic steering policy and the charging policy to the traffic steering policy execution function entity comprises:

And carrying the identifier of the traffic steering policy and the charging policy in a predetermined rule;

Sending the predetermined rule to the traffic steering policy enforcement function entity.
The method of claim 1, wherein formulating the charging policy comprises:

If the traffic-oriented policy indicates that the data of the third-party application is directed to the service function of the third-party application deployment, the corresponding traffic policy is formulated for the traffic-oriented policy.
The method according to any one of claims 1 to 3, wherein the traffic steering policy enforcement function entity comprises one of the following:

Policy and billing execution function PCEF, service check function TDF, and traffic steering support function TSSF.
A third-party application access method, including:

Receiving a traffic-oriented policy for the user equipment UE to access the third-party application and a charging policy corresponding to the traffic-oriented policy, where the traffic-oriented policy includes a downlink traffic-oriented policy and / or upstream traffic-oriented strategy;

Executing the traffic steering policy and the charging policy.
The method of claim 5, wherein receiving the PCRF determined for the The traffic steering policy and the charging policy corresponding to the traffic steering policy when the UE accesses the third-party application includes:

Receiving a predetermined rule from the PCRF, where the predetermined rule carries an identifier of the traffic steering policy and the charging policy.
The method of claim 5, wherein the performing the traffic steering policy and the charging policy comprises:

Charging, according to the charging policy, the data that the UE accesses the third-party application, and reporting the generated charging information to the charging system, where the charging information carries the traffic-oriented policy Logo.
The method of claim 7 comprising:

And performing charging on the downlink data of the third-party application by the UE according to the charging policy corresponding to the downlink traffic-directed policy, and reporting the generated first charging information to the charging system, where the The identifier of the downlink traffic steering policy is carried in a charging information, and/or

And performing charging on the uplink data of the third-party application by the UE according to the charging policy corresponding to the uplink traffic-directed policy, and reporting the generated second charging information to the charging system, where The second charging information carries the identifier of the uplink traffic steering policy.
A third-party application access device, including:

a module for determining a traffic steering policy for the user equipment UE to access the third-party application and a charging policy corresponding to the traffic steering policy, where the traffic steering policy includes a downlink traffic steering policy and/or an uplink traffic Oriented strategy;

The notification module is configured to notify the traffic steering policy execution function entity to the traffic steering policy and the charging policy.
The apparatus of claim 9 wherein said formulating module comprises:

a determining unit, configured to: when the data guiding policy indicates that the data of the UE accessing the third-party application is directed to a service function of the third-party application deployment, The corresponding charging policy is slightly formulated.
A policy and charging rules function PCRF comprising the apparatus of claim 9 or 10.
A third-party application access device, including:

a receiving module, configured to learn, by the policy and charging rule function, a traffic-oriented policy for the user equipment UE to access the third-party application, and a charging policy corresponding to the traffic-oriented policy, where the traffic-oriented policy includes Downstream traffic steering strategy and/or upstream traffic steering strategy;

An execution module is configured to execute the traffic steering policy and the charging policy.
The apparatus of claim 12, wherein the execution module comprises:

a charging unit, configured to perform charging on the data of the third-party application accessed by the UE according to the charging policy, and report the generated charging information to the charging system, where the charging information is carried in the charging information. The identifier of the traffic steering policy.
A traffic steering policy enforcement functional entity comprising the apparatus of claim 12 or 13.
The traffic steering policy enforcement function entity according to claim 14, wherein the traffic steering policy execution function entity comprises one of the following:

Policy and billing execution function PCEF, service check function TDF, and traffic steering support function TSSF.