TWI912420B - A method for managing member information and an apparatus for the same - Google Patents

Abstract

A method for managing member information includes at least one among confirming whether a login is performed on a first application, confirming whether to log in on the first application using information on a user of the first application from the user, confirming whether a authentication procedure of the first application is performed from the user using information on the user of a second application, confirming whether the second application is installed in a terminal device of the user, and confirming whether the user is logged in using member information with respect to the second application.

Description

Methods for managing member information and the equipment used for it

This invention relates to a method and apparatus for integrating and managing member information. More specifically, this invention relates to a method and apparatus for integrating and managing member information using an integrated authentication process.

Single Sign-On (SSO) is a system that allows users to register for multiple sites or services with a single login. It gains attention because users can easily access multiple sites or services without having to enter large amounts of personal information. In the case of individuals, the inconvenience of having to record personal information (such as a name, phone number, ID, and password) for each site to access them is eliminated in a single operation. Companies can maximize marketing by implementing integrated member management.

In this regard, as a patent document in the relevant field, there is Korean Patent No. 10-2157743 (September 14, 2020).

[Technical Objectives]

OneState provides a method and equipment for integrating and managing member information.

More specifically, a single sign-on (SSO) solution provides a method and equipment for simplifying the authentication process of multiple service applications that provide different services through a single sign-on (SSO) connection, and for sharing necessary information among these services via a single server. [Technical Solution]

According to one embodiment, a method for managing member information is provided, comprising: confirming whether a login is performed on a first application; confirming whether a login is performed on the first application using login information from the user regarding the first application; confirming whether an authentication process of the first application is performed by the user using the login information regarding a second application; confirming whether the second application is installed on a terminal device of the user; and confirming whether the user is logged in using member information regarding the second application.

According to the example implementation, the method for managing member information may include performing an authentication process on the first application based on the member information about the second application.

According to the embodiments, the method for managing member information may include providing the first application with information about the user based on the member information about the second application.

A method for managing member information may include providing the user's terminal with a page for performing a member registration process on the first application when the user determines that the login information of the second application has been used to log in to the first application.

The method for managing member information may further include providing a second application installation page to the user terminal when the second application is not installed on the user terminal.

According to the example implementation, performing the authentication process on the first application based on the member information of the second application includes: generating a Single Sign-On (SSO) login token and transmitting the SSO login token to the user's first application; receiving an access token and the SSO login token from the second application, which is different from the first application; confirming whether the user is a member of the second application based on the access token of the second application; when the user is a member of the second application, transmitting a membership confirmation success signal to the second application, receiving the SSO login token from the first application; and transmitting an access token of the first application to the first application.

According to the example embodiment, providing the first application with information about the user based on the member information of the second application may include: receiving an SSO symbol and a request for user information from the user's terminal; confirming whether the SSO symbol is a valid symbol for the user; and confirming the information about the user based on the SSO symbol and transmitting the information about the user. [Effect]

According to the embodiment of the electronic device, the integrated process can be used to perform the authentication process for the user, without the need for separate authentication processes for each of the plurality of applications, thereby simplifying the process required for the user to perform a login.

Based on the SSO notation, electronic devices in the example implementation can share storage for the use and management of various services by various applications, thereby minimizing the re-entry of unnecessary information in the process of providing various services to the user, thereby reducing user confusion.

Furthermore, the electronic device according to the embodiment can share the storage for the use and management of each application of each service based on the SSO symbol, so that information about the user can be managed as a whole for each interactive service, and since the information about the user is based on a taste or a purchase history, a personalized and differentiated service can be provided to the user.

The following description, with reference to the accompanying figures, will provide a detailed example of the embodiments of the invention.

When describing examples and embodiments, descriptions of technical contents well-known in the art field to which this invention pertains but not directly related to this invention will be omitted. This is to more clearly convey the main idea of this invention, without obscuring the main idea of this invention by omitting unnecessary descriptions.

For the same reason, some components are exaggerated, omitted, or shown schematically in the accompanying drawings. Furthermore, the sizes of the components do not necessarily reflect their actual sizes. In each drawing, identical or corresponding components are assigned the same component symbol.

The advantages and features of the present invention, and the manner in which they are achieved, will be understood with reference to the embodiments described in detail below in conjunction with the accompanying drawings. However, the present invention can be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. The embodiments are provided to make the present invention completely and fully convey the scope of the invention to those skilled in the art, and the present invention is defined only by the scope of the appended patent claims. Throughout the present invention, the same reference numerals refer to the same components.

In this context, it will be understood that the blocks of a flowchart and the combination of flowcharts can be executed by computer program instructions. These computer program instructions may be embodied in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that instructions executed by the processor of the computer or other programmable data processing device produce portions for performing the functions described in (a few) flowchart blocks. These computer program instructions may be used by a computer or other programmable data processing device to implement a function in a particular manner or may be stored in a computer-readable memory, and thus the use of the computer or instructions stored in the computer-readable memory can produce an article of manufacture containing instruction components for performing the functions described in (a few) flowchart blocks. Since computer program instructions can also be embedded in a computer or other programmable data processing device, these instructions perform a series of operations on the computer or other programmable data processing device to produce a computer execution process, thereby operating the computer or other programmable data processing device to provide operations for performing the functions described in (a few) flowchart blocks.

Additionally, each block may represent a portion of a module, segment, or code, containing one or more executable instructions for performing one or more specified logical functions. It should also be noted that in some alternative embodiments, the functions mentioned in a block may appear out of order. For example, two consecutively displayed blocks may be executed in practically parallel order, or sometimes, two blocks may be executed in reverse order according to their corresponding functions.

In this context, the term "~part" as used in the embodiments refers to a software or hardware component, such as a field-programmable gate array (FPGA) or a dedicated integrated circuit (ASIC), performing a predetermined role. However, the term "~part" is not limited to either software or hardware. A "~part" can be formed by storing in an addressable storage medium or by reproducing one or more processors. Therefore, as an example, a "~part" includes components such as software components, object-oriented software components, class components, and task components, as well as the procedures, functions, attributes, processes, subroutines, segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables of code. The functions provided in the components and "~parts" can be combined into a smaller number of components and "~parts" or can be further divided into additional components and "~parts". In addition, the components and "~parts" can be implemented as one or more central processing units (CPUs) in a device or a secure multimedia card.

Figure 1 is a diagram illustrating one example of the internal components of an electronic device according to one embodiment.

Referring to Figure 1, the internal components of an electronic device 100 are not limited to those shown. The electronic device 100 may include at least one of a processor 110, a transceiver 120, and a memory 130.

Processor 110 can process a series of operations for performing a method for managing the feeding of information of an article according to various embodiments of the present invention. Processor 110 can control other components of electronic device 100. An article can be sold to a user in connection with a service of electronic device 100.

Processor 110 may perform at least one of the following: confirming whether a registration is performed on a first application; confirming whether a user is registered on the first application based on user information about the first application; confirming whether an authentication process of the first application is performed based on user information about the second application; confirming whether the second application is installed on a user's terminal device; and confirming whether the user is registered using membership information about the second application. A program or computer-readable command executed by processor 110 may be pre-stored in memory 130 or received externally via transceiver 120. Processor 110 may provide a first page to a display of electronic device 100.

The transceiver 120 can perform one of the functions of transmitting information stored in the memory 130 of the electronic device 100 or information processed by the processor 110 to another device or receiving information from another device to the electronic device 100.

Memory 130 is a component implemented in a predetermined storage space of electronic device 100 and may include a database in which functions such as storing, searching, deleting, editing, and adding data can be freely executed. For example, memory 130 may include fields or components for processing functions (such as storing, searching, deleting, editing, and adding data). Memory 130 may store data related to electronic device 100 performing an information provision method. For example, memory 130 may store instructions or data for performing operations of processor 110. According to an embodiment, memory 130 may include a database for storing information about items.

An electronic device according to an example embodiment can manage member information for a service. The member information according to the example embodiment includes, for example, information that can identify a user of a corresponding service or information that can authenticate a user. For example, member information may include an identity (ID) for a corresponding user and a password used to access a service using that ID.

For each application service, the member information may be presented differently according to the embodiments. For example, the member information of an application operating a platform that orders food and delivers it to a user's location (hereinafter, it may refer to a first application or a first application service) may be different from the member information of an application operating a platform that searches for, purchases, pays for, and delivers an item to a user's location (hereinafter, it may refer to a second application or a second application service). Meanwhile, in one embodiment, the first application is described as performing a function related to food delivery, but the invention is not limited thereto, and the first application may be an application that retrieves an item from a specific location based on a customer's order and delivers the item to the customer's location.

The electronic device according to the embodiment can store information about a user who subscribes to an application service in memory 130 according to the embodiment and can manage the information about the user stored in memory 130. The information about the user may include, for example, at least one of the following: information about the user's name, information about the user's item delivery address, information about the user's item order history, and information about the user's item search history.

Due to reasons such as personal information storage policies and security considerations related to personal information, the electronic device according to the embodiment may store user information separately for each application service. For example, the electronic device may include a first storage device for use in a first application (a first application service) operating a first service and a second storage device for use in a second application (a second application service) operating a second service. That is, the electronic device may include a plurality of databases or a plurality of tables, and each database or table may contain at least one of membership information about the user and information about the user (e.g., personal information and information about the delivery of an item), which are used in one application service. That is, the electronic device according to the embodiment may include a separate storage device for various services provided by the electronic device (e.g., an application of a terminal device). Additionally, the electronic device according to the embodiment may, according to a separate authentication process, use a terminal device according to the embodiment for various services and a storage device (e.g., a database) associated with the electronic device.

For example, a first storage device for operating a first application of a platform for ordering food and delivering food to a user's location may include at least one of the following: first member information about a user of a first service, first location information for indicating the location of a seller of food, the seller's name and price of an item (food), information about the courier who delivers the goods when the user orders the item, and first delivery location information for indicating the user's delivery location.

For example, a second storage device for a second application of a platform for delivering items to a user's location by searching, purchasing, and paying for items may include at least one of the following: membership information for a user of a second service; information about the fulfillment center where the items are stored; a name and a price of each item stored in a server of the second application; and second delivery location information for indicating the user's delivery location.

When the first application is executed, in order to use the information about the user stored in the first storage device and used in the first application service, the user's terminal device according to the embodiment can use the electronic device according to the embodiment to perform an authentication process on the first application. That is, based on an access token of the first application generated after the authentication process of the first application is completed, the electronic device according to the embodiment can provide the information about the user stored in the first storage device to the first application. Similarly, when the second application is executed, in order to use the information about the user stored in the second storage device and used in the second application service, the user's terminal device according to the embodiment can use the electronic device according to the embodiment to perform an authentication process on the second application. That is, based on an access token for the second application generated after the authentication process of the second application is completed, the electronic device according to the embodiment can provide information about the user stored in the second storage device to the second application.

On the other hand, in an electronic device providing multiple services, when a separate authentication process is performed for each service and the terminal device (e.g., when the electronic device generates access tokens for a first application and access tokens for a second application, and the user's terminal device retrieves information about the user from the electronic device based on a single token), because the user bears the burden of the process and information about the user is retrieved separately for each application based on a single token for each application, it can be difficult to share information commonly required by the services among the applications. Furthermore, because overlapping data between services is separated and stored, it is inefficient in terms of storage space.

Accordingly, the electronic device according to the embodiment can perform an effective integrated authentication process in the second application (service), thereby simplifying the authentication process of the first application. Furthermore, the electronic device according to the embodiment uses an effective integrated authentication process between the second applications (and an authentication symbol generated by the effective authentication process for the second application) to perform the authentication process between the first applications in a simplified manner. Additionally, through the aforementioned integrated authentication process, the first application according to the embodiment can receive and share member information (or user information) used in the second application. Examples of the operation and configuration of the electronic device performing the above method will be described below.

Figure 2 is a flowchart illustrating one example of a method for managing member information based on a specific implementation example.

The electronic device according to the embodiment can perform some or all of the operations shown in Figure 2 for managing member information. Specifically, Figure 2 illustrates one example of an operation of managing member information by the electronic device according to the embodiment. For example, Figure 2 illustrates performing a login process for a first application to perform a login operation for the first application, or using login information for a second application to perform a login process operation for the first application. Referring to Figure 2, the electronic device according to the embodiment can perform at least one of operations 200 to 204c.

All operations of the example embodiment shown in Figure 2 can be performed by the electronic device according to the example embodiment, and some operations can be performed by the user's terminal device.

The electronic device according to the embodiment can verify whether a registration (authentication of the first application between the electronic device and the user's terminal device) has been legally performed on the first application (200). For example, the user's terminal device according to the embodiment responds to an execution signal from the user's first application to execute the first application. The electronic device according to the embodiment can verify whether session information indicating legal authentication of the first application exists in the user's terminal device. That is, the electronic device can verify whether the user's terminal device has completed registration on the first application (200). In the user's terminal device according to the embodiment, when the registration of the first application has been performed, the user's terminal device may have an access token generated from the electronic device to the first application (e.g., a first application server in the electronic device).

When a user is in a state where registration on the first application is complete (i.e., authentication of the first application has been performed between the electronic device and the user's terminal device), the electronic device according to the embodiment can provide information about the user to the first application based on the membership information of the first application (200a). The electronic device according to the embodiment receives an access token from the user's terminal device to the first application and uses the received access token to confirm the membership information about the user. The electronic device provides information about the user based on the confirmed membership information (200a). In this case, the information about the user according to the embodiment may refer to the information about the user confirmed by the membership information of the first application in the electronic device according to the embodiment.

When a user is in a state where no login has been performed on the first application (i.e., when no authentication of the first application has been performed between the electronic device and the user's terminal device), the electronic device according to the embodiment can use the login information of the first application to confirm whether the user has performed a login (201). For example, the login information is information received by the user's terminal device from the user and may refer to information about the user performing an authentication process for a peer application service. The login information may include, for example, ID information, email information, and password information used to perform an authentication process for a peer application service. The electronic device according to the embodiment can request a query from the user's terminal device to confirm whether the user has performed a login using the login information of the first application.

When a user chooses to log in using the login information of the first application, the electronic device in the example embodiment confirms the login information. The electronic device may confirm the user's membership information in the first application based on the login information and may perform a login process based on the confirmed membership information of the first application (201a). For example, the electronic device may confirm the user's membership information for the first application, perform the first application based on the confirmed membership information, and provide information about the user to the first application (200a). The membership information of the first application may be included in, for example, a first storage device of the first application.

When a user does not choose to use the login information of the first application to perform login, the electronic device according to the embodiment can confirm whether the user has used the login information of the second application to perform login on the first application (202). For example, when a user chooses to use the login information of the second application to perform login on the first application, the electronic device can confirm the user's membership information of the second application from the second storage device based on the login information entered by the user in the second application.

On the other hand, when a user chooses not to use the login information of the second application to perform login on the first application, the electronic device may perform a member registration process to generate member information of the first application in the first storage device (202a) or may provide the first application in a state where authentication is not completed. However, when the user continues and completes the member registration process of the first application, the electronic device according to the example embodiment may use the newly entered member information of the first application by the user to provide the first application and may provide information about the user to the first application (200a).

When a user chooses to use the login information of the second application to perform login on the first application, the electronic device (or the user's terminal device) according to the embodiment can confirm whether the second application is installed on the user's terminal device (203). When the second application is not installed on the user's terminal device, the electronic device according to the embodiment can provide the user's terminal device with a page for installing the second application (203a). When the second application is not installed on the user's terminal device, the user's terminal device according to the embodiment can search for and confirm the second application in an app store in order to install the second application.

When the second application is installed on the user's terminal device, the electronic device according to the embodiment can request or control the user's terminal device to execute the second application.

On the other hand, when the second application is installed on the user's terminal device, the electronic device according to the embodiment can use the registration information of the second application to confirm whether the user has registered on the second application (204). For example, the second application according to the embodiment can confirm whether an access token (or session) to the second application is stored in the user's terminal device and confirm through the electronic device whether the stored access token or session is valid.

When a user is not currently logged into the second application (i.e., when there is no authentication between the electronic device and the user's terminal device for the second application), the electronic device according to the embodiment can provide the user's terminal device with a login page of the second application to perform the login process for the second application (204a). When a user is currently logged into the second application, the electronic device according to the embodiment can query the user's membership information for the second application. Based on the queried membership information for the second application, the electronic device according to the embodiment can perform an integrated login process (an integrated authentication process) for the first application (204b). An integrated login process (integrated authentication process) refers to a process in which, when a user legitimately executes an authentication process based on the authentication process of a specific application, an authentication process is then executed on another(s) applications based on the result of that successful authentication process. The integrated authentication process will be described in detail with reference to, for example, Figures 4 and 5. When the integrated authentication process is legitimately executed with the user's terminal device, the electronic device, according to an example embodiment, can provide the user's terminal device with a Single Sign-On (SSO) token, and the user's terminal device can store the SSO token. According to the example embodiment, multiple applications associated with the user's terminal device can perform an authentication process based on the SSO symbol of the example embodiment and share data contained in the storage device associated with the electronic device based on the SSO symbol.

According to the embodiment of the electronic device, the information required during the integration registration process of the first application can be confirmed from the member information of the second application as queried. According to the embodiment of the electronic device, the information that cannot be confirmed from the member information of the second application in the necessary information can be received by the user and the information can be queried and obtained from other applications (some) other than the first and second applications.

On the other hand, through the process described above throughout the exemplary embodiments, a customer subscribing to the second application can register on the first application, where the customer is not registered, using the registration information for the second application. Therefore, the electronic device managing the first application can obtain at least a portion of the user information for the second application and use the obtained information as customer information for the first application. Thus, based on the subscription information for the second application, a separate registration process for the first application is unnecessary. Furthermore, a first set of information can be shared between the two applications, and a second set of information can be managed independently in the two applications. For example, the first set of information may include points information, and the second set of information may include delivery destination information. However, when an initial login is performed on the first application, some information included in the second group can be set based on the information entered into the second application, and the information included in the second group can be corrected or added separately in the first application after the initial setup.

After performing the above-described integrated authentication process, the electronic device according to the example embodiment can provide the user's terminal device with information about the user of the first application based on the membership information about the second application (204c).

According to the embodiment, the electronic device can use an integrated process to perform the authentication process for the user, instead of requiring separate authentication processes for each of multiple applications, thereby simplifying the process required for the user to log in.

Figure 3 is a diagram illustrating one example of a user interface for managing member information, based on an example implementation.

Specifically, Figure 3 illustrates one method of performing an authentication process for the first application based on member information about the second application. Some or all of the operations according to the example embodiments shown in Figure 3 can be performed by an electronic device. For example, some or all of the operations according to the example embodiments shown in Figure 3 can correspond to some or all of operations 200 to 204c in Figure 2.

Figure 3A illustrates a scenario where a user is executing a first application on a user's terminal device, showing a state where the user is not logged in to the first application on the user's terminal device. For example, Figure 3A could illustrate a scenario where, in operation 200 of Figure 2, login to the first application is not currently being performed.

Referring to Figure 3A, the electronic device according to the embodiment can request the user's terminal device to register on the first application. In order to register on the first application, the electronic device according to the embodiment can use registration information about the second application to determine whether to perform registration on the first application (300a).

Meanwhile, according to the embodiment, a user may attempt to log in to the first application using login information different from the membership information for the second application. Accordingly, in order to allow the user to attempt to log in to the first application using login information different from the login information for the second application, the electronic device according to the embodiment can directly receive login information for the second application from the user and can confirm whether to log in on the first application (300b).

In addition, in order to register on the first application, the electronic device according to the embodiment can determine whether to perform a registration on the first application (300c) or to perform registration using registration information about the first application.

According to an embodiment of the user's terminal device, a first area 300-1 for querying a login method from the user can be displayed on a page 300 of the first application. According to an embodiment of the first area 300-1, at least one of the following may be included: a first interface 300a for confirming whether to log in to the first application using login information about the second application (300a) in order to log in to the first application; a second interface 300b for confirming whether to perform a login to the first application by directly receiving login information about the second application from the user (300b); a third interface for confirming whether to perform a login to the first application (300c); and a fourth interface for confirming whether to perform a login using login information about the first application.

Figure 3B illustrates the example implementation of moving from the first application to the homepage of one of the second applications and performing one of the operations of the first application.

The page shown in Figure 3B can be a page displayed when the second application is executed. Specifically, the page can be a page displayed when the user selects to log in to the first application using the login information for the second application (300a). That is, when the user clicks the first interface 300a in Figure 3A, the user's terminal device or electronic device according to the embodiment can execute the second application (e.g., operation 203 in Figure 2) (when the second application is installed on the user's terminal device). On the other hand, when the user clicks the first interface 300a, but the second application is not installed on the user's terminal device, the electronic device according to the embodiment can provide the user's terminal device with an installation page for the second application (e.g., operations 203 and 203a in Figure 2).

When the second application according to the embodiment is executed by the user's terminal device, the electronic device according to the embodiment or the user's terminal device can provide a fifth interface 301a for querying whether to attempt to register using the registration information about the second application in order to register on the first application. When the user clicks the fifth interface 301a, the electronic device according to the embodiment can perform an authentication process on the first application based on the registration information about the second application (e.g., operation 204b in Figure 2) and provide information about the user to the first application based on the registration information about the second application (e.g., operation 204c in Figure 2).

According to the embodiment of the electronic device, the information required during the integration registration process of the first application can be confirmed from the member information of the second application after being queried. According to the embodiment of the electronic device, the information regarding the member information of the second application that cannot be confirmed from the necessary information can be queried and obtained from other (some) applications other than the first and second applications.

At the same time, as described above, a user may attempt to log in to the first application using login information different from the login information for the second application. Additionally, there may be a situation where a user requests to log in to the first application using login information for the second application, but the user does not log in to the second application on the user's terminal device.

That is, when the user clicks the second interface 300b (31), or when the user clicks the first interface 300a but does not log in to the second application because of executing the second application (32), as shown in FIG3C, the user's terminal device or electronic device can provide one of the login pages of the second application.

Figure 3C illustrates the example implementation of moving from the first application to the login page of the second application and performing one of the operations of the first application.

One of the pages shown in Figure 3C could be a login page displayed when a user attempts to log in to a second application.

That is, when a user clicks on the first interface 300a in FIG3A, the user's terminal device or electronic device according to the embodiment can execute the second application (e.g., operation 203 in FIG2) (when the second application is installed on the user's terminal device). On the other hand, when the user clicks on the first interface 300a, but the second application is not installed on the user's terminal device, the electronic device according to the embodiment can provide the user's terminal device with an installation page for the second application (e.g., operations 203 and 203a in FIG2).

According to the embodiment, the electronic device can use an integrated process to perform the authentication process for the user, instead of requiring separate authentication processes for each of multiple applications, thereby simplifying the process required for the user to log in.

Figure 4 is a diagram illustrating an example of an operation in which an authentication process is performed on a first application based on the registration information of a second application, according to an example implementation.

The operations shown in Figure 4 may include, for example, some or all of operations 204, 204b and 204c of Figure 2 and may perform the operations shown in Figures 3A to 3C.

Referring to Figure 4, the user can execute the first application (4a) according to the embodiment. The terminal device 400 according to the embodiment executes the first application 400a. When the first application 400a is executed, the electronic device 401 according to the embodiment can request the user of the terminal device 400 to register.

The user's terminal device 400 can respond to a user's input request for SSO registration on an electronic device 401 according to an embodiment. For example, SSO registration may refer to registration in an authentication process based on user information (registration information) used for registration on the first application. That is, the user's terminal device 400 can use the registration information of the second application to request SSO registration for registration on the first application (4b).

In response to receiving an SSO registration request from the user's terminal device 400 (4b), the electronic device 401 of the embodiment may generate an SSO symbol for an SSO and transmit the SSO symbol to the user's terminal device 400 (4c). The SSO symbol may be generated by a first application member information manager 401a or by an SSO symbol generator of the electronic device 401 of the embodiment.

According to the embodiment of the user's terminal device 400, the first application 400a can transmit the received SSO symbol to a second application 400b (4d). According to the embodiment of the user's terminal device 400 executes the second application 400b and transmits the received SSO symbol to the second application 400b.

When a user is not registered on the second application in the user's terminal device 400 (i.e., when there is no access token for the second application in the user's terminal device 400), the user's terminal device 400 or electronic device 401 according to the embodiment may request the user to perform a registration (4e). When the user registers for the second application, the user's terminal device 400 and electronic device 401 according to the embodiment will have an access token for the second application.

According to the embodiment, the user's terminal device 400 transmits the user's access token for the second application and the SSO token according to the embodiment to the electronic device 401 (4f) according to the embodiment. Specifically, the user's terminal device 400 may transmit the access token and SSO token to the first application member information manager 401a included in the electronic device 401 or to one of the authentication confirmation parts 401b included in the member information manager 401a (4f).

According to the embodiment of the electronic device 401 (first application member information manager 401a or authentication confirmation part 401b), the user's access token for the second application received from the second application is confirmed, and as described above, the electronic device 401 compares and contrasts the SSO token generated in the first application with the SSO token received from the second application. In order to confirm whether the user is a legitimate or valid user of the second application, the electronic device 401 (first application member information manager 401a or authentication confirmation part 401b) according to the embodiment of the electronic device 401 can query the access token (4g) of the second application member information manager 401c for the user of the second application.

When a user is confirmed by the second application member information manager 401c as a legitimate or valid user of the second application, the electronic device 401 (first application member information manager 401a or authentication confirmation part 401b) of the embodiment may transmit an authentication success signal to the second application (4h). One of the conditions for the electronic device 401 to transmit the authentication success signal (4h) may be either the user being confirmed by the second application member information manager 401c as a legitimate or valid user of the second application, or the SSO symbol generated in the first application being equal to the SSO symbol received from the second application (or when the user is determined to be a legitimate user based on two SSO symbols).

When an authentication success signal is received from electronic device 401 (4h), in response to the authentication success signal, according to the second application 400b of the embodiment, an authentication success signal can be transmitted to the first application (4i).

In response to receiving an authentication success signal (4i) via the second application, the first application 400a according to the embodiment may transmit at least one of the aforementioned SSO symbol and authentication success signal to the electronic device 401 or the first application member information manager 401a according to the embodiment (4j). When receiving at least one of the SSO symbol and authentication success signal (4j), the electronic device 401 or the first application member information manager 401a according to the embodiment may transmit an access symbol (authentication symbol) to the first application to allow the user to access the first application 400a (4k). The first application 400a according to the embodiment may perform user (41) registration (4k) based on the received access symbol.

According to the embodiment, the electronic device can use an integrated process to perform the authentication process for the user, instead of requiring separate authentication processes for each of multiple applications, thereby simplifying the process required for the user to log in.

Figure 5 is a flowchart illustrating one of the methods for managing member information, based on the example implementation.

Specifically, Figure 5 is a diagram illustrating an example of an operation performed on an authentication process for a first application based on registration information of a second application, according to an embodiment of the example. For example, Figure 5 may include some or all of the operations 4a to 4l shown in Figure 4. Some or all of the operations shown in Figure 5 may be performed by an electronic device according to an embodiment of the example. The operations shown in Figure 5 may include, for example, some or all of operations 204, 204b, and 204c of Figure 2 and include the operations shown in Figures 3A to 3C.

The electronic device according to the embodiment can generate an integrated registration mark and transmit the integrated registration mark to the user's first application (500). Operation 500 may include, for example, operation 4c of FIG4. The electronic device according to the embodiment can receive an access mark for a second application different from the first application and an integrated registration mark from the second application (501). Operation 501 may include, for example, operation 4f of FIG4. The electronic device according to the embodiment can confirm whether the user is a member of the second application based on the access mark for the second application (502). Operation 502 may include, for example, operation 4g of FIG4. When the user is a member of the second application, the electronic device according to the embodiment can transmit a membership confirmation success signal to the second application (503). Operation 503 may include, for example, operation 4h of FIG4. The electronic device according to the embodiment can receive an integrated registration mark from the first application (504). Operation 504 may include, for example, operation 4j of FIG4. The electronic device according to the embodiment can transmit an access mark to the first application to the first application (505). Operation 505 may include, for example, operation 4k of FIG4.

For example, the operation 502 of confirming whether a user is a member according to the embodiment may include an operation of querying an access token from a storage device (a second storage device) of a second application included in the electronic device according to the embodiment.

The first application receiving the integrated login symbol, based on the example implementation, may include, for example, the integrated login symbol and a member confirmation success signal.

On the other hand, when the SSO process is completed from the user's terminal device, the electronic device according to the embodiment can share information about the user (e.g., user membership information, user personal information, and user history information) with multiple applications based on the SSO symbol.

That is, the electronic device according to the embodiment can share information about the user used in the second application with the first application based on the SSO symbol.

For example, suppose the first application is related to a shopping mall service, and the second application is related to a food ordering and delivery service. In this case, in order to select an item that can be recommended to a user in the first application, the electronic device can use past order (payment) details for food ordering and delivery and a search history for an item (or food), which are managed and stored in a storage device (database) of the second application. For example, when a user has multiple purchase histories of ordering steak through the second application, the electronic device can refer to the multiple purchase histories and control the first application to recommend (a number of) items that can cook steak in the first application of the user with high priority.

For example, the user's burden can be high if they set a delivery location in the first application and then need to set the same delivery location in the second application. Accordingly, the electronic device can share information with the second application to indicate the delivery location set in the first application.

Figure 6 is an example of a method for managing member information stored in multiple storage devices and sharing the member information in various applications, according to one of the embodiments of the example.

Specifically, referring to Figure 6, the member information stored in multiple storage devices according to the example implementation can be shared with various applications based on SSO symbols. Some or all of the operations of the example implementation shown in Figure 6 can be included in operation 204c of Figure 2 and are included in the operations following operation 41 of Figure 4.

That is, the electronic device according to the embodiment can share information about the user in each application with other applications based on an SSO symbol 602.

Based on SSO notation 602, the electronic device 601 according to the embodiment includes at least one of a processor 601c and a transceiver 601d to perform (a certain number of) operations that share information about users used in each application with other applications. For example, processor 601c and transceiver 601d may refer to processor 110 and transceiver 120 of FIG1, respectively.

The electronic device according to the example embodiment may include separate storage devices 600a and 600b for each service (or application). Storage devices 601a and 601b of the example embodiment shown in Figure 6 can each be understood as a physical storage device, a storage space included in a storage device, and a logical space region included in a storage device. For example, each of the plurality of storage devices 601a and 601b may be a database or a table included in a database. According to the example embodiments shown in Figure 6, each of the storage devices 601a and 601b may not necessarily correspond to a single application, and one or more applications may share information stored in a single storage device.

As a result of an SSO process executed by a first application 600a through an nth application 600b, a terminal device 600 of a user according to an example embodiment can receive and store an SSO symbol 602 from an electronic device 601. For example, the SSO process may refer to the integrated authentication process described with reference to Figures 4 and 5.

According to the embodiment, the first application 600a of the user's terminal device 600 can use itself to receive information about the user or to drive the first application 600a via a first storage device 601a of the electronic device of the first application 600a. Alternatively, the first application 600a can use itself, based on the SSO symbol, to receive information about the user or to drive the first application 600a via a m-th storage device 601b of the electronic device of another application.

Based on the SSO symbol stored in the user terminal device, according to the example embodiment, the first application can request data required by the first application from the m-th storage device 601b for an application different from the first application.

For example, when a first application operating a platform for ordering food and delivering it to a user's location directly receives information about the user's delivery address from the user, it can increase the user's burden. Accordingly, the first application according to an embodiment can use an SSO symbol to request information about the delivery address from an electronic device according to an embodiment. In response to the above request, the electronic device according to an embodiment can verify the SSO symbol, obtain the SSO symbol from another storage device (e.g., a second storage device) containing information about the user's delivery address, and provide the information about the user's delivery address to the first application.

Based on the SSO symbol stored in the user's terminal device, the first application according to the embodiment can correct, add, delete, or update some or all of the data stored in the first storage device. For example, suppose the user corrects information about the transmission address through a second application. In this case, when the first application receives information about the user's corrected transmission address directly from the user again, it can increase the user's burden. Accordingly, the first application according to the embodiment can use the SSO symbol to request an update to the transmission address information from the electronic device according to the embodiment. In response to the above request, the electronic device according to the embodiment can verify the SSO symbol by obtaining the SSO symbol from another storage device (e.g., a second storage device) containing information about the user's transmitted address, and updating or overwriting the correction information about the user's transmitted address in the first storage device. Based on the SSO symbol, the electronic device according to the embodiment can share the storage device used and managed by various applications for each service, minimizing the re-entry of unnecessary information in the process of providing various services to the user, thereby reducing user confusion.

Furthermore, the electronic devices according to the embodiments can be shared as storage devices for the use and management of each application of each service based on SSO symbols, so that information about users can be managed as a whole for each interactive service, and since the information about users is based on a user's taste or purchase history, a personalized and differentiated service can be provided to the user.

Figure 7 is a diagram illustrating one example of a method for sharing member information in various applications using an electronic device, according to one of the embodiments.

Specifically, referring to Figure 7, the member information stored in a plurality of storage devices 702 according to the example embodiment can be shared with various applications based on an SSO symbol 703. Some or all of the operations of the example embodiment shown in Figure 7 may be included in operation 204c of Figure 2, may include operations after operation 41l of Figure 4, and may include some or all of the operations shown in Figure 6.

Referring to Figure 7, the first application according to the embodiment can receive information about the user or membership information about the user from a plurality of storage devices 702 contained in the electronic device according to the embodiment.

According to the embodiment, the first application can receive information about the user or membership information about the user from the storage device of the first application contained in the electronic device. Simultaneously, when the information about the user or membership information about the user is not present in the storage device of the first application contained in the electronic device, the electronic device can request an SSO symbol 703 from the user's terminal device. The electronic device can receive the SSO symbol 703 from the user's (first application's) terminal device and verify whether the SSO symbol 703 received from the user's terminal device is a valid SSO symbol. When an SSO symbol is determined to be a valid SSO symbol, the electronic device can search for an application other than the first application in a storage device and provide the first application with the information required from the first application (e.g., membership information or information about the user).

Similarly, the electronic device can receive the SSO symbol 703 from the user's (first application's) terminal device and verify whether the SSO symbol 703 received from the user's terminal device is a valid SSO symbol. When the SSO symbol is determined to be a valid SSO symbol, the electronic device can search for an application other than the second application in a storage device and provide the second application with the required information (e.g., membership information or information about the user).

For example, suppose the first application is an application related to a shopping mall service, and the second application is an application related to a food ordering and delivery service. In order to select an item that can be recommended to the user in the first application, the electronic device can use past order (payment) details and a search history of food (or an item) for food ordering and delivery, which are managed and stored in a storage device (database) of the second application.

According to the embodiments of the example, the electronic device can provide a personalized service to a user in a specific application service based on the details of purchasing, ordering, or searching for items. For example, in order to enable an application to operate on a platform for ordering food and having the food delivered to the user's location, the electronic device according to the embodiments of the example can provide the aforementioned details of purchasing, ordering, or searching for items to a corresponding application.

According to the first application of the embodiment, the SSO symbol 703 can be transmitted to an electronic device. Based on the SSO symbol 703, the electronic device can query order information about items purchased or ordered by the user through multiple application services. For example, the electronic device can confirm an order history or search history for purchased or ordered items over a time period from a current time to a specific time. The electronic device according to the embodiment can confirm historical information about items purchased or ordered by the user through multiple application services or historical information about items searched through multiple application services and configure a history of purchased or ordered items and historical information about items searched in chronological order. For example, the history of purchasing or ordering items may include information about the delivery location of each item, information about the order or purchase time of each item, and information about the category of each item.

For example, an electronic device according to an embodiment may receive a request from a user's first application for a recommended item to be recommended to the user, the first application being used to order food and have the food delivered to the user's location. In this case, the electronic device may further receive a request for recommended items and SSO symbols for the user. After verifying the legitimacy of the SSO symbol, the electronic device according to the embodiment may verify and retrieve a search history of items purchased or ordered by the user and a search history of items searched through multiple application services from multiple storage devices in the electronic device.

According to the embodiments of the electronic device, a personalized service can be provided to the user using the history of items purchased or ordered by the user and the search history of items searched through multiple application services. For example, when the electronic device confirms that the history of items purchased or ordered by the user shows that the word "beef" is included in the name of an item or multiple words similar to the word "beef" are included in a word list, the electronic device can control the first application to expose an item related to "beef" among the items stored in the storage device of the first application (the first storage device) to an advertisement or recommended item area on the home screen of the first application. Alternatively, when the electronic device confirms that the word "beef" is included in the name of an item as part of the user's search history, the electronic device may control the first application to expose an item related to "beef" among the items stored in the first application's storage device (the first storage device) to an advertisement or recommended item area on the first application's home screen.

For example, when a user has multiple purchase histories of ordering steak food through a second application, the electronic device can refer to the multiple purchase histories and control the first application to recommend (a number of) items that can cook steak in the first application of the user with high priority.

The electronic device according to the embodiment may share points information used to indicate a user's points with multiple applications. Points may refer to online currency or virtual currency that a user can use to purchase goods or order food. For example, a user can earn points through a second application. On the other hand, in order for a user to use points to order a good or food item or receive a service required by the user through multiple applications, the electronic device according to the embodiment needs to share points information 700a with the user managed by the second application and other applications.

Accordingly, the first application of the embodiment can request user's points information 700a stored in the storage device of the second application when transmitting the SSO symbol 703 to the electronic device. Based on the SSO symbol 703, the first application can receive user's points information 700b used in the second application, and the points information 700a can be used in the first application. The electronic device of the embodiment can confirm the SSO symbol 703, verify the applicability of the SSO symbol 703, and then transmit the user's points information used in the second application to the first application.

The electronic device according to the embodiment can share user delivery information with multiple applications. Accordingly, the first application according to the embodiment can request delivery information 700b of the user stored in the storage device of the second application when transmitting the SSO symbol 703 to the electronic device. For example, the delivery information may include delivery destination information indicating a delivery location, information indicating a request for delivery, and information indicating a payment method when purchasing an item.

Based on the SSO symbol 703, the first application can receive information 701b about the transmission to be used in the second application, and the information 701b about the transmission can be used in the first application. The electronic device according to the embodiment can confirm the SSO symbol 703, verify the applicability of the SSO symbol 703, and then transmit the information about the transmission to be used in the second application to the first application.

For example, suppose a user stores three delivery information in a first application. When the user purchases or orders a specific item from a second application, the electronic device according to an embodiment can confirm the three delivery address information contained in the storage device (first storage) of the first application based on the SSO symbol 703 received from the second application. The electronic device according to an embodiment can provide the confirmed three delivery address information to the user through the first application. The electronic device according to an embodiment can update the confirmed three delivery address information in the storage device (second storage) of the second application.

Additionally, for example, suppose a user stores two pieces of information in a second application to indicate a payment method. When the user purchases or orders a specific item from the first application, the electronic device according to the embodiment can confirm the two pieces of information indicating a payment method contained in the storage device (first storage device) of the first application based on the SSO symbol 703 received from the first application.

The electronic device according to the embodiment can correct and update data stored in the storage device (first storage device) of the first application through the first application. In addition, the electronic device according to the embodiment can use the SSO symbol 703 to store, correct and update data stored in a storage device of another application.

Based on SSO notation, electronic devices in the example implementation can share a storage device for the use and management of various applications for each service, thereby minimizing the re-entry of unnecessary information in the process of providing various services to users, thereby reducing user confusion.

Furthermore, according to the example implementation, the electronic device can share the storage device for each application of each service for use and management based on the SSO symbol, so that information about users can be managed as a whole for each interactive service, and since the information about users is based on a user's taste or purchase history, a personalized and differentiated service can be provided to the user.

Furthermore, although examples and embodiments of the invention have been disclosed and specific terms have been used in this specification and accompanying drawings, these are used only in a general sense to facilitate the description of the technical content of the invention and to aid in understanding the invention, and are not intended to limit the scope of the invention. Those skilled in the art to which the invention pertains will understand that other modifications can be made based on the technical spirit of the invention.

The electronic device or terminal according to the above embodiments may include a processor, memory for storing and executing program data, a permanent storage device (such as a hard disk drive), a communication port for communicating with an external device, and a user interface device (such as a touch panel, key, and buttons). The method of implementation as a software module or algorithm may be computer-readable code or program instructions executable on the processor and stored on a computer-readable recording medium. Here, a computer-readable recording medium includes a magnetic storage medium (e.g., a read-only memory (ROM), a random access memory (RAM), a floppy disk, and a hard disk) and an optically readable medium (e.g., an optical disc (CD)-ROM and a digital versatile disc (DVD)). The computer-readable recording medium can also be distributed across a computer system connected via a network, allowing a computer-readable program or code to be stored and executed in a distributed manner. The computer-readable recording medium can be read by a computer, stored in memory, and executed by a processor.

Implementation examples can be represented by functional block components and various processing operations. These functional blocks can be implemented using various hardware and/or software configurations that perform specific functions. For example, an implementation example can employ an integrated circuit component capable of performing various functions under the control of one or more microprocessors or other control devices, such as memory, processing, logic, or a lookup table. Similar to components that can be implemented as software programs or software components, implementation examples can contain various algorithms implemented as a combination of data structures, procedures, constants, or other programmable components and can be implemented in a programming or descriptive language (such as C, C++, Java, or an assembler). Functional examples can be implemented using algorithms that run on one or more processors. Furthermore, the embodiments may apply the relevant technology to an electronic environment setup, signal processing, and/or data processing. Terms such as "mechanism," "component," "part," and "assembly" are used broadly and are not limited to mechanical and physical components. The terminology may encompass one of a range of software common meanings associated with a processor or the like.

The above examples and embodiments are merely examples, and other examples and embodiments may be implemented within the scope of the appended patent application described below.

Furthermore, although examples and embodiments of the invention have been disclosed and specific terms have been used in this specification and accompanying drawings, these are used only in a general sense to facilitate the description of the technical content of the invention and to aid in understanding the invention, and are not intended to limit the scope of the invention. Those skilled in the art to which the invention pertains will understand that other modifications can be made based on the technical spirit of the invention.

4a: Operation 4b: Operation 4c: Operation 4d: Operation 4e: Operation 4f: Operation 4g: Operation 4h: Operation 4i: Operation 4j: Operation 4k: Operation 4l: Operation 31: User clicks second interface 300b 32: Execute second application 100: Electronic device 110: Processor 120: Transceiver 130: Memory 200: Operation 200a: Operation 201: Operation 201a: Operation 202: Operation 202a: Operation 203: Operation 203a: Operation 204: Operation 204a: Operation 204b: Operation 204c: Operation 300: Page 300a: First Interface 300b: Second Interface 300c: First Application 300-1: First Area 301a: Fifth Interface 400: Terminal Device 400a: First Application 400b: Second Application 401: Electronic Device 401a: Member Information Manager 401b: Authentication Confirmation Section 401c: Second Application Member Information Manager 500: Operation 501: Operation 502: Operation 503: Operation 504: Operation 505: Operation 600: Terminal Device 600a: First Application 600b: nth Application 601: Electronic Device 601a: Storage Device 601b: Storage Device 601c: Processor 601d: Transceiver 602: SSO Symbol 700a: Integration Information 700b: Integration Information 701b: Information 702: Storage Device 703: SSO Symbol

Figure 1 is a diagram illustrating one example of the internal components of an electronic device according to one embodiment.

Figure 2 is a flowchart illustrating one example of a method for managing member information based on a specific implementation example.

Figure 3 is a diagram illustrating one example of a user interface for managing member information, based on an example implementation.

Figure 4 is a diagram illustrating an example of an operation that performs an authentication process on a first application based on the registration information of a second application in an example implementation.

Figure 5 is a flowchart illustrating one of the methods for managing member information, based on the example implementation.

Figure 6 is an example of a method for managing member information stored in multiple storage devices and sharing the member information in various applications, according to one of the embodiments of the example.

Figure 7 is a diagram illustrating one example of a method for sharing member information in various applications using an electronic device, according to one of the embodiments.

100: Electronic Devices

110: Processor

120: Transceiver

130: Memory

Claims (11)

A method for managing member information of an electronic device, the method comprising: responding to the execution of a first application to confirm whether a user terminal is logged in on the first application; when the user terminal is not logged in on the first application, confirming member information corresponding to the user on a second application; performing a login process for the user on the first application based on the member information on the second application; confirming the user's search history associated with the second application based on the member information; and providing information on an item associated with the search history on the first application. The method of claim 1, wherein confirming the member information on the second application includes confirming whether the second application is installed on one of the user's terminal devices. The method of claim 1 further includes: when the login process performed by the member information of the second application is completed, providing the member information on the second application to the first application, wherein the user terminal logs in to the first application based on the member information on the second application. The method of claim 1 further includes: using login information of the first application or login information of the second application to confirm whether the user has logged in on the first application. The method of claim 4 further includes: when the user determines that the login information of the second application is used to log in on the first application, providing the user terminal with a first page for performing a registration process on the first application. The method of claim 1, wherein confirming the member information on the second application includes: providing the user terminal with a second page for installing the second application when the second application is not installed on the user terminal. The method of claim 1, wherein the login process includes: generating a Single Message (SSO) login token and transmitting the SSO login token to the user's first application; receiving an access token of the second application and the SSO login token from the second application; and confirming, based on the access token of the second application, whether the user is a member of the second application. As in the method of claim 7, wherein when the user is a member of the second application, the login process includes: transmitting a member confirmation success message to the second application; receiving the SSO login token from the first application; and transmitting an access token to the first application to the first application. As in the method of claim 3, the provision of the member information includes: receiving an SSO symbol and a request for information about the user from the user terminal; confirming whether the SSO symbol is a valid symbol of the user; and confirming the information about the user based on the SSO symbol and transmitting the information about the user. An electronic device for performing a method for managing member information, the electronic device comprising: a memory configured to store at least one program; and a processor configured to, in response to the execution of a first application, confirm whether a user terminal is logged in on the first application, and when the user terminal is not logged in on the first application, confirm member information corresponding to the user on a second application, perform a login process for the user on the first application based on the member information on the second application, confirm the user's search history associated with the second application based on the member information, and provide information on an item associated with the search history on the first application. A non-temporary computer-readable storage medium includes: a medium configured to store computer-readable commands, wherein, when the computer-readable commands are executed by a processor, the processor includes: responding to the execution of a first application to confirm whether a user terminal is logged in on the first application; when the user terminal is not logged in on the first application, confirming membership information corresponding to the user on a second application; performing a login process for the user on the first application based on the membership information on the second application; confirming the user's search history associated with the second application based on the membership information; and providing information on an item associated with the search history on the first application.