Communication protocols

• US 8,819,170 B2
• Filed: 07/14/2011
• Issued: 08/26/2014
• Est. Priority Date: 07/14/2011
• Status: Active Grant

• Current Assignee: Schneider Electric IT Corporation (Schneider Electric SE)
• Original Assignee: Schneider Electric IT Corporation (Schneider Electric SE)
• Inventors: Cohen, Daniel C., Spitaels, James S., Melanson, Mark R.
• Primary Examiner(s): Whipple, Brian P
• Application Number:
  US13/182,723
• Publication Number:
  US 20130018979A1
• Time in Patent Office: 1,139 Days
• Field of Search: None
• US Class Current: 709/217
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 69/12 Protocol engines
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols

Abstract

A system for exchanging information is provided. The system includes a memory, a first communication link, and at least one processor implementing a first protocol. The at least one processor is coupled to the memory and the first communication link. The at least one processor is configured to receive, via the first communication link, a first request message including a first globally unique identifier (GUID); start, responsive to receipt of the first request message, a communication session over the first communication link; provide a first response message including the first GUID; receive, via the first communication link, a second request message including data and a second GUID; write the data to a location indicated by the second GUID; read information stored at the indicated location; and provide a second response message including the second GUID and the information.

Claims

1. A system for exchanging information comprising:

a memory;

a first communication link;

at least one processor implementing a first protocol, the at least one processor being coupled to the memory and the first communication link and being configured to;

receive, via the first communication link, a first request message including a first globally unique identifier (GUID);

start, responsive to receipt of the first request message, a communication session over the first communication link;

provide a first response message including the first GUID;

receive, via the first communication link, a second request message including a start of frame field storing a value that indicates a type of the second request message, a framelength field storing a value that indicates a length of the second request message, a data field storing data, a datalength field storing a value that indicates a length of the data field, and a GUID field storing a value of a second GUID that identifies a second usage;

write the data to a location indicated by the second GUID;

read information stored at the indicated location; and

provide a second response message including the second GUID and the information.

2. The system according to claim 1, wherein the first request message includes:

a start of frame field storing a value that indicates a type of the first request message;

a framelength field storing a value that indicates a length of the first request message;

a datalength field storing a value that indicates a length of a data field; and

a GUID field storing a value that identifies a first usage that when executed by the at least one processor will start a communication session.

3. The system according to claim 1, wherein the data includes an array index and other data and the second request message includes:

a start of frame field storing a value that indicates a type of the second request message;

a framelength field storing a value that indicates a length of the second request message;

a datalength field storing a value that indicates a length of a data field;

a GUID field storing a value that identifies a second usage;

an index field storing the array index; and

the data field storing the other data.

4. The system according to claim 1, wherein the at least one processor is further configured to:

receive, via the first communication link, a third request message including a third GUID and a fourth GUID;

determine whether the first protocol supports a fourth usage identified by the fourth GUID; and

provide a third response message including the third GUID, the fourth GUID, information describing the fourth usage and a fifth GUID that identifies another usage supported by the first protocol.

5. The system according to claim 4, wherein the third request message includes:

a start of frame field storing a value that indicates a type of the third request message;

a framelength field storing a value that indicates a length of the third request message;

a DiscoveryGUID field storing a value that identifies the third usage; and

a RequestedGUID field storing a value that identifies the fourth usage.

6. The system according to claim 1, further comprising:

a memory map disposed within the memory, the memory map storing operational and configuration information;

a second communication link coupled to the at least one processor, wherein the at least one processor further implements a second protocol different from the first protocol and is further configured to;

receive a message, via the second communication link, including an update to a location of the memory map;

store the update at the location; and

provide a third response message including the update and a third GUID that identifies a usage that utilizes data stored at the location.

7. The system according to claim 6, wherein the first communication link includes a universal serial bus (USB) link and the second communication link includes a serial link.

8. The system according to claim 6, wherein the first protocol is a request-response protocol and the second protocol is a streaming protocol.

9. A system for exchanging information comprising:

a memory;

a first communication link;

at least one first processor coupled to the memory and the first communication link and configured to;

generate a first request message including a first globally unique identifier (GUID) that identifies a first usage that when executed by at least one second processor will start a communication session;

transmit the first request message on the first communication link;

receive a first response message including the first GUID;

generate a second request message including a start of frame field storing a value that indicates a type of the second request message, a framelength field storing a value that indicates a length of the second request message, a data field storing data, a datalength field storing a value that indicates a length of the data field, and a GUID field storing a value of a second GUID that identifies a second usage supported by a protocol implemented by the at least one second processor;

transmit the second request message on the first communication link; and

receive a second response message including the second GUID and information having the same value as the data.

10. The system according to claim 9, wherein the first request message includes:

a start of frame field storing a value that indicates a type of the first request message;

a framelength field storing a value that indicates a length of the first request message;

a datalength field storing a value that indicates a length of a data field; and

a GUID field storing a value that identifies the first usage.

11. The system according to claim 9, wherein the data includes an array index and other data and the second request message includes:

a start of frame field storing a value that indicates a type of the second request message;

a framelength field storing a value that indicates a length of the second request message;

a datalength field storing a value that indicates a length of a data field;

a GUID field storing a value that identifies the second usage;

an index field storing the array index; and

the data field storing the other data.

12. A method for exchanging information using a first computer, the method comprising:

generating, by the first computer, a first request message including a first globally unique identifier (GUID) that identifies a first usage that when executed by a second computer will start a communication session on a link shared by the first computer and the second computer;

transmitting the first request message on the link;

receiving a first response message including the first GUID;

generating a second request message including data and a second GUID that identifies a second usage supported by the second computer, wherein generating the second request message includes storing a value that indicates a type of the second request message within a start of frame field, storing a value that indicates a length of the second request message within a framelength field, storing a value that indicates a length of a data field within a datalength field, storing a value of the second GUI within a GUID field, and storing the data within the data field;

transmitting the second request message on the link; and

receiving a second response message including the second GUID and information having the same value as the data.

13. The method according to claim 12, wherein generating the first request message includes:

storing a value that indicates a type of the first request message within a start of frame field;

storing a value that indicates a length of the first request message within a framelength field;

storing a value that indicates a length of a data field within a datalength field; and

storing a value that identifies the first usage within a GUID field.

14. The method according to claim 12, wherein the data includes an array index and other data and generating the second request message includes:

storing a value that indicates a type of the second request message within a start of frame field;

storing a value that indicates a length of the second request message within a framelength field;

storing a value that indicates a length of a data field within a datalength field;

storing a value that identifies the second usage within a GUID field;

storing the array index within a index field; and

storing the other data within a data field.

15. The method according to claim 12, further comprising:

generating a third request message including a third GUID that identifies a third usage that when executed by the second computer will determine whether the second computer supports a fourth usage identified by a fourth GUID;

transmitting the third request message on the link; and

receiving a third response message including the third GUID, the fourth GUID, information describing the fourth usage and a fifth GUID that identifies another usage supported by the second computer.

16. The method according to claim 15, wherein generating the third request message includes:

storing a value that indicates a type of the third request message within a start of frame field;

storing a value that indicates a length of the third request message within a framelength field;

storing a value that identifies the third usage within a DiscoveryGUID field; and

storing a value that identifies the fourth usage within a RequestedGUID field.

17. The method according to claim 12, further comprising

receiving, via the link, the first request message;

starting, responsive to receipt of the first request message, the communication session;

providing, responsive to receipt of the first request message, the first response message;

receiving, via the link, the second request message;

writing, responsive to receipt of the second request message including the data, the data to a location indicated by the second GUID;

reading, responsive to receipt of the second message, information stored at the location;

and providing, responsive to receipt of the second request message, the second response message.