METHOD AND DEVICES TO SEAMLESSLY INJECT SERVICES IN CONTENT FLOWS

• US 20090150503A1
• Filed: 12/09/2008
• Published: 06/11/2009
• Est. Priority Date: 12/10/2007
• Status: Active Grant

• Current Assignee: RPX Corporation
• Original Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Inventors: Waegeman, Eric Victor, Theeten, Bart Antoon Rika
• Granted Patent: US 8,856,242 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06F 16/957 Browsing optimisation, e.g. caching or content distillation
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• 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

Abstract

A method for automating service invocation in message flows between a client (2100) and a server (2104), includes a step of generating a message (2300) including content by said client (2100), a step of transmitting said message by said client (2100) via a network (2103) to said server (2104), wherein said method further includes a step of intercepting said message (2300) by a message interception device (2105) in the network (2103), and a step of determination by said message interception device (2105) whether a service is needed for further execution on said content part of said message. In case a service is needed, said method includes a further step of selecting at least one service engine for further execution of at least one service on said content part of said message.

Claims

1. Method for automating service invocation in message flows between a client (2100) and a server (2104), said method including a step of generating a message (2300) including content by said client (2100), a step of transmitting said message by said client (2100) via a network (2103) to said server (2104),

wherein said method further includes a step of intercepting said message (2300) by a message interception device (2105) in the network (2103), and a step of determination by said message interception device (2105) whether a service is needed for further execution by at least one service engine (2106) of a service environment network (21032) on said content part of said message.

2. Method according to claim 1 wherein, in case a service is needed, said method includes a further step of selecting at least one service engine (2106) for further execution at least one service on said content part of said message (2300), and a step of adapting said message such as to include the necessary information to further route said message towards said at least one service engine (2106) thereby generating an adapted message (2301).

3. Method according to claim 1 wherein said step of determination is based upon said content included in said message and/or upon information related to said client.

4. Method according to claim 2 further including a step of routing the adapted message (2301) towards said at least one service engine (2106).

5. Method according to claim 4 further including a step of determination, by said service engine (2106) whether an additional service is needed.

6. Message interception device (2105) of a network (2103) between a client (2100) and a server (2104), said message interception device (2105) being adapted to receive a message (2300) including content from said client (2100) with destination to said server(2104), to analyze said message and to determine therefrom whether a service is needed for further execution by a service engine (2106) of a service environment network (21032) on said content part of said message.

7. Message interception device (2105) according to claim 6 further being adapted to determine, in case a service is needed, at least one service engine (2106) for further execution of at least one service on said content part of said message, and to adapt said message such as to further include the necessary information to further route said message to said at least one service engine (2106) thereby generating an adapted message (2301) for transmission to said at least one service engine (2106).

8. Message interception device (2105) according to claim 6 further being adapted to receive client information related to said client and to perform said determination based upon said client information and/or based upon information extracted from said content of said message (2300).

9. Service engine (2106) for executing a service on a content part of a message, said service engine being adapted to receive an adapted message (2301) previously generated by a message interception device (2105) and to determine therefrom whether or not o invoke operation of said service on said content from said adapted message (2301), and to generate a second adapted message (2302) for further provision towards a server (2104) or to said message interception device (2105)

10. Service engine (2106) according to claim 9 further being adapted to determine, from said adapted message (2301), whether an additional service is needed, and to further route said second adapted message (2302) towards an additional service engine.