WO2022165765A1 - Message exchange method and apparatus in internet of things, and computer device and storage medium - Google Patents

Abstract

The present application belongs to the technical field of the Internet of Things. Disclosed are a message exchange method and apparatus in the Internet of Things, and a computer device and a storage medium. The method comprises: receiving a first model message sent by a second device, wherein the first model message includes an attribute type, and the attribute type is used to indicate a functional attribute of a target application function. According to the solution, interaction modes of multiple different application functions are supported by means of the same type of model message, and there is no need to provide an individual BLE mesh model for each application function in an Internet of Things device, thereby reducing the complexity of model message exchange of devices in a BLE mesh and improving message exchange efficiency and resource utilization in the BLE mesh.

Description

Message interaction method, device, computer equipment and storage medium in the Internet of Things technical field

The present application relates to the technical field of the Internet of Things, and in particular, to a message interaction method, apparatus, computer equipment and storage medium in the Internet of Things.

Background technique

In the Internet of Things (IOT), to achieve remote management of server devices through clients, it is necessary to instantiate models of client devices and server devices.

In the Bluetooth Low Energy Mesh (BLE Mesh) based on Bluetooth Low Energy, the Bluetooth SIG defines a BLE Mesh model for IoT devices, in which each application function and feature corresponds to a BLE Mesh model. Different IoT devices can implement different BLE Mesh models, and interact with other IoT devices based on the BLE Mesh model to provide different application functions and features.

However, for IoT devices with multiple application functions and features, multiple BLE Mesh models need to be implemented in BLE Mesh, which leads to high complexity of message interaction between IoT devices and affects the efficiency of message interaction in BLE Mesh. .

SUMMARY OF THE INVENTION

Embodiments of the present application provide a message interaction method, apparatus, computer device, and storage medium in the Internet of Things. The technical solution is as follows:

On the one hand, an embodiment of the present application provides a message interaction method in the Internet of Things, the method is executed by a first device in the Internet of Things, and the method includes:

receiving the first model message sent by the second device;

Wherein, the first model message includes an attribute type, and the attribute type is used to indicate the function attribute of the target application function.

On the other hand, an embodiment of the present application provides a message interaction method in the Internet of Things, the method is executed by a second device in the Internet of Things, and the method includes:

sending a first model message to the first device;

Wherein, the first model message includes an attribute type, and the attribute type is used to indicate the function attribute of the target application function.

On the other hand, an embodiment of the present application provides a message interaction device in the Internet of Things, the device is used in a first device in the Internet of Things, and the device includes:

a first message receiving module, configured to receive the first model message sent by the second device;

Wherein, the first model message includes an attribute type, and the attribute type is used to indicate the function attribute of the target application function.

On the other hand, an embodiment of the present application provides a message interaction device in the Internet of Things, the device is used in a second device in the Internet of Things, and the device includes:

a first message sending module, configured to send a first model message to the first device;

Wherein, the first model message includes an attribute type, and the attribute type is used to indicate the function attribute of the target application function.

In another aspect, an embodiment of the present application provides a computer device, the computer device includes a processor, a memory, and a transceiver, the memory stores a computer program, and the computer program is configured to be executed by the processor to Implement the above message interaction method in the Internet of Things.

In another aspect, an embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored in the storage medium, and the computer program is loaded and executed by a processor to implement the above-mentioned message interaction method in the Internet of Things.

In another aspect, a computer program product or computer program is provided, the computer program product or computer program comprising computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the above-mentioned message interaction method in the Internet of Things.

The technical solutions provided in the embodiments of the present application can bring the following beneficial effects:

The Internet of Things devices exchange information through model messages that support one or more application functions. The model message carries the attribute type to indicate the application function corresponding to the current message. That is, for a variety of different application functions, send The end and the receiving end only need to be accurately distinguished by the attribute type in the model message, so that the same model message can support a variety of different application functions. An application function sets a BLE Mesh model separately, thereby reducing the complexity of model message interaction of devices in BLE Mesh, thereby improving the efficiency and resource utilization of message interaction in BLE Mesh.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present application more clearly, the following briefly introduces the drawings that are used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative effort.

1 is a schematic diagram of a network architecture of the Internet of Things provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of a message interaction involved in the embodiment shown in FIG. 1;

3 is a flowchart of a message interaction method in the Internet of Things provided by an embodiment of the present application;

4 is a message interaction architecture diagram in the Internet of Things provided by an embodiment of the present application;

5 is a flowchart of a message interaction method in the Internet of Things provided by an embodiment of the present application;

6 is a message interaction architecture diagram in the Internet of Things provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of an attribute reading process involved in the embodiment shown in FIG. 6;

8 is a schematic diagram of an interaction flow for updating attribute information involved in the embodiment shown in FIG. 6;

9 is a schematic diagram of an interaction flow of an attribute status notification message involved in the embodiment shown in FIG. 6;

10 is a block diagram of a file generation device in the Internet of Things provided by an embodiment of the present application;

11 is a block diagram of a file generation device in the Internet of Things provided by an embodiment of the present application;

FIG. 12 is a schematic structural diagram of a computer device provided by an embodiment of the present application.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

The network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. The evolution of new business scenarios and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

Please refer to FIG. 1 , which shows a schematic diagram of a network architecture of the Internet of Things provided by an embodiment of the present application. The network architecture of the Internet of Things may include: a server device 110 and a client device 120;

The server device 110 may be a device for providing Internet of Things functional services.

For example, the server device 110 may be a smart home device, for example, a smart lamp, a smart TV, a smart air conditioner, a smart refrigerator, a smart microwave oven, a smart rice cooker, a cleaning robot, and the like.

Alternatively, the server device 110 may be an industrial production device such as a lathe, an industrial robot, a solar panel, a wind turbine, and the like.

Alternatively, the server device 110 may be a commercial service device, such as a vending machine or the like.

Alternatively, the server device 110 may be an intelligent monitoring device, such as a monitoring camera, an infrared sensor, a sound sensor, a temperature sensor, and the like.

The client device 120 is a device controlled or managed by the server device 110. For example, the management device 120 may be a mobile management terminal such as a smart phone and a tablet computer, or the management device 120 may also be a personal computer, such as a desktop computer, a portable Computers, personal workstations, etc.

The server device 110 and the client device 120 can be connected through BLE Mesh networking.

Optionally, the network architecture of the Internet of Things further includes a cloud platform 130 .

The cloud platform 130 is a cloud service platform deployed on the network side. For example, the cloud platform 130 may be a cloud service platform implemented based on a single or multiple servers.

The cloud platform 130 may be connected to the server device 110 and the client device 120 through a wired or wireless network, respectively.

The BLE Mesh model includes a client model (ie, Server Model, hereinafter referred to as client) and a server model (ie, Client Model, hereinafter referred to as server). The client and server interact by sending BLE Mesh messages. For example, BLE Mesh defines the switch model, the lighting as the server implements the On/Off Server Model, and the devices that control the lighting (such as mobile APPs, lighting switches, etc.) implement the On/Off Client Model as the client.

Client model: Define the BLE Mesh model messages that can be sent or received by devices implementing this client model. The client obtains the status of the server or operates the functions of the server by sending the corresponding model message. For example, the client model (On/Off Client Model) that supports the switch function sends a GET On/Off Server Model message to the server model (On/Off Server Model) that supports the switch function to get the status of the switch, the On/Off Client Model Send the SET On/Off Server Model message to the On/Off Server Model to set the switch on or off.

Server model: Define the state and device functions of the device implementing this server model, as well as the BLE Mesh model messages that can be sent or received by the device implementing this server model. For example, when the switch state changes, the On/Off Server Model sends an On/Off Server Model STATUS message to the On/Off Client Model to notify the switch state change.

Please refer to FIG. 2 , which shows a schematic diagram of a message interaction involved in the implementation of the present application. Among them, Figure 2 is an example of the interaction of On/Off model messages between the switch that implements the On/Off Client Model and the lamp that implements the On/Off Server Model.

Table 1 shows the message structure of the BLE Mesh model in the above scheme. The message of each BLE Mesh model consists of opcodes and application parameters. The opcode size is 1, 2 or 3 bytes, and the application parameters cannot exceed 379 words. Festival.

Table 1

field name	size (8-bit bytes)	Notes
opcode	1-3	opcode to indicate the type of model message
Ranges	0-379	Application parameters

The Bluetooth SIG currently defines dozens of BLE Mesh models, each of which defines different message types. Table 2 shows the model message types defined by the On/Off Server Model.

Table 2

In the above solutions, the BLE Mesh standard defines different BLE Mesh client models and server models for different application functions and characteristics of IoT devices. IoT devices need to implement corresponding models according to their functional characteristics, and each model defines and implements this model. The state of the device and device capabilities, and the model messages this model supports to send or receive. To support different application functions, IoT devices need to implement different BLE Mesh models and model messages dedicated to different models. When an IoT device implements multiple models and dedicated messages for different models, it undoubtedly increases the complexity of device processing. It also increases the overhead of additional computing and storage resources, especially for resource-constrained IoT devices, the above problems are particularly prominent, and the technical feasibility of implementation is low.

Please refer to FIG. 3 , which shows a flowchart of a message interaction method in the Internet of Things provided by an embodiment of the present application, and the method can be executed interactively by a first device and a second device. For example, the first device and the second device may be the server device 110 and the client device 120 in the system shown in FIG. 1 above. The method may include the following steps:

Step 301, the first device and the second device are networked through BLE Mesh.

Step 302, the second device sends a first model message to the first device; correspondingly, the first device receives the first model message sent by the second device. Wherein, the above-mentioned first model message includes an attribute type, and the attribute type is used to indicate the function attribute of the target application function.

In a possible implementation manner, the second device sends a first model message to the first device based on the BLE Mesh model, and correspondingly, the first device receives the first model message sent by the second device based on the BLE Mesh model.

The above target application function is any one of at least one application function supported by the BLE Mesh model.

To sum up, in the solutions shown in the embodiments of the present application, IoT devices exchange information through model messages that support one or more application functions, and attribute types are carried in the model messages to indicate the application functions corresponding to the current message. , that is to say, for a variety of different application functions, the sender and the receiver can accurately distinguish only by the attribute type in the model message, so that the same model message can support a variety of different application functions. Correspondingly, it is not necessary to set a BLE Mesh model separately for each application function in the IoT device, thereby reducing the complexity of the model message interaction of the devices in the BLE Mesh, thereby improving the message interaction in the BLE Mesh. efficiency and resource utilization.

In addition, the solutions shown in the embodiments of this application perform information exchange through model messages that support one or more different application functions, which reduces the overhead of computing and storage resources of IoT devices, thereby improving the message flow in BLE Mesh. Interaction resource utilization.

Through the solution shown in Figure 3 above, for various application functions supported by IoT devices in BLE Mesh, it is only necessary to build a general BLE Mesh model in IoT devices, which can realize the message interaction of various application functions. . For example, please refer to FIG. 4 , which shows a message interaction architecture diagram in the Internet of Things provided by an embodiment of the present application. As shown in FIG. 4 , the client device 41 and the server device 42 are respectively constructed with BLE Mesh models, and the BLE Mesh models support a variety of application functions (shown as 3 in FIG. 4 ), each application function has a corresponding property type. When a message is exchanged between the client device 41 and the server device 42, the model message sent by the sending side contains the attribute type corresponding to a certain application function. After the receiving side receives the model message, the model can be judged by the attribute type. Which application function the message corresponds to, and based on the type attribute, perform subsequent operations on the corresponding application function.

That is to say, the above technical solution of this application proposes a method for message interaction between BLE Mesh devices. By defining an extended BLE Mesh model, the model provides a general model message type, so that even if the IoT device supports different application functions , and there is no need to implement different models and model message types specific to different models.

Please refer to FIG. 5 , which shows a flowchart of a message interaction method in the Internet of Things provided by an embodiment of the present application. The method can be executed interactively by a first device and a second device. They are connected through BLE Mesh. For example, the first device and the second device may be the server device 110 and the client device 120 in the system shown in FIG. 1 above. The method may include the following steps:

Step 501, the first device and the second device are networked through BLE Mesh.

In this embodiment of the present application, the first device and the second device are respectively a server device and a client device, and both the server device and the client device support the BLE function, and the server device and the client device are pre-connected through BLE Mesh Network.

Step 502, the second device sends a first model message to the first device based on the BLE Mesh model; correspondingly, the first device receives the first model message sent by the second device based on the BLE Mesh model.

Wherein, the above-mentioned first model message includes an attribute type, and the attribute type is used to indicate the function attribute of the target application function; the target application function is any one of at least one application function supported by the BLE Mesh model.

In the embodiment of the present application, the BLE Mesh model can be divided into a server model and a client model, and the server model and the client model can be respectively set in the first device and the second device.

Among them, the BLE Mesh model can support a single application function or indicate multiple application functions.

For example, when the server devices in the first device and the second device are lighting devices and support the lighting switch function, the above BLE Mesh model can support the lighting switch function, and the BLE Mesh model is provided with lighting corresponding to the lighting switch function The property type of the switch.

For another example, when the server devices in the first device and the second device are lighting devices and support the lighting switch function, lighting mode adjustment function, and brightness adjustment function at the same time, the above BLE Mesh model can simultaneously support the lighting switch function, lighting Mode adjustment function and brightness adjustment function, and the BLE Mesh model corresponding to the above three functions are respectively set with the attribute type of the lighting switch, the attribute type of the lighting mode, and the attribute type of the brightness.

In a possible implementation manner, the first model message further includes a first operation code, where the first operation code is used to indicate a message type of the first model message.

In this embodiment of the present application, in order to enable the first device to clearly know the subsequent processing method corresponding to the first model message, the first model message further includes a first operation code, and the first device receives the first model message Afterwards, how to perform subsequent processing based on the first model message may be determined through the first operation code in the first model message.

In a possible implementation manner, the message type of the first model message includes: read property message, update property message or property state notification message;

The read attribute message is used to read data related to the attribute type from the first device;

The update attribute message is used to instruct the first device to update the data related to the attribute type;

The attribute status notification message is used to notify the first device of data related to the attribute type.

The message type of the first model message indicated by the first operation code may be any one of a read attribute message, an attribute update message, or an attribute status notification message.

Among them, the read attribute message is usually used for the client device to view the current parameter/status of a function in the server device. For example, the user checks the current ON state of the desk lamp (server device) in the mobile phone (client device). In the scenario of /brightness, the mobile phone can send a read attribute message to the desk lamp to read the current ON state/brightness value of the desk lamp.

The above update attribute message is usually used in the scenario where the client device controls the server device to change the current parameter/state of a certain function. For example, in the scenario where the user needs to adjust the brightness of the desk lamp through the mobile phone, the mobile phone can send an update attribute message to the desk lamp to Instruct the desk lamp to adjust the brightness.

The above property status notification message is usually used in the scenario where the server device actively reports the current parameter/status of a certain function to the client device. For example, after the user adjusts the brightness of the desk lamp through the mobile phone, the desk lamp can return the property status notification message to the mobile phone. to notify the phone of the adjusted brightness.

In a possible implementation manner, the first model message further includes a transaction identifier, where the transaction identifier is used to indicate that the corresponding message is a retransmitted message or a new message.

In this embodiment of the present application, in order to improve the successful reception of the message by the receiving end, a model message can be sent multiple times. Correspondingly, in order to enable the receiving end to accurately distinguish which messages are retransmitted messages and which messages are newly transmitted messages , when the second device sends the first model message, it may carry a transaction indication in the first model message to indicate whether the current model message is a retransmitted message or a newly transmitted message, and the first device performs processing based on the transaction identifier indication For example, when the transaction identifier indicates that the first model message is a retransmission message, the first device may combine the first model message with a previously received message.

In a possible implementation manner, the first model message further includes an attribute parameter, where the attribute parameter is used to indicate a parameter of the attribute type, or the attribute parameter is used to indicate an attribute value of the attribute type.

In this embodiment of the present application, when the first model message needs to indicate a parameter/attribute value (eg, a state value) corresponding to the attribute type, the first model message may also carry the attribute parameter corresponding to the attribute type.

In a possible implementation manner, when the message type of the first model message is an attribute update message or an attribute status notification message, the first model message further includes the attribute parameter.

In this embodiment of the present application, when the message type of the first model message is an attribute update message or an attribute status notification message, the parameter/attribute value corresponding to the attribute type needs to be indicated.

For example, in the scenario where the user needs to adjust the brightness of the desk lamp through the mobile phone, the mobile phone can send an update attribute message to the desk lamp. In order to enable the desk lamp to be adjusted to the brightness required by the user, the update attribute message also includes a target brightness for indicating adjustment or adjustment. Difference property parameter.

For another example, the user checks the current brightness of the table lamp on the mobile phone, or, after the user adjusts the brightness of the table lamp through the mobile phone, the table lamp can send a property status notification message to the mobile phone, so that the current brightness of the table lamp can be accurately displayed in the mobile phone interface. The attribute parameter indicating the current brightness needs to be carried in the attribute status notification message.

Step 503, the first device performs a related operation corresponding to the attribute type according to the first model message.

In this embodiment of the present application, after receiving the first model message, the first device may determine a corresponding application function according to the attribute type, and perform operations related to the first model message according to the determined application function.

For example, when the first model message is a read attribute message, the first device queries the attribute parameter corresponding to the application function to be read according to the attribute type in the read attribute message, and the queried attribute parameter is carried in the attribute status notification message back to the second device.

For another example, when the first model message is an attribute update message, the first device determines the application function to be updated according to the attribute type in the attribute update message, and updates the attribute parameter corresponding to the determined application function.

In a possible implementation manner, when the message type of the first model message is an attribute status notification message, a second model message is sent to the second device; the second model message includes a second operation code; the first model message The second operation code is used to indicate that the message type of the second model message is an attribute status notification confirmation message.

Wherein, when the first model message is an attribute state notification message, the first device may feed back to the second device whether the attribute state notification message is received, and at this time, the first device may send an attribute state notification confirmation message to the second device.

For example, the following Table 3 is a message structure of a BLE Mesh model proposed by this application, including: an operation code, a transaction identifier, an attribute type, and an attribute parameter.

Opcode: used to indicate the type of BLE Mesh message, including read attribute message, update attribute message, attribute status notification message and attribute status notification confirmation message;

Transaction ID (TID): The message ID is used to indicate whether the message is a retransmitted message or a new message. The transaction ID of the retransmitted message and the recently sent message is the same, and the transaction ID of the new message and the recently sent message is different. with the message incrementing;

Attribute type (AttrType): indicates the type of attribute, such as switch attribute, target temperature attribute, brightness attribute, etc.;

Attribute parameter (AttrParameter): The parameter representing the attribute type or the value of the attribute type, for example, the value of the switch attribute is "on" or "off", the value of the target temperature attribute is 25, and the value of the brightness attribute is 100.

table 3

field	size	Notes
Opcode	1-3	Opcode to indicate the type of BLE Mesh message
TID	1	Transaction ID, i.e. message ID, used to indicate retransmission or new message
AttrType	2	property type, indicating the type of property
AttrParameter	n	Attribute parameter, representing the parameter of the attribute type or the value of the attribute type

In a possible implementation solution, the attribute type and attribute parameter fields in the above fields are optional. For example, the read attribute message does not need to indicate the attribute parameter, and the update attribute message can indicate the attribute type and attribute parameter that need to be updated.

In a possible implementation manner, the second model message includes a transaction identifier, where the transaction identifier is used to indicate that the corresponding message is a retransmitted message or a new message.

Similar to the first model message, in this embodiment of the present application, the second model message may also carry a transaction identifier.

In a possible implementation manner, the attribute type is included in the second model message.

In this embodiment of the present application, similar to the first model message, the attribute status notification confirmation message may also include the above attribute type, so that the second device can judge by the attribute type that the attribute status notification confirmation message is a confirmation corresponding to the first model message feedback.

In another possible implementation manner, the attribute status notification confirmation message may not include the above attribute type.

In a possible implementation manner, the second model message further includes an attribute parameter, where the attribute parameter is used to indicate a parameter of the attribute type, or the attribute parameter is used to indicate an attribute value of the attribute type.

In this embodiment of the present application, when the attribute status notification confirmation message includes an attribute type, the attribute status notification confirmation message may also include an attribute parameter, so that the second device can determine whether the first device has correctly received the first device through the attribute parameter. Model message.

In a possible implementation manner, when the message type of the first model message is an attribute status notification message, and a confirmation indication for indicating feedback of an attribute status notification confirmation message is received, the second device is sent to the second device. model message;

or,

The second model message is sent to the second device when the message type of the first model message is an attribute state notification message, and no confirmation indication is received for indicating whether to feed back an attribute state notification confirmation message.

Correspondingly, the above-mentioned second device may send a confirmation indication to the first device.

The confirmation indication may be sent by the second device to the first device through an independent message, or the confirmation indication may also be carried in the attribute status notification message.

In this embodiment of the present application, when a second device (such as a server device) sends an attribute status notification message to a first device (such as a client device), it may indicate whether confirmation from the client device is required, and if it indicates that the attribute status notification message requires confirmation , or, without an instruction, the client device may send an attribute status notification confirmation message, and if the instruction does not require client confirmation, the client device may not send an attribute status notification confirmation message, thereby reducing the number of message sending and saving communication resources.

Alternatively, if the second device indicates that the property status notification message requires confirmation, the client device may send the property status notification confirmation message, and if the indication does not require client confirmation, or, if no indication is made, the client device may not send the property status notification Confirmation message.

To sum up, in the solutions shown in the embodiments of the present application, IoT devices exchange information through model messages that support one or more application functions, and attribute types are carried in the model messages to indicate the application functions corresponding to the current message. , that is to say, for a variety of different application functions, the sender and the receiver can accurately distinguish only by the attribute type in the model message, so that the same model message can support a variety of different application functions. Correspondingly, it is not necessary to set a BLE Mesh model separately for each application function in the IoT device, thereby reducing the complexity of the model message interaction of the devices in the BLE Mesh, thereby improving the message interaction in the BLE Mesh. efficiency and resource utilization.

In addition, the solutions shown in the embodiments of this application perform information exchange through model messages that support one or more different application functions, which reduces the overhead of computing and storage resources of IoT devices, thereby improving the message flow in BLE Mesh. Interaction resource utilization.

Taking the scenario shown in the above-mentioned FIG. 3 or FIG. 5 applied to a mobile phone (client device) to control and manage an air conditioner (server device) as an example, please refer to FIG. 6 , which shows an embodiment of the present application Provides a message interaction architecture diagram in the Internet of Things. As shown in Figure 6, the mobile phone 61 and the air conditioner 62 have BLE Mesh models built respectively, and the BLE Mesh model supports a variety of air conditioning functions (shown in Figure 6 are the three functions of switch function, temperature adjustment function, and wind adjustment function), Each application function has a corresponding attribute type (ie switch attribute, temperature attribute and wind attribute). When a message is exchanged between the mobile phone 61 and the air conditioner 62, the model message sent by the sending side includes the attribute type (such as a switch attribute) corresponding to a certain application function. After the receiving side receives the model message, the attribute type can be used to determine the The model message corresponds to the switch function, and based on the type attribute, the corresponding switch function performs subsequent operations such as turning on/off the air conditioner.

Please refer to FIG. 7 , which is a schematic diagram of an attribute reading process involved in an embodiment of the present application. Take the air conditioner attribute reading process as an example, the attribute reading process is as follows:

S71, the mobile phone sends a read attribute message to the air conditioner, and the read attribute message includes an operation code (indicating that the message type is a read attribute message), a transaction identifier, and an attribute type (for example, it can indicate a switch attribute, a temperature attribute, or a wind attribute) .

Taking the attribute type as the temperature attribute as an example, Table 4 is an example of the read attribute message.

Table 4

Opcode	TID	AttrType
0xD2A801	0x01	0x09F0
read attribute message	Transaction ID	The read attribute type, for example, 0x09F0 represents the current temperature attribute

S72, the air conditioner returns an attribute status notification message to the mobile phone, and the attribute status notification message includes an operation code (indicating that the message type is an attribute status notification message), a transaction identifier, an attribute type, and an attribute parameter (which can indicate the opening state corresponding to the attribute type) , temperature value or wind level).

Taking the attribute type as the temperature attribute as an example, Table 5 is an example of the attribute status notification message.

table 5

The transaction identifier of the above message may be the transaction identifier of the read attribute message, indicating that the message is a response message of the read attribute message.

Please refer to FIG. 8 , which is a schematic diagram of an interaction flow for updating attribute information involved in an embodiment of the present application. Taking the air conditioner attribute update process as an example, the update attribute information exchange process is as follows:

S81, the mobile phone sends an update attribute message to the air conditioner, and the update attribute message includes an operation code (indicating that the message type is an update attribute message), a transaction identifier, an attribute type (for example, it can indicate a switch attribute, a temperature attribute or a wind attribute), and an attribute Parameters (may indicate updated lighting status, temperature value or wind level).

Taking the attribute type as the temperature attribute as an example, Table 6 is an example of the update attribute message.

Table 6

S82, the air conditioner returns an attribute status notification message to the mobile phone, and the attribute status notification message includes an operation code (indicating that the message type is an attribute status notification message), a transaction identifier, an attribute type, and an attribute parameter (which can indicate the updated activation status, temperature value or wind level).

Taking the attribute type as the temperature attribute as an example, Table 7 is an example of the attribute status notification message.

Table 7

The transaction identifier of the above message may be the transaction identifier of the update attribute message, indicating that the message is a response message of the update attribute message.

Please refer to FIG. 9 , which is a schematic diagram of an interaction flow of an attribute status notification message involved in an embodiment of the present application. Take the air conditioner attribute status notification process as an example, the process is as follows:

S91 , the air conditioner sends an attribute status notification message to the mobile phone, where the attribute status notification message includes an operation code (indicating that the message type is an attribute status notification message), a transaction identifier, an attribute type, and an attribute parameter.

Taking the attribute type as the temperature attribute as an example, Table 8 is an example of the attribute status notification message.

Table 8

S92, the mobile phone sends an attribute status notification confirmation message to the air conditioner, where the attribute status notification confirmation message includes an operation code (indicating that the message type is an attribute status notification confirmation message) and a transaction identifier.

Taking the attribute type as the temperature attribute as an example, Table 9 is an example of the attribute status notification confirmation message.

Table 9

Opcode	TID
0xD2A804	0x01
Property Status Notification Confirmation Message	Transaction ID

The transaction identifier of the above message is the transaction identifier of the attribute status notification message, indicating that the message is a response message of the attribute status notification message.

The following are apparatus embodiments of the present application, which can be used to execute the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

Please refer to FIG. 10 , which shows a block diagram of a message interaction apparatus in the Internet of Things provided by an embodiment of the present application. The device is used in the first device in the Internet of Things. As shown in Figure 10, the apparatus may include:

a first message receiving module 1001, configured to receive a first model message sent by a second device;

Wherein, the first model message includes an attribute type, and the attribute type is used to indicate the function attribute of the target application function.

In a possible implementation manner, the first model message further includes a first opcode, where the first opcode is used to indicate a message type of the first model message.

In a possible implementation manner, the message type of the first model message includes: read property message, update property message or property state notification message;

The read attribute message is used to read data related to the attribute type from the first device;

The update attribute message is used to instruct the first device to update the data related to the attribute type;

The attribute status notification message is used to notify the first device of data related to the attribute type.

In a possible implementation manner, the first model message further includes a transaction identifier, where the transaction identifier is used to indicate that the corresponding message is a retransmitted message or a new message.

In a possible implementation manner, the first model message further includes an attribute parameter, where the attribute parameter is used to indicate a parameter of the attribute type, or the attribute parameter is used to indicate an attribute value of the attribute type.

In a possible implementation manner, when the message type of the first model message is an attribute update message or an attribute status notification message, the first model message further includes the attribute parameter.

In a possible implementation, the apparatus further includes:

a second message sending module, configured to send a second model message to the second device when the message type of the first model message is an attribute state notification message; the second model message includes a second operation code; The second operation code is used to indicate that the message type of the second model message is an attribute status notification confirmation message.

In a possible implementation manner, the second model message includes a transaction identifier, and the transaction identifier is used to indicate that the corresponding message is a retransmitted message or a new message.

In a possible implementation manner, the attribute type is included in the second model message.

In a possible implementation manner, the second model message further includes an attribute parameter, where the attribute parameter is used to indicate a parameter of the attribute type, or the attribute parameter is used to indicate an attribute value of the attribute type.

In a possible implementation manner, the second message sending module is configured to:

sending the second model message to the second device when the message type of the first model message is an attribute state notification message and a first confirmation indication for indicating feedback of an attribute state notification confirmation message is received;

or,

When the message type of the first model message is an attribute status notification message and a second confirmation indication for indicating whether to feed back an attribute status notification confirmation message is not received, the second model message is sent to the second device .

In a possible implementation manner, the first device and the second device are connected through BLE Mesh; the first message receiving module 1001 is configured to receive a message sent by the second device based on the BLE Mesh model the first model message.

In a possible implementation manner, the target application function is any one of at least one application function supported by the BLE Mesh model.

To sum up, in the solutions shown in the embodiments of the present application, IoT devices exchange information through model messages that support one or more application functions, and attribute types are carried in the model messages to indicate the application functions corresponding to the current message. , that is to say, for a variety of different application functions, the sender and the receiver can accurately distinguish only by the attribute type in the model message, so that the same model message can support a variety of different application functions. Correspondingly, it is not necessary to set a BLE Mesh model separately for each application function in the IoT device, thereby reducing the complexity of the model message interaction of the devices in the BLE Mesh, thereby improving the message interaction in the BLE Mesh. efficiency and resource utilization.

In addition, the solutions shown in the embodiments of this application perform information exchange through model messages that support one or more different application functions, which reduces the overhead of computing and storage resources of IoT devices, thereby improving the message flow in BLE Mesh. Interaction resource utilization.

Please refer to FIG. 11 , which shows a block diagram of a message interaction apparatus in the Internet of Things provided by an embodiment of the present application. The device is used in a second device in the Internet of Things. As shown in Figure 11, the apparatus may include:

a first message sending module 1101, configured to send a first model message to a first device;

Wherein, the first model message includes an attribute type, and the attribute type is used to indicate the function attribute of the target application function.

In a possible implementation manner, the first model message further includes a first opcode, where the first opcode is used to indicate a message type of the first model message.

In a possible implementation manner, the message type of the first model message includes: read property message, update property message or property state notification message;

The read attribute message is used to read data related to the attribute type from the first device;

The update attribute message is used to instruct the first device to update the data related to the attribute type;

The attribute status notification message is used to notify the first device of data related to the attribute type.

In a possible implementation manner, the first model message further includes a transaction identifier, where the transaction identifier is used to indicate that the corresponding message is a retransmitted message or a new message.

In a possible implementation manner, the first model message further includes an attribute parameter, where the attribute parameter is used to indicate a parameter of the attribute type, or the attribute parameter is used to indicate an attribute value of the attribute type.

In a possible implementation manner, when the message type of the first model message is an attribute update message or an attribute status notification message, the first model message further includes the attribute parameter.

In a possible implementation, the apparatus further includes:

A second message receiving module, configured to receive a second model message sent by the second device when the message type of the first model message is an attribute state notification message; the second model message includes a second operation code ; The second operation code is used to indicate that the message type of the second model message is an attribute status notification confirmation message.

In a possible implementation manner, the second model message includes a transaction identifier, and the transaction identifier is used to indicate that the corresponding message is a retransmitted message or a new message.

In a possible implementation manner, the attribute type is included in the second model message.

In a possible implementation manner, the second model message further includes an attribute parameter, where the attribute parameter is used to indicate a parameter of the attribute type, or the attribute parameter is used to indicate an attribute value of the attribute type.

In a possible implementation, the apparatus further includes:

The instruction sending module is configured to send a second confirmation indication to the first device, where the second confirmation indication is used to indicate whether to feed back an attribute status notification confirmation message.

In a possible implementation manner, the second device and the first device are connected through BLE Mesh, and the first message sending module is configured to send the first device based on the BLE Mesh model. First model message.

In a possible implementation manner, the target application function is any one of at least one application function supported by the BLE Mesh model.

To sum up, in the solutions shown in the embodiments of the present application, IoT devices exchange information through model messages that support one or more application functions, and attribute types are carried in the model messages to indicate the application functions corresponding to the current message. , that is to say, for a variety of different application functions, the sender and the receiver can accurately distinguish only by the attribute type in the model message, so that the same model message can support a variety of different application functions. Correspondingly, it is not necessary to set a BLE Mesh model separately for each application function in the IoT device, thereby reducing the complexity of the model message interaction of the devices in the BLE Mesh, thereby improving the message interaction in the BLE Mesh. efficiency and resource utilization.

In addition, the solutions shown in the embodiments of this application perform information exchange through model messages that support one or more different application functions, which reduces the overhead of computing and storage resources of IoT devices, thereby improving the message flow in BLE Mesh. Interaction resource utilization.

It should be noted that, when the device provided in the above embodiment realizes its functions, only the division of the above functional modules is used as an example for illustration. In practical applications, the above functions can be allocated to different functional modules according to actual needs. That is, the content structure of the device is divided into different functional modules to complete all or part of the functions described above.

Regarding the apparatus in the above-mentioned embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be described in detail here.

Please refer to FIG. 12 , which shows a schematic structural diagram of a computer device 1200 provided by an embodiment of the present application. The computer device 1200 may include: a processor 1201 , a receiver 1202 , a transmitter 1203 , a memory 1204 and a bus 1205 .

The processor 1201 includes one or more processing cores, and the processor 1201 executes various functional applications and information processing by running software programs and modules.

The receiver 1202 and the transmitter 1203 may be implemented as a communication component, which may be a communication chip. The communication chip may also be referred to as a transceiver.

The memory 1204 is connected to the processor 1201 through the bus 1205 .

The memory 1204 can be used to store a computer program, and the processor 1201 is used to execute the computer program to implement each step performed by the server device, configuration device, cloud platform or account server in the above method embodiments.

Additionally, memory 1204 may be implemented by any type or combination of volatile or non-volatile storage devices including, but not limited to, magnetic or optical disks, electrically erasable programmable Read Only Memory, Erasable Programmable Read Only Memory, Static Anytime Access Memory, Read Only Memory, Magnetic Memory, Flash Memory, Programmable Read Only Memory.

In an exemplary embodiment, the computer device includes a processor, a memory, and a transceiver (the transceiver may include a receiver for receiving information and a transmitter for transmitting information) and a transmitter.

In a possible implementation manner, when the computer device is implemented as the first device,

the transceiver, configured to receive the first model message sent by the second device;

Wherein, the first model message includes an attribute type, and the attribute type is used to indicate the function attribute of the target application function.

When the computer device is implemented as the first device, the processor and transceiver in the computer device involved in the embodiments of the present application may perform the steps performed by the first device in the method shown in FIG. 3 or FIG. No longer.

In a possible implementation manner, when the computer device is implemented as the second device,

a transceiver for sending a first model message to the first device;

Wherein, the first model message includes an attribute type, and the attribute type is used to indicate the function attribute of the target application function.

When the computer device is implemented as a second device, the processor and transceiver in the computer device involved in the embodiments of the present application may perform the steps performed by the second device in the method shown in FIG. 3 or FIG. No longer.

Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored in the storage medium, and the computer program is loaded and executed by a processor to implement the above-mentioned Internet of Things shown in FIG. 3 or FIG. 5 . The various steps in the information exchange method.

The application also provides a computer program product or computer program, the computer program product or computer program comprising computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes each step in the information interaction method in the Internet of Things shown in the above 3 or FIG. 5 .

Those skilled in the art should realize that, in one or more of the above examples, the functions described in the embodiments of the present application may be implemented by hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

The above are only exemplary embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the protection of the present application. within the range.

Claims (31)

1. A message interaction method in the Internet of Things, characterized in that the method is executed by a first device in the Internet of Things, and the method includes:

   receiving the first model message sent by the second device;

   Wherein, the first model message includes an attribute type, and the attribute type is used to indicate the function attribute of the target application function.
2. The method according to claim 1, wherein the first model message further includes a first operation code, and the first operation code is used to indicate a message type of the first model message.
3. The method according to claim 2, wherein the message type of the first model message comprises: read attribute message, update attribute message or attribute status notification message;

   The read attribute message is used to read data related to the attribute type from the first device;

   The update attribute message is used to instruct the first device to update the data related to the attribute type;

   The attribute status notification message is used to notify the first device of data related to the attribute type.
4. The method according to claim 1, wherein the first model message further includes a transaction identifier, and the transaction identifier is used to indicate that the corresponding message is a retransmission message or a new message.
5. The method according to claim 1, wherein the first model message further includes an attribute parameter, and the attribute parameter is used to indicate the parameter of the attribute type, or the attribute parameter is used to indicate the attribute type property value.
6. The method according to claim 5, wherein when the message type of the first model message is an attribute update message or an attribute status notification message, the first model message further includes the attribute parameter.
7. The method according to claim 1, wherein the method further comprises:

   When the message type of the first model message is an attribute status notification message, a second model message is sent to the second device; the second model message includes a second operation code; the second operation code is used for Indicates that the message type of the second model message is an attribute status notification confirmation message.
8. The method according to claim 7, wherein the second model message includes a transaction identifier, and the transaction identifier is used to indicate that the corresponding message is a retransmission message or a new message.
9. The method according to claim 7, wherein the attribute type is included in the second model message.
10. The method according to claim 9, wherein the second model message further includes an attribute parameter, and the attribute parameter is used to indicate a parameter of the attribute type, or the attribute parameter is used to indicate the attribute type property value.
11. The method according to claim 7, wherein, when the message type of the first model message is an attribute status notification message, sending the second model message to the second device comprises:

    sending the second model message to the second device when the message type of the first model message is an attribute state notification message and a first confirmation indication for indicating feedback of an attribute state notification confirmation message is received;

    or,

    When the message type of the first model message is an attribute status notification message and a second confirmation indication for indicating whether to feed back an attribute status notification confirmation message is not received, the second model message is sent to the second device .
12. The method according to any one of claims 1 to 11, wherein the first device and the second device are connected through a wireless mesh network BLE Mesh based on Bluetooth low energy consumption, and the receiving the second device The first model message sent by the device, including:

    Receive the first model message sent by the second device based on the BLE Mesh model.
13. The method according to claim 12, wherein the target application function is any one of at least one application function supported by the BLE Mesh model.
14. A message interaction method in the Internet of Things, characterized in that the method is executed by a second device in the Internet of Things, and the method includes:

    sending a first model message to the first device;

    Wherein, the first model message includes an attribute type, and the attribute type is used to indicate the function attribute of the target application function.
15. The method according to claim 14, wherein the first model message further includes a first operation code, and the first operation code is used to indicate a message type of the first model message.
16. The method according to claim 15, wherein the message type of the first model message comprises: read property message, update property message or property status notification message;

    The read attribute message is used to read data related to the attribute type from the first device;

    The update attribute message is used to instruct the first device to update the data related to the attribute type;

    The attribute status notification message is used to notify the first device of data related to the attribute type.
17. The method according to claim 14, wherein the first model message further includes a transaction identifier, and the transaction identifier is used to indicate that the corresponding message is a retransmission message or a new message.
18. The method according to claim 14, wherein the first model message further includes an attribute parameter, and the attribute parameter is used to indicate a parameter of the attribute type, or the attribute parameter is used to indicate the attribute type property value.
19. The method according to claim 18, wherein when the message type of the first model message is an attribute update message or an attribute status notification message, the first model message further includes the attribute parameter.
20. The method of claim 14, wherein the method further comprises:

    When the message type of the first model message is an attribute status notification message, a second model message sent by the second device is received; the second model message includes a second operation code; the second operation code uses to indicate that the message type of the second model message is an attribute status notification confirmation message.
21. The method according to claim 20, wherein the second model message includes a transaction identifier, and the transaction identifier is used to indicate that the corresponding message is a retransmission message or a new message.
22. The method according to claim 20, wherein the attribute type is included in the second model message.
23. The method according to claim 22, wherein the second model message further includes an attribute parameter, and the attribute parameter is used to indicate a parameter of the attribute type, or the attribute parameter is used to indicate the attribute type property value.
24. The method of claim 20, wherein the method further comprises:

    Sending a second confirmation indication to the first device, where the second confirmation indication is used to indicate whether to feed back an attribute status notification confirmation message.
25. The method according to any one of claims 14 to 24, wherein the second device is connected to the first device through BLE Mesh, and the sending the first model message to the first device includes:

    Send the first model message to the first device based on the BLE Mesh model.
26. The method according to claim 25, wherein the target application function is any one of at least one application function supported by the BLE Mesh model.
27. A message interaction device in the Internet of Things, characterized in that the device is used in a first device in the Internet of Things, and the device comprises:

    a first message receiving module, configured to receive the first model message sent by the second device;

    Wherein, the first model message includes an attribute type, and the attribute type is used to indicate the function attribute of the target application function.
28. A message interaction device in the Internet of Things, characterized in that the device is used in a second device in the Internet of Things, and the device comprises:

    a first message sending module, configured to send a first model message to the first device;

    Wherein, the first model message includes an attribute type, and the attribute type is used to indicate the function attribute of the target application function.
29. A computer device, characterized in that the computer device is implemented as a first device; the computer device includes a processor, a memory, and a transceiver;

    a transceiver, configured to receive the first model message sent by the second device;

    Wherein, the first model message includes an attribute type, and the attribute type is used to indicate the function attribute of the target application function.
30. A computer device, characterized in that the computer device is implemented as a second device; the computer device includes a processor, a memory, and a transceiver;

    a transceiver for sending a first model message to the first device;

    Wherein, the first model message includes an attribute type, and the attribute type is used to indicate the function attribute of the target application function.
31. A computer-readable storage medium, characterized in that, a computer program is stored in the storage medium, and the computer program is used to be executed by a processor to implement the Internet of Things according to any one of claims 1 to 26. message interaction method.

Images