Access control method and apparatus based on service level
US-2018167982-A1 · Jun 14, 2018 · US
US11690010B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11690010-B2 |
| Application number | US-202016799157-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 24, 2020 |
| Priority date | Dec 15, 2016 |
| Publication date | Jun 27, 2023 |
| Grant date | Jun 27, 2023 |
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.
The normalization of data originating from endpoints within low power wide area networks (LPWANs) is contemplated. The normalization may be beneficial to facilitate normalizing data when collected and/or communicated according to disparate protocols, languages, formats, syntaxes, structures, etc. of the endpoints and/or the LPWANs so as to enable commonization of the data prior to being interfaced with applications or other entities intending to make use thereof.
Opening claim text (preview).
What is claimed is: 1. 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 devices, 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; a message handler interfacing messages between the LPWAN interface and the application interface, the message handler normalizing data carried within messages received at the LPWAN interface 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; a processor and non-transitory computer-readable medium having a plurality of non-transitory instructions executable with the processor, the plurality of non-transitory instructions being sufficient to facilitate: receiving a plurality of translation instructions from a plurality of applications, the plurality of translation instructions being sufficient for normalizing the data carried within the messages received at the LPWAN interface according to formatting characteristics of the plurality of endpoints and the LPWAN associated therewith, controlling the message handler on a message-by-message basis to lookup one or more of the plurality of translation instructions for each message received at the LPWAN interface, and based thereon, normalize the data included therewith prior to the data being interfaced to the at least one application, 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. 2. The LPWAL of claim 1 , wherein the plurality of non-transitory instructions are sufficient to facilitate an endpoint registration process for each of the plurality of endpoints, the endpoint registration process including: 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; receiving a plurality of device identifiers (deviceIDs) for the plurality of endpoints, the plurality of device identifiers globally and uniquely identifying one of the plurality of endpoints; generating a plurality of application identifiers (appIDs) for the plurality of applications as a function of the appEUIs, each of the appIDs being different than the appEUI; and generating a plurality of application keys (appKeys) for the plurality of appIDs, each of the appKeys uniquely encrypting messaging for the application associated with each of the plurality of appIDs. 3. The LPWAL of claim 1 , 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. 4. The LPWAL of claim 1 , 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. 5. The LPWAL of claim 4 , wherein the 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. 6. A method for normalizing data from a wireless low power wide area network (LPWAN), the method comprising: receiving, at an application interface of an abstraction layer, a plurality of translation instructions from a plurality of applications, the plurality of translation instructions being sufficient for normalizing data carried within messages received at a LPWAN interface of the abstraction layer according to formatting characteristics of a plurality of endpoints and the LPWAN; using a controller of the abstraction layer, controlling a message handler of the abstraction layer on a message-by-message basis to lookup one or more of the plurality of translation instructions for each message received at the LPWAN interface of the abstraction layer, and based thereon, normalize data included therewith prior to the data being interfaced to the plurality of applications; collecting accounting information for the LPWAN, the accounting information including a volume of data traffic for the LPWAN; and transmitting an accounting report to an operator associated with the LPWAN, the accounting report including the accounting information.
using a pre-established activity schedule, e.g. traffic indication frame · CPC title
Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561) · CPC title
in wireless communication networks · CPC title
Protocols for interworking; Protocol conversion · CPC title
involving control of end-device applications over a network · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.