Real time correlation of parallel charging events
Abstract
A network providing service to an end user may include a first client, a second client and a charging system. A method implemented by the network may include the first client receiving a service event that is destined for an end user and retrieving a first logical clock value from memory, where the first logical clock value specifies a number of service events received at the second client. The first client may increment a second logical clock value based on receipt of the service event and may construct a first time stamp parameter based on the first logical clock value and the second logical clock value. The first client may send a charging request to a charging system, where the charging request includes the first time stamp parameter and where the charging request requests credit authorization associated with providing the service event to the end user.
Claims
exact text as granted — not AI-modified1 .- 15 . (canceled)
16 . A credit control device, comprising:
a first memory to store a first time stamp parameter received in a first charging request from a first client, where the first time stamp parameter relates to a number of service events received at the first client; a second memory to store a second time stamp parameter received in a second charging request from a second client, where the second time stamp parameter relates to a number of service events received at the second client; a third memory to store a third time stamp parameter maintained at the credit control device that relates to past time stamp parameters received from the first and second clients; and a credit control unit to:
compare the first time stamp parameter with the third time stamp parameter, and
send a service authorization or denial message to the first client based on the comparison.
17 . The credit control device of claim 16 , where the credit control unit is further configured to:
update the third time stamp parameter, based on the comparison, such that the third time stamp parameter corresponds to the first time stamp parameter.
18 . The credit control device of claim 16 , where the credit control unit is further configured to:
compare the second time stamp parameter with the third time stamp parameter, and send a service authorization or denial message to the second client based on the comparison.
19 . The credit control device of claim 18 , where the credit control unit is further configured to:
update the third time stamp parameter, based on the comparison of the second time stamp parameter with the third time stamp parameter, such that the third time stamp parameter corresponds to the second time stamp parameter.
20 . The credit control device of claim 16 , where the service events are associated with one of Multimedia messaging service (MMS) data, a Session Initiation Protocol (SIP) signaling message, or a Hypertext Transfer Protocol (HTTP) message received at the first client.
21 . The credit control device of claim 16 , where the first client comprises a Gateway General Packet Radio Service (GPRS) Support Node (GGSN), the second client comprises a MultiMedia Messaging Service Center (MMSC) and the service events involve Multimedia messaging service (MMS) data.
22 . The credit control device of claim 16 , where the first client comprises a Gateway General Packet Radio Service (GPRS) Support Node (GGSN), the second client comprises a Serving Call Session Control Function (S-CSCF) and the service events involve Session Initiation Protocol (SIP) signaling messages.
23 . The credit control device of claim 16 , where the first client comprises a router, the second client comprises a Serving Call Session Control Function (S-CSCF), and the service events involve Session Initiation Protocol (SIP) signaling messages.
24 . The credit control device of claim 16 , where the first client comprises a Serving Call Session Control Function (S-CSCF), the second client comprises an Internet Protocol (IP) Multimedia Subsystem Application Server (IMS AS), and the service events involve Session Initiation Protocol (SIP) signaling messages.
25 . The credit control device of claim 16 , where the first client comprises a first Internet Protocol (IP) Multimedia Subsystem Application Server (IMS AS), the second client comprises a second IMS AS and the service events involve Session Initiation Protocol (SIP) signaling messages.
26 . The credit control device of claim 16 , where the first client comprises a Gateway General Packet Radio Service (GPRS) Support Node (GGSN), the second client comprises a Wireless Application Protocol (WAP) portal, and the service events involve Hypertext Transfer Protocol (HTTP) messages.Join the waitlist — get patent alerts
Track US2013196624A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.