CN113783829B - Method and device for realizing equipment access across platforms - Google Patents
Method and device for realizing equipment access across platforms Download PDFInfo
- Publication number
- CN113783829B CN113783829B CN202011349806.3A CN202011349806A CN113783829B CN 113783829 B CN113783829 B CN 113783829B CN 202011349806 A CN202011349806 A CN 202011349806A CN 113783829 B CN113783829 B CN 113783829B
- Authority
- CN
- China
- Prior art keywords
- platform
- verification
- accessed
- equipment
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000012795 verification Methods 0.000 claims abstract description 340
- 238000013475 authorization Methods 0.000 claims abstract description 119
- 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 20
- 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
- 238000012790 confirmation Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000008901 benefit Effects 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
- 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
- 238000005516 engineering process Methods 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
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 manner, and relates to the technical field of computers. One embodiment of the method comprises the following steps: 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 designated platform for authorization verification; and accessing the equipment according to the authorization verification result returned by the appointed platform. According to the method and the device, cross-ecological authentication and device access can be achieved, the devices of the Internet of things with different ecologies are accessed into an ecological system of an application service provider, embedding of a software development kit is not needed, user experience is improved, meanwhile, control flows and data flows can be transmitted simultaneously, and response time is saved.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and an apparatus for implementing device access across platforms.
Background
The ecology of the Internet of things, particularly the ecology of intelligent home, is in a state of being cut off at present, namely ecological equipment accessed by different factories and platforms cannot be directly connected with ecology of a third party. In order to realize interconnection and interworking of devices among different ecologies, a common form is to adopt a cloud-to-cloud mode to realize interworking of control flow and data flow.
In the process of implementing the present 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, the equipment needs the participation of an ecological application program of the other party when the equipment activates the distribution network, or the application program needs to be embedded into a software development kit of the other party, so that the user experience is poor; secondly, the control and data streams pass through both platforms, resulting in longer response times.
Disclosure of Invention
In view of the above, the embodiment of the invention provides a method and a device for realizing device access in a cross-platform manner, which can realize cross-ecological authentication and device access, and access the internet of things devices with different ecology into an ecosystem of an application service provider without embedding a software development kit, thereby improving user experience, simultaneously transmitting control flow and data flow simultaneously, and 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 implementing device access across platforms, comprising:
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 designated 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 appointed platform is the platform to be accessed, the platform verification request comprises a token of the platform to be accessed, the equipment identifier, 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, sending the platform verification request 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 included in the platform verification request; after the verification is passed, forwarding the platform verification request to the equipment platform so as to verify the legitimacy of the platform to be accessed and the equipment through the equipment platform; and acquiring 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 appointed platform is the equipment platform, the platform verification request comprises domain name information of the platform to be accessed, the equipment identifier, platform verification information generated by the equipment and 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 generating 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 pre-stored certificate corresponding to the domain name information of the platform to be accessed.
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 device access comprises:
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 method for realizing equipment access in a cross-platform manner is provided.
A method for implementing device access across platforms, comprising:
an application associated with a platform to be accessed sends a device activation binding request to a device;
the device generates a platform verification request according to the device activation binding request, and sends the platform verification request to a designated platform;
the appointed platform performs 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 appointed platform is the platform to be accessed, the platform verification request comprises a token of the platform to be accessed, the equipment identifier, 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 designated 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 appointed platform carrying out 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 included in the platform verification request; after the verification is passed, forwarding the platform verification request 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.
Optionally, the device activation binding request includes 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, the equipment identifier, platform verification information generated by the equipment and signature of the equipment private key on the platform verification information;
the appointed platform carrying out 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 pre-stored certificate corresponding to the domain name information of the platform to be accessed.
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 accessing the device according to the authorization verification result comprises the following steps:
and the equipment uses the public key or the certificate of the equipment platform to verify the authorization verification result, and accesses the platform to be accessed after the verification is passed.
According to another aspect of the embodiment of the invention, a device for realizing equipment access in a cross-platform manner is provided.
An apparatus for implementing device access across platforms, the apparatus being adapted for devices 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 designated platform for authorization verification;
and the equipment access module is used for performing equipment access 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 appointed platform is the platform to be accessed, the platform verification request comprises a token of the platform to be accessed, the equipment identifier, 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 configured to: according to the domain name information of the platform to be accessed, sending the platform verification request 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 included in the platform verification request; after the verification is passed, forwarding the platform verification request to the equipment platform so as to verify the legitimacy of the platform to be accessed and the equipment through the equipment platform; and acquiring 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 appointed platform is the equipment platform, the platform verification request comprises domain name information of the platform to be accessed, the equipment identifier, platform verification information generated by the equipment and signature of the equipment private key on the platform verification information;
the authorization verification module 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 generating an authorization verification result.
Optionally, the apparatus further comprises a device authentication 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 further comprises a platform verification module for: and the equipment platform verifies the legality of the platform to be accessed according to a pre-stored certificate corresponding to the domain name information of the platform to be accessed.
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 still another aspect of the embodiment of the invention, an apparatus for realizing device access across platforms is provided.
An apparatus for implementing device access across platforms, comprising:
the request sending module is used for sending a device activation binding request to the device by an 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 designated platform;
The authorization verification module is used for carrying out authorization verification on the appointed platform according to the platform verification request and returning an authorization verification result to the equipment;
and the equipment access module is used for the equipment to access 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 appointed platform is the platform to be accessed, the platform verification request comprises a token of the platform to be accessed, the equipment identifier, platform verification information generated by the equipment and a signature of the equipment private key on the platform verification information;
the request verification module is further configured 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 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 included in the platform verification request; after the verification is passed, forwarding the platform verification request 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.
Optionally, the device activation binding request includes 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, the equipment identifier, platform verification information generated by the equipment and signature of the equipment private key on the platform verification information;
the authorization verification module is further configured 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 authentication 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 further comprises a platform verification module for: and the equipment platform verifies the legality of the platform to be accessed according to a pre-stored certificate corresponding to the domain name information of the platform to be accessed.
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 uses the public key or the certificate of the equipment platform to verify the authorization verification result, and accesses the platform to be accessed after the verification is passed.
According to still another aspect of the embodiment of the present invention, an electronic device for implementing device access across platforms is provided.
An electronic device for implementing device access across platforms, comprising: one or more processors; and 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 realize the method for realizing the cross-platform device access provided by the embodiment of the invention.
According to yet another aspect of an embodiment of the present invention, a computer-readable medium is provided.
A computer readable medium having stored thereon a computer program which 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 designated platform for authorization verification; according to the authorization verification result returned by the appointed platform, the technical means of equipment access is carried out, under the condition that protocols and schemes of a communication layer are not required to be agreed, and only the process of cross-ecological authentication and access is involved, the access of the internet of things equipment with different ecologies into the ecological system can be realized, the embedding of a software development kit is not required, the process is simple, and the user experience is improved; and the control flow and the data flow can be transmitted at the same time, thereby saving response time. Meanwhile, the whole process of realizing equipment authentication access by crossing the platforms only needs to carry out simple authorization on the other platform, thereby ensuring the ecological controllability of the other side.
Further effects of the above-described non-conventional alternatives are 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 schematic diagram of a device-centric cross-platform device authentication access process according to one embodiment of the present invention;
FIG. 3 is a schematic diagram of a platform-centric cross-platform device authentication access process according to another embodiment of the present invention;
FIG. 4 is a schematic diagram of the main modules of an apparatus for cross-platform implementation of device access according to one embodiment of the invention;
FIG. 5 is a schematic diagram of the main modules of an apparatus for cross-platform implementation of device access 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 applied;
fig. 7 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present invention are included to facilitate understanding, and are to be considered 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, where the scenario aimed at by the embodiment of the present invention is an ecological device of different manufacturers and platforms, and generally cannot directly connect to a third party ecological problem. As shown in fig. 1, the method for implementing device access across platforms in 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 designated 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, the whole process does not need to agree with protocols and schemes of a communication layer, only the process of cross-ecological authentication and access is related, the method has strong practical operability, the simple process can realize that the Internet of things equipment with different ecologies is accessed into the ecological system of the method, strong constraint on the verification scheme is not needed, only the platform of the other party is needed to carry out simple authorization, and meanwhile, the ecological controllability of the other party is ensured.
In the embodiment of the invention, the appointed platform is a 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.
According to one embodiment of the invention, the device activation binding request includes a token and domain name information of the platform to be accessed;
if the appointed platform is a platform to be accessed, 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;
sending the platform verification request to the designated platform for authorization verification includes:
according to domain name information of the platform to be accessed, sending a platform verification request 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 to be accessed to the platform included in the platform verification request; after the verification is passed, forwarding a platform verification request to the equipment platform so as to verify the legitimacy of the platform to be accessed and the equipment through the equipment platform; and acquiring an authorization verification result fed back by the equipment platform.
According to another embodiment of the invention, the device activation binding request includes domain name information of the platform to be accessed;
If the appointed platform is an equipment platform, the platform verification request comprises domain name information of the platform to be accessed, equipment identification, platform verification information generated by equipment and signature of an equipment private key on the platform verification information;
sending the platform verification request to the designated platform for authorization verification includes:
and sending a 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 generating an authorization verification result.
According to yet 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 legitimacy of the device;
the equipment platform verifies the legality of the platform to be accessed according to a 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 of the verification information using a private key of the device platform;
according to the authorization verification result returned by the appointed platform, the device access comprises:
and verifying the authorization verification result returned by the appointed platform by using the public key or 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 procedure according to one embodiment of the present invention. In the description of the embodiment of the invention, the platform to be accessed and the device platform are mutually trusted platforms, namely the platform A has trusted platform B in advance (such as putting in a platform B certificate). As shown in fig. 2, the process of performing device authentication access by using a device-centric cross-platform in the embodiment of the present invention is mainly as follows:
1. an application associated with the platform to be accessed sends a device activation binding request to the device, the device activation binding request including a token and domain name information of the platform to be accessed, and the like. In this embodiment, namely: the APP of manufacturer B requests to activate the binding A equipment, and the request carries B platform information, such as token, domain name information and the like, which are accessed to the B platform;
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 private key of the device on the platform verification information. In this embodiment, namely: the a device requests verification from the a platform whether the B platform is an accessible, trusted platform. The request can carry information such as domain name information of a B platform, generation verification information of an A device, signature of a private key of the A device on the verification information, device identification id of the A device and the like;
3. The device platform verifies the legality of the device and the platform to be accessed, generates an authorization verification result, returns the authorization verification result to the device, 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 legality of the device, verifies the legality of the platform to be accessed according to the certificate corresponding to the pre-stored domain name information of the platform to be accessed, and the authorization verification result comprises the verification information generated by the device platform and the signature performed on the verification information by using the 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 a device public key or certificate to verify the legitimacy of the a-device. If the validity of the device a passes, it is verified whether the platform B is in the trusted information list, for example: and checking whether the platform certificate corresponding to the domain name of the B platform is authorized and trusted. After the verification of the A device and the B platform is passed, the A platform transmits confirmation information to the A device, otherwise, transmits negative information, and the information transmitted by the A platform to the A device includes verification information of the A platform, for example, including: the verification information generated by the A platform and the signature of the A platform on the verification information by using a private key;
4. And the equipment uses the public key or certificate of the equipment platform to verify the authorization verification result, and accesses the platform to be accessed after the verification is passed. In this embodiment, namely: the a device performs validity verification on the information of the a platform, for example, verifies the verification information and its signature with a public key or certificate of the a platform. After the validity of the information of the platform A is verified, if the information is the verification that the platform B is legal, the information is connected to the platform B. Otherwise, the connection is denied.
5. And informing the B manufacturer APP to activate the access result by the A device or the B platform.
Fig. 3 is a schematic diagram of a process for performing device authentication access across platform-centric cross-platforms according to another embodiment of the present invention. In the description of the embodiment of the invention, the platform to be accessed and the device platform are mutually trusted platforms, namely the platform A has trusted platform B in advance (such as putting in a platform B certificate). As shown in fig. 3, the process of performing device authentication access by using a platform as a center in a cross-platform manner according to the embodiment of the present invention is as follows:
1. an application associated with the platform to be accessed sends a device activation binding request to the device, the device activation binding request including a token and domain name information of the platform to be accessed. In this embodiment, namely: b manufacturer APP requests to activate binding A equipment, wherein the request carries B platform information, such as token and domain name information accessed to B platform;
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 private key of the device on the platform verification information. In this embodiment, namely: the A device requests to the B platform to verify whether the B platform is an accessible and trusted platform, wherein the request comprises information such as token of the B platform, verification information generated by the A device, signature of a private key of the A device on the verification information, device identification id of the A device 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 included in the platform verification request, and forwards the platform verification request to the equipment platform after the verification is passed. In this embodiment, namely: b platform verifies the legality of the access information (such as token included in the verification request) sent by A device, after the verification is passed, the information carried by A device is forwarded to A platform, and verification and authorization are requested;
4. the device platform verifies the legality of the platform to be accessed and the device, generates an authorization verification result, feeds back the authorization verification result to the platform to be accessed, verifies platform verification information and a 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, verifies the legality of the platform to be accessed according to a certificate corresponding to the domain name information of the pre-stored platform to be accessed, and the authorization verification result comprises verification information generated by the device platform and the 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 B-platform, for example by B-platform certificate verification. After passing the verification, the legitimacy of the device A is verified, for example, the device public key or certificate is used for verifying the verification information signature and signature. And after the validity of the equipment A passes the verification, replying the confirmation information of the platform B. If the legitimacy of the B platform or the legitimacy of the A device is not verified, replying to the negative information of the B platform. The confirmation information replied to the B-platform should include verification information that the a-platform authorizes the a-device, for example, including: the verification information generated by the A platform and the signature of the A platform on the verification information by using a private key;
5. And the equipment uses the public key or certificate of the equipment platform to verify the authorization verification result, and accesses the platform to be accessed after the verification is passed. In this embodiment, namely: the device a verifies after receiving the authorization information forwarded by the platform B, for example, by verifying the verification information and the signature with the public key or certificate of the platform a. After the verification is passed, the equipment A is accessed to the platform B, otherwise, the access is refused;
6. and informing the B manufacturer APP to activate the access result by the A device or the B platform.
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 in an embodiment of the present invention mainly includes a receiving request 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;
the authorization verification module 402 is configured to generate a platform verification request according to the device activation binding request, and send the platform verification request to a designated 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 appointed platform is a 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.
According to one embodiment of the invention, the device activation binding request includes a token and domain name information of the platform to be accessed;
if the appointed platform is a platform to be accessed, 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;
the authorization verification module 402 is further configured to: according to domain name information of the platform to be accessed, sending a platform verification request 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 to be accessed to the platform included in the platform verification request; after the verification is passed, forwarding a platform verification request to the equipment platform so as to verify the legitimacy of the platform to be accessed and the equipment through the equipment platform; and acquiring an authorization verification result fed back by the equipment platform.
According to another embodiment of the invention, the device activation binding request includes domain name information of the platform to be accessed;
if the appointed platform is an equipment platform, the platform verification request comprises domain name information of the platform to be accessed, equipment identification, platform verification information generated by equipment and signature of an equipment private key on the platform verification information;
The authorization verification module 402 is further configured to: and sending a 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 generating 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 figure) for: 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; the apparatus 400 further comprises a platform verification module (not shown in the figures) for: the equipment platform verifies the legality of the platform to be accessed according to a 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 of 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 the public key or 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 in an embodiment of the present invention mainly includes a request sending module 501, a request verifying module 502, an authorization verifying 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 an application associated with a platform to be accessed;
the request verification module 502 is configured to generate a platform verification request according to the device activation binding request, and send the platform verification request to a specified platform;
an authorization verification module 503, 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 according to the authorization verification result.
In the embodiment of the invention, the appointed platform is a 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.
According to one embodiment of the invention, the device activation binding request includes a token and domain name information of the platform to be accessed;
if the appointed platform is a platform to be accessed, 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;
the request verification module 502 is further configured to: the equipment sends a platform verification request to the platform to be accessed according to 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 included in the platform verification request; after the verification is passed, forwarding a platform verification request 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 includes domain name information of the platform to be accessed;
if the appointed platform is an equipment platform, the platform verification request comprises domain name information of the platform to be accessed, equipment identification, platform verification information generated by equipment and signature of an equipment private key on the platform verification information;
the authorization verification module is also for: the device platform verifies the legitimacy of the device 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 figure) for: 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;
The apparatus further comprises a platform verification module (not shown in the figures) for: the equipment platform verifies the legality of the platform to be accessed according to a pre-stored certificate corresponding to the domain name information of the platform to be accessed.
According to a further embodiment of the invention, the authorization verification result comprises verification information generated by the device platform and a signature of the verification information using a private key of the device platform;
the device access module 504 is further configured to: and the equipment uses the public key or certificate of the equipment platform to verify the authorization verification result, and accesses the platform to be accessed after the verification is passed.
According to the technical scheme of the embodiment of the invention, the device 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 designated platform for authorization verification; according to the authorization verification result returned by the appointed platform, the technical means of equipment access is carried out, under the condition that protocols and schemes of a communication layer are not required to be agreed, and only the process of cross-ecological authentication and access is involved, the access of the internet of things equipment with different ecologies into the ecological system can be realized, the embedding of a software development kit is not required, the process is simple, and the user experience is improved; and the control flow and the data flow can be transmitted at the same time, thereby saving response time. Meanwhile, the whole process of realizing equipment authentication access by crossing the platforms only needs to carry out simple authorization on the other platform, thereby ensuring the ecological controllability of the other side.
Fig. 6 illustrates an exemplary system architecture 600 of a method of cross-platform device access or an apparatus of cross-platform device access 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 is used as a medium to provide communication links between the terminal devices 601, 602, 603 and the server 605. The network 604 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the server 605 via the network 604 using the terminal devices 601, 602, 603 to receive or send messages, etc. Various applications, such as a device control class application, a smart home class application, a platform connection class application, etc. (only 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 smartphones, tablets, laptop and desktop computers, and the like.
The server 605 may be a server providing various services, such as a background management server (by way of example only) providing support for smart home appliances controlled by users using the terminal devices 601, 602, 603. The background management server may perform analysis and other processing on the received data such as the connection request, and feed back the processing result (for example, the connection result—merely an example) to the terminal device.
It should be noted that, the method for implementing device access across platforms provided by the embodiment of the present invention is generally executed by the server 605, and correspondingly, the device 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, there is illustrated a schematic diagram of a computer system 700 suitable for use in implementing a terminal device or server in accordance with an embodiment of the present invention. The terminal device or server shown in fig. 7 is only an example, and should not impose any limitation on the functions and 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 according to 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 required for the operation of the system 700 are also stored. The CPU 701, ROM 702, and RAM 703 are connected to each other through 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 section 706 including a keyboard, a mouse, and the like; an output portion 707 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 708 including a hard disk or 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. The 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 therefrom is mounted into the storage section 708 as necessary.
In particular, according to embodiments of the present disclosure, the processes described above with reference to 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 shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 709, and/or installed from the removable medium 711. The above-described functions defined in the system of the present invention are performed when the computer program is executed by a Central Processing Unit (CPU) 701.
The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any 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 context of this document, 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, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. 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 flowcharts 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 involved in the embodiments of the present invention may be implemented in software or in hardware. The described units or modules may also be provided in a processor, for example, as: a processor includes a receive request module, an authorization verification module, and a device access module. Where the names of these units or modules do not in some way constitute a limitation of the unit or module itself, the reception request module may also be described as "module for receiving a device activation binding request sent by 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 present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to include: 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 designated 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 device 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 designated platform for authorization verification; according to the authorization verification result returned by the appointed platform, the technical means of equipment access is carried out, under the condition that protocols and schemes of a communication layer are not required to be agreed, and only the process of cross-ecological authentication and access is involved, the access of the internet of things equipment with different ecologies into the ecological system can be realized, the embedding of a software development kit is not required, the process is simple, and the user experience is improved; and the control flow and the data flow can be transmitted at the same time, thereby saving response time. Meanwhile, the whole process of realizing equipment authentication access by crossing the platforms only needs to carry out simple authorization on the other platform, thereby ensuring the ecological controllability of the other side.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.
Claims (8)
1. A method for implementing device access across platforms, the method being applicable to a device to be accessed to a platform, the method comprising:
receiving a device activation binding request sent by an application associated with the platform to be accessed, wherein the device activation binding request comprises a token and domain name information of 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 designated platform for authorization verification;
performing equipment access according to an authorization verification result returned by the appointed platform;
if the appointed platform is the platform to be accessed, the platform verification request comprises a token of the platform to be accessed, the equipment identifier, 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, sending the platform verification request 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 included in the platform verification request; after the verification is passed, forwarding the platform verification request to an equipment platform so as to verify the legitimacy of the platform to be accessed and the equipment through the equipment platform; and acquiring an authorization verification result fed back by the equipment platform.
2. The method of 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 includes 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, the equipment identifier, platform verification information generated by the equipment and 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 generating an authorization verification result.
4. A method according to claim 1 or 3, wherein the device platform verifies the platform verification information generated by the device and the signature in accordance with a public key or certificate of the device to verify the legitimacy of the device;
and the equipment platform verifies the legality of the platform to be accessed according to a pre-stored certificate corresponding to the domain name information of the platform to be accessed.
5. A method according to claim 1 or 3, wherein the authorization verification result comprises verification information generated by the device platform and a signature of the verification information using a private key of the device platform;
according to the authorization verification result returned by the appointed platform, the device access comprises:
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.
6. An apparatus for implementing device access across platforms, the apparatus being adapted for a device to be accessed to a platform, the apparatus comprising:
the device activation binding module is used for receiving a device activation binding request sent by an application associated with the platform to be accessed, wherein the device activation binding request comprises a token and domain name information of 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 designated platform for authorization verification;
the device access module is used for performing device access according to the authorization verification result returned by the appointed platform;
if the appointed platform is the platform to be accessed, the platform verification request comprises a token of the platform to be accessed, the equipment identifier, 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 configured to: according to the domain name information of the platform to be accessed, sending the platform verification request 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 included in the platform verification request; after the verification is passed, forwarding the platform verification request to an equipment platform so as to verify the legitimacy of the platform to be accessed and the equipment through the equipment platform; and acquiring an authorization verification result fed back by the equipment platform.
7. An electronic device for implementing device access across platforms, comprising:
one or more processors;
storage means for storing one or more programs,
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-5.
8. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-5.
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 CN113783829A (en) | 2021-12-10 |
| CN113783829B true 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) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116346842A (en) * | 2021-12-23 | 2023-06-27 | 深圳Tcl新技术有限公司 | Cross-ecological device management and control method and device, storage medium and electronic device |
| 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 |
Citations (3)
| 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 |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107995215B (en) * | 2017-12-20 | 2020-09-01 | 青岛海信智慧家居系统股份有限公司 | Control method and device of intelligent household equipment and cloud platform server |
| CN110417730B (en) * | 2019-06-17 | 2022-07-19 | 平安科技（深圳）有限公司 | Unified access method of multiple application programs and related equipment |
| CN110365711B (en) * | 2019-08-20 | 2022-03-25 | 中国工商银行股份有限公司 | Multi-platform user identity association method and device, computer equipment and computer readable storage medium |
| CN110972131B (en) * | 2019-10-31 | 2023-08-15 | 阿里巴巴集团控股有限公司 | Authorization and management method, device, system and storage medium |
-
2020
- 2020-11-26 CN CN202011349806.3A patent/CN113783829B/en active Active
Patent Citations (3)
| 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 |
Non-Patent Citations (1)
| Title |
|---|
| 基于特征密钥的跨平台网络接入认证控制研究;吴伟敏;;计算机仿真(03);第174-177页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113783829A (en) | 2021-12-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113783829B (en) | Method and device for realizing equipment access across platforms | |
| CN105472192B (en) | The smart machine, terminal device and method realizing control security certificate and sharing | |
| US8561172B2 (en) | System and method for virtual information cards | |
| CN108540433B (en) | User identity verification method and device | |
| CN107241339B (en) | Identity authentication method, identity authentication device and storage medium | |
| CN112039826B (en) | Login method and device applied to applet end, electronic equipment and readable medium | |
| CN103685139A (en) | Authentication and authorization processing method and device | |
| US20140298441A1 (en) | Authentication method, authentication system, and service delivery server | |
| CN104160653A (en) | Multi-factor certificate authority | |
| KR20120002836A (en) | Apparatus and method for controlling access to combined services | |
| CN112583834B (en) | Method and device for single sign-on through gateway | |
| CN113364795B (en) | Data transmission method and proxy server | |
| CN111784887A (en) | Authorization releasing method, device and system for user access | |
| CN102984046A (en) | Processing method of instant messaging business and corresponding network equipment | |
| CN114049122A (en) | Service processing method and system | |
| CN107920060B (en) | Data access method and device based on account | |
| US9455972B1 (en) | Provisioning a mobile device with a security application on the fly | |
| CN110247917B (en) | Method and apparatus for authenticating identity | |
| CN111600787B (en) | Information processing method, information processing apparatus, electronic device, and medium | |
| CN111787048B (en) | Connection method of terminal equipment, scheduling server and Internet of things system | |
| CN111030900A (en) | Authentication-free login method and device and electronic equipment | |
| CN112905990A (en) | Access method, client, server and access system | |
| CN108228280A (en) | The configuration method and device of browser parameters, storage medium, electronic equipment | |
| CN113055186B (en) | Cross-system service processing method, device and system | |
| CN114417318A (en) | Third-party page jumping method and device and electronic equipment |
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 |