Method for implementing an internet protocol (ip) charging and rating middleware platform and gateway system
Abstract
A method for Internet Protocol (IP) charging and rating gateway within a system having: a proxy server for connection to an Authentication, Authorization, and Accounting (AAA) server; an access gateway, an IP classification engine for connection between a data network and the access gateway; and a gateway controller connected to the proxy server and the IP classification engine, including the steps of: receiving IP packets at the IP classification engine, the IP packets originating from the data network and destined for a subscriber device via the access gateway; classifying the IP packets according to the protocol of each of the packets at the IP classification engine; and selectively instructing the IP classification engine to permit or deny the flow of IP packets between the data network and the access gateway at the gateway controller. Preferably, the proxy server is configured to emulate the access gateway and the AAA server.
Claims
exact text as granted — not AI-modified1 - 14 . (canceled)
15 . A method comprising:
receiving IP packets at an IP classification engine connected between a data network and an access gateway, said IP packets originating from said data network and destined for a subscriber device via said access gateway; determining a type of said IP packets at said IP classification engine based on a protocol type of said IP packets; updating, by a gateway controller connected to said IP classification engine, a subscriber balance stored at an account server, based on said determined type of said packet and on rating rules associated with said subscriber device; and at said IP classification engine, permitting or denying the flow of said IP packets associated with said subscriber device between said data network and said access gateway.
16 . The method of claim 15 , further comprising: loading said rating rules into said IP classification engine prior to receiving said IP packets.
17 . The method of claim 16 , further comprising: arming one or more triggers in said IP Classification Engine, each trigger for detecting an event selected from a protocol state, a destination identifier, a time of day, a text string, a message content, and a volume of data.
18 . The method of claim 17 , wherein said triggers are armed based on attributes associated with OSI layers 2-7 including protocol-specific attributes and according to said protocol type of said IP packets, said protocol type including at least one of HTTP, POP3, SMTP, MMS, FTP, and WAP.
19 . The method of claim 18 , further comprising: prior to receiving said IP packet, creating a decision tree at said IP classification engine based on said rating rules, said decision tree for analyzing and determining said type of said IP packets.
20 . The method of claim 19 , wherein determining said type of said IP packet includes analyzing said IP packets using said decision tree.
21 . The method of claim 15 , wherein denying the flow of further IP packets comprises:
receiving at said gateway controller, from said account server, an indication that flow of said IP packets is not permitted; and instructing said IP classification engine to drop or redirect the flow of said IP packets between said data network and said subscriber device.
22 . The method of claim 15 , wherein the access gateway comprises one of a Gateway GPRS Support Node (GGSN) and a Packet Data Service Node (PDSN).
23 . The method of claim 15 , wherein said permitting or denying is performed according to said determined type of said IP packets.
24 . The method of claim 23 , wherein said denying comprises dropping or redirecting said IP packets.
25 . The method of claim 15 , wherein said protocol type includes one or more of: Hyper Text Transfer Protocol (“HTTP”), Post Office Protocol (“POP3”), Simple Mail Transfer Protocol (“SMTP”), File Transfer Protocol (“FTP”), Multi-media Messaging Service (“MMS”), Wireless Application Protocol (“WAP”), Real Time Protocol (“RTP”), and Real Time Streaming Protocol (“RTSP”).
26 . A system comprising:
an IP classification engine connected between a data network and an access gateway; and a gateway controller connected to said IP classification engine; said IP classification engine configured to:
receive IP packets, said IP packets originating from said data network and destined for a subscriber device via said access gateway;
determine a type of said IP packets at said IP classification engine based on a protocol type of said IP packets; and
permit or deny the flow of said IP packets associated with said subscriber device between said data network and said access gateway;
said gateway controller configured to update a subscriber balance stored at an account server, based on said determined type of said packet and on rating rules associated with said subscriber device.
27 . A non-transitory computer readable medium storing computer readable instructions executable by a processor of a system having an IP classification engine, connected between a data network and an access gateway, and a gateway controller connected to said IP classification engine, said computer readable instructions for implementing a method comprising:
receiving IP packets at said IP classification engine, said IP packets originating from said data network and destined for a subscriber device via said access gateway; determining a type of said IP packets at said IP classification engine based on a protocol type of said IP packets; updating, by said gateway controller, a subscriber balance stored at an account server, based on said determined type of said packet and on rating rules associated with said subscriber device; and at said IP classification engine, permitting or denying the flow of said IP packets associated with said subscriber device between said data network and said access gateway.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.