WO2023065353A1

WO2023065353A1 - Data transmission method, sensing system and sensor hub

Info

Publication number: WO2023065353A1
Application number: PCT/CN2021/125887
Authority: WO
Inventors: Kai Yu
Original assignee: Shenzhen Rakwireless Technology Co., Ltd.
Priority date: 2021-10-22
Filing date: 2021-10-22
Publication date: 2023-04-27

Abstract

Provided are a data transmission method, a sensing system and a sensor hub, the sensing system includes a sensor hub and at least one sensor probe connectable to the sensor hub, where a respective sensor probe is configured to: acquire sensor data; convert the sensor data into first communication protocol data, wherein the sensor data and the first communication protocol data correspond to different communication protocols; and send the first communication protocol data to the sensor hub based on a first communication protocol. Based on the solution described in the present disclosure, a sensing system can be easily implemented and flexibly extendable to adapt to various needs for different application scenarios.

Description

DATA TRANSMISSION METHOD, SENSING SYSTEM AND SENSOR HUB

TECHNICAL FIELD

The present disclosure relates generally to the technical field of Internet of Things and, in particular, to a data transmission method, a sensing system and a sensor hub.

BACKGROUND

With the fast development of Internet of Things technology, the functionality of an Internet of Things system is evolving more and more complicated. Typically, a great deal amount of sensors may be integrated in an Internet of Things system. For example, sensors of different types may be required for a system. Theses sensors of different types may include a temperature sensor, a humidity sensor, an illuminance sensor or the like. Moreover, in a practical application, sensors from different manufactures may be used in the system.

Sensors of a same type or different types usually adopt different interfaces/communication protocols, such as an I ²C protocol, a 1-wire protocol, an SPI (Serial Peripheral Interface) protocol, a UART (Universal Asynchronous Receiver/Transmitter) protocol, an RS-232 protocol or an RS-485 protocol. Therefore, in a practical application, an Internet of Things system is typically required to be compatible with various interfaces/communication protocols.

This background information is provided to reveal information believed by the applicant to be of possible relevance to the present disclosure. No admission is necessarily intended, nor should be construed, that any of the preceding information constitutes prior art against the present disclosure.

SUMMARY

One objective of the present disclosure is to provide a universal solution with unified and interchangeable products to implement a sensing system, for example, an Internet of Things system, which can be easily implemented and flexibly extendable to adapt to different application scenarios.

The present disclosure provides a data transmission method, a sensing system and a sensor hub.

A first aspect of the present disclosure relates to a sensing system, including: a sensor hub and at least one sensor probe connectable to the sensor hub, where,

a respective sensor probe is configured to:

acquire sensor data;

convert the sensor data into first communication protocol data, where the sensor data and the first communication protocol data correspond to different communication protocols; and

send the first communication protocol data to the sensor hub based on a first communication protocol.

In a possible implementation, where the sensor hub is connectable to a plurality of sensor probes of at least one type; where a respective type of sensor probe is connectable to at least one sensor corresponding to a fixed communication protocol; where a communication protocol corresponding to a sensor that is connectable to one type of sensor probe is different from a communication protocol corresponding to a sensor that is connectable a different one type of sensor probe.

In a possible implementation, the at least one sensor probe includes a first sensor probe, the first sensor probe is connectable to at least one sensor and is configured to acquire the sensor data through the at least one sensor;

where sensor data of the at least one sensor is based on a second communication protocol.

In a possible implementation, the at least one sensor probe includes a second sensor probe, the second sensor probe is connectable to at least two sensors and is configured to acquire the sensor data through the at least two sensors, where sensor data of the at least two sensors is based on at least a third communication protocol and a fourth communication protocol;

the second sensor probe is configured to, before converting sensor data of a respective sensor which is connected with the second sensor probe into the first communication protocol data, determine a communication protocol corresponding to the sensor data of the respective sensor which is connected with the second sensor probe.

In a possible implementation, the sensor hub is provided with at least one port; and the respective sensor probe is connectable to the sensor hub via one of the at least one port using a corresponding unified communication interface.

In a possible implementation, the unified communication interface includes a connector that is suitable to be plugged in the one of the at least one port of the sensor hub.

In a possible implementation, the sensor hub is configured to maintain a sensor probe list, and communicate with the respective sensor probe based on the sensor probe list;

where the sensor probe list includes a mapping relationship between a communication ID of the respective sensor probe, and registration information of the respective sensor probe.

In a possible implementation, the registration information of the respective sensor probe includes a registration ID of the respective sensor probe, and the sensor hub is configured to:

receive the registration ID of the respective sensor probe from the respective sensor probe;

determine whether the registration ID of the respective sensor probe is recorded in the sensor probe list; and

in response to determining that the registration ID of the respective sensor probe is not recorded in the sensor probe list, assign a communication ID for the respective sensor probe.

In a possible implementation, the sensor hub is further configured to:

add the assigned communication ID of the respective sensor probe in the sensor probe list.

In a possible implementation, a registration ID of a sensor probe includes a universally unique identifier (UUID) or a serial number (SN) of a sensor probe, and the sensor hub is configured to:

assign the communication ID for the respective sensor probe based on the registration ID of the respective sensor probe.

In a possible implementation, the sensor hub is further configured to send a respective communication ID to the respective sensor probe to instruct the respective sensor probe to store the respective communication ID.

In a possible implementation, the sensor hub is further configured to:

determine a respective communication ID associated with the registration ID of the respective sensor probe in response to determining that the registration ID of the respective sensor probe is already recorded in the sensor probe list, and

send the respective communication ID to the respective sensor probe.

In a possible implementation, the respective sensor probe gets power supply from the sensor hub when the respective sensor probe is plugged into one of the at least one port of the sensor hub, and the respective sensor probe is configured to:

run bootup codes when the respective sensor probe gets power supply from the sensor hub;

send a first wakeup request to the sensor hub; and

in response to receiving a first wakeup response from the sensor hub, send the registration ID of the respective sensor probe to the sensor hub.

In a possible implementation, the registration information of the respective sensor probe further includes user configuration information of the respective sensor probe, and the sensor hub is further configured to:

send the user configuration information of the respective sensor probe to the respective sensor probe to instruct the respective sensor probe to perform configuration according to the user configuration information of the respective sensor probe.

In a possible implementation, the sensor hub is further configured to:

acquire the user configuration information of the respective sensor probe; and

add the user configuration information of the respective sensor probe in the sensor probe list.

In a possible implementation, the sensor hub is specifically configured to:

when the sensor hub receives the registration ID of the respective sensor probe, determine whether the sensor probe list includes user configuration information associated with a communication ID of the respective sensor probe; and

in response to determining that the sensor probe list includes user configuration information associated with the communication ID of the respective sensor probe, send the user configuration information of the respective sensor probe to the first sensor probe.

In a possible implementation, the registration information of the respective sensor probe includes connection status information of the respective sensor probe, and the sensor hub is configured to:

update the connection status information of the respective sensor probe when the respective sensor probe is plugged into or unplugged from the one of the at least one port of the sensor hub.

In a possible implementation, the at least one sensor probe includes at least two sensor probes, the sensor hub is configured to:

determine a target sensor probe out of the at least two sensor probes; and

send a triggering signal to the target sensor probe to enable the target sensor probe to send the first communication protocol data to the sensor hub based on the first communication protocol, and send a stopping signal to the sensor probe other than the target sensor probe to disable the sensor probe other than the target sensor probe from sending the first communication protocol data to the sensor hub based on the first communication protocol.

In a possible implementation, the sensor hub is further configured to:

send a second wakeup request to the target sensor probe, where the second wakeup request includes a communication ID of the target sensor probe;

receive a second wakeup response from the target sensor probe; and

receive the first communication protocol data from the target sensor probe.

In a possible implementation, the at least one sensor probe includes a third sensor probe, and the sensor hub is configured to:

in response to being triggered to wake up by a third wakeup request from the third sensor probe, send a third wakeup response to the third sensor probe; and

receive the first communication protocol data from the third sensor probe.

A second aspect of the present disclosure relates to a data transmission method, including:

acquiring, by a sensor probe, sensor data through at least one sensor;

converting, by the sensor probe, the sensor data into first communication protocol data, where the sensor data of the at least one sensor and the first communication protocol data correspond to different communication protocols; and

sending, by the sensor probe, the first communication protocol data to a sensor hub based on a first communication protocol.

In a possible implementation, sensor data of a respective sensor corresponds to a second communication protocol;

the converting, by the sensor probe, the sensor data into the first communication protocol data, includes:

converting, by the sensor probe, the sensor data corresponding to the second communication protocol into the first communication protocol data.

In a possible implementation, sensor data of a respective sensor corresponds to one of at least a third communication protocol and a fourth communication protocol;

before the converting, by the sensor probe, the sensor data into the first communication protocol data, the method further includes:

determining, by the sensor probe, a communication protocol corresponding to the sensor data of the respective sensor;

converting, by the sensor probe, the sensor data corresponding to the determined communication protocol into the first communication protocol data.

In a possible implementation, the sensor hub is connected with at least two sensor probes, the method further includes:

determining, by the sensor hub, a target sensor probe out of the at least two sensor probes; and

sending, by the sensor hub, a triggering signal to the target sensor probe to enable the target sensor probe to send the first communication protocol data to the sensor hub based on the first communication protocol, and sending, by the sensor hub, a stopping signal to the sensor probe other than the target sensor probe to disable the sensor probe other than the target sensor probe from sending the first communication protocol data to the sensor hub based on the first communication protocol.

In a possible implementation, before the sending, by the sensor probe, the first communication protocol data to a sensor hub based on a first communication protocol, the method further includes:

receiving, by the sensor probe, a wakeup request from the sensor hub, where the wakeup request includes a communication ID which is assigned for the sensor probe by the sensor hub;

sending, by the sensor probe, a wakeup response to the sensor hub.

sending, by the sensor probe, a wakeup request to the sensor hub; and

receiving, by the sensor probe, a wakeup response from the sensor hub.

In a possible implementation, the method further includes:

maintaining, by the sensor hub, a sensor probe list, and communicating, by the sensor hub, with the respective sensor probe based on the sensor probe list;

where the sensor probe list includes a mapping relationship between a communication ID of a respective sensor probe, and registration information of the respective sensor probe.

In a possible implementation, where the registration information of the respective sensor probe includes ID of the respective sensor probe, and the method includes:

receiving, by the sensor hub, the registration ID of the respective sensor probe from the respective sensor probe;

determining, by the sensor hub, whether the ID on of the respective sensor probe is recorded in the sensor probe list; and

in response to determining that the registration ID of the respective sensor probe is not recorded in the sensor probe list, assigning, by the sensor hub, a communication ID for the respective sensor probe.

In a possible implementation, the method further includes:

adding, by the sensor hub, the assigned communication ID of the respective sensor probe in the sensor probe list.

In a possible implementation, the method further includes:

sending, by the sensor hub, the respective communication ID to the respective sensor probe to instruct the respective sensor probe to store the communication ID.

In a possible implementation, the method further includes:

determining, by the sensor hub, a respective communication ID associated with the registration ID of the respective sensor probe in response to determining that the registration ID of the respective sensor probe is already recorded in the sensor probe list, and

sending, by the sensor hub, the respective communication ID to the respective sensor probe

A third aspect of the present disclosure relates to a sensor hub, including:

at least one processor; and a memory communicatively connected with the at least one processor; where the sensor hub is connectable to at least one sensor probe, the memory stores instructions executable by the at least one processor, and the instructions, when executed by the at least one processor, cause the at least one processor to: receive first communication protocol data from the at least one sensor probe based on the first communication protocol.

In a possible implementation, the instructions cause the at least one processor to maintain a sensor probe list, and communicate with the respective sensor probe based on the sensor probe list;

In a possible implementation, where the registration information of the respective sensor probe includes a registration ID of the respective sensor probe, the at least one sensor probe includes a first sensor probe, and the instructions cause the at least one processor to:

receive a registration ID of the first sensor probe from the first sensor probe;

determine whether the registration ID of the first sensor probe is recorded in the sensor probe list; and

in response to determining that the registration ID of the first sensor probe is not recorded in the sensor probe list, assign a communication ID for the first sensor probe.

In a possible implementation, the instructions further cause the at least one processor to:

add the assigned communication ID and the registration ID of the first sensor probe in the sensor probe list.

In a possible implementation, where the registration ID of the first sensor probe includes a universally unique identifier (UUID) or a serial number (SN) of a sensor probe, the instructions cause the at least one processor to:

assign the communication ID for the first sensor probe based on the registration ID of the first sensor prob.

In a possible implementation, the instructions cause the at least one processor to:

send the communication ID to the first sensor probe to instruct the first sensor probe to store the communication ID.

determine a communication ID associated with the registration ID of the first sensor probe in response to determining that the registration ID of the first sensor probe is already recorded in the sensor probe list, and

send the communication ID to the first sensor probe.

In a possible implementation, where the instructions cause the at least one processor to:

provide power supply to the first sensor probe when the first sensor probe is plugged into the one of the at least one port of the sensor hub; and

send a first wakeup response to the first sensor probe in response to receiving a first wakeup request from the first sensor probe.

In a possible implementation, where registration information of the first sensor probe further includes user configuration information of the first sensor probe, and the instructions cause the at least one processor to:

send the user configuration information of the first sensor probe to the first sensor probe to instruct the first sensor probe to perform configuration according to the user configuration information of the first sensor probe.

acquire the user configuration information of the first sensor probe; and

add the user configuration information of the first sensor probe in the sensor probe list.

when the sensor hub receives the registration ID of the first sensor probe, determine whether the sensor probe list includes user configuration information associated with a communication ID of the first sensor probe; and

in response to determining that the sensor probe list includes user configuration information associated with the communication ID of the first sensor probe, send the user configuration information of the first sensor probe to the first sensor probe.

In a possible implementation, the registration information of the respective sensor probe includes connection status information of the respective sensor probe, and the instructions cause the at least one processor to:

In a possible implementation, the at least one sensor probe includes at least two sensor probes, the instructions cause the at least one processor to:

determine a target sensor probe out of the at least two sensor probes; and

receive a second wakeup response from the target sensor probe; and

receive the first communication protocol data from the target sensor probe.

In a possible implementation, the at least one sensor probe includes a second sensor probe, and the instructions cause the at least one processor to:

in response to being triggered to wake up by a third wakeup request from the second sensor probe, send a third wakeup response to the second sensor probe; and

receive the first communication protocol data from the second sensor probe.

A fourth aspect of the present disclosure relates to a data transmission method implemented by a sensor hub, including:

receiving, by the sensor hub, first communication protocol data sent by a respective sensor probe connected to the sensor hub based on a first communication protocol.

In a possible implementation, the method further includes:

In a possible implementation, the registration information of the respective sensor probe includes ID of the respective sensor probe, the at least one sensor probe includes a first sensor probe, the method further includes:

receiving, by the sensor hub, a registration ID of the first sensor probe from the first sensor probe;

determining, by the sensor hub, whether the registration ID of the first sensor probe is recorded in the sensor probe list; and

in response to determining that the registration ID of the first sensor probe is not recorded in the sensor probe list, assigning, by the sensor hub, a communication ID for the first sensor probe.

In a possible implementation, the method further includes:

adding, by the sensor hub, the assigned communication ID and the registration ID of the first sensor probe in the sensor probe list.

In a possible implementation, the registration ID of a sensor probe includes a universally unique identifier (UUID) or a serial number (SN) of a sensor probe;

the assigning, by the sensor hub, a communication ID for the first sensor probe, includes:

assigning, by the sensor hub, the communication ID for the first sensor probe based on the UUID of the first sensor probe.

In a possible implementation, before the receiving, by the sensor hub, the method further includes:

sending, by the sensor hub, the communication ID to the first sensor probe to instruct the first sensor probe to store the communication ID.

determining, by the sensor hub, a communication ID associated with the registration ID of the first sensor probe in response to determining that the registration ID of the first sensor probe is already recorded in the sensor probe list, and

sending, by the sensor hub, the communication ID to the first sensor probe.

In a possible implementation, before the receiving, by the sensor hub, a registration ID of the first sensor probe from the first sensor probe, the method further includes:

sending, by the sensor hub, a first wakeup response to the first sensor probe in response to receiving a first wakeup request from the first sensor probe.

In a possible implementation, registration information of the first sensor probe further includes user configuration information of the first sensor probe, and the method further includes:

sending, by the sensor hub, the user configuration information of the first sensor probe to the first sensor probe to instruct the first sensor probe to perform configuration according to the user configuration information of the first sensor probe.

In a possible implementation, the method further includes:

acquiring, by the sensor hub, the user configuration information of the first sensor probe; and

adding, by the sensor hub, the user configuration information of the first sensor probe in the sensor probe list.

In a possible implementation, the method further includes:

when the sensor hub receives the attribution information of the first sensor probe, determining, by the sensor hub, whether the sensor probe list includes user configuration information associated with a communication ID of the first sensor probe; and

in response to determining that the sensor probe list includes user configuration information associated with the communication ID of the first sensor probe, sending, by the sensor hub, the user configuration information of the first sensor probe to the first sensor probe.

In a possible implementation, the registration information of the respective sensor probe includes connection status information of the respective sensor probe, the method further includes:

updating, by the sensor hub, the connection status information of the respective sensor probe when the respective sensor probe is plugged into or unplugged from the one of the at least one port of the sensor hub.

In a possible implementation, the at least one sensor probe includes at least two sensor probes, the method further includes:

sending, by the sensor hub, a triggering signal to the target sensor probe to enable the target sensor probe to send the first communication protocol data to the sensor hub based on the first communication protocol, and simultaneously, sending, by the sensor hub, a stopping signal to the sensor probe other than the target sensor probe to disable the sensor probe other than the target sensor probe from sending the first communication protocol data to the sensor hub based on the first communication protocol.

In a possible implementation, the method further includes:

sending, by the sensor hub, a second wakeup request to the target sensor probe, where the second wakeup request includes a communication ID of the target sensor probe;

receiving, by the sensor hub, a second wakeup response from the target sensor probe; and

receiving, by the sensor hub, the first communication protocol data from the target sensor probe.

In a possible implementation, the at least one sensor probe includes a second sensor probe, the method further includes:

in response to being triggered to wake up by a third wakeup request from the second sensor probe, sending, by the sensor hub, a third wakeup response to the second sensor probe; and

receiving, by the sensor hub, the first communication protocol data from the second sensor probe.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram of a sensing system according to an embodiment of the present disclosure;

FIG. 2A is an exemplary structural diagram of a sensor probe according to an embodiment of the present disclosure;

FIG. 2B is an exemplary structural diagram of a sensor probe according to an embodiment of the present disclosure;

FIG. 3 is a structural diagram of a sensor hub according to an embodiment of the present disclosure;

FIG. 4 is a schematic illustration of an application scenario of a sensing system according to an embodiment of the present disclosure;

FIG. 5 is a schematic diagram of a sensing system according to an embodiment of the present disclosure;

FIG. 6 is an exemplary schematic flowchart of data transmission between a sensor hub and a sensor probe according to an embodiment of the present disclosure;

FIG. 7 is an exemplary schematic statechart of a sensor probe according to an embodiment of the present disclosure;

FIG. 8 is an exemplary schematic flowchart of data transmission between a sensor hub and a sensor probe according to an embodiment of the present disclosure;

FIG. 9 is an exemplary schematic flowchart of data transmission between a sensor hub and a sensor probe according to an embodiment of the present disclosure;

FIG. 10 is a schematic flowchart of a data transmission method according to an embodiment of the present disclosure;

FIG. 11 is a schematic flowchart of a data transmission method according to an embodiment of the present disclosure;

FIG. 12 is a schematic structural diagram of a sensor hub according to an embodiment of the present disclosure; and

FIG. 13 is a schematic structural diagram of a sensor probe according to an embodiment of the present disclosure.

DESCRIPTION OF EMBODIMENTS

In the following description, reference is made to the accompanying figures, which form part of the disclosure, and which show, by way of illustration, specific aspects of embodiments of the present disclosure or specific aspects in which embodiments of the present disclosure may be used. It is understood that embodiments of the present disclosure may be used in other aspects and comprise structural or logical changes not depicted in the figures. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims.

For instance, it is understood that a disclosure in connection with a described method may also hold true for a corresponding device or system configured to perform the method and vice versa. For example, if one or a plurality of specific method steps are described, a corresponding device may include one or a plurality of units, e.g. functional units, to perform the described one or plurality of method steps (e.g. one unit performing the one or plurality of steps, or a plurality of units each performing one or more of the plurality of steps) , even if such one or more units are not explicitly described or illustrated in the figures. On the other hand, for example, if a specific apparatus is described based on one or a plurality of units, e.g. functional units, a corresponding method may include one step to perform the functionality of the one or plurality of units (e.g. one step performing the functionality of the one or plurality of units, or a plurality of steps each performing the functionality of one or more of the plurality of units) , even if such one or plurality of steps are not explicitly described or illustrated in the figures. Further, it is understood that the features of the various exemplary embodiments and/or aspects described herein may be combined with each other, unless specifically noted otherwise.

Terms such as “first” , “second” and the like in the specification and claims of the present disclosure as well as in the above drawings are intended to distinguish different objects, but not intended to define a particular order or quantity. For example, when there is a second object, it does not necessarily mean that there is a first object, and vice versa.

The term “a” or “an” is not intended to specify one or a single element, instead, it may be used to represent a plurality of elements where appropriate.

In the embodiments of the present disclosure, expressions such as “exemplary” or “for example” are used to indicate illustration of an example or an instance. In the embodiments of the present disclosure, any embodiment or design scheme described as “exemplary” or “for example” should not be interpreted as preferred or advantageous over other embodiments or design schemes. In particular, the use of “exemplary” or “for example” is aimed at presenting related concepts in a specific manner.

Normally, different types of sensors use different hardware interfaces corresponding to different communication protocols. Even, sensors of a same type but from different manufactures still may not be used interchangeably due to different interfaces or communication protocols.

Therefore, integrating sensors in an Internet of Things system often requires adaptation of both a hardware level and a software level, considering how widely Internet of Things technology is applied, which could be greatly laborious and therefore time, cost consuming.

FIG. 1 is a schematic diagram of a sensing system according to an embodiment of the present disclosure. With reference to FIG. 1, several terms that may be used in the present disclosure are briefly explained, and an overall introduction of the solution provided in the present disclosure is made in the following.

With reference to FIG. 1, a sensor 11 is used to acquire sensor data. The sensor may be a temperature sensor, a humidity sensor, an illuminance sensor or the like. The sensor 11 may be set in any environment from which it is necessary for the purpose to acquire sensor data. For example, the sensor may be set in a wall of a building to detect a movement, or set in a frame structure of a bridge to detect a vibration range, or buried underground to detect the humidity of soil, which will not be elaborated herein.

It is noted that an environment where a sensor is set, an application purpose of a sensor or a sensor type is not specifically limited in the present disclosure.

With reference to FIG. 1, a sensor probe 12 serves as an interface between a sensor 11 and a hub 13 (which will be described in the following) . One end of the sensor probe 12 is connectable to the hub 13, and the other end of the sensor probe 12 is connectable to one or a plurality of sensors 11.

In an implementation, an end of a sensor probe 12 may be provided with one or a plurality of sockets, and a plurality of sensors 11 may be respectively attached to and detached from the plurality of sockets.

In another implementation, a plurality of sensors 11 are integrated in a sensor probe 12, that is, the probe 12, as a ready-made product, includes a plurality of sensors 12 as its components integrated within.

In a case where a sensor probe 12 is connectable to a plurality of sensors 11, the plurality of sensors 11 connected with or integrated in the sensor probe 12 may use a same communication protocol or different communication protocols to communicate sensor data with the sensor probe 12. However, sensor data acquired through different sensors are all converted by the sensor probe 12 into data of a unified communication protocol, and transmitted from the sensor probe 12 to the sensor hub 13. The sensor data is transmitted in the direction indicated with by arrows in FIG. 1.

For example, a sensor probe 12 acquires sensor data of a certain communication protocol through any one of a plurality of sensors 11, converts the sensor data into data of the unified communication protocol, and send the converted data to the sensor hub 13.

In a case where a sensor probe 12 is connectable to one sensor 11, the sensor probe 12 acquires sensor data of a certain communication protocol through the one sensor 11 that is connected to the sensor probe, converts the sensor data into data of the unified communication protocol, and send the converted data to the sensor hub 13. In a case where the communication protocol is the same as the unified communication protocol, the sensor probe 12 does not converts the sensor data but transmits the sensor data to the sensor hub 13.

In an implementation, the sensor probe 12 is provided with a processor, for example, a MCU (Micro Processing Unit) or the like, which is preferably a low power and low cost element, and the processor is configured to convert sensor data acquired through a sensor 11 into data of the unified communication protocol.

For the purpose of conciseness and clarity, in the following description, the unified communication protocol used for data transmission between the sensor probe 12 and the sensor hub 13 is referred to as a first communication protocol, and a communication protocol used for data transmission between a sensor 11 and the processor of the sensor probe 12 is referred to as a second communication protocol, a third communication protocol or a fourth communication protocol.

Correspondingly, sensor data of the first communication protocol is referred to as first communication protocol sensor data or first communication protocol data, sensor data of the second/third/fourth communication protocol is referred to as second/third/fourth communication protocol sensor data or second/third/fourth communication protocol data.

FIG. 2A and 2B are exemplary structural diagrams of a sensor probe according to an embodiment of the present disclosure.

With reference to FIG. 2A, a sensor probe includes a cable 21 with an interface 22 which is suitable to be connected with a sensor hub and communicate based on the first communication protocol, and one interface 23 which is connectable to one sensor.

With reference to FIG. 2B, a sensor probe includes a cable 21 with an interface 22, and a plurality of interfaces 23 which are respectively connectable to one sensor.

Preferably, the first communication protocol is a communication protocol suitable for long distance data transmission, which normally means higher noise tolerance. For example, the first communication protocol may be but not limited to a serial communication protocol such as a UART (Universal Asynchronous Receiver/Transmitter) protocol.

In a practical application scenario, a long distance transmission for the sensor data may be required, for example, a sensor may be set a long distance away from a sensor hub. However, a communication protocol that the sensor supports, an I ²C protocol for example, may not be suitable for long distance data transmission due to weak noise tolerance. Based on a protocol suitable for long distance data transmission, sensor data transmission is guaranteed even from a long distance. Moreover, since a sensor can be set in a longer distance away from the sensor hub, a wider coverage for a sensor hub can be achieved.

Preferably, sensor probes are made in different types, where a respective type of sensor probe is connectable to one or a plurality of sensors which communicate sensor data based on one or a plurality of communication protocols.

In an implementation, sensor probes of different types are designed to communicate sensor data to a sensor hub based on a same communication. In addition, each of the sensor probes of different types is connectable to the sensor hub using a unified communication interface. For example, the sensor hub is provided with at least one port, and sensor probes of different types can be respectively connected to the sensor hub via one of the at least one port interchangeably.

With reference to FIG. 2A, in a case where the probe is connectable to one sensor, the sensor may use the first communication protocol or use a communication protocol that is different from the first communication protocol.

For example, a sensor probe of type I is connectable to one sensor which communicate sensor data based on the first communication protocol. Regarding to a sensor probe of type I, when the sensor probe acquires sensor data (first communication protocol sensor data) through one sensor, it does not converts the sensor data but transmits the sensor data acquired through the sensor to the sensor hub.

For another example, a sensor probe of type II is connectable to one sensor which communicate sensor data based on the second communication protocol. Regarding to a sensor probe of type II, when the sensor probe acquires sensor data (second communication protocol sensor data) through one sensor, it convert the sensor data into first communication protocol data and send the converted data to a sensor hub.

With reference to FIG. 2B, in a case where the probe is connectable to a plurality of sensors, the plurality of sensors may use a same communication protocol.

For example, a sensor probe of type III is connectable to 4 sensors all using the second communication protocol.

With reference to FIG. 2B, in a case where the probe is connectable to a plurality of sensors, the plurality of sensors may use two or more communication protocols which are different from the first communication protocol.

For another example, a sensor probe of type IV is connectable to 4 sensors, where 1 sensor uses the third communication protocol and 3 sensors uses the fourth communication protocol.

With reference to FIG. 2B, in a case where the probe is connectable to a plurality of sensors, the plurality of sensors may use two or more communication protocols which may include the first communication protocol.

For example, a sensor probe of type V is connectable to 4 sensors, where 1 sensor uses the first communication protocol and 3 sensors uses the second, the third and the fourth communication protocol respectively. Regarding to a sensor probe of type V, when the sensor probe acquires sensor data through a sensor using a communication protocol other than the first communication protocol, it converts the sensor data into first communication protocol data and sends the converted data to a sensor hub; when the sensor probe acquires sensor data through a sensor using the first communication protocol, it is not necessary to perform the data conversion operation, so the sensor probe may just transmit the sensor data acquired from the sensor to the sensor hub.

It is noted that the sensor probe type I, II, III, IV or V as specified above are merely exemplary. More sensor probe types may be designed based on practical needs.

A sensor that is connected with a sensor probe may communicate sensor data based on any one of the first, the second, the third and the fourth communication protocol. However, the sensor data communication between a sensor probe and a sensor hub is always the first communication protocol.

The second/third/fourth communication protocol may include but not limited to an I ²C protocol, a 1-wire protocol, an SPI (Serial Peripheral Interface) protocol, an RS-232 protocol, an RS-485 protocol, an analog RS-232 protocol, a PWM (Pulse Width Modulation) protocol, etc.

With reference to FIG. 1, the sensor hub 103 in the present disclosure, which can be connected with one or a plurality of sensor probes, performs multiple functions including but not limited to: providing power supply to sensor probes 102 connected with the sensor hub 103, storing sensor data received from the sensor probes 102, and providing an interface to connect to a host 104 (such as a user interface device, a server or a big data platform) , so that the host 104 may access the data the sensor hub 103 stores, or access the sensor probes 102 connected with the sensor hub 103 (for example, to re-configure a sensor probe 102 connected with the sensor hub 103) .

A sensor hub 103 is provided with one or a plurality of ports, and a sensor probe can be connected with the sensor hub via a port of the sensor hub using a unified communication interface (for example, the interface 22 as shown in FIG. 2A and FIG. 2B) .

FIG. 3 is a structural diagram of a sensor hub according to an embodiment of the present disclosure. With reference to FIG. 3, a sensor hub is provided with a plurality of ports 31, the plurality of ports 31 are preferably the same in terms of hardware. In an implementation, with reference to FIG. 2A and 2B, the unified communication interface 23 includes a connector that is suitable to be plugged in any one of the plurality of ports 31 of the sensor hub. For example, when a sensor probe is unplugged from one port 31 of the hub, it can be then plugged into another port 31 of the hub since the plurality of ports 31 are the same in terms of hardware, and the communication interfaces of different sensor probes are unified.

In a practical application scenario, there may be one or a plurality of sensor probes that are connected with the sensor hub.

In a case where there is one sensor probe that is connected with the sensor hub, the type of the sensor probe may be any one type as specified above or any other type that those skilled in the art may envisage based on the present disclosure.

In a case where there are a plurality of sensor probes that are connected with the sensor hub, the plurality of sensor probes may be of the same type, or of different types.

It is noted that the quantity of sensor probes that are actually connected with the sensor hub may be more than the quantity of the ports of the sensor hub. For example, a splitter (for example, a Y-type splitter) may be connected to the hub via a port, and a plurality of sensor probes may be connected to the splitter, that is, a plurality of sensor probes may be connected with the sensor hub via one port of the hub, thereby a sensing system provided in the present disclosure can be flexibly extendable to adapt to various application scenarios.

The sensor hub is normally a low power device which may be set in different environment. FIG. 4 is a schematic illustration of an application scenario of a sensing system according to an embodiment of the present disclosure. In an example, with reference to FIG. 4, a sensor hub 41 may be set in a farmland connected to a solar panel 42 for power supply, and connected with at least one sensor probe 43 which is connected with sensors 44 buried underground in the farmland for detecting temperature, humidity or the like. The sensor hub may be connected to a host 45 (for example, a user interface device, a server, or a big data platform) via wireless communication technology, such as LoRa technology, which is not specifically limited in the present disclosure.

Based on the embodiments corresponding to FIG. 1 to FIG. 4, another sensing system is provided in the present disclosure. FIG. 5 is a schematic diagram of a sensing system according to an embodiment of the present disclosure. The above description about a sensor hub and a sensor probe made with reference to FIG. 1 to FIG. 4 can be combined in the embodiment corresponding to FIG. 5, same description will not be repeated in the embodiment.

With reference to FIG. 5, the sensing system includes a sensor hub 51 and at least one sensor probe 52 connectable to the sensor hub 51.

A respective sensor probe 51 is configured to:

acquire sensor data;

send the first communication protocol data to the sensor hub 51 based on a first communication protocol.

The sensor hub 51 is configured to receive the first communication protocol data. It is noted that the data transmission between the sensor hub 51 and the at least one sensor probe 52 is based on the first communication protocol.

There may be one or a plurality of sensor probes that are connected with the sensor hub. In a case where a plurality of sensor probes are connected with the sensor hub, the plurality of sensor probes may be of the same type, or of different types.

In an implementation, the sensor hub 51 is connectable with the at least one sensor probe 52 of at least one type, where a respective type of sensor probe is connectable to at least one sensor corresponding to a fixed communication protocol, where a communication protocol corresponding to a sensor that is connectable to one type of sensor probe is different from a communication protocol corresponding to a sensor that is connectable a different one type of sensor probe.

For example, a sensor probe of type VI is connectable one or a plurality of sensors corresponding to the second communication protocol, and a sensor probe of type VII is connectable one or a plurality of sensors corresponding to the third communication protocol. In other words, all sensors that are connected with a sensor probe of type VI communicate sensor data based on the second communication protocol, and all sensors that are connected with a sensor probe of type VII communicate sensor data based on the third communication protocol.

Based on the needs in a practical scenario, the sensor hub 51 may be connected with only one sensor probe 52, which may be of any type as specified in the present disclosure, or any other type that those skilled in the art may envisage based on the present disclosure. Or, the sensor hub 51 may be connected with a plurality of sensor probes 52 of a same type. Or, the sensor hub 51 may be connected with a plurality of sensor probes 52 of different types, and the different types may include but not limited to type VI and type VII, where each type supports sensors corresponding to a fixed communication protocol. Or the different types may further include other types such as type I to type VI.

In an implementation, the at least one sensor probe 52 includes a first sensor probe, the first sensor probe is connectable to at least one sensor and is configured to acquire the sensor data through the at least one sensor, where sensor data of the at least one sensor is based on a second communication protocol.

In a case where a plurality of sensors are connectable to the first sensor probe, all of the plurality of sensors communicate sensor data with a same communication protocol (the second communication protocol) .

In another implementation, the at least one sensor probe 52 includes a second sensor probe, the second sensor probe is connectable to the at least two sensors and is configured to acquire the sensor data through the at least two sensors, where sensor data of the at least two sensors is based on at least a third communication protocol and a fourth communication protocol.

In a case where a plurality of sensors are connectable to the second sensor probe, different sensors that are connectable to the second sensor probe communicate sensor data using different communication protocols which may include but not limited to the third communication protocol and a fourth communication protocol.

Since the sensors that can be connected to the second sensor probe use different communication protocols, when sensor data is acquired through a respective sensor which is connected with the second sensor probe, (the processor of) the second sensor probe firstly needs to determine a communication protocol corresponding to the sensor data of the respective sensor, and then convert the sensor data into the first communication protocol data.

For example, when sensor data is acquired through a sensor, the second sensor probe firstly determines that the sensor communicates the sensor data with the third communication protocol, then the sensor probe convert the sensor data corresponding to the third communication protocol to the first communication protocol data.

However, regarding to the first sensor probe, since all of the plurality of sensors communicate sensor data with the second communication protocol, it is not necessary for the first sensor probe to determine what communication protocol is used, so the first sensor probe, when sensor data is acquired through a respective sensor which is connected with the first sensor probe, directly convert the sensor data based on the second communication protocol and the first communication protocol.

In an implementation, the sensor hub 51 is provided with at least one port, and the respective sensor probe 52 is connectable to the sensor hub 51 via one of the at least one port using a corresponding unified communication interface. For example, the unified communication interface includes a connector that is suitable to be plugged in one of the at least one port of the sensor hub 51.

The sensor hub 51 may maintain a sensor probe list, and communicate with the respective sensor probe 52 that is connected with the senor hub 51 based on the sensor probe list. As shown in Table 1, the sensor probe list includes a mapping relationship between a communication ID (identifier) of the respective sensor probe 51, and registration information of the respective sensor probe 51.

Table 1

In an implementation, the communication ID is assigned by the sensor hub 51 for a sensor probe 52 for data or information transmission between the sensor hub 51 and the sensor probe 52 during the lifecycle when the sensor probe 52 is connected with the sensor hub 51. Registration information of a sensor probe 52 includes but not limited to at least one of attribution information, user configuration information and connection status information of the sensor probe 52, which will be explained in the following examples. In addition, the detailed process of data or information transmission between the sensor hub 51 and a sensor probe 52 will also be specified in the following examples with reference to FIG. 6-FIG. 9.

FIG. 6 is an exemplary schematic flowchart of data transmission between a sensor hub and a sensor probe according to an embodiment of the present disclosure.

With reference to FIG. 6, when a sensor probe is plugged into a port of the sensor hub, the power supply is applied by the sensor hub to the sensor probe via the unified interface.

When a power supply is applied, the sensor probe is configured to run bootup codes, and send a first wakeup request to the sensor hub.

The sensor hub is usually designed as a low power device. For example, when there is no data transmission between the sensor hub and any sensor probe that is connected with the sensor hub, the sensor hub will enter a power saving mode (sleep mode) .

In a case the sensor hub receives the wakeup request in the power saving mode, it will switch from the power saving mode to a wakeup mode, this mode transition is usually called as “waken up” . After wakening up, it will send a first wakeup response to the sensor probe as ACK (Acknowledge) information.

In a case the sensor hub receives the first wakeup request in the wakeup mode, it will just send the first wakeup response to the sensor probe.

It is noted that data or information transmission between the sensor hub and the sensor probe are in a form of a data packet of the first communication protocol, so the data or information transmission between the two may also be referred to as a “packet” in this disclosure. For example, a wakeup request may also be referred to as a wakeup packet, and the wakeup response may also be referred to as a response packet or ACK packet.

The sensor probe, in response to receiving the first wakeup response from the sensor hub, will send the attribution information of the sensor probe to the sensor hub.

The attribution information of the sensor probe is normally locally stored in the sensor probe (for example, in an EEPROM (Electrically Erasable Programmable Read Only Memory) of the sensor probe) . The attribution information of the sensor probe includes a registration ID of the sensor probe, the registration ID of the sensor probe is preferably the sensor probe’s unique hardware ID which may include but not limited to an UUID (universally unique identifier) or a SN (serial number) of the sensor probe. The attribution information may further include preset configuration information, a hardware version and a firmware version of the sensor probe, and at least one sensor type supported by the sensor probe. Where the preset configuration information may include but not limited to a period for collecting sensor data, or a threshold for triggering an event, an error, an alert, a report or the like.

FIG. 7 is an exemplary schematic statechart of a sensor probe according to an embodiment of the present disclosure.

With reference to FIG. 7, a sensor probe is in an off state when it is unplugged (disconnected) from a sensor hub. When it is plugged in the hub, it runs bootup codes and enters a non-provisioned state. In the non-provisioned state, the sensor probe sends a provisioning request packet to the sensor hub, and enters a provisioned state when it receives a provisioning response packet from the sensor hub. In the provisioned state, it may trigger an event, an error, an alert or a report, send sensor data to the sensor hub, or the sensor hub may access the sensor probe (for example, request sensor data from the sensor probe or re-configure the sensor probe) .

With reference to FIG. 6 and FIG. 7, in an example, the sensor probe sends the attribution information to the hub through a provisioning request packet when the sensor probe is in the non-provisioned state.

In the example, the sensor hub is configured to assign a communication ID for each sensor probe that is plugged in the sensor hub, record the assigned communication ID and corresponding registration information in the sensor probe list, and send the assigned communication ID to a corresponding sensor probe. The communication ID will be used as the identification information of the corresponding sensor probe in subsequent packet transmission between the hub and the sensor probe.

In a practical application scenario, a sensor probe may be plugged in or unplugged from the senor hub for multiple times. In the example, if a sensor probe is plugged in a sensor hub for the first time, sensor probe will send its attribution information to the sensor hub. The sensor hub will determine whether the registration ID of the sensor probe is recorded in the sensor probe list. If the sensor hub finds that this ID of the sensor probe is new, it will add this ID of the sensor probe to the sensor probe list and assign a communication ID to the sensor probe based on the registration ID of the sensor probe. The communication ID may be recorded in the sensor probe list in associated with the attribution information of the sensor probe, and if a sensor probe is plugged in the sensor hub for a second time, since the communication ID is already recorded in the sensor hub’s sensor probe list when the sensor probe is plugged in the sensor hub for the first time, the sensor hub will assign the recorded communication ID to the sensor probe.

To adapt the solution of the present disclosure to the practical application scenario, in an implementation, on receiving a provisioning request packet (attribution information) from a sensor probe, a sensor hub firstly determines whether the registration ID of the sensor probe is already recorded in the sensor probe list.

With reference to FIG. 6, In response to determining that the registration ID of the sensor probe is not recorded in the sensor probe list, the sensor hub assigns a communication ID for the first sensor probe, updates the sensor probe list by adding the communication ID of the first sensor probe in the sensor probe list, and sends the assigned communication ID to the sensor probe.

In response to determining that the registration ID of the sensor probe is already recorded in the sensor probe list, the sensor hub finds a communication ID in its sensor probe list based on the registration ID of the sensor probe, and sends the communication ID to the sensor probe.

In an implementation, the registration ID of the sensor probe is a UUID of the sensor probe, and the communication ID is a parameter devADDR under LoRaWAN protocol. The sensor hub may determine whether the UUID of the sensor probe is already recorded in the sensor probe list, if the UUID is not recorded in the sensor probe list, the sensor hub assigns a devADDR in associated with the UUID, adds the devADDR and the attribution information of the sensor probe in the sensor probe list, and sends the devADDR to the sensor probe. If the UUID is already recorded in the sensor probe list, the sensor hub sends the devADDR which is already recorded in the sensor probe list to the sensor probe.

In LoRaWAN protocol communication, a parameter devADDR is essentially required. Conventionally, the parameter devADDR is burned into an EEPROM of a device which is connected in a LoRaWAN network. The present disclosure, when implemented in a LoRaWAN network, a sensor probe can be accessed by a hub or a host based on a parameter devADDR assigned by a sensor hub for a sensor probe without burning the parameter devADDR into an EEPROM of a sensor probe.

By recording only a (hardware) ID on a sensor probe rather than recording both the ID and devADDR on the sensor probe, a sensor probe will not be bind to only one sensor hub. Thus one sensor probe may be disconnected from one sensor hub and connect to another sensor hub, or disconnected from one sensor hub and replaced with another sensor probe, that is, one sensor probe can be used interchangeably between different sensor hubs. This makes it more flexible to use the sensor probe and sensor hub especially when the sensor probe or the sensor hub is broken and need to be replaced or repaired.

Another implement is that the sensor probe will store the devADDR the first time the sensor hub assigns the devADDR to it. So next time the sensor probe doesn’ t need to wait for the sensor hub to assign the devADDR to it. This could shorten the time of data transmission between the sensor probe and the sensor hub.

With reference to FIG. 6 and FIG. 7, when a new sensor probe is plugged into a sensor hub, it is in the non-provisioned state. The device will request a Device Address from sensor hub with its unique hardware ID (S/N or UUID) . Before sending the provisioning request packet, it needs to send a wakeup request packet to wake up the sensor hub and wait for a wakeup response. Once the wakeup response is replied, the sensor probe will send the provisioning request packet with its attributes in payload to the sensor hub. The provisioning request packet may include a UUID, and may also include a hardware version, a firmware version, or sensor profile data, etc. When the sensor hub receives the provisioning request packet, it will check if the UUID is registered or not, and then reply a unique devADDR with its stored setting via the provisioning request packet in its payload format, including the devADDR, a sensor setting, etc. The sensor setting may be a period to get the sensor data, and/or a threshold for triggering a sensor data report such as the upper limit of the temperature etc.

In an implementation, the registration information of a sensor probe further includes user configuration information of the sensor probe. For example, the sensor hub may acquire the user configuration information of the sensor probe from a host (such as a user interface device, a server or a big data platform) , and send the user configuration information to the sensor probe to instruct the sensor probe to perform configuration according to the user configuration information.

In addition, the sensor hub may add the user configuration information of the sensor probe in the sensor probe list. When the sensor probe is plugged in the sensor hub for a second time, the sensor hub may send the user configuration information to the sensor probe again. For example, with reference to FIG. 6, when the sensor probe is plugged in the sensor hub for a second time, it will send attribution information of the sensor probe (through a provisioning request packet) to the sensor hub. The hub, on receiving the attribution information of the sensor probe, determines whether the sensor probe list includes user configuration information associated with the assigned communication ID, in response to determining that the sensor probe list includes user configuration information associated with the communication ID, send the user configuration information in the sensor probe list to the sensor probe.

The sensor probe, on receiving the user configuration information, performs configuration according to the user configuration information.

In an implementation, the registration information of a sensor probe further includes connection status information of the respective sensor probe that is recorded in the sensor probe list. The connection status information of a sensor probe indicates whether the sensor probe is plugged in (connected with) the sensor probe, or unplugged from (disconnected from) the sensor probe. In an example, the sensor hub updates the connection status information of the respective sensor probe that is recorded in the sensor probe list when the respective sensor probe is plugged into or unplugged from a port of the sensor hub.

The sensor probe is usually designed as a low power device, in the Provisioned state, if there is no data to be transmitted to the sensor hub, it will switch to a power saving mode. In other words, both of the sensor hub and the sensor probe may switch to a power saving mode respectively.

In an example, both the sensor hub and the sensor probe may trigger sensor data packet transmission between the sensor hub and the sensor probe, which will be specified in the following with reference to FIG. 8 and FIG. 9.

FIG. 8 is an exemplary schematic flowchart of data transmission between a sensor hub and a sensor probe according to an embodiment of the present disclosure, which illustrate a situation where sensor data packet transmission between the sensor hub and the sensor probe is triggered by the sensor hub.

For example, the sensor hub receives a sensor data request from a host, where the sensor data request includes a communication ID. Accordingly, the sensor hub determines from the sensor probes, which are currently plugged in the sensor hub as indicated by the connection status information recorded in the sensor probe list, the sensor probe corresponding to the communication ID as the target sensor probe.

With reference to FIG. 8, the sensor hub sends a second wakeup request to the target sensor probe, where the second wakeup request includes the communication ID of the target sensor probe. The target sensor probe, on receiving the second wakeup request, switches from the power saving mode to the wakeup mode, sends a second wakeup response to the sensor hub. Subsequently, the target sensor probe forms sensor data of a sensor that is connected with the target sensor probe into a sensor data packet based on the first communication protocol, and sends the sensor data packet (the first communication protocol data) to the sensor hub. The sensor hub checks data packet integrity and sends a sensor data ACK packet back to the target sensor probe. On receiving the sensor data ACK packet, the target sensor enters the power saving mode.

In a case where a plurality of sensor probes are plugged in the sensor hub, if two or more sensor probes transmit sensor data packets simultaneously, interference between different sensor probes may be incurred. In an example, to avoid the interference, the sensor hub may enable only the target sensor probe to send sensor data packet, and disable the sensor probe (s) other than the target sensor probe from sending the sensor data packet.

In an implementation, on determining the target sensor probe, the sensor hub sends a triggering signal to the target sensor probe and a stopping signal to the sensor probe (s) other than the target sensor probe before sending a second wakeup request to the target sensor probe.

Where, the sensor hub sends the triggering signal to the target sensor probe to enable the target sensor probe to send the first communication protocol data to the sensor hub based on the first communication protocol, and the sensor hub sends a stopping signal to the sensor probe (s) other than the target sensor probe to disable the sensor probe (s) other than the target sensor probe from sending the first communication protocol data to the sensor hub based on the first communication protocol. The sensor hub may send the triggering signal and the stopping signal simultaneously.

In a case where a first sensor probe and a second sensor probe are connected with a sensor hub, and the first sensor probe is determined as the target sensor probe, the first sensor probe receives a triggering signal from the sensor hub, and the second sensor probe receives a stopping signal from the sensor hub.

On condition that the triggering signal is received from the sensor hub, the first sensor probe sends the first communication protocol data to the sensor hub. For example, on condition that the triggering signal is received from the sensor hub, the first sensor probe receives the second wakeup request, sends the second wakeup response to the sensor hub and sends the first communication protocol data to the sensor hub. On condition that the stopping signal is received from the sensor hub, the second sensor probe does not send sensor data, or any other data to the sensor hub.

FIG. 9 is an exemplary schematic flowchart of data transmission between a sensor hub and a sensor probe according to an embodiment of the present disclosure, which illustrate a situation where sensor data packet transmission between the sensor hub and the sensor probe is triggered by the sensor probe.

For example, a third sensor probe, in response to being triggered to wake up by a sensor interrupt or a timer, sends a third wakeup request to the sensor hub. The sensor hub receives the third wakeup request, wakens up and sends a third wakeup response to the third sensor probe. In response to receiving the third wakeup response from the sensor hub, the third sensor probe forms sensor data of a sensor that is connected with the third sensor probe into a sensor data packet based on the first communication protocol, and sends the sensor data packet (the first communication protocol data) to the sensor hub. The sensor hub checks data packet integrity and sends a sensor data ACK packet back to the third sensor probe. On receiving the sensor data ACK packet, the third sensor probe enters the power saving mode.

According to the sensor system explained in the embodiments of the present disclosure, a sensor hub is connectable to at least one sensor probe, and a sensor probe is connectable to at least one sensor.

A plurality of sensors connectable to a sensor probe may use a same communication protocol or different communication protocols to communicate sensor data. However, sensor data acquired through different sensors are all converted into data of a unified communication protocol, and sent to the sensor hub based on the unified communication protocol.

Based on the solution provided in the present disclosure, the sensor probes can be made as interchangeable products. For example, a sensor probe may be plugged in or unplugged from a sensor hub, a sensor probe that is plugged in a sensor hub may be easily replaced with another sensor probe. Sensor data may be acquired through sensor supporting various communication protocols but transmitted to a sensor hub through a unified communication protocol. Therefore, a sensing system may be easily built up just by selecting suitable sensor probes and connect them with a sensor hub directly or via a splitter.

Thereby, a universal solution with unified and interchangeable products to implement a sensing system is provided in the present disclosure, and by selecting a combination of sensor probes of different types, the sensing system can be easily implemented and flexibly extendable to adapt to various needs for different application scenarios.

According to embodiments of the present disclosure, sensor data transmitted between a sensor hub and a sensor probe is based on a first communication protocol. Preferably, the first communication protocol is a communication protocol suitable for long distance data transmission such that a wider coverage of the sensing system can be achieved.

As an example, taking UART protocol as the first communication protocol, the protocol data packet transmitted between a sensor hub and a sensor probe is further explained in the following.

As shown in Table 2, the basic UART protocol frame structure uses the HDLC (High-Level Data Link Control) -like format for Protocol Data Unit transmitted between a sensor probe and a sensor hub. The frame includes 8 field.

Table 2

The start and end flag indicates starting and ending point of a message transmitted between a sensor hub and a sensor probe.

The destination address indicates a device the message is going to. In an example, if the message is going to a sensor hub, the destination address is 0x00; if the message is going to a sensor probe that is in a non-provisioned state, the address is 0xFF; if the message is going to a sensor probe that is in a provisioned state, the address is 0xID, where the 0xID is a communication ID that is assigned for the sensor probe.

The source address indicates a device that creates the message. In an example, if the source device is a sensor hub, the source address is 0x00; if the source device is a sensor probe that is in a non-provisioned state, the source address is 0xFF; if the source device is a sensor probe that is in a provisioned state, the source address is 0xID, where the 0xID is a communication ID that is assigned for the sensor probe;

The sequence number is used to correlate a request frame and its ACK frame for loss packet or error messages handling.

The frame type indicates which message is encapsulated in the payload of the frame and is used at a receiving end to determine how the payload is to be processed. The exemplary values and corresponding indication includes:

0x00: Wakeup frame;

0x01: Provision Request frame;

0x02: Provision Response frame;

0x03: Parameter Setting frame;

0x04: Sensor Data frame;

0x05: Event frame;

0x06: Alert frame;

0x07: Error frame;

0x08: ACK frame;

0x09: NACK frame.

The payload field is a variable length in TLV (type-length-value) format, encoding three fields: payload length, payload type and payload data.

Where the payload length indicates the length of the payload; the payload type indicates how to parse and identify the payload data array, the exemplary values and corresponding indication of the payload type includes:

0x00: sensor probe provision packet;

0x01: sensor probe parameter setting packet;

0x02: sensor probe sensor data packet.

The payload data includes byte array of payload data that relates to the payload type. The payload data format is dependent on payload type. In the present disclosure, the payload data may be provision payload, parameter setting payload, or sensor data payload.

The present disclosure also provides a data transmission method implemented by a sensing system as described in the embodiments of the present disclosure. It is noted that elements/functions/packet transmission processes described in the above embodiments, may be combined with the following method, which will not be repeated again.

FIG. 10 is a schematic flowchart of a data transmission method according to an embodiment of the present disclosure. As shown in FIG. 10, the data transmission method includes:

S1001, a sensor probe acquires sensor data through at least one sensor.

In an implementation, a sensor probe is connectable to at least one sensor. On condition that he sensor probe is connected with the at least one sensor, the sensor probe may acquire sensor data through the at least one sensor. For example, the sensor probe receives sensor data from the at least one sensor.

S1002, the sensor probe converts the sensor data into first communication protocol data, where the sensor data of the at least one sensor and the first communication protocol data correspond to different communication protocols.

S1003, the sensor probe sends the first communication protocol data to a sensor hub based on a first communication protocol.

In an implementation, a sensor hub is connectable to at least one sensor probe, and a sensor probe is connectable to at least one sensor.

In an example, the sensor probe is connectable to one or a plurality of sensors, and sensor data of the one or the plurality of sensors corresponds to a second communication protocol. The sensor probe is configured to convert acquired sensor data into the first communication protocol data. That is, the sensor probe does not determine what communication protocol the acquired sensor data corresponds to, but directly converts the acquired sensor data into the first communication protocol data and sends to the sensor hub.

In another example, the sensor probe is connectable to one or a plurality of sensors, and sensor data of the one or the plurality of sensors corresponds to a second communication protocol. The sensor probe determines a communication protocol corresponding to the sensor data of acquired through a sensor, convert the acquired sensor data into the first communication protocol data based on the determination, and sends the first communication protocol data to the sensor hub.

FIG. 11 is a schematic flowchart of a data transmission method according to an embodiment of the present disclosure. As shown in FIG. 11, the data transmission method includes:

S1101, a sensor hub assigns a communication ID for a sensor probe, and sends the assigned communication ID to the sensor probe.

In an implementation, a sensor hub is provided with one or a plurality of ports, correspondingly, one or a plurality of sensor probes are connectable to the sensor hub. Each sensor probe is connectable to the sensor hub via a port of the sensor hub using a corresponding unified communication interface. For example, the unified communication interface includes a connector that is suitable to be plugged in any one port of the sensor hub.

When a sensor probe is plugged into a port of the sensor hub, the power supply is applied by the sensor hub to the sensor probe via the unified interface. Subsequently, the sensor hub and the sensor probe carry out the data transmission process as illustrated in FIG. 6.

During the data transmission process as illustrated in FIG. 6, in response to determining that the registration ID of the sensor probe is not recorded in the sensor probe list, the sensor hub assigns a communication ID for the sensor probe and sends the assigned communication ID to the sensor probe.

During the data transmission process as illustrated in FIG. 6, in response to determining that the registration ID of the sensor probe is already recorded in the sensor probe list, the sensor hub sends a communication ID which is already recorded in the sensor probe list in associated with the attribution information.

In an example, the attribution information of the sensor probe includes a UUID of the sensor probe, and the communication ID includes a parameter devADDR under LoRaWAN protocol. The sensor hub may determine whether the UUID of the sensor probe is already recorded in the sensor probe list, if the UUID is not recorded in the sensor probe list, the sensor hub assigns a devADDR in associated with the UUID, adds the devADDR in the sensor probe list, and sends the devADDR to the sensor probe. If the UUID is already recorded in the sensor probe list, the sensor hub sends the devADDR which is already recorded in the sensor probe list to the sensor probe.

In another example, when a sensor probe is plugged into a sensor hub for the first time, the sensor hub determines that the UUID of the sensor probe is not recorded in the sensor probe list, assigns a devADDR and sends the devADDR to the sensor probe to indicate the sensor probe to store the devADDR. The sensor probe stores the devADDR. When the sensor probe is plugged into the sensor hub for a second time, if the sensor hub determines that the UUID is already recorded in the sensor probe list, it will not send the devADDR to the sensor probe since the sensor probe has already stored the devADDR when it is plugged into the sensor hub for the first time.

S1102, the sensor hub communicate with a respective sensor probe which is connected with the sensor hub based on the communication ID.

The communication ID is assigned for a sensor probe for a packet transmission between the sensor hub and the sensor probe during the lifecycle when the sensor probe is connected with the sensor hub.

For example, a packet transmitted between the sensor hub and the sensor probe may include the communication ID. The packet transmitted between the sensor hub and the sensor probe includes but not limited to a packet transmitted from the sensor hub to the sensor probe or a packet transmitted from the sensor probe to the sensor hub.

For example, with reference to FIG. 8, FIG. 9 and Table 2, the destination address of a packet transmitted from the sensor hub to the sensor probe, such as the second wakeup request or the sensor data ACK packet, includes the communication ID; the source address of a packet transmitted from the sensor probe to the sensor hub, such as the third wakeup request or the sensor data packet, includes the communication ID.

In an implementation, the sensor hub requests and receives sensor data from a sensor probe that is connected with the sensor hub.

For example, the sensor hub determines a target sensor probe from the sensor probes that are currently connected with the sensor hub, sends a triggering signal to the target sensor probe, and sends a stopping signal to the sensor probe (s) other than the target sensor probe. Subsequently, the sensor hub and the sensor probe carry out the data transmission process as illustrated in FIG. 8.

In an implementation, a sensor probe that is currently connected with the sensor hub initiates sensor data transmission to the sensor hub.

For example, when a sensor probe is triggered to wake up by a sensor interrupt or a timer, subsequently, the sensor hub and the sensor probe carry out the data transmission process as illustrated in FIG. 9.

In an implementation, the sensor hub receives a configuration request from a host, the configuration request includes user configuration information and a communication ID. On receiving the configuration request, the sensor hub sends the user configuration information to the sensor probe to instruct the sensor probe to perform configuration according to the user configuration information.

In addition, the sensor hub may add the user configuration information in the sensor probe list in associated with the communication ID. When the sensor probe is unplugged from the sensor hub and plugged in the sensor hub again, the sensor hub may send the user configuration information to the sensor probe again, such that the sensor probe may be configured accordingly.

In an implementation, the sensor hub updates connection status information of a sensor probe that is recorded in the sensor probe list when the sensor probe is plugged into or unplugged from a port of the sensor hub. The connection status information of a sensor probe indicates whether the sensor probe is plugged in (connected with) the sensor probe, or unplugged from (disconnected from) the sensor probe.

The present disclosure also provides a sensor hub as described in the embodiments of the present disclosure. It is noted that elements/functions/packet transmission processes implemented by a sensor hub as described in the above embodiments may be combined with the following embodiment, which will not be repeated again.

FIG. 12 is a schematic structural diagram of a sensor hub according to an embodiment of the present disclosure. As shown in FIG. 12, the sensor hub includes: at least one processor 1201; and a memory 1202 communicatively connected with the at least one processor 1201.

Where the sensor hub is connectable to at least one sensor probe, the memory 1202 stores instructions executable by the at least one processor 1201, and the instructions, when executed by the at least one processor 1201, cause the at least one processor 1201 to perform the functions/steps implemented by a sensor hub as described in the embodiments of the present disclosure.

In a possible implementation, the instructions cause the at least one processor 1201 to receive first communication protocol data from the at least one sensor probe based on the first communication protocol.

In a possible implementation, the sensor hub is provided with at least one port, and a respective sensor probe is connectable to the sensor hub via one of the at least one port using a corresponding unified communication interface.

In a possible implementation, the instructions cause the at least one processor 1201 to maintain a sensor probe list, and communicate with the respective sensor probe based on the sensor probe list;

In a possible implementation, where the registration information of the respective sensor probe includes a registration ID of the respective sensor probe, the at least one sensor probe includes a first sensor probe, and the instructions cause the at least one processor 1201 to:

determine whether the registration ID of the first sensor probe is recorded in the sensor probe list;

in response to determining that the registration ID of the first sensor probe is not recorded in the sensor probe list, assign a communication ID for the first sensor probe; and

add the assigned communication ID in the sensor probe list.

In a possible implementation, the instructions cause the at least one processor 1201 to send the communication ID to the first sensor probe to instruct the first sensor probe to store the communication ID.

In a possible implementation, the instructions cause the at least one processor 1201 to:

send the communication ID to the first sensor probe.

In a possible implementation, where the attribution information of the first sensor probe includes a universally unique identifier UUID of the first sensor probe, the instructions cause the at least one processor 1201 to:

assign the communication ID for the first sensor probe based on the UUID of the first sensor probe, where the communication ID includes a parameter devADDR under LoRaWAN protocol; and

send the communication ID to the first sensor probe.

In a possible implementation, where the instructions cause the at least one processor 1201 to:

In a possible implementation, where registration information of the first sensor probe further includes user configuration information of the first sensor probe, and the instructions cause the at least one processor 1201 to:

acquire the user configuration information of the first sensor probe; and

when the sensor hub receives the attribution information of the first sensor probe, determine whether the sensor probe list includes user configuration information associated with a communication ID of the first sensor probe; and

In a possible implementation, the registration information of the respective sensor probe includes connection status information of the respective sensor probe, and the instructions cause the at least one processor 1201 to:

In a possible implementation, the at least one sensor probe includes at least two sensor probes, the instructions cause the at least one processor 1201 to:

determine a target sensor probe out of the at least two sensor probes; and

receive a second wakeup response from the target sensor probe; and

receive the first communication protocol data from the target sensor probe.

In a possible implementation, the at least one sensor probe includes a second sensor probe, and the instructions cause the at least one processor 1201 to:

receive the first communication protocol data from the second sensor probe.

The present disclosure also provides a data transmission method implemented by a sensor hub as described in the embodiments of the present disclosure, the method includes:

In a possible implementation, the method further includes:

In a possible implementation, the registration information of the respective sensor probe includes a registration ID of the respective sensor probe, the at least one sensor probe includes a first sensor probe, the method further includes:

determining, by the sensor hub, whether the registration ID of the first sensor probe is recorded in the sensor probe list;

in response to determining that the registration ID of the first sensor probe is not recorded in the sensor probe list, assigning, by the sensor hub, a communication ID for the first sensor probe, and

adding, by the sensor hub, the assigned communication ID in the sensor probe list.

In a possible implementation, attribution information of the first sensor probe includes a universally unique identifier UUID of the first sensor probe;

assigning, by the sensor hub, the communication ID for the first sensor probe based on the UUID of the first sensor probe, where the communication ID includes a parameter devADDR under LoRaWAN protocol;

the method further includes:

sending, by the sensor hub, the communication ID to the first sensor probe.

In a possible implementation, the method further includes:

sending, by the sensor hub, the communication ID to the first sensor probe.

In a possible implementation, before the receiving, by the sensor hub, the registration ID of the first sensor probe from the first sensor probe, the method further includes:

In a possible implementation, the method further includes:

The present disclosure also provides a sensor probe as described in the embodiments of the present disclosure. It is noted that elements/functions/packet transmission processes implemented by a sensor probe as described in the above embodiments may be combined with the following embodiment, which will not be repeated again.

FIG. 13 is a schematic structural diagram of a sensor probe according to an embodiment of the present disclosure. As shown in FIG. 13, the sensor probe includes: a processor 1301; and a memory 1302 communicatively connected with the processor 1301; where the sensor probe is connectable to a sensor hub; the memory 1302 stores instructions executable by the processor 1301, and the instructions, when executed by the processor 1301, cause the processor 1301 to perform the functions/steps implemented by a sensor hub as described in the embodiments of the present disclosure.

In a possible implementation, the instructions cause the processor 1301 to:

acquire sensor data;

In a possible implementation, the sensor probe is connectable to at least one sensor, and the instructions cause the processor 1301 to acquire the sensor data through the at least one sensor;

In a possible implementation, the sensor probe is connectable to at least two sensors, and the instructions cause the processor 1301 to acquire the sensor data through the at least two sensors;

where sensor data of the at least two sensors is based on at least a third communication protocol and a fourth communication protocol;

In a possible implementation, the instructions further cause the processor 1301 to:

before converting sensor data of a respective sensor which is connected with the second sensor probe into the first communication protocol data, determine a communication protocol corresponding to the sensor data of the respective sensor which is connected with the second sensor probe.

In a possible implementation, the sensor probe gets power supply from the sensor hub when the sensor probe is plugged into one of at least one port of the sensor hub;

the instructions further cause the processor 1301 to:

run bootup codes when the sensor probe gets power supply from the sensor hub;

send a first wakeup request to the sensor hub; and

in response to receiving a first wakeup response from the sensor hub, send the registration ID of the sensor probe to the sensor hub.

In a possible implementation, the instructions cause the processor 1301 to:

send an identifier ID of the sensor probe to a sensor hub;

receive a communication ID from the sensor hub, where the communication ID is assigned for the sensor probe in a case where the registration ID of the sensor probe is not recorded in a sensor probe list of the sensor hub; and

store the communication ID.

In a possible implementation, the instructions cause the processor 1301 to:

send a registration ID of the sensor probe to a sensor hub; and

receive a communication ID from the sensor hub, where the communication ID is assigned for the sensor probe in a case where the registration ID of the sensor probe is already recorded in a sensor probe list of the sensor hub.

In a possible implementation, the instructions cause the processor 1301 to:

in response to receiving a second wakeup request from the sensor hub, send a second wakeup response to the sensor hub, where the second wakeup request includes the communication ID;

form the sensor data into a sensor data packet based on the first communication protocol; and

send the sensor data packet to the sensor hub.

In a possible implementation, the instructions cause the processor 1301 to:

in response to being triggered to wake up by an sensor interrupt or a timer, send a third wakeup request to the sensor hub;

in response to receiving a third wakeup response from the sensor hub, form the sensor data into a sensor data packet based on the first communication protocol; and

send the sensor data packet to the sensor hub.

receive user configuration information of the sensor probe from the sensor hub; and

perform configuration according to the user configuration information of the sensor probe.

receive a triggering signal from the sensor hub; and

on condition that the triggering signal is received from the sensor hub, send the first communication protocol data to the sensor hub.

receive a stopping signal from the sensor hub; and

on condition that the triggering signal is received from the sensor hub, not to send the first communication protocol data to the sensor hub.

The present disclosure also provides a data transmission method implemented by a sensor probe as described in the embodiments of the present disclosure, the data transmission method includes:

acquiring, by the sensor probe, sensor data;

converting, by the sensor probe, the sensor data into first communication protocol data, where the sensor data and the first communication protocol data correspond to different communication protocols; and

sending, by the sensor probe, the first communication protocol data to the sensor hub based on a first communication protocol.

In a possible implementation, before converting, by the sensor probe, the sensor data into the first communication protocol data, further including:

determining, by the sensor probe, a communication protocol corresponding to the sensor data.

In a possible implementation, before acquiring, by the sensor probe, the sensor data, further including;

sending, by the sensor probe, a first wakeup request to the sensor hub; and

in response to receiving a first wakeup response from the sensor hub, sending, by the sensor probe, attribution information of the sensor probe to the sensor hub.

In a possible implementation, the method further includes:

sending, by the sensor probe, an identifier ID of the sensor probe to a sensor hub;

receiving, by the sensor probe, a communication ID from the sensor hub, where the communication ID is assigned for the sensor probe in a case where the registration ID of the sensor probe is not recorded in a sensor probe list of the sensor hub; and

storing, by the sensor probe, the communication ID.

In a possible implementation, the method further includes:

sending, by the sensor probe, a registration ID of the sensor probe to a sensor hub; and

receiving, by the sensor probe, a communication ID from the sensor hub, where the communication ID is assigned for the sensor probe in a case where the registration ID of the sensor probe is already recorded in a sensor probe list of the sensor hub.

In a possible implementation, the method includes:

in response to receiving a second wakeup request from the sensor hub, sending, by the sensor probe, a second wakeup response to the sensor hub, where the second wakeup request includes the communication ID;

forming, by the sensor probe, the sensor data into a sensor data packet based on the first communication protocol; and

sending, by the sensor probe, the sensor data packet to the sensor hub.

In a possible implementation, the method includes:

in response to being triggered to wake up by an sensor interrupt or a timer, sending, by the sensor probe, a third wakeup request to the sensor hub;

in response to receiving a third wakeup response from the sensor hub, forming, by the sensor probe, the sensor data into a sensor data packet based on the first communication protocol; and

sending, by the sensor probe, the sensor data packet to the sensor hub.

In a possible implementation, the method further includes:

receiving user configuration information of the sensor probe from the sensor hub; and

performing configuration according to the user configuration information of the sensor probe.

In a possible implementation, the method further includes:

receiving, by the sensor probe, a triggering signal sent by the sensor hub; and

on receiving the triggering signal from the sensor hub, sending, by the sensor probe, the first communication protocol data to the sensor hub based on the first communication protocol.

In a possible implementation, the method further includes:

receiving, by the sensor probe, a stopping signal sent by the sensor hub; and on receiving the triggering signal from the sensor hub, not to send the first communication protocol data to the sensor hub based on the first communication protocol.

The present disclosure also provides a computer readable storage medium, storing thereon computer executable instructions which, when being executed by a processor, implement the data transmission method as described in the embodiments of the present disclosure.

In one or more examples, the functions described may be implemented in hardware, software, firmware, or any combination thereof. For example, the functions may be implemented by one or more processors, such as one or more application specific integrated circuits (ASICs) , field programmable logic arrays (FPGAs) , or other equivalent integrated or discrete logic circuitry. Accordingly, the term “processor, ” as used herein may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein. In addition, the techniques could be fully implemented in one or more circuits or logic elements.

In the claims, the word “including” does not exclude other elements or steps, and the indefinite article “a” or “an” does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate, preclude or suggest that a combination of these measures cannot be used to advantage.

The foregoing detailed description has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the subject matter claimed herein to the precise form (s) disclosed. Many modifications and variations are possible in light of the above teachings. The described embodiments were chosen in order to best explain the principles of the disclosed technology and its practical application to thereby enable others skilled in the art to best utilize the technology in various embodiments and with various modifications as are suited to the particular use contemplated. Those embodiments with various modifications are within the range and scope of the following claims.

Claims

A sensor hub, comprising:

at least one processor; and

a memory communicatively connected with the at least one processor; wherein,

the sensor hub is connectable to at least one sensor probe;

the memory stores instructions executable by the at least one processor, and the instructions, when executed by the at least one processor, cause the at least one processor to:

receive first communication protocol data from the at least one sensor probe based on the first communication protocol.
The sensor hub according to claim 1, wherein the instructions cause the at least one processor to maintain a sensor probe list, and communicate with the respective sensor probe based on the sensor probe list;

wherein the sensor probe list comprises a mapping relationship between a communication identifier ID of the respective sensor probe, and registration information of the respective sensor probe.
The sensor hub according to claim 2, wherein the registration information of the respective sensor probe comprises a registration ID of the respective sensor probe, the at least one sensor probe comprises a first sensor probe, and the instructions cause the at least one processor to:

receive a registration ID of the first sensor probe from the first sensor probe;

determine whether the registration ID of the first sensor probe is recorded in the sensor probe list; and

in response to determining that the registration ID of the first sensor probe is not recorded in the sensor probe list, assign a communication ID for the first sensor probe.
The sensor hub according to claim 3, wherein the instructions cause the at least one processor to:

send the communication ID to the first sensor probe to instruct the first sensor probe to store the communication ID; or

determine a communication ID associated with the registration ID of the first sensor probe in response to determining that the registration ID of the first sensor probe is already recorded in the sensor probe list, and send the communication ID to the first sensor probe.
The sensor hub according to claim 3, wherein registration information of the first sensor probe further comprises user configuration information of the first sensor probe, and the instructions cause the at least one processor to:

send the user configuration information of the first sensor probe to the first sensor probe to instruct the first sensor probe to perform configuration according to the user configuration information of the first sensor probe.
The sensor hub according to claim 5, wherein the instructions cause the at least one processor to:

acquire the user configuration information of the first sensor probe; and

add the user configuration information of the first sensor probe in the sensor probe list.
The sensor hub according to claim 5, wherein the instructions cause the at least one processor to:

when the sensor hub receives the registration ID of the first sensor probe, determine whether the sensor probe list comprises user configuration information associated with a communication ID of the first sensor probe; and

in response to determining that the sensor probe list comprises user configuration information associated with the communication ID of the first sensor probe, send the user configuration information of the first sensor probe to the first sensor probe.
The sensor hub according to claim 2, wherein the at least one sensor probe comprises at least two sensor probes, the instructions cause the at least one processor to:

determine a target sensor probe out of the at least two sensor probes; and

send a triggering signal to the target sensor probe to enable the target sensor probe to send the first communication protocol data to the sensor hub based on the first communication protocol, and send a stopping signal to the sensor probe other than the target sensor probe to disable the sensor probe other than the target sensor probe from sending the first communication protocol data to the sensor hub based on the first communication protocol.
The sensor hub according to claim 8, wherein the instructions cause the at least one processor to:

send a wakeup request to the target sensor probe, wherein the wakeup request comprises a communication ID of the target sensor probe;

receive a wakeup response from the target sensor probe; and

receive the first communication protocol data from the target sensor probe.
The sensor hub according to claim 2, wherein the at least one sensor probe comprises a second sensor probe, and the instructions cause the at least one processor to:

in response to being triggered to wake up by a wakeup request from the second sensor probe, send a wakeup response to the second sensor probe; and

receive the first communication protocol data from the second sensor probe.
A data transmission method implemented by a sensor hub according to any one of claims 1 to 10, wherein the sensor hub is connectable to at least one sensor probe, the method comprises:

receiving, by the sensor hub, first communication protocol data sent by a respective sensor probe connected to the sensor hub based on a first communication protocol.
The method according to claim 11, wherein the method further comprises:

maintaining, by the sensor hub, a sensor probe list, and communicating, by the sensor hub, with the respective sensor probe based on the sensor probe list;

wherein the sensor probe list comprises a mapping relationship between a communication identifier ID of the respective sensor probe, and registration information of the respective sensor probe.
The method according to claim 12, wherein the registration information of the respective sensor probe comprises a registration ID of the respective sensor probe, the at least one sensor probe comprises a first sensor probe, the method further comprises:

receiving, by the sensor hub, a registration ID of the first sensor probe from the first sensor probe;

determining, by the sensor hub, whether the registration ID of the first sensor probe is recorded in the sensor probe list; and

in response to determining that the registration ID of the first sensor probe is not recorded in the sensor probe list, assigning, by the sensor hub, a communication ID for the first sensor probe.
The method according to claim 13, further comprising:

sending, by the sensor hub, the communication ID to the first sensor probe to instruct the first sensor probe to store the communication ID; or

determining, by the sensor hub, a communication ID associated with the registration ID of the first sensor probe in response to determining that the registration ID of the first sensor probe is already recorded in the sensor probe list, and sending, by the sensor hub, the communication ID to the first sensor probe.
The method according to claim 13, wherein registration information of the first sensor probe further comprises user configuration information of the first sensor probe, and the method further comprises:

sending, by the sensor hub, the user configuration information of the first sensor probe to the first sensor probe to instruct the first sensor probe to perform configuration according to the user configuration information of the first sensor probe.
The method according to claim 15, wherein the method further comprises:

when the sensor hub receives the registration ID of the first sensor probe, determining, by the sensor hub, whether the sensor probe list comprises user configuration information associated with a communication ID of the first sensor probe; and

in response to determining that the sensor probe list comprises user configuration information associated with the communication ID of the first sensor probe, sending, by the sensor hub, the user configuration information of the first sensor probe to the first sensor probe.
The method according to claim 12, wherein the at least one sensor probe comprises at least two sensor probes, the method further comprises:

determining, by the sensor hub, a target sensor probe out of the at least two sensor probes; and

sending, by the sensor hub, a triggering signal to the target sensor probe to enable the target sensor probe to send the first communication protocol data to the sensor hub based on the first communication protocol, and sending, by the sensor hub, a stopping signal to the sensor probe other than the target sensor probe to disable the sensor probe other than the target sensor probe from sending the first communication protocol data to the sensor hub based on the first communication protocol.
The method according to claim 17, further comprising:

sending, by the sensor hub, a wakeup request to the target sensor probe, wherein the wakeup request comprises a communication ID of the target sensor probe;

receiving, by the sensor hub, a wakeup response from the target sensor probe; and

receiving, by the sensor hub, the first communication protocol data from the target sensor probe.
The method according to claim 12, wherein the at least one sensor probe comprises a second sensor probe, the method further comprises:

in response to being triggered to wake up by a wakeup request from the second sensor probe, sending, by the sensor hub, a wakeup response to the second sensor probe; and

receiving, by the sensor hub, the first communication protocol data from the second sensor probe.
A sensing system, comprising: a sensor hub according to any one of claims 1-10 and at least one sensor probe connectable to the sensor hub, wherein,

a respective sensor probe is configured to:

acquire sensor data;

convert the sensor data into first communication protocol data, wherein the sensor data and the first communication protocol data correspond to different communication protocols; and

send the first communication protocol data to the sensor hub based on a first communication protocol.
The sensing system according to claim 20, wherein the sensor hub is connectable to a plurality of sensor probes of at least one type;

wherein a respective type of sensor probe is connectable to at least one sensor corresponding to a fixed communication protocol;

wherein a communication protocol corresponding to a sensor that is connectable to one type of sensor probe is different from a communication protocol corresponding to a sensor that is connectable a different one type of sensor probe.
The sensing system according to claim 20, wherein the at least one sensor probe comprises a first sensor probe, the first sensor probe is connectable to at least one sensor and is configured to acquire the sensor data through the at least one sensor;

wherein sensor data of the at least one sensor is based on a second communication protocol.
The sensing system according to claim 20, wherein the at least one sensor probe comprises a second sensor probe, the second sensor probe is connectable to at least two sensors and is configured to acquire the sensor data through the at least two sensors, wherein sensor data of the at least two sensors is based on at least a third communication protocol and a fourth communication protocol;

the second sensor probe is configured to, before converting sensor data of a respective sensor which is connected with the second sensor probe into the first communication protocol data, determine a communication protocol corresponding to the sensor data of the respective sensor which is connected with the second sensor probe.
The sensing system according to claim 20, wherein the sensor hub is configured to maintain a sensor probe list, and communicate with the respective sensor probe based on the sensor probe list;

wherein the sensor probe list comprises a mapping relationship between a communication identifier ID of the respective sensor probe, and registration information of the respective sensor probe.
The sensing system according to claim 24, wherein the registration information of the respective sensor probe comprises a registration ID of the respective sensor probe, and the sensor hub is configured to:

receive the registration ID of the respective sensor probe from the respective sensor probe;

determine whether the registration ID of the respective sensor probe is recorded in the sensor probe list; and

in response to determining that the registration ID of the respective sensor probe is not recorded in the sensor probe list, assign a communication ID for the respective sensor probe.
The sensing system according to claim 25, wherein the sensor hub is further configured to:

send a respective communication ID to the respective sensor probe to instruct the respective sensor probe to store the respective communication ID; or

determine a respective communication ID associated with the registration ID of the respective sensor probe in response to determining that the registration ID of the respective sensor probe is already recorded in the sensor probe list, and send the respective communication ID to the respective sensor probe.
The sensing system according to claim 25, wherein the respective sensor probe gets power supply from the sensor hub when the respective sensor probe is plugged into one of at least one port of the sensor hub, and the respective sensor probe is configured to:

run bootup codes when the respective sensor probe gets power supply from the sensor hub;

send a first wakeup request to the sensor hub; and

in response to receiving a first wakeup response from the sensor hub, send the registration ID of the respective sensor probe to the sensor hub.
The sensing system according to claim 25, wherein the registration information of the respective sensor probe further comprises user configuration information of the respective sensor probe, and the sensor hub is further configured to:

send the user configuration information of the respective sensor probe to the respective sensor probe to instruct the respective sensor probe to perform configuration according to the user configuration information of the respective sensor probe.
The sensing system according to claim 28, wherein the sensor hub is further configured to:

acquire the user configuration information of the respective sensor probe; and

add the user configuration information of the respective sensor probe in the sensor probe list.
The sensing system according to claim 28, wherein the sensor hub is specifically configured to:

when the sensor hub receives the registration ID of the respective sensor probe, determine whether the sensor probe list comprises user configuration information associated with a communication ID of the respective sensor probe; and

in response to determining that the sensor probe list comprises user configuration information associated with the communication ID of the respective sensor probe, send the user configuration information of the respective sensor probe to the first sensor probe.
The sensing system according to claim 24, wherein the at least one sensor probe comprises at least two sensor probes, the sensor hub is configured to:

determine a target sensor probe out of the at least two sensor probes; and

send a triggering signal to the target sensor probe to enable the target sensor probe to send the first communication protocol data to the sensor hub based on the first communication protocol, and send a stopping signal to the sensor probe other than the target sensor probe to disable the sensor probe other than the target sensor probe from sending the first communication protocol data to the sensor hub based on the first communication protocol.
The sensing system according to claim 31, wherein the sensor hub is further configured to:

send a second wakeup request to the target sensor probe, wherein the second wakeup request comprises a communication ID of the target sensor probe;

receive a second wakeup response from the target sensor probe; and

receive the first communication protocol data from the target sensor probe.
The sensing system according to claim 24, wherein the at least one sensor probe comprises a third sensor probe, and the sensor hub is configured to:

in response to being triggered to wake up by a third wakeup request from the third sensor probe, send a third wakeup response to the third sensor probe; and

receive the first communication protocol data from the third sensor probe.
A data transmission method, comprising:

acquiring, by a sensor probe, sensor data through at least one sensor;

converting, by the sensor probe, the sensor data into first communication protocol data, wherein the sensor data of the at least one sensor and the first communication protocol data correspond to different communication protocols; and

sending, by the sensor probe, the first communication protocol data to a sensor hub based on a first communication protocol.
The method according to claim 34, wherein sensor data of a respective sensor corresponds to a second communication protocol;

the converting, by the sensor probe, the sensor data into the first communication protocol data, comprises:

converting, by the sensor probe, the sensor data corresponding to the second communication protocol into the first communication protocol data.
The method according to claim 34, wherein sensor data of a respective sensor corresponds to one of at least a third communication protocol and a fourth communication protocol;

before the converting, by the sensor probe, the sensor data into the first communication protocol data, the method further comprises:

determining, by the sensor probe, a communication protocol corresponding to the sensor data of the respective sensor;

the converting, by the sensor probe, the sensor data into the first communication protocol data, comprises:

converting, by the sensor probe, the sensor data corresponding to the determined communication protocol into the first communication protocol data.
The method according to claim 34, wherein the sensor hub is connected with at least two sensor probes, the method further comprises:

determining, by the sensor hub, a target sensor probe out of the at least two sensor probes; and

sending, by the sensor hub, a triggering signal to the target sensor probe to enable the target sensor probe to send the first communication protocol data to the sensor hub based on the first communication protocol, and sending, by the sensor hub, a stopping signal to the sensor probe other than the target sensor probe to disable the sensor probe other than the target sensor probe from sending the first communication protocol data to the sensor hub based on the first communication protocol.
The method according to claim 37, before the sending, by the sensor probe, the first communication protocol data to a sensor hub based on a first communication protocol, further comprising:

receiving, by the sensor probe, a wakeup request from the sensor hub, wherein the wakeup request comprises a communication ID which is assigned for the sensor probe by the sensor hub;

sending, by the sensor probe, a wakeup response to the sensor hub.
The method according to claim 37, before the sending, by the sensor probe, the first communication protocol data to a sensor hub based on a first communication protocol, further comprising:

sending, by the sensor probe, a wakeup request to the sensor hub; and

receiving, by the sensor probe, a wakeup response from the sensor hub.