Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method for normalizing data for a plurality of sensors wirelessly broadcasting the data to a plurality of low power wide area networks (LPWANs), the method comprising: receiving the data (dataE) from the LPWANS according to disparate data formats, the disparate data formats characterized by some of the plurality of sensors formatting a measurement differently from some of the other of the plurality of sensors; normalizing the dataE to data having a common data format (dataC), the common data format characterized by the measurement being formatted the same for each of the plurality of sensors; making the dataC available to an application for processing; receiving the dataE, normalizing the dataE and making the dataC available with an LPWAN abstraction layer (LPWAL), including receiving the dataE without the plurality of sensors having to undergo synchronization or other exchange with the LPWANS prior to the dataE being communicated thereover; normalizing the dataE according to translation information provided to the LPWAL from an application vendor associated with the application; and determining mapping instructions from the translation information, the mapping instructions being sufficient to map a language-dependent format of the dataE to a language-independent format of the dataC, the translation information being determined from a cross-reference with an appID included with the dataE, the appID being a shared secret between the application vendor and the LPWAL to cross-reference the translation information associated therewith, the appID being different than a globally unique appEUI associated with the application.
This invention addresses the challenge of integrating sensor data from multiple low power wide area networks (LPWANs) into a unified format for application processing. Sensors in LPWANs often broadcast data in disparate formats, where different sensors may represent measurements differently, complicating data processing. The method normalizes this heterogeneous data into a common format (dataC) for seamless application use. An LPWAN abstraction layer (LPWAL) handles the normalization, receiving data (dataE) from LPWANs without requiring prior synchronization between sensors and networks. The LPWAL uses translation information provided by the application vendor to convert language-dependent dataE into a language-independent dataC. This translation relies on an appID, a shared secret between the vendor and LPWAL, which cross-references the correct translation rules. Unlike a globally unique appEUI, the appID ensures secure and efficient mapping of sensor data formats. The normalized dataC is then made available to the application for further processing. This approach simplifies data integration across diverse LPWAN sensor networks while maintaining security and compatibility.
2. The method claim 1 further comprising the mapping instructions being sufficient to map a non-JavaScript Object Notation (JSON) format of the dataE to a JSON format of the dataC.
A system and method for processing data involves converting data between different formats, particularly focusing on transforming non-JSON data into JSON format. The method includes receiving data in a first format (dataE) and converting it into a second format (dataC) using mapping instructions. These mapping instructions are designed to handle the conversion of non-JSON data into JSON format, ensuring compatibility and interoperability between systems that rely on JSON for data exchange. The process may involve parsing the original data structure, identifying key-value pairs or hierarchical relationships, and restructuring the data to conform to JSON syntax rules. This conversion is essential for applications where data must be transmitted or processed in JSON format, such as web services, APIs, or data storage systems that require standardized data structures. The method ensures that non-JSON data can be seamlessly integrated into JSON-based workflows without manual intervention, improving efficiency and reducing errors in data processing pipelines. The mapping instructions are configured to handle various non-JSON formats, including but not limited to XML, CSV, or proprietary binary formats, by defining rules for field mappings, data type conversions, and structural transformations. This approach enables flexible and automated data conversion, supporting diverse data sources and destinations in modern computing environments.
3. The method of claim 1 further comprising receiving the dataE with the LPWAN following communication from at least one gateway and at least one network server, the least one gateway and the least one network server being associated with a first LPWAN of the one or more LPWANs, the at least one gateway operating independently of the least one network server to facilitate forwarding the dataE to the at least one network server following receipt from the first endpoint.
This invention relates to low-power wide-area network (LPWAN) communication systems, specifically addressing challenges in data transmission between endpoints and network servers through multiple LPWANs. The technology enables efficient and reliable data forwarding from endpoints to network servers via independent gateways, ensuring seamless communication even when multiple LPWANs are involved. The method involves receiving data from an endpoint device (dataE) via an LPWAN. The data is transmitted through at least one gateway and at least one network server, where the gateway and server are part of a first LPWAN among one or more available LPWANs. The gateway operates independently of the network server, meaning it does not rely on direct coordination with the server to forward the received data. Instead, the gateway autonomously facilitates the transfer of dataE to the network server after receiving it from the endpoint. This independence enhances flexibility and robustness in LPWAN communication, particularly in scenarios where multiple networks are used or when network conditions vary. The system ensures that data is reliably relayed even if the network server is temporarily unavailable or if the gateway must switch between different LPWANs. This approach improves scalability and fault tolerance in LPWAN-based IoT applications.
4. The method of claim 1 further comprising normalizing the dataE by mapping raw data included therein as the measurement to a predefined, text-based syntax of the dataC.
This invention relates to data processing, specifically methods for normalizing raw measurement data into a standardized text-based format. The problem addressed is the inconsistency and lack of interoperability in raw data collected from various sources, which complicates analysis and integration. The solution involves mapping raw data to a predefined, text-based syntax to ensure uniformity and compatibility across different datasets. The method begins by collecting raw data, which may include measurements from sensors, instruments, or other data sources. This raw data is then processed to extract relevant measurement values. The extracted values are mapped to a predefined text-based syntax, which serves as a standardized representation. This syntax may include structured text formats, such as JSON, XML, or custom-defined schemas, ensuring that the data can be easily parsed and interpreted by different systems. The normalization process ensures that data from diverse sources can be integrated seamlessly, enabling more accurate analysis and decision-making. By converting raw data into a standardized format, the method facilitates interoperability between different software applications, databases, and analytical tools. This approach is particularly useful in fields such as industrial monitoring, environmental sensing, and healthcare, where data consistency is critical. The invention improves data usability by eliminating inconsistencies and ensuring that all data adheres to a common syntax, thereby enhancing efficiency and reliability in data-driven applications.
5. The method of claim 4 further comprising making the raw data available to the application such that the application independently receives both of the dataC and the raw data.
A system and method for data processing involves capturing raw data from a sensor or data source and generating processed data (dataC) from the raw data. The processed data is derived through a series of operations, including filtering, normalization, or transformation, to enhance usability or accuracy. The system ensures that the raw data remains accessible alongside the processed data, allowing applications to independently receive and utilize both datasets. This dual-data approach enables applications to perform additional processing, validation, or analysis as needed, improving flexibility and reliability in data-driven applications. The method is particularly useful in fields requiring high-fidelity data, such as scientific research, industrial monitoring, or real-time analytics, where both raw and processed data may be necessary for comprehensive analysis. By maintaining access to the original raw data, the system supports transparency, reproducibility, and customization of data processing workflows.
6. A method for normalizing data for a plurality of endpoints associated with one or more low power wide area networks (LPWANs), the method comprising: receiving a plurality of application global identifiers (appEUI) for a plurality of applications; cross-referencing at least one of a plurality of application identifiers (appIDs) with each of the plurality of appEUIs, each of the plurality of appIDs being different than each of the plurality of appEUIs; cross-referencing translation information with each of the plurality of appIDs, the translation information including instructions sufficient for mapping data originating from the endpoints (dataE) having dissimilar formats to data having a common data format (dataC) utilized by one or more of the plurality of applications associated therewith, including receiving the dataE without the endpoints having to undergo synchronization or other exchange with the LPWANS prior to the dataE being communicated thereover; receiving a first message from a first endpoint of the plurality of endpoints, the first message including dataE and a first appID of the plurality of appIDs; determining first translation information of the translation information to be cross-referenced with the first appID; and transmitting a second message to a first application of the plurality of applications, the first application being associated with the first appEUI, the second message including the first appEUI and dataC derived from normalizing the dataE within the first message according to the first translation information.
This invention relates to normalizing data from multiple endpoints in low power wide area networks (LPWANs) to ensure compatibility with different applications. The problem addressed is the inconsistency in data formats across endpoints, which complicates integration with applications that require standardized data. The solution involves a method that receives application global identifiers (appEUIs) for various applications and cross-references them with application identifiers (appIDs), which differ from appEUIs. Translation information is then linked to each appID, containing instructions for converting endpoint data (dataE) from dissimilar formats into a common format (dataC) used by the associated applications. This process occurs without requiring endpoints to synchronize or communicate with the LPWANs beforehand. When a message containing dataE and an appID is received from an endpoint, the system identifies the corresponding translation information, normalizes the dataE into dataC, and transmits the standardized data along with the appEUI to the appropriate application. This ensures seamless data exchange between endpoints and applications, regardless of their native formats.
7. The method of claim 6 further comprising: receiving a third message from a second endpoint of the plurality of endpoints, the third message including dataE and the first appID; and transmitting a fourth message to the first application, the fourth message including the first appEUI and dataC derived from normalizing the dataE within the second message according to the first translation information.
This invention relates to a system for managing and translating data between multiple endpoints and applications in a networked environment. The problem addressed is the need to efficiently route and normalize data from diverse endpoints to specific applications, ensuring compatibility and proper processing. The system involves a networked device that receives messages from multiple endpoints, each message containing data and an application identifier (appID). The device maintains translation information that defines how to normalize data from each endpoint for specific applications. When a first message is received from a first endpoint, the device identifies the corresponding application based on the appID and retrieves the translation information for that application. The device then normalizes the data from the first message according to the translation information and transmits a second message to the application, including the normalized data and an application-specific identifier (appEUI). Additionally, the system handles subsequent messages from other endpoints. If a third message is received from a second endpoint, the device again uses the appID to identify the target application and retrieves the appropriate translation information. The data in the third message is normalized according to this information, and a fourth message is transmitted to the application, containing the normalized data and the appEUI. This ensures that data from different endpoints is consistently processed by the application in a standardized format. The system thus facilitates seamless communication between heterogeneous endpoints and applications by dynamically applying the correct translation rules.
8. The method of claim 6 further comprising: receiving a plurality of device identifiers (deviceIDs) for the plurality of endpoints; associating subsets of the first translation information with the plurality of deviceIDs; receiving a third message from the first endpoint, the third message including dataE, the first appID and a first deviceID of the plurality of device identifiers, the first deviceID being associated with the first endpoint; and transmitting a fourth message to the first application, the fourth message including the first appEUI and dataC derived from normalizing the dataE within the third message according to a first subset of the subsets of the first translation information.
This invention relates to a system for managing and translating data between endpoints and applications in a networked environment. The problem addressed is the need to efficiently route and normalize data from multiple endpoints to specific applications, ensuring compatibility and proper handling of different data formats. The system involves a method for processing messages between endpoints and applications. A plurality of endpoints, each identified by a unique device identifier (deviceID), communicate with applications using application identifiers (appIDs). The system maintains translation information that maps application identifiers to endpoint identifiers (appEUI) and defines normalization rules for data conversion. Subsets of this translation information are associated with specific deviceIDs to customize data handling for different endpoints. When an endpoint sends a message containing data (dataE), its appID, and its deviceID, the system identifies the corresponding appEUI and normalizes the dataE according to the translation rules linked to the deviceID. The normalized data (dataC) is then transmitted to the application. This ensures that data from diverse endpoints is properly formatted and routed to the correct application, improving interoperability and reducing processing errors. The method supports dynamic association of translation rules with endpoints, allowing flexible and scalable data management in distributed systems.
9. The method claim 8 further comprising: receiving a fifth message from a second endpoint of the plurality of endpoints, the fifth message including dataE and the first appID; determining a second subset of the subsets of the first translation information to be associated with a second deviceID and the first appID, the second deviceID being associated with the second endpoint, the second subset being different from the first subset such that the second subset maps dataE to dataC differently than the first subset; and transmitting a sixth message to the first application, the sixth message including the first appID and dataC derived from normalizing the dataE within the fifth message according to the second subset, the dataC of the second message and the sixth message being identically formatted.
This invention relates to a system for normalizing and translating data between different endpoints in a distributed computing environment. The problem addressed is the inconsistency in data formats and mappings when multiple endpoints interact with a central application, leading to inefficiencies and errors in data processing. The system involves a method for managing data translation between a central application and multiple endpoints. Each endpoint communicates with the application using a unique application identifier (appID) and a device identifier (deviceID). The system maintains translation information that defines how data from different endpoints should be normalized into a consistent format for the application. This translation information is organized into subsets, where each subset corresponds to a specific deviceID and appID combination. When a first endpoint sends a message containing dataA and the appID, the system identifies a first subset of the translation information associated with the first endpoint's deviceID and the appID. This subset maps dataA to dataB, and the system normalizes dataA into dataB according to this mapping. The normalized dataB is then transmitted to the application. Similarly, when the application sends a response message containing dataC and the appID, the system uses the same subset to map dataC back to dataA and transmits it to the first endpoint. For a second endpoint, the system uses a different subset of the translation information associated with the second endpoint's deviceID and the appID. This subset maps dataE to dataC differently than the first subset. When the second endpoint sends a message containing dataE and the appID, the system normalizes dataE into dataC using the second subset and transmits it to the appl
10. The method of claim 9 further comprising: receiving a seventh message from the first endpoint, the seventh message including dataE and a second appID of the plurality of appIDs; determining third translation information of the translation information to be associated with the second appID, the second appID being associated with the second appEUI; and transmitting an eighth message to a second application of the plurality of applications, the second application being associated with the second appEUI, the seventh message including the second appEUI and dataC derived from normalizing the dataE within the seventh message according to the third translation information.
This invention relates to a system for managing and translating data between multiple applications in a networked environment. The problem addressed is the need to efficiently route and normalize data from various endpoints to their respective applications, ensuring compatibility and proper handling of different data formats. The method involves receiving a message from a first endpoint, where the message includes data and an application identifier (appID) from a set of appIDs. The system determines translation information associated with the appID, which is linked to a specific application endpoint identifier (appEUI). The data is then normalized according to the translation information and transmitted to the corresponding application. This ensures that the data is properly formatted and routed to the correct application. Additionally, the method includes receiving a subsequent message from the same endpoint, which contains new data and a second appID. The system identifies the appropriate translation information for the second appID, which is associated with a second appEUI. The data is normalized again according to this new translation information and sent to the second application. This process allows for dynamic handling of multiple applications and endpoints, ensuring seamless data exchange and compatibility. The system efficiently manages data translation and routing, improving interoperability in networked application environments.
11. The method of claim 6 further comprising: transmitting an application ID message to a vendor of the first endpoint, the application ID message indicating the cross-referencing of the first appID with the first appEUI; receiving the first message from the first endpoint after the vendor subsequently instructs the first endpoint to transmit the first message with the first appID and without the first appEUI in order to thwart snooping of the first message, the first message being wirelessly broadcasted from the first endpoint in a connectionless manner.
This invention relates to secure communication in wireless networks, specifically addressing the problem of message snooping in connectionless communication environments. The method involves a system where a first endpoint device transmits messages wirelessly in a connectionless manner, initially using both an application identifier (appID) and an extended unique identifier (appEUI). To enhance security and prevent unauthorized interception, the system cross-references the appID with the appEUI and transmits an application ID message to the vendor of the first endpoint. This message indicates the successful cross-referencing, prompting the vendor to instruct the endpoint to transmit subsequent messages using only the appID and omitting the appEUI. This approach reduces the risk of snooping by minimizing the exposure of the appEUI, which could otherwise be exploited by malicious actors to intercept or manipulate communications. The first message is then received from the endpoint after these changes, ensuring that future transmissions are more secure. The method leverages vendor coordination to dynamically adjust communication protocols, improving overall network security in environments where connectionless wireless broadcasts are used.
12. A low power wide area network abstraction layer (LPWAL) comprising: a low power wide area network (LPWAN) interface interfacing with a plurality of LPWANs, each of the plurality of LPWANs including: i) at least one network server; ii) at least one gateway; iii) a plurality of endpoints, the plurality of endpoints being solely battery-operated sensors for asynchronously broadcasting messages having sensed measurements, the messages being broadcasted to a surrounding area in a non-mesh or a connectionless manner without requiring prior association or synchronization with any of the gateways; and iv) wherein the at least one network server interfaces with the LPWAN interface and the at least one gateway and the plurality of endpoints interface with one or more of the at least one gateway; an application interface interfacing with at least one application connected thereto via the Internet or other communication network; and a message handler for interfacing the messages between the LPWAN interface and the application interface, the message handler normalizing data carried within the messages such that disparate data formats employed therewith are normalized to a common format prior to being interfaced to the at least one application via the application interface, the message handler including a processor for executing a plurality of instructions stored on a non-transitory computer-readable medium associated therewith, the plurality of instructions been sufficient for: i) receiving a plurality of application global identifiers (appEUI) from vendors associated with each of the plurality of applications, the plurality of appEUIs globally and uniquely identifying one of the plurality of applications; ii) cross-referencing at least one of a plurality of application identifiers (appIDs) with each of the plurality of appEUIs, each of the plurality of appIDs being different than each of the plurality of appEUIs; iii) receiving a plurality of translation instructions for the plurality of applications, the plurality of translations instructions being sufficient for normalizing the data carried within the messages according to formatting characteristics of the plurality of endpoints and the LPWAN associated therewith; iv) cross-referencing each of the plurality of translation instructions with at least one of the plurality of appIDs; and v) for each of the messages, normalizing the data formats therein to the common format according to the plurality of translation instructions cross-referenced with a one of the plurality of appIDs included therein.
A low power wide area network abstraction layer (LPWAL) provides a unified interface between multiple low power wide area networks (LPWANs) and applications. The system addresses challenges in managing diverse LPWAN technologies, which typically involve battery-operated sensors broadcasting data asynchronously without prior synchronization or association with gateways. Each LPWAN includes network servers, gateways, and endpoints (sensors) that transmit messages in a connectionless manner. The LPWAL bridges these LPWANs with applications via the Internet or other networks, normalizing data formats to ensure compatibility. The LPWAL includes an LPWAN interface connecting to multiple LPWANs, an application interface for applications, and a message handler that processes and normalizes data. The message handler uses a processor and stored instructions to manage application identifiers (appEUIs and appIDs) and translation rules. Vendors provide appEUIs to uniquely identify applications, which are cross-referenced with appIDs. Translation instructions, tailored to the LPWAN and endpoint formats, are stored and applied to normalize incoming messages into a common format before delivery to applications. This ensures seamless integration of heterogeneous LPWAN data into application systems.
13. The LPWAL of claim 12 wherein the plurality of non-transitory instructions are sufficient to facilitate: collecting accounting information for each of the plurality of LPWANs, the accounting information including a volume of data traffic for each of the LPWANs; and transmitting an accounting report to each operator associated with the plurality of LPWANs, the accounting report including the accounting information.
Low-power wide-area networks (LPWANs) are used for long-range, low-bandwidth communication, often in IoT applications. A challenge in managing multiple LPWANs is tracking and reporting data usage across different operators. This invention addresses this by providing a system that collects and distributes accounting information for LPWANs. The system includes a processor and non-transitory instructions that, when executed, enable the collection of accounting data for each LPWAN in a network. This data includes the volume of data traffic generated by each LPWAN. The system then generates an accounting report containing this traffic volume information and transmits the report to the respective operators managing each LPWAN. This allows operators to monitor usage, bill customers, and optimize network performance based on actual traffic patterns. The solution ensures accurate tracking of data usage across multiple LPWANs, providing transparency and operational efficiency for network operators. By automating the collection and distribution of accounting reports, the system reduces manual effort and improves data accuracy. This is particularly useful in environments where multiple LPWANs coexist, such as smart cities or industrial IoT deployments.
14. The LPWAL of claim 12 wherein at least a plurality of the translation instructions normalize the data carried within the messages received at the LPWAN interface such that the data is translated from a non-JavaScript Object Notation (JSON) format to a JSON format.
This invention relates to a Low-Power Wide-Area Network (LPWAN) gateway system designed to facilitate communication between LPWAN devices and a cloud-based server. The system addresses the challenge of integrating LPWAN devices, which often use proprietary or non-standard data formats, with cloud platforms that typically require standardized data formats like JavaScript Object Notation (JSON) for efficient processing and interoperability. The LPWAN gateway includes a translation module that processes messages received from LPWAN devices. The translation module normalizes the data within these messages, converting non-JSON formats into JSON format. This ensures compatibility with cloud-based systems that rely on JSON for data exchange. The translation process may involve parsing the incoming data, extracting relevant fields, and restructuring the data into a JSON-compatible structure. The gateway also handles protocol conversion, ensuring seamless communication between the LPWAN devices and the cloud server. Additionally, the system may include security features to protect data during transmission, such as encryption and authentication mechanisms. The overall goal is to provide a reliable and efficient bridge between LPWAN devices and cloud-based applications, enabling real-time data exchange and remote management of IoT devices.
15. The LPWAL of claim 12 wherein the plurality of endpoints: operate according to a messaging strategy whereby a radio interface or other wireless communication mechanisms associated therewith to communicate with the gateways is shutdown or turned off during non-data intervals such that the endpoints are unable to receive downstream transmission or otherwise wirelessly communicate during non-data intervals; and the radio interface or other wireless communication mechanisms are woken up during data intervals to consume battery energy for purposes of transmitting data upstream to the gateways.
This invention relates to low-power wide-area networks (LPWAN) for wireless communication, specifically addressing the challenge of energy efficiency in battery-powered endpoints. The system includes a plurality of endpoints and gateways, where the endpoints are configured to minimize power consumption by selectively activating and deactivating their radio interfaces or other wireless communication mechanisms. During non-data intervals, the endpoints shut down or turn off their communication hardware, rendering them unable to receive downstream transmissions or engage in any wireless communication. This reduces power consumption when no data is being transmitted. During data intervals, the endpoints wake up their communication hardware to transmit data upstream to the gateways, consuming battery energy only when necessary for active communication. The messaging strategy ensures that endpoints remain in a low-power state for extended periods, conserving battery life while maintaining the ability to send data when required. This approach is particularly useful in applications where endpoints are battery-powered and need to operate for long durations without frequent recharging or replacement. The system may also include additional features such as synchronization mechanisms to coordinate communication intervals between endpoints and gateways, further optimizing energy efficiency.
16. The LPWAL of claim 15 wherein radio interface or other wireless communication mechanisms are kept temporarily operational during the data intervals following upstream transmission of the data to facilitate receipt of downstream communications from one or more the gateways.
This invention relates to low-power wide-area networks (LPWAN) and addresses the challenge of maintaining efficient communication while minimizing power consumption in battery-operated devices. The system involves a wireless communication device that transmits data upstream to a gateway during designated data intervals. To conserve power, the device typically deactivates its radio interface or other wireless communication mechanisms after transmission. However, this approach risks missing downstream communications from the gateway, such as acknowledgments or control messages. The invention improves upon this by temporarily keeping the radio interface or other wireless communication mechanisms operational during the data intervals following upstream transmission. This allows the device to receive downstream communications from one or more gateways without requiring a separate wake-up period, reducing latency and ensuring reliable two-way communication. The solution balances power efficiency with the need for timely downstream responses, making it suitable for applications like IoT sensors and smart meters where energy conservation is critical. The system may also include mechanisms to adjust the duration of the operational period based on network conditions or device requirements, further optimizing performance.
17. The LPWAL of claim 12 wherein the plurality of endpoints are incapable of encrypting or tunneling the messages such that omittance of the appEUIs in the messages and secrecy of the cross-referencing between the appEUIs and the appIDs acts as security for broadcast of the messages.
This invention relates to a lightweight protocol for wireless ad hoc networks (LPWAL) designed to secure message broadcasting in environments where endpoints lack encryption or tunneling capabilities. The system addresses the challenge of maintaining security in decentralized networks where traditional encryption methods are impractical or unavailable. The LPWAL protocol ensures security through the omission of application endpoint identifiers (appEUIs) in broadcast messages and the secrecy of the cross-referencing mechanism between appEUIs and application identifiers (appIDs). By excluding appEUIs from the messages, the protocol prevents unauthorized entities from identifying or targeting specific endpoints. The cross-referencing between appEUIs and appIDs is kept confidential, further enhancing security by obscuring the relationship between applications and their endpoints. The system relies on this indirect referencing to protect message integrity and confidentiality without requiring endpoints to perform encryption or tunneling. This approach is particularly useful in resource-constrained or low-power wireless networks where computational overhead must be minimized. The protocol ensures that only authorized recipients can interpret the messages, leveraging the secrecy of the cross-referencing mechanism to maintain security in the absence of traditional encryption.
Unknown
February 25, 2020
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.