CN113783829A - Method and device for realizing equipment access in cross-platform manner - Google Patents
Method and device for realizing equipment access in cross-platform manner Download PDFInfo
- Publication number
- CN113783829A CN113783829A CN202011349806.3A CN202011349806A CN113783829A CN 113783829 A CN113783829 A CN 113783829A CN 202011349806 A CN202011349806 A CN 202011349806A CN 113783829 A CN113783829 A CN 113783829A
- Authority
- CN
- China
- Prior art keywords
- platform
- equipment
- verification
- accessed
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 53
- 238000012795 verification Methods 0.000 claims abstract description 329
- 238000013475 authorization Methods 0.000 claims abstract description 116
- 230000004913 activation Effects 0.000 claims abstract description 52
- 238000004590 computer program Methods 0.000 claims description 9
- 230000004044 response Effects 0.000 abstract description 6
- 230000008569 process Effects 0.000 description 21
- 238000010586 diagram Methods 0.000 description 17
- 238000004891 communication Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000010200 validation analysis Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3263—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements
Abstract
The invention discloses a method and a device for realizing equipment access in a cross-platform mode, and relates to the technical field of computers. One embodiment of the method comprises: receiving a device activation binding request sent by an application associated with a platform to be accessed; generating a platform verification request according to the equipment activation binding request, and sending the platform verification request to a specified platform for authorization verification; and accessing the equipment according to the authorization verification result returned by the appointed platform. The implementation mode can realize cross-ecological authentication and equipment access, different ecological Internet of things equipment is accessed into an ecological system of an application service provider, and a software development kit is not required to be embedded, so that the user experience is improved, and meanwhile, the control flow and the data flow can be transmitted simultaneously, and the response time is saved.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and a device for realizing cross-platform equipment access.
Background
The ecology of the internet of things, especially the ecology of smart homes, is in a comparatively cracked state at present, that is, ecological devices accessed by different manufacturers and platforms generally cannot be directly connected with the ecology of a third party. In order to implement interconnection and intercommunication between devices in different ecology, a common form is to implement interconnection and intercommunication between control stream and data stream by using a cloud-to-cloud manner.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:
there are two problems with the cloud-to-cloud interworking approach: firstly, when the equipment activates the distribution network, an ecological application program of the opposite side needs to participate, or the application program of the local side needs to be embedded into a software development kit of the opposite side, so that the user experience is poor; second, the control and data streams pass through two stages, resulting in a longer response time.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for implementing device access across platforms, which can implement cross-ecological authentication and device access, and access devices of internet of things of different ecology to an ecosystem of an application service provider without embedding a software development kit, so as to improve user experience, and meanwhile, control streams and data streams can be transmitted simultaneously, thereby saving response time.
To achieve the above object, according to an aspect of the embodiments of the present invention, a method for implementing device access across platforms is provided.
A method for realizing device access in a cross-platform mode comprises the following steps:
receiving a device activation binding request sent by an application associated with the platform to be accessed;
generating a platform verification request according to the equipment activation binding request, and sending the platform verification request to a specified platform for authorization verification;
and accessing the equipment according to the authorization verification result returned by the appointed platform.
Optionally, the designated platform is the platform to be accessed or the device platform corresponding to the device, and the platform to be accessed and the device platform are mutually trusted platforms.
Optionally, the device activation binding request includes a token and domain name information of the platform to be accessed;
if the designated platform is the platform to be accessed, the platform verification request comprises a token of the platform to be accessed, the equipment identification, platform verification information generated by the equipment and a signature of the equipment private key on the platform verification information;
sending the platform verification request to a designated platform for authorization verification comprises:
according to the domain name information of the platform to be accessed, the platform verification request is sent to the platform to be accessed, so that the platform to be accessed performs the following authorization verification: verifying the validity of the platform verification request according to the token of the platform to be accessed, which is included in the platform verification request; after the platform verification request passes the verification, forwarding the platform verification request to the equipment platform so as to verify the legality of the platform to be accessed and the equipment through the equipment platform; and obtaining an authorization verification result fed back by the equipment platform.
Optionally, the device activation binding request includes domain name information of the platform to be accessed; if the designated platform is the equipment platform, the platform verification request comprises the domain name information of the platform to be accessed, the equipment identification, the platform verification information generated by the equipment and the signature of the equipment private key on the platform verification information;
sending the platform verification request to a designated platform for authorization verification comprises:
and sending the platform verification request to the equipment platform so that the equipment platform verifies the legality of the equipment and the platform to be accessed and generates an authorization verification result.
Optionally, the device platform verifies the platform verification information and the signature generated by the device according to the public key or the certificate of the device, so as to verify the validity of the device;
and the equipment platform verifies the legality of the platform to be accessed according to a certificate corresponding to the domain name information of the platform to be accessed, which is stored in advance.
Optionally, the authorization verification result includes verification information generated by the device platform and a signature performed on the verification information by using a private key of the device platform;
according to the authorization verification result returned by the appointed platform, the equipment access comprises the following steps:
and verifying the authorization verification result returned by the appointed platform by using the public key or the certificate of the equipment platform, and accessing the platform to be accessed after the verification is passed.
According to another aspect of the embodiments of the present invention, a method for implementing device access across platforms is provided.
A method for realizing device access in a cross-platform mode comprises the following steps:
an application associated with a platform to be accessed sends a device activation binding request to a device;
the equipment generates a platform verification request according to the equipment activation binding request and sends the platform verification request to a specified platform;
the appointed platform carries out authorization verification according to the platform verification request and returns an authorization verification result to the equipment;
and the equipment accesses the equipment according to the authorization verification result.
Optionally, the designated platform is the platform to be accessed or the device platform corresponding to the device, and the platform to be accessed and the device platform are mutually trusted platforms.
Optionally, the device activation binding request includes a token and domain name information of the platform to be accessed;
if the designated platform is the platform to be accessed, the platform verification request comprises a token of the platform to be accessed, the equipment identification, platform verification information generated by the equipment and a signature of the equipment private key on the platform verification information;
the device sending the platform verification request to a specified platform comprises:
the equipment sends the platform verification request to the platform to be accessed according to the domain name information of the platform to be accessed;
the step of the appointed platform performing authorization verification according to the platform verification request comprises the following steps:
the platform to be accessed verifies the validity of the platform verification request according to the token of the platform to be accessed, which is included in the platform verification request; after the platform passes the verification, the platform verification request is forwarded to the equipment platform;
the equipment platform verifies the legality of the platform to be accessed and the equipment, generates an authorization verification result and feeds the authorization verification result back to the platform to be accessed;
and the platform to be accessed receives the authorization verification result fed back by the equipment platform.
Optionally, the device activation binding request includes domain name information of the platform to be accessed;
if the designated platform is the equipment platform, the platform verification request comprises the domain name information of the platform to be accessed, the equipment identification, the platform verification information generated by the equipment and the signature of the equipment private key on the platform verification information;
the step of the appointed platform performing authorization verification according to the platform verification request comprises the following steps:
and the equipment platform verifies the legality of the equipment and the platform to be accessed and generates an authorization verification result.
Optionally, the device platform verifies the platform verification information and the signature generated by the device according to the public key or the certificate of the device, so as to verify the validity of the device;
and the equipment platform verifies the legality of the platform to be accessed according to a certificate corresponding to the domain name information of the platform to be accessed, which is stored in advance.
Optionally, the authorization verification result includes verification information generated by the device platform and a signature performed on the verification information by using a private key of the device platform;
the device performs device access according to the authorization verification result, and the method comprises the following steps:
and the equipment verifies the authorization verification result by using the public key or the certificate of the equipment platform, and accesses the platform to be accessed after the verification is passed.
According to another aspect of the embodiments of the present invention, an apparatus for implementing device access across platforms is provided.
An apparatus for enabling device access across platforms, the apparatus being adapted to a device to be accessed to a platform, the apparatus comprising:
a receiving request module, configured to receive a device activation binding request sent by an application associated with the platform to be accessed;
the authorization verification module is used for generating a platform verification request according to the equipment activation binding request and sending the platform verification request to a specified platform for authorization verification;
and the equipment access module is used for accessing the equipment according to the authorization verification result returned by the appointed platform.
Optionally, the designated platform is the platform to be accessed or the device platform corresponding to the device, and the platform to be accessed and the device platform are mutually trusted platforms.
Optionally, the device activation binding request includes a token and domain name information of the platform to be accessed;
if the designated platform is the platform to be accessed, the platform verification request comprises a token of the platform to be accessed, the equipment identification, platform verification information generated by the equipment and a signature of the equipment private key on the platform verification information;
the authorization verification module is further to: according to the domain name information of the platform to be accessed, the platform verification request is sent to the platform to be accessed, so that the platform to be accessed performs the following authorization verification: verifying the validity of the platform verification request according to the token of the platform to be accessed, which is included in the platform verification request; after the platform verification request passes the verification, forwarding the platform verification request to the equipment platform so as to verify the legality of the platform to be accessed and the equipment through the equipment platform; and obtaining an authorization verification result fed back by the equipment platform.
Optionally, the device activation binding request includes domain name information of the platform to be accessed; if the designated platform is the equipment platform, the platform verification request comprises the domain name information of the platform to be accessed, the equipment identification, the platform verification information generated by the equipment and the signature of the equipment private key on the platform verification information;
the authorization verification module is further to: and sending the platform verification request to the equipment platform so that the equipment platform verifies the legality of the equipment and the platform to be accessed and generates an authorization verification result.
Optionally, the apparatus further comprises a device verification module configured to: the equipment platform verifies the platform verification information and the signature generated by the equipment according to the public key or the certificate of the equipment so as to verify the validity of the equipment;
the apparatus also includes a platform verification module to: and the equipment platform verifies the legality of the platform to be accessed according to a certificate corresponding to the domain name information of the platform to be accessed, which is stored in advance.
Optionally, the authorization verification result includes verification information generated by the device platform and a signature performed on the verification information by using a private key of the device platform;
the device access module is further configured to: and verifying the authorization verification result returned by the appointed platform by using the public key or the certificate of the equipment platform, and accessing the platform to be accessed after the verification is passed.
According to another aspect of the embodiment of the invention, a device for realizing cross-platform device access is provided.
An apparatus for enabling device access across platforms, comprising:
the request sending module is used for sending a device activation binding request to the device by the application associated with the platform to be accessed;
the request verification module is used for generating a platform verification request by the equipment according to the equipment activation binding request and sending the platform verification request to a specified platform;
the authorization verification module is used for the appointed platform to carry out authorization verification according to the platform verification request and return an authorization verification result to the equipment;
and the equipment access module is used for accessing the equipment by the equipment according to the authorization verification result.
Optionally, the designated platform is the platform to be accessed or the device platform corresponding to the device, and the platform to be accessed and the device platform are mutually trusted platforms.
Optionally, the device activation binding request includes a token and domain name information of the platform to be accessed;
if the designated platform is the platform to be accessed, the platform verification request comprises a token of the platform to be accessed, the equipment identification, platform verification information generated by the equipment and a signature of the equipment private key on the platform verification information;
the request validation module is further to: the equipment sends the platform verification request to the platform to be accessed according to the domain name information of the platform to be accessed;
the authorization verification module is further to: the platform to be accessed verifies the validity of the platform verification request according to the token of the platform to be accessed, which is included in the platform verification request; after the platform passes the verification, the platform verification request is forwarded to the equipment platform; the equipment platform verifies the legality of the platform to be accessed and the equipment, generates an authorization verification result and feeds the authorization verification result back to the platform to be accessed; and the platform to be accessed receives the authorization verification result fed back by the equipment platform.
Optionally, the device activation binding request includes domain name information of the platform to be accessed;
if the designated platform is the equipment platform, the platform verification request comprises the domain name information of the platform to be accessed, the equipment identification, the platform verification information generated by the equipment and the signature of the equipment private key on the platform verification information;
the authorization verification module is further to: and the equipment platform verifies the legality of the equipment and the platform to be accessed and generates an authorization verification result.
Optionally, the apparatus further comprises a device verification module configured to: the equipment platform verifies the platform verification information and the signature generated by the equipment according to the public key or the certificate of the equipment so as to verify the validity of the equipment;
the apparatus also includes a platform verification module to: and the equipment platform verifies the legality of the platform to be accessed according to a certificate corresponding to the domain name information of the platform to be accessed, which is stored in advance.
Optionally, the authorization verification result includes verification information generated by the device platform and a signature performed on the verification information by using a private key of the device platform;
the device access module is further configured to: and the equipment verifies the authorization verification result by using the public key or the certificate of the equipment platform, and accesses the platform to be accessed after the verification is passed.
According to another aspect of the embodiment of the invention, the electronic equipment for realizing equipment access in a cross-platform mode is provided.
An electronic device for enabling device access across platforms, comprising: one or more processors; the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement the method for realizing the cross-platform device access provided by the embodiment of the invention.
According to yet another aspect of embodiments of the present invention, a computer-readable medium is provided.
A computer readable medium, on which a computer program is stored, the program, when executed by a processor, implements a method for cross-platform device access provided by an embodiment of the present invention.
One embodiment of the above invention has the following advantages or benefits: receiving a device activation binding request sent by an application associated with the platform to be accessed; generating a platform verification request according to the equipment activation binding request, and sending the platform verification request to a specified platform for authorization verification; according to the authorization verification result returned by the appointed platform, the technical means of equipment access is carried out, different ecological Internet of things equipment can be accessed into the ecological system of the user without agreement on protocols and schemes of a communication layer and only under the condition of involving a cross-ecological authentication and access process, a software development kit is not required to be embedded, the process is simple, and therefore user experience is improved; and the control flow and the data flow can be transmitted simultaneously, so that the response time is saved. Meanwhile, the whole process of realizing the equipment authentication access by crossing the platforms only needs the platform of the other party to carry out simple authorization, thereby ensuring the ecological controllability of the other party.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic diagram of the main steps of a method for implementing device access across platforms according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating a device-centric cross-platform device authentication access process according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a process for platform-centric cross-platform device authenticated access according to another embodiment of the present invention;
FIG. 4 is a schematic diagram of the main modules of an apparatus for cross-platform device access implementation according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of the main modules of an apparatus for cross-platform device access implementation according to another embodiment of the present invention;
FIG. 6 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 7 is a schematic block diagram of a computer system suitable for use in implementing a terminal device or server of an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic diagram of main steps of a method for implementing device access across platforms according to an embodiment of the present invention, and the embodiment of the present invention addresses a problem that a scene is an ecological device of different manufacturers and platforms, and generally cannot be directly connected to a third-party ecology. As shown in fig. 1, the method for implementing device access across platforms according to the embodiment of the present invention mainly includes the following steps S101 to S103.
Step S101: receiving a device activation binding request sent by an application associated with a platform to be accessed;
step S102: generating a platform verification request according to the equipment activation binding request, and sending the platform verification request to a specified platform for authorization verification;
step S103: and accessing the equipment according to the authorization verification result returned by the appointed platform.
According to the steps S101 to S103, protocols and schemes of a communication layer do not need to be agreed in the whole process, only the process of cross-ecological authentication and access is involved, the method has strong practical operability, the simple process can realize the access of different ecological Internet of things devices into the ecological system of the local side, strong constraint on the authentication scheme is not needed, only simple authorization is needed to be carried out on the platform of the opposite side, and meanwhile, the ecological controllability of the opposite side is ensured.
In the embodiment of the invention, the designated platform is a platform to be accessed or an equipment platform corresponding to the equipment, and the platform to be accessed and the equipment platform are mutually trusted platforms.
According to one embodiment of the invention, the device activation binding request comprises a token and domain name information of the platform to be accessed;
if the appointed platform is the platform to be accessed, the platform verification request comprises a token of the platform to be accessed, an equipment identifier, platform verification information generated by equipment and a signature of an equipment private key on the platform verification information;
sending the platform verification request to a designated platform for authorization verification comprises:
according to the domain name information of the platform to be accessed, a platform verification request is sent to the platform to be accessed, so that the platform to be accessed performs the following authorization verification: verifying the validity of the platform verification request according to the token of the platform to be accessed, which is included in the platform verification request; after the verification is passed, the platform verification request is forwarded to the equipment platform so as to verify the legitimacy of the platform to be accessed and the equipment through the equipment platform; and obtaining an authorization verification result fed back by the equipment platform.
According to another embodiment of the invention, the device activation binding request comprises domain name information of the platform to be accessed;
if the appointed platform is the equipment platform, the platform verification request comprises domain name information of the platform to be accessed, equipment identification, platform verification information generated by the equipment and a signature of an equipment private key on the platform verification information;
sending the platform verification request to a designated platform for authorization verification comprises:
and sending the platform verification request to the equipment platform so that the equipment platform verifies the legality of the equipment and the platform to be accessed and generates an authorization verification result.
According to another embodiment of the present invention, the device platform verifies the platform verification information and signature generated by the device according to the public key or certificate of the device to verify the validity of the device;
and the equipment platform verifies the legality of the platform to be accessed according to the pre-stored certificate corresponding to the domain name information of the platform to be accessed.
According to yet another embodiment of the present invention, the authorization verification result includes verification information generated by the device platform and a signature on the verification information using a private key of the device platform;
according to the authorization verification result returned by the appointed platform, the equipment access comprises the following steps:
and verifying the authorization verification result returned by the appointed platform by using a public key or a certificate of the equipment platform, and accessing the platform to be accessed after the verification is passed.
Fig. 2 is a schematic diagram of a device-centric cross-platform device authentication access process according to an embodiment of the present invention. In the introduction of the embodiment of the present invention, the platform to be accessed and the device platform are mutually trusted platforms, that is, the a platform has previously trusted the B platform (for example, a B platform certificate is placed). As shown in fig. 2, the process of performing device authentication access across platforms with a device as a center in the embodiment of the present invention mainly includes:
1. and the application associated with the platform to be accessed sends a device activation binding request to the device, wherein the device activation binding request comprises a token, domain name information and the like of the platform to be accessed. In this embodiment, namely: the manufacturer B APP requests to activate and bind the equipment A, and the request carries platform B information, such as token, domain name information and the like accessed to the platform B;
2. the device generates a platform verification request according to the device activation binding request, and sends the platform verification request to the device platform, wherein the platform verification request comprises domain name information of the platform to be accessed, a device identifier, platform verification information generated by the device, and a signature of a device private key on the platform verification information. In this embodiment, namely: the a device requests from the a platform to verify whether the B platform is an accessible, trusted platform. The request can carry information such as B platform domain name information, A equipment generation verification information, signature of A equipment private key to the verification information, equipment identification id of A equipment and the like;
3. the device platform verifies the legality of the device and the platform to be accessed, generates an authorization verification result and returns the authorization verification result to the device, the device platform verifies platform verification information and signature generated by the device according to a public key or a certificate of the device so as to verify the legality of the device, the device platform verifies the legality of the platform to be accessed according to a prestored certificate corresponding to domain name information of the platform to be accessed, and the authorization verification result comprises verification information generated by the device platform and signature performed on the verification information by using a private key of the device platform. In this embodiment, namely: the a-platform first verifies the legitimacy of the a-device, for example, by verifying the verification information and its signature with the device public key or certificate to verify the legitimacy of the a-device. If the A equipment passes the validity verification, then verifying whether the B platform is in the trusted information list, for example: and checking whether the platform certificate corresponding to the domain name of the platform B is authorized and trusted. After the verification of the device a and the platform B passes, the platform a issues acknowledgement information to the device a, otherwise, issues negative information, and the information issued by the platform a to the device a should include the verification information of the platform a, including, for example: the verification information generated by the platform A and the signature of the platform A on the verification information by using a private key;
4. the equipment verifies the authorization verification result by using the public key or the certificate of the equipment platform, and accesses the platform to be accessed after the verification is passed. In this embodiment, namely: the A device verifies the legality of the information of the A platform, for example, the public key or certificate of the A platform is used for verifying the verification information and the signature thereof. And after the legality of the information of the platform A is verified, if the information confirms that the platform B is legal, connecting to the platform B. Otherwise, the connection is refused.
5. And informing the manufacturer B of the APP activation access result by the device A or the platform B.
Fig. 3 is a schematic diagram of a process of performing device authentication access across platforms with platform as a center according to another embodiment of the present invention. In the introduction of the embodiment of the present invention, the platform to be accessed and the device platform are mutually trusted platforms, that is, the a platform has previously trusted the B platform (for example, a B platform certificate is placed). As shown in fig. 3, the process of performing device authentication access across platforms with platform as a center according to the embodiment of the present invention is as follows:
1. and the application associated with the platform to be accessed sends a device activation binding request to the device, wherein the device activation binding request comprises the token and the domain name information of the platform to be accessed. In this embodiment, namely: the manufacturer B APP requests to activate and bind the equipment A, and the request carries platform B information, such as token and domain name information accessed to the platform B;
2. the device sends a platform verification request to the platform to be accessed according to the domain name information of the platform to be accessed, wherein the platform verification request comprises a token of the platform to be accessed, a device identifier, platform verification information generated by the device and a signature of a device private key on the platform verification information. In this embodiment, namely: the method comprises the steps that the device A requests the platform B to verify whether the platform B is an accessible and trusted platform or not, wherein the request comprises information such as token of the platform B, verification information generated by the device A, signature of a private key of the device A on the verification information, device identification id of the device A and the like;
3. and the platform to be accessed verifies the validity of the platform verification request according to the token of the platform to be accessed, which is included in the platform verification request, and forwards the platform verification request to the equipment platform after the platform verification passes. In this embodiment, namely: the platform B verifies the validity of the access information sent by the equipment A (for example, a token included in the verification request), and after the verification is passed, the information carried by the equipment A is forwarded to the platform A to request verification and authorization;
4. the equipment platform verifies the legality of the platform to be accessed and the equipment, an authorization verification result is generated, the authorization verification result is fed back to the platform to be accessed, the equipment platform verifies platform verification information and a signature generated by the equipment according to a public key or a certificate of the equipment so as to verify the legality of the equipment, the equipment platform verifies the legality of the platform to be accessed according to a prestored certificate corresponding to domain name information of the platform to be accessed, and the authorization verification result comprises verification information generated by the equipment platform and a signature performed on the verification information by using a private key of the equipment platform. In this embodiment, namely: platform a first verifies the legitimacy of platform B, for example by means of a platform B certificate. After the verification is passed, the validity of the a device is verified, for example, the verification information signature and the signature are verified by using the device public key or certificate. And after the validity verification of the device A passes, replying the platform B confirmation information. And if the legality of the B platform or the legality of the A equipment is not verified, replying to the B platform negative information. The confirmation message of the reply B platform should include verification information that the a platform authorizes the a device, including: the verification information generated by the platform A and the signature of the platform A on the verification information by using a private key;
5. the equipment verifies the authorization verification result by using the public key or the certificate of the equipment platform, and accesses the platform to be accessed after the verification is passed. In this embodiment, namely: after receiving the authorization information forwarded by the B platform, the a device performs authentication, for example, using a public key or a certificate of the a platform to verify the authentication information and the signature. After the verification is passed, the device A is accessed to the platform B, otherwise, the access is refused;
6. and informing the manufacturer B of the APP activation access result by the device A or the platform B.
Fig. 4 is a schematic diagram of main modules of an apparatus for implementing device access across platforms according to an embodiment of the present invention. As shown in fig. 4, an apparatus 400 for implementing device access across platforms according to an embodiment of the present invention mainly includes a request receiving module 401, an authorization verification module 402, and a device access module 403.
A receiving request module 401, configured to receive a device activation binding request sent by an application associated with a platform to be accessed;
an authorization verification module 402, configured to generate a platform verification request according to the device activation binding request, and send the platform verification request to a specified platform for authorization verification;
and the device access module 403 is configured to perform device access according to an authorization verification result returned by the designated platform.
In the embodiment of the invention, the designated platform is a platform to be accessed or an equipment platform corresponding to the equipment, and the platform to be accessed and the equipment platform are mutually trusted platforms.
According to one embodiment of the invention, the device activation binding request comprises a token and domain name information of the platform to be accessed;
if the appointed platform is the platform to be accessed, the platform verification request comprises a token of the platform to be accessed, an equipment identifier, platform verification information generated by equipment and a signature of an equipment private key on the platform verification information;
the authorization verification module 402 is further configured to: according to the domain name information of the platform to be accessed, a platform verification request is sent to the platform to be accessed, so that the platform to be accessed performs the following authorization verification: verifying the validity of the platform verification request according to the token of the platform to be accessed, which is included in the platform verification request; after the verification is passed, the platform verification request is forwarded to the equipment platform so as to verify the legitimacy of the platform to be accessed and the equipment through the equipment platform; and obtaining an authorization verification result fed back by the equipment platform.
According to another embodiment of the invention, the device activation binding request comprises domain name information of the platform to be accessed;
if the appointed platform is the equipment platform, the platform verification request comprises domain name information of the platform to be accessed, equipment identification, platform verification information generated by the equipment and a signature of an equipment private key on the platform verification information;
the authorization verification module 402 is further configured to: and sending the platform verification request to the equipment platform so that the equipment platform verifies the legality of the equipment and the platform to be accessed and generates an authorization verification result.
According to yet another embodiment of the present invention, the apparatus 400 further comprises a device authentication module (not shown in the figures) for: the equipment platform verifies the platform verification information and the signature generated by the equipment according to the public key or the certificate of the equipment so as to verify the validity of the equipment; the apparatus 400 further comprises a platform verification module (not shown) for: and the equipment platform verifies the legality of the platform to be accessed according to the pre-stored certificate corresponding to the domain name information of the platform to be accessed.
According to yet another embodiment of the present invention, the authorization verification result includes verification information generated by the device platform and a signature on the verification information using a private key of the device platform;
the device access module 403 is further configured to: and verifying the authorization verification result returned by the appointed platform by using a public key or a certificate of the equipment platform, and accessing the platform to be accessed after the verification is passed.
Fig. 5 is a schematic diagram of main modules of an apparatus for implementing device access across platforms according to another embodiment of the present invention. As shown in fig. 5, an apparatus 500 for implementing device access across platforms according to an embodiment of the present invention mainly includes a request sending module 501, a request verification module 502, an authorization verification module 503, and a device access module 504.
A request sending module 501, configured to send a device activation binding request to a device by using an application associated with a platform to be accessed;
a request verification module 502, configured to generate a platform verification request according to the device activation binding request, and send the platform verification request to a specified platform;
the authorization verification module 503 is configured to designate a platform to perform authorization verification according to the platform verification request, and return an authorization verification result to the device;
and the device access module 504 is configured to perform device access by the device according to the authorization verification result.
In the embodiment of the invention, the designated platform is a platform to be accessed or an equipment platform corresponding to the equipment, and the platform to be accessed and the equipment platform are mutually trusted platforms.
According to one embodiment of the invention, the device activation binding request comprises a token and domain name information of the platform to be accessed;
if the appointed platform is the platform to be accessed, the platform verification request comprises a token of the platform to be accessed, an equipment identifier, platform verification information generated by equipment and a signature of an equipment private key on the platform verification information;
the request validation module 502 is further configured to: the equipment sends a platform verification request to the platform to be accessed according to the domain name information of the platform to be accessed;
the authorization verification module 503 is further configured to: the platform to be accessed verifies the validity of the platform verification request according to the token of the platform to be accessed, which is included in the platform verification request; after the verification is passed, the platform verification request is forwarded to the equipment platform; the equipment platform verifies the legality of the platform to be accessed and the equipment, generates an authorization verification result and feeds back the authorization verification result to the platform to be accessed; and the platform to be accessed receives the authorization verification result fed back by the equipment platform.
According to another embodiment of the invention, the device activation binding request comprises domain name information of the platform to be accessed;
if the appointed platform is the equipment platform, the platform verification request comprises domain name information of the platform to be accessed, equipment identification, platform verification information generated by the equipment and a signature of an equipment private key on the platform verification information;
the authorization verification module is further to: and the equipment platform verifies the legality of the equipment and the platform to be accessed and generates an authorization verification result.
According to a further embodiment of the invention, the apparatus further comprises a device authentication module (not shown in the figures) for: the equipment platform verifies the platform verification information and the signature generated by the equipment according to the public key or the certificate of the equipment so as to verify the validity of the equipment;
the apparatus further comprises a platform verification module (not shown in the figures) for: and the equipment platform verifies the legality of the platform to be accessed according to the pre-stored certificate corresponding to the domain name information of the platform to be accessed.
According to a further embodiment of the present invention, the authorization verification result includes verification information generated by the device platform and a signature on the verification information using a private key of the device platform;
the device access module 504 is further configured to: the equipment verifies the authorization verification result by using the public key or the certificate of the equipment platform, and accesses the platform to be accessed after the verification is passed.
According to the technical scheme of the embodiment of the invention, the equipment activation binding request sent by the application associated with the platform to be accessed is received; generating a platform verification request according to the equipment activation binding request, and sending the platform verification request to a specified platform for authorization verification; according to the authorization verification result returned by the appointed platform, the technical means of equipment access is carried out, different ecological Internet of things equipment can be accessed into the ecological system of the user without agreement on protocols and schemes of a communication layer and only under the condition of involving a cross-ecological authentication and access process, a software development kit is not required to be embedded, the process is simple, and therefore user experience is improved; and the control flow and the data flow can be transmitted simultaneously, so that the response time is saved. Meanwhile, the whole process of realizing the equipment authentication access by crossing the platforms only needs the platform of the other party to carry out simple authorization, thereby ensuring the ecological controllability of the other party.
Fig. 6 illustrates an exemplary system architecture 600 of a method for enabling device access across platforms or an apparatus for enabling device access across platforms to which embodiments of the present invention may be applied.
As shown in fig. 6, the system architecture 600 may include terminal devices 601, 602, 603, a network 604, and a server 605. The network 604 serves to provide a medium for communication links between the terminal devices 601, 602, 603 and the server 605. Network 604 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.
A user may use the terminal devices 601, 602, 603 to interact with the server 605 via the network 604 to receive or send messages or the like. Various applications, such as a device control type application, an intelligent household appliance type application, a platform connection type application, etc. (just examples), may be installed on the terminal devices 601, 602, 603.
The terminal devices 601, 602, 603 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 605 may be a server providing various services, such as a background management server (for example only) providing support for intelligent appliances controlled by users using the terminal devices 601, 602, 603. The backend management server may analyze and perform other processing on the received data such as the connection request, and feed back a processing result (for example, a connection result — just an example) to the terminal device.
It should be noted that the method for implementing device access across platforms provided in the embodiment of the present invention is generally executed by the server 605, and accordingly, the apparatus for implementing device access across platforms is generally disposed in the server 605.
It should be understood that the number of terminal devices, networks, and servers in fig. 6 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 7, a block diagram of a computer system 700 suitable for use with a terminal device or server implementing an embodiment of the invention is shown. The terminal device or the server shown in fig. 7 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU)701, which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data necessary for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 701.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units or modules described in the embodiments of the present invention may be implemented by software, or may be implemented by hardware. The described units or modules may also be provided in a processor, and may be described as: a processor comprises a request receiving module, an authorization verification module and a device access module. The names of these units or modules do not in some cases form a limitation on the units or modules themselves, for example, the module for receiving a request may also be described as a "module for receiving a device activation binding request from an application associated with the platform to be accessed".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: receiving a device activation binding request sent by an application associated with the platform to be accessed; generating a platform verification request according to the equipment activation binding request, and sending the platform verification request to a specified platform for authorization verification; and accessing the equipment according to the authorization verification result returned by the appointed platform.
According to the technical scheme of the embodiment of the invention, the equipment activation binding request sent by the application associated with the platform to be accessed is received; generating a platform verification request according to the equipment activation binding request, and sending the platform verification request to a specified platform for authorization verification; according to the authorization verification result returned by the appointed platform, the technical means of equipment access is carried out, different ecological Internet of things equipment can be accessed into the ecological system of the user without agreement on protocols and schemes of a communication layer and only under the condition of involving a cross-ecological authentication and access process, a software development kit is not required to be embedded, the process is simple, and therefore user experience is improved; and the control flow and the data flow can be transmitted simultaneously, so that the response time is saved. Meanwhile, the whole process of realizing the equipment authentication access by crossing the platforms only needs the platform of the other party to carry out simple authorization, thereby ensuring the ecological controllability of the other party.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (9)
1. A method for realizing device access across platforms is characterized in that the method is suitable for a device to be accessed to a platform, and the method comprises the following steps:
receiving a device activation binding request sent by an application associated with the platform to be accessed;
generating a platform verification request according to the equipment activation binding request, and sending the platform verification request to a specified platform for authorization verification;
and accessing the equipment according to the authorization verification result returned by the appointed platform.
2. The method according to claim 1, wherein the designated platform is the platform to be accessed or a device platform corresponding to the device, and the platform to be accessed and the device platform are mutually trusted platforms.
3. The method of claim 2, wherein the device activation binding request comprises a token and domain name information of the platform to be accessed;
if the designated platform is the platform to be accessed, the platform verification request comprises a token of the platform to be accessed, the equipment identification, platform verification information generated by the equipment and a signature of the equipment private key on the platform verification information;
sending the platform verification request to a designated platform for authorization verification comprises:
according to the domain name information of the platform to be accessed, the platform verification request is sent to the platform to be accessed, so that the platform to be accessed performs the following authorization verification: verifying the validity of the platform verification request according to the token of the platform to be accessed, which is included in the platform verification request; after the platform verification request passes the verification, forwarding the platform verification request to the equipment platform so as to verify the legality of the platform to be accessed and the equipment through the equipment platform; and obtaining an authorization verification result fed back by the equipment platform.
4. The method of claim 2, wherein the device activation binding request includes domain name information of the platform to be accessed;
if the designated platform is the equipment platform, the platform verification request comprises the domain name information of the platform to be accessed, the equipment identification, the platform verification information generated by the equipment and the signature of the equipment private key on the platform verification information;
sending the platform verification request to a designated platform for authorization verification comprises:
and sending the platform verification request to the equipment platform so that the equipment platform verifies the legality of the equipment and the platform to be accessed and generates an authorization verification result.
5. The method according to claim 3 or 4, wherein the device platform verifies the platform verification information and the signature generated by the device according to a public key or certificate of the device to verify the validity of the device;
and the equipment platform verifies the legality of the platform to be accessed according to a certificate corresponding to the domain name information of the platform to be accessed, which is stored in advance.
6. The method of claim 3 or 4, wherein the authorization verification result comprises verification information generated by the device platform and a signature on the verification information using a private key of the device platform;
according to the authorization verification result returned by the appointed platform, the equipment access comprises the following steps:
and verifying the authorization verification result returned by the appointed platform by using the public key or the certificate of the equipment platform, and accessing the platform to be accessed after the verification is passed.
7. An apparatus for enabling device access across platforms, the apparatus being adapted to a device to be accessed to a platform, the apparatus comprising:
a receiving request module, configured to receive a device activation binding request sent by an application associated with the platform to be accessed;
the authorization verification module is used for generating a platform verification request according to the equipment activation binding request and sending the platform verification request to a specified platform for authorization verification;
and the equipment access module is used for accessing the equipment according to the authorization verification result returned by the appointed platform.
8. An electronic device for realizing device access in a cross-platform manner, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-6.
9. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011349806.3A CN113783829B (en) | 2020-11-26 | 2020-11-26 | Method and device for realizing equipment access across platforms |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011349806.3A CN113783829B (en) | 2020-11-26 | 2020-11-26 | Method and device for realizing equipment access across platforms |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113783829A true CN113783829A (en) | 2021-12-10 |
| CN113783829B CN113783829B (en) | 2024-03-05 |
Family
ID=78835248
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011349806.3A Active CN113783829B (en) | 2020-11-26 | 2020-11-26 | Method and device for realizing equipment access across platforms |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113783829B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114584313A (en) * | 2022-02-25 | 2022-06-03 | 杭州萤石软件有限公司 | Equipment physical identity authentication method, system and device and first platform |
| WO2023116131A1 (en) * | 2021-12-23 | 2023-06-29 | 深圳Tcl新技术有限公司 | Cross-ecological device management and control method and apparatus, and storage medium and electronic device |
| WO2024016124A1 (en) * | 2022-07-18 | 2024-01-25 | Oppo广东移动通信有限公司 | Device configuration methods and apparatuses, and communication device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9112854B1 (en) * | 2013-09-11 | 2015-08-18 | Amazon Technologies, Inc. | Secure communication between applications on untrusted platforms |
| WO2016015436A1 (en) * | 2014-07-28 | 2016-02-04 | 百度在线网络技术（北京）有限公司 | Platform authorization method, platform server, application client, system, and storage medium |
| CN107819805A (en) * | 2016-09-14 | 2018-03-20 | 北京京东尚科信息技术有限公司 | Smart machine control method and system |
| CN107995215A (en) * | 2017-12-20 | 2018-05-04 | 青岛海信智慧家居系统股份有限公司 | Control method, device and the cloud platform server of smart home device |
| CN110365711A (en) * | 2019-08-20 | 2019-10-22 | 中国工商银行股份有限公司 | Multi-platform user identification relevancy method and device |
| CN110417730A (en) * | 2019-06-17 | 2019-11-05 | 平安科技（深圳）有限公司 | The unified access method and relevant device of multiple utility program |
| CN110972131A (en) * | 2019-10-31 | 2020-04-07 | 阿里巴巴集团控股有限公司 | Authorization and control method, device, system and storage medium |
-
2020
- 2020-11-26 CN CN202011349806.3A patent/CN113783829B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9112854B1 (en) * | 2013-09-11 | 2015-08-18 | Amazon Technologies, Inc. | Secure communication between applications on untrusted platforms |
| WO2016015436A1 (en) * | 2014-07-28 | 2016-02-04 | 百度在线网络技术（北京）有限公司 | Platform authorization method, platform server, application client, system, and storage medium |
| CN107819805A (en) * | 2016-09-14 | 2018-03-20 | 北京京东尚科信息技术有限公司 | Smart machine control method and system |
| CN107995215A (en) * | 2017-12-20 | 2018-05-04 | 青岛海信智慧家居系统股份有限公司 | Control method, device and the cloud platform server of smart home device |
| CN110417730A (en) * | 2019-06-17 | 2019-11-05 | 平安科技（深圳）有限公司 | The unified access method and relevant device of multiple utility program |
| CN110365711A (en) * | 2019-08-20 | 2019-10-22 | 中国工商银行股份有限公司 | Multi-platform user identification relevancy method and device |
| CN110972131A (en) * | 2019-10-31 | 2020-04-07 | 阿里巴巴集团控股有限公司 | Authorization and control method, device, system and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 吴伟敏;: "基于特征密钥的跨平台网络接入认证控制研究", 计算机仿真, no. 03, pages 174 - 177 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023116131A1 (en) * | 2021-12-23 | 2023-06-29 | 深圳Tcl新技术有限公司 | Cross-ecological device management and control method and apparatus, and storage medium and electronic device |
| CN114584313A (en) * | 2022-02-25 | 2022-06-03 | 杭州萤石软件有限公司 | Equipment physical identity authentication method, system and device and first platform |
| WO2023160299A1 (en) * | 2022-02-25 | 2023-08-31 | 杭州萤石软件有限公司 | Device physical identity authentication method and apparatus, and system and first platform |
| CN114584313B (en) * | 2022-02-25 | 2023-11-03 | 杭州萤石软件有限公司 | Equipment physical identity authentication method, system, device and first platform |
| WO2024016124A1 (en) * | 2022-07-18 | 2024-01-25 | Oppo广东移动通信有限公司 | Device configuration methods and apparatuses, and communication device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113783829B (en) | 2024-03-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113783829B (en) | Method and device for realizing equipment access across platforms | |
| CN108512846B (en) | Bidirectional authentication method and device between terminal and server | |
| JP5980961B2 (en) | Multi-factor certificate authority | |
| US8918641B2 (en) | Dynamic platform reconfiguration by multi-tenant service providers | |
| CN103685139A (en) | Authentication and authorization processing method and device | |
| CN111784887A (en) | Authorization releasing method, device and system for user access | |
| CN110958119A (en) | Identity verification method and device | |
| CN107920060B (en) | Data access method and device based on account | |
| CN114049122A (en) | Service processing method and system | |
| CN113221148A (en) | Information verification method and device | |
| CN110247917B (en) | Method and apparatus for authenticating identity | |
| US9455972B1 (en) | Provisioning a mobile device with a security application on the fly | |
| CN111814131A (en) | Method and device for equipment registration and configuration management | |
| CN111030900A (en) | Authentication-free login method and device and electronic equipment | |
| CN111787044A (en) | Internet of things terminal platform | |
| CN113206745B (en) | Digital certificate management method and device | |
| CN111917554B (en) | Method and device for verifying digital certificate | |
| CN113206738B (en) | Digital certificate management method and device | |
| CN108228280A (en) | The configuration method and device of browser parameters, storage medium, electronic equipment | |
| CN114417318A (en) | Third-party page jumping method and device and electronic equipment | |
| CN113055186A (en) | Cross-system service processing method, device and system | |
| CN115828309B (en) | Service calling method and system | |
| CN110602074B (en) | Service identity using method, device and system based on master-slave association | |
| CN110611656B (en) | Identity management method, device and system based on master identity multiple mapping | |
| CN110602076B (en) | Identity using method, device and system based on master identity multiple authentication |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |