Methods and systems for changing a topology of a network

• US 7,246,178 B2
• Filed: 05/07/2002
• Issued: 07/17/2007
• Est. Priority Date: 05/07/2002
• Status: Active Grant

• Current Assignee: Avaya Incorporated
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: Kumar, Mahesh, Hansell, Jeffrey Stuart, Roberts, David Gary
• Primary Examiner(s): VU, THONG H
• Application Number:
  US10/141,444
• Publication Number:
  US 20030212776A1
• Time in Patent Office: 1,897 Days
• Field of Search: 709220-225, 709/227, 709/230, 709/217, 709/238, 709/239, 709/203, 709/204, 709/215, 709/250, 370/225, 370/352, 717/158, 717/174, 719/314, 719/313, 710/8
• US Class Current: 709/249
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

Methods and systems for processing a request of changing a first node having a first service connecting with a second node in a network environment are described herein. In one aspect of the invention, an exemplary method includes dynamically launching a second service at the first node, connecting the second service with the second node, directing requests for service to the second service, and terminating the first service. Other methods and systems are also described.

Claims

1. A method for processing a request of changing a first node having a first service connecting with a second node in a network environment, the method comprising:

dynamically launching a second service at the first node;

connecting the second service with the second node;

determining whether requests for service come from a new session of data after the second service was launched;

transmitting the requests for service to the second service if the requests for service come from the new session of data;

transmitting the requests for service to the first service if the requests for service come from an existing session of data opened before the second service was launched; and

changing the first node by terminating the first service.

2. The method of claim 1, wherein the first service is terminated when a pre-specified condition is satisfied.

3. The method of claim 2, wherein the pre-specified condition comprises an amount of data that needs to be processed.

4. The method of claim 2, wherein the pre-specified condition comprises passage of a period of time.

5. The method of claim 2, further comprising:

detecting whether the request has been aborted before the condition is satisfied; and

dynamically rolling back configuration of the first node to its original configuration.

6. The method of claim 5, wherein rollback operation comprises:

directing all requests for services through the first service; and

terminating data processing at the second service.

7. The method of claim 6, further comprising:

disconnecting the second service from the network; and

terminating the second service.

8. The method of claim 1, wherein connection of between the second service and the second node is established while the first service processing the requests for service.

9. The method of claim 1, wherein the request for changing the first node is received from an input through a user interface.

10. A method for processing a request of changing a topology having a direct connection between a first node and a second node in a network environment, the method comprising:

dynamically launching a new service, the service intended to be added between the first and second nodes;

connecting the new service with the first and the second nodes;

determining whether requests for service come from a new session of data after the new service was launched;

transmitting the requests for service to the new service if the requests for service come from the new session of data;

transmitting the requests for service to the direct connection between the first and second nodes if the requests for service come from an existing session of data opened before the new service was launched; and

changing the topology by terminating the direct connection between the first and second node.

11. The method of claim 10, wherein the direct connection is terminated when a pre-specified condition is satisfied.

12. The method of claim 11, wherein the pre-specified condition comprises an amount of data that needs to be processed.

13. The method of claim 11, wherein the pre-specified condition comprises passage of a period of time.

14. The method of claim 11, further comprising:

detecting whether the request has been aborted before the condition is satisfied; and

dynamically rolling back configuration between the first and the second nodes to its original configuration.

15. The method of claim 14, wherein rollback operation comprises:

directing all requests for services directly from the first node to the second node; and

terminating the new service.

16. The method of claim 10, wherein connections between the new service and the first and the second node are established while the requests for service being processed.

17. A method in a network environment, for processing a request of changing a topology having a first node, a second node, and a third node, the first node being directly connected to the second node and die second node being directly connected to the third node, the method comprising:

dynamically connecting the first and third nodes;

determining whether requests for service come from a new session of data after the first and third nodes were connected;

transmitting the requests for service directly from the first node to the third node, if the requests for service come from the new session of data;

transmitting the requests for service from the first node to the second node and from second node to the third node, if the requests for service come from an existing session of data opened before the first and third nodes were connected; and

changing the topology by terminating the second node.

18. The method of claim 17, wherein the second node is terminated when a pro-specified condition is satisfied.

19. The method of claim 18, wherein the pre-specified condition comprises an amount of data that needs to be processed.

20. The method of claim 18, wherein the pre-specified condition comprises passage of a period of time.

21. The method of claim 18, further comprising:

detecting whether the request has been aborted before the condition is satisfied; and

dynamically rolling back configuration between the first and the third nodes to its original configuration.

22. The method of claim 21, wherein rollback operation comprises:

directing all requests for services from the first node to the second node;

terminating remaining requests for services being processed between the first and the third nodes; and

disconnecting direct connection between the first and the third nodes.

23. The method of claim 17, wherein connection of between the first node and the third node is established while the requests for service being processed through the first, the second, and the third nodes.

24. A system for changing a node having a first service in a network environment, the system comprising:

a second service dynamically launched at the node, the second service operating in parallel with the first service, wherein the first service processes an existing flow of data and the second processes a subsequent new flow of data simultaneously; and

a pre-specified condition when satisfied, the node is changed so that the second service processes all flows of data and the first service is terminated.

25. The system of claim 24, wherein the pre-specified condition comprises an amount of data that needs to be processed.

26. The system of claim 24, wherein the pre-specified condition comprises a period of time.

27. The system of claim 24, further comprising an abortion request when received before the condition is satisfied, configuration of the node is rolled back to its original configuration dynamically.

28. The system of claim 27, wherein the rollback operation comprises:

directing all flows of data to the first service for processing; and

terminating the second service.

29. A system for changing a topology having a direct connection between a first node and a second node in a network environment, the system comprising:

at least one new services dynamically launched, the at least one new services coupling the first and the second nodes, wherein the at least one new services process a subsequent new flow of data, while an existing flow of data being transferred from the first node to the second node directly; and

a pre-specified condition when satisfied, the topology is changed so that the at least one new services process all flows of data and the direct connection between the first and the second nodes is terminated.

30. The system of claim 29, wherein time pre-specified condition comprises an amount of data that needs to be processed.

31. The system of claim 29, wherein the pre-specified condition comprises a period of time.

32. The system of claim 29, further comprising an abortion request when received before the condition is satisfied, configuration of the topology is rolled back to its original configuration dynamically.

33. The system of claim 32, wherein the rollback operation comprises:

directing all flows of data directly from the first node to the second node; and

terminating the at least one new services.

34. A machine-readable medium having executable code to cause a machine to perform a method for processing a request of changing a first node having a first service connecting with a second node in a network environment, the method comprising:

dynamically launching a second service at the first node;

connecting the second service with the second node;

determining whether requests for service come from a new session of data after the second service was launched;

transmitting the requests for service to the first service if the requests for service come from an existing session of data opened before the second service was launched; and

modifying the first node by terminating the first service.

35. The machine-readable medium of claim 34, wherein the method further comprises:

detecting whether the request has been aborted; and

dynamically rolling back configuration of the first node to its original configuration, if the request has been aborted.

36. A machine-readable medium having executable code to cause a machine to perform a method for processing a request of changing a topology having a direct connection between a first node and a second node in a network environment, the method comprising:

dynamically launching a new service, the service intended to be added between the first and second nodes;

connecting the new service with the first and the second nodes;

determining whether requests for service come from a new session of data after connecting the new service with the first and the second nodes;

transmitting the requests for service to the new service if the requests for service come from the new session of data;

transmitting the requests for service to the direct connection between the first and second nodes if the requests for service come from an existing session of data opened before connecting the new service with the first and the;

second nodes; and

modifying the topology by terminating the direct connection between the first and second node.

37. The machine-readable medium of claim 36, wherein the method further comprises:

detecting whether the request has been aborted; and

dynamically rolling back configuration between;

the first and the second nodes to its original configuration, if the request has been aborted.

38. A machine-readable medium having executable code to cause a machine to perform a method for processing a request of changing a topology having a first node, a second node, and a third node, the first node being directly connected to the second node and the second node being directly connected to the third node, the method comprising:

dynamically connecting the first and third nodes;

transmitting requests for service directly from the first node to the third node, if the requests for service come from a new session of data opened after connecting the first and third nodes; and

changing the topology by transmitting the requests for service from the first node to the second node and from second node to the third node, if the requests for service come from an existing session of data opened before connecting the first and third nodes.

39. The machine-readable medium of claim 38, wherein the method further comprises:

detecting whether the request has been aborted; and

dynamically rolling back configuration between the first and the second nodes to its original configuration, if the request has been aborted.