Abstract: Systems and methods for utilizing unused space in expensive message based communication to embed messages from a sender device to a receiver device to maximize payload usage over a potentially fee-based messaging service. One or more machine-to-machine messages may be embedded in unutilized transport space when other communications, that may potentially be delivered over a fee-based network, are initiated at a device. The machine-to-machine message and other communications may be extracted from a combined message package at a receiving device and processed as if they were independently transported. Machine-to-machine messages may be segmented and embedded across multiple unrelated communication packages and later reassembled.

Abstract: Disclosed in some examples is a method for communications between a client and a server using a stateless messaging protocol by transmitting from a client to a server a first message using the stateless messaging protocol; receiving from the server a response message, the response message including an indication of the presence of a second message at the server intended for the client, the indication including message retrieval information; sending a third message from the client to the server including the message retrieval information; and receiving a fourth message from the server, the fourth message including the contents of the second message.

Abstract: A method comprising compressing a first XML document into a binary stream, converting the binary stream into a compressed valid XML document, and associating at least one XML tag with the compressed valid XML document in order to identify the document as a compressed XML document.

Abstract: A networked firmware management system is operable to manage firmware in one or more target devices by receiving one or more firmware target specifications from one or more target devices, the firmware target specifications each identifying a firmware target in the target device. The server stores the one or more received firmware target specification, associated with the one or more firmware targets in the target device. When the server receives a firmware update, the server matches a firmware attribute of the received firmware update against the one or more firmware target specifications stored in the server, and sends the received firmware update to any firmware targets in the target device having a firmware target specification that matches the received firmware update attribute.

Abstract: A method comprising compressing a first XML document into a binary stream, converting the binary stream into a compressed valid XML document, and associating at least one XML tag with the compressed valid XML document in order to identify the document as a compressed XML document.

Abstract: A wireless mesh network server is operable to receive a message to one or more mesh network nodes from a client external to the mesh network, the message comprising an alias identifying the one or more mesh network nodes. The server is further operable to identify the one or more receiving mesh network nodes by the received message alias via an alias table, and forward the received message to the one or more mesh network nodes identified by the alias.

Abstract: Systems and methods for the remote data exchange and device management with efficient file replication over heterogeneous communication transports. A user or application may provide a server with a communication bundle that may include a command and a data file. A transfer of the bundle from the server to one or more devices coupled to the server by a network over a first protocol may be initiated. Before the completion of the transfer, if a more cost effective connection becomes available the transfer of the bundle from the server to one or more devices may be completed via the more cost effective connection. The bundle may be transmitted in multiple segments. The individual segments may be transferred in any order and over various network protocols, and reassembled at the receiving device.

Abstract: Systems and methods for automatically provisioning devices that do not include or cannot provide a unique hardware identifier over a machine-to-machine network. A device or application may provide a server with a non-unique provisioning identifier during restricted communication between the server and the device. In response to receiving a provisioning identifier from a device, a server may generate a globally unique device identifier associated with the provisioning identifier for the individual device, and transmit the unique identifier to the device. The device may retain the unique identifier for future transactions. A request may be provided to a user, at the device, the server or any other interface, requesting that a newly identified device be authenticated. Upon authentication the device may communicate with the server with additional interactions that were not provided after provisioning and before authentication.

Abstract: Systems and methods for utilizing unused space in expensive message based communication to embed messages from a sender device to a receiver device to maximize payload usage over a potentially fee-based messaging service. One or more machine-to-machine messages may be embedded in unutilized transport space when other communications, that may potentially be delivered over a fee-based network, are initiated at a device. The machine-to-machine message and other communications may be extracted from a combined message package at a receiving device and processed as if they were independently transported. Machine-to-machine messages may be segmented and embedded across multiple unrelated communication packages and later reassembled.

Abstract: Disclosed in some examples is a method for communications between a client and a server using a stateless messaging protocol by transmitting from a client to a server a first message using the stateless messaging protocol; receiving from the server a response message, the response message including an indication of the presence of a second message at the server intended for the client, the indication including message retrieval information; sending a third message from the client to the server including the message retrieval information; and receiving a fourth message from the server, the fourth message including the contents of the second message.

Abstract: Systems and methods for automatically provisioning devices that do not include or cannot provide a unique hardware identifier over a machine-to-machine network. A device or application may provide a server with a non-unique provisioning identifier during restricted communication between the server and the device. In response to receiving a provisioning identifier from a device, a server may generate a globally unique device identifier associated with the provisioning identifier for the individual device, and transmit the unique identifier to the device. The device may retain the unique identifier for future transactions. A request may be provided to a user, at the device, the server or any other interface, requesting that a newly identified device be authenticated. Upon authentication the device may communicate with the server with additional interactions that were not provided after provisioning and before authentication.

Abstract: An embedded processor system includes an integrated development environment and an embedded processor operating system. The embedded processor operating system is operable to run on the embedded processor system, and a command queue is operable to receive commands from a debugging module external to the embedded processor system. A command queue processing module is operable to change settings in the embedded processor system in response to commands in the command queue.

Abstract: Apparatus, methods, and systems are disclosed to manage memory in an embedded system. The system registers video applications and video sources with a memory manager. The memory manager in turn provides memory to the video applications and video sources. The system has an input to receive an output from at least one video source. The memory manager receives a frame from the video source and transfers the frame to memory. Once the frame is in memory the video application may work with the frame. All of these operations are conducted with the memory manager actively managing and allocating the memory resources.

Abstract: A markup language file comprises software build options usable to determine at least one software build configuration setting. One or more software build options are specified in a markup language file to specify one or more software build configuration settings for use in compilation of software. The markup language is an XML file, is editable in an Integrated Development Environment such as via a Graphical User Interface, and includes settings specific to an embedded processor system configuration.

Abstract: A networked firmware management system is operable to manage firmware in one or more target devices by receiving a virtual bundled firmware update package comprising two or more individual firmware update files. The system identifies one or more networked target devices having a virtual firmware target matching the virtual bundled firmware update package, and sends the virtual bundled firmware update package to the virtual firmware target on the one or more networked devices.

Abstract: A networked firmware management system is operable to manage firmware in one or more target devices by receiving one or more firmware target specifications from one or more target devices, the firmware target specifications each identifying a firmware target in the target device. The server stores the one or more received firmware target specification, associated with the one or more firmware targets in the target device. When the server receives a firmware update, the server matches a firmware attribute of the received firmware update against the one or more firmware target specifications stored in the server, and sends the received firmware update to any firmware targets in the target device having a firmware target specification that matches the received firmware update attribute.

Abstract: A wireless mesh network server is operable to receive a message to one or more mesh network nodes from a client external to the mesh network, the message comprising an alias identifying the one or more mesh network nodes. The server is further operable to identify the one or more receiving mesh network nodes by the received message alias via an alias table, and forward the received message to the one or more mesh network nodes identified by the alias.

Abstract: A system comprising a communication (COM) port server that, together with a COM port client, establishes COM port redirection over a network and communicates data with a serial port, at least one embedded application which is configured to communicate data via a serial port, and at least one virtual serial port application communicatively coupled to the embedded application and the COM port server. The virtual serial port application translates data communicated between the COM port server and the embedded application as if the COM port server and the embedded application were connected by a serial communication link.

Abstract: A communications device comprising an embedded application-specific device driver for an application-specific display and an embedded remote access application that execute on a processor. The embedded application-specific device driver is configured to communicate data with a communication (COM) port via a serial port and to provide a video signal to the application-specific display. The embedded remote access application is configured to remotely access the application-specific display and to communicate display data via a network.

Abstract: Apparatus, methods, and systems are disclosed to manage memory in an embedded system. The system registers video applications and video sources with a memory manager. The memory manager in turn provides memory to the video applications and video sources. The system has an input to receive an output from at least one video source. The memory manager receives a frame from the video source and transfers the frame to memory. Once the frame is in memory the video application may work with the frame. All of these operations are conducted with the memory manager actively managing and allocating the memory resources.