Combined registration and telemetry reporting

By multiplexing telemetry data and registration messages in IoT devices, provisioning and reporting using a single SDK and API, and managing devices based on geolocation, solving the complexity and authorization issues of low-resource devices, improving system efficiency and security.

CN113574844BActive Publication Date: 2024-11-01MICROSOFT TECHNOLOGY LICENSING LLC
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202080021196.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-03-19
Filing Date
2020-03-12
Publication Date
2024-11-01
Estimated Expiration
2040-03-12

AI Technical Summary

Technical Problem

Low-power and/or low-memory IoT devices face complexity and high resource consumption when communicating between multiple SDKs and APIs, especially when repeated provisioning processes are required during the restart cycle and cannot effectively manage the geographic of telemetry devices Location and authorization.

Method used

Reauthorization of devices is achieved by multiplexing telemetry data with registration messages, using a single SDK and API for stateless device provisioning and data reporting, reducing the memory and computing burden of devices, and limiting device usage based on geographic location.

Benefits of technology

Improves the efficiency and bandwidth usage of the telemetry reporting system, reduces the resource requirements of the device, ensures simple connection and geographic location management of the device upon restart, and prevents unauthorized devices from being used.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113574844B_ABST
    Figure CN113574844B_ABST
Patent Text Reader

Abstract

Examples are disclosed involving registering a telemetry device with a telemetry system using a multiplexed transmission and reporting telemetry data on behalf of the telemetry device to the telemetry system. One disclosed example provides a method that includes receiving a multiplexed transmission including a registration message and telemetry data from a telemetry device, demultiplexing the multiplexed transmission to obtain the registration message and the telemetry data, registering the telemetry device with the telemetry system based on the registration message, sending the telemetry data to the telemetry system, and sending a registration response to the telemetry device, the registration response confirming registration of the telemetry device with the telemetry system.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art

[0001] Internet of Things (IoT) devices such as various sensors can be configured to communicate telemetry data to an online service such as a cloud-hosted IoT hub. Summary of the invention

[0002] This summary is provided to introduce a selection of concepts in a simplified form, which are further described below in the detailed description. This summary is not intended to identify the key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. In addition, the claimed subject matter is not limited to implementations that address any or all of the disadvantages mentioned in any part of this disclosure.

[0003] A disclosed example provides a method including receiving a multiplexed transmission from a telemetry device, the multiplexed transmission including a registration message and telemetry data, demultiplexing the multiplexed transmission to obtain the registration message and the telemetry data, registering the telemetry device with a telemetry system based on the registration message, sending the telemetry data to the telemetry system, and sending a registration response to the telemetry device, the registration response confirming registration of the telemetry device with the telemetry system.

[0004] Another disclosed example provides a method that includes receiving telemetry data from a telemetry device, the telemetry data including location data, comparing the location data to defined geographic boundaries for the telemetry device, and taking action to limit use of the telemetry device when the location data does not satisfy predefined conditions regarding the defined geographic boundaries. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 An example usage environment is shown in which telemetry devices register with a single IoT endpoint and report telemetry data thereto.

[0006] Figure 2 is a block diagram illustrating an example system for performing device registration and telemetry reporting via multiplexed messaging.

[0007] Figure 3 is a flow chart illustrating an example method for providing a registration message multiplexed with telemetry data to an IoT endpoint.

[0008] Figure 4 is a flow chart illustrating an example method for registering a telemetry device with a telemetry system and reporting telemetry data on behalf of the telemetry device to the telemetry system.

[0009] Figure 5A and Figure 5B An example usage scenario is schematically illustrated, in which a telemetry device is requested to perform a re-authorization procedure after leaving a predefined geographical boundary.

[0010] Figure 6 is a flow diagram illustrating an example data exchange between a telemetry device and a cloud-based service that selectively limits usage of the telemetry device based on the geographic location of the telemetry device.

[0011] Figure 7 is a block diagram illustrating an example computing system. DETAILED DESCRIPTION

[0012] As mentioned above, IoT devices can deliver telemetry data to a cloud-based telemetry service. Before reporting of such data may occur, IoT devices can register with the service via a provisioning process. Currently, different software development kits (SDKs) and application programming interfaces (APIs) can be used for telemetry device provisioning and telemetry data reporting, because different types of communications can utilize different endpoints in network-accessible IoT services. The use of multiple SDKs and / or APIs to communicate with multiple service endpoints on a telemetry device may require IoT devices to handle more complexity, and therefore may place relatively higher memory and processing requirements on the device. This may be particularly problematic for low-power and / or low-memory devices, which may lack non-volatile storage to persistently store connection information for connecting to multiple endpoints over a restart cycle, thus requiring such devices to repeat the provisioning process at each restart. As a more specific example, a medical alert device may be configured as a small, inexpensive, low-power device that is connected to an IoT solution only when a predefined condition such as a button press or voice command is detected, and may not be configured to support multiple SDKs and APIs.

[0013] Thus, examples are disclosed involving a telemetry device that is configured to multiplex telemetry data with a registration message and pass the multiplexed transmission including the registration message and the telemetry data to a single IoT endpoint. The IoT endpoint, referred to herein as a provisioning system, handles the complexity of provisioning the telemetry device to an associated IoT solution, referred to herein as the telemetry system, and also forwards telemetry data to the telemetry system on behalf of the telemetry device. This can help reduce the memory and / or computational burden of the telemetry device by allowing the telemetry device to utilize a single SDK and API to perform stateless device provisioning and telemetry data reporting. In addition, sending the telemetry data as a multiplexed transmission with the registration message can help improve the efficiency and bandwidth usage of the telemetry reporting system.

[0014] Figure 1An example use environment 100 is shown in which telemetry devices 102, 104 each send registration data and telemetry data to a single IoT endpoint 106. Example telemetry devices include a thermostat 102 and a sensor device 104 associated with a water heater 108. In some examples, such telemetry devices 102, 104 may be configured to report telemetry data on an occasional basis, such as when a predefined condition is sensed. For example, the sensor device 104 may include a humidity sensor positioned below the water heater 108 and may be configured to report telemetry data to the IoT endpoint 106 when the presence of water is sensed. As another example, the thermostat 102 may be configured to send the measured temperature according to a schedule and / or whenever the measured temperature reaches or exceeds a threshold. In other examples, the telemetry device(s) may report telemetry data at any suitable frequency and / or based on any other trigger. Although in Figure 1 In the example of FIG. 1 , a residential environment 100 is shown, but the examples described herein can be implemented in any other suitable use environment and with any other telemetry device. Examples of other use environments include other indoor spaces, such as commercial spaces (e.g., offices, warehouses, retail stores, etc.) and outdoor spaces (e.g., farms, construction sites, parks, parking lots, etc.).

[0015] As mentioned above, sensing the presence of water can trigger the sensor device 104 to connect to the network. The sensor device 104 records the humidity sensor data as telemetry data, multiplexes the telemetry data with a registration message, and sends the multiplexed transmission to the IoT endpoint 106. For example, the registration message can include identity information that identifies the IoT endpoint 106 to the sensor device 104, a public portion of an X.509 certificate, a public portion of a trusted platform module (TPM) endorsement key, a public portion of a TPM storage root key, latitude / longitude information, and / or information about the current configuration (e.g., firmware version). In the depicted example, the sensor device 104 passes the multiplexed transmission to the local network access point 110, which transmits the received communication to the IoT endpoint 106 via a wide area network (WAN). In other examples, the telemetry device can be configured to send the multiplexed transmission directly to the IoT endpoint, rather than via an intermediate access point.

[0016] The thermostat 102 may also transmit telemetry data on an occasional basis. For example, the thermostat 102 may be configured to report thermostat telemetry data according to a schedule or threshold temperature (e.g., to help monitor home energy usage and / or adjust home temperature). The thermostat 102 may remain in a low power state until a scheduled temperature reporting time or a threshold temperature is sensed, at which time the thermostat 102 may multiplex the measurement data with the registration message and transmit the multiplexed transmission.

[0017] Figure 2A block diagram illustrating an example system 200 for combined device provisioning and telemetry data reporting is shown. System 200 includes one or more telemetry devices 202, which can represent any suitable device with a sensor. Each telemetry device 202 includes an embedded computing system, such as a microcontroller unit (MCU), a processor, a system on a chip (SoC), etc. Figure 2 204. In addition, each telemetry device 202 includes one or more sensors 204. Any suitable sensor(s) may be used. Example sensors include chemical sensors, moisture sensors, touch sensors, pressure sensors, temperature sensors, global positioning system (GPS) sensors, humidity sensors, inertial motion sensors, image sensors (depth and / or visible light), photoelectric sensors, particle sensors, smoke sensors, acoustic sensors, optical sensors, motion sensors, and proximity sensors.

[0018] Each telemetry device 202 also includes a multiplexer 206 configured to combine telemetry data (raw and / or processed sensor data) and registration messages into a multiplexed message for transmission. The multiplexed message may include any suitable data structure for conveying both registration information and telemetry data. Figure 2 As indicated by arrow 1 , the multiplexed message is sent to the IoT endpoint (provisioning system 208 ) via the provisioning system API.

[0019] In some examples, multiplexed message transmissions occur once each telemetry device is powered on. This can allow telemetry device 202 to include little persistent memory, as telemetry device 202 can simply store instructions / code for contacting a single IoT endpoint (e.g., provisioning system 208) each time telemetry device 202 undergoes a power-on process. In other examples, telemetry device 202 can transmit multiplexed transmissions according to a schedule or another periodic basis, upon sensing a predefined condition (e.g., a measurement that meets or exceeds a threshold), upon receiving a report request from a system administrator, and / or based on any other suitable trigger.

[0020] The provisioning system 208 includes a demultiplexer 210 that separates the multiplexed message into a registration message and telemetry data. After demultiplexing the multiplexed message, the provisioning system 208 stores the telemetry data in a telemetry data storage 212, at least until the telemetry data is provided to the telemetry system. An example of the provisioning system 208 is the Azure IoT Device Provisioning System (DPS), which is available from Microsoft Corporation of Redmond, Washington.

[0021] Based on the received registration message, the provisioning system 208 sends the device ID for the telemetry device 202 to the telemetry system 214, such as Figure 2 202. An example of a telemetry system is Azure IoT Hub, which is available from Microsoft Corporation of Redmond, Washington. Sending the device ID to telemetry system 214 configures telemetry system 214 to receive telemetry data from telemetry device 202 at a future time. In some examples, provisioning system 208 can select a telemetry system from a plurality of possible telemetry systems, and telemetry device 202 registers with the selected telemetry system based on information received from telemetry device 202, such as an IP address, a serial number, and / or a geographic location of telemetry device 202 (e.g., determined from global positioning satellite data).

[0022] The telemetry system 214 stores device registration data 216 for each associated telemetry device 1 to N registered / provisioned to the telemetry system 214. For each telemetry device 202, the device registration data 216 may include information such as a device ID 218 and security credentials 220 for connecting to and / or operating with the telemetry system 214.

[0023] After receiving the device ID, such as Figure 2 As indicated by arrow 3 in FIG. 2 , telemetry system 214 creates a device response for telemetry device 202 and sends it to provisioning system 208. For example, the device response may include a confirmation that the registration was successful or unsuccessful. The device response may also include information about the success or failure of registering the device with the telemetry system. In addition, in an example where the telemetry device is directly connected to the telemetry system after registration, the device response may also include information that can be used by telemetry device 202 to connect to telemetry system 214 and send data directly to telemetry system 214.

[0024] When receiving a device response, such as Figure 2 As shown by arrow 4 in FIG. 1 , the provisioning system 208 sends telemetry data to the telemetry system 214. This is different from the provisioning and telemetry data reporting systems and methods that use different SDKs / APIs to perform device provisioning and telemetry reporting respectively. Figure 2 The system allows a single endpoint to be used for both device registration and telemetry reporting, allowing telemetry devices to have less memory and computing resources than devices that use different SDKs / APIs for provisioning and telemetry reporting.

[0025] The telemetry system 214 receives telemetry data from the provisioning system 208 and stores the telemetry data in a telemetry data storage device 222. The telemetry system 214 may also provide the telemetry data to one or more telemetry data processing programs 224.

[0026] After receiving the device response, the provisioning system 208 registers the device response with the telemetry device 202, such as Figure 25. Once registration is complete, in some examples, telemetry device 202 may continue to send telemetry data to provisioning system 208 for forwarding to telemetry system 214. This may be advantageous for telemetry devices that include limited or no non-volatile storage, as such telemetry devices may continue to send telemetry data without persistently storing information for connecting to telemetry system 214. In other examples, telemetry device 202 may send telemetry data directly to telemetry system 214. Telemetry device 202 may use connection information received from provisioning system 208, for example, in a registration response message to open a direct communication channel with telemetry system 214 and send additional telemetry data directly to telemetry system 214, such as Figure 2 In another example, whenever the device sends telemetry data to the telemetry system, Figure 2 Steps 1 to 5 can all be executed.

[0027] Figure 3 An example method 300 is illustrated that can be operated by a telemetry device to send a registration message multiplexed with telemetry data to a single endpoint for registration and telemetry reporting. For example, the method 300 can be used for stateless provisioning and telemetry data transmission. The method 300 can be implemented as stored instructions that can be executed by a logic subsystem of a telemetry device such as the telemetry device 102, 104, 202, 500, and / or 602.

[0028] At 302, method 300 includes receiving telemetry data from one or more sensors. The telemetry data may include raw data (e.g., digitized sensor output), and / or may include processed sensor data (e.g., reports on threshold conditions satisfied by the sensor data). At 304, method 300 includes generating, via a multiplexer, a multiplexed transmission including a registration message and the telemetry data. In some examples, the telemetry device may be configured to generate the multiplexed transmission once the device is booted, as indicated at 306.

[0029] At 308, method 300 includes sending the multiplexed transmission to a remote computing device, the remote computing device configured to demultiplex the multiplexed transmission and forward the telemetry data to the telemetry system. Sending the multiplexed transmission to the remote computing device may include sending the multiplexed transmission to the IoT provisioning system.

[0030] At 310, method 300 includes receiving a registration response from the remote computing device, wherein the registration response confirms registration of the telemetry device with the telemetry system. In some examples, receiving the registration response includes receiving information that can be used to communicate with the telemetry system, as indicated at 312. In some such examples, the telemetry device can then connect to the telemetry system and send data directly to the telemetry system, as indicated at 314. In other examples, in addition to or as an alternative to sending data directly to the telemetry system, the telemetry device can send additional telemetry data to the remote computing device, as indicated at 316. In yet another example, the telemetry device can repeat method 300 for each transmission of telemetry data.

[0031] Figure 4 An example method 400 is illustrated for registering a telemetry device with a telemetry system and reporting telemetry data to the telemetry system on behalf of the telemetry device. The method 400 may be implemented as stored instructions executable by a logical subsystem of a provisioning system, such as an IoT endpoint 106 and / or a provisioning system 208.

[0032] At 402, method 400 includes receiving a multiplexed transmission including a registration message and telemetry data from a telemetry device. At 404, method 400 includes demultiplexing the multiplexed transmission via a demultiplexer of a provisioning system to obtain the registration message and the telemetry data. Based on the registration message extracted from the multiplexed transmission, method 400 includes, at 406, registering the telemetry device with a telemetry system. Registering the telemetry device with the telemetry system may include creating a device ID for the telemetry device, sending the device ID to the telemetry system, and receiving a device response from the telemetry system. In some examples, registering the telemetry device with the telemetry system includes registering the telemetry device with a cloud-based service associated with a user of the telemetry device, as indicated at 408.

[0033] After registering the telemetry device with the telemetry system, method 400 includes, at 410, sending telemetry data obtained from the multiplexed transmission to the telemetry system. The provisioning system may store the telemetry data at least until the telemetry system provides a device response to the telemetry device, at which point the provisioning system forwards the telemetry data to the telemetry system. In some examples, the telemetry data may cease to persist in a data storage device of the provisioning system after being forwarded to the telemetry system.

[0034] At 412, method 400 includes sending a registration response to the telemetry device, wherein the registration response confirms registration of the telemetry device with the telemetry system. Optionally, the registration response can notify the telemetry device that the telemetry system received the telemetry data. In some examples, additionally or alternatively, sending the registration response includes sending information that can be used by the telemetry device to connect to the telemetry system and send data directly to the telemetry system, as indicated at 414.

[0035] In some cases, telemetry devices may naturally operate within a defined geographic area. For example, a thermostat temperature sensor or security camera may typically be stationary once installed in the use environment. Similarly, various vehicles such as construction equipment and shopping carts may be associated with specific geographic areas (e.g., a construction site or yard, a grocery store and surrounding parking lots, etc.). When such telemetry devices leave the associated geographic area, the device may have been stolen or otherwise moved without authorization. In such cases, it may be necessary to restrict the use of the telemetry device, or take other ameliorative actions.

[0036] Thus, the telemetry system can be configured to monitor the geographic location of the telemetry device and control the use of the telemetry device based on the geographic location falling outside a defined operating area. Reauthorization of the device may be required before normal use of the telemetry device can be resumed. In some examples, the ingestion of telemetry data by the telemetry service can be restricted until reauthorization is performed. In other examples, telemetry device operation can be restricted (whether partially blocked or completely shut down) until reauthorization is performed. In yet another example, telemetry data collection can continue, but for the purpose of detecting theft or other unauthorized movement of the device, rather than for conventional telemetry purposes (e.g., by continuing to collect image data, acoustic data, and / or location data). In any of these instances, the owner and / or authorized user of the telemetry device can receive an alert about the reported location of the telemetry device outside its operating area. These actions can provide methods of theft protection and / or damage prevention for the telemetry device.

[0037] As an example, a telemetry device in the form of a shopping cart may be configured to operate within an associated retail store and a parking lot adjacent to the retail store. Thus, if the shopping cart is moved to a location outside of its designated operating range, the data collected by the shopping cart outside the designated operating range may reduce the relevance of the shopping cart tracking data set stored by the telemetry system for the retail store. Thus, data from the shopping cart may not be saved in the data set until reauthorization. As another example, a telemetry device in the form of a golf cart may be configured to operate within the perimeter of a golf course. To prevent golf course vehicles from being stolen, the telemetry system may send a command to the telemetry device to restrict operation—for example, by disabling the operation of the golf cart's motor when the telemetry device reports a location outside the golf course property until reauthorization is performed. Other example telemetry devices that may be controlled based on geographic location include other vehicles (heavy machinery, luggage carts, drones, bicycles, etc.), soil sensors, water quality sensors, containers, and any other device configured to report data for a specific location / geographic area.

[0038] Figure 5AAn example scenario is depicted in which a telemetry device 500 in the form of a work vehicle is configured to operate within a work location 502. In short, the telemetry device 500 is registered with a telemetry system 504 as being intended for use within a particular geographic boundary 506. The telemetry system 504 then monitors the geographic location of the telemetry device 500 to determine, for example based on GPS data, whether the telemetry device 500 is operating within the geographic boundary 506, and controls the use of the telemetry device 500 based on whether the geographic location of the telemetry device 500 is outside of the geographic boundary 506.

[0039] Telemetry system 504 stores telemetry device data 508 for each telemetry device 1 through N associated with work location 502 (in Figure 5A and Figure 5B 500). For each telemetry device, the telemetry device data 508 includes a device ID 510, security credentials 512, and a geographic boundary 506 in which the telemetry device is expected to be located. In some examples, each telemetry device 1 to N registered with the telemetry system 504 can be assigned to a different geographic boundary, which can be linked to the corresponding device ID of the telemetry device. In other examples, the telemetry devices 1 to N registered with the telemetry system 504 can each be assigned to the same geographic boundary.

[0040] exist Figure 5B 506, the telemetry device 500 has moved to a location 514 outside of the geographic boundary 506. In some examples, the telemetry device 500 reports the location, and the telemetry system 504 determines that the reported location is not within the geographic boundary 506. In other examples, the crossing of the geographic boundary 506 can be detected locally on the telemetry device, and the crossing is reported as an event to the telemetry system 504. In either case, the telemetry system 504 can take one or more actions to restrict the use of the telemetry device 500, such as not receiving data from the telemetry device to the telemetry system 504 until reauthorization is performed.

[0041] The telemetry system 504 may also take action to restrict the use of the telemetry device 500 by sending an alert 516 regarding a location outside of a geographic boundary, such as notifying an owner, operator, and / or other authorized personnel of an unauthorized location. Figure 5B As shown in , the alarm 516 may request reauthorization and may prompt the operator to return the telemetry device 500 to the associated working location 502. Such an alarm 516 may be output by the telemetry device 500, such as Figure 5B , and / or output to a device (e.g., a smart phone) associated with the owner of telemetry device 500.

[0042] As another example, telemetry system 504 can limit the use of telemetry device 500 by sending a command to prevent operation of telemetry device 500 when telemetry device 500 is outside geographic boundary 506. Figure 5B In the case of a bulldozer telemetry device 500 in FIG. 1 , the telemetry system 504 can send a command to disable operation of the power system of the bulldozer. This can help prevent unauthorized users from causing damage. As another example, the telemetry system 504 can take action to limit the use of the telemetry device 500 by shutting down the telemetry device 500 before reauthorization is performed.

[0043] In some cases, the operator of the telemetry device 500 may move the telemetry device 500 off-site, such as moving the telemetry device 500 to a different work site. In this case, the operator can perform a manual override to reauthorize the telemetry device 500 and remove any previously imposed barriers to the use of the device. This (and other possible reauthorization processes, such as password entry, biometric authentication, etc.) can be performed, for example, via a dashboard of the telemetry system 504 accessible to the authorized user / owner of the telemetry device 500 using a web browser or application. The operator can also redefine the geographic boundaries for the telemetry device 500 to correspond to different work sites. As another example, a store owner may intentionally transfer a shopping cart between two retail store locations. Based on its registration with the telemetry system for the first retail store or based on the geographic boundaries linked to its device ID, the shopping cart can be associated with the geographic boundaries for the first retail store. When the shopping cart is moved out of the geographic boundaries of the first retail store, the telemetry system for the first store can send an alert to the store owner indicating that the telemetry device is in an unauthorized location, and action can be taken to prevent the use of the telemetry device (e.g., by locking the wheels). The store owner can respond to the notification (e.g., via a website or mobile app dashboard for the telemetry system) to authorize the movement of the shopping cart and specify that the shopping cart will be associated with the second store. The telemetry system for the first retail store can cancel the action to restrict the use of the shopping cart and reallocate the shopping cart to the geographic boundaries of the second retail store. In the event that the second retail store is associated with a different telemetry system (e.g., a different IoT hub) than the first retail store, the shopping cart can be reallocated to the geographic boundaries of the second retail store when the second store is registered / provisioned with the telemetry system.

[0044] Figure 6A flow chart is illustrated that illustrates an example method 600 of restricting a telemetry system 604 from using a telemetry device 602. In some examples, the telemetry system 604 can take the form of software as a service (SaaS), platform as a service (PaaS), or application PaaS (aPaaS). In other examples, aspects of the telemetry system 604 can be implemented as stored instructions that can be executed by a logic subsystem of the telemetry device 602 itself, or a network edge device residing between the telemetry device 602 and the telemetry system 604.

[0045] The method 600 includes, at a telemetry device 602, reporting telemetry data including location data to a telemetry system 604, as indicated at 606. In some examples, the telemetry device 602 may report the location data without any other accompanying telemetry data. In other examples, the telemetry device 602 may report the location data and other sensor data. The location data may include any suitable type of data, including GPS data and IP address location data.

[0046] At 608, telemetry system 604 compares the received location data to predefined geographic boundaries of telemetry device 602. In some examples, comparing the location data to the defined geographic boundaries includes comparing the location data to geographic boundaries linked to the telemetry system with which the telemetry device is registered. In other examples, comparing the location data to the defined geographic boundaries includes comparing the location data to geographic boundaries linked to a device ID of the telemetry device.

[0047] In some examples, the predefined geographic boundaries may also include time constraints. Thus, comparing the location data to the defined geographic boundaries may also include comparing a timestamp or other time information associated with the location data to the time constraints on the defined geographic boundaries. For example, when the telemetry device 602 includes a container configured to be transported between locations, the predefined geographic boundaries of the container may include time constraints specifying when the container is expected to be within (or expected to leave) each of a plurality of geographic boundaries, such as geographic boundaries defined by a country, state, and / or city perimeter. In addition, the telemetry system 604 may utilize a variety of authentication factors to verify whether the telemetry device 602 is within or outside the predefined geographic boundaries. For example, the telemetry system 604 may verify whether the GPS coordinates reported by the telemetry device 602 are valid via the IP address of the telemetry device 602.

[0048] Telemetry device 602 may report location data to telemetry system 604 at any suitable frequency. The reporting frequency may depend on hardware constraints of telemetry device 602, such as battery life and / or bandwidth constraints of a network over which telemetry device 602 and telemetry system 604 communicate. For example, a telemetry device connected to a local power source may be configured to report location data more frequently than a telemetry device not connected to a local power source. In yet another example, location data may be reported based on the occurrence of an event (e.g., detection of the crossing of a geographic boundary), rather than at a selected frequency.

[0049] Based on the comparison at 608, the telemetry system 604 determines whether the location reported by the telemetry device 602 is outside the defined geographic boundaries at 610. If the location is not outside the predefined geographic boundaries of the telemetry device 602, the method 600 ends. If the location is outside the predefined geographic boundaries of the telemetry device 602, the method 600 proceeds to 612 where the telemetry system 604 takes action to restrict the use of the telemetry device 602.

[0050] The telemetry system 604 may take any suitable action to restrict the use of the telemetry device 602. In some cases, the telemetry system 604 may revoke the credentials of the telemetry device 602 so that the telemetry device is unable to connect to the telemetry system 604 using these credentials and requires reauthorization before the supply of telemetry data to the telemetry system can be resumed. For example, this can help prevent the data collected by the telemetry device 602 outside the predefined geographic boundaries from reducing the relevance of the data set stored in the telemetry system 604 for the defined geographic boundaries. In addition, in some cases, the telemetry system 604 may send a command to prevent the operation of the telemetry device 602, as indicated at 616. In response, the telemetry device 602 may reduce its functionality, as indicated at 618. In addition, in some examples, as indicated at 620, the cloud-based service telemetry system 604 may send an alert for output by the telemetry device 602 and / or for output by a device (e.g., a mobile device) associated with an authorized user or owner of the telemetry device 602. In response, telemetry device 602 and / or a device associated with a user of telemetry device 602 may output an alert, as indicated at 622 .

[0051] In any of these instances, the telemetry system 604 may also send a revocation of authorization and require reauthorization to resume normal telemetry device use, as indicated at 624. In response, the telemetry device 602 may send reauthorization data, such as location data and / or user input to the telemetry device, as indicated at 626. Additionally or alternatively, the telemetry system may receive reauthorization data from an owner / administrator of the telemetry system 604, for example, via a web portal or application for the telemetry system 604. At 628, if reauthorization of the telemetry device 602 is successful, a command is sent at 630 to resume normal use of the telemetry device. This may include removing previously imposed blocks on device use and / or restoring connection information for connecting with the telemetry system 604. In the event that reauthorization is unsuccessful, the method 600 maintains usage restrictions for the telemetry device 602 and may send additional alerts regarding the reauthorization failure, as indicated.

[0052] In some embodiments, the methods and processes described herein may be bound to a computing system of one or more computing devices. In particular, such methods and processes may be implemented as a computer application or service, an application programming interface (API), a library, and / or other computer program products.

[0053] Figure 7 A non-limiting embodiment of a computing system 700 that can perform one or more of the above methods and processes is schematically illustrated. The computing system 700 is shown in simplified form. The computing system 700 can take the form of one or more personal computers, server computers, tablet computers, home entertainment computers, network computing devices, gaming devices, mobile computing devices, mobile communication devices (e.g., smart phones), and / or other computing devices.

[0054] The computing system 700 includes a logic machine 702 and a storage machine 704. Optionally, the computing system 700 may include a display subsystem 706, an input subsystem 708, a communication subsystem 710, and / or Figure 7 Other components not shown.

[0055] The logic machine 702 includes one or more physical devices configured to execute instructions. For example, the logic machine 702 may be configured to execute instructions that are part of one or more applications, services, programs, routines, libraries, objects, components, data structures, or other logical constructs. Such instructions may be implemented to perform a task, implement a data type, transform the state of one or more components, achieve a technical effect, or otherwise achieve a desired result.

[0056] The logic machine 702 may include one or more processors configured to execute software instructions. Additionally or alternatively, the logic machine may include one or more hardware or firmware logic machines configured to execute hardware or firmware instructions. The processor of the logic machine 702 may be single-core or multi-core, and the instructions executed thereon may be configured for sequential, parallel and / or distributed processing. Optionally, the various components of the logic machine 702 may be distributed among two or more separate devices, which may be remotely located and / or configured for coordinated processing. Various aspects of the logic machine 702 may be virtualized and executed by a remotely accessible networked computing device configured in a cloud computing configuration.

[0057] The storage machine 704 includes one or more physical devices configured to hold instructions executable by a logic machine to implement the methods and processes described herein. When implementing such methods and processes, the state of the storage machine 704 may be transformed—for example, holding different data.

[0058] The storage machine 704 may include removable and / or built-in devices. The storage machine 704 may include optical storage (e.g., CD, DVD, HD-DVD, Blu-ray disc, etc.), semiconductor storage (e.g., RAM, EPROM, EEPROM, etc.), and / or magnetic storage (e.g., hard disk drive, floppy disk drive, tape drive, MRAM, etc.), etc. The storage machine 704 may include volatile, non-volatile, dynamic, static, read / write, read-only, random access, sequential access, location addressable, file addressable, and / or content addressable devices.

[0059] It should be understood that storage 704 includes one or more physical devices. However, aspects of the instructions described herein may alternatively be propagated by a communication medium (eg, electromagnetic signals, optical signals, etc.) that is not retained by a physical device for a finite duration.

[0060] Aspects of the logic machine 702 and the memory machine 704 may be integrated together into one or more hardware logic components. Such hardware logic components may include field programmable gate arrays (FPGAs), program and application specific integrated circuits (PASIC / ASIC), program and application specific standard products (PSSP / ASSP), systems on chips (SOCs), and complex programmable logic devices (CPLDs).

[0061] The term "program" may be used to describe aspects of the computing system 700 that are implemented to perform a particular function. In some cases, a program may be instantiated via the logic machine 702 executing instructions held by the storage machine 704. It should be understood that different programs may be instantiated from the same application, service, code block, object, library, routine, API, function, etc. Likewise, the same program may be instantiated by different applications, services, code blocks, objects, routines, APIs, functions, etc. The term "program" may include a single or a group of executable files, data files, libraries, drivers, scripts, database records, etc.

[0062] It should be understood that, as used herein, a "service" is an application program that is executable across multiple user sessions. A service may be available to one or more system components, programs, and / or other services. In some implementations, a service may run on one or more server computing devices.

[0063] When included, display subsystem 706 can be used to present a visual representation of the data held by storage machine 704. This visual representation can take the form of a graphical user interface (GUI). Since the methods and processes described herein change the data held by the storage machine, thereby transforming the state of the storage machine, the state of display subsystem 706 can also be transformed to visually represent the change of the underlying data. Display subsystem 706 can include one or more display devices using almost any type of technology. Such display devices can be combined in a shared shell with logic machine 702 and / or storage machine 704, or such display devices can be peripheral display devices.

[0064] When included, the input subsystem 708 may include one or more user input devices or interfaces thereof, such as a keyboard, mouse, touch screen, or game controller. In some embodiments, the input subsystem 708 may include or interface with selected natural user input (NUI) components. Such components may be integrated or peripheral, and the conversion and / or processing of input actions may be processed on-board or off-board. Example NUI components may include microphones for voice and / or sound recognition; infrared, color, stereo, and / or depth cameras for machine vision and / or gesture recognition; head trackers, eye trackers, accelerometers, and / or gyroscopes for motion detection and / or intent recognition; and electric field sensing components for assessing brain activity.

[0065] When included, the communication subsystem 710 can be configured to communicatively couple the computing system 700 with one or more other computing devices. The communication subsystem 710 can include wired and / or wireless communication devices compatible with one or more different communication protocols. As non-limiting examples, the communication subsystem can be configured to communicate via a wireless telephone network or a wired or wireless local area network or wide area network. In some embodiments, the communication subsystem can allow the computing system 700 to send and / or receive messages to and / or from other devices via a network such as the Internet.

[0066] Another example provides a method that includes receiving a multiplexed transmission from a telemetry device, the multiplexed transmission including a registration message and telemetry data, demultiplexing the multiplexed transmission to obtain the registration message and the telemetry data, registering the telemetry device with a telemetry system based on the registration message, sending the telemetry data to the telemetry system, and sending a registration response to the telemetry device, the registration response confirming the registration of the telemetry device with the telemetry system. In this example, additionally or alternatively, sending the registration response to the telemetry device may include sending information that can be used by the telemetry device to connect to the telemetry system. In this example, additionally or alternatively, registering the telemetry device with the telemetry system may include registering the telemetry device with a cloud-based service associated with a user of the telemetry device. In this example, the telemetry data may additionally or alternatively include location data, and the method may additionally or alternatively include comparing the received location data to predefined physical boundaries of the telemetry device, and when the location data does not satisfy a predefined condition about the defined physical boundaries, taking an action to restrict the use of the telemetry device. In such an example, additionally or alternatively, taking action to limit use of the telemetry device may include ceasing to send telemetry data received from the telemetry device to the telemetry system. In such an example, additionally or alternatively, taking action to limit use of the telemetry device may include one or more of sending an alert to one or more of the telemetry device and / or the telemetry system, and sending a command to the telemetry device to limit operability of the telemetry device.

[0067] Another example provides a telemetry device including a multiplexer, one or more sensors, a logic subsystem including one or more processing devices, and a memory storing instructions executable by the logic subsystem, the instructions being executed to: receive telemetry data from one or more sensors, generate a multiplexed transmission including a registration message and telemetry data via the multiplexer, send the multiplexed transmission to a remote computing device, the remote computing device being configured to demultiplex the multiplexed transmission and forward the telemetry data to a telemetry system, and receive a registration response from the remote computing device, the registration response confirming the registration of the telemetry device with the telemetry system. In such an example, the registration response may additionally or alternatively include information for communicating with the telemetry system, and the instructions may additionally or alternatively be executable to connect to the telemetry system after receiving the registration response and send data directly to the telemetry system. In such an example, the instructions may additionally or alternatively be executable to generate a multiplexed transmission once the telemetry device is started. In such an example, the instructions may additionally or alternatively be executable to power off after receiving the registration response from the remote computing device, and generate another multiplexed transmission once the telemetry device is subsequently started. In such an example, the instructions may additionally or alternatively be executable to send additional telemetry data to the remote computing device after receiving the registration response. In such an example, the telemetry device may additionally or alternatively include a microcontroller unit (MCU). In such an example, the one or more sensors may additionally or alternatively include a temperature sensor, a pressure sensor, a touch sensor, a global positioning system (GPS) sensor, a humidity sensor, a motion sensor, a water quality sensor, a chemical sensor, a level sensor, an image sensor, a smoke sensor, an acoustic sensor, and / or a gas detector / sensor.

[0068] Another example provides a method, including receiving telemetry data including location data from a telemetry device, comparing the location data to a defined geographic boundary of the telemetry device, and taking an action to limit the use of the telemetry device when the location data does not satisfy a predefined condition about the defined geographic boundary. In such an example, the telemetry device may additionally or alternatively include a vehicle. In such an example, taking the action to limit the use of the telemetry device may additionally or alternatively include sending a command to the telemetry device to reduce the operability of the telemetry device. In such an example, taking the action to limit the use of the telemetry device may additionally or alternatively include stopping communication from the telemetry device to the telemetry system. In such an example, taking the action to limit the use of the telemetry device may additionally or alternatively include sending an alert about a location that does not satisfy the predefined condition. In such an example, taking the action to limit the use of the telemetry device may additionally or alternatively include sending a command to perform a reauthorization process. In such an example, the method may additionally or alternatively include receiving reauthorization data, and in response to the reauthorization data satisfying a predefined reauthorization condition, sending a command to remove a previously imposed block on the use of the telemetry device.

[0069] It should be understood that the configuration and / or method described herein are exemplary in nature, and these specific embodiments or examples should not be considered restrictive, because many variations are possible. The specific routine or method described in this article can represent one or more of any number of processing strategies. Therefore, the various actions illustrated and / or described can be performed or omitted in the order illustrated and / or described, in other orders, in parallel. Equally, the order of the process described above can be changed.

[0070] The subject matter of the present disclosure includes all novel and non-obvious combinations and sub-combinations of the various processes, systems and configurations, and other features, functions, acts, and / or properties disclosed herein, as well as any and all equivalents thereof.

Claims

1. A method for communication, comprising: receiving a multiplexed transmission from a telemetry device via an application programming interface (API), the multiplexed transmission comprising a registration message and telemetry data; demultiplexing the multiplexed transmission to obtain the registration message and the telemetry data; registering the telemetry device with the telemetry system based on the registration message; sending the telemetry data to the telemetry system; sending a registration response to the telemetry device, the registration response confirming registration of the telemetry device with the telemetry system; as well as An additional transmission is received from the telemetry device via the API, the additional transmission including additional telemetry data but not including a registration message. 2 . The method of claim 1 , wherein sending the registration response to the telemetry device comprises sending information that can be used by the telemetry device to connect to the telemetry system. 3 . The method of claim 1 , wherein registering the telemetry device with the telemetry system comprises registering the telemetry device with a cloud-based service associated with a user of the telemetry device.

4. The method of claim 1 , wherein the telemetry data comprises location data, the method further comprising: comparing the received location data to predefined physical boundaries for the telemetry device; as well as When the location data does not satisfy the predefined condition with respect to the predefined physical boundary, action is taken to restrict use of the telemetry device.

5. The method of claim 4, wherein taking the action to limit the use of the telemetry device comprises ceasing to send the telemetry data received from the telemetry device to the telemetry system.

6. A method according to claim 4, wherein the action taken to limit the use of the telemetry device includes one or more of the following: sending an alarm to one or more of the telemetry device and / or the telemetry system, and sending a command to the telemetry device to limit the operability of the telemetry device.

7. A telemetry device comprising: multiplexer; one or more sensors; a logic subsystem, the logic subsystem comprising one or more processing devices; as well as a memory storing instructions executable by the logic subsystem to: receiving telemetry data from the one or more sensors; generating, via the multiplexer, a multiplexed transmission comprising a registration message and the telemetry data; sending the multiplexed transmission to a remote computing device via an application programming interface API, the remote computing device being configured to demultiplex the multiplexed transmission and forward the telemetry data to a telemetry system; receiving a registration response from the remote computing device, the registration response confirming registration of the telemetry device with the telemetry system; as well as An additional transmission is sent via the API, the additional transmission including the additional telemetry data but not including the registration message.

8. The telemetry device of claim 7, wherein the registration response includes information for communicating with the telemetry system, and wherein after receiving the registration response the instructions are further executable to connect to the telemetry system and send data directly to the telemetry system.

9. The telemetry device of claim 7, wherein the instructions are executable to generate the multiplexed transmission upon startup of the telemetry device.

10. The telemetry device of claim 9, wherein the instructions are further executable to power down after receiving the registration response from the remote computing device and generate another multiplexed transmission upon subsequent startup of the telemetry device.

11. The telemetry device according to claim 7, wherein the telemetry device comprises a microcontroller unit (MCU).

12. The telemetry device of claim 7, wherein the one or more sensors include one or more of a temperature sensor, a pressure sensor, a touch sensor, a global positioning system (GPS) sensor, a humidity sensor, a motion sensor, a water quality sensor, a chemical sensor, a level sensor, an image sensor, a smoke sensor, an acoustic sensor, and / or a gas detector / sensor.

13. A method for communication, comprising: receiving a multiplexed transmission from a telemetry device via an application programming interface (API), the multiplexed transmission comprising a registration message and telemetry data including location data; demultiplexing the multiplexed transmission to obtain the position data; comparing the location data to defined geographic boundaries for the telemetry device; receiving, via the API, an additional transmission from the telemetry device, the additional transmission comprising additional telemetry data but not including a registration message; and When the location data does not satisfy predefined conditions with respect to defined physical boundaries, action is taken to restrict usage of the telemetry device. The method of claim 13 , wherein the telemetry device comprises a vehicle.

15. The method of claim 13, wherein taking the action to limit the use of the telemetry device comprises sending a command to the telemetry device to reduce operability of the telemetry device.

16. The method of claim 13, wherein taking the action to limit the use of the telemetry device comprises stopping communications from the telemetry device to a telemetry system.

17. The method of claim 13, wherein taking the action to limit the use of the telemetry device comprises sending an alert that the location does not satisfy the predefined condition.

18. The method of claim 13, wherein taking the action to restrict the use of the telemetry device comprises sending a command to perform a reauthorization process.

19. The method of claim 18, further comprising receiving reauthorization data, and in response to the reauthorization data satisfying a predefined reauthorization condition, sending a command to remove a previously imposed block on the use of the telemetry device.

Citation Information

Patent Citations

  • Method and system for generation and use of sensor device identifiers and related devices

    CN103001838A

  • Middleware registration method under RESTful framework

    CN103986709A

  • Device registration and sounding in time-division multiple access network

    CN104756584A

  • Method for operating a sensor arrangement with multiple sensor devices, sensor device, sensor arrangement and sensor system

    EP3016351A1

  • Method of joint registration and de-registration for proximity services and internet of things services

    EP3047662A1