Method, system, and computer-readable recording medium for managing user account

Abstract

The disclosure is related to a method for managing user account performed by at least one processor. The method may comprise providing a first login page used for performing a first type of login to an application; and providing, based on a user input selecting a first region of the first login page, a second login page used for performing a second type of login to the application. The second type of login may be associated with using biometric information of the user. The first type of login may be different from the second type of login.

Description

Technical Field

[0001] This invention relates to user account management methods, systems, and computer-readable recording media. Prior Technology

[0002] With the development of e-commerce, various online platforms have also emerged. Among them, food delivery platforms have grown rapidly in recent years, becoming an important service that further simplifies the connection between consumers and restaurants. On these food delivery platforms, restaurant owners can use various devices in a mobile environment, such as smartphones, tablets, and POS terminals, to accept and process customer orders.

[0003] To utilize various online platforms, users need to log in with a registered account for the corresponding service. Recently, multiple login methods have been developed. Therefore, the process of accessing and switching between multiple login methods becomes cumbersome, leading to increased user fatigue. Summary of the Invention

[0004] [The problem the invention aims to solve] In order to solve the problems mentioned above, the purpose of this invention is to provide a user account management method, system, and computer-readable recording medium.

[0005] [Technical means to solve the problem] The present invention can be implemented in a variety of ways, including methods, apparatus (systems), computer-readable recording media, or computer programs stored on readable recording media.

[0006] According to an embodiment of the present invention, a user account management method executed by at least one processor includes the following steps: providing a first login page for performing a first type of login on an application; and providing a second login page for performing a second type of login on the application based on user input that selects a first area of ​​the first login page, wherein the second type of login is related to the use of the user's biometric information, and the first type of login may be different from the second type of login.

[0007] According to one embodiment of the present invention, biometric information may include information pre-stored on a user terminal receiving an application.

[0008] According to an embodiment of the present invention, the first type of login includes type 1_1 login and type 1_2 login. The step of providing the first login page may include the following steps: based on user input that selects a second page of the first login page, providing a first input box related to type 1_1 login or a second input box related to type 1_2 login.

[0009] According to one embodiment of the present invention, the first type of login includes type 1_1 login and type 1_2 login, and the first login page may include a third input box to receive information for identifying type 1_1 login or type 1_2 login.

[0010] According to an embodiment of the present invention, the user account management method further includes the following steps: before providing the first login page, providing a second login page for performing a second type of login on the application or a third login page for performing a third type of login on the application, wherein the third type of login is related to using pre-stored user account information, and the user account information may be related to the user.

[0011] According to an embodiment of the present invention, the step of providing a second login page or a third login page may include the following steps: if the user terminal receiving the application has pre-stored biometric information, then a second login page is provided; and if the user terminal does not have pre-stored biometric information, then a third login page is provided.

[0012] According to an embodiment of the present invention, the step of providing a first login page may include the following steps: providing a first login page based on the determination that the user terminal receiving the application does not have pre-stored biometric information and pre-stored user account information related to the user.

[0013] According to an embodiment of the present invention, the user account management method further includes the following steps: before providing the first login page, providing a second login page for performing a second type of login on the application, wherein the step of providing the first login page may include the following steps: providing the first login page based on user input that selects a first area of ​​the second login page.

[0014] According to an embodiment of the present invention, the user account management method further includes the following steps: before providing the first login page, providing a second login page for performing a second type of login on the application; the step of providing the first login page may include the following steps: providing a widget for selecting a login method based on user input that selects a first area of ​​the second login page; and providing the first login page based on user input that selects a first area of ​​the widget.

[0015] According to an embodiment of the present invention, the user account management method further includes the following steps: before providing the first login page, providing a third login page for performing a third type of login on the application, and the step of providing the first login page may include the following steps: providing the first login page based on user input that selects a first area of ​​the third login page.

[0016] According to an embodiment of the present invention, the user account management method further includes the following steps: before providing the first login page, providing a third login page for performing a third type of login on the application, wherein the step of providing the first login page may include the following steps: providing a widget for selecting a login method based on user input that selects a first area of ​​the third login page; and providing the first login page based on user input that selects a first area of ​​the widget.

[0017] According to an embodiment of the present invention, the step of providing a first login page may include the following steps: providing a widget for selecting a login method; and providing a first login page based on user input that selects a first area of ​​the widget.

[0018] According to an embodiment of the present invention, the step of providing a second login page may include the following steps: providing a widget for selecting a login method based on user input that selects a first area of ​​a first login page; and providing a second login page based on user input that selects a second area of ​​the widget.

[0019] According to an embodiment of the present invention, a user account management method executed by at least one processor may include the following steps: providing a first login page for performing a first type of login on an application; and providing a third login page for performing a third type of login on an application based on user input that selects a third area of ​​the first login page, wherein the third type of login is associated with pre-stored user account information, the user account information may be associated with a user, and the first type of login may be different from the third type of login.

[0020] According to one embodiment of the present invention, the pre-stored user account information may include information pre-stored on the user terminal receiving the application.

[0021] According to an embodiment of the present invention, the step of providing a third login page may include the following steps: providing a widget for selecting a login method based on user input that selects a third area of ​​a first login page; and providing a third login page based on user input that selects a third area of ​​the widget.

[0022] An embodiment of the present invention provides a computer-readable recording medium that can record instructions for executing a user account management method on a computer.

[0023] According to an embodiment of the present invention, an information processing system includes: a memory; and at least one processor connected to the memory for executing at least one computer-readable program included in the memory. The at least one program may include instructions for performing the following steps: providing a first login page for performing a first type of login on an application; and providing a second login page for performing a second type of login on the application based on user input selecting a first area of ​​the first login page. The second type of login may be related to the use of the user's biometric information, and the first type of login may be different from the second type of login.

[0024] [Comparison with the effectiveness of previous technologies] According to various embodiments of the present invention, users can navigate to the login page to use multiple login methods based on their selection, thereby improving user convenience.

[0025] According to various embodiments of the present invention, a login page corresponding to user input can be provided to the user, thereby providing an environment for easy login. The effects of the present invention are not limited to those mentioned above; those skilled in the art (hereinafter referred to as "skilled persons") can clearly understand other effects not mentioned through the description in the claims. Simple Explanation of the Diagram

[0026] Hereinafter, several embodiments of the present invention will be described with reference to the accompanying drawings. In this process, similar reference numerals indicate similar structures, but are not limited thereto.

[0027] Figure 1 is a schematic diagram illustrating a user account management method according to an embodiment of the present invention.

[0028] Figure 2 is a schematic diagram illustrating the connection structure of an information processing system according to an embodiment of the present invention for communicating with multiple user terminals in order to manage user accounts.

[0029] Figure 3 is a block diagram illustrating the internal structure of a user terminal and information processing system according to an embodiment of the present invention.

[0030] Figure 4 is an example diagram of the first login page according to an embodiment of the present invention.

[0031] Figure 5 is an example diagram of the first login page according to an embodiment of the present invention.

[0032] Figure 6 is an example diagram of the first login page according to an embodiment of the present invention.

[0033] Figure 7 is an example diagram of an additional login page according to an embodiment of the present invention.

[0034] Figure 8 is an example diagram of the second login page according to an embodiment of the present invention.

[0035] Figure 9 is an example diagram of the third login page according to an embodiment of the present invention.

[0036] Figure 10 is an example diagram of the first login page according to an embodiment of the present invention.

[0037] Figure 11 is an example diagram of the first login page according to an embodiment of the present invention.

[0038] Figure 12 is an example diagram of the first login page according to an embodiment of the present invention.

[0039] Figure 13 is an example diagram of the first login page according to an embodiment of the present invention.

[0040] Figure 14 is an example diagram of a micro-part of an embodiment of the present invention.

[0041] Figure 15 is an illustrative flowchart of a user account management method according to an embodiment of the present invention.

[0042] Figure 16 is an illustrative flowchart of a user account management method according to an embodiment of the present invention. Implementation

[0043] The following is a detailed description of the specific contents used to implement the present invention with reference to the accompanying drawings. However, in the following description, specific descriptions of well-known functions or structures will be omitted when there is a possibility that they may unnecessarily obscure the spirit of the present invention.

[0044] In the accompanying drawings, the same or corresponding structural elements are given the same reference numerals. Furthermore, in describing the following embodiments, repeated descriptions related to the same or corresponding structural elements will be omitted. However, even if the description of structural elements is omitted, this does not mean that such structural elements are not included in any embodiment.

[0045] The advantages, features, and implementation methods of the disclosed embodiments become clear with reference to the embodiments described in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, and can be implemented through different methods. Furthermore, these embodiments are provided to ensure the completeness of this disclosure, and are only provided to enable those skilled in the art to fully understand the scope of the present invention.

[0046] In this specification, the terminology used will be briefly described and specific embodiments will be illustrated. While widely used terms have been selected as much as possible in consideration of the functionality of the invention, the terminology used herein may vary depending on the intent or convention of those skilled in the art, the emergence of new technologies, etc. Furthermore, in certain cases, terms arbitrarily chosen by the applicant may exist; in such cases, their meanings are detailed in the corresponding description of the invention. Therefore, the terminology used in this specification should be defined based on its meaning and the full text of this specification, and not limited to the name of the term.

[0047] In this specification, unless explicitly specified in the context as singular, singular expressions include plural expressions. Furthermore, unless explicitly specified in the context as plural, plural expressions include singular expressions. Throughout this specification, when indicating that a structural element includes any structural element, it means, unless specifically stated otherwise, that other structural elements may also be included, and not excluded.

[0048] Furthermore, in this specification, the terms "module" or "unit" as used refer to software structural elements or hardware structural elements that perform a certain function. However, "module" or "unit" is not limited to software or hardware. "Module" or "unit" may reside in accessible storage media, or may be reproduced on one or more processors. Thus, as an example, "module" or "unit" may include structural elements such as software structural elements, object-oriented software structural elements, class structural elements, and task structural elements, processes, functions, attributes, programs, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, lists, arrays, or variables. The functionality provided internally by structural elements and "modules" or "units" may be formed by combining fewer structural elements and "modules" or "units" or further separated into additional structural elements and "modules" or "units".

[0049] According to one embodiment of the present invention, a "module" or "unit" may be implemented by a processor and memory. The term "processor" is broadly interpreted to include general-purpose processors, central processing units (CPUs), microprocessors, digital signal processors (DSPs), controllers, microcontrollers, state machines, etc. In many contexts, "processor" may also refer to application-specific integrated circuits (ASICs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), etc. For example, "processor" may also refer to a combination of a digital signal processor and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors combined with a digital signal processing chip, or any other combination of the aforementioned structures. Furthermore, "memory" is broadly interpreted to include any electronic component capable of storing electronic information. "Memory" may also refer to various types of processor-readable media such as random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic or tagged data storage devices, and registers. When the processor reads information from or writes information to memory, the memory and the processor are in electronic communication. The memory integrated into the processor is in a state of electronic communication with the processor.

[0050] In this specification, "system" may include at least one of server devices and cloud devices, but is not limited thereto. For example, a system may also consist of more than one server device. As another example, a system may consist of more than one cloud device. As yet another example, a system may be configured and operated by combining server devices and cloud devices.

[0051] In this specification, "display" means any display device associated with a computing device, for example, any display device controlled by or capable of displaying any information / data provided by the computing device.

[0052] In this specification, "each of the plurality of A" or "each of the plurality of A" means all the structural elements included in the plurality of A, or it may also mean some of the structural elements included in the plurality of A.

[0053] In this specification, "user" refers to a user using the application or a user account of the application. A user account may refer to an account or related information generated and used by a user through the application.

[0054] Hereinafter, several embodiments of the present invention will be described in detail with reference to the accompanying drawings. The dimensions or positions of the display screens, images, buttons, etc., shown in the drawings are merely examples and are not limiting. For example, some buttons may be added or omitted, or the layout may be different in size and position from those shown in the drawings. Furthermore, the flowcharts and descriptions shown in the drawings are merely examples, and some embodiments may be implemented through different methods. For example, one or more steps may be omitted, or the order of the steps may be changed, or one or more steps may be repeated, or one or more steps may be executed multiple times.

[0055] Figure 1 is a schematic diagram illustrating a user account management method according to an embodiment of the present invention. User 110 can utilize an application (e.g., an application providing user account management services). User terminal 120 can send and receive data and / or information with an information processing system providing user account management services through the application. The services provided by the application include any service for managing user accounts; for example, it can be a composite service integrating e-commerce services, content streaming services, food delivery services, etc.

[0056] User 110 can log in to the application using a user account registered in the application. Login refers to the verification steps required to obtain access rights to the application, related systems, networks, etc., through a user's registered user account.

[0057] Login can be achieved through the following steps. An information processing system (e.g., information processing system 230 and / or user terminal 120 of Figures 2 and 3) can pre-store registration information related to the user account. The user terminal 120 can obtain input information through a user interface, etc. A processor (e.g., at least one processor included in the information processing system and / or the user terminal) can determine whether the registration information corresponds to the input information by comparing the registration information with the input information. For example, the processor can identify information related to the user account corresponding to the input information from the registration information. When it is determined that the identified user account information corresponds to the registration information, the user account login can be successful. Alternatively, if it is determined that the identified user account information does not correspond to the registration information, the user account login can fail. Furthermore, when it is impossible to identify information related to the user account corresponding to the input information from the registration information, login can fail.

[0058] Registration information related to a user account can be stored and managed in the database of the information processing system. Registration information can be generated during the process of user 110 subscribing to a membership to utilize the application. To subscribe to a membership, user 110 can enter their information into a specified form. A user account can be generated based on the information entered in the specified form. The information processing system can link the user account to register the information entered in the specified form. The information processing system can store the registration information related to the user account in the database. Furthermore, the user terminal 120 can retrieve and store the registration information. In one embodiment, user 110 can perform a membership subscription step by selecting a portion of the login page (e.g., the "Membership Subscription" area of ​​the first login page 130 in FIG. 1).

[0059] In one embodiment, the information processing system and / or user terminal 120 may pre-store multiple pieces of information related to the user account as registration information. For example, the registration information may include the user 110's name, date of birth, address, mobile phone number, email address, password, biometric information, etc.

[0060] In one embodiment, login may have at least one type. For example, a first type of login may be associated with basic information using a user account. For example, a first-type login may be associated with a mobile phone number. A second-type login may be associated with an email address. A third type of login may be associated with user 110's biometric information.

[0061] In one embodiment, the biometric information of user 110, as an inherent physical or physiological characteristic of user 110, can represent measurable and identifiable information. The biometric information of user 110 may include information obtainable through the input device of user terminal 120. For example, the biometric information of user 110 may include fingerprints, facial shape (e.g., information for FACE IN in iOS), iris, retina, hand shape, vein pattern, voice pattern, etc.

[0062] In one embodiment, the application can perform at least one type of login. For example, as registration information for a first type of login, the user terminal 120 and / or the information processing system can pre-store the user 110's mobile phone number and / or the user 110's email address. As registration information for a second type of login, the user terminal 120 and / or the information processing system can pre-store user account information. The corresponding user account information can be information related to the user account pre-logged into the application through the user terminal 120.

[0063] In one embodiment, user terminal 120 may link to a user account to pre-store the biometric information of user 110. For example, user terminal 120 may obtain information related to the user account (e.g., a user account pre-logged into the application via user terminal 120) and the biometric information of user 110. User terminal 120 may link to the corresponding user account to store the biometric information of user 110 as registration information.

[0064] In one embodiment, user terminal 120 may provide a second type of login method, utilizing the biometric information of user 110 stored as registration information. For example, user terminal 120 may obtain the biometric information of user 110 as input information via its input device. User terminal 120 may determine whether the biometric information used as registration information corresponds to the biometric information used as input information. When it is determined that the input information and registration information correspond to each other, the user account login can be successful.

[0065] In one embodiment, the user terminal 120 may pre-store user account information. For example, the user terminal 120 may pre-store user account information that has been pre-logged in through the user terminal 120 as registration information.

[0066] In one embodiment, user terminal 120 can provide a third type of login method, utilizing user account information pre-stored as registration information. For example, user terminal 120 can log in to the corresponding user account based on input from user 110 who has selected the pre-stored user account information. As another example, user terminal 120 can request additional information (e.g., user account password, mobile phone number, etc.) related to the pre-stored user account information from user 110. User terminal 120 can obtain the additional information and determine whether it corresponds to the pre-stored user account information. When it is determined that the additional information corresponds to the pre-stored user account information, the user account login can be successful.

[0067] In one embodiment, user terminal 120 may provide a login page for user 110 to perform at least one type of login. For example, user terminal 120 may provide a first login page 130 for performing a first type of login on an application. User terminal 120 may provide a second login page for performing a second type of login on an application. User terminal 120 may provide a third login page for performing a third type of login on an application. The second login page will be described in detail later with reference to FIG8, and the third login page will be described in detail with reference to FIG9.

[0068] In one embodiment, user terminal 120 can identify biometric information of user 110 stored on user terminal 120. If biometric information is identified, user terminal 120 can provide a second login page for performing a second type of login. If biometric information cannot be identified, user terminal 120 can identify user account information pre-stored on user terminal 120. If pre-stored user account information is identified, user terminal 120 can provide a third login page for performing a third type of login. If neither biometric information nor pre-stored user account information can be identified, user terminal 120 can provide a first login page 130 for performing a first type of login. That is, based on the determination that user terminal 120 does not have pre-stored biometric information and pre-stored user account information, the processor can provide a first login page 130.

[0069] In one embodiment, the first login page 130 can be used to perform a Type 1_1 login. For example, the first login page 130 may include a first input box 136 and a login button 138. Text can be entered through the first input box 136. After the text is entered, when the processor receives input from the user selecting the login button 138, it can identify a user account registered with a mobile phone number corresponding to the text entered as registration information. If the user account is identified, part of the login process can be successful. Subsequently, the processor can provide an additional login page for additional verification. If the user account cannot be identified, the login for the user account can fail. The additional login page will be described in detail later with reference to FIG7.

[0070] In one embodiment, the first login page 130 may include a first area 131 and a third area 134. The processor may provide a second login page for performing a second type of login on the application based on user 110 input selecting the first area 131. Furthermore, the processor may provide a third login page for performing a third type of login on the application based on user 110 input selecting the third area 134.

[0071] In one embodiment, the first login page 130 may include a second area 132. The processor may provide a first input box 136 associated with login type 1_1 or a second input box associated with login type 1_2 based on user input from user 110 who selects the second area 132. Referring to FIG1, the processor may provide a second input box based on user input from user 110 who selects the "email login" area in the second area 132. The processor may provide a first input box 136 based on user input from user 110 who selects the "phone number login" area in the second area 132. The first login page including the second input box will be described in detail later with reference to FIG4.

[0072] In one embodiment, the first login page 130 may include a fourth region 139, which includes a first region 131 and a third region 134. In another embodiment, the first login page may not include the fourth region 139. For example, a first login page may be provided when the user terminal 120 performs a login for the first time. As another example, the user terminal 120 may recognize the biometric information and user account information of the user 110 pre-stored on the user terminal 120. If neither the biometric information nor the pre-stored user account information can be recognized, a first login page excluding the fourth region 139 may be provided.

[0073] As described above, user 110 can be redirected to the login page to use various login methods based on their selection. This improves user convenience.

[0074] Figure 2 is a schematic diagram illustrating the connection structure of an information processing system 230 according to an embodiment of the present invention for communicating with multiple user terminals 210_1, 210_2, and 210_3 to manage user accounts. As shown in the figure, the multiple user terminals 210_1, 210_2, and 210_3 can be connected to the information processing system 230, which can provide user account management services, via network 220. The multiple user terminals 210_1, 210_2, and 210_3 may include user terminals that receive user account management services.

[0075] In one embodiment, the information processing system 230 may include a computer executable program (e.g., a downloadable application) related to providing user account management services, and one or more server devices and / or databases or one or more distributed computing devices and / or distributed databases based on cloud computing services capable of storing, providing and executing data.

[0076] The user account management service provided by the information processing system 230 can be provided to users through user account management service applications, web browsers, web browser extensions, etc., installed on multiple user terminals 210_1, 210_2, and 210_3 respectively. For example, the information processing system 230 can provide information or perform corresponding processing for login requests and information requests related to user accounts received from user terminals 210_1, 210_2, and 210_3 through user account management service applications, etc.

[0077] Multiple user terminals 210_1, 210_2, and 210_3 can communicate with the information processing system 230 via network 220. Network 220 enables communication between multiple user terminals 210_1, 210_2, and 210_3 and the information processing system 230. For example, network 220 can be implemented using wired networks such as Ethernet, Power Line Communication, telephone line communication devices, and RS-serial communication, as well as mobile communication networks, wireless local area networks (WLANs), Wi-Fi, Bluetooth, and ZigBee, or combinations thereof, depending on the setup environment. The communication method is not limited; in addition to communication networks that network 220 can include (e.g., mobile communication networks, wired internet, wireless internet, broadcast networks, satellite networks, etc.), it can also include short-range wireless communication between user terminals 210_1, 210_2, and 210_3.

[0078] In Figure 2, mobile phone terminal 210_1, tablet terminal 210_2, and personal computer (PC) terminal 210_3 are shown as examples of user terminals, but the model is not limited to these. User terminals 210_1, 210_2, and 210_3 can be any computing device capable of wired and / or wireless communication and capable of executing or installing applications or web browsers that provide user account management services. For example, user terminals may include artificial intelligence speakers, smartphones, mobile phones, navigators, computers, laptops, digital broadcasting terminals, personal digital assistants (PDAs), portable multimedia players (PMPs), tablet computers, game consoles, wearable devices, Internet of Things (IoT) devices, virtual reality (VR) devices, augmented reality (AR) devices, set-top boxes, etc. Furthermore, although Figure 2 shows three user terminals 210_1, 210_2, and 210_3 communicating with the information processing system 230 via network 220, it is not limited to this, and the number of user terminals communicating with the information processing system 230 via network 220 can also be different.

[0079] Figure 2 illustrates a structure in which user requests (e.g., login requests, information requests related to user accounts) are transmitted to the information processing system 230 via user terminals 210_1, 210_2, and 210_3. However, the system is not limited to this. User requests can be provided to the information processing system 230 via input devices associated with the information processing system 230, and the processing results of user requests (e.g., information related to user accounts) can also be provided to the user via output devices associated with the information processing system 230 (e.g., displays).

[0080] Figure 3 is a block diagram illustrating the internal structure of a user terminal 210 and an information processing system 230 according to an embodiment of the present invention. The user terminal 210 can also be referred to as any computing device capable of executing applications, web browsers, or wired / wireless communication, such as the mobile phone terminal 210_1, tablet terminal 210_2, and PC terminal 210_3 shown in Figure 2. As shown in Figure 3, the user terminal 210 may include a memory 312, a processor 314, a communication module 316, and an input / output interface 318. Similarly, the information processing system 230 may include a memory 332, a processor 334, a communication module 336, and an input / output interface 338. As shown in Figure 3, the user terminal 210 and the information processing system 230 can use the respective communication modules 316 and 336 to send and receive information and / or data via the network 220. Furthermore, the input / output device 320 can input information and / or data to the user terminal 210 through the input / output interface 318, or it can output information and / or data generated by the user terminal 210.

[0081] Memory modules 312 and 332 may include any non-transitory computer-readable recording medium. According to one embodiment, memory modules 312 and 332 may include non-volatile mass storage devices such as read-only memory (ROM), disk drives, solid-state drives (SSDs), or flash memory. As another example, non-volatile mass storage devices such as read-only memory, solid-state drives, flash memory, and disk drives, as additional permanent storage devices different from memory modules, may be included within the user terminal 210 or the information processing system 230. Furthermore, memory modules 312 and 332 may store an operating system and at least one program code.

[0082] Such software structural elements can be loaded from an additional computer-readable recording medium other than the memories 312 and 332. This additional computer-readable recording medium may include a recording medium that can be directly connected to the user terminal 210 and the information processing system 230, such as a floppy disk drive, magnetic disk, magnetic tape, DVD / CD-ROM drive, and / or memory card. As another example, the software structural elements may also be loaded into the memories 312 and 332 via communication modules 316 and 336, instead of a computer-readable recording medium. For example, at least one program may be loaded into the memories 312 and 332 based on a file-installed computer program provided by a developer or a file distribution system that distributes application installation files via network 220.

[0083] Processors 314 and 334 can process computer program instructions by performing basic arithmetic, logic, and input / output operations. Instructions can be provided to processors 314 and 334 via memory 312 and 332 or communication modules 316 and 336. For example, processors 314 and 334 can execute instructions received based on program code stored in recording devices such as memory 312 and 332. Processors 314 and 334 can be configured to execute programs for providing user account management services.

[0084] Communication modules 316 and 336 can provide a structure or function that enables user terminal 210 and information processing system 230 to communicate with each other via network 220, and can provide a structure or function that enables user terminal 210 and / or information processing system 230 to communicate with other user terminals or other systems (e.g., additional cloud systems, etc.). As an example, under the control of communication module 316, requests or data (e.g., information related to user accounts, etc.) generated by processor 314 of user terminal 210 based on program code stored in recording devices such as memory 312 can be transmitted to information processing system 230 via network 220. Conversely, user terminal 210 can receive control information or instructions provided by processor 334 of information processing system 230 via communication module 316 through communication module 336 and network 220.

[0085] Input / output interface 318 refers to a device used to connect input / output device 320. As an example, input devices may include devices with audio sensors and / or image sensors, such as cameras, keyboards, microphones, and mice; and output devices may include displays, speakers, haptic feedback devices, etc. As another example, input / output interface 318 can be an interface device for a device that integrates input and output functions, such as a touchscreen. For example, as the processor 314 of user terminal 210 executes computer program instructions loaded in memory 312, service screens and other data based on information and / or data provided by information processing system 230 or other user terminals can be displayed on the monitor through input / output interface 318. In Figure 3, although input / output device 320 is not included in user terminal 210, it is not limited to this and can also be integrated with user terminal 210 as a single device. Furthermore, the input / output interface 338 of the information processing system 230 can be connected to the information processing system 230, or it can be an interface device of any input / output device (not shown) that the information processing system 230 may include. In FIG3, although the input / output interfaces 318 and 338 are separated from the processors 314 and 334 as separate structural elements, this is not a limitation, and the input / output interfaces 318 and 338 may also be included within the processors 314 and 334.

[0086] Compared to the structural elements in Figure 3, the user terminal 210 and information processing system 230 may include more structural elements. In one embodiment, the user terminal 210 may include at least a portion of the input / output devices 320. Furthermore, the user terminal 210 may also include a transceiver, a Global Positioning System (GPS) module, a camera (e.g., a TrueDepth camera, an infrared camera, etc.), various sensors, a database, and other structural elements. For example, if the user terminal 210 is a smartphone, it may include structural elements typically found in smartphones, such as a fingerprint sensor (e.g., an optical fingerprint sensor, an ultrasonic fingerprint sensor, etc.), an accelerometer, a gyroscope sensor, a microphone module, a camera module, various physical buttons, buttons using a touchpad, output / output ports, a vibrator for vibration, and other structural elements.

[0087] During the operation of a program or application, the processor 314 can input or receive selected text, images, videos, voice and / or work through input devices such as a touch screen, keyboard, camera with audio sensor and / or image sensor, and microphone connected to the input / output interface 318. The processor can store the received text, images, videos, voice and / or work in the memory 312 or provide it to the information processing system 230 through the communication module 316 and the network 220.

[0088] The processor 314 of user terminal 210 can manage, process, and / or store information and / or data received from input / output device 320, other user terminals, information processing system 230, and / or multiple external systems. The information and / or data processed by processor 314 can be provided to information processing system 230 via communication module 316 and network 220. The processor 314 of user terminal 210 can transmit and output information and / or data to input / output device 320 via input / output interface 318. For example, processor 314 can output or display received information and / or data to a screen associated with user terminal 210.

[0089] The processor 334 of the information processing system 230 can manage, process, and / or store information and / or data received from multiple user terminals 210 and / or multiple external systems. The information and / or data processed by the processor 334 can be provided to the user terminals 210 through the communication module 336 and the network 220.

[0090] Figure 4 is an example diagram of a first login page 400 according to an embodiment of the present invention.

[0091] In one embodiment, the first login page 400 can be used to perform a first-type login. For example, the first login page 400 may include second input boxes 440 and 442 and a login button 444. The second input boxes 440 and 442 may include a second-type input box 440 for inputting first text and a second-type input box 442 for inputting second text. After inputting the first text and the second text, if input for selecting the login button 444 is received, the processor (e.g., at least one processor included in the information processing system 230 and / or user terminal 210 of FIG3) can identify a user account registered with an email address corresponding to the first text. If the user account is identified, the processor can determine whether the second text corresponds to the password of the identified user account. If the second text corresponds to the password, the user account login can be successful. If the second text does not correspond to the identified account password, or if the user account cannot be identified, the user account login can fail.

[0092] In one embodiment, the first login page 400 may include a retrieval button 450 for retrieving user account information. For example, if user input is received that selects the retrieval button 450, the processor can provide a page or widget for retrieving registration information related to the user account. The processor can provide information related to the user account's email address, password, etc., included in the registration information through prescribed verification steps, or it can provide it via other media.

[0093] In one embodiment, the first login page 400 may include a first region 410 and a third region 430. The processor may provide a second login page for performing a second type of login on the application based on user input selecting the first region 410. In the first region 410 of FIG4, the "fingerprint verification login" described is related to fingerprint verification, but is not limited to this. Besides fingerprints, the first region 410 may also be associated with at least one other biometric information such as iris, retina, hand shape, vein pattern, or voice pattern.

[0094] Furthermore, the processor can provide a third login page for performing a third type of login on the application based on user input that selects the third region 430.

[0095] In one embodiment, the first login page 400 may include a second area 420. The processor may provide a first input box associated with login type 1_1 or a second input box associated with login type 1_2 based on user input selecting the second area 420. Referring to FIG4, the processor may provide second input boxes 440 and 442 based on user input selecting the "email login" area in the second area 420. The processor may provide a first input box based on user input selecting the "phone number login" area in the second area 420. Referring to FIG1, a first login page including a first input box can be understood.

[0096] In one embodiment, the first login page 400 may include a fourth region 460, which includes a first region 410 and a third region 430. In another embodiment, the first login page may not include the fourth region 460. For example, a first login page may be provided when a user terminal performs a login for the first time. As another example, the user terminal may identify the user's biometric information and user account information pre-stored on the user terminal. If neither biometric information nor pre-stored user account information can be identified, a first login page excluding the fourth region 460 may be provided.

[0097] Figure 5 is an example diagram of a first login page 500 according to an embodiment of the present invention.

[0098] In one embodiment, the first login page 500 can be used to perform both Type 1_1 login and Type 1_2 login. For example, the first login page 500 may include a third input field 530 and a continue button 532 to receive information for identifying Type 1_1 login or Type 1_2 login. Text can be entered through the third input field 530. After entering text, if the processor receives input to select the continue button 532, it can determine whether the entered text corresponds to a mobile phone number or email address.

[0099] In one example, if the text meets the first rule (e.g., 11 digits), the processor can determine that the text is a mobile phone number. The processor can then identify the user account registered with the mobile phone number corresponding to the entered text. If the user account is identified, part of the login process can succeed. The processor can then provide an additional login page for further verification. The additional login page will be described in detail later with reference to Figure 7.

[0100] In another example, if the text satisfies the second rule (e.g., text containing "@"), the processor can determine that the text is an email address. The processor can identify a user account registered with an email address corresponding to the text entered as registration information. If the user account is identified, part of the login process can succeed. The processor can then provide a first login page, which also includes additional input fields for receiving additional text. The first login page, which also includes additional input fields, will be described in detail later with reference to FIG6.

[0101] In another example, if the text does not meet the first rule, the processor can determine that the text is not a phone number. Furthermore, if the text does not meet the second rule, the processor can determine that the text is not an email address. In this case, login may fail. The processor can output information to guide the user to enter an email address or phone number.

[0102] In one embodiment, the first login page 500 may include a first area 510 and a third area 520. The processor may provide a second login page for performing a second type of login on the application based on user input selecting the first area 510. Furthermore, the processor may provide a third login page for performing a third type of login on the application based on user input selecting the third area 520.

[0103] In one embodiment, the first login page 500 may include a retrieval button 540 for retrieving user account information. For example, if user input is received that selects the retrieval button 540, the processor can provide a page or widget for retrieving registration information related to the user account.

[0104] In one embodiment, the first login page 500 may include a fourth region 550, which includes a first region 510 and a third region 520. In another embodiment, the first login page may not include the fourth region 550. For example, a first login page may be provided when a user terminal performs a login for the first time. As another example, the user terminal may identify the user's biometric information and user account information pre-stored on the user terminal. If neither biometric information nor pre-stored user account information can be identified, a first login page excluding the fourth region 550 may be provided.

[0105] Figure 6 is an illustrative diagram of a first login page 600 according to an embodiment of the present invention. The first login page 600 may also include the additional input box 632 in the first login page 500 of Figure 5. Descriptions related to the structures repeated in Figure 5 may be omitted. Furthermore, the first login page 600 may replace the continue button 532 of the first login page 500 with a login button 634.

[0106] In one embodiment, text can be entered through an additional input field 632. After text is entered, if input is received via the login button 634, the processor can acquire the entered text. The processor can determine whether the entered text corresponds to a user account password. The determined user account password can be the password of a user account with an email address corresponding to the pre-entered text (e.g., the text entered in the third input field 530). If the entered text corresponds to a user account password, the user account login is successful. If the entered text does not correspond to a user account password, the user account login may fail.

[0107] Figure 7 is an example diagram of an additional login page 700 according to an embodiment of the present invention. In one embodiment, the processor obtains input information and can identify a user account registered with a mobile phone number corresponding to the input information. If the user account is identified, the processor can provide an additional login page 700.

[0108] In one embodiment, the processor may obtain a verification code. If a user account is identified, the processor may transmit a verification message including the verification code to a mobile terminal with a mobile phone number associated with the identified user account. An additional login page 700 may include information related to the mobile phone number.

[0109] In one embodiment, the additional login page 700 may include an input field 710 for receiving a verification code and a login button 730. After text is entered into the input field 710, if input is received to select the login button 730, the processor can compare the entered text with the verification code. If the entered text matches the verification code, the user account login is successful. If the entered text does not match the verification code, the user account login may fail.

[0110] In one embodiment, the additional login page 700 may include a resend button 720 for resending the verification message. If user input is received selecting the resend button 720, the processor may obtain a new verification code. Furthermore, the processor may transmit a new verification message including the new verification code to the mobile terminal.

[0111] In one embodiment, the additional login page 700 may include a movement button 740 for navigating to a login page for performing other types of logins. If user input selecting the movement button 740 is received, the processor can provide a first login page.

[0112] Figure 8 is an exemplary diagram of a second login page 800 according to an embodiment of the present invention. In one embodiment, before providing the first login page, the processor can provide a second login page 800 for performing a second type of login or a third login page for performing a third type of login on an application. Specifically, if the user terminal has pre-stored biometric information, the processor can provide a second login page 800. Alternatively, if the user terminal does not have pre-stored biometric information, the processor can provide a third login page.

[0113] In one embodiment, the processor may provide a second login page based on user input that selects a first area of ​​a first login page (e.g., first login page 130 of FIG1, first login page 400 of FIG4, first login page 500 of FIG5, and first login page 600 of FIG6).

[0114] In one embodiment, the processor may provide a widget for selecting a login method. The processor may provide a second login page 800 based on user input that selects a portion of the widget. The widget for selecting a login method will be described later with reference to FIG13.

[0115] In one embodiment, the second login page 800 may include a first area 810. In one example, the processor may provide the first login page based on user input selecting the first area 810. In yet another example, the processor may provide a widget for selecting a login method based on user input selecting the first area 810. Referring to FIG8, although "login using other methods" is stated in the first area 810, it is not limited to this. For example, "login using other accounts" may also be stated.

[0116] In one embodiment, the second login page 800 may include information 820 related to a user account. For example, information 820 may include information related to the email address of the user account included in the registration information. Furthermore, information 820 may include information for guiding users to perform a second type of login using their biometric information.

[0117] In one embodiment, the second login page 800 may include a login button 830. If user input is received selecting the login button 830, the processor may request the user's biometric information. For example, to obtain the user's biometric information, the processor may activate the input device of the user terminal. The processor may receive the user's biometric information through the input device. The processor may determine whether the biometric information included in the registration information corresponds to the biometric information used as input information. If it is determined that the input biometric information corresponds to the registered biometric information, the user account login may be successful. If it is determined that the input biometric information does not correspond to the registered biometric information, the user account login may fail.

[0118] Figure 9 is an example diagram of a third login page 900 according to an embodiment of the present invention.

[0119] In one embodiment, before providing the first login page, the processor can provide a second login page for performing a second type of login or a third login page 900 for performing a third type of login on an application. Specifically, if the user terminal has pre-stored biometric information, the processor can provide the second login page. Alternatively, if the user terminal does not have pre-stored biometric information, the processor can provide the third login page 900.

[0120] In one embodiment, after determining that no pre-stored biometric information exists, the processor may determine whether the user terminal has pre-stored user account information. If the user terminal has pre-stored user account information, the processor can provide a third login page 900. Alternatively, if the processor determines that no pre-stored user account information exists, it can provide a first login page.

[0121] In one embodiment, the third login page 900 may include a first area 910. In one example, the processor may provide the first login page based on user input that selects the first area 910. In yet another example, the processor may provide a widget for selecting a login method based on user input that selects the first area 910. Referring to FIG9, although "Login with another account" is stated in the first area 910, it is not limited to this. For example, "Login with another method" may also be stated.

[0122] In one embodiment, the third login page 900 may include information 920 related to the user account. For example, information 920 may include information related to the email address of the user account included in the registration information. The information 920 related to the user account may be information related to the user account pre-stored on the user terminal. For example, the user terminal may have a history of logins performed by the user account. The user terminal may pre-store the user account information obtained in advance in order to perform the corresponding login.

[0123] In one embodiment, the processor may enable a user account associated with information 920 to log in based on user input that selects a region corresponding to information 920. For example, in response to receiving user input, login for the corresponding user account may be successful. As another example, the processor may request information associated with the corresponding user account (e.g., the user account's password, etc.).

[0124] Figure 10 is an example diagram of a first login page 1000 according to an embodiment of the present invention.

[0125] In one embodiment, the first login page 1000 may include a first area 1010. In one example, the processor may provide a widget for selecting a login method based on user input that selects the first area 1010. Referring to FIG10, although "Login using other methods" is stated in the first area 1010, it is not limited to this. For example, "Login using other accounts" may also be stated.

[0126] In one embodiment, the first login page 1000 can be used to perform a Type 1_1 login. For example, the first login page 1000 may include a first input box 1030 and a continue button 1032. Text can be entered through the first input box 1030. After entering text, if input to the continue button 1032 is received, the processor can identify a user account registered with a mobile phone number corresponding to the text entered as registration information. If the user account is identified, part of the login process can be successful. The processor can then provide an additional login page for additional verification (e.g., the additional login page 700 of FIG. 7). If the user account cannot be identified, the login of the user account may fail.

[0127] In one embodiment, the first login page 1000 may include a second area 1020. The processor may provide a first input box 1030 related to login type 1_1 or a second input box related to login type 1_2 based on user input to the second area 1020. Referring to FIG10, the processor may provide a second input box based on user input selecting an "email login" area in the second area 1020. The processor may provide a first input box 1030 based on user input selecting a "phone number login" area in the second area 1020. Hereinafter, the first login page including the second input box will be described in detail with reference to FIG11.

[0128] Figure 11 is an example diagram of a first login page 1100 according to an embodiment of the present invention.

[0129] In one embodiment, the first login page 1100 may include a first area 1110. In one example, the processor may provide a widget for selecting a login method based on user input that selects the first area 1100. Referring to FIG11, although "Login using other methods" is stated in the first area 1110, it is not limited to this. For example, "Login using other accounts" may also be stated.

[0130] In one embodiment, the first login page 1100 can be used to perform a first-type login. For example, the first login page 1100 may include second input boxes 1130 and 1132 and a login button 1134. The second input boxes 1130 and 1132 may include a second-type input box 1130 for inputting first text and a second-type input box 1132 for inputting second text. After inputting the first text and the second text, if input is received to select the login button 1134, the processor can identify a user account registered through an email address corresponding to the first text. If the user account is identified, the processor can determine whether the second text corresponds to the password of the identified user account. If the second text corresponds to the password, the user account login can be successful. If the second text does not correspond to the password of the account or the user account cannot be identified, the user account login can fail.

[0131] In one embodiment, the first login page 1100 may include a retrieval button 1140 for retrieving user account information. For example, if user input is received that selects the retrieval button 1140, the processor can provide a page or widget for retrieving registration information related to the user account.

[0132] In one embodiment, the first login page 1100 may include a second area 1120. The processor may provide a first input box associated with login type 1_1 and a second input box 1130, 1132 associated with login type 1_2 based on user input selecting the second area 1120. Referring to FIG11, the processor may provide the second input boxes 1130, 1132 based on user input selecting the "email login" area in the second area 1120. The processor may provide a first input box (e.g., the first input box 1030 in FIG10) based on user input selecting the "mobile number login" area in the second area 1120.

[0133] Figure 12 is an example diagram of a first login page 1200 according to an embodiment of the present invention.

[0134] In one embodiment, the first login page 1200 may include a first area 1210. In one example, the processor may provide a widget for selecting a login method based on user input that selects the first area 1210. Referring to FIG12, although "Login using other methods" is stated in the first area 1210, it is not limited to this. For example, "Login using other accounts" may also be stated.

[0135] In one embodiment, the first login page 1200 can be used to perform a Type 1_1 login. For example, the first login page 1200 may include a first input box 1220 and a login button 1222. Text can be entered through the first input box 1220. After entering text, if input to select the login button 1222 is received, the processor can identify a user account registered with a mobile phone number corresponding to the text entered as registration information. If the user account is identified, part of the login process can be successful. Subsequently, the processor can provide an additional login page for additional verification (e.g., the additional login page 700 of FIG. 7). If the user account cannot be identified, the login of the user account may fail.

[0136] Figure 13 is an example diagram of a first login page 1300 according to an embodiment of the present invention.

[0137] In one embodiment, the first login page 1300 may include a first area 1310. In one example summary, the processor may provide a widget for selecting a login method based on user input that selects the first area 1310. Referring to FIG13, although "login using another method" is described in the first area 1310, it is not limited thereto. For example, "login using another account" may also be described, etc.

[0138] In one embodiment, the first login page 1300 can be used to perform a first-type login. For example, the first login page 1300 may include second input fields 1320 and 1322 and a login button 1324. The second input fields 1320 and 1322 may include a second-type input field 1320 for inputting first text and a second-type input field 1322 for inputting second text. After inputting the first text and the second text, if input to select the login button 1324 is received, the processor can identify a user account registered through an email address corresponding to the first text. If the user account is identified, the processor can determine whether the second text corresponds to the password of the identified user account. If the second text corresponds to the password, the user account login can be successful. If the second text does not correspond to the password or the user account cannot be identified, the user account login can fail.

[0139] In one embodiment, the first login page 1300 may include a retrieval button 1330 for retrieving user account information. For example, if user input is received that selects the retrieval button 1330, the processor may provide a page or widget for retrieving registration information related to the user account.

[0140] Figure 14 is an exemplary diagram of a widget 1400 according to an embodiment of the present invention. In one embodiment, the widget 1400 may be configured on a login page (e.g., a first login page, a second login page, a third login page). However, it is not limited to this, and the widget 1400 may be configured on other pages. Furthermore, the widget 1400 may be provided in various ways, such as through a page.

[0141] In one embodiment, widget 1400 can be provided in a variety of ways. For example, widget 1400 can be provided based on user input that selects a first area of ​​a first login page (e.g., first area 1010 in FIG. 10, first area 1110 in FIG. 11, first area 1210 in FIG. 12, first area 1310 in FIG. 13, etc.). As another example, widget 1400 can be provided based on user input that selects a first area of ​​a second login page (e.g., first area 810 in FIG. 8). As yet another example, widget 1400 can be provided based on user input that selects a first area of ​​a third login page (e.g., first area 910 in FIG. 9). As yet another example, widget 1400 can be provided when a user terminal initially accessing the application performs a login for the first time.

[0142] In one embodiment, widget 1400 can be used to select a login method. For example, a first login page for performing a first type of login can be provided based on input selecting a first region 1410, 1412 of widget 1400. Specifically, a first login page for performing a first type of login can be provided based on input selecting a first region 1410 of widget 1400 (e.g., first login page 1000 of FIG. 10, first login page 1200 of FIG. 12, etc.). A first login page for performing a first type of login can be provided based on input selecting a first region 1412 of widget 1400 (e.g., first login page 1100 of FIG. 11, first login page 1300 of FIG. 13, etc.). A second login page for performing a second type of login can be provided based on input selecting a second region 1420 of widget 1400 (e.g., second login page 800 of FIG. 8, etc.). A third login page (e.g., the third login page 900 in Figure 9) for performing a third type of login can be provided based on input that selects the third region 1430 of the widget 1400.

[0143] Figure 15 is an exemplary flowchart 1500 of a user account management method according to an embodiment of the present invention. The user account management method may be executed by a processor (e.g., at least one processor included in the user terminal and / or information processing system of Figure 3).

[0144] User account management methods may begin by providing a first login page for performing a first type of login on an application (step S1510). For example, the first type of login may include type 1_1 login and type 1_2 login.

[0145] In one embodiment, the processor may provide a first input box associated with type 1_1 login or a second input box associated with type 1_2 login based on user input that selects a second area of ​​the first login page.

[0146] In one embodiment, the first login page may include a third input field to receive information for identifying type 1_1 login or type 1_2 login.

[0147] In one embodiment, before providing the first login page, the processor may provide a second login page for performing a second type of login on the application or a third login page for performing a third type of login on the application. The third type of login is associated with pre-stored user account information, which may be associated with a user.

[0148] In one embodiment, if the user terminal receiving the application has pre-stored biometric information, the processor can provide a second login page. Alternatively, if the user terminal does not have pre-stored biometric information, the processor can provide a third login page.

[0149] In one embodiment, based on the determination that the user terminal receiving the application does not have pre-stored biometric information and pre-stored user account information related to the user, the processor can provide a first login page.

[0150] In one embodiment, before providing the first login page, the processor may provide a second login page for performing a second type of login on the application. The processor may provide the first login page based on user input that selects a first area of ​​the second login page.

[0151] In one embodiment, prior to providing the first login page, the processor may provide a second login page for performing a second type of login on the application. The processor may provide a widget for selecting a login method based on user input selecting a first area of ​​the second login page. The processor may provide the first login page based on user input selecting a first area of ​​the widget.

[0152] In one embodiment, before providing the first login page, the processor may provide a third login page for performing a third type of login on the application. The processor may provide the first login page based on user input that selects a first area of ​​the third login page.

[0153] In one embodiment, prior to providing the first login page, the processor may provide a third login page for performing a third type of login on the application. The processor may provide a widget for selecting a login method based on user input selecting a first area of ​​the third login page. The processor may provide the first login page based on user input selecting a first area of ​​the widget.

[0154] In one embodiment, the processor may provide a widget for selecting a login method. The processor may provide a first login page based on user input that selects a first area of ​​the widget.

[0155] The processor may provide a second login page for performing a second type of login on the application based on user input that selects a first area of ​​the first login page (step S1520). The second type of login may be associated with utilizing the user's biometric information. The first type of login may be different from the second type of login. For example, the biometric information may include information pre-stored on the user's terminal receiving the application.

[0156] In one embodiment, the processor may provide a widget for selecting a login method based on user input that selects a first area of ​​a first login page. The processor may provide a second login page based on user input that selects a second area of ​​the widget.

[0157] Figure 16 is an illustrative flowchart 1600 of a user account management method according to an embodiment of the present invention.

[0158] User account management methods may begin by providing a first login page for performing a first type of login on the application (step S1610).

[0159] In one embodiment, the processor may provide a third login page for performing a third type of login on the application based on user input that selects a third area of ​​the first login page (step S1620). The third type of login is associated with pre-stored user account information, which may be associated with a user. The first type of login may be different from the third type of login. For example, the pre-stored user account information may include information pre-stored on the user's terminal receiving the application.

[0160] In one embodiment, the processor may provide a widget for selecting a login method based on user input that selects a third area of ​​the first login page. The processor may also provide a third login page based on user input that selects a third area of ​​the widget.

[0161] To enable a computer to execute the method, it can be provided by a computer program stored on a computer-readable recording medium. The medium can also be temporary storage for continuously storing, executing, or downloading a computer executable program. Furthermore, the medium can be a combination of various recording or storage units composed of one or more hardware components, and is not limited to media that directly access any computer system; it can also be distributed across a network. As examples, the medium includes magnetic media such as hard drives, floppy disks, and magnetic tapes; optical recording media such as CD-ROMs and DVDs; magneto-optical media such as floppy disks; and structures storing program instructions such as ROM, RAM, and flash memory. Furthermore, as another example, the medium can be a recording or storage medium managed by an application store that sells applications, or a website or server that provides and sells various other software.

[0162] The methods, operations, or techniques of this invention can be implemented by various units. For example, the techniques can also be implemented by hardware, firmware, software, or a combination thereof. In relation to the disclosure of this invention, those skilled in the art should understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described can also be implemented by electronic hardware, computer software, or a combination thereof. To clearly illustrate this interchangeability between hardware and software, various exemplary structural elements, blocks, modules, circuits, and steps have been simply described above from a functional perspective. However, whether such functionality is implemented by hardware or software depends on the design requirements of the specific application and the overall system. Those skilled in the art can also implement the described functions in various ways for each specific application; therefore, such implementations should not be construed as departing from the scope of this invention.

[0163] In hardware instances, the processing unit for executing the technology may also be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), graphics processing units (GPUs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions of the present invention, computers, or combinations thereof.

[0164] Therefore, the various exemplary logic blocks, modules, and circuits described in conjunction with this invention can also be implemented or executed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete logic gates or transistor logic, discrete hardware components, or any combination designed to perform the functions of this invention. The general-purpose processor can be a microprocessor; alternatively, the processor can also be any processor, controller, microcontroller, or state machine. The processor can also be implemented by a combination of computing devices, such as a digital signal processor, a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processing chip, or any other combination of structures.

[0165] In firmware and / or software instances, the technology may also be implemented by instructions stored on computer-readable media such as random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc (CD), magnetic or optical data storage devices. The instructions may be executed by one or more processors, or may cause processors (multiple processors) to perform the functions described herein according to a specific implementation.

[0166] When implemented in software, the technology can be used to store or transmit one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, including any medium that facilitates the transfer of computer programs from one location to another. Storage media can also be any available medium accessible to a computer. As a non-limiting example, such computer-readable media may include random access memory, read-only memory, electrically erasable programmable read-only memory, CD-ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other computer-accessible medium used to transfer or store prescribed program code in the form of instructions or data structures. Furthermore, any access can be appropriately performed by the computer-readable medium.

[0167] For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, stranded wire, digital subscriber line (DSL), or wireless technologies such as infrared, wireless, and microwave, then coaxial cable, fiber optic cable, stranded wire, digital subscriber line (DSL), or wireless technologies such as infrared, wireless, and microwave are included within the definition of media. In this application, the terms "disk" and "disc" include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically reproduce magnetic data, while discs utilize lasers to reproduce optical data. The combinations described are also included within the scope of computer-readable media.

[0168] The software module can reside within random access memory, flash memory, read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, cache, hard disk, removable disk, CD-ROM, or any known form of storage medium. As an example, the storage medium is connected to a processor so that the processor reads information from or records information to the storage medium. Alternatively, the storage medium can be integrated into the processor. The processor and storage medium can also reside within a dedicated integrated circuit. The dedicated integrated circuit can also reside within a user terminal. Alternatively, the processor and storage medium can also exist as separate structural elements within the user terminal.

[0169] In the embodiments described above, although the currently disclosed main implementation method can be applied through one or more independent computer systems, the present invention is not limited thereto, and can also be implemented in any computing environment such as a network or a distributed computing environment. Furthermore, the main implementation method of the present invention can also be implemented by multiple processing chips or devices, and storage can be similarly affected by multiple devices. Such devices may also include personal computers, network servers, and portable devices.

[0170] While this specification describes content related to certain embodiments, those skilled in the art can make various modifications and alterations without departing from the scope of this invention. Furthermore, such modifications and alterations also fall within the scope of the appended patent applications.

[0171] 110: User 120: User Terminal 130: First login page 131: Area 1 132: Second Area 134: Third Region 136: First input box 138: Login button 139: Fourth Region

Claims

1. A user account management method, executed by at least one processor, wherein, The process includes the following steps: determining whether the user's biometric information is pre-stored on the user terminal receiving the application; if the biometric information is determined not to be pre-stored on the user terminal, determining whether user account information associated with the user is pre-stored on the user terminal; if the user account information is determined not to be pre-stored on the user terminal, providing a first login page for performing a first type of login on the application; and if the biometric information is determined to be pre-stored on the user terminal, providing a second login page for performing a second type of login on the application, wherein the second type of login is related to utilizing the user's biometric information, and the first type of login and the second type of login are different from each other.

2. As in request item 1, the user account management method, wherein, The biometric information includes information pre-stored on the user terminal.

3. As in request item 1, the user account management method, wherein, The first type of login includes type 1_1 login and type 1_2 login. The step of providing the first login page includes the following steps: based on the user input of selecting the second page of the first login page, providing a first input box related to type 1_1 login or a second input box related to type 1_2 login.

4. As in request item 1, the user account management method, wherein, The first type of login includes type 1_1 login and type 1_2 login. The first login page includes a third input box to receive information for identifying type 1_1 login or type 1_2 login.

5. The user account management method as described in request item 1, wherein the method further includes: If the biometric information is determined not to be pre-stored on the user terminal, and the user account information is determined to be pre-stored on the user terminal, then a third login page for performing a third type of login on the application is provided. The third type of login is related to the pre-stored user account information, and the user account information is related to the user.

6. As in request item 1, the user account management method, wherein, The steps of providing the second login page include the following steps: providing the first login page based on user input that selects a first area of ​​the second login page.

7. As in request item 1, the user account management method, wherein, The steps of providing the second login page include the following steps: providing a widget for selecting a login method based on user input that selects a first area of ​​the second login page; and providing the first login page based on user input that selects a first area of ​​the widget.

8. As in request item 5, the user account management method, wherein, The steps of providing the third login page include the following steps: providing the first login page based on user input that selects a first area of ​​the third login page.

9. As in request item 5, the user account management method, wherein, The steps of providing the third login page include the following steps: providing a widget for selecting a login method based on user input that selects a first area of ​​the third login page; and providing the first login page based on user input that selects a first area of ​​the widget.

10. The user account management method as described in request item 1, wherein, The steps of providing the first login page include the following steps: providing a widget for selecting a login method; and providing the first login page based on user input that selects a first area of ​​the widget.

11. As in request item 1, the user account management method, wherein, The steps of providing the first login page include the following steps: providing a widget for selecting a login method based on user input that selects a first area of ​​the first login page; and providing the second login page based on user input that selects a second area of ​​the widget.

12. As in request item 5, the user account management method, wherein, The steps of providing the first login page include the following steps: providing a widget for selecting a login method based on user input that selects a third area of ​​the first login page; and providing the third login page based on user input that selects a third area of ​​the widget.

13. A computer-readable recording medium, wherein, The record contains instructions for performing any of the methods requested in Request 1 to 12 on the computer.

14. An information processing system, wherein, include: Memory; The system also includes at least one processor connected to the memory for executing at least one computer-readable program included in the memory, the at least one program including instructions to perform the following steps: determining whether a user's biometric information is pre-stored on a user terminal receiving the application; if the biometric information is determined not to be pre-stored on the user terminal, determining whether user account information associated with the user is pre-stored on the user terminal; if the user account information is determined not to be pre-stored on the user terminal, providing a first login page for performing a first type of login on the application; and if the biometric information is determined to be pre-stored on the user terminal, providing a second login page for performing a second type of login on the application, the second type of login being associated with utilizing the user's biometric information, and the first type of login and the second type of login being different from each other.

Images