Extensible resource messaging between user applications and network elements in a communication network

• US 20060075042A1
• Filed: 09/30/2004
• Published: 04/06/2006
• Est. Priority Date: 09/30/2004
• Status: Abandoned Application

• Current Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: Lavian, Tal, Travostino, Franco, Wang, Phil Yonghui
• Application Number:
  US10/955,163
• Publication Number:
  US 20060075042A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Extensible resource messaging in a communication network is provided through creation of a flexible, extensible, and secure messaging environment. A client-server architecture may be implemented in which user applications employ messaging clients to send resource requests for network information, allocation and other operations and receive resource responses, and in which network elements, through resource agents, may use messaging servers to accept resource requests and return resource responses. Resource agents in different network domains may interact through the messaging environment and work together to fulfill resource requests. An XML-based messaging mechanism may be built with a defined message format that can provide flexible message contexts. Network resource semantics may be specified using XML schemas so that network resources are expressed as resource-specific XML elements and network updates can be implemented by updating the XML resource schemas. Secure enhancements may be realized by secure transport, message verification and other means.

Claims

1. A method of messaging between an application and network elements in a communication network, the method comprising the steps of:

instantiating a messaging client associated with the application;

generating by the messaging client an XML document using an XML schema containing tags indicative of resources required by the application; and

transmitting the XML document over a messaging channel to a messaging stub associated with the communication network.

2. The method of claim 1, wherein the messaging stub is associated with a resource agent configured to interface network elements on the communication network.

3. The method of claim 1, wherein the resources required by the application comprise bandwidth on the communication network.

4. The method of claim 1, wherein the resources required by the application comprise VPN resources on the communication network.

5. The method of claim 1, wherein. the resources required by the application comprise information relating to the available network resources on the communication network.

6. The method of claim 1, wherein the messaging channel is a secure messaging channel.

7. The method of claim 6, wherein the secure messaging channel is provided using at least one of authentication and digital signatures.

8. The method of claim 1, wherein the XML document defies network operations.

9. The method of claim 8, wherein the operations comprise at least one of discovery, status updates, information, and allocations.

10. The method of claim 1, wherein the XML schema allows network resources to be expressed as resource specific XML elements.

11. The method of claim 1, wherein the transmitted XML document is a request message, the method further comprising the step of receiving a response message related to the request message.

12. The method of claim 11, wherein the response message and the request message share a common format.

13. The method of claim 1, further comprising the step of instantiating a second messaging client associated with the messaging stub to enable the messaging stub to establish a second messaging channel to obtain at least a portion of the resources required by the application.

14. The method of claim 13, wherein the messaging stub is associated with a first network domain, and wherein tile portion of the resources are associated with a second network domain.

15. An XML schema configured to enable network resources to be requested on a communications network, the XML schema comprising:

a header field configured to enable a request created using the schema to include identifying information; and

an allocation field configured to enable the request created using the schema to include a request for allocation of network resources.

16. The XML schema of claim 15, wherein the allocation field allows network resources to be expressed as resource specific XML elements.

17. The XML schema of claim 15, wherein the resources are virtual private network (VPN) resources.

18. The XML schema of claim 15, wherein the header field includes an XML tag configured to enable identification of the XML schema used to create the request, and a request ID tag configured to enable identifying information to be input into the request.

19. The XML schema of claim 15, wherein the allocation field contains tags configured to enable the request to specify resources to be allocated, reallocated, and released.

20. The XML schema of claim 19, wherein the resources may be specified using at least one of resource ID, resource type, resource name, and wherein the request may include resource parameters comprising at least one of a bandwidth profile, a traffic route profile, a start time and an end time.

21. The XML schema of claim 15, wherein the XLM schema further comprises an information field configured to enable the request created using the schema to include a request for information about network resources.

22. The XML schema of claim 21, wherein the information field includes at least one of a discovery tag that may be used to discover network resources, a refresh tag that may be used to update a list of network resources, and a query tag that may be used to inquire as to particular identified network resources.

23. One or more processor readable storage devices having processor readable code embodied thereon, said processor readable code being configured to program one or more processors to create a response message using an XML schema configured to enable network resource semantics to be expressed as resource specific XML elements,

24. The one or more processor readable storage devices of claim 23, wherein the XML schema includes a header field configured to enable the response message created using the schema to include identifying information, and an allocation field configured to enable the response message created using the schema to include information associated with an allocation of network resources.

25. The one or more processor readable storage devices of claim 24, wherein the header field includes an XML tag configured to enable identification of the XML schema used to create the response, and an ID tag configured to enable the request to include identifying information about an associated request

26. The one or more processor readable storage devices of claim 24, wherein the information associated with the allocation of network resources comprises at least one of resource ID, resource type, and resource name, and wherein the response may further include resource parameters comprising at least one of a bandwidth profile, a traffic route profile, a start time and an end time,

27. The one or more processor readable storage devices of claim 24, wherein the XLM schema includes an information field configured to enable the response to include information about network resources.