WO2023151439A1

WO2023151439A1 - Account login processing

Info

Publication number: WO2023151439A1
Application number: PCT/CN2023/071261
Authority: WO
Inventors: 党家豪; 王少龙; 边炀凯; 马静; 刘鹏飞
Original assignee: 支付宝(杭州)信息技术有限公司
Priority date: 2022-02-11
Filing date: 2023-01-09
Publication date: 2023-08-17
Also published as: CN114547569A

Abstract

Embodiments of the present description provide an account login processing method and apparatus. The account login processing method comprises: obtaining an account login log generated when an IoT device implements account login, and device registration information obtained when performing device registration for the IoT device; performing login relationship verification on the IoT device on the basis of the account login log and the device registration information; and generating a login message of the IoT device according to a verification result, and pushing the login message to a device user by means of a login sub-application, wherein the device user accesses the login message by means of a host application installed in a user terminal, and achieves account login according to an application account of the host application.

Description

Account login processing

technical field

This document relates to the technical field of data processing, and in particular to an account login processing method and device.

Background technique

With the development of Internet technology and the popularity of mobile terminals, more and more services have begun to extend to online scenarios, such as application platform software that can carry multiple sub-applications, which prevents users from installing different types of applications on mobile terminals. Instead, the sub-application carried in the application platform software is used to realize the service management. At the same time, the sub-application can also make full use of the sufficient user traffic of the application platform software, so as to provide assistance for the service improvement of the sub-application.

Contents of the invention

One or more embodiments of this specification provide an account login processing method, including: acquiring an account login record generated by an IoT device for 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 check is performed on the IoT device. Generate a login message of the IoT device according to the verification result, and push the login message to the device user through the login sub-application. Wherein, the device user accesses the login message through a host application installed on the user terminal, and performs the account login according to an application account in the host application.

One or more embodiments of this specification provide an account login processing device, an information acquisition module, configured to acquire an account login record generated by an IoT device for account login, and device registration information obtained by performing device registration for the IoT device . The login relationship checking module is configured to check the login relationship of the IoT device based on the account login record and the device registration information. The login message push module is configured to generate the login message of the IoT device according to the verification result, and push the login message to the device user through the login sub-application. Wherein, the device user accesses the login message through a host application installed on the user terminal, and performs the account login according to an application account in the host application.

One or more embodiments of the present specification provide an account login processing device, including a processor and a memory configured to store computer-executable instructions. Wherein, when the computer-executable instructions are executed, the processor: acquires an account login record generated by an IoT device for 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 check is performed on the IoT device. Generate the login message of the IoT device according to the verification result, and push the login message to the device user through the login sub-application. Wherein, the device user accesses the login message through a host application installed on the user terminal, and performs the account login according to an application account in the host application.

One or more embodiments of this specification provide a storage medium for storing computer-executable instructions, and when the computer-executable instructions are executed by a processor, the following process is implemented: obtain an account login record generated by an IoT device for account login , and the 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 check is performed on the IoT device. Generate a login message of the IoT device according to the verification result, and push the login message to the device user through the login sub-application. Wherein, the device user accesses the login message through a host application installed on the user terminal, and performs the account login according to an application account in the host application.

Description of drawings

In order to more clearly illustrate one or more embodiments of this specification or the technical solutions in the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, in the following description The accompanying drawings are only some embodiments recorded in this specification. For those skilled in the art, other drawings can also be obtained according to these drawings without any creative effort;

Fig. 1 is a processing flowchart of an account login processing method provided by one or more embodiments of this specification;

Fig. 2 is a processing flowchart of an account login processing method applied to IoT device scenarios provided by one or more embodiments of this specification;

Fig. 3 is a schematic diagram of an account login processing device provided by one or more embodiments of this specification;

Fig. 4 is a schematic structural diagram of an account login processing device provided by one or more embodiments of this specification.

Detailed ways

In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the following will describe the technical solutions in one or more embodiments of this specification in conjunction with the drawings in one or more embodiments of this specification The technical solution is clearly and completely described, and obviously, the described embodiments are only a part of the embodiments in this specification, rather than all the embodiments. Based on one or more embodiments in this specification, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the scope of protection of this document.

An embodiment of an account login processing method provided in this specification: the account login processing method provided in this application provides IoT devices with a login method using the application account of the host application for account login, and the account login generated based on IoT device account login Record and register the device registration information of the IoT device, verify the login relationship of the IoT device to obtain the verification result and generate the corresponding login message, and provide the device user with an access channel to access the login message through the login sub-application in the host application , so that the device user can conveniently and quickly access the login status of the IoT device through the login sub-application, and also improve the device user's perception of the application account login, which helps to protect the account security and account privacy of the device user.

Referring to FIG. 1 , the account login processing method provided by this embodiment specifically includes step S102 to step S106 .

Step S102, acquiring an account login record generated by the IoT device for account login, and device registration information obtained by performing device registration for the IoT device.

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

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 perform account login. The application account is obtained by the device user during the application access process. The login sub-application accesses the login information of the IoT device, so this application is called the host application, that is, the application is the host application of the login sub-application.

The login sub-application refers to a sub-application used to provide the device user with a service of managing the IoT device for account login and pushing the login message of the IoT device, and the sub-application includes a program function module or an application loaded in the host application Components, or program function modules or application components loaded and installed by the host application, such as applets in the host application. From a service point of view, the sub-applications have the ability to independently provide self-closed-loop services, such as a small program running in the payment application for account login management of IoT devices and self-closed-loop capability for login message push.

In this embodiment, the application account of the device user in the host application is used as the login basis for account login on the IoT device, and the account login of the device user's IoT device is realized through the application account of the host application, and the login sub-application of the host application is used to realize the login of the IoT device. Access to the account login status of the device, so as to realize the account login control of the IoT device of the device user by means of the application account and the login sub-application, so that the device user can perform more flexible and convenient login management of the IoT device through the host application.

In practical applications, since the device user may have one or more IoT devices, multiple IoT devices may log in to the same application account at the same time. For this, in order to ensure account login security, avoid multiple IoT devices from logging in at the same time If there is a problem of privacy data leakage in the same application account, it is optional to configure a login control policy for the application account, and control the account login of the IoT device through the login control policy. The login control policy includes: the device type in the same time interval The login status of the application account is mutually exclusive for the same IoT device, and the login status of the application account is not mutually exclusive for IoT devices of different device types within the same time interval. 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, and conversely, IoT devices with different device names or models are IoT devices of different device types. equipment.

On the basis of the login control strategy configured by 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, the account login control of the IoT device is realized by switching logins during the account login process, Specifically, this embodiment provides an optional implementation manner in which the account login includes: querying whether the login device of the application account contains a mutually exclusive device that is mutually exclusive with the IoT device in a login state; if so, Cancel the login status of the mutually exclusive device for the application account, and perform the login process of the application account on the IoT device; if not, perform the login process of the application account on the IoT device.

Further, in order to improve the convenience and flexibility of the account login process of the IoT device, in the process of the account login of the IoT device based on the application account, in the above query whether the login device of the application account includes the Before the IoT device has a mutually exclusive device in the login state, the host application scans the code for the IoT device to log in to the account. Specifically, in an optional implementation mode provided in this embodiment, the account login is also Including: scanning the login identification code displayed by the IoT device or the configured entity identification code through the scanning component of the host application to log in and access; wherein, the account login record is based on the application account and the device of the IoT device A type and a device identifier are generated, and the device type and the device identifier are obtained after decoding the login identification code or decoding the identification code image of the entity identification code.

In practical applications, for an IoT device configured with a display component, 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 to log in and access, for example, in the The login QR code is displayed on the screen, and the device user uses the host application to scan the login QR code to initiate login access; for IoT devices without display components, the host application can scan the identification code pasted on the outside of the IoT device for login access.

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's 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, while The application account management of the host application is managed by the application provider of the host application. Specifically, the application account association is performed through the account login system. For this, in an optional implementation mode provided by this embodiment, the IoT device is obtained for account management. The process of logging into the generated account login record specifically includes 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.

In this embodiment, in order to improve the service diversity of IoT devices and enrich the use scenarios of IoT devices, a sub-application pool is provided for IoT devices, and IoT devices can perform corresponding service access and processing by accessing sub-applications in the sub-application pool. The prerequisite for accessing the sub-applications in the sub-application pool is that the device provider registers the IoT device. In an optional implementation mode provided in this embodiment, the device registration includes: according to the information submitted by the device provider on the service platform The device type carried in the device registration request, associate each IoT device in the device list submitted by the device provider with the device type, and generate the device registration information of each IoT device; the device registration information includes the device identification Associated with the device type. The service platform may be the executor who executes the account login processing method; it may also be connected to a server as the executor of the account login processing method, and register the device registration information of the IoT device with the server synchronously, or the server may Obtain the device registration information of the IoT device for device registration from the service platform. The device provider includes the producer, seller and/or service operator of the IoT device.

Optionally, the IoT device after device registration on the service platform obtains the access right to access the sub-applications in the sub-application pool accessed by the service platform.

Optionally, the IoT device is installed with a device client and a service container, or the IoT device is installed with a device client configured with a service container; wherein, the IoT device implements the sub-application through the service container access.

Wherein, the device client refers to a system program on which the operation of the IoT device itself depends. The service container refers to the running framework or running 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 implement remote Access to sub-applications in the sub-application pool. The service container, as a lightweight container, reduces the occupation of the operating resources of the IoT device, so that when the operating resources of the IoT device are limited, at the same time, the IoT device reduces the occupation of the operating resources of the IoT device. It helps to improve the operating efficiency of IoT devices.

In practical applications, the service client is installed and configured by the device provider of the IoT device. After the installation and configuration is completed, the device client can communicate with the service container through an interface call after the IoT device is started. Specifically, the IoT device When starting, 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 messages of the device user generated by the application server of the sub-application to the service container. , and the service container returns the delivered service data or service message to the device client for display or processing.

Step S104, based on the account login record and the device registration information, check the login relationship of the IoT device.

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 identifier. Created later, specifically based on the device type of the IoT device and the device identifier of the IoT device.

During specific implementation, during the process of verifying the login relationship of the IoT device based on the account login record and the device registration information, the device type and device identifier association relationship contained in the account login record and the device Based on the relationship between the device type and the device identifier contained in the registration information, the login relationship check is performed for the IoT device, so as to verify the currently logged-in device information and the device information registered by the device provider for the IoT device, so as to This is to prevent the currently logged-in IoT device from being inconsistent with the IoT device registered by the device provider in advance (for example, before the device leaves the factory), thereby preventing the device user's application account from being illegally logged in.

Specifically, in an optional implementation manner provided by this embodiment, based on the account login record and the device registration information, performing login relationship verification on the IoT device includes: verifying that the account login record contains Whether the association relationship between the device type and the device identifier contained in the device registration information and the device type and the device identifier contained in the device registration information are consistent; The device information of the IoT device during the registration process is consistent, and the verification result is determined to be verified; if it is inconsistent, it indicates that the device information of the IoT device of the currently logged-in application account is the same as that of the IoT device in the device registration process of the previous device provider. The device information does not match, and the device provider is the party that produces, sells or provides device services, the device information provided during the device registration process is valid, and there is no possibility of abnormality, and as the party that owns the IoT device, the device user’s Obviously, there is no motive to forge device information. Therefore, if the device information of the IoT device in the application account logged in before does not match the device information of the IoT device in the device registration process performed by the device provider, the possible reason can only be 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 failure.

Step S106, generating a login message of the IoT device according to the verification result, and pushing the login message to the device user through the login sub-application.

As mentioned above, the login sub-application refers to the sub-application used to provide the device user with the service of managing the IoT device for account login and pushing the login message of the IoT device. On the basis of the verification result, generate the login message of the IoT device according to the obtained verification result, and push the login message to the device user through the login sub-application, so that the device user can timely perceive the IoT device login application account This provides the possibility for device users to perform account login control and management in a timely manner.

Specifically, on the basis that the verification results obtained after the verification of the login relationship in the above steps are divided into two types: the verification passed and the verification failed, this step generates the login message of the IoT device according to the verification results, which are also divided into It is a login message corresponding to the two verification results of passing the verification and failing the verification. Specifically, in an optional implementation manner provided in this embodiment, the login message of the IoT device is generated according to the verification result, including : If the verification result is that the verification is passed, generate a login success message that the IoT device logs into the application account; if the verification result is that the verification fails, generate an exception for the IoT device to log in to the application account The login exception message for .

During specific implementation, in order to improve the device user's awareness of the device login status of the application account, in an optional implementation mode provided by this embodiment, the device user is provided with an access interface for accessing the device login status of the application account through the login sub-application , to enhance the device user’s device login management and control of the application account. Specifically, if the device query request submitted by the device user through the login sub-application is detected, the application is queried in the account login record containing the application account The login device in the login state of the account, and return the device list of the queried login device to the login sub-application.

Based on this, on 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 management and control of the IoT device that logs into the application account, the device user can also provide The implementation of remote device login management through the login sub-application is to perform more in-depth account login management and control through remote device login management. In an optional implementation mode provided in this embodiment, the 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 cancels the login status of the target login device for the application account.

The following uses an account login processing method provided in this embodiment in an IoT device scenario as an example to further explain the account login processing method provided in this embodiment. See Figure 2 for an account login processing method applied to an IoT device scenario. , including the following steps.

Step S202, the device user scans the login identification code displayed by the IoT device through the code scanning component of the host application to log in and access.

Step S204, query whether the login device of the application account of the host application includes a mutually exclusive device that is mutually exclusive with the IoT device in the login state; if yes, perform steps S206 to S212; if not, call the account login system to register the application account on the IoT device The log-in process of , and execute step S208 to step S212.

Step S206, cancel the login status of the mutually exclusive device for the application account, and call the account login system to perform application account login processing on the IoT device A.

Step S208, obtaining the device login message of the IoT device synchronized by the account login system, and extracting the account login record carried in the device login message.

Step S210, obtaining the device registration information obtained by the device provider registering the IoT device on the service platform.

Step S212, verify whether the association relationship between the device type and the device identifier included in the account login record is consistent with the association relationship between the device type and the device identifier included in the device registration information; if yes, execute step S214; if yes, execute step S216.

Step S214, generating a successful login message of the IoT device logging into the application account, and pushing the successful login message of the IoT device to the device user through the login sub-application of the host application.

Step S216, generating an abnormal login message indicating that the account of the IoT device login application is abnormal, and pushing the abnormal login message of the IoT device to the device user through the login sub-application of the host application.

After the successful login message or abnormal login message of the IoT device is pushed to the IoT device, the host application installed on the device user's mobile terminal displays the message. Go to the login sub-application of the host application; after jumping to the login sub-application, the device user can query all the login devices of the application account through the login sub-application. Correspondingly, if the device query request submitted by the device user through the login sub-application is detected , query the login device of the login status of the application account in the account login record containing the application account, and return the device list of the queried login device to the login sub-application; further, the device user can also log in to the login device in the device list Management, specifically according to the login cancel instruction of the target login device selected by the device user in the device list, cancel the login status of the target login device for the application account.

An example of an account login processing device provided in this specification is as follows: In the above-mentioned embodiment, an account login processing method is provided, and correspondingly, an account login processing device is also provided. Be explained.

Referring to FIG. 3 , it shows a schematic diagram of an account login processing device provided in this embodiment.

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

This embodiment provides an account login processing device, which includes: an information acquisition module 302 configured to acquire an account login record generated by an IoT device for account login, and device registration information obtained by performing device registration for the IoT device The login relationship verification module 304 is configured to verify the login relationship for the IoT device based on the account login record and the device registration information; the login message push module 306 is configured to generate the The login message of the IoT device, and push the login message to the device user through the login sub-application; wherein, the device user accesses the login message through the host application installed on the user terminal, and according to the application account in the host application Log in to the account.

An example of an account login processing device provided in this specification is as follows: 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. The login processing device is configured to execute the account login processing method provided above, and FIG. 4 is a schematic structural diagram of an account login processing device provided by one or more embodiments of this specification.

An account login processing device provided in this embodiment includes: as shown in FIG. 4 , the account login processing device may have relatively large differences due to different configurations or performances, and may include one or more than one processor 401 and memory 402 , one or more stored application programs or data may be stored in the memory 402 . Wherein, the storage 402 may be a short-term storage or a persistent storage. The application program stored in the memory 402 may include one or more modules (not shown in the figure), and each module 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, and execute a 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 sources 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.

In a specific embodiment, the account login processing device includes a memory, and one or more programs, wherein 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 into an account login processing device, and configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following: acquire an IoT device The account login record generated by account login, and the device registration information obtained by device registration for the IoT device; based on the account login record and the device registration information, the login relationship verification is performed for the IoT device; Generate a login message of the IoT device based on the verification result, and push the login message to the device user through the login sub-application; wherein, the device user accesses the login message through the host application installed on the user terminal, and according to the The application account of the application performs the account login.

An embodiment of a storage medium provided in this specification is as follows: 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.

The storage medium provided in this embodiment is used to store computer-executable instructions, and when the computer-executable instructions are executed by a processor, the following process is implemented: obtaining an account login record generated by an IoT device for account login, and targeting the IoT device The device registration information obtained by device registration; based on the account login record and the device registration information, the login relationship verification of the IoT device is performed; the login message of the IoT device is generated according to the verification result, and the login information is passed through the login sub- The application pushes the login message to the device user; wherein the device user accesses the login message through a host application installed on the user terminal, and performs account login according to an application account in the host application.

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, so the specific implementation of this embodiment can refer to the implementation of the corresponding method above. Let me repeat.

The foregoing describes specific embodiments of this specification. Other implementations are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. Multitasking and parallel processing are also possible or may be advantageous in certain embodiments.

In the 1930s, the improvement of a technology can be clearly distinguished as an improvement in hardware (for example, improvements in circuit structures such as diodes, transistors, switches, etc.) or improvements in software (improvement in method flow). However, with the development of technology, the improvement of many current method flows can be regarded as the direct improvement of the hardware circuit structure. Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose logic function is determined by programming the device by the user. It is programmed by the designer to "integrate" a digital system on a PLD, instead of asking a chip manufacturer to design and make a dedicated integrated circuit chip. Moreover, nowadays, instead of making integrated circuit chips by hand, this kind of programming is mostly realized by "logic compiler (logic compiler)" software, which is similar to the software compiler used when program development and writing, but before compiling The original code of the computer must also be written in a specific programming language, which is called a hardware description language (Hardware Description Language, HDL), and there is not only one kind of HDL, but many kinds, 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., are currently the most commonly used The most popular are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. It should also be clear to those skilled in the art that only a little logical programming of the method flow in the above-mentioned hardware description languages and programming into an integrated circuit can easily obtain a hardware circuit for realizing the logic method flow.

The controller may be implemented in any suitable way, for example the controller may take the form of a microprocessor or processor and a computer readable medium storing computer readable program code (such as software or firmware) executable by the (micro)processor , logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers and embedded microcontrollers, examples of controllers include but are not limited to the following microcontrollers: ARC 625D, 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 also know that, in addition to realizing the controller in a purely computer-readable program code mode, it is entirely possible to make the controller use logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded The same function can be realized in the form of a microcontroller or the like. Therefore, such a controller can be regarded as a hardware component, and the devices included in it for realizing various functions can also be regarded as structures within the hardware component. Or even, means for realizing various functions can be regarded as a structure within both a software module realizing a method and a hardware component.

The systems, devices, modules, or units described in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementing device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or Combinations of any of these devices.

For the convenience of description, when describing the above devices, functions are divided into various units and described separately. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and/or hardware.

Those skilled in the art should understand that one or more embodiments of this specification may be provided as a method, system or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The description is described with reference to flowchart and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

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

Memory may include non-permanent storage in computer readable media, in the form of random access memory (RAM) and/or nonvolatile memory such as read-only memory (ROM) or flash RAM. Memory is an example of computer readable media.

Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can be implemented by any method or technology for storage of information. Information may be computer readable instructions, data structures, modules of a program, 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, A magnetic tape cartridge, disk storage or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media excludes transitory computer-readable media, such as modulated data signals and carrier waves.

It should also be noted that the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes Other elements not expressly listed, or elements inherent in the process, method, commodity, or apparatus are also included. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

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

Each embodiment in this specification is described in a progressive manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for relevant parts, refer to part of the description of the method embodiment.

The above description is only an embodiment of this document, and is not intended to limit this document. Various modifications and changes to this document will occur to those skilled in the art. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this document shall be included within the scope of the claims of this document.

Claims

A method for processing account login, comprising:

Obtain the account login record generated by the account login of the IoT device, and the device registration information obtained by device registration for the IoT device;

Based on the account login record and the device registration information, perform login relationship verification for the IoT device;

Generate a login message of the IoT device according to the verification result, and push the login message to the device user through the login sub-application;

Wherein, the device user accesses the login message through a host application installed on the user terminal, and performs the account login according to an application account in the host application.
The account login processing method according to claim 1,

The application account is configured with a login control policy;

The login control strategy includes: IoT devices of the same device type in the same time interval are mutually exclusive of the login states of the application account.
The account login processing method according to claim 2, said account login comprising:

Query whether the login device of the application account includes a mutually exclusive device that is mutually exclusive with the IoT device in the login state;

If so, cancel the login state of the mutually exclusive device for the application account, and perform login processing of the application account on the IoT device.
The account login processing method according to claim 3, said account login further comprising:

Scan the login identification code displayed by the IoT device or the configured entity identification code through the code scanning component of the host application to perform login access;

Wherein, the account login record is generated based on the application account and the device type and device ID of the IoT device, and the device type and the device ID decode the login ID code or identify the entity The identification code image of the code is obtained after decoding.
The account login processing method according to claim 1, further comprising:

If the device query request submitted by the device user through the login sub-application is detected, query the login device of the login state of the application account in the account login record containing the application account;

The device list of the queried login devices is returned to the login sub-application.
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 cancelled.
According to the account login processing method according to claim 1, said checking the login relationship of the IoT device based on the account login record and the device registration information includes:

Verifying whether the association between the device type and the device identifier included in the account login record is consistent with the association between the device type and the device identifier included in the device registration information;

If they are consistent, it is determined that the verification result is passed;

If they are inconsistent, it is determined that the verification result is that the verification fails.
According to the account login processing method according to claim 7, said generating the login message of the IoT device according to the verification result comprises:

If the verification result is that the verification is passed, generate a login success message for the IoT device to log into the application account;

If the verification result is that the verification fails, generate an abnormal login message indicating that the IoT device is abnormally logged into the application account.
According to the account login processing method according to claim 1, said device registration includes:

According to the device type carried in the device registration request submitted by the device provider on the service platform, associate each IoT device in the device list submitted by the device provider with the device type, and generate device registration information for each IoT device.
According to the account login processing method according to claim 9, the IoT device after device registration on the service platform obtains the access right to access the sub-applications in the sub-application pool accessed by the service platform.
According to the account login processing method according to claim 10, the IoT device is installed with a device client and a service container, or, the IoT device is installed with a device client configured with a service container;

Wherein, the IoT device accesses the sub-application through the service container.
According to the account login processing method according to claim 1, the acquisition of the account login record generated by the IoT device for account login includes:

Obtaining the device login message of the IoT device synchronized by the account login system, and extracting the account login record carried in the device login message.
An account login processing device, comprising:

The information acquisition module is configured to acquire the account login record generated by the account login of the IoT device, and the device registration information obtained by device registration for the IoT device;

The 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;

The login message push module is configured to generate the login message of the IoT device according to the verification result, and push the login message to the device user through the login sub-application;

Wherein, the device user accesses the login message through a host application installed on the user terminal, and performs the account login according to an application account in the host application.
An account login processing device, comprising:

a processor; and, a memory configured to store computer-executable instructions that, when executed, cause the processor to:

Obtain the account login record generated by the account login of the IoT device, and the device registration information obtained by device registration for the IoT device;

Based on the account login record and the device registration information, perform login relationship verification for the IoT device;

Generate a login message of the IoT device according to the verification result, and push the login message to the device user through the login sub-application;

Wherein, the device user accesses the login message through a host application installed on the user terminal, and performs the account login according to an application account in the host application.
A storage medium for storing computer-executable instructions that, when executed by a processor, implement the following processes:

Obtain the account login record generated by the account login of the IoT device, and the device registration information obtained by device registration for the IoT device;

Based on the account login record and the device registration information, perform login relationship verification for the IoT device;

Generate a login message of the IoT device according to the verification result, and push the login message to the device user through the login sub-application;

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