Communication method, device, system and computer equipment between intelligent devices

Abstract

The present application relates to a method, apparatus, system, computer equipment, storage medium and computer program product for communication between smart devices. The method includes: receiving a device authentication request, extracting a target playback box identifier, a sensor identifier and real-time sensor data carried in the device authentication request; responding to a target sensor selection operation performed according to the real-time sensor data, determining the target sensor identifier; associating the target playback box identifier and the target sensor identifier to obtain an association relationship, and extracting the target sensor data corresponding to the target sensor from the real-time sensor data; generating a program file according to the association relationship and the target sensor data, and encoding the program file; pushing a decoded message to the target playback box, the decoded message carrying the encoded program file, extracting the target sensor data in the program file, and pushing the target sensor data. The use of this method can realize communication between smart devices without relying on protocols.

Description

Technical Field

[0001] The present application relates to the field of information publishing technology, and in particular to a method, apparatus, system, computer equipment, storage medium and computer program product for communication between smart devices. Background Art

[0002] With the development of Internet of Things technology, we can use LED screens to play some multimedia programs to publish information to users.

[0003] In traditional technology, program publishing uses physical connection to communicate between smart devices (playback box and sensor), and uses program playback box to display the program on LED screen. That is, the user publishes the sensor program, the playback box receives the sensor program file through physical connection, and sends the program file to the LED screen for viewing.

[0004] However, although the use of a playback box can be used to watch programs, since the communication protocols and usage methods of each playback box are different, the use of physical connection to communicate between smart devices will be restricted by the communication protocol. In this case, it is impossible to solve the problem that when the playback box is not compatible with the user's existing sensor model, it is necessary to purchase a sensor that is compatible with the playback box to achieve communication between smart devices. Summary of the invention

[0005] Based on this, it is necessary to provide a method, apparatus, system, computer equipment, computer-readable storage medium and computer program product that can realize communication between smart devices without relying on protocols to address the above technical problems.

[0006] In a first aspect, the present application provides a method for communication between smart devices. The method comprises:

[0007] Receive a device authentication request, and extract a target playback box identifier, a sensor identifier, and real-time sensor data carried in the device authentication request;

[0008] In response to a target sensor selection operation performed based on the real-time sensing data of the sensor, determining a target sensor identifier;

[0009] Associating the target playback box identifier and the target sensor identifier to obtain an association relationship, and extracting target sensor data corresponding to the target sensor from the real-time sensor data of the sensor;

[0010] generating a program file according to the association relationship and the target sensor data, and encoding the program file;

[0011] A decoding message is pushed to a target playback box, the decoding message carrying an encoded program file, the decoding message being used to control the target playback box to decode the encoded program file, extract target sensor data from the program file, and push the target sensor data.

[0012] In one embodiment, before receiving the device authentication request and extracting the target playback box identifier, sensor identifier, and sensor real-time sensing data carried in the device authentication request, the method further includes:

[0013] Receive a user authentication request, and extract an authentication requester identifier carried in the user authentication request;

[0014] According to the authentication requester identifier, a device information upload prompt message is issued;

[0015] Receive the device information uploaded by the authentication requester.

[0016] In one embodiment, the determining the target sensor identifier in response to the target sensor selection operation performed according to the real-time sensing data of the sensor includes:

[0017] Obtaining an association table of the target playback box identifier and the sensor identifier;

[0018] Determine the available sensors according to the association table;

[0019] Pushing a target sensor selection prompt message, wherein the target sensor selection prompt message carries the real-time sensor data of the selectable sensor, and the target sensor selection prompt message is used to prompt the user to select a target sensor;

[0020] In response to a target sensor selection operation, a target sensor identification is determined.

[0021] In one embodiment, generating a program file according to the association relationship and the target sensor data, and encoding the program file includes:

[0022] generating an initial program file according to the association relationship;

[0023] The target sensor data is filled into the initial program file to generate a program file, and the program file is encoded.

[0024] In one embodiment, filling the target sensor data into the initial program file, generating a program file, and encoding the program file includes:

[0025] Filling the target sensor data into the initial program file to generate a program file;

[0026] Get the message format of the target player box;

[0027] The program file is encoded according to the message format to obtain an encoded program file.

[0028] In a second aspect, the present application also provides a communication device between smart devices. The device includes:

[0029] The device authentication module is used to receive a device authentication request and extract the target playback box identifier, sensor identifier and real-time sensor data carried in the device authentication request;

[0030] a sensor selection module, configured to determine a target sensor identifier in response to a target sensor selection operation performed according to the real-time sensing data of the sensor;

[0031] A data acquisition module, used for associating the target playback box identifier and the target sensor identifier to obtain an association relationship, and extracting target sensor data corresponding to the target sensor from the real-time sensor data of the sensor;

[0032] A program generating module, used for generating a program file according to the association relationship and the target sensor data, and encoding the program file;

[0033] The program push module is used to push a decoded message to a target playback box, wherein the decoded message carries an encoded program file, and the decoded message is used to control the target playback box to decode the encoded program file, extract target sensor data from the program file, and push the target sensor data.

[0034] In a third aspect, the present application also provides a communication system between smart devices. The system includes an information publishing platform and an Internet of Things platform;

[0035] The Internet of Things platform receives the authentication request, extracts the target playback box identifier, the sensor identifier, and the real-time sensor data carried in the authentication request; the Internet of Things platform sends the target playback box identifier, the sensor identifier, and the real-time sensor data to the information publishing platform;

[0036] The information publishing platform publishes the real-time sensor data of the sensor, responds to the target sensor selection operation performed according to the real-time sensor data of the sensor, determines the target sensor identifier, associates the target playback box identifier and the target sensor identifier to obtain an association relationship, and extracts the target sensor data corresponding to the target sensor from the real-time sensor data of the sensor, and extracts the target sensor data corresponding to the target sensor from the real-time sensor data of the sensor, generates a program file according to the association relationship and the target sensor data, and pushes the program file to the Internet of Things platform;

[0037] The Internet of Things platform encodes the program file and pushes a decoding message to a target playback box. The decoding message carries the encoded program file. The decoding message is used to control the target playback box to decode the encoded program file, extract target sensor data from the program file, and push the target sensor data.

[0038] In a fourth aspect, the present application further provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0039] Receive a device authentication request, and extract a target playback box identifier, a sensor identifier, and real-time sensor data carried in the device authentication request;

[0040] In response to a target sensor selection operation performed based on the real-time sensing data of the sensor, determining a target sensor identifier;

[0041] Associating the target playback box identifier and the target sensor identifier to obtain an association relationship, and extracting target sensor data corresponding to the target sensor from the real-time sensor data of the sensor;

[0042] generating a program file according to the association relationship and the target sensor data, and encoding the program file;

[0043] A decoding message is pushed to a target playback box, the decoding message carrying an encoded program file, the decoding message being used to control the target playback box to decode the encoded program file, extract target sensor data from the program file, and push the target sensor data.

[0044] In a fifth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0045] Receive a device authentication request, and extract a target playback box identifier, a sensor identifier, and real-time sensor data carried in the device authentication request;

[0046] In response to a target sensor selection operation performed based on the real-time sensing data of the sensor, determining a target sensor identifier;

[0047] Associating the target playback box identifier and the target sensor identifier to obtain an association relationship, and extracting target sensor data corresponding to the target sensor from the real-time sensor data of the sensor;

[0048] generating a program file according to the association relationship and the target sensor data, and encoding the program file;

[0049] A decoding message is pushed to a target playback box, the decoding message carrying an encoded program file, the decoding message being used to control the target playback box to decode the encoded program file, extract target sensor data from the program file, and push the target sensor data.

[0050] In a sixth aspect, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0051] Receive a device authentication request, and extract a target playback box identifier, a sensor identifier, and real-time sensor data carried in the device authentication request;

[0052] In response to a target sensor selection operation performed based on the real-time sensing data of the sensor, determining a target sensor identifier;

[0053] Associating the target playback box identifier and the target sensor identifier to obtain an association relationship, and extracting target sensor data corresponding to the target sensor from the real-time sensor data of the sensor;

[0054] generating a program file according to the association relationship and the target sensor data, and encoding the program file;

[0055] A decoding message is pushed to a target playback box, the decoding message carrying an encoded program file, the decoding message being used to control the target playback box to decode the encoded program file, extract target sensor data from the program file, and push the target sensor data.

[0056] The above-mentioned communication method, device, system, computer equipment, storage medium and computer program product between smart devices, first, receive a device authentication request, extract the target playback box identifier, sensor identifier and sensor real-time sensor data carried in the device authentication request; respond to the target sensor selection operation performed according to the sensor real-time sensor data, determine the target sensor identifier; associate the target playback box identifier and the target sensor identifier to obtain an association relationship, and extract the target sensor data corresponding to the target sensor from the sensor real-time sensor data, by obtaining the association relationship between the target playback box identifier and the target sensor identifier, it is possible to achieve a connection between the target playback box and the target sensor without a protocol; generate a program file according to the association relationship and the target sensor data, and encode the program file; push a decoding message to the target playback box, the decoding message carries the encoded program file, the decoding message is used to control the target playback box to decode the encoded program file, extract the target sensor data in the program file, and push the target sensor data. In this application, by associating the target playback box identifier and the target sensor identifier, communication between smart devices without relying on protocols is achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] Figure 1 A diagram of an application environment of a method for communication between smart devices in one embodiment;

[0058] Figure 2 A schematic diagram of a flow chart of a method for communication between smart devices in one embodiment;

[0059] Figure 3 A schematic diagram of a flow chart of a method for communication between smart devices in one embodiment;

[0060] Figure 4 is a flow chart of a method for communication between smart devices in another embodiment;

[0061] Figure 5 A timing diagram for publishing a sensor program in one embodiment;

[0062] Figure 6 is a structural block diagram of a communication device between smart devices in one embodiment;

[0063] Figure 7 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0064] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0065] The communication method between smart devices provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown in the figure, the terminal side is composed of multiple terminals 102, and the terminal 102 includes devices such as sensors, playback boxes, and LED screens. The terminal side can communicate bidirectionally with the server 104 through the network. The data storage system can store data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. The terminal side sends a device authentication request to the server 104, the device authentication request contains the target playback box identifier, sensor identifier and sensor real-time sensor data, the server 104 receives the device authentication request, extracts the target playback box identifier, sensor identifier and sensor real-time sensor data carried in the device authentication request; responds to the target sensor selection operation performed according to the sensor real-time sensor data, determines the target sensor identifier; associates the target playback box identifier and the target sensor identifier to obtain an association relationship, and extracts the target sensor data corresponding to the target sensor from the sensor real-time sensor data; generates a program file according to the association relationship and the target sensor data, and encodes the program file; pushes a decoding message to the target playback box, the decoding message carries the encoded program file, and the decoding message is used to control the target playback box to decode the encoded program file, extract the target sensor data in the program file, and push the target sensor data. Furthermore, the target sensor data can be pushed to the LED screen on the terminal side for display. The server 104 can be implemented with an independent server or a server cluster consisting of multiple servers.

[0066] In one embodiment, Figure 2 As shown, a method for communication between smart devices is provided, and the method is applied to Figure 1 The server 104 is used as an example for description, and the following steps are included:

[0067] S100, receiving a device authentication request, and extracting a target playback box identifier, a sensor identifier, and real-time sensor data carried in the device authentication request.

[0068] Among them, the device in this application refers to an intelligent device, including a sensor and a playback box; the device authentication request is a request to determine whether the device can access the server for authentication, that is, to determine whether the device is a request for the corresponding user's device; the playback box is a playback terminal that can play programs in real time by connecting to a display device. In this application, the playback box is used to connect to a display device to realize the display of programs, i.e., real-time sensor data of the sensor; the playback box identifier is used to characterize the identity of the playback box, and the target playback box can be identified by using the playback box identifier; the sensor identifier is used to characterize the identity of the sensor, and the sensor identifier can be used to identify the sensor; a sensor is a detection device that can sense the measured information and can convert the sensed information into an electrical signal or other required form of information output according to a certain rule to meet the requirements of information transmission, processing, storage, display, recording and control, including but not limited to temperature sensors and humidity sensors that can sense the surrounding environment; sensor real-time sensor data refers to data sensed, measured and transmitted by the sensor.

[0069] Specifically, the terminal side is composed of multiple terminals 102, and the terminal 102 includes devices such as sensors, playback boxes and LED screens. The terminal side can communicate bidirectionally with the server 104 through the network; the terminal 102 sends a device authentication request to the server 104, and the device authentication request contains a target playback box identifier, a sensor identifier and real-time sensor data. The server 104 receives the device authentication request and determines whether the device to be authenticated is the device of the corresponding user. When processing the device authentication request, a communication message will be obtained from the device authentication request. This communication information will be parsed by the server 104, and the target playback box identifier, sensor identifier and real-time sensor data carried in the device authentication request can be extracted from the communication information, i.e., the device authentication request, so that the playback box identifier corresponding to the user, the multiple sensor identifiers corresponding to the user and the real-time sensor data of these sensors when they are working can be obtained.

[0070] S200, in response to a target sensor selection operation performed according to real-time sensing data of the sensor, determining a target sensor identifier.

[0071] The sensor refers to a sensor represented by a sensor identifier, which is a hardware device and also an intelligent device; the target sensor is a sensor required by a user selected from multiple sensors.

[0072] Specifically, the user can freely select the sensor real-time data and can check the sensor identification he needs from multiple sensor identifications according to the sensor real-time sensing data. At this time, the server 104 responds to the target sensor selection operation performed by the user according to the sensor real-time sensing data, and can confirm the target sensor identification corresponding to the target sensor selected by the user, that is, determine the target sensor identification.

[0073] Furthermore, the target sensor identifier includes but is not limited to one, and may also be multiple.

[0074] S300, associating the target playback box identifier and the target sensor identifier to obtain an association relationship, and extracting target sensor data corresponding to the target sensor from the real-time sensor data.

[0075] Specifically, in order to achieve a connection between the playback box and the sensor without relying on a physical connection, the server 104 associates the target sensor identifier selected by the user with the user's target playback box identifier, so that there is a certain association between the target playback box and the target sensor. Since the association is with the target sensor identifier corresponding to the target sensor selected by the user, rather than all sensor identifiers, only the target sensor data corresponding to the target sensor is needed. Therefore, the target sensor data corresponding to the target sensor is also extracted from the real-time sensor data.

[0076] S400, generating a program file according to the association relationship and the target sensor data, and encoding the program file.

[0077] Among them, in this application, program refers to real-time data of sensors; program file refers to a file including real-time data of the target sensor selected by the user, and the program file is decoded and transmitted to the smart device for decoding to realize the playback of real-time data on the display device; encoding is the process of converting information from one form or format to another.

[0078] Specifically, after the server 104 associates the target sensor identifier selected by the user with the target player box identifier of the user, what is obtained is the association relationship between the target player box corresponding to the target player box identifier and the target sensor corresponding to the target sensor identifier. The server 104 automatically parses and generates a program file based on the association relationship between the target player box and the target sensor and the target sensor data corresponding to the target sensor. Since the message format between the server 104 and the smart device is different, the server 104 will encode the program file and then send it to the target player box associated with the target sensor.

[0079] S500, pushing a decoding message to a target playback box, the decoding message carrying the encoded program file, the decoding message being used to control the target playback box to decode the encoded program file, extract target sensor data from the program file, and push the target sensor data.

[0080] Among them, decoding is the process by which the recipient restores the received symbols or codes into information, which corresponds to the encoding process.

[0081] Specifically, sending the encoded program file to the target playback box associated with the target sensor is achieved by pushing a decoding message. The decoding message carries the encoded program file. The encoded program file needs to be decoded to restore the program file, so the decoding message is also used to control the target playback box to decode the encoded program file. After decoding, the program file is restored to the association between the target playback box and the target sensor and the target sensor data corresponding to the target sensor. The server 104 extracts the target sensor data in the program file and pushes the target sensor data out.

[0082] In the above-mentioned communication method between smart devices, first, a device authentication request is received, and the target playback box identifier, sensor identifier, and real-time sensor data carried in the device authentication request are extracted; the target sensor selection operation performed according to the real-time sensor data is responded to, and the target sensor identifier is determined; the target playback box identifier and the target sensor identifier are associated to obtain an association relationship, and the target sensor data corresponding to the target sensor is extracted from the real-time sensor data of the sensor. By obtaining the association relationship between the target playback box identifier and the target sensor identifier, it is possible to achieve a connection between the target playback box and the target sensor without a protocol; a program file is generated according to the association relationship and the target sensor data, and the program file is encoded; a decoding message is pushed to the target playback box, the decoding message carries the encoded program file, and the decoding message is used to control the target playback box to decode the encoded program file, extract the target sensor data in the program file, and push the target sensor data. In this application, by associating the target playback box identifier and the target sensor identifier, communication between smart devices without relying on a protocol is achieved.

[0083] In one embodiment, Figure 3 As shown, before S100, it also includes:

[0084] S120, receiving a user authentication request, and extracting an authentication requester identifier carried in the user authentication request.

[0085] Among them, user authentication refers to the verification of the user's identity; the authentication requester identifier is an identifier that represents the identity of the user who issues the authentication request, and the authentication requester identifier includes but is not limited to a spatial identifier used to represent the user's identity.

[0086] Exemplarily, in a space where multiple users exist, each user has his or her own exclusive spatial node. When a user issues an authentication request, server 104 receives the user's authentication request, which carries an authentication requester identifier. Since the authentication requester identifier can be a spatial identifier used to characterize the user's identity, the authentication requester identifier carried in the user's authentication request is extracted to determine which spatial node the user is in.

[0087] S140: Send a device information upload prompt message according to the authentication requester identifier.

[0088] Exemplarily, when the spatial node where user A is located is Space 1, based on the authentication requester identifier, server 104 can know which spatial node the user's request is transmitted from, that is, identify the spatial node where user A is located as Space 1. After the identification is completed, user A's request is redirected to the identified Space 1, so that a device information upload prompt message can be sent to Space 1, and then the device information of the user, that is, the authentication requester, can be read and uploaded based on the permission given to the server to read the devices in the space where the user is located during authentication.

[0089] S160, receiving device information uploaded by the authentication requester.

[0090] Exemplarily, when the spatial node where user A is located is space 1, the device information uploaded by user A, i.e. the authentication requester, carries the playback box identifier of space 1 and multiple sensor identifiers in space 1; the server 104 receives the device information uploaded by the authentication requester, and can read the playback box identifier of space 1 as the target playback box identifier, and read multiple sensor identifiers in space 1 to obtain the device information corresponding to space 1 where user A is located.

[0091] Furthermore, the device information corresponding to space 1 where user A is located will be used in the device authentication stage to determine whether the information carried in the device authentication request issued by the device is consistent with the device information corresponding to space 1 where user A is located at this time. If they are consistent, the device authentication is successful and confirmed as user A's device, avoiding mutual interference with other users' devices.

[0092] In this embodiment, the authentication center uses spatial isolation to identify authentication requests issued by a single user in a multi-user environment, thereby achieving user data isolation and preventing device data of different users in different spaces from interfering with each other.

[0093] In one embodiment, Figure 4 As shown, S200 includes:

[0094] S220, obtaining an association table of target playback box identifiers and sensor identifiers.

[0095] Among them, the association relationship table refers to the existence of one-to-one, one-to-many, or many-to-many relationships between the data in the association relationship table.

[0096] Specifically, after the device is successfully authenticated, since the target player box identifier and sensor identifier carried in the device authentication request are extracted, an association table of the target player box identifier and sensor identifier that is exclusive to the user can be formed, that is, the user's target player box can be associated with multiple sensors, and the association table of the user's target player box identifier and sensor identifier can be obtained at this time.

[0097] S240, determining available sensors according to the association table.

[0098] Specifically, since the association table represents the relationship between the target playback box identifier and the sensor identifier, after user A obtains the association table, at this time, the association table of the target playback box identifier and the sensor identifier contains the corresponding relationship between the target playback box and multiple sensors, and multiple sensors can be selected by the user, that is, the selectable sensors can be determined according to the association table.

[0099] S260: Push a target sensor selection prompt message, where the target sensor selection prompt message carries real-time sensor data of available sensors, and is used to prompt the user to select a target sensor.

[0100] Specifically, the server 104 pushes a target sensor selection prompt message to the user, which carries real-time sensor data of available sensors and is used to prompt the user to select the target sensor he needs from the available sensors based on the real-time sensor data of the available sensors.

[0101] S280, responding to the target sensor selection operation, determining the target sensor identifier.

[0102] Specifically, after receiving the pushed target sensor selection prompt message, respond to the target sensor selection operation, select the target sensor, and determine the sensor you need from multiple available sensors, that is, check the target sensor identifier you need in the association table.

[0103] In this embodiment, by determining the target sensor identifier from the sensor identifier, the sensor and sensor real-time data required by the user can be freely selected, and personalized customization can be achieved according to the user's demand for the sensor real-time data.

[0104] In one embodiment, generating a program file according to the association relationship and the target sensor data, and encoding the program file includes:

[0105] Generate an initial program file based on the association relationship.

[0106] Specifically, when the user publishes a sensor program, an initial program file including the association relationship between the target player box identifier and the target sensor identifier is generated according to the association relationship between the target player box identifier and the target sensor identifier.

[0107] Fill the target sensor data into the initial program file, generate the program file, and encode the program file.

[0108] Specifically, the initial program file only contains the association between the target playback box identifier and the target sensor identifier. At this time, the real-time sensor data of the target sensor, i.e., the target sensor data, is filled into the initial program file to generate a program file. The program file contains the target sensor data and the association between the target sensor data and the initial program file. The generated program file is encoded so that the encoded program file can be sent to the corresponding device.

[0109] In this embodiment, the program file is generated by automatically parsing the association relationship and the target sensor data, so that the program file for transmitting the target sensor data of the target sensor to the target playback box can be obtained.

[0110] In one embodiment, filling the target sensor data into the initial program file, generating the program file, and encoding the program file includes:

[0111] Fill the target sensor data into the initial program file to generate a program file.

[0112] Specifically, the real-time sensing data of the target sensor, namely the target sensing data, is filled into the initial program file to generate a program file, in which there exists the target sensing data and the association relationship in the initial program file.

[0113] Get the message format of the target player box.

[0114] Specifically, since the program file cannot be directly pushed to the target playback box at this time, the program file needs to be processed to a certain extent to convert the program file into a form that matches the message format of the target playback box, so the message format of the target playback box needs to be obtained first.

[0115] The program file is encoded according to the message format to obtain an encoded program file.

[0116] Specifically, the generated program file is encoded according to the message format of the target playback box, and the program file is encoded into a form matching the message format of the target playback box to obtain the encoded program file, so that the encoded program file can be pushed to the target playback box.

[0117] In this embodiment, the program file can be pushed to the target playback box by encoding the program file.

[0118] In one embodiment, after decoding the encoded program file, a restored program file can be obtained, and the program file can be pushed to a display device for playing.

[0119] The display device includes but is not limited to LED screens and other devices capable of displaying.

[0120] In one embodiment, when publishing a sensor program to an LED display screen, data interaction is achieved between the front-end subsystem, the back-end subsystem, the IoTHub subsystem, and the playback box. The timing diagram for publishing the sensor program is as follows: Figure 5 As shown, it includes three parts: reviewing the playlist, publishing the playlist and executing the playlist, among which the sensor program is the environmental parameter detected by the sensor.

[0121] Specifically, during the data interaction between the front-end subsystem, the back-end subsystem, the IoTHub subsystem, and the playback box when reviewing the playlist, the front-end subsystem needs to first ask the back-end subsystem to review the program files carrying the real-time sensor data. At this time, the back-end subsystem requests the IoTHub subsystem to generate the program files. The IoTHub subsystem generates the program files and stores them in the IoTHub subsystem. It returns the generated program files to the back-end subsystem. After receiving the generated program files, the back-end subsystem returns the review results of the program files to the front-end subsystem.

[0122] After reviewing the playlist and during the data interaction between the front-end subsystem, back-end subsystem, IoTHub subsystem and playback box when publishing the playlist, the front-end subsystem needs to publish the program file carrying the real-time sensor data. At this time, the back-end subsystem stores the execution record and publishes the program to the LED screen specified by the IoTHub subsystem. The IoTHub subsystem replaces the original sensor data and then sends it to the playback box. The playback box returns the result to the IoTHub subsystem, and the IoTHub subsystem returns the result of publishing the program to the specified LED screen to the back-end subsystem. The back-end subsystem returns the publishing result to the front-end subsystem.

[0123] After publishing the playlist, since the LED screen is specified when publishing the playlist, in the data interaction process between the front-end subsystem, the back-end subsystem, the IoTHub subsystem and the playback box when executing the playlist, multiple sensors and the playback box must be associated first, and the playback box is directly associated with the specified LED screen. Therefore, to execute the playback of the sensor on the LED screen, the front-end subsystem must associate multiple sensors with the specified LED screen, and the back-end subsystem stores the association relationship between the multiple sensors and the LED screen, and returns the obtained association result to the front-end subsystem; when the playback box wants to receive the program file, it must request the environmental parameter html page detected by the sensor, and the front-end subsystem returns the environmental parameter html page detected by the sensor; when the playback box queries the real-time sensor data, that is, the real-time environmental data, from the back-end subsystem on the html page, the back-end subsystem queries the stored association relationship between the LED screen and multiple sensors, and then queries the IoTHub subsystem for sensor real-time data based on the queried association relationship, the IoTHub subsystem returns the sensor real-time data to the back-end subsystem, and the back-end subsystem transmits the sensor real-time data to the playback box.

[0124] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0125] Based on the same inventive concept, the embodiment of the present application also provides an inter-intelligent device communication device for implementing the inter-intelligent device communication method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the one or more inter-intelligent device communication device embodiments provided below can refer to the above limitations on the inter-intelligent device communication method, and will not be repeated here.

[0126] In one embodiment, Figure 6 As shown, a communication device between smart devices is provided, including: a device authentication module 100, a sensor selection module 200, a data acquisition module 300, a program generation module 400 and a program push module 500, wherein:

[0127] The device authentication module 100 is used to receive a device authentication request and extract the target playback box identifier, sensor identifier and real-time sensor data carried in the device authentication request.

[0128] The sensor selection module 200 is used to respond to the target sensor selection operation performed according to the real-time sensing data of the sensor and determine the target sensor identification.

[0129] The data acquisition module 300 is used to associate the target playback box identifier and the target sensor identifier to obtain an association relationship, and extract target sensor data corresponding to the target sensor from the real-time sensor data.

[0130] The program generation module 400 is used to generate a program file according to the association relationship and the target sensor data, and encode the program file.

[0131] The program push module 500 is used to push a decoded message to a target playback box. The decoded message carries an encoded program file. The decoded message is used to control the target playback box to decode the encoded program file, extract target sensor data from the program file, and push the target sensor data.

[0132] In one embodiment, it also includes a user authentication module, which is used to: receive a user authentication request, extract the authentication requester identifier carried in the user authentication request; issue a device information upload prompt message based on the authentication requester identifier; and receive the device information uploaded by the authentication requester.

[0133] In one embodiment, the sensor selection module 200 is also used to: obtain an association table of the target playback box identifier and the sensor identifier; determine the selectable sensors based on the association table; push a target sensor selection prompt message, the target sensor selection prompt message carries real-time sensor data of the selectable sensors, and the target sensor selection prompt message is used to prompt the user to select a target sensor; respond to the target sensor selection operation and determine the target sensor identifier.

[0134] In one embodiment, the program generation module 400 is further used to: generate an initial program file according to the association relationship; fill the target sensor data into the initial program file to generate a program file, and encode the program file.

[0135] In one embodiment, the program generation module 400 is also used to: fill the target sensor data into the initial program file to generate the program file; obtain the message format of the target playback box; encode the program file according to the message format to obtain the encoded program file.

[0136] Each module in the above-mentioned communication device between intelligent devices can be implemented in whole or in part by software, hardware and their combination. Each module can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each module above.

[0137] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 7 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store target sensor data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a communication method between intelligent devices is implemented.

[0138] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0139] In one embodiment, a communication system between smart devices is also provided, including an information publishing platform and an Internet of Things platform;

[0140] The Internet of Things platform receives the authentication request, and extracts the target playback box identifier, sensor identifier, and real-time sensor data carried in the authentication request; the Internet of Things platform sends the target playback box identifier, sensor identifier, and real-time sensor data to the information publishing platform; the information publishing platform publishes the real-time sensor data, responds to the target sensor selection operation performed according to the real-time sensor data, determines the target sensor identifier, associates the target playback box identifier and the target sensor identifier to obtain an association relationship, and extracts the target sensor data corresponding to the target sensor from the real-time sensor data, and extracts the target sensor data corresponding to the target sensor from the real-time sensor data, generates a program file according to the association relationship and the target sensor data, and pushes the program file to the Internet of Things platform; the Internet of Things platform encodes the program file, and pushes a decoding message to the target playback box, the decoding message carries the encoded program file, and the decoding message is used to control the target playback box to decode the encoded program file, extract the target sensor data in the program file, and push the target sensor data.

[0141] Specifically, the IoT platform receives a device authentication request, determines whether the device being authenticated is the device of the corresponding user, obtains a communication message from the device authentication request when processing the device authentication request, parses the communication message, extracts the target player box identifier, sensor identifier, and sensor real-time sensing data carried in the device authentication request, thereby obtaining the player box identifier corresponding to the user, multiple sensor identifiers corresponding to the user, and real-time sensing data of these sensors when working, and sends them to the information publishing platform; the information publishing platform publishes the sensor real-time sensing data, and responds to the target sensor selection operation performed by the user based on the sensor real-time sensing data, confirms the target sensor identifier corresponding to the target sensor selected by the user The target sensor identifier selected by the user and the target player box identifier of the user are associated with each other, so that there is a certain association between the target player box and the target sensor, the target sensor data corresponding to the target sensor is extracted from the real-time sensor data, and a program file is generated according to the association relationship and the target sensor data, and the program file is pushed to the Internet of Things platform; the Internet of Things platform encodes the program file, and because the encoded program file needs to be decoded to restore the program file, a decoding message carrying the encoded program file can be pushed to the target player box to control the target player box to decode the encoded program file, and at this time, the target sensor data in the program file is extracted from the decoded program file, and the target sensor data is pushed out.

[0142] In one embodiment, the communication system between smart devices further includes a unified authentication center platform;

[0143] The unified authentication center platform receives the user authentication request and extracts the authentication requester identifier carried in the user authentication request; the unified authentication center platform issues a device information upload prompt message based on the authentication requester identifier; the unified authentication center platform receives the device information uploaded by the authentication requester.

[0144] Specifically, when a user logs in to the unified authentication center platform, he sends a user authentication request. The unified authentication center platform extracts the authentication requester identifier carried in the user authentication request. The authentication requester identifier includes but is not limited to the space identifier that represents the user's identity. Therefore, the unified authentication center can obtain the space where the user is located and achieve data isolation from other users; the unified authentication center platform redirects the user authentication request to the space where the user is located based on the authentication requester identifier, and sends a device information upload prompt message to the space where the user is located; the unified authentication center platform receives the device information uploaded by the authentication requester based on the permission given by the user to read the devices in his own space during authentication.

[0145] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0146] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0147] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0148] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0149] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0150] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for communication between smart devices, characterized in that: The method comprises: Receive a device authentication request, and extract a target playback box identifier, a sensor identifier, and real-time sensor data carried in the device authentication request; In response to a target sensor selection operation performed based on the real-time sensing data of the sensor, determining a target sensor identifier; Associating the target playback box identifier and the target sensor identifier to obtain an association relationship, and extracting target sensor data corresponding to the target sensor from the real-time sensor data of the sensor; generating a program file according to the association relationship and the target sensor data, and encoding the program file; A decoding message is pushed to a target playback box, the decoding message carrying an encoded program file, the decoding message being used to control the target playback box to decode the encoded program file, extract target sensor data from the program file, and push the target sensor data.

2. The method according to claim 1, characterized in that Before receiving the device authentication request and extracting the target playback box identifier, sensor identifier, and sensor real-time sensing data carried in the device authentication request, the method further includes: Receive a user authentication request, and extract an authentication requester identifier carried in the user authentication request; According to the authentication requester identifier, a device information upload prompt message is issued; Receive the device information uploaded by the authentication requester.

3. The method according to claim 1, characterized in that The determining of the target sensor identifier in response to the target sensor selection operation performed according to the real-time sensing data of the sensor includes: Obtaining an association table of the target playback box identifier and the sensor identifier; Determine the available sensors according to the association table; Pushing a target sensor selection prompt message, wherein the target sensor selection prompt message carries the real-time sensor data of the selectable sensor, and the target sensor selection prompt message is used to prompt the user to select a target sensor; In response to a target sensor selection operation, an identification of the target sensor is determined.

4. The method according to claim 1, characterized in that: The generating a program file according to the association relationship and the target sensor data, and encoding the program file comprises: generating an initial program file according to the association relationship; The target sensor data is filled into the initial program file to generate a program file, and the program file is encoded.

5. The method according to claim 4, characterized in that The step of filling the target sensor data into the initial program file, generating a program file, and encoding the program file comprises: Filling the target sensor data into the initial program file to generate a program file; Get the message format of the target player box; The program file is encoded according to the message format to obtain an encoded program file.

6. A communication device between smart devices, characterized in that: The device comprises: The device authentication module is used to receive a device authentication request and extract the target playback box identifier, sensor identifier and real-time sensor data carried in the device authentication request; a sensor selection module, configured to determine a target sensor identifier in response to a target sensor selection operation performed according to the real-time sensing data of the sensor; A data acquisition module, used for associating the target playback box identifier and the target sensor identifier to obtain an association relationship, and extracting target sensor data corresponding to the target sensor from the real-time sensor data of the sensor; A program generating module, used for generating a program file according to the association relationship and the target sensor data, and encoding the program file; The program push module is used to push a decoded message to a target playback box, wherein the decoded message carries an encoded program file, and the decoded message is used to control the target playback box to decode the encoded program file, extract target sensor data from the program file, and push the target sensor data.

7. A communication system between smart devices, characterized in that: Including information publishing platform and Internet of Things platform; The Internet of Things platform receives a device authentication request, and extracts a target playback box identifier, a sensor identifier, and real-time sensor data carried in the device authentication request; The Internet of Things platform sends the target playback box identifier, the sensor identifier, and the real-time sensor data to the information publishing platform; The information publishing platform publishes the real-time sensor data of the sensor, responds to the target sensor selection operation performed according to the real-time sensor data of the sensor, determines the target sensor identifier, associates the target playback box identifier and the target sensor identifier to obtain an association relationship, and extracts the target sensor data corresponding to the target sensor from the real-time sensor data of the sensor, and extracts the target sensor data corresponding to the target sensor from the real-time sensor data of the sensor, generates a program file according to the association relationship and the target sensor data, and pushes the program file to the Internet of Things platform; The Internet of Things platform encodes the program file and pushes a decoding message to a target playback box. The decoding message carries the encoded program file. The decoding message is used to control the target playback box to decode the encoded program file, extract target sensor data from the program file, and push the target sensor data.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 5 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are implemented.

Images