CN114584971A - Account registration method and device, electronic equipment and storage medium - Google Patents
Account registration method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114584971A CN114584971A CN202210138620.6A CN202210138620A CN114584971A CN 114584971 A CN114584971 A CN 114584971A CN 202210138620 A CN202210138620 A CN 202210138620A CN 114584971 A CN114584971 A CN 114584971A
- Authority
- CN
- China
- Prior art keywords
- terminal
- communication identifier
- server
- communication
- identifier
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 80
- 238000004891 communication Methods 0.000 claims abstract description 325
- 238000012795 verification Methods 0.000 claims description 19
- 230000002452 interceptive effect Effects 0.000 abstract description 5
- 238000012545 processing Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 6
- 230000003993 interaction Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000630 rising effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000001356 surgical procedure Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/03—Protecting confidentiality, e.g. by encryption
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/40—Security arrangements using identity modules
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
Abstract
The embodiment of the disclosure provides an account registration method and device, an electronic device and a storage medium, wherein the account registration method comprises the following steps: receiving a communication identifier through a User Interface (UI); based on a long connection channel established between the terminal and the server, the communication identifier is sent to the server; receiving a login key returned when the server determines that the communication identifier is not a registered communication identifier on the basis of the long connection channel; and saving the login key, wherein the saved login key and the communication identifier are used for logging in the server. Therefore, the login key sent by the server is received through the long connecting channel, the expense caused by sending the login key by calling a short message interface is not needed, meanwhile, the interactive information between the terminal and the server can be fed back in time, and the efficiency in the account registration process is ensured.
Description
Technical Field
The present disclosure relates to the field of network technologies, and in particular, to an account registration method, an electronic device, and a computer-readable storage medium.
Background
With the development of science and technology and the increasing diversification of people's requirements, various application programs are gradually rising, and most software products need users to register before being used.
The method adopted at present mainly comprises the following steps: by using the mode of mobile phone number and short message registration, the account registration can be completed after receiving the correct input verification code by sending the short message verification code to the input registered mobile phone number. However, in the existing technical solution, a short message interface needs to be called to send a verification short message, which inevitably increases the cost of the short message, and at the same time, the problem of poor efficiency in the user registration process caused by the untimely reception of the short message exists.
Disclosure of Invention
The embodiment of the disclosure provides an account registration method and device, electronic equipment and a storage medium.
In a first aspect, the present application provides an account registration method, which may be applied to a terminal, where the method may include:
receiving a communication identifier through a User Interface (UI);
based on a long connection channel established between the terminal and the server, sending the communication identifier to the server;
receiving a login key returned when the server determines that the communication identifier is not the registered communication identifier based on the long connection channel;
and saving the login key, wherein the saved login key and the communication identifier are used for logging in the server.
In some possible embodiments, receiving, through the user interface UI, the communication identification includes:
receiving the communication identification at least twice through the UI, wherein the communication identification received twice through the UI is used for mutually verifying that the communication identification received by the UI has no input error;
receiving a login key returned when the server determines that the communication identifier is not the registered communication identifier based on the long connection channel, wherein the login key comprises the following steps:
and receiving a login key returned when the server determines that the communication identification without input error is not the registered communication identification based on the long connection channel.
In some possible embodiments, the sending the communication identifier to the server based on establishing a long connection channel between the terminal and the server includes:
based on a long connecting channel established between the terminal and the server, when a communication identifier is received from the UI for one time, the communication identifier and the terminal identifier of the terminal are sent to the server; the terminal identification is used for the server to determine whether the communication identification sent by the terminal twice continuously has no input error.
In some possible embodiments, the sending the communication identifier to the server based on establishing a long connection channel between the terminal and the server includes:
verifying whether the communication identifiers received from the UI twice consecutively are the same;
when the communication identifiers received from the UI twice consecutively are the same, it is determined that the communication identifiers have no input error.
In some possible embodiments, when the communication identifiers received from the UI twice consecutively are different, prompt information is output at the UI, wherein the prompt information is used for prompting that the communication identifiers are input incorrectly.
In some possible embodiments, after the application program is started, whether the terminal has a registration requirement is determined;
when the terminal has a registration requirement, a long connection channel is established.
In some possible embodiments, after the application program is started, determining whether the terminal has a registration requirement includes:
when the application program is started for the first time, determining that the terminal has a registration requirement;
alternatively, the first and second electrodes may be,
and when the communication identifier and the login key are not correspondingly stored in the catalog of the application program, determining that the terminal has the registration requirement.
In some possible embodiments, when the terminal has a registration requirement, a UI receiving the communication identifier is displayed.
In a second aspect, the present application provides an account registration method, which may be applied to a server, and the method includes:
based on a long connection channel established between the server and the terminal, receiving a communication identifier sent by the terminal;
when the communication identifier is determined not to be the registered communication identifier, generating a login key corresponding to the communication identifier;
based on the long connection channel, sending the login key to the terminal; the login identification and the communication identification are used for an application program running in the terminal to log in the server.
In some possible embodiments, when it is determined that the communication identifier is not the registered communication identifier, generating a login key corresponding to the communication identifier includes:
and when the communication identifier without input error is determined not to be the registered communication identifier, generating a login key corresponding to the communication identifier.
In some possible embodiments, the receiving, based on establishing a long connection channel between the server and the terminal, a communication identifier sent by the terminal includes:
based on a long connecting channel established between the server and the terminal, receiving a communication identifier and a terminal identifier which are continuously sent by the terminal twice;
verifying whether the communication identifiers sent by the same terminal twice are the same or not based on the terminal identifier;
if the communication identifiers sent by the same terminal in two adjacent times are the same, it can be determined that the communication identifier received by the terminal UI has no input error.
In some possible embodiments, after sending the login key to the terminal based on the long connection channel, the method further includes:
the server closes the long connection path.
In a third aspect, the present application provides an account registration apparatus, which may be applied to a terminal and includes several functional units for implementing any one of the methods of the first aspect. The account registration apparatus may include:
the UI module is used for receiving the communication identification through a User Interface (UI);
the first sending module is used for establishing a long connecting channel between the terminal and the server and sending the communication identifier to the server;
the first receiving module is used for receiving a login key returned when the server determines that the communication identifier is not the registered communication identifier on the basis of the long connection channel;
and the storage module is used for storing the login key, wherein the stored login key and the communication identifier are used for logging in the server.
In some possible embodiments, the UI module is configured to receive the communication identifier at least twice through the UI, where the communication identifiers received twice adjacent through the UI are configured to mutually verify that the communication identifiers received by the UI have no input error;
the first receiving module is specifically configured to receive, based on the long connection channel, a login key returned when the server determines that the communication identifier without the input error is not the registered communication identifier.
In some possible embodiments, the first sending module is configured to send, when receiving a communication identifier from the UI for one time, the communication identifier and a terminal identifier of the terminal to the server based on a long connection channel established between the terminal and the server; the terminal identification is used for the server to determine whether the communication identification sent by the terminal twice continuously has no input error.
In some possible embodiments, the image processing apparatus further includes:
the first verification module is used for verifying whether the communication identifiers received from the UI twice continuously are the same;
and the determining module is used for determining that the communication identification has no input error when the communication identification received from the UI twice continuously is the same.
In some possible embodiments, the image processing apparatus further includes:
and the prompt information output module is used for outputting prompt information at the UI when the communication identifiers received from the UI twice continuously are different, wherein the prompt information is used for prompting that the communication identifiers are input wrongly.
In some possible embodiments, the image processing apparatus further includes:
the registration requirement determining module is used for determining whether the terminal has a registration requirement after the application program is started; when the terminal has a registration requirement, a long connection channel is established.
In some possible embodiments, the registration requirement determining module is configured to: when the application program is started for the first time, determining that the terminal has a registration requirement; or when the communication identifier and the login key are not correspondingly stored in the catalog of the application program, determining that the terminal has the registration requirement.
In some possible embodiments, the registration requirement determining module is configured to: when the terminal has a registration requirement, a UI for receiving a communication identifier is displayed.
In a fourth aspect, the present application provides an account registration apparatus, which may be applied to a server and includes several functional units for implementing any one of the methods of the second aspect. The account registration apparatus may include: the system comprises a communication identifier receiving module, a first generating module and a login key sending module;
the communication identifier receiving module is used for establishing a long connecting channel between the server and the terminal and receiving the communication identifier sent by the terminal;
the first generation module is used for generating a login key corresponding to the communication identifier when the communication identifier is determined not to be the registered communication identifier;
the login key sending module is used for sending the login key to the terminal based on the long connection channel; the login identification and the communication identification are used for an application program running in the terminal to log in the server.
In some possible embodiments, the first generating module is configured to generate a login key corresponding to the communication identifier when it is determined that the communication identifier without the input error is not the registered communication identifier.
In some possible embodiments, the account registration apparatus may further include: a second authentication module;
the communication identifier receiving module is used for establishing a long connecting channel between the server and the terminal and receiving the communication identifier and the terminal identifier which are continuously sent by the terminal twice; the second verification module is used for verifying whether the communication identifiers sent by the same terminal twice are the same or not based on the terminal identifier; if the communication identifiers sent by the same terminal in two adjacent times are the same, it can be determined that the communication identifier received by the terminal UI has no input error.
In some possible embodiments, the account registration apparatus may further include: and the resource release module is used for closing the long connecting channel by the server after the login key is sent to the terminal based on the long connecting channel.
In a fifth aspect, the present application further provides an electronic device, including:
a memory for storing processor-executable instructions;
a processor; wherein the processor is configured to: for executing executable instructions to implement the method as described in the first aspect and possible embodiments thereof.
In a sixth aspect, the present application provides a computer-readable storage medium storing an executable program, wherein the executable program, when executed by a processor, implements the method according to the first aspect and possible embodiments thereof.
Compared with the prior art, the technical scheme provided by the embodiment of the application has the beneficial effects that:
in the application, a terminal receives a communication identifier through a user interface UI, the communication identifier is sent to a server based on a long connecting channel established between the terminal and the server, a corresponding login key is received through the long connecting channel when the communication identifier returned by the server is not a registered communication identifier, and the login key is stored, wherein the stored login key and the stored communication identifier are used for logging in the corresponding server. Therefore, the login key sent by the server is received through the long connecting channel, the expense caused by sending the login key by additionally calling a short message interface is not needed, meanwhile, the interactive information between the terminal and the server can be fed back in time, and the efficiency in the account registration process is ensured.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
Fig. 1 is a flowchart illustrating an embodiment of an account registration method in the embodiment of the present application.
Fig. 2 is a flowchart illustrating another account registration method in the embodiment of the present application.
Fig. 3 is a flowchart illustrating another account registration method in this embodiment of the application.
Fig. 4 is a flowchart illustrating another account registration method in this embodiment of the application.
Fig. 5 is a schematic structural diagram of an account registration apparatus in this embodiment of the present application.
Fig. 6 is a schematic structural diagram of another account registration apparatus in this embodiment.
Fig. 7 is a schematic structural diagram of an electronic device in an embodiment of the present application.
Detailed Description
In the following description, reference is made to the accompanying drawings which form a part hereof and in which is shown by way of illustration specific aspects of embodiments of the present application or in which specific aspects of embodiments of the present application may be employed. It should be understood that embodiments of the present application may be used in other ways and may include structural or logical changes not depicted in the drawings. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present application is defined by the appended claims. For example, it should be understood that the disclosure in connection with the described methods may equally apply to the corresponding apparatus or device for performing the methods, and vice versa. For example, if one or more particular method steps are described, the corresponding apparatus may comprise one or more units, such as functional units, to perform the described one or more method steps (e.g., a unit performs one or more steps, or multiple units, each of which performs one or more of the multiple steps), even if such one or more units are not explicitly described or illustrated in the figures. On the other hand, for example, if a particular apparatus is described based on one or more units, such as functional units, the corresponding method may comprise one step to perform the functionality of the one or more units (e.g., one step performs the functionality of the one or more units, or multiple steps, each of which performs the functionality of one or more of the plurality of units), even if such one or more steps are not explicitly described or illustrated in the figures. Further, it is to be understood that features of the various exemplary embodiments and/or aspects described herein may be combined with each other, unless explicitly stated otherwise.
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a flowchart illustrating an embodiment of an account registration method in the embodiment of the present application, and is applied to a terminal. The terminal may also be referred to as a terminal device, and may be a mobile terminal, a fixed terminal or a portable terminal, and the terminal device may be a mobile phone (mobile phone), a smart tv, a wearable device, a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self-driving (self-driving), a wireless terminal in remote surgery (remote management), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), or the like.
Referring to fig. 1, the account registration method may include:
s101, receiving a communication identifier through a User Interface (UI);
s102, a long connection channel is established between the terminal and the server, and the communication identifier is sent to the server;
s103, receiving a login key returned when the server determines that the communication identifier is not the registered communication identifier based on the long connection channel;
s104, the login key is saved.
The stored login key and the communication identifier are used for logging in the server.
The communication identifier is: the communication identification with uniqueness is used for distinguishing each user; the communication identifier may be a user-defined identifier, a mailbox address, an identity document number of the user, including but not limited to an identification with uniqueness such as an identification number, a passport number and the like, or a mobile phone number, such as an identification with uniqueness. In the embodiment of the application, the communication identifier may be a communication identifier input by a user through a UI interface, and the server directly performs a registration operation after receiving the communication identifier.
The User Interface (User Interface) is called UI for short, and is a medium for interaction and information exchange between a system and a User, and the conversion between the internal form of information and a human acceptable form is realized. The user interface is designed to interact and communicate with the hardware between the user and the hardware, and aims to enable the user to conveniently and efficiently operate the hardware to achieve bidirectional interaction and complete the work which is expected to be completed by the hardware, and the user interface comprises a man-machine interaction interface and a graphical user interface. In this embodiment of the application, the UI may be a front-end interface of the various types of terminals, for example, when the terminal is a mobile phone, the UI may be a display interface of an application program in the mobile phone.
In this embodiment, before the account registration, the terminal may establish a long connection channel with the server in advance.
It should be understood that a long connection means that multiple packets may be sent continuously over a connection, and that during connection maintenance, if no packets are sent, a bi-directional link check packet is required. Correspondingly, the short connection means that a connection is established when both communication parties have data interaction, and the connection is disconnected after the data transmission is completed, namely, only one service is transmitted after each connection. Thus, long connections are often used for frequent, point-to-point communications. Each TCP connection requires a three-way handshake, which takes time, and if three handshakes are performed for each communication, the processing speed is greatly reduced. Therefore, in the embodiment of the application, the long connection is used, the connection is not disconnected after data interaction every time, the data can be directly sent in the next processing, and the data receiving and sending efficiency can be greatly improved.
Optionally, the establishing of the long connection channel may be developed according to a practical application requirement. Of course, existing long link technologies such as WebSocket, push-push, and the like may also be used, and this is not specifically limited in this embodiment of the present application.
In view of this, in this embodiment of the application, as shown in fig. 2, before S101, the account registration method may further include:
s201, after an application program is started, determining whether the terminal has a registration requirement;
s202, when the terminal has the registration requirement, the long connection channel is established.
After the application program is started every time, the terminal firstly judges whether the terminal has a registration requirement, and when the terminal has the registration requirement, a long connecting channel is immediately established between the terminal and the server, so that the waiting time for establishing the long connecting channel between the terminal and the server when the terminal has the registration requirement is reduced, and the account registration efficiency can be obviously improved.
In one embodiment, the terminal determines whether the terminal has a registration requirement by detecting whether the application is started for the first time.
For example, when the terminal detects that the application program is installed for the first time, the application program is determined to be started for the first time; or, the application in the terminal is the reinstalled application, or the application may be considered to be started for the first time, and at this time, it is determined that the terminal has the registration requirement.
In another embodiment, the terminal may determine whether the terminal has a registration requirement by determining whether the communication identifier and the login key are stored under the directory of the application program.
Illustratively, after the application program is started, the terminal traverses that the communication identifier and the corresponding login key are not stored in the root directory of the application program at the same time, and then the terminal is determined to have the registration requirement; or, when the terminal traverses to the position under the application program and the directory, only the communication identifier is stored, and the login key corresponding to the communication identifier is not available, the terminal is determined to have the registration requirement.
In one embodiment, when the terminal is not detected to have the registration requirement, the terminal displays a UI for selecting whether account registration is performed or not.
For example, the UI interface of the application program may display a UI for selecting whether to perform an account registration interface, and when it is not detected that the terminal has a registration requirement, the user clicks the account registration interface, a long connection channel is established between the terminal and the server, and the application program displays a UI for receiving a communication identifier.
In another embodiment, the method further comprises: when it is determined that the terminal has a registration requirement, the terminal displays a UI for receiving a communication identifier. Specifically, when it is determined that the terminal has a registration requirement, the terminal immediately establishes a long connection channel with the server, and an application program in the terminal displays a UI for receiving a communication identifier to a user.
The communication identifier may be a communication identifier manually input by a user through a UI interface, and in an embodiment, referring to fig. 3, the account registration method may further include:
s301, receiving a communication identifier at least twice through a UI;
s302, based on the long connection channel, receiving a login key returned when the server determines that the communication identifier without input error is not the registered communication identifier.
And the communication identifications received twice through the UI are used for mutually verifying that the communication identifications received by the UI have no input error.
In the embodiment of the application, the communication identifier can be manually input by a user, the terminal receives the communication identifier at least twice, whether the communication identifier received by the terminal is input incorrectly is verified, the correctness of the registration information in the registration process of the user account is ensured, and the safety of the account is improved.
In an embodiment, the terminal receives the communication identifier at least twice through the UI, and may display n communication identifier input interfaces on a UI interface for receiving the communication identifier, where n is a preset value and is greater than or equal to 2. And receiving the communication identification to be registered, which is input on each communication identification input interface by a user.
In another embodiment, the terminal receives the communication identifier at least twice through the UI, or alternatively, only one communication identifier input interface is displayed on the UI interface for receiving the communication identifier, and the terminal resets the data already input in the UI communication identifier input interface once each time the terminal receives the communication identifier. Repeating the resetting process for n times, wherein n is a preset number of times and the value of n is more than or equal to 2.
In an embodiment, the method further comprises:
and based on a long connecting channel established between the terminal and the server, when a communication identifier is received from the UI, the communication identifier and the terminal identifier of the terminal are sent to the server.
The terminal identification is used for the server to determine whether the communication identification sent by the terminal twice continuously has no input error.
For example, the terminal sends the communication identifier and the terminal identifier of the terminal to the server every time the terminal receives the communication identifier through the long connection channel, and after the server receives the communication identifier and the terminal identifier for the preset times, the server determines that the communication identifier has no input error when judging that the communication identifiers sent from the same terminal identifier every time are the same.
The terminal identifier may be unique identification information for identifying the terminal, including but not limited to Mac address information and other information with a unique identifier.
Preferably, the method may further comprise:
verifying whether the communication identifications continuously received from the UI are the same;
when the communication identifiers continuously received from the UI are the same, it is determined that the communication identifiers have no input error.
Specifically, the terminal continuously receives communication identifiers of preset times from the UI, judges whether the communication identifiers are the same or not, and determines that the communication identifiers have no input errors when the terminal judges that each received communication identifier is the same.
In one embodiment, the terminal sends the communication identifier without input error to the server after determining that the communication identifier has no input error.
Specifically, after the terminal locally determines that the communication identifier has no input error, the terminal only needs to send the communication identifier to the server once through the long connection channel. The received communication identification does not need to be sent to the server every time, whether input errors exist in the communication identification is verified locally, and compared with the method of sending the communication identification to the server for verification, time delay in the network transmission process is avoided, whether the error verification result is input in the communication identification can be fed back more timely, and efficiency in the account registration process is improved.
In another embodiment, the method may further include:
when the communication identifications successively received from the UI are different, the prompt information is output at the UI.
And the prompt information is used for prompting the communication identifier input error.
The prompt information can be generated by the terminal when the terminal locally detects that the communication identifier is input incorrectly, and the prompt information is displayed on an application program UI (user interface); or, the prompt information may be generated by the server, sent to the terminal and displayed on the UI interface of the application program when the server detects that the communication identifier is input incorrectly.
In an optional embodiment, the prompt message may be a text prompt message, or may be a preset error prompt symbol.
For example, when the communication identifiers continuously received from the UI are different, an input error, a text prompt asking for re-input, or a preset error prompt symbol is displayed at the communication identifier input interface on the UI interface. Of course, the prompt information may also be displayed at other positions on the UI interface, and a suitable display position and mode of the prompt on the UI interface may be selected as needed.
In one embodiment, after the communication identifier is displayed on the UI interface and the error prompt information is input, the terminal may redisplay the UI receiving the communication identifier.
Specifically, after detecting that the communication identifier is input incorrectly, the terminal resets the input times of the communication identifier, re-verifies whether the communication identifier has no input error according to the received new communication identifier.
In this embodiment of the present application, after the terminal sends the communication identifier without the input error to the server, the method may further include:
and the terminal receives the login key which is sent by the server when the communication identifier is not the registered communication identifier through the long connection channel.
The login key can be a key generated by the server according to the communication identifier and a preset algorithm; similarly, the login key may be a random login key generated by the server according to a preset rule. The generation rule of the login key in the embodiment of the application is not limited.
The terminal directly receives the login key through a long connecting channel established between the terminal and the server, the expense generated by sending the login key by calling a short message interface is not needed, meanwhile, the interactive information between the terminal and the server can be fed back in time, and the efficiency in the account registration process is ensured.
In one embodiment, the login key received by the terminal may be an encrypted login key. Specifically, after the server generates the login key according to the preset rule, the server encrypts the login key by using a preset encryption algorithm, and sends the encrypted login key to the terminal. The login key is encrypted, so that the risk of leakage of the user account registration information is avoided, and the user information security is ensured.
In another embodiment, the login key received by the terminal may also be a plaintext key.
Optionally, after receiving the login key of the plaintext key, the terminal may encrypt the login key according to a preset encryption algorithm.
In this embodiment of the present application, after the terminal receives the login key, the method further includes: the login key is saved.
The stored login key and the communication identifier are used for logging in the server.
After the terminal stores the login key, the account can be directly logged in according to the registered communication identifier and the stored login key in the subsequent login process without repeatedly submitting a request login key, so that the subsequent account login after the account registration process is improved, and the user experience is optimized.
In an embodiment, the login key stored by the terminal may be directly displayed on a UI interface of the application, and specifically, after the terminal receives the login key sent by the server, the UI interface of the application displays the registered communication identifier and the login key received by the terminal.
Optionally, the login key displayed on the UI interface may be a plaintext key, and may also be a key for hiding content, for example, the login key may be displayed as a corresponding number of asterisks.
In another alternative embodiment, the application interface UI may further provide an interface for displaying a hidden login key, and after clicking by the user, the login key may be displayed in a clear text manner, or the clear login key may be displayed in a form of hidden content, for example, the login key is displayed as a corresponding number of asterisks.
In another alternative embodiment, the login key stored by the terminal may also be directly stored in the login key file in the application root directory. In the subsequent login process, the login key corresponding to the communication identifier can be called from the key login file in the application program and the directory directly according to the registered communication identifier.
In an embodiment, the method further includes:
and when the communication identifier is determined to be the registered communication identifier, displaying registration error prompt information on an application UI interface.
Specifically, when the server determines that the communication identifier is the registered communication identifier, registration error prompt information is sent to the terminal, and after receiving the registration error prompt information, the terminal displays the information on an application program UI interface. The registration error prompt message may be a text message, a preset special symbol message, or any other form of error prompt message.
In another embodiment, after the terminal receives the registration error notification message, the method may further include:
and displaying whether the account number retrieving interface is performed or not on the UI interface.
Illustratively, when the communication identifier is a mobile phone number, after the user clicks the account to retrieve the interface, the application program displays a UI for receiving the mobile phone number to be verified, and after the terminal receives the mobile phone number to be verified, the application program displays a UI for receiving the short message verification code. The terminal sends the mobile phone number to be verified to the server through the long connecting channel, the server generates a corresponding short message verification code according to a preset rule, the uplink short message channel is called, and the short message verification code is sent to the corresponding mobile phone number. The terminal receives the short message verification code input by the user through the UI, and sends the short message verification code to the server through the long connecting channel, and the short message verification code is verified by the server. If the mobile phone number passes the verification, the server deletes the mobile phone number in the database as the registration information of the communication identifier, and the application program redisplays the UI for receiving the communication identifier.
In the application, a terminal receives a communication identifier through a user interface UI, the communication identifier is sent to a server based on a long connecting channel established between the terminal and the server, a corresponding login key when the communication identifier returned by the server is not a registered communication identifier is received through the long connecting channel, and the login key is stored, wherein the stored login key and the stored communication identifier are used for logging in the corresponding server. Therefore, the login key sent by the server is received through the long connecting channel, the expense caused by sending the login key by additionally calling a short message interface is not needed, meanwhile, the interactive information between the terminal and the server can be fed back in time, and the efficiency in the account registration process is ensured.
Fig. 4 is a flowchart illustrating another embodiment of an account registration method in this embodiment, which is applied to the server shown in fig. 1, and referring to fig. 4, the account registration method may include:
s401, a long connection channel is established between the server and the terminal, and a communication identifier sent by the terminal is received;
s402, when the communication identifier is determined not to be the registered communication identifier, generating a login key corresponding to the communication identifier;
and S403, sending the login key to the terminal based on the long connection channel.
In an embodiment, the server receives the communication identifier and the terminal identifier sent by the terminal twice continuously through the long connection channel, verifies whether the communication identifiers sent by the same terminal twice are the same based on the terminal identifier, and determines whether the received communication identifiers are input incorrectly.
Illustratively, the server receives the communication identifier and the terminal identifier through the long connection channel, determines whether the communication identifiers sent by the same terminal twice continuously are the same according to the terminal identifier, determines that the received communication identifiers have no input errors when the communication identifiers sent by the same terminal twice continuously are determined to be the same, otherwise, determines that the communication identifiers have input errors, and returns communication identifier input error information to the terminal.
It can be understood that, after acquiring the communication identifier without the input error through S401, the server generates a corresponding login key according to whether the received communication identifier is the registered communication identifier.
In some possible embodiments, the server determines that the received communication identifier without the input error is an unregistered communication identifier, and generates a unique login key corresponding to the communication identifier according to a preset algorithm.
In other possible embodiments, the server determines that the received communication identifier without the input error is the registered communication identifier, and returns registration error information to the terminal through the long connection channel.
In the embodiment of the present application, the server may determine whether the communication identifier is a registered communication identifier in any existing manner, for example, the server may search, from the database, whether the received communication identifier has corresponding registration information, and determine whether the communication identifier is a registered communication identifier, where the manner for determining whether the communication identifier is registered is not limited in the present application.
The login identification and the communication identification are used for logging in the server by the application program running in the terminal.
In some possible embodiments, the server may use a preset encryption algorithm to encrypt the login key, and then send the login key to the terminal through the long connection channel. By encrypting the login key, the risk of leakage of the user account registration information is avoided, and the safety of the user information is ensured.
In some possible embodiments, after the server sends the login key to the terminal, it determines that the account registration process is completed, and then after the server sends the login key to the terminal, the method further includes: the server releases the resources and closes the long connection channel.
In the embodiment of the application, the terminal receives the communication identifier through the user interface UI, the communication identifier is sent to the server based on a long connecting channel established between the terminal and the server, and the communication identifier returned by the server is received through the long connecting channel and is a corresponding login key when the communication identifier is a registered communication identifier, and the login key is used for logging in the corresponding server. Therefore, the login key sent by the server is received through the long connecting channel, the expense caused by sending the login key by additionally calling a short message interface is not needed, meanwhile, the interactive information between the terminal and the server can be fed back in time, and the efficiency in the account registration process is ensured.
Based on the same inventive concept, the embodiment of the present application provides an account registration apparatus, which can be applied to a terminal, and the account registration apparatus includes a plurality of functional units for implementing the account registration method.
Fig. 5 is a schematic structural diagram of an account registration apparatus in an embodiment of the present application, and referring to fig. 5, the account registration apparatus 500 may include:
a UI module 501, configured to receive a communication identifier through a user interface UI;
a first sending module 502, configured to send the communication identifier to the server based on a long connection channel established between the terminal and the server;
a first receiving module 503, configured to receive, based on the long connection channel, a login key returned when the server determines that the communication identifier is not the registered communication identifier;
a saving module 504, configured to save the login key, where the saved login key and the communication identifier are used to log in the server.
In some possible embodiments, the UI module 501 is configured to receive the communication identifier at least twice through the UI, where the communication identifiers received twice adjacent through the UI are configured to mutually verify that the communication identifiers received by the UI have no input error;
the first receiving module 503 is specifically configured to receive, based on the long connection channel, a login key returned when the server determines that the communication identifier without the input error is not the registered communication identifier.
In some possible embodiments, the first sending module 502 is configured to send, when receiving a communication identifier from the UI for one time, the communication identifier and a terminal identifier of the terminal to the server based on a long connection channel established between the terminal and the server; the terminal identification is used for the server to determine whether the communication identification sent by the terminal twice continuously has no input error.
In some possible embodiments, the image processing apparatus 500 further includes: the first verification module is used for verifying whether the communication identifiers received from the UI twice continuously are the same or not; when the communication identifiers received from the UI twice consecutively are the same, it is determined that the communication identifiers have no input error.
In some possible embodiments, the image processing apparatus 500 further includes:
the registration requirement determining module is used for determining whether the terminal has a registration requirement after the application program is started; when the terminal has a registration requirement, a long connection channel is established.
In some possible embodiments, the registration requirement determining module is configured to: when the application program is started for the first time, determining that the terminal has a registration requirement; or when the communication identifier and the login key are not correspondingly stored in the catalog of the application program, determining that the terminal has the registration requirement.
In some possible embodiments, the registration requirement determining module is configured to: when the terminal has a registration requirement, a UI for receiving a communication identifier is displayed.
It should be noted that, for the specific implementation process of the UI module 401, the first sending module 402, the first receiving module 403, and the saving module 404, reference may be made to the detailed description of the embodiments in fig. 1 to fig. 2, and for simplicity of the description, details are not repeated here.
Based on the same inventive concept, the embodiment of the present application provides an account registration apparatus, which can be applied to a server, and the account registration apparatus includes a plurality of functional units for implementing the account registration method.
Fig. 6 is a schematic structural diagram of an account registration apparatus in an embodiment of the present application, and referring to fig. 6, an account registration apparatus 600 may include:
a communication identifier receiving module 601, configured to receive a communication identifier sent by a terminal based on a long connection channel established between the server and the terminal;
a first generating module 602, configured to generate a login key corresponding to the communication identifier when it is determined that the communication identifier is not a registered communication identifier;
a login key sending module 603, configured to send a login key to the terminal based on the long connection channel; the login identification and the communication identification are used for an application program running in the terminal to log in the server.
In some possible embodiments, the first generating module 602 is configured to generate a login key corresponding to the communication identifier when it is determined that the communication identifier without the input error is not the registered communication identifier.
In some possible embodiments, the account registration apparatus 600 may further include: a second authentication module;
a communication identifier receiving module 601, configured to receive a communication identifier and a terminal identifier sent by a terminal twice continuously based on a long connection channel established between the server and the terminal; the second verification module is used for verifying whether the communication identifiers sent by the same terminal twice are the same or not based on the terminal identifier; if the communication identifiers sent by the same terminal in two adjacent times are the same, it can be determined that the communication identifier received by the terminal UI has no input error.
In some possible embodiments, the account registration apparatus 600 may further include: and the resource release module is used for closing the long connecting channel by the server after the login key is sent to the terminal based on the long connecting channel.
It should be noted that, for the specific implementation process of the communication identifier receiving module 601, the first generating module 602, and the login key sending module 603, reference may be made to the detailed description of the embodiment in fig. 4, and for the sake of brevity of the description, no further description is given here.
Based on the same inventive concept, the embodiments of the present application provide an electronic device, which may be consistent with the account registration method described in one or more embodiments above. Fig. 7 is a schematic structural diagram of an electronic device in this embodiment, and referring to fig. 7, an electronic device 700 may adopt general computer hardware, and includes a processor 701, a memory 702, and an input/output interface 703.
In some possible implementations, the at least one processor may constitute any physical device having circuitry to perform logical operations on one or more inputs. For example, at least one processor may include one or more Integrated Circuits (ICs) including an Application Specific Integrated Circuit (ASIC), a microchip, a microcontroller, a microprocessor, all or a portion of a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or other circuitry suitable for executing instructions or performing logical operations. The instructions executed by the at least one processor may be preloaded into a memory integrated with or embedded in the controller, for example, or may be stored in a separate memory. The memory may include Random Access Memory (RAM), Read Only Memory (ROM), hard disk, optical disk, magnetic media, flash memory, other permanent, fixed, or volatile memory, or any other mechanism capable of storing instructions. In some embodiments, the at least one processor may comprise more than one processor. Each processor may have a similar structure, or the processors may have different configurations that are electrically connected or disconnected from each other. For example, the processor may be a separate circuit or integrated in a single circuit. When more than one processor is used, the processors may be configured to operate independently or cooperatively. The processors may be coupled electrically, magnetically, optically, acoustically, mechanically or by other means allowing them to interact.
Based on the same inventive concept, the present application provides a computer storage medium, where computer-executable instructions are stored, and the computer-executable instructions are executed by a processor, so as to implement the account registration method according to one or more embodiments.
It should be understood by those skilled in the art that the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
The above description is only an exemplary embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (26)
1. An account registration method is applied to a terminal, and the method comprises the following steps:
receiving a communication identifier through a User Interface (UI);
based on a long connection channel established between the terminal and the server, the communication identifier is sent to the server;
receiving a login key returned when the server determines that the communication identifier is not the registered communication identifier based on the long connection channel;
and saving the login key, wherein the saved login key and the communication identifier are used for logging in the server.
2. The method of claim 1, wherein receiving the communication identifier through the UI comprises:
receiving the communication identification at least twice through the UI, wherein the communication identifications received twice adjacent through the UI are used for mutually verifying that the communication identifications received by the UI have no input error;
the receiving, based on the long connection channel, a login key returned when the server determines that the communication identifier is not a registered communication identifier includes:
receiving a login key returned when the server determines that the communication identifier without input error is not the registered communication identifier based on the long connection channel.
3. The method according to claim 2, wherein the sending the communication identifier to a server based on establishing a long connection channel with the terminal and the server comprises:
based on a long connection channel established between the terminal and the server, when the communication identifier is received from the UI once, the communication identifier and the terminal identifier of the terminal are sent to the server; the terminal identifier is used for the server to determine whether the communication identifier sent by the terminal twice continuously has no input error.
4. The method according to claim 2, wherein the sending the communication identifier to a server based on establishing a long connection channel with the terminal and the server comprises:
verifying whether the communication identifications received from the UI twice consecutively are the same;
and when the communication identifiers received from the UI twice continuously are the same, determining that the communication identifiers have no input errors.
5. The method of claim 2, further comprising:
when the communication identifiers received from the UI twice continuously are different, outputting prompt information at the UI, wherein the prompt information is used for prompting that the communication identifiers are input incorrectly.
6. The method according to any one of claims 1 to 5, further comprising:
after the application program is started, determining whether the terminal has a registration requirement;
and when the terminal has a registration requirement, establishing the long connection channel.
7. The method according to claim 6, wherein determining whether the terminal has a registration requirement after the application program is started comprises:
when the application program is started for the first time, determining that the terminal has the registration requirement;
alternatively, the first and second electrodes may be,
and when the communication identifier and the login key are not correspondingly stored in the catalog of the application program, determining that the terminal has the registration requirement.
8. The method of claim 6, further comprising:
and when the terminal has a registration requirement, displaying a UI for receiving the communication identifier.
9. An account registration method is applied to a server, and the method comprises the following steps:
receiving a communication identifier sent by the terminal based on a long connection channel established between the server and the terminal;
when the communication identifier is determined not to be the registered communication identifier, generating a login key corresponding to the communication identifier;
sending the login key to the terminal based on the long connection channel; the login identification and the communication identification are used for logging in the server by the application program running in the terminal.
10. The method of claim 9, wherein generating a login key corresponding to the communication identifier when it is determined that the communication identifier is not a registered communication identifier comprises:
and when the communication identifier without input error is determined not to be the registered communication identifier, generating a login key corresponding to the communication identifier.
11. The method according to claim 10, wherein the receiving the communication identifier sent by the terminal based on establishing a long connection channel with the server and the terminal comprises:
receiving a communication identifier and a terminal identifier which are continuously sent twice by the terminal based on a long connecting channel established between the server and the terminal;
verifying whether the communication identifiers sent by the same terminal twice are the same or not based on the terminal identifier;
if the communication identifiers sent by the same terminal twice are the same, it can be determined that the communication identifier received by the terminal UI has no input error.
12. The method of claim 9, wherein after sending the login key to the terminal based on the long connection channel, the method further comprises:
the server closes the long connection channel.
13. An account registration apparatus, applied to a terminal, the apparatus comprising:
the UI module is used for receiving the communication identification through a User Interface (UI);
the first sending module is used for sending the communication identifier to the server based on a long connection channel established between the terminal and the server;
a first receiving module, configured to receive, based on the long connection channel, a login key returned when the server determines that the communication identifier is not a registered communication identifier;
and the storage module is used for storing the login key, wherein the stored login key and the communication identifier are used for logging in the server.
14. The apparatus according to claim 13, wherein the UI module is configured to receive the communication identifier at least twice through the UI, and wherein the communication identifiers received twice next through the UI are configured to mutually verify that the communication identifiers received by the UI have no input error;
the first receiving module is specifically configured to receive, based on the long connection channel, a login key returned when the server determines that the communication identifier without the input error is not the registered communication identifier.
15. The apparatus according to claim 14, wherein the first sending module is configured to, when the communication identifier is received from the UI once, send the communication identifier and the terminal identifier of the terminal to the server this time based on a long connection channel established between the terminal and the server; the terminal identifier is used for the server to determine whether the communication identifier sent by the terminal twice continuously has no input error.
16. The apparatus of claim 14, further comprising:
a first verification module for verifying whether the communication identifiers received from the UI twice consecutively are the same;
and the determining module is used for determining that the communication identifier has no input error when the communication identifiers received from the UI twice continuously are the same.
17. The apparatus of claim 14, further comprising:
and the prompt information output module is used for outputting prompt information at the UI when the communication identifiers received from the UI twice continuously are different, wherein the prompt information is used for prompting that the communication identifiers are input wrongly.
18. The apparatus of any one of claims 13 to 17, further comprising:
the registration requirement determining module is used for determining whether the terminal has a registration requirement after the application program is started; and when the terminal has a registration requirement, establishing the long connection channel.
19. The method of claim 18, wherein the registration requirement determining module is specifically configured to:
when the application program is started for the first time, determining that the terminal has the registration requirement;
alternatively, the first and second electrodes may be,
and when the communication identifier and the login key are not correspondingly stored in the catalog of the application program, determining that the terminal has the registration requirement.
20. The apparatus of claim 19, wherein the registration requirement determining module is specifically configured to:
and when the terminal has a registration requirement, displaying a UI for receiving the communication identifier.
21. An account registration apparatus, applied to a server, the apparatus comprising: the system comprises a communication identifier receiving module, a first generating module and a login key sending module;
the communication identifier receiving module is used for establishing a long connecting channel between the server and the terminal and receiving the communication identifier sent by the terminal;
the first generation module is used for generating a login key corresponding to the communication identifier when the communication identifier is determined not to be the registered communication identifier;
the login key sending module is used for sending the login key to the terminal based on the long connecting channel; the login identification and the communication identification are used for logging in the server by the application program running in the terminal.
22. The apparatus of claim 21, wherein the first generating module is configured to generate a login key corresponding to the communication identifier when it is determined that the communication identifier without input error is not a registered communication identifier.
23. The apparatus of claim 22, further comprising: a second verification module;
the communication identifier receiving module is used for receiving the communication identifier and the terminal identifier which are continuously sent by the terminal twice based on a long connecting channel established between the server and the terminal;
the second verification module is configured to verify whether the communication identifiers sent by the same terminal twice are the same based on the terminal identifier; if the communication identifiers sent by the same terminal twice are the same, it can be determined that the communication identifier received by the terminal UI has no input error.
24. The apparatus of claim 21, further comprising: and the resource release module is used for closing the long connecting channel by the server after the login key is sent to the terminal based on the long connecting channel.
25. An electronic device, comprising:
a memory for storing processor-executable instructions;
a processor; wherein the processor is configured to: for implementing the method of any one of claims 1 to 8 or 9 to 12 when executing the executable instructions.
26. A computer-readable storage medium, characterized in that the readable storage medium stores an executable program, wherein the executable program, when executed by a processor, implements the method of any of claims 1 to 8 or 9 to 12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210138620.6A CN114584971A (en) | 2022-02-15 | 2022-02-15 | Account registration method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210138620.6A CN114584971A (en) | 2022-02-15 | 2022-02-15 | Account registration method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114584971A true CN114584971A (en) | 2022-06-03 |
Family
ID=81774000
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210138620.6A Pending CN114584971A (en) | 2022-02-15 | 2022-02-15 | Account registration method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114584971A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116436905A (en) * | 2023-04-19 | 2023-07-14 | 广州市迪士普音响科技有限公司 | Network broadcast communication method and device, storage medium and computer equipment |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110099612A1 (en) * | 2009-10-28 | 2011-04-28 | Research In Motion Limited | Automatic user authentication and identification for mobile instant messaging application |
| CN103227786A (en) * | 2013-04-08 | 2013-07-31 | 优视科技有限公司 | Method and device for filling in website login information |
| CN103259795A (en) * | 2013-05-14 | 2013-08-21 | 百度在线网络技术（北京）有限公司 | Method for executing automatic register and login, mobile terminal and server |
| CN103647695A (en) * | 2013-10-31 | 2014-03-19 | 北京奇虎科技有限公司 | Client application program user registration method, mobile terminal and server |
| CN105429961A (en) * | 2015-11-03 | 2016-03-23 | 竞技世界（杭州）网络技术有限公司 | Automatic account number registration and login method |
| US20160219059A1 (en) * | 2015-01-27 | 2016-07-28 | Hyundai Motor Company | Method of providing telematics service and registering vehicle and apparatus therefor |
| CN108809931A (en) * | 2018-04-09 | 2018-11-13 | 天津五八到家科技有限公司 | Driver's register method, driver terminal and server-side |
| CN110858968A (en) * | 2018-08-23 | 2020-03-03 | 刘高峰 | Client registration method, device and system |
| CN111740942A (en) * | 2020-01-17 | 2020-10-02 | 北京沃东天骏信息技术有限公司 | Login/registration method, device, system, electronic equipment and storage medium |
-
2022
- 2022-02-15 CN CN202210138620.6A patent/CN114584971A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110099612A1 (en) * | 2009-10-28 | 2011-04-28 | Research In Motion Limited | Automatic user authentication and identification for mobile instant messaging application |
| CN103227786A (en) * | 2013-04-08 | 2013-07-31 | 优视科技有限公司 | Method and device for filling in website login information |
| CN103259795A (en) * | 2013-05-14 | 2013-08-21 | 百度在线网络技术（北京）有限公司 | Method for executing automatic register and login, mobile terminal and server |
| CN103647695A (en) * | 2013-10-31 | 2014-03-19 | 北京奇虎科技有限公司 | Client application program user registration method, mobile terminal and server |
| US20160219059A1 (en) * | 2015-01-27 | 2016-07-28 | Hyundai Motor Company | Method of providing telematics service and registering vehicle and apparatus therefor |
| CN105429961A (en) * | 2015-11-03 | 2016-03-23 | 竞技世界（杭州）网络技术有限公司 | Automatic account number registration and login method |
| CN108809931A (en) * | 2018-04-09 | 2018-11-13 | 天津五八到家科技有限公司 | Driver's register method, driver terminal and server-side |
| CN110858968A (en) * | 2018-08-23 | 2020-03-03 | 刘高峰 | Client registration method, device and system |
| CN111740942A (en) * | 2020-01-17 | 2020-10-02 | 北京沃东天骏信息技术有限公司 | Login/registration method, device, system, electronic equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116436905A (en) * | 2023-04-19 | 2023-07-14 | 广州市迪士普音响科技有限公司 | Network broadcast communication method and device, storage medium and computer equipment |
| CN116436905B (en) * | 2023-04-19 | 2023-11-28 | 广州市迪士普音响科技有限公司 | Network broadcast communication method and device, storage medium and computer equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8769784B2 (en) | Secure and efficient authentication using plug-in hardware compatible with desktops, laptops and/or smart mobile communication devices such as iPhones | |
| CN105592065B (en) | A kind of Website logging method and its login system based on SMS | |
| CN107249004B (en) | Identity authentication method, device and client | |
| CN102546914A (en) | Automatic login system based on smart phone and control method | |
| CN104320703A (en) | Method, device and system for logging in intelligent television terminal | |
| US11824854B2 (en) | Communication system and computer readable storage medium | |
| CN107241336B (en) | Identity verification method and device | |
| CN107872447A (en) | Electronic device, server, communication system and communication method | |
| CN103747012A (en) | Security verification method, device and system of network transaction | |
| CN104820944A (en) | Method and system for bank self-service terminal authentication, and device | |
| WO2023050524A1 (en) | Im-based user identity authentication method and apparatus, and server and storage medium | |
| CN111404695B (en) | Token request verification method and device | |
| CN105741116B (en) | A kind of quick payment method, apparatus and system | |
| CN110213247A (en) | A kind of method and system improving pushed information safety | |
| CN102045335A (en) | Terminal device, signature generation server, simple id management system, simple id management method, and program | |
| CN109918211A (en) | A kind of method, apparatus of Auto-writing identifying code | |
| CN103152401A (en) | Mobile terminal, login method and system through mobile terminal, and cloud server | |
| CN115150072A (en) | Cloud network issuing authentication method, equipment, device and storage medium | |
| CN107819766A (en) | Safety certifying method, system and computer-readable recording medium | |
| CN114584971A (en) | Account registration method and device, electronic equipment and storage medium | |
| CN108200075B (en) | Identity authentication method, system, terminal and storage medium | |
| CN105306577A (en) | Data sharing system and method between handheld devices based on APP | |
| CN104079527A (en) | Information processing method and electronic equipment | |
| CN117336092A (en) | Client login method and device, electronic equipment and storage medium | |
| CN109005187A (en) | A kind of communication information guard 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 |