IP Library Granted Patent US 7,710,955
Granted Patent B2
US 7,710,955 · App. 10/197,402 · Granted May 4, 2010

Taking account of information relating to the environment of active nodes when determining the code associated with an active application

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,710,955
App. No.
10/197,402
Granted
May 4, 2010
Kind
B2
Abstract

We describe an active node, which receives an active message containing an active application identifier, transmits the active application identifier to an active applications server. receives associated code from the active applications server, and executes the associated code. The active node also may transmit to the active applications server information relating to its own environment, and information relating to whether it is an edge node or core node in the network, enabling the active applications server to determine the associated code to return to the active node.

Claims (41)

1. An active node, comprising:

means for receiving an active message, said active message containing an active application identifier;

means for transmitting said active application identifier to an active applications server;

means for receiving associated code from said active applications server, said associated code comprising an active application identified by said active application identifier;

means for executing said associated code; and

means for transmitting to said active applications server information relating to an environment of said active node.

2. An active node according to claim 1 , wherein said information relating to an environment of said active node comprises an identifier of the execution environment of said active node.

3. An active node according to claim 1 , wherein said information relating to an environment of said active node comprises information indicating whether said active node is a core or an edge node.

4. An active applications server comprising:

means for receiving an active application identifier from an active node;

association means for determining associated code depending on said active application identifier, said associated code comprising an active application;

means for transmitting said associated code to said active node; and

means for receiving information relating to an environment of said active node;

wherein said association means determines said associated code as a function of said information relating to an environment of said active node.

5. An active applications server according to claim 4 , in which said information relating to an environment of said active node comprises an identifier of the execution environment of said active node.

6. An active applications server according to claim 4 , in which said information relating to an environment of said active node comprises information indicating whether said active node is a core or an edge node.

7. A method of forwarding an active message via an active node, comprising:

receiving said active message, said active message containing an active application identifier;

sending a request message to an active applications server, the message containing said active application identifier;

receiving associated code from said active applications server, said associated code determined by said active applications server as a function of said active application identifier;

executing said associated code; and

forwarding the active message to a following active node;

wherein said request message contains information relating to an environment of said active node, and the associated code is determined by said active applications server as a function of said information.

8. A method according to claim 7 , in which said information relating to an environment of said active node comprises an identifier of the execution environment of said active node.

9. A method according to claim 7 , in which said information relating to an environment of said active node comprises information indicating whether said active node is a core or an edge node.

10. A method according to claim 7 , in which said request message complies with the HTTP protocol.

11. A method according to claim 7 , wherein said active node comprises a router.

12. A method according to claim 7 , wherein said active message is received from a source active node.

13. A method according to claim 12 , wherein said source active node comprises a router.

14. A method according to claim 7 , wherein said active node executes said active application to manage network traffic.

15. An active node according to claim 1 , said active node comprising a router.

16. An active node according to claim 1 , wherein said active message is received from a source active node.

17. An active node according to claim 16 , wherein said source active node comprises a router.

18. An active node according to claim 1 , wherein said active node executes said active application to manage network traffic.

19. An active node according to claim 1 , wherein said active node forwards said active message to a following active node.

20. A according to claim 4 , wherein said active node comprises a router.

21. A server according to claim 4 , wherein said active message is received from a source active node.

22. A server according to claim 21 , wherein said source active node comprises a router.

23. A server according to claim 4 , wherein said active node executes said active application to manage network traffic.

24. A server according to claim 4 , wherein said active node forwards said active message to a following active node.

25. An active node according to claim 1 , wherein said associated code is determined by said active applications server as a function of said information relating to an environment of said active node.

Assignments (6)
CHANGE OF NAME Recorded Jan 27, 2022
From: FACEBOOK, INC.
To: META PLATFORMS, INC.
Reel/Frame 058871/0336 →
RELEASE OF SECURITY INTEREST Recorded Dec 12, 2018
From: NOKIA USA INC.
To: PROVENANCE ASSET GROUP, LLC
Reel/Frame 047791/0566 →
RELEASE OF SECURITY INTEREST Recorded Dec 12, 2018
From: NOKIA USA INC.
To: PROVENANCE ASSET GROUP HOLDINGS LLC
Reel/Frame 049139/0088 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 3, 2018
From: PROVENANCE ASSET GROUP LLC
To: FACEBOOK, INC.
Reel/Frame 047190/0360 →
PARTIAL RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 043967/0001 Recorded Aug 30, 2018
From: CORTLAND CAPITAL MARKET SERVICES LLC
To: PROVENANCE ASSET GROUP, LLC
Reel/Frame 046981/0600 →
SECURITY AGREEMENT Recorded Jan 30, 2013
From: ALCATEL LUCENT
To: CREDIT SUISSE AG
Reel/Frame 029821/0001 →