System and method for performing multi-enforcement point charging

US9686084B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9686084-B2
Application numberUS-201615046844-A
CountryUS
Kind codeB2
Filing dateFeb 18, 2016
Priority dateSep 12, 2012
Publication dateJun 20, 2017
Grant dateJun 20, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Systems and methods for accomplishing charging operations in a communications network in which a plurality of charging and enforcement (CaE) components operate as enforcement points for a single data communication may include receiving in a server computing device usage records from a first CaE component and a second CaE component, generating correlated usage records by using a common Service Data Flow (SDF) to correlate the one or more usage records received from the first CaE component with the one or more records received from the second CaE component, and using the correlated usage records to determine a charge value that identifies correct charges to be applied.

First claim

Opening claim text (preview).

What is claimed is: 1. A method of charging in a communications network in which a plurality of charging and enforcement (CaE) components operate as enforcement points for a single data communication, comprising: receiving, from a first CaE component, one or more usage records related to enforcement of the single data communication by the first CaE component; receiving, from a second CaE component, one or more usage records related to enforcement of the single data communication by the second CaE component; generating correlated usage records related to enforcement of the single data communication by the first CaE component and the second CaE component by using a common Service Data Flow (SDF) to correlate the one or more usage records received from the first CaE component with the one or more usage records received from the second CaE component; and using the correlated usage records related to enforcement of the single data communication to determine a charge value that identifies correct charges to be applied for the single data communication. 2. The method of claim 1 , wherein the first CaE component and the second CaE component operate at different communication architecture layers. 3. The method of claim 2 , wherein: the first CaE component operates at an application layer; and the second CaE component operates at an Internet protocol layer. 4. The method of claim 1 , wherein receiving the one or more usage records related to enforcement of the single data communication by the first CaE component comprises receiving a usage record that includes a SDF identifier. 5. The method of claim 1 , wherein receiving the one or more usage records related to enforcement of the single data communication by the first CaE component comprises receiving application-to-service data flow mapping information. 6. The method of claim 1 , further comprising: receiving, in the second CaE component, information identifying an SDF that is active on the first CaE component; and generating, in the second CaE component, usage information based on the received information identifying the SDF that is active on the first CaE component, wherein receiving the one or more usage records related to enforcement of the single data communication by the second CaE component comprises receiving the usage information from the second CaE component. 7. The method of claim 1 , wherein the first CaE component is one of: a traffic detection function component; and a policy and charging enforcement function component. 8. A server computing device, comprising: a processor configured with processor-executable instructions to perform operations comprising: receiving, from a first CaE component of a plurality of CaE components that operate as enforcement points for a single data communication, one or more usage records related to enforcement of the single data communication by the first CaE component; receiving, from a second CaE component of the plurality of CaE components that operate as enforcement points for the single data communication, one or more usage records related to enforcement of the single data communication by the second CaE component; generating correlated usage records related to enforcement of the single data communication by the first CaE component and the second CaE Component by using a common Service Data Flow (SDF) to correlate the one or more usage records received from the first CaE component with the one or more usage records received from the second CaE component; and using the correlated usage records related to enforcement of the single data communication to determine a charge value that identifies correct charges to be applied for the single data communication. 9. The server computing device of claim 8 , wherein the first CaE component and the second CaE component operate at different communication architecture layers. 10. The server computing device of claim 9 , wherein: the first CaE component operates at an application layer; and the second CaE component operates at an Internet protocol layer. 11. The server computing device of claim 8 , wherein the processor is configured with processor-executable instructions to perform operations such that receiving the one or more usage records related to enforcement of the single data communication by the first CaE component comprises receiving a usage record that includes a SDF identifier. 12. The server computing device of claim 8 , wherein the processor is configured with processor-executable instructions to perform operations such that receiving the one or more usage records related to enforcement of the single data communication by the first CaE component comprises receiving application-to-service data flow mapping information. 13. The server computing device of claim 8 , wherein: the processor is configured with processor-executable instructions to perform operations further comprising: receiving in the second CaE component information identifying an SDF that is active on the first CaE component; and generating in the second CaE component usage information based on the received information identifying the SDF that is active on the first CaE component; and the processor is configured with processor-executable instructions to perform operations such that receiving the one or more usage records related to enforcement of the single data communication by the second CaE component comprises receiving the usage information from the second CaE component. 14. The server computing device of claim 8 , wherein the first CaE component is one of: a traffic detection function component; and a policy and charging enforcement function component. 15. A non-transitory computer readable storage medium having stored thereon processor-executable software instructions configured to cause a processor to perform operations comprising: receiving, from a first CaE component of a plurality of CaE components that operate as enforcement points for a single data communication, one or more usage records related to enforcement of the single data communication by the first CaE component; receiving, from a second CaE component of the plurality of CaE components that operate as enforcement points for the single data communication, one or more records related to enforcement of the single data communication by the second CaE component; generating correlated usage records related to enforcement by the first CaE component and the second CaE component by using a common Service Data Flow (SDF) to correlate the one or more usage records received from the first CaE component with the one or more usage records received from the second CaE component; and using the correlated usage records related to enforcement of the single data communication to determine a charge value that identifies correct charges to be applied for the single data communication. 16. The non-transitory computer readable storage medium of claim 15 , wherein: the first CaE component operates at an application layer; and the second CaE component operates at an Internet protocol layer. 17. The non-transitory computer readable storage medium of claim 15 , wherein the stored processor-executable software instructions are configured to cause a processor to perform operations such that receiving the one or more usage records related to enforcement of the single data communication by the first CaE component comprises receiving a usage record that includes a SDF identifier. 18. The non-transitory computer readable storage medium of claim 15 , wherein the stored processor

Assignees

Inventors

Classifications

  • Accounting or billing · CPC title

  • based on actual use of network resources · CPC title

  • Policy-and-charging control [PCC] architecture · CPC title

  • Electricity · mapped topic

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9686084B2 cover?
Systems and methods for accomplishing charging operations in a communications network in which a plurality of charging and enforcement (CaE) components operate as enforcement points for a single data communication may include receiving in a server computing device usage records from a first CaE component and a second CaE component, generating correlated usage records by using a common Service D…
Who is the assignee on this patent?
Openet Telecom Ltd
What technology area does this patent fall under?
Primary CPC classification H04L12/1407. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Jun 20 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).