Account login processing method and device

Abstract

The embodiments of this specification provide an account login processing method and apparatus, wherein an account login processing method includes: obtaining an account login record generated by an IoT device for account login, and device registration information obtained by registering the IoT device; performing a login relationship verification on the IoT device based on the account login record and the device registration information; generating a login message for the IoT device according to the verification result, and pushing the login message to the device user through a login sub-application; wherein the device user accesses the login message through a host application installed on a user terminal, and performs the account login according to an application account in the host application.

Description

Technical Field

[0001] This document relates to the field of data processing technology, and in particular to an account login processing method and device. Background Art

[0002] With the development of Internet technology and the popularization of mobile terminals, more and more services have begun to extend to online scenarios, and application platform software that can carry multiple sub-applications has emerged, avoiding users from installing different types of applications on mobile terminals. Instead, services are handled with the help of sub-applications installed in the application platform software. At the same time, sub-applications can also make full use of the sufficient user traffic of the application platform software to provide support for the service improvement of sub-applications. Summary of the Invention

[0003] One or more embodiments of this specification provide an account login processing method, comprising: obtaining an account login record generated by an IoT device performing an account login, and device registration information obtained by performing device registration for the IoT device. Based on the account login record and the device registration information, a login relationship verification is performed for the IoT device. A login message for the IoT device is generated based on the verification result, and the login message is pushed to the device user through a login sub-application. The device user accesses the login message through a host application installed on a user terminal, and performs the account login based on an application account in the host application.

[0004] One or more embodiments of the present specification provide an account login processing device, an information acquisition module, configured to obtain the account login record generated by the account login of the IoT device, and the device registration information obtained by registering the IoT device. A login relationship verification module is configured to perform login relationship verification for the IoT device based on the account login record and the device registration information. A login message push module is configured to generate a login message for the IoT device based on the verification result, and push the login message to the device user through the login sub-application. The device user accesses the login message through a host application installed on the user terminal, and performs the account login based on the application account in the host application.

[0005] One or more embodiments of the present specification provide an account login processing device, comprising: a processor; and a memory configured to store computer-executable instructions, wherein the computer-executable instructions, when executed, cause the processor to: obtain an account login record generated by an IoT device for account login, and device registration information obtained by registering the IoT device. Based on the account login record and the device registration information, a login relationship verification is performed for the IoT device. A login message for the IoT device is generated based on the verification result, and the login message is pushed to the device user through a login sub-application. The device user accesses the login message through a host application installed on a user terminal, and performs the account login based on an application account in the host application.

[0006] One or more embodiments of this specification provide a storage medium for storing computer-executable instructions, which implement the following process when executed by a processor: obtaining an account login record generated by an IoT device performing an account login, and device registration information obtained by performing device registration for the IoT device. Based on the account login record and the device registration information, a login relationship verification is performed for the IoT device. A login message for the IoT device is generated based on the verification result, and the login message is pushed to the device user through a login sub-application. The device user accesses the login message through a host application installed on a user terminal, and performs the account login based on an application account in the host application. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] In order to more clearly illustrate one or more embodiments of this specification or technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or descriptions of the prior art. Obviously, the drawings described below are only some embodiments described in this specification. Those skilled in the art can derive other drawings based on these drawings without inventive effort.

[0008] Figure 1 A flowchart of an account login processing method provided in one or more embodiments of this specification;

[0009] Figure 2 A flowchart of an account login processing method applied to IoT device scenarios provided by one or more embodiments of this specification;

[0010] Figure 3 A schematic diagram of an account login processing device provided in one or more embodiments of this specification;

[0011] Figure 4A schematic diagram of the structure of an account login processing device provided in one or more embodiments of this specification. DETAILED DESCRIPTION

[0012] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this document.

[0013] This specification provides an example of an account login processing method:

[0014] The account login processing method provided in this application provides an IoT device with a login method for account login using the application account of the host application, and based on the account login record generated by the IoT device account login and the device registration information obtained by the IoT device device registration, performs a login relationship verification on the IoT device to obtain a verification result and generates a corresponding login message, and provides the device user with an access channel to the login message through the login sub-application within the host application, so that the device user can access the login status of the IoT device conveniently and quickly through the login sub-application, while also improving the device user's perception of application account login, which helps to protect the device user's account security and account privacy.

[0015] Reference Figure 1 The account login processing method provided in this embodiment specifically includes steps S102 to S106.

[0016] Step S102: Acquire an account login record generated by performing account login on an IoT device, and device registration information obtained by performing device registration on the IoT device.

[0017] The IoT (Internet of Things) devices include but are not limited to at least one of the following: vehicle-mounted terminals, vehicle-connected terminal devices, smart speakers, unmanned vending machines, autonomous radios, interactive advertising screens, POS devices, and smart home appliances such as smart TVs and smart refrigerators.

[0018] In this embodiment, when the IoT device performs account login, it specifically uses the application account of the device user of the IoT device to log in. The application account is applied for by the device user during the application access process. The subsequent device user accesses the login message of the IoT device through the login sub-application within the application. Therefore, this application is called the host application, that is, the application is the host application of the login sub-application.

[0019] The login sub-application is a sub-application used to provide device users with services such as managing IoT devices that perform account logins and pushing login messages to IoT devices. The sub-application includes a program function module or application component that is hosted on the host application, or a program function module or application component that is loaded and installed by the host application, such as a mini-program within the host application. From a service perspective, the sub-application has the ability to independently provide self-contained services, such as a mini-program running within a payment application that manages IoT device account logins and pushes login messages.

[0020] This embodiment uses the application account of the device user in the host application as the login basis for account login in the IoT device, realizes the account login of the device user's IoT device through the application account of the host application, and uses the login sub-application of the host application to realize access to the account login status of the IoT device, thereby realizing account login control of the device user's IoT device with the help of the application account and the login sub-application, enabling the device user to perform more flexible and convenient login management of the IoT device through the host application.

[0021] In actual applications, since the device user may have one or more IoT devices, there may be a situation where multiple IoT devices log in to the same application account at the same time. In order to ensure the security of account login and avoid the problem of privacy data leakage caused by multiple IoT devices logging in to the same application account at the same time, a login control policy is optionally configured for the application account, and the account login of the IoT device is controlled by the login control policy. The login control policy includes: the login status of IoT devices with the same device type for the application account in the same time interval is mutually exclusive, while the login status of IoT devices with different device types for the application account in the same time interval is non-mutually exclusive. The device type refers to the device type determined according to the device model. Specifically, IoT devices with the same device name and model are IoT devices of the same device type. Conversely, IoT devices with different device names or models are IoT devices of different device types.

[0022] On the basis of the login control policy configured for the application account, in order to prevent multiple IoT devices of the same device type from logging into the same application account at the same time, account login control of the IoT device is achieved through login switching during the account login process. Specifically, this embodiment provides an optional implementation method, in which the account login includes: querying whether the login devices of the application account include mutually exclusive devices that have mutually exclusive login states with the IoT device; if so, canceling the login state of the mutually exclusive device for the application account, and performing login processing for the application account on the IoT device; if not, performing login processing for the application account on the IoT device.

[0023] Furthermore, to improve the convenience and flexibility of IoT device account login, during account login using an application account as the basis for the IoT device, before querying whether the login devices of the application account include mutually exclusive devices with mutually exclusive login states with the IoT device, the host application performs account login by scanning a code on the IoT device. Specifically, in an optional implementation manner provided in this embodiment, the account login further includes:

[0024] Scan the login identification code displayed by the IoT device or the configured entity identification code through the host application's code scanning component to log in and access;

[0025] The account login record is generated based on the application account and the device type and device identification of the IoT device, and the device type and the device identification are obtained after decoding the login identification code or decoding the identification code image of the entity identification code.

[0026] In actual applications, for IoT devices equipped with display components, the login identification code for account login can be displayed on the display component of the IoT device, and the host application scans the login identification code for login access. For example, the login QR code is displayed on the screen of the vehicle terminal, and the device user uses the host application to scan the login QR code to initiate login access; for IoT devices not equipped with display components, the host application can scan the identification code pasted on the outside of the IoT device for login access.

[0027] During specific implementation, after the IoT device performs account login processing based on the application account, the account login record generated by the IoT device for account login is obtained. In this embodiment, the IoT device uses the application account of the device user in the host application for account login, and the application account management of the host application is managed by the application provider of the host application. Specifically, the application account is associated through the account login system. In view of this, an optional implementation method provided in this embodiment is to obtain the account login record generated by the IoT device for account login, specifically including obtaining the device login message of the IoT device synchronized by the account login system, and extracting the account login record carried by the device login message.

[0028] In this embodiment, to enhance the service diversity of IoT devices and enrich their usage scenarios, a sub-application pool is provided for IoT devices. IoT devices can access and process corresponding services by accessing sub-applications in the sub-application pool. Accessing sub-applications in the sub-application pool requires that the device provider register the IoT device. In an optional implementation provided by this embodiment, the device registration process includes: associating each IoT device in the device list submitted by the device provider with the device type contained in the device registration request submitted by the device provider to the service platform, and generating device registration information for each IoT device; the device registration information includes the association between the device identifier and the device type. The service platform can be the execution entity of the account login processing method; it can also be connected to the server that is the execution entity of the account login processing method and synchronously register the device registration information of the IoT device with the server, or the server can obtain the device registration information of the registered IoT device from the service platform. The device provider includes the manufacturer, seller, and / or service operator of the IoT device.

[0029] Optionally, after registering the IoT device on the service platform, the IoT device obtains access rights to the sub-applications in the sub-application pool accessed by the service platform.

[0030] Optionally, the IoT device is installed with a device client and a service container, or the IoT device is installed with a device client that configures a service container; wherein, the IoT device accesses the sub-application through the service container.

[0031] The device client refers to the system program that the IoT device itself relies on for operation. The service container refers to the runtime framework or runtime engine that loads and runs sub-applications on the IoT device. By installing the service container on the IoT device or configuring the service container on the device client installed on the IoT device, the IoT device can access sub-applications in the remote sub-application pool. As a lightweight container, the service container reduces the usage of the IoT device's operating resources. Therefore, when the IoT device's operating resources are limited, the IoT device's reduced usage of the IoT device's operating resources also helps improve the IoT device's own operating efficiency.

[0032] In actual applications, the service client is installed and configured by the device provider of the IoT device. After the installation and configuration is completed, after the IoT device is started, the device client can communicate data with the service container through interface calls. Specifically, when the IoT device is started, the device client calls the service container to establish a data connection with the service platform. Based on the established data connection, the service platform can send the service data or service message of the device user generated by the application service provider of the sub-application to the service container, and the service container will return the sent service data or service message to the device client for display or processing.

[0033] Step S104: Based on the account login record and the device registration information, a login relationship verification is performed on the IoT device.

[0034] The account login record generated by the above-mentioned IoT device based on the account login of the application account includes the association relationship between the device type and the device identification. The device type and device management relationship is created after the IoT device logs in to the application account, and is specifically created based on the device type of the IoT device and the device identification of the IoT device.

[0035] In specific implementation, in the process of performing login relationship verification for the IoT device based on the account login record and the device registration information, starting from the device type and device identification association relationship contained in the account login record and the device type and device identification relationship contained in the device registration information, a login relationship verification is performed for the IoT device, so as to verify the currently logged-in device information with the device information registered for the IoT device by the device provider, so as to avoid inconsistency between the currently logged-in IoT device and the IoT device registered in advance by the device provider (for example, before the device leaves the factory), thereby avoiding illegal login of the device user's application account.

[0036] Specifically, in an optional implementation provided by this embodiment, performing a login relationship verification on the IoT device based on the account login record and the device registration information includes:

[0037] Verifying whether the device type and device identification association relationship included in the account login record is consistent with the device type and device identification association relationship included in the device registration information;

[0038] If they are consistent, it indicates that the device information of the IoT device of the currently logged-in application account is consistent with the device information of the IoT device in the previous device provider registration process, and the verification result is determined to be passed;

[0039] If there is any inconsistency, it indicates that the device information of the IoT device of the currently logged-in application account is inconsistent with the device information of the IoT device during the previous device registration process by the device provider. As the party that produces, sells or provides device services, the device information provided by the device provider during the device registration process is valid and there can be no abnormality. As the party that owns the IoT device, the device user obviously has no motivation to forge the device information. Therefore, when the device information of the IoT device of the previously logged-in application account is inconsistent with the device information of the IoT device during the previous device registration process by the device provider, the possible reason can only be that the application account of the device user is leaked and other users illegally use the application account of the device user to log in to the account. In this case, the verification result is determined to be verification failed.

[0040] Step S106: Generate a login message for the IoT device based on the verification result, and push the login message to the device user through the login sub-application.

[0041] As mentioned above, the login sub-application refers to a sub-application used to provide device users with management of IoT devices for account login and push login message services for IoT devices. This step generates a login message for the IoT device based on the verification result obtained by performing the login relationship verification mentioned above, and pushes the login message to the device user through the login sub-application, so that the device user can promptly perceive the situation of the IoT device logging into the application account, providing the possibility for the device user to promptly control and manage the account login.

[0042] Specifically, based on the fact that the verification results obtained after the login relationship verification in the above steps are divided into two types, namely, verification passed and verification failed, this step generates a login message for the IoT device based on the verification results, which is also divided into login messages corresponding to the two verification results, namely, verification passed and verification failed. Specifically, in an optional implementation provided by this embodiment, a login message for the IoT device is generated based on the verification result, including: if the verification result is verification passed, a login success message is generated for the IoT device to log in to the application account; if the verification result is verification failed, a login exception message is generated for the IoT device to log in to the application account abnormally.

[0043] During specific implementation, in order to enhance the device user's awareness of the device login status of the application account, this embodiment provides an optional implementation method, which provides the device user with an access interface for accessing the device login status of the application account through the login sub-application, so as to enhance the device user's control over the device login of the application account. Specifically, if a device query request submitted by the device user through the login sub-application is detected, the login device in the login state of the application account is queried in the account login record containing the application account, and a device list of the queried login devices is returned to the login sub-application.

[0044] Based on this, under the premise that the device user can access the device login status of the application account through the login sub-application of the host application, in order to further enhance the device user's account login control over the IoT device that logs in to the application account, the device user can also be provided with an implementation method for remote device login management through the login sub-application, and more in-depth account login control is performed through remote device login management. In an optional implementation method provided by this embodiment, remote device login management is implemented in the following way: according to the login cancellation instruction of the target login device selected by the device user in the device list submitted by the login sub-application, the login state of the target login device for the application account is canceled.

[0045] The following uses the application of an account login processing method provided in this embodiment in an IoT device scenario as an example to further illustrate the account login processing method provided in this embodiment. Figure 2 , an account login processing method applied to IoT device scenarios, specifically including the following steps.

[0046] In step S202, the device user scans the login identification code displayed by the IoT device through the host application's code scanning component to log in and access.

[0047] Step S204: Check whether the login devices of the application account of the host application include mutually exclusive devices that are mutually exclusive with the IoT device in login state;

[0048] If yes, execute steps S206 to S212;

[0049] If not, the account login system is called to perform login processing of the application account on the IoT device, and steps S208 to S212 are executed.

[0050] Step S206 , cancel the login state of the mutually exclusive device for the application account, and call the account login system to perform the application account login process on IoT device A.

[0051] Step S208: Obtain the device login message of the IoT device synchronized with the account login system, and extract the account login record carried in the device login message.

[0052] Step S210: Obtain device registration information obtained by the device provider through device registration for the IoT device on the service platform.

[0053] Step S212: Verify whether the device type and device identification association relationship included in the account login record is consistent with the device type and device identification association relationship included in the device registration information;

[0054] If yes, go to step S214;

[0055] If so, execute step S216.

[0056] Step S214: Generate a login success message for the IoT device to log in to the application account, and push the login success message of the IoT device to the device user through the login sub-application of the host application.

[0057] Step S216: Generate a login exception message indicating that the IoT device has logged into the application account abnormally, and push the IoT device login exception message to the device user through the login sub-application of the host application.

[0058] After the IoT device's login success message or login exception message is pushed to the IoT device, the message is displayed on the host application installed on the device user's mobile terminal. If the displayed login success message or login exception message is triggered by the device user, the user is redirected to the host application's login sub-application.

[0059] After jumping to the login sub-application, the device user can query all login devices of the application account through the login sub-application. Accordingly, if a device query request submitted by the device user through the login sub-application is detected, the login devices in the login state of the application account are queried in the account login record containing the application account, and the device list of the queried login devices is returned to the login sub-application; further, the device user can also manage the login devices in the device list, specifically cancel the login state of the target login device for the application account according to the login cancellation instruction of the target login device selected by the device user in the device list.

[0060] An embodiment of an account login processing device provided in this specification is as follows:

[0061] In the above embodiment, an account login processing method is provided, and correspondingly, an account login processing device is also provided, which is described below with reference to the accompanying drawings.

[0062] Reference Figure 3 , which shows a schematic diagram of an account login processing device provided by this embodiment.

[0063] Since the device embodiment corresponds to the method embodiment, the description is relatively simple. For the relevant parts, please refer to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0064] This embodiment provides an account login processing device, the device comprising:

[0065] An information acquisition module 302 is configured to acquire an account login record generated by an IoT device performing account login, and device registration information obtained by performing device registration for the IoT device;

[0066] A login relationship verification module 304 is configured to perform a login relationship verification on the IoT device based on the account login record and the device registration information;

[0067] A login message push module 306 is configured to generate a login message for the IoT device according to the verification result, and push the login message to the device user through the login sub-application;

[0068] The device user accesses the login message through a host application installed on a user terminal, and performs the account login according to an application account in the host application.

[0069] An embodiment of an account login processing device provided in this specification is as follows:

[0070] Corresponding to the account login processing method described above, based on the same technical concept, one or more embodiments of this specification also provide an account login processing device, which is used to execute the account login processing method provided above. Figure 4 A schematic diagram of the structure of an account login processing device provided in one or more embodiments of this specification.

[0071] This embodiment provides an account login processing device, including:

[0072] like Figure 4 As shown, the account login processing device may vary significantly due to different configurations or performance, and may include one or more processors 401 and memory 402. The memory 402 may store one or more applications or data. The memory 402 may be either short-term or persistent storage. The application stored in the memory 402 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in the account login processing device. Furthermore, the processor 401 may be configured to communicate with the memory 402 to execute the series of computer-executable instructions in the memory 402 on the account login processing device. The account login processing device may also include one or more power supplies 403, one or more wired or wireless network interfaces 404, one or more input / output interfaces 405, one or more keyboards 406, and the like.

[0073] In a specific embodiment, the account login processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the account login processing device, and the one or more programs are configured to be executed by one or more processors, including computer-executable instructions for performing the following:

[0074] Obtaining the account login record generated by the IoT device through account login, as well as the device registration information obtained by registering the IoT device;

[0075] Performing a login relationship verification on the IoT device based on the account login record and the device registration information;

[0076] Generate a login message for the IoT device based on the verification result, and push the login message to the device user through the login sub-application;

[0077] The device user accesses the login message through a host application installed on a user terminal, and performs the account login according to an application account in the host application.

[0078] An embodiment of a storage medium provided in this specification is as follows:

[0079] Corresponding to the account login processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0080] The storage medium provided in this embodiment is used to store computer-executable instructions. When the computer-executable instructions are executed by a processor, the following process is implemented:

[0081] Obtaining the account login record generated by the IoT device through account login, as well as the device registration information obtained by registering the IoT device;

[0082] Performing a login relationship verification on the IoT device based on the account login record and the device registration information;

[0083] Generate a login message for the IoT device based on the verification result, and push the login message to the device user through the login sub-application;

[0084] The device user accesses the login message through a host application installed on a user terminal, and performs the account login according to an application account in the host application.

[0085] It should be noted that the embodiment of the storage medium in this specification and the embodiment of the account login processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0086] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0087] In the 1930s, technological improvements could be clearly distinguished as either hardware improvements (for example, improvements to circuit structures like diodes, transistors, and switches) or software improvements (improvements to process flows). However, with the advancement of technology, many process flow improvements today can now be considered direct improvements to hardware circuit structures. Designers almost always create the corresponding hardware circuit structure by programming the improved process flow into the hardware circuit. Therefore, it cannot be said that a process flow improvement cannot be implemented using hardware modules. For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA), is an integrated circuit whose logical function is determined by user programming. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to hire a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly done using "logic compiler" software. This is similar to the software compiler used when developing programs. Before compilation, the original code must also be written in a specific programming language, called a hardware description language (HDL). There is not just one HDL, but many, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art will also understand that by simply programming the method flow in one of these hardware description languages ​​and then programming it into an integrated circuit, a hardware circuit that implements the logic method flow can be easily obtained.

[0088] The controller can be implemented in any suitable manner. For example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also know that in addition to implementing the controller in a purely computer-readable program code format, the controller can be implemented in the form of logic gates, switches, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the means for implementing various functions included therein can also be considered as structures within the hardware component. Or even, the means for implementing various functions can be considered as both a software module implementing the method and a structure within the hardware component.

[0089] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0090] For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0091] Those skilled in the art will appreciate that one or more embodiments of this specification may be provided as a method, system, or computer program product. Thus, one or more embodiments of this specification may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0092] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0093] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0094] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0095] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0096] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0097] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0098] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0099] One or more embodiments of this specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types. One or more embodiments of this specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0100] The various embodiments in this specification are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiments are generally similar to the method embodiments, so the description is relatively simple. For relevant parts, refer to the description of the method embodiments.

[0101] The foregoing description is merely an example of the present invention and is not intended to limit the present invention. Persons skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention are intended to be included within the scope of the claims herein.

Claims

1. A method for processing account login, comprising: Obtaining an account login record generated by an IoT device through account login using an application account of a host application, as well as device registration information obtained by registering the IoT device; Verify that the device type and device identification associations contained in the account login record and the device registration information are consistent; Generate a login message for the IoT device based on the verification result, and push the login message to the device user through the login sub-application; The IoT device accesses the sub-application through the installed service container, and the login states of IoT devices of different device types for the application account in the same time interval are not mutually exclusive.

2. The account login processing method according to claim 1, wherein the application account is configured with a login control policy; the login control policy includes: The login states of IoT devices of the same device type within the same time period for the application account are mutually exclusive.

3. The account login processing method according to claim 2, wherein the account login comprises: Check whether the login devices of the application account include mutually exclusive devices that have mutually exclusive login states with the IoT device; If so, cancel the login state of the mutually exclusive device for the application account, and perform the login process of the application account on the IoT device.

4. The account login processing method according to claim 3, wherein the account login further comprises: Scan the login identification code displayed by the IoT device or the configured entity identification code through the host application's code scanning component to log in and access; The account login record is generated based on the application account and the device type and device identification of the IoT device, and the device type and the device identification are obtained after decoding the login identification code or decoding the identification code image of the entity identification code.

5. The account login processing method according to claim 1, further comprising: If a device query request submitted by the device user through the login sub-application is detected, querying the login device of the application account in the account login record containing the application account; Return the device list of the queried login devices to the login sub-application.

6. The account login processing method according to claim 5, further comprising: According to the login cancellation instruction of the target login device selected by the device user in the device list submitted by the login sub-application, the login state of the target login device for the application account is canceled.

7. The account login processing method according to claim 1, if the device type and device identification association relationship contained in the account login record and the device registration information are consistent, the verification result is determined to be verification passed; if they are inconsistent, the verification result is determined to be verification failed.

8. The account login processing method according to claim 7, wherein generating a login message for the IoT device based on the verification result comprises: If the verification result is passed, a login success message is generated indicating that the IoT device has logged into the application account. If the verification result is that the verification fails, a login exception message is generated indicating that the IoT device has logged into the application account abnormally.

9. The account login processing method according to claim 1, wherein the device registration comprises: According to the device type carried in the device registration request submitted by the device provider on the service platform, each IoT device in the device list submitted by the device provider is associated with the device type, and device registration information of each IoT device is generated.

10. The account login processing method according to claim 9, wherein the IoT device, after registering the device on the service platform, obtains access rights to the sub-applications in the sub-application pool accessed by the service platform.

11. The account login processing method according to claim 10, wherein the IoT device is installed with a device client and the service container.

12. The account login processing method according to claim 1, wherein obtaining the account login record generated by the IoT device through account login based on the application account of the host application comprises: Obtain the device login message of the IoT device synchronized with the account login system, and extract the account login record carried in the device login message.

13. An account login processing device, comprising: An information acquisition module is configured to obtain an account login record generated by an IoT device through account login according to an application account of a host application, and device registration information obtained by registering the IoT device; a login relationship verification module configured to verify whether the device type and device identification association relationship contained in the account login record and the device registration information are consistent; a login message push module, configured to generate a login message for the IoT device based on the verification result, and push the login message to the device user via the login sub-application; The IoT device accesses the sub-application through the installed service container, and the login states of IoT devices of different device types for the application account in the same time interval are not mutually exclusive.

14. An account login processing device, comprising: processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: Obtaining an account login record generated by an IoT device through account login using an application account of a host application, as well as device registration information obtained by registering the IoT device; Verify that the device type and device identification associations contained in the account login record and the device registration information are consistent; Generate a login message for the IoT device based on the verification result, and push the login message to the device user through the login sub-application; The IoT device accesses the sub-application through the installed service container, and the login states of IoT devices of different device types for the application account in the same time interval are not mutually exclusive.

15. A storage medium for storing computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the following process: Obtaining an account login record generated by an IoT device through account login using an application account of a host application, as well as device registration information obtained by registering the IoT device; Verify that the device type and device identification associations contained in the account login record and the device registration information are consistent; Generate a login message for the IoT device based on the verification result, and push the login message to the device user through the login sub-application; The IoT device accesses the sub-application through the installed service container, and the login states of IoT devices of different device types for the application account in the same time interval are not mutually exclusive.

Images