WO2023077922A1 - 设备连接方法、装置、电子设备和计算机可读存储介质 - Google Patents
设备连接方法、装置、电子设备和计算机可读存储介质 Download PDFInfo
- Publication number
- WO2023077922A1 WO2023077922A1 PCT/CN2022/114351 CN2022114351W WO2023077922A1 WO 2023077922 A1 WO2023077922 A1 WO 2023077922A1 CN 2022114351 W CN2022114351 W CN 2022114351W WO 2023077922 A1 WO2023077922 A1 WO 2023077922A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- information
- target application
- application program
- connection
- manufacturer
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 77
- 238000013475 authorization Methods 0.000 claims description 137
- 238000012795 verification Methods 0.000 claims description 58
- 238000004590 computer program Methods 0.000 claims description 28
- 238000010586 diagram Methods 0.000 description 10
- 238000004891 communication Methods 0.000 description 9
- 230000009286 beneficial effect Effects 0.000 description 8
- 230000006870 function Effects 0.000 description 8
- 238000012790 confirmation Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000004044 response Effects 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- G06F21/71—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information
- G06F21/73—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information by creating or determining hardware identification, e.g. serial numbers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K7/00—Methods or arrangements for sensing record carriers, e.g. for reading patterns
- G06K7/10—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation
- G06K7/14—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation using light without selection of wavelength, e.g. sensing reflected white light
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K7/00—Methods or arrangements for sensing record carriers, e.g. for reading patterns
- G06K7/10—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation
- G06K7/14—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation using light without selection of wavelength, e.g. sensing reflected white light
- G06K7/1404—Methods for optical code recognition
- G06K7/1408—Methods for optical code recognition the method being specifically adapted for the type of code
- G06K7/1417—2D bar codes
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
- G16Y10/00—Economic sectors
- G16Y10/80—Homes; Buildings
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
- G16Y20/00—Information sensed or collected by the things
- G16Y20/20—Information sensed or collected by the things relating to the thing itself
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
- G16Y40/00—IoT characterised by the purpose of the information processing
- G16Y40/30—Control
- G16Y40/35—Management of things, i.e. controlling in accordance with a policy or in order to achieve specified objectives
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Definitions
- the present application relates to the technical field of smart home, and specifically relates to a device connection method, device, electronic device, and computer-readable storage medium.
- IOT Internet of Things
- each manufacturer is independent of each other and does not perform interconnection. That is, the IoT device is generally connected through the application program (Application) set by the manufacturer of the IoT device, and cannot be connected through other Vendor apps connect IoT devices.
- Application Application
- Embodiments of the present application provide a device connection method, device, electronic device, and computer-readable storage medium, which can solve the technical problem that manufacturers cannot communicate with each other.
- An embodiment of the present application provides a device connection method applied to a terminal device, including:
- this embodiment of the present application provides a device connection method applied to a device cloud, including:
- the above-mentioned target information includes the manufacturer information of the target application program, then based on the above-mentioned manufacturer information, determine the type of cooperation between the equipment manufacturer of the IoT device and the manufacturer of the above-mentioned target application program, and the connection information corresponding to the above-mentioned cooperation type;
- the above connection information is sent to the terminal device, so that the above terminal device establishes a connection with the above Internet of Things device based on the above connection information through the above target application program.
- an embodiment of the present application provides a device connection device, which is applied to a terminal device, including:
- the first obtaining module is used to obtain the configuration information of the Internet of Things device
- a determination module configured to determine the type of cooperation between the equipment manufacturer of the above-mentioned IoT device and the manufacturer of the target application program on the above-mentioned terminal device based on the above-mentioned configuration information;
- the second obtaining module is used to obtain the connection information corresponding to the above cooperation type
- a connection module configured to establish a connection with the above-mentioned Internet of Things device based on the above-mentioned connection information through the above-mentioned target application program.
- an embodiment of the present application provides a device connection apparatus applied to a device cloud, including:
- a receiving module configured to receive target information
- a determination module configured to determine the type of cooperation between the device manufacturer and the manufacturer of the target application program based on the above vendor information if the target information includes the vendor information of the target application program;
- the sending module is configured to send the connection information corresponding to the above-mentioned cooperation type to the terminal device, so that the above-mentioned terminal device establishes a connection with the above-mentioned Internet of Things device based on the above-mentioned connection information through the above-mentioned target application program.
- the embodiment of the present application also provides an electronic device, including a processor and a memory, the memory stores a computer program, and the processor is configured to run the computer program in the memory to implement the device connection method provided in the embodiment of the present application.
- an embodiment of the present application also provides a computer-readable storage medium, the above-mentioned computer-readable storage medium stores a computer program, and the above-mentioned computer program is suitable for being loaded by a processor to execute any device provided by the embodiment of the present application. connection method.
- an embodiment of the present application further provides a computer program product, including a computer program, and when the computer program is executed by a processor, any device connection method provided in the embodiment of the present application is implemented.
- the configuration information of the IoT device is obtained first. Then based on the configuration information, determine the type of cooperation between the device manufacturer of the IoT device and the manufacturer of the target application program on the terminal device. Then obtain the connection information corresponding to the cooperation type. Finally, a connection is established with the IoT device based on the connection information through the target application.
- the cooperation type is associated with the connection information, and then different connection information can be set according to the cooperation type between the equipment manufacturer of the IoT device and the manufacturer of the target application program, so that when different target applications are used based on the connection Information and Internet of Things devices are connected in different ways, which makes the interconnection between device manufacturers and different manufacturers different, which can ensure the economic interests of device manufacturers and the security of Internet of Things devices.
- FIG. 1 is a schematic flowchart of a device connection method provided in an embodiment of the present application
- Fig. 2 is a schematic diagram of a relational table provided by an embodiment of the present application.
- Fig. 3 is a schematic diagram of another relationship table provided by the embodiment of the present application.
- Fig. 4 is a schematic diagram of a storage table provided by an embodiment of the present application.
- Fig. 5 is a schematic diagram of another storage table provided by the embodiment of the present application.
- Fig. 6 is a schematic flowchart of another device connection method provided by the embodiment of the present application.
- FIG. 7 is an interactive schematic diagram of a device connection method provided in an embodiment of the present application.
- Fig. 8 is a schematic structural diagram of a device connection device provided by an embodiment of the present application.
- Fig. 9 is a schematic structural diagram of another equipment connection device provided by the embodiment of the present application.
- FIG. 10 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
- Embodiments of the present application provide a device connection method, device, and computer-readable storage medium.
- the device connection device may be integrated in an electronic device, and the electronic device may be a server, or a terminal or other device.
- the server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, and can also provide cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication , middleware service, domain name service, security service, network acceleration service (Content Delivery Network, CDN), and cloud servers for basic cloud computing services such as big data and artificial intelligence platforms.
- cloud databases cloud computing, cloud functions, cloud storage, network services, cloud communication , middleware service, domain name service, security service, network acceleration service (Content Delivery Network, CDN), and cloud servers for basic cloud computing services such as big data and artificial intelligence platforms.
- the terminal may be a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, etc., but is not limited thereto.
- the terminal and the server may be connected directly or indirectly through wired or wireless communication, which is not limited in this application.
- FIG. 1 is a schematic flowchart of a device connection method provided by an embodiment of the present application.
- the device connection methods may include:
- the way to obtain the configuration information of the IoT device can be: store the configuration information of the IoT device in a QR code, and then scan the graphic code through the target application program (the graphic code can be a QR code or a bar code), and the terminal device thus Obtain the configuration information of the IoT device.
- the method of obtaining the configuration information of the IoT device may also be: the short-range communication information broadcast by the IoT device includes the configuration information, and when the IoT device broadcasts, the terminal device can scan the configuration information.
- Near field communication information includes but not limited to Bluetooth information, SoftAp information, near field communication (Near Field Communication, NFC) information.
- the way to obtain the configuration information of the IoT device can also be: the IoT device broadcasts short-range communication information, the short-range communication information includes the device information of the IoT device, and after the terminal device scans the device information, it sends the information from the public server (The public server can be a blockchain, for example) to find the configuration information corresponding to the device information, and the terminal device can obtain the configuration information of the IoT device.
- the public server can be a blockchain, for example
- the user can choose according to the actual situation, which is not limited in this application.
- Configuration information includes but is not limited to device information of IoT devices, device manufacturers, device cloud addresses, relationship tables between device manufacturers and other manufacturers, etc.
- the relationship table includes the type and type of cooperation between device manufacturers and other manufacturers corresponding connection information.
- the terminal device After the terminal device obtains the configuration information of the IoT device, if the configuration information is obtained by scanning the QR code through the target application program, the terminal device can automatically determine the device manufacturer of the IoT device based on the configuration information, and match the target The type of cooperation between the vendors of the application. If the configuration information is obtained by the terminal device through scanning, the terminal device may present the scanned configuration information to the user for confirmation by the user. After receiving the confirmation instruction from the user, the terminal device then determines the type of cooperation between the device manufacturer of the IoT device and the manufacturer of the target application program on the terminal device based on the confirmed configuration information.
- the relationship table can be stored in the file of the target application program, and the terminal device can obtain the relationship table from the file of the target application program after downloading the target application program.
- the terminal device After receiving the configuration information, the terminal device looks up the cooperation type between the device manufacturer and the target application program manufacturer from the relationship table based on the device manufacturer in the configuration information.
- the terminal device can send the vendor information of the target application to the device cloud according to the address, so that the device cloud can determine the vendor's relationship between the device vendor of the IoT device and the target application based on the vendor information. cooperation type.
- the target application is an application designed by another vendor.
- the device manufacturer of the IoT device is manufacturer A
- the application program configured by manufacturer A for the IoT device is the original application program.
- the target application program can be the application program designed by manufacturer B. manufacturer.
- the device manufacturer may set it based on the cooperation relationship with each manufacturer, which is not limited in this application.
- the terminal device After determining the cooperation type, the terminal device looks up the connection information corresponding to the cooperation type from the relationship table.
- the terminal device sends the vendor information of the target application program to the device cloud based on the address, so that the device cloud can determine the cooperation type between the device manufacturer of the IoT device and the target application program manufacturer based on the vendor information, the terminal device receives the information returned by the device cloud The connection information corresponding to the cooperation type.
- the relationship table stores the cooperation type between the equipment manufacturer of the IoT device and each manufacturer and the connection information corresponding to the cooperation type, for example, as shown in Figure 2, after obtaining the configuration information, the terminal device first searches for the relationship Whether the device manufacturer exists in the table, and if so, then search the cooperation type between the manufacturer of the target application program and the device manufacturer from the relationship table, and finally find the connection information corresponding to the cooperation type.
- Connection information for different cooperation types may be different. Because the types of cooperation are different and the connection information is different, the way of interconnection between equipment manufacturers and various manufacturers is different, so as to ensure the economic interests of equipment manufacturers and the security of IoT devices.
- the connection information is the information indicating the manner in which the terminal device connects to the IoT device. For example, if the device manufacturer does not have a cooperative relationship with the manufacturer of the target application program, at this time, the cooperation type can be set to the guarantee type, and the connection information can be the information prompting to download the original application program of the IoT device, that is, the terminal device needs to pass the The original application establishes a connection with the IoT device.
- the cooperation type can be set to normal, and the connection information can be the information prompting to enter the account and password corresponding to the device cloud, that is, at this time, the terminal device connects to the device cloud
- the corresponding account and password are bound to the target application, and then the connection with the IoT device needs to be established through the original application.
- equipment manufacturers can produce more kinds of IoT devices, in order to further ensure the economic interests of equipment manufacturers, equipment manufacturers can communicate with other manufacturers based on a specific type of IoT equipment, that is, according to the The model or serial number sets the type of cooperation between the device manufacturer and other manufacturers.
- the relationship table also includes device information of the IoT device.
- the terminal device After the terminal device obtains the configuration information, it can first search whether there is a device manufacturer in the configuration information from the relationship table, and if it exists, it can then search for the manufacturer of the target application program and the device manufacturer on the IoT device based on the device information. Cooperation type, and finally find the connection information corresponding to the cooperation type.
- the device manufacturer is manufacturer A
- the device information is model 1.
- the terminal device After the terminal device obtains the configuration information, it searches whether there is a manufacturer A in the relationship table. If there is a manufacturer A, it searches for the target application The type of cooperation between manufacturer A and manufacturer A on model 1, and finally find the connection information corresponding to the cooperation type.
- Device information includes, but is not limited to, the device model and device serial number.
- the terminal device After receiving the connection information, the terminal device establishes a connection with the IoT device through the target application program based on the connection information, so that the IoT device can be controlled through the target application program.
- the configuration information of the IoT device is obtained first. Then based on the configuration information, determine the type of cooperation between the device manufacturer of the IoT device and the manufacturer of the target application program on the terminal device. Then obtain the connection information corresponding to the cooperation type. Finally, a connection is established with the IoT device based on the connection information through the target application.
- the cooperation type is associated with the connection information, and then different connection information can be set according to the cooperation type between the equipment manufacturer of the IoT device and the manufacturer of the target application program, so that when different target applications are used based on the connection Information and Internet of Things devices are connected in different ways, which makes the interconnection between device manufacturers and different manufacturers different, which can ensure the economic interests of device manufacturers and the security of Internet of Things devices.
- the configuration information includes an address of a device cloud, which is a server of an IoT device.
- determine the type of cooperation between the equipment manufacturer of the IoT device and the manufacturer of the target application program on the terminal device including:
- the device cloud sends the vendor information of the target application program to the device cloud according to the address, so that the device cloud determines the type of cooperation between the device vendor of the IoT device and the vendor of the target application program based on the vendor information, and the connection information corresponding to the cooperation type.
- Obtaining the connection information corresponding to the cooperation type includes: receiving the connection information corresponding to the cooperation type returned by the device cloud.
- the terminal device After the terminal device obtains the configuration information of the IoT device, if the configuration information is obtained by scanning the QR code of the target application program, the terminal device can automatically send the manufacturer information of the target application program to the device cloud according to the address. If the configuration information is obtained by the terminal device through scanning, the terminal device may present the scanned configuration information to the user for confirmation by the user. After receiving the confirmation instruction from the user, the terminal device sends the vendor information of the target application program to the device cloud according to the address.
- the detailed method for the terminal device to send the vendor information of the target application program to the device cloud according to the address may be as follows: the terminal device sends a URL request to the device cloud according to the address, and the vendor information of the target application program may exist in the URL request in the form of URL parameters , or, the vendor information of the target application can be included in the header of the URL request (HTTP Header).
- the device cloud Since the device cloud stores the cooperation type between the equipment manufacturer of the IoT device and each manufacturer and the connection information corresponding to the cooperation type, for example, as shown in Figure 4, after receiving the manufacturer information, the device cloud stores the information in the storage table Look up the manufacturer corresponding to the manufacturer information, that is, the manufacturer of the target application program, and then find out the cooperation type between the manufacturer of the target application program and the device manufacturer.
- the device cloud After the device cloud queries the cooperation type, it searches for the connection information corresponding to the cooperation type, and returns the connection information to the terminal device.
- the address of the device cloud may be a uniform resource locator (Uniform Resource Locator, URL).
- URL Uniform Resource Locator
- What the device cloud returns to the terminal device may be an HTML page, and the HTML page carries connection information.
- the server of the IoT device can be a server specially established for the IoT device by the device manufacturer of the IoT device, or it can be a server of the device manufacturer of the IoT device. At this time, the server can be a variety of IoT devices. device server.
- the configuration information includes device information of the IoT device.
- the device cloud sends the vendor information of the target application program to the device cloud according to the address, so that the device cloud can determine the type of cooperation between the device vendor of the IoT device and the vendor of the target application program based on the vendor information, including:
- the device cloud can determine the cooperation type between the device manufacturer of the IoT device and the manufacturer of the target application program, and the connection corresponding to the cooperation type based on the manufacturer information and device information information.
- the device cloud can first find out whether there is cooperation with the vendor corresponding to the vendor information, and then find out the device information corresponding to the vendor. cooperation type.
- the manufacturer information is manufacturer B
- the device information is model 1.
- the device cloud After receiving the manufacturer information and device information of the target application, the device cloud will check whether there is manufacturer B in the storage table. , and then find out that the type of cooperation between the device manufacturer and B manufacturer on model 1 is guaranteed. At this time, the device cloud returns the connection information 1 to the terminal device.
- connection information is information prompting to download the original application program corresponding to the IoT device (in this case, the cooperation type may be guaranteed)
- establish a connection with the IoT device based on the connection information through the target application program Can include:
- the way to share the authorization information of the IoT device to the target application program through the original application program can be as follows: the user opens the target application program, and then manually enters the authorization information on the page of the target application program, and the target application program obtains the authorization information .
- the way to share the authorization information of the IoT device to the target application program through the original application program can also be: the original application program stores the authorization information in the graphic code, and then scans the graphic code through the target application program, and the terminal device thus passes The target application obtains authorization information.
- the authorization information includes limited to an identification code (Personal Identification Number, PIN), device manufacturer and device information, and so on.
- the terminal device After the terminal device obtains the authorization information through the target application program, it uses the target application program to search for the IoT device based on the device information in the authorization information, and after finding the IoT device corresponding to the device information, the terminal device then uses the target application program based on the identification code and IoT devices establish connections. It should be noted that the IoT device can verify the identification code, and when the verification is passed, the IoT device establishes a connection with the terminal device.
- the terminal device can also send the information of the LAN to the IoT device.
- the terminal device may be required to download the original application program corresponding to the IoT device.
- connection information is information prompting to input the account number and password corresponding to the device cloud (in this case, the cooperation type may be common)
- establishing a connection with the IoT device through the target application based on the connection information may include:
- the terminal device may be required to bind the account and password corresponding to the target application program and the device cloud.
- the device cloud may verify the account and password using OAuth2 technology after receiving the account and password.
- the device cloud After the device cloud has passed the verification of the account and password, it can also perform HTTPS authentication on the terminal device, and the terminal device can also perform HTTPS authentication on the device cloud, that is, HTTPS two-way authentication is performed at this time to further ensure security.
- the terminal device can find out the reason for the connection failure, prompt the reason for the connection failure, and return to execute the target application to the device cloud according to the address.
- the vendor information of the program is not limited to the vendor information of the program.
- the terminal device After the terminal device establishes a connection with the IoT device through the target application program, it can send the device information and user information of the IoT device to the device cloud based on the account to realize the synchronization of user information.
- the cooperation type when the cooperation relationship between the device manufacturer and the target application manufacturer is relatively close (for example, when the cooperation type is advanced or the highest level), the cooperation type may be stored in the server of the target application.
- sending the vendor information of the target application program to the device cloud according to the address may include: first searching for the cooperation type between the device vendor corresponding to the address and the vendor of the target application program from the server of the target application program. If the cooperation type is not found, send the vendor information of the target application to the device cloud according to the address.
- the terminal device can send a verification request to the server of the target application program, and the server of the target application program then sends the verification request to the device cloud for identity verification, and receives the authorization information returned by the device cloud when the verification is passed.
- the server of the target application then sends the authorization information to the terminal device.
- the terminal device thus receives the authorization information, and finally establishes a connection with the IoT device based on the authorization information through the target application program.
- the process of cooperation between the device manufacturer corresponding to the address in the server of the target application program and the manufacturer of the target application program can be: send the address to the server of the target application program, and after the server receives the address, query the device manufacturer corresponding to the address and the target application program The partnership type of the application's vendor.
- the server of the target application can also directly generate a verification request, and send the verification request to the device cloud for identity verification, without waiting for the verification request sent by the terminal device, and receive the verification request from the device The authorization information returned by the cloud when the verification is passed.
- the server of the target application program may refer to a server specially set up by the manufacturer of the target application program for the target application program, or may be a server of the manufacturer of the target application program, and the server of the manufacturer of the target application program may be servers of various target application programs.
- the server of the target application program needs to be controlled by the device cloud, that is, the identity of the device cloud to the server of the target application program before connecting (that is, to verify the identity of the manufacturer of the target application) for verification, and if the verification is passed, the device cloud will return the authorization information to the server of the target application.
- a request for obtaining offline authorization information is sent to the server of the target application program, and the offline authorization information is the authorization information signed by the device cloud using a private key.
- the private key and public key may be the private key and public key of the device cloud.
- the Internet of Things device uses the public key to verify the authorization information, you can also check whether the identification code in the offline authorization information is consistent with its own identification code and/or whether the device information in the offline authorization information is consistent with its own device information. Consistent, if consistent, then establish a connection with the target application.
- the server of the target application program can be separated from the control of the device cloud, that is, the device cloud first sends the offline authorization information to the target application program. stored in the server.
- the server of the target application program returns the offline authorization information after receiving the acquisition request sent by the terminal device.
- the IoT device can periodically query the device cloud whether the offline authorization information is invalid. If it is invalid, the target application program will not respond to the control command sent by the terminal device, and the reason for the non-response will be Return to the terminal device.
- the terminal device may also directly send a request to the server of the target application program. After receiving the request, the server of the target application checks whether there is offline authorization information locally. If not, the server of the target application sends a verification request to the device cloud. If offline authorization information exists, the offline authorization information is directly returned to the terminal device.
- the method further includes: sending a control command to the IoT device based on the connection through the target application program, so that the IoT device executes an operation corresponding to the control command.
- the IoT device can execute the operation corresponding to the control instruction received through the connection.
- this embodiment provides another device connection method.
- description will be made from the perspective of the device connection apparatus.
- the device connection apparatus may specifically be integrated in the device cloud. The following will take the device cloud as the execution subject for detailed description.
- FIG. 6 is a schematic flowchart of a device connection method provided by an embodiment of the present application.
- the device connection methods may include:
- the target information includes, but is not limited to, vendor information, verification request, and authorization information of the target application program.
- the target information may be sent by the terminal device to the device cloud, and the device cloud receives the target information.
- the verification request may be sent by the server of the target application program to the device cloud, and the device cloud receives the target information. If the target information includes a verification request, the verification request may be directly generated by the server of the target application program and sent to the device cloud when the cooperation type is queried, or the verification request may be In cooperation type, the terminal device sends the verification request to the server of the target application program, and the server of the target application program forwards the verification request to the device cloud.
- the device cloud can acquire the target information locally. If the target information is obtained locally, the device cloud may obtain the target information locally when receiving the instruction. Alternatively, the device cloud may acquire the target information locally when receiving the acquisition request sent by the server of the target application program.
- target information includes the vendor information of the target application
- the target application is an application designed by another manufacturer.
- the equipment manufacturer of the IoT device is manufacturer A
- the application program configured by manufacturer A for the IoT device is the original application program.
- the target application program can be the application program designed by manufacturer B, and manufacturer A and manufacturer B are different factory.
- the device cloud may acquire the target information by receiving a URL request.
- the manufacturer information of the target application program may exist in the URL request in the form of URL parameters, or the manufacturer information of the target application program may be included in a message header (HTTP Header) of the URL request.
- the device cloud Since the device cloud stores the type of cooperation between the device manufacturer of the IoT device and each manufacturer and the connection information corresponding to the cooperation type, for example, as shown in Figure 4, after receiving the manufacturer information, the device cloud searches for the manufacturer The manufacturer corresponding to the information, that is, the manufacturer of the target application program, and then find out the type of cooperation between the manufacturer of the target application program and the device manufacturer.
- the device cloud After the device cloud queries the cooperation type, it searches for the connection information corresponding to the cooperation type, and returns the connection information to the terminal device.
- the device manufacturer can set it based on the cooperation relationship with each manufacturer, which is not limited in this application. Then set the connection information corresponding to the cooperation type, and the connection information of different cooperation types may be different.
- the connection information is the information indicating the manner in which the terminal device connects to the IoT device. For example, if the device manufacturer does not have a cooperative relationship with the manufacturer of the target application program, at this time, the cooperation type can be set to the guarantee type, and the connection information can be the information prompting to download the original application program of the IoT device, that is, the terminal device needs to pass the The original application establishes a connection with the IoT device.
- the cooperation type can be set as common, and the connection information can be the information prompting to enter the account and password corresponding to the device cloud, that is, at this time, the terminal device connects to the device cloud
- the corresponding account and password are bound to the target application, and then the connection with the IoT device needs to be established through the original application.
- the target information also includes device information of the IoT device.
- the device cloud can first find out whether there is cooperation with the manufacturer corresponding to the manufacturer information, and then find out the corresponding manufacturer information on the device information. cooperation type.
- the manufacturer information is manufacturer B
- the device information is model 1.
- the device cloud After receiving the manufacturer information and device information of the target application, the device cloud will check whether there is manufacturer B in the storage table. , and then find out that the type of cooperation between the device manufacturer and B manufacturer on model 1 is guaranteed. At this time, the device cloud returns the connection information 1 to the terminal device.
- What the device cloud returns to the terminal device may be an HTML page, and the HTML page carries connection information.
- the terminal device After receiving the connection information, the terminal device establishes a connection with the IoT device based on the connection information through the target application program, so that the IoT device can be controlled through the target application program.
- the process for the terminal device to establish a connection with the IoT device based on the connection information through the target application program may be: download the original application program corresponding to the IoT device based on the connection information, and then use the original application program to generate authorization information.
- the authorization information of the IoT device is then shared to the target application through the original application.
- the connection with the IoT device is established through the target application based on the authorization information.
- the way to share the authorization information of the IoT device to the target application program through the original application program can be as follows: the user opens the target application program, and then manually enters the authorization information on the page of the target application program, and the target application program obtains the authorization information .
- the way to share the authorization information of the IoT device to the target application program through the original application program can also be: the original application program stores the authorization information in the graphic code, and then scans the graphic code through the target application program, and the terminal device thus passes The target application obtains authorization information.
- the authorization information includes limited to an identification code (Personal Identification Number, PIN), device manufacturer and device information, and so on.
- the terminal device After the terminal device obtains the authorization information through the target application program, it uses the target application program to search for the IoT device based on the device information in the authorization information, and after finding the IoT device corresponding to the device information, the terminal device then uses the target application program based on the identification code and IoT devices establish connections. It should be noted that the IoT device can verify the identification code, and when the verification is passed, the IoT device establishes a connection with the terminal device.
- the process of sending the connection information to the terminal device so that the terminal device establishes a connection with the IoT device based on the connection information through the target application program may also be: sending the connection information to the terminal device, and receiving the terminal device based on the connection information Send the account number and password, and verify the account number and password. And when the verification is passed, the authorization information of the IoT device is returned to the terminal device. In order to enable the terminal device to establish a connection with the IoT device based on the authorization information through the target application program.
- the device cloud may verify the account and password using OAuth2 technology after receiving the account and password.
- the device cloud After the device cloud has passed the verification of the account and password, it can also perform HTTPS authentication on the terminal device, and the terminal device can also perform HTTPS authentication on the device cloud, that is, HTTPS two-way authentication is performed at this time to further ensure security.
- the target information after acquiring the target information, it also includes:
- the target information includes a verification request, authenticating the server of the target application based on the verification request;
- the authorization information is sent to the server of the target application program, so that the server of the target application program sends the authorization information to the terminal device, and the authorization information is used to instruct the terminal device to establish a connection with the IoT device through the target application program.
- the server of the target application program may refer to a server specially set up by the manufacturer of the target application program for the target application program, or may be a server of the manufacturer of the target application program, and the server of the manufacturer of the target application program may be servers of various target application programs.
- the server of the target application program needs to be controlled by the device cloud, that is, the identity of the device cloud to the server of the target application program before connecting (that is, to verify the identity of the manufacturer of the target application) for verification, and if the verification is passed, the device cloud will return the authorization information to the server of the target application.
- the target information after acquiring the target information, it also includes:
- If the target information includes authorization information, use the private key to sign the authorization information to obtain offline authorization information;
- the program establishes a connection with the IoT device.
- the private key and public key may be the private key and public key of the device cloud.
- the Internet of Things device uses the public key to verify the authorization information, you can also check whether the identification code in the offline authorization information is consistent with its own identification code and/or whether the device information in the offline authorization information is consistent with its own device information. Consistent, if consistent, then establish a connection with the target application.
- the server of the target application program can be separated from the control of the device cloud, that is, the device cloud first sends the offline authorization information to the target application program. stored in the server.
- the server of the target application program returns the offline authorization information after receiving the acquisition request sent by the terminal device.
- the IoT device can periodically query the device cloud whether the offline authorization information is invalid. If it is invalid, the target application program will not respond to the control command sent by the terminal device, and the reason for the non-response will be Return to the terminal device.
- the target information is acquired first. If the target information includes the vendor information of the target application, then based on the vendor information, determine the type of cooperation between the device vendor of the IoT device and the vendor of the target application, and the connection information corresponding to the cooperation type. Finally, the connection information is sent to the terminal device, so that the terminal device establishes a connection with the IoT device based on the connection information through the target application program.
- the cooperation type is associated with the connection information, and then different connection information can be set according to the cooperation type between the equipment manufacturer of the IoT device and the manufacturer of the target application program, so that when the terminal device passes through different target application programs Based on the connection information and the Internet of Things devices, the connection methods are different, so that the interconnection and intercommunication methods between device manufacturers and different manufacturers are different, which can ensure the economic interests of the device manufacturers and the security of the Internet of Things devices.
- FIG. 7 is a schematic diagram of a device connection method provided by an embodiment of the present application.
- the device connection methods may include:
- the terminal device obtains the address of the device cloud of the IoT device and the device information of the IoT device, and sends the address to the server of the target application through the target application.
- the server of the target application program inquires about the cooperation type between the device manufacturer corresponding to the address and the target application program manufacturer. Return the query result to the terminal device.
- the terminal device sends a URL request to the device cloud according to the address, and the URL request includes the manufacturer information and device information of the target application program.
- the device cloud determines the type of cooperation between the device manufacturer of the IoT device and the manufacturer of the target application program on the IoT device, and searches for the connection information corresponding to the cooperation type. Return the connection information to the terminal device in the form of an HTML page.
- the terminal device downloads the original application program corresponding to the IoT device based on the connection information, and uses the original application program to generate authorization information. Share the authorization information of the IoT device to the target application through the original application. Finally, the connection with the IoT device is established through the target application based on the authorization information.
- the terminal device obtains the account and password corresponding to the device cloud based on the connection information, and sends the account and password to the device cloud through the target application program.
- the device cloud verifies the account and password.
- the authorization information of the IoT device is returned to the terminal device.
- the terminal device establishes a connection with the IoT device based on the authorization information through the target application.
- the terminal device sends a verification request to the server of the target application program.
- the server of the target application then sends the verification request to the device cloud.
- the device cloud verifies the identity of the server of the target application program according to the verification request, and returns the authorization information of the IoT device to the server of the target application program when the verification is passed.
- the server of the target application then sends the authorization information to the terminal device.
- the terminal device establishes a connection with the IoT device based on the authorization information through the target application.
- the terminal device sends a request for obtaining offline authorization information to the server of the target application program, and the offline authorization information is the authorization information signed by the device cloud using a private key.
- the server of the target application returns the offline authorization information to the terminal device.
- the terminal device establishes a connection with the IoT device based on the offline authorization information through the target application program, that is, the terminal device sends the offline authorization information to the IoT device through the target application program.
- the Internet of Things device uses the public key to verify the offline authorization information, and establishes a connection with the target application after verification.
- the terminal device After establishing a connection with the Internet of Things device based on the connection information through the target application program, the terminal device sends a control instruction to the Internet of Things device based on the connection through the target application program.
- the IoT device executes the operation corresponding to the control command.
- the embodiment of the present application further provides an apparatus based on the above device connection method.
- the meanings of the nouns are the same as those in the above-mentioned device connection method, and for specific implementation details, please refer to the description in the method embodiments.
- the equipment connection device may include:
- the first acquiring module 801 is configured to acquire the configuration information of the IoT device.
- the determining module 802 is configured to determine the cooperation type between the device manufacturer of the IoT device and the manufacturer of the target application program on the terminal device based on the configuration information.
- the second obtaining module 803 is configured to obtain connection information corresponding to the cooperation type.
- a connection module 804 configured to establish a connection with the IoT device based on the connection information through the target application.
- the configuration information includes the address of the device cloud, and the device cloud is a server of the IoT device.
- the determining module 802 is specifically configured to execute:
- the device cloud sends the vendor information of the target application program to the device cloud according to the address, so that the device cloud determines the type of cooperation between the device vendor of the IoT device and the vendor of the target application program based on the vendor information, and the connection information corresponding to the cooperation type.
- the second acquiring module 803 is specifically configured to execute:
- the configuration information includes device information of the IoT device.
- the determining module 802 is specifically configured to execute:
- the device cloud can determine the cooperation type between the device manufacturer of the IoT device and the manufacturer of the target application program, and the connection corresponding to the cooperation type based on the manufacturer information and device information information.
- the determining module 802 is specifically configured to execute:
- the equipment connection device also includes:
- the sending module is used to send a verification request to the server of the target application program if the cooperation type is queried, so that the server of the target application program sends the verification request to the device cloud for identity verification, and receives the device cloud when the verification is passed. authorization information.
- connection module 804 is specifically used to execute:
- the sending module is also used to perform:
- a request for obtaining offline authorization information is sent to the server of the target application program, and the offline authorization information is the authorization information signed by the device cloud using a private key.
- connection module 804 is specifically used to execute:
- the offline authorization information is sent to the Internet of Things device through the target application program, so that the Internet of Things device uses the public key to verify the offline authorization information, and establishes a connection with the target application program after verification.
- connection module 804 is specifically configured to execute:
- connection module 804 is specifically configured to execute:
- the equipment connection device also includes:
- the control module is configured to send a control command to the IoT device based on the connection through the target application program, so that the IoT device executes an operation corresponding to the control command.
- each of the above modules can be implemented as an independent entity, or can be combined arbitrarily as the same or several entities.
- each of the above modules and the corresponding beneficial effects please refer to the previous method embodiments. I won't repeat them here.
- the embodiment of the present application further provides an apparatus based on the above device connection method.
- the meanings of the nouns are the same as those in the above-mentioned device connection method, and for specific implementation details, please refer to the description in the method embodiments.
- the equipment connection device may include:
- the receiving module 901 is configured to receive target information.
- the determining module 902 is configured to determine a cooperation type between the device manufacturer and the target application manufacturer based on the manufacturer information if the target information includes the target application vendor information.
- the sending module 903 is configured to send the connection information corresponding to the cooperation type to the terminal device, so that the terminal device establishes a connection with the IoT device based on the connection information through the target application program.
- the sending module 903 is specifically configured to execute:
- the equipment connection device also includes:
- An authentication module configured to authenticate the server of the target application program based on the authentication request if the target information includes the authentication request.
- the information sending module is used to send the authorization information to the server of the target application program when the verification is passed, so that the server of the target application program sends the authorization information to the terminal device, and the authorization information is used to instruct the terminal device to communicate with the Internet of Things through the target application program
- the device establishes a connection.
- the equipment connection device also includes:
- the signature module is configured to, if the target information includes authorization information, use the private key to sign the authorization information to obtain offline authorization information.
- the information sending module is also used to execute:
- the program establishes a connection with the IoT device.
- each of the above modules can be implemented as an independent entity, or can be combined arbitrarily as the same or several entities.
- each of the above modules and the corresponding beneficial effects please refer to the previous method embodiments. I won't repeat them here.
- the embodiment of the present application also provides an electronic device, which may be a server or a terminal device, etc., as shown in FIG. 10 , which shows a schematic structural diagram of the electronic device involved in the embodiment of the present application. Specifically:
- the electronic device may include a processor 1001 of one or more processing cores, a memory 1002 of one or more computer-readable storage media, a power supply 1003, an input unit 1004 and other components.
- a processor 1001 of one or more processing cores may include a processor 1001 of one or more processing cores, a memory 1002 of one or more computer-readable storage media, a power supply 1003, an input unit 1004 and other components.
- FIG. 10 does not constitute a limitation on the electronic device, and may include more or less components than shown in the figure, or combine some components, or arrange different components. in:
- the processor 1001 is the control center of the electronic device, and uses various interfaces and lines to connect various parts of the entire electronic device, by running or executing computer programs and/or modules stored in the memory 1002, and calling the Data, perform various functions of electronic equipment and process data, so as to monitor electronic equipment as a whole.
- the processor 1001 may include one or more processing cores; preferably, the processor 1001 may integrate an application processor and a modem processor, wherein the application processor mainly processes operating systems, user interfaces, and application programs, etc. , the modem processor mainly handles wireless communications. It can be understood that the foregoing modem processor may not be integrated into the processor 1001 .
- the memory 1002 can be used to store computer programs and modules, and the processor 1001 executes various functional applications and data processing by running the computer programs and modules stored in the memory 1002 .
- the memory 1002 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, computer programs required by at least one function (such as sound playback function, image playback function, etc.); Data created by the use of electronic devices, etc.
- the memory 1002 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage devices.
- the memory 1002 may further include a memory controller to provide the processor 1001 with access to the memory 1002 .
- the electronic device also includes a power supply 1003 for supplying power to various components.
- the power supply 1003 can be logically connected to the processor 1001 through a power management system, so that functions such as charging, discharging, and power consumption management can be realized through the power management system.
- the power supply 1003 may also include one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, power status indicators and other arbitrary components.
- the electronic device can also include an input unit 1004, which can be used to receive input numbers or character information, and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.
- an input unit 1004 can be used to receive input numbers or character information, and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.
- the electronic device may also include a display unit, etc., which will not be repeated here.
- the processor 1001 in the electronic device will load the executable file corresponding to the process of one or more computer programs into the memory 1002 according to the following instructions, and the processor 1001 will run the executable file stored in the The computer program in memory 1002, thereby realizes various functions, such as:
- an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored, and the computer program can be loaded by a processor to execute the steps in any of the device connection methods provided in the embodiments of the present application.
- the computer program can perform the following steps:
- the computer-readable storage medium may include: a read-only memory (ROM, Read Only Memory), random access memory (RAM, Random Access Memory), disk or CD, etc.
- a computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium.
- the processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the above device connection method.
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- General Business, Economics & Management (AREA)
- Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Development Economics (AREA)
- Structural Engineering (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Artificial Intelligence (AREA)
- Toxicology (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Architecture (AREA)
- Civil Engineering (AREA)
- General Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Mathematical Physics (AREA)
- Economics (AREA)
- Electromagnetism (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Medical Informatics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
本申请公开了一种设备连接方法、装置、电子设备和计算机可读存储介质;方法包括:获取物联网设备的配置信息;基于配置信息确定物联网设备的设备厂商,与终端设备上目标应用程序的厂商之间的合作类型;获取合作类型对应的连接信息;通过目标应用程序基于连接信息与物联网设备建立连接。本申请可以保证设备厂商的经济利益和物联网设备的安全性。
Description
本申请要求申请日为2021年11月02日、申请号为202111288774.5、发明名称为“设备连接方法、装置、电子设备和计算机可读存储介质”的中国专利申请的优先权,其全部内容通过引用结合在本申请中
本申请涉及智能家居技术领域,具体涉及一种设备连接方法、装置、电子设备和计算机可读存储介质。
随着科学技术的发展,物联网(Internet of Things,IOT)设备的应用越来越广泛。
目前,由于安全性问题和经济利益问题,各个厂商之间都是互相独立的,不进行互联互通,即一般是通过物联网设备的厂商设置的应用程序(Application)连接物联网设备,不能通过其他厂商的应用程序连接物联网设备。
本申请实施例提供一种设备连接方法、装置、电子设备和计算机可读存储介质,可以解决厂商之间不能互联互通的技术问题。
本申请实施例提供一种设备连接方法,应用于终端设备,包括:
获取物联网设备的配置信息;
基于上述配置信息确定上述物联网设备的设备厂商,与上述终端设备上目标应用程序的厂商之间的合作类型;
获取上述合作类型对应的连接信息;
通过上述目标应用程序基于上述连接信息与上述物联网设备建立连接。
可选地,本申请实施例提供一种设备连接方法,应用于设备云,包括:
获取目标信息;
若上述目标信息包括目标应用程序的厂商信息,则基于上述厂商信息确定物联网设备的设备厂商与上述目标应用程序的厂商的合作类型,以及上述合作类型对应的连接信息;
将上述连接信息发送至终端设备,以使上述终端设备通过上述目标应用程序,基于上述连接信息与上述物联网设备建立连接。
相应地,本申请实施例提供一种设备连接装置,应用于终端设备,包括:
第一获取模块,用于获取物联网设备的配置信息;
确定模块,用于基于上述配置信息确定上述物联网设备的设备厂商,与上述终端设备上目标应用程序的厂商之间的合作类型;
第二获取模块,用于获取上述合作类型对应的连接信息;
连接模块,用于通过上述目标应用程序基于上述连接信息与上述物联网设备建立连接。
相应地,本申请实施例提供一种设备连接装置,应用于设备云,包括:
接收模块,用于接收目标信息;
确定模块,用于若上述目标信息包括上述目标应用程序的厂商信息,则基于上述厂商信息确定设备厂商与上述目标应用程序的厂商的合作类型;
发送模块,用于将上述合作类型对应的连接信息发送至终端设备,以使上述终端设备通过上述目标应用程序,基于上述连接信息与上述物联网设备建立连接。
此外,本申请实施例还提供一种电子设备,包括处理器和存储器,上述存储器存储有计算机程序,上述处理器用于运行上述存储器内的计算机程序实现本申请实施例提供的设备连接方法。
此外,本申请实施例还提供一种计算机可读存储介质,上述计算机可读存储介质存储有计算机程序,上述计算机程序适于处理器进行加载,以执行本申请实施例所提供的任一种设备连接方法。
此外,本申请实施例还提供一种计算机程序产品,包括计算机程序,所述计算机程序被处理器执行时实现本申请实施例所提供的任一种设备连接方法。
在本申请实施例中,先获取物联网设备的配置信息。然后基于配置信息确定物联网设备的设备厂商,与终端设备上目标应用程序的厂商之间的合作类型。然后获取合作类型对应的连接信息。最后通过目标应用程序基于连接信息与物联网设备建立连接。
即在本申请实施例中,将合作类型与连接信息进行对应,然后可以根据物联网设备的设备厂商与目标应用程序的厂商合作类型设置不同的连接信息,使得当通过不同的目标应用程序基于连接信息与物联网设备建立连接时连接的方式不相同,从而使得设备厂商与不同厂商之间的互联互通的方式不同,进而可以保证设备厂商的经济利益和物联网设备的安全性。
为了更清楚地说明本申请实施例中的技术方案,下面将对实施例描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本申请的一些实施例,对于本领域技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1是本申请实施例提供的设备连接方法的流程示意图;
图2是本申请实施例提供的关系表的示意图;
图3是本申请实施例提供的另一种关系表的示意图;
图4是本申请实施例提供的存储表的示意图;
图5是本申请实施例提供的另一种存储表的示意图;
图6是本申请实施例提供的另一种设备连接方法的流程示意图;
图7是本申请实施例提供的设备连接方法的交互示意图;
图8是本申请实施例提供的设备连接装置的结构示意图;
图9是本申请实施例提供的另一种设备连接装置的结构示意图;
图10是本申请实施例提供的电子设备的结构示意图。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
本申请实施例提供一种设备连接方法、装置和计算机可读存储介质。其中,该设备连接装置可以集成在电子设备中,该电子设备可以是服务器,也可以是终端等设备。
其中,服务器可以是独立的物理服务器,也可以是多个物理服务器构成的服务器集群或者分布式系统,还可以是提供云服务、云数据库、云计算、云函数、云存储、网络服务、云通信、中间件服务、域名服务、安全服务、网络加速服务(Content
Delivery Network,CDN)、以及大数据和人工智能平台等基础云计算服务的云服务器。
终端可以是智能手机、平板电脑、笔记本电脑、台式计算机、智能音箱、智能手表等,但并不局限于此。终端以及服务器可以通过有线或无线通信方式进行直接或间接地连接,本申请在此不做限制。
另外,本申请实施例中的“多个”指两个或两个以上。本申请实施例中的“第一”和“第二”等用于区分描述,而不能理解为暗示相对重要性。
以下分别进行详细说明。需要说明的是,以下实施例的描述顺序不作为对实施例优选顺序的限定。
在本实施例中,将从设备连接装置的角度进行描述,该设备连接装置具体可以集成在终端设备中,以下将以终端设备作为执行主体进行详细说明。
请参阅图1,图1是本申请一实施例提供的设备连接方法的流程示意图。该设备连接方法可以包括:
S101、获取物联网设备的配置信息。
获取物联网设备的配置信息的方式可以为:将物联网设备的配置信息存储在二维码中,然后通过目标应用程序扫描该图形码(图形码可以为二维码或条形码),终端设备从而获取到物联网设备的配置信息。
或者,获取物联网设备的配置信息的方式也可以为:物联网设备广播的近距离通讯信息包括了该配置信息,当物联网设备进行广播时,终端设备从而可以扫描到该配置信息。
近距离通讯信息包括但不限于蓝牙信息、SoftAp信息、近场通讯(Near
Field Communication,NFC)信息。
又或者,获取物联网设备的配置信息的方式也可以为:物联网设备广播近距离通讯信息,近距离通讯信息中包括了物联网设备的设备信息,终端设备扫描到设备信息之后,从公共服务器(公共服务器比如可以为区块链)中查找设备信息对应的配置信息,终端设备从而获取物联网设备的配置信息。
对于获取物联网设备的配置信息的方式,用户可以根据实际情况进行选择,本申请在此不做限定。
配置信息包括但不限于物联网设备的设备信息、设备厂商、设备云的地址、设备厂商与其他厂商之间的关系表等,关系表包括了设备厂商与其他厂商之间的合作类型和合作类型对应的连接信息。
S102、基于配置信息确定物联网设备的设备厂商,与终端设备上目标应用程序的厂商之间的合作类型。
终端设备在获取物联网设备的配置信息后,如果该配置信息是通过目标应用程序扫描二维码获取到的,则终端设备可以自动基于配置信息确定物联网设备的设备厂商,与终端设备上目标应用程序的厂商之间的合作类型。如果该配置信息是终端设备通过扫描得到的,则终端设备可以将扫描到的配置信息呈现给用户,以供用户进行确认。接收到用户的确认指令后,终端设备再基于确认的配置信息确定物联网设备的设备厂商,与终端设备上目标应用程序的厂商之间的合作类型。
如果配置信息包括设备厂商且没有包括关系表,则该关系表可以存储于目标应用程序的文件中,终端设备在下载目标应用程序之后,可以从目标应用程序的文件中获取到关系表。
终端设备在接收到配置信息后,基于配置信息中的设备厂商从关系表中查找设备厂商与目标应用程序的厂商之间的合作类型。
如果配置信息包括设备云的地址,则终端设备可以根据地址向设备云发送目标应用程序的厂商信息,以使设备云基于厂商信息,确定物联网设备的设备厂商与目标应用程序之间的厂商的合作类型。
目标应用程序为其他厂商设计的应用程序。比如,物联网设备的设备厂商为A厂商,A厂商为物联网设备配置的应用程序为原始应用程序,此时,目标应用程序可以为B厂商设计的应用程序,A厂商和B厂商为不同的厂商。
应注意,对于合作类型,设备厂商可以基于与各个厂商之间的合作关系进行设置,本申请在此不做限定。
S103、获取合作类型对应的连接信息。
终端设备在确定合作类型之后,再从关系表中查找合作类型对应的连接信息。
如果终端设备是根据地址向设备云发送目标应用程序的厂商信息,以使设备云基于厂商信息,确定物联网设备的设备厂商与目标应用程序的厂商的合作类型,则终端设备接收设备云返回的合作类型对应的连接信息。
由于关系表中存储了物联网设备的设备厂商与各个厂商之间的合作类型以及合作类型对应的连接信息,比如,如图2所示,因此,终端设备在获取到配置信息之后,先查找关系表中是否存在该设备厂商,如果存在,再从关系表中查找目标应用程序的厂商与设备厂商之间的厂商的合作类型,最后查找合作类型对应的连接信息。
不同合作类型的连接信息可以是不同的。因为合作类型不同,连接信息不同,所以,设备厂商与各个厂商之间的互通互联的方式不相同,以便可以保证设备厂商的经济利益和物联网设备的安全性。
连接信息为表明终端设备连接物联网设备的方式的信息。比如,如果设备厂商和目标应用程序的厂商没有合作关系,此时,可以将合作类型设置为保底类,连接信息可以为提示下载物联网设备的原始应用程序的信息,即此时终端设备需通过原始应用程序与物联网设备建立连接。
又比如,如果设备厂商和目标应用程序的厂商存在合作关系,则可以将合作类型设置为普通类,连接信息可以为提示输入设备云对应的账号和密码的信息,即此时终端设备将设备云对应的账号和密码与目标应用程序进行绑定,然后再需通过原始应用程序与物联网设备建立连接。
可选地,由于设备厂商可以生产较多种物联网设备,因此,为了进一步保证设备厂商的经济利益,设备厂商可以基于具体一种物联网设备与其他厂商进行互通,即可以根据物联网设备的型号或序列号设置设备厂商与其他厂商之间的合作类型。此时,关系表还包括物联网设备的设备信息。
则终端设备在获取到配置信息后,可以先从关系表中查找是否存在该配置信息中的设备厂商,如果存在,再基于设备信息查找目标应用程序的厂商与设备厂商在该物联网设备上的合作类型,最后查找合作类型对应的连接信息。
比如,如图3所示,设备厂商为A厂商,设备信息为型号1,则终端设备在获取到配置信息之后,在关系表中查找是否存在A厂商,如果存在A厂商,则查找目标应用程序的厂商与A厂商在型号1上的合作类型,最后查找合作类型对应的连接信息。
设备信息包括但不限于设备型号和设备序列号等。
S104、通过目标应用程序基于连接信息与物联网设备建立连接。
终端设备在接收到连接信息,再基于连接信息,通过目标应用程序与物联网设备建立连接,以便可以通过目标应用程序控制物联网设备。
由上可见,在本申请实施例中,先获取物联网设备的配置信息。然后基于配置信息确定物联网设备的设备厂商,与终端设备上目标应用程序的厂商之间的合作类型。然后获取合作类型对应的连接信息。最后通过目标应用程序基于连接信息与物联网设备建立连接。
即在本申请实施例中,将合作类型与连接信息进行对应,然后可以根据物联网设备的设备厂商与目标应用程序的厂商合作类型设置不同的连接信息,使得当通过不同的目标应用程序基于连接信息与物联网设备建立连接时连接的方式不相同,从而使得设备厂商与不同厂商之间的互联互通的方式不同,进而可以保证设备厂商的经济利益和物联网设备的安全性。
在一些实施例中,配置信息包括设备云的地址,设备云为物联网设备的服务器。相应地,基于配置信息确定物联网设备的设备厂商,与终端设备上目标应用程序的厂商之间的合作类型,包括:
根据地址向设备云发送目标应用程序的厂商信息,以使设备云基于厂商信息,确定物联网设备的设备厂商与目标应用程序的厂商之间的合作类型,以及合作类型对应的连接信息。
获取合作类型对应的连接信息包括:接收设备云返回的合作类型对应的连接信息。
终端设备在获取物联网设备的配置信息后,如果该配置信息是通过目标应用程序扫描二维码获取到的,则终端设备可以自动根据地址向设备云发送目标应用程序的厂商信息。如果该配置信息是终端设备通过扫描得到的,则终端设备可以将扫描到的配置信息呈现给用户,以供用户进行确认。接收到用户的确认指令后,终端设备再根据地址向设备云发送目标应用程序的厂商信息。
其中,终端设备根据地址向设备云发送目标应用程序的厂商信息的详细方式可以为:终端设备根据地址向设备云发送URL请求,目标应用程序的厂商信息可以以URL参数的形式存在于URL请求中,或者,目标应用程序的厂商信息可以包含在URL请求的消息头(HTTP
Header)中。
由于设备云中存储了物联网设备的设备厂商与各个厂商之间的合作类型以及合作类型对应的连接信息,比如,如图4所示,因此,设备云在接收到厂商信息后,在存储表上查找厂商信息对应的厂商,即目标应用程序的厂商,然后查找目标应用程序的厂商与设备厂商之间的合作类型。
设备云查询到合作类型之后,再查找合作类型对应的连接信息,并把连接信息返回至终端设备。
设备云的地址可以为统一资源定位器(Uniform Resource Locator,URL)。设备云返回终端设备的可以是HTML页面,HTML页面上携带了连接信息。
需要说明的是,物联网设备的服务器可以是物联网设备的设备厂商专门为物联网设备建立的服务器,也可以是物联网设备的设备厂商的服务器,此时,该服务器可以是多种物联网设备的服务器。
由于设备厂商可以生产较多种物联网设备,因此,为了进一步保证设备厂商的经济利益,设备厂商可以基于具体一种物联网设备与其他厂商进行互通,即可以根据物联网设备的型号或序列号设置设备厂商与其他厂商之间的合作类型。此时,配置信息包括物联网设备的设备信息。
相应地,根据地址向设备云发送目标应用程序的厂商信息,以使设备云基于厂商信息,确定物联网设备的设备厂商与目标应用程序的厂商的合作类型,包括:
根据地址向设备云发送目标应用程序的厂商信息和设备信息,以使设备云基于厂商信息和设备信息,确定物联网设备的设备厂商与目标应用程序的厂商的合作类型,以及合作类型对应的连接信息。
即设备云在接收到终端设备发送的目标应用程序的厂商信息和设备信息之后,设备云可以先查找与厂商信息对应的厂商是否存在合作,然后再找出与该厂商在该设备信息上对应的合作类型。
比如,如图5所示,厂商信息为B厂商,设备信息为型号1,则设备云在接收到目标应用程序的厂商信息和设备信息之后,查找存储表中是否存在B厂商,如果存在B厂商,再查找设备厂商与B厂商在型号1上的合作类型为保底类,此时,设备云再返回连接信息1至终端设备。
在另一些实施例中,当连接信息为提示下载物联网设备对应的原始应用程序的信息(此时合作类型可以为保底类)时,通过所述目标应用程序基于连接信息与物联网设备建立连接可以包括:
基于该连接信息下载物联网设备对应的原始应用程序;
通过原始应用程序将物联网设备的授权信息分享至目标应用程序;
通过目标应用程序基于授权信息与物联网设备建立连接。
其中,通过原始应用程序将物联网设备的授权信息分享至目标应用程序的方式可以为:用户打开目标应用程序,然后在目标应用程序的页面上手动输入授权信息,目标应用程序从而获取到授权信息。
或者,通过原始应用程序将物联网设备的授权信息分享至目标应用程序的方式也可以为:原始应用程序将授权信息存储于图形码中,然后通过目标应用程序扫描该图形码,终端设备从而通过目标应用程序获取到授权信息。
另外,通过原始应用程序将物联网设备的授权信息分享至目标应用程序之前,还可以先通过原始应用程序与物联网设备建立连接。
授权信息包括限于识别码(Personal Identification Number,PIN)、设备厂商和设备信息等。
终端设备在通过目标应用程序获取到授权信息后,通过目标应用程序基于授权信息中的设备信息查找物联网设备,找到设备信息对应的物联网设备之后,终端设备再通过目标应用程序基于识别码与物联网设备建立连接。需要说明的是,物联网设备可以对识别码进行校验,在校验通过时,物联网设备再与终端设备建立连接。
如果终端设备通过目标应用程序与物联网设备连接在同一个局域网里,则终端设备还可以将局域网的信息发送至物联网设备。
在本实施例中,当合作类型为保底类时,可以要求终端设备下载物联网设备对应的原始应用程序。
在另一些实施例中,当连接信息为提示输入设备云对应的账号和密码的信息(此时合作类型可以为普通类)时,通过目标应用程序基于连接信息与物联网设备建立连接可以包括:
基于连接信息获取设备云对应的账号和密码;
通过目标应用程序将账号和密码发送至设备云,以使设备云对账号和密码进行验证;
接收设备云在验证通过时返回的物联网设备的授权信息;
通过目标应用程序基于授权信息与物联网设备建立连接。
本实施例中,当合作类型为普通类时,可以要求终端设备将目标应用程序与设备云对应的账号和密码进行绑定。
应理解,如果用户是利用第三方应用的账号和密码作为设备云对应的账号和密码,则设备云在接收到账号和密码后,可以采用OAuth2技术对账号和密码进行校验。
设备云在对账号和密码进行校验通过之后,还可以对终端设备进行HTTPS认证,终端设备也可以对设备云进行HTTPS认证,即此时进行HTTPS双向认证,从而进一步保证安全性。
需要说明的是,当通过目标应用程序基于授权信息与物联网设备建立连接失败时,终端设备可以查找连接失败的原因,将连接失败的原因进行提示,并返回执行根据地址向设备云发送目标应用程序的厂商信息。
另外,终端设备在通过目标应用程序与物联网设备建立连接后,可以基于账号将物联网设备的设备信息和用户信息发送至设备云,实现用户信息的同步。
在另一些实施例中,当设备厂商与目标应用程序的厂商的合作关系较为密切(比如,当合作类型为高级类或最高级类)时,可以将合作类型存储于目标应用程序的服务器中。此时,根据地址向设备云发送目标应用程序的厂商信息,可以包括:先从目标应用程序的服务器中查找地址对应的设备厂商与目标应用程序的厂商的合作类型。若没有查询到合作类型,则根据地址向设备云发送目标应用程序的厂商信息。
如果查询到合作类型,则终端设备可以向目标应用程序的服务器发送验证请求,目标应用程序的服务器再将验证请求发送至设备云进行验证身份,并接收设备云在验证通过时返回的授权信息。目标应用程序的服务器再将授权信息发送至终端设备。终端设备从而接收到授权信息,最后再通过目标应用程序基于授权信息与物联网设备建立连接。
从目标应用程序的服务器中地址对应的设备厂商与目标应用程序的厂商的合作类型的过程可以为:将地址发送至目标应用程序的服务器,服务器接收到地址后,查询地址对应的设备厂商与目标应用程序的厂商的合作类型。
如果目标应用程序的服务器有查询到合作类型,则目标应用程序的服务器也可以直接生成验证请求,并将验证请求发送至设备云进行验证身份,无需等待接收终端设备发送的验证请求,并接收设备云在验证通过时返回的授权信息。
目标应用程序的服务器可以指目标应用程序的厂商专门为该目标应用程序设置的服务器,也可以是目标应用程序的厂商的服务器,目标应用程序的厂商的服务器可以是多种目标应用程序的服务器。
在本实施例中,无需将目标应用程序与设备云对应的账号和密码进行绑定,但目标应用程序的服务器需受设备云的控制,即在连接之前设备云对目标应用程序的服务器的身份(即验证目标应用程序的厂商的身份)进行验证,如果验证通过,设备云则将授权信息返回至目标应用程序的服务器。
或者,如果查询到合作类型,则向目标应用程序的服务器发送离线授权信息的获取请求,离线授权信息为设备云采用私钥签名后的授权信息。接收目标应用程序的服务器基于获取请求返回的离线授权信息;通过目标应用程序将离线授权信息发送至物联网设备,以使物联网设备采用公钥对离线授权信息进行验证,并在验证通过与目标应用程序建立连接。
该私钥和公钥可以为设备云的私钥和公钥。另外,如果物联网设备采用公钥对授权信息的验证通过,则还可以查看离线授权信息中的识别码与本身的识别码是否一致和/或离线授权信息中的设备信息与本身的设备信息是否一致,如果一致,再与目标应用程序建立连接。
在本实施例中,无需将目标应用程序与设备云对应的账号和密码进行绑定,且目标应用程序的服务器可以脱离设备云的控制,即设备云先将离线授权信息发送至目标应用程序的服务器中进存储。目标应用程序的服务器在接收到终端设备发送的获取请求后再返回离线授权信息。
需要说明的是,为了保证安全,物联网设备可以在周期性地向设备云查询该离线授权信息是否失效,如果失效,则目标应用程序不响应终端设备发送的控制指令,并将不响应的原因返回至终端设备。
应注意,如果终端设备查询到合作类型,则终端设备也可以直接向目标应用程序的服务器发送请求。目标应用程序的服务器在接收到请求后,查找本地是否存在离线授权信息。如果不存在,则目标应用程序的服务器向设备云发送验证请求。如果存在离线授权信息,则直接将离线授权信息返回至终端设备。
在通过目标应用程序基于连接信息与物联网设备建立连接之后,还包括:通过目标应用程序基于连接将控制指令发送至物联网设备,以使物联网设备执行控制指令对应的操作。
由于此时可以保证该目标应用程序是安全的,因此,物联网设备可以执行通过连接接收到的控制指令对应的操作。
可选地,本实施例提供另一种设备连接方法。在本实施例中,将从设备连接装置的角度进行描述,该设备连接装置具体可以集成在设备云中,以下将以设备云作为执行主体进行详细说明。
请参阅图6,图6是本申请一实施例提供的设备连接方法的流程示意图。该设备连接方法可以包括:
S601、获取目标信息。
目标信息包括但不限于目标应用程序的厂商信息、验证请求以及授权信息等。
如果目标信息包括目标应用程序的厂商信息,则该目标信息可以是终端设备向设备云发送的,设备云从而接收到目标信息。
如果该目标信息包括验证请求,则该验证请求可以是目标应用程序的服务器向设备云发送的,设备云从而接收到目标信息。如果该目标信息包括验证请求,则该验证请求可以是目标应用程序的服务器在查询到合作类型时直接生成的并发送给设备云,或者,该验证请求也可以是目标应用程序的服务器在查询到合作类型时,终端设备发送给目标应用程序的服务器,目标应用程序的服务器再将验证请求转发至设备云。
如果该目标信息包括授权信息,则设备云可以从本地获取该目标信息。如果是从本地获取该目标信息,则设备云可以是在接收到指令时从本地获取目标信息。或者,设备云也可以是在接收到目标应用程序的服务器发送的获取请求时,从本地获取目标信息。
S602、若目标信息包括目标应用程序的厂商信息,则基于厂商信息确定物联网设备的设备厂商与目标应用程序的厂商的合作类型,以及合作类型对应的连接信息。
目标应用程序为其他厂家设计的应用程序。比如,物联网设备的设备厂家为A厂家,A厂家为物联网设备配置的应用程序为原始应用程序,此时,目标应用程序可以为B厂家设计的应用程序,A厂家和B厂家为不同的厂家。
其中,如果目标信息包括目标应用程序的厂商信息,则设备云可以以接收URL请求的方式获取目标信息。目标应用程序的厂家信息可以以URL参数的形式存在于URL请求中,或者,目标应用程序的厂家信息可以包含在URL请求的消息头(HTTP Header)中。
由于设备云中存储了物联网设备的设备厂商与各个厂商之间的合作类型以及合作类型对应的连接信息,比如,如图4所示,因此,设备云在接收到厂商信息后,再查找厂商信息对应的厂商,即目标应用程序的厂商,然后查找目标应用程序的厂商与设备厂商之间的合作类型。
设备云查询到合作类型之后,再查找合作类型对应的连接信息,并把连接信息返回至终端设备。
应注意,对于合作类型,设备厂家可以基于与各个厂家之间的合作关系进行设置,本申请在此不做限定。然后再设置合作类型对应的连接信息,不同合作类型的连接信息可以是不同的。
因为合作类型不同,连接信息不同,所以,设备厂家与各个厂家之间的互通互联的方式不相同,以便可以保证设备厂家的经济利益和物联网设备的安全性。
连接信息为表明终端设备连接物联网设备的方式的信息。比如,如果设备厂家和目标应用程序的厂家没有合作关系,此时,可以将合作类型设置为保底类,连接信息可以为提示下载物联网设备的原始应用程序的信息,即此时终端设备需通过原始应用程序与物联网设备建立连接。
又比如,如果设备厂家和目标应用程序的厂家存在合作关系,则可以将合作类型设置为普通类,连接信息可以为提示输入设备云对应的账号和密码的信息,即此时终端设备将设备云对应的账号和密码与目标应用程序进行绑定,然后再需通过原始应用程序与物联网设备建立连接。
由于设备厂商可以生产较多种物联网设备,因此,为了进一步保证设备厂商的经济利益,设备厂商可以基于具体一种物联网设备与其他厂商进行互通,即可以根据物联网设备的型号或序列号设置设备厂商与其他厂商之间的合作类型。此时,目标信息还包括所述物联网设备的设备信息。
则设备云在接收到终端设备发送的目标应用程序的厂商信息和设备信息之后,设备云可以先查找与厂商信息对应的厂商是否存在合作,然后再找出与该厂商在该设备信息上对应的合作类型。
比如,如图5所示,厂商信息为B厂商,设备信息为型号1,则设备云在接收到目标应用程序的厂商信息和设备信息之后,查找存储表中是否存在B厂商,如果存在B厂商,再查找设备厂商与B厂商在型号1上的合作类型为保底类,此时,设备云再返回连接信息1至终端设备。
S603、将连接信息发送至终端设备,以使终端设备通过目标应用程序,基于连接信息与物联网设备建立连接。
设备云返回终端设备的可以是HTML页面,HTML页面上携带了连接信息。端设备在接收到连接信息,再通过目标应用程序,基于连接信息与物联网设备建立连接,以便可以通过目标应用程序控制物联网设备。
可选地,终端设备通过目标应用程序,基于连接信息与物联网设备建立连接的过程可以为:基于该连接信息下载物联网设备对应的原始应用程序,然后利用原始应用程序生成授权信息。接着通过原始应用程序将物联网设备的授权信息分享至目标应用程序。最后通过目标应用程序基于授权信息与物联网设备建立连接。
其中,通过原始应用程序将物联网设备的授权信息分享至目标应用程序的方式可以为:用户打开目标应用程序,然后在目标应用程序的页面上手动输入授权信息,目标应用程序从而获取到授权信息。
或者,通过原始应用程序将物联网设备的授权信息分享至目标应用程序的方式也可以为:原始应用程序将授权信息存储与图形码中,然后通过目标应用程序扫描该图形码,终端设备从而通过目标应用程序获取到授权信息。
另外,通过原始应用程序将物联网设备的授权信息分享至目标应用程序之前,还可以先通过原始应用程序与物联网设备建立连接。
授权信息包括限于识别码(Personal Identification Number,PIN)、设备厂商和设备信息等。
终端设备在通过目标应用程序获取到授权信息后,通过目标应用程序基于授权信息中的设备信息查找物联网设备,找到设备信息对应的物联网设备之后,终端设备再通过目标应用程序基于识别码与物联网设备建立连接。需要说明的是,物联网设备可以对识别码进行校验,在校验通过时,物联网设备再与终端设备建立连接。
可选地,将连接信息发送至终端设备,以使终端设备通过目标应用程序,基于连接信息与物联网设备建立连接的过程也可以为:将连接信息发送至终端设备,接收终端设备基于连接信息发送的账号和密码,对账号和密码进行验证。并在验证通过时,将物联网设备的授权信息返回至终端设备。以使终端设备通过目标应用程序基于授权信息与物联网设备建立连接。
应理解,如果用户是利用第三方应用的账号和密码作为设备云对应的账号和密码,则设备云在接收到账号和密码后,可以采用OAuth2技术对账号和密码进行校验。
设备云在对账号和密码进行校验通过之后,还可以对终端设备进行HTTPS认证,终端设备也可以对设备云进行HTTPS认证,即此时进行HTTPS双向认证,从而进一步保证安全性。
在一些实施例中,在获取目标信息之后,还包括:
若目标信息包括验证请求,则基于验证请求对目标应用程序的服务器进行身份验证;
当验证通过时将授权信息发送至目标应用程序的服务器,以使目标应用程序的服务器将授权信息发送至终端设备,授权信息用于指示终端设备通过目标应用程序与物联网设备建立连接。
目标应用程序的服务器可以指目标应用程序的厂商专门为该目标应用程序设置的服务器,也可以是目标应用程序的厂商的服务器,目标应用程序的厂商的服务器可以是多种目标应用程序的服务器。
在本实施例中,无需将目标应用程序与设备云对应的账号和密码进行绑定,但目标应用程序的服务器需受设备云的控制,即在连接之前设备云对目标应用程序的服务器的身份(即验证目标应用程序的厂商的身份)进行验证,如果验证通过,设备云则将授权信息返回至目标应用程序的服务器。
在另一些实施例中,在获取目标信息之后,还包括:
若目标信息包括授权信息,则采用私钥对授权信息进行签名,得到离线授权信息;
将离线授权信息发送至目标应用程序的服务器,以使目标应用程序的服务器在接收到终端设备发送的获取请求后,将离线授权信息发送至终端设备,离线授权信息用于指示终端设备通过目标应用程序与物联网设备建立连接。
该私钥和公钥可以为设备云的私钥和公钥。另外,如果物联网设备采用公钥对授权信息的验证通过,则还可以查看离线授权信息中的识别码与本身的识别码是否一致和/或离线授权信息中的设备信息与本身的设备信息是否一致,如果一致,再与目标应用程序建立连接。
在本实施例中,无需将目标应用程序与设备云对应的账号和密码进行绑定,且目标应用程序的服务器可以脱离设备云的控制,即设备云先将离线授权信息发送至目标应用程序的服务器中进存储。目标应用程序的服务器在接收到终端设备发送的获取请求后再返回离线授权信息。
需要说明的是,为了保证安全,物联网设备可以在周期性地向设备云查询该离线授权信息是否失效,如果失效,则目标应用程序不响应终端设备发送的控制指令,并将不响应的原因返回至终端设备。
由上可见,在本申请实施例中,先获取目标信息。若目标信息包括目标应用程序的厂商信息,则基于厂商信息确定物联网设备的设备厂商与目标应用程序的厂商的合作类型,以及合作类型对应的连接信息。最后将连接信息发送至终端设备,以使终端设备通过目标应用程序,基于连接信息与物联网设备建立连接。
即在本申请实施例中,将合作类型与连接信息进行对应,然后可以根据物联网设备的设备厂商与目标应用程序的厂商合作类型设置不同的连接信息,使得当终端设备通过不同的目标应用程序基于连接信息与物联网设备建立连接时连接的方式不相同,从而使得设备厂商与不同厂商之间的互联互通的方式不同,进而可以保证设备厂商的经济利益和物联网设备的安全性。
以上各个操作的具体其他实施方式以及对应的有益效果可参见上述另外一个设备连接方法实施例的详细描述,在此不作赘述。
根据上述实施例所描述的方法,以下将作进一步详细说明。
请参阅图7,图7为本申请实施例提供的设备连接方法的示意图。该设备连接方法可以包括:
终端设备获取物联网设备的设备云的地址和物联网设备的设备信息,通过目标应用程序向目标应用程序的服务器发送地址。目标应用程序的服务器查询该地址对应的设备厂商与目标应用程序的厂商的合作类型。将查询结果返回至终端设备。
如果查询结果为没有查询到合作类型,终端设备则根据地址向设备云发送URL请求,URL请求中包括了目标应用程序的厂商信息和设备信息。
设备云基于厂家信息和设备信息,确定物联网设备的设备厂家与目标应用程序的厂家在该物联网设备上的合作类型,并查找该合作类型对应的连接信息。将连接信息以HTML页面的形式返回至终端设备。
终端设备基于连接信息下载物联网设备对应的原始应用程序,利用原始应用程序生成授权信息。通过原始应用程序将物联网设备的授权信息分享至目标应用程序。最后通过目标应用程序基于授权信息与物联网设备建立连接。
终端设备基于连接信息获取设备云对应的账号和密码,通过目标应用程序将账号和密码发送至设备云。设备云对账号和密码进行验证。当验证通过时,将物联网设备的授权信息返回至终端设备。终端设备通过目标应用程序基于授权信息与物联网设备建立连接。
如果查询结果为查询到合作类型,则终端设备向目标应用程序的服务器发送验证请求。目标应用程序的服务器再将验证请求发送至设备云。设备云根据验证请求对目标应用程序的服务器的身份进行验证,当验证通过时,返回物联网设备的授权信息至目标应用程序的服务器。目标应用程序的服务器再将授权信息发送至终端设备。终端设备通过目标应用程序基于授权信息与物联网设备建立连接。
如果查询结果为查询到合作类型,终端设备向目标应用程序的服务器发送离线授权信息的获取请求,离线授权信息为设备云采用私钥签名后的授权信息。目标应用程序的服务器将离线授权信息返回至终端设备。终端设备通过目标应用程序基于离线授权信息与物联网设备建立连接,即终端设备通过目标应用程序将离线授权信息发送至物联网设备。物联网设备采用公钥对离线授权信息进行验证,并在验证通过与目标应用程序建立连接。
终端设备在通过目标应用程序基于连接信息与物联网设备建立连接之后,通过目标应用程序基于连接将控制指令发送至物联网设备。物联网设备执行控制指令对应的操作。
以上各个操作的具体实施方式以及对应的有益效果可参见上述设备连接方法实施例的详细描述,在此不作赘述。
为便于更好的实施本申请实施例提供的设备连接方法,本申请实施例还提供一种基于上述设备连接方法的装置。其中名词的含义与上述设备连接方法中相同,具体实现细节可以参考方法实施例中的说明。
例如,如图8所示,该设备连接装置可以包括:
第一获取模块801,用于获取物联网设备的配置信息。
确定模块802,用于基于配置信息确定物联网设备的设备厂商,与终端设备上目标应用程序的厂商之间的合作类型。
第二获取模块803,用于获取合作类型对应的连接信息。
连接模块804,用于通过目标应用程序基于连接信息与物联网设备建立连接。
可选地,配置信息包括设备云的地址,设备云为物联网设备的服务器。
相应地,确定模块802具体用于执行:
根据地址向设备云发送目标应用程序的厂商信息,以使设备云基于厂商信息,确定物联网设备的设备厂商与目标应用程序的厂商之间的合作类型,以及合作类型对应的连接信息。
第二获取模块803具体用于执行:
接收设备云返回的合作类型对应的连接信息。
可选地,配置信息包括物联网设备的设备信息。
相应地,确定模块802具体用于执行:
根据地址向设备云发送目标应用程序的厂商信息和设备信息,以使设备云基于厂商信息和设备信息,确定物联网设备的设备厂商与目标应用程序的厂商的合作类型,以及合作类型对应的连接信息。
可选地,确定模块802具体用于执行:
从目标应用程序的服务器中查询地址对应的设备厂商与目标应用程序的厂商的合作类型;
若没有查询到合作类型,则根据地址向设备云发送目标应用程序的厂商信息。
可选地,该设备连接装置还包括:
发送模块,用于若查询到合作类型,则向目标应用程序的服务器发送验证请求,以使目标应用程序的服务器将验证请求发送至设备云进行验证身份,并接收设备云在验证通过时返回的授权信息。
相应地,连接模块804具体用于执行:
接收目标应用程序的服务器返回的授权信息;
通过目标应用程序基于授权信息与物联网设备建立连接。
可选地,发送模块还用于执行:
若查询到合作类型,则向目标应用程序的服务器发送离线授权信息的获取请求,离线授权信息为设备云采用私钥签名后的授权信息。
相应地,连接模块804具体用于执行:
接收目标应用程序的服务器基于获取请求返回的离线授权信息;
通过目标应用程序将离线授权信息发送至物联网设备,以使物联网设备采用公钥对离线授权信息进行验证,并在验证通过与目标应用程序建立连接。
可选地,连接模块804具体用于执行:
基于连接信息下载物联网设备对应的原始应用程序;
通过原始应用程序将物联网设备的授权信息分享至目标应用程序;
通过目标应用程序基于授权信息与物联网设备建立连接。
可选地,连接模块804具体用于执行:
基于连接信息获取设备云对应的账号和密码;
通过目标应用程序将账号和密码发送至设备云,以使设备云对账号和密码进行验证;
接收设备云在验证通过时返回的物联网设备的授权信息;
通过目标应用程序基于授权信息与物联网设备建立连接。
可选地,该设备连接装置还包括:
控制模块,用于通过目标应用程序基于连接将控制指令发送至物联网设备,以使物联网设备执行控制指令对应的操作。
具体实施时,以上各个模块可以作为独立的实体来实现,也可以进行任意组合,作为同一或若干个实体来实现,以上各个模块的具体实施方式以及对应的有益效果可参见前面的方法实施例,在此不再赘述。
为便于更好的实施本申请实施例提供的设备连接方法,本申请实施例还提供一种基于上述设备连接方法的装置。其中名词的含义与上述设备连接方法中相同,具体实现细节可以参考方法实施例中的说明。
例如,如图9所示,该设备连接装置可以包括:
接收模块901,用于接收目标信息。
确定模块902,用于若目标信息包括目标应用程序的厂商信息,则基于厂商信息确定设备厂商与目标应用程序的厂商的合作类型。
发送模块903,用于将合作类型对应的连接信息发送至终端设备,以使终端设备通过目标应用程序,基于连接信息与物联网设备建立连接。
可选地,发送模块903具体用于执行:
将连接信息发送至终端设备;
接收终端设备基于连接信息发送的账号和密码;
对账号和密码进行验证,并在验证通过时将物联网设备的授权信息返回至终端设备,以使终端设备通过目标应用程序基于授权信息与物联网设备建立连接。
可选地,该设备连接装置还包括:
验证模块,用于若目标信息包括验证请求,则基于验证请求对目标应用程序的服务器进行身份验证。
信息发送模块,用于当验证通过时将授权信息发送至目标应用程序的服务器,以使目标应用程序的服务器将授权信息发送至终端设备,授权信息用于指示终端设备通过目标应用程序与物联网设备建立连接。
可选地,该设备连接装置还包括:
签名模块,用于若目标信息包括授权信息,则采用私钥对授权信息进行签名,得到离线授权信息。
相应地,信息发送模块还用于执行:
将离线授权信息发送至目标应用程序的服务器,以使目标应用程序的服务器在接收到终端设备发送的获取请求后,将离线授权信息发送至终端设备,离线授权信息用于指示终端设备通过目标应用程序与物联网设备建立连接。
具体实施时,以上各个模块可以作为独立的实体来实现,也可以进行任意组合,作为同一或若干个实体来实现,以上各个模块的具体实施方式以及对应的有益效果可参见前面的方法实施例,在此不再赘述。
本申请实施例还提供一种电子设备,该电子设备可以是服务器或终端设备等,如图10所示,其示出了本申请实施例所涉及的电子设备的结构示意图,具体来讲:
该电子设备可以包括一个或者一个以上处理核心的处理器1001、一个或一个以上计算机可读存储介质的存储器1002、电源1003和输入单元1004等部件。本领域技术人员可以理解,图10中示出的电子设备结构并不构成对电子设备的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。其中:
处理器1001是该电子设备的控制中心,利用各种接口和线路连接整个电子设备的各个部分,通过运行或执行存储在存储器1002内的计算机程序和/或模块,以及调用存储在存储器1002内的数据,执行电子设备的各种功能和处理数据,从而对电子设备进行整体监控。可选的,处理器1001可包括一个或多个处理核心;优选的,处理器1001可集成应用处理器和调制解调处理器,其中,应用处理器主要处理操作系统、用户界面和应用程序等,调制解调处理器主要处理无线通信。可以理解的是,上述调制解调处理器也可以不集成到处理器1001中。
存储器1002可用于存储计算机程序以及模块,处理器1001通过运行存储在存储器1002的计算机程序以及模块,从而执行各种功能应用以及数据处理。存储器1002可主要包括存储程序区和存储数据区,其中,存储程序区可存储操作系统、至少一个功能所需的计算机程序(比如声音播放功能、图像播放功能等)等;存储数据区可存储根据电子设备的使用所创建的数据等。此外,存储器1002可以包括高速随机存取存储器,还可以包括非易失性存储器,例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。相应地,存储器1002还可以包括存储器控制器,以提供处理器1001对存储器1002的访问。
电子设备还包括给各个部件供电的电源1003,优选的,电源1003可以通过电源管理系统与处理器1001逻辑相连,从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。电源1003还可以包括一个或一个以上的直流或交流电源、再充电系统、电源故障检测电路、电源转换器或者逆变器、电源状态指示器等任意组件。
该电子设备还可包括输入单元1004,该输入单元1004可用于接收输入的数字或字符信息,以及产生与用户设置以及功能控制有关的键盘、鼠标、操作杆、光学或者轨迹球信号输入。
尽管未示出,电子设备还可以包括显示单元等,在此不再赘述。具体在本实施例中,电子设备中的处理器1001会按照如下的指令,将一个或一个以上的计算机程序的进程对应的可执行文件加载到存储器1002中,并由处理器1001来运行存储在存储器1002中的计算机程序,从而实现各种功能,比如:
获取物联网设备的配置信息;
基于配置信息确定物联网设备的设备厂商,与终端设备上目标应用程序的厂商之间的合作类型;
获取合作类型对应的连接信息;
通过目标应用程序基于连接信息与物联网设备建立连接。
以上各个操作的具体实施方式以及对应的有益效果可参见上文对设备连接方法的详细描述,在此不作赘述。
本领域普通技术人员可以理解,上述实施例的各种方法中的全部或部分步骤可以通过计算机程序来完成,或通过计算机程序控制相关的硬件来完成,该计算机程序可以存储于一计算机可读存储介质中,并由处理器进行加载和执行。
为此,本申请实施例提供一种计算机可读存储介质,其中存储有计算机程序,该计算机程序能够被处理器进行加载,以执行本申请实施例所提供的任一种设备连接方法中的步骤。例如,该计算机程序可以执行如下步骤:
获取物联网设备的配置信息;
基于配置信息确定物联网设备的设备厂商,与终端设备上目标应用程序的厂商之间的合作类型;
获取合作类型对应的连接信息;
通过目标应用程序基于连接信息与物联网设备建立连接。
以上各个操作的具体实施方式以及对应的有益效果可参见前面的方法实施例,在此不再赘述。
其中,该计算机可读存储介质可以包括:只读存储器(ROM,Read Only
Memory)、随机存取记忆体(RAM,Random
Access Memory)、磁盘或光盘等。
由于该计算机可读存储介质中所存储的计算机程序,可以执行本申请实施例所提供的任一种设备连接方法中的步骤,因此,可以实现本申请实施例所提供的任一种设备连接方法所能实现的有益效果,详见前面的实施例,在此不再赘述。
其中,根据本申请的一个方面,提供了一种计算机程序产品或计算机程序,该计算机程序产品或计算机程序包括计算机指令,该计算机指令存储在计算机可读存储介质中。计算机设备的处理器从计算机可读存储介质读取该计算机指令,处理器执行该计算机指令,使得该计算机设备执行上述设备连接方法。
以上对本申请实施例所提供的一种设备连接方法、装置、电子设备和计算机可读存储介质进行了详细介绍,本文中应用了具体个例对本申请的原理及实施方式进行了阐述,以上实施例的说明只是用于帮助理解本申请的方法及其核心思想;同时,对于本领域的技术人员,依据本申请的思想,在具体实施方式及应用范围上均会有改变之处,综上所述,本说明书内容不应理解为对本申请的限制。
Claims (20)
- 一种设备连接方法,其中,应用于终端设备,包括:获取物联网设备的配置信息;基于所述配置信息确定所述物联网设备的设备厂商,与所述终端设备上目标应用程序的厂商之间的合作类型;获取所述合作类型对应的连接信息;通过所述目标应用程序基于所述连接信息与所述物联网设备建立连接。
- 根据权利要求1所述的设备连接方法,其中,所述配置信息包括设备云的地址,所述设备云为所述物联网设备的服务器;相应地,所述基于所述配置信息确定所述物联网设备的设备厂商,与所述终端设备上目标应用程序的厂商之间的合作类型,包括:根据所述地址向所述设备云发送所述目标应用程序的厂商信息,以使所述设备云基于所述厂商信息,确定所述物联网设备的设备厂商与所述目标应用程序的厂商之间的合作类型,以及所述合作类型对应的连接信息;所述获取所述合作类型对应的连接信息包括:接收所述设备云返回的所述合作类型对应的连接信息。
- 根据权利要求2所述的设备连接方法,其中,所述配置信息包括所述物联网设备的设备信息;相应地,所述根据所述地址向所述设备云发送目标应用程序的厂商信息,以使所述设备云基于所述厂商信息,确定所述物联网设备的设备厂商与所述目标应用程序的厂商的合作类型,包括:根据所述地址向所述设备云发送目标应用程序的厂商信息和所述设备信息,以使设备云基于所述厂商信息和所述设备信息,确定所述物联网设备的设备厂商与所述目标应用程序的厂商的合作类型,以及所述合作类型对应的连接信息。
- 根据权利要求2所述的设备连接方法,其中,所述根据所述地址向所述设备云发送目标应用程序的厂商信息,包括:从所述目标应用程序的服务器中查询所述地址对应的设备厂商与所述目标应用程序的厂商的合作类型;若没有查询到所述合作类型,则根据所述地址向所述设备云发送目标应用程序的厂商信息。
- 根据权利要求4所述的设备连接方法,其中,在所述从所述目标应用程序的服务器中查询所述地址对应的设备厂商与所述目标应用程序的厂商的合作类型之后,还包括:若查询到所述合作类型,则向所述目标应用程序的服务器发送验证请求,以使所述目标应用程序的服务器将所述验证请求发送至所述设备云进行验证身份,并接收所述设备云在验证通过时返回的授权信息;接收所述目标应用程序的服务器返回的授权信息;通过所述目标应用程序基于所述授权信息与所述物联网设备建立连接。
- 根据权利要求4所述的设备连接方法,其中,在所述从所述目标应用程序的服务器中查询所述地址对应的设备厂商与所述目标应用程序的厂商的合作类型之后,还包括:若查询到所述合作类型,则向所述目标应用程序的服务器发送离线授权信息的获取请求,所述离线授权信息为所述设备云采用私钥签名后的授权信息;接收所述目标应用程序的服务器基于所述获取请求返回的离线授权信息;通过目标应用程序将所述离线授权信息发送至物联网设备,以使所述物联网设备采用公钥对所述离线授权信息进行验证,并在验证通过与所述目标应用程序建立连接。
- 根据权利要求1-4任一项所述的设备连接方法,其中,所述通过所述目标应用程序基于所述连接信息与所述物联网设备建立连接,包括:基于所述连接信息下载所述物联网设备对应的原始应用程序;通过所述原始应用程序将所述物联网设备的授权信息分享至所述目标应用程序;通过所述目标应用程序基于所述授权信息与所述物联网设备建立连接。
- 根据权利要求7所述的设备连接方法,其中,所述通过所述原始应用程序将所述物联网设备的授权信息分享至所述目标应用程序,包括:通过所述原始应用程序将授权信息存储于图形码中;通过目标应用程序扫描存储有所述授权信息的图形码,以将所述授权信息分享至所述目标应用程序。
- 根据权利要求1-4任一项所述的设备连接方法,其中,所述通过所述目标应用程序基于所述连接信息与所述物联网设备建立连接,包括:基于所述连接信息获取所述设备云对应的账号和密码;通过所述目标应用程序将所述账号和所述密码发送至所述设备云,以使所述设备云对所述账号和密码进行验证;接收所述设备云在验证通过时返回的所述物联网设备的授权信息;通过所述目标应用程序基于所述授权信息与所述物联网设备建立连接。
- 根据权利要求1所述的设备连接方法,其中,在所述通过所述目标应用程序基于所述连接信息与所述物联网设备建立连接之后,还包括:通过目标应用程序基于所述连接将控制指令发送至所述物联网设备,以使所述物联网设备执行所述控制指令对应的操作。
- 根据权利要求2所述的设备连接方法,其中,所述物联网设备的配置存储在所述物联网设备的图像码中,所述获取物联网设备的配置信息,包括:通过目标应用程序,扫描所述物联网设备的图形码,以获取物联网设备的配置信息。
- 根据权利要求2所述的设备连接方法,其中,所述根据所述地址向所述设备云发送所述目标应用程序的厂商信息,包括:根据所述目标应用程序的厂商信息和所述地址,生成统一资源定位器请求;向所述设备云发送所述统一资源定位器请求。
- 一种设备连接方法,其中,应用于设备云,包括:获取目标信息;若所述目标信息包括目标应用程序的厂商信息,则基于所述厂商信息确定物联网设备的设备厂商与所述目标应用程序的厂商的合作类型,以及所述合作类型对应的连接信息;将所述连接信息发送至终端设备,以使所述终端设备通过所述目标应用程序,基于所述连接信息与所述物联网设备建立连接。
- 根据权利要求13所述的设备连接方法,其中,所述将所述连接信息发送至终端设备,以使所述终端设备通过所述目标应用程序,基于所述连接信息与所述物联网设备建立连接,包括:将所述连接信息发送至终端设备;接收所述终端设备基于所述连接信息发送的所述账号和所述密码;对所述账号和密码进行验证,并在验证通过时将所述物联网设备的授权信息返回至所述终端设备,以使所述终端设备通过所述目标应用程序基于所述授权信息与所述物联网设备建立连接。
- 根据权利要求13所述的设备连接方法,其中,在所述获取目标信息之后,还包括:若所述目标信息包括验证请求,则基于所述验证请求对所述目标应用程序的服务器进行身份验证;当验证通过时将授权信息发送至所述目标应用程序的服务器,以使所述目标应用程序的服务器将所述授权信息发送至终端设备,所述授权信息用于指示所述终端设备通过所述目标应用程序与所述物联网设备建立连接。
- 根据权利要求13所述的设备连接方法,其中,在所述获取目标信息之后,还包括:若所述目标信息包括授权信息,则采用私钥对授权信息进行签名,得到离线授权信息;将所述离线授权信息发送至目标应用程序的服务器,以使所述目标应用程序的服务器在接收到终端设备发送的获取请求后,将所述离线授权信息发送至所述终端设备,所述离线授权信息用于指示所述终端设备通过所述目标应用程序与所述物联网设备建立连接。
- 一种设备连接装置,其中,应用于终端设备,包括:第一获取模块,用于获取物联网设备的配置信息;确定模块,用于基于所述配置信息确定所述物联网设备的设备厂商,与所述终端设备上目标应用程序的厂商之间的合作类型;第二获取模块,用于获取所述合作类型对应的连接信息;连接模块,用于通过所述目标应用程序基于所述连接信息与所述物联网设备建立连接。
- 一种设备连接装置,其中,应用于设备云,包括:接收模块,用于接收目标信息;确定模块,用于若所述目标信息包括所述目标应用程序的厂商信息,则基于所述厂商信息确定设备厂商与所述目标应用程序的厂商的合作类型;发送模块,用于将所述合作类型对应的连接信息发送至终端设备,以使所述终端设备通过所述目标应用程序,基于所述连接信息与所述物联网设备建立连接。
- 一种电子设备,其中,包括处理器和存储器,所述存储器存储有计算机程序,所述处理器用于运行所述存储器内的计算机程序,以执行权利要求1至12任一项所述的设备连接方法或权利要求13至16任一项所述的设备连接方法。
- 一种计算机可读存储介质,其中,所述计算机可读存储介质存储有计算机程序,所述计算机程序适于处理器进行加载,以执行权利要求1至12任一项所述的设备连接方法或权利要求13至16任一项所述的设备连接方法。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202111288774.5 | 2021-11-02 | ||
CN202111288774.5A CN116070290A (zh) | 2021-11-02 | 2021-11-02 | 设备连接方法、装置、电子设备和计算机可读存储介质 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023077922A1 true WO2023077922A1 (zh) | 2023-05-11 |
Family
ID=86170420
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/114351 WO2023077922A1 (zh) | 2021-11-02 | 2022-08-23 | 设备连接方法、装置、电子设备和计算机可读存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN116070290A (zh) |
WO (1) | WO2023077922A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20240106896A1 (en) * | 2022-09-23 | 2024-03-28 | T-Mobile Innovations Llc | Iot device one tap activation |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150052061A1 (en) * | 2011-05-26 | 2015-02-19 | Facebook, Inc. | Methods and systems for facilitating e-commerce payments |
CN112689006A (zh) * | 2020-12-22 | 2021-04-20 | 青岛海尔科技有限公司 | 物联网设备控制方法、装置、存储介质及电子装置 |
CN113438314A (zh) * | 2021-06-29 | 2021-09-24 | 青岛海尔科技有限公司 | 一种设备控制方法、装置、存储介质及电子装置 |
-
2021
- 2021-11-02 CN CN202111288774.5A patent/CN116070290A/zh active Pending
-
2022
- 2022-08-23 WO PCT/CN2022/114351 patent/WO2023077922A1/zh unknown
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150052061A1 (en) * | 2011-05-26 | 2015-02-19 | Facebook, Inc. | Methods and systems for facilitating e-commerce payments |
CN112689006A (zh) * | 2020-12-22 | 2021-04-20 | 青岛海尔科技有限公司 | 物联网设备控制方法、装置、存储介质及电子装置 |
CN113438314A (zh) * | 2021-06-29 | 2021-09-24 | 青岛海尔科技有限公司 | 一种设备控制方法、装置、存储介质及电子装置 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20240106896A1 (en) * | 2022-09-23 | 2024-03-28 | T-Mobile Innovations Llc | Iot device one tap activation |
Also Published As
Publication number | Publication date |
---|---|
CN116070290A (zh) | 2023-05-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10187474B2 (en) | Method and device for resource sharing between devices | |
CN107995215A (zh) | 智能家居设备的控制方法、装置及云平台服务器 | |
JP5601638B2 (ja) | ネットワークサービス交換の提供に使用される方法及びシステム | |
US9807166B2 (en) | Preconfigured SyncML profile categories | |
CN113347242B (zh) | 跨设备资源访问方法、装置、存储介质及电子设备 | |
US20140136720A1 (en) | Biometric-based wireless device association | |
CN113746633A (zh) | 物联网设备绑定方法、装置、系统、云服务器和存储介质 | |
WO2023077922A1 (zh) | 设备连接方法、装置、电子设备和计算机可读存储介质 | |
CN114844663B (zh) | 一种桌面共享方法、系统、存储介质及设备 | |
WO2022105365A1 (zh) | 设备控制的方法及系统、电子设备、及存储介质 | |
TW201543403A (zh) | 用於參與及響應應用程序的邀約方法、裝置以及系統 | |
US8135742B2 (en) | Proxy service providing apparatus, service providing method, and network system | |
EP3890376B1 (en) | Managing connections between a user device and peripheral devices | |
WO2013178157A2 (zh) | 私有云中设备间自动建立基于wifi局域网的方法及装置 | |
US9887872B2 (en) | Hybrid application environments including hosted applications and application servers for interacting with data in enterprise environments | |
CN113489695B (zh) | 私有云组网方法、装置、系统、计算机设备及存储介质 | |
AU2003234152A1 (en) | Method and system for distributing data | |
US7774464B2 (en) | Automatic syncML client profile creation for new servers | |
JP2005534099A (ja) | データベースの同期 | |
WO2023005434A1 (zh) | 设备配网方法、装置、存储介质及电子设备 | |
WO2017185498A1 (zh) | 一种注册管理方法和装置 | |
CN113746909A (zh) | 网络连接方法、装置、电子设备和计算机可读存储介质 | |
WO2024032085A1 (zh) | 终端设备的复位方法、系统、装置、智能设备及存储介质 | |
JP6551176B2 (ja) | 認証制御方法、認証プログラム、エージェントプログラム、サーバ装置、及びクライアント装置 | |
CN114650183B (zh) | 资源管理方法、装置、服务器及存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22888954 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |