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

Abstract

Methods for managing member information according to embodiments include checking whether a user is logged in to a first application; Confirming whether to log in to the first application from the user using information about the user of the first application; Confirming whether the first application has performed an authentication process using information about the user of the second application from the user; Checking whether the second application is installed on the user's terminal device; and checking whether the user is logged in with member information for the second application; It may include at least one of:

Description

Member information management method and device {A METHOD FOR MANAGING MEMBER INFORMATION AND AN APPARATUS FOR THE SAME}

Disclosure of the present invention relates to a method and device for integrating and managing member information. More specifically, the present disclosure relates to a method and device for integrating and managing member information using an integrated authentication procedure.

SSO (Single Sign-On) is a system that allows users to use multiple sites or services with a single login, and is gaining popularity because it allows users to use it easily without having to enter a lot of personal information. In the case of individuals, the inconvenience of having to record personal information such as ID and password as well as name and phone number for each site is eliminated in order to access the site, but this is done in one task, and for companies, integrated management of members is possible. This has the advantage of maximizing marketing.

Related prior patent documents include Republic of Korea Patent Publication No. 10-2157743 (2020.09.14).

The problem that this embodiment aims to solve is to provide a management method and device by integrating member information to solve the above-mentioned problems.

More specifically, the present disclosure simplifies the authentication process for multiple service applications providing different services through an integrated authentication procedure, and provides a method and device for sharing necessary information between multiple services through a server. It's about.

In order to solve the above-described problem, a method for managing member information according to embodiments includes the steps of checking whether a user is logged in to a first application; Checking whether the user will log in to the first application using the login information of the first application; Confirming whether the authentication process of the first application is performed from the user using the login information of the second application; Checking whether the second application is installed on the user's terminal device; and checking whether the user is logged in with member information for the second application; It may include at least one of:

Methods for managing member information according to embodiments may include performing an authentication procedure for the first application based on member information of the second application.

Member information management methods according to embodiments may include providing information about a user to a first application based on member information about the second application.

Methods for managing member information according to embodiments include, when the user decides to log in to the first application with the login information of the second application, a page for performing the membership registration process for the first application is created on the user's terminal device. It may include providing steps.

Methods for managing member information according to embodiments may further include providing a second application installation page to the user's terminal device when the second application is not installed on the user's terminal device.

Performing an authentication procedure for the first application based on member information of the second application according to embodiments includes generating an integrated login token and transmitting it to the user's first application; Receiving an access token for a second application different from the first application and the integrated login token from the second application; confirming whether the user is a member of the second application based on the access token for the second application; If the user is a member of the second application, transmitting a member confirmation success signal to the second application; Receiving an integrated login token from the first application; and transmitting an access token for the first application to the first application.

Providing information about the user to the first application based on member information about the second application according to embodiments includes receiving a request for an integrated authentication token and information about the user from the user's terminal device; confirming whether the integrated authentication token is a legitimate token for the user; and confirming information about the user based on the integrated authentication token and transmitting the information about the user. It may include at least one of:

Electronic devices according to embodiments can perform an authentication process for a user through an integrated process without an individual authentication process for each of a plurality of applications, thereby simplifying the process required for a user to log in.

Electronic devices according to embodiments share a storage unit used and managed for each service application based on an integrated authentication token, thereby minimizing user confusion by re-entering unnecessary information in the process of providing multiple services to the user. can be reduced.

In addition, electronic devices according to embodiments share a storage unit used and managed for each application of each service based on an integrated authentication token, thereby enabling integrated management of information about the user for each linked service and the user's preferences. Alternatively, since it is based on purchase history, personalized and differentiated services can be provided to users.

1 shows an example of internal components of an electronic device according to embodiments.
Figure 2 shows an example of a method for managing member information according to embodiments.
Figure 3 shows an example of a user interface for a method of managing member information according to embodiments.
Figure 4 shows an example of an operation of performing an authentication procedure for a first application based on login information of a second application according to embodiments.
Figure 5 shows an example of a member information management method according to embodiments.
Figure 6 shows an example of a method in which an electronic device manages member information stored in a plurality of storage units and shares member information for each application, according to embodiments.
Figure 7 shows an example of a method by which an electronic device shares member information for each application according to embodiments.

Hereinafter, embodiments of the present invention will be described in detail with reference to the attached drawings.

In describing the embodiments, description of technical content that is well known in the technical field to which the present invention belongs and that is not directly related to the present invention will be omitted. This is to convey the gist of the present invention more clearly without obscuring it by omitting unnecessary explanation.

For the same reason, some components are exaggerated, omitted, or schematically shown in the accompanying drawings. Additionally, the size of each component does not entirely reflect its actual size. In each drawing, identical or corresponding components are assigned the same reference numbers.

The advantages and features of the present invention and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below and may be implemented in various different forms. The present embodiments are merely provided to ensure that the disclosure of the present invention is complete and to provide common knowledge in the technical field to which the present invention pertains. It is provided to fully inform those who have the scope of the invention, and the present invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

At this time, it will be understood that each block of the processing flow diagram diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions. These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory It is also possible to produce manufactured items containing instruction means that perform the functions described in the flowchart block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). Additionally, it should be noted that in some alternative execution examples it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible that two blocks shown in succession are actually performed in parallel, or the blocks can sometimes be performed in reverse order according to the corresponding functions.

At this time, the term '~unit' used in this embodiment refers to software or hardware components such as FPGA or ASIC, and the '~unit' performs certain roles. However, '~part' is not limited to software or hardware. The '~ part' may be configured to reside in an addressable storage medium and may be configured to reproduce on one or more processors. Therefore, as an example, '~ part' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and 'parts' may be combined into a smaller number of components and 'parts' or may be further separated into additional components and 'parts'. Additionally, components and 'parts' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card.

1 shows an example of internal components of an electronic device according to embodiments.

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

The processor 110 may process a series of steps for performing an item feed information management method according to various embodiments of the present disclosure. The processor 110 may control other components of the electronic device 100. Items may be sold to users in services related to the electronic device 100.

The processor 110 checks whether the first application is logged in; Confirming whether to log in to the first application from the user using information about the user of the first application; Confirming whether the first application has performed an authentication process using information about the user of the second application from the user; Checking whether the second application is installed on the user's terminal device; and checking whether the user is logged in with member information for the second application; You can do at least one of the following: Programs or computer-readable instructions executed by the processor 110 may be pre-stored in the memory 130 or may be received from the outside through the transceiver 120. The processor 110 may provide the first page to the display of the electronic device 100.

The transceiver 120 has a function 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. It can be done.

The memory 130 is a component implemented in a predetermined storage space of the electronic device 100 and may include a database in which functions such as storing, searching, deleting, editing, or adding data can be freely performed. there is. For example, the memory 130 may include fields or components for processing functions such as storing, searching, deleting, editing, or adding data. The memory 130 may store data related to the electronic device 100 performing an information provision method. For example, the memory 130 may store instructions or data for execution of the processor 110. The memory 130 according to embodiments may include a database for storing information about items, etc.

Electronic devices according to embodiments may manage member information for one service. Member information according to embodiments includes, for example, information that can identify a user using the corresponding service or authenticate the user. For example, member information may include the user's ID and a password for accessing the service with that ID.

Member information according to embodiments may exist differently for each application service. For example, member information for an application that operates a platform for ordering food and delivering it to the user's location (hereinafter referred to as the first application or first application service) may be used to search, purchase, and pay for items. Therefore, it may be different from the member information for the application that operates the platform that delivers the item to the user's location (hereinafter referred to as the second application or second application service). Meanwhile, in the embodiment, the first application is described as performing a function related to food delivery, but is not limited thereto, and the first application is an application that picks up an item from a specific location according to the customer's order and delivers it to the customer's location. You can.

An electronic device according to embodiments may store information about users subscribed to one application service in the memory 130 according to embodiments, and may manage information about users stored in the memory. Information about the user may include, for example, at least one of the user's name information, the user's item delivery address information, the user's item order history information, and the user's item search history.

Electronic devices according to embodiments may store information about users separately for each application service due to reasons such as personal information storage policies and security issues related to personal information. For example, the electronic device includes a first storage unit for use by a first application that operates a first service (first application service) and a second application that operates a second service (second application service). It may include a second storage unit for use in. That is, the electronic device may include a plurality of databases or a plurality of tables, and each database or each table includes member information about users used in one application service and information about users (e.g., personal information , information related to delivery of the item, etc.) may be included. That is, electronic devices according to embodiments may include separate storage units for each service (eg, application of a terminal device) provided by the electronic device. Additionally, the electronic device according to the embodiments may use a storage unit (for example, a database, etc.) related to the electronic device for each service according to a separate authentication procedure from the terminal device according to the embodiments.

For example, the first storage unit for the first application that operates a platform for ordering food and delivering it to the user's location includes the user's first member information for the first service and the first storage unit indicating the location of the seller selling food. It may include at least one of location information, the name and price of each item (food) by the seller, information about the delivery people who will deliver the item when the user orders the item, and first delivery location information indicating the user's delivery location. there is.

For example, the second storage unit for the second application that operates a platform that searches, purchases, and pays for items and delivers the items to the user's location stores the user's second member information for the second service and the items. It may include at least one of information about distribution centers, each name and price of items stored in the server of the second application, and second delivery location information indicating the user's delivery location.

When executing the first application, the user's terminal device according to the embodiments uses the electronic device and the first application according to the embodiments to use information about the user used in the first application service stored in the first storage. Certification procedures can be performed for . That is, the electronic device according to embodiments provides information about the user stored in the first storage as the first application based on the access token for the first application generated after completing the authentication procedure for the first application. Information can be provided. Likewise, when executing a second application, the user's terminal device according to the embodiments may use the electronic device and the user terminal device according to the embodiments to use information about the user used in the second application service stored in the second storage. 2Authentication procedures for applications can be performed. That is, the electronic device according to embodiments may provide information about the user stored in the second storage to the second application based on the access token to the second application generated after completing the authentication procedure for the second application. You can.

On the other hand, in an electronic device that provides multiple services, if a separate authentication procedure must be completed with the terminal device for each service (for example, the electronic device must use the access token for the first application and the access token for the second application) (generated separately, and the user's terminal device retrieves information about the user from the electronic device based on a separate token), imposes a burden of procedures on the user, and provides the user with information about the user separately for each application based on a separate token for each application. Because it retrieves information about each service, it may be difficult to share information commonly needed for each service between applications. In addition, it is not efficient in terms of storage space as overlapping data between services is stored separately.

Accordingly, the electronic device according to embodiments can simplify the authentication procedure of the first application by performing a valid integrated authentication procedure in the second application (service). Additionally, electronic devices according to embodiments simply perform an authentication procedure between first applications using a valid integrated authentication procedure between second applications (and an authentication token for the second application generated by a valid authentication procedure). can do. Additionally, through this integrated authentication process, the first application according to embodiments can receive and share member information (or information about the user) used in the second application. Below, we look at examples of the operation and configuration of an electronic device that performs this method.

Figure 2 shows an example of a method for managing member information according to embodiments.

Electronic devices according to embodiments may perform some or all of the operations of the method for managing member information shown in FIG. 2 . Specifically, Figure 2 is an example of an operation in which an electronic device manages member information according to embodiments. 2 illustrates, for example, an operation of performing a login procedure for a first application to perform a login procedure for a first application, or an operation of performing a login procedure for a first application using login information for a second application. Indicates action. Referring to FIG. 2 , an electronic device according to embodiments may perform at least one of steps 200 to 204c.

All of the operations according to the embodiments shown in FIG. 2 may be performed in the electronic device according to the embodiments, and some of the operations may be performed by the user's terminal device.

The electronic device according to embodiments may check (200) whether login to the first application (authentication of the first application between the electronic device and the user's terminal device) has already been legally performed. For example, the user's terminal device according to embodiments executes the first application according to an execution signal of the user's first application. Electronic devices according to embodiments may check whether session information indicating legitimate authentication for one application exists in the terminal device. That is, the electronic device can check (200) whether the terminal device has already completed logging into the first application. According to embodiments, when the user's terminal device has already logged in to the first application, the user's terminal device accesses the first application created by the electronic device (for example, the first application server in the electronic device). You can hold tokens.

If the user has completed logging in to the first application (i.e., authentication for the first application between the electronic device and the user's terminal device has already been completed), the electronic device according to embodiments may log in to the first application. Information about the user may be provided to the first application based on the member information (200a). The electronic device according to embodiments receives an access token for the first application from the user's terminal device and verifies member information about the user using the received access token. The electronic device provides information about the user based on the confirmed member information (200a). In this case, information about the user according to the embodiments may mean information about the user confirmed by member information about the first application in the electronic device according to the embodiments.

If the user is not logged in to the first application (i.e., authentication of the first application between the electronic device and the user's terminal device is not in progress), the electronic device according to embodiments may allow the user to log in to the first application. You can check (201) whether to log in using the application's login information. Login information, for example, is information that the user's terminal device receives from the user, and may mean information for the user to perform an authentication procedure for the corresponding application service. Login information may include, for example, ID information, email information, and password information for performing an authentication procedure for the corresponding application service. The electronic device according to embodiments may request a query from the user's terminal device to confirm whether the user will log in using the login information of the first application.

When the user selects to log in using the login information of the first application, the electronic device according to embodiments verifies the login information. The electronic device can check the member information of the user's first application based on the login information and perform a login procedure based on the confirmed member information of the first application (201a). For example, the electronic device can check the user's member information for the first application, execute the first application based on the confirmed member information, and provide information about the user to the first application (200a). can do. Member information of the first application may be included in, for example, a first storage for the first application.

If the user does not select to log in using the login information of the first application, the electronic device according to embodiments determines whether the user will log in to the first application using the login information of the second application (202). can do. For example, when the user selects to log in to the first application using the login information of the second application, the electronic device collects the user's membership information for the second application based on the login information of the second application entered by the user. can be checked from the second storage unit.

Meanwhile, if the user chooses not to log in to the first application using the login information of the second application, the electronic device performs a membership registration process to generate member information for the first application in the first storage (202a). Alternatively, the first application may be provided in a state where authentication has not been completed. However, when the user completes the membership registration process for the first application, the electronic device according to embodiments may provide the first application using membership information for the first application newly entered by the user. , information about the user may be provided to the first application (200a).

When the user selects to log in to the first application using the login information of the second application, the electronic device (or the user's terminal device) according to embodiments determines whether the second application is installed on the user's terminal device. You can check (203). If the second application is not installed on the user's terminal device, the electronic device according to embodiments may provide a page for installing the second application to the user's terminal device (203a). If the second application is not installed on the user's terminal device, the terminal device according to embodiments may search for and check the second application in the App Store in order to install the second application.

If the second application is installed on the user's terminal device, the electronic device according to embodiments may request or control the user's terminal device to execute the second application.

Meanwhile, when the second application is installed on the user's terminal device, the electronic device according to embodiments checks (204) whether the user is logged in to the second application using login information for the second application. You can. For example, the second application according to embodiments checks whether an access token (or session) for the second application is stored in the user's terminal device, and electronically determines whether the stored access token or session is legitimate. You can check it through the device.

If the user is not currently logged in to the second application (i.e., authentication for the second application between the electronic device and the user's terminal device is not in progress), the electronic device according to embodiments may use the second application. A login page of the second application for performing a login procedure for the application may be provided to the user's terminal device (204a). If the user is currently logged in to the second application, the electronic device according to embodiments may query member information of the second application about the user. The electronic device according to embodiments may perform an integrated login procedure (integrated authentication procedure) for the first application based on member information for the searched second application (204b). The integrated login procedure (integrated authentication procedure) is an authentication procedure for other application(s) based on the results of the legally performed authentication procedure, if the user has legally performed the authentication procedure based on the authentication procedure for a specific application. refers to the procedure for performing . The integrated authentication procedure is described in detail, for example, in Figures 4 and 5. When an electronic device according to embodiments properly performs an integrated authentication procedure with the user's terminal device, it can provide an integrated authentication token to the user's terminal device, and the terminal device can store the integrated authentication token. A plurality of application(s) related to the user's terminal device according to embodiments may proceed with an authentication process based on the integrated authentication token according to embodiments, and storage units related to the electronic device based on the integrated authentication token. The data contained in can be shared.

The electronic device according to embodiments may confirm necessary information in the process of performing an integrated login procedure for the first application from member information for the searched second application. Electronic devices according to embodiments may receive information from the user that cannot be confirmed from member information for the second application among necessary information, and may search for information from application(s) other than the first application and the second application. You can obtain it by doing this.

Meanwhile, through this procedure throughout the embodiment, a customer registered in the second application can log in to the first application that is not registered as a member using the login information of the second application, and through this, the electronic device that manages the first application The device may obtain at least some of the user information of the second application and use it as customer information in the first application later. Through this, there is no need for a separate sign-in procedure in the first application based on the second application registration information. Additionally, the first set of information can be shared between the two applications, and the second set of information can be managed individually. For example, the first set of information may include point information, and the second set of information may include delivery address information. However, when you first log in to the first application, some of the information included in the second set may be set based on information entered in the second application, and after initial setup, the information included in the second set may be modified separately in the first application. Or it can be added.

After performing this integrated authentication process, the electronic device according to embodiments may provide information about the user of the first application to the user's terminal device based on member information about the second application (204c).

Electronic devices according to embodiments can perform an authentication process for a user through an integrated process without an individual authentication process for each of a plurality of applications, thereby simplifying the process required for a user to log in.

Figure 3 shows an example of a user interface for a method of managing member information according to embodiments.

Specifically, Figure 3 shows a method of performing an authentication procedure for a first application based on member information for the second application. Some or all of the operations according to the embodiments shown in FIG. 3 may be performed by an electronic device. Some or all of the operations according to the embodiments shown in FIG. 3 may correspond to, for example, some or all of steps 200 to 204c of FIG. 2 .

Figure 3(A) shows a case where the user runs the first application on the user's terminal device, and shows a state in which the user is not logged in to the first application on the user's terminal device. For example, FIG. 3(A) may represent a case where login to the first application is not currently performed in step 200 of FIG. 2.

Referring to FIG. 3(A), the electronic device according to embodiments may request login to the first application from the user's terminal device. In order to log in to the first application, the electronic device according to embodiments may use login information of the second application to check whether to log in to the first application (300a).

Meanwhile, users according to embodiments may attempt to log in to the first application using login information that is different from the member information of the second application. Therefore, the electronic device according to embodiments directly receives the login information of the second application from the user so that the user can attempt to log in to the first application with login information that is different from the login information of the second application. It is possible to check whether to log in to the first application (300b).

Additionally, in order to log in to the first application, the electronic device according to embodiments may check whether to perform membership registration for the first application (300c) or log in using login information for the first application. .

The user's terminal device according to embodiments may render a first area 300-1 on the page 300 of the first application for inquiring about a login method from the user. The first area 300-1 according to embodiments is configured to check whether to log in to the first application using the login information of the second application (300a) in order to log in to the first application. 1st interface (300a), a second interface (300b) to receive login information for the second application directly from the user and check whether to log in to the first application (300b), to register as a member of the first application It may include at least one of a third interface for checking whether to perform logging (300c), and a fourth interface for checking whether to perform logging in using login information for the first application.

Figure 3(B) shows an operation of moving to and executing a main page of a second application from a first application according to embodiments.

The page shown in FIG. 3(B) may be a page that appears when the second application is executed. Specifically, in FIG. 3(A), the user logs in to the first application using the login information of the second application (300a). ) may be the page that appears when you select it. That is, when the user clicks on the first interface 300a in FIG. 3(A), the user's terminal device or electronic device according to the embodiments (if the second application is installed on the user's terminal device) runs the second application. may be executed (e.g., step 203 in FIG. 2). Meanwhile, 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 embodiments provides an installation page of the second application to the user's terminal device ( For example, steps 203 and 203a of FIG. 2) can be performed.

When the second application according to the embodiments is executed by the terminal device, the electronic device or the user's terminal device according to the embodiments determines whether to attempt to log in with the login information for the second application in order to log in to the first application. A fifth interface 301a for making inquiries may be provided. When the user clicks on the fifth interface 301a, the electronic device according to embodiments may perform an authentication procedure for the first application based on the login information of the second application (e.g., 204b of FIG. 2), Based on the login information for the second application, information about the user may be provided to the first application (for example, 204c of FIG. 2).

The electronic device according to embodiments may confirm necessary information in the process of performing an integrated login procedure for the first application from member information for the searched second application. Electronic devices according to embodiments may receive information from the user that cannot be confirmed from member information for the second application among necessary information, and may search for information from application(s) other than the first application and the second application. You can obtain it by doing this.

Meanwhile, as described above, the user may attempt to log in to the first application using login information that is different from the login information to the second application. Additionally, there may be a case where the user requests to log in to the first application using the login information of the second application, but the user is not logged in to the second application of the user's terminal device.

That is, when the user clicks on the second interface 300b (31), or when the user clicks on the first interface 300a but the user is not logged in in the second application as a result of running the second application (32). As shown in 3(C), the user's terminal device or electronic device may provide a login page of the second application.

Figure 3(C) shows an operation of moving to and executing a login page of a second application from a first application according to embodiments.

The page shown in FIG. 3(C) may be a login page that appears when a user attempts to log in in the second application.

That is, when the user clicks on interface 1 300a in FIG. 3(A), the user's terminal device or electronic device according to the embodiments (if the second application is installed on the user's terminal device) runs the second application. It may be executed (e.g., step 203 in FIG. 2). Meanwhile, 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 embodiments provides an installation page of the second application to the user's terminal device ( For example, steps 203 and 203a of FIG. 2) can be performed.

Electronic devices according to embodiments can perform an authentication process for a user through an integrated process without an individual authentication process for each of a plurality of applications, thereby simplifying the process required for a user to log in.

Figure 4 shows an example of an operation of performing an authentication procedure for a first application based on login information of a second application according to embodiments.

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

Referring to FIG. 4, users according to embodiments may execute the first application (4a). The terminal device 400 according to embodiments executes the first application 400a. When the first application 400a is executed, the electronic device 401 according to embodiments may request the user to log in to the user's terminal device 400.

The user's terminal device 400 may request single sign-on (SSO) login to the electronic device 401 according to embodiments according to the user's input. Integrated authentication login may mean, for example, a login based on an authentication procedure for logging in to a first application with information (login information) about the user of the second application. That is, the user's terminal device may request integrated authentication login to log in to the first application using the login information of the second application (4b).

In response to receiving the integrated authentication login request 4b from the terminal device 400, the electronic device 401 according to embodiments generates an integrated authentication token (SSO Token) for integrated authentication to provide the user's terminal device 400. ) can be transmitted (4c). The integrated authentication token (SSO Token) may be generated by the first application member information management unit 401a or the integrated authentication token generator (SSO Token Generator) of the electronic device 401 according to embodiments.

The first application 400a of the user's terminal device according to embodiments may transfer the received integrated authentication token to the second application 400b (4d). The user's terminal device 400 according to embodiments executes the second application 400b and transmits the received integrated authentication token to the second application 400b.

According to embodiments, the user's terminal device 400 or the electronic device 401 is configured to operate the second application in the user's terminal device when the user is not logged in (i.e., the second application in the user's terminal device). (if there is no access token), the user can be requested to log in (4e). When the user logs in to the second application, the user's terminal device and electronic device according to embodiments hold an access token to the second application for the user.

The user's terminal device 400 according to the embodiments transmits (4f) the user's access token to the second application and the integrated authentication token according to the embodiments to the electronic device 401 according to the embodiments. Specifically, the user's terminal device 400 sends the access token and the integrated authentication token to the first application member information management unit 401a included in the electronic device 401 or the authentication confirmation unit 401b included in the member information management unit 401a. ) can be transmitted (4f).

The electronic device 401 (the first application member information management unit 401a or the authentication confirmation unit 401b) according to embodiments verifies the user's access token for the second application received from the second application, and Accordingly, the integrated authentication token generated by the first application is compared and contrasted with the integrated authentication token received from the second application. The electronic device 401 according to embodiments (the first application member information management unit 401a or the authentication confirmation unit 401b) uses the second application to check whether the user is a legal or valid user of the second application. The member information management unit 401c may be queried (4g) for the user's access token to the second application.

When the user is confirmed as a legal or valid user of the second application by the second application member information management unit 401c, the electronic device 401 according to embodiments (the first application member information management unit 401a or authentication confirmation) The unit 401b may transmit an authentication success signal 4h to the second application. The conditions for the electronic device to transmit the authentication success signal (4h) are when the user is confirmed as a legal or valid user of the second application by the second application member information management unit 401c and the integration generated in the first application This may be the case where the authentication token and the integrated authentication token received from the second application are the same (or are determined to be legitimate based on the two tokens).

When the second application 400b according to embodiments receives an authentication success signal 4h from the electronic device 401, it may transmit an authentication success signal 4i to the first application in response.

In response to receiving an authentication success signal from the second application (4i), the first application 400a according to embodiments sends the information to the electronic device 401 or the first application member information management unit 401a according to embodiments. At least one of the integrated authentication token and authentication success signal described above may be transmitted (4j). When the electronic device 401 or the first application member information management unit 401a according to embodiments receives at least one of an integrated authentication token and an authentication success signal (4j), the user sends the first application to the first application 400a. An access token (authentication token) for the first application can be transmitted (4k) so that the application can be accessed. The first application 400a according to embodiments may perform login (4l) for the user based on the received access token 4k.

Electronic devices according to embodiments can perform an authentication process for a user through an integrated process without an individual authentication process for each of a plurality of applications, thereby simplifying the process required for a user to log in.

Figure 5 shows an example of a member information management method according to embodiments.

Specifically, FIG. 5 is a flowchart illustrating an example of an operation of performing an authentication procedure for a first application based on login information of a second application according to embodiments. FIG. 5 may include, for example, some or all of operations 4a to 4l shown in FIG. 4 . Some or all of the operations shown in FIG. 5 may be performed by electronic devices according to embodiments. The operations shown in FIG. 5 may include, for example, some or all of operations 204, 204b, and 204c of FIG. 2, and may include the operations shown in FIGS. 3(A) to 3(C). .

The electronic device according to embodiments may generate an integrated login token and transmit it to the user's first application (500). The operation of step 500 may include, for example, operation 4c of FIG. 4. The electronic device according to embodiments may receive (501) an access token for a second application different from the first application and the integrated login token from the second application. The operation of step 501 may include, for example, operation 4f of FIG. 4. The electronic device according to embodiments may check (502) whether the user is a member of the second application based on the access token for the second application. The operation of step 502 may include, for example, operation 4g of FIG. 4. If the user is a member of the second application, the electronic device according to embodiments may transmit (503) a member confirmation success signal to the second application. The operation of step 503 may include, for example, operation 4h of FIG. 4. The electronic device according to embodiments may receive (504) an integrated login token from the first application. The operation of step 504 may include, for example, operation 4j of FIG. 4. The electronic device according to embodiments may transmit (505) an access token for the first application to the first application. The operation of step 505 may include, for example, the 4k operation of FIG. 4.

Step 502 of checking whether a member is a member according to embodiments may include, for example, storing an access token for the second application in a storage unit (second) for the second application included in the electronic device according to the embodiments. It may include a step of querying the storage unit.

The step of receiving an integrated login token from the first application according to embodiments may include, for example, receiving the integrated login token and the member verification success signal.

Meanwhile, when the integrated authentication process is completed from the user's terminal device, the electronic device according to embodiments provides information about the user (e.g., member information about the user) to a plurality of applications based on integrated authentication based on the integrated authentication token. , personal information about the user, history information about the user, etc.) can be shared.

That is, the electronic device according to embodiments may share information about the user used in the second application to the first application based on the integrated authentication token.

For example, assume that the first application is an application related to shopping mall services, and the second application is an application related to food ordering and delivery services. In this case, in order to select an item that can be recommended to the user in the first application, the electronic device includes past order (payment) details of food orders and deliveries managed and stored in a storage unit (database) for the second application; You can use the search history of the item (or food). For example, if the user has a purchase history of ordering multiple steak foods through the second application, the electronic device refers to this and assigns item(s) that can cook steak foods in the user's first application to high priority. The first application can be controlled to recommend.

For example, if the user sets a delivery location in the first application, the burden on the user may be significant if the user must set the same delivery location in the second application. Accordingly, the electronic device can share information indicating the delivery location set in the first application to the second application.

Figure 6 shows an example of a method in which an electronic device manages member information stored in a plurality of storage units and shares member information for each application, according to embodiments.

Specifically, referring to FIG. 6, member information stored in a plurality of storage units according to embodiments may be shared for each application based on an integrated authentication token. Some or all of the operations according to the embodiments shown in FIG. 6 may be included in step 204c of FIG. 2 and may include operations after step 4l of FIG. 4.

Electronic devices according to embodiments may share information about users used in each application with other applications based on the integrated authentication token 602.

The electronic device 601 according to embodiments includes a processor 601c and a transceiver for performing the operation(s) of sharing information about the user used in each application with other applications based on the integrated authentication token 602. It may include at least one of (601d). The processor 601c and the transceiver 601d may refer to, for example, the processor 110 and the transceiver 120 of FIG. 1 .

Electronic devices according to embodiments may include separate storage unit(s) 600a to 600b for each service (or each application). The storage units 601a to 601b according to the embodiments shown in FIG. 6 may each be understood as a physical storage device, or may be understood as each storage space included in one storage unit, and may be understood as each storage space within one storage unit. It can also be understood as each logical spatial region included. For example, each of the plurality of storage units 601a to 601b may be a database or a table included in one database. Each of the storage units 601a to 601b according to the embodiments shown in FIG. 6 may not necessarily correspond to one application, and one or more applications may share information stored in one storage unit.

The user's terminal device 600 according to embodiments receives an integrated authentication token 602 from the electronic device 601 through an integrated authentication procedure performed by the first application 600a to the nth application 600b. and can be saved. The integrated authentication procedure may mean, for example, the integrated authentication procedure described in FIGS. 4 and 5 .

The first application 600a of the user's terminal device 600 according to embodiments may collect information about the user or the first application 600a from the first storage unit 601a of the electronic device for the first application 600a. ) can receive information to drive. In addition, the first application 600a may receive information about the user or information for running the first application 600a from the mth storage unit 601b of the electronic device for other applications based on the integrated authentication token. You can.

The first application according to embodiments may request data required by the first application from the storage unit 601b for the first application and other applications to the electronic device based on the integrated authentication token stored in the user's terminal device. .

For example, if the first application, which operates a platform for ordering food and delivering it to the user's location, requires the user to input information about the user's delivery address directly, the burden on the user may increase. Accordingly, the first application according to the embodiments may request information about the delivery address from the electronic device according to the embodiments using the integrated authentication token. The electronic device according to embodiments may verify the integrated authentication token in response to the request, obtain the integrated authentication token from another storage unit (e.g., a second storage unit, etc.) containing information about the user's delivery address, and , information about the user's delivery address can be provided to the first application.

The first application according to embodiments may modify, add, delete, or update some or all of the data stored in the first storage unit based on the integrated authentication token stored in the user's terminal device. For example, assume that the user has modified information about the delivery address through a second application. In this case, if the first application directly asks the user to re-enter information about the user's revised delivery address, the burden on the user may increase. Accordingly, the first application according to the embodiments may request an update of information about the delivery address from the electronic device according to the embodiments using the integrated authentication token. The electronic device according to embodiments may verify the integrated authentication token in response to the request, obtain the integrated authentication token from another storage unit (e.g., a second storage unit, etc.) containing information about the user's delivery address, and , information about the modified user's delivery address may be updated or overridden in the first storage unit. Electronic devices according to embodiments include a storage unit used and managed for each application of each service based on an integrated authentication token. By sharing, users can minimize re-entering unnecessary information in the process of receiving multiple services, thereby reducing user confusion.

In addition, electronic devices according to embodiments share a storage unit used and managed for each application of each service based on an integrated authentication token, thereby enabling integrated management of information about the user for each linked service and the user's preferences. Alternatively, since it is based on purchase history, personalized and differentiated services can be provided to users.

Figure 7 shows an example of a method by which an electronic device shares member information for each application according to embodiments.

Specifically, referring to FIG. 7 , member information stored in a plurality of storage units 702 according to embodiments may be shared for each application based on the integrated authentication token 703. Some or all of the operations according to the embodiments shown in FIG. 7 may be included in step 204c of FIG. 2, may include operations after step 4l of FIG. 4, and may include some or all of the operations shown in FIG. 6. can do.

Referring to FIG. 7 , a first application according to embodiments may receive information about a user or member information about a user from a plurality of storage units 702 included in an electronic device according to embodiments.

The first application according to embodiments may receive information about the user or member information about the user through a storage unit for the first application included in the electronic device. Meanwhile, if there is no information about the user or member information about the user in the storage for the first application included in the electronic device, the electronic device may request an integrated authentication token 703 from the user's terminal device. The electronic device may receive the integrated authentication token 703 from the user's terminal device (first application) and check whether the integrated authentication token 703 received from the user's terminal device is a legitimate integrated authentication token. If the electronic device determines that the integrated authentication token is legal, the electronic device searches the storage for applications other than the first application and provides the information required by the first application (for example, member information or information about the user) to the first application. It can be provided as an application.

Likewise, the electronic device can receive the integrated authentication token 703 from the user's terminal device (second application) and check whether the integrated authentication token 703 received from the user's terminal device is a legitimate integrated authentication token. there is. If the electronic device determines that the integrated authentication token is legitimate, the electronic device searches the storage for applications other than the second application and retrieves the information required by the second application (for example, member information about the user or information about the user). It can be provided as an application.

For example, assume that the first application is an application related to shopping mall services, and the second application is an application related to food ordering and delivery services. In order to select items that can be recommended to the user in the first application, the electronic device records past order (payment) details of food orders and deliveries, which were managed and stored in a storage unit (database) for the second application, and food (item) information. ) You can use the search history.

Electronic devices according to embodiments may provide personalized services to users in specific application services based on details of items purchased, ordered, or searched. For example, the electronic device according to embodiments may provide the above-described details of items purchased, ordered, or searched for an application that operates a platform for ordering food and delivering it to the user's location.

The first application according to embodiments may transmit the integrated authentication token 703 to the electronic device. Based on the integrated authentication token 703, the electronic device can inquire order information about items purchased or ordered by the user through a plurality of application services. For example, the electronic device may check order details or search details of purchased or ordered items for a period from the current time to a specific time before. The electronic device according to embodiments may check the history information of items purchased or ordered by the user through a plurality of application services or the search history information of items searched through a plurality of application services, and the details of the items purchased or ordered and the items You can sort your search history information in chronological order. Details of purchased or ordered items may include, for example, the delivery location of each item, the order or purchase time of each item, and category information for each item.

For example, an electronic device according to embodiments may receive a request for a recommended item to be recommended to the user from the user's first application that operates a platform for ordering food and delivering it to the user's location. At this time, the electronic device may further receive a request for a recommended item and an integrated authentication token for the user. After confirming the legitimacy of the integrated authentication token, the electronic device according to embodiments verifies the details of items purchased or ordered by the user and search details of items searched through a plurality of application services from a plurality of storage units in the electronic device, and It can be extracted.

Electronic devices according to embodiments may provide personalized services to users by using details of items purchased or ordered by the user and search details of items searched through a plurality of application services. For example, if the electronic device checks the details of the items purchased or ordered by the user and the name of the item includes the word 'beef' or contains many words included in a list of words similar to 'beef', The first application can be controlled so that items related to 'beef' among the items stored in the storage unit (first storage unit) for one application are exposed to the advertisement or recommended item area in the main screen of the first application. Alternatively, if the electronic device checks the user's search history and the name of the item contains a number of words such as 'beef', 'beef' and 'beef' are selected among the items stored in the storage unit (first storage unit) for the first application. The first application can be controlled so that related items are displayed in an advertisement or recommended item area within the main screen of the first application.

For example, if the user has a purchase history of ordering multiple steak foods through the second application, the electronic device refers to this and assigns item(s) that can cook steak foods in the user's first application to high priority. The first application can be controlled to recommend.

Electronic devices according to embodiments may share point information indicating the user's points with a plurality of applications. Points may refer to cyber money or virtual currency that a user can use to purchase items or order food. The user may acquire points through, for example, a second application. Meanwhile, in order for a user to order items or food using points or to receive services necessary for the user through a plurality of applications, the electronic device according to embodiments may use the user's point information managed in the second application. needs to be shared with other applications.

Accordingly, the first application according to embodiments may request the user's point information 700a stored in the storage unit for the second application while transmitting the integrated authentication token 703 to the electronic device. The first application can receive the user's point information (700b) used in the second application based on the integrated authentication token (703), and use the corresponding point information (700a) in the first application. The electronic device according to embodiments may verify the suitability of the integrated authentication token 703 by checking the integrated authentication token 703 and then transmit the user's point information used in the second application to the first application.

An electronic device according to embodiments may share a user's delivery information with a plurality of applications. Accordingly, the first application according to embodiments may request the user's delivery-related information 700b stored in the storage unit for the second application while transmitting the integrated authentication token 703 to the electronic device. Delivery-related information may include, for example, delivery address information indicating the delivery location, information indicating requests required for delivery, and payment method information indicating the method of payment when purchasing an item.

Based on the integrated authentication token 703, the first application can receive the user's delivery-related information (701b) used in the second application, and the first application can use the user's delivery-related information (700a). there is. The electronic device according to embodiments may verify the suitability of the integrated authentication token 703 by checking the integrated authentication token 703 and then transmit the user's delivery-related information used in the second application to the first application. .

For example, assume that the user has saved three pieces of delivery information in the first application. When a user purchases a specific item or orders a specific item in the second application, the electronic device according to embodiments may store a storage unit for the first application based on the integrated authentication token 703 received from the second application. You can check the three delivery address information included in the storage section. The electronic device according to embodiments may provide three pieces of confirmed delivery address information to the user through the first application. The electronic device according to embodiments may update the three pieces of confirmed delivery address information in the storage unit (second storage unit) for the second application.

Also, for example, assume that the user has stored two pieces of information indicating payment methods in the second application. When a user purchases a specific item or orders a specific item in the first application, the electronic device according to embodiments may store a storage unit for the second application based on the integrated authentication token 703 received from the first application. You can check two pieces of information indicating the payment method included in the storage unit.

Electronic devices according to embodiments may modify and update data stored in a storage unit (first storage unit) for the first application through the first application. Additionally, electronic devices according to embodiments may store, modify, and update data stored in a storage unit for other applications using the integrated authentication token 703.

Electronic devices according to embodiments share a storage unit used and managed for each service application based on an integrated authentication token, thereby minimizing user confusion by re-entering unnecessary information in the process of providing multiple services to the user. can be reduced.

In addition, electronic devices according to embodiments share a storage unit used and managed for each application of each service based on an integrated authentication token, thereby enabling integrated management of information about the user for each linked service and the user's preferences. Alternatively, since it is based on purchase history, personalized and differentiated services can be provided to users.

Meanwhile, the specification and drawings disclose preferred embodiments of the present invention, and although specific terms are used, they are used in a general sense to easily explain the technical content of the present invention and to aid understanding of the present invention. It is not intended to limit the scope of the invention. In addition to the embodiments disclosed herein, it is obvious to those skilled in the art that other modifications based on the technical idea of the present invention can be implemented.

The electronic device or terminal according to the above-described embodiments includes a processor, memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with an external device, a touch panel, and a key. ), user interface devices such as buttons, etc. may be included. Methods implemented as software modules or algorithms may be stored on a computer-readable recording medium as computer-readable codes or program instructions executable on a processor. Here, computer-readable recording media include magnetic storage media (e.g., ROM (read-only memory), RAM (random-access memory), floppy disk, hard disk, etc.) and optical read media (e.g., CD-ROM). ), DVD (Digital Versatile Disc), etc. The computer-readable recording medium is distributed among computer systems connected to a network, so that computer-readable code can be stored and executed in a distributed manner. The media may be readable by a computer, stored in memory, and executed by a processor.

This embodiment can be represented by functional block configurations and various processing steps. These functional blocks may be implemented as any number of hardware or/and software configurations that execute specific functions. For example, embodiments include integrated circuit configurations such as memory, processing, logic, look-up tables, etc. that can execute various functions under the control of one or more microprocessors or other control devices. can be hired. Similar to how the components can be implemented as software programming or software elements, this embodiment includes various algorithms implemented as combinations of data structures, processes, routines or other programming constructs, such as C, C++, Java ( It can be implemented in a programming or scripting language such as Java), assembler, etc. Functional aspects may be implemented as algorithms running on one or more processors. Additionally, this embodiment may employ conventional technologies for electronic environment settings, signal processing, and/or data processing. Terms such as “mechanism,” “element,” “means,” and “configuration” may be used broadly and are not limited to mechanical and physical configurations. The term may include the meaning of a series of software routines in connection with a processor, etc.

The above-described embodiments are merely examples and other embodiments may be implemented within the scope of the claims described below.

Meanwhile, the specification and drawings disclose preferred embodiments of the present invention, and although specific terms are used, these are merely used in a general sense to easily explain the technical content of the present invention and aid understanding of the present invention. It is not intended to limit the scope of the invention. In addition to the embodiments disclosed herein, it is obvious to those skilled in the art that other modifications based on the technical idea of the present invention can be implemented.

Claims (11)

As a method of managing member information of an electronic device,
Checking whether the user terminal is logged in to the first application in response to execution of the first application;
If the user terminal is not logged in to the first application, checking member information for the second application corresponding to the user; and
Comprising a step of performing a login procedure of the first application for the user based on member information of the second application,
The member information includes point information associated with the second application of the user,
The above member information management method is
In response to the user's login to the first application, the member information management method further includes providing the point information associated with the second application to the user terminal. The method of claim 1, wherein the step of checking member information for the second application includes checking whether the second application is installed on the user's terminal device.
How to manage member information. According to paragraph 1,
The above member information management method is:
When the login procedure performed using the member information of the second application is completed, providing member information about the second application to the first application,
The user terminal logs in to the first application based on member information for the second application,
How to manage member information. The method of claim 1, wherein the member information management method is:
Further comprising checking whether the user will log in to the first application using the login information of the first application or the login information of the second application,
How to manage member information. The method of claim 4, wherein the member information management method is:
When the user decides to log in to the first application with the login information of the second application, providing a first page for performing a membership registration process for the first application to the user's terminal device. Including more,
How to manage member information. The method of claim 1, wherein the step of checking member information for the second application is
If the second application is not installed on the user's terminal device, providing a second page for installing the second application to the user's terminal device,
How to manage member information. The method of claim 1, wherein the login procedure is:
generating an integrated login token and transmitting it to the first application of the user;
Receiving an access token for the second application and the integrated login token from the second application; and
confirming whether the user is a member of the second application based on the access token for the second application; Including,
How to manage member information. The method of claim 7, wherein if the user is a member of the second application, the login procedure is:
Transmitting a member confirmation success message to the second application;
Receiving the integrated login token from the first application; and
transmitting an access token for the first application to the first application; Including,
How to manage member information. The method of claim 3, wherein the providing step includes:
Receiving a request for an integrated authentication token and information about the user from the user's terminal device;
confirming whether the integrated authentication token is a legitimate token for the user; and
Confirming information about the user based on the integrated authentication token and transmitting the information about the user; Including,
How to manage member information. In an electronic device that performs a method of managing member information,
a memory in which at least one program is stored; and
In response to execution of the first application, it is checked whether the user terminal is logged in to the first application, and if the user terminal is not logged in to the first application, member information about the second application corresponding to the user is stored. a processor that verifies and performs a login procedure of the first application for the user based on member information of the second application;
The member information includes point information associated with the second application of the user,
The processor is configured to provide the point information associated with the second application to the user terminal in response to the user's login to the first application,
Electronic devices. A non-transitory computer-readable storage medium, comprising:
Includes a medium on which computer-readable instructions are stored,
When the computer-readable instructions are executed by a processor, the processor:
Checking whether the user terminal is logged in to the first application in response to execution of the first application;
If the user terminal is not logged in to the first application, checking member information for the second application corresponding to the user; and
configured to perform a login procedure of the first application for the user based on member information of the second application,
The member information includes point information associated with the second application of the user,
The processor is
In response to the user's login to the first application, further configured to provide the point information associated with the second application to the user terminal,
A non-transitory computer-readable storage medium.