SYSTEM AND METHOD OF USING DYNAMIC REST MESSAGES WITH WEB-SOCKETS

• US 20150271271A1
• Filed: 03/21/2014
• Published: 09/24/2015
• Est. Priority Date: 03/21/2014
• Status: Abandoned Application

• Current Assignee: PTC Inc.
• Original Assignee: PTC Inc.
• Inventors: Bullotta, Rick, Canosa, John, DeRemer, Bob, Mahoney, Mike
• Application Number:
  US14/222,083
• Publication Number:
  US 20150271271A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70

Abstract

A system and method thereof of a communication device that uses dynamic REST messages with Web sockets. The device includes a port configured to transmit and receive a data stream via a persistent stateless connection. The device includes a memory for storing a dynamic REST API model. The device includes a processor configured to connect to a second communication device over the persistent stateless connection. The processor formats a request message with the stored dynamic REST API model to produce a self-describing request message. The processor causes the self-describing request message to be transmitted over the port.

Claims

1. A communication device, comprising:

a port configured to transmit and receive a data stream via a persistent stateless connection;

a memory storing a dynamic REST API model; and

a processor configured to connect to a second communication device over the persistent stateless connection, the processor formatting a request message with the stored dynamic REST API model to produce a self-describing request message, the processor causing the self-describing request message to be transmitted over the port.

2. The communication device of claim 1, wherein the persistent stateless connection is over a web-socket connection.

3. The communication device of claim 1, wherein the port is a HTTP or HTTPS port.

4. The communication device of claim 1, wherein the port has a port value of 80 or 443.

5. The communication device of claim 1, wherein the dynamic REST API model includes a data model comprising a data object, an event object, a service object, a property object, and an attribute object.

6. The communication device of claim 1, wherein the self-describing request message is presented in at least one of a JavaScript Object Notation (JSON) object and an Extensible Markup Language (XML) object.

7. The communication device of claim 1, wherein the self-describing request message is in a binary format.

8. The communication device of claim 1, wherein the self-describing request message is encrypted.

9. A computer-implemented method comprising:

storing, at a memory of a device, a binary dynamic REST API model;

formatting, via a processor at the device, a request message using the binary dynamic REST API model to produce a self-describing request message; and

transmitting, via a port of the device, the request message over a persistent state connection.

10. The computer-implemented method of claim 9, wherein the persistent stateless connection is over a Web socket connection.

11. The computer-implemented method of claim 9, wherein the port is a HTTP or HTTPS port.

12. The computer-implemented method of claim 9, wherein the port has a port value of 80 or 443.

13. The computer-implemented method of claim 9, wherein the binary dynamic REST API model includes a data model comprising a data object, an event object, a service object, a property object, and an attribute object.

14. The communication device of claim 9, wherein the self-describing request message is encrypted.

15. A non-transitory computer readable medium having instruction stored thereon, wherein the instructions, when executed by a processor at a platform server, cause the processor to:

store a binary dynamic REST API model;

format a request message using the binary dynamic REST API model to produce a self-describing request message; and

transmit the request message over a persistent state connection.

16. The computer readable medium of claim 15, wherein the persistent stateless connection is over a Web socket connection.

17. The computer readable medium of claim 15, wherein the port is a HTTP or HTTPS port.

18. The computer readable medium of claim 15, wherein the port has a port value of 80 or 443.

19. The computer readable medium of claim 15, wherein the binary dynamic REST API model includes a data model comprising a data object, an event object, a service object, a property object, and an attribute object.

20. The computer readable medium of claim 15, wherein the self-describing request message is encrypted.