CN113645714A

CN113645714A - Equipment connection method, device, system, equipment and storage medium

Info

Publication number: CN113645714A
Application number: CN202110510536.8A
Authority: CN
Inventors: 周波; 冯波; 胡永强
Original assignee: CCB Finetech Co Ltd
Current assignee: China Construction Bank Corp
Priority date: 2021-05-11
Filing date: 2021-05-11
Publication date: 2021-11-12
Anticipated expiration: 2041-05-11
Also published as: CN113645714B

Abstract

The invention discloses a device connection method, a device, a system, a device and a storage medium, and relates to the technical field of mobile interconnection. The method comprises the following steps: receiving a device operation request sent by a master device; the equipment operation request carries a main equipment identifier and a main equipment name; identifying and extracting a sub-device list corresponding to the main device according to the device operation request; and feeding back the sub-equipment list to the main equipment so that the main equipment updates a local equipment list according to the sub-equipment list. The application layer of the embodiment of the invention is accessed to the platform of the Internet of things in a mode of integrating the application SDK, thereby realizing the functions of equipment management, equipment reporting data receiving, instruction issuing and the like.

Description

Equipment connection method, device, system, equipment and storage medium

Technical Field

The embodiment of the invention relates to the technical field of mobile interconnection, in particular to a device connection method, a device, a system, a device and a storage medium.

Background

With the rapid development of the internet of things, more and more types and types of equipment are added into the internet of things. In order to make these devices work together to provide rich intelligent services to users, a binding relationship between these devices needs to be established to control these devices.

At present, the establishment of the binding relationship between the devices is mainly initiated by the device side, but the adoption of the method is inconvenient for unbinding and binding the devices again.

Disclosure of Invention

In view of this, the present invention provides a device connection method, apparatus, system, device and storage medium, which implement flexible binding and unbinding between a main device and a sub-device.

In a first aspect, an embodiment of the present invention provides an apparatus connection method, which is applied to an internet of things platform, and includes:

receiving a device operation request sent by a master device; the equipment operation request carries a main equipment identifier and a main equipment name;

identifying and extracting a sub-device list corresponding to the main device according to the device operation request;

and feeding back the sub-equipment list to the main equipment so that the main equipment updates a local equipment list according to the sub-equipment list.

In a second aspect, an embodiment of the present invention further provides an apparatus connection method, applied to a master apparatus, including:

sending an equipment operation request to an Internet of things platform; the equipment operation request carries a main equipment identifier and a main equipment name;

receiving a sub-device list fed back by the Internet of things platform;

and updating a local equipment list according to the sub-equipment list.

In a third aspect, an embodiment of the present invention further provides an apparatus connecting device, which is applied to an internet of things platform, and includes:

the first receiving module is used for receiving a device operation request sent by the main device; the equipment operation request carries a main equipment identifier and a main equipment name;

the identification extraction module is used for identifying and extracting a sub-equipment list corresponding to the main equipment according to the equipment operation request;

and the feedback module is used for feeding back the sub-equipment list to the main equipment so that the main equipment updates the local equipment list according to the sub-equipment list.

In a fourth aspect, an embodiment of the present invention further provides an apparatus connecting device, which is applied to a main apparatus, and includes:

the sending module is used for sending an equipment operation request to the Internet of things platform; the equipment operation request carries a main equipment identifier and a main equipment name;

the receiving module is used for receiving a sub-device list fed back by the Internet of things platform;

and the updating module is used for updating the local equipment list according to the sub-equipment list.

In a fifth aspect, an embodiment of the present invention further provides an apparatus connection system, including: the system comprises an equipment end, an Internet of things platform and an application layer; wherein, the equipment end includes: a master device and a slave device; the sub-equipment and the main equipment belong to the same application layer and the same Internet of things platform;

the main equipment in the equipment end establishes communication connection with the Internet of things platform through the equipment end SDK; and the application layer establishes communication connection with the Internet of things platform in an SDK (software development kit) mode.

In a sixth aspect, an embodiment of the present invention further provides an apparatus connecting apparatus, where the apparatus includes:

one or more processors;

a memory for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement a device connection method as in any one of the above embodiments.

In a seventh aspect, the embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the device connection method according to any one of the embodiments of the present invention.

The embodiment of the invention receives the equipment operation request sent by the main equipment; the equipment operation request carries a main equipment identifier and a main equipment name; identifying and extracting a sub-device list corresponding to the main device according to the device operation request; and feeding back the sub-equipment list to the main equipment so that the main equipment updates a local equipment list according to the sub-equipment list. The application layer of the embodiment of the invention is accessed to the platform of the Internet of things in a mode of integrating the application SDK, thereby realizing the functions of equipment management, equipment reporting data receiving, instruction issuing and the like.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.

Fig. 1 is a flowchart of a device connection method according to an embodiment of the present invention;

fig. 2 is a flowchart of another device connection method provided in an embodiment of the present invention;

fig. 3 is a flowchart of another device connection method provided in an embodiment of the present invention;

fig. 4 is a flowchart of a further method for connecting devices according to an embodiment of the present invention;

fig. 5 is a flowchart of a further method for connecting devices according to an embodiment of the present invention;

fig. 6 is a flowchart of a further method for connecting devices according to an embodiment of the present invention;

fig. 7 is a flowchart of a further method for connecting devices according to an embodiment of the present invention;

fig. 8 is a flowchart of a further method for connecting devices according to an embodiment of the present invention;

fig. 9 is a flowchart illustrating an automatic start of a master device according to an embodiment of the present invention;

FIG. 10 is a schematic diagram of an interface display of an apparatus for adding a binding partner according to an embodiment of the present invention;

fig. 11 is a schematic diagram of an interface display for releasing a binding relationship between a master device and a slave device according to an embodiment of the present invention;

fig. 12 is a flowchart of releasing a binding relationship between a master device and a slave device according to an embodiment of the present invention;

fig. 13 is a schematic view of an interface display of a delete sub-device according to an embodiment of the present invention;

fig. 14 is a flowchart of a method for deleting a child device according to an embodiment of the present invention;

fig. 15 is a flowchart illustrating a sub-device sending a message to an internet of things platform according to an embodiment of the present invention;

fig. 16 is a flowchart illustrating an update of a local device list of a master device according to an embodiment of the present invention;

FIG. 17 is a schematic structural diagram of an apparatus connecting device according to an embodiment of the present invention;

FIG. 18 is a schematic structural diagram of another device connecting apparatus provided in the embodiments of the present invention;

FIG. 19 is a schematic diagram of a device connection system according to an embodiment of the present invention;

FIG. 20 is a block diagram of another device connection system provided by embodiments of the present invention;

fig. 21 is a schematic structural diagram of a device connection device according to an embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present invention, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.

At present, a binding relationship is established between each device, a user needs to operate at a device end, and the user uploads device identification information of the main device and the sub-device to an internet of things platform for binding. However, the binding mode at the device end requires that the user is around the device and the usage scenario is limited; or only binding sub-devices can be added to a single master device, and the binding sub-devices cannot be imported to a plurality of master devices in batch, so that the binding efficiency is low.

In view of this, embodiments of the present invention provide an apparatus connection method, which implements flexible binding and unbinding between a main apparatus and a sub apparatus under an application layer, so that a binding relationship between apparatuses is more flexible, and a requirement of a variable service scenario is met; meanwhile, the technical effect that a plurality of main devices are bound, unbound or deleted in batch can be achieved.

It should be noted that the device registration refers to that the application layer registers the device to be accessed by calling the platform interface through the integrated internet of things application SDK, and only the device registered by the application layer on the platform can be activated.

Activating the equipment: the device is activated by configuring a device identifier in device registration to connect with the platform, and the device can communicate with the Internet of things platform only after being activated.

And (3) SDK: is an abbreviation of Software Development Kit, and the Chinese means "Software Development Kit". The SDK provides files for application program interface for 2113 in a certain programming language.

Agent: namely, the proxy can effectively place the local service in a calling plane with the Internet of things platform through a reverse proxy channel (namely, through calling the packaged SDK), so that the Internet of things platform and the local service are linked conveniently.

EMQ: a mode of realizing communication by subscribing topics, a device end can subscribe a plurality of topics to a server through EMQ, and an 'issuing instruction' is that the device end receives corresponding topic information; the 'event reporting' is that the equipment terminal issues information on different topics.

In an embodiment, fig. 1 is a flowchart of a device connection method provided in an embodiment of the present invention, where this embodiment is applicable to a case of managing devices, and the method may be executed by a device connection apparatus in an embodiment of the present invention, and the apparatus may be implemented in a software and/or hardware manner. Wherein, this embodiment is applied to thing networking platform.

As shown in fig. 1, the method specifically includes the following steps:

and S110, receiving a device operation request sent by the master device.

The device operation request carries a master device identifier and a master device name. The main equipment identification refers to a serial number of the main equipment and is used for representing the unique identification of the main equipment; the master device name refers to the name of the master device. Of course, in actual operation, the same master device name may exist between two different master devices, but the master device identifications are different. It will be appreciated that each master device is configured with a unique master device identification. In an embodiment, the device operation request refers to a request for performing some operation on the master device. In an embodiment, the device operation request refers to a self-initiation request of the master device.

The equipment belongs to specific equipment under a certain application, can communicate with the Internet of things platform, receives an instruction issued by the application, and sends events such as measurement, alarm and the like to the application.

The main device refers to a device with the capability of accessing the internet of things, and can be a physical device or a virtual device; and when the device is created by an internet of things platform/internet of things application (also called an application layer), the selected device attribute type is 'composite device'. The main equipment is also essentially equipment, a plurality of sub-equipment can be connected under the main equipment, and the sub-equipment is connected with the Internet of things platform through the main equipment. The master device also has the capability to become a child device.

A sub-device is also a device in nature. The sub-devices do not have the capability of directly communicating with the internet of things platform, generally do not directly communicate with the internet of things platform, and receive an instruction issued by the application and report events such as measurement or alarm through the main device. The kid device does not have the capability of becoming a master kid device.

In the embodiment, when the main device is started automatically, the device SDK connected with the main device is initialized, so that communication connection with the Internet of things platform is established through the device SDK, the device operation request is sent to the Internet of things platform, and the main device logs in the Internet of things platform.

And S120, identifying and extracting a sub-device list corresponding to the main device according to the device operation request.

Wherein the list of sub-devices refers to a list containing sub-devices. One or more sub-devices may be included in the sub-device list, or no sub-device may be present. It should be noted that a mapping relationship is established between each master device and the sub-device list, that is, the corresponding sub-device list can be found according to the master device identifier. Wherein the sub-device list includes: child device identification, child device name, and metadata. In an embodiment, the sub-device identifier refers to a serial number of the sub-device, and is used to characterize a unique identifier of the sub-device; the child device name refers to the name of the child device; metadata refers to information describing the data attributes of a sub-device to support functions such as indicating storage locations, history data, resource lookups, file records, and the like.

In an embodiment, after the internet of things platform receives the device operation request, the internet of things platform executes a device login operation; after the operation is finished, judging whether the equipment is logged in successfully; if the device logs in successfully, the SDK judges whether the main device is activated on the Internet of things platform or not; if the main equipment is successfully logged in and activated, the Internet of things platform searches the sub-equipment list corresponding to the main equipment identification from the storage space.

S130, feeding back the sub-device list to the main device, so that the main device updates the local device list according to the sub-device list.

The local device list refers to a sub-device list stored locally by the main device. In an embodiment, the internet of things platform returns the sub-device list to the main device through the device SDK, so that the main device updates the local sub-device list of the main device according to the sub-device list, and performs list maintenance.

According to the technical scheme of the embodiment, the equipment operation request sent by the main equipment is received; the equipment operation request carries a main equipment identifier and a main equipment name; identifying and extracting a sub-equipment list corresponding to the main equipment according to the equipment operation request; and feeding back the sub-device list to the main device so that the main device updates the local device list according to the sub-device list. The application layer of the embodiment of the invention is accessed to the platform of the Internet of things in a mode of integrating the application SDK, thereby realizing the functions of equipment management, equipment reporting data receiving, instruction issuing and the like.

In an embodiment, fig. 2 is a flowchart of another device connection method provided in an embodiment of the present invention. This embodiment is further described with reference to the above embodiments. As shown in fig. 2, the device connection method of the present embodiment includes the following steps:

s210, receiving a device operation request sent by the main device.

The device operation request carries a master device identifier and a master device name.

And S220, determining the activation state of the main equipment on the platform of the Internet of things.

The activation state refers to whether the master device is activated on the platform of the Internet of things; if the main equipment is activated on the Internet of things platform, the activation state is activated; and if the main equipment is not activated on the Internet of things platform, the activation state is not activated. In an embodiment, after the main device successfully logs in the internet of things platform, the device SDK determines whether the main device is activated on the internet of things platform, and if so, executes S260; if not, go to step S230.

And S230, receiving a device activation application request sent by the main device.

In an embodiment, when the master device is not activated on the internet of things platform, the master device automatically sends a device activation application request to the internet of things platform through the device SDK. The equipment activation application request is used for applying request information for activating the main equipment to the platform of the Internet of things.

S240, activating the main equipment according to the equipment activation application request and generating an activation notice.

After the main device is successfully activated on the Internet of things platform, the Internet of things platform automatically generates an activation notification.

And S250, returning the activation notification to the main equipment.

In the embodiment, the Internet of things platform listens to the device SDK and feeds back the activation notification to the main device; and after the device SDK receives the activation notification meeting, the login success notification is sent to the corresponding main device.

And S260, identifying and extracting a sub-device list corresponding to the main device according to the device operation request.

In an embodiment, when the main device successfully logs in the internet of things and is activated, the internet of things platform finds the corresponding sub-device list according to the main device identifier carried in the device operation request.

And S270, feeding back the sub-device list to the main device so that the main device updates the local device list according to the sub-device list.

According to the technical scheme, the communication connection between the main device and the Internet of things platform is established through the SDK, so that the main device maintains all the sub-devices under the main device, and the communication connection between the sub-devices is maintained through the Internet of things platform.

In an embodiment, fig. 3 is a flowchart of another device connection method provided in an embodiment of the present invention. The present embodiment is to explain a device binding process based on the above embodiments. As shown in fig. 3, the device connection method in this embodiment includes the following steps:

s310, receiving a device operation request sent by the main device.

And S320, identifying and extracting a sub-device list corresponding to the main device according to the device operation request.

S330, feeding back the sub-device list to the main device so that the main device updates the local device list according to the sub-device list.

S340, receiving a device binding request which is sent by the main device and carries the father device identification and the son device identification.

Wherein, the device binding request refers to a binding request between the sub-device and the main device. In an embodiment, the device binding request carries a parent device identifier and a child device identifier, so that the internet of things platform can directly know the connection relationship between the parent device and the child device according to the fact that the device receives the device binding request. The main device sends a device binding request to the Internet of things platform through the device SDK.

And S350, inquiring the corresponding sub-equipment activation state according to the equipment binding request.

The activation state of the sub-device refers to the activation state of the sub-device on the platform of the internet of things. Illustratively, the sub-device activation state includes: the child device has been activated; the kid device is not activated. In an embodiment, after the internet of things platform receives the device binding request, the internet of things platform queries an activation state of a sub device corresponding to the main device on the internet of things platform.

And S360, binding the main equipment and the sub-equipment according to the activation state of the sub-equipment.

In the embodiment, under the condition that the activation state of the sub-device corresponding to the main device is activated, the internet of things platform performs device binding on the sub-device and the main device, so that the purpose of maintaining the binding relationship between the main device and the sub-device through the internet of things platform is achieved.

Of course, it should be noted that S340-S360 may be executed before S310 or after S330, which is not limited to this, and only needs to ensure that the master device is successfully logged in and activated on the internet of things platform.

In an embodiment, fig. 4 is a flowchart of a further device connection method according to an embodiment of the present invention. In this embodiment, a process of unbinding a device is described on the basis of the above embodiment. As shown in fig. 4, the device connection method in this embodiment includes the following steps:

and S410, receiving a device operation request sent by the main device.

And S420, identifying and extracting a sub-device list corresponding to the main device according to the device operation request.

And S430, feeding back the sub-device list to the main device so that the main device updates the local device list according to the sub-device list.

S440, receiving a device unbinding request which is sent by the main device and carries the parent device identifier and the child device identifier.

The device unbinding request refers to a request for releasing the binding relationship between the main device and the sub-device. In an embodiment, the device unbinding request carries a parent device identifier and a child device identifier, so that the internet of things platform can directly know the connection relationship between the parent device and the child device according to the fact that the device unbinding request is received by the device. The main device sends a device unbinding request to the Internet of things platform through the device SDK.

S450, according to the equipment unbinding request, the main equipment and the sub-equipment are unbound.

In an embodiment, after the internet of things platform receives the device unbinding request, the internet of things platform performs an unbinding operation between the master device and the slave device.

And S460, generating a sub-device unbinding instruction.

In an embodiment, the child device unbinding instruction is generated after the master device and the child device are successfully unbound.

And S470, feeding back the sub-equipment unbinding instruction to the main equipment.

In an embodiment, the device SDK feeds back to the master device via the device unbinding instruction, so that the master device updates the local device list and simultaneously notifies the master device that the child device has been unbound; meanwhile, the main device feeds back a command receipt to the Internet of things through the device SDK to reply that the Internet of things platform has received the device unbinding request, so that the unbinding relation between the main device and the sub-device is realized through the Internet of things platform.

Of course, it should be noted that S440-S470 may be executed before S410 or after S430, which is not limited to this, and only needs to ensure that the master device is successfully logged in and activated on the platform of the internet of things.

In an embodiment, fig. 5 is a flowchart of a further device connection method according to an embodiment of the present invention. This embodiment is to explain the process of deleting the child device on the basis of the above embodiment. As shown in fig. 5, the device connection method in this embodiment includes the following steps:

and S510, receiving a device operation request sent by the main device.

And S520, identifying and extracting a sub-device list corresponding to the main device according to the device operation request.

And S530, feeding back the sub-device list to the main device so that the main device updates the local device list according to the sub-device list.

And S540, receiving a child device deleting request which is sent by the main device and carries the parent device identification and the child device identification.

The sub-device deleting request refers to a request for deleting the sub-device from the platform of the internet of things. In an embodiment, the child device deletion request carries the parent device identifier and the child device identifier, so that the internet of things platform can directly know the connection relationship between the parent device and the child device according to the fact that the device receives the child device deletion request. The main device sends a sub-device deleting request to the Internet of things platform through the device SDK.

And S550, unbinding the main device and the sub-device according to the sub-device deleting request.

For the explanation of S550, reference may be made to the description of S450 in the above embodiment, which is not described herein again.

And S560, generating a sub-device unbinding instruction.

For the explanation of S560, reference may be made to the description of S550 in the above embodiment, which is not repeated herein.

And S570, feeding back the sub-device unbinding instruction to the main device so as to disconnect the main device from the sub-device.

In an embodiment, the device SDK feeds back to the master device via the device unbinding instruction, so that the master device updates the local device list and simultaneously notifies the master device that the child device has been unbound; meanwhile, the main device feeds back a command receipt to the Internet of things through the device SDK to reply that the Internet of things platform has received the device unbinding request, so that the unbinding relation between the main device and the sub-device is realized through the Internet of things platform. After the main device receives the sub-device unbinding instruction and completes the binding relationship with the sub-device, the main device disconnects the connection relationship with the sub-device.

Of course, it should be noted that S540-S570 may be executed before S510, or may be executed after S530, which is not limited to this, and it is only required to ensure that the master device is successfully logged in and activated on the internet of things platform.

In an embodiment, fig. 6 is a flowchart of a further device connection method according to an embodiment of the present invention. The present embodiment is to explain a message transmission process based on the above embodiments. As shown in fig. 6, the device connection method in this embodiment includes the following steps:

s610, receiving a device operation request sent by the master device.

And S620, identifying and extracting a sub-device list corresponding to the main device according to the device operation request.

S630, feeding back the sub-device list to the main device, so that the main device updates the local device list according to the sub-device list.

And S640, receiving a message transmission request which is sent by the main equipment and carries the parent equipment identification and the child equipment identification.

The message transmission request refers to a request for data transmission between the master device and the slave device. Wherein, according to different types of the devices, the communication protocol between the sub-device and the main device is different. The communication protocol between the master device and the slave device may include: bluetooth, WiFi, http, etc. In the embodiment, the sub-device sends a message transmission request to the main device, and the main device sends the message transmission request to the internet of things platform through the device SDK after receiving the message transmission request.

S650, determining the existence condition of the sub-equipment corresponding to the sub-equipment identification in the message transmission request.

In an embodiment, after the internet of things platform receives the message transmission request, whether the sub-device corresponding to the sub-device identifier in the message transmission request exists in the internet of things platform is judged by querying a local sub-device list.

And S660, when the sub-equipment corresponding to the sub-equipment identification exists in the Internet of things platform, sending the message transmission request to an application layer.

In an embodiment, when the sub-device corresponding to the sub-device identifier exists on the internet of things platform, the internet of things platform sends the message sent by the sub-device to the application layer to which the sub-device belongs, so that message transmission between the sub-device and the main device is achieved through the internet of things platform and the application layer.

In an embodiment, fig. 7 is a flowchart of a further device connection method according to an embodiment of the present invention. In this embodiment, a process of deleting the master device is described on the basis of the above embodiments. As shown in fig. 7, the device connection method in this embodiment includes the following steps:

and S710, receiving a device operation request sent by the main device.

S720, identifying and extracting a sub-device list corresponding to the main device according to the device operation request.

And S730, feeding back the sub-device list to the main device so that the main device updates the local device list according to the sub-device list.

And S740, receiving a main equipment deleting request which is sent by the main equipment and carries the main equipment identification.

The main equipment deleting request refers to a request for deleting the main equipment from the platform of the internet of things. In an embodiment, the main device identifier is carried in the main device deletion request, so that the internet of things platform can directly know the main device executing the device deletion according to the fact that the device receives the main device deletion request. The main device sends a main device deleting request to the Internet of things platform through the device SDK.

And S750, determining whether the main equipment corresponding to the main equipment identification has the bound sub-equipment.

In the embodiment, after the internet of things receives a main device deleting request, whether a bound sub device exists under the main device is judged.

S760, when the bound sub-equipment exists in the main equipment, returning an error prompt to the main equipment, or deleting/unbinding the sub-equipment, and executing main equipment deleting operation.

When the bound sub-equipment exists in the main equipment, the platform of the internet of things returns an error prompt: and the sub-equipment is arranged below the main equipment, and after the corresponding sub-equipment is deleted or unbound, the main equipment deleting operation is executed, and the process is ended.

And S770, when the bound sub-device does not exist in the main device, executing a main device deleting operation.

When no bound sub-device exists under the main device, the Internet of things platform deletes the main device on the Internet of things platform; and generating an instruction for deleting the main equipment, and sending the instruction to the equipment SDK. After the device SDK receives the instruction, deleting the main device, replying to the Internet of things platform, and ending the process after receiving the request of deleting the main device; and notifying the main device that the device is deleted and the process is finished; and disconnecting the communication connection of the EMQ between the equipment SDK and the Internet of things platform, and ending the process.

In an embodiment, when the number of the child devices in the local device list of the master device is less than the number of the child devices in the local device list of the internet of things platform, the method further includes: and sending a data issuing instruction to the main equipment so that the main equipment updates the local equipment list of the main equipment according to the local equipment list of the Internet of things platform. In an embodiment, when the number of the sub-devices in the local device list of the master device is smaller than the number of the sub-devices in the local device list of the internet of things platform, the local device list of the master device is updated by using the number of the sub-devices in the local device list of the internet of things platform as a criterion.

In an embodiment, fig. 8 is a flowchart of a further device connection method according to an embodiment of the present invention. The present embodiment is applied to a master device. As shown in fig. 8, the device connection method in the present embodiment includes S810 to S830.

And S810, sending an equipment operation request to the Internet of things platform.

And S820, receiving the sub-device list fed back by the Internet of things platform.

And S830, updating the local equipment list according to the sub-equipment list.

In the embodiment, the main device sends a device operation request to the internet of things platform through the device SDK, so that the internet of things platform identifies and extracts a sub-device list corresponding to the main device according to the device operation request, returns the sub-device list to the main device, and after the main device receives the fed back sub-device list, the main device updates the local device list according to the sub-device list.

In an embodiment, fig. 9 is a flowchart of an automatic start of a master device according to an embodiment of the present invention. As shown in fig. 9, the process of automatically starting the master device in this embodiment includes the following steps:

step one, initializing a device SDK when the main device is self-started (for example, calling the SDK to log in when an agent is initialized), establishing communication between the main device and the Internet of things platform through the device SDK, and logging in the device.

And step two, the Internet of things platform executes equipment login operation, and enters a judging link after the operation is finished.

Step three, a judging link of the Internet of things platform: if the main equipment is successfully logged in, entering the step four; if the main device fails to log in, the device SDK informs the main device that the login fails, the main device receives the message that the login result fails, and the process is finished.

Step four, after the main device successfully logs in, the device SDK enters the next judging link: whether the main equipment is activated on the Internet of things platform or not, if so, entering a fifth step; if the device is not active, step seven is entered.

Step five: and the device SDK updates the local sub-device list of the main device according to the sub-device list (including the ID, the name and the metadata of the sub-device) of the main device returned by the platform of the Internet of things and maintains the list.

It should be noted that, when the primary device logs in and is not activated for the first time, the internet of things platform does not return to the sub-device list.

Step six: and after the maintenance of the sub-device list is finished, the SDK informs the main device that the login is successful.

Step seven: the method comprises the steps that the main device is not activated, the device SDK automatically applies for activating the device to the Internet of things platform, the main device returns the device SDK to inform that activation is successful after the Internet of things platform is successfully activated, and the device SDK sends a login success notice to the main device after receiving the notice.

In an embodiment, fig. 10 is an interface display schematic diagram of an apparatus for adding a binding child according to an embodiment of the present invention. As shown in fig. 10, an "add" button may be clicked on a display interface of the internet of things platform to pop up a display interface of the device information, so as to query whether the sub-device information to be added exists in the sub-device list on the display interface of the device information, and if so, no adding and binding operation is performed; and if not, executing the binding adding operation.

The process of adding the binding sub-device in the embodiment includes the following steps:

the method comprises the following steps: a user initiates a binding request (binding parameters: parent equipment ID and child equipment ID) to an Internet of things platform on a display interface of the Internet of things platform;

or the application to which the master device belongs initiates a request for binding (binding parameters: parent device ID, child device ID), and the request for the application is sent to the internet of things platform through the application SDK.

Step two: and after receiving the binding request, the Internet of things platform inquires the activation state of the sub-equipment and binds the equipment on the Internet of things platform. And generating a sub-device binding instruction, and issuing the instruction and the activation state of the sub-device to the device SDK.

Step three: after receiving the sub-device binding instruction of the Internet of things platform and the activation state of the sub-devices, the device SDK updates a local sub-device list of the main device, and meanwhile, the main device sends a command receipt to the Internet of things platform to inform the Internet of things platform that a binding application request is received, and the process is ended; and informing the main device that the binding of the sub-device and the activation state of the sub-device are added, and entering the step four.

Step four: after the main device receives the notification of adding the sub-device binding, if the sub-device is activated, the process is ended; and if the sub-equipment is not activated, the main equipment applies for activating the sub-equipment to the Internet of things platform through the SDK, and the step five is carried out.

Step five: the device SDK forwards the application for activating the sub-device to the Internet of things platform, the Internet of things platform activates the sub-device and returns a result for activating the sub-device to the device SDK; if the Internet of things platform is successfully activated, returning a sub-device activation notification to the device SDK; entering the step six for the metadata of the sub-equipment; and if the Internet of things platform fails to be activated, returning a notification of the failure of the activation of the equipment to the SDK, and entering the seventh step.

Step six: after receiving the result of the activation of the child device: and issuing the metadata to the main equipment according to the metadata of the sub-equipment returned by the platform, and informing the sub-equipment by the main equipment. And simultaneously, sending the message of successful activation of the sub-equipment to the main equipment, and ending the process.

Step seven: after the activation of the main equipment fails, the platform returns the result of the activation failure to the equipment SDK, and the main equipment receives the prompt information: manual reactivation is required and the process ends.

Fig. 11 is a schematic interface display diagram for releasing the binding relationship between the master device and the child device according to the embodiment of the present invention. As shown in fig. 11, a "delete" button may be clicked on a display interface of the internet of things platform to pop up a display interface on which whether to determine to unbind the sub-device, and if "unbind" is clicked, the binding relationship between the main device and the sub-device is released; and if the 'cancel' is clicked, the binding relationship between the main equipment and the sub-equipment is not removed.

Fig. 12 is a flowchart of releasing a binding relationship between a master device and a slave device according to an embodiment of the present invention. As shown in fig. 12, the process of releasing the binding relationship between the master device and the child device in this embodiment includes the following steps:

the method comprises the following steps: a user initiates a main device unbinding sub-device request (unbinding parameters: parent device ID and sub-device ID) to the Internet of things platform on a display interface of the Internet of things platform;

or the application to which the main device belongs initiates a request for unbinding the sub-device, and the request for the application is sent to the internet of things platform through the application SDK.

Step two: after the Internet of things platform receives the message for applying for unbinding, the sub-equipment is unbound on the Internet of things platform; and generating a sub-device unbinding instruction and sending the instruction to the device SDK.

Step three: and after the SDK receives the sub-equipment unbinding instruction of the Internet of things platform, updating a local sub-equipment list of the main equipment, and simultaneously informing the equipment end that the sub-equipment is unbound, and ending the process. And meanwhile, the SDk of the equipment receives the command receipt and replies that the platform of the Internet of things has received the unbinding request, and the process is finished.

Fig. 13 is a schematic interface display diagram of a deletion sub-device according to an embodiment of the present invention. As shown in fig. 13, a "delete" button may be clicked on the display interface of the internet of things platform to pop up a display interface on which whether to determine to unbind the child device, and if "delete" is clicked, the child device is deleted; if "cancel" is clicked, the child device is not deleted.

Fig. 14 is a flowchart of deleting a child device according to an embodiment of the present invention. As shown in fig. 14, the process of deleting a child device in this embodiment includes the following steps:

the method comprises the following steps: a user sends a request for deleting the bottle opener equipment to the platform of the Internet of things on a display interface of the platform of the Internet of things;

or the application to which the master device belongs sends a request for deleting the driver device, and the request of the application is sent to the platform of the internet of things through the application SDK.

Step two: after the Internet of things platform receives the message for deletion application, the sub-equipment is deleted on the Internet of things platform; and generating a sub-device deleting instruction, and sending the instruction to the device SDK.

Step three: and after receiving the sub-device deleting instruction of the Internet of things platform, the SDK updates the local sub-device list of the main device, simultaneously informs the device end that the sub-device is deleted, disconnects the sub-device and finishes the process. And meanwhile, the SDk carries out command receipt, replies that the Internet of things platform receives the deletion request, and ends the process.

Fig. 15 is a flowchart of sending a message to an internet of things platform by a piece of sub-equipment according to an embodiment of the present invention. As shown in fig. 15, the process of sending a message to the internet of things platform by the child device in this embodiment includes the following steps:

the communication protocols of the sub-device and the main device are different according to the types of the devices, and most of the currently adopted protocols include: bluetooth, wife, http, etc. The specific flow of the sub-device sending the message to the platform/application through the main device is as follows:

the method comprises the following steps: the sub-device sends a message transmission request to the main device, and the main device sends request data to the SDK/agent after receiving the data.

Step two: after receiving the message, the device SDK determines by querying a local list of child devices: whether the child device is present; if the sub-equipment exists, entering a step three; and if the sub-equipment does not exist, entering the step four.

Step three: the sub-device exists, and the device SDK sends a message application to the Internet of things platform.

Step four: after the Internet of things platform receives the request, inquiring whether the equipment exists or not by comparing the data of the Internet of things platform; if the Internet of things platform judges that the equipment exists, the Internet of things platform sends the information sent by the equipment to the application to which the equipment belongs, and the process is ended; and if the Internet of things platform judges that the equipment does not exist, entering a fifth step.

Step five: the sub-equipment does not exist, the Internet of things platform returns an error prompt to the equipment end, and the process is finished.

In one embodiment, the process of deleting the master device includes the following steps:

the method comprises the following steps: a user initiates a request for deleting the main equipment to the Internet of things platform on an Internet of things platform interface; or the application of the main equipment initiates a request for deleting the main equipment, the request of the application is sent to the platform of the Internet of things through the application SDK,

step two: after receiving the message for applying for deleting the master equipment, the Internet of things platform enters a judging link: whether the bound sub-equipment exists under the main equipment or not; the judgment is as follows: if the sub-equipment exists, entering the step five; and judging whether: if no sub-equipment exists, the step three is carried out.

Step three: the method comprises the following steps that no sub-device exists under the main device, and the main device is deleted at a server side by the Internet of things platform; and generating an instruction for deleting the main equipment, and sending the instruction to the equipment SDK.

Step four: after receiving the instruction, the device SDK deletes the main device, and: and replying to the Internet of things platform, and ending the process after the request for deleting the main equipment is received. And simultaneously, informing the main equipment that the equipment is deleted, and ending the process. And simultaneously, disconnecting the communication connection of the EMQ between the SDK and the Internet of things platform, and ending the process.

Step five: if the sub-equipment is arranged below the main equipment, the Internet of things platform returns an error prompt: and (4) the sub-equipment is arranged below the main equipment, and after the sub-equipment is deleted/unbound, the main equipment deleting operation is executed, and the process is ended.

Fig. 16 is a flowchart of updating a local device list of a master device according to an embodiment of the present invention. As shown in fig. 16, the update process of the local device list of the master device in this embodiment includes:

in this embodiment, extreme conditions (such as device failure, network failure, etc.) that may occur result in: when the platform issues data, the number of the equipment terminal devices is found to be smaller than the number of the service terminal devices, and the following implementation scheme is implemented:

and updating the sub-equipment list of the equipment end by taking the sub-equipment list of the service end as a criterion. Because the process is clear, the detailed description of the steps is not repeated here, and the process is shown in fig. 16.

In actual life, each website of thing networking in the row is used extensively to the bluetooth bracelet that the website staff used is the example: this bluetooth bracelet is the thing of in-line website staff wearing allies oneself with equipment, and the thing allies oneself with and uses "website management center" management and control. The gateway equipment of the network A is set as main equipment a, and a Bluetooth bracelet worn by the network staff is set as sub-equipment (i). After the sub-equipment (i) is bound with the main equipment (a), the on-duty data of the staff can be collected and the business notification message can be issued to the staff through the Bluetooth bracelet, so that the performance management and control of the staff and the operation management of a network point can be realized.

However, in the practical application process, the network point staff have the business requirements of shift: namely, a bluetooth bracelet sub-device of an employee needs to be unbound from a main device gateway a of a network A, and the sub-device is bound to a main device gateway B of a network B on the premise of not deleting the sub-device. The embodiment of the invention solves the business requirements of flexible binding and unbinding between the main equipment and the sub-equipment.

Fig. 17 is a schematic structural diagram of an apparatus connection device according to an embodiment of the present invention. The present embodiment is applied to a case of connecting devices, and as shown in fig. 17, the device connecting apparatus specifically includes: a first receiving module 910, an identification extraction module 920 and a first feedback module 930.

The first receiving module 910 is configured to receive a device operation request sent by a master device; the equipment operation request carries a main equipment identifier and a main equipment name;

the identification extraction module 920 is provided with a sub-device list corresponding to the main device according to the device operation request;

a first feedback module 930, configured to feed back the sub-device list to the master device, so that the master device updates the local device list according to the sub-device list.

On the basis of the above embodiment, the child device list includes: child device identification, child device name, and metadata.

On the basis of the above embodiment, the device connecting apparatus further includes:

the first determining module is used for determining the activation state of the main device on the platform of the internet of things after receiving the device operation request sent by the main device and before identifying and extracting the sub-device list corresponding to the main device according to the device operation request.

the first receiving module is used for receiving an equipment activation application request sent by the main equipment before the main equipment is not activated on the platform of the Internet of things and the sub-equipment list corresponding to the main equipment is identified and extracted according to the equipment operation request;

the activation module is used for activating the main equipment according to the equipment activation application request and generating an activation notice;

a first return module for returning the activation notification to the master device.

the second receiving module is used for receiving a device binding request which is sent by the main device and carries the father device identifier and the son device identifier;

the query module is used for querying the corresponding sub-equipment activation state according to the equipment binding request;

and the binding module is used for binding the main equipment and the sub-equipment according to the activation state of the sub-equipment.

the third receiving module is used for receiving a device unbinding request which is sent by the main device and carries the father device identifier and the child device identifier;

the first unbinding module is used for unbinding the main equipment and the sub-equipment according to the equipment unbinding request;

the first generation module is used for generating a sub-equipment unbinding instruction;

and the second feedback module is used for feeding back the sub-equipment unbinding instruction to the main equipment.

the fourth receiving module is used for receiving a child device deleting request which is sent by the main device and carries the parent device identifier and the child device identifier;

the second unbinding module is used for unbinding the main equipment and the sub-equipment according to the sub-equipment deleting request;

the second generation module is used for generating a sub-equipment unbinding instruction;

and the second feedback module is used for feeding back the sub-equipment unbinding instruction to the main equipment so as to disconnect the main equipment from the sub-equipment.

a fifth receiving module, configured to receive a message transmission request that is sent by the master device and carries a parent device identifier and a child device identifier;

the second determining module is used for determining the existence condition of the sub-equipment corresponding to the sub-equipment identification in the message transmission request;

and the first sending module is used for sending the message transmission request to the application layer when the sub-equipment corresponding to the sub-equipment identifier exists in the application of the Internet of things.

a sixth receiving module, configured to receive a master device deletion request carrying a master device identifier sent by a master device;

a third determining module, configured to determine whether a bound sub-device exists in a main device corresponding to the main device identifier;

the second returning module is used for returning an error prompt to the main equipment or deleting/unbinding the sub-equipment to execute the deleting operation of the main equipment when the bound sub-equipment exists in the main equipment;

the first execution module is used for executing the main equipment deleting operation when the main equipment does not have the bound sub-equipment.

and the second sending module is used for sending a data issuing instruction to the main equipment when the number of the sub-equipment in the local equipment list of the main equipment is smaller than that of the sub-equipment in the local equipment list of the Internet of things platform, so that the main equipment updates the local equipment list of the main equipment according to the local equipment list of the Internet of things platform.

The device connection device provided by the embodiment can execute the device connection method applied to the platform of the internet of things provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the device connection method.

Fig. 18 is a schematic structural diagram of another device connection apparatus according to an embodiment of the present invention. The present embodiment is applied to a case of connecting devices, and as shown in fig. 18, the device connecting apparatus specifically includes: a sending module 1010, a receiving module 1020, and an updating module 1030.

The sending module 1010 is configured to send a device operation request to the internet of things platform; the equipment operation request carries a main equipment identifier and a main equipment name;

a receiving module 1020, configured to receive a sub-device list fed back by the internet of things platform;

the updating module 1030 is configured to update the local device list according to the sub device list.

The device connection apparatus provided in this embodiment can execute the device connection method applied to the main device provided in any embodiment of the present invention, and has functional modules and beneficial effects corresponding to the execution of the device connection method.

Fig. 19 is a schematic structural diagram of a device connection system according to an embodiment of the present invention. The present embodiment is applied to a case of connecting devices, and as shown in fig. 19, the device connection system specifically includes: a device side 1110, an internet of things platform 1120, and an application layer 1130; wherein, the device end 1110 includes: a master device and a slave device; the sub-device and the main device belong to the same application layer 1130 and the same internet of things platform 1120;

the main device in the device end 1110 establishes communication connection with the internet of things platform 1120 through the device end SDK; the application layer 1130 establishes a communication connection with the internet of things platform 1120 in an SDK application manner.

Fig. 20 is a schematic structural diagram of another device connection system according to an embodiment of the present invention. As shown in fig. 20, the device connection system includes: the system comprises a device end, a device end Agent/SDK, an Internet of things device management platform (namely the Internet of things platform can also be called an Internet of things platform), and an Internet of things application (also can be called an application Cen).

The equipment is divided into main equipment and sub-equipment, and the conditions are as follows: the main device needs to be provided with a device agent/sdk which can communicate with the Internet of things platform; the sub-equipment needs to belong to the same application, the same site and not composite equipment as the main equipment;

the device agent/sdk can be connected with the device to communicate with the Internet of things platform;

the Internet of things platform can be connected with the equipment end and communicated with the application end;

the Internet of things application is accessed to the Internet of things platform in a mode of integrating the application SDK, and functions of equipment management, equipment reporting and instruction issuing can be achieved.

Fig. 21 is a schematic structural diagram of a device connection device according to an embodiment of the present invention. As shown in fig. 21, the apparatus connection device includes a processor 1210, a memory 1220, an input device 1230, and an output device 1240; the number of the processors 1210 in the device connection device may be one or more, and one processor 1210 is taken as an example in fig. 21; the processor 1210, memory 1220, input device, and 1230 output device 1240 in the device connection apparatus may be connected by a bus or other means, as exemplified by a bus connection in fig. 21.

The memory 1220, which is a computer-readable storage medium, may be used to store software programs, computer-executable programs, and modules, such as program modules corresponding to the device connection method in the embodiment of the present invention (e.g., the first receiving module, the identification extracting module, and the feedback module in the device connection apparatus). The processor 1210 executes various functional applications and data processing of the device-connected apparatus by executing software programs, instructions, and modules stored in the memory 1220, that is, implements the device-connecting method described above.

The memory 1220 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the memory 1220 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, the memory 1220 can further include memory located remotely from the data forwarding system 1210, which can be connected to the vehicle over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and their blocks.

The input device 1230 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the vehicle. The output device 1240 may include a display device such as a display screen.

Embodiments of the present invention also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, perform a device connectivity method, the method comprising:

receiving a device operation request sent by a master device; the equipment operation request carries a main equipment identifier and a main equipment name; identifying and extracting a sub-equipment list corresponding to the main equipment according to the equipment operation request; and feeding back the sub-device list to the main device so that the main device updates the local device list according to the sub-device list.

Of course, the storage medium containing the computer-executable instructions provided by the embodiments of the present invention is not limited to the above method operations, and may also perform related operations in the device connection method applied to the platform of the internet of things provided by any embodiment of the present invention.

The storage medium containing the computer-executable instructions provided by the embodiments of the present invention is not limited to the above method operations, and may also perform related operations in the device connection method applied to the master device provided by any embodiments of the present invention.

From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods of the embodiments of the present invention.

It should be noted that, in the embodiment of the text classification apparatus, the included units and modules are only divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments illustrated herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. The equipment connection method is applied to an Internet of things platform and comprises the following steps:

2. The method of claim 1, wherein the list of child devices comprises: child device identification, child device name, and metadata.

3. The method according to claim 1, wherein after receiving a device operation request sent by a master device, and before identifying and extracting a sub-device list corresponding to the master device according to the device operation request, further comprising:

and determining the activation state of the main equipment on the platform of the Internet of things.

4. The method according to claim 3, further comprising, before the extracting, according to the device operation request identification, the sub-device list corresponding to the master device when the master device is not activated on an internet of things platform:

receiving a device activation application request sent by a main device;

activating the main equipment according to the equipment activation application request and generating an activation notice;

returning the activation notification to the master device.

5. The method of claim 1, further comprising:

receiving a device binding request which is sent by a main device and carries a parent device identifier and a child device identifier;

inquiring the corresponding sub-equipment activation state according to the equipment binding request;

and binding the main equipment and the sub-equipment according to the activation state of the sub-equipment.

6. The method of claim 1, further comprising:

receiving a device unbinding request which is sent by a main device and carries a parent device identifier and a child device identifier;

unbinding the main equipment and the sub-equipment according to the equipment unbinding request;

generating a sub-equipment unbinding instruction;

and feeding back the sub-equipment unbinding instruction to the main equipment.

7. The method of claim 1, further comprising:

receiving a child device deleting request which is sent by a main device and carries a parent device identifier and a child device identifier;

unbinding the main equipment and the sub-equipment according to the sub-equipment deleting request;

generating a sub-equipment unbinding instruction;

and feeding back the sub-equipment unbinding instruction to the main equipment so as to disconnect the main equipment from the sub-equipment.

8. The method of claim 1, further comprising:

receiving a message transmission request which is sent by a main device and carries a father device identifier and a child device identifier;

determining the existence condition of the sub-equipment corresponding to the sub-equipment identification in the message transmission request;

and when the sub-equipment corresponding to the sub-equipment identification exists in the application of the Internet of things, sending the message transmission request to an application layer.

9. The method of claim 1, further comprising:

receiving a main equipment deleting request which is sent by main equipment and carries a main equipment identifier;

determining whether a bound sub-device exists in a main device corresponding to the main device identifier;

when the bound sub-equipment exists in the main equipment, returning an error prompt to the main equipment, or deleting/unbinding the sub-equipment, and executing main equipment deleting operation;

and when the bound sub-equipment does not exist in the main equipment, executing main equipment deleting operation.

10. The method of claim 1, wherein when the number of child devices in the local device list of the master device is less than the number of child devices in the local device list of the internet of things platform, the method further comprises:

and sending a data issuing instruction to the main equipment so that the main equipment updates the local equipment list of the main equipment according to the local equipment list of the Internet of things platform.

11. A device connection method applied to a master device includes:

receiving a sub-device list fed back by the Internet of things platform;

and updating a local equipment list according to the sub-equipment list.

12. The utility model provides an equipment connecting device which characterized in that is applied to thing networking platform, includes:

13. An apparatus connecting device, applied to a main apparatus, comprising:

14. A device connection system, comprising: the system comprises an equipment end, an Internet of things platform and an application layer; wherein, the equipment end includes: a master device and a slave device; the sub-equipment and the main equipment belong to the same application layer and the same Internet of things platform;

15. A device connection device, characterized in that the device comprises:

one or more processors;

a memory for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the device connection method of any of claims 1-11.

16. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the device connecting method according to any one of claims 1 to 11.