US20240179142A1 - Method and apparatus for account association, and computer device and storage medium - Google Patents

Method and apparatus for account association, and computer device and storage medium Download PDF

Info

Publication number
US20240179142A1
US20240179142A1 US18/430,564 US202418430564A US2024179142A1 US 20240179142 A1 US20240179142 A1 US 20240179142A1 US 202418430564 A US202418430564 A US 202418430564A US 2024179142 A1 US2024179142 A1 US 2024179142A1
Authority
US
United States
Prior art keywords
cloud platform
account
platform
authorization
cloud
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.)
Pending
Application number
US18/430,564
Other languages
English (en)
Inventor
Xiaoqiang LYU
Zhao RU
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Publication of US20240179142A1 publication Critical patent/US20240179142A1/en
Pending legal-status Critical Current

Links

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/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
    • 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

Definitions

  • the present disclosure relates to the technical field of the Internet of Things, and in particular to a method, a device, a computer device and a storage medium for account association.
  • a server-side device may be accessed to a cloud platform, and a client device may manage and control the server-side device through the cloud platform.
  • IOT Internet of Things
  • server-side devices owned by a same user may belong to different cloud platforms. If the user wants to manage the server-side devices in different cloud platforms through an application, the user needs to establish association relationship between the user's accounts in multiple cloud platforms.
  • a cloud platform service provider may add a program module associated with other cloud platforms in the application program corresponding to the cloud platform, and the program module in the application program is adopted to process intermediate information (such as an access token) to achieve secure account association.
  • the embodiments of the present disclosure provide a method for account association.
  • the method is performed by a client device.
  • the method includes: obtaining an authorization code from an authorizing platform, in which the authorizing platform is one of a first cloud platform and a second cloud platform, and the first cloud platform is a cloud platform to which the client device belongs; and sending the authorization code to an authorized platform, in which the authorization code is configured for account association interaction between the authorized platform and the authorizing platform, so as to associate a first account with a second account.
  • the first account is a user account of the client device logging in the first cloud platform
  • the second account is a user account of the client device logging in the second cloud platform
  • the authorized platform is another cloud platform other than the authorizing platform in the first cloud platform and the second cloud platform.
  • the embodiments of the present disclosure provide a method for account association.
  • the method is performed by an authorizing platform, and the authorizing platform is one of a first cloud platform and a second cloud platform.
  • the method includes: sending an authorization code to a client device, in which the authorization code is configured to be sent to an authorized device by the client device, and the first cloud platform is a cloud platform to which the client device belongs; and performing account association interaction with the authorized platform based on the authorization code to associate a first account and a second account, in which the authorized platform is another cloud platform other than the authorizing platform in the first cloud platform and the second cloud platform.
  • the first account is a user account of the client device logging in the first cloud platform
  • the second account is a user account of the client device logging in the second cloud platform.
  • the embodiments of the present disclosure provide an IoT device.
  • the IoT device is implemented as a client device, and the IoT device includes a processor, a memory, and a transceiver.
  • the processor is configured to execute an instruction stored in the memory to implement the method for account association described above.
  • FIG. 1 is a schematic diagram of a network architecture of an IoT according to an embodiment of the present disclosure.
  • FIG. 2 is a flow chart of a method for account association according to an embodiment of the present disclosure.
  • FIG. 3 is a flow chart of a method for account association according to an embodiment of the present disclosure.
  • FIG. 4 is a flow chart of a method for account association according to an embodiment of the present disclosure.
  • FIG. 5 is a flow chart of a method for account association according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of a binding of an account and a device involved in the embodiment illustrated in FIG. 5 .
  • FIG. 7 is a flow chart of a method for account association according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic diagram of a binding of an account and a device involved in the embodiment illustrated in FIG. 7 .
  • FIG. 9 is a block diagram of a device for account association according to an embodiment of the present disclosure.
  • FIG. 10 is a block diagram of a device for account association according to an embodiment of the present disclosure.
  • FIG. 11 is a block diagram of a device for account association according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of an IoT device according to an embodiment of the present disclosure.
  • Network architectures and business scenarios described in the embodiments of the present disclosure are to more clearly explain the technical solutions of the embodiments of the present disclosure, and do not constitute a limitation on the technical solutions provided by the embodiments of the present disclosure.
  • Those skilled in the art will know that with the network architecture evolution and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present disclosure are further applicable to similar technical problems.
  • FIG. 1 is a schematic diagram of a network architecture of an IoT according to an embodiment of the present disclosure.
  • the network architecture of the IoT may include a client device 120 , a first cloud platform 140 and a second cloud platform 150 .
  • the network architecture may further include a server-side device 110 , a gateway device 130 , etc.;
  • the client device 120 is a user-side terminal device.
  • the client device may be a smartphone, a tablet, a smart watch, a smart TV, etc.; or the client device may further be a personal computer, such as a desktop computer, a portable computer, a personal workstation, etc.
  • the client device 120 is a client entity (which may be a virtual entity), the running of which is based on a terminal device.
  • the client device 120 may be an application (APP) running on a terminal device and configured to perform operations such as access, control, and management on the service-side device.
  • APP application
  • the first cloud platform 140 and the second cloud platform 150 are servers deployed on the network-side.
  • the server-side device 110 may be a device configured to provide functional services of the IoT.
  • the server-side device 110 may be a smart home device, such as a smart lamp, a smart TV, a smart air conditioner, a smart refrigerator, a smart microwave oven, a smart rice cooker, a sweeping robot, etc.
  • a smart home device such as a smart lamp, a smart TV, a smart air conditioner, a smart refrigerator, a smart microwave oven, a smart rice cooker, a sweeping robot, etc.
  • the server device 110 may be an industrial production device, such as a lathe, an industrial robot, a solar panel, a wind turbine, etc.
  • the server device 110 may be a commercial service device, such as an unmanned vending machine, etc.
  • the server device 110 may be an intelligent monitoring device, such as a surveillance camera, an infrared sensor, a sound sensor, a temperature sensor, etc.
  • Multiple server devices 110 may be accessed to the first cloud platform 140 and the second cloud platform 150 respectively.
  • the gateway device 130 is a network device implementing network interconnection above a network layer, and is also called an inter-network connector, a protocol converter, etc.
  • the gateway device 130 provides network connection services for the server device 110 .
  • the gateway device 130 may be a professional gateway, such as a home gateway, or the gateway device 130 may be an access device with a gateway function, such as a router with the gateway function.
  • the above-mentioned server device 110 , the client device 120 , the gateway device 130 , the first cloud platform 140 and the second cloud platform 150 may be IoT devices that meet industry standards.
  • they may be IoT devices that meet the requirements standardized by Open Connectivity Foundation (OCF).
  • OCF Open Connectivity Foundation
  • the server device 110 and the gateway device 130 are connected through a wired or wireless network.
  • the first cloud platform 140 and the second cloud platform 150 may be connected to the gateway device 130 and the client device 120 through the wired or wireless network respectively.
  • the above-mentioned wired or wireless network applies to standard communication technologies and/or protocols.
  • the above wired or wireless network may be a communication network based on an IoT protocol.
  • the user may have an account in two cloud platforms (namely, an original cloud and a target cloud) at the same time; each cloud has some server devices; the user may want a unified view for devices associated with both cloud platforms.
  • a client i.e., the client device installed with an application
  • OAuth2.0 authorization code grant type flow is a prerequisite for it to initiate an OAuth2.0 authorization code grant type flow.
  • the client of the origin cloud After the client registers to the target cloud, the client of the origin cloud obtains a client ID, a client secret and other information.
  • the origin cloud may request an authorization code (AuthCode) from the target cloud based on the client ID and the client secret obtained in the above operations, and then the client uses the AuthCode to obtain an access token and a refresh token.
  • AuthCode authorization code
  • the access token identifies a user identifier of the user logged in the client in the target cloud.
  • the origin cloud may associate the above-mentioned token with a local UserID.
  • the user may request information about all devices (server devices in the origin cloud and server devices in the target cloud) of the origin cloud through the origin cloud, and carry out relevant management and control operations.
  • the origin cloud may obtain allowable device information of the server device in the target cloud through a device API provided by the target cloud.
  • a current manufacturer's implementation plan mainly integrates a target cloud-related software development kit (SDK), a quick application, a H5 program and other program modules on the client, and adopts these program modules to complete the association of a user account in the target cloud with a user account in the origin cloud and the binding of the device. Therefore, one client needs to integrate information such as SDKs or quick applications from different manufacturers, which increases capacity burden and complexity of the client and has a great impact on the efficiency of the development, update and maintenance of the client.
  • SDK software development kit
  • FIG. 2 is a flow chart of a method for account association according to an embodiment of the present disclosure.
  • the method may be executed by a client device.
  • the client device may be the client device 120 of the network architecture illustrated in FIG. 1 .
  • the method may include the following operations.
  • the authorizing platform is one of a first cloud platform and a second cloud platform.
  • the first cloud platform is a cloud to which the client device belongs.
  • the above-mentioned client device may run a management application (APP) corresponding to the first cloud platform, and the management APP may be configured to control and manage the client device for accessing to the first cloud platform.
  • APP management application
  • the first cloud platform and the second cloud platform serve as an authorizing platform and an authorized platform respectively.
  • the first cloud platform may be the authorizing platform and the second cloud platform may be the authorized platform; or the first cloud platform may be the authorized platform and the second cloud platform may be the authorizing platform.
  • the client device may request the authorizing platform to issue an authorization code (AuthCode) to the authorized platform.
  • AuthCode authorization code
  • the management APP may request the authorizing platform of the first cloud platform and the second cloud platform to obtain the authorization code of the authorized platform.
  • the authorization code is configured for account association interaction between the authorized platform and the authorizing platform to associate a first account with a second account.
  • the first account is a user account of the client device logging in the first cloud platform.
  • the second account is a user account of the client device logging in the second cloud platform.
  • the authorized platform is another cloud platform other than the authorized platform in the first cloud platform and the second cloud platform.
  • the client device may send the authorization code to the authorized platform.
  • the authorized platform and the authorizing platform may verify the account association interaction based on the authorization code to ensure security of the account association.
  • the first cloud platform has the first account assigned to the user to log in the client device
  • the second cloud platform has the second account assigned to the user to log in the client device. Since the first cloud platform and the second cloud platform are two different cloud platforms and may belong to two different ecosystems. Accordingly, account systems of the two cloud platforms are usually independent and may not be directly interchangeable. Through the technical solution illustrated in the embodiments of the present disclosure, the first cloud platform and the second cloud platform may associate the accounts assigned to the same user.
  • the authorization code of the authorized platform is first obtained from the authorizing platform in the two cloud platforms through the client device. Then the authorization code is provided to the authorized platform, such that the subsequent account association interaction between the authorizing platform and the authorized platform may be carried out through the authorization code. Since the account association interaction process does not require the participation of the client device, there is also no need to integrate program modules associated with other cloud platforms in the applications installed on the client device, thereby reducing capacity burden and complexity of the client device and improving efficiency of development, update and maintenance of the client.
  • FIG. 3 is a flow chart of a method for account association according to an embodiment of the present disclosure.
  • the method may be executed by an authorizing platform.
  • the authorizing platform may be one of the first cloud platform 140 and the second cloud platform 150 in the network architecture illustrated in FIG. 1 .
  • the method may include the following operations.
  • the authorization code is configured to be provided to the authorized platform by the client device.
  • the first cloud platform is a cloud platform to which the client device belongs.
  • the authorized platform is another cloud platform other than the authorized platform in the first cloud platform and the second cloud platform.
  • the first account is a user account of the client device logging in the first cloud platform
  • the second account is a user account of the client device logging in the second cloud platform.
  • the authorization code of the authorized platform is first obtained from the authorizing platform in the two cloud platforms through the client device. Then the authorization code is provided to the authorized platform.
  • the authorizing platform and the authorized platform may interact with each other through the authorization code.
  • the account association interaction process does not require the participation of the client device. Therefore, there is no need to integrate program modules associated with other cloud platforms in the application installed on the client device, thereby reducing capacity burden and complexity of the client and improving efficiency of the development, update and maintenance of the client.
  • FIG. 4 is a flow chart of a method for account association according to an embodiment of the present disclosure.
  • the method may be executed by an authorized platform.
  • the authorized platform may be one of the first cloud platform 140 and the second cloud platform 150 in the network architecture illustrated in FIG. 1 .
  • the method may include the following operations.
  • receiving an authorization code sent by a client device is obtained by the client device from an authorizing platform.
  • the first cloud platform is the cloud platform to which the client device belongs.
  • the authorizing platform is another cloud platform other than one of the first cloud platform and the second cloud platform.
  • performing account association interaction with the authorizing platform based on the authorization code so as to associate a first account and a second account.
  • the first account is a user account of the client device logging in the first cloud platform
  • the second account is a user account of the client device logging in the second cloud platform.
  • the authorization code of the authorized platform is first obtained from the authorizing platform in the two cloud platforms through the client device. Then the authorization code is provided to the authorized platform.
  • the authorizing platform and the authorized platform may interact with each other through the authorization code.
  • the account association interaction process does not require the participation of the client device. Therefore, there is no need to integrate program modules associated with other cloud platforms in the application installed on the client device, thereby reducing capacity burden and complexity of the client and improving efficiency of the development, update and maintenance of the client.
  • the above-mentioned authorizing platform may be the first cloud platform, and the authorized platform may be the second cloud platform.
  • the second cloud platform may initiate the process of account association with the first cloud platform.
  • FIG. 5 is a flow chart of a method for account association according to an embodiment of the present disclosure.
  • the method may be executed interactively between the client device, the first cloud platform and the second cloud platform.
  • the method may include the following operations.
  • the client device sends an authorization-code acquisition request to the first cloud platform; and the first cloud platform receives the authorization-code acquisition request.
  • the authorization-code acquisition request may include an identifier of the second cloud platform.
  • the identifier of the second cloud platform may be obtained from the first cloud platform when the second cloud platform registers with the first cloud platform in advance.
  • the second cloud platform may register with the first cloud platform in advance. After the registration is completed, the first cloud platform may have the identifier of the second cloud platform, an address of the second cloud platform and other information. Afterwards, the client device establishes a connection with the first cloud platform. The first cloud platform may provide the identifier of the second cloud platform to the client device. When the user wants to establish an account association between the first cloud platform and the second cloud platform, the client device may select the identifier of the second cloud platform and initiate the account association process. At this time, the client device may send the authorization-code acquisition request including the identifier of the second cloud platform to the first cloud platform, thereby requesting the authorization code for the second cloud platform.
  • the first cloud platform sends an authorization-code response message to the client device; the client device receives the authorization-code response message sent by the first cloud platform, and the authorization-code response message includes the authorization code.
  • the first cloud platform generates the authorization-code response message based on the identifier of the second cloud platform included in the authorization-code acquisition request.
  • the authorization-code response message includes the authorization code assigned to the second cloud platform.
  • the above authorization-code response message may further include the address of the second cloud platform.
  • the address of the second cloud platform may be obtained by the first cloud platform based on the identifier of the second cloud platform included in the authorization-code acquisition request.
  • the first cloud platform may store the above-mentioned authorization code and the identifier of the second cloud platform, such that the authorization code may be verified in the subsequent account association process.
  • the client device sends authorization-code information to the second cloud platform.
  • the second cloud platform receives the authorization-code information sent by the client device; and the authorization-code information includes the authorization code.
  • the above authorization-code response message further includes the address of the second cloud platform.
  • the client device sends the authorization-code information to the second cloud platform based on the address of the second cloud platform.
  • the authorization-code information further includes at least one of an identifier of the first cloud platform and an identifier of the client device in the second cloud platform.
  • the identifier of the first cloud platform may be an address of the first cloud platform, such as a uniform resource locator (URL).
  • URL uniform resource locator
  • the identifier of the client device in the second cloud platform may be an identifier assigned to the client device by the second cloud platform when the client device registers with the second cloud platform.
  • the first cloud platform and the second cloud platform may perform account association interaction based on the authorization code to associate the first account with the second account.
  • the first account is the user account of the client device logging in the first cloud platform
  • the second account is the user account of the client device logging in the second cloud platform.
  • the second cloud platform sends a first-token acquisition request to the first cloud platform; the first cloud platform receives the first-token acquisition request sent by the second cloud platform; and the first-token acquisition request includes the authorization code.
  • the second cloud platform may request a token from the first cloud platform based on the authorization code.
  • the first cloud platform sends a first-access token and an open identifier to the second cloud platform; and the second cloud platform receives the first-access token and the open identifier sent by the first cloud platform.
  • the above-mentioned open identifier is an identifier assigned to the client device by the first cloud platform.
  • the open identifier may be an identifier assigned by the first cloud platform to the user corresponding to the client device, and the identifier is different from the first account.
  • the open identifier is configured to subsequently associate the first account in the first cloud platform with the second account in the second cloud platform.
  • the above-mentioned first-access token is used by the second cloud platform to send a user binding request to the first cloud platform.
  • the first cloud platform may query the authorization code corresponding to the second cloud platform, and compare the queried authorization code with the authorization code in the first-token acquisition request. If the two match, it is determined that the verification based on the authorization code is passed. Afterwards, the first cloud platform may send the first-access token and the open identifier (OpenID) to the second cloud platform.
  • OpenID open identifier
  • the first cloud platform may compare the queried authorization code with the authorization code in the first-token acquisition request. If the two are the same authorization code, it is determined that they match; otherwise, it is determined that they do not match.
  • the first cloud platform may query the authorization code corresponding to the second cloud platform according to the identifier of the second cloud platform carried in the first-token acquisition request.
  • the second cloud platform may generate the second account for the user corresponding to the client device.
  • the second cloud platform may generate the second account based on the above-mentioned open identifier.
  • the second cloud platform may further generate the second account through other methods.
  • the second cloud platform may randomly generate the second account for the user corresponding to the client device.
  • the embodiments of the present disclosure do not limit the method of generating the second account.
  • the second cloud platform sends an account binding request to the first cloud platform; the first cloud platform receives the account binding request sent by the second cloud platform, and the account binding request includes the first-access token and a second-access token.
  • the second cloud platform may generate the second-access token, and then request the first cloud platform to perform the account association based on the first-access token and the second-access token.
  • the second-access token is configured to access the second cloud platform by the first cloud platform.
  • the first cloud platform binds the first account with the open identifier and the second-access token.
  • the first cloud platform may verify the account binding of the first-access token. For example, the first cloud platform may query the first-access token allocated for the second cloud platform based on the identifier of the second cloud platform carried in the account binding request. Then the first cloud platform may compare the queried first-access token with the first-access token carried in the account binding request. If the two match (for example, both are the same authorization code), it is determined that the verification based on the first-access token is passed. Afterwards, the first account of the user corresponding to the client device in the first cloud platform is bound with the above-mentioned open account, and the first account may be bound with the second-access token.
  • the first cloud platform may query the first-access token allocated for the second cloud platform based on the identifier of the second cloud platform carried in the account binding request. Then the first cloud platform may compare the queried first-access token with the first-access token carried in the account binding request. If the two match (for example, both are the same authorization code), it is determined that the verification based on the
  • the first cloud platform may further bind the first account with the identifier of the second cloud platform.
  • the account binding request is configured to instruct the first cloud platform to bind the first account with the open identifier, the second-access token, and the identifier of the second cloud platform. Accordingly, the first cloud platform binds the first account with the open identifier, the second-access token and the identifier of the second cloud platform according to the account binding request.
  • the first cloud platform when sending the first-access token and the open identifier to the second cloud platform, may send the first-access token, the open identifier, the updated identifier of the first-access token, and the expiration time of the first-access token to the second cloud platform.
  • the second cloud platform when receiving the first-access token and the open identifier, may receive the first-access token, the open identifier, the updated token of the first-access token and the expiration time of the first-access token sent by the first cloud platform.
  • the updated token is configured to update the corresponding access token when the corresponding access token is expired.
  • the above expiration time may be configured to indicate a time point when the corresponding access token expires.
  • the expiration time may include the time point at which the corresponding access token expires, or the expiration time may further include an effective time point and a validity period of the corresponding access token.
  • the above-mentioned first-access token further has at least one of the updated token of the first-access token and the expiration time of the first-access token correspondingly.
  • the first cloud platform may further send the updated token of the first-access token to the second cloud platform.
  • the first cloud platform may further bind the first account with the updated token of the first-access token.
  • the account binding request further includes the open identifier, an updated token of the second-access token, and an expiration time of the second-access token.
  • the above-mentioned second-access token further has the updated token of the second-access token and/or the expiration time of the second-access token correspondingly.
  • the updated token of the second-access token and/or the expiration time of the second-access token may be carried in the account binding request and be sent to the first cloud platform.
  • the first cloud platform sends an account binding response to the second cloud platform; and the second cloud platform receives the account binding response sent by the first cloud platform.
  • the first cloud platform may send a response of a successful binding to the second cloud platform.
  • the second cloud platform binds the second account with the open identifier according to the account binding response.
  • the account binding response is configured to instruct the second cloud platform to bind the second account with the open identifier.
  • the second cloud platform After receiving the account binding response, the second cloud platform determines that the first cloud platform has completed the account binding. At this time, the second cloud platform may locally bind the second account with the open identifier.
  • the second cloud platform may further bind the second account with the second-access token.
  • the second cloud platform may further bind the second account with the updated token of the second-access token and/or the expiration time of the second-access token.
  • the client device sends a first-device binding request to the first cloud platform; and the first cloud platform receives the first-device binding request.
  • the first-device binding request includes a device identifier and the identifier of the second cloud platform; and the device identifier is an identifier of the server device for accessing to the second cloud platform.
  • the user when the user wants to associate the server device in the second cloud platform with the first cloud platform, the user may send the device binding request to the first cloud platform through the client device.
  • the binding request carries the identifier of the server device, and the identifier of the second cloud platform to which the server device belongs.
  • the first cloud platform sends a second-device binding request to the second cloud platform; the second cloud platform receives the second-device binding request sent by the first cloud platform; and the second-device binding request includes the device identifier, the second-access token and the open identifier.
  • the above-mentioned first-device binding request and the second-device binding request may further include device information such as a device model and manufacturer information of the server device, etc.
  • the first cloud platform may forward the device binding request to the second cloud platform, and during the forwarding process, the second-access token and open identifier may be added to the device binding request such that the second cloud platform may perform the verification based on the device binding.
  • the second-access token and open identifier in the device binding request may be queried and obtained by the first cloud platform based on the pre-established binding relationship.
  • the second cloud platform binds the server device with the second account based on the open identifier and the device identifier.
  • the second cloud platform may obtain the second-access token by querying the pre-established binding relationship according to the open identifier, and compare the obtained second-access token through querying with the second-access token carried in the second-device binding request. If the two are consistent, the second cloud platform may determine that the verification based on the second-access token is passed, query the second account based on the open identifier, and bind the service device with the second account.
  • an APP belonging to the O Cloud obtains an AuthCode for the T Cloud.
  • the AuthCode may be issued under a circumstance that the user does not have a T Cloud account; a T cloud identifier is carried during the requesting process.
  • the O Cloud delivers the AuthCode to the APP, it carries an access address registered by the T Cloud.
  • the APP sends the AuthCode and an O cloud identifier to the above access address of the T cloud.
  • the T Cloud sends the AuthCode to the O Cloud and applies for an Access Token (corresponding to the first-access token mentioned above) and an OpenID.
  • the T Cloud initiates an account binding request to the O Cloud, and the request carries the Access Token (corresponding to the above-mentioned second-access token) assigned by the T Cloud to the O Cloud and a Refresh Token (corresponding to the updated token of the above-mentioned second-access token) and other information. Afterwards, the T Cloud and the O Cloud completed user binding respectively.
  • the technical solution illustrated in the embodiments of the present disclosure may help the user without an account to complete user binding and access on the T Cloud, and does not require the user to do too much configuration work.
  • FIG. 6 is a schematic diagram of account and device binding related to an embodiment of the present disclosure.
  • the account and device binding process may include the following operations.
  • the user initiates an account association process on an APP.
  • the so-called account association process is to complete the binding of the user's accounts on the O_Cloud and the T_Cloud, such that the device registered with T_Cloud may be controlled through the APP in the O_Cloud.
  • the App requests the O_Cloud to distribute an AuthCode to the T_Cloud. Subsequently, the T_Cloud needs to apply for an Access Token from the O_Cloud based on the AuthCode. The request needs to carry an ID assigned by the O_Cloud to the T_Cloud. The above ID is generated through offline registration, which already exists in this process.
  • the O_Cloud sends its applied AuthCode to the APP.
  • the response message carries the access address of the T_Cloud. This access address is further registered offline in the O_Cloud.
  • the O_Cloud may confirm the access address based on the ID assigned at operation S 1 .
  • the APP sends the AuthCode to the T_Cloud; the message may further carry an ID (which may further be an URL) of the O_Cloud, an ClientID (assigned when the APP registers with the T_Cloud) of the APP and other information.
  • the T_Cloud applies for an Access Token and an OpenID from the O_Cloud; the AccessToken is configured for subsequent O_Cloud verification for access right of the T_Cloud.
  • the OpenID is an identifier assigned by the O_Cloud. There is no user identity in the T_Cloud yet. Therefore, the T_Cloud generates a user identity and binds it with the OpenID. The user identity in the O Cloud is further bound with the OpenID, thus completing the user identity on the two cloud platforms.
  • the O_Cloud returns the AccessToken 1 and the OpenID to the T_Cloud.
  • the T_Cloud generates a new user identity (may be generated based on the OpenID).
  • the T_Cloud sends a user binding request to the O_Cloud; the request needs to carry the Access Token 1 , an AccessToken 2 issued by the T_Cloud to the O_Cloud, a Refresh Token, an expiration time of the AccessToken 2 , the OpenID and other information.
  • the O_Cloud completes the binding of the user's O_Cloud account with the OpenID, the AccessToken 2 , the Refresh Token, and the identifier of the T_Cloud.
  • the so-called binding is to maintain the relationship between these elements.
  • the T_Cloud completes the user binding; performing the binding of the new user identity (i.e, the generated new account) generated at operation S 7 with the OpenID; and the binding of the accessToken 2 with the identifier of the O_Cloud may also be performed.
  • the APP initiates a device binding request to the O_Cloud.
  • the message includes device information (an ID, a model, a manufacturer, etc.) and the T_Cloud identifier.
  • the O_Cloud initiates a device binding request to the T_Cloud.
  • the request needs to carry the device information carried in the request at operation S 13 as well as the AccessToken 2 and the OpenID information.
  • the T_Cloud completes the binding of the T_Cloud account with the device.
  • the device binding only requires completing the binding of the device and user identity and a series of necessary configurations after the device is accessed to the cloud platform.
  • the authorization code of the authorized platform is first obtained from the authorizing platform in the two cloud platforms through the client device.
  • the authorization code is provided to the authorized platform.
  • the authorizing platform and the authorized platform may interact with each other through the authorization code.
  • the account association interaction process does not require the participation of the client device. Therefore, there is no need to integrates program modules associated with other cloud platforms in the application installed on the client device, thereby reducing the capacity burden and complexity of the client and improving the efficiency of the development, update and maintenance of the client.
  • the above-mentioned authorizing platform may be the second cloud platform, and the authorized platform may be the first cloud platform.
  • the first cloud platform may initiate the process of account association with the second cloud platform.
  • FIG. 7 is a flow chart of a method for account association according to an embodiment of the present disclosure.
  • the method may be executed interactively between the client device, the first cloud platform and the second cloud platform.
  • the method may include the following operations.
  • the client device sends an authorization-code acquisition request to the second cloud platform; and the second cloud platform receives the authorization-code acquisition request.
  • the authorization-code acquisition request may include the identifier of the first cloud platform.
  • the identifier of the first cloud platform may be obtained or generated by the second cloud platform when the first cloud platform registers with the second cloud platform in advance.
  • the first cloud platform may register with the second cloud platform in advance. After the registration is completed, the identifier of the first cloud platform may be stored in the second cloud platform. Correspondingly, the first cloud platform may further store the identifier of the first cloud platform. After the subsequent client device establishes a connection with the first cloud platform, the first cloud platform may provide the identifier of the first cloud platform to the client device. When the user wants to establish the account association between the first cloud platform and the second cloud platform, the account association process may be initiated in the client device. At this time, the client device may send the authorization-code acquisition request including the identifier of the first cloud platform to the second cloud platform, thereby requesting the authorization code for the first cloud platform.
  • the second cloud platform sends an authorization-code response message to the client device; the client device receives the authorization-code response message sent by the second cloud platform, and the authorization-code response message includes the authorization code.
  • the second cloud platform generates the authorization-code response message based on the identifier of the first cloud platform included in the authorization-code acquisition request.
  • the authorization-code response message includes the authorization code assigned to the first cloud platform.
  • the second cloud platform may store the above-mentioned authorization code and the identifier of the first cloud platform correspondingly, such that the authorization code may be verified in the subsequent account association process.
  • the client device sends the authorization-code information to the first cloud platform, the first cloud platform receives the authorization-code information sent by the client device correspondingly; and the authorization-code information includes the authorization code.
  • the authorization-code information further includes at least one of the identifier of the second cloud platform and the identifier of the client device in the second cloud platform.
  • the identifier of the client device in the second cloud platform may be an identifier assigned to the client device by the second cloud platform when the client device registers with the second cloud platform.
  • the first cloud platform and the second cloud platform may perform the account association interaction based on the authorization code to associate the first account with the second account.
  • the first account is a user account of the client device logging in the first cloud platform
  • the second account is a user account of the client device logging in the second cloud platform.
  • the first cloud platform sends a second-token acquisition request to the second cloud platform; the second cloud platform receives the second-token acquisition request sent by the first cloud platform; and the second-token acquisition request includes the authorization code and the open identifier.
  • the second cloud platform sends the second-access token to the first cloud platform; and the first cloud platform receives the second-access token sent by the second cloud platform.
  • the second-access token is configured to access the second cloud platform by the first cloud platform.
  • the second cloud platform may generate a second account after the verification based on the authorization code is passed.
  • the second cloud platform may generate the second account based on the open identifier after the verification based on the authorization code is passed.
  • the above-mentioned second cloud platform sending a second-access token to the first cloud platform includes the following operations.
  • the second cloud platform sends the second-access token to the first cloud platform, as well as an updated token of the second-access token and an expiration time of the second-access token.
  • the first cloud platform receiving the second-access token sent by the second cloud platform includes the following operations.
  • the first cloud platform receives the second-access token, the updated token of the second-access token and the expiration time of the second-access token sent by the second cloud platform.
  • the second cloud platform sends an account binding request to the first cloud platform; the first cloud platform receives the account binding request sent by the second cloud platform, and the account binding request includes the open identifier.
  • the first cloud platform binds the first account with the open identifier and the second-access token according to the account binding request.
  • the account binding request is configured to instruct the first cloud platform to bind the first account with the open identifier, the second-access token, and the identifier of the second cloud platform.
  • the first cloud platform binds the first account with the open identifier, the second-access token and the identifier of the second cloud platform according to the account binding request.
  • the first cloud platform sends an account binding response to the second cloud platform; and the second cloud platform receives the account binding response sent by the first cloud platform.
  • the account binding response is configured to instruct the second cloud platform to bind the second account with the open identifier.
  • the second cloud platform binds the second account with the open identifier according to the account binding response.
  • the client device sends a first-device binding request to the first cloud platform; the first cloud platform receives the first-device binding request; the first-device binding request includes a device identifier and the identifier of the second cloud platform; and the device identifier is an identifier of the server device for accessing to the second cloud platform.
  • the first cloud platform sends a second-device binding request to the second cloud platform; the second cloud platform receives the second-device binding request sent by the first cloud platform; the second-device binding request includes the device identifier, the second-access token and the open identifier.
  • the second cloud platform binds the server device with the second account based on the open identifier and the device identifier.
  • the authorization code verification, the token verification, and the device binding process in the embodiments of the present disclosure may refer to the description in the embodiments illustrated in FIG. 5 above, and will not be limited here.
  • FIG. 8 is a schematic diagram of an account and device binding according to an embodiment of the present disclosure.
  • the account and device binding process may include the following operations.
  • a user initiates an account association process on an APP.
  • the so-called account association process is to complete the binding of the user's accounts on an O_Cloud and a T Cloud, such that a device registered with the T_Cloud may be controlled through the APP on the O_Cloud.
  • the App requests the T_Cloud to distribute an AuthCode to the O Cloud. Subsequently, the O_Cloud needs to apply for an Access Token from the T_Cloud based on the AuthCode.
  • the T_Cloud sends its applied AuthCode to the APP.
  • the APP sends the AuthCode to the O_Cloud; the message may further carry an ID (may be a URL) of the T_Cloud.
  • the O_Cloud applies for an Access Token from the T_Cloud; the message needs to carry an OpenID generated by the O_Cloud.
  • the AccessToken is configured for subsequent authentication of access right of the O_Cloud by the T_Cloud.
  • the OpenID is an identifier assigned by the O_Cloud. There is no user identity on the T_Cloud yet. Therefore, the T_Cloud generates a user identity and binds it with the OpenID. The user identity on the O_Cloud is further bound with the OpenID, thus completing binding of the user identity on the two cloud platforms.
  • the T_Cloud generates a new user identity (possibly based on the OpenID).
  • the T_Cloud sends the Access Token and a Refresh Token to the O_Cloud.
  • the T_Cloud sends a user binding request to the O_Cloud, carrying the OpenID in the request.
  • the O_Cloud completes the binding of the user's O_Cloud account with the OpenID, the AccessToken, the Refresh Token, and the identifier of the T_Cloud.
  • the so-called user binding is to maintain the relationship between these elements.
  • the APP initiates a device binding request to the O_Cloud.
  • the message includes device information (an ID, a model, a manufacturer, etc.) and the identifier of the T_Cloud.
  • the O_Cloud initiates the device binding request to the T_Cloud. This request needs to carry the AccessToken and the OpenID information.
  • the T_Cloud completes the binding of the T_Cloud account with the device.
  • the device binding only requires completing the binding of the device and the user identity and a series of necessary configurations after the device is accessed to the cloud platform.
  • the authorization code of the authorized platform is first obtained from the authorizing platform in the two cloud platforms through the client device.
  • the authorization code is provided to the authorized platform.
  • the authorizing platform and the authorized platform may interact with each other through the authorization code.
  • the account association interaction process does not require the participation of the client device. Therefore, there is no need to integrates program modules associated with other cloud platforms on the application installed in the client device, thereby reducing the capacity burden and complexity of the client and improving the efficiency of the development, update and maintenance of the client.
  • FIG. 9 is a block diagram of a device for account association according to an embodiment of the present disclosure.
  • the device has a function of implementing the above method embodiments for account association.
  • the function may be implemented by hardware, or may be implemented by hardware through executing corresponding software.
  • the device may be the client device introduced above, or may be set in the client device.
  • the device may include an authorization-code acquisition module 901 and an authorization-code sending module 902 .
  • the authorization-code acquisition module 901 is configured to obtain an authorization code from an authorizing platform; the authorizing platform is one of the first cloud platform and the second cloud platform; and the first cloud platform is the cloud platform to which the client device belongs.
  • the authorization-code sending module 902 is configured to send the authorization code to the authorized platform; the authorization code is configured for account association interaction between the authorized platform and the authorizing platform, so as to associate the first account with the second account.
  • the first account is a user account of the client device logging in the first cloud platform
  • the second account is a user account of the client device logging in the second cloud platform.
  • the authorized platform is another cloud platform other than the authorized platform in the first cloud platform and the second cloud platform.
  • the authorization-code acquisition module 901 in response to the authorizing platform being the first cloud platform, is configured to: send an authorization-code acquisition request to the first cloud platform; receive an authorization-code response message sent by the first cloud platform, in which the authorization-code response message includes the authorization code; and send authorization-code information to the second cloud platform, in which the authorization-code information includes the authorization code.
  • the authorization-code acquisition request includes an identifier of the second cloud platform
  • the authorization-code response message further includes an address of the second cloud platform
  • the authorization-code acquisition module 901 is configured to send the authorization-code information to the second cloud platform according to the address of the second cloud platform.
  • the authorization-code information further includes at least one of an identifier of the first cloud platform and an identifier of the client device in the second cloud platform.
  • the authorization-code acquisition module 901 in response to the authorizing platform being the second cloud platform, is configured to: send an authorization-code acquisition request to the second cloud platform; receive an authorization-code response message sent by the second cloud platform, in which the authorization-code response message includes the authorization code; and send the authorization-code information to the first cloud platform, in which the authorization-code information includes the authorization code.
  • the authorization-code information further includes an identifier of the second cloud platform.
  • the apparatus further includes a device binding request module.
  • the device binding request module is configured to send a first-device binding request to the first cloud platform after the association between the first account and the second account is completed.
  • the first-device binding request includes a device identifier and the identifier of the second cloud platform.
  • the device identifier is an identifier of the server device for accessing to the second cloud platform;
  • the first-device binding request is configured to instruct the first cloud platform to send a second-device binding request to the second cloud platform.
  • the second-device binding request is configured to instruct the second cloud platform to bind the server device with the second account.
  • the authorization code of the authorized platform is first obtained from the authorizing platform in the two cloud platforms through the client device.
  • the authorization code is provided to the authorized platform, such that the subsequent authorizing platform and the authorized platform may interact with the account through the authorization code. Since the account association interaction process does not require the participation of the client device, there is no need to integrate program modules associated with other cloud platforms in the applications installed on the client device, thereby reducing the capacity burden and complexity of the client and improving the efficiency of the development, update and maintenance of the client.
  • FIG. 10 is a block diagram of a device for account association according to an embodiment of the present disclosure.
  • the device has the function of implementing the above method embodiments for account association.
  • the function may be implemented by hardware, or may be implemented by hardware through executing corresponding software.
  • the device may be the authorizing device introduced above, or may be set in the authorizing device.
  • the authorizing platform is one of the first cloud platform and the second cloud platform.
  • the device may include an authorization-code sending module 1001 and an association module 1002 .
  • the authorization-code sending module 1001 is configured to send an authorization code to a client device.
  • the authorization code is configured to send the authorization code to an authorized device by the client device.
  • the first cloud platform is the cloud platform to which the client device belongs.
  • the association module 1002 is configured to perform account association interaction with an authorized platform based on the authorization code, so as to associate the first account and the second account.
  • the authorized platform is another cloud platform other than the authorized platform in the first cloud platform and the second cloud platform.
  • the first account is a user account of the client device logging in the first cloud platform
  • the second account is a user account of the client device logging in the second cloud platform.
  • the authorization-code sending module 1001 is configured to: receive an authorization-code acquisition request sent by the client device; and send an authorization-code response message to the client device, in which the authorization-code response message includes the authorization code.
  • the authorization-code acquisition request in response to the authorizing platform being the first cloud platform, includes an identifier of the second cloud platform, and the authorization-code response message further includes an address of the second cloud platform.
  • the association module 1002 in response to the authorizing platform being the first cloud platform, is configured to receive a first-token acquisition request sent by the second cloud platform, in which the first-token acquisition request includes the authorization code; send a first-access token and an open identifier to the second cloud platform after a verification based on the authorization code is passed, in which the open identifier is an identifier assigned by the first cloud platform to the client device; receive an account binding request sent by the second cloud platform, in which the account binding request includes the first-access token and the second-access token; bind the first account with the open identifier and the second-access token after a verification based on the first-access token is passed; and send an account binding response to the second cloud platform; in which the account binding response is configured to instruct the second cloud platform to bind the second account with the open identifier.
  • the association module 1002 is configured to send the first-access token, the open identifier, an updated token of the first-access token, and an expiration time of the first-access token to the second cloud platform.
  • the account binding request further includes the open identifier, an updated token of the second-access token, and an expiration time of the second-access token.
  • the association module 1002 is configured to bind the first account with the open identifier, the second-access token, and the identifier of the second cloud platform.
  • the apparatus further includes a first-device binding request receiving module and a second-device binding request sending module.
  • the first-device binding request receiving module is configured to receive a first-device binding request; the first-device binding request includes a device identifier and an identifier of the second cloud platform; and the device identifier is an identifier of a server device for accessing to the second cloud platform.
  • the second-device binding request sending module is configured to send a second-device binding request to the second cloud platform; and the second-device binding request is configured to instruct the second cloud platform to bind the server device with the second account.
  • the second-device binding request includes the device identifier, the second-access token and the open identifier.
  • the association module 1002 in response to the authorizing platform being the second cloud platform, is configured to receive a second-token acquisition request sent by the first cloud platform, in which the second-token acquisition request includes the authorization code and an open identifier and the open identifier is an identifier assigned to the client device by the first cloud platform; send a second-access token to the first cloud platform after the verification according to the authorization code is passed; send an account binding request to the first cloud platform, in which the account binding request includes the open identifier and the account binding request is configured to instruct the first cloud platform to bind the first account with the open identifier and the second-access token; receive the account binding response sent by the first cloud platform; and bind the second account with the open identifier according to the account binding response.
  • the association module 1002 is configured to send the second-access token, an updated token of the second-access token and an expiration time of the second-access token to the first cloud platform.
  • the account binding request is configured to instruct the first cloud platform to bind the first account with the open identifier, the second-access token and the identifier of the second cloud platform.
  • the apparatus further includes a second-device binding request receiving module and a device binding module.
  • the second-device binding request receiving module is configured to receive a second-device binding request sent by the first cloud platform.
  • the second-device binding request includes the device identifier, the second-access token and the open identifier.
  • the device binding module is configured to bind the server device to the second account according to the open identifier and the device identifier after a verification based on the second-access token is passed.
  • the apparatus further includes an account generation module.
  • the account generation module is configured to generate the second account after the verification based on the authorization code is passed.
  • the account generation module is configured to generate the second account based on the open identifier after the verification based on the authorization code is passed.
  • the authorization code of the authorized platform is first obtained from the authorizing platform in the two cloud platforms through the client device.
  • the authorization code is provided to the authorized platform.
  • the authorizing platform and the authorized platform may interact with each other through the authorization code.
  • the account association interaction process does not require the participation of the client device, so there is no need to integrate program modules associated with other cloud platforms on the applications installed in the client device, thereby reducing the capacity burden and complexity of the client and improving the efficiency of the development, update and maintenance of the client.
  • FIG. 11 is a block diagram of a device for account association according to an embodiment of the present disclosure.
  • the device has a function of implementing the above method embodiments for account association.
  • the function may be implemented by hardware, or may be implemented by hardware through executing corresponding software.
  • the device may be the authorized device introduced above, or may be set in the authorized device.
  • the authorized platform is one of the first cloud platform and the second cloud platform.
  • the device may include an authorization-code receiving module 1101 and an association module 1102 .
  • the authorization-code receiving module 1101 is configured to receive an authorization code sent by a client device; the authorization code is obtained by the client device from the authorizing platform; and the first cloud platform is a cloud platform to which the client device belongs.
  • the authorized platform is another cloud platform other than the authorized platform in the first cloud platform and the second cloud platform.
  • the association module 1102 is configured to perform account association interaction with the authorizing platform based on the authorization code, so as to associate the first account with the second account.
  • the first account is a user account of the client device logging in the first cloud platform
  • the second account is a user account of the client device logging in the second cloud platform.
  • the association module 1102 in response to the authorized platform being the second cloud platform, is configured to send a first-token acquisition request to the first cloud platform, in which the first-token acquisition request includes the authorization code; receive a first-access token and an open identifier sent by the first cloud platform, in which the open identifier is an identifier assigned by the first cloud platform to the client device; send an account binding request to the first cloud platform, in which the account binding request includes the first-access token and a second-access token and the account binding request is configured to instruct the first cloud platform to bind the first account with the open identifier and the second-access token; receive an account binding response sent by the first cloud platform; and bind the second account with the open identifier according to the account binding response.
  • the association module 1102 is configured to receive the first-access token, the open identifier, the updated token of the first-access token and the expiration time of the first-access token sent by the first cloud platform.
  • the account binding request further includes the open identifier, an updated token of the second-access token, and an expiration time of the second-access token.
  • the account binding request is configured to instruct the first cloud platform to bind the first account with the open identifier, the second-access token and the identifier of the second cloud platform.
  • the apparatus further includes a second-device binding request receiving module and a device binding module.
  • the second-device binding request receiving module is configured to receive a second-device binding request sent by the first cloud platform.
  • the second-device binding request includes the device identifier, the second-access token and the open identifier.
  • the device binding module is configured to bind the server device with the second account according to the open identifier and the device identifier after a verification based on the second-access token is passed.
  • the apparatus further includes an account generation module.
  • the account generation module is configured to generate the second account.
  • the account generation module is configured to generate the second account according to the open identifier.
  • the association module 1102 in response to the authorized platform being the first cloud platform, is configured to send a second-token acquisition request to the second cloud platform, in which the second-token acquisition request includes the authorization code and an open identifier and the open identifier is an identifier assigned to the client device by the first cloud platform; receive the second-access token sent by the second cloud platform; receive an account binding request sent by the second cloud platform, in which the account binding request includes the open identifier; bind the first account with the open identifier and the second-access token according to the account binding request; and send an account binding response to the second cloud platform, in which the account binding response is configured to instruct the second cloud platform to bind the second account with the open identifier.
  • the association module 1102 is configured to receive the second-access token, an updated token of the second-access token and an expiration time of the second-access token sent by the second cloud platform.
  • the association module 1102 is configured to bind the first account with the open identifier, the second-access token and the identifier of the second cloud platform according to the account binding request.
  • the apparatus further includes a first-device binding request receiving module and a second-device binding request sending module.
  • the first-device binding request receiving module is configured to receive a first-device binding request sent by the client device.
  • the first-device binding request includes a device identifier and an identifier of the second cloud platform.
  • the device identifier is an identifier of a server device for accessing to the second cloud platform.
  • the second-device binding request sending module is configured to send a second-device binding request to the second cloud platform.
  • the second-device binding request is configured to instruct the second cloud platform to bind the server device with the second cloud platform.
  • the second-device binding request includes the device identifier, the second-access token and the open identifier.
  • the authorization code of the authorized platform is first obtained from the authorizing platform in the two cloud platforms through the client device.
  • the authorization code is provided to the authorized platform.
  • the authorizing platform and the authorized platform may interact with each other through the authorization code.
  • the account association interaction process does not require the participation of the client device, so there is no need to integrate program modules associated with other cloud platforms on the applications installed in the client device, thereby reducing the capacity burden and complexity of the client and improving the efficiency of the development, update and maintenance of the client.
  • the division of the above functional modules is used as an example only. In practical applications, the above functions may be allocated to different functional modules according to actual needs. In other words, the content structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • FIG. 12 is a schematic structural diagram of an IoT device 1200 according to an embodiment of the present disclosure.
  • the IoT device 1200 may include a processor 1201 , a receiver 1202 , a transmitter 1203 , a memory 1204 , and a bus 1205 .
  • the processor 1201 includes one or more processing cores.
  • the processor 1201 executes various functional applications and information processing by running a software programs and modules.
  • the receiver 1202 and the transmitter 1203 may be implemented as a communication component, and the communication component may be a communication chip. This communication chip may also be called a transceiver.
  • the memory 1204 is accessed to the processor 1201 through the bus 1205 .
  • the memory 1204 may be configured to store a computer program, and the processor 1201 is configured to execute the computer program to implement various operations performed by the terminal in the above method embodiments.
  • the memory 1204 may be implemented by any type of volatile or non-volatile storage device, or combination thereof, including but not limited to: a magnetic or optical disk, an electrically erasable programmable read-only memory, an erasable programmable read-only memory, a static ready-access memory, a read-only memory, magnetic memory, a flash memory, a programmable read-only memory.
  • the IoT device includes a processor, a memory, and a transceiver (the transceiver may include a receiver and a transmitter, the receiver is configured to receive information, and the transmitter is configured to send information).
  • the transceiver may include a receiver and a transmitter, the receiver is configured to receive information, and the transmitter is configured to send information).
  • the processor is configured to execute an instruction stored in the memory to implement all or part of the operations in the above-mentioned methods executed by the client device illustrated in FIG. 2 , FIG. 5 or FIG. 7 , which will not be repeated here.
  • the processor is configured to execute an instruction stored in the memory to implement all or part of the operations in the above-mentioned methods illustrated executed by the authorizing platform in FIG. 3 , FIG. 5 or FIG. 7 , which will not be repeated here.
  • the processor is configured to execute an instruction stored in the memory to implement all or part of the operations in the above-mentioned methods executed by the authorized platform illustrated in FIG. 4 , FIG. 5 or FIG. 7 , which will not be repeated here.
  • the embodiments of the present disclosure further provide a computer-readable storage medium.
  • a computer program is stored in the storage medium.
  • the computer program is loaded and executed by a processor to implement all or part of the operations in the above-mentioned methods executed by the client device, the authorizing platform or the authorized platform illustrated in FIG. 2 , FIG. 3 , FIG. 4 , FIG. 5 or FIG. 7 .
  • the present disclosure further provides a chip.
  • the chip is configured to run in an IoT device, to cause the IoT device to implement all or part of the operations in the above-mentioned methods executed by the client device, the authorizing platform or the authorized platform illustrated in FIG. 2 , FIG. 3 , FIG. 4 , FIG. 5 or FIG. 7 .
  • the present disclosure further provides a computer program product.
  • the computer program product or computer program includes a computer instruction, and the computer instruction is stored in a computer-readable storage medium.
  • the processor of the IoT device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction to cause the IoT device to implement all or part of the operations in the above-mentioned methods executed by the client device, the authorizing platform or the authorized platform illustrated in FIG. 2 , FIG. 3 , FIG. 4 , FIG. 5 or FIG. 7 .
  • the present disclosure further provides a computer program.
  • the computer program is executed by the processor of the IoT device to implement all or part of the operations in the above-mentioned methods executed by the client device, the authorizing platform or the authorized platform illustrated in FIG. 2 , FIG. 3 , FIG. 4 , FIG. 5 or FIG. 7 .
  • the functions described in the embodiments of the present disclosure may be implemented by using hardware, software, firmware, or any combination thereof.
  • the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • the computer-readable media includes a computer storage media and a communication media including any media that facilitates transfer of a computer program from one place to another.
  • the storage media may be any available media that may be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer And Data Communications (AREA)
  • Information Transfer Between Computers (AREA)
US18/430,564 2021-08-13 2024-02-01 Method and apparatus for account association, and computer device and storage medium Pending US20240179142A1 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/112626 WO2023015574A1 (zh) 2021-08-13 2021-08-13 用于账号关联的方法、装置、计算机设备及存储介质

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/112626 Continuation WO2023015574A1 (zh) 2021-08-13 2021-08-13 用于账号关联的方法、装置、计算机设备及存储介质

Publications (1)

Publication Number Publication Date
US20240179142A1 true US20240179142A1 (en) 2024-05-30

Family

ID=85199767

Family Applications (1)

Application Number Title Priority Date Filing Date
US18/430,564 Pending US20240179142A1 (en) 2021-08-13 2024-02-01 Method and apparatus for account association, and computer device and storage medium

Country Status (3)

Country Link
US (1) US20240179142A1 (zh)
CN (1) CN117751553A (zh)
WO (1) WO2023015574A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023150143A1 (en) * 2022-02-02 2023-08-10 Oracle International Corporation Multi-cloud control plane architecture

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107995215B (zh) * 2017-12-20 2020-09-01 青岛海信智慧家居系统股份有限公司 智能家居设备的控制方法、装置及云平台服务器
CN108055339B (zh) * 2017-12-22 2021-02-23 海尔优家智能科技（北京）有限公司 家电设备互联的方法、装置、存储介质及云平台服务器
CN110944035A (zh) * 2019-10-22 2020-03-31 珠海格力电器股份有限公司 一种物联网设备控制方法、系统以及可读介质
CN112600856A (zh) * 2020-12-28 2021-04-02 青岛海尔科技有限公司 设备授权方法及装置、存储介质、电子装置

Also Published As

Publication number Publication date
CN117751553A (zh) 2024-03-22
WO2023015574A1 (zh) 2023-02-16

Similar Documents

Publication Publication Date Title
CN113746633B (zh) 物联网设备绑定方法、装置、系统、云服务器和存储介质
JP6494149B2 (ja) 認可処理方法およびデバイス
CN102710640B (zh) 请求授权的方法、装置和系统
CN108632216B (zh) 网络功能授权方法、装置、可读存储介质及实体设备
US20240179142A1 (en) Method and apparatus for account association, and computer device and storage medium
WO2018202284A1 (en) Authorizing access to user data
CN105450582A (zh) 业务处理方法、终端、服务器及系统
CN106375442B (zh) 一种跨平台管理设备信息的方法和装置
CN110677383B (zh) 防火墙开墙方法、装置、存储介质及计算机设备
CN103384237A (zh) 一种共享IaaS业务云账号的方法、及共享平台和网络装置
JP2023505471A (ja) プロビジョニング方法及び端末機器
EP2693691B1 (en) Method and apparatus for initializing gateway in device management system
WO2021155515A1 (zh) 物联网设备的注册方法、装置、设备及存储介质
CN113596141B (zh) 设备控制权限的设置方法、装置、计算机设备和存储介质
WO2021134562A1 (zh) 配置设备更换方法、装置、设备及存储介质
CN115486033B (zh) 物联网中的设备接入方法、装置、计算机设备及存储介质
CN112367297B (zh) 一种业务控制方法及装置
CN111918268B (zh) 智能设备的控制方法、装置、电子设备及存储介质
WO2016165443A1 (zh) 一种保护机器类通信设备的方法、网络实体及mtc设备
CN115525442A (zh) 一种远程命令执行方法及装置
US20240179145A1 (en) Method for connection establishment and internet of things (iot) device
CN117478449B (zh) 一种第三方设备的控制方法、装置、电子设备及介质
WO2023184559A1 (zh) 设备共享方法、装置、设备、存储介质及程序产品
WO2021237536A1 (zh) 基于物联网的通信方法、装置及设备
CN111767524B (zh) 权限管理方法、装置、系统、服务器及介质

Legal Events

Date Code Title Description
STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION