WO2013166625A1 - 一种检测报告上报方法、报告上报*** - Google Patents

一种检测报告上报方法、报告上报*** Download PDF

Info

Publication number
WO2013166625A1
WO2013166625A1 PCT/CN2012/000635 CN2012000635W WO2013166625A1 WO 2013166625 A1 WO2013166625 A1 WO 2013166625A1 CN 2012000635 W CN2012000635 W CN 2012000635W WO 2013166625 A1 WO2013166625 A1 WO 2013166625A1
Authority
WO
WIPO (PCT)
Prior art keywords
report
reporting
application
tdf
mode
Prior art date
Application number
PCT/CN2012/000635
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 华为技术有限公司
Priority to PCT/CN2012/000635 priority Critical patent/WO2013166625A1/zh
Priority to CN201280001395.6A priority patent/CN103518392B/zh
Publication of WO2013166625A1 publication Critical patent/WO2013166625A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/02Capturing of monitoring data
    • H04L43/028Capturing of monitoring data by filtering

Definitions

  • the present invention belongs to the field of network technologies, and in particular, to a detection report reporting method and a report reporting system. Background technique
  • the Policy and Charging Rules Function indicates to the TDF the application type Application s that needs to detect the data.
  • the TDF detects the data flow of the application type based on the granularity of the application instance of the application type.
  • the report includes the start and end times of the data streams corresponding to the application instances, and the flow descriptions of all the data streams. Therefore, as the multimedia applications of the mobile terminals continue to increase, the application instances of the same application type are gradually increased, and these differences are The corresponding data flow of the application instance may start and end frequently. Then the TDF needs to report the report of each application instance frequently to the PCRF, including the start time, the end time, and the flow description. Obviously, so many report information is occupied. Multiple system resources, reducing network performance. Summary of the invention It is an object of the present invention to provide a report reporting method for a data stream detection function TDF, which aims to solve the technical problem of network performance degradation.
  • a method for reporting a test report is provided, including:
  • the TDF obtains the reporting method corresponding to the type of application to be detected, and generates a detection report of the corresponding mode.
  • the TDF reports the detection report to the policy and charging rule function PCRF.
  • the PCRF combines the local service shield control charging policy to determine the reporting mode corresponding to the application type that needs to be detected, and adds the reporting mode field to the application detection control rule to generate an enhanced application detection control rule.
  • the PCRF sends a session request to the data stream detection function TDF, where the session request includes the enhanced application detection control rule, so that the TDF can generate a detection report of the corresponding mode according to the report mode information included in the enhanced application detection control rule;
  • the PCRF receives the detection report sent by the TDF.
  • a TDF including:
  • a report generating unit configured to acquire a reporting manner corresponding to the type of the application to be detected, and generate a detection report of the corresponding mode
  • the report sending unit is configured to report the detection report generated by the report generating unit to the policy and charging function PCRF.
  • a PCRF comprising:
  • a rule generating unit configured to combine a local QoS policy and/or a charging policy, determine a reporting manner corresponding to an application type that needs to be detected, and add the reporting mode field to the application detection control rule to generate an enhanced type Apply detection control rules;
  • a session sending unit configured to send a session request to the data flow detecting function TDF, where the session request includes an enhanced application detection control rule generated by the rule generating unit;
  • a report receiving unit configured to send, by the TDF, a session request sent according to a session sending unit
  • the included report mode information generates a test report corresponding to the mode.
  • a report reporting system comprising the TDF of claims 11-16 and the PCRF of claims 17-20.
  • the TDF obtains and knows the upper 4 ⁇ mode corresponding to the type of the detection application by a certain method, for example, the above method can be sent by the PCRF, or It is stored in the local TDF.
  • Different application types may have different reporting modes.
  • This allows the TDF to use the appropriate reporting method according to the actual requirements.
  • the TDF reporting method is fixed, and the data needs to be reported every time. The start time, the end time, and the flow description of the flow, so much report information occupies too much system resources.
  • the TDF provided by the present invention can use the appropriate reporting method according to actual needs, and report the required report information at an appropriate time. It reduces the reporting frequency and the reported data volume, improves the efficiency of data flow detection and reporting, and helps to rationally utilize network resources.
  • 1 is a flowchart of a method for reporting report detection according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for reporting report detection according to another embodiment of the present invention
  • FIG. 3 is a time chart of four application examples of an application type
  • FIG. 4 is a flowchart of a method for reporting report detection according to another embodiment of the present invention
  • FIG. 5 is a flowchart of a method for reporting report detection according to another embodiment of the present invention
  • FIG. 6 is another embodiment of the present invention
  • FIG. 7 is an interaction flowchart of a report reporting method according to another embodiment of the present invention
  • FIG. 8 is a report reporting method according to another embodiment of the present invention
  • Figure 9 is a block diagram showing the structure of a TDF according to another embodiment of the present invention.
  • FIG. 10 is a structural block diagram of a TDF according to another embodiment of the present invention.
  • FIG. 11 is a block diagram showing the structure of a TDF according to another embodiment of the present invention.
  • FIG. 12 is a structural block diagram of a PCRF according to another embodiment of the present invention. detailed description
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • FIG. 1 is a flowchart of a method for reporting a report report according to an embodiment of the present invention. For the convenience of description, only parts related to the embodiment of the present invention are shown.
  • the TDF obtains a reporting manner corresponding to the type of the application to be detected, and generates a detection report of the corresponding mode.
  • the TDF obtains the corresponding reporting manner of the application type that needs to be detected, and different application types may have different reporting manners, and the specific reporting manner is based on which control strategy is adopted for the application type data. / or the accounting policy determines, in short, the purpose of this step is to take appropriate reporting methods according to the actual situation of different application types, to meet the control charging requirements for this application type data.
  • TDF has also known the format of the detection report corresponding to different reporting methods, and the TDF can produce the detection report of the corresponding mode according to the information of the reporting mode.
  • the TDF reports the detection report to the PCRF.
  • test report may consist of multiple sub-reports, such as start 4 report and end report, and update report.
  • the information of the report mode obtained by the TDF is determined by the PCR according to the actual situation, and the information content of the test report reported by the TDF to the PCRF is no longer fixed, and the content that the PCRF needs to know is reported at an appropriate time.
  • the overall report reduction is reduced and the network performance is improved.
  • FIG. 2 is a flowchart of a report reporting method of a data stream detecting function TDF according to another embodiment of the present invention. For the convenience of description, only parts related to the embodiment of the present invention are shown.
  • S201 Receive a session request sent by the PCRF, where the session request carries an enhanced application detection control rule, and the report mode information is obtained according to the report mode field in the enhanced application detection control rule.
  • the PCRF sends a session request to the TDF, where the session request includes an enhanced ADC (Application Detection Control) rule, where the enhanced ADC rule includes a report mode for detecting application type data.
  • the existing ADC rules include: an ADC Rule identifier, an Application ID, and an optional Enforcement Control, which indicates that the PCRF indicates TDF to the application.
  • the action taken by the data stream of the application type identified by the ID usually includes the state of the truncated data stream (gate status), the UL-maximum bit rate, and the DL-maximum bit rate. Redirect operation (Redirect), etc.
  • the field information of the reporting mode is added to the ADC rule to generate an enhanced ADC rule.
  • the TDF can be known according to the application ID field in the enhanced ADC rule. What type of application is required for the data to be detected, such as P2P applications, http applications, Voip applications, and so on.
  • the PCRF determines a local QoS policy and/or a charging policy to be used according to the application type. 3, etc. represent the reporting mode 1, the reporting mode 2, the reporting mode 3, etc., of course, the reporting mode may also be a numeric type value, for example, the number 0 can be used to represent the reporting mode 1, and the number 4 is the reporting mode 2, the number 7 The report mode 3 or the like, or the report mode is also a value of a character type.
  • the character a can be used to represent the report mode 1, the character b is the report mode 2, the character c is the report mode 3, etc., it can be understood that No matter what kind of logo is used to represent the reporting method, Both the PCRF and the TDF have a common understanding and understanding of this identifier, and know the specific reporting method represented by the Reporting mode field value.
  • the detection report generated by the reporting manner includes at least one of the following information:
  • the start report or the end report of the data flow is reported by the application type Application ID granularity, or by the application instance Application instance granularity;
  • the data flow detection reports the hysteresis time value.
  • reporting methods For the sake of understanding, you can specify several types of reporting methods.
  • the application type that needs to be detected is a P2P application.
  • the corresponding reporting methods and reporting contents are as follows: :
  • the PCRF does not need to know any data flow description information, mode 5, and the TDF detection corresponding P2P application start end time point information. Only the data flow of the TDF execution phase is required, and the action of the ADC rule indication (such as limiting bandwidth, blocking, etc.) is performed (restricted, blocking etc), and no report can be sent to the PCRF.
  • the ADC rule indication such as limiting bandwidth, blocking, etc.
  • the PCRF hopes that the TDF will detect the target data stream starting mode 6.
  • the TDF continuously detects the skype or ends for a period of time (for example, two minutes), it will only apply for 2 minutes before reporting the Skype line report to the PCRF in order to avoid short-term data communication.
  • the PCRF-series follow-up reaction such as the P2P application is not detected, the PCRF uplink bearer update, etc.
  • Table 1 is only an example of the correspondence between the local QoS control policy and/or the charging policy and the reporting mode. It is obvious that the description is based on actual conditions, including but not limited to the types described in the table. The situation is as long as the local QoS control policy and/or the charging policy and the corresponding reporting manner required according to the actual selection are within the protection scope of the present invention.
  • Table 1 is a different reporting method for different application types according to different policies. For different application types, different reporting methods can also be used. For example, for P2P applications, reporting mode 1 can be adopted.
  • reporting method 2 For Voip applications, You can use the reporting method 2, for the microsoft update application, you can use the upper mode 3, for the http application, you can use the reporting method 4, etc., so whether it is the same type of application data or different types of application data, the reporting method is required by Determined by the local quality of service control policy and/or charging policy employed in the data.
  • the TDF Before implementing this step, the TDF has been aware of the reporting mode of the detection report corresponding to various reporting modes. For ease of understanding, referring to FIG. 3, the time of four application instances of the application type is shown. The figure shows the start and end times of each application instance (application instance 1 to application instance4).
  • the detection report generated here includes the start report.
  • the reporting mode is the mode 2 shown in Table 1, the start and end times of each subflow with the application instance granularity need to be reported.
  • the detection report generated here includes four start reports, and the mode is as follows:
  • the detection report generated here includes the start report.
  • the detection report typically includes a plurality of sub-reports, such as the start report, the update report, the end report, and the like described in step S202.
  • the number of application instances corresponding to the application type for the specific report time of these sub-reports Referring to the flow change, referring again to FIG. 3, as shown in the time diagram of each application example shown in the figure, assuming that the reporting mode is mode 1 as shown in Table 1, then at time T1, the TDF reports the start report to the PCRF ⁇ Application identifier 1, T1 time, start ⁇ , report end report at time T3 ⁇ Application identifier 1, T3 time, end ⁇ ;
  • the TDF reports four start 4 reports to the PCRF.
  • the specific format is as follows:
  • the TDF reports two end reports to the PCRF.
  • the specific format is as follows:
  • the TDF reports two other end reports to the PCRF.
  • the specific format is as follows:
  • Application instance 3 flow 3 flow description, T3 time, end ⁇ .
  • TDF reports to the PCRF to start reporting ⁇ Application ID, flow 1+flow 2+flow 3+flow 4 flow description, Tl time, start ⁇ , At T2, the TDF reports an update report to the PCRF ⁇ Application ID, flow 1+ flow
  • TDF reports the end report to PCRF
  • the TDF obtains a specific implementation manner in which the TDF obtains the corresponding detection report.
  • the TDF receives the session request sent by the PCRF, where the session request carries the enhanced ADC rule, TDF.
  • the reporting mode information is obtained according to the reporting mode field included in the enhanced ADC rule, and a detection report of the corresponding mode is generated.
  • FIG. 4 is a flowchart of a report reporting method of a data stream detecting function TDF according to a third embodiment of the present invention. For the convenience of description, only parts related to the embodiment of the present invention are shown.
  • step S401 The session request sent by the PCRF, where the session request includes an application detection control rule.
  • the TDF receives the request sent by the PCRF.
  • the ADC rule included in the session request in this step is not an enhanced ADC rule, and the ADC rule includes the need for detection.
  • Information about the application type data including the ADC Rule identifier, the Application ID, and the optional Enforcement Control, and does not include reporting mode information.
  • the TDF knows the application type of the data it needs to detect based on the application ID field information. Obviously, in this step, both PCRF and TDF have the same understanding and knowledge of the application type represented by the application ID field.
  • the session request in this step includes establishing a session request or modifying a session request. If the session connection is not established between the TDF and the PCRF, the PCRF needs to instruct the TDF to detect the data of an application type, and send a setup session request to the TDF, where the setup session request includes the application type information of the data to be detected. If the session connection has been established, but the currently detected application type needs to be modified, the PCRF needs to send a modification session request to the TDF, and correspondingly modify the Application ID field information in the ADC rule, and the TDF can detect the application ID field accordingly.
  • the mapping table of the application type and the reporting mode is stored in the TDF. If the reporting mode corresponding to the application type needs to be modified, the mapping table may be modified.
  • the mapping table is pre-configured into the TDF by manual or automatic manner, or the mapping table is accompanied by the PCRF to the TDF when the session request is sent to the TDF, and the TDF will map the mapping table before the ADC rule received by the TDF takes effect.
  • Stored in the local area so that the TDF can find a corresponding reporting manner in the mapping table according to the application type information in the received ADC rule, and generate a detection report of the corresponding mode according to the reporting manner, the reporting manner and detection.
  • the format of the report has been described in the second embodiment, and details are not described herein again.
  • the TDF reports the detection report to the PCRF.
  • This step is the same as S203 and will not be described here.
  • the embodiment of the present invention provides another specific implementation manner in which the TDF obtains the corresponding detection report, and the TDF stores the mapping table of the application type and the reporting mode.
  • the TDF receives the session request sent by the PCRF, and the session request only includes the information of the application type that needs to be detected.
  • the TDF searches for the corresponding reporting mode information in the mapping table, and generates a detection report of the corresponding mode.
  • FIG. 5 is a flowchart of a method for reporting a report report according to another embodiment of the present invention. For the convenience of description, only parts related to the embodiment of the present invention are shown.
  • the S50K PCRF combines the local QoS control policy and/or the charging policy to determine the reporting mode corresponding to the application type that needs to be detected, and adds the reporting mode information to the target application detection control rule ADC rule to generate an enhanced type. Detection control rules.
  • this step it is first necessary to determine an appropriate reporting manner for the application type that needs to detect the data, and the local quality of service control policy and/or the charging policy that needs to be captured for the type of data.
  • the local quality of service control policy and/or the charging policy that needs to be captured for the type of data.
  • operators may adopt different charging policies and/or control policies for data of different application types. Even for data of the same application type, different data may be used according to different application instances.
  • the charging policy and/or the control policy Therefore, in this step, the PCRF can determine the corresponding reporting mode according to the local QoS control charging policy.
  • Table 1 is a different reporting method for different application types according to different policies. For different application types, different reporting methods can also be used. For example, for P2P applications, reporting mode 1 can be obtained. For Voip applications.
  • the reporting mode is determined by the local quality of service control charging policy that needs to be used for the data.
  • the reporting mode may be a value of an enumerated type, for example, the reporting mode 1, the reporting mode 2, the reporting mode 3, etc. may be represented by 1, 2, 3, etc., of course, the reporting mode may also be a numeric type value, for example.
  • the number 0 can be used to represent the reporting mode 1, the number 4 is the reporting mode 2, the number 7 is the reporting mode 3, etc., or the reporting mode is also the value of the character type.
  • the character a can be used to represent the reporting mode 1
  • the character b represents the reporting mode 2
  • the character c represents the reporting mode 3, etc.
  • the PCRF sends a session request to the TDF, where the session request includes the enhanced application detection control rule, so that the TDF can generate a detection report of the corresponding mode according to the reporting mode information included in the enhanced application detection control rule.
  • the session request sent by the PCRF to the TDF includes an enhanced ADC rule, where the enhanced ADC rule adds a reporting mode field indicating the reporting mode information in the existing ADC rule, and the TDF is based on the received enhanced ADC rule.
  • the Aplication ID and Reporting mode field information, and the data of the application type to be detected and the corresponding reporting manner are included in the enhanced ADC rule.
  • the session request in this step includes establishing a session request or modifying a session request. If the session connection is not established between the TDF and the PCRF, the PCRF needs to instruct the TDF to detect the data of an application type, and send a setup session request to the TDF, where the setup session request includes the application type information of the data to be detected. If the session connection has been established, but you need to modify the currently detected application type, or you need to modify the report mode information, the PCRF needs to be sent to the TDF. Send modify session request, modify the Application ID and Reporting mode field information in the enhanced ADC rule, and send enhanced information ADC rules.
  • the PCRP receives the detection report sent by the TDF.
  • the PCRF receives the detection report sent by the TDF, and the detection report usually includes multiple sub-reports, such as a start report, an update report, and an end report.
  • the detection report triggers the PCRF to further process the detected data stream of the TDF, including closing the data stream, limiting bandwidth, redirecting, differentiated charging, and the like.
  • This embodiment provides a specific implementation manner in which the PCRF sends the information including the reporting mode, and determines the reporting mode to be adopted according to the actual control policy and/or the charging policy, and adds the reporting mode field to the existing ADC rule.
  • the enhanced ADC rule is generated, and the enhanced ADC rule is sent to the TDF, and the TDF generates a detection report corresponding to the mode according to the report mode information, and reports it to the PCRF.
  • the structure of the ADC rule is changed by adding a reporting mode field, and the implementation manner is simple, and the network utilization rate can be effectively improved.
  • FIG. 6 is a flowchart showing an interaction process of a report reporting method according to another embodiment of the present invention.
  • the method is used for communication between a PCRF and a TDF, and the method includes the following steps:
  • the PCRF combines the local service shield control policy and/or the charging policy to determine the upper 4 ⁇ mode corresponding to the application type that needs to be detected, and adds the reporting mode information to the application detection control rule ADC rule to generate Enhanced detection control rules.
  • the PCRF sends a session request to the TDF, where the session request includes the enhanced application detection control rule.
  • the TDF receives the session request sent by the PCRF, where the session request carries an enhanced application detection control rule, and obtains the upper mode information according to the report mode field in the enhanced application detection control rule.
  • the TDF generates a phase according to the reporting manner information in the enhanced application detection control rule. A test report for the mode.
  • the TDF reports the detection report to the PCRF.
  • the PCRF receives the detection report sent by the TDF.
  • the PCRF adds the report mode field corresponding to the application type data to be detected to the ADC rule to generate an enhanced ADC rule, and the TDF generates a corresponding mode according to the report mode field information in the received enhanced ADC rule.
  • the detection report is sent to the PCRF.
  • the reporting mode in this embodiment is not uniquely determined. According to the actual local QoS control policy and/or the charging policy, selecting the appropriate reporting method according to local conditions can reduce the network load and improve the network. Utilization rate.
  • Example 6 Example 6:
  • FIG. 7 is a flowchart showing an interaction process of a report reporting method according to another embodiment of the present invention.
  • the method is used for communication between a PCRF and a TDF, and the method includes the following steps:
  • TDF saves the application type 3 ⁇ 4 on the >3 ⁇ 4 mode mapping table.
  • the PCRF sends a session request to the TDF, where the session request includes an application detection control rule.
  • the TDF receives the session request sent by the PCRF.
  • the TDF searches for the corresponding reporting manner information in the mapping table according to the application type information included in the application detection control rule, and generates a detection report of the corresponding mode according to the reporting manner information.
  • the TDF reports the detection report to the PCRF.
  • the PCRF receives the detection report.
  • a mapping table of an application type and a reporting manner is pre-stored in the TDF, and the TDF searches for the mapping table according to the application type information included in the received ADC rule to find a corresponding reporting manner, and then reports the corresponding reporting manner according to the report.
  • the mode information generates a test report of the corresponding mode.
  • the reporting manner is selected according to actual conditions, thereby generally reducing the reporting frequency and reporting data volume, improving the efficiency of data flow detection reporting, and facilitating the rational use of network resources.
  • FIG. 8 is a flowchart of a report reporting method according to another embodiment of the present invention, where the method is used for communication between a PCRF and a TDF, and the method includes the following steps:
  • the PCRF sends a session request and a mapping table to the TDF, where the session request includes an application detection control rule, where the mapping table includes mapping information of an application type and a reporting manner.
  • the TDF receives a session request and a mapping table sent by the PCRF, and the TDF saves the mapping table.
  • the TDF searches for the corresponding reporting manner information in the mapping table according to the application type information included in the application detection control rule, and generates a detection report of the corresponding mode according to the reporting manner information.
  • the TDF reports the detection report to the PCRF.
  • the PCRF receives the detection report.
  • the embodiment of the present invention is different from the seventh embodiment in that the mapping table is sent to the TDF along with the session request, and the TDF saves the i mapping table to the local, and searches for the mapping table according to the application type information included in the ADC rule.
  • the corresponding reporting manner can be found, and then the detection report of the corresponding mode can be generated according to the reporting manner information.
  • the reporting mode is selected according to the actual situation, which generally reduces the reporting frequency and the reported data volume, improves the efficiency of data flow detection and reporting, and helps to rationally utilize network resources.
  • Example 8 Example 8:
  • FIG. 9 shows a structure of a TDF according to another embodiment of the present invention, and only parts related to the embodiment of the present invention are shown for convenience of description.
  • the TDF includes:
  • the report generating unit 91 is configured to obtain a reporting manner corresponding to the type of the application to be detected, and generate a detection report of the corresponding mode.
  • the report generating unit acquires the corresponding type of the application type that needs to be detected.
  • different application types may have different reporting modes. Which of the above four methods is determined according to which control charging policy is adopted for the application type data. In short, the purpose of this step is to apply according to different applications. The actual situation of the type adopts an appropriate reporting method to meet the control charging requirement for the data of the application type.
  • TDF has also learned the format of the test report corresponding to different reporting methods, and TDF can produce the test report of the corresponding mode according to the information of the reporting mode.
  • the report sending unit 92 is configured to report the detection report generated by the report generating unit to the PCRF.
  • test report may consist of multiple sub-reports, such as start and end reports, and update reports.
  • the report mode information obtained by the report generation unit is determined by the PCRF according to the actual situation, and the information content of the test report reported by the report sending unit to the PCRF is no longer fixed, and is required for reporting the PCRF at an appropriate time.
  • Fig. 10 shows a structure of a TDF according to another embodiment of the present invention, and only parts related to the embodiment of the present invention are shown for convenience of explanation.
  • the TDF includes:
  • the report generating unit 101 is configured to generate a detection report of the corresponding mode according to the reporting manner corresponding to the type of the application to be detected.
  • the report sending unit 102 is configured to report the detection report generated by the report generating unit to the PCRF.
  • the report generating unit 101 specifically includes:
  • the session receiving enhancement module 1011 is configured to receive a session request sent by the PCRF, where the session request carries an enhanced application detection control rule, and the report mode information is obtained according to the report mode field in the enhanced application detection control rule;
  • the report generation enhancement module 1012 is configured to generate a detection report of the corresponding mode according to the report mode information in the enhanced application detection control rule received by the session receiving enhancement module.
  • the TDF obtains a report to be generated by the TDF.
  • the session receiving enhancement module receives a session request sent by the PCRF, where the session request carries an enhanced ADC.
  • the rule generation report generation enhancement module obtains the report mode information according to the report mode field included in the enhanced ADC rule, and generates a detection report of the corresponding mode.
  • Fig. 11 is a view showing the structure of a TDF according to a tenth embodiment of the present invention, and only parts related to the embodiment of the present invention are shown for convenience of explanation.
  • the TDF includes:
  • the report generating unit 111 is configured to generate a detection report of the corresponding mode according to the reporting manner corresponding to the type of the application to be detected.
  • the report sending unit 112 is configured to report the detection report generated by the report generating unit to the PCRF.
  • the report generating unit 111 specifically includes:
  • the confirmation module 1111 is configured to confirm a mapping table in which the application type and the reporting manner are saved.
  • the session receiving standard module 1112 is configured to receive the session request sent by the PCRF when the confirmation module confirms that the mapping table of the application type and the reporting manner is saved.
  • the session request includes an application detection control rule
  • a report generation standard module 1113 configured to search for corresponding report mode information in the mapping table according to the application type information included in the application detection control rule received by the session receiving standard module, and according to the reporting manner The information generates a test report of the corresponding mode.
  • the report generating unit 111 further includes:
  • a storage module 1110 configured to pre-store the mapping table; or, for receiving the session, please The mapping table sent together is obtained, and the received mapping table is saved locally.
  • the storage module is configured to store a mapping table, and when the confirmation module confirms that the mapping table exists in the storage module, the session receiving standard module receives the session request sent by the PCRF, where the session request only includes the need to detect The information of the application type, the report generation standard module searches for the corresponding report mode information in the mapping table, and generates a detection report of the corresponding mode.
  • Fig. 12 is a diagram showing the structure of a PCRF according to another embodiment of the present invention, and only parts related to the embodiment of the present invention are shown for convenience of explanation.
  • the PCRF includes:
  • the rule generating unit 121 is configured to combine the local QoS policy and/or the charging policy to determine a reporting manner corresponding to the application type that needs to be detected, and add the reporting mode information to the standard application detection control rule. Generating enhanced detection control rules;
  • the message sending unit 122 is configured to send a session request to the TDF, where the session request includes an enhanced application detection control rule generated by the rule generating unit;
  • the report receiving unit 123 is configured to receive a detection report of the corresponding mode generated by the TDF mode according to the report mode information included in the session request sent by the session sending unit.
  • the rule generating unit determines the reporting manner corresponding to the application type that needs to be detected before, and adds the reporting mode information to the ADC rule to generate an enhanced ADC rule, and the session sending unit sends the enhanced ADC to the TDF.
  • the rule receiving request, the report receiving unit receives the detection report generated by the TDF according to the reporting mode information.
  • the structure of the ADC rule is changed by adding a reporting mode field, which is simple in implementation and can effectively improve network utilization.
  • the PCRF determines a corresponding reporting manner according to the control charging policy actually adopted by the application type, and transmits the reporting manner information to the TDF, or pre-stores a mapping of different application types and corresponding reporting manners in the TDF. Relationships, so that the TDF reporting method is no longer single, you can take appropriate reporting methods according to the actual strategy, which can improve the efficiency of data flow detection reporting, help Rational use of network resources.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本发明适用于网络技术领域,提供一种数据流检测功能TDF的报告上报方法,所述方法包括:TDF获取需要检测的应用类型所对应的上报方式,生成相应模式的检测报告;TDF向PCRF上报所述检测报告。本方法通过根据不同的应用类型在合适的时机选用合适的上报方式,总体上减少了报告的上报频率及上报数据量,提高数据流检测上报的效率,有助于合理利用网络资源。

Description

说 明 书
一种检测报告上报方法、 报告上报*** 技术领域
本发明属于网络技术领域, 尤其涉及一种检测报告上报方法、 报告上报系 统。 背景技术
在移动网络中存在有不同的业务应用, 例如大量下载型和流媒体型的 P2P ( Peer-to-Peer, 点到点)应用、 QQ应用, http浏览应用。 这些基于英特网的业 务应用对于运营商的业务收益、 用户的应用需求、 甚至业务本身的时延敏感特 点这些方面都是不同的, 因此对这些不同的业务应用, 可能存在不同的流量控 制策略, 为此, 3GPP ( 3G Partnership Project, 第三代伙伴项目) 引入了 PCC ( Policy and Charging Control , 策略和计费控制)构架, 通过 TDF ( Traffic Detection Function, 业务数据流检测功能)来实现对不同的应用类型的数据进 行流量控制, 包括数据流的关闭、 带宽限制和重定向等。
PCRF ( Policy and Charging Rules Function, 策略计费规则功能)向 TDF指 示需要检测数据的应用类型 Application s, TDF检测该应用类型的数据流, 是 基于此应用类型下的各个应用实例 application instance的粒度进行上报,包括各 个应用实例对应的数据流的开始和结束时刻, 以及所有数据流的流描述, 因此, 随着移动终端的多媒体应用不断的增加,同一应用类型的应用实例也逐渐增多, 而且这些不同的应用实例的对应的数据流可能会频繁地开始和结束, 那么 TDF 需要向 PCRF频繁地上报每个应用实例的报告, 包括开始时刻、 结束时刻以及 流描述, 显然如此多的报告信息占用了过多***资源, 降低了网络性能。 发明内容 本发明的目的是提供一种数据流检测功能 TDF的报告上报方法, 旨在解决 网络性能降低的技术问题。 一方面, 提供了一种检测报告上报方法, 包括:
TDF获取需要检测的应用类型所对应的上报方式, 生成相应模式的检测报 告.
TDF向策略与计费规则功能 PCRF上报所述检测报告。
一方面, 提供了另一种检测报告上报方法, 包括:
PCRF 结合本地服务盾量控制计费策略, 决策出当前需要检测的应用类型 对应的上报方式, 并将所述上报方式字段添加在应用检测控制规则中, 生成增 强型应用检测控制规则;
PCRF向数据流检测功能 TDF发送会话请求, 所述会话请求包括所述增强 型应用检测控制规则 ,以使得 TDF能够根据增强型应用检测控制规则中包含的 上报方式信息生成相应模式的检测报告;
PCRF接收所述 TDF发送的检测报告。
一方面, 提供了一种 TDF, 包括:
报告生成单元, 用于获取需要检测的应用类型所对应的上报方式, 生成相 应模式的检测报告;
报告发送单元, 用于向策略与计费功能 PCRF上报所述报告生成单元生成 的所述检测报告。
一方面, 提供了一种 PCRF, 包括:
规则生成单元, 用于结合本地服务质量控制策略和 /或计费策略, 决策出当 前需要检测的应用类型对应的上报方式, 并将所述上报方式字段添加在应用检 测控制规则中, 生成增强型应用检测控制规则;
会话发送单元, 用于向数据流检测功能 TDF发送会话请求, 所述会话请求 包括所述规则生成单元生成的增强型应用检测控制规则;
报告接收单元,用于所述 TDF发送的根据会话发送单元发送的会话请求中 包含的上报方式信息生成对应模式的检测报告。
一方面, 提供了一种报告上报***, 所述***包括如权利要求 11-16所述 的 TDF以及如权利要求 17-20所述的 PCRF。
本发明的有益效果是: 本发明技术方案中, TDF通过一定的方法获取、 知 晓所需检测应用类型所对应的上 4艮方式, 比如所述的上^ ¾方式可以是 PCRF发 送过来, 或是存储在本地 TDF中, 不同的应用类型可能有不同的上报方式, 这 样使得 TDF能够根据实际需求使用合适的上报方式, 而现有技术中, TDF的上 报方式是固定的, 每次都需要上报数据流的开始时刻、 结束时刻以及流描述, 如此多的报告信息占用了过多的***资源,本发明提供的 TDF能够根据实际需 求使用合适的上报方式, 在适当时刻上报所需要的报告信息, 总体上减少了报 告的上报频率及上报数据量, 提高数据流检测上报的效率, 有助于合理利用网 络资源。 附图说 图 1是本发明实施例提供的一种检测报告上报方法的流程图;
图 2是本发明另一实施例提供的一种检测报告上报方法的流程图; 图 3是一种应用类型的四个应用实例的时间图;
图 4是本发明另一实施例提供的一种检测报告上报方法的流程图; 图 5是本发明另一实施例提供的一种检测报告上报方法的流程图; 图 6是本发明另一实施例提供的一种报告上报方法的交互流程图; 图 7是本发明另一实施例提供的一种报告上报方法的交互流程图; 图 8是本发明另一实施例提供的一种报告上报方法的交互流程图; 图 9是本发明另一实施例提供的一种 TDF的结构方框图;
图 10是本发明另一实施例提供的一种 TDF的结构方框图;
图 11是本发明另一实施例提供的一种 TDF的结构方框图; 图 12是本发明第另一实施例提供的一种 PCRF的结构方框图。 具体实施方式
为了使本发明的目的、 技术方案及优点更加清楚明白, 以下结合附图及实 施例, 对本发明进行进一步详细说明。 应当理解, 此处所描述的具体实施例仅 仅用以解释本发明, 并不用于限定本发明。
为了说明本发明所述的技术方案, 下面通过具体实施例来进行说明。
实施例一:
图 1示出了本发明实施例提供的一种检测报告上报方法的流程, 为了便于 说明仅示出了与本发明实施例相关的部分。
本实施例所述方法包括:
5101、 TDF获取需要检测的应用类型所对应的上报方式, 生成相应模式的 检测报告。
在本步骤中, TDF获取需要检测的应用类型所述对应的上报方式, 不同的 应用类型可能有不同的上报方式, 具体采用何种上报方式是根据对这种应用类 型数据采用哪种控制策略和 /或计费策略决定的, 总之, 本步骤的目的就是为了 根据不同应用类型的实际情况采取合适的上报方式, 满足对这种应用类型数据 的控制计费需求即可。 同时, TDF也已经悉知了不同上报方式所对应的检测报 告的格式, TDF根据上报方式的信息可以生产对应模式的检测报告。
5102、 TDF向 PCRF上报所述检测报告。
在实际情况下, 所述检测报告可能会由多个子报告组成, 比如开始 4艮告和 结束报告以及更新报告等。
在本实施例中, TDF获取到的上报方式信息是根据实际情况由 PCR 决策 出来的 , TDF向 PCRF上报的检测报告的信息内容不再固定, 在合适的时间 上报 PCRF所需要知晓的内容, 这样从整体上减少了报告的上报量, 提高了网 路性能。 实施例二:
图 2示出了本发明另一实施例提供的一种数据流检测功能 TDF的报告上报 方法的流程, 为了便于说明仅示出了与本发明实施例相关的部分。
S201、 接收 PCRF发送的会话请求, 所述会话请求中携带有增强型应用检 测控制规则, 根据所述增强型应用检测控制规则中的上报方式字段得到上报方 式信息。
在本发明实施例中, PCRF向 TDF发送了会话请求, 该会话请求包括增强 型 ADC ( Application Detection Control,应用检测控制)规则,所述增强型 ADC 规则中包括需要检测应用类型数据的上报方式的字段信息。 现有的 ADC规则 中一^:包括 ADC 规则标记(ADC Rule identifier ) 、 应用 ID ( Application identifier ) , 以及可选的执行控制策略( Enforcement control ) , 所述执行控制 策略表明了 PCRF指示 TDF对应用 ID所标识的应用类型的数据流所采取的动 作,通常包括截断数据流的状态( Gate status )、上行最大比特率( UL-maximum bit rate ) 、 下行最大比特率( DL-maximum bit rate ) 、 重定向操作 ( Redirect ) 等, 在具体实现时, 将上报方式(Reporting mode )的字段信息添加到 ADC规 则中即可生成增强型 ADC规则, TDF根据增强型 ADC规则中的应用 ID字段 即可知道所需检测的数据是何种应用类型, 比如 P2P应用、 http应用、 Voip应 用等等。
其中, PCRF根据此应用类型需要采取的本地服务质量控制策略和 /或计费 策略决策出相应的上报方式,具体实现时,所述上报方式可以是枚举类型的值, 例如可以通过 1、 2、 3等分别代表上报方式 1、 上报方式 2、 上报方式 3等, 当 然所述上报方式也可以是数值类型的值, 例如可以用数字 0代表上报方式 1 , 数字 4代表上报方式 2, 数字 7代表上报方式 3等, 又或者, 所述上报方式也 以是字符类型的值,例如可以用字符 a代表上报方式 1 ,字符 b代表上报方式 2, 字符 c代表上报方式 3等等, 可以理解, 无论用何种标识代表上报方式, 只要 是 PCRF和 TDF双方对此标识有共同理解和认识,知悉 Reporting mode字段值 所代表的具体的上报方式即可。 所述上报方式对应生成的检测报告至少包括以 下信息中的一条:
数据流的开始报告或者结束报告是以应用类型 Application ID粒度上报,或 者以应用实例 Application instance粒度上才艮;
上^ 据流的开始时刻或者结束时刻;
上报数据流的描述信息;
上报数据流描述的更新信息;
数据流检测上报的迟滞时间值。
为了便于理解, 可以具体列出几种上报方式, 比如假设当前需要检测的应 用类型是 P2P应用, 对于采取不同的本地服务质量控制策略和 /或计费策略, 对 应上报方式及上报内容如下表 1 :
Figure imgf000007_0001
PCRF不需要了解任何数据流描述信息、 方式 5 , TDF检测对应的 P2P应用 开始结束时间点信息。 只需要 TDF执行相 的数据流, 并执行 ADC规则指示 应的操作(例如 限制带宽、 阻断等) 即 的动作 (限制, 阻断 etc ) , 并不 可 向 PCRF发送任何报告
PCRF希望 TDF在检测到目标数据流开始 方式 6, 当 TDF持续检测到 skype 或者结束一段时间 (例如 两分钟)才进 应用 2分钟, 才向 PCRF上报 Skype 行上报, 目的是为了避免短暂的数据通信 应用的开始; 而当 TDF持续 2分钟 带来的 PCRF—系列的后续反应 (比如进 检测不到 P2P应用, 才向 PCRF上 行承载更新等)信令风暴, 以及频繁上报 报 Skype数据流的结束
带来的信令风暴
表 1
需要说明的是,表 1只是给出的本地服务质量控制策略和 /或计费策略和上 报方式对应关系的举例, 显然所述是根据实际情况选取, 包括但不限于表中所 述的几种情况 ,只要根据实际选取需要的本地服务质量控制策略和 /或计费策略 和对应的上报方式, 均在本发明的保护范围之内。 此外, 表 1是对于同一应用 类型根据不同策略所采取不同的上报方式, 对于不同应用类型的数据, 同样可 以釆用不同的上报方式, 如对于 P2P应用, 可以采取上报方式 1 , 对于 Voip应 用, 可以采用上报方式 2, 对于 microsoft update应用, 可以采用上 方式 3, 对于 http应用, 可以采用上报方式 4等等, 因此无论是相同类型的应用数据还 是不同类型的应用数据, 其上报方式是由需要对该数据所述采用的本地服务质 量控制策略和 /或计费策略所决定的。
S202、 根据所述增强型应用检测控制规则中的上报方式信息, 生成相应模 式的检测报告。
在实现本步骤之前, TDF已经知悉各种上报方式所对应的检测报告的报告 模式, 为了便于理解, 参照图 3 , 示出了一种应用类型的四个应用实例的时间 图, 显示出了各个应用实例 ( application instance 1至 application instance4 )的开 始和结束时刻。
假设上报方式为如表 1所示的方式 1, 只需上报以 Application ID粒度的数 据流的开始时刻和结束时刻, 那么这里生成的检测报告包括开始报告
{Application identifier 1 , Tl时刻 , 开始 }和结束报告 {Application identifier 1 , Τ3时刻, 结束 }。
假设上报方式为如表 1所示的方式 2, 需要上报以 application instance粒度 的每个子流的开始和结束时刻, 那么这里生成的检测报告包括四个开始报告, 模式如下:
{Application instance 1, flow 1的流描述, T1时刻 , 开始 }、
{ Application instance 2, flow 2的流描述, T1时刻, 开始 }、
{ Application instance 3 , flow 3的流描述, T1时刻, 开始 }、
{ Application instance 4, flow 4的流描述, T1时刻, 开始 }, 以及四个结束
-, 模式如下:
{ Application instance 2, flow 2的流描述, T2时刻, 结束 }、
{ Application instance 4, flow 4的流描述, T2时刻, 结束 }、
{Application instance 1, flow 1的流描述, T3时刻, 结束 }、
{ Application instance 3 , flow 3的流描述, T3时刻, 结束 }。
假设上报方式为如表 1所示的方式 3 , 需要上报以 Application ID粒度的数 据流的开始时刻、 更新、 结束时刻, 那么这里生成的检测报告包括开始报告
{Application ID , flow 1 +flow 2+flow 3+flow 4的流描述, T 1时刻, 开始 } , 更 新报告 { Application ID, flow 1+ flow 3 的流描述, T2时刻, 更新 } , 以及结束 报告 {Application ID, T3时刻, 结束 }。
S203、 TDF向 PCRF上才艮所述检测报告。
所述检测报告通常包括多个子报告,如步骤 S202所述的开始报告、更新报 告、 结束报告等。 这些子报告的具体上报时间与应用类型对应的应用实例的数 据流变化有关, 再次参照图 3, 如该图所示的各个应用实例的时间图, 假设上报方式为如表 1所示的方式 1, 那么在 T1时刻, TDF向 PCRF上报 开始报告 {Application identifier 1, T1时刻, 开始 }, 在 T3时刻上报结束报告 {Application identifier 1, T3时刻, 结束 };
假设上报方式为如表 1所示的方式 2, 那么在 T1时刻 , TDF向 PCRF上报 四个开始 4艮告, 具体格式如下:
{Application instance 1, flow 1的流描述, T1时刻, 开始 }、
{ Application instance 2, flow 2的流描述, T1时刻, 开始 }、
{ Application instance 3 , flow 3的流描述, T 1时刻, 开始 }、
{ Application instance 4, flow 4的流描述, T1时刻, 开始 } , 在 T2时刻,
TDF向 PCRF上报两个结束报告, 具体格式如下:
{ Application instance 2, flow 2的流描述, T2时刻, 结束 }、
{ Application instance 4, flow 4的流描述, T2时刻, 结束 } , 在 T3时刻,
TDF向 PCRF上报另两个结束报告, 具体格式如下:
{Application instance 1 , flow 1的流描述, T3时刻, 结束 }、
{ Application instance 3, flow 3的流描述, T3时刻, 结束 }。
假设上报方式为如表 1所示的方式 3, 那么在 T1时刻, TDF向 PCRF上报 开始报告 {Application ID, flow 1+flow 2+flow 3+flow 4的流描述, Tl时刻, 开始 } , 在 T2时刻, TDF向 PCRF上报更新报告 { Application ID, flow 1+ flow
3 的流描述, T2时刻, 更新 } , 以及在 Τ3时刻, TDF向 PCRF上报结束报告
{Application ID, T3时刻, 结束 }。
本实施例给出了 TDF获取需上报方式生成相应检测报告的一种具体实现 方式, 在本发明实施例中, TDF接收 PCRF发送的会话请求, 所述会话请求中 携带有增强型 ADC规则, TDF根据增强型 ADC规则中包含的上报方式字段得 到上报方式信息, 再生成相应模式的检测报告。 实施例三:
图 4示出了本发明第三实施例提供的一种数据流检测功能 TDF的报告上报 方法的流程, 为了便于说明仅示出了与本发明实施例相关的部分。
5401、 接 PCRF发送的会话请求, 所述会话请求包括应用检测控制规则。 在本步骤中, TDF接收到 PCRF发送的 ^舌请求, 与步驟 S201不同的是, 本步骤所述的会话请求中包括的 ADC规则不是增强型 ADC规则, 所述 ADC 规则中包含有需要检测的应用类型数据的相关信息,包括 ADC规则标记( ADC Rule identifier ) 、 应用 ID ( Application identifier ) , 以及可选的执行控制策略 ( Enforcement control ) , 并不包含上报方式( reporting mode )信息。 TDF根据 该 application ID字段信息知晓其需要检测的数据的应用类型。 显然, 在本步骤 中 , PCRF和 TDF对 application ID字段所表示的应用类型都有相同的了解和认 识。
同样, 本步骤中所述会话请求包括建立会话请求或修改会话请求。 如果之 前 TDF和 PCRF间没有建立会话连接, PCRF需要指示 TDF对某一应用类型的 数据进行检测时, 向 TDF发送建立会话请求, 所述建立会话请求中包括需要检 测出的数据的应用类型信息, 如果当前已经建立了会话连接, 但是需要修改当 前检测的应用类型,此时 PCRF需要向 TDF发送修改会话请求,相应修改 ADC 规则中的 Application ID字段信息, TDF相应检测其中的 application ID字段即 可。
5402、 根据所述应用检测控制规则中所包含的应用类型信息, 在所述映射 表中查找对应的上报方式信息, 并根据所述上报方式信息生成相应模式的检测 报告。
实现本步骤之前, TDF中存储有应用类型与上报方式的映射表, 如果需要 修改应用类型对应的上报方式, 修改所述映射表即可。 所述映射表通过人工或 自动方式预配置到 TDF中, 或者所述映射表是 PCRF向 TDF发送会话请求时 伴随传递给 TDF的,在 TDF接收到的 ADC规则生效之前, TDF将所述映射表 存储在本地中, 这样 TDF可以根据接收到的 ADC规则中的应用类型信息, 在 所述映射表中找到对应的上报方式, 并根据该上报方式生成相应模式的检测报 告, 所述上报方式和检测报告的格式在实施例二中已做描述, 此处不再赘述。
S403、 TDF向 PCRF上报所述检测报告。
本步骤与 S203相同, 此处不再赘述。
本实施例给出了 TDF获取需上报方式生成相应检测报告的另一种具体实 现方式, 与实施例三不同的是, 在本发明实施例中, TDF存储有应用类型与上 报方式的映射表, TDF接收 PCRF发送的会话请求, 所述会话请求中仅仅包含 有需要检测的应用类型的信息, TDF在所述映射表中查找对应的上报方式信息, 再生成相应模式的检测报告。 实施例四:
图 5示出了本发明另一实施例提供的一种检测报告上报方法的流程, 为了 便于说明仅示出了与本发明实施例相关的部分。
S50K PCRF结合本地服务质量控制策略和 /或计费策略, 决策出当前需要 检测的应用类型对应的上报方式, 并将所述上报方式信息添加在标应用检测控 制规则 ADC rule中, 生成增强型用检测控制规则。
在本步骤中, 首先需要针对当前需要检测数据的应用类型, 结合需要对该 类型数据所要釆取的本地服务质量控制策略和 /或计费策略, 决策出合适的上报 方式。 在实际情况中, 运营商为了提供差异化服务, 对不同的应用类型的数据 可能采取不同的计费策略和 /或控制策略, 即使对同一应用类型的数据, 也可能 根据不同的应用实例采取不同的计费策略和 /或控制策略,因此本步骤中, PCRF 根据本地服务质量控制计费策略可以决策出相应的上报方式。 为了便于理解是 如何根据不同本地服务质量控制计费策略决策出对应上报方式, 参照实施例二 中的表 1 , 示出了几种本地服务质量控制计费策略以及对应的上报方式和需要 上报的内容, 显然, 这只是几种本地服务质量控制策略和 /或计费策略和对应上 报方式的举例, 本发明实施例不限于上述几种情况。 此外, 表 1是对于同一应 用类型根据不同策略所采取不同的上报方式, 对于不同应用类型的数据, 同样 可以釆用不同的上报方式, 如对于 P2P应用, 可以釆取上报方式 1, 对于 Voip 应用, 可以采用上艮方式 2, 对于 Microsoft update应用, 可以采用上^ =艮方式 3, 对于 http应用, 可以采用上报方式 4等等, 因此无论是相同类型的应用数据还 是不同类型的应用数据, 其上报方式是由需要对该数据所述采用的本地服务质 量控制计费策略所决定的。
所述上报方式可以是枚举类型的值, 例如可以通过 1、 2、 3等分别代表上 报方式 1、上报方式 2、上报方式 3等, 当然所述上报方式也可以是数值类型的 值, 例如可以用数字 0代表上报方式 1 , 数字 4代表上报方式 2, 数字 7代表上 报方式 3等, 又或者, 所述上报方式也以是字符类型的值, 例如可以用字符 a 代表上报方式 1, 字符 b代表上报方式 2, 字符 c代表上报方式 3等等, 可以理 解, 无论用何种标识代表上^^方式, 只要是 PCRF和 TDF双方对此标识有共同 理解和认识, 悉知 Reporting mode字段值所代表的具体的上报方式即可。
S502、 PCRF向 TDF发送会话请求, 所述会话请求包括所述增强型应用检 测控制规则,以使得 TDF能够根据增强型应用检测控制规则中包含的上报方式 信息生成相应模式的检测报告。
其中, PCRF向 TDF发送的会话请求中包括增强型 ADC规则, 所述增强 型 ADC规则是在现有 ADC规则中添加表示上报方式信息的 reporting mode字 段, TDF根据接收到的增强型 ADC规则中的 Aplication ID和 Reporting mode 字段信息, 知悉需要检测的应用类型的数据和对应的上报方式。
进一步的, 本步骤中所述会话请求包括建立会话请求或修改会话请求。 如 果之前 TDF和 PCRF间没有建立会话连接, PCRF需要指示 TDF对某一应用类 型的数据进行检测时, 向 TDF发送建立会话请求, 所述建立会话请求中包括需 要检测出的数据的应用类型信息, 如杲当前已经建立了会话连接, 但是需要修 改当前检测的应用类型, 或者需要修改上报方式信息, 此时 PCRF需要向 TDF 发送修改会话请求,相应修改增强型 ADC规则中的 Application ID和 Reporting mode字段信息, 发送信息的增强型 ADC规则。
S503、 PCRP接收 TDF发送的检测报告。
PCRF接收 TDF发送的检测报告 , 所述的检测报告通常包含多个子报告, 如开始报告、 更新报告和结束报告等等。 所述的检测报告触发 PCRF对 TDF对 检测的数据流进一步处理, 包括关闭数据流、 宽带限制、 重定向, 差异化计费 等等。
本实施例给出了 PCRF发送包含有上报方式信息的一种具体实现方式, 根 据实际控制策略和 /或计费策略决策出需要采取的上报方式,将上报方式字段添 加到现有的 ADC规则中, 生成增强型 ADC规则, 并将所述增强型 ADC规则 发送到 TDF, TDF根据其中的上报方式信息生成对应模式的检测报告, 并上报 给 PCRF。 本实施例通过添加上报方式字段来更改 ADC规则的结构, 实现方式 简单, 可以有效地提高网络利用率。 实施例五:
图 6示出了本发明另一实施例提供的一种报告上报方法的交互流程, 所述 方法用于 PCRF与 TDF间的通信, 所述方法包括下述步骤:
5601、 PCRF结合本地服务盾量控制策略和 /或计费策略, 决策出当前需要 检测的应用类型对应的上 4艮方式, 并将所述上报方式信息添加在应用检测控制 规则 ADC rule中, 生成增强型用检测控制规则。
5602、 PCRF向 TDF发送会话请求, 所述会话请求包括所述增强型应用检 测控制规则。
5603、 TDF接收 PCRF发送的会话请求, 所述会话请求中携带有增强型应 用检测控制规则, 根据所述增强型应用检测控制规则中的上报方式字段得到上 才艮方式信息。
5604、 TDF根据所述增强型应用检测控制规则中的上报方式信息, 生成相 应模式的检测报告。
5605、 TDF向 PCRF上报所述检测报告。
5606、 PCRF接收 TDF发送的检测报告。
本发明实施例中, PCRF将需要检测的应用类型数据对应的上报方式字段 添加到 ADC规则中, 生成增强型 ADC规则, TDF根据接收到的增强型 ADC 规则中的上报方式字段信息生成相应模式的检测报告并发送到 PCRF, 本实施 例中的上报方式不是唯一确定的,根据实际的本地服务质量控制策略和 /或计费 策略决定的, 因地制宜地选择合适的上报方式可以减轻网络负载, 提高网络利 用率。 实施例六:
图 7示出了本发明另一实施例提供的一种报告上报方法的交互流程, 所述 方法用于 PCRF与 TDF间的通信, 所述方法包括下述步骤:
5701、 TDF保存应用类型 ¾上>¾方式的映射表。
5702、 PCRF向 TDF发送会话请求,所述会话请求包括应用检测控制规则。
5703、 TDF接收 PCRF发送的会话请求。
5704、 TDF根据所述应用检测控制规则中所包含的应用类型信息, 在所述 映射表中查找对应的上报方式信息, 并根据所述上报方式信息生成相应模式的 检测报告。
5705、 TDF向 PCRF上报所述检测报告。
5706、 PCRF接收报所述检测报告。
在本发明实施中, TDF中预先存储有应用类型与上报方式的映射表, TDF 根据接收到 ADC规则中包含的应用类型信息查找所述映射表即可找到对应的 上报方式, 再根据所述上报方式信息生成相应模式的检测报告即可。 同样, 在 本实施例中, 上报方式是根据实际情况选择的, 这样总体上减少了报告的上报 频率及上报数据量, 提高数据流检测上报的效率, 有助于合理利用网絡资源。 实施例七:
图 8示出了本发明另一实施例提供的一种报告上报方法的流程, 所述方法 用于 PCRF与 TDF间的通信, 所述方法包括下述步骤:
5801、 PCRF向 TDF发送会话请求和映射表, 所述会话请求包括应用检测 控制规则, 所述映射表包含有应用类型与上报方式的映射信息。
5802、 TDF接收 PCRF发送的会话请求和映射表, TDF保存所述映射表。
5803、 TDF根据所述应用检测控制规.则中所包含的应用类型信息, 在所述 映射表中查找对应的上报方式信息, 并根据所述上报方式信息生成相应模式的 检测报告。
5804、 TDF向 PCRF上报所述检测报告。
S805、 PCRF接收报所述检测报告。
本发明实施例与实施例七不同的是, 所述的映射表是随同会话请求一齐发 送到 TDF, TDF保存所i映射表至本地, 并根据 ADC规则中包含的应用类型 信息查找所述映射表即可找到对应的上报方式, 再根据所述上报方式信息生成 相应模式的检测报告即可。 同样, 在本实施例中, 上报方式是根据实际情况选 择的, 这样总体上减少了报告的上报频率及上报数据量, 提高数据流检测上报 的效率, 有助于合理利用网络资源。 实施例八:
图 9示出了本发明另一实施例提供的一种 TDF的结构,为了便于说明仅示 出了与本发明实施例相关的部分。
所述 TDF包括:
报告生成单元 91 , 用于获取需要检测的应用类型所对应的上报方式, 生成 相应模式的检测报告。
在本发明实施例中, 报告生成单元获取需要检测的应用类型所述对应的上 方式, 不同的应用类型可能有不同的上报方式, 具体采用何种上 4艮方式是根 据对这种应用类型数据采用哪种控制计费策略决定的, 总之, 本步骤的目的就 是为了根据不同应用类型的实际情况采取合适的上报方式, 满足对这种应用类 型数据的控制计费需求即可。 同时, TDF也已经知悉了不同上报方式所对应的 检测报告的格式, TDF根据上报方式的信息可以生产对应模式的检测报告。
报告发送单元 92, 用于向 PCRF上报所述报告生成单元生成的所述检测报 告。
在实际情况下, 所述检测报告可能会由多个子报告组成, 比如开始报告和 结束报告以及更新报告等。
在本发明实施例中, 报告生成单元获取到的上报方式信息是根据实际情况 由 PCRF决策出来的 ,报告发送单元向 PCRF上报的检测报告的信息内容不再 固定, 在合适的时间上报 PCRF所需要知晓的内容, 这样从整体上减少了报告 的上报量, 提高了网路性能。 实施例九:
图 10示出了本发明另一实施例提供的一种 TDF的结构, 为了便于说明仅 示出了与本发明实施例相关的部分。
所述 TDF包括:
报告生成单元 101, 用于根据需要检测的应用类型所对应的上报方式, 生 成相应模式的检测报告。
报告发送单元 102, 用于向 PCRF上报所述报告生成单元生成的所述检测 报告。
其中, 所述报告生成单元 101具体包括:
会话接收增强模块 1011 , 用于接收 PCRF发送的会话请求, 所述会话请求 中携带有增强型应用检测控制规则 , 根据所述增强型应用检测控制规则中的上 报方式字段得到上报方式信息; 报告生成增强模块 1012, 用于根据所述会话接收增强模块接收的所述增强 型应用检测控制规则中的上报方式信息, 生成相应模式的检测报告。
本实施例给出了 TDF获取需上报方式生成相应检测报告的一种具体实现 方式, 在本发明实施例中, 会话接收增强模块接收 PCRF发送的会话请求, 所 述会话请求中携带有增强型 ADC规则, 报告生成增强模块根据增强型 ADC规 则中包含的上报方式字段得到上报方式信息, 再生成相应模式的检测报告。
实施例十:
图 11示出了本发明第十实施例提供的一种 TDF的结构, 为了便于说明仅 示出了与本发明实施例相关的部分。
所述 TDF包括:
报告生成单元 111, 用于根据需要检测的应用类型所对应的上报方式, 生 成相应模式的检测报告。
报告发送单元 112, 用于向 PCRF上报所报告生成单元生成的所述述检测 报告。
其中, 所述报告生成单元 111具体包括:
确认模块 1111 , 用于确认保存有应用类型与上报方式的映射表; 会话接收标准模块 1112,用于所述确认模块确认保存有应用类型与上报方 式的映射表时, 接收 PCRF发送的会话请求, 所述会话请求包括应用检测控制 规则;
报告生成标准模块 1113,用于根据所述会话接收标准模块接收的所述应用 检测控制规则中所包含的应用类型信息, 在所述映射表中查找对应的上报方式 信息, 并根据所述上报方式信息生成相应模式的检测报告。
作为优选的, 所述报告生成单元 111还包括:
存储模块 1110, 用于预先存储所述映射表; 或者, 用于接收随所述会话请 求一齐发送的所述映射表, 将接收到的映射表保存至本地。
在本发明是实例中, 存储模块用于存储映射表, 当确认模块确认所述存储 模块中存在映射表时, 会话接收标准模块接收 PCRF发送的会话请求, 所述会 话请求中仅仅包含有需要检测的应用类型的信息, 报告生成标准模块在所述映 射表中查找对应的上报方式信息, 再生成相应模式的检测报告。 实施例十一:
图 12示出了本发明另一实施例提供的一种 PCRF的结构,为了便于说明仅 示出了与本发明实施例相关的部分。
所述 PCRF包括:
规则生成单元 121, 用于结合本地服务质量控制策略和 /或计费策略, 决策 出当前需要检测的应用类型对应的上报方式, 并将所述上报方式信息添加在标 准型应用检测控制规则中, 生成增强型用检测控制规则;
话发送单元 122, 用于向 TDF发送会话请求, 所述会话请求包括所述规 则生成单元生成的增强型应用检测控制规则;
报告接收单元 123, 用于接收 TDF发送的根据会话发送单元发送的会话请 求中包含的上报方式信息生成对应模式的检测报告。
本实施例中,规则生成单元决策出前需要检测的应用类型对应的上报方式, 并将上报方式信息添加到 ADC规则中, 生成增强型 ADC规则, 所述会话发送 单元向 TDF发送带有增强型 ADC规则的会话请求,报告接收单元接收 TDF根 据上报方式信息生成的检测报告。本实例例通过添加上报方式字段来更改 ADC 规则的结构, 实现方式简单, 可以有效地提高网络利用率。
在本发明实施例中, PCRF根据对应用类型实际采取的控制计费策略决策 出对应的上报方式,并将上报方式信息传递给 TDF,或者 TDF中预存有不同应 用类型与对应的上报方式的映射关系,使得 TDF的报告方式不再单一, 可以根 据实际策略采取合适的上报方式, 这样可以提高数据流检测的上报效率, 有助 于合理利用网络资源。
本领域普通技术人员可以理解, 实现上述实施例方法中的全部或部分步骤 是可以通过程序来指令相关的硬件来完成, 所述的程序可以在存储于一计算机 可读取存储介貭中, 所述的存储介质, 如 ROM/RAM、 磁盘、 光盘等。
以上所述仅为本发明的较佳实施例而已, 并不用以限制本发明, 凡在本发 明的精神和原则之内所作的任何修改、 等同替换和改进等, 均应包含在本发明 的保护范围之内。

Claims

权 利 要 求 书
1、 一种检测报告上报方法, 其特征在于, 包括:
数据流检测功能 TDF获取需要检测的应用类型所对应的上报方式,生成相 应模式的检测报告;
数据流检测功能 TDF向策略与计费规则功能 PCRF上报所述检测报告。
2、 如权利要求 1所述方法, 其特征在于, 所述数据流检测功能 TDF获取 需要检测的应用类型所对应的上报方式, 生成相应的检测报告, 包括:
接收所述 PCRF发送的会话请求, 所述会话请求中携带有增强型应用检测 控制规则, 根据所述增强型应用检测控制规则中的上报方式字段得到上报方式 信息;
根据所述增强型应用检测控制规则中的上报方式信息, 生成相应模式的检 测报告。
3、 如权利要求 1所述方法, 其特征在于, 如果所述 TDF保存有应用类型 与上报方式的映射表,所述数据流检测功能 TDF获取需要检测的应用类型所对 应的上报方式, 生成相应模式的检测报告, 包括:
接收所述 PCRF发送的会话请求, 所述会话请求包括应用检测控制规则; 根据所述应用检测控制规则中所包含的应用类型信息 , 在所述映射表中查 找对应的上报方式信息, 并根据所述上报方式信息生成相应模式的检测报告。
4、如权利要求 3所述方法,其特征在于, 所述映射表预先存储在所述 TDF 中, 或者, 所述映射表随所述会话请求一齐发送到所述 TDF, 所述 TDF将接收 到的映射表保存至本地。
5、 如权利要求 2-4任一项所述方法, 其特征在于, 所述会话请求包括建立 会话请求或修改会话请求。
6、 一种检测报告上报方法, 其特征在于, 包括:
策略与计费规则功能 PCRF结合本地服务质量控制策略和 /或计费策略, 决 策出当前需要检测的应用类型对应的上报方式, 并将所述上报方式字段添加在 应用检测控制规则中, 生成增强型应用检测控制规则;
所述 PCRF向数据流检测功能 TDF发送会话请求,所述会话请求包括所述 增强型应用检测控制规则,以使得 TDF能够根据增强型应用检测控制规则中包 含的上报方式信息生成相应模式的检测报告;
所述 PCRF接收所述 TDF发送的检测报告。
7、 如权利要求 6所述方法, 其特征在于, 所述上报方式是枚举类型、 数值 类型或者字符类型的标识。
8、如权利要求 6或 7所述方法, 其特征在于, 所述会话请求包括建立会话 请求或修改会话请求。
9、如权利要求 2或 6所述方法,所述增强型应用检测控制规则是携带了上 报方式信息的应用检测控制规则。
10、 如权利要求 6-9任一项所述方法, 其特征在于, 所述上报方式对应生 成的检测报告至少包括以下信息中的一条:
数据流的开始报告或者结束报告是以应用类型 Application ID粒度上报,或 者以应用实例 Application instance粒度上报;
上才艮数据流的开始时刻和结束时刻;
上报数据流的描述信息;
上报数据流描述的更新信息;
数据流检测上报的迟滞时间值。
11、 一种数据流检测功能 TDF, 其特征在于, 所述 TDF包括:
报告生成单元, 用于获取需要检测的应用类型所对应的上报方式, 生成相 应模式的检测报告;
报告发送单元, 用于向策略与计费功能 PCRF上报所述报告生成单元生成 的所述检测报告。
12、 如权利要求 11所述的 TDF, 其特征在于, 所迷报告生成单元包括: 会话接收增强模块,用于接收策略与计费规则功能 PCRF发送的会话请求, 所述会话请求中携带有增强型应用检测控制规则, 根据所述增强型应用检测控 制规则中的上报方式字段得到上报方式信息;
报告生成增强模块, 用于根据所述会话接收增强模块接收的所述增强型应 用检测控制规则中的上报方式信息, 生成相应模式的检测报告。
13、 如权利要求 11所述的 TDF, 其特征在于, 所述报告生成单元包括: 确认模块, 用于确认保存有应用类型与上报方式的映射表;
^^接收标准模块, 用于所述确认模块确认保存有应用类型与上报方式的 映射表时,接收 PCRF发送的会话请求, 所述会话请求包括应用检测控制规则; 报告生成标准模块, 用于根据所述会话接收标准模块接收的所述应用检测 控制规则中所包含的应用类型信息,在所述映射表中查找对应的上报方式信息, 并根据所述上报方式信息生成相应模式的检测报告。
14、 如权利要求 13所述的 TDF, 其特征在于, 所述 TDF还包括: 存储模块, 用于预先存储所述映射表; 或者, 用于接收随所述会话请求一 齐发送的所述映射表, 将接收到的映射表保存至本地。
15、 如权利要求 11-14任一项所述的 TDF, 其特征在于, 所述会话接收增 强模块接收的会话请求包括建立会话请求或修改会话请求。
16、 如权利要求 11-15任一项所述的 TDF, 其特征在于, 所述报告生成单 元获取的上报方式对应生成的检测报告至少包括以下信息中的一条:
数据流的开始报告或者结束报告是以应用类型 Application ID粒度上报, 或者以应用实例 Application instance粒度的上才艮;
上报数据流的开始时刻和者结束时刻;
上报数据流的描述信息;
上报数据流描述的更新信息;
数据流检测上报的迟滞时间值。
17、 一种策略与计费规则功能 PCRF, 其特征在于, 所述 PCRF包括: 规则生成单元, 用于结合本地服务质量控制策略和 /或计费策略, 决策出当 前需要检测的应用类型对应的上报方式, 并将所述上报方式字段添加在应用检 测控制规则中, 生成增强型应用检测控制规则;
会话发送单元, 用于向数据流检测功能 TDF发送会话请求, 所述会话请求 包括所述规则生成单元生成的增强型应用检测控制规则;
报告接收单元,用于接收所述 TDF发送的根据会话发送单元发送的会话请 求中包含的上报方式信息生成对应模式的检测报告。
18如权利要求 17所述的一种 PCRF,其特征在于, 所述上报方式是枚举类 型、 数值类型或者字符类型的标识。
19、 如权利要求 18所述的一种 PCRF, 其特征在于, 所述会话请求包括建 立会话请求或修改会话请求。
20、如权利要求 17-19任一项所述的 PCRF, 其特征在于, 所述规则生成单 元决策出的上报方式对应的检测报告至少包括以下信息中的一条:
数据流的开始报告或者结束报告是以应用类型 Application ID粒度上报, 或者以应用实例 Application instance粒度的上报;
上报数据流的开始时刻和结束时刻;
上报数据流的描述信息;
上报数据流描述的更新信息;
数据流检测上报的迟滞时间值。
21、 一种报告上报***, 所述***包括如权利要求 11-16所述的数据流检 测功能 TDF和如权利要求 17-20所述的策略与计费规则功能 PCRF。
PCT/CN2012/000635 2012-05-11 2012-05-11 一种检测报告上报方法、报告上报*** WO2013166625A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2012/000635 WO2013166625A1 (zh) 2012-05-11 2012-05-11 一种检测报告上报方法、报告上报***
CN201280001395.6A CN103518392B (zh) 2012-05-11 2012-05-11 一种检测报告上报方法、报告上报***

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/000635 WO2013166625A1 (zh) 2012-05-11 2012-05-11 一种检测报告上报方法、报告上报***

Publications (1)

Publication Number Publication Date
WO2013166625A1 true WO2013166625A1 (zh) 2013-11-14

Family

ID=49550041

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/000635 WO2013166625A1 (zh) 2012-05-11 2012-05-11 一种检测报告上报方法、报告上报***

Country Status (2)

Country Link
CN (1) CN103518392B (zh)
WO (1) WO2013166625A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9961212B2 (en) 2014-07-02 2018-05-01 Alcatel Lucent Policy and charging control method and apparatus for an application service chain based on an SDN network
WO2018233015A1 (zh) * 2017-06-21 2018-12-27 深圳市盛路物联通讯技术有限公司 一种终端设备的物联网数据上报频率的控制及***

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101662415A (zh) * 2008-08-29 2010-03-03 华为技术有限公司 一种策略控制方法及通讯***以及相关设备
CN102131172A (zh) * 2010-01-18 2011-07-20 中兴通讯股份有限公司 业务处理方法及***
US20120087262A1 (en) * 2010-10-06 2012-04-12 Nokia Siemens Networks Oy Method, Apparatus and System for Detecting Service Data of a Packet Data Connection

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101662415A (zh) * 2008-08-29 2010-03-03 华为技术有限公司 一种策略控制方法及通讯***以及相关设备
CN102131172A (zh) * 2010-01-18 2011-07-20 中兴通讯股份有限公司 业务处理方法及***
US20120087262A1 (en) * 2010-10-06 2012-04-12 Nokia Siemens Networks Oy Method, Apparatus and System for Detecting Service Data of a Packet Data Connection

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9961212B2 (en) 2014-07-02 2018-05-01 Alcatel Lucent Policy and charging control method and apparatus for an application service chain based on an SDN network
WO2018233015A1 (zh) * 2017-06-21 2018-12-27 深圳市盛路物联通讯技术有限公司 一种终端设备的物联网数据上报频率的控制及***

Also Published As

Publication number Publication date
CN103518392A (zh) 2014-01-15
CN103518392B (zh) 2017-05-31

Similar Documents

Publication Publication Date Title
EP2204011B1 (en) Method and apparatus for improving the efficiency of resource utilisation in a communications system
US11418552B2 (en) Device service capability discovery
US8355325B2 (en) Control method, system and function entity for reporting bearer event of signaling IP flow
US10305952B2 (en) Preference-aware content streaming
JP7411827B2 (ja) メディアストリーミングサービス伝送を制御する方法、ユーザ端末、ネットワークノード、システム、プログラム及び電子機器
WO2019050694A1 (en) FUNCTION SELECTION BASED ON LEVEL OF USE IN 5G ENVIRONMENTS
RU2435205C2 (ru) Способ законного перехвата информации и устройство для этого
US20180103389A1 (en) Service rate adjustment method and apparatus
US20120275300A1 (en) Service event trigger
US8838156B2 (en) Multi-bearer rate control for transporting user plane data
KR20120103749A (ko) 통신 시스템에서 이진 마킹을 사용한 명시적 혼잡 통지 기반의 레이트 적응
CN103119981B (zh) 服务质量控制方法和设备
WO2021148012A1 (zh) 报告信息的发送方法和通信装置以及通信***
KR20130114647A (ko) 패킷교환 액세스 망에서 회선교환 액세스 망으로 세션을 이동하기 위한 방법, 장치 및 컴퓨터 프로그램
WO2023035894A1 (zh) 一种数据处理方法、设备、可读存储介质和程序产品
US20120166659A1 (en) Node and Method for Quality of Service (QoS) Control
WO2013159617A1 (zh) 一种网络拥塞的处理方法、***和控制网元
WO2015069165A1 (en) Allocation of ressources for real-time communication
CN103095664B (zh) Ip多媒体会话建立方法和***
WO2014180210A1 (zh) 一种控制网络拥塞的方法和负荷感知功能
WO2014180410A1 (zh) 一种实现媒体QoS承载资源控制的方法及装置
WO2012037817A1 (zh) 一种实现策略同步的方法及***
WO2013166625A1 (zh) 一种检测报告上报方法、报告上报***
CN101247325B (zh) 一种实现新业务加入的方法和***
WO2016000378A1 (zh) 资源共享处理方法、装置及p-cscf

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: 12876371

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: 12876371

Country of ref document: EP

Kind code of ref document: A1