CN114547569A - Account login processing method and device - Google Patents

Account login processing method and device Download PDF

Info

Publication number
CN114547569A
CN114547569A CN202210129227.0A CN202210129227A CN114547569A CN 114547569 A CN114547569 A CN 114547569A CN 202210129227 A CN202210129227 A CN 202210129227A CN 114547569 A CN114547569 A CN 114547569A
Authority
CN
China
Prior art keywords
login
account
application
iot
equipment
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210129227.0A
Other languages
Chinese (zh)
Inventor
党家豪
王少龙
边炀凯
马静
刘鹏飞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alipay Hangzhou Information Technology Co Ltd
Original Assignee
Alipay Hangzhou Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alipay Hangzhou Information Technology Co Ltd filed Critical Alipay Hangzhou Information Technology Co Ltd
Priority to CN202210129227.0A priority Critical patent/CN114547569A/en
Publication of CN114547569A publication Critical patent/CN114547569A/en
Priority to PCT/CN2023/071261 priority patent/WO2023151439A1/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31User authentication
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/107License processing; Key processing
    • G06F21/1078Logging; Metering

Abstract

The embodiment of the specification provides an account login processing method and device, wherein the account login processing method comprises the following steps: acquiring an account login record generated by account login of an IoT device and device registration information obtained by device registration of the IoT device; performing login relationship verification for the IoT device based on the account login record and the device registration information; generating a login message of the IoT equipment according to a verification result, and pushing the login message to an equipment user through a login sub-application; and the equipment user accesses the login message through a host application installed on the user terminal, and performs account login according to an application account of the host application.

Description

Account login processing method and device
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a method and an apparatus for processing account login.
Background
With the development of internet technology and the popularization of mobile terminals, more and more services begin to extend to online scenes, application platform software capable of carrying a plurality of sub-applications appears, the situation that a user installs different types of application programs on the mobile terminal is avoided, the service is handled by means of the sub-applications carried in the application platform software, and meanwhile, the sub-applications can also make full use of the sufficient user traffic of the application platform software to provide assistance for the service improvement of the sub-applications.
Disclosure of Invention
One or more embodiments of the present specification provide an account login processing method, including: the method comprises the steps of obtaining an account login record generated by account login of an IoT device and device registration information obtained by device registration of the IoT device. And performing login relationship verification on the IoT equipment based on the account login record and the equipment registration information. And generating a login message of the IoT equipment according to a verification result, and pushing the login message to an equipment user through a login sub-application. And the equipment user accesses the login message through a host application installed on the user terminal, and performs account login according to an application account of the host application.
One or more embodiments of the present specification provide an account login processing apparatus, an information obtaining module configured to obtain 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. A login relationship checking module configured to perform login relationship checking for the IoT device based on the account login record and the device registration information. And the login message pushing module is configured to generate a login message of the IoT equipment according to the verification result and push the login message to the equipment user through the login sub-application. And the equipment user accesses the login message through a host application installed on the user terminal, and the account login is carried out according to an application account of 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 that, when executed, cause the processor to: the method comprises the steps of obtaining an account login record generated by account login of an IoT device and device registration information obtained by device registration of the IoT device. And performing login relationship verification on the IoT equipment based on the account login record and the equipment registration information. And generating a login message of the IoT equipment according to a verification result, and pushing the login message to an equipment user through a login sub-application. And the equipment user accesses the login message through a host application installed on the user terminal, and performs account login according to an application account of the host application.
One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed by a processor, implement the following: the method comprises the steps of obtaining an account login record generated by account login of an IoT device, and obtaining device registration information obtained by device registration of the IoT device. And performing login relationship verification on the IoT equipment based on the account login record and the equipment registration information. And generating a login message of the IoT equipment according to a verification result, and pushing the login message to an equipment user through a login sub-application. And the equipment user accesses the login message through a host application installed on the user terminal, and performs account login according to an application account of the host application.
Drawings
In order to more clearly illustrate one or more embodiments or technical solutions in the prior art in the present specification, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without inventive exercise;
FIG. 1 is a flowchart of a processing method of an account login processing method according to one or more embodiments of the present disclosure;
fig. 2 is a process flow diagram of an account login processing method applied to an IoT device scenario according to one or more embodiments of the present specification;
FIG. 3 is a schematic diagram of an account login processing device according to one or more embodiments of the present disclosure;
fig. 4 is a schematic structural diagram of an account login processing device according to one or more embodiments of the present specification.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.
An embodiment of a method for processing account login provided by the present specification:
according to the account login processing method, a login mode of account login by adopting an application account of a host application is provided for IoT equipment, account login records generated by account login of the IoT equipment and equipment registration information obtained by equipment registration of the IoT equipment are based on, login relation verification is carried out on the IoT equipment to obtain verification results and generate corresponding login information, an access channel for accessing the login information through a login sub-application in the host application is provided for an equipment user, the equipment user can conveniently and quickly access the login state of the IoT equipment through the login sub-application, meanwhile, perception of the equipment user on application account login is improved, and account safety and account privacy of the equipment user are protected.
Referring to fig. 1, the account login processing method provided in this embodiment specifically includes step S102 to step S106.
Step S102, obtaining an account login record generated by account login of an IoT device, and device registration information obtained by device registration of the IoT device.
The IoT (Internet of things) device, including but not limited to at least one of: the car machine terminal of vehicle installation, the external terminal equipment of vehicle, intelligent audio amplifier, unmanned machine of selling, independently the radio, interactive advertising screen, POS equipment to and intelligent household electrical appliances products such as intelligent TV, intelligent refrigerator.
In this embodiment, when the IoT device performs account login, specifically, the application account of the device user of the IoT device is used for account login, the application account is applied for obtaining by the device user in the access process of the application, and the subsequent device user accesses the login message of the IoT device through the login sub-application in the application, so that the application is called a host application, that is, the application is the host application of the login sub-application.
The login sub-application is a sub-application for providing a login message service for managing and pushing an IoT device performing account login to a device user, and the sub-application includes a program function module or an application component loaded on a host application, or a program function module or an application component loaded and installed by the host application, such as an applet in the host application. From a service perspective, the sub-application has the capability of independently providing self-closed loop services, such as an applet running within the payment application that performs account login management, login message pushing for IoT devices.
In the embodiment, the application account of the device user in the host application is used as a login basis for account login in the IoT device, the account login of the IoT device of the device user is realized through the application account of the host application, and the access to the account login situation of the IoT device is realized through the login sub-application of the host application, so that the account login control of the IoT device of the device user is realized through the application account and the login sub-application, and the device user can perform more flexible and convenient login management on the IoT device through the host application.
In practical applications, since one or more IoT devices of a device user may be provided, a situation that multiple IoT devices log in to a same application account at the same time may occur, and for this reason, in order to ensure account login security and avoid a problem that privacy data is leaked when multiple IoT devices log in to the same application account at the same time, optionally, a login control policy is configured for the application account, and account login of the IoT devices is controlled through the login control policy, where the login control policy includes: IoT devices with the same device type in the same time interval are mutually exclusive in login state of the application account, and IoT devices with different device types in the same time interval are not mutually exclusive in login state of the application account. The device type refers to a device type determined according to a device model, specifically, IoT devices with the same device name and model are IoT devices with the same device type, and conversely, IoT devices with different device names or models are IoT devices with different device types.
Specifically, in this embodiment, an optional implementation is provided, where the account login includes, in order to prevent multiple IoT devices of the same device type from logging in the same application account at the same time and to implement account login control on the IoT devices through login switching in an account login process, the login control includes: inquiring whether login devices of the application account contain mutually exclusive devices which are mutually exclusive with the IoT devices in login states; if yes, canceling the login state of the mutual exclusion device aiming at the application account, and performing login processing of the application account on the IoT device; if not, performing login processing of the application account on the IoT device.
Further, to improve convenience and flexibility of an IoT device in an account login process, in an account login process of the IoT device based on an application account, before querying whether a login device of the application account includes a mutex device that is mutually exclusive to a login state of the IoT device, the IoT device is scanned by a host application to perform account login, and specifically, in an optional implementation manner provided in this embodiment, the account login further includes:
scanning a login identification code displayed by the IoT equipment or a configured entity identification code through a code scanning component of the host application to perform login access;
the account login record is generated based on the application account and the device type and the device identifier of the IoT device, and the device type and the device identifier are obtained after decoding the login identification code or decoding an identification code image of the entity identification code.
In practical applications, for an IoT device configured with a display component, a login identification code for account login is displayed on the display component of the IoT device, a host application scans the login identification code to perform login access, for example, a login two-dimensional code is displayed on a screen of a car terminal, and a device user scans the login two-dimensional code by using the host application to initiate login access; for an IoT device that is not configured with a display component, login access may be performed by the host application scanning an identification code that is pasted externally to the IoT device.
In a specific implementation, after an IoT device performs account login processing based on an application account, an account login record generated by the IoT device performing account login is acquired, in this embodiment, the IoT device performs account login using an application account of a device user in a host application, and application account management of the host application is managed by an application provider of the host application, specifically, application account association is performed through an account login system.
In this embodiment, in order to improve service diversity of an IoT device, enrich a usage scenario of the IoT device, and provide a sub-application pool for the IoT device, the IoT device may perform corresponding service access and processing by accessing a sub-application in the sub-application pool, and a premise of accessing the sub-application in the sub-application pool is that a device provider performs device registration on the IoT device, in an optional implementation manner provided in this embodiment, the device registration includes: associating each IoT device in a device list submitted by a device provider to the device type according to the device type carried by a device registration request submitted by the device provider on a service platform, and generating device registration information of each IoT device; the device registration information contains the association relationship between the device identification and the device type. The service platform may be an execution subject that executes the account login processing method; the IoT device registration information may be synchronized with the server, or the server may obtain the IoT device registration information from the service platform. The device provider comprises a producer, a seller and/or a service operation and maintenance party of the IoT device.
Optionally, the IoT device after device registration is performed on the service platform obtains an access right to access a sub-application in a 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 configuring a service container; wherein the IoT device performs access of the sub-application through the service container.
The device client refers to a system program on which the IoT device itself runs. The service container refers to a running framework or a running engine for loading and running the sub-application on the IoT device, and the IoT device can access the sub-application in the remote sub-application pool by installing the service container on the IoT device or configuring the service container on a device client installed on the IoT device. The service container is used as a light-weight container, so that the occupation of the operation resources of the IoT equipment is reduced, and under the condition that the operation resources of the IoT equipment are limited, the occupation of the operation resources of the IoT equipment is reduced by the IoT equipment, and the operation efficiency of the IoT equipment is improved.
In practical application, the service client is installed and configured by an equipment provider of the IoT equipment, after the installation and configuration are completed, the equipment client can perform data communication with the service container in an interface calling manner after the IoT equipment is started, specifically, when the IoT equipment is started, the equipment client calls the service container to establish data connection with the service platform, based on the established data connection, the service platform can issue service data or service messages of the equipment user generated by the application service provider of the sub-application to the service container, and the service container transmits the issued service data or service messages back to the equipment client for display or processing.
Step S104, based on the account login record and the device registration information, performing login relation verification on the IoT device.
The account login record generated by the IoT device performing account login based on the application account includes an association between a device type and a device identifier, where the association between the device type and the device identifier is created after the IoT device performs account login for the application account, and specifically, the association is created based on the device type of the IoT device and the device identifier of the IoT device.
In specific implementation, in the process of checking the login relationship of the IoT device based on the account login record and the device registration information, a login relationship check is performed on the IoT device based on the association relationship between the device type and the device identifier included in the account login record and the relationship between the device type and the device identifier included in the device registration information, so that the currently logged-in device information is checked against the device information, which is registered by the device provider for the IoT device, to prevent the currently logged-in IoT device from being inconsistent with the IoT device, which is registered by the device provider in advance (for example, before the device leaves a factory), and thus prevent the application account of the device user from being logged in illegally.
Specifically, in an optional implementation manner provided by this embodiment, the performing login relationship verification on the IoT device based on the account login record and the device registration information includes:
checking whether the association relation between the equipment type and the equipment identifier contained in the account login record is consistent with the association relation between the equipment type and the equipment identifier contained in the equipment registration information;
if the IoT equipment information is consistent with the equipment information of the IoT equipment, the IoT equipment is registered by the equipment provider, and the verification result is determined to be passed;
if the IoT equipment information of the application account is inconsistent with the equipment information of the IoT equipment registered by the previous equipment provider, the equipment provider is used as a party for producing, selling or providing equipment service, the device information provided during the device registration process is valid, no anomalies are likely to exist, and, as the party owning the IoT device, the device user's apparently no incentive to forge the device information, and therefore, in the case that the device information of the IoT device of the application account previously logged in does not match the device information of the IoT device in the device registration process performed by the previous device provider, the possible reason may only be that the application account of the device user is leaked, and other users illegally utilize the application account of the equipment user to log in the account, and in the case, the verification result is determined to be that the verification fails.
And step S106, generating a login message of the IoT equipment according to the verification result, and pushing the login message to the equipment user through the login sub-application.
As described above, the login sub-application is a sub-application for providing a login message service for managing and pushing IoT devices performing account login to device users, and in this step, on the basis of obtaining a verification result through the above login relationship verification, a login message of the IoT devices is generated according to the obtained verification result, and the login message is pushed to the device users through the login sub-application, so that the device users can timely sense the situation that the IoT devices log in application accounts, and the realization possibility is provided for the device users to timely perform account login control and management.
Specifically, on the basis that the check result obtained after the check of the login relationship in the above step is divided into two types, namely, a check-pass result and a check-fail result, the step generates the login message of the IoT device according to the check result, and also divides the login message into login messages corresponding to the two types of check-pass result and the check-fail result, specifically, in an optional implementation manner provided in this embodiment, the generating of the login message of the IoT device according to the check result includes: if the verification result is that the verification is passed, generating a login success message of the IoT equipment for logging in the application account; and if the verification result is that the verification fails, generating a login abnormal message that the IoT equipment logs in the application account abnormally.
In a specific implementation, in order to improve the perception degree of the device user on the device login condition of the application account, in an optional implementation manner provided in this embodiment, an access interface for accessing the device login condition of the application account is provided for the device user through the login sub-application, so as to enhance the device login control of the device user on the application account.
Based on this, on the premise that the device user can access the device login condition of the application account through the login sub-application of the host application, in order to further enhance account login control of the device user on the IoT device that logs in the application account, an implementation manner of remotely performing device login management through the login sub-application may be provided for the device user, and deeper account login control is performed through the remote device login management, in an optional implementation manner provided in this embodiment, the following manner is adopted to implement the remote device login management: and according to a login canceling instruction of the target login device selected by the device user in the device list and submitted by the login sub-application, canceling the login state of the target login device aiming at the application account.
The account login processing method provided in this embodiment is further described below by taking an application of the account login processing method provided in this embodiment in an IoT device scenario as an example, and referring to fig. 2, the account login processing method applied in the IoT device scenario specifically includes 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 perform login access.
Step S204, inquiring whether login equipment of the application account of the host application contains mutually exclusive equipment with login state mutual exclusion with the IoT equipment;
if yes, go to step S206 to step S212;
if not, the account login system is called to perform login processing of the application account on the IoT device, and step S208 to step S212 are performed.
Step S206, canceling the login state of the mutual exclusion device aiming at the application account, and calling the account login system to perform login processing of the application account on the IoT device A.
Step S208, obtaining the device login information of the IoT device synchronized with the account login system, and extracting the account login record carried by the device login information.
Step S210, obtaining device registration information obtained by the device provider performing device registration on the IoT device in the service platform.
Step S212, checking whether the association relationship between the equipment type and the equipment identifier contained in the account login record is consistent with the association relationship between the equipment type and the equipment identifier contained in the equipment registration information;
if yes, go to step S214;
if yes, go to step S216.
Step S214, a login success message of the IoT device for logging in the application account is generated, and the login success message of the IoT device is pushed to the device user through the login sub-application of the host application.
Step S216, generating a login abnormal message of the IoT device login application account abnormality, and pushing the login abnormal message of the IoT device to the device user through the login sub-application of the host application.
After the login success message or the login abnormal message of the IoT equipment is pushed to the IoT equipment, the host application installed on the mobile terminal of the equipment user displays the message, and if the login success message or the login abnormal message displayed by the message is triggered by the equipment user, the host application is jumped to;
after jumping to the login sub-application, the device user can inquire all login devices of the application account through the login sub-application, correspondingly, if a device inquiry 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 inquired in an account login record containing the application account, and an inquired device list of the login devices is returned to the login sub-application; further, the device user may also perform login management on the login device in the device list, specifically, according to a login cancellation instruction of the target login device selected by the device user in the device list, cancel the login state of the target login device for the application account.
An embodiment of an account login processing apparatus provided in this specification is as follows:
in the above embodiment, an account login processing method is provided, and correspondingly, an account login processing apparatus is also provided, which is described below with reference to the accompanying drawings.
Referring to fig. 3, a schematic diagram of an account login processing apparatus provided in this embodiment is shown.
Since the device embodiments correspond to the method embodiments, the description is relatively simple, and the relevant portions may refer to the corresponding description of the method embodiments provided above. The device embodiments described below are merely illustrative.
The present embodiment provides an account login processing apparatus, where the apparatus includes:
an information obtaining module 302 configured to obtain an account login record generated by account login of an IoT device and device registration information obtained by device registration of the IoT device;
a login relationship checking module 304 configured to perform login relationship checking for the IoT device based on the account login record and the device registration information;
a login message pushing module 306 configured to 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;
and the equipment user accesses the login message through a host application installed on the user terminal, and performs account login according to an application account of the host application.
An embodiment of an account login processing device provided in this specification is as follows:
on the basis of the same technical concept, corresponding to the account login processing method described above, one or more embodiments of the present specification further provide an account login processing device, where the account login processing device is configured to execute the account login processing method, and fig. 4 is a schematic structural diagram of an account login processing device provided in one or more embodiments of the present specification.
The account login processing device provided by the embodiment comprises:
as shown in fig. 4, the account login processing device may have a relatively large difference due to different configurations or performances, and may include one or more processors 401 and a memory 402, where one or more stored applications or data may be stored in the memory 402. Wherein memory 402 may be transient or persistent. The application program stored in memory 402 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in an account login processing device. Still further, the processor 401 may be configured to communicate with the memory 402 to 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 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.
In one particular 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 configured to be executed by the one or more processors include computer-executable instructions for:
acquiring an account login record generated by account login of an IoT device and device registration information obtained by device registration of the IoT device;
performing login relationship verification for the IoT device based on the account login record and the device registration information;
generating a login message of the IoT equipment according to a verification result, and pushing the login message to an equipment user through a login sub-application;
and the equipment user accesses the login message through a host application installed on the user terminal, and performs account login according to an application account of the host application.
An embodiment of a storage medium provided in this specification is as follows:
on the basis of the same technical concept, one or more embodiments of the present specification further provide a storage medium corresponding to the above-described account login processing method.
The present embodiment provides a storage medium for storing computer-executable instructions, which when executed by a processor implement the following procedures:
acquiring an account login record generated by account login of an IoT device and device registration information obtained by device registration of the IoT device;
performing login relationship verification for the IoT device based on the account login record and the device registration information;
generating a login message of the IoT equipment according to a verification result, and pushing the login message to an equipment user through a login sub-application;
and the equipment user accesses the login message through a host application installed on the user terminal, and performs account login according to an application account of 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, and therefore, for specific implementation of this embodiment, reference may be made to implementation of the foregoing corresponding method, and repeated details are not described here.
The foregoing description of specific embodiments has been presented for purposes of illustration and description. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than 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. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
In the 30 s of the 20 th century, improvements in a technology could clearly be distinguished between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process 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 functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, 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 which include, but are not limited to, the following microcontrollers: the ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, 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.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in multiple software and/or hardware when implementing the embodiments of the present description.
One skilled in the art will appreciate that one or more embodiments of the present description 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 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, and the like) having computer-usable program code embodied therein.
The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The 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 Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
One or more embodiments of the present description 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 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 memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of this document and is not intended to limit this document. Various modifications and changes may occur to those skilled in the art from this document. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.

Claims (15)

1. An account login processing method comprises the following steps:
acquiring an account login record generated by account login of an IoT device and device registration information obtained by device registration of the IoT device;
performing login relationship verification for the IoT device based on the account login record and the device registration information;
generating a login message of the IoT equipment according to a verification result, and pushing the login message to an equipment user through a login sub-application;
and the equipment user accesses the login message through a host application installed on the user terminal, and performs account login according to an application account of the host application.
2. The account login processing method of claim 1, wherein the application account is configured with a login control policy; the login control policy comprises: and the login state of the IoT devices with the same device type in the same time interval is mutually exclusive to the login state of the application account.
3. The account login processing method of claim 2, wherein the account login comprises:
inquiring whether login devices of the application account contain mutually exclusive devices which are mutually exclusive with the IoT devices in login states;
and if so, canceling the login state of the mutual exclusion device aiming at the application account, and performing login processing of the application account on the IoT device.
4. The account login processing method of claim 3, the account login further comprising:
scanning a login identification code displayed by the IoT equipment or a configured entity identification code through a code scanning component of the host application to perform login access;
the account login record is generated based on the application account and the device type and the device identifier of the IoT device, and the device type and the device identifier are obtained after decoding the login identification code or decoding an identification code image of the entity identification code.
5. The account login processing method of claim 1, further comprising:
if the device query request submitted by the device user through the login sub-application is detected, querying login devices in the login state of the application account in account login records containing the application account;
and returning the inquired device list of the login device to the login sub-application.
6. The account login processing method of claim 5, further comprising:
and according to a login canceling instruction of the target login device selected by the device user in the device list and submitted by the login sub-application, canceling the login state of the target login device aiming at the application account.
7. The account login processing method of claim 1, wherein the performing login relationship verification for the IoT device based on the account login record and the device registration information comprises:
checking whether the association relation between the equipment type and the equipment identifier contained in the account login record is consistent with the association relation between the equipment type and the equipment identifier contained in the equipment registration information;
if the verification result is consistent, determining that the verification result is verification pass;
and if the verification result is not consistent, determining that the verification result is verification failure.
8. The account login processing method of claim 7, the generating a login message for the IoT device according to the verification result, comprising:
if the verification result is that the verification is passed, generating a login success message of the IoT equipment for logging in the application account;
and if the verification result is that the verification fails, generating a login abnormal message that the IoT equipment logs in the application account abnormally.
9. The account login processing method of claim 1, the device registering, comprising:
associating each IoT device in a device list submitted by a device provider to the device type according to the device type carried by a device registration request submitted by the device provider on a service platform, and generating device registration information of each IoT device.
10. The account login processing method according to claim 9, wherein the IoT device after device registration is performed on the service platform obtains an access right to access a sub-application in a sub-application pool accessed by the service platform.
11. The account login processing method of claim 10, the IoT device being installed with a device client and a service container, or the IoT device being installed with a device client configuring a service container;
wherein the IoT device performs access of the sub-application through the service container.
12. The account login processing method of claim 1, wherein the obtaining of the account login record generated by the IoT device for account login comprises:
and acquiring the equipment login information of the IoT equipment synchronized by an account login system, and extracting the account login record carried by the equipment login information.
13. An account login processing device, comprising:
the information acquisition module is configured to acquire an account login record generated by account login of an IoT device and device registration information obtained by device registration of the IoT device;
a login relation checking module configured to perform login relation checking for the IoT device based on the account login record and the device registration information;
the login message pushing module is configured to generate a login message of the IoT equipment according to a verification result and push the login message to an equipment user through a login sub-application;
and the equipment user accesses the login message through a host application installed on the user terminal, and performs account login according to an application account of the host application.
14. An account login processing device, comprising:
a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to:
acquiring an account login record generated by account login of an IoT device and device registration information obtained by device registration of the IoT device;
performing login relationship verification for the IoT device based on the account login record and the device registration information;
generating a login message of the IoT equipment according to a verification result, and pushing the login message to an equipment user through a login sub-application;
and the equipment user accesses the login message through a host application installed on the user terminal, and performs account login according to an application account of the host application.
15. A storage medium storing computer-executable instructions that when executed by a processor implement the following:
acquiring an account login record generated by account login of an IoT device and device registration information obtained by device registration of the IoT device;
performing login relationship verification for the IoT device based on the account login record and the device registration information;
generating a login message of the IoT equipment according to a verification result, and pushing the login message to an equipment user through a login sub-application;
and the equipment user accesses the login message through a host application installed on the user terminal, and performs account login according to an application account of the host application.
CN202210129227.0A 2022-02-11 2022-02-11 Account login processing method and device Pending CN114547569A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202210129227.0A CN114547569A (en) 2022-02-11 2022-02-11 Account login processing method and device
PCT/CN2023/071261 WO2023151439A1 (en) 2022-02-11 2023-01-09 Account login processing

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210129227.0A CN114547569A (en) 2022-02-11 2022-02-11 Account login processing method and device

Publications (1)

Publication Number Publication Date
CN114547569A true CN114547569A (en) 2022-05-27

Family

ID=81672667

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210129227.0A Pending CN114547569A (en) 2022-02-11 2022-02-11 Account login processing method and device

Country Status (2)

Country Link
CN (1) CN114547569A (en)
WO (1) WO2023151439A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116436707A (en) * 2023-06-14 2023-07-14 北京创新乐知网络技术有限公司 Login method, device, medium and computer equipment based on applet
WO2023151439A1 (en) * 2022-02-11 2023-08-17 支付宝(杭州)信息技术有限公司 Account login processing

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102523134A (en) * 2011-12-08 2012-06-27 中兴通讯股份有限公司 Method for detecting abnormal exit of client terminal and website server
CN107404488B (en) * 2017-08-07 2020-11-27 台州市吉吉知识产权运营有限公司 Method and device for mutual exclusion of multiple terminal devices in same application
CN110300117B (en) * 2019-07-05 2021-03-02 杭州博联智能科技股份有限公司 IOT device and user binding authentication method, device and medium
CN114896570A (en) * 2020-05-27 2022-08-12 支付宝(杭州)信息技术有限公司 Installation management method, device and system of applet
CN111651746B (en) * 2020-06-01 2023-03-10 支付宝(杭州)信息技术有限公司 Login data processing method, device, equipment and system
CN114547569A (en) * 2022-02-11 2022-05-27 支付宝(杭州)信息技术有限公司 Account login processing method and device

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023151439A1 (en) * 2022-02-11 2023-08-17 支付宝(杭州)信息技术有限公司 Account login processing
CN116436707A (en) * 2023-06-14 2023-07-14 北京创新乐知网络技术有限公司 Login method, device, medium and computer equipment based on applet
CN116436707B (en) * 2023-06-14 2023-08-25 北京创新乐知网络技术有限公司 Login method, device, medium and computer equipment based on applet

Also Published As

Publication number Publication date
WO2023151439A1 (en) 2023-08-17

Similar Documents

Publication Publication Date Title
CN107426169B (en) Service processing method and device based on permission
CN109002362B (en) Service method, device and system and electronic equipment
KR102194052B1 (en) Service execution method and device
CN107038042B (en) Service execution method and device
WO2023151439A1 (en) Account login processing
CN111538980B (en) Account binding method, device and system for application program
CN107479868B (en) Interface loading method, device and equipment
CN108804399B (en) Form verification method and device
KR20190069574A (en) Wireless network type detection method and apparatus, and electronic device
CN108550033B (en) Method and device for displaying unique identifier of digital object
CN111460428A (en) Authority management method and device of android system and readable medium
CN109343970B (en) Application program-based operation method and device, electronic equipment and computer medium
CN108804120B (en) Page construction method, device, equipment and storage medium
CN111198677A (en) Equipment object generation method, device and equipment
CN113296740A (en) Service object processing method, device, equipment and machine readable medium
WO2023216872A1 (en) Event processing method and apparatus applied to iot device
WO2023151440A1 (en) Program update processing
CN114527983A (en) Interface adaptation method and device based on middleware and electronic equipment
CN112114804A (en) Application program generation method, device and system
CN112579118A (en) Method, device, system, medium and equipment for updating configuration information of microservice
CN107483534B (en) Service processing method and device
CN115878860A (en) Menu generation method, device, server equipment and medium
CN114546843A (en) Program debugging processing method and device
CN113626787B (en) Equipment fingerprint generation method and related equipment
CN114500635A (en) Service processing method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination