A cellular traffic monitoring system includes: a traffic detection function (TDF) module to monitor cellular traffic associated with a cellular subscriber device, and to generate application detection output indicative of an application used by the cellular subscriber device; an application-based charging module to generate, based on the application detection output of said TDF module, application-based charging data related to said cellular subscriber device; a policy charging and enforcement function (PCEF) module to enforce one or more charging rules that are Service Data flow (sdf) based and are related to said cellular subscriber device; an sdf-based charging module to generate sdf-based charging data related to said cellular subscriber device; and a charging correlator module to identify a potential over-charging due to an overlap between the application-based charging data and the sdf-based charging data.
|
0. 19. An apparatus comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processor, cause the apparatus to:
generate application detection output indicative of an application used by a cellular subscriber device;
generate, based on the application detection output, application-based charging data related to the cellular subscriber device;
enforce one or more charging rules that are Service Data flow (sdf) based and are related to the cellular subscriber device;
generate sdf-based charging data related to the cellular subscriber device; and
identify a potential over-charging due to an overlap between the application-based charging data and the sdf-based charging data.
0. 25. An apparatus comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processor, cause the apparatus to:
monitor cellular traffic associated with a cellular subscriber device;
generate application detection output indicative of an application used by the cellular subscriber device;
generate, based on the application detection output, application-based charging data related to the cellular subscriber device;
enforce one or more charging rules that are Service Data flow (sdf) based and are related to the cellular subscriber device;
generate sdf-based charging data related to the cellular subscriber device; and
charge based on an overlap between the application-based charging data and the sdf-based charging data.
0. 26. An apparatus comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processor, cause the apparatus to:
monitor cellular traffic associated with a cellular subscriber device;
generate application detection output indicative of an application used by the cellular subscriber device;
set a value of a parameter indicating which of one or more charging rules to apply;
enforce the one or more charging rules that are Service Data flow (sdf) based and are related to the cellular subscriber device;
generate sdf-based charging data related to the cellular subscriber device; and
identify a potential over-charging due to an overlap between the sdf-based charging data and application-based charging data related to the cellular subscriber device and based on the application detection output.
0. 21. An apparatus comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processor, cause the apparatus to:
monitor cellular traffic associated with a cellular subscriber device;
based on the monitored cellular traffic, generate application detection output indicative of an application used by the cellular subscriber device;
enable application-based charging of the cellular subscriber device based on the application detection output and based on one or more application-based charging rules;
enforce one or more charging rules that are Service Data flow (sdf) based and are related to the cellular subscriber device;
generate sdf-based charging data related to the cellular subscriber device; and
identify a potential over-charging due to an overlap between the application-based charging data and the sdf-based charging data.
18. A method of cellular traffic monitoring, the method comprising:
in a traffic detection function (TDF) module, monitoring cellular traffic associated with a cellular subscriber device, and generating application detection output indicative of an application used by the cellular subscriber device;
in an application-based charging module, generating, based on the application detection output of said TDF module, application-based charging data related to said cellular subscriber device;
in a policy charging and enforcement function (PCEF) module, enforcing one or more charging rules that are Service Data flow (sdf) based and are related to said cellular subscriber device;
in an sdf-based charging module, generating sdf-based charging data related to said cellular subscriber device;
in a charging correlator module, identifying a potential over-charging due to an overlap between the application-based charging data and the sdf-based charging data.
0. 23. A method comprising:
monitoring, by a computing device, cellular traffic associated with a cellular subscriber device;
based on the monitored cellular traffic, generating application detection output indicative of an application used by the cellular subscriber device;
enforcing one or more charging rules that are Service Data flow (sdf) based and are related to the cellular subscriber device;
generating sdf-based charging data related to the cellular subscriber device;
detecting an overlap between (i) application-based charging data related to the cellular subscriber device and that is based on the application detection output, and (ii) the sdf-based charging data,
performing an enforcement action with regard to at least some packets, that are transported to or from the cellular subscriber device, based on the application detection output that is indicative of the application used by the cellular subscriber device,
wherein the enforcement action comprises switching off charging for the sdf-based charging data.
1. A cellular traffic monitoring system comprising:
a traffic detection function (TDF) module to monitor cellular traffic associated with a cellular subscriber device, and to generate application detection output indicative of an application used by the cellular subscriber device;
an application-based charging module to generate, based on the application detection output of said TDF module, application-based charging data related to said cellular subscriber device;
a policy charging and enforcement function (PCEF) module to enforce one or more charging rules that are Service Data flow (sdf) based and are related to said cellular subscriber device;
an sdf-based charging module to generate sdf-based charging data related to said cellular subscriber device;
a charging correlator module to identify a potential over-charging due to an overlap between the application-based charging data and the sdf-based charging data,
wherein at least one of: said TDF module, said application-based charging module, said PCEF module, said sdf-based charging module, and said charging correlator module, is implemented by at least a hardware component.
2. The system of
an application detection and Control (ADC) module, associated with said TDF module, to generate an ADC rule indicating an identity of said application used by the cellular subscriber device;
wherein the PCEF module takes into account said ADC rule for generating sdf-based charging data.
3. The system of
a policy and charging Rules function (PCRF) to set a value of a charging Method parameter indicating whether application-based charging or sdf-based charging is to be used in association with cellular traffic of said application used by said cellular subscriber device.
4. The system of
a policy and charging Rules function (PCRF) to set a value of a Measurement Method parameter indicating a method of measurement for charging to be used in association with cellular traffic of said application used by said cellular subscriber device, wherein said value of the Measurement Method parameter indicates to measure charging in accordance with a charging method selected from the group consisting of:
a charging method based on volume of transferred data,
a charging method based on duration of transferred transfer,
a charging method based on both duration and volume of transferred data, and
an event-based charging method.
5. The system of
a policy and charging Rules function (PCRF) to set a value of a Service Identifier Level Reporting parameter indicating whether separate usage reports are required to be generated for a current Service Identifier associated with said application used by said cellular subscriber device.
6. The system of
a policy and charging Rules function (PCRF) set a value of a Service Identifier parameter identifying said application used by said cellular subscriber device, wherein said Service Identifier parameter and a rating group value is utilized via Multiple Services Credit Control (MSCC) per application for application-based charging.
7. The system of
a policy and charging Rules function (PCRF) to set a value of a charging Key parameter indicating a charging tariff to be applied if sdf-based charging is to be performed.
8. The system of
a Generic Tunneling Protocol (GTP) encapsulator to mark in downlink direction, within a GTP extension header, an application type associated with cellular traffic transferred in said downlink direction;
wherein the PCEF module comprises a reflective QoS module to determine, based on said GTP extension header, which cellular packets belong to said application type and to avoid double-counting of said cellular packets in both sdf-based charging and application-based charging.
9. The system of
a Differentiated Services Code Point (DSCP) marking module to mark Internet Protocol (IP) headers of cellular packets that belong to said application used by the cellular subscriber device, as cellular packets that belong to said application;
wherein the PCEF module comprises a reflective QoS module to determine, based on said IP headers marked by said DSCP marking module, which cellular packets belong to said application and to avoid double-counting of said cellular packets in both sdf-based charging and application-based charging.
10. The system of
a charging method selector to selectively activate or deactivate an application-based charging module and an sdf-based charging module to prevent over-charging due to an overlap between the application-based charging data and the sdf-based charging data.
11. The system of
a packet count adjuster to adjust a count of cellular packets transferred to said cellular subscriber device, based on output generated by said charging correlator module, to prevent over-charging due to overlap between the application-based charging data and the sdf-based charging data.
12. The system of
13. The system of
a policy and charging Rules function (PCRF) to generate a charging rule in accordance with subscriber data, and to send said charging rule to the TDF module;
wherein the TDF module is to apply said charging rule within an application-based charging operation.
14. The system of
a policy and charging Rules function (PCRF) to provide to the TDF module all downlink-direction sdfs that are covered by at least one policy charging and Control (PCC) rule;
wherein the TDF module is to enforce a bandwidth limitation in downlink direction for said downlink-direction sdfs.
15. The system of
16. The system of
17. The system of
0. 20. The apparatus of claim 19, wherein the instructions, when executed by the one or more processors, further cause the apparatus to:
monitor cellular traffic associated with the cellular subscriber device.
0. 22. The apparatus of claim 21, wherein the instructions, when executed by the one or more processors, further cause the apparatus to:
establish a session with one or more of an online charging server configured to perform the application-based charging or an offline charging server configured to perform the application-based charging.
0. 24. The method of claim 23,
wherein the computing device is a wireless communication unit.
|
|||||||||||||||||||
This application FIGS. 2A-2M are flow diagrams illustrating the operation of a cellular traffic monitoring system according to the disclosure.FIGS. 2A-2M are flow diagrams illustrating the operation of a cellular traffic monitoring system according to the disclosure. In step 201, a Traffic Detection Function (TDF) module monitors cellular traffic associated with a cellular subscriber device. In step 203, the TDF module generates application detection output indicative of an application used by the cellular subscriber device. In step 205, an application-based charging module generates, based on the application detection output of the TDF module, application-based charging data related to the cellular subscriber device. In step 207, a Policy Charging and Enforcement Function (PCEF) module enforces one or more charging rules that are Service Data Flow (SDF) based and are related to the cellular subscriber device. In step 209, an Application Detection and Control (ADC) module, associated with the TDF module, generates an ADC rule indicating an identity of the application used by the cellular subscriber device before proceeding to step 211. Alternatively, step 211 may be proceeded to directly after step 207, where in step 211 an SDF-based charging module generates SDF-based charging data related to the cellular subscriber device. If following step 209, in step 211, the PCEF module takes into account the ADC rule for generating SDF-based charging data. In step 213, a charging correlator module identifies a potential over-charging due to an overlap between the application-based charging data and the SDF-based charging data. Alternatively, the process may proceed starting at step 203.
In step 215 in FIG. 2B, a Policy and Charging Rules Function (PCRF) sets a value of a Charging Method parameter indicating whether application-based charging or SDF-based charging is to be used in association with cellular traffic of the application used by the cellular subscriber device before proceeding to step 201. In step 217 in FIG. 2C, a PCRF sets a value of a Measurement Method parameter indicating a method of measurement for charging to be used in association with cellular traffic of the application used by the cellular subscriber device before proceeding to step 201. In step 219 in FIG. 2D, a PCRF sets a value of a Service Identifier Level Reporting parameter indicating whether separate usage reports are required to be generated for a current Service Identifier associated with the application used by the cellular subscriber device before proceeding to step 201. In step 221 in FIG. 2E, a PCRF sets a value of a Service Identifier parameter identifying the application used by the cellular subscriber device, wherein the Service Identifier parameter and a rating group value is utilized via Multiple Services Credit Control (MSCC) per application for application-based charging before proceeding to step 201. In step 223 in FIG. 2F, a PCRF sets a value of a Charging Key parameter indicating a charging tariff to be applied if SDF-based charging is to be performed before proceeding to step 201. In step 225 in FIG. 2G, a Generic Tunneling Protocol (GTP) encapsulator marks in downlink direction, within a GTP extension header, an application type associated with cellular traffic transferred in the downlink direction. In step 227, the PCEF module comprises a reflective QoS module to determine, based on the GTP extension header, which cellular packets belong to the application type and to avoid double-counting of the cellular packets in both SDF-based charging and application-based charging before proceeding to step 201. In step 229 in FIG. 2H, a Differentiated Services Code Point (DSCP) marking module marks Internet Protocol (IP) headers of cellular packets that belong to the application used by the cellular subscriber device, as cellular packets that belong to the application. In step 231, a reflective QoS module, of the PCEF module, determines, based on the IP headers marked by the DSCP marking module, which cellular packets belong to the application and to avoid double-counting of the cellular packets in both SDF-based charging and application-based charging before proceeding to step 201. In step 233 in FIG. 2I, a charging method selector selectively activates or deactivates an application-based charging module and an SDF-based charging module prevents over-charging due to an overlap between the application-based charging data and the SDF-based charging data before proceeding to step 201. In step 235 in FIG. 2J, a packet count adjuster adjusts a count of cellular packets transferred to the cellular subscriber device, based on output generated by the charging correlator module, to prevent over-charging due to overlap between the application-based charging data and the SDF-based charging data before proceeding to step 201. In step 237 in FIG. 2K, the cellular traffic monitoring system utilizes a charging algorithm which assumes that the SDF is non-deducible from the detected application, regardless of whether or not the SDF is deducible from the detected application before proceeding to step 201. In step 239 in FIG. 2L, a PCRF generates a charging rule in accordance with subscriber data and sends the charging rule to the TDF module, where the TDF module applies the charging rule within an application-based charging operation before proceeding to step 201. In step 241 in FIG. 2M, a PCRF provides to the TDF module all downlink-direction SDFs that are covered by at least one Policy Charging and Control (PCC) rule and the TDF module enforces a bandwidth limitation in downlink direction for the downlink-direction SDFs before proceeding to step 201. Alternatively, following step 241, in step 243 if the downlink-direction SDFs belong to an application that requires reporting to a charging system, the TDF module (a) obtains a usage monitoring report about usage of the downlink-direction SDFs, and (b) utilizes the usage monitoring report to prevent over-charging before proceeding to step 201. In another alternative, following step 241, in step 245 if the downlink-direction SDFs belong to an application that requires reporting to a charging system, the PCRF adjusts an Application Data and Control (ADC) rule for the application in downlink direction to match an enforcement action defined in one or more PCC Rules for the SDFs belonging to the detected application before proceeding to step 201. In still another alternative, following step 241, in step 247 if the downlink-direction SDFs belong to an application that requires reporting to a charging system, the TDF module (a) obtains Quality of Service (QoS) information about the downlink-direction SDFs, and (b) transfers the QoS information about the downlink-direction SDFs to a charging system together with an application ID corresponding to the downlink-direction SDFs before proceeding to step 201.
FIGS. 3A-3B are flow diagrams illustrating the operation of a cellular traffic monitoring apparatus according to the disclosure utilizing one or more processors and memory storing instructions that, when executed by the one or more processor, cause the apparatus to perform the operation of FIG. 3A or FIG. 3B. In step 301, the one or more processors monitors cellular traffic associated with a cellular subscriber device. In step 303, the one or more processors generates, based on the monitored cellular traffic, application detection output indicative of an application used by the cellular subscriber device. In step 305, the one or more processors enables application-based charging of the cellular subscriber device based on the application detection output and based on one or more application-based charging rules. In step 307, the one or more processors enforces one or more charging rules that are Service Data Flow (SDF) based and are related to the cellular subscriber device. In step 309, the one or more processors generates SDF-based charging data related to the cellular subscriber device. In step 311, the one or more processors identifies a potential over-charging due to an overlap between the application-based charging data and the SDF-based charging data. In step 313 in FIG. 3B, the one or more processors establishes a session with one or more of an online charging server configured to perform the application-based charging or an offline charging server configured to perform the application-based charging before proceeding to step 301.
FIGS. 4A-4B are flow diagrams illustrating the operation of a cellular traffic monitoring system according to the disclosure. In step 401, a computing device monitors cellular traffic associated with a cellular subscriber device. In step 403, application detection output indicative of an application used by the cellular subscriber device is generated based on the monitored cellular traffic. In step 405, one or more charging rules that are Service Data Flow (SDF) based and are related to the cellular subscriber device are enforced. In step 407, SDF-based charging data related to the cellular subscriber device is generated. In step 409, a potential over-charging due to an overlap between the application-based charging data and the SDF-based charging data is identified. In step 411 in FIG. 4B, an enforcement action with regard to at least some packets, that are transported to or from the cellular subscriber device, based on the application detection output that is indicative of the application used by the cellular subscriber device is performed before proceeding to step 401. Alternatively, following step 411, in step 413 charging for the SDF-based charging data is switched off before proceeding to step 401.
FIG. 5 is a flow diagram illustrating the operation of a cellular traffic monitoring apparatus according to the disclosure utilizing one or more processors and memory storing instructions that, when executed by the one or more processor, cause the apparatus to perform the operation of FIG. 5. In step 501, the one or more processors monitors cellular traffic associated with a cellular subscriber device. In step 503, the one or more processors generates application detection output indicative of an application used by the cellular subscriber device. In step 505, the one or more processors generates, based on the application detection output, application-based charging data related to the cellular subscriber device. In step 507, the one or more processors enforces one or more charging rules that are Service Data Flow (SDF) based and are related to the cellular subscriber device. In step 309, the one or more processors generates SDF-based charging data related to the cellular subscriber device. In step 311, the one or more processors charges based on an overlap between the application-based charging data and the SDF-based charging data.
FIG. 6 is a flow diagram illustrating the operation of a cellular traffic monitoring apparatus according to the disclosure utilizing one or more processors and memory storing instructions that, when executed by the one or more processor, cause the apparatus to perform the operation of FIG. 6. In step 601, the one or more processors monitors cellular traffic associated with a cellular subscriber device. In step 603, the one or more processors generates application detection output indicative of an application used by the cellular subscriber device. In step 605, the one or more processors sets a value of a parameter indicating which of one or more charging rules to apply. In step 607, the one or more processors enforces one or more charging rules that are Service Data Flow (SDF) based and are related to the cellular subscriber device. In step 609, the one or more processors generates SDF-based charging data related to the cellular subscriber device. In step 611, the one or more processors identifies a potential over-charging due to an overlap between the SDF-based charging data and application-based charging data related to the cellular subscriber device and based on the application detection output.
It is noted that the drawings may show demonstrative implementations of links, interfaces and/or connections; yet other suitable links, interfaces or connections may be used in accordance with the present invention. For example, Gyn interface may be used instead of Gy interface; Gzn interface may be used instead of Gz interface; or the like.
The present invention may be implemented by using any suitable combination of hardware components and/or software modules; and may utilize, for example, processors, controllers, Integrated Circuits (ICs), logic units, memory units, storage units, buffers, modems, radios, transmitters, receivers, transmitters, wireless communication units, wired communication units, cellular communication units, routers, hubs, switches, antennas, power sources, distributed architecture, client/server architecture, peer-to-peer architecture, Operating Systems, drivers, firmware, software applications, stand-alone units or systems, integrated system or units, or any suitable combination thereof.
Functions, operations, components and/or features described herein with reference to one or more embodiments, may be combined with, or may be utilized in combination with, one or more other functions, operations, components and/or features described herein with reference to one or more other embodiments, or vice versa.
While certain features of some embodiments of the present invention have been illustrated and described herein, many modifications, substitutions, changes, and equivalents may occur to those skilled in the art. Accordingly, the claims are intended to cover all such modifications, substitutions, changes, and equivalents.
| Patent | Priority | Assignee | Title |
| 11563756, | Apr 15 2020 | CrowdStrike, Inc. | Distributed digital security system |
| 11616790, | Apr 15 2020 | CrowdStrike, Inc. | Distributed digital security system |
| 11645397, | Apr 15 2020 | Crowd Strike, Inc. | Distributed digital security system |
| 11711379, | Apr 15 2020 | CrowdStrike, Inc. | Distributed digital security system |
| 11836137, | May 19 2021 | CROWDSTRIKE, INC | Real-time streaming graph queries |
| 11861019, | Apr 15 2020 | CrowdStrike, Inc. | Distributed digital security system |
| ER2399, | |||
| ER2707, |
| Patent | Priority | Assignee | Title |
| 6347224, | Mar 29 1996 | British Telecommunications public limited company | Charging systems for services in communications |
| 8880023, | Dec 09 2010 | ALLOT LTD | Device, system, and method of cellular traffic monitoring |
| 9065936, | Dec 09 2010 | ALLOT LTD | Cellular traffic monitoring and charging using application detection rules |
| 9179008, | Dec 09 2010 | ALLOT LTD | Cellular traffic monitoring and charging using application detection rules |
| 9258742, | Sep 30 2013 | Juniper Networks, Inc. | Policy-directed value-added services chaining |
| 20060111077, | |||
| 20080056304, | |||
| 20090141625, | |||
| 20090182883, | |||
| 20100191612, | |||
| 20100287121, | |||
| 20110106933, | |||
| 20110202485, | |||
| 20110202653, | |||
| 20110208853, | |||
| 20110296489, | |||
| 20120233325, | |||
| 20130054800, | |||
| EP2466932, | |||
| EP2648367, | |||
| WO2010051853, | |||
| WO2012097676, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Aug 05 2013 | GOLDNER, ALLA | ALLOT COMMUNICATIONS LTD | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 065143 | /0156 | |
| May 02 2018 | Allot Ltd. | (assignment on the face of the patent) | / | |||
| Oct 24 2018 | ALLOT COMMUNICATIONS LTD | ALLOT LTD | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 048451 | /0243 |
| Date | Maintenance Fee Events |
| May 02 2018 | BIG: Entity status set to Undiscounted (note the period is included in the code). |
| May 02 2018 | BIG: Entity status set to Undiscounted (note the period is included in the code). |
| May 04 2018 | SMAL: Entity status set to Small. |
| May 04 2018 | SMAL: Entity status set to Small. |
| Oct 15 2023 | BIG: Entity status set to Undiscounted (note the period is included in the code). |
| Oct 19 2023 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
| Date | Maintenance Schedule |
| Jul 20 2024 | 4 years fee payment window open |
| Jan 20 2025 | 6 months grace period start (w surcharge) |
| Jul 20 2025 | patent expiry (for year 4) |
| Jul 20 2027 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Jul 20 2028 | 8 years fee payment window open |
| Jan 20 2029 | 6 months grace period start (w surcharge) |
| Jul 20 2029 | patent expiry (for year 8) |
| Jul 20 2031 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Jul 20 2032 | 12 years fee payment window open |
| Jan 20 2033 | 6 months grace period start (w surcharge) |
| Jul 20 2033 | patent expiry (for year 12) |
| Jul 20 2035 | 2 years to revive unintentionally abandoned end. (for year 12) |