Platform and method for providing data services in a communication network

• US 7,586,871 B2
• Filed: 01/11/2006
• Issued: 09/08/2009
• Est. Priority Date: 05/22/2001
• Status: Expired due to Term

• Current Assignee: OptiMorphix, Inc.
• Original Assignee: Bytemobile Network Services Corporation
• Inventors: Chen, Chuanfei, Hamilton, Thomas E., Descoteaux, Kenneth Gerard, Atwood, Clifford S.
• Primary Examiner(s): Chan; Wing F
• Assistant Examiner(s): Jones; Prenell P
• Application Number:
  US11/330,588
• Publication Number:
  US 20060114832A1
• Time in Patent Office: 1,336 Days
• Field of Search: 370/465, 370/338, 370/352, 370/410, 370/356, 370/349, 370/401, 370/389, 370/254, 370/466, 379/265, 379/229, 455/433, 455/432, 455/427, 455/512, 455/560, 709/200, 709/223, 709/225, 709/219, 709/229, 709/224, 709/206, 707/9
• US Class Current: 370/328
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5029 Service quality level-based billing, e.g. dependent on measured service level customer is charged more or less
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/091 Measuring contribution of individual network components to actual service level
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04M 15/43 Billing software details
• CPC Class Codes: H04M 15/51 for resellers, retailers or service providers
• CPC Class Codes: H04M 15/55 for hybrid networks
• CPC Class Codes: H04M 2215/2033 WLAN
• CPC Class Codes: H04M 2215/204 UMTS; GPRS
• CPC Class Codes: H04M 2215/2046 Hybrid network
• CPC Class Codes: H04M 2215/54 Resellers-retail or service providers billing, e.g. agreements with telephone service operator, activation, charging/recharging of accounts
• CPC Class Codes: H04W 24/00 Supervisory, monitoring or testing arrangements
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor
• CPC Class Codes: H04W 4/24 : Accounting or billing
• CPC Class Codes: H04W 76/20 : Manipulation of established connections
• CPC Class Codes: H04W 88/16 : Gateway arrangements
• CPC Class Codes: H04W 92/02 : Inter-networking arrangements

Abstract

A communication node and corresponding method for processing data communication passing through the node between a first data network and a second data network is described. The method includes detecting an event associated with data communication arriving at the node from the first data network, and determining whether the data communication is to be suspended for service at the node based on the detected event. Suspended data communication is processed based on information in the data communication. Return data communication arriving at the node from the second data network in response to the processed data communication from the first data network is detected. The detected return data communication is allowed to pass through the node without processing the detected return data communication.

Claims

1. A method for processing data communication passing through a node between a first data network and a second data network, the method comprising:

detecting an event associated with data communication arriving at the node from the first data network;

determining whether the data communication is to be suspended for service at the node based on the detected event;

processing suspended data communication based on information in the data communication; and

detecting return data communication arriving at the node from the second data network in response to the processed data communication from the first data network, and allowing the detected return data communication to pass through the node without processing the detected return data communication.

2. The method of claim 1, wherein the event is detected at communication protocol layers implemented in hardware without the need for assistance from communication protocol layers implemented in software.

3. The method of claim 1, wherein the event is detected without requiring processing to terminate or establish a communication session associated with the data communication.

4. The method of claim 1, wherein the event is detected at an external node in communication with the node, and the external node suspends the data communication for service at the node based on the detected event.

5. The method of claim 4, wherein the external node communicates with the node using commands associated with an application programming interface for the node.

6. The method of claim 1, wherein processing the data communication comprises determining whether the data communication should be continued or discontinued.

7. The method of claim 1, wherein processing the data communication based on information in the data communication comprises:

categorizing request information in the data communication based on a categorization database; and

determining whether the data communication should be continued or discontinued based on the categorizing.

8. The method of claim 7, wherein determining whether the data communication should be continued or discontinued is further based on stored metadata.

9. The method of claim 7, wherein the request information is categorized after determining whether information in the data communication corresponds to an entry in a list.

10. The method of claim 1, wherein processing the data communication based on information in the data communication comprises determining whether the data communication should be continued or discontinued based on whether information in the data communication corresponds to an entry in a list.

11. The method of claim 10, wherein the list comprises a black list and the data communication is discontinued if information in the data communication corresponds to an entry in the black list.

12. The method of claim 11, wherein discontinuing the data communication comprises responding to the data communication with a reply indicating that a request associated with the data communication is denied.

13. The method of claim 10, wherein the list comprises a white list and the data communication is continued if information in the data communication corresponds to an entry in the white list.

14. The method of claim 10, wherein the entry in the list indicates whether the data communication should be continued or discontinued based on a determined identity of a subscriber associated with the data communication.

15. The method of claim 1, wherein processing the data communication comprises processing the data communication based on a determined identity of a subscriber associated with the data communication.

16. The method of claim 1, wherein detecting the event comprises detecting a request for access to a resource.

17. The method of claim 16, wherein the request comprises at least a portion of a uniform resource locator.

18. The method of claim 16, wherein detecting the request comprises identifying a data packet in a flow of data packets.

19. The method of claim 16, wherein detecting the request comprises transforming a request string to generate information identifying the resource.

20. The method of claim 19, wherein the request string comprises an address corresponding to a cache storing content associated with the resource.

21. The method of claim 16, wherein detecting the request comprises detecting a request for access to a resource identified as illegal content.

22. The method of claim 21, wherein the request is detected at communication protocol layers implemented in hardware without the need for assistance from communication protocol layers implemented in software.

23. The method of claim 1, wherein detecting the event comprises detecting a protocol state based on characteristics of the data communication.

24. The method of claim 23, wherein detecting the event comprises detecting a protocol state based on protocol information in a header of a packet of the data communication.

25. The method of claim 23, wherein detecting the event comprises detecting a protocol state based on protocol information in a payload of a packet of the data communication.

26. The method of claim 25, wherein the protocol information in the payload of the packet comprises application layer protocol information.

27. The method of claim 23, wherein detecting the event comprises detecting states of a Hyper Text Transport Protocol (HTTP).

28. The method of claim 23, wherein detecting the event comprises detecting states of a Wireless Application Protocol (WAP).

29. The method of claim 1, wherein the data communication comprises a flow of packets.

30. The method of claim 29, wherein the flow of packets comprises Internet Protocol (IP) packets.

31. A communication node for processing data communication passing through the node between a first data network and a second data network, the node comprising:

means for detecting an event associated with data communication arriving at the node from the first data network;

means for determining whether the data communication is to be suspended for service at the node based on the detected event;

means for processing suspended data communication based on information in the data communication; and

means for detecting return data communication arriving at the node from the second data network in response to the processed data communication from the first data network, and allowing the detected return data communication to pass through the node without processing the detected return data communication.

32. The communication node of claim 31, wherein the event is detected at communication protocol layers implemented in hardware without the need for assistance from communication protocol layers implemented in software.

33. The communication node of claim 31, wherein the event is detected without requiring processing to terminate or establish a communication session associated with the data communication.

34. A communication node for processing data communication passing through the node between a first data network and a second data network, the node comprising:

a packet inspection engine including circuitry to

detect an event associated with data communication arriving at the node from the first data network, and

determine whether the data communication is to be suspended for service at the node based on the detected event; and

a content filtering engine including circuitry to process suspended data communication based on information in the data communication;

wherein the packet inspection engine is configured to detect return data communication arriving at the node from the second data network in response to the processed data communication from the first data network, and allow the detected return data communication to pass through the node without processing the detected return data communication in the content filtering engine.

35. The communication node of claim 34, wherein the event is detected at communication protocol layers implemented in hardware without the need for assistance from communication protocol layers implemented in software.

36. The communication node of claim 34, wherein the event is detected without requiring processing to terminate or establish a communication session associated with the data communication.