WO2018082707A1 - 应用检测控制方法及装置 - Google Patents

应用检测控制方法及装置 Download PDF

Info

Publication number
WO2018082707A1
WO2018082707A1 PCT/CN2017/109729 CN2017109729W WO2018082707A1 WO 2018082707 A1 WO2018082707 A1 WO 2018082707A1 CN 2017109729 W CN2017109729 W CN 2017109729W WO 2018082707 A1 WO2018082707 A1 WO 2018082707A1
Authority
WO
WIPO (PCT)
Prior art keywords
pfd
application
deleted
modified
pcrf
Prior art date
Application number
PCT/CN2017/109729
Other languages
English (en)
French (fr)
Inventor
周晓云
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018082707A1 publication Critical patent/WO2018082707A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]

Definitions

  • the present disclosure relates to the field of communications, for example, to an application detection control method and apparatus.
  • FIG. 1 is a schematic diagram of a Policy and Charging Control (PCC) structure defined by the 3rd Generation Partnership Project (3GPP).
  • PCC Policy and Charging Control
  • a Policy and Charging Rules Function formulates a Quality of Service (QoS) and a charging policy for services using network resources.
  • the PCRF formulates a control policy that can be combined with service information received from an Application Function (AF), user subscription information received from a User Profile Repository (SPR), and a policy configured by the operator.
  • AF Application Function
  • SPR User Profile Repository
  • the SPR communicates with the PCRF through the Sp interface, and the PCRF communicates with the AF through the Rx interface.
  • PCRF Charging Enforcement Function
  • BBERF Bearer Binding and Event Reporting Function
  • PCEF and CCERF are located in the Gateway (Gate-Way, GW).
  • the PCRF may subscribe to bearer layer related events from at least one of the PCEF and the BBERF, so that the PCRF senses events occurring at the bearer layer in time and changes the control strategy.
  • the PCRF communicates with the PCEF via the Gx interface.
  • the PCRF communicates with the BBERF via the Gxx interface.
  • the PCEF can perform application detection and control functions according to the PCC rules issued by the PCRF, and the Traffic Detection Function (TDF) can perform application detection according to the Application Detection Control (ADC) rules issued by the PCRF. control function.
  • the application detection function of the PCEF and the TDF enables the bearer network to perceive the application layer related information in the data transmitted in the network, such as the application type and the data flow description information, without the AF providing the service information.
  • the PCRF can formulate corresponding policies for these applications based on these application information and related network policies, thereby enabling differentiated QoS control and guarantee.
  • PCEF and TDF detect the application information of the data packet according to the detection rule, according to the application information and The network policy should control the data packets.
  • the PCEF can detect an application according to Packet Flow Descriptions (PFD) (also referred to as a packet filter description) stored in the PCEF, and the TDF can detect the application according to the PFD stored in the TDF.
  • PFD Packet Flow Descriptions
  • O&M Local Operations Management
  • PFDF Packet Flow Description Function
  • SCEF Service Capability Exposure Function
  • PFDF Packet Flow Description Function
  • the third-party service provider can learn or use the 3GPP network to provide services and capabilities through the SCEF.
  • the PFDF can store a packet flow description PFD associated with an application identity provided by a third party service provider.
  • PFDF provides PFD to PCEF and TDF.
  • the PFDF can provide a PFD to the PCEF or TDF in a Push mode and a Pull mode.
  • the PCRF communicates with the SCEF through the Nt interface.
  • the PCRF communicates with the TDF through the Sd interface.
  • the SCEF communicates with the PFDF through the Nu interface.
  • An application detection control method and device can solve the problem that the PCRF cannot adjust the policy according to the change of the PFD in the related art, which leads to the problem that the policy executed by the service that the user is accessing is inconsistent with the strategy of the network configuration.
  • An application detection control method includes:
  • the application detection control entity determines that the packet filter description PFD is modified or deleted
  • the PFD of the notification policy and charging rule function entity PCRF is modified or deleted, so that the PCRF detects the PFD sent by the control entity according to the application.
  • the modified or deleted notification makes a policy decision, wherein the PFD is used to detect an application.
  • the application detection control entity determines that the packet filter description PFD is modified or deleted
  • the PFD is modified or deleted by the notification policy and the charging rule function entity PCRF, including:
  • the application detection control entity determines that the at least one session activates the application detection rule
  • the application detection control entity notifies the PCRF that the PFD is modified or deleted, wherein the application detection rule includes the PFD corresponding to the PFD.
  • the application detection control entity notifies the PCRF that the PFD is modified or deleted.
  • the application detection control entity notifies the PCRF that the PFD is modified or deleted.
  • the application detection control entity notifies the message of the PCRF to carry at least one of the application identifier, the PFD modified indication, the modified Id of the modified PFD, and the modified PFD; as well as
  • the application detection control entity notifies the message of the PCRF to carry the application identifier, the indication that the PFD is deleted, the Id of the deleted PFD, and at least one of the deleted PFDs. .
  • the PCRF performs policy decision according to the notification that the PFD sent by the application detection control entity is modified or deleted, including:
  • the PCRF checks the context of each network interconnection protocol to connect to the access network IP-CAN session, and separately corrects the value before the PFD modification and the modified value to the PFD respectively.
  • the description of the service data flow reported by the application detection control entity is compared; if the value of the PFD before the modification matches the description of the service data flow, and the value of the modified PFD does not match the description of the service data flow
  • the PCRF deletes, according to the service data flow description, a policy and charging control PCC rule from a context of the IP-CAN session, wherein the IP-CAN session activates an application detection rule including the application identifier ;as well as,
  • the PCRF checks the context of each IP-CAN session, and compares the value of the PFD with the service data flow description reported by the application detection control entity before the PFD is deleted; If the value of the PFD matches the service data flow description, the PCRF deletes the PCC rule defined according to the service data flow description from the context of the IP-CAN session.
  • the method further includes:
  • the application detection control entity acquires an indication to modify or delete the PFD from the packet filter description function entity PFDF.
  • the application detection control entity is a policy and charging execution function entity PCEF or a service detection function entity TDF.
  • An application detection control method includes:
  • the application detection control entity determines that the packet filter description PFD is modified or deleted, and the notification policy and The charging rule function entity PCRF application is stopped or invalid, so that the PCRF makes a policy decision according to the notification that the PFD sent by the application detection control entity is modified or deleted, wherein the PFD is used to detect an application.
  • the application detection control entity determines that the PCRF application is stopped or invalid after the PFD is modified or deleted, including:
  • the application detection function entity checks each application detection rule that is activated and includes an application identifier corresponding to the PFD;
  • the application detection control entity detects the application by using the value of the PFD before the modification, the value of the modified PFD does not match the service data flow description of the application, and the application detects Before the control entity reports the application information of the application to the PCRF, the application detection control entity notifies the PCRF that the application stops or is invalid;
  • the application detection control entity detects the application by using the value of the deleted PFD, and the application detection control entity reports the application information of the application to the PCRF, and the application detection control entity notifies the application.
  • the application of the PCRF is stopped or invalid.
  • the method further includes:
  • the application detection control entity If the application detection control entity notifies the PCRF application to stop, the application detection control entity notifies the PCRF that the message also carries the cause value of the PFD failure.
  • the PCRF performs policy decision according to the notification that the PFD sent by the application detection control entity is modified or deleted, including:
  • the PCRF deletes a PCC rule formulated according to the application information.
  • the method further includes that the application detection control entity acquires an indication of modifying or deleting the PFD from the packet filter description function entity PFDF.
  • An application detection control device includes:
  • Determining a module configured to determine whether the packet filter describes whether the PFD is modified or deleted, wherein the PFD is used to detect an application
  • a notification module configured to notify the policy charging rule function entity PCRF that the PFD is modified or deleted if the PFD is modified or deleted, so that the PCRF controls the application according to the application detection
  • the notification that the PFD sent by the body is modified or deleted makes a policy decision.
  • the determining module includes:
  • a determining unit configured to notify, by the notification module, that the PFD is modified or deleted by the notification module when the application detection rule is activated by at least one session, where the application detection rule includes an application corresponding to the PFD Logo.
  • the notification that the notification module notifies the PCRF carries the application identifier, the indication that the PFD is modified, the identifier of the modified PFD, and the modified At least one of the PFDs;
  • the notification module notifies the message informing the PCRF that the application identifier, the indication that the PFD is deleted, the identifier of the deleted PFD, and at least one of the deleted PFDs are carried. .
  • the device further includes:
  • the obtaining module is configured to obtain an indication to modify or delete the PFD from the packet filter description function entity PFDF.
  • the application detection control device is a policy and charging execution function entity PCEF or a service detection function entity TDF.
  • An application detection control device includes:
  • Determining a module configured to determine whether the packet filter describes whether the PFD is modified or deleted, wherein the PFD is used to detect an application
  • a notification module configured to notify the policy and charging rule function entity PCRF that the application is stopped or invalid when the PFD is modified or deleted, so that the PCRF sends the PFD sent according to the application detection control entity to be modified or
  • the deleted notification makes a policy decision.
  • the device further includes:
  • the checking module is configured to check an application detection rule that is activated and includes an application identifier corresponding to the PFD, where the notification module further includes a first notification unit and a second notification unit,
  • the first notification unit is configured to detect that the PFD is modified, and the value of the modified PFD is used to detect an application, and the value of the modified PDF does not match the service data flow description of the application, and In the case that the application information of the application is reported to the PCRF, the application of the PCRF is notified to stop or invalidate;
  • the second notification unit is configured to notify the PCRF that the application stops or when the PFD is deleted, the application is detected by using the value of the deleted PFD, and the application information of the application is reported to the PCRF. invalid.
  • the message that the application stops in the PCRF is further configured to carry a cause value of the PFD failure.
  • the device further includes:
  • the obtaining module is configured to obtain an indication to modify or delete the PFD from the packet filter description function entity PFDF.
  • the application detection control device is a policy and charging execution function entity PCEF or a service detection function entity TDF.
  • a policy and charging rule function device comprising:
  • a receiving module configured to receive a notification that the packet filter description PFD is modified or deleted by the application detection control entity, where the notification is sent by the application detection control entity after determining that the PFD is modified or deleted, and The PFD is used to detect an application;
  • a policy decision module is arranged to make policy decisions based on the notifications.
  • the policy decision module includes:
  • a first policy decision unit configured to check, in the case that the PFD is modified, a context in which each network interconnection protocol communicates with an access network IP-CAN session, and separately obtains values and modified values of the PFD before modification The value is compared with the description of the service data flow reported by the application detection control entity before the PFD modification; if the value of the PFD before the modification matches the description of the service data flow, and the value of the modified PFD is If the service data flow description does not match, the policy and charging control PCC rule defined according to the service data flow description is deleted from the context of the IP-CAN session, wherein the IP-CAN session is activated to include the application. Identification of application detection rules; and,
  • a second policy decision unit configured to check a context of each IP-CAN session if the PFD is deleted, and report the value of the PFD to the application detection control entity before the PFD is deleted.
  • the service data flow description is compared, if the value of the PFD is related to the service data flow Describe the match, then the PCC rules defined according to the service data flow description are deleted from the context of the IP-CAN session.
  • a policy and charging rule function device comprising:
  • a receiving module configured to receive a notification that the application detection control entity stops or invalidates, wherein the notification is sent by the application detection control entity after determining that the packet filter description PFD is modified or deleted, and the PFD is used by the application detection control entity For testing applications;
  • a policy decision module is arranged to make policy decisions based on the notifications.
  • the notification in the case that the notification is that the application is stopped, the notification further carries a cause value of the PFD failure.
  • the device further includes:
  • the module is deleted, and is set to delete the PCC rule that is determined according to the application information reported by the application detection control entity.
  • a computer readable storage medium storing computer executable instructions arranged to perform the above method.
  • An application detection control entity comprising:
  • At least one processor At least one processor
  • the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform the method of the application detection control entity execution described above.
  • a policy and charging rule functional entity including:
  • At least one processor At least one processor
  • the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform the method performed by the policy and charging rules function entity.
  • FIG. 1 is a schematic diagram of a PCC structure according to the related art
  • Embodiment 2 is a schematic flow chart of an application detection control method in Embodiment 1;
  • Embodiment 3 is a schematic flow chart of an application detection control method in Embodiment 2;
  • Embodiment 4 is a schematic flow chart of an application detection control method in Embodiment 3.
  • Embodiment 5 is a schematic flow chart of an application detection control method in Embodiment 4.
  • Figure 6 is a block diagram showing the structure of an application detecting control device in Embodiment 5.
  • Figure 7 is a block diagram showing the structure of an application detecting control device in Embodiment 6;
  • Embodiment 8 is a structural block diagram of a function device of a policy and charging rule in Embodiment 7;
  • Embodiment 9 is a structural block diagram of a function device of a policy and charging rule in Embodiment 8.
  • Embodiment 10 is a schematic diagram showing the hardware structure of an application detection control entity in Embodiment 9;
  • FIG. 11 is a schematic diagram showing the hardware structure of a policy and charging rule function entity in Embodiment 10.
  • Third-party service providers can add, update, or delete PFDs for application IDs saved on PCEF or TDF through SCEF or PFDF.
  • the PCEF or TDF detects the corresponding application according to the PFD provided by the third-party service provider (ie, represented by the application identifier)
  • the PCRF can formulate a corresponding policy.
  • the PFD of an application identifier is updated or deleted, some policies of the application corresponding to the application identifier may be changed.
  • the PCRF cannot adjust the policy according to the change of the PFD, and the policy executed by the service that the user is accessing is inconsistent with the policy of the network configuration.
  • the PFD of the one or more application identifiers provided before the third-party application (for example, the Service Capability Servers (SCS) or the Application Server (AS) is updated or the third-party application update is deleted.
  • the PCEF sends a message to the PCRF that the PFD is modified or deleted. The steps are as shown in FIG. 2.
  • the third-party application (for example, SCS) sends a PFD management request message to the SCEF.
  • the PFD management request message carries the SCS identifier, the service provider (SP) reference identifier, the external application identifier (Application Identifier), and the request.
  • the modified PFD or the PFD requesting deletion is the third-party application (for example, SCS) sends a PFD management request message to the SCEF.
  • the PFD management request message carries the SCS identifier, the service provider (SP) reference identifier, the external application identifier (Application Identifier), and the request.
  • SP service provider
  • Application Identifier Application Identifier
  • the SCS identifier in step 201 is replaced with an AS identifier, and the AS can continue to perform the method in this embodiment.
  • the SCEF performs authorization, and converts the external application identifier (Application Identifier) into an application identifier (Application Identifier) that can be learned by the PFDF.
  • the application identifier that the PFDF can learn can be an application identifier that converts the external application identifier into a required format in the PFDF.
  • the SCEF sends a PFD management request message to the PFDF, where the PFD management request message carries the SCEF identifier, the SCEF reference identifier, the application identifier (Application Identifier), and the PFD requesting the modification or the PFD requesting the deletion.
  • the PFD management request message carries the SCEF identifier, the SCEF reference identifier, the application identifier (Application Identifier), and the PFD requesting the modification or the PFD requesting the deletion.
  • step 204 the PFDF saves the received information.
  • step 205 the PFDF returns an acknowledgement message to the SCEF.
  • step 206 the SCEF returns a confirmation message to the third party application.
  • steps 207a-208a are performed; if the PFDF provides the PFD to the PCEF in the Pull mode, steps 207b-208b are performed.
  • step 207a the PFDF sends a PFD update or delete message to the PCEF.
  • the PFDF if the PFDF requests to modify the PFD, the PFDF carries an Application Identifier, an indication of the PFD modification, an identifier of the PFD requesting the modification (Identifier, Id), and a new PFD in the message.
  • the PFDF if the PFDF requests to delete the PFD, the PFDF carries an Application Identifier, a PFD deletion indication, and an Id of the PFD requesting the deletion.
  • the message may carry a list of PFD Ids requesting modification. If the PFDF requests to delete multiple PFDs of an Application Identifier, the message may carry the Id list of the PFD requesting to be deleted.
  • step 208a the PCEF saves the received message and returns a confirmation message to the PFDF.
  • the PCEF replaces the new PFD corresponding to the PFD Id provided by the PFDF with the old PFD corresponding to the PFD Id, and binds the PFD Id provided by the PFDF to the Application Identifier.
  • the PCEF deletes the PFD corresponding to the PFD Id that is requested to be deleted from the PFD list corresponding to the Application Identifier.
  • step 207b the application timer of the application identifier (Application Identifier) is timed to be scheduled.
  • the PCEF sends a request message for obtaining the PFD to the PFDF, and the request message for acquiring the PFD carries an application identifier (Application Identifier).
  • step 208b the PFDF returns a confirmation message to the PCEF.
  • the PFDF carries an Application Identifier, an indication of the PFD modification, an Id of the modified PFD, and a new PFD in the acknowledgment message.
  • the acknowledgment message carries an Application Identifier, an indication to delete the PFD, and an Id of the deleted PFD.
  • the confirmation message carries the Id list of the PFD requesting the modification.
  • the confirmation message carries the Id list of the PFD requesting modification.
  • the PCEF saves the received information. If the PFDF requests to modify the PFD, the PCEF replaces the new PFD corresponding to the PFD Id provided by the PFDF with the old PFD corresponding to the PFD Id, and binds the new PFD corresponding to the PFD Id provided by the PFDF to the Application Identifier. If the PFDF requests to delete the PFD, the PCEF deletes the PFD corresponding to the Id of the PFD that is requested to be deleted from the PFD list corresponding to the Application Identifier. The PCEF returns a confirmation message to the PFDF.
  • the PCEF detects that at least one IP-Connectivity Access Network (IP-CAN) session activates the PCC rule, and the PCEF sends a notification message to the PCRF that the PFD is modified or deleted.
  • IP-CAN IP-Connectivity Access Network
  • the PCC rule includes an Application Identifier and a PCC rule is set to detect the application.
  • the application identifier Application Identifier
  • the PFD modification indication the modified PFD Id
  • the value of the modified PFD the value of the modified PFD
  • the value of the modified PFD the value of the modified PFD
  • the notification message carries the application identifier (Application Identifier), the PFD deletion indication, the Id of the deleted PFD, and the value of the deleted PFD.
  • Application Identifier Application Identifier
  • step 210 the PCRF saves the information reported by the PCEF and returns a confirmation message.
  • step 211 the PCRF makes a policy decision.
  • the PCRF checks the context of each IP-CAN session and will modify it separately. The former PFD and the modified PFD are compared with the SDFD (Service Data Flow Description) reported by the previous PCEF, wherein the IP-CAN session activates the PCC rule including the application identifier. If the modified PFD matches the SDFD and the modified PFD does not match the SDFD, the PCRF deletes the PCC rules based on the SDFD reported by the previous PCEF from the context of the IP-CAN session. If the IP-CAN session has a BBERF, the PCRF can also delete the corresponding QoS rule.
  • SDFD Service Data Flow Description
  • the PCRF checks the context of each IP-CAN session and compares the deleted PFD with the SDFD reported by the PCEF before the PFD is deleted.
  • the IP-CAN session activates the PCC rule containing the application identifier. If the deleted PFD matches the SDFD reported by the previous PCEF, the PCRF deletes the PCC rule established according to the SDFD reported by the previous PCEF from the context of the IP-CAN session. If the IP-CAN session has a BBERF, the PCRF can also delete the corresponding QoS rule.
  • the PCRF sends a policy and rule providing message to the PCEF, deletes the corresponding PCC rule, and the PCEF returns an acknowledgement message.
  • the PCEF deletes the PCC rules and initiates the corresponding process (for example, the PCEF modifies the bearer or deletes the bearer).
  • step 213 if the QoS rule is deleted in step 211, the PCRF will delete the QoS rule from the BBERF, and the BBERF returns an acknowledgement message. BBERF deletes the QoS rules and initiates the corresponding process.
  • the third party application (such as SCS or AS) updates the PFD of one or more application identifiers provided before or deletes the PFD of one or more application identifiers provided before the third party application is updated.
  • the PCEF sends a message to the PCRF that the PFD is modified or deleted. The steps are shown in Figure 3.
  • the third-party application sends a PFD management request message to the SCEF, where the PFD management request message carries the SCS identifier, the service provider (SP) reference identifier, the external application identifier (Application Identifier), and the request modification.
  • the PFD is either a PFD requesting deletion.
  • the SCS identifier in step 301 is replaced with the AS identifier, and the AS can continue to perform the method in this embodiment.
  • the SCEF performs authorization, and converts an external application identifier (Application Identifier) into an application identifier (Application Identifier) that can be learned by the PFDF.
  • the application identifier that the PFDF can learn can be an application identifier that converts the external application identifier into a required format in the PFDF.
  • the SCEF sends a PFD management request message to the PFDF, where the PFD management request message carries the SCEF identifier, the SCEF reference identifier, the application identifier (Application Identifier), and the request. Ask for a modified PFD or a PFD requesting deletion.
  • step 304 the PFDF saves the received information.
  • step 305 the PFDF returns an acknowledgement message to the SCEF.
  • step 306 the SCEF returns a confirmation message to the third party application.
  • steps 307a-308a are performed; if the PFDF provides the PFD to the PCEF in the Pull mode, steps 307b-308b are performed.
  • step 307a the PFDF sends a PFD update or delete message to the PCEF.
  • the PFDF if the PFDF requests to modify the PFD, the PFDF carries an Application Identifier, a PFD modification indication, an identifier of the PFD requesting the modification (Identifier, Id), and a new PFD in the message.
  • the PFDF if the PFDF requests to delete the PFD, the PFDF carries an Application Identifier, a PFD deletion indication, and an Id of the PFD requesting the deletion.
  • the message may carry a list of PFD Ids requesting modification. If the PFDF requests to delete multiple PFDs of an Application Identifier, the message may carry the Id list of the PFD requesting to be deleted.
  • step 308a the PCEF saves the received message and returns a confirmation message to the PFDF.
  • the PCEF replaces the new PFD corresponding to the PFD Id provided by the PFDF with the old PFD (modified PFD) corresponding to the PFD Id, and binds the PFD Id provided by the PFDF to the Application Identifier. .
  • the PCEF deletes the PFD corresponding to the PFD Id that is requested to be deleted from the PFD list corresponding to the Application Identifier.
  • step 307b when the buffer timer of the application identifier (Application Identifier) is timed to a predetermined value, the PCEF sends a request message for obtaining the PFD to the PFDF, and the request message for acquiring the PFD carries an application identifier (Application Identifier).
  • step 308b the PFDF returns a confirmation message to the PCEF.
  • the PFDF carries an Application Identifier, an indication of the PFD modification, an Id of the modified PFD, and a new PFD in the acknowledgment message.
  • the confirmation message is received.
  • the application identifier Application Identifier
  • the indication of deleting the PFD and the Id of the deleted PFD are carried.
  • the confirmation message carries the Id list of the PFD requesting the modification.
  • the confirmation message carries the Id list of the PFD requesting modification.
  • the PCEF saves the received information. If the PFDF requests to modify the PFD, the PCEF replaces the new PFD corresponding to the PFD Id provided by the PFDF with the old PFD corresponding to the PFD Id, and binds the new PFD corresponding to the PFD Id provided by the PFDF to the Application Identifier. If the PFDF requests to delete the PFD, the PCEF deletes the PFD corresponding to the Id of the PFD that is requested to be deleted from the PFD list corresponding to the Application Identifier. The PCEF returns a confirmation message to the PFDF.
  • the PCEF checks each IP-CAN session (i.e., the context of the IP-CAN session), wherein the IP-CAN session activates the PCC rules containing the application identification.
  • the PCEF detects the corresponding service data flow by using the old PFD (that is, the PFD before modification), and the new PFD (ie, the modified PFD) does not match the service data flow description. If the PCEF detects the application by using the modified PFD, the application information reported by the PFD before the modification is reported to the PCRF (the application information includes the application identifier and the application start event indication, and may also include the instance identifier (Instance Id). And the service data flow description information), the PCEF sends an event report message to the PCRF, where the message carries an application identifier and an application invalidation indication. If the application information of the report before the PCEF sends the event report message to the PCRF carries the instance identifier, the instance identifier is still carried in the message.
  • the PCEF detects the corresponding service data stream using the old PFD (deleted PFD). If the PCEF detects the application by using the old PFD, and reports to the PCRF the application information detected by the deleted PFD (the application information includes an application identifier, an application start event indication, and an optional instance identifier. (Instance Id) and the flow description information, the PCEF sends an event report message to the PCRF, where the event report message carries an application identifier and an application invalidation indication. If the application information of the previous report carries the instance identifier, the event report message still carries the instance identifier.
  • the PCEF carries an application identifier, an application stop indication, a cause value, and a PFD failure indication in the reported event report message. If the application information of the previous report carries an instance identifier The instance identifier is still carried in the time report message.
  • step 310 the PCRF saves the information reported by the PCEF and returns a confirmation message.
  • step 311 the PCRF makes a policy decision.
  • the PCRF deletes the PCC rules established according to the SDFD reported by the previous PCEF from the context of the IP-CAN session. If the IP-CAN session has a BBERF, the PCRF can also delete the corresponding QoS rule.
  • step 312 the PCRF sends a policy and rule providing message to the PCEF, deletes the corresponding PCC rule, and the PCEF returns an acknowledgement message.
  • the PCEF deletes the PCC rules and initiates the corresponding process.
  • step 313 the PCRF will delete the QoS rule from the BBERF, and the BBERF returns an acknowledgment message. BBERF deletes the QoS rules and initiates the corresponding process.
  • the third party application (such as SCS or AS) updates the PFD of one or more application identifiers provided before or deletes the PFD of one or more application identifiers provided before the third party application is updated.
  • the TDF sends a message to the PCRF that the PFD is modified or deleted. The steps are shown in Figure 4.
  • the third-party application sends a PFD management request message to the SCEF.
  • the PFD management request message carries the SCS identifier, the SP reference identifier, the external application identifier (Application Identifier), and the PFD requesting the modification or the PFD requesting the deletion.
  • the SCS identifier in step 401 is replaced with an AS identifier, and the AS can continue to perform the method in this embodiment.
  • the SCEF performs authorization and converts the external application identifier (Application Identifier) into an application identifier (Application Identifier) that the PFDF can recognize.
  • the application identifier that the PFDF can learn can be an application identifier that converts the external application identifier into a required format in the PFDF.
  • the SCEF sends a PFD management request message to the PFDF, where the PFD management request message carries the SCEF identifier, the SCEF reference identifier, the application identifier (Application Identifier), and the PFD requesting the modification or the PFD requesting the deletion.
  • the PFD management request message carries the SCEF identifier, the SCEF reference identifier, the application identifier (Application Identifier), and the PFD requesting the modification or the PFD requesting the deletion.
  • step 404 the PFDF saves the received information.
  • step 405 the PFDF returns an acknowledgement message to the SCEF.
  • step 406 the SCEF returns a confirmation message to the third party application.
  • steps 407a-408a are performed; if the PFDF is used Steps 407b-408b are performed by providing the PFD to the PCEF in the Pull mode.
  • step 407a the PFDF sends a PFD update or delete message to the TDF.
  • the PFDF if the PFDF requests to modify the PFD, the PFDF carries an Application Identifier, a PFD modification indication, an identifier of the PFD requesting the modification (Identifier, Id), and a new PFD in the message.
  • the PFDF if the PFDF requests to delete the PFD, the PFDF carries an Application Identifier, a PFD deletion indication, and an Id of the PFD requesting the deletion.
  • the message may carry a list of PFD Ids requesting modification. If the PFDF requests to delete multiple PFDs of an Application Identifier, the message may carry the Id list of the PFD requesting to be deleted.
  • step 408a the TDF saves the received message and returns a confirmation message to the PFDF.
  • the TDF replaces the new PFD corresponding to the PFD Id provided by the PFDF with the old PFD corresponding to the PFD Id, and binds the PFD Id provided by the PFDF to the Application Identifier.
  • the TDF deletes the PFD corresponding to the PFD Id that is requested to be deleted from the PFD list corresponding to the Application Identifier.
  • step 407b when the buffer timer of the application identifier (Application Identifier) is timed to a predetermined value, the TDF sends a request message for acquiring the PFD to the PFDF, and the request message for acquiring the PFD carries an application identifier (Application Identifier).
  • step 408b the PFDF returns an acknowledgement message to the TDF.
  • the PFDF carries an Application Identifier, an indication of the PFD modification, an Id of the modified PFD, and a new PFD in the acknowledgment message.
  • the acknowledgment message carries an Application Identifier, an indication to delete the PFD, and an Id of the deleted PFD.
  • the confirmation message carries the Id list of the PFD requesting the modification.
  • the confirmation message is received. It will carry the list of Ids of the PFD requesting modification.
  • the TDF saves the received information. If the PFDF requests to modify the PFD, the TDF replaces the new PFD corresponding to the PFD Id provided by the PFDF with the old PFD corresponding to the PFD Id, and binds the new PFD corresponding to the PFD Id provided by the PFDF to the Application Identifier. If the PFDF requests to delete the PFD, the TDF deletes the PFD corresponding to the Id of the PFD that is requested to be deleted from the PFD list corresponding to the Application Identifier. The TDF returns a confirmation message to the PFDF.
  • the TDF detects that there is at least one TDF session that activates the ADC rule, wherein the ADC rule includes the application identification and the ADC rule is set to detect the application. Then the TDF sends a PFD modification or deletion notification message to the PCRF.
  • the application identifier Application Identifier
  • the PFD modification indication the modified PFD Id
  • the value of the modified PFD the value of the modified PFD
  • the value of the modified PFD the value of the modified PFD
  • the notification message carries the application identifier (Application Identifier), the PFD deletion indication, the Id of the deleted PFD, and the value of the deleted PFD.
  • Application Identifier Application Identifier
  • step 410 the PCRF saves the information reported by the TDF and returns a confirmation message.
  • step 411 the PCRF makes a policy decision.
  • the PCRF checks the context of each IP-CAN session (the IP-CAN session corresponds to the TDF session one by one), and separately updates the PFD before the modification and the modified PFD to the SDFD (Service data reported by the previous TDF). Flow description, business data flow description) For comparison, the ADC rule contains the application identifier and the IP-CAN session activates the ADC rules. If the modified PFD matches the SDFD and the modified PFD does not match the SDFD, the PCRF deletes the PCC rules based on the SDFD reported by the previous PCEF from the context of the IP-CAN session. If the IP-CAN session has a BBERF, the PCRF can also delete the corresponding QoS rule.
  • the PCRF checks the context of each IP-CAN session and compares the deleted PFD with the SDFD reported by the previous PCEF, wherein the IP-CAN session activates the PCC rule containing the Application Id. If the deleted PFD matches the SDFD reported by the previous PCEF, the PCRF deletes the PCC rule established according to the SDFD reported by the previous PCEF from the context of the IP-CAN session. If the IP-CAN session has a BBERF, the PCRF can also delete the corresponding QoS rule.
  • step 412 the PCRF sends a policy and rule providing message to the TDF, deletes the corresponding PCC rule, and the PCEF returns an acknowledgement message.
  • the PCEF deletes the PCC rules and initiates the corresponding process.
  • step 413 the PCRF will delete the QoS rule from the BBERF, and the BBERF returns an acknowledgment message. BBERF deletes the QoS rules and initiates the corresponding process.
  • the third party application (such as SCS or AS) updates the PFD of one or more application identifiers provided before or deletes the PFD of one or more application identifiers provided before the third party application is updated.
  • the TDF sends a message to the PCRF that the PFD is modified or deleted. The steps are shown in Figure 5.
  • the third-party application sends a PFD management request message to the SCEF.
  • the PFD management request message carries the SCS identifier, the SP reference identifier, the external application identifier (Application Identifier), and the PFD requesting the modification or the PFD requesting the deletion.
  • the SCS identifier in step 401 is replaced with an AS identifier, and the AS can continue to perform the method in this embodiment.
  • the SCEF performs authorization and converts the external application identifier (Application Identifier) into an application identifier (Application Identifier) that the PFDF can recognize.
  • the application identifier that the PFDF can learn can be an application identifier that converts the external application identifier into a required format in the PFDF.
  • the SCEF sends a PFD management request message to the PFDF, where the PFD management request message carries the SCEF identifier, the SCEF reference identifier, the application identifier (Application Identifier), and the PFD requesting the modification or the PFD requesting the deletion.
  • the PFD management request message carries the SCEF identifier, the SCEF reference identifier, the application identifier (Application Identifier), and the PFD requesting the modification or the PFD requesting the deletion.
  • step 504 the PFDF saves the received information.
  • step 505 the PFDF returns an acknowledgement message to the SCEF.
  • step 506 the SCEF returns a confirmation message to the third party application.
  • steps 507a-508a are performed; if the PFDF provides the PFD to the TDF in the Pull mode, steps 507b-508b are performed.
  • step 507a the PFDF sends a PFD update or delete message to the TDF.
  • the PFDF if the PFDF requests to modify the PFD, the PFDF carries an Application Identifier, a PFD modification indication, an identifier of the PFD requesting the modification (Identifier, Id), and a new PFD in the message.
  • the PFDF if the PFDF requests to delete the PFD, the PFDF carries an Application Identifier, a PFD deletion indication, and an Id of the PFD requesting the deletion.
  • the information can carry a list of PFD Ids that request modification. If the PFDF requests to delete multiple PFDs of an Application Identifier, the message may carry the Id list of the PFD requesting to be deleted.
  • step 508a the TDF saves the received message and returns a confirmation message to the PFDF.
  • the TDF replaces the new PFD corresponding to the PFD Id provided by the PFDF with the old PFD corresponding to the PFD Id, and binds the PFD Id provided by the PFDF to the Application Identifier.
  • the TDF deletes the PFD corresponding to the PFD Id that is requested to be deleted from the PFD list corresponding to the Application Identifier.
  • step 507b when the buffer timer of the application identifier (Application Identifier) is timed to a predetermined value, the TDF sends a request message for acquiring the PFD to the PFDF, and the request message for acquiring the PFD carries an application identifier (Application Identifier).
  • step 508b the PFDF returns an acknowledgement message to the TDF.
  • the PFDF carries an Application Identifier, an indication of the PFD modification, an Id of the modified PFD, and a new PFD in the acknowledgment message.
  • the acknowledgment message carries an Application Identifier, an indication to delete the PFD, and an Id of the deleted PFD.
  • the confirmation message carries the Id list of the PFD requesting the modification.
  • the confirmation message carries the Id list of the PFD requesting modification.
  • the TDF saves the received message. If the PFDF requests to modify the PFD, the TDF replaces the new PFD corresponding to the PFD Id provided by the PFDF with the old PFD corresponding to the PFD Id, and binds the new PFD corresponding to the PFD Id provided by the PFDF to the Application Identifier. If the PFDF requests to delete the PFD, the TDF deletes the PFD corresponding to the Id of the PFD that is requested to be deleted from the PFD list corresponding to the Application Identifier. The TDF returns a confirmation message to the PFDF.
  • step 509 the TDF checks each TDF session (ie, the TDF session corresponding to the IP-CAN session).
  • the TDF uses the old PFD (ie, the pre-modified PFD) to detect the corresponding industry.
  • the traffic data flow description, the new PFD (ie, the modified PFD) does not match the corresponding service data flow description.
  • the TDF detects the application by using the modified PFD the application information reported by the PFD is reported to the PCRF.
  • the application information includes an application identifier, an application startup event indication, an optional instance identifier (Instance Id), and service data.
  • the flow description information is sent by the TDF to the PCRF, where the event report message carries an application identifier and an application invalidation indication. If the application information of the report before the TDF sends the event report message to the PCRF carries the instance identifier, the TDF sends the event report message to the PCRF to still carry the instance identifier.
  • the TDF detects the corresponding service data flow by using the old PFD, and the TDF uses the old PFD to detect the application, and reports the application information detected by the PFD to the PCRF (the application information includes the application identifier, The application start event indication, the optional instance identifier (Instance Id) and the flow description information, the TDF sends an event report message to the PCRF, where the event report message carries the application identifier and the application invalid indication. If the application information of the report before the TDF sends the event report message to the PCRF carries the instance identifier, the event report message sent by the TDF to the PCRF still carries the instance identifier.
  • the TDF carries an Application Identifier, an Application Stop indication, a Cause value, and a PFD failure indication in the reported event report message. If the application information of the report before the TDF sends the event report message to the PCRF carries the instance identifier, the event report message still carries the instance identifier.
  • step 510 the PCRF saves the information reported by the TDF and returns a confirmation message.
  • step 511 the PCRF makes a policy decision.
  • the PCRF deletes the PCC rules previously formulated according to the SDFD from the context of the IP-CAN session. If the IP-CAN session has a BBERF, the PCRF can also delete the corresponding QoS rule.
  • step 512 the PCRF sends a policy and rule providing message to the TDF, deletes the corresponding PCC rule, and the PCEF returns an acknowledgement message.
  • the PCEF deletes the PCC rules and initiates the corresponding process.
  • step 513 the PCRF deletes the QoS rule from the BBERF, and the BBERF returns an acknowledgement message.
  • BBERF deletes the QoS rules and initiates the corresponding process.
  • the method in the foregoing embodiment may be implemented by means of software plus a general hardware platform, or may be implemented by hardware.
  • the above technical solution can be embodied in the form of a software product stored in a storage medium (such as a read-only memory (ROM), a random access memory (RAM), a magnetic disk,
  • a storage medium such as a read-only memory (ROM), a random access memory (RAM), a magnetic disk
  • the optical disc includes one or more instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device) to perform the method in the above embodiments.
  • the embodiment provides an application detection control apparatus, and the application detection control apparatus includes: a first determination module 60 and a first notification module 61.
  • the first determining module 60 is configured to determine whether the PFD is modified or deleted, wherein the PFD is for detecting an application.
  • the first notification module 61 is configured to notify the policy charging rule function entity PCRF that the PFD is modified if the PFD is modified, and notify the PCRF that the PFD is Deleting, so that the PCRF makes a policy decision according to the notification that the PFD sent by the application detection control entity is modified or deleted.
  • the first determining module 60 includes: a determining unit 601.
  • the determining unit 601 is configured to notify the PCRF that the PFD is modified or deleted by the notification module when it is determined that the at least one session is activated, wherein the application detection rule includes an application identifier corresponding to the PFD. .
  • the notification that the notification module notifies the PCRF carries the application identifier, the indication that the PFD is modified, the identifier of the modified PFD, and the modified At least one of the PFDs.
  • the notification by the notification module, the message that is sent to the PCRF, the application identifier, the indication that the PFD is deleted, the identifier of the deleted PFD, and the deleted PFD. At least one of them.
  • the application detection control device further includes: a first acquisition module 62.
  • the first obtaining module 62 is configured to acquire an indication of modifying the PFD or an indication of deleting the PFD from the packet filter description function entity PFDF.
  • the application detection control device is a policy and charging execution function entity PCEF or a service detection function entity TDF.
  • this embodiment provides an application detection control apparatus.
  • the application detection control device includes a second determination module 70 and a second notification module 71.
  • the second determining module 70 is configured to determine whether the packet filter describes whether the PFD is modified or deleted, The PFD is used to detect an application.
  • the second notification module 71 is configured to notify the policy and charging rule function entity PCRF that the application is stopped or invalid if the PFD is modified or deleted, so that the PCRF is detected according to the application detection control entity. Modify or be deleted notifications for policy decisions.
  • the application detection control device further includes: an inspection module 72.
  • the checking module 72 is arranged to check each of the application detection rules that are activated and that contain the application identifier corresponding to the PFD.
  • the second notification module 71 includes a first notification unit 711 and a second notification unit 712.
  • the first notification unit 711 is configured to detect the application when the PFD is modified, and the value of the modified PFD is used, and the value of the modified PDF does not match the service data flow description of the application, and the foregoing When the PCRF reports the application information of the application, the PCRF is notified that the application is stopped or invalid.
  • the second notification unit 712 is configured to notify the PCRF that the application stops or is invalid if the PFD is deleted, the application is detected by using the value of the deleted PFD, and the application information of the application is reported to the PCRF. .
  • the message that the application stops in the PCRF is further configured to carry a cause value of the PFD failure.
  • the foregoing apparatus further includes a second obtaining module 73.
  • the second obtaining module 73 is configured to acquire an indication of modifying the PFD or an indication of deleting the PFD from the packet filter description function entity PFDF.
  • the application detection control device is a policy and charging execution function entity PCEF or a service detection function entity TDF.
  • the embodiment provides a policy and charging rule function device.
  • the policy and charging rule function device includes: a first receiving module 80 and a first policy determining module 81.
  • the first receiving module 80 is configured to receive a notification that the packet filter description PFD sent by the application detection control entity is modified or deleted, wherein the notification is sent by the application detection control entity after determining that the PFD is modified or deleted. And the PFD is used to detect an application.
  • the first policy decision module 81 is arranged to make policy decisions based on the notifications.
  • the first policy decision module 81 includes: a first policy decision unit 811 and a second policy decision unit 812.
  • the first policy decision unit 811 is configured to check the context of each IP-CAN session if the PFD is modified, and separately compare the value before the PFD modification and the modified value to the PFD respectively.
  • the service data flow description reported by the application detection control entity is compared before the modification; if the value of the PFD before the modification matches the description of the service data flow, and the value of the modified PFD and the service data flow description are not Matching, the policy and charging control PCC rules defined according to the service data flow description are deleted from the context of the IP-CAN session, wherein the IP-CAN session activates an application detection rule including the application identifier.
  • the second policy decision unit 812 is configured to check the context of each IP-CAN session if the PFD is deleted, and report the value of the PFD and the application detection control entity before the PFD is deleted. The service data flow description is compared. If the value of the PFD matches the service data flow description, the PCC rule defined according to the service data flow description is deleted from the context of the IP-CAN session.
  • the embodiment provides a policy and charging rule function device, where the policy and charging rule function device includes: a second receiving module 90 and a second policy determining module 91.
  • the second receiving module 90 is configured to receive a notification that the application detection control entity stops or invalidates, wherein the notification is that the application detection control entity determines that the packet filter description PFD is modified or deleted, and the PFD is used to detect applications.
  • the second policy decision module 91 is arranged to make policy decisions based on the notifications.
  • the notification in the case that the notification is that the application is stopped, the notification further carries a cause value of the PFD failure.
  • the policy and charging rule function device further includes a deleting module 92.
  • the deletion module 92 is configured to delete the PCC rules formulated according to the application information reported by the application detection control entity.
  • the application detection control entity includes:
  • At least one processor 100 one processor 100 is exemplified in FIG. 10; a memory 101; and a communication interface 102 and a bus 103.
  • the processor 100, the memory 101, and the communication interface 102 can be completed through the bus 103. Communication with each other.
  • the processor 100 can call logic instructions in the memory 101 to perform the method performed by the application detection control entity in the above embodiments.
  • logic instructions in the memory 101 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium.
  • the memory 101 is a computer readable storage medium, and can be used to store a software program, a computer executable program, such as the program instruction or module corresponding to the method executed by the detection control entity in the above embodiment.
  • the processor 100 executes a function application and data processing by executing a software program, an instruction or a module stored in the memory 101, that is, a method of implementing the application detection control entity in the above embodiment.
  • the memory 101 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to usage of the terminal device, and the like. Further, the memory 101 may include a high speed random access memory, and may also include a nonvolatile memory.
  • the application detection control entity includes:
  • At least one processor 110 is exemplified by a processor 110 in FIG. 11; a memory 111; and a communication interface 112 and a bus 113.
  • the processor 110, the memory 111, and the communication interface 112 can complete communication with each other through the bus 113.
  • the processor 110 can invoke logic instructions in the memory 111 to perform the method performed by the policy and charging rules function entity in the above embodiments.
  • logic instructions in the memory 111 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium.
  • the memory 111 is a computer readable storage medium and can be used to store a software program, a computer executable program, such as a program instruction or module corresponding to a method executed by a policy and charging rule function entity in the above embodiment.
  • the processor 110 performs a function application and data processing by executing a software program, an instruction or a module stored in the memory 111, that is, a method of implementing the policy and charging rule function entity in the above embodiment.
  • the memory 111 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function; and the storage data area may be stored according to the terminal device Use the data created, etc. Further, the memory 111 may include a high speed random access memory, and may also include a nonvolatile memory.
  • An embodiment provides an application detection control system that is configured to implement the above-described embodiments.
  • the above technical solution may be embodied in the form of a software product stored in a storage medium, including one or more instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to execute All or part of the steps of the method described in the above embodiments.
  • a computer device which may be a personal computer, a server, a network device, etc.
  • An embodiment provides a program code storage medium storing a flow step configured to perform the above-described embodiments.
  • the storage medium described above may be arranged to store program code for performing the steps in any of the above method embodiments.
  • the storage medium can be a non-transitory computer readable storage medium.
  • the foregoing storage medium may include, but is not limited to, a U disk, a ROM, a RAM, a mobile hard disk, a magnetic disk, or an optical disk, and the like, which can store program codes.
  • the plurality of modules or steps in the above embodiments may be implemented by a general purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • the plurality of modules or steps in the above embodiments may be implemented by program code executable by the computing device.
  • the plurality of modules or steps in the above-described embodiments may be stored in a storage device to be executed by the computing device, and in some cases, the steps shown or described may be performed in a different order than in the above-described embodiments.
  • the plurality of modules or steps in the above embodiments may be separately fabricated into a plurality of integrated circuit modules, or a plurality of modules or steps thereof may be fabricated into a single integrated circuit module.
  • the application detection control method and device can solve the problem that the PCRF cannot adjust the policy according to the change of the PFD in the related art, and the policy of the service that the user is accessing is inconsistent with the strategy of the network configuration.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种应用检测控制方法包括：应用检测控制实体确定分组过滤器描述PFD被修改或被删除后，通知策略与计费规则功能实体PCRF所述PFD被修改或被删除，以使所述PCRF根据应用检测控制实体发送的所述PFD被修改或被删除的通知进行策略决策，其中，所述PFD用于检测应用。

Description

应用检测控制方法及装置 技术领域
本公开涉及通信领域，例如，涉及一种应用检测控制方法及装置。
背景技术
图1是第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)定义的策略和计费控制(Policy and Charging Control，PCC)结构示意图。
参见图1，策略和计费规则功能实体(Policy and Charging Rules Function，PCRF)为使用网络资源的业务制定服务质量(Quality of Service，QoS)和计费策略。PCRF制定控制策略可以结合从应用功能实体(Application function，AF)接收的业务信息，从用户签约数据库(Subscription Profile Repository，SPR)接收的用户签约信息，以及运营商配置的策略。其中，SPR与PCRF通过Sp接口通信，PCRF通过Rx接口与AF通信。
PCRF下发为业务制定的控制策略至策略和计费执行功能实体(Policy and Charging Enforcement Function，PCEF)或者承载绑定和事件上报功能实体(Bearer Binding and Event Reporting Function，BBERF)执行。参见图1，PCEF和CCERF位于网关(Gate-Way，GW)内。PCRF可以从PCEF和BBERF中的至少一个订阅承载层相关事件，以便PCRF及时感知承载层发生的事件，并更改控制策略。PCRF通过Gx接口与PCEF通信。PCRF通过Gxx接口与BBERF通信。
PCEF能够根据PCRF下发的PCC规则执行应用检测和控制功能，以及业务检测功能实体(Traffic Detection Function，TDF)能够根据PCRF下发的应用检测控制实体(Application Detection Control，ADC)规则执行应用检测和控制功能。PCEF和TDF的应用检测功能能够使得承载网络在没有AF提供业务信息的情况下，感知正在承载网络中传输的数据中的应用层相关信息，譬如应用类型以及数据流描述信息等应用信息。PCRF可以根据这些应用信息以及相关的网络策略针对这些应用制定相应的策略，从而能够差异化的QoS控制和保障。PCEF和TDF根据检测规则检测数据包的应用信息，根据这些应用信息以及对 应的网络策略，对数据包进行控制。
相关技术中，PCEF可以根据保存在PCEF中的分组流描述(Packet Flow Descriptions，PFD)(也称，分组过滤器描述)检测应用，TDF可以根据保存在TDF中的PFD检测应用。可以从本地操作管理流程(Operation and Management，O&M)获取PFD或从第三方业务提供商获取PFD。参见图1，从第三方业务提供商获取PFD，需要业务能力开放功能实体(Service Capability Exposure Function，SCEF)和分组流描述功能实体(Packet Flow Description Function，PFDF)参与。其中，第三方业务提供商通过SCEF可以获知或者使用3GPP网络提供业务和能力。PFDF可以保存第三方业务提供商提供的与一个应用标识相关的分组流描述PFD。PFDF提供PFD给PCEF和TDF。PFDF可以采用推送(Push)模式和拉取(Pull)模式向PCEF或TDF提供PFD。PCRF通过Nt接口与SCEF通信。PCRF通过Sd接口与TDF通信。SCEF通过Nu接口与PFDF通信。
发明内容
一种应用检测控制方法及装置，能够解决相关技术中PCRF无法根据PFD的改变进行策略调整，导致了针对用户正在访问的业务执行的策略和网络配置的策略不一致的问题。
一种应用检测控制方法，包括：
应用检测控制实体确定分组过滤器描述PFD被修改或被删除后，通知策略与计费规则功能实体PCRF所述PFD被修改或被删除，以使所述PCRF根据应用检测控制实体发送的所述PFD被修改或被删除的通知进行策略决策，其中，所述PFD用于检测应用。
可选的，所述应用检测控制实体确定分组过滤器描述PFD被修改或删除后，通知策略与计费规则功能实体PCRF所述PFD被修改或删除，包括：
所述应用检测控制实体确定存在至少一个会话激活了应用检测规则时，所述应用检测控制实体通知所述PCRF所述PFD被修改或被删除，其中，所述应用检测规则包括所述PFD对应的应用标识。
可选的，所述应用检测控制实体通知所述PCRF所述PFD被修改或删除的 步骤中，
若所述PFD被修改，则所述应用检测控制实体通知所述PCRF的消息中携带所述应用标识、PFD被修改指示、被修改的PFD的标识Id和被修改后的PFD中的至少一个；以及
若所述PFD被删除，则所述应用检测控制实体通知所述PCRF的消息中携带所述应用标识、所述PFD被删除的指示、被删除的PFD的Id和被删除的PFD中的至少一个。
可选的，所述PCRF根据应用检测控制实体发送的所述PFD被修改或被删除的通知进行策略决策，包括：
若所述PFD被修改，所述PCRF检查每一个网络互联协议连通接入网IP-CAN会话的上下文，并且分别将所述PFD修改前的取值和修改后的取值分别与所述PFD修改前所述应用检测控制实体上报的业务数据流描述进行比较；若修改前的PFD的取值与所述业务数据流描述匹配，且修改后的PFD的取值和所述业务数据流描述不匹配，则所述PCRF从IP-CAN会话的上下文中删除根据所述业务数据流描述制定的策略与计费控制PCC规则，其中，所述IP-CAN会话激活了包含所述应用标识的应用检测规则；以及，
若所述PFD被删除，所述PCRF检查每一个IP-CAN会话的上下文，并且将所述PFD的取值与所述PFD被删除之前所述应用检测控制实体上报的业务数据流描述进行比较；若所述PFD的取值与所述业务数据流描述匹配，则所述PCRF从IP-CAN会话的上下文中删除根据所述业务数据流描述制定的PCC规则。
可选的，所述应用检测控制实体确定所述PFD被修改或被删除后通知策略与计费规则功能实体PCRF所述PFD被修改或被删除之前，所述方法还包括：
所述应用检测控制实体从分组过滤器描述功能实体PFDF获取修改或删除PFD的指示。
可选的，所述应用检测控制实体为策略与计费执行功能实体PCEF或业务检测功能实体TDF。
一种应用检测控制方法，包括：
应用检测控制实体确定分组过滤器描述PFD被修改或删除后，通知策略与 计费规则功能实体PCRF应用停止或无效，以使所述PCRF根据应用检测控制实体发送的所述PFD被修改或被删除的通知进行策略决策，其中，所述PFD用于检测应用。
可选的，应用检测控制实体确定所述PFD被修改或被删除后通知所述PCRF应用停止或无效，包括：
所述应用检测功能实体检查每一个激活的且包含所述PFD对应的应用标识的应用检测规则；
若所述PFD被修改，且所述应用检测控制实体采用修改前的PFD的取值检测到应用，修改后的PFD的取值与所述应用的业务数据流描述不匹配，并且所述应用检测控制实体之前向所述PCRF上报所述应用的应用信息，则所述应用检测控制实体通知所述PCRF所述应用停止或无效；以及
若所述PFD被删除，所述应用检测控制实体采用被删除的PFD的取值检测到应用，且所述应用检测控制实体向PCRF上报所述应用的应用信息，则所述应用检测控制实体通知所述PCRF所述应用停止或无效。
可选的，所述的方法还包括：
若所述应用检测控制实体通知所述PCRF应用停止，则所述应用检测控制实体通知所述PCRF的消息中还携带PFD失效的原因值。
可选的，所述PCRF根据应用检测控制实体发送的所述PFD被修改或被删除的通知进行策略决策，包括：
所述PCRF删除根据所述应用信息制定的PCC规则。
可选的，所述的方法还包括，所述应用检测控制实体从分组过滤器描述功能实体PFDF获取修改或删除PFD的指示。
一种应用检测控制装置，包括：
确定模块，设置为确定分组过滤器描述PFD是否被修改或被删除，其中，所述PFD用于检测应用；以及
通知模块，设置为在所述PFD被修改或删除的情况下，通知策略计费规则功能实体PCRF所述PFD被修改或删除，以使所述PCRF根据应用检测控制实 体发送的所述PFD被修改或被删除的通知进行策略决策。
可选的，所述确定模块包括：
确定单元，设置为在确定存在至少一个会话激活了应用检测规则时，通过所述通知模块通知所述PCRF所述PFD被修改或被删除，其中，所述应用检测规则包括所述PFD对应的应用标识。
可选的，若所述PFD被修改，则在所述通知模块通知通知所述PCRF的消息中携带所述应用标识、所述PFD被修改的指示、被修改的PFD的标识和被修改后的PFD中的至少一个；以及，
若所述PFD被删除，则在所述通知模块通知通知所述PCRF的消息中携带所述应用标识、所述PFD被删除的指示、被删除的PFD的标识和被删除的PFD中的至少一个。
可选的，所述的装置还包括：
获取模块，设置为从分组过滤器描述功能实体PFDF获取修改或删除PFD的指示。
可选的，所述应用检测控制装置为策略和计费执行功能实体PCEF或业务检测功能实体TDF。
一种应用检测控制装置，包括：
确定模块，设置为确定分组过滤器描述PFD是否被修改或被删除，其中，所述PFD用于检测应用；以及
通知模块，设置为在PFD被修改或被删除的情况下，通知策略与计费规则功能实体PCRF所述应用停止或无效，以使所述PCRF根据应用检测控制实体发送的所述PFD被修改或被删除的通知进行策略决策。
可选的，所述的装置还包括：
检查模块，设置为检查每一个激活的且包含所述PFD对应的应用标识的应用检测规则；其中，所述通知模块还包括第一通知单元和第二通知单元，
所述第一通知单元设置为在所述PFD被修改，采用修改之前的PFD的取值检测到应用，修改后的PDF的取值与所述应用的业务数据流描述不匹配，并且 之前向所述PCRF上报所述应用的应用信息的情况下，通知所述PCRF所述应用停止或无效；以及
所述第二通知单元设置为在所述PFD被删除，采用被删除的PFD的取值检测到应用，且向PCRF上报所述应用的应用信息的情况下，通知所述PCRF所述应用停止或无效。
可选的，在通知所述应用停止的情况下，通知所述PCRF所述应用停止的消息中还携带PFD失效的原因值。
可选的，所述装置还包括：
获取模块，设置为从分组过滤器描述功能实体PFDF获取修改或删除PFD的指示。
可选的，所述应用检测控制装置为策略和计费执行功能实体PCEF或业务检测功能实体TDF。
一种策略与计费规则功能装置，包括：
接收模块，设置为接收应用检测控制实体发送的分组过滤器描述PFD被修改或被删除的通知，其中，所述通知是所述应用检测控制实体确定所述PFD被修改或删除后发送的，以及所述PFD用于检测应用；以及
策略决策模块，设置为根据所述通知进行策略决策。
可选的，所述策略决策模块包括：
第一策略决策单元，设置为在所述PFD被修改的情况下，检查每一个网络互联协议连通接入网IP-CAN会话的上下文，并且分别将所述PFD修改前的取值和修改后的取值分别与所述PFD修改前所述应用检测控制实体上报的业务数据流描述进行比较；若修改前的PFD的取值与所述业务数据流描述匹配，且修改后的PFD的取值和所述业务数据流描述不匹配，则从IP-CAN会话的上下文中删除根据所述业务数据流描述制定的策略与计费控制PCC规则，其中，所述IP-CAN会话激活了包含所述应用标识的应用检测规则；和，
第二策略决策单元，设置为在所述PFD被删除的情况下，检查每一个IP-CAN会话的上下文，并且将所述PFD的取值与所述PFD被删除之前所述应用检测控制实体上报的业务数据流描述进行比较，若所述PFD的取值与所述业务数据流 描述匹配，则从IP-CAN会话的上下文中删除根据所述业务数据流描述制定的PCC规则。
一种策略与计费规则功能装置，包括：
接收模块，设置为接收应用检测控制实体发送的应用停止或无效的通知，其中，所述通知是所述应用检测控制实体确定分组过滤器描述PFD被修改或删除后发送的，以及所述PFD用于检测应用；以及
策略决策模块，设置为根据所述通知进行策略决策。
可选的，在所述通知为所述应用停止的情况下，所述通知中还携带PFD失效的原因值。
可选的，所述的装置，还包括：
删除模块，设置为删除根据应用检测控制实体上报的应用信息制定的PCC规则。
一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行上述方法。
一种应用检测控制实体，包括：
至少一个处理器；以及
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器执行上述应用检测控制实体执行的方法。
一种策略与计费规则功能实体，包括：
至少一个处理器；以及
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器执行上述策略与计费规则功能实体执行的方法。
附图说明
图1是根据相关技术的PCC结构示意图；
图2为实施例1中应用检测控制方法的流程示意图；
图3为实施例2中应用检测控制方法的流程示意图；
图4为实施例3中应用检测控制方法的流程示意图；
图5为实施例4中应用检测控制方法的流程示意图；
图6为实施例5中应用检测控制装置的结构框图；
图7为实施例6中应用检测控制装置的结构框图；
图8为实施例7中策略与计费规则功能装置的结构框图；
图9为实施例8中策略与计费规则功能装置的结构框图；
图10为实施例9中应用检测控制实体的硬件结构示意图；以及
图11为实施例10中策略与计费规则功能实体的硬件结构示意图。
具体实施方式
第三方业务提供商可以通过SCEF或PFDF新增、更新或删除在PCEF或TDF上保存的应用标识的PFD。当PCEF或TDF根据第三方服务提供商提供的PFD检测到相应的应用时(即用应用标识表示)，则PCRF可以制定相应的策略。当更新或删除一个应用标识的PFD时，可能改变该应用标识对应的应用的一些策略。相关技术中，PCRF无法根据PFD的变化调整策略，导致用户正在访问的业务执行的策略和网络配置的策略不一致。
实施例1
在本实施例中，修改第三方应用(如，业务能力服务器(Service Capability Servers，SCS)或应用服务器(Application Server，AS)更新之前提供的一个或多个应用标识的PFD或删除第三方应用更新前提供的一个或多个应用标识的PFD。PCEF向PCRF发送PFD被修改或被删除的消息。步骤如图2所示。
步骤201中，第三方应用(如，SCS)向SCEF发送PFD管理请求消息，PFD管理请求消息中携带SCS标识，服务提供商(Service Provider，SP)参考标识，外部应用标识(Application Identifier)和请求修改的PFD或是请求删除的PFD。
如果第三方应用为AS，步骤201中的SCS标识替换为AS标识，AS可继续执行本实施例中的方法。
步骤202中，SCEF进行授权，并将外部应用标识(Application Identifier)转换成PFDF能够获知的应用标识(Application Identifier)。PFDF能够获知的应用标识可以是将外部应用标识转换成PFDF中要求格式的应用标识。
步骤203中，SCEF向PFDF发送PFD管理请求消息，该PFD管理请求消息中携带SCEF标识，SCEF参考标识，应用标识(Application Identifier)和请求修改的PFD或是请求删除的PFD。
步骤204中，PFDF保存接收到的信息。
步骤205中，PFDF向SCEF返回确认消息。
步骤206中，SCEF向第三方应用返回确认消息。
若PFDF采用Push模式向PCEF提供PFD，则执行步骤207a-208a；若PFDF采用Pull模式向PCEF提供PFD，则执行步骤207b-208b。
步骤207a中，PFDF向PCEF发送PFD更新或删除消息。
可选的，若PFDF请求修改PFD，PFDF在消息中携带应用标识(Application Identifier)、PFD修改的指示、请求修改的PFD的标识(Identifier，Id)以及新的PFD。
可选的，若PFDF请求删除PFD，则PFDF在消息中携带应用标识(Application Identifier)、PFD删除指示和请求删除的PFD的Id。
若PFDF请求修改一个应用标识(Application Identifier)的多个PFD，则消息中可以携带请求修改的PFD Id列表。若PFDF请求删除一个应用标识(Application Identifier)的多个PFD，则消息中可以携带请求删除的PFD的Id列表。
步骤208a中，PCEF保存接收到信息，并向PFDF返回确认消息。
若PFDF请求修改PFD，则PCEF将PFDF提供的PFD Id对应的新的PFD替换PFD Id对应的旧的PFD，并将PFDF提供的PFD Id绑定到应用标识(Application Identifier)。
若PFDF请求删除PFD，则PCEF将请求删除的PFD Id对应的PFD从应用标识(Application Identifier)对应的PFD列表中删除。
步骤207b中，应用标识(Application Identifier)的缓存定时器计时到预定 值时，PCEF向PFDF发送获取PFD的请求消息，获取PFD的请求消息中携带应用标识(Application Identifier)。
步骤208b中，PFDF向PCEF返回确认消息。
若应用标识(Application Identifier)对应的一个PFD的Id的PFD被修改，则PFDF在确认消息中携带应用标识(Application Identifier)、PFD修改的指示、修改的PFD的Id以及新的PFD。
若应用标识(Application Identifier)对应的一个PFD被删除，则确认消息中携带应用标识(Application Identifier)、删除PFD的指示以及删除的PFD的Id。
若应用标识(Application Identifier)对应的多个PFD被修改，则确认消息中会携带请求修改的PFD的Id列表。
若应用标识(Application Identifier)对应的多个PFD被删除，则确认消息中会携带请求修改的PFD的Id列表。
PCEF保存接收到的信息。若PFDF请求修改PFD，则PCEF将PFDF提供的PFD Id对应的新的PFD替换PFD Id对应的旧的PFD，并将PFDF提供的PFD Id对应的新的PFD绑定到应用标识(Application Identifier)。若PFDF请求删除PFD，则PCEF将请求删除的PFD的Id对应的PFD从应用标识(Application Identifier)对应的PFD列表中删除。PCEF向PFDF返回确认消息。
步骤209中，PCEF检测到存在至少一个网络互联协议连通接入网(IP-Connectivity Access Network，IP-CAN)会话激活了PCC规则，PCEF向PCRF发送PFD被修改或被删除的通知消息。其中，PCC规则包含应用标识(Application Identifier)以及PCC规则设置为检测应用。
若PFD被修改，则在通知消息中携带应用标识(Application Identifier)、PFD修改指示、被修改的PFD Id、被修改的PFD的取值以及被修改后的PFD的取值。
若PFD被删除，则通知消息中携带应用标识(Application Identifier)、PFD删除指示、被删除的PFD的Id以及被删除的PFD的取值。
步骤210中，PCRF保存PCEF上报的信息，返回确认消息。
步骤211中，PCRF进行策略决策。
若PFD被修改，PCRF检查每一个IP-CAN会话的上下文，并且分别将修改 前的PFD和修改后的PFD与之前PCEF上报的SDFD(Service data flow description，业务数据流描述)进行比较，其中，IP-CAN会话激活了包含应用标识的PCC规则。若修改前的PFD与SDFD匹配，而修改后的PFD与SDFD不匹配，则PCRF从该IP-CAN会话的上下文中删除根据之前PCEF上报的SDFD制定的PCC规则。若该IP-CAN会话存在BBERF，PCRF还可以删除对应的QoS规则。
若PFD被删除，PCRF检查每一个IP-CAN会话的上下文，将被删除的PFD和PFD被删除之前PCEF上报的SDFD进行比较，其中，IP-CAN会话激活了包含应用标识的PCC规则。若被删除的PFD和之前PCEF上报的SDFD匹配，则PCRF从该IP-CAN会话的上下文中删除根据之前PCEF上报的SDFD制定的PCC规则。若该IP-CAN会话存在BBERF，PCRF还可以删除对应的QoS规则
步骤212中，PCRF向PCEF发送策略和规则提供消息，删除相应的PCC规则，PCEF返回确认消息。PCEF删除PCC规则，并发起相应的流程(如，PCEF修改承载或删除承载)。
步骤213中，若步骤211中删除了QoS规则，PCRF将从BBERF中删除QoS规则，BBERF返回确认消息。BBERF删除QoS规则，并发起相应的流程。
实施例2
在本实施例中，第三方应用(如SCS或AS)更新之前提供的一个或多个应用标识的PFD或删除第三方应用更新前提供的一个或多个应用标识的PFD。PCEF向PCRF发送PFD被修改或被删除的消息。步骤如图3所示。
步骤301中，第三方应用(SCS)向SCEF发送PFD管理请求消息，PFD管理请求消息中携带SCS标识，服务提供商(Service Provider，SP)参考标识，外部应用标识(Application Identifier)和请求修改的PFD或是请求删除的PFD。
如果第三方应用为AS，步骤301中的SCS标识替换为AS标识，AS可继续执行本实施例中的方法。
步骤302中，SCEF进行授权，并将外部用标识(Application Identifier)转换成PFDF能够获知的应用标识(Application Identifier)。PFDF能够获知的应用标识可以是将外部应用标识转换成PFDF中要求格式的应用标识。
步骤303中，SCEF向PFDF发送PFD管理请求消息，该PFD管理请求消息中携带SCEF标识，SCEF参考标识，应用标识(Application Identifier)和请 求修改的PFD或是请求删除的PFD。
步骤304中，PFDF保存接收到的信息。
步骤305中，PFDF向SCEF返回确认消息。
步骤306中，SCEF向第三方应用返回确认消息。
若PFDF采用Push模式向PCEF提供PFD，则执行步骤307a-308a；若PFDF采用Pull模式向PCEF提供PFD，则执行步骤307b-308b。
步骤307a中，PFDF向PCEF发送PFD更新或删除消息。
可选的，若PFDF请求修改PFD，PFDF在消息中携带应用标识(Application Identifier)、PFD修改指示、请求修改的PFD的标识(Identifier，Id)以及新的PFD。
可选的，若PFDF请求删除PFD，则PFDF在消息中携带应用标识(Application Identifier)、PFD删除指示和请求删除的PFD的Id。
若PFDF请求修改一个应用标识(Application Identifier)的多个PFD，则消息中可以携带请求修改的PFD Id列表。若PFDF请求删除一个应用标识(Application Identifier)的多个PFD，则消息中可以携带请求删除的PFD的Id列表。
步骤308a中，PCEF保存接收到信息，并向PFDF返回确认消息。
若PFDF请求修改PFD，则PCEF将PFDF提供的PFD Id对应的新的PFD替换PFD Id对应的旧的PFD(被修改的PFD)，并将PFDF提供的PFD Id绑定到应用标识(Application Identifier)。
若PFDF请求删除PFD，则PCEF将请求删除的PFD Id对应的PFD从应用标识(Application Identifier)对应的PFD列表中删除。
步骤307b中，应用标识(Application Identifier)的缓存定时器计时到预定值时，PCEF向PFDF发送获取PFD的请求消息，获取PFD的请求消息中携带应用标识(Application Identifier)。
步骤308b中，PFDF向PCEF返回确认消息。
若应用标识(Application Identifier)对应的一个PFD的Id的PFD被修改，则PFDF在确认消息中携带应用标识(Application Identifier)、PFD修改的指示、修改的PFD的Id以及新的PFD。
若应用标识(Application Identifier)对应的一个PFD被删除，则确认消息 中携带应用标识(Application Identifier)、删除PFD的指示以及删除的PFD的Id。
若应用标识(Application Identifier)对应的多个PFD被修改，则确认消息中会携带请求修改的PFD的Id列表。
若应用标识(Application Identifier)对应的多个PFD被删除，则确认消息中会携带请求修改的PFD的Id列表。
PCEF保存接收到的信息。若PFDF请求修改PFD，则PCEF将PFDF提供的PFD Id对应的新的PFD替换PFD Id对应的旧的PFD，并将PFDF提供的PFD Id对应的新的PFD绑定到应用标识(Application Identifier)。若PFDF请求删除PFD，则PCEF将请求删除的PFD的Id对应的PFD从应用标识(Application Identifier)对应的PFD列表中删除。PCEF向PFDF返回确认消息。
步骤309中，PCEF检查每一IP-CAN会话(即IP-CAN会话的上下文)，其中，IP-CAN会话激活了包含应用标识的PCC规则。
若PFD被修改，PCEF采用旧的PFD(即修改前的PFD)检测到了对应的业务数据流，且新的PFD(即修改后的PFD)与业务数据流描述不匹配。若PCEF采用修改前的PFD检测到应用后，向PCRF上报采用修改前的PFD检测到的应用信息(该应用信息包括应用标识以及应用启动(Application Start)事件指示，还可以包括实例标识(Instance Id)和业务数据流描述信息)，则PCEF向PCRF发送事件报告消息，消息中携带应用标识和应用无效指示。若PCEF向PCRF发送事件报告消息之前的报告的应用信息中携带有实例标识，则消息中仍携带实例标识。
若PFD被删除，PCEF采用旧的PFD(被删除的PFD)检测到了对应的业务数据流。若PCEF采用旧的PFD检测到应用后，且向PCRF上报了采用该被删除的PFD检测到的应用信息(该应用信息中包括应用标识、应用启动(Application Start)事件指示、可选的实例标识(Instance Id)和流描述信息)，PCEF向PCRF发送事件上报消息，事件上报消息中携带应用标识和应用无效指示。若之前的报告的应用信息中携带有实例标识，则事件上报消息中仍携带实例标识。
在一实施例中，PCEF在上报的事件报告消息中携带应用更标识、应用停止指示、原因值以及PFD失效指示。若之前的报告的应用信息中携带有实例标 识，时间报告消息中仍携带实例标识。
步骤310中，PCRF保存PCEF上报的信息，返回确认消息。
步骤311中，PCRF进行策略决策。
PCRF从该IP-CAN会话的上下文中删除根据之前PCEF上报的SDFD制定的PCC规则。若该IP-CAN会话存在BBERF，PCRF还可以删除对应的QoS规则。
步骤312中，PCRF向PCEF发送策略和规则提供消息，删除相应的PCC规则，PCEF返回确认消息。PCEF删除PCC规则，并发起相应的流程。
步骤313中，PCRF将从BBERF删除QoS规则，BBERF返回确认消息。BBERF删除QoS规则，并发起相应的流程。
实施例3
在本实施例中，第三方应用(如SCS或AS)更新之前提供的一个或多个应用标识的PFD或删除第三方应用更新前提供的一个或多个应用标识的PFD。TDF向PCRF发送PFD被修改或被删除的消息。步骤如图4所示。
步骤401中，第三方应用(SCS)向SCEF发送PFD管理请求消息，PFD管理请求消息中携带SCS标识，SP参考标识，外部应用标识(Application Identifier)和请求修改的PFD或是请求删除的PFD。
如果第三方应用为AS，步骤401中的SCS标识替换为AS标识，AS可继续执行本实施例中的方法。
步骤402中，SCEF进行授权，并将外部应用标识(Application Identifier)转换成PFDF能够识别的应用标识(Application Identifier)。PFDF能够获知的应用标识可以是将外部应用标识转换成PFDF中要求格式的应用标识。
步骤403中，SCEF向PFDF发送PFD管理请求消息，该PFD管理请求消息中携带SCEF标识，SCEF参考标识，应用标识(Application Identifier)和请求修改的PFD或是请求删除的PFD。
步骤404中，PFDF保存接收到的信息。
步骤405中，PFDF向SCEF返回确认消息。
步骤406中，SCEF向第三方应用返回确认消息。
若PFDF采用Push模式向PCEF提供PFD，则执行步骤407a-408a；若PFDF 采用Pull模式向PCEF提供PFD，则执行步骤407b-408b。
步骤407a中，PFDF向TDF发送PFD更新或删除消息。
可选的，若PFDF请求修改PFD，PFDF在消息中携带应用标识(Application Identifier)、PFD修改指示、请求修改的PFD的标识(Identifier，Id)以及新的PFD。
可选的，若PFDF请求删除PFD，则PFDF在消息中携带应用标识(Application Identifier)、PFD删除指示和请求删除的PFD的Id。
若PFDF请求修改一个应用标识(Application Identifier)的多个PFD，则消息中可以携带请求修改的PFD Id列表。若PFDF请求删除一个应用标识(Application Identifier)的多个PFD，则消息中可以携带请求删除的PFD的Id列表。
步骤408a中，TDF保存接收到信息，并向PFDF返回确认消息。
若PFDF请求修改PFD，则TDF将PFDF提供的PFD Id对应的新的PFD替换PFD Id对应的旧的PFD，并将PFDF提供的PFD Id绑定到应用标识(Application Identifier)。
若PFDF请求删除PFD，则TDF将请求删除的PFD Id对应的PFD从应用标识(Application Identifier)对应的PFD列表中删除。
步骤407b中，应用标识(Application Identifier)的缓存定时器计时到预定值时，TDF向PFDF发送获取PFD的请求消息，获取PFD的请求消息中携带应用标识(Application Identifier)。
步骤408b中，PFDF向TDF返回确认消息。
若应用标识(Application Identifier)对应的一个PFD的Id的PFD被修改，则PFDF在确认消息中携带应用标识(Application Identifier)、PFD修改的指示、修改的PFD的Id以及新的PFD。
若应用标识(Application Identifier)对应的一个PFD被删除，则确认消息中携带应用标识(Application Identifier)、删除PFD的指示以及删除的PFD的Id。
若应用标识(Application Identifier)对应的多个PFD被修改，则确认消息中会携带请求修改的PFD的Id列表。
若应用标识(Application Identifier)对应的多个PFD被删除，则确认消息 中会携带请求修改的PFD的Id列表。
TDF保存接收到的信息。若PFDF请求修改PFD，则TDF将PFDF提供的PFD Id对应的新的PFD替换PFD Id对应的旧的PFD，并将PFDF提供的PFD Id对应的新的PFD绑定到应用标识(Application Identifier)。若PFDF请求删除PFD，则TDF将请求删除的PFD的Id对应的PFD从应用标识(Application Identifier)对应的PFD列表中删除。TDF向PFDF返回确认消息。
步骤409中，TDF检测到存在至少一个TDF会话激活了ADC规则，其中，ADC规则包含应用标识，以及ADC规则设置为检测应用。则TDF向PCRF发送PFD修改或删除通知消息。
若PFD被修改，则在通知消息中携带应用标识(Application Identifier)、PFD修改指示、被修改的PFD Id、被修改的PFD的取值以及被修改后的PFD的取值。
若PFD被删除，则通知消息中携带应用标识(Application Identifier)、PFD删除指示、被删除的PFD的Id以及被删除的PFD的取值。
步骤410中，PCRF保存TDF上报的信息，返回确认消息。
步骤411中，PCRF进行策略决策。
若PFD被修改，PCRF检查每一个IP-CAN会话的上下文(IP-CAN会话与TDF会话一一对应)，并且分别将新修改前的PFD和修改后的PFD与之前TDF上报的SDFD(Service data flow description，业务数据流描述)进行比较，ADC规则包含应用标识，IP-CAN会话激活了ADC规则。若修改前的PFD与SDFD匹配，而修改后的PFD与SDFD不匹配，则PCRF从该IP-CAN会话的上下文中删除根据之前PCEF上报的SDFD制定的PCC规则。若该IP-CAN会话存在BBERF，PCRF还可以删除对应的QoS规则。
若PFD被删除，PCRF检查每一个IP-CAN会话的上下文，将被删除的PFD和之前PCEF上报的SDFD进行比较，其中，IP-CAN会话激活了包含Application Id的PCC规则。若被删除的PFD和之前PCEF上报的SDFD匹配，则PCRF从该IP-CAN会话的上下文中删除根据之前PCEF上报的SDFD制定的PCC规则。若该IP-CAN会话存在BBERF，PCRF还可以删除对应的QoS规则。
步骤412中，PCRF向TDF发送策略和规则提供消息，删除对应的PCC规则，PCEF返回确认消息。PCEF删除PCC规则，并发起相应的流程。
步骤413中，PCRF将从BBERF中删除QoS规则，BBERF返回确认消息。BBERF删除QoS规则，并发起相应的流程。
实施例4
在本实施例中，第三方应用(如SCS或AS)更新之前提供的一个或多个应用标识的PFD或删除第三方应用更新前提供的一个或多个应用标识的PFD。TDF向PCRF发送PFD被修改或被删除的消息。步骤如图5所示。
步骤501中，第三方应用(SCS)向SCEF发送PFD管理请求消息，PFD管理请求消息中携带SCS标识，SP参考标识，外部应用标识(Application Identifier)和请求修改的PFD或是请求删除的PFD。
如果第三方应用为AS，步骤401中的SCS标识替换为AS标识，AS可继续执行本实施例中的方法。
步骤502中，SCEF进行授权，并将外部应用标识(Application Identifier)转换成PFDF能够识别的应用标识(Application Identifier)。PFDF能够获知的应用标识可以是将外部应用标识转换成PFDF中要求格式的应用标识。
步骤503中，SCEF向PFDF发送PFD管理请求消息，该PFD管理请求消息中携带SCEF标识，SCEF参考标识，应用标识(Application Identifier)和请求修改的PFD或是请求删除的PFD。
步骤504中，PFDF保存接收到的信息。
步骤505中，PFDF向SCEF返回确认消息。
步骤506中，SCEF向第三方应用返回确认消息。
若PFDF采用Push模式向TDF提供PFD，则执行步骤507a-508a；若PFDF采用Pull模式向TDF提供PFD，则执行步骤507b-508b。
步骤507a中，PFDF向TDF发送PFD更新或删除消息。
可选的，若PFDF请求修改PFD，PFDF在消息中携带应用标识(Application Identifier)、PFD修改指示、请求修改的PFD的标识(Identifier，Id)以及新的PFD。
可选的，若PFDF请求删除PFD，则PFDF在消息中携带应用标识(Application Identifier)、PFD删除指示和请求删除的PFD的Id。
若PFDF请求修改一个应用标识(Application Identifier)的多个PFD，则消 息中可以携带请求修改的PFD Id列表。若PFDF请求删除一个应用标识(Application Identifier)的多个PFD，则消息中可以携带请求删除的PFD的Id列表。
步骤508a中，TDF保存接收到信息，并向PFDF返回确认消息。
若PFDF请求修改PFD，则TDF将PFDF提供的PFD Id对应的新的PFD替换PFD Id对应的旧的PFD，并将PFDF提供的PFD Id绑定到应用标识(Application Identifier)。
若PFDF请求删除PFD，则TDF将请求删除的PFD Id对应的PFD从应用标识(Application Identifier)对应的PFD列表中删除。
步骤507b中，应用标识(Application Identifier)的缓存定时器计时到预定值时，TDF向PFDF发送获取PFD的请求消息，获取PFD的请求消息中携带应用标识(Application Identifier)。
步骤508b中，PFDF向TDF返回确认消息。
若应用标识(Application Identifier)对应的一个PFD的Id的PFD被修改，则PFDF在确认消息中携带应用标识(Application Identifier)、PFD修改的指示、修改的PFD的Id以及新的PFD。
若应用标识(Application Identifier)对应的一个PFD被删除，则确认消息中携带应用标识(Application Identifier)、删除PFD的指示以及删除的PFD的Id。
若应用标识(Application Identifier)对应的多个PFD被修改，则确认消息中会携带请求修改的PFD的Id列表。
若应用标识(Application Identifier)对应的多个PFD被删除，则确认消息中会携带请求修改的PFD的Id列表。
TDF保存接收到信息。若PFDF请求修改PFD，则TDF将PFDF提供的PFD Id对应的新的PFD替换PFD Id对应的旧的PFD，并将PFDF提供的PFD Id对应的新的PFD绑定到应用标识(Application Identifier)。若PFDF请求删除PFD，则TDF将请求删除的PFD的Id对应的PFD从应用标识(Application Identifier)对应的PFD列表中删除。TDF向PFDF返回确认消息。
步骤509中，TDF检查每一TDF会话(即与IP-CAN会话对应的TDF会话)。
若PFD被修改，TDF采用旧的PFD(即修改前的PFD)检测到了对应的业 务数据流描述，新的PFD(即修改后的PFD)与对应的业务数据流描述不匹配。若TDF采用修改前的PFD检测到应用后，向PCRF上报了采用该PFD检测到的应用信息(该应用信息中包括应用标识、应用启动事件指示、可选的实例标识(Instance Id)和业务数据流描述信息)，则TDF向PCRF发送事件报告消息，事件报告消息中携带应用标识和应用无效指示。若TDF向PCRF发送事件报告消息之前的报告的应用信息中携带了实例标识，则TDF向PCRF发送事件报告消息中仍携带实例标识。
若PFD被删除，TDF采用旧的PFD检测到了对应的业务数据流，且TDF采用旧的PFD检测到应用后，向PCRF上报了采用该PFD检测到的应用信息(该应用信息中包括应用标识，应用启动(Application Start)事件指示，可选的实例标识(Instance Id)和流描述信息)，则TDF向PCRF发送事件上报消息，事件上报消息中携带应用标识和应用无效指示。若TDF向PCRF发送事件上报消息之前的报告的应用信息中携带了实例标识，则TDF向PCRF发送的事件上报消息中仍携带实例标识。
在一实施例中，TDF在上报的事件报告消息中携带应用标识(Application Identifier)、应用(Application)停止指示、原因值以及PFD失效指示。若TDF向PCRF发送事件上报消息之前的报告的应用信息携带了实例标识，则事件上报消息中仍携带实例标识。
步骤510中，PCRF保存TDF上报的信息，返回确认消息。
步骤511中，PCRF进行策略决策。
PCRF从该IP-CAN会话的上下文中删除之前根据SDFD制定的PCC规则。若该IP-CAN会话存在BBERF，PCRF还可以删除对应的QoS规则。
步骤512中，PCRF向TDF发送策略和规则提供消息，删除对应的PCC规则，PCEF返回确认消息。PCEF删除PCC规则，并发起相应的流程。
步骤513中，PCRF从BBERF删除QoS规则，BBERF返回确认消息。BBERF删除QoS规则，并发起相应的流程。
通过以上的实施方式的描述，上述实施例的方法可借助软件加通用硬件平台的方式来实现，也可以通过硬件实现。上述技术方案可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟、 光盘)中，包括一个或多个指令用以使得一台终端设备(可以是手机、计算机、服务器或者网络设备)执行上述实施例中的方法。
实施例5
如图6所示，本实施例提供了一种应用检测控制装置，应用检测控制装置包括：第一确定模块60和第一通知模块61。
第一确定模块60设置为确定PFD是否被修改或被删除，其中，所述PFD用于检测应用。
第一通知模块61设置为在所述PFD被修改的情况下，通知策略计费规则功能实体PCRF所述PFD被修改，以及在所述PFD被删除的情况下，通知所述PCRF所述PFD被删除，以使所述PCRF根据应用检测控制实体发送的所述PFD被修改或被删除的通知进行策略决策。
可选的，第一确定模块60包括：确定单元601。
确定单元601设置为在确定存在至少一个会话激活了应用检测规则时，通过所述通知模块通知所述PCRF所述PFD被修改或删除，其中，所述应用检测规则包括所述PFD对应的应用标识。
可选的，若所述PFD被修改，则在所述通知模块通知通知所述PCRF的消息中携带所述应用标识、所述PFD被修改的指示、被修改的PFD的标识和被修改后的PFD中的至少一个。
可选的，若所述PFD被删除，则在所述通知模块通知通知所述PCRF的消息中携带所述应用标识、所述PFD被删除的指示、被删除的PFD的标识和被删除的PFD中的至少一个。
可选的，应用检测控制装置还包括：第一获取模块62。
第一获取模块62设置为从分组过滤器描述功能实体PFDF获取修改PFD的指示或删除PFD的指示。
可选的，所述应用检测控制装置为策略和计费执行功能实体PCEF或业务检测功能实体TDF。
实施例6
如图7所示，本实施例提供了一种应用检测控制装置。
应用检测控制装置包括：第二确定模块70和第二通知模块71。
第二确定模块70设置为确定分组过滤器描述PFD是否被修改或被删除，其 中，所述PFD用于检测应用。
第二通知模块71设置为在PFD被修改或被删除的情况下，通知策略与计费规则功能实体PCRF所述应用停止或无效，以使所述PCRF根据应用检测控制实体发送的所述PFD被修改或被删除的通知进行策略决策。
可选的，应用检测控制装置还包括：检查模块72。
检查模块72设置为检查每一个激活的且包含所述PFD对应的应用标识的应用检测规则。第二通知模块71包括第一通知单元711和第二通知单元712。
第一通知单元711设置为在所述PFD被修改，采用修改之前的PFD的取值检测到应用，修改后的PDF的取值与所述应用的业务数据流描述不匹配，并且之前向所述PCRF上报所述应用的应用信息的情况下，通知所述PCRF所述应用停止或无效。
第二通知单元712设置为在所述PFD被删除，采用被删除的PFD的取值检测到应用，且向PCRF上报所述应用的应用信息的情况下，通知所述PCRF所述应用停止或无效。
可选的，在通知所述应用停止的情况下，通知所述PCRF所述应用停止的消息中还携带PFD失效的原因值。
可选的，上述装置还包括第二获取模块73。
第二获取模块73设置为从分组过滤器描述功能实体PFDF获取修改PFD的指示或删除PFD的指示。
可选的，所述应用检测控制装置为策略和计费执行功能实体PCEF或业务检测功能实体TDF。
实施例7
如图8所示，本实施例提供了一种策略与计费规则功能装置，策略与计费规则功能装置包括：第一接收模块80和第一策略决策模块81。
第一接收模块80设置为接收应用检测控制实体发送的分组过滤器描述PFD被修改或被删除的通知，其中，所述通知是所述应用检测控制实体确定所述PFD被修改或删除后发送的，以及所述PFD用于检测应用。
第一策略决策模块81设置为根据所述通知进行策略决策。
可选的，第一策略决策模块81包括：第一策略决策单元811和第二策略决策单元812。
第一策略决策单元811设置为在所述PFD被修改的情况下，检查每一个IP-CAN会话的上下文，并且分别将所述PFD修改前的取值和修改后的取值分别与所述PFD修改前所述应用检测控制实体上报的业务数据流描述进行比较；若修改前的PFD的取值与所述业务数据流描述匹配，且修改后的PFD的取值和所述业务数据流描述不匹配，则从IP-CAN会话的上下文中删除根据所述业务数据流描述制定的策略与计费控制PCC规则，其中，所述IP-CAN会话激活了包含所述应用标识的应用检测规则。
第二策略决策单元812设置为在所述PFD被删除的情况下，检查每一个IP-CAN会话的上下文，并且将所述PFD的取值与所述PFD被删除之前所述应用检测控制实体上报的业务数据流描述进行比较，若所述PFD的取值与所述业务数据流描述匹配，则从IP-CAN会话的上下文中删除根据所述业务数据流描述制定的PCC规则。
实施例8
参见图9，本实施例提供了一种策略与计费规则功能装置，该策略与计费规则功能装置包括：第二接收模块90和第二策略决策模块91。
第二接收模块90设置为接收应用检测控制实体发送的应用停止或无效的通知，其中，所述通知是所述应用检测控制实体确定分组过滤器描述PFD被修改或删除后发送的，以及所述PFD用于检测应用。
第二策略决策模块91设置为根据所述通知进行策略决策。
可选的，在所述通知为所述应用停止的情况下，所述通知中还携带PFD失效的原因值。
可选的，策略与计费规则功能装置还包括删除模块92。
删除模块92设置为删除根据应用检测控制实体上报的应用信息制定的PCC规则。
实施例9
本实施例提供了一种应用检测控制实体的硬件结构示意图。参见图10，该应用检测控制实体包括：
至少一个处理器(processor)100，图10中以一个处理器100为例；存储器(memory)101；还可以包括通信接口(Communications Interface)102和总线103。其中，处理器100、存储器101以及通信接口102可以通过总线103完成 相互间的通信。处理器100可以调用存储器101中的逻辑指令，以执行上述实施例中应用检测控制实体执行的方法。
此外，上述的存储器101中的逻辑指令可以通过软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。
存储器101作为一种计算机可读存储介质，可用于存储软件程序、计算机可执行程序，如上述实施例中应用检测控制实体执行的方法对应的程序指令或模块。处理器100通过运行存储在存储器101中的软件程序、指令或模块，从而执行功能应用以及数据处理，即实现上述实施例中应用检测控制实体执行的方法。
存储器101可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据终端设备的使用所创建的数据等。此外，存储器101可以包括高速随机存取存储器，还可以包括非易失性存储器。
实施例10
本实施例提供了一种应用检测控制实体的硬件结构示意图。参见图11，该应用检测控制实体包括：
至少一个处理器(processor)110，图11中以一个处理器110为例；存储器(memory)111；还可以包括通信接口(Communications Interface)112和总线113。其中，处理器110、存储器111以及通信接口112可以通过总线113完成相互间的通信。处理器110可以调用存储器111中的逻辑指令，以执行上述实施例中策略与计费规则功能实体执行的方法。
此外，上述的存储器111中的逻辑指令可以通过软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。
存储器111作为一种计算机可读存储介质，可用于存储软件程序、计算机可执行程序，如上述实施例中策略与计费规则功能实体执行的方法对应的程序指令或模块。处理器110通过运行存储在存储器111中的软件程序、指令或模块，从而执行功能应用以及数据处理，即实现上述实施例中策略与计费规则功能实体执行的方法。
存储器111可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据终端设备的使 用所创建的数据等。此外，存储器111可以包括高速随机存取存储器，还可以包括非易失性存储器。
一实施例提供了一种应用检测控制系统，该系统设置为实现上述实施例。
以上技术方案可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括一个或多个指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行上述实施例所述方法的全部或部分步骤。
一实施例提供了一种存储设置为执行上述实施例的流程步骤的程序代码存储介质。可选地，上述存储介质可以被设置为存储用于执行上述任一方法实施例中步骤的程序代码。该存储介质可以是非暂态计算机可读存储介质。
可选地，上述存储介质可以包括但不限于：U盘、ROM、RAM、移动硬盘、磁碟或者光盘等多种可以存储程序代码的介质。
上述实施例中的多个模块或多个步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上。可选地，上述实施例中的多个模块或多个步骤可以用计算装置可执行的程序代码来实现。可以将上述实施例中的多个模块或多个步骤存储在存储装置中由计算装置来执行，并且在一些情况下，可以以不同于上述实施例中的顺序执行所示出或描述的步骤，或者将上述实施例中的多个模块或多个步骤分别制作成多个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块。
工业实用性
应用检测控制方法和装置能够解决相关技术中PCRF无法根据PFD的变化调整策略，导致用户正在访问的业务执行的策略和网络配置的策略不一致的问题。

Claims (27)

  1. 一种应用检测控制方法，包括：
    应用检测控制实体确定分组过滤器描述PFD被修改或被删除后，通知策略与计费规则功能实体PCRF所述PFD被修改或被删除，以使所述PCRF根据应用检测控制实体发送的所述PFD被修改或被删除的通知进行策略决策，其中，所述PFD用于检测应用。
  2. 根据权利要求1所述的方法，其中，所述应用检测控制实体确定分组过滤器描述PFD被修改或删除后，通知策略与计费规则功能实体PCRF所述PFD被修改或删除，包括：
    所述应用检测控制实体确定存在至少一个会话激活了应用检测规则时，所述应用检测控制实体通知所述PCRF所述PFD被修改或被删除，其中，所述应用检测规则包括所述PFD对应的应用标识。
  3. 根据权利要求2所述的方法，其中，所述应用检测控制实体通知所述PCRF所述PFD被修改或删除的步骤中，
    若所述PFD被修改，则所述应用检测控制实体通知所述PCRF的消息中携带所述应用标识、PFD被修改指示、被修改的PFD的标识Id和被修改后的PFD中的至少一个；以及
    若所述PFD被删除，则所述应用检测控制实体通知所述PCRF的消息中携带所述应用标识、所述PFD被删除的指示、被删除的PFD的Id和被删除的PFD中的至少一个。
  4. 根据权利要求3所述的方法，其中，所述PCRF根据应用检测控制实体发送的所述PFD被修改或被删除的通知进行策略决策，包括：
    若所述PFD被修改，所述PCRF检查每一个网络互联协议连通接入网 IP-CAN会话的上下文，并且分别将所述PFD修改前的取值和修改后的取值分别与所述PFD修改前所述应用检测控制实体上报的业务数据流描述进行比较；若修改前的PFD的取值与所述业务数据流描述匹配，且修改后的PFD的取值和所述业务数据流描述不匹配，则所述PCRF从IP-CAN会话的上下文中删除根据所述业务数据流描述制定的策略与计费控制PCC规则，其中，所述IP-CAN会话激活了包含所述应用标识的应用检测规则；以及，
    若所述PFD被删除，所述PCRF检查每一个IP-CAN会话的上下文，并且将所述PFD的取值与所述PFD被删除之前所述应用检测控制实体上报的业务数据流描述进行比较；若所述PFD的取值与所述业务数据流描述匹配，则所述PCRF从IP-CAN会话的上下文中删除根据所述业务数据流描述制定的PCC规则。
  5. 根据权利要求1所述的方法，所述应用检测控制实体确定所述PFD被修改或被删除后通知策略与计费规则功能实体PCRF所述PFD被修改或被删除之前，所述方法还包括：
    所述应用检测控制实体从分组过滤器描述功能实体PFDF获取修改或删除PFD的指示。
  6. 根据权利要求1所述的方法，其中，所述应用检测控制实体为策略与计费执行功能实体PCEF或业务检测功能实体TDF。
  7. 一种应用检测控制方法，包括：
    应用检测控制实体确定分组过滤器描述PFD被修改或删除后，通知策略与计费规则功能实体PCRF应用停止或无效，以使所述PCRF根据应用检测控制实体发送的所述PFD被修改或被删除的通知进行策略决策，其中，所述PFD用于检测应用。
  8. 根据权利要求7所述的方法，其中，应用检测控制实体确定所述PFD被修改或被删除后通知所述PCRF应用停止或无效，包括：
    所述应用检测功能实体检查每一个激活的且包含所述PFD对应的应用标识的应用检测规则；
    若所述PFD被修改，且所述应用检测控制实体采用修改前的PFD的取值检测到应用，修改后的PFD的取值与所述应用的业务数据流描述不匹配，并且所述应用检测控制实体之前向所述PCRF上报所述应用的应用信息，则所述应用检测控制实体通知所述PCRF所述应用停止或无效；以及
    若所述PFD被删除，所述应用检测控制实体采用被删除的PFD的取值检测到应用，且所述应用检测控制实体向PCRF上报所述应用的应用信息，则所述应用检测控制实体通知所述PCRF所述应用停止或无效。
  9. 根据权利要求7所述的方法，还包括：
    若所述应用检测控制实体通知所述PCRF应用停止，则所述应用检测控制实体通知所述PCRF的消息中还携带PFD失效的原因值。
  10. 根据权利要求8所述的方法，其中，所述PCRF根据应用检测控制实体发送的所述PFD被修改或被删除的通知进行策略决策，包括：
    所述PCRF删除根据所述应用信息制定的PCC规则。
  11. 根据权利要求7所述的方法，还包括，所述应用检测控制实体从分组过滤器描述功能实体PFDF获取修改或删除PFD的指示。
  12. 一种应用检测控制装置，包括：
    确定模块，设置为确定分组过滤器描述PFD是否被修改或被删除，其中，所述PFD用于检测应用；以及
    通知模块，设置为在所述PFD被修改或删除的情况下，通知策略计费规则功能实体PCRF所述PFD被修改或删除，以使所述PCRF根据应用检测控制实体发送的所述PFD被修改或被删除的通知进行策略决策。
  13. 根据权利要求12所述的装置，其中，所述确定模块包括：
    确定单元，设置为在确定存在至少一个会话激活了应用检测规则时，通过所述通知模块通知所述PCRF所述PFD被修改或删除，其中，所述应用检测规则包括所述PFD对应的应用标识。
  14. 根据权利要求13所述的装置，其中，
    若所述PFD被修改，则在所述通知模块通知通知所述PCRF的消息中携带所述应用标识、所述PFD被修改的指示、被修改的PFD的标识和被修改后的PFD中的至少一个；以及，
    若所述PFD被删除，则在所述通知模块通知通知所述PCRF的消息中携带所述应用标识、所述PFD被删除的指示、被删除的PFD的标识和被删除的PFD中的至少一个。
  15. 根据权利要求12-14任一项所述的装置，还包括：
    获取模块，设置为从分组过滤器描述功能实体PFDF获取修改或删除PFD的指示。
  16. 根据权利要求15的装置，其中，
    所述应用检测控制装置为策略和计费执行功能实体PCEF或业务检测功能实体TDF。
  17. 一种应用检测控制装置，包括：
    确定模块，设置为确定分组过滤器描述PFD是否被修改或被删除，其中， 所述PFD用于检测应用；以及
    通知模块，设置为在PFD被修改或被删除的情况下，通知策略与计费规则功能实体PCRF所述应用停止或无效，以使所述PCRF根据应用检测控制实体发送的所述PFD被修改或被删除的通知进行策略决策。
  18. 根据权利要求17所述的装置，还包括：
    检查模块，设置为检查每一个激活的且包含所述PFD对应的应用标识的应用检测规则；其中，所述通知模块还包括第一通知单元和第二通知单元，
    所述第一通知单元设置为在所述PFD被修改，采用修改之前的PFD的取值检测到应用，修改后的PDF的取值与所述应用的业务数据流描述不匹配，并且之前向所述PCRF上报所述应用的应用信息的情况下，通知所述PCRF所述应用停止或无效；以及
    所述第二通知单元设置为在所述PFD被删除，采用被删除的PFD的取值检测到应用，且向PCRF上报所述应用的应用信息的情况下，通知所述PCRF所述应用停止或无效。
  19. 根据权利要求18所述的装置，其中，在通知所述应用停止的情况下，通知所述PCRF所述应用停止的消息中还携带PFD失效的原因值。
  20. 根据权利要求17-19任一项所述的装置，还包括：
    获取模块，设置为从分组过滤器描述功能实体PFDF获取修改或删除PFD的指示。
  21. 根据权利要求20所述的装置，其中，
    所述应用检测控制装置为策略和计费执行功能实体PCEF或业务检测功能实体TDF。
  22. 一种策略与计费规则功能装置，包括：
    接收模块，设置为接收应用检测控制实体发送的分组过滤器描述PFD被修改或被删除的通知，其中，所述通知是所述应用检测控制实体确定所述PFD被修改或删除后发送的，以及所述PFD用于检测应用；以及
    策略决策模块，设置为根据所述通知进行策略决策。
  23. 根据权利要求22所述的装置，其中，所述策略决策模块包括：
    第一策略决策单元，设置为在所述PFD被修改的情况下，检查每一个网络互联协议连通接入网IP-CAN会话的上下文，并且分别将所述PFD修改前的取值和修改后的取值分别与所述PFD修改前所述应用检测控制实体上报的业务数据流描述进行比较；若修改前的PFD的取值与所述业务数据流描述匹配，且修改后的PFD的取值和所述业务数据流描述不匹配，则从IP-CAN会话的上下文中删除根据所述业务数据流描述制定的策略与计费控制PCC规则，其中，所述IP-CAN会话激活了包含所述应用标识的应用检测规则；和，
    第二策略决策单元，设置为在所述PFD被删除的情况下，检查每一个IP-CAN会话的上下文，并且将所述PFD的取值与所述PFD被删除之前所述应用检测控制实体上报的业务数据流描述进行比较，若所述PFD的取值与所述业务数据流描述匹配，则从IP-CAN会话的上下文中删除根据所述业务数据流描述制定的PCC规则。
  24. 一种策略与计费规则功能装置，包括：
    接收模块，设置为接收应用检测控制实体发送的应用停止或无效的通知，其中，所述通知是所述应用检测控制实体确定分组过滤器描述PFD被修改或删除后发送的，以及所述PFD用于检测应用；以及
    策略决策模块，设置为根据所述通知进行策略决策。
  25. 根据权利要求24所述的装置，其中，在所述通知为所述应用停止的情况下，所述通知中还携带PFD失效的原因值。
  26. 根据权利要求25所述的装置，还包括：
    删除模块，设置为删除根据应用检测控制实体上报的应用信息制定的PCC规则。
  27. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行权利要求1-11中任一项的方法。
PCT/CN2017/109729 2016-11-07 2017-11-07 应用检测控制方法及装置 WO2018082707A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610986511.4A CN108064032A (zh) 2016-11-07 2016-11-07 一种应用检测控制方法及装置
CN201610986511.4 2016-11-07

Publications (1)

Publication Number Publication Date
WO2018082707A1 true WO2018082707A1 (zh) 2018-05-11

Family

ID=62076733

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/109729 WO2018082707A1 (zh) 2016-11-07 2017-11-07 应用检测控制方法及装置

Country Status (2)

Country Link
CN (1) CN108064032A (zh)
WO (1) WO2018082707A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019184680A1 (zh) * 2018-03-30 2019-10-03 华为技术有限公司 一种策略控制的方法、网元及系统
CN110830387A (zh) * 2018-08-10 2020-02-21 中国移动通信有限公司研究院 一种pfd发送失败的处理方法、装置、设备及介质
WO2020164226A1 (en) * 2019-02-15 2020-08-20 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for traffic detection
CN112020100A (zh) * 2019-05-31 2020-12-01 华为技术有限公司 分组流描述信息的管理方法、设备及系统
CN113169884A (zh) * 2018-11-21 2021-07-23 瑞典爱立信有限公司 移除应用标识符

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110768810B (zh) * 2018-07-25 2021-03-30 华为技术有限公司 确定报文流描述的方法、装置和系统
CN113873453B (zh) * 2020-06-29 2022-11-18 华为技术有限公司 通信方法、装置、系统及介质
WO2023274366A1 (en) * 2021-07-01 2023-01-05 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for setting up session with required quality of service

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102625272A (zh) * 2011-01-31 2012-08-01 中兴通讯股份有限公司 一种支持流检测功能的用量监控方法及系统
WO2016173364A1 (zh) * 2015-04-29 2016-11-03 中兴通讯股份有限公司 策略规则制定方法、系统及装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102625272A (zh) * 2011-01-31 2012-08-01 中兴通讯股份有限公司 一种支持流检测功能的用量监控方法及系统
WO2016173364A1 (zh) * 2015-04-29 2016-11-03 中兴通讯股份有限公司 策略规则制定方法、系统及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE: "Pull And Push Mode For PFD Management For Key", SA WG2 MEETING#114 S 2-161749, 15 April 2016 (2016-04-15), XP051086713 *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019184680A1 (zh) * 2018-03-30 2019-10-03 华为技术有限公司 一种策略控制的方法、网元及系统
US11233666B2 (en) 2018-03-30 2022-01-25 Huawei Technologies Co., Ltd. Policy control method, network element, and system
CN110830387A (zh) * 2018-08-10 2020-02-21 中国移动通信有限公司研究院 一种pfd发送失败的处理方法、装置、设备及介质
CN113169884A (zh) * 2018-11-21 2021-07-23 瑞典爱立信有限公司 移除应用标识符
US11849351B2 (en) 2018-11-21 2023-12-19 Telefonaktiebolaget Lm Ericsson (Publ) Removal of application identifier
CN113169884B (zh) * 2018-11-21 2023-12-26 瑞典爱立信有限公司 移除应用标识符
WO2020164226A1 (en) * 2019-02-15 2020-08-20 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for traffic detection
US11750523B2 (en) 2019-02-15 2023-09-05 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for traffic detection
CN112020100A (zh) * 2019-05-31 2020-12-01 华为技术有限公司 分组流描述信息的管理方法、设备及系统

Also Published As

Publication number Publication date
CN108064032A (zh) 2018-05-22

Similar Documents

Publication Publication Date Title
WO2018082707A1 (zh) 应用检测控制方法及装置
EP3780682B1 (en) Method and device for subscribing to service
EP2239884B1 (en) Pcc rules updating method, device and system
CN110324800B (zh) 一种策略控制的方法、网元及系统
CN101583112B (zh) 会话信息的标识方法及装置
US11563649B2 (en) NF service consumer restart detection using direct signaling between NFs
US20140003225A1 (en) Dynamic reaction to diameter routing failures
US20090203356A1 (en) Method, system and apparatus for locking information
CN106304195B (zh) 第三方应用的策略控制方法、scef和pcrf
WO2017173941A1 (zh) 服务质量QoS策略的处理方法、装置及系统
US10103943B2 (en) Network topology hiding method and device
US8787382B2 (en) Per-peer request delivery timeouts
US8737202B2 (en) Automatic connection recovery
US20110320584A1 (en) Method for determining a pcc rule waiting for pcef action
CN103856968B (zh) Gx接口故障后PCC规则获取的方法及装置
WO2020048532A1 (zh) Gx会话异常的处理方法及装置
WO2011063559A1 (zh) 控制机器类型通信mtc终端行为的方法、装置和系统
WO2017107563A1 (zh) 进出区域监控的处理方法及装置
US20080184261A1 (en) Method for re-enabling a disabled capability of a terminal and a device management system for the same
WO2018201810A1 (zh) Pcrf实体、存储介质、竞态条件解除方法及系统
US20170026524A1 (en) Charging method and apparatus
EP4035309A1 (en) Communications network architecture
WO2016062061A1 (zh) 一种网元间同步策略规则的方法及设备
US20230379261A1 (en) Pfd management method, network element and computer-readable storage medium
WO2023016400A1 (en) Method and apparatus for session restoration

Legal Events

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

Ref document number: 17866999

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17866999

Country of ref document: EP

Kind code of ref document: A1