WO2009006816A1

WO2009006816A1 - Policy control method, device and system for application

Info

Publication number: WO2009006816A1
Application number: PCT/CN2008/071404
Authority: WO
Inventors: Shibi Huang; Yuxin Mao; Peng Zhao; Shiyong Tan; Yan Li; Weihua Wei
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-07-10
Filing date: 2008-06-23
Publication date: 2009-01-15

Abstract

A policy control method and device for an application, and the policy control method for the application includes the following steps: a PCRF acquiring an application service provider identifier; the PCRF making a policy decision according to the application service provider identifier. A policy control and charging rules function entity includes: an acquirement unit, for acquiring the application service provider identifier; a decision unit, for making a policy decision according to the application service provider identifier acquired by the acquirement unit. A policy control method, device and system for the data application are also provided.

Description

应用的策略控制方法、装置及*** Applied strategy control method, device and system

本申请要求于 2007 年 7 月 10 日提交中国专利局、申请号为 This application is submitted to the Chinese Patent Office on July 10, 2007, and the application number is

200710137704.3、发明名称为"数据应用的策略控制方法、装置及***"的中国专利申请的优先权，以及要求于 2007年 9月 28日提交中国专利局、申请号为200710137704.3, the priority of the Chinese patent application entitled "Strategy Control Method, Device and System for Data Application", and the request to be submitted to the Chinese Patent Office on September 28, 2007, the application number is

200710152062.4、发明名称为"一种应用的策略控制方法及装置"的中国专利申请的优先权，其全部内容通过引用结合在本申请中。 200710152062.4, the entire disclosure of which is incorporated herein by reference in its entirety in its entirety in its entirety in the the the the the the the the the the

技术领域 Technical field

本发明涉及通信领域，特别是涉及一种应用的策略控制方法及装置。 The present invention relates to the field of communications, and in particular, to a policy control method and apparatus for an application.

背景技术 Background technique

一、通信网路在向全 IP演进过程中，为了提供令客户满意的业务，需解决端到端的 QoS ( Quality of Service服务质量）问题。 IP网络可以提供各种各样的业务（如 VoIP, 视频点播，文件下载， web浏览等），不同的业务对 QoS有不同的要求，而且对计费的要求也不一样（比如可以釆用在线计费或者离线计费，可以根据流量计费或者根据时间计费等）。为解决上述 QoS和计费相关问题， 3GPP定义了 PCC (策略和计费控制功能 Policy Control and Charging ) 架构，以此满足对不同的业务进行不同的 QoS控制和计费需求。 TS 23.203中对 PCC架构进行了定义，参见图 1所示，其中各实体的功能描述如下： 1. In the evolution of the communication network to the full IP, in order to provide services that satisfy the customer, the end-to-end QoS (Quality of Service) problem needs to be solved. IP networks can provide a variety of services (such as VoIP, video on demand, file download, web browsing, etc.). Different services have different requirements for QoS, and the charging requirements are different (for example, online can be used). Billing or offline billing, which can be based on traffic billing or billing according to time, etc.). To solve the above QoS and charging related issues, 3GPP defines the PCC (Policy and Charging Control Function) architecture to meet different QoS control and charging requirements for different services. The PCC architecture is defined in TS 23.203, as shown in Figure 1, where the functions of each entity are described as follows:

AF ( Application Function ): 应用功能实体。主要为 PCRF ( Policy Control and Charging Rules Function 策略控制和计费规则功能实体）制订策略和计费控制规则动态提供应用层会话信息，例如： IMS中的 P-CSCF就属于 AF。 AF ( Application Function ): Application functional entity. The policy and charging control rules are dynamically provided for the PCRF (Policy Control and Charging Rules Function) to dynamically provide application layer session information. For example, the P-CSCF in the IMS belongs to the AF.

PCRF: 策略控制和计费控制功能实体。根据用户接入网络的限制、用户当前正在进行的应用业务信息、本地运营商配置及用户签约信息，制订相应的策略，并将策略提供给 PCEF ( Policy and Charging Enforcement Function 策略和计费执行功能实体）执行。策略包括：业务数据流检测、 QoS控制、门控和基于流的计费等。 PCRF: Policy Control and Charging Control Function Entity. According to the limitation of the user access network, the application service information currently being performed by the user, the local carrier configuration, and the user subscription information, formulate a corresponding policy and provide the policy to the PCEF (Policy and Charging Enforcement Function and the charging execution function entity). )carried out. Policies include: traffic data flow detection, QoS control, gating, and flow-based charging.

PCEF: 策略和计费执行实体。执行 PCRF下发或指定的策略，即完成对业务数据流的检测、保证业务数据流的 QoS、门控、完成在线 /离线计费以及触发与控制面的会话等功能。例如： GPRS ( General Packet Radio Service 通用无线分组业务）中的 GGSN实体（ Gateway GPRS Support Node GPRS网关支持节点）。 PCEF: Policy and Charging Enforcement Entity. The policy that is delivered or specified by the PCRF is performed, that is, the detection of the service data flow, the QoS of the service data flow, the gating, the completion of the online/offline charging, and the triggering session with the control plane are completed. For example: GGSN entity in GPRS (General Packet Radio Service) (Gateway GPRS Support Node GPRS gateway branch Hold the node).

各接口功能描述如下： The function of each interface is described as follows:

Rx: 该参考点用于 AF下发应用层会话相关信息，包括用于识别业务数据流的 IP过滤器、业务流所需的带宽信息，该接口使用 IETF定义的 Diameter 协议。 Rx: This reference point is used by the AF to deliver application layer session related information, including the IP filter used to identify the service data stream and the bandwidth information required by the service flow. The interface uses the Diameter protocol defined by the IETF.

Gx: 该参考点用于 PCRF动态控制 PCEF执行的 PCC规则。具备以下功能：建立，维护和终止 IP-CAN会话； PCEF向 PCRF请求 PCC规则； PCRF 向 PCEF提供 PCC规则；协商 IP-CAN承载建立模式等。该参考点使用 IETF 定义的 Diameter协议。 Gx: This reference point is used by the PCRF to dynamically control the PCC rules executed by the PCEF. It has the following functions: Establish, maintain and terminate IP-CAN sessions; PCEF requests PCC rules from PCRF; PCRF provides PCC rules to PCEF; Negotiates IP-CAN bearer setup mode. This reference point uses the Diameter protocol defined by the IETF.

其余实体，如 SPR ( Subscription Profile Repository 签约信息库）、 OCS ( Online Charging System在线计费***）、 OFCS ( Offline Charging System 离线计费***）和接口（Sp、 Gy、 Gz ) 与本发明内容无关，这里不再赘述。 The remaining entities, such as SPR (Subscription Profile Repository), OCS (Online Charging System), OFCS (Offline Charging System) and interfaces (Sp, Gy, Gz) are not relevant to the present invention. I won't go into details here.

二、为了更容易理解后续介绍的流程，先阐述几个术语： Second, in order to make it easier to understand the process of the subsequent introduction, several terms are explained first:

IP-CAN: IP Connectivity Access Network 即 IP连接接入网，当用户在接入网络内漫游（位置改变时）仍能保存 IP业务连续性（即不中断业务），具有这样性质的接入网络称为 IP-CAN, 比如 GPRS网络， I-WLAN网络等。 IP-CAN: The IP Connectivity Access Network is an IP-connected access network. When a user roams within the access network (when the location changes), the IP service continuity can still be preserved (ie, the service is not interrupted). For IP-CAN, such as GPRS network, I-WLAN network, etc.

IP-CAN bearer: IP-CAN承载，具有明确速率，延迟和比特率的 IP传输路径（该路径指的是接入网到 PCEF之间 ) , 对于 GPRS来说 IP-CAN承载对应 PDP ( Packet Data Protocol分组数据协议）上下文。 IP-CAN bearer: IP-CAN bearer, IP transmission path with clear rate, delay and bit rate (this path refers to the access network to PCEF). For GPRS, IP-CAN bearer corresponds to PDP ( Packet Data Protocol Packet Data Protocol) Context.

IP-CAN session: IP-CAN会话，指的是 UE ( User Equipment用户设备 ) 和 PDN ( Packet Data Network分组数据网）之间的关联关系，通过 UE的 IP地址和 UE的标识（如：国际移动用户识别码 IMSI ( International Mobile Subscriber Identity ) )来识别。只要 UE分配了 IP地址并且能被 IP网络识别，则 IP-CAN会话（ IP-CAN Session )存在。一个 IP-CAN会话可以包含一个或者多个 IP-CAN 承载。 IP-CAN session: IP-CAN session, which refers to the association between the UE (User Equipment User Equipment) and the PDN (Packet Data Network), through the IP address of the UE and the identity of the UE (eg, international mobile User Identification Code IMSI (International Mobile Subscriber Identity)) to identify. As long as the UE is assigned an IP address and can be identified by the IP network, an IP-CAN Session exists. An IP-CAN session can contain one or more IP-CAN bearers.

三、 3GPP定义的 PCC架构，通过静态或者动态提供的 PCC规则，实现对业务数据流的 QoS、计费、门控等策略控制。静态 PCC规则在 PCRF或者 PCEF 上通过预定义的方法实现；而动态 PCC规则可以在整个 IP-CAN Session过程中根据实际需要由 PCRF动态生成。根据应用启动、变更和终止等导致应用业务流变化时， AF动态下发相关应用业务信息给 PCRF, PCRF可以根据应用业务信息针对应用业务流动态生成 PCC规则并将 PCC规则动态下发给 PCEF。例如：用户在一次多媒体通话过程中，决定临时取消视频，这时会导致应用层的会话协商信息发生更改， AF需要将更改后的应用业务信息下发给 PCRF,以供 PCRF 动态生成新 PCC规则或改变已有的 PCC规则，然后下发给 PCEF执行，以控制业务数据流的更改。 3. The PCC architecture defined by 3GPP implements QoS, charging, gating and other policy control of service data flows through static or dynamically provided PCC rules. The static PCC rules are implemented on the PCRF or PCEF through a predefined method; and the dynamic PCC rules can be dynamically generated by the PCRF according to actual needs during the entire IP-CAN Session. Application business based on application startup, change, and termination When the flow changes, the AF dynamically sends the relevant application service information to the PCRF. The PCRF can dynamically generate the PCC rule for the application service flow according to the application service information and dynamically send the PCC rule to the PCEF. For example, the user decides to temporarily cancel the video during a multimedia call. In this case, the session negotiation information of the application layer is changed. The AF needs to send the changed application service information to the PCRF for the PCRF to dynamically generate a new PCC rule. Or change the existing PCC rules and then send them to the PCEF for execution to control the changes of the business data flow.

下面是一个关于 AF会话业务流策略控制的流程，根据 AF下发的应用业务信息， PCRF制订 PCC规则进行动态策略控制，参见图 2所示，包括下列步骤：流程描述如下： The following is a process for controlling the traffic policy of the AF session. According to the application service information delivered by the AF, the PCRF formulates the PCC rules for dynamic policy control. As shown in Figure 2, the following steps are included: The process description is as follows:

1、 AF接收到一个触发事件（例如 UE发起的多媒体呼叫控制信令）后，需要建立一个新的 Diameter会话； 1. After the AF receives a trigger event (such as UE-initiated multimedia call control signaling), it needs to establish a new Diameter session.

2、 AF从触发事件中提取需要的业务信息（比如 IP流的地址信息，端口号，媒体类型，带宽等），将该业务信息通过 Diameter AAR消息发送给 PCRF; 2. The AF extracts the required service information (such as the address information of the IP stream, the port number, the media type, the bandwidth, and the like) from the triggering event, and sends the service information to the PCRF through the Diameter AAR message;

3、 PCRF保存接收到的业务信息； 3. The PCRF saves the received business information;

4、如果 PCRF此时没有用户签约信息，则向 SPR请求用户签约信息； 4. If the PCRF does not have user subscription information at this time, request the user subscription information from the SPR;

5、 PCRF根据接收的业务信息和此前从 PCEF接收到的信息（比如 IP-CAN Session建立时），将该新建的 AF会话关联到一个对应的 IP-CAN Session, 并进行策略决策；认消息； 5. The PCRF associates the newly created AF session with a corresponding IP-CAN Session according to the received service information and the information previously received from the PCEF (for example, when the IP-CAN session is established), and performs policy decision;

7、 PCRF向 AF返回 AAA消息。 7. The PCRF returns an AAA message to the AF.

四、 PCC架构定义 Rx接口下发应用业务信息的能力。 IV. PCC Architecture Definition The ability of the Rx interface to deliver application service information.

从上述 AF会话业务流策略控制流程可以看出， PCRF根据 AF下发的应用业务信息、用户签约信息等完成策略决策。现有 PCC架构定义通过 Rx接口釆用 Diameter协议实现应用业务信息的下发，下发的应用业务信息中的业务流信息中包含以下内容： It can be seen from the above-mentioned AF session service flow policy control process that the PCRF completes the policy decision based on the application service information and user subscription information delivered by the AF. The existing PCC architecture defines the application service information to be delivered through the Rx interface using the Diameter protocol. The service flow information in the delivered application service information includes the following contents:

媒体流：会话过程可能使用多个媒体，例如音频、视频。一个媒体流就对应 IMS应用下 SDP消息中的一个 m行（媒体描述行）。每个媒体流通过一个 Media-Component-Description AVP描述并通过 Media-Component-Number A VP 标识 , Media-Component-Number AVP就是该 m行在 SDP消息中出现的顺序号。媒体流中还包含其它信息：应用标识（ AF-Application-Identifier )表示该媒体流属于什么应用、媒体类型（Media-Type ) 、最大请求上下行带宽 Media Streaming: The session process may use multiple media, such as audio, video. A media stream corresponds to one m line (media description line) in the SDP message under the IMS application. Each media stream is described by a Media-Component-Description AVP and passed through Media-Component-Number A VP Identification, Media-Component-Number AVP is the sequence number in which the m line appears in the SDP message. The media stream also contains other information: The application identifier (AF-Application-Identifier) indicates what application the media stream belongs to, the media type (Media-Type), and the maximum request uplink and downlink bandwidth.

( Max-Requested-Bandwidth-U/DL ) 、流状态（ Flow- Status ) 、媒体流的预留优先级（Reservation-priority ) 、 RTCP收发带宽（ RR/RS-Bandwidth ) 、媒体编译码 ( Codec-Data )格式等信息。 (Max-Requested-Bandwidth-U/DL), Flow-Status, Reservation-priority of Media Stream, RTCP Transmit Bandwidth (RR/RS-Bandwidth), Media Encoding Code (Codec- Data) format and other information.

媒体子流：媒体子流是对媒体流的进一步细分，比如一个音频流釆用 RTP 方式传输时，相应的 RTP流和 RTCP流分别对应一个媒体子流。在应用业务信息下发时，每个媒体子流通过一个 Media-Sub-Component AVP描述，同一个媒体流中的多个媒体子流通过 Flow-Number AVP标识， Flow-NumberAVP可以根据各媒体子流对应的端口号等排序。媒体子流可以对应一个双向流（包含两个 Media substream: The media substream is a further subdivision of the media stream. For example, when an audio stream is transmitted by RTP, the corresponding RTP stream and RTCP stream respectively correspond to one media substream. When the application service information is delivered, each media substream is described by a Media-Sub-Component AVP, and multiple media substreams in the same media stream are identified by a Flow-Number AVP, and the Flow-NumberAVP may be based on each media substream. Sort the corresponding port number. The media substream can correspond to a bidirectional stream (including two

Flow-Description AVP, 描述两个 IP流），也可以对应一个单向流（只包含一个 Flow-Description AVP, 描述一个 IP流）。媒体子流中还包含流用途（Flow Usage )和其它参数。这些参数在媒体流中也包含，在前面已经说明，这里不再重复描述。 The Flow-Description AVP, which describes two IP flows, can also correspond to a unidirectional flow (containing only one Flow-Description AVP, describing an IP flow). The media subflow also contains Flow Usage and other parameters. These parameters are also included in the media stream, as explained above, and will not be repeated here.

IP流：由具有相同源 IP位址、目的 IP位址、传输层协议、源端口号和目的端口号（合称 IP-5元组，如果对应的传输层协议没有端口号的概念，源端口号和目的端口号可以省略）的 IP报文组成的单向流。在 Rx界面上，每个 IP Flow 通过一个 Flow-Description AVP描述。 IP flow: The source port has the same source IP address, destination IP address, transport layer protocol, source port number, and destination port number (collectively IP-5 tuples, if the corresponding transport layer protocol does not have a port number concept, source port The unidirectional flow consisting of IP packets whose number and destination port number can be omitted. On the Rx interface, each IP Flow is described by a Flow-Description AVP.

应用业务信息描述了 IMS应用中通过 SDP协商的业务流信息，包括业务流对应的 QoS、门控、计费等信息。另外，应用业务信息下发还包含用户标识 ( Subscription-ID ) 、用户 IP地址 ( Framed-IP-Address/ Framed-IPv6 -Prefix ) 、会话优先级 ( Reservation-Priority )等信息。 The application service information describes the service flow information negotiated by the SDP in the IMS application, including the QoS, gating, and accounting information corresponding to the service flow. In addition, the application service information is also sent with information such as a user ID (Subscription-ID), a user IP address (Framed-IP-Address/Framed-IPv6-Prefix), and a Reservation-Priority.

具体下发应用业务信息的示例如下： Examples of specific application service information are as follows:

<AA-Request> ::= < Diameter Header: 265, REQ, PXY > <AA-Request> ::= < Diameter Header: 265, REQ, PXY >

[ Media-Component-Description ] [ Media-Component-Description ]

[ AF-Charging-Identifier ] [ AF-Charging-Identifier ]

[ Subscription-ID ] [ Reservation-Priority ] [ Subscription-ID ] [ Reservation-Priority ]

[ Framed-IP- Address ] [ Framed-IP- Address ]

[ Framed-IPv6-Prefix ] 上述示例仅列出部分与业务相关的信息。其中媒体组件描述 [ Framed-IPv6-Prefix ] The above example only lists some of the business-related information. Media component description

( Media-Component-Description AVP ) 需要根据 IMS应用中的 SDP协商消息导出，它包括如下信息： (Media-Component-Description AVP) needs to be derived according to the SDP negotiation message in the IMS application, which includes the following information:

Media-Component-Description ::= < AVP Header: 517 > Media-Component-Description ::= < AVP Header: 517 >

{ Media-Component-Number } { Media-Component-Number }

*[ Media-Sub-Component ] *[ Media-Sub-Component ]

[ AF-Application-Identifier ] [ AF-Application-Identifier ]

[ Media-Type ] [ Media-Type ]

[ Max-Requested-Bandwidth-UL ] [ Max-Requested-Bandwidth-UL ]

[ Max-Requested-Bandwidth-DL ] [ Max-Requested-Bandwidth-DL ]

[ Flow- Status ] [ Flow- Status ]

[ Reservation-priority ] [ Reservation-priority ]

[ RS-Bandwidth ] [ RS-Bandwidth ]

[ RR-Bandwidth ] [ RR-Bandwidth ]

*[ Codec-Data ] *[ Codec-Data ]

其中 Media-Component-Description AVP还可能包^ 某体子组件 ( Media Sub Component AVP )信息，其消息结构如下： The Media-Component-Description AVP may also include a Media Sub Component AVP message whose message structure is as follows:

Media-Sub-Component ::= < AVP Header: 519 > Media-Sub-Component ::= < AVP Header: 519 >

{ Flow-Number } { Flow-Number }

0*2[ Flow-Description ] 0*2[ Flow-Description ]

[ Flow- Status ] [ Flow- Status ]

[ Flow-Usage ] [ Flow-Usage ]

[ Max-Requested-Bandwidth-UL ] [ Max-Requested-Bandwidth-DL ] 发明人在发明过程中发现：基于 PCC架构可满足 IMS中的应用业务的 QoS 和计费需求，但在非 IMS应用中还存在若干与 IMS应用不同的数据应用业务， PCC架构作为一种可满足 QoS和计费需求的架构，应该支持这些非 IMS的数据应用业务。但现有 PCC架构中的 AF主要面向 IMS应用， AF通过 Rx接口下发给 PCRF的应用业务信息主要面向 IMS应用的需求进行设计，这导致 PCC架构应用于非 IMS数据应用的策略控制时，无法将数据应用业务信息下发到 PCRF , 使得 PCRF无法进行策略决策，从而无法满足网络对非 IMS数据应用业务的 QoS, 计费等策略控制的需求。 [Max-Requested-Bandwidth-UL] [Max-Requested-Bandwidth-DL] The inventor discovered during the invention: Based on the PCC architecture, it can satisfy the QoS of application services in IMS. And billing requirements, but there are also several data application services that are different from IMS applications in non-IMS applications. The PCC architecture, as an architecture that can meet QoS and billing requirements, should support these non-IMS data application services. However, the AF in the existing PCC architecture is mainly for the IMS application. The application service information that the AF sends to the PCRF through the Rx interface is mainly designed for the requirements of the IMS application. This causes the PCC architecture to be applied to the policy control of the non-IMS data application. The data application service information is sent to the PCRF, so that the PCRF cannot make policy decisions, which cannot meet the requirements of the network for policy control such as QoS and charging for non-IMS data application services.

而且现有技术中， PCRF进行策略决策时，没有考虑不同业务提供商提供相同的业务时可能釆用不同的策略。例如：在电信网络上开展的视频点播业务可以由业务提供商 ASP1或者 ASP2提供。尽管业务内容一样，但是 ASP1和 ASP2可能釆取不同的收费策略，比如 ASP1按照内容计费，而 ASP2釆取流量计费的方式。 Moreover, in the prior art, when the PCRF makes policy decisions, it may not adopt different policies when different service providers provide the same service. For example: The video on demand service carried out on the telecommunication network can be provided by the service provider ASP1 or ASP2. Although the business content is the same, ASP1 and ASP2 may adopt different charging policies, such as ASP1 charging according to content, and ASP2 taking traffic charging method.

发明内容 Summary of the invention

本发明实施例提供了一种应用的策略控制方法及装置，以实现对应用的策略控制时，可针对不同应用业务提供商提供的相同业务进行不同的策略决策。 The embodiment of the present invention provides an application policy control method and device, so as to implement policy control on an application, different policy decisions can be made for the same service provided by different application service providers.

本发明实施例还提供了一种数据应用的策略控制方法、装置及***，以实现 PCC架构应用于非 IMS数据应用的策略控制时，可将数据应用业务信息下发到 PCRF, 使 PCRF可进行策略决策。 The embodiment of the present invention further provides a method, a device, and a system for controlling a data application. When the PCC architecture is applied to a policy control of a non-IMS data application, the data application service information can be sent to the PCRF, so that the PCRF can be performed. Strategic decision making.

本发明实施例的一种应用的策略控制方法，包括下列步骤： PCRF获取应用业务提供商标识； PCRF根据所述应用业务提供商标识进行策略决策。 An applied policy control method according to an embodiment of the present invention includes the following steps: The PCRF obtains an application service provider identifier; and the PCRF performs policy decision according to the application service provider identifier.

本发明实施例的一种策略控制和计费规则功能实体，包括：获取单元，用于获取应用业务提供商标识；决策单元，用于根据获取单元获取的所述应用业务提供商标识进行策略决策。 The policy control and charging rule function entity of the embodiment of the present invention includes: an obtaining unit, configured to acquire an application service provider identifier; and a determining unit, configured to perform a policy decision according to the application service provider identifier acquired by the obtaining unit .

本发明实施例的一种数据应用的策略控制方法包括：策略控制和计费规则功能实体 PCRF接收非 IMS中的数据应用 AF发来的数据应用业务信息；以及 PCRF根据所述数据应用业务信息进行策略决策。 The policy control method for the data application in the embodiment of the present invention includes: the policy control and charging rule function entity PCRF receives the data application service information sent by the data application AF in the non-IMS; and the PCRF performs the service information according to the data application. Strategic decision making.

本发明实施例的一种非 IMS 中的数据应用功能实体，包括：触发单元，用于接收触发事件；下发单元，用于在触发单元收到触发事件时，下发相应的数据应用业务信息。本发明实施例的另一种策略控制和计费规则功能实体，包括：接收单元，用于接收数据应用业务信息；决策单元，用于根据接收单元收到的数据应用业务信息进行策略决策。 The non-IMS data application function entity in the embodiment of the present invention includes: a triggering unit, configured to receive a triggering event; and a sending unit, configured to send a corresponding data application service information when the triggering unit receives the triggering event . Another policy control and charging rule function entity of the embodiment of the present invention includes: a receiving unit, configured to receive data application service information; and a decision unit, configured to perform policy decision according to data application service information received by the receiving unit.

本发明实施例的一种非 IMS数据应用的策略控制***，包括：非 IMS中的数据应用 AF, 用于下发数据应用业务信息； PCRF, 用于接收非 IMS中的数据应用 AF下发的数据应用业务信息，并根据该数据应用业务信息进行策略决策。 A policy control system for a non-IMS data application according to an embodiment of the present invention includes: a data application AF in a non-IMS, which is used to deliver data application service information; and a PCRF, which is used to receive data in a non-IMS application. The data applies business information, and the business information is used according to the data to make policy decisions.

本发明实施例中 PCRF获取应用业务提供商标识，并根据所述应用业务提供商标识进行策略决策。由于应用业务提供商标识对应不同的应用业务提供商，所以使得 PCRF进行策略决策时，可考虑不同业务提供商提供相同业务时可能釆用不同的策略。 In the embodiment of the present invention, the PCRF obtains an application service provider identifier, and performs policy decision according to the application service provider identifier. Since the application service provider identifiers correspond to different application service providers, when the PCRF makes policy decisions, it may be considered that different service providers may use different policies when providing the same service.

本发明实施例中 PCRF接收非 IMS中的数据应用 AF发来的数据应用业务信息；以及 PCRF根据所述数据应用业务信息进行策略决策。从而实现了 PCC 对非 IMS数据应用业务的策略控制，有利于增进用户对非 IMS数据应用的体验、提升网络资源的利用率。此外扩大了 PCC的使用范围，使得 PCC不仅可以使用 IMS场景的策略控制，而且也使得 PCC在非 IMS场景下的策略控制变为可行。 In the embodiment of the present invention, the PCRF receives the data in the non-IMS and applies the data application service information sent by the AF; and the PCRF performs the policy decision according to the data application service information. Therefore, the PCC's policy control for non-IMS data application services is realized, which is beneficial to improving the user experience of non-IMS data applications and improving the utilization of network resources. In addition, the scope of use of the PCC is expanded, so that the PCC can not only use the policy control of the IMS scenario, but also make the PCC policy control in the non-IMS scenario feasible.

附图说明 DRAWINGS

图 1为现有 PCC架构示意图； Figure 1 is a schematic diagram of an existing PCC architecture;

图 2为现有 AF会话业务流策略控制的流程图； 2 is a flow chart of control of an existing AF session service flow policy;

图 3为本发明实施例的一种数据应用的策略控制方法步骤流程图；图 4为本发明实施例的一种非 IMS中的数据应用功能实体结构示意图；图 5为本发明实施例的一种策略控制和计费规则功能实体结构示意图；图 6为本发明实施例一的流程图； 3 is a flowchart of a method for controlling a policy of a data application according to an embodiment of the present invention; FIG. 4 is a schematic structural diagram of a function of a data application function in a non-IMS according to an embodiment of the present invention; FIG. 6 is a flowchart of a first embodiment of the present invention;

图 7为本发明实施例二的流程图； 7 is a flowchart of Embodiment 2 of the present invention;

图 8为本发明实施例的一种应用的策略控制方法步骤流程图； FIG. 8 is a flowchart of a method for applying a policy control method according to an embodiment of the present invention;

图 9为本发明实施例的另一种策略控制和计费规则功能实体结构示意图；图 10为本发明实施例三的流程图； FIG. 9 is a schematic structural diagram of another policy control and charging rule function entity according to an embodiment of the present invention; FIG. 10 is a flowchart of Embodiment 3 of the present invention;

图 11为本发明实施例四的流程图。具体实施方式 FIG. 11 is a flowchart of Embodiment 4 of the present invention. detailed description

现有 IMS中，例如：语音、视频电话、即时消息等 IMS业务被称为应用业务，所述应用业务是通过 IMS AF ( Application Function应用功能实体）等提供。 IMS AF ,如 IMS网络中的 P-CSCF ( Proxy- Call Session Control Function 代理呼叫会话控制功能）、 AS(Application Server: 应用服务器)等，可以通过 PCC 架构实现对这些应用业务进行 QoS、计费等策略控制的需求。 In the existing IMS, for example, voice, video telephony, instant messaging, etc., the IMS service is called an application service, and the application service is provided through an IMS AF (Application Function Application Function Entity) or the like. IMS AF, such as P-CSCF (Proxy-Call Session Control Function) and AS (Application Server) in the IMS network, can implement QoS, charging, etc. for these application services through the PCC architecture. The need for policy control.

随着网络的飞速发展，非 IMS中的数据应用业务正变得越来越丰富。在非 IMS中，例如：视频点播、网络游戏、网络电子表单、网络数据会议、电子商务、网络银行、电子证券等业务，被称为数据应用业务。由于这些数据应用业务或者其包含信息的重要性，或者由于为了保证用户体验，它们对网络提供的 QoS保证有很高的要求。例如电子证券，网络必须保证数据实时、准确的传输，否则会影响用户的判断和操作，导致经济损失；又如用户进行视频点播，在网络缺少 QoS保证的情况下，可能会引发视频画面模糊、声音时断时续等现象；再如用户进行网络游戏时，如果网络不能为游戏提供 QoS保证，则对游戏操作的数据无法及时传达服务器，从而引发用户动作比对手迟钝，导致游戏战败等情况。 With the rapid development of the network, data application services in non-IMS are becoming more and more abundant. In non-IMS, for example: video on demand, online games, network electronic forms, network data conferencing, e-commerce, online banking, electronic securities, etc., is called data application business. Due to the importance of these data application services or their inclusion of information, or because of the user experience, they have high requirements for the QoS guarantee provided by the network. For example, in electronic securities, the network must ensure real-time and accurate transmission of data. Otherwise, it will affect the judgment and operation of users, resulting in economic loss. If the user performs video on demand, the video may be blurred if the network lacks QoS guarantee. When the user plays the online game, if the network can not provide QoS guarantee for the game, the data of the game operation cannot communicate the server in time, which causes the user action to be slower than the opponent, resulting in the game being defeated.

对于前述非 IMS 中的数据应用业务，一旦传输数据发生延迟或错误，将严重影响用户体验，甚至由于数据丟失而导致无法开展业务；同时这些增值业务流量不同于一般的上网业务流量，网络应该可以根据业务内容的不同实现对其进行不同的计费控制，因此网络需要能够提供对这些数据应用业务的 QoS、计费等控制能力。 For the data application service in the non-IMS mentioned above, once the data transmission delay or error occurs, the user experience will be seriously affected, and even the data loss may result in the inability to conduct services; at the same time, the value-added service traffic is different from the general Internet traffic, and the network should be able to Different charging controls are implemented according to different service contents. Therefore, the network needs to be able to provide control functions such as QoS and charging for these data application services.

为了实现 PCC架构应用于非 IMS数据应用的策略控制，进一步为了使上述非 IMS的数据应用业务的数据应用 AF (如视频点播应用服务器、网络游戏应用服务器、网络数据会议应用服务器等），可将数据应用业务信息下发到 PCRF, 使 PCRF可进行策略决策，从而满足网络对数据应用业务的 QoS、计费等策略控制的需求。 In order to implement the policy control of the PCC architecture applied to the non-IMS data application, the data application AF (such as a video on demand application server, a network game application server, a network data conference application server, etc.) may be further applied to enable the non-IMS data application service. The data application service information is sent to the PCRF, so that the PCRF can make policy decisions, thereby satisfying the network's requirements for policy control such as QoS and charging for the data application service.

本发明实施例提供了一种数据应用的策略控制方法，参见图 3所示，包括下列主要步骤： The embodiment of the invention provides a policy control method for data application, as shown in FIG. 3, which includes the following main steps:

Sl l、 PCRF接收非 IMS中的数据应用 AF发来的数据应用业务信息。本发明实施例中，非 IMS中的数据应用 AF根据数据应用业务的触发信息 (例如：收到 PCRF的请求或用户的请求），向 PCRF下发数据应用业务信息。 The Sl1 and the PCRF receive the data application service information sent by the AF in the non-IMS data. In the embodiment of the present invention, the data application AF in the non-IMS sends the data application service information to the PCRF according to the trigger information of the data application service (for example, the request of the PCRF or the request of the user).

具体可通过下述三种方式之一实现数据应用业务信息的下发： The data application service information can be delivered in one of the following three ways:

方式一、通过修订 Rx接口定义中的 IMS应用业务流信息单元，数据应用 AF向 PCRF下发包含数据应用业务流信息的数据应用业务信息。 The first step is to modify the IMS application service flow information unit in the Rx interface definition, and the data application AF sends the data application service information including the data application service flow information to the PCRF.

应用业务信息中包含了一部分组成业务的业务流信息，例如多媒体会话业务，可能由视频和音频组成。现有 PCC架构定义 Rx接口下发的应用业务信息包含的业务流信息需要根据 IMS场景下的 SDP ( Session Description Protocol 会话描述协议）协商导出到 Media-Component-Description AVP参数 (即 IMS 应用业务流信息单元）中，才能实现下发。 The application service information contains a part of the service flow information that constitutes the service, such as the multimedia session service, which may be composed of video and audio. The existing PCC architecture defines the service flow information of the application service information delivered by the Rx interface and needs to be exported to the Media-Component-Description AVP parameter (ie, the IMS application service flow information according to the SDP (Session Description Protocol) protocol negotiation in the IMS scenario. In the unit), the delivery can be achieved.

在非 IMS场景下，用于描述业务流信息的 Media-Component-Description AVP参数值无法导出，对此需要修订 Rx接口定义中的 IMS应用业务流信息单元，使其描述业务流信息时不再依赖于 IMS场景下的 SDP协商形式导出，从而使 PCC也满足对非 IMS数据应用业务的策略控制需求。示例如下： In a non-IMS scenario, the Media-Component-Description AVP parameter value used to describe the service flow information cannot be exported. For this, the IMS application service flow information element in the Rx interface definition needs to be revised so that it does not depend on the service flow information. The SDP negotiation form is exported in the IMS scenario, so that the PCC also satisfies the policy control requirements for the non-IMS data application service. An example is as follows:

Media-Component-Description：： = < AVP Header: 517 > Media-Component-Description:: = < AVP Header: 517 >

edia-Component-Niimber j *[ Media-Sub-Component ] edia-Component-Niimber j *[ Media-Sub-Component ]

[ Media-Type ] [ Media-Type ]

[ Reservation-priority ] [ Reservation-priority ]

[ Flow- Status ] [ Flow- Status ]

[ AF-Application-Identifier ] [ AF-Application-Identifier ]

[ Max-Requested-Bandwidth-UL ] [ Max-Requested-Bandwidth-UL ]

[ Max-Requested-Bandwidth-DL ] [ Max-Requested-Bandwidth-DL ]

[ RS-Bandwidth ] [ RS-Bandwidth ]

[ RR-Bandwidth ] [ RR-Bandwidth ]

*[ Codec-Data ] 其中 Media- Sub-Component AVP表示形式如下： *[ Codec-Data ] The Media-Sub-Component AVP representation is as follows:

Media- Sub-Component ::= < AVP Header: 519 > Media- Sub-Component ::= < AVP Header: 519 >

[ Flow-Number ] [ Flow-Number ]

0*2[ Flow-Description ] 0*2[ Flow-Description ]

[ Flow- Status ] [ Flow- Status ]

[ Flow-Usage ] [ Flow-Usage ]

[ Max-Requested-Bandwidth-UL ] [ Max-Requested-Bandwidth-DL ] 本示例将 Media-Component-Description AVP 结构下的 Media-Component-Number AVP 和 Media-Sub-Component AVP 结构下的 Flow-Number AVP作为可选参数。当修订后的 Rx接口定义中的 IMS应用业务流信息单元使用于 IMS 场景下的业务应用时， Media-Component-Description AVP和 Media- Sub-Component AVP需要分另¹ J包含 Media-Component-Number AVP和 Flow-Number AVP, 其中 Media-Component-Number AVP根据 IMS应用下 SDP协商消息的" m"行导出 , 而 Flow-Number AVP按照各媒体行对应媒体流所使用的端口号的递增顺序导出；当修订后的 Rx接口定义中的 IMS应用业务流信息单元使用于非 IMS 场景下的数据应用业务时， Media-Component-Description AVP 和 Media- Sub-Component AVP 无需包含 Media-Component-Number AVP和 Flow-Number AVP„ [ Max-Requested-Bandwidth-UL ] [ Max-Requested-Bandwidth-DL ] This example will use the Media-Component-Number AVP under the Media-Component-Description AVP structure and the Flow-Number AVP under the Media-Sub-Component AVP structure. As an optional parameter. When the IMS application service flow information element in the revised Rx interface definition is used for the service application in the IMS scenario, the Media-Component-Description AVP and the Media-Sub-Component AVP need to be separated into ¹ J to include the Media-Component-Number AVP. And the Flow-Number AVP, where the Media-Component-Number AVP is derived according to the "m" line of the SDP negotiation message under the IMS application, and the Flow-Number AVP is derived according to the increasing order of the port numbers used by the corresponding media stream of each media line; When the IMS application service flow information element in the revised Rx interface definition is used for the data application service in the non-IMS scenario, the Media-Component-Description AVP and the Media-Sub-Component AVP need not include the Media-Component-Number AVP and Flow- Number AVP„

方式二、通过在 Rx接口定义中新增数据应用业务流信息单元，数据应用 AF向 PCRF下发包含数据应用业务流信息的数据应用业务信息。 In the second method, the data application service information is added to the Rx interface definition, and the data application AF sends the data application service information including the data application service flow information to the PCRF.

在非 IMS场景下，用于描述业务流信息的 Media-Component-Description AVP参数（即 IMS应用业务流信息单元）值无法导出，对此需要在 Rx接口定义中新增数据应用业务流信息单元，使其描述业务流信息时不再依赖于 IMS 场景下的 SDP协商形式导出，从而使 PCC也满足对非 IMS数据应用业务的策略控制需求。 In a non-IMS scenario, the value of the Media-Component-Description AVP parameter (that is, the IMS application service flow information element) used to describe the service flow information cannot be exported. In this case, the data application service flow information element needs to be added in the Rx interface definition. The description of the service flow information is no longer dependent on the SDP negotiation form in the IMS scenario, so that the PCC also satisfies the policy control requirements for the non-IMS data application service.

示例如下： Data- Application-Description ::= < AVP Header: χ χ χ > An example is as follows: Data- Application-Description ::= < AVP Header: χ χ χ >

* { Data-Description } * { Data-Description }

[ Data-Type ] [ Data-Type ]

[ Data- Status ] [ Data- Status ]

[ Reservation-priority ] [ Reservation-priority ]

[ Data-Usage ] [ Data-Usage ]

[ AF-Application-Identifier ] [ AF-Application-Identifier ]

[ Max-Requested-Bandwidth-UL ] [ Max-Requested-Bandwidth-UL ]

[ Max-Requested-Bandwidth-DL ] [ Max-Requested-Bandwidth-DL ]

[ RTCP-Bandwidth-UL ] [ RTCP-Bandwidth-UL ]

[ RTCP-Bandwidth-DL ] [ RTCP-Bandwidth-DL ]

*[ Codec-Data ] *[ Codec-Data ]

该示例重新定义了 Data- Application-Description AVP用于非 IMS数据应用中的数据应用业务流信息的表示。 This example redefines the representation of Data Application-Description AVP for data application traffic flow information in non-IMS data applications.

Data- Application-Description AVP ( AVP code χ χ χ ) Grouped型 , 用于表示非 IMS数据应用中的数据应用业务流信息，包含的参数如下（参数取值可以根据实际情况进行扩充）： Data-Application-Description AVP (AVP code χ χ χ ) Grouped type, used to represent data application service flow information in non-IMS data applications, including the following parameters (parameters can be expanded according to actual conditions):

Data-Description AVP ( AVP code ) IPFilterRule型，用于表示业务流的五元组，包括源地址和端口号、目的地址和端口号、协议。 Data-Description AVP (AVP code) IPFilterRule type, used to represent the quintuple of the service flow, including the source address and port number, destination address and port number, and protocol.

Data-Type AVP ( AVP code ) Enumerated型，表示业务流类型，可以有如下取值： AUDIO (0)、 VIDEO (1)、 DATA(2) Data-Type AVP (AVP code) Enumerated type, indicating the service flow type, can have the following values: AUDIO (0), VIDEO (1), DATA (2)

Data-Status AVP ( AVP code ) Enumerated型，表示业务流^ 态，可以有如下取值： ENABLED(0)、 DISABLED(l) Data-Status AVP ( AVP code ) Enumerated type, which represents the service flow state, can have the following values: ENABLED(0), DISABLED(l)

Data-Usage AVP ( AVP code ) Enumerated型，表示业务流用途，可以有如下取值： RTCP(0)、 OTHER(l) 该参数与 Media-Component-Description AVP并列位于 Diameter消息下, 并互斥使用。当 PCC应用于 IMS业务时，使用 Media-Component-Description AVP传递业务流信息；应用于非 IMS业务时，使用 Data-Application-DescriptionData-Usage AVP (AVP code) Enumerated type, which indicates the purpose of the service flow, and can have the following values: RTCP(0), OTHER(l) This parameter is placed in parallel with the Media-Component-Description AVP under the Diameter message and is used mutually exclusive. When the PCC is applied to the IMS service, the Media-Component-Description AVP is used to deliver the service flow information; when applied to the non-IMS service, the Data-Application-Description is used.

AVP传递数据应用业务流信息。 The AVP passes the data application service flow information.

方式三、通过 HTTP协议，所述数据应用 AF向 PCRF下发数据应用业务信息。 In the third method, the data application application AF sends the data application service information to the PCRF.

现有 PCC架构规定实现应用业务信息下发的 Rx接口使用 Diameter协议，而对非 IMS数据应用业务实施策略控制，由于 ASP (应用业务提供商）都釆用基于 web的协议进行信息传递，根据现有 PCC架构的定义和规定，显然限制了 PCC在非 IMS数据应用业务中的应用。需要增设其它协议传递数据应用业务信息，以满足 PCC对非 IMS数据应用进行策略控制的需要。考虑到 XML ( Extensible Markup Language 可扩展标记语言）在数据描述上的优势及其在 IP网络上的事实标准地位，数据应用业务信息下发可以使用 XML语法进行描述，并用 HTTP ( Hypertext Transfer Protocol超文本传输协议）协议进行数据应用业务信息的下发。 The existing PCC architecture stipulates that the Rx interface delivered by the application service information uses the Diameter protocol, and the non-IMS data application service implements policy control. Since ASP (application service provider) uses the web-based protocol for information transmission, according to the present The definition and provisions of the PCC architecture clearly limit the application of PCC in non-IMS data application services. Additional protocols need to be added to deliver data application service information to meet the PCC's need for policy control of non-IMS data applications. Considering the advantages of XML (Extensible Markup Language) in data description and its de facto standard status on IP networks, data application service information can be described using XML syntax and HTTP (Hypertext Transfer Protocol hypertext) The transmission protocol protocol is used to deliver data application service information.

一个使用 XML语法描述数据应用业务信息下发的示例如下： An example of using the XML syntax to describe data application business information is as follows:

<?xml version:" 1.0" encoding="UTF-8 " ?> <?xml version:" 1.0" encoding="UTF-8 " ?>

<xs： schema targetNamespace="http://www.w3 schools . com" <xs: schema targetNamespace="http://www.w3 schools . com"

xmlns:xs="http：〃 www.w3.org/2001/XMLSchema" Xmlns:xs="http:〃 www.w3.org/2001/XMLSchema"

xmlns="http：〃 www. w3schools.com" elementFormDefault=" qualified" attributeFormDefault="unqualified"> Xmlns="http:〃 www. w3schools.com" elementFormDefault=" qualified" attributeFormDefault="unqualified">

<xs: element name="af-session"> <xs: element name="af-session">

<xs： complexType> <xs: complexType>

<!一该部分定义 session的属性，包括 session initialization (会话开始) 、 <! This part defines the properties of the session, including session initialization (session start),

session modification (会话更改) 、 session termination (会话终止) 三种属性-- > Session modification (session change), session termination (session termination) three properties -->

<xs: attribute name="state"> <xs: attribute name="state">

<xs:simpleType> <xs:simpleType>

<xs:restriction base="xs: string" > <xs: enumeration value="session initialization"/ <xs:restriction base="xs: string"> <xs: enumeration value="session initialization"/

<xs: enumeration value="session modification"/ <xs: enumeration value="session modification"/

<xs: enumeration value="session termination'7> <xs: enumeration value="session termination'7>

</xs:restriction> </xs:restriction>

</xs:simpleType> </xs:simpleType>

</xs:attribute> </xs:attribute>

<!--该部分说明包含的具体应用业务信息- > <!--This section describes the specific application business information contained in ->

<xs:sequence> <xs:sequence>

<xs: element name="Media-Component-Description" minOccours="0 maxOccurs="unbound"/> <xs: element name="Media-Component-Description" minOccours="0 maxOccurs="unbound"/>

<xs: element name="Data- Application-Description" minOccours="0" maxOccurs="unbound"> <xs: element name="Data- Application-Description" minOccours="0" maxOccurs="unbound">

<xs： complexType> <xs: complexType>

<xs element name= ^:" Codec-Data " type="xs: string" <xs element name= ^: " Codec-Data "type="xs:string"

maxOccurs="unbound"/> </xs:sequence> maxOccurs="unbound"/> </xs:sequence>

</xs： complexType> </xs: complexType>

</xs:element> </xs:element>

<xs: element name =" ASP-Identifier " type="xs:string'7> <xs: element name =" ASP-Identifier " type="xs:string'7>

<xs: element name ="AF-Charging-Identifier" type="xs:string'7> <xs: element name ="AF-Charging-Identifier" type="xs:string'7>

<xs: element name =" subscription-ID" type="xs:string'7> <xs: element name =" subscription-ID" type="xs:string'7>

<xs: element name ="Reservation-Priority" type="priority'7> <xs: element name ="Reservation-Priority" type="priority'7>

<xs: element name ="UE-IP- Address" type="xs： string'7> <xs: element name ="UE-IP- Address" type="xs: string'7>

<xs: element name ="Termination-Cause" type=" cause-type "/> <xs: element name ="Termination-Cause" type=" cause-type "/>

<xs: element name ="class" type="xs: string" maxOccurs="unbounded"/> </xs:sequence> <xs: element name ="class" type="xs: string" maxOccurs="unbounded"/> </xs:sequence>

</xs： complexType> </xs: complexType>

<!--该部分对没有定义属性进行定义 > <!--This section defines undefined properties >

<xs： simpleType name="Data-status"> <xs: simpleType name="Data-status">

<xs： restriction base="xs： string"> <xs: restriction base="xs: string">

<xs: enumeration value="enabled-uplink"/> <xs: enumeration value="enabled-uplink"/>

<xs: enumeration value="enabled-downlink"/> <xs: enumeration value="enabled-downlink"/>

<xs: enumeration value="enabled"/> <xs: enumeration value="enabled"/>

<xs: enumeration value="disabled"/> <xs: enumeration value="disabled"/>

<xs: enumeration value="removed"/> <xs: enumeration value="removed"/>

</xs:restriction> </xs:restriction>

</xs： simpleType> </xs: simpleType>

<xs： simpleType name="Data-Usage"> <xs: simpleType name="Data-Usage">

<xs： restriction base="xs： string"> <xs: restriction base="xs: string">

<xs: enumeration value="no_information"/> <xs: enumeration value="no_information"/>

<xs: enumeration value="RTCP"/> <xs: enumeration value="RTCP"/>

<xs: enumeration value="AF_signalling'7> <xs: enumeration value="AF_signalling'7>

</xs:restriction> </xs： simpleType> </xs:restriction> </xs: simpleType>

<xs： simpleType name="Data-type"> <xs： restriction base="xs： string"> <xs: enumeration value="video'7> <xs: enumeration value="audio'7> <xs: enumeration value="data"/> <xs: simpleType name="Data-type"> <xs: restriction base="xs: string"> <xs: enumeration value="video'7> <xs: enumeration value="audio'7> <xs: enumeration Value="data"/>

</xs:restriction> </xs:restriction>

</xs： simpleType> </xs: simpleType>

<xs： simpleType name="priority"> <xs: simpleType name="priority">

<xs： restriction base="xs： string"> <xs: enumeration value="l "/> <xs: enumeration value="2"/> <xs: restriction base="xs: string"> <xs: enumeration value="l "/> <xs: enumeration value="2"/>

<xs: enumeration value="9"/> </xs:restriction> <xs: enumeration value="9"/> </xs:restriction>

</xs： simpleType> </xs: simpleType>

<xs: simpleType name="cause-type"> <xs： restriction base="xs： string"> <xs: enumeration value="l "/> <xs: enumeration value="2"/> <xs: simpleType name="cause-type"> <xs: restriction base="xs: string"> <xs: enumeration value="l "/> <xs: enumeration value="2"/>

<xs: enumeration value="8"/> </xs:restriction> <xs: enumeration value="8"/> </xs:restriction>

</xs： simpleType> </xs:element> </xs: simpleType> </xs:element>

<xs： complexType name="IPFilterRule" > <xs: complexType name="IPFilterRule" >

<xs: attribute name: ="source-IP-address" type="xs:string'7> <xs: attribute name: ="source-IP-address" type="xs:string'7>

<xs: attribute name: ="source-IP-port" type="xs: string" use="optional"/> <xs: attribute name: ="source-IP-port" type="xs: string" use="optional"/>

<xs: attribute name: ="destination-IP-address" type="xs:string"/> <xs: attribute name: ="destination-IP-address" type="xs:string"/>

<xs: attribute name: ="destination-IP-port" type="xs:string'7> <xs: attribute name: ="destination-IP-port" type="xs:string'7>

<xs: attribute name: ="protocol" type="xs:string'7> <xs: attribute name: ="protocol" type="xs:string'7>

</xs:complexType> </xs:complexType>

</xs: schema > </xs: schema >

如上所述，数据应用业务信息以根元素 "af-session"开始，同时为 "af-session"元素设置属性 "state", 用以描述 "af-session"的状态，可以是 "session initialization(会话开： ½ )"、 "session modification(会话修改 )"、 "session termination (会话终止) "三种状态。下发的数据应用业务信息所包含的元素可以根据实际需求按照 XML语法进行灵活定义，例如当对非 IMS数据应用业务进行策略控制时， Media-Component-Description元素不包含于 XML定义中；再如业务流釆用 RTP方式传输时， Data-Description元素可以出现多次。 As mentioned above, the data application service information starts with the root element "af-session" and sets the attribute "state" for the "af-session" element to describe the state of "af-session", which can be "session initialization". Open: 1⁄2)", "session modification", "session termination". The elements of the delivered data application service information can be flexibly defined according to the actual requirements according to the XML syntax. For example, when the policy control of the non-IMS data application service is performed, the Media-Component-Description element is not included in the XML definition; The Data-Description element can appear multiple times when the traffic is transmitted in RTP mode.

基于上述三种数据应用 AF向 PCRF下发数据应用业务信息的方式之一，还可在数据应用业务信息中携带应用业务提供商信息。如：应用业务提供商标识（ ASP-Identifier ) 。 Based on the foregoing three types of data, the application of the service information by the AF to the PCRF is performed, and the application service provider information may also be carried in the data application service information. For example: ASP-Identifier is provided by the application business.

对于非 IMS数据应用业务，存在相同数据应用业务可以由不同业务提供商提供的情况，因此非 IMS中的数据应用 AF下发数据应用业务信息时，除了需要携带 AF应用标识表示具体的数据应用之外，还可携带 ASP标识，以使 PCRF为不同 ASP提供业务实施不同的策略控制。 For a non-IMS data application service, there is a case where the same data application service can be provided by different service providers. Therefore, when the data application service information is sent by the non-IMS data, the AF application identifier is required to represent the specific data application. In addition, the ASP identifier can also be carried, so that the PCRF implements different policy control for different ASPs to provide services.

本发明实施例给出一个定义 ASP标识的示例如下： An example of defining an ASP identifier is given in the embodiment of the present invention as follows:

ASP-Identifier AVP ( AVP code χ χ χ ) , OctetString型，包含识别 ASP的标识信息，由数据应用 AF给 PCRF下发数据应用业务信息时包含，用以区分提供相同非 IMS数据应用业务的不同应用业务提供商。 The ASP-Identifier AVP (AVP code χ χ χ ), the OctetString type, includes the identifier information for identifying the ASP, and is included when the data application AF sends the data application service information to the PCRF to distinguish different applications that provide the same non-IMS data application service. Service provider.

对于增设的 ASP-Identifier AVP可以直接位于 Dimeter会话消息结构下；也可以置于 Media-Component-Description AVP 结构下；还可以通过爹改 AF-Application-Identifier AVP ( AF-Charging-Identifier AVP ) , 使之包含应用业务提供商信息，例如通过修改 AF-Application-Identifier AVP定义，以邮件地址形式作为其取值，其中主机名部分可以作为 ASP 标识，如 abc(¾carrier.com中 , carrier.com为 ASP标识。 The added ASP-Identifier AVP can be directly located under the Dimeter session message structure; it can also be placed under the Media-Component-Description AVP structure; AF-Application-Identifier AVP (AF-Charging-Identifier AVP), which includes the application service provider information, for example, by modifying the AF-Application-Identifier AVP definition, taking the value of the email address as the value, where the host name part can be used as ASP logo, such as abc (3⁄4carrier.com, carrier.com is the ASP logo.

ASP-Identifier AVP位于 Diameter会话消息结构中的一个示例如下: An example of the ASP-Identifier AVP in the Diameter session message structure is as follows:

<AA-Request> ::= < Diameter Header: 265, REQ, PXY >

ASP Ide tifier ASP Ide tifier

[ AF-Charging-Identifier ] 从上述示例中可看出，在数据应用业务信息中，通过 ASP-Identifier AVP 来标识由 ASP1提供业务和由 ASP2提供业务的区别。根据下发的数据应用业务信息， PCRF可以为 ASP1提供业务制订控制策略。 [AF-Charging-Identifier] As can be seen from the above example, in the data application service information, the difference between the service provided by ASP1 and the service provided by ASP2 is identified by the ASP-Identifier AVP. Based on the delivered data application service information, the PCRF can provide a control strategy for the service provided by ASP1.

此外也可以通过在 PCRF 上配置与数据应用业务信息对应的应用业务提供商相关信息（如 ASP配置信息）， PCRF根据数据应用 AF下发的数据应用业务信息中包含的 AF地址或域名信息或者其他方式实现数据应用业务信息和 PCRF上配置的应用业务提供商相关信息的关联，从而感知提供该应用业务的应用业务提供商，并根据该应用业务提供商相关信息、数据应用业务信息以及结合其他策略策略上下文信息，对应用业务进行策略决策。 In addition, the application service provider related information (such as the ASP configuration information) corresponding to the data application service information may be configured on the PCRF, and the PCRF applies the AF address or domain name information included in the service information delivered by the AF application data or other information. The method implements association between the data application service information and the application service provider related information configured on the PCRF, so as to perceive the application service provider that provides the application service, and according to the application service provider related information, the data application service information, and other strategies. Policy context information, making policy decisions for the application business.

S12、 PCRF根据所述数据应用业务信息进行策略决策。 S12. The PCRF performs policy decision according to the data application service information.

本步骤中，根据数据应用业务信息并结合其它信息完成策略决策。 In this step, the policy decision is made according to the data application service information combined with other information.

PCRF根据数据应用 AF下发的数据应用业务信息，以及从其它实体获知的信息（比如用户签约信息、运营商本地策略、接入网类型）完成策略决策，并下发给 PCEF执行。 The PCRF applies the service information based on the data sent by the AF, and the information learned from other entities (such as the user subscription information, the carrier local policy, and the access network type) to complete the policy decision and deliver the policy decision to the PCEF.

PCEF收到控制策略信息后，根据该控制策略信息执行相应数据应用业务流的 QoS、计费和 /或门控等策略控制。进一步如果控制策略信息是门控信息，则 PCEF对数据应用报文进行过滤，对匹配数据应用业务流的报文根据门控控制策略给出的指示（Disable, Enable等）进行转发或者丟弃等门控控制；如果控制策略信息是 Qos控制策略，则 PCEF可以根据 QoS控制策略发起 QoS策略控制，进行 IP-CAN会话的更新操作，例如 IP-CAN会话的 Qos参数更新，或 IP-CAN 承载的建立、删除等操作；如果控制策略信息是计费控制策略，则 PCEF可以根据计费控制策略进行计费控制，如按流量或时长计费，在线或离线计费等计费控制。 After receiving the control policy information, the PCEF performs policy control such as QoS, charging, and/or gating of the corresponding data application service flow according to the control policy information. Further, if the control policy information is the gating information, the PCEF filters the data application message, and forwards or discards the packet matching the data application service flow according to the indication (Disable, Enable, etc.) given by the gating control policy. Gating control; The control policy information is a QoS control policy, and the PCEF can initiate QoS policy control according to the QoS control policy, and perform an update operation of the IP-CAN session, such as an QoS parameter update of the IP-CAN session, or an operation of establishing and deleting an IP-CAN bearer. If the control policy information is a charging control policy, the PCEF may perform charging control according to the charging control policy, such as charging according to traffic or duration, online or offline charging, and the like.

本发明实施例还提供了一种非 IMS中的数据应用功能实体，参见图 4所示，其包括：触发单元和下发单元。 The embodiment of the present invention further provides a data application function entity in the non-IMS, as shown in FIG. 4, which includes: a trigger unit and a sending unit.

触发单元，用于接收触发事件。 A trigger unit, configured to receive a trigger event.

下发单元，用于在触发单元收到触发事件时，下发相应的数据应用业务信息。具体的，下发单元通过修订 Rx接口定义中的 IMS应用业务流信息单元，下发数据应用业务信息所包含的数据应用业务流信息；或者下发单元通过在 Rx 接口定义中新增数据应用业务流信息单元，下发数据应用业务信息所包含的数据应用业务流信息；或者下发单元通过 HTTP协议下发数据应用业务信息。 The sending unit is configured to send corresponding data application service information when the trigger unit receives the trigger event. Specifically, the sending unit modifies the IMS application service flow information unit in the Rx interface definition, and sends the data application service flow information included in the data application service information; or the sending unit adds a data application service by defining the Rx interface. The flow information unit sends the data application service flow information included in the data application service information; or the delivery unit sends the data application service information through the HTTP protocol.

本发明实施例还提供了一种策略控制和计费规则功能实体，参见图 5所示，其包括：接收单元和决策单元。 The embodiment of the present invention further provides a policy control and charging rule function entity. As shown in FIG. 5, the method includes: a receiving unit and a decision unit.

接收单元，用于接收数据应用业务信息。具体的，接收单元通过修订 Rx 接口定义中的 IMS应用业务流信息单元，接收数据应用业务信息所包含的数据应用业务流信息；或者接收单元通过在 Rx接口定义中新增数据应用业务流信息单元，接收数据应用业务信息所包含的数据应用业务流信息；或者接收单元通过 HTTP协议接收数据应用业务信息。 The receiving unit is configured to receive data application service information. Specifically, the receiving unit receives the data application service flow information included in the data application service information by modifying the IMS application service flow information unit in the Rx interface definition; or the receiving unit adds the data application service flow information unit by adding the data in the Rx interface definition. Receiving data application service flow information included in the data application service information; or receiving the data application service information through the HTTP protocol.

决策单元，用于根据接收单元收到的数据应用业务信息进行策略决策。本发明实施例还提供了一种非 IMS数据应用的策略控制***，包括数据应用 AF和 PCRF。 The decision unit is configured to apply the service information according to the data received by the receiving unit to make a policy decision. The embodiment of the invention further provides a policy control system for non-IMS data applications, including data applications AF and PCRF.

非 IMS中的数据应用 AF, 用于下发数据应用业务信息。 The data application AF in the non-IMS is used to deliver data application service information.

PCRF, 用于接收非 IMS中的数据应用 AF下发的数据应用业务信息，并根据该数据应用业务信息进行策略决策。 The PCRF is configured to receive data application service information delivered by the AF application in the non-IMS, and apply the service information according to the data to perform policy decision.

具体的， PCRF与非 IMS中的数据应用 AF之间通过修订 Rx接口定义中的 IMS应用业务流信息单元，收发数据应用业务信息所包含的数据应用业务流信息；或者 PCRF与数据应用 AF之间通过在 Rx接口定义中新增数据应用业务流信息单元，收发数据应用业务信息所包含的数据应用业务流信息；或者 PCRF与数据应用 AF之间通过 HTTP协议收发数据应用业务信息。 Specifically, between the PCRF and the non-IMS data application AF, the IMS application service flow information unit in the definition of the Rx interface is modified, and the data application service flow information included in the service application information is sent and received; or between the PCRF and the data application AF. Add a data application service flow letter by adding an Rx interface definition. The information unit transmits and receives data application service flow information included in the service application information; or sends and receives data application service information between the PCRF and the data application AF through the HTTP protocol.

为了对上述 PCC应用于非 IMS数据应用业务进行策略控制的可行性做进一步说明，后续将给出策略控制的实施例。 In order to further explain the feasibility of applying the above PCC to the non-IMS data application service for policy control, an embodiment of policy control will be given later.

实施例一：歌曲点播 Embodiment 1: Song on demand

歌曲点播通常釆用 RTSP作为流控制协议，数据应用业务数据流釆用 RTP 方式传输。用户终端通过 RTSP信令可以实现点播开始、暂停、终止等操作。下表给出了点播过程的 RTSP信令示例： Song on-demand usually uses RTSP as the flow control protocol, and the data application service data stream is transmitted in RTP mode. The user terminal can implement operations such as start, pause, and termination of the on-demand through the RTSP signaling. The following table shows an example of RTSP signaling for the on-demand process:

① C->M: DESCRIBE rts ://audio . example . com/twister/audio .wav 1 C->M: DESCRIBE rts ://audio . example . com/twister/audio .wav

RTSP/1.0 RTSP/1.0

CSeq: 1 CSeq: 1

M->C: RTSP/1.0 200 1 OK M->C: RTSP/1.0 200 1 OK

Content-Type: application/sdp Content-Type: application/sdp

Content-Length: 164 Content-Length: 164

v=0 V=0

o=- 2890844256 2890842807 IN IP4 172.16.2.93 o=- 2890844256 2890842807 IN IP4 172.16.2.93

s=RTSP Session s=RTSP Session

i=An Example of RTSP Session Usage i=An Example of RTSP Session Usage

t=0 0 t=0 0

m=audio 0 RTP/AVP 0 m=audio 0 RTP/AVP 0

② C -〉 M: SETUP rtsp：〃 audio.example.com/twister/audio.wav RTSP/1.0 2 C -> M: SETUP rtsp:〃 audio.example.com/twister/audio.wav RTSP/1.0

CSeq: 2 CSeq: 2

Transport: RTP/AVP;unicast;client_port=8000-8001 Session: 12345678 Transport: RTP/AVP; unicast; client_port=8000-8001 Session: 12345678

M->C: RTSP/1.0 200 OK M->C: RTSP/1.0 200 OK

CSeq: 2 CSeq: 2

Transport: RTP/AVP;unicast;client_port=8000-8001； Transport: RTP/AVP; unicast; client_port=8000-8001;

server_port=9000-9001 Server_port=9000-9001

Session: 12345678 3) C->M: PLAY rtsp://audio. example.com/twister/audio.wav RTSP/1.0 Session: 12345678 3) C->M: PLAY rtsp://audio. example.com/twister/audio.wav RTSP/1.0

CSeq: 3 CSeq: 3

Session: 12345678 Session: 12345678

M->C: RTSP/1.0 200 OK M->C: RTSP/1.0 200 OK

CSeq: 3 CSeq: 3

Session: 12345678 Session: 12345678

RTP-Info: url=rtsp://foo/twister/audio; RTP-Info: url=rtsp://foo/twister/audio;

seq=9810092;rtptime=3450012 Seq=9810092;rtptime=3450012

④ C->M: PAUSE rtsp：〃 audio. example.com/twister/audio.wav RTSP/1.0 4 C->M: PAUSE rtsp:〃 audio. example.com/twister/audio.wav RTSP/1.0

CSeq: 4 CSeq: 4

Session: 12345678 Session: 12345678

M->C: RTSP/1.0 200 OK M->C: RTSP/1.0 200 OK

CSeq: 4 CSeq: 4

Session: 12345678 Session: 12345678

⑤ C->M: TEARDOWN rtsp：〃 audio. example.com/twister/audio.wav 5 C->M: TEARDOWN rtsp:〃 audio. example.com/twister/audio.wav

RTSP/1.0 RTSP/1.0

CSeq: 5 CSeq: 5

Session: 12345678 Session: 12345678

M->C: RTSP/1.0 200 OK M->C: RTSP/1.0 200 OK

CSeq: 5 CSeq: 5

"C"表示用户终端； "M"表示媒体服务器，存放媒体内容。 "C" represents the user terminal; "M" represents the media server, which stores the media content.

其中，过程 1显示的是用户终端向媒体服务器请求提取业务流描述，媒体服务器根据请求返回信息；过程 2表示用户终端和媒体服务器各自设置传输业务流所使用的端口号；过程 3表示用户终端启动歌曲点播的过程；过程 4表示用户终端要求暂停点播业务；过程 5表示用户终端请求终止点播业务。对歌曲点播过程实施策略控制的具体流程见图 6所示： The process 1 shows that the user terminal requests the media server to extract the service flow description, and the media server returns the information according to the request; the process 2 indicates that the user terminal and the media server respectively set the port number used for transmitting the service flow; and the process 3 indicates that the user terminal starts. The process of song on demand; the process 4 indicates that the user terminal requests to suspend the on-demand service; the process 5 indicates that the user terminal requests to terminate the on-demand service. The specific process for implementing policy control on the song on demand process is shown in Figure 6:

点播开始: Start on-demand:

1-2 )该过程为 RTSP的媒体初始化阶段，用户终端通过 "DESCRIBE"消息向点播服务器（即数据应用 AF )请求获取业务流描述信息；该点播服务器返回响应，包括媒体类型、媒体地址、媒体传输方式等。 1-2) The process is a media initialization phase of the RTSP, and the user terminal requests the service flow description information to the on-demand server (ie, the data application AF) through the "DESCRIBE"message; the on-demand server returns Back response, including media type, media address, media transfer method, and so on.

3 )用户终端使用 "SETUP"消息将用户终端用于接收媒体的端口号发送给该点播服务器。 . 3) The user terminal sends a port number for receiving the media by the user terminal to the on-demand server using a "SETUP" message. .

4 )点播服务器使用 Diameter AAR消息向 PCRF下发应用业务请求信息，下发信息如下： 4) The on-demand server sends the application service request information to the PCRF by using the Diameter AAR message, and the following information is sent:

[ Data-Application-Description [ Data-Application-Description

[ AF-Charging-Identifier ] [ AF-Charging-Identifier ]

[ Subscription-ID ] [ Subscription-ID ]

[ Reservation-Priority ] [ Reservation-Priority ]

[ Framed-IP- Address ] [ Framed-IP- Address ]

[ Data-Type ] [ Data-Type ]

[ Data- Status ] [ Data- Status ]

[ Data-Usage ] [ Data-Usage ]

[ AF-Application-Identifier ] [ AF-Application-Identifier ]

[ Max-Requested-Bandwidth-UL ] [ Max-Requested-Bandwidth-UL ]

[ Max-Requested-Bandwidth-DL ] [ Max-Requested-Bandwidth-DL ]

[ RS-Bandwidth ] [ RS-Bandwidth ]

[ RR-Bandwidth ] [ RR-Bandwidth ]

*[ Codec-Data ] Data- Application-Description AVP描述数据应用业务流，其中： Data-Description AVP表示描述数据应用业务流的五元组，根据用户与点播服务器的 "DESCRIBE", "SETUP"设置及响应过程导出，本实施例中，由于数据应用业务流以 RTP方式传输，因此 Data- Application-Description AVP结构下有两个 Data-Description AVP, 一个表示 RTP流，取值为用户接收数据应用业务流的地址（ 170.34.4.28可通过 Via消息头获取）和端口号（ 8000 ) 、点播服务器发送数据应用业务流的地址（ 172.16.2.93 )和端口号（9000 ) 、传输协议；另一个表示 RTCP流，取值为用户接收数据应用业务流的地址和端口号（8001 ) 、点播服务器发送数据应用业务流的地址和端口号（ 9001 )、协议。 Data-Type AVP 取值为 "audio"; Data-Status AVP取值为 "enabled"。 RTCP流对应的 Data-Usage AVP取值为 "RTCP"; 其余各参数取值与本发明无关，这里不再列举说明。 *[ Codec-Data ] The Data-Application-Description AVP describes the data application service flow, where: Data-Description AVP represents a quintuple describing the data application service flow, and is derived according to the "DESCRIBE", "SETUP" setting and response process of the user and the on-demand server. For example, since the data application service flow is transmitted in RTP mode, there are two Data-Description AVPs in the Data-Application-Description AVP structure, one representing the RTP stream, and the value is the address of the user receiving the data application service flow (170.34.4.28) It can be obtained through Via header and port number (8000), the address server sends the address of the data application service flow (172.16.2.93) and the port number (9000), the transmission protocol; the other represents the RTCP stream, and the value is the user receiving data. The address and port number (8001) of the application service flow, the address and port number (9001) of the data application service flow are sent by the on-demand server, and the protocol. The value of the Data-Type AVP is "audio"; the value of the Data-Status AVP is "enabled". The value of the Data-Usage AVP corresponding to the RTCP stream is "RTCP"; the values of the remaining parameters are not related to the present invention, and the description is not repeated here.

5-7 ) PCRF根据数据应用业务信息及其它信息 (运营商策略、用户签约信息、接入网类型）为数据应用业务流决策相应的策略并以 PCC规则的形式下发给 PCEF执行， PCEF收到控制策略信息后，根据该控制策略信息执行相应数据应用业务流的 QoS、计费和 /或门控等策略控制。本实施例中 PCEF根据下发的 PCC规则中的 QCI ( QoS-Class-Identifier QoS等级）需要新建相应的 IP-CAN bearer来承载点播业务流；同时根据 PCC规则包含的 Data-Type为" enabled"的指示，开启门控，允许数据应用业务流报文通过 PCEF;对于计费， PCEF根据 PCC 规则中包含的计费策略为歌曲点播釆取按流量的计费方式。 5-7) The PCRF applies the service information and other information (operator policy, user subscription information, access network type) to the data application service flow decision-making strategy and sends it to the PCEF in the form of PCC rules. After the control policy information is obtained, policy control such as QoS, charging, and/or gating of the corresponding data application service flow is performed according to the control policy information. In this embodiment, the PCEF needs to create a corresponding IP-CAN bearer to carry the on-demand service flow according to the QCI (QoS-Class-Identifier QoS level) in the issued PCC rule; and the Data-Type included in the PCC rule is "enabled". The indication is that the gating is enabled, and the data application service flow message is allowed to pass through the PCEF; for charging, the PCEF collects the traffic-based charging mode for the song on-demand according to the charging policy included in the PCC rule.

8-9 ) PCC规则执行成功， PCRF向点播服务器 AF返回确认信息，该点播服务器返回 200OK响应给用户终端，其中包括该点播服务器传输媒体所使用的端口号。 8-9) The PCC rule is successfully executed, and the PCRF returns an acknowledgement message to the on-demand server AF, and the on-demand server returns a 200 OK response to the user terminal, including the port number used by the on-demand server to transmit the media.

10-11 ) 用户终端发送 "PLAY"消息请求启动点播；点播服务器返回 "200OK", 启动点播过程。 10-11) The user terminal sends a "PLAY" message requesting to start on-demand; the on-demand server returns "200OK" to start the on-demand process.

点播暂停： On-demand pause:

12 )用户终端向点播服务器 AF发送" PAUSE"消息请求暂停点播； 12) The user terminal sends a "PAUSE" message to the on-demand server AF to request to pause on-demand;

13 )点播服务器 AF将更改的应用业务信息下发给 PCRF: 13) On-demand server AF sends the changed application service information to the PCRF:

<AA-Request> ::= < Diameter Header: 265, REQ, PXY > [ Data- Application-Description ] 其中 Media-Component-Description A VP包含的参数如下： <AA-Request> ::= < Diameter Header: 265, REQ, PXY > [ Data- Application-Description ] where the Media-Component-Description A VP contains the following parameters:

Media-Component-Description ::= < A VP Header: 517 > Media-Component-Description ::= < A VP Header: 517 >

* [ Data-Description ] * [ Data-Description ]

[ Data-Status ] [ Data-Status ]

将 Data-Status AVP取值改为 "disabled"表示暂停业务数据流。 Changing the value of the Data-Status AVP to "disabled" means suspending the traffic.

14-15 )根据下发的数据应用业务信息， PCRF修改策略，并以 PCC规则的形式下发给 PCEF执行。根据门控策略， PCEF关闭门控，暂停业务数据流从 14-15) Apply the service information according to the delivered data, and the PCRF modifies the policy and sends it to the PCEF in the form of a PCC rule. According to the gating strategy, the PCEF closes the gating and suspends the traffic data flow from

PCEF通过。 PCEF passed.

16-17 ) PCC规则执行成功， PCRF向点播服务器 AF返回确认信息，点播服务器 AF向用户终端返回 200OK响应，暂停点播业务。 16-17) The PCC rule is executed successfully. The PCRF returns confirmation information to the on-demand server AF. The on-demand server AF returns a 200 OK response to the user terminal to suspend the on-demand service.

点播结束： End of on-demand:

18 )用户终端向点播服务器 AF发送" TEARDOWN"消息，要求终止点播业务； 19 ) 点播服务器 AF向 PCRF发送终止业务请求； 18) The user terminal sends a "TEARDOWN" message to the on-demand server AF, requesting termination of the on-demand service; 19) the on-demand server AF sends a termination service request to the PCRF;

20-21 )根据请求， PCRF删除 PCC规则，并要求 PCEF释放 PCC规则对应的 IP-CAN bearer, PCEF完成操作返回响应； 20-21) According to the request, the PCRF deletes the PCC rule, and requests the PCEF to release the IP-CAN bearer corresponding to the PCC rule, and the PCEF completes the operation and returns a response;

22-23 )根据 PCEF返回的响应， PCRF向点播服务器 AF返回确认信息，点播服务器 AF向用户终端返回 200OK响应，终止点播业务。 22-23) According to the response returned by the PCEF, the PCRF returns confirmation information to the on-demand server AF, and the on-demand server AF returns a 200 OK response to the user terminal to terminate the on-demand service.

实施例二： FTP下载。 Embodiment 2: FTP download.

FTP下载是最常用的数据应用业务，用户在进行 FTP业务时只进行传输端口号的协商，没有 SDP协商的过程。另外由于进行 FTP下载业务的业务提供商或网络运营商都釆用基于 web的协议，因此考虑在本实施例实现数据应用业务信息下发时，釆用 XML描述下发信息，用 HTTP协议传递信息。 The FTP download is the most commonly used data application service. When the FTP service is performed, the user only negotiates the transmission port number. There is no SDP negotiation process. In addition, since the service provider or the network operator that performs the FTP download service uses the web-based protocol, when the data application service information is delivered in this embodiment, the information is sent by the XML description and the information is transmitted by using the HTTP protocol.

电信网络上开展的 FTP下载业务可以由 ASP1和 ASP2提供，但是 ASP1和 ASP2对提供 FTP下载釆取的收费方式存在区别，例如 ASP1可能釆取按流量计费的方式，而 ASP2可能釆取按下载内容的计费方式，因此在对 FTP下载业务实施策略控制时，下发的应用业务信息中应包含 ASP标识，以使 PCRF为不同的 ASP制订不同的控制策略。具体流程见图 7所示： The FTP download service carried out on the telecommunication network can be provided by ASP1 and ASP2, but ASP1 and ASP2 have different charging methods for providing FTP downloading. For example, ASP1 may take the method of charging according to the flow rate, and ASP2 may extract the download by downloading. The content charging method. Therefore, when implementing policy control on the FTP download service, the application service information delivered should include the ASP identifier to make the PCRF different. ASP develops different control strategies. The specific process is shown in Figure 7:

FTP下载开始： FTP download starts:

1 )用户终端与 ASP1 (即非 IMS中的数据应用 AF )之间完成 FTP应用协商； 2 ) ASP1将下载业务对应的数据应用业务信息下发给 PCRF , 下发信息包含 ASP-Identifier标识，表示该 FTP下载业务由 ASP1提供。釆用 XML描述如下： <?xml version:" 1.0"?> 1) The user terminal and the ASP1 (that is, the non-IMS data application AF) complete the FTP application negotiation; 2) the ASP1 sends the data application service information corresponding to the download service to the PCRF, and the delivery information includes the ASP-Identifier identifier, indicating The FTP download service is provided by ASP1. The XML description is as follows: <?xml version:" 1.0"?>

<af-session xmlns:xsi=http：〃 www.w3.org/2001/XMLSchema-instance <af-session xmlns:xsi=http:〃 www.w3.org/2001/XMLSchema-instance

xsi:noNamespaceSchemaLocation="D:\XML\test.xsd" state="sessiom Xsi:noNamespaceSchemaLocation="D:\XML\test.xsd" state="sessiom

ieitiaIization"> ieitiaIization">

<Data-Application-Description> <Data-Application-Description>

<Data-Description>l 70.34,4,28, 20, 172,16,2,93， 6015, <Data-Description>l 70.34,4,28, 20, 172,16,2,93, 6015,

TCP</Data-Description> TCP</Data-Description>

<Data-Type>data</Data-Type> <Data-Type>data</Data-Type>

<Reservation-priority> 1 </Reservation-priority> <Reservation-priority> 1 </Reservation-priority>

<Data-status>enabled</Data-status> <Data-status>enabled</Data-status>

<AF-Application-Identifier>abcdef</AF-Application-Identifier>

</Data-Application-Description> </Data-Application-Description>

<ASP-Identifier>asp-l</ASP-Ideiitifier> <ASP-Identifier>asp-l</ASP-Ideiitifier>

<AF-Charging-Identifier>adfasd</AF-Charging-Identifier> <AF-Charging-Identifier>adfasd</AF-Charging-Identifier>

<subscription-ID>23432608</subscription-ID> <subscription-ID>23432608</subscription-ID>

<UE-IP-Address> 172.16.2.93</UE-IP-Address> <UE-IP-Address> 172.16.2.93</UE-IP-Address>

</af-session> </af-session>

注：以 170.34.4.28表示 FTP服务器 IP地址， 20表示发送数据的端口号；以 172.16.2.93表示用户 IP地址， 6015表示端口号。本次数据应用的标识为 abcdef; FTP服务器标识为 asp- 1 Note: The IP address of the FTP server is indicated by 170.34.4.28, the port number of the data is sent by 20; the IP address of the user is indicated by 172.16.2.93, and the port number is indicated by 6015. The identifier of the data application is abcdef; the FTP server identifier is asp- 1

采用 HTTP传递信息示例如下： GET An example of passing information over HTTP is as follows: GET

http：〃 www.pcc.rule. com/xml/session-initializati m HTTP/1.1 3-5 ) PCRF根据数据应用业务信息及其它信息（运营商策略、用户签约信息、接入网类型）为数据应用业务数据流决策相应的策略，并以 PCC规则的形式下发给 PCEF执行。 PCEF收到控制策略信息后，根据控制策略信息执行相应数据应用业务流的 QoS、计费和 /或门控等策略控制。本实施例中 PCEF根据下发的 PCC规则中的 QCI ( QoS-Class-Identifier QoS等级）发现需要新建相应的 IP-CAN bearer来承载下载数据应用业务流；同时根据 PCC规则包含的 Data-Type为" enabled"的指示，开启门控，允许数据应用业务流 4艮文通过 PCEF; 对于计费， PCEF根据 PCC规则中包含的计费策略为 ASP1提供的下载业务釆取按流量计费的方式。 Http:〃 www.pcc.rule. com/xml/session-initializati m HTTP/1.1 3-5) The PCRF determines the corresponding policy for the data application service data flow according to the data application service information and other information (operator policy, user subscription information, and access network type), and sends the policy to the PCEF in the form of a PCC rule. After receiving the control policy information, the PCEF performs policy control such as QoS, charging, and/or gating of the corresponding data application service flow according to the control policy information. In this embodiment, the PCEF needs to create a corresponding IP-CAN bearer to carry the downloaded data application service flow according to the QCI (QoS-Class-Identifier QoS level) in the issued PCC rule; and the Data-Type included in the PCC rule is The "enabled" command enables the gating to allow the data application service flow to pass through the PCEF. For billing, the PCEF fetches the download service provided by ASP1 according to the charging policy included in the PCC rule.

6-7 ) PCC规则执行成功， PCRF向 ASP1返回确认消息， ASP1与用户终端启动 FTP下载过程。 6-7) The PCC rule is successfully executed. The PCRF returns an acknowledgement message to ASP1, and ASP1 and the user terminal start the FTP download process.

FTP下载终止： FTP download terminated:

8-9 )用户终端要求终止 FTP下载业务， ASP1向 PCRF发出终止请求，釆用 8-9) The user terminal requests to terminate the FTP download service, and ASP1 sends a termination request to the PCRF.

XML描述如下: The XML description is as follows:

<?xml version:" 1.0"?> <?xml version:" 1.0"?>

xsi:noNamespaceSchemaLocation="D:\XML\test.xsd" state="sessio¾ Xsi:noNamespaceSchemaLocation="D:\XML\test.xsd" state="sessio3⁄4

termi atio¾"> Termi atio3⁄4">

<Data-Application-Description> <Data-Application-Description>

<Data-Description>l 70,34,4,28， 20， 172,16,2,93， 6015, <Data-Description>l 70,34,4,28, 20, 172,16,2,93, 6015,

TCP</Data-Description> TCP</Data-Description>

</Data-Application-Description> </Data-Application-Description>

<subscription-ID/> <subscription-ID/>

<UE-IP-Address/> <UE-IP-Address/>

</af-session> </af-session>

http：〃 www.pcc.rule. com/xml/session-termina ion HTTP/ 1.1 Http:〃 www.pcc.rule. com/xml/session-termina ion HTTP/ 1.1

10-11 )根据下发的终止请求消息， PCRF删除 PCC规则，并要求 PCEF释放 PCC规则对应的 IP-CAN bearer, PCEF完成操作返回响应； 12-13 )根据 PCEF返回的响应， PCRF向 ASP1返回响应消息， ASP1与终止 FTP下载业务。 10-11) According to the issued termination request message, the PCRF deletes the PCC rule, and requests the PCEF to release the IP-CAN bearer corresponding to the PCC rule, and the PCEF completes the operation and returns a response; 12-13) According to the response returned by the PCEF, the PCRF returns a response message to ASP1, and ASP1 terminates the FTP download service.

为了使 PCRF进行策略决策时，可考虑不同业务提供商提供相同业务时可能釆用不同的策略，本发明实施例还提供了一种应用的策略控制方法，参见图 8所示，包括下列主要步骤： In order to make the policy decision of the PCRF, it may be considered that different services may provide different policies when the service provider provides the same service. The embodiment of the present invention further provides an application policy control method, as shown in FIG. 8, including the following main steps. :

521、 PCRF获取应用业务提供商标识。 521. The PCRF obtains an application service provider identifier.

522、 PCRF根据所述应用业务提供商标识进行策略决策。 522. The PCRF performs policy decision according to the application service provider identifier.

所述 S21中 PCRF可根据 AF发来的应用业务信息获取应用业务提供商标识，具体包括下述两种方式： The PCRF in the S21 can obtain the trademark of the application service according to the application service information sent by the AF, and specifically includes the following two methods:

方式 A、 AF下发的应用业务信息中携带有应用业务提供商标识， PCRF直接从 AF下发的应用业务信息中获得。 The application service information sent by the AF carries the application service provider identifier, and the PCRF is directly obtained from the application service information delivered by the AF.

具体的，所述 AF可为 IMS中的 AF, 该 AF将应用业务提供商标识携带于应用业务信息中向 PCRF下发； AF也可为非 IMS中的数据应用 AF,该数据应用 AF 将应用业务提供商标识携带于数据应用业务信息中向 PCRF下发。具体下发方式参见实施例二中的描述，例如： ASP1将下载业务对应的数据应用业务信息下发给 PCRF, 下发信息包含 ASP-Identifier标识，表示该 FTP下载业务由 ASP1 提供。之后， S22中 PCRF根据该 ASP-Identifier标识，指示 PCEF执行相应应用业务流的 QoS、计费和 /或门控的控制策略。 Specifically, the AF may be an AF in the IMS, where the AF carries the application service identifier in the application service information and sends the message to the PCRF; the AF may also apply the AF to the data in the non-IMS, and the data application AF will be applied. The service provider identifier is carried in the data application service information and sent to the PCRF. For the specific delivery method, refer to the description in the second embodiment. For example, the ASP1 sends the data application service information corresponding to the download service to the PCRF. The information sent includes the ASP-Identifier identifier, indicating that the FTP download service is provided by ASP1. Then, the PCRF in S22 instructs the PCEF to perform a QoS, charging, and/or gating control policy of the corresponding application service flow according to the ASP-Identifier identifier.

方式 B、 PCRF将 AF下发的应用业务信息与 PCRF中预设的应用业务提供商配置信息进行关联，得到应用业务提供商标识。 The method B and the PCRF associate the application service information delivered by the AF with the application service provider configuration information preset in the PCRF to obtain the application service provider identifier.

具体的，所述 AF可为 IMS中的 AF, 该 AF向 PCRF下发应用业务信息；所述 AF也可为非 IMS中的数据应用 AF,该数据应用 AF向 PCRF下发数据应用业务信息。具体下发方式参见实施例二中的描述。 Specifically, the AF may be an AF in the IMS, and the AF sends the application service information to the PCRF. The AF may also apply the AF to the data in the non-IMS, and the data application AF sends the data application service information to the PCRF. For details of the delivery method, refer to the description in the second embodiment.

在 PCRF上预设应用业务提供商标识以及应用业务提供商标识与应用业务信息 (包括但不限于 AF地址、域名信息或者其他方式实现数据应用业务信息）之间的关联关系。若 S21釆用本方式，则 S22中 PCRF先根据所述应用业务提供商标识与应用业务信息之间的关联关系，得出与 AF发来的应用业务信息关联的应用业务提供商标识，再以该应用业务提供商标识进行策略决策。策略决策得出的策略包括：指示 PCEF执行相应应用业务流的 QoS、计费和 /或门控的控制策略。 The association between the application service provider identifier and the application service provider identifier and the application service information (including but not limited to the AF address, the domain name information, or other manners to implement the data application service information) is preset on the PCRF. If the S21 uses the present mode, the PCRF in S22 first obtains the application service provider identifier associated with the application service information sent by the AF according to the association relationship between the application service provider identifier and the application service information, and then The application service provider identity makes policy decisions. The strategy decision-making strategy includes: Instructing the PCEF to perform QoS, charging, and/or gating control of the corresponding application service flow System strategy.

本发明实施例还提供了一种策略控制和计费规则功能实体，参见图 9所示，其包括：获取单元和决策单元；进一步所述获取单元中可包括第一获取子单元。 The embodiment of the present invention further provides a policy control and charging rule function entity. As shown in FIG. 9, the method includes: an obtaining unit and a determining unit. Further, the acquiring unit may include a first acquiring subunit.

获取单元，用于获取应用业务提供商标识；其中，第一获取子单元，用于从应用功能实体 AF发来的应用业务信息中获取应用业务提供商标识。 And an obtaining unit, configured to obtain an application service provider identifier, where the first obtaining subunit is configured to obtain an application service provider identifier from the application service information sent by the application function entity AF.

决策单元，用于根据获取单元获取的所述应用业务提供商标识进行策略决策。若第一获取子单元从应用功能实体 AF发来的应用业务信息中直接获得应用业务提供商标识，则决策单元直接以所述应用业务提供商标识进行策略决策；若第一获取子单元从应用功能实体 AF发来的应用业务信息中获得该 AF地址等信息，则根据预设的应用业务提供商标识与应用业务信息之间的关联关系，得出与该 AF发来的应用业务信息关联的应用业务提供商标识，之后决策单元再根据该应用业务提供商标识进行策略决策。 And a decision unit, configured to perform policy decision according to the application service provider identifier obtained by the obtaining unit. If the first acquisition sub-unit obtains the application service provider identifier directly from the application service information sent by the application function entity AF, the decision unit directly performs policy decision with the application service provider identifier; if the first acquisition sub-unit is from the application Obtaining the information such as the AF address in the application service information sent by the function entity AF, and obtaining, according to the association relationship between the preset application service provider identifier and the application service information, the association service information sent by the AF is obtained. After applying the service provider identifier, the decision unit then makes a policy decision based on the application service provider identifier.

以下通过两个实施例进一步详述该方法。 The method is further detailed below by two examples.

实施例三： FTP下载。参见图 10所示，包括下列步骤： Embodiment 3: FTP download. See Figure 10, which includes the following steps:

1 )客户端与 ASP1之间完成 FTP应用协商； 1) The FTP application negotiation is completed between the client and ASP1;

2 ) ASP1将下载业务对应的应用业务信息下发给 PCRF , 下发信息包含 ASP-Identifier标识，表示该 FTP下载业务由 ASP1提供； 2) ASP1 sends the application service information corresponding to the download service to the PCRF, and the delivery information includes an ASP-Identifier identifier, indicating that the FTP download service is provided by ASP1;

3 ) PCRF收到 ASP1下发的应用业务信息，根据 ASP-Identifier感知由 ASP1 提供 FTP下载业务，并结合应用业务信息及其它信息（运营商策略、用户签约信息、接入网类型）为业务制定相应的策略，比如为 ASP1提供的 FTP下载业务分配 QoS、制定计费策略、门控策略等； 3) The PCRF receives the application service information delivered by ASP1, and provides the FTP download service provided by ASP1 according to the ASP-Identifier, and combines the application service information and other information (operator policy, user subscription information, access network type) for the service. Corresponding strategies, such as assigning QoS, formulating charging policies, and gate control policies for the FTP download service provided by ASP1;

4 ) PCRF将策略下发给 PCEF执行； 4) The PCRF sends the policy to the PCEF for execution;

5 )根据策略， PCEF进行相应的 IP-CAN会话的修改； 5) According to the policy, the PCEF performs the modification of the corresponding IP-CAN session;

6 ) PCRF向 ASP1返回确认消息； 6) The PCRF returns an acknowledgement message to ASP1;

7 )用户终端开始 FTP下载业务， PCEF对下载业务执行策略控制。 7) The user terminal starts the FTP download service, and the PCEF performs policy control on the download service.

实施例四：视频点播。 Embodiment 4: Video on demand.

基于应用业务提供商策略或者客户群的不同，不同的应用业务提供商可能要求以不同的 QoS为用户提供相同的应用业务。假设 ASP— A和 ASP— B都提供 VOD业务，但是 ASP— A主要针对 VIP客户提供 VoD业务，而 ASP— B主要针对普通客户提供 VoD业务，即 ASP— A为客户提供业务时，比 ASP— B要求更高的 QoS 保证（例如更高的 QoS优先级、更大的带宽等）。因此网络运营商需要为不同的应用业务提供商提供的 VoD业务提供不同的 QoS保证。此时 PCRF需要根据配置的 ASP信息，并结合其他策略上下文信息，为应用业务提供商提供的 VoD 业务进行策略决策。例如 ASP— A为用户提供 VoD业务的策略控制，具体流程见图 11所示，包括下列步骤： Different application service providers may require different QoS to provide the same application service to users based on application service provider policies or customer groups. Assume that both ASP-A and ASP-B provide VOD services, but ASP-A mainly provides VoD services for VIP customers, while ASP-B mainly targets Providing VoD services to customers, that is, when ASP-A provides services to customers, it requires higher QoS guarantees than ASP-B (such as higher QoS priority, greater bandwidth, etc.). Therefore, network operators need to provide different QoS guarantees for VoD services provided by different application service providers. At this time, the PCRF needs to make policy decisions for the VoD service provided by the application service provider according to the configured ASP information and combined with other policy context information. For example, ASP-A provides the user with policy control of the VoD service. The specific process is shown in Figure 11, which includes the following steps:

1 )用户终端和点播服务器 AF之间进行视频点播业务的协商； 1) Negotiating video on demand services between the user terminal and the on-demand server AF;

2 ) 点播服务器 AF将视频点播相关的数据应用业务信息下发给 PCRF; 所述数据应用业务信息包含了点播服务器 AF的地址信息以及点播服务器 AF可支持的带宽范围等； 2) the on-demand server AF sends the video-on-demand data application service information to the PCRF; the data application service information includes the address information of the on-demand server AF and the bandwidth range that the on-demand server AF can support;

3 )根据收到的数据应用业务信息中包含的点播服务器 AF的地址信息， PCRF感知与该数据应用业务信息对应的 ASP配置信息，从而感知该 VoD业务由 ASP— A提供。 PCRF根据数据应用业务信息、 ASP配置信息并结合其他策略上下文信息，为 ASP— A提供的 VoD业务进行策略决策，比如为 ASP— A提供的 VoD的业务分配较高的 QoS优先级和带宽等。 3) According to the received address information of the on-demand server AF included in the service information, the PCRF senses the ASP configuration information corresponding to the data application service information, so that the VoD service is perceived by the ASP-A. Based on the data application service information, the ASP configuration information, and the other policy context information, the PCRF makes policy decisions for the VoD service provided by the ASP-A, for example, assigns a higher QoS priority and bandwidth to the VoD service provided by the ASP-A.

4 ) PCRF将制定的策略下发给 PCEF执行； 4) The PCRF sends the formulated policy to the PCEF for execution;

6 ) PCRF向点播服务器 AF返回确认消息； 6) The PCRF returns a confirmation message to the on-demand server AF;

7 )用户终端开始体验 VoD业务。 7) The user terminal begins to experience the VoD service.

综上所述，本发明实施例中 PCRF接收非 IMS中的数据应用 AF发来的数据应用业务信息；以及 PCRF根据所述数据应用业务信息进行策略决策。从而实现了 PCC对非 IMS数据应用业务的策略控制，有利于增进用户对非 IMS数据应用的体验、提升网络资源的利用率。此外扩大了 PCC的使用范围，使得 PCC不仅可以使用 IMS场景的策略控制，而且也使得 PCC在非 IMS场景下的策略控制变为可行。通过本发明实施例，网络可以实现对诸如视频点播、网络游戏、电子表单、数据会议、电子商务、网络银行、电子证券等非 IMS中的数据应用业务的策略控制。 In summary, in the embodiment of the present invention, the PCRF receives the data in the non-IMS and applies the data application service information sent by the AF; and the PCRF performs the policy decision according to the data application service information. Therefore, the PCC's policy control for non-IMS data application services is realized, which is beneficial to improving the user experience of non-IMS data applications and improving the utilization of network resources. In addition, the scope of use of the PCC is expanded, so that the PCC can not only use the policy control of the IMS scenario, but also make the policy control of the PCC in the non-IMS scenario feasible. Through embodiments of the present invention, the network can implement policy control of data application services in non-IMS such as video on demand, online games, electronic forms, data conferencing, e-commerce, online banking, electronic securities, and the like.

进一步，由于在会话过程中，非 IMS中的数据应用 AF将动态更改的数据应用业务信息及时下发给 PCRF, 以制订 PCC规则控制业务数据流，显然增加了对会话在承载层控制的灵活性，有助于更好的规划有限的网络资源，同时保证为用户提供高质量的服务。 Further, since the data application service information of the non-IMS is sent to the PCRF in time for the PCC rule to control the service data flow, the data application in the non-IMS is obviously increased. The flexibility of controlling the session at the bearer layer helps to better plan for limited network resources while ensuring high quality services for users.

进一步，由于现有 PCC架构定义 Rx接口下发的应用业务信息包含的业务流信息是根据 IMS应用下的 SDP协商形式导出，即用于描述业务流信息的 Media-Component-Description AVP参数值导出需要依赖于 IMS应用下的 SDP协商形式。而在非 IMS数据应用场景中，如网络游戏应用中往往使用网络游戏终端和网络游戏应用服务器之间的专用协议实现业务流的确定；或者虽然使用 SDP, 但 SDP并不是用于终端和数据应用服务器之间协商业务流，如在 RTSP 视频点播应用中， SDP主要用于应用服务器向终端说明流媒体的媒体地址和媒体类型，终端和媒体服务器之间的业务流参数是使用 RTSP协议的 SETUP消息进行协商，并不使用 SDP。因此现有技术的 Rx接口描述 IMS应用业务流信息的 Media-Component-Description AVP参数无法使用在非 IMS数据应用场景中。 Further, the service flow information included in the application service information delivered by the Rx interface of the existing PCC architecture is derived according to the SDP negotiation form in the IMS application, that is, the Media-Component-Description AVP parameter value used to describe the service flow information needs to be exported. It depends on the SDP negotiation form under the IMS application. In a non-IMS data application scenario, for example, a network game application often uses a dedicated protocol between the network game terminal and the network game application server to determine the service flow; or although SDP is used, the SDP is not used for the terminal and the data application. The service flow is negotiated between the servers. For example, in an RTSP video on demand application, the SDP is mainly used by the application server to describe the media address and media type of the streaming media to the terminal, and the service flow parameter between the terminal and the media server is a SETUP message using the RTSP protocol. Negotiation does not use SDP. Therefore, the Media-Component-Description AVP parameter describing the IMS application service flow information of the prior art Rx interface cannot be used in the non-IMS data application scenario.

因此本发明实施例中，通过修订 Rx接口定义中的 IMS应用业务流信息单元，非 IMS中的数据应用 AF向 PCRF下发包含数据应用业务流信息的数据应用业务信息（即上述方式一）。这种实现方式在不同的应用领域，选择不同的业务流信息单元属性，从而不但可满足本发明的目的，还可兼顾现有 PCC架构在 IMS中的应用。 Therefore, in the embodiment of the present invention, by modifying the IMS application service flow information unit in the Rx interface definition, the data application AF in the non-IMS sends the data application service information including the data application service flow information to the PCRF (that is, the above manner 1). This implementation selects different service flow information unit attributes in different application fields, and not only satisfies the purpose of the present invention, but also considers the application of the existing PCC architecture in IMS.

本发明实施例中，还可通过在 Rx接口定义中新增数据应用业务流信息单元，非 IMS中的数据应用 AF向 PCRF下发包含数据应用业务流信息的数据应用业务信息（即上述方式二）。这种实现方式在不同的应用领域，选择使用不同的业务流信息单元，从而不但可满足本发明的目的，还可兼顾现有 PCC架构在 IMS中的应用。 In the embodiment of the present invention, the data application service information unit may be added by adding the data in the Rx interface definition, and the data application AF in the non-IMS is used to deliver the data application service information including the data application service flow information to the PCRF. ). This implementation chooses to use different service flow information units in different application fields, which not only satisfies the purpose of the present invention, but also balances the application of the existing PCC architecture in IMS.

进一步，由于 PCC现有机制定义了 AF向 PCRF提供制订策略所需的应用业务信息包括了业务流信息、计费标识、用户 IP地址以及 AF应用标识等信息。如果将 PCC应用于非 IMS数据应用业务或基于现有的 IMS应用业务，针对相同数据应用业务存在可以由不同业务提供商经营的情况，对此类数据应用进行策略控制时， PCRF需要根据不同的业务提供商制订不同的控制策略。例如在电信网络上开展的视频点播业务可以由业务提供商 ASP1或者 ASP2提供，尽管业务提供内容一样，但是 ASP1和 ASP2可能釆取不同的收费策略，比如 ASP1按照内容计费，而 ASP2釆取流量计费的方式，因此 PCRF需要根据不同业务提供商制订不同的控制策略。但下发应用业务信息时，仅提供了 AF应用标识，根据该标识无法区分该业务由哪个业务提供商提供，从而无法为视频点播业务制订控制策略。 Further, the existing mechanism of the PCC defines that the application service information required by the AF to provide a policy for the PCRF includes information such as service flow information, charging identifier, user IP address, and AF application identifier. If the PCC is applied to a non-IMS data application service or based on an existing IMS application service, the same data application service may be operated by different service providers. When the policy is controlled by such a data application, the PCRF needs to be different according to different Service providers develop different control strategies. For example, the video on demand service carried out on the telecommunication network can be provided by the service provider ASP1 or ASP2. Although the service provides the same content, ASP1 and ASP2 may adopt different charging strategies, such as ASP1. Content charging, and ASP2 takes the way of billing fees, so PCRF needs to develop different control strategies according to different service providers. When the application service information is delivered, only the AF application identifier is provided. According to the identifier, it is impossible to distinguish which service provider is provided by the service provider, and thus the control policy cannot be formulated for the video on demand service.

因此本发明实施例中，在下发的数据应用业务信息中携带应用业务提供商标识，从而可针对不同的提供商制订不同的控制策略。 Therefore, in the embodiment of the present invention, the application service provider identifier is carried in the delivered data application service information, so that different control policies can be formulated for different providers.

进一步，由于目前 3GPP规定， PCC架构釆用 Diameter协议进行 Rx接口的信息传递。而对于非 IMS数据应用业务，由于各业务提供商或网络提供商都釆用基于 web的协议传递信息，因此结合网络的实际应用状况，将对 PCC应用于非 IMS数据应用业务实施策略控制带来一定的困难。 Further, due to the current 3GPP regulations, the PCC architecture uses the Diameter protocol to perform information transfer on the Rx interface. For the non-IMS data application service, since each service provider or network provider uses the web-based protocol to transmit information, combined with the actual application status of the network, the PCC application to the non-IMS data application service policy control will be brought to a certain extent. Difficulties.

因此本发明实施例中，提供了通过 HTTP协议下发非 IMS数据应用业务信息的方案，从而满足业务提供商或网络提供商基于 web协议传递信息的需求。 Therefore, in the embodiment of the present invention, a solution for delivering non-IMS data application service information through the HTTP protocol is provided, thereby satisfying the requirement of the service provider or the network provider to transmit information based on the web protocol.

进一步，由于 PCC现有机制定义了 AF向 PCRF提供制订策略所需的应用业务信息包括了业务流信息、计费标识、用户 IP地址以及 AF应用标识等信息。如果将 PCC应用于非 IMS数据应用业务或基于现有的 IMS应用业务，针对相同数据应用业务存在可以由不同业务提供商经营的情况，对此类数据应用进行策略控制时， PCRF需要根据不同的业务提供商制订不同的控制策略。例如在电信网络上开展的视频点播业务可以由业务提供商 ASP1或者 ASP2提供，尽管业务提供内容一样，但是 ASP1和 ASP2可能釆取不同的收费策略，比如 ASP1按照内容计费，而 ASP2釆取流量计费的方式，因此 PCRF需要根据不同业务提供商制订不同的控制策略。但下发应用业务信息时，仅提供了 AF应用标识，根据该标识无法区分该业务由哪个业务提供商提供，从而无法为视频点播业务制订控制策略。 Further, the existing mechanism of the PCC defines that the application information required by the AF to provide a policy for the PCRF includes information such as service flow information, charging identifier, user IP address, and AF application identifier. If the PCC is applied to a non-IMS data application service or based on an existing IMS application service, the same data application service may be operated by different service providers. When the policy is controlled by such a data application, the PCRF needs to be different according to different Service providers develop different control strategies. For example, the video on demand service carried out on the telecommunication network can be provided by the service provider ASP1 or ASP2. Although the service provides the same content, ASP1 and ASP2 may adopt different charging policies, for example, ASP1 charges according to content, and ASP2 captures traffic. The method of billing, so the PCRF needs to formulate different control strategies according to different service providers. When the application service information is delivered, only the AF application identifier is provided. According to the identifier, it is impossible to distinguish which service provider is provided by the service provider, so that the control policy cannot be formulated for the video on demand service.

因此本发明实施例中，在下发的数据应用业务信息中携带应用业务提供商标识，或者在 PCRF上预设应用业务提供商标识以及应用业务提供商标识与数据应用业务信息之间的关联关系，从而可针对不同的提供商制订不同的控制策略。明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。 Therefore, in the embodiment of the present invention, the application service provider identifier is carried in the data application service information that is delivered, or the application service provider identifier and the application service provider identifier and the number are preset on the PCRF. According to the relationship between the application business information, different control strategies can be developed for different providers. The spirit and scope of the Ming. Thus, it is intended that the present invention cover the modifications and modifications of the invention

Claims

权利要求 Rights request

1、一种数据应用的策略控制方法，其特征在于，包括下列步骤：策略控制和计费规则功能实体 PCRF接收非 IMS中的数据应用 AF发来的数据应用业务信息；以及 A method for controlling a data application, comprising the steps of: a policy control and a charging rule function entity; a PCRF receiving a data application service information sent by an AF in a non-IMS; and

PCRF根据所述数据应用业务信息进行策略决策。 The PCRF makes policy decisions based on the data application service information.

2、如权利要求 1所述的方法，其特征在于，通过修订 Rx接口定义中的 IMS应用业务流信息单元，所述非 IMS中的数据应用 AF向 PCRF下发数据应用业务信息所包含的数据应用业务流信息。 The method of claim 1, wherein the IMS application service flow information unit in the Rx interface definition is modified, and the data application AF in the non-IMS delivers data included in the data application service information to the PCRF. Apply business flow information.

3、如权利要求 1所述的方法，其特征在于，通过在 Rx接口定义中新增数据应用业务流信息单元，所述非 IMS中的数据应用 AF向 PCRF下发数据应用业务信息所包含的数据应用业务流信息。 The method of claim 1, wherein the data application service information unit is added to the Rx interface definition, and the data application AF in the non-IMS is sent to the PCRF to include the data application service information. Data application business flow information.

4、如权利要求 1所述的方法，其特征在于，通过 HTTP协议，所述非 IMS 中的数据应用 AF向 PCRF下发数据应用业务信息。 The method according to claim 1, wherein the data application AF in the non-IMS sends the data application service information to the PCRF through the HTTP protocol.

5、如权利要求 4所述的方法，其特征在于，所述数据应用业务信息以 XML 描述。 5. The method of claim 4 wherein the data application service information is described in XML.

6、如权利要求 1至 5任一项所述的方法，其特征在于，所述数据应用业务信息包括：应用业务提供商信息。 The method according to any one of claims 1 to 5, wherein the data application service information comprises: application service provider information.

7、如权利要求 1 所述的方法，其特征在于， PCRF根据所述数据应用业务信息决策得出的策略包括：指示策略和计费执行功能实体 PCEF执行相应应用业务流的 QoS、计费和 /或门控的控制策略。 The method according to claim 1, wherein the policy determined by the PCRF according to the data application service information comprises: indicating that the policy and the charging execution function entity PCEF perform QoS, charging, and accounting of the corresponding application service flow. / or gated control strategy.

8、一种非 IMS中的数据应用功能实体，其特征在于，包括： 8. A non-IMS data application functional entity, comprising:

触发单元，用于接收触发事件； a trigger unit, configured to receive a trigger event;

下发单元，用于在触发单元收到触发事件时，下发相应的数据应用业务信息。 The sending unit is configured to send corresponding data application service information when the trigger unit receives the trigger event.

9、如权利要求 8 所述的实体，其特征在于，所述下发单元通过修订 Rx 接口定义中的 IMS应用业务流信息单元，下发数据应用业务信息所包含的数据应用业务流信息。 The entity according to claim 8, wherein the sending unit sends the data application service flow information included in the data application service information by modifying the IMS application service flow information unit in the Rx interface definition.

10、如权利要求 8所述的实体，其特征在于，所述下发单元通过在 Rx接口定义中新增数据应用业务流信息单元，下发数据应用业务信息所包含的数据应用业务流信息。 The entity according to claim 8, wherein the sending unit adds the data application service flow information unit in the Rx interface definition, and delivers the data included in the data application service information. Apply business flow information.

11、如权利要求 8所述的实体，其特征在于，所述下发单元通过 HTTP协议下发数据应用业务信息。 The entity according to claim 8, wherein the sending unit delivers data application service information through an HTTP protocol.

12、一种策略控制和计费规则功能实体，其特征在于，包括： 12. A policy control and charging rule function entity, comprising:

接收单元，用于接收数据应用业务信息； a receiving unit, configured to receive data application service information;

决策单元，用于根据接收单元收到的数据应用业务信息进行策略决策。 The decision unit is configured to apply the service information according to the data received by the receiving unit to make a policy decision.

13、如权利要求 12所述的实体，其特征在于，所述接收单元通过修订 Rx 接口定义中的 IMS应用业务流信息单元，接收数据应用业务信息所包含的数据应用业务流信息。 The entity according to claim 12, wherein the receiving unit receives the data application service flow information included in the data application service information by modifying an IMS application service flow information element in the Rx interface definition.

14、如权利要求 12 所述的实体，其特征在于，所述接收单元通过在 Rx 接口定义中新增数据应用业务流信息单元，接收数据应用业务信息所包含的数据应用业务流信息。 The entity according to claim 12, wherein the receiving unit receives the data application service flow information included in the data application service information by adding a data application service flow information unit to the Rx interface definition.

15、如权利要求 12所述的实体，其特征在于，所述接收单元通过 HTTP 协议接收数据应用业务信息。 The entity according to claim 12, wherein the receiving unit receives data application service information through an HTTP protocol.

16、一种非 IMS数据应用的策略控制***，其特征在于，包括：非 IMS中的数据应用 AF, 用于下发数据应用业务信息； A policy control system for non-IMS data application, comprising: a data application AF in a non-IMS, for transmitting data application service information;

17、如权利要求 16所述的***，其特征在于， PCRF与数据应用 AF之间通过修订 Rx接口定义中的 IMS应用业务流信息单元，收发数据应用业务信息所包含的数据应用业务流信息。 The system of claim 16, wherein the PCRF and the data application AF modify the RIMS interface definition in the IMS application service flow information unit to send and receive data application service information included in the data application service information.

18、如权利要求 16所述的***，其特征在于， PCRF与数据应用 AF之间通过在 Rx接口定义中新增数据应用业务流信息单元，收发数据应用业务信息所包含的数据应用业务流信息。 The system according to claim 16, wherein the data application service flow information included in the data application service information is sent and received between the PCRF and the data application AF by adding a data application service flow information unit in the Rx interface definition. .

19、如权利要求 16所述的***，其特征在于， PCRF与数据应用 AF之间通过 HTTP协议收发数据应用业务信息。 The system according to claim 16, wherein the PCRF and the data application AF send and receive data application service information through the HTTP protocol.

20、一种应用的策略控制方法，其特征在于，包括下列步骤： 20. An applied policy control method, comprising the steps of:

PCRF获取应用业务提供商标识； The PCRF obtains an application service provider identifier;

PCRF根据所述应用业务提供商标识进行策略决策。 The PCRF makes policy decisions based on the application service provider identity.

21、如权利要求 20所述的方法，其特征在于，所述 PCRF获取应用业务提供商标识的方式为： PCRF根据应用功能实体 AF发来的应用业务信息获取应用业务提供商标识。 The method of claim 20, wherein the PCRF obtains the application service provider identifier by: the PCRF obtains the application service provider identifier according to the application service information sent by the application function entity AF.

22、如权利要求 20或 21所述的方法，其特征在于， PCRF根据所述应用业务提供商标识进行策略决策得出的策略包括：指示 PCEF执行相应应用业务流的 QoS、计费和 /或门控的控制策略。 The method according to claim 20 or 21, wherein the policy that the PCRF makes a policy decision according to the application service provider identifier comprises: instructing the PCEF to perform QoS, charging, and/or execution of the corresponding application service flow. Gated control strategy.

23、一种策略控制和计费规则功能实体，其特征在于，包括： 23. A policy control and charging rule function entity, comprising:

获取单元，用于获取应用业务提供商标识； An obtaining unit, configured to obtain an application service provider identifier;

决策单元，用于根据获取单元获取的所述应用业务提供商标识进行策略决來。 And a decision unit, configured to perform a policy decision according to the application service provider identifier acquired by the obtaining unit.

24、如权利要求 23所述的实体，其特征在于，所述获取单元中包括：第一获取子单元，用于根据应用功能实体 AF发来的应用业务信息获取应用业务提供商标识。 The entity according to claim 23, wherein the acquiring unit comprises: a first acquiring subunit, configured to acquire an application service provider identifier according to application service information sent by the application function entity AF.