Coding of routing protocol messages in markup language

• US 20050195820A1
• Filed: 12/16/2004
• Published: 09/08/2005
• Est. Priority Date: 12/19/2003
• Status: Active Grant

• Current Assignee: Solace Corp.
• Original Assignee: Solace Systems, Inc. (United Kingdom)
• Inventors: Barnes, Martin, Bertin, Greg, Pochopsky, David, Burwell, Wayne, Betts, Craig
• Granted Patent: US 7,512,125 B2
• Time in Patent Office: Days
• US Class Current: 370/392
• CPC Class Codes: H04L 45/52 Multiprotocol routers

Abstract

An implicit routing protocol for content-based networks having a plurality of XML routers includes an XML Link State Protocol and an XML Subscription Management Protocol that routes customer data based on XML content. The XML Link State Protocol and the XML Subscription Management Protocol includes several messages that must be exchanged between XML routers in the network. These messages are encoded using XML.

Claims

1. A method of controlling communication networks including a plurality of network elements, comprising:

encoding control plane protocol messages using a markup language; and

transferring said encoded messages between said network elements.

2. The method of claim 1, wherein said markup language is XML.

3. The method of claim 2, wherein said messages include a plurality of nested elements.

4. The method of claim 3, wherein said nested elements include XML tags, attributes reflecting message type and version number, or a combination of XML tags and attributes reflecting message type and version number.

5. The method of claim 3, wherein the outermost message nested element reflects message type.

6. The method of claim 4, wherein said nested message includes additional nested elements representing data fields.

7. The method of claim 6, wherein said additional nested elements are tagged with attributes defining rules associated with that particular field.

8. The method of claim 7 wherein said rules include parsing and backwards compatibility rules.

9. The method of claim 4, wherein a network element receiving an incoming message examines said incoming message to determine whether the message type is a recognized message, and if the incoming message is not recognized type discards the incoming message.

10. The method of claim 9, wherein said network element receiving an incoming message examines said incoming message to determine the version number, and if the incoming message has a version is incompatible with the receiving network element, said receiving network element discards the incoming message.

11. The method of claim 10, wherein said receiving network element generates a log or alarm in the event of a version mismatch.

12. The method of claim 1, wherein said messages form part of a link state protocol.

13. The method of claim 1, wherein said messages form part of a subscription management protocol.

14. A method of routing in content-based networks including a plurality of XML routers, comprising:

assembling routing messages for exchanged between XML routers in the network;

encoding said messages using XML; and

exchanging said coded messages between said routers.

15. The method of claim 14, wherein said messages comprise nested elements reflecting data fields.

16. The method of claim 15, wherein said messages include an XML element indicating protocol message type.

17. The method of claim 16, wherein said XML element indicating protocol message type is the outermost nested element.

18. The method of claim 17, wherein the outermost element includes an attribute indicating the version of a protocol employed in the message.

19. The method of claim 15, wherein each message element is tagged with attributes which define the parsing and backwards compatibility rules for that particular field.

20. A method of routing packets in a content-based network including a plurality of XML routers, comprising:

establishing an XML Link State Protocol and an XML Subscription Management Protocol that routes customer data based on XML content; and

exchanging implicit routing protocol (IRP) messages encoded using XML between said routers using said XML Link State Protocol and XML Subscription Management Protocol.

21. A method as claimed in claim 20, wherein said IRP messages are enclosed within an XML element, and a first level element defines the message type.

22. A method as claimed in claim 21, wherein said first level elements each include an attribute indicating the version of the protocol.

23. A method as claimed in claim 22, wherein remaining elements nested within first level elements represent the fields of a given protocol message.

24. A method as claimed in claim 23, wherein each element is tagged with attributes which define the parsing and backwards compatibility rules for that particular field.

25. A content router for use in a content routed network, said router being configured to exchange control messages containing control information with other content routers in the network, and said router further being configured to encode said control information using a markup language.

26. The content router of claim 25, wherein said markup language is XML.

27. The content router of claim 26, wherein said content router employs an XML link state protocol to manage links within the network and an XML subscription management protocol that routes customer data based on XML content, said content router being configured to employ said control messages as part of said link state protocol and said subscription management protocol.