WO2009067918A1

WO2009067918A1 - Method, system and functional entity of pfo for application event detection

Info

Publication number: WO2009067918A1
Application number: PCT/CN2008/073002
Authority: WO
Inventors: Shibi Huang; Yu Zuo; Peng Zhao; Fengbo Wang; Yuxin Mao
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-11-28
Filing date: 2008-11-11
Publication date: 2009-06-04
Also published as: CN101453380B; CN101453380A

Abstract

An application event detecting method is provided, comprising the steps that the PFO acquires the application range information of the application event detection rules and the PFO performs corresponding application event detection according to the application range information of the application event detection rules. A system and a functional entity of PFO for application event detection are also provided. By means of designating application range of the application event detection rules, configuring the application event detection rules applied to multiple users, and using the same application event detection rules in the range, it can beachieved that users with the same policy requirements can share application event detection rules, so that the control can be simplified, the control efficiency can be improved and the complexity for detection management and maintenance can be reduced.

Description

Method, system and packet stream optimization function entity for applying event detection This application claims to be filed on November 28, 2007, the Chinese Patent Office, the application number is 200710031760.9, and the invention name is "application event detection method, system and packet stream optimization function entity" The priority of the Chinese Patent Application, the entire contents of which is incorporated herein by reference. Technical field

The present invention relates to the field of communications, and in particular, to a method, system, and packet stream optimization function entity for applying event detection. Background technique

The 3rd Generation Mobile Communications Standardization Partnership Project (3GPP) defines the Policy and Charging Control (PCC) architecture to meet different Quality of Service (QoS) control and billing requirements for different services. . The PCC framework is a functional framework that can be applied to multiple access technologies. Some typical access technologies include Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), GSM/EDGE Radio Access Network (GERAN). And I-WLAN (Interworking WLAN, interworking WLAN (specifically refers to interworking with 3GPP systems)). With the development of the network and the enrichment of services, more functions are implemented on the PCC architecture, such as: Packet Flow Optimization (PFO)

The PFO function is to filter the IP flow under the control of the policy. The policy rule specifies which application the PFO should detect and how to handle it after detecting the application. There are two architectures in the specific implementation, one is a separate architecture, that is, the PFO function is an independent bearer layer functional entity, which is separated from the gateway (GW); the other is a unified architecture, that is, the policy and charging execution function. The Policy and Charging Enforcement Function (PCEF) and PFO functions coexist on the Gateway (GW) entity. Policy and Charging Rules, regardless of the PFO architecture Functions, PCRF) can activate the detection of application events based on the capabilities of the PFO. When the application event detection is activated, the PCRF needs to give the following application event detection indication information: the identification information of the activated detection application, such as a BT application, an FTP application, an RTSP streaming video on demand application, a network game, etc.; The detection rules of the application event include application events of the activated detection, such as application startup, application termination, application change, etc., and may also give some restrictions to match the detection of the activated application, such as application filtering rules. The application event detection rule can be pre-configured on the PFO function. The PCRF can only carry the application identification information to indicate which rule needs to be activated when the application event detection is activated. Of course, the detection rule of the application event can also be activated by the PCRF. The indication of the event detection is sent to the PFO for execution. The problem is that the existing application event detection activation mechanism is only for the user, that is, if it is required to perform the same application event detection for multiple users, the PCRF needs to separately activate the application event detection for each user. In practical applications, there is a need to capture the same application event detection rules for multiple users. For example: The telecom operator prohibits all users from using Skype and BT downloads using P2P technology. When the PFO function detects that any user is conducting the service, it needs to adopt the same policy to deny the user to carry out the service. Another example: Many users釆Experience the IPTV video on demand service (VOD) by paying monthly subscription fees.

When the PFO detects that such a user performs a video on demand service, it can obtain the same charging policy or QoS control policy for the service. The policy can be obtained through local configuration or request to the PCRF. For these scenarios, the existing active application event detection mechanism cannot meet the requirements of these users to share application event detection rules when performing business. The existing mechanism only implements independent application event detection rules for each user. If the existing mechanism is used to meet the above application requirements, the efficiency of subscribing/activating application event detection is low, maintenance and management are complicated. The same application event detection rule cannot be met for the needs of multiple users. Summary of the invention

The technical problem to be solved by the embodiment of the present invention is to provide a method and system for applying event detection. And the packet flow optimization function entity, in order to conduct business for multiple users, the same application event detection rule is used to easily and efficiently detect application events. To solve the above technical problem, an embodiment of the present invention provides a method for applying event detection, including the following steps: The packet flow optimization function entity PFO acquires application range information of an application event detection rule;

The PFO applies the application event detection rule to perform application event detection according to the application scope information of the application event detection rule in the corresponding application scope. The embodiment of the present invention further provides a system for applying event detection, including: a policy control and charging control function entity PCRF, configured to deliver activation or installation indication information directed to at least one application event detection rule; and a packet flow optimization function entity The PFO is configured to obtain the application scope information of the application event detection rule, and apply the detection rule to perform the application event detection within the application scope of the application event detection rule when the activation or installation indication information is received. An embodiment of the present invention further provides a packet flow optimization function entity, including:

An acquiring unit, configured to acquire an application event detection rule, and application scope information of the application event detection rule; and an execution unit, configured to use, according to the application scope detection information of the application event detection rule acquired by the acquiring unit, The detection rule is applied within the application range of the application event detection rule. The embodiments of the present invention have the following beneficial effects: By specifying the application scope of the application event detection rule, setting an application event detection rule applied to multiple users, using the same application event detection rule within the range, so that the policy requirements are the same. Users can share application event detection rules to simplify control, improve control efficiency, and reduce detection management and maintenance complexity. DRAWINGS

1 is a schematic structural diagram of a PCC architecture defined in TS 23.203; 2 is a schematic flowchart of a method for specifying an application scope of an application event detection rule according to an embodiment of the present invention; FIG. 3 is a schematic flowchart of performing PFO control on a user service by using a network system level application event detection rule according to an embodiment of the present invention;

FIG. 5 is a schematic flowchart of PFO control of an application by using a user group level application event detection rule according to an embodiment of the present invention;

6 is a schematic flow chart of applying event detection rules predefined on a PFO and setting an application range of the application event detection rule to perform application event detection control according to an embodiment of the present invention. detailed description

The embodiments of the present invention are described in detail below with reference to the accompanying drawings. Referring to Figure 1, the PCC architecture defined in TS 23.203 is illustrated. The PCC framework mainly implements two major functions, one is a policy control function, and the other is a charging function. The policy control function mainly includes: monitoring a service parameter (mainly a QoS parameter) negotiation process of the user; authorizing the network bearer resource used by the service according to the obtained service information; controlling the service flow in real time on the data bearer plane Passing or not; notifying the relevant changes of the business plane to the data bearer surface; notifying the relevant changes of the data bearer surface to the business plane, etc.; performing policy control based on the user subscription information. In the PCC framework, the main entities involved in the policy control function include Application Function (AF), PCRF, PCEF, and Subscription Profile Repository (SPR). The charging function mainly includes: comprehensive service information, bearer information, and user subscription information, and formulating charging rules; association between charging data on the service side and charging data on the carrying surface; in the dynamic charging mode, performing credit control. In the PCC framework, the entities involved in the billing function include AF, PCRF, PCEF, SPR, Online Charging System (OCS), and Offline Charging System (OFCS).

The functions of some entities in the PCC architecture shown in Figure 1 are described as follows:

AF: Application functional entity. The application layer session information is dynamically provided for the PCRF policy and charging control. For example, the P-CSCF in the IP Multimedia Subsystem (IMS) belongs to the AF.

PCRF: Policy Control and Charging Control Function Entity. Based on the restrictions of the user accessing the network, the application service information currently being performed by the user, the local carrier configuration, and the user subscription information, the corresponding policies are formulated and the policies are provided to the PCEF for execution. Policies include: traffic data flow detection, QoS control, gating, and flow-based charging.

PCEF: Policy and Charging Enforcement Entity. The policy that is delivered or specified by the PCRF performs the functions of detecting the service data flow, ensuring the QoS of the service data flow, gate control, completing the online/offline charging, and triggering the session with the control plane. For example: GPRS Gateway Support Node (GGSN) entity in General Packet Radio Service (GPRS).

Some of the interface functions in the PCC architecture shown in Figure 1 are described as follows:

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: 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 Session (IP-CAN SESSION); 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 (a new generation (authentication, authorization, charging) technology, an interface between entities in the IP multimedia domain of the 3G network). In data transmission of a network, a service data stream is composed of multiple IP packets including a quintuple (source address, source port number, destination address, destination port number, protocol). The user-developed service can be composed of multiple service data streams. For example, when a user conducts a multimedia call, one video stream is a service data stream.

In the defined PCC policy control architecture, the PCRF needs to formulate a corresponding policy for the service based on the policy context information obtained from each functional entity (AF/PCEF/SPR, etc.) and deliver it to the PCEF on the bearer layer entity to implement Policy control of QoS, gating, and accounting for services.

However, with the development of the network and the richness of services, more functions are implemented on the PCC architecture. Packet Flow Optimization (PFO) is one of them. The PFO function is to filter the IP flow under the control of the policy. The policy rule specifies which application the PFO should detect and how to process it after detecting the application.

Referring to FIG. 2, an embodiment of the present invention specifies a method for applying an application scope of an event detection rule, including the following steps:

Step 1: The packet flow optimization function entity PFO obtains the application scope information of the application event detection rule. Step 2: The PFO applies the application event detection rule to apply the event detection according to the application scope information of the application event detection rule in the corresponding application scope.

Specifically, the application scope information of the application event detection rule is used to indicate that the application event detection rule is applied to multiple users. The multiple users may refer to users within a user group, and may also refer to network system users. If the application scope information of the application event detection rule is applied to the user group, perform the same application event detection rule for all users in the user group; if the application scope information of the application event detection rule indicates that the application scope information is applied to the network system , implement the same application event detection rules for all users who use the bearer layer functional entity. Further, the application event detection rule includes: the detected application event, the filtering rule of the detection application, and the like. Dynamic PCC rules and pre-defined are included in the 3GPP defined Policy and Charging Control (PCC) architecture

PCC rules. The dynamic PCC rule is generated by the PCRF according to the application service information, the user subscription information, the operator policy, or other policy context information when the trigger information is sent by the PCRF, and includes the quintuple, QoS, and gating of the service data flow. Rule content such as billing, the dynamic PCC rule is uniquely identified by the rule name. The rules are sent to the PCEF for execution by the PCRF. The predefined PCC rules are pre-configured on the PCEF, and the corresponding rule name is saved on the PCRF. When the PCRF receives the trigger information of the rule activation,

The PCRF sends an activation command containing the rule name to the PCEF, instructing the PCEF to activate the predefined PCC rule.

Based on the PCC architecture, the PFO obtains one of the following methods for applying the event detection rule application range information:

Method 1: Pre-defined application event detection rules on the PFO.

The application event detection rule is first defined on the PFO, but the application scope of the predefined rule is not set. After the triggering information of the application event detection is sent by the PCRF, the PCRF sends the indication information for activating the predefined application event detection rule to the PCEF, that is, the identification information of the activated detection application and the application range indication of the predefined application event detection rule. The information of the activation detection application is used by the PFO to identify a predefined application event detection rule of the application, and the application scope indication information of the predefined application event detection rule is used to specify a predefined application event detection rule application. The user group is still applied to the network system. An example is as follows:

App-Event- Activate: := < AVP Header: χ χ χ >

{ Αρρ- Identifier AVP } [ Detect-Regulate-Info ]

Detect-Regulate-Info ::= < AVP Header: χ χ χ >

[ Usergroup-Requirement ] [ System-Requirement ] The APP-Event-Activate AVP indicates that the detection of an application event is activated. To activate and detect multiple applications, multiple APP-Event-Activate AVPs can be used. App-Identifier AVP indicates the identification information of the activated detection application, such as BT application, FTP application, and so on.

Detect-Regulate-Info AVP indicates the application event detection range indication information, Grouped type. If the Detect-Regulate-Info AVP is not included in the APP-Event-Activate AVP, the application event detection rule is applied to a single user.

User-group-Requirement AVP indicates that the application event detection rule is applied to the user group, OctetString. The value of the AVP can be the user group ID or the address list of all or some users under the user group.

System-Requirement AVP indicates that application event detection rules are applied to the network system.

OctetString type.

Method 2: Use dynamic application event detection rules.

When the PCRF receives the trigger information of the application event detection rule, the PCRF generates a dynamic application event detection rule to be sent to the PFO according to the operator policy, the user subscription information, and/or other context information, and the application event detection rule is further The application scope indication information of the rule is sent to indicate the application scope of the application event detection rule. An example of this is similar to the description of the example in the first mode.

App-Event- Activate: := < AVP Header: χ χ χ >

{ Αρρ- Identifier AVP }

[ Detect-Regulate-Info ]

[Αρρ- Filter-Rule]

The App-Filter-Rule AVP is used to indicate the application event detection rule.

Method 3: Use predefined application event detection rules, and set the application scope of the application event detection rule. First, an application event detection rule is predefined on the PFO, and application scope information of the predefined application event detection rule is set. The PCRF then sends an indication to the PFO to activate the predefined application event detection rule, where the indication information includes an identifier of the activation detection application, and is only used to activate a specific application event detection rule. Since the application scope of the application event detection has been set, when the application event detection rule is activated, the application range of the application event detection rule is also limited.

Its example 3⁄4 mouth:

App-Event- Activate ::= < AVP Header: χ χ χ >

{ Αρρ- Identifier AVP } In the above three manners, if the application scope information indication of the application event detection rule is applied to a user group, the application event detection rule is applied to datagrams of all or a part of users in the user group. If the information indicating the application scope of the control policy is applied to the network system, the application event detection rule is applied to the data packets of all users in the network system.

The specific corresponding mode 1: The PFO needs to apply the predefined application event detection rule activation to the corresponding data packet according to the application scope information of the application event detection rule.

The specific corresponding mode 2: The PFO needs to install and apply the dynamic application event detection rule to the corresponding data packet according to the application scope information of the application event detection rule.

Specific Correspondence 3: The PFO needs to apply the predefined application event detection rule activation to the data packet within the application scope set for the predefined application event detection rule. The embodiment of the present invention further provides a system for specifying an application scope of an application event detection rule, including: a policy control and charging control function entity PCRF, configured to deliver activation or installation indication information directed to at least one application event detection rule;

The packet flow optimization function entity PFO is configured to acquire information about the application event detection rule, and apply the detection rule to apply the event detection within the application scope of the application event detection rule when the activation or installation indication information is received. . The embodiment of the present invention further provides a packet flow optimization function entity, including: an obtaining unit, configured to acquire an application event detection rule, and application scope information of the application event detection rule; and an execution unit, configured to be used according to the acquiring unit The obtained application scope information of the application event detection rule is obtained, and the detection rule is applied within the application scope of the application event detection rule. The obtaining unit obtains the application range information of the application event detection rule by using one of the following methods:

The first application of the predefined application event detection rule is obtained by the PFO, and the PFO obtains the application scope information of the predefined application event detection rule from the received indication information of the application scope of the predefined application event detection rule.

In the second mode, the PFO receives the application scope indication information sent by the application event detection rule, and the PFO obtains the application scope information of the application event detection rule from the indication information.

Method 3: Pre-define the application event detection rule on the PFO, and set the application scope information of the application event detection rule.

The following is further described by four embodiments.

Embodiment 1: Implementing policy control by using a network system level strategy. For some restricted applications specified by the network operator, the PCC uses the same application event detection rules for all network users and draws the same policy. In this embodiment, the PCEF and the PFO are combined to configure a filtering rule for the network system level application event for all users using the functional entity on the PFO functional entity, where the filtering rule includes the restricted data packet. Related information (such as IP quintuple), and configure the corresponding control strategy at the same time. After the PCRF activates the application event detection rule of the network system level, once any user performs the limited application, and the data packet of the restricted application passes the PFO function, the network system level application event detection rule detects the If the data packet matches the filtering rule, the "closed" gating policy can be directly retrieved, and the user is prohibited from accessing. This application event detection mechanism obviously simplifies the complexity and avoids the independent generation of application event detection rules for each user. The rate of decline. The process of PFO control of user services using network system level application event detection rules, as shown in Figure 3, includes the following steps:

S201. Configure, on the PFO functional entity, a filtering rule for a network system level application event for all users that use the functional entity, where the filtering rule includes information about the restricted data packet (such as an IP quintuple), and configures the corresponding Control strategy.

5202. The triggering of the event by the PCRF requires activation of the detection of the application event.

5203. The PCRF sends an instruction to activate the application event detection to the PFO functional entity.

The PCRF sends the identification information of the application event (such as the SKYPE application) to the PFO function entity, and indicates that the application event detection filtering rule and the related control policy of the specified application are activated; and the application event detection range is included. The indication information indicates that the rule is applicable to the network system level; the form of the application event detection indication information and the application event detection range indication information is as follows:

APP-EVENT- ACTIVATE:: = < AVP Header: χ χ χ >

{APP- Identifier AVP}

[Detect-Regulate-Info]

[System-Requirement] The APP-Identifier AVP is used to indicate the application identifier that needs to be activated. The Detect-Regulate-Info AVP contains the System-Requirement AVP to indicate that the filtering rule of the specified application to be activated is applied to the network system. All users in the system can share the same filtering rules;

S204. The PFO functional entity activates the corresponding network within the network system according to the obtained application identifier. Filter rules and corresponding control strategies.

S205. The PFO function entity detects whether the type of the data packet of the service carried by the user matches the filtering rule of the network system level.

If the type of the data packet is consistent with the filtering rule of the network system level, step S206 is performed, that is, the PFO function performs a "closed" gate on the detected data packet that matches the filtering rule according to the pre-configured corresponding control policy. The control policy does not allow the data packet to pass. The data packet that is detected does not match the filtering rule is allowed to pass.

For example, the user carries out the restricted SKYPE service, and the data message is transmitted to the PFO functional entity, the SKYPE data packet is consistent with the network system level filtering rule, and the PFO function performs the detected SKYPE data packet according to the corresponding control policy. The "closed" gating policy does not allow the data message to pass. Embodiment 2: Implementing PFO control by using user group-level application event detection rules (the user group is represented by the user group identifier) In this embodiment, using the architecture of PCEF and PFO, the filtering rules of each application event are configured on the PFO and User group information, the PCRF activates the user group-level application event detection to the PFO. After detecting the application, the PFO dynamically requests an accounting policy from the PCRF. The PCRF generates a policy rule according to the operator's policy and sends the policy to the PCEF. The policy rule charges the detected traffic data stream.

Many users listen to the IPTV video on demand service (VOD) in a monthly subscription manner. The PCC architecture can use the same application event detection rule to detect the VOD services carried out by these monthly subscription users, thereby using the same charging strategy. Taking the VOD application as an example, the process of applying event detection control to the user service by using the user group-level application detection rule, as shown in FIG. 4, includes the following steps:

S301. Configure an identifier of the application to be detected and a corresponding application event detection on the PFO functional entity. Filter the rules, and configure the user group ID and the user group member list information represented by the user group ID.

5302. The triggering of the event by the PCRF requires activation of the detection of the application event.

5303. The PCRF sends an instruction to activate the application event detection to the PFO function.

The PCRF sends the identification information of the application event (VOD application) to be detected to the PFO by using the Diameter message to indicate the filtering rule applied to activate the VOD. The indication information including the application event detection range indicates that the rule is applicable to the user group level. The form of the application event detection indication information and the application event detection range indication information is as follows:

APP-EVENT- ACTIVATE := < AVP Header: χ χ χ >

{APP-IdentifierAVP}

[ Detect-Regulate-Info ]

[Usergroup-Requirement] The APP-Identifier AVP is used to indicate the application identifier that needs to be activated for detection. It can also include other AVPs to indicate the detected application events (such as application termination). Detect-Regulate-Info AVP contains the Usergroup-Requirement AVP for The application event detection rule that is sent to the user group is applied to the user group. The user group ID (12345678) indicates that the same detection rule is implemented for all users in the user group.

S304: The PFO functional entity activates the application group-level application detection filtering rule according to the obtained application identifier and the user group identifier.

The user views the VOD service, and the data message is transmitted to the PFO function entity. The PFO function entity detects that the user is in the user group, and the VOD data packet matches the application-level application event filtering rule of the user level; 5305. The PFO functional entity detects a data packet that meets a user-level application filtering rule.

5306. The PFO function entity reports to the PCRF a data packet that is detected to meet the application-level application filtering rule.

5307. The PCRF generates a new policy rule for the detected application according to the policy context.

S308 and PCRF issue PCC rules to PCEF;

S309. The PCEF executes a new policy rule for the application that meets the filtering rule.

Embodiment 3: Implementing policy control by using user group-level policies (user groups are represented by user lists) Operators can divide users of the same level into one user group, and implement the same QoS control policy for all users in the user group. .

In this embodiment, the PCEF is separated from the PFO, and the PFO is used as an independent functional entity. The PCRF activates the user group-level application event detection to the PFO, and the PFO detects the related application according to the application event detection filtering rule delivered by the PCRF. The QoS policy is dynamically requested from the PCRF. The PCRF generates a policy rule according to the policy of the operator and sends it to the PCEF. The PCEF performs QoS control on the detected application according to the policy rule. Taking the online game application as an example, the process of performing PFO control corresponding to the user group-level application event detection rule, as shown in FIG. 5, includes the following steps:

S401. The PCRF is triggered by an event to activate the detection of an application event.

S402. The PCRF sends a detection instruction for activating an application event to the PFO functional entity.

The PCRF sends the application event information (including the application identification information (the network game application) and the application filter rule information (such as the IP quintuple)) to the PFO function, indicating that the activation detection network game application is activated; An indication of the scope of the application event detection indicates that the rule applies to the user group level. The form of the application event detection indication information and the application event detection range indication information is as follows:

APP-EVENT- ACTIVATE:: = < AVP Header: χ χ χ > {APP-IdentifierAVP}

[APP-Filter-Rule]

[ Detect-Regulate-Info ]

[Usergroup-Requirement] where the APP-Identifier AVP is used to indicate the application ID that needs to be activated for detection, and the APP-Filter-Rule AVP is used to detect the application's filtering rules. The Detect-Regulate-Info AVP contains the Usergroup-Requirement AVP to indicate the delivery. The application event detection rules are applied to the user group, and the user list (for example: ABCD, abcd, ...) indicates that the same detection rule is implemented for all users in the user group.

5403. The PFO functional entity performs application group level application event detection according to the application identifier obtained from the PCRF, the applied filtering rule, and the user group member information.

The user launches the online game application, and the data message is transmitted to the PFO functional entity. The PFO functional entity detects that the user is in the user group, and the data message matches the user-level filtering rule.

5404. The PFO detects a data packet that meets a user-level filtering rule.

5405. The PFO reports to the PCRF a data packet that is detected to meet the user-level filtering rule.

5406. The PCRF generates a new policy rule for the detected application according to the policy context.

S407 and PCRF issue PCC rules to PCEF.

S408. The PCEF executes a new policy rule for the application that meets the filtering rule.

Embodiment 4: The application event detection rule is predefined on the PFO, and the application scope of the application event detection rule is set; the application event detection rule includes a predefined application applied to the user group. Event detection rules and application event detection rules applied to the network system (that is, various application event detection rules and application scope of each application event detection rule are predefined on the PFO); the PCRF issues an instruction to the PFO functional entity to activate the application event. Detection rules; PFO functional entities execute the corresponding application event detection rules. The specific implementation process of the program is shown in Figure 6:

5501. Configure a predefined application event detection rule applied to the multi-user on the PFO functional entity, including a user group level predefined application event detection rule and a network system level predefined application event detection rule. These two predefined application event detection rules are identified by different rule names and have a rule name stored in the PCRF.

5502. The PCRF is triggered by an event to activate an application event detection to the PFO.

5503. The predefined application event detection rule name to be activated is included in the issuing instruction, and is sent to the PFO function entity by using a Diameter message.

5504. The PFO function entity uses the predefined application event detection rule to detect the application event according to the rule name included in the issued instruction.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by hardware, or can be implemented by means of software plus necessary general hardware platform, and the technical solution of the present invention. It may be embodied in the form of a software product, which may be stored in a computer readable storage medium (which may be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), including a number of instructions for making a computer device (may be A personal computer, server, or network device, etc., performs the methods described in various embodiments of the present invention.

In summary, the embodiment of the present invention sets an application event detection rule applied to multiple users by specifying an application scope of an application event detection rule, and uses the same application event detection rule in the application scope, so that the policy requirements are the same. Users can share application event detection rules to simplify control, improve control efficiency, and reduce detection management and maintenance complexity.

The spirit and scope of the Ming. Thus, if such modifications and variations of the present invention are within the scope of the present invention The present invention is also intended to cover such modifications and variations within the scope of the equivalents.

Claims

Rights request

1. A method for applying event detection, comprising the following steps:

The packet flow optimization function entity PFO acquires the application scope information of the application event detection rule; and the PFO applies the application event detection rule within the application scope determined by the application scope information according to the application scope information of the application event detection rule. Perform application event detection.

2. The method according to claim 1, wherein: the application scope information of the PFO to acquire an application event detection rule comprises:

Pre-defining an application event detection rule on the PFO, and receiving application scope indication information of the predefined application detection rule;

The PFO obtains application range information of the predefined application event detection rule from the application range indication information.

3. The method according to claim 1, wherein: the application scope information of the PFO to acquire an application event detection rule comprises:

The PFO receives an application event detection rule and an application range indication information of the application event detection rule;

The PFO obtains application range information of the application event detection rule from the application range indication information of the application event detection rule.

4. The method according to claim 1, wherein: the application scope information of the PFO to acquire an application event detection rule comprises:

Predefined application event detection rules on the PFO;

The application scope information of the application event detection rule is set on the PFO.

The method of claim 2, wherein: the applying, by the PFO, the detection rule in the application scope determined by the application scope information refers to: the PFO in the predefined application event detection rule The detection rule is activated within the scope of the application.

6. The method of claim 3, wherein: said PFO is in said application range information Applying the detection rule within the determined application scope means: the PFO installs the application event detection rule.

The method according to claim 2 or 3, wherein: the application range indication information of the application event detection rule is sent by the policy control and charging control function entity PCRF to the PFO.

The method according to claim 1, wherein: the application scope information of the application event detection rule is used to indicate that the application event detection rule is applied to multiple users, and the multiple users refer to all users in the user group or Part of the user, or all users within the network system to which the PFO belongs.

9. The method according to claim 1, wherein: the PFO is set on a gateway device or as a separate bearer layer functional entity.

10. The method according to claim 8, wherein: if the application scope information of the application event detection rule indicates that the application event detection rule is applied to a user group, the PFO implements the same for all users in the user group. Application event detection rules.

11. The method according to claim 8, wherein: if the application scope information of the application event detection rule indicates that the application event detection rule is applied to a network system, the PFO implements the same for all users using the PFO. Application event detection rules.

The method according to claim 8, wherein: the application event detection rule comprises: a detected application event, a filtering rule of the detection application, or a restriction condition of the detection application.

A system for detecting event detection, comprising: a policy control and charging control function entity, configured to deliver activation or installation indication information directed to at least one application event detection rule;

a packet flow optimization function entity, configured to acquire application scope information of an application event detection rule, and apply the detection rule to apply an application event within an application scope of the application event detection rule when the activation or installation indication information is received Detection.

14. A packet flow optimization function entity, comprising: An acquiring unit, configured to acquire an application event detection rule, and application scope information of the application event detection rule; and an execution unit, configured to use, according to the application scope information of the application event detection rule acquired by the acquiring unit, The detection rule is applied within the application scope of the application event detection rule.