MESSAGE EXCHANGE VIA GENERIC TLV GENERATOR AND PARSER
A system and methods are provided for processing Type-Length-Value (TLV) Messages with TLV Engines in any TLV-based protocol by using configuration files associated with the protocol. One method provides for generating a TLV message by receiving output from a sender at a message engine, loading one or more configuration files associated with a TLV-based protocol onto the message engine, wherein the configuration files describe information about one more message elements, generating a TLV message at the message engine by creating and ordering the message elements into a TLV message according to the configurations files, and transmitting the TLV message over a network from the message engine.
1 . A method of generating a Type-Length-Value message, comprising:
receiving output from a sender at a message engine;
loading one or more configuration files associated with a Type-Length-Value (TLV)-based protocol onto said message engine, wherein said one or more configuration files describes information about one or more message elements;
generating a TLV message at said message engine by creating and ordering said one or more message elements into a TLV message according to said one or more configurations files; and
transmitting said TLV message over a network from said message engine.
2 . The method of claim 1 , wherein said TLV message is transmitted from said message engine to a second message engine linked to a receiver.
3 . The method of claim 1 , wherein one of said one or more configuration files is a type definition file that describes information about a type of one of said one or more message elements.
4 . The method of claim 3 , wherein said information about said type of one of said one or more message elements describes a data type of said one of said one or more message elements.
5 . The method of claim 1 , wherein one of said one or more configuration files is a layout definition file that describes information about a structural layout of said one or more message elements within said TLV message.
6 . The method of claim 5 , wherein said information about said structural layout of said one or more message elements within said TLV message comprises identification of nesting relationships of one or more of said one or more message elements within another one or more of said one or more message elements.
7 . The method of claim 1 , comprising loading one or more alternate configuration files associated with a different protocol other than said protocol onto said message engine, to configure said message engine to generate a new TLV message in said different protocol by using said one or more alternate configuration files.
8 . A method of parsing a Type-Length-Value message, comprising:
receiving a Type-Length-Value (TLV) message comprising a plurality of message elements at a message engine linked to a receiver, wherein said TLV message was generated according to a protocol;
loading a type definition file associated with said protocol onto said message engine, said type definition file describing information about said plurality of message elements;
using said type definition file to parse the message elements of said TLV message into parsed data in another format that is compatible with said receiver; and
transmitting said parsed data to said receiver.
9 . The method of claim 8 , wherein said type definition file describes data types of said plurality of message elements.
10 . The method of claim 8 , comprising loading an alternate type definition file associated with a different protocol other than said protocol onto said message engine, to configure said message engine to parse a new TLV message in said different protocol by using said alternate type definition file.
11 . A message engine comprising:
a Message Generator and Parser configured to load one or more configuration files associated with a protocol that describe information about a plurality of Type-Length Value (TLV) Elements within a TLV Message; and
a Message Data Container configured to process said TLV Message according to said protocol.
12 . The message engine of claim 11 , wherein said one of said one or more configuration files is a type definition file that describes details of one of said plurality of TLV Elements.
13 . The message engine of claim 11 , wherein said one of said one or more configuration files is a layout definition file that describes the structural layout of at least some of said plurality of TLV Elements within said TLV Message in relation to at least one other one of said plurality of TLV Elements.