Discontinuous reception (DRX) enhancements in LTE systems
US-11979768-B2 · May 7, 2024 · US
US2017099332A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2017099332-A1 |
| Application number | US-201515127896-A |
| Country | US |
| Kind code | A1 |
| Filing date | Mar 20, 2015 |
| Priority date | Mar 21, 2014 |
| Publication date | Apr 6, 2017 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system and method of a communication device including a port configured to receive a plurality of binary data streams having a binary header and a binary body. The device includes a memory storing a first message structure description of the binary header and the binary body, and a second message structure description of a metadata construct of the message. The device includes a processor configured to parse a received binary data stream using the first message structure description to determine the binary header and the binary body. The processor parses the binary body using the second message structure description to determine the one or more groups of description values forming the metadata construct. The processor uses a portion of the determined description values of the metadata construct to determine the one or more groups of data values of the message construct.
Opening claim text (preview).
What is claimed is: 1 . A communication device (e.g., a platform server, an edge server, an endpoint device, etc.), comprising: a port configured to receive one or more data streams (e.g., one or more packets) corresponding to a message represented in a binary format, wherein each data stream comprises a binary header and a binary body, the binary body comprising a metadata construct (e.g., a list of field definitions) and a message construct (e.g., a list of row data), collectively forming a self-describing schema for the message in which the metadata construct describes properties of the message construct, a memory storing (i) a first message structure description associated with the binary header and the binary body, and (ii) a second message structure description associated with the metadata construct; and a processor configured to parse a received data stream to produce a received message (e.g., a compressed message represented in a binary and truncated format), wherein the processor parses the received data stream using the first message structure description to determine the binary header and the binary body of the received message, wherein the processor parses the binary body using the second message structure description to determine one or more groups of description values forming the metadata construct, and wherein the processor uses a portion of the determined description values of the metadata construct to determine one or more groups of data values of the message construct. 2 . The communication device of claim 1 , wherein each group of the one or more groups of description values is associated with a given data value of each group of the one or more groups of data values of the message construct. 3 . The communication device of claim 1 or 2 , wherein both the message construct and the metadata construct of the received message are represented in a truncated format such that notation objects (e.g., character strings of attributes in a JSON attribute-value pair and/or names in an XML name-value pair) associated with each data value of the message construct and each description value of the metadata construct are not present in the received message, wherein the notation objects are present in an uncompressed version of the received message. 4 . The communication device of claim 3 , wherein the uncompressed version of the received message conforms to an open standard format selected from the group consisting of JavaScript Object Notation (JSON) and Extensible Markup Language (XML). 5 . The communication device of any one of claims 1 - 4 , wherein the binary header comprises a field associated with a HTTP REST message, wherein the HTTP REST message comprises at least one of a binary symbol representing at least one of a HTTP request method (e.g., GET, PUT, DELETE, POST) and a HTTP status code definition. 6 . The communication device of any one of claims 1 - 5 , wherein the data stream comprises a supplemental binary header, wherein the supplemental binary header comprises one or more fields associated with an identity of a targeted recipient of the received data stream. 7 . The communication device of any one of claims 1 - 6 , wherein each group of the one or more groups of description values forming the metadata construct comprises a binary representation of a type definition for each type of data value of the message construct, wherein the type definition comprises a member selected from the group consisting of a string, a number, a Boolean, a datetime object, a timespan object, an Infotable object, a location object, an XML object, a JSON object, a query object, an image, a hyperlink, an imagelink object, a password object, an html object, a text, a tag object, a schedule object, a variant object, a global unique identifier (GUID) object, a binary large object (BLOB), and an integer. 8 . The communication device of any one of claims 1 - 7 , wherein each group of the one or more groups of data values of the message construct and each group of the one or more groups of description values of the metadata construct comprises one or more binary markers, wherein the one or more binary markers indicate at least one of a beginning and an end of each of the respective one or more groups. 9 . The communication device of any one of claims 1 - 8 , wherein each of the one or more groups of description values forming the metadata construct comprises: a data-value name descriptor, a data-value description-descriptor, and a data value type-descriptor, wherein the descriptors are defined by a model-based schema. 10 . The communication device of any one of claims 1 - 9 , wherein the metadata construct precedes the message construct in the binary body. 11 . The communication device of any one of claims 1 - 10 , wherein portions of the metadata construct and the message construct corresponding to a set of string characters are represented, in the received message, as a binary symbol based on a universal standard code native to the communication device (e.g., Unicode-8). 12 . The communication device of any one of claims 1 - 11 , wherein the port is configured to receive the one or more data streams via a WebSocket connection. 13 . A computer-implemented method for communicating a compressed and binarized dynamic REST API message formatted according to a model-based schema and self-describing schema, the method comprising: storing, at a memory of a computing device, a first message structure description and a second message structure description for a data stream, wherein the first message structure description defines a shape of a binary header and a binary body for a message represented in a binary format, wherein the binary body comprises a metadata construct (e.g., a list of field definitions) and a message construct (e.g., a list of row data), collectively forming a self-describing schema for the message in which the metadata construct describes properties of the message construct, wherein the second message structure description defines a structure for the metadata construct; receiving, at a port of the computing device, one or more data streams corresponding to a compressed and binarized dynamic REST API message formatted according to a model-based schema and self-describing schema; and parsing, by a processor of the computing device, the received data stream to produce a received message, wherein the parsing of the received data stream comprises: parsing the received data stream using the first message structure description to determine the binary header and the binary body of the received message, parsing the binary body using the second message structure description to determine one or more groups of description values forming the metadata construct of the received message, and determining one or more groups of data values of the message construct using a portion of the determined description values of the metadata construct. 14 . The method of claim 13 , wherein each group of the one or more groups of description values is associated with a given data value of each group of the one or more groups of data values of the message construct. 15 . The method of claim 13 or 14 , wherein both the message construct and the metadata construct of the received message are represented in a truncated format such that notation objects (e.g., character strings of attributes in a JSON attribute-value pair and/or names in an XML name-value pair) associated with each data value of the message construct and each description value of the metadata construct are not present in the rec
Physics · mapped topic
Network streaming of media packets · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Multiprotocol handlers, e.g. single devices capable of handling multiple protocols · CPC title
based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.