CN111666546B - Application login method and device - Google Patents
Application login method and device Download PDFInfo
- Publication number
- CN111666546B CN111666546B CN202010564127.1A CN202010564127A CN111666546B CN 111666546 B CN111666546 B CN 111666546B CN 202010564127 A CN202010564127 A CN 202010564127A CN 111666546 B CN111666546 B CN 111666546B
- Authority
- CN
- China
- Prior art keywords
- phone number
- mobile phone
- application
- information
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/34—User authentication involving the use of external additional devices, e.g. dongles or smart cards
- G06F21/35—User authentication involving the use of external additional devices, e.g. dongles or smart cards communicating wirelessly
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0853—Network architectures or network communication protocols for network security for authentication of entities using an additional device, e.g. smartcard, SIM or a different communication terminal
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computing Systems (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a login method and a login device of an application, and relates to the technical field of Internet. The specific embodiment comprises the following steps: responding to detection of login operation of an application, and acquiring mobile phone number information of a user of the application; responding to successful acquisition of the mobile phone number information, and acquiring registration information of the user in the application; acquiring first indication information indicating whether the mobile phone number information is matched with the registration information; the application is logged in response to the first indication indicating a match. The application can determine the flow of the login application through the matching condition of the mobile phone number information and the user identifier, and can realize quick login application without paying to an operator under the matching condition, thereby avoiding the generation of cost in the login process and improving the login efficiency of the registered user.
Description
Technical Field
The embodiment of the application relates to the technical field of computers, in particular to the technical field of Internet, and particularly relates to a login method and device of an application.
Background
With the development of internet technology, users can use applications by using terminals such as mobile phones and the like at any time and any place. The kinds of applications are also diverse, such as video applications, image processing applications, instant messaging applications, and the like.
Users often need to first log in to an application in order to use the application. In the related art, a user needs to perform a registration operation in advance, thereby leaving information such as an account number and a password. Thus, when a user logs in, three ways can be adopted: the first method is to input account numbers, passwords and the like for users, and realize login to an application for login; the second is that the terminal carries out password-free login by taking a number from an operator; and thirdly, acquiring a verification code for the terminal through a mobile phone number input by a user by using a service provided by an operator, so as to log in. The latter two of these three login modes can be achieved by requiring the application platform to pay the operator.
Disclosure of Invention
Provided are a login method and device of an application, electronic equipment and a storage medium.
According to a first aspect, there is provided a login method of an application, comprising: responding to the detection of login operation of the application, and acquiring mobile phone number information of a user of the application; responding to successful acquisition of the mobile phone number information, and acquiring registration information of a user in an application; acquiring first indication information indicating whether the mobile phone number information is matched with registration information or not; in response to the first indication information indicating a match, the application is logged in.
According to a second aspect, there is provided a login device for an application, comprising: the first acquisition unit is configured to acquire mobile phone number information of a user of the application in response to detection of login operation of the application; the second acquisition unit is configured to acquire registration information of the user in the application in response to successful acquisition of the mobile phone number information; a third acquisition unit configured to acquire first indication information indicating whether the mobile phone number information and the registration information match; and a login unit configured to login the application in response to the first indication information indicating the match.
According to a third aspect, there is provided an electronic device comprising: one or more processors; and a storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the method as any of the embodiments of the login method for the application.
According to a fourth aspect, there is provided a computer readable storage medium having stored thereon a computer program which when executed by a processor implements a method as in any of the embodiments of the login method of an application.
According to the scheme of the application, the flow of the login application can be determined through the matching condition of the mobile phone number information and the user identifier, and under the matching condition, the quick login application can be realized without paying to an operator, thereby avoiding the generation of cost in the login process and improving the login efficiency of the registered user.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the accompanying drawings in which:
FIG. 1 is an exemplary system architecture diagram in which some embodiments of the present application may be applied;
FIG. 2 is a flow chart of one embodiment of a login method for an application according to the present application;
FIG. 3 is a schematic illustration of an application scenario of a login method of an application according to the present application;
FIG. 4 is a schematic diagram of the architecture of one embodiment of a login device for an application according to the present application;
fig. 5 is a block diagram of an electronic device for implementing a login method for an application of an embodiment of the application.
Detailed Description
Exemplary embodiments of the present application will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present application are included to facilitate understanding, and are to be considered merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other. The application will be described in detail below with reference to the drawings in connection with embodiments.
Fig. 1 shows an exemplary system architecture 100 of an embodiment of a login method of an application or a login device of an application to which the present application may be applied.
As shown in fig. 1, a system architecture 100 may include a terminal device 101, a network 104, and servers 102, 103. The network 104 is the medium used to provide communication links between the terminal device 101 and the servers 102, 103. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the servers 102, 103 via the network 104 using the terminal device 101 to receive or send messages or the like. Various communication client applications, such as a video-type application, a live application, an instant messaging tool, a mailbox client, social platform software, etc., may be installed on the terminal device 101.
The terminal device 101 may be hardware or software. When the terminal device 101 is hardware, it may be various electronic devices with a display screen including, but not limited to, a smart phone, a tablet computer, an electronic book reader, a laptop portable computer, a desktop computer, and the like. When the terminal apparatus 101 is software, it can be installed in the above-listed electronic apparatus. Which may be implemented as multiple software or software modules (e.g., multiple software or software modules for providing distributed services) or as a single software or software module. The present application is not particularly limited herein.
The servers 102, 103 may be servers providing various services, such as a background server providing support for the terminal device 101. The background server may analyze and process the received data such as the matching request, and feed back the processing result (for example, the first indication information) to the terminal device. In practice, server 102 may be an operator server and server 103 may be an application server.
It should be noted that, the login method of the application provided by the embodiment of the present application may be executed by the servers 102, 103 or the terminal device 101, and accordingly, the login device of the application may be set in the servers 102, 103 or the terminal device 101.
It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
With continued reference to FIG. 2, a flow 200 of one embodiment of a login method for an application in accordance with the present application is shown. The login method of the application is used for the terminal and specifically comprises the following steps:
in step 201, in response to detecting a login operation to an application, mobile phone number information of a user of the application is acquired.
In this embodiment, an execution body (for example, a terminal device shown in fig. 1) on which the login method of an application runs may acquire cell phone number information for logging in the application in response to detecting a login operation to the application. Specifically, the application here is an application installed in the above-described terminal. The user's login operation to the application may be clicking on an icon of the application, launching the application using voice, and so on. The user of the application refers to a registered user of the application, and is also a user registered or logged in at the terminal, for example, a user who has finally logged in to an account of the application at the terminal.
The mobile phone number information is information related to the mobile phone number of the user and can be used for logging in an application. For example, the mobile phone number information may include at least a part of the mobile phone number information, that is, the mobile phone number information may be the mobile phone number of the user itself or a part of the mobile phone number of the user. For another example, the mobile phone number information may be information obtained by processing a mobile phone number of a user, for example, may be an MD5 value obtained by an information Digest Algorithm (MD 5 Message-Digest Algorithm).
Step 202, in response to successful acquisition of the mobile phone number information, acquiring the registration information of the user in the application.
In this embodiment, if the execution body successfully acquires the mobile phone number information, that is, acquires the mobile phone number information, the execution body may acquire the registration information of the user in the application from a local (or other electronic devices). Specifically, the registration information may include information that the user inputs and generates (server generation or terminal generation employed by registration) at the time of application registration. For example, the registration information may include a unique identification generated by the application server for the user at registration, i.e., a user identification (DHID). In addition, the registration information may further include information such as a mobile phone number. In practice, the executing body may acquire all or part of the registration information to log in the application. The application server is a server that provides services for the applications.
Step 203, obtaining first indication information indicating whether the mobile phone number information is matched with the registration information.
In this embodiment, the executing body may acquire, from a local or other electronic device, indication information indicating whether the mobile phone number information matches the registration information, and use the indication information as the first indication information. In practice, the matched mobile phone number information corresponds to the same account as the above registration information, that is, corresponds to the same user, for example, the registration information of the account of the user for the third party is matched with the mobile phone number information acquired for the third party.
In step 204, the application is logged in response to the first indication indicating a match.
In this embodiment, the executing entity may log in to the application in response to the first indication information indicating that the mobile phone number information matches the registration information. Specifically, the execution body may execute a preset code for logging in the application, so as to log in the application. For example, the executing body may implement login by using a service provided by the operator server, specifically, the executing body needs to perform password-free login to the operator server (after obtaining the pre-fetching number of the mask mobile phone number), and once the number is successfully fetched, the executing body may log in the application.
The method provided by the embodiment of the application can determine the flow of the login application through the matching condition of the mobile phone number information and the user identifier, and can realize quick login application without paying to an operator under the matching condition, thereby avoiding the generation of cost in the login process and improving the login efficiency of the registered user.
In some optional implementations of the present embodiment, the login application in step 204 may include: displaying a preset password-free login page, and logging in an application by using a local application login inlet, wherein the application login inlet is an inlet provided by a non-operator server.
In these optional implementations, the executing body may display a preset password-free login page and log in the application when the first indication information indicates that the mobile phone number information matches the registration information. The password-free login refers to a login mode without inputting an account number and a password and also without verification.
In the prior art, in order to implement a login application, a terminal generally needs to receive a password-free login service provided by an operator server. An operator refers to an operator providing a data network, such as chinese mobile communication, etc. The terminal receives the service provided by the operator server, namely, the process of fetching the number is carried out, and the application server is required to pay the operator.
In order to avoid this cost, in case the first indication information indicates a match, the step of executing the subject login application may not utilize the service provided by the operator server, i.e. the step of logging in the application is independent of the service enhanced by the operator server. The execution body may directly run a local preset password-free login code to login the application using a local application login entry. The password-free login page is a page for indicating that the terminal is currently performing password-free login. In some cases, the password-free login page may display a mobile phone number or a mask mobile phone number of the user returned by the application server, and log in the application after the user confirms that the displayed mobile phone number or the mask mobile phone number is correct.
The implementation modes can log in the application without using the service provided by the operator server, thereby avoiding the cost in the login process and saving the cost of the application server in the login process.
In some optional implementations of this embodiment, the mobile phone number information is a masked mobile phone number, where the masked mobile phone number includes a part of numbers in the mobile phone number of the user; acquiring mobile phone number information of a user of an application, comprising the following pre-fetching steps of: the method includes sending a prefetch number request to an operator server and receiving a masked handset number of a user from the operator server.
In these alternative implementations, the execution entity may perform the pre-fetching of the number from the operator server, that is, send a pre-fetching request and receive the feedback of the masked mobile phone number. The masking mobile phone number refers to a result obtained by masking a part of numbers in the mobile phone number. For example, the mask phone number of phone number 1340202105 may be 134×105.
The implementation modes can obtain the mask mobile phone number through the pre-fetching number, so that quick login is realized.
In some optional implementations of this embodiment, the method may further include: in response to the prefetch number step failing to execute or the login application failing to execute the following verification login step: displaying a login page for receiving a mobile phone number, and receiving the input mobile phone number of a user; based on the received handset number, the application is logged in.
In these alternative implementations, the executing body may first perform the password-free login, and after the password-free login is unsuccessful, obtain the input mobile phone number, so as to perform the verification login based on the mobile phone number. In the case where the acquisition of the mobile phone number information fails or the login application fails, the execution body may execute the login step. The step of logging in may include receiving a user-entered cell phone number at a log-in page, where the cell phone number is a cell phone number entered for the user.
The implementation modes can acquire the mobile phone number input by the user under the condition of login failure, so that the login application is ensured.
Optionally, logging in the application based on the received mobile phone number in these implementations may include: and logging in the application based on the received mobile phone number and the corresponding verification code.
In these implementations, the executing body may log in to the application through a verification code logging step. Specifically, the terminal may receive the verification code corresponding to the received mobile phone number, and pass verification and log in the application when the verification code input by the user is consistent with the verification code received by the terminal. The mobile phone number corresponds to the verification code, which means that the verification code is generated by the server aiming at the mobile phone number.
Optionally, logging in the application based on the received mobile phone number in these implementations may include: responding to the failure of the pre-fetching step to obtain second indication information indicating whether the received mobile phone number is matched with the registration information; logging in the application in response to the second indication information indicating a match; and responding to the second indication information to indicate the mismatch, and logging in the application based on the received mobile phone number and the corresponding verification code.
In these implementations, the executing body may acquire, in the case where the execution of the prefetch number step fails, indication information indicating whether the input mobile phone number matches with the registration information of the user, and use the indication information as the second indication information. Specifically, the executing body may acquire the first instruction information by using the application server or acquire the second instruction information locally. If the second indication information indicates that the input mobile phone number is matched with the registration information, the application can be directly logged in. If the second indication information indicates that the verification codes are not matched, the verification codes received by the user at the login page input terminal can be input, or the terminal can display the verification code input page, so that the user can input the verification codes, and login application is realized. The authentication code here may be sent by the application server or by the operator server.
In the implementation manners, the terminal can execute the verification login step under the condition that the password-free login is unsuccessful, so that the login process of injecting the account passwords by the user is not executed, and the problems that the user forgets the passwords to cause the incapability of login, influence on user experience and the like can be avoided.
In some optional implementations of this embodiment, the method may further include: and responding to the first indication information to indicate the mismatch, sending a number-taking request to an operator server, and logging in an application based on the service provided by the operator server.
In these optional implementations, the executing body may send a number taking request to the operator server and receive the feedback information when the first indication information indicates that the mobile phone number information is not matched with the registration information, so that the service provided by the operator server may be used to log in the application through the feedback information, that is, the password-free login page is displayed and the application is logged in. In these implementations, if the acquired mobile phone number information does not match the user identifier, the user may be an unregistered user, and direct login may risk a logged account. Thus, these implementations may log in through a service provided by the carrier server, ensuring account security.
In some optional implementations of this embodiment, the mobile phone number information includes at least part of a mobile phone number of the user, and the registration information includes a user identifier of the user; step 203 may include: sending a matching request comprising registration information and mobile phone number information to an application server of an application, so that the application server determines whether the mobile phone number information is matched with the registration information and generates first indication information for indicating a matching result based on a pre-stored matching relation, wherein the matching relation comprises a matched mobile phone number and a user identifier; first indication information is received from an application server.
In these alternative implementations, the execution entity may send the registration information and the mobile phone number information to the application server, so that the application server performs matching, and generates a matching result. The application server may pre-store information acquired during user registration: user identification generated for the user and a mobile phone number of the terminal input by the user. There is a matching relationship between these pieces of information. For example, the matching relationship may be presented in the form of a matching relationship table. The matched information is correspondingly stored in the matching relation table. The mobile phone number information may include all or part of the mobile phone number of the user. In practice, the login in these implementations may be a password-free login or a verification login.
The application server may determine whether the mobile phone number information matches registration information (e.g., user identification) using the matching relationship. Specifically, the application server may search the mobile phone number completely including the mobile phone number information in the matching relationship, and if the mobile phone number is found, the application server may compare the user identifier in the registration information with the user identifier corresponding to the found mobile phone number in the matching relationship table. If so, a match may be determined. When the user registers the account numbers of the plurality of applications using the same mobile phone number, the execution body determines that only one user identifier is consistent among the user identifiers corresponding to the mobile phone number, and can determine the matching.
In addition, the application server may also search the matching relation table for whether there is registration information, such as a user identifier, sent by the execution body. And then, the application server can compare the mobile phone number corresponding to the searched user identifier in the matching relation table with the mobile phone number information sent by the execution main body in the presence of the user identifier so as to determine whether the mobile phone number completely contains the number of the mobile phone number information. If the determination is complete, the application server may determine a match.
The implementation modes can be used for transmitting the registration information comprising the user identification to the server, so that the server executes a matching process to determine whether the mobile phone number information transmitted by the terminal is matched with the user identification, and the matching speed is improved. In addition, under the condition that a user registers a plurality of accounts by using one mobile phone number, quick login can still be realized.
In some optional application scenarios of these implementations, the matching relationship further includes a matched mobile phone number and a SIM card identifier, and the registration information further includes a SIM card identifier of the terminal; in these implementations, to enable the application server to determine whether the mobile phone number information and the registration information match and generate first indication information indicating a matching result based on a pre-stored matching relationship may include: the application server determines whether the mobile phone number information is matched with the sent user identification based on a pre-stored matching relation, and determines whether the mobile phone number information is matched with the SIM card identification in the registration information under the condition of no match, wherein the matching result is used for representing whether the mobile phone number information is matched with the SIM card identification in the registration information.
In these alternative application scenarios, the matching relationship may also include a matching phone number and SIM (Subscriber Identity Module) card identification. Specifically, the matching relationship may be a matching relationship table corresponding to the current mobile phone number, the user identifier and the SIM card identifier. In addition, the matching relationship may also be two matching relationship tables: a matching relation table of the mobile phone number and the user identifier, and a matching relation table of the mobile phone number and the SIM card identifier.
The application server may determine whether the mobile phone number information is matched with the SIM card identifier in the registration information in case the mobile phone number information is not matched with the transmitted user identifier. And taking the result of whether the mobile phone number information is matched with the SIM card identification in the registration information as a matching result indicated by the first indication information.
Under the condition that the user logs in after using a new mobile phone or uninstalling the application, the application scenes can still realize a quick login process through the SIM card identification.
In some optional implementations of this embodiment, the mobile phone number information includes at least a part of a mobile phone number of the user, and the registration information includes a SIM card identifier of the terminal; step 203 may include: sending a matching request comprising the registration information and the mobile phone number information to an application server of the application, so that the application server determines whether the mobile phone number information is matched with the registration information and generates first indication information for indicating a matching result based on a pre-stored matching relation, wherein the matching relation comprises a matched mobile phone number and a SIM card identifier; the first indication information is received from the application server.
In these alternative implementations, the application server may directly use the SIM card identifier to perform matching, so that in the case where the user logs in after using a new mobile phone or uninstalling the application, the quick login process may still be directly implemented through the SIM card identifier.
In some optional implementations of this embodiment, the mobile phone number information includes at least a portion of a mobile phone number of the user; step 203 may include: determining whether the mobile phone number information is matched with the registration information and generating first indication information for indicating a matching result based on a pre-stored matching relation, wherein the matching relation comprises a matched mobile phone number and a user identification; or, determining whether the mobile phone number information is matched with the registration information and generating first indication information for indicating a matching result based on a pre-stored matching relation in response to the registration information including the SIM card identification of the terminal, wherein the matching relation includes the matched mobile phone number and the SIM card identification.
In these alternative implementations, the execution body may perform matching locally, so that, in the case that the user registers multiple accounts with one mobile phone number, quick login can still be implemented, and time consumption caused by a communication process with the server is avoided.
In some optional implementations of this embodiment, the mobile phone number information is an input mobile phone number of the user; the obtaining mobile phone number information of the user of the application in step 201 may include: displaying a login page for receiving the mobile phone number and receiving the input mobile phone number of the user. Optionally, the method may further include: and responding to the first indication information to indicate that the mobile phone number is not matched, and logging in the application based on the received mobile phone number and the corresponding verification code.
In these alternative implementation manners, the execution body can skip the password-free login process and directly perform verification login, namely, the process of directly logging in the mobile phone number input by the user, so that the quick login manner is enriched.
Optionally, logging in the application based on the received mobile phone number and the corresponding verification code in the above implementations may include: sending a verification code request to an application server, wherein the verification code request comprises a received mobile phone number; receiving a verification code fed back by the application server through an operator server, wherein the fed back verification code is generated by the application server for the received mobile phone number; and in response to receiving the input verification code, logging in the application if the input verification code is consistent with the feedback verification code.
Specifically, the executing body may receive the verification code input by the user in the login page for receiving the mobile phone number, or may display a new verification code receiving page for receiving the verification code input by the user.
The application server may generate a verification code for the received mobile phone number and send the verification code to the operator server, so that the operator server sends the verification code to the terminal, for example, in the form of a short message.
With continued reference to fig. 3, fig. 3 is a schematic diagram of an application scenario of the login method of the application according to the present embodiment. The user may trigger a password-free login using a login operation, or the user may trigger a verification login using a login operation.
With further reference to fig. 4, as an implementation of the method shown in the above figures, the present application provides an embodiment of a login device for an application, where the embodiment of the device corresponds to the embodiment of the method shown in fig. 2, and the embodiment of the device may further include the same or corresponding features or effects as the embodiment of the method shown in fig. 2, except for the features described below. The device can be applied to various electronic equipment.
As shown in fig. 4, the login device 400 of the application of the present embodiment includes: a first acquisition unit 401, a second acquisition unit 402, a third acquisition unit 403, and a login unit 404. Wherein, the first obtaining unit 401 is configured to obtain mobile phone number information of a user of the application in response to detecting a login operation to the application; a second obtaining unit 402, configured to obtain registration information of the user in the application in response to successful obtaining of the mobile phone number information; a third acquisition unit 403 configured to acquire first instruction information indicating whether the mobile phone number information and the registration information match; a login unit 404 configured to login the application in response to the first indication information indicating a match.
In this embodiment, the specific processes and the technical effects of the first obtaining unit 401, the second obtaining unit 402, the third obtaining unit 403 and the login unit 404 of the login device 400 of the application may refer to the relevant descriptions of step 201, step 202, step 203 and step 204 in the corresponding embodiment of fig. 2, and are not repeated here.
In some optional implementations of this embodiment, the mobile phone number information is a masked mobile phone number, where the masked mobile phone number includes a part of numbers in the mobile phone number of the user; the first acquisition unit is further configured to perform acquisition of mobile phone number information of a user of the application as follows: performing a prefetch number step: the method includes sending a prefetch number request to an operator server and receiving a masked handset number of a user from the operator server.
In some optional implementations of this embodiment, the apparatus further includes: an execution unit configured to display a login page for receiving a mobile phone number in response to the prefetch number step failure or the login application failure, and to receive an input mobile phone number of the user; an application login unit configured to login the application based on the received mobile phone number.
In some optional implementations of this embodiment, the application login unit is further configured to perform the logging in of the application based on the received mobile phone number as follows: and logging in the application based on the received mobile phone number and the corresponding verification code.
In some optional implementations of this embodiment, the application login unit is further configured to perform the logging in of the application based on the received mobile phone number as follows: responding to the failure of the pre-fetching step to obtain second indication information indicating whether the received mobile phone number is matched with the registration information; logging in the application in response to the second indication information indicating a match; and responding to the second indication information to indicate the mismatch, and logging in the application based on the received mobile phone number and the corresponding verification code.
In some optional implementations of this embodiment, the mobile phone number information includes at least a portion of the number of the user's mobile phone number; the registration information comprises a user identification of the user; the third acquisition unit is further configured to perform acquisition of first indication information indicating whether the mobile phone number information and the registration information match in the following manner: sending a matching request comprising registration information and mobile phone number information to an application server of an application, so that the application server determines whether the mobile phone number information is matched with the registration information and generates first indication information for indicating a matching result based on a pre-stored matching relation, wherein the matching relation comprises a matched mobile phone number and a user identifier; first indication information is received from an application server.
In some optional implementations of this embodiment, the matching relationship further includes a matched mobile phone number and a SIM card identifier, and the registration information further includes a SIM card identifier of the terminal; the third obtaining unit is further configured to perform the following manner to enable the application server to determine whether the mobile phone number information and the registration information are matched based on a pre-stored matching relationship and generate first indication information indicating a matching result: the application server determines whether the mobile phone number information is matched with the sent user identification based on a pre-stored matching relation, and determines whether the mobile phone number information is matched with the SIM card identification in the registration information under the condition of no match, wherein the matching result is used for representing whether the mobile phone number information is matched with the SIM card identification in the registration information.
In some optional implementations of this embodiment, the mobile phone number information includes at least a part of a mobile phone number of the user, and the registration information includes a SIM card identifier of the terminal; the third obtaining unit is further configured to perform the obtaining of the first indication information indicating whether the mobile phone number information and the registration information match in the following manner: sending a matching request comprising the registration information and the mobile phone number information to an application server of the application, so that the application server determines whether the mobile phone number information is matched with the registration information and generates first indication information for indicating a matching result based on a pre-stored matching relation, wherein the matching relation comprises a matched mobile phone number and a SIM card identifier; the first indication information is received from the application server.
In some optional implementations of this embodiment, the mobile phone number information is an input mobile phone number of the user; the first acquisition unit is further configured to perform acquisition of mobile phone number information of a user of the application as follows: displaying a login page for receiving the mobile phone number and receiving the input mobile phone number of the user.
In some optional implementations of this embodiment, the foregoing apparatus may further include: and the verification unit is configured to respond to the first indication information to indicate that the mobile phone number is not matched, and log in the application based on the received mobile phone number and the corresponding verification code.
In some optional implementations of this embodiment, the apparatus further includes: and the verification login unit is configured to respond to the fact that the first indication information indicates that the first indication information is not matched, send a number-taking request to an operator server and login the application based on the service provided by the operator server.
In some optional implementations of this embodiment, logging in the application based on the received mobile phone number and the corresponding authentication code, where any of the devices is configured to perform, may include: sending a verification code request to an application server, wherein the verification code request comprises a received mobile phone number; receiving a verification code fed back by the application server through an operator server, wherein the fed back verification code is generated by the application server for the received mobile phone number; and in response to receiving the input verification code, logging in the application if the input verification code is consistent with the feedback verification code.
According to an embodiment of the present application, the present application also provides an electronic device and a readable storage medium.
As shown in fig. 5, a block diagram of an electronic device of a login method of an application according to an embodiment of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the applications described and/or claimed herein.
As shown in fig. 5, the electronic device includes: one or more processors 501, memory 502, and interfaces for connecting components, including high-speed interfaces and low-speed interfaces. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions executing within the electronic device, including instructions stored in or on memory to display graphical information of the GUI on an external input/output device, such as a display device coupled to the interface. In other embodiments, multiple processors and/or multiple buses may be used, if desired, along with multiple memories and multiple memories. Also, multiple electronic devices may be connected, each providing a portion of the necessary operations (e.g., as a server array, a set of blade servers, or a multiprocessor system). One processor 501 is illustrated in fig. 5.
Memory 502 is a non-transitory computer readable storage medium provided by the present application. The memory stores instructions executable by the at least one processor to cause the at least one processor to perform the login method of the application provided by the application. The non-transitory computer readable storage medium of the present application stores computer instructions for causing a computer to execute the login method of the application provided by the present application.
The memory 502 is a non-transitory computer readable storage medium, and may be used to store a non-transitory software program, a non-transitory computer executable program, and modules, such as program instructions/modules corresponding to the login method of the application in the embodiment of the present application (for example, the first obtaining unit 401, the second obtaining unit 402, the third obtaining unit 403, and the login unit 404 shown in fig. 4). The processor 501 executes various functional applications of the server and data processing, i.e., implements the login method of the application in the above-described method embodiment, by running non-transitory software programs, instructions, and modules stored in the memory 502.
Memory 502 may include a storage program area that may store an operating system, at least one application program required for functionality, and a storage data area; the storage data area may store data created according to the use of the logged-in electronic device of the application, etc. In addition, memory 502 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory 502 may optionally include memory located remotely from processor 501, which may be connected to the application's login electronics via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The electronic device of the login method of the application may further include: an input device 503 and an output device 504. The processor 501, memory 502, input devices 503 and output devices 504 may be connected by a bus or otherwise, for example in fig. 5.
The input device 503 may receive entered numeric or character information and generate key signal inputs related to user settings and function control of the logged-in electronic device of the application, such as a touch screen, keypad, mouse, trackpad, touchpad, pointer stick, one or more mouse buttons, trackball, joystick, and like input devices. The output devices 504 may include a display device, auxiliary lighting devices (e.g., LEDs), and haptic feedback devices (e.g., vibration motors), among others. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device may be a touch screen.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASIC (application specific integrated circuit), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
These computing programs (also referred to as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.
The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present application may be implemented in software or in hardware. The described units may also be provided in a processor, for example, described as: a processor includes a first acquisition unit, a second acquisition unit, a third acquisition unit, and a login unit. Wherein the names of the units do not constitute a limitation of the unit itself in some cases, for example, the login unit may also be described as "a unit that logs in an application in response to the first indication information indicating a match".
As another aspect, the present application also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to: responding to the detection of login operation of the application, and acquiring mobile phone number information of a user of the application; responding to successful acquisition of the mobile phone number information, and acquiring registration information of a user in an application; acquiring first indication information indicating whether the mobile phone number information is matched with registration information or not; in response to the first indication information indicating a match, the application is logged in.
The above description is only illustrative of the preferred embodiments of the present application and of the principles of the technology employed. It will be appreciated by persons skilled in the art that the scope of the application referred to in the present application is not limited to the specific combinations of the technical features described above, but also covers other technical features formed by any combination of the technical features described above or their equivalents without departing from the inventive concept described above. Such as the above-mentioned features and the technical features disclosed in the present application (but not limited to) having similar functions are replaced with each other.
Claims (13)
1. A method of logging in an application, the method comprising:
in response to detecting a login operation to an application, acquiring mobile phone number information of a user of the application, including the following pre-fetching number steps: sending a pre-fetching number request to an operator server, and receiving a mask mobile phone number of the user from the operator server;
responding to successful acquisition of the mobile phone number information, and acquiring registration information of the user in the application;
acquiring first indication information indicating whether the mobile phone number information is matched with the registration information;
in response to the first indication indicating a match, logging in the application, comprising: displaying a preset password-free login page, and logging in an application by using a local application login inlet, wherein the application login inlet is an inlet provided by a non-operator server;
Responding to the first indication information to indicate that the first indication information is not matched, sending a number-taking request to an operator server, and logging in the application based on a service provided by the operator server;
responding to the failure of the pre-fetching step or the failure of logging in the application, displaying a login page for receiving a mobile phone number, and receiving an input mobile phone number of the user;
based on the received handset number, the application is logged in.
2. The method of claim 1, wherein the phone number information is a masked phone number that includes a partial number in the user's phone number.
3. The method of claim 1, wherein the logging in the application based on the received handset number comprises:
and logging in the application based on the received mobile phone number and the corresponding verification code.
4. The method of claim 1, wherein the logging in the application based on the received handset number comprises:
responding to the failure of the pre-fetching step to obtain second indication information indicating whether the received mobile phone number is matched with the registration information;
logging in the application in response to the second indication information indicating a match;
And responding to the second indication information to indicate the mismatch, and logging in the application based on the received mobile phone number and the corresponding verification code.
5. The method of claim 1, wherein the mobile phone number information is an entered mobile phone number of the user;
the obtaining the mobile phone number information of the user of the application comprises the following steps:
displaying a login page for receiving the mobile phone number and receiving the input mobile phone number of the user.
6. The method of claim 5, wherein the method further comprises:
and responding to the first indication information to indicate that the mobile phone number is not matched, and logging in the application based on the received mobile phone number and the corresponding verification code.
7. The method of one of claims 3, 4, 6, wherein the logging in the application based on the received handset number and corresponding authentication code comprises:
sending a verification code request to an application server, wherein the verification code request comprises a received mobile phone number;
receiving a verification code fed back by the application server through an operator server, wherein the fed back verification code is generated by the application server for the received mobile phone number;
and in response to receiving the input verification code, logging in the application if the input verification code is consistent with the feedback verification code.
8. The method according to one of claims 1-5, wherein the phone number information comprises at least part of the phone number of the user, and the registration information comprises a user identification of the user;
the obtaining the first indication information indicating whether the mobile phone number information is matched with the registration information includes:
sending a matching request comprising the registration information and the mobile phone number information to an application server of the application, so that the application server determines whether the mobile phone number information is matched with the registration information and generates first indication information for indicating a matching result based on a pre-stored matching relation, wherein the matching relation comprises a matched mobile phone number and a user identifier;
the first indication information is received from the application server.
9. The method of claim 8, wherein the matching relationship further comprises a matched mobile phone number and a SIM card identification, and the registration information further comprises a SIM card identification of the terminal;
the determining, by the application server, whether the mobile phone number information matches the registration information based on a pre-stored matching relationship and generating first indication information indicating a matching result includes:
And the application server determines whether the mobile phone number information is matched with the sent user identifier or not based on a pre-stored matching relation, and determines whether the mobile phone number information is matched with the SIM card identifier in the registration information or not under the condition of no match, wherein the matching result is used for representing whether the mobile phone number information is matched with the SIM card identifier in the registration information or not.
10. The method according to one of claims 1 to 5, wherein the handset number information comprises at least part of the handset number of the user, the registration information comprising a SIM card identification of the terminal;
the obtaining the first indication information indicating whether the mobile phone number information is matched with the registration information includes:
sending a matching request comprising the registration information and the mobile phone number information to an application server of the application, so that the application server determines whether the mobile phone number information is matched with the registration information and generates first indication information for indicating a matching result based on a pre-stored matching relation, wherein the matching relation comprises a matched mobile phone number and a SIM card identifier;
the first indication information is received from the application server.
11. The method according to one of claims 1-5, wherein the cell phone number information comprises at least part of the cell phone number of the user;
the obtaining the first indication information indicating whether the mobile phone number information is matched with the registration information includes:
determining whether the mobile phone number information is matched with the registration information and generating first indication information for indicating a matching result based on a pre-stored matching relation, wherein the matching relation comprises a matched mobile phone number and a user identification;
or (b)
And responding to the registration information including the SIM card identification of the terminal, and determining whether the mobile phone number information is matched with the registration information based on a pre-stored matching relation and generating first indication information for indicating a matching result, wherein the matching relation includes the matched mobile phone number and the SIM card identification.
12. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs,
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-11.
13. A computer readable storage medium having stored thereon a computer program, wherein the program when executed by a processor implements the method of any of claims 1-11.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010564127.1A CN111666546B (en) | 2020-06-19 | 2020-06-19 | Application login method and device |
| PCT/CN2021/094505 WO2021254075A1 (en) | 2020-06-19 | 2021-05-19 | Application login method and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010564127.1A CN111666546B (en) | 2020-06-19 | 2020-06-19 | Application login method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111666546A CN111666546A (en) | 2020-09-15 |
| CN111666546B true CN111666546B (en) | 2023-10-13 |
Family
ID=72388911
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010564127.1A Active CN111666546B (en) | 2020-06-19 | 2020-06-19 | Application login method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN111666546B (en) |
| WO (1) | WO2021254075A1 (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111666546B (en) * | 2020-06-19 | 2023-10-13 | 上海连尚网络科技有限公司 | Application login method and device |
| CN112612922A (en) * | 2020-12-16 | 2021-04-06 | 平安普惠企业管理有限公司 | Method and device for safely storing mobile phone number, computer equipment and medium |
| CN113157375A (en) * | 2021-04-27 | 2021-07-23 | 北京达佳互联信息技术有限公司 | Content display method, device, equipment, system and storage medium |
| CN114727276A (en) * | 2021-09-03 | 2022-07-08 | 王恩惠 | Method and system for determining account information in user non-login state |
| CN114338132B (en) * | 2021-12-24 | 2023-08-01 | 中国联合网络通信集团有限公司 | Secret-free login method, client application, operator server and electronic equipment |
| CN113993127B (en) * | 2021-12-28 | 2022-05-06 | 支付宝(杭州)信息技术有限公司 | Method and device for realizing one-key login service |
| CN114466353A (en) * | 2022-02-09 | 2022-05-10 | 号百信息服务有限公司 | App user ID information protection device and method, electronic equipment and storage medium |
| CN114666116B (en) * | 2022-03-16 | 2024-05-10 | 深圳金蝶账无忧网络科技有限公司 | Authentication processing method, device, equipment and storage medium based on applet |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2004343500A (en) * | 2003-05-16 | 2004-12-02 | Nippon Telegr & Teleph Corp <Ntt> | Method and system for registering radio communication service |
| WO2012116543A1 (en) * | 2011-03-02 | 2012-09-07 | 中兴通讯股份有限公司 | Method and system for logging in online bank through mobile phone, and bank server |
| CN103259795A (en) * | 2013-05-14 | 2013-08-21 | 百度在线网络技术（北京）有限公司 | Method for executing automatic register and login, mobile terminal and server |
| WO2017152820A1 (en) * | 2016-03-11 | 2017-09-14 | 腾讯科技（深圳）有限公司 | Client login method and device, and storage medium |
| CN109241722A (en) * | 2018-09-25 | 2019-01-18 | 上海盛付通电子支付服务有限公司 | For obtaining method, electronic equipment and the computer-readable medium of information |
| CN110149629A (en) * | 2019-05-22 | 2019-08-20 | 中国联合网络通信集团有限公司 | A kind of method and system of fast registration and login application program based on mobile phone |
| CN110414208A (en) * | 2019-07-25 | 2019-11-05 | 中国工商银行股份有限公司 | Login validation method, calculates equipment and medium at device |
| CN110730446A (en) * | 2018-07-16 | 2020-01-24 | 中移信息技术有限公司 | Login method, terminal and computer storage medium |
| WO2020093214A1 (en) * | 2018-11-05 | 2020-05-14 | 深圳市欢太科技有限公司 | Application program login method, application program login device and mobile terminal |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9479499B2 (en) * | 2013-03-21 | 2016-10-25 | Tencent Technology (Shenzhen) Company Limited | Method and apparatus for identity authentication via mobile capturing code |
| US9888380B2 (en) * | 2014-10-30 | 2018-02-06 | The Western Union Company | Methods and systems for validating mobile devices of customers via third parties |
| CN106203021B (en) * | 2016-07-26 | 2018-05-29 | 中卓信（北京）科技有限公司 | A kind of more certification modes are integrated to apply login method and system |
| US10853789B2 (en) * | 2017-07-07 | 2020-12-01 | Bank Of America Corporation | Dynamic digital consent |
| CN111666546B (en) * | 2020-06-19 | 2023-10-13 | 上海连尚网络科技有限公司 | Application login method and device |
-
2020
- 2020-06-19 CN CN202010564127.1A patent/CN111666546B/en active Active
-
2021
- 2021-05-19 WO PCT/CN2021/094505 patent/WO2021254075A1/en active Application Filing
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2004343500A (en) * | 2003-05-16 | 2004-12-02 | Nippon Telegr & Teleph Corp <Ntt> | Method and system for registering radio communication service |
| WO2012116543A1 (en) * | 2011-03-02 | 2012-09-07 | 中兴通讯股份有限公司 | Method and system for logging in online bank through mobile phone, and bank server |
| CN103259795A (en) * | 2013-05-14 | 2013-08-21 | 百度在线网络技术（北京）有限公司 | Method for executing automatic register and login, mobile terminal and server |
| WO2017152820A1 (en) * | 2016-03-11 | 2017-09-14 | 腾讯科技（深圳）有限公司 | Client login method and device, and storage medium |
| CN110730446A (en) * | 2018-07-16 | 2020-01-24 | 中移信息技术有限公司 | Login method, terminal and computer storage medium |
| CN109241722A (en) * | 2018-09-25 | 2019-01-18 | 上海盛付通电子支付服务有限公司 | For obtaining method, electronic equipment and the computer-readable medium of information |
| WO2020093214A1 (en) * | 2018-11-05 | 2020-05-14 | 深圳市欢太科技有限公司 | Application program login method, application program login device and mobile terminal |
| CN110149629A (en) * | 2019-05-22 | 2019-08-20 | 中国联合网络通信集团有限公司 | A kind of method and system of fast registration and login application program based on mobile phone |
| CN110414208A (en) * | 2019-07-25 | 2019-11-05 | 中国工商银行股份有限公司 | Login validation method, calculates equipment and medium at device |
Non-Patent Citations (4)
| Title |
|---|
| Android手机安全登录系统;王振辉;王振铎;;计算机系统应用(02);全文 * |
| 刘文印 ; 吴鸿文 ; 李昕 ; 凡帅 ; 张启翔 ; 巫家宏 ; 沈治恒 ; .登录易,一种基于可信用户代理的多方闭环网络身份认证及管理机制.信息安全研究.2018,(07),全文. * |
| 基于标识符的Android客户端身份认证方案;王亚伟;彭长根;丁红发;周凯;;网络与信息安全学报(04);全文 * |
| 手机支付客户端安全登录及防盗用的研究与实现;孟佳伟;;福建电脑(04);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111666546A (en) | 2020-09-15 |
| WO2021254075A1 (en) | 2021-12-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111666546B (en) | Application login method and device | |
| US20220115012A1 (en) | Method and apparatus for processing voices, device and computer storage medium | |
| CN111586128B (en) | Method, device, equipment and storage medium for acquiring applet data | |
| CN111932246A (en) | Method and apparatus for transmitting information | |
| CN111913707B (en) | Multiplexing method and device for running process | |
| US11990130B2 (en) | Method, apparatus, device and computer storage medium for processing voices | |
| CN115222176A (en) | Risk control method, apparatus, device and medium | |
| CN112307357A (en) | Social method and device for strangers | |
| CN111669744A (en) | Information processing method and device and electronic equipment | |
| CN113778590B (en) | Remote assistance method, device, electronic equipment and medium | |
| CN112565225B (en) | Method and device for data transmission, electronic equipment and readable storage medium | |
| CN111615171B (en) | Access method and device of wireless local area network | |
| CN111522599B (en) | Method and device for transmitting information | |
| WO2023169193A1 (en) | Method and device for generating smart contract | |
| CN111988829B (en) | Access method and device of wireless local area network | |
| CN115600213A (en) | Vulnerability management method, device, medium and equipment based on application program | |
| US20230121470A1 (en) | Preventing phishing attempts of one-time passwords | |
| CN110262813B (en) | Method and apparatus for installing applications | |
| CN112489659B (en) | Data processing method, system, server and terminal equipment based on input method | |
| CN111506499B (en) | Method and device for detecting availability of parameters in applet and electronic equipment | |
| CN112785312A (en) | Information sharing method and device, electronic equipment and readable storage medium | |
| CN112770415A (en) | Information processing method and device about wireless hotspot | |
| CN112118576A (en) | Method and apparatus for networking over wireless hotspots | |
| CN111651229A (en) | Font changing method, device and equipment | |
| CN111177558A (en) | Channel service construction 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |