KR20120120021A - Access authentification for multiple devices and flatforms - Google Patents

Access authentification for multiple devices and flatforms Download PDF

Info

Publication number
KR20120120021A
KR20120120021A KR1020120038885A KR20120038885A KR20120120021A KR 20120120021 A KR20120120021 A KR 20120120021A KR 1020120038885 A KR1020120038885 A KR 1020120038885A KR 20120038885 A KR20120038885 A KR 20120038885A KR 20120120021 A KR20120120021 A KR 20120120021A
Authority
KR
South Korea
Prior art keywords
authentication
account
authentication key
target device
key
Prior art date
Application number
KR1020120038885A
Other languages
Korean (ko)
Inventor
권영민
Original Assignee
주식회사 이노디스
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 주식회사 이노디스 filed Critical 주식회사 이노디스
Priority to KR1020120038885A priority Critical patent/KR20120120021A/en
Priority to PCT/KR2012/003055 priority patent/WO2012144849A2/en
Priority to US13/452,702 priority patent/US9071422B2/en
Publication of KR20120120021A publication Critical patent/KR20120120021A/en

Links

Images

Classifications

    • 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/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • 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

Abstract

PURPOSE: An access authentication method is provided to conveniently connect other devices only with the operation of a source device in which an initial account is registered without inputting personal information including an ID or a password, etc in the other devices. CONSTITUTION: An authentication key for a target device(130) is requested to a server(140) of a membership site. A source device(110) receives a generated authentication key from an account authentication system(190). A target device receives an access authentication request from the source device with the authentication key. The target device transmits the authentication key to the server of the membership site. The server of the membership performs access authentication by confirming the account authentication system and the presence of a registered user account. The target device receives an access authentication completion report from the server of the membership site. [Reference numerals] (110) Source device; (130) Target device; (140) Server for a membership site; (191) Random number type coefficient authentication key generation part; (192) Database; (193) Account authentication part; (AA) Authentication key; (BB,DD) Authentication key issuing request; (CC) Authentication key issuing

Description

Access authentication method for multiple devices and platforms {Access authentification for multiple devices and flatforms}

The present invention relates to a technology for enabling the connection of multiple devices without additional account registration or input of account related information, and more particularly, to a method for authenticating access for multiple devices and platforms.

In general, in the case of subscribing to a specific site using the Internet or purchasing an item using a shopping mall site, not only real name authentication but also various information about the user are required. Due to the development of the Internet, countless sites exist on the Internet, and hundreds of thousands of sites are created and disappeared in Korea alone. However, if an Internet user enters his / her real name and social security number every time he joins a new site, his / her personal information is leaked by various hacking programs flooded on the Internet, and the leaked personal information can be misused in various ways. There is this.

In order to prevent leakage of data, general server systems apply a security policy that allows only authenticated users to access the system. For example, a general server system grants ID and password (PW) for each user and requests authentication of the user by inputting ID and password from the user. That is, the user transmits the authentication information consisting of ID and password to the server using the terminal, and the server side authenticates the connection by comparing with information previously registered for authentication.

As the popularity of smartphones and tablet PCs increases, so does the tendency for users to own multiple devices. There are rarely any promises made regarding the access of a particular account between these devices. The user must enter a new ID and password and perform the authentication process, even though the user uses the same account each time they switch devices. In particular, as devices are diversified and platforms are diversified, when using a specific service on multiple devices and platforms, an additional account registration and access authentication are required.

In order to reduce such inconvenience, there is a method of storing personal information such as user ID and password in the form of cookie information for each device, but cookie information can be applied only within a specific application and there is a great risk of personal information leakage due to hacking. There is no way.

The technical problem to be achieved by the present invention is to register an account on a specific site in a specific device and then to register or log in separately from another device or another platform, the first account to be able to easily register and approve access using only the authentication key temporarily granted. It is to provide a connection authentication method for multiple devices and platforms that can easily avoid the risk of hacking personal information while easily performing the connection of multiple devices by only operating the source device registered.

In order to achieve the above technical problem, the access authentication method for a multi-device and platform according to an embodiment of the present invention, when a multi-access request is received at the source device registered the first user account on the registration site, Requesting an authentication key for a target device from a server; When the source device receives the authentication key generated when the server of the membership site requests the authentication key from the account authentication system from the account authentication system, the target device authenticates the connection with the authentication key from the source device. Receiving a request; Transmitting, by the target device, the authentication key to a server of the member registration site, causing the server of the member registration site to check the existence of the account authentication system and a registered user account and perform access authentication; And when the access authentication is completed, the target device receiving a connection authentication completion notification from a server of the subscription site.

In order to achieve the above technical problem, the access authentication method for multiple devices and platforms according to another embodiment of the present invention, if a multi-access request is received to the source device registered the first user account in the account authentication system, Requesting an authentication key for the target device; Receiving, by the secondary device, the authentication key from the account authentication system, and transmitting an access authentication request together with the authentication key to any one of the target devices registered with the auxiliary device; And sending, by the target device, the authentication key to the account authentication system, checking whether a registered user account exists and performing access authentication.

In another embodiment of the present invention, an access authentication method for multiple devices and platforms is provided with an authentication key for a target device in the account authentication system when a multiple access request is received from a source device that has registered an initial user account in an account authentication system. Requesting; Receiving, by the source device, the authentication key from the account authentication system, and transmitting a connection authentication request together with the authentication key to a target device connected to the source device; And sending, by the target device, the authentication key to the account authentication system, checking whether a registered user account exists and performing access authentication.

In another embodiment of the present invention, an access authentication method for multiple devices and platforms may be performed by the account authentication system generating an authentication key when a source device that has registered an initial user account in an account authentication system requests an authentication key for a target device. Transmitting to either the source device or the auxiliary device; When the target device receiving the authentication key from the source device or the auxiliary device sends the authentication key to the account authentication system, confirming whether a registered user account corresponding to the authentication key exists; And when the registered user account is confirmed, transmitting, by the account authentication system, a notification of completion of access authentication to the target device.

According to embodiments of the present invention, a user possessing devices of various platforms avoids the risk of hacking personal information, and operates only the source device that registers the initial account without inputting personal information such as ID or password to another device. Connection can be performed easily.

1A illustrates a connection authentication system for multiple devices and platforms according to an embodiment of the present invention.
FIG. 1B is a signal flow diagram of a connection authentication method for multiple devices and platforms performed in the system of FIG. 1A.
FIG. 1C illustrates the flow chart of FIG. 1B in more detail.
2A illustrates a connection authentication system for multiple devices and platforms according to various embodiments of the present disclosure.
FIG. 2B is a signal flow diagram of a connection authentication method for multiple devices and platforms performed in the system of FIG. 2A.
3 illustrates a connection authentication system for multiple devices and platforms according to another embodiment of the present invention.
4 is a signal flow diagram of a connection authentication method for multiple devices and platforms performed in the system of FIG.
5 is a flowchart illustrating an internal operation of the account authentication system.

Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings. However, embodiments of the present invention illustrated below may be modified in various other forms, and the scope of the present invention is not limited to the embodiments described below.

1A illustrates a connection authentication system for multiple devices and platforms according to an embodiment of the present invention.

The platform may refer to a type of OS such as Windows or Linux, or may mean a development environment of a device or software, in particular, an environment of a mobile device with limited resources. Different types of OSs and different environments often have different applications for accessing specific services, and different methods for inputting information. In this case, at least one account needs to be easily accessible to the user using any device or platform, and requiring an iterative procedure may be a significant disadvantage in the user experience.

The source device 110 is a device that registers a specific account for the first time in the account authentication system 190. The source device 110 and the target devices 131 and 132 include a smart TV, a mobile phone, a smartphone, a tablet PC, a PDA, a PMP, an MP3 player, a notebook, a smart card, and the like. The source device 110 and the target device 130 have a built-in communication module that can connect to Wifi, Bluetooth, ZigBee, 3G network, etc., and an application capable of performing the algorithm described with reference to FIG. 1B is installed or in the form of firmware. It is built. If necessary, the source device 110 and the target device 130 may be connected to each other by a wide area communication method.

When the server 140 of the member registration site requests for issuance of the authentication key of the source device 110, the server 140 requests issuance of the authentication key to the account authentication system 190 so that the authentication key is newly generated in the account authentication system 190. When the server 140 of the member registration site receives the authentication key from the target device 130, the server 140 transmits the authentication key to the account authentication system 190 to confirm whether the account authentication system 190 is registered, and performs access authentication. Let's do it.

The account authentication system 190 includes a random number type authentication key generator 191 for generating an authentication key for the target device 130, a database 192 for storing user ID and password, and other personal information, and a database 192. The account authentication unit 193 retrieves the user's personal information and performs an access authentication process with the target device 131. The account authentication system 190 is a kind of server, and the communication method may be the same as that between the source device 110 and the target device 130 or may be performed through a dedicated network.

FIG. 1B is a signal flow diagram of a connection authentication method for multiple devices and platforms performed in the system of FIG. 1A.

First, when a multi-access request is received at a source device that has registered an initial user account at a subscription site, an authentication key for a target device is requested to a server of a subscription site at step S100.

Next, the server of the membership site requests the authentication key to the account authentication system (S110).

The account authentication system 190 generates a new authentication key for the authentication key issuance request of the member registration site (S111). In this case, attributes such as the authentication validity period, the validity count, the encrypted mobile phone number, and the encrypted email may be given to the generated authentication key. For example, if the authentication validity period is one hour and five times the validity period, if the target device 130 can authenticate up to five times using the same authentication key, and if one hour has elapsed since the authentication key was issued. Even if the user authentication is less than five times, the user cannot be authenticated using the same authentication key. Information such as the authentication validity period, the validity number, the encrypted mobile phone number, the encrypted e-mail, the latest authentication date and time, and the number of authentication (confirmation) to date may be stored in the database 192.

Next, the source device 110 receives the authentication key from the account authentication system 190 (S120).

Next, when the target device 130 receives the access authentication request with the authentication key from the source device 110 (S130), and transmits the authentication key to the server 140 of the registration site (S131) of the registration site The server 140 confirms the existence of an account authentication system and a registered user account and performs access authentication.

The server 140 of the registration site transmits the authentication key confirmation request to the account authentication system 190 together with the authentication key (S140).

The account authentication system 190 checks the presence of a registered user account and performs access authentication (S141). Preferably, when the account authentication system 190 receives the authentication key issuance request from the server of the member registration site, to check the access URL of the user stored in the database 192 to check the validity of the URL included in the authentication key issuance request Can be. The URL address at which the user accesses the registration site may be stored in the database 192. This is done by checking whether the same URL address is used even when the registration site requests the account authentication system 190 to issue an authentication key. It is possible to prevent the case of exploiting the system according to an embodiment of the present invention.

When the access authentication is completed, the account authentication system 190 notifies the server 140 of the member registration site of the user authentication completion (S142).

Finally, the target device 130 receives the access authentication completion notification from the server 140 of the registration site (S150).

FIG. 1C illustrates the flow chart of FIG. 1B in more detail.

In this embodiment, the source device 110 or the target device 130 does not have a direct association with the account authentication system 190 except for issuing an authentication key. Issuance of the authentication key and user authentication process is performed on behalf of the server 190 of the registration site. The request for issuance of the authentication key may include information such as an ID, an e-mail address, a phone number, a verification frequency, and an authentication period of the registration site. When the authentication key is newly generated, information such as an authentication validity period, an effective number of times, an encrypted mobile phone number, an encrypted email, a recent authentication date and time, and a number of authentication (confirmation) to date may be stored in the database 192. In the site request reply processing, a process of notifying a member registration site that a new authentication key is to be transmitted to the source device 110 in response to a user confirmation of the subscription site and a request for issuing an authentication key may be performed.

In the process of processing the authentication key verification request in the account authentication system 190, the user authentication is performed by comparing the presence or absence of the authentication key, whether or not it is within the authentication period, the site ID comparison, and the number of times of use.

2A illustrates a connection authentication system for multiple devices and platforms according to another embodiment of the present invention.

The source device 110 is a device that registers a specific account for the first time in the account authentication system 190. The source device 110, the auxiliary device 120, and the target devices 131 and 132 include a mobile phone, a smartphone, a tablet PC, a PDA, a PMP, an MP3 player, a notebook, a smart card, and the like. Alternatively, the source device 110 may be a communication device in which an encryption module is not built in a separate function.

The auxiliary device 120 is an apparatus for assisting connection authentication of the target devices 131 and 132, and may establish one-to-one connection with the source device 110 or the target devices 131 and 132. The secondary device 120 may store a list of target devices to receive the authentication key and an ID of the target device to receive the authentication key in an internal storage space, for example, a flash memory or a memory card.

The source device 110, the auxiliary device 120, and the target devices 131 and 132 have a built-in communication module that can connect to Wifi, Bluetooth, ZigBee, 3G network, etc., and can perform the algorithm described with reference to FIG. 2. The application is installed or embedded in firmware. If necessary, the source device 110, the auxiliary device 120, and the target devices 131 and 132 may be connected to each other by a wide area communication method.

The account authentication system 190 includes a random number type authentication key generation unit 191 for generating authentication keys for the target devices 131 and 132, a database 192 for storing user ID and password and other personal information, and a database ( The account authentication unit 193 retrieves the personal information of the corresponding user from the 192 and performs an access authentication process with the target device 131. The account authentication system 190 is a kind of server, and the communication method may be the same as that of the source device 110, the auxiliary device 120, and the target devices 131 and 132, or may be performed through a dedicated network.

FIG. 2B is a signal flow diagram of a connection authentication method for multiple devices and platforms performed in the system of FIG. 2A.

First, when a multiple access request is received from the source device 110 that has registered an initial user account in the account authentication system 190, the account authentication system 190 requests an authentication key for the target device 131 (S210). The account authentication system 190 generates an authentication key. The generated authentication key may be a random number authentication key. In order to enhance security, it is desirable to increase the number of digits of the authentication key.

Next, the secondary device 120 receives the authentication key from the account authentication system 190 (S220).

Next, an access authentication request is transmitted with an authentication key to any one of the target devices 131 and 132 registered in the auxiliary device 120 (S230). At this time, the auxiliary device 120 is connected to the target device 131 through the Ad-hoc network, Wifi network, 3G network, ZigBee, Bluetooth.

Finally, when the target device 131 receives the access authentication request, the target device 131 transmits the authentication key to the account authentication system 190 (S240). The account authentication system 190 searches the database 192 using the received authentication key (S241). When the user account registered in the database 192 is found, the access authentication completion notification is transmitted to the target device 131 (S250).

3 illustrates a connection authentication system for multiple devices and platforms according to another embodiment of the present invention.

In FIG. 3, the auxiliary device 120 is omitted, and the source device 110 is in charge of all the functions of this part. In this case, there is a disadvantage in that the resources of the source device 110 are used much in order to support connection authentication of the target devices 131 and 132, but there is an advantageous aspect in portability.

4 is a signal flow diagram of a connection authentication method for multiple devices and platforms performed in the system of FIG.

First, when a multiple access request is received at the source device 110 that has registered an initial user account in the account authentication system 190, the account authentication system 190 requests an authentication key for the target device 131 (S410). The account authentication system 190 generates an authentication key. The generated authentication key may be a random number authentication key.

Next, the source device 110 receives the authentication key from the account authentication system 190 (S420). Before and after this process, the source device 110 establishes a connection with the target device 131. At this time, the source device 110 is connected to the target device 131 through the Ad-hoc network, Wifi network, 3G network, ZigBee, Bluetooth.

The source device 110 transmits an access authentication request together with the authentication key to the target device 131 where the connection is established (S430).

Finally, when the target device 131 receives the access authentication request, the target device 131 transmits the authentication key to the account authentication system 190 (S440). The account authentication system 190 searches the database 192 using the received authentication key (S441). When the user account registered in the database 192 is found, an access authentication completion notification is transmitted to the target device 131 (S450).

5 is a flowchart illustrating an internal operation of the account authentication system.

First, the source device 110 that registered the first user account in the account authentication system 190 receives an authentication key request for the target devices 131 and 132 (S510).

The account authentication system 190 generates an authentication key using the random number type authentication key generation unit 191 (S520).

Next, the account authentication system 190 generates an authentication key and transmits it to either the source device 110 or the auxiliary device 120 (S530). At this time, the source device 110 or the secondary device 120 receiving the authentication key transmits a connection authentication request to the target device 131 together with the authentication key.

Next, the account authentication system 190 receives a user account presence confirmation request registered with the authentication key from the target device 131 (S540).

The account authentication system 190 checks the database 192 and checks the existence of a registered user account corresponding to the authentication key (S550).

Finally, if the registered user account is confirmed, the account authentication system 190 transmits the access authentication completion notification to the target device 131 (S560).

In order to enhance security, you may limit the number of times or the time of use of the authentication key. That is, the simultaneous access authentication of two or more target devices is performed with one authentication key, but if the target number of target devices succeeds in access authentication, a method of discarding the corresponding authentication key may be adopted.

According to another embodiment of the present invention, after the account authentication system 190 transmits the access authentication completion notification, the validity period (available time) of the authentication key may be treated as expired.

The invention can be implemented via software. Preferably, a program for executing a connection authentication method for a multi-device and a platform according to embodiments of the present invention may be provided by recording a program for executing in a computer on a computer-readable recording medium. When implemented in software, the constituent means of the present invention are code segments that perform the necessary work. The program or code segments may be stored on a processor readable medium or transmitted by a computer data signal coupled with a carrier on a transmission medium or network.

A computer-readable recording medium includes all kinds of recording apparatuses in which data that can be read by a computer system is stored. Examples of computer-readable recording devices include ROM, RAM, CD-ROM, DVD ± ROM, DVD-RAM, magnetic tape, floppy disk, hard disk, optical data storage, flash memory, memory card, etc. There is this. The computer readable recording medium can also be distributed over network coupled computer devices so that the computer readable code is stored and executed in a distributed fashion.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those skilled in the art that various changes and modifications may be made therein without departing from the scope of the present invention. And, such modifications should be considered to be within the technical protection scope of the present invention. Therefore, the true technical protection scope of the present invention will be defined by the technical spirit of the appended claims.

Claims (12)

Requesting an authentication key for a target device from a server of the subscription site when a multiple access request is received from a source device that has registered an initial user account on a subscription site;
When the source device receives the authentication key generated when the server of the membership site requests the authentication key from the account authentication system from the account authentication system, the target device authenticates the connection with the authentication key from the source device. Receiving a request;
Transmitting, by the target device, the authentication key to a server of the member registration site, causing the server of the member registration site to check the existence of the account authentication system and a registered user account and perform access authentication; And
Receiving the access authentication completion notification from the server of the membership site when the access authentication is completed;
Including, the connection authentication method for multiple devices and platforms. The method of claim 1,
Receiving an access authentication request with the authentication key from the source device
When the account authentication system receives the authentication key issuance request from the server of the member registration site, retrieving the access URL of the user stored in the database to verify the validity of the URL included in the authentication key issuance request A connection authentication method for multiple devices and platforms. Requesting an authentication key for a target device from the account authentication system when a multiple access request is received from a source device that has registered an initial user account in an account authentication system;
Receiving, by the secondary device, the authentication key from the account authentication system, and transmitting an access authentication request together with the authentication key to any one of the target devices registered with the auxiliary device; And
Transmitting, by the target device, the authentication key to the account authentication system, checking whether a registered user account exists and performing access authentication;
Including, the connection authentication method for multiple devices and platforms. The method of claim 3,
The authentication key is a random authentication key, characterized in that the connection authentication method for multiple devices and platforms. The method of claim 3,
The auxiliary device is connected to the target device through any one of the ad-hoc network, Wifi network, 3G network, ZigBee, Bluetooth, connection authentication method for multiple devices and platforms. The method of claim 3,
The auxiliary device
A mobile phone, a smart phone, a PDA, a PMP, an MP3 player, a notebook, a smart card, any one of a communication device with a built-in encryption module, connection authentication method for multiple devices and platforms. The method of claim 3,
The auxiliary device
Storing a list of target devices to receive the authentication key and an ID of the target device to receive the authentication key preferentially. Requesting an authentication key for a target device from the account authentication system when a multiple access request is received from a source device that has registered an initial user account in an account authentication system;
Receiving, by the source device, the authentication key from the account authentication system, and transmitting a connection authentication request together with the authentication key to a target device connected to the source device; And
Transmitting, by the target device, the authentication key to the account authentication system, checking whether a registered user account exists and performing access authentication;
Including, the connection authentication method for multiple devices and platforms. 9. The method of claim 8,
The step of transmitting a connection authentication request with the authentication key to the target device connected to the source device
And establishing, by the source device, the connection with the target device through any one of an Ad-hoc network, a Wifi network, a 3G network, a ZigBee, and a Bluetooth. When a source device that has registered an initial user account in an account authentication system requests an authentication key for a target device, generating, by the account authentication system, an authentication key and transmitting the generated authentication key to either the source device or an auxiliary device;
When the target device receiving the authentication key from the source device or the auxiliary device sends the authentication key to the account authentication system, confirming whether a registered user account corresponding to the authentication key exists; And
If the registered user account is confirmed, transmitting, by the account authentication system, an access authentication completion notification to the target device;
Including, the connection authentication method for multiple devices and platforms. The method of claim 10,
The authentication key is a random authentication key, characterized in that the connection authentication method for multiple devices and platforms. The method of claim 10,
And after the account authentication system transmits the access authentication completion notification, processing the validity period of the authentication key as expired.
KR1020120038885A 2011-04-20 2012-04-16 Access authentification for multiple devices and flatforms KR20120120021A (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
KR1020120038885A KR20120120021A (en) 2011-04-20 2012-04-16 Access authentification for multiple devices and flatforms
PCT/KR2012/003055 WO2012144849A2 (en) 2011-04-20 2012-04-20 Access authentication method for multiple devices and platforms
US13/452,702 US9071422B2 (en) 2011-04-20 2012-04-20 Access authentication method for multiple devices and platforms

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020110036467 2011-04-20
KR1020120038885A KR20120120021A (en) 2011-04-20 2012-04-16 Access authentification for multiple devices and flatforms

Related Child Applications (1)

Application Number Title Priority Date Filing Date
KR20140072679A Division KR101479903B1 (en) 2011-04-20 2014-06-16 Access authentification for multiple devices and flatforms

Publications (1)

Publication Number Publication Date
KR20120120021A true KR20120120021A (en) 2012-11-01

Family

ID=47507071

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020120038885A KR20120120021A (en) 2011-04-20 2012-04-16 Access authentification for multiple devices and flatforms

Country Status (1)

Country Link
KR (1) KR20120120021A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015160775A1 (en) * 2014-04-15 2015-10-22 Google Inc. Auto-user registration and unlocking of a computing device

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015160775A1 (en) * 2014-04-15 2015-10-22 Google Inc. Auto-user registration and unlocking of a computing device
US9276914B2 (en) 2014-04-15 2016-03-01 Google Inc. Auto-user registration and unlocking of a computing device
KR20160137648A (en) * 2014-04-15 2016-11-30 구글 인코포레이티드 Auto-user registration and unlocking of a computing device
US9882895B2 (en) 2014-04-15 2018-01-30 Google Llc Auto-user registration and unlocking of a computing device
US10848484B2 (en) 2014-04-15 2020-11-24 Google Llc Auto-user registration and unlocking of a computing device

Similar Documents

Publication Publication Date Title
US10412575B2 (en) System and method for virtual SIM card
US9071422B2 (en) Access authentication method for multiple devices and platforms
US9537661B2 (en) Password-less authentication service
US9529985B2 (en) Global authentication service using a global user identifier
US10728244B2 (en) Method and system for credential management
US9680841B2 (en) Network authentication method for secure user identity verification using user positioning information
US11044604B2 (en) Method and system for protecting and utilizing internet identity, using smartphone
US9178874B2 (en) Method, device and system for logging in through a browser application at a client terminal
KR20150124933A (en) Secure user two factor authentication method from Personal infomation leaking and smishing
EP3937040B1 (en) Systems and methods for securing login access
CN105612731A (en) Roaming internet-accessible application state across trusted and untrusted platforms
KR20240023589A (en) Cross authentication method and system between online service server and client
US20190238532A1 (en) Authentication system utilizing secondary connection
US9906516B2 (en) Security system for preventing further access to a service after initial access to the service has been permitted
KR101479903B1 (en) Access authentification for multiple devices and flatforms
US11475139B2 (en) System and method for providing secure data access
KR20120120021A (en) Access authentification for multiple devices and flatforms
KR101879842B1 (en) User authentication method and system using one time password
KR20130005635A (en) System for providing secure card payment system using mobile terminal and method thereof
KR20140042222A (en) User identity authentication method using mobile terminal
US10798574B1 (en) Mobile communication device certification framework
WO2023283542A1 (en) User authentication
KR20140007984A (en) Method for login with instant message

Legal Events

Date Code Title Description
A201 Request for examination
E902 Notification of reason for refusal
AMND Amendment
E601 Decision to refuse application
AMND Amendment
E801 Decision on dismissal of amendment
A107 Divisional application of patent
WITB Written withdrawal of application