Chunk-based communication of binary dynamic rest messages

• US 9,462,085 B2
• Filed: 03/21/2014
• Issued: 10/04/2016
• Est. Priority Date: 03/21/2014
• Status: Active Grant

• Current Assignee: PTC Inc.
• Original Assignee: PTC Inc.
• Inventors: Bullotta, Rick, Canosa, John, Mahoney, Mike
• Primary Examiner(s): Gidado, Rasheed
• Application Number:
  US14/222,027
• Publication Number:
  US 20150271109A1
• Time in Patent Office: 928 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 63/029 Firewall traversal, e.g. tunnelling or, creating pinholes
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion

Abstract

A communication engine and a method thereof of chunk-based communication of binary Dynamic REST messages. The communication engine includes a port to receive one or more data streams. The communication engine having a first buffer to store a received first data stream and a received second data stream. The communicate engine includes a second buffer to store portions of a decoded message. The communication engine includes a processor configured to decode the received data stream buffered within the first buffer to produce a given decoded portion. The processor storing the given decoded portion to the second buffer where the processor initiates decoding of the received first data stream buffered within the first buffer prior to a complete receipt of the received second data stream.

Claims

1. A An apparatus comprising:

a communication port configured to receive a plurality of data streams each having a header comprising a field that indicates that the data stream is one of a plurality of data stream that collectively form a single serialized dynamic REST (Representative State Transfer) message, wherein the single serialized dynamic REST message comprises self-describing components that include a plurality of definition portions and a plurality of data portions, wherein each of the plurality of data portions include data values that correspond to each of the plurality of definition portions, and wherein each of the plurality of definition portions comprises a data structure that describes a data element selected from the group consisting of a name, an attribute, and a property of a respective data portion;

a processor coupled to the communication port; and

a memory having instructions stored thereon, wherein the instructions, when executed by the processor, cause the processor to;

establish a first buffer and a second buffer in the memory data stream;

upon receiving a first data stream via the communication port, interrogate a given header of the first data stream; and

in response to the given header having a value, in the multi-part field, that indicates that the data stream is a multiple-part serialized dynamic REST message, decode a payload of the first data stream buffered in the first buffer to produce a first decoded portion and store the first decoded portion in the second buffer, wherein decoding of the payload of the first data stream is initiated prior to a complete receipt of a second data stream, wherein the first data stream and the second data stream collectively include, in whole, or in part, the single serialized dynamic REST message.

2. The apparatus of claim 1, wherein the instructions, when executed by the processor, cause the processor to

interrogate the first data stream at a current multi-part identifier field, a number of multi-part field, and a size field,

wherein a first parameter interrogated at the number of multi-part field and a second parameter interrogated at the size field are used to determine a buffer size for the second buffer.

3. The apparatus of claim 1, wherein the instructions, when executed by the processor, cause the processor to

interrogate the first data stream at a current multi-part identifier field, a number of multi-part field, and a size field,

wherein a second parameter interrogated at the current multi-part identifier field is used to determine a location to store the first decoded portion in the second buffer.

4. The apparatus of claim 1, comprising a decryption engine that decodes the payload of the first data stream to produce the first decoded portion.

5. The apparatus of claim 1, wherein the data structure includes an event object, a service object, a property object, and an attribute object.

6. The apparatus of claim 2, wherein the first parameter associated with the number of multi-part field defines a number of the plurality of data streams that form the single serialized dynamic REST message, wherein the single serialized dynamic REST message comprises a complete message.

7. The apparatus of claim 3, wherein the second parameter associated with the current multi-part identifier field defines a message number identifier that indicate a location of a given decoded data stream within the single serialized dynamic REST message, wherein the single serialized dynamic REST message comprises a complete message.

8. The apparatus of claim 1, wherein the communication port receives the one or more data stream over a web-socket connection.

9. The apparatus of claim 2, wherein the current multi-part identifier field, the number of multi-part field, and the size field are located in the header of the first data stream.

10. The apparatus of claim 2, wherein the current multi-part identifier field, the number of multi-part field, and the size field are located in the payload of the first data stream.

11. A computer-implemented method comprising:

receiving, at a port of a computing device, a plurality of data streams each having a header comprising a field that indicates that the data stream is one of a plurality of data stream that collectively form a single serialized dynamic REST (Representative State Transfer) message, wherein the single serialized dynamic REST message comprises self-describing components that include a plurality of definition portions and a plurality of data portions, wherein each of the plurality of data portions include data values that correspond to each of the plurality of definition portions, and wherein each of the plurality of definition portions comprises a data structure that describes a data element selected from the group consisting of a name, an attribute, and a property of a respective data portion;

establishing, a first buffer and a second buffer in a memory of the computing device;

upon receiving a first data stream via the port, interrogating a given header of the first data stream; and

in response to the given header having a value, in the multi-part field, that indicates that the data stream is a multiple-part serialized dynamic REST message, decoding, using a processor, a payload of the first data stream buffered in the first buffer to produce a first decoded portion and storing the first decoded portion in the second buffer, wherein decoding of the first data stream is initiated prior to a complete receipt of a second data stream, wherein the first data stream and the second data stream collectively include, in whole, or in part, the single serialized dynamic REST message.

12. The computer-implemented method of claim 11, comprising

interrogating the first data stream at a current multi-part identifier field, a number of multi-part field, and a size field, wherein a first parameter interrogated at the number of multi-part field and a second parameter interrogated at the size field are used to determine a buffer size for the second buffer.

13. The computer-implemented method of claim 11, comprising

interrogating the first data stream at a current multi-part identifier field, a number of multi-part field, and a size field, wherein a second parameter interrogated at the current multi-part identifier field is used to determine a location to store the first decoded portion in the second buffer.

14. The computer-implemented method of claim 11, wherein the port receives the plurality of data streams over a web-socket connection.

15. The computer-implemented method of claim 11, wherein decoding of the payload is performed by a decryption engine.

16. The computer-implemented method of claim 11, wherein the data structure includes an event object, a service object, a property object, and an attribute object.

17. The computer-implemented method of claim 12, wherein the first parameter associated with the number of multi-part field defines a number of one or more data streams that form a given complete executable message.

18. The computer-implemented method of claim 17, wherein the second parameter associated with the current multi-part identifier field defines a message number identifier that indicate a location of a given decoded data stream within the single serialized dynamic REST message, wherein the single serialized dynamic REST message comprises a complete message.

19. A non-transitory computer readable medium having instruction stored thereon, wherein the instructions, when executed by a processor of a computing device, cause the processor to:

receive, at a port of the computing device, a plurality of data streams each having a header comprising a field that indicates that the data stream is one of a plurality of data stream that collectively form a single serialized dynamic REST (Representative State Transfer) message, wherein the single serialized dynamic REST message comprises self-describing components that include a plurality of definition portions and a plurality of data portions, wherein each of the plurality of data portions include data values that correspond to each of the plurality of definition portions, and wherein each of the plurality of definition portions comprises a data structure that describes a data element selected from the group consisting of a name, an attribute, and a property of a respective data portion;

establish a first buffer and a second buffer of the computing device;

upon receiving a first data stream via the port, interrogating a given header of the first data stream; and

in response to the given header having a value, in the multi-part field, that indicates that the data stream is a multiple-part serialized dynamic REST message, decode a payload of the first data stream buffered in the first buffer to produce a first decoded portion and storing the first decoded portion in the second buffer, wherein decoding of the first data stream is initiated prior to a complete receipt of a second data stream, wherein the first data stream and the second data stream collectively include, in whole, or in part, the single serialized dynamic REST message.