METHOD AND SYSTEM FOR PROVIDING NETWORK SERVICES

• US 20120089677A1
• Filed: 10/04/2011
• Published: 04/12/2012
• Est. Priority Date: 10/08/2010
• Status: Active Grant

• Current Assignee: F5 Networks, Inc. (F5 Incorporated)
• Original Assignee: Traffic Systems LLC
• Inventors: Shafran, Gil, Ridel, Lenny
• Granted Patent: US 8,738,700 B2
• Time in Patent Office: Days
• US Class Current: 709/204
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 67/288 Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Abstract

The present invention provides a system for intermediating between client nodes and pools of server nodes in an NGN network where the server nodes provide network services to client nodes, wherein the client nodes use various communication protocols and at least part of said communication protocols are different from the communication protocol used by the server nodes. The system comprising: a cluster of associated gateway nodes providing an integrated service for the clients nodes, where each gateway provides services of at least one of: translations of request and answers between the client node and a provider server node, load balancing and managing scenario rules. Each gateway comprise: a database of scripts including, scenario rules, routing scripts and associated transformation scripts, an execution processing module for handling events of at least client requests and server answers according to scenario rules.

Claims

1. A system for intermediating between client nodes and pools of server nodes in an NGN network where the server nodes provide network services to client nodes, wherein the client nodes use various communication protocols and at least part of said communication protocols are different from the communication protocol used by the server nodes, said system comprising;

a cluster of associated gateway nodes providing an integrated service for the clients nodes, where each gateway provides services of at least one of;

translations of request and answers between the client node and a provider server node, load balancing and managing scenario rules, each gateway comprising;

i. a database of scripts including, scenario rules, routing scripts and associated transformation scripts;

ii. an execution processing module for handling events of at least client requests and server answers according to scenario rules, said module including;

ii. a routing manager for selecting the appropriate routing script for the incoming messages or answers from the servers by selecting at least routing script according to the request properties, client profile and session history, where the selected routing script determines the destination server or pools of servers;

iii. a transformation manager for selecting the appropriate transformation script for the incoming messages or answers according to the selected routing script, the request properties, client profile and information of session history;

iv. scenario manager for applying scenario rules on incoming requests and the received answers for generating new subsequence requests derived from clients original requests and received answers;

wherein the handling of the clients requests and generated subsequence request includes activating rules of the selected scripts for transforming sequence of incoming user requests into sequence of transformed requests adapted to destination server communication protocols and transforming sequence of answers coming form the server into sequence of transformed answers adapted to clients nodes communication protocols, where the sequence of incoming user requests or answers includes consecutive client requests or answers having a correlated context.

2. The system of claim 1 wherein the scenario rules define analyzing the requests content and properties for deriving new subsequence requests or answers which perform actions for completing the execution of the original client request.

3. The system of claim 1 wherein the scenario rules define analyzing the requests or answers content and properties for deriving new subsequence equivalent requests which are transmitted in parallel to different servers.

4. The system of claim 1 wherein the gateway nodes are interconnected through peer to peer connections.

5. The system of claim 1 wherein the sequence of requests having correlated context is a single session flow.

6. The system of claim 1 wherein the selection of the routing scripts and the transformation scripts is preformed by checking at least part of the transformation scripts and checking at least part of the routing scripts.

7. The system of claim 1 wherein execution processing module further handles timeout events, error events, and maintenance events.

8. The system of claim 1 wherein the database structure is hierarchical and each routing script is related to a plurality of transformation scripts and each scenario rule is related to plurality of routing scripts.

9. A method for intermediating between client node and pools of server nodes in an NGN network where the server nodes provide network services to client nodes, wherein the client nodes use various communication protocols, wherein at least part of said communication protocols are different from the communication protocol used by the server nodes, said method comprising;

i. receiving incoming requests from client nodes;

ii. temporarily recording sequence of incoming requests having correlated context.

iii. generating subsequent derived requests by analyzing the received incoming request from the client according to scenario rules;

iv. selecting the appropriate routing script for each message according to request properties, client profile and session history.

v. determining the destination pool of servers of at least one server according to selected routing script;

vi. selecting the appropriate transformation script for each message according to the selected routing script, the request properties, client profile and session history.

vii. identifying end of client request sequence according context of requests;

viii. activating rules of the selected scripts for transforming sequence of incoming user requests into seqaence of transformed requests adapted to destination servers communication protocols, where the sequence of incoming user requests are consecutive client requests having a correlated context.

ix. sending transformed requests to destination servers;

x. receiving answers from servers;

xi. temporarily recording sequence of received answers related to a correlated context;

xii. applying selected transformation script to adapt recorded sequence answers related to a correlated context, to the client node protocol;

xiii. analyzing answers according to scenarios rules, for generating new subsequent request or activating originating request utilizing the received answers; and

xiv. sending transformed answers to client nodes.

10. The method of claim 9 wherein the selection of the routing scripts and the transformation scripts is preformed by checking at least part of the transformation scripts and checking at least part of the routing scripts.

11. The method of claim 9 wherein the sequence of requests or answers are related to a single session flow.

12. The method of claim 9 wherein the scenario rules define analyzing the requests content and properties for deriving new serial subsequence requests which perform actions for completing the execution of the original client request.

13. The method of claim 9 wherein the scenario rules define analyzing the requests content and properties for deriving parallel new subsequence equivalent requests which are transmitted in parallel to different destination servers.

14. The method of claim 9 wherein at least part of the scenario rules define deriving new serial subsequence equivalent requests which are transmitted in parallel to different destination servers.

15. The method of claim 13 wherein the scenario rules enable deriving parallel new subsequence equivalent requests originated from serial subsequence request, said parallel requests are transmitted simultaneously to different destination servers.

16. The method of claim 9 wherein the at least some of the requests are originated from the server.