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

Abstract

According to embodiments, provided is a method for managing member information, which may include the steps of: determining whether a user is logged in to a first application; checking whether to log in the first application with information on a user of the first application from the user; checking whether an authentication procedure of the first application is performed using information on the user of the second application from the user; checking whether the second application is installed in a terminal device of the user; and checking whether the user is logged in with member information for the second application.

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 apparatus for integrating and managing member information. More specifically, the present disclosure relates to a method and apparatus 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 log-in, and is in the spotlight because users can use it easily without entering 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 in order to access the site is completed in one operation, eliminating the inconvenience. It has the advantage of being able to maximize marketing.

Regarding prior patent literature, there is Republic of Korea Patent Registration No. 10-2157743 (2020.09.14).

The problem to be solved by the present embodiment is to provide a management method and apparatus by integrating member information to solve the above problems.

More specifically, the present disclosure provides a method and apparatus for simplifying an authentication procedure for a plurality of service applications providing different services through an integrated authentication procedure and sharing necessary information between a plurality of services through a server. it's about

In order to solve the above problems, a method for managing member information according to embodiments includes the steps of checking whether or not a log-in is performed for a first application; checking whether to log in to the first application with login information of the first application from the user; checking whether or not an authentication procedure of the first application is performed using log-in information of the second application from the user; checking whether the second application is installed in the user's terminal device; and checking whether the user is logged in with member information for the second application. may include at least one of them.

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

A member information management method according to embodiments may include providing information about a user to a first application based on member information about a second application.

In a method for managing member information according to embodiments, when a user determines to log in to a first application with login information of a second application, a page for proceeding with a membership sign-up procedure for the first application is provided to the user's terminal device. It may include providing steps.

The method 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 a first application based on member information of a second application according to embodiments may include generating an integrated login token and transmitting the integrated login token 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; checking whether the user is a member of the second application based on the access token for the second application; transmitting a member verification success signal to the second application if the user is a member of 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 a user to a first application based on member information about a second application according to embodiments includes receiving a request for an integrated authentication token and information about a user from a terminal device of the user; checking whether the integrated authentication token is a legitimate token for the user; and verifying information about the user based on the integrated authentication token and transmitting the information about the user. may include at least one of them.

An electronic device according to embodiments may perform an authentication procedure for a user through an integrated procedure without individual authentication processes for each of a plurality of applications, thereby simplifying a procedure required for a user to log in.

The electronic device according to the embodiments shares a storage used and managed for each application of each service based on an integrated authentication token, thereby minimizing unnecessary re-entry of information in the process of providing various services to the user, resulting in user confusion. can reduce

In addition, the electronic device according to the embodiments shares a storage unit used and managed for each application of each service based on the integrated authentication token, enabling integrated management of user information for each interlocking service, and user preference Or, since it is based on the purchase history, personalized and differentiated services can be provided to the user.

1 shows an example of internal components of an electronic device according to embodiments.
2 shows an example of a method for managing member information according to embodiments.
3 shows an example of a user interface for a method for managing member information according to embodiments.
4 illustrates an example of performing an authentication procedure for a first application based on login information of a second application according to embodiments.
5 shows an example of a member information management method according to embodiments.
6 illustrates 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.
7 illustrates an example of a method for an electronic device to share member information for each application according to embodiments.

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

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

For the same reason, in the accompanying drawings, some components are exaggerated, omitted, or schematically illustrated. Also, the size of each component does not entirely reflect the actual size. In each figure, the same reference number is assigned to the same or corresponding component.

Advantages and features of the present invention, and methods for achieving them, will become clear with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only the present embodiments make the disclosure of the present invention complete, and common knowledge in the art to which the present invention belongs It is provided to fully inform the holder of the scope of the invention, and the present invention is only defined by the scope of the claims. Like reference numbers designate like elements throughout the specification.

At this time, it will be understood that each block of the process flow chart diagrams and combinations of the flow chart diagrams can be performed by computer program instructions. These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment are described in the flowchart block(s). It creates means to perform functions. These computer program instructions may also be stored in a computer usable or computer readable memory that can be directed to a computer or other programmable data processing equipment to implement functionality in a particular way, such that the computer usable or computer readable memory The instructions stored in are also capable of producing an article of manufacture containing instruction means that perform the functions described in the flowchart block(s). The computer program instructions can also be loaded 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 computer-executed process to generate computer or other programmable data processing equipment. Instructions for performing processing equipment may also provide steps for performing the functions described in the flowchart 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). It should also be noted that in some alternative implementations it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible that two blocks shown one after another may in fact be executed substantially in parallel, or that the blocks may sometimes be executed in reverse order depending on their function.

At this time, the term '~unit' used in this embodiment means software or a hardware component such as FPGA or ASIC, and '~unit' performs certain roles. However, '~ part' is not limited to software or hardware. '~bu' may be configured to be in an addressable storage medium and may be configured to reproduce one or more processors. Therefore, as an example, '~unit' 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. Functions provided within components and '~units' may be combined into smaller numbers of components and '~units' or further separated into additional components and '~units'. In addition, components and '~units' may be implemented to play one or more CPUs in 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 , internal components of the electronic device 100 are not limited to the illustrated components. 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 a method for managing item feed information according to various embodiments of the present disclosure. The processor 110 may control other elements of the electronic device 100 . An item may be sold to a user in a service related to the electronic device 100 .

Checking, by the processor 110, whether the first application is logged in; checking whether to log in the first application with information about the user of the first application from the user; confirming whether an authentication procedure of the first application is performed using information about the user of the second application from the user; checking whether the second application is installed in the user's terminal device; and checking whether the user is logged in with member information for the second application. At least one of these may be performed. Programs or computer readable instructions executed by the processor 110 may be previously 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 transmits information stored in the memory 130 of the electronic device 100 or information processed by the processor 110 to another device, or functions to receive information from another device to the electronic device 100. can be done

The memory 130 is a configuration implemented in a predetermined storage space of the electronic device 100, and may include a database in which functions such as storage, search, deletion, editing, or addition of data can be freely performed. there is. For example, the memory 130 may include fields or components for processing functions such as data storage, search, deletion, editing, or addition. The memory 130 may store data related to the electronic device 100 performing an information providing method. For example, the memory 130 may store instructions or data for an execution operation of the processor 110 . The memory 130 according to embodiments may include a database for storing information on items and the like.

An electronic device according to embodiments may manage member information for one service. Member information according to embodiments includes, for example, information capable of identifying a user using a corresponding service or authenticating a user. For example, member information may include an ID of a corresponding user and a password for accessing a service with the corresponding ID.

Member information according to embodiments may exist differently for each application service. For example, member information for an application that operates a platform that orders food and delivers it to the user's location (hereinafter referred to as a first application or a first application service) is used to search for, purchase, and pay for items. It may be different from member information for an application (hereinafter referred to as a second application or a second application service) that operates a platform that delivers a corresponding item to the user's location. 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 may be 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. 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 manage information about users stored in the memory. The 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.

An electronic device according to embodiments may separately store information about users for each application service due to reasons such as a personal information storage policy and a security problem related to personal information. For example, the electronic device may include a first storage unit for use in 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 (eg, personal information). , item delivery related information, etc.). That is, an electronic device according to embodiments may include a separate storage unit for each service provided by the electronic device (eg, application of the terminal device). In addition, the electronic device according to the embodiments may use a storage unit (eg, a database, etc.) related to the electronic device according to a separate authentication procedure from the terminal device according to the embodiments for each service.

For example, a first storage unit for a first application that operates a platform for ordering food and delivering it to the user's location includes first member information of the user for the first service and a first storage unit indicating the location of a seller who sells food. It may include at least one of location information, each name and price of each item (food) by the seller, information about deliverymen 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, a second storage unit for a second application that operates a platform that searches for, purchases, and pays for items and delivers the items to the user's location stores second member information of the user for the second service and items. It may include at least one of information about distribution centers, names and prices of items stored in the server of the second application, and second delivery location information indicating a user's delivery location.

When the user's terminal device according to the embodiments executes the first application, the electronic device and the first application according to the embodiments are used to use information about the user used in the first application service stored in the first storage unit. You can perform an authentication procedure for That is, the electronic device according to the embodiments provides information about the user stored in the first storage unit as the first application based on an access token for the first application generated after completing the authentication process for the first application. can provide information. Similarly, when a second application is executed, the user's terminal device according to the embodiments may use the information about the user used in the second application service stored in the second storage unit and the electronic device according to the embodiments. 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 unit to the second application based on the access token for the second application generated after completing the authentication process for the second application. can

Meanwhile, in an electronic device that provides a plurality of services, when a separate authentication procedure with a terminal device is required for each service (for example, an access token for a first application and an access token for a second application are provided by the electronic device). If the user's terminal device retrieves information about the user from the electronic device based on a separate token), the burden of the procedure is given to the user, and the user's terminal device is separately generated for each application based on a separate token for each application. It may be difficult to share commonly required information for each service between applications. In addition, since redundant data between services is separated and stored, it is not efficient in terms of storage space.

Accordingly, the electronic device according to embodiments may simplify the authentication procedure of the first application by performing a valid integrated authentication procedure in the second application (service). In addition, the electronic device according to the embodiments simply performs an authentication procedure between the first applications by using a valid integrated authentication procedure between the second applications (and an authentication token for the second application generated by the valid authentication procedure). can do. In addition, through such an integrated authentication process, the first application according to embodiments may receive and share member information (or information about a user) used in the second application. Hereinafter, examples of the operation and configuration of an electronic device performing this method will be described.

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

An electronic device according to embodiments may perform some or all of the operations of the member information management method shown in FIG. 2 . Specifically, FIG. 2 is an example of an operation of managing member information by an electronic device according to embodiments. 2 illustrates, for example, an operation of performing a login procedure for a first application in order to log in to a first application, or 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 by 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 for 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 the embodiments executes the first application according to the execution signal of the user's first application. An electronic device according to embodiments may check whether session information indicating legitimate authentication for one application is present in the terminal device. That is, the electronic device may check (200) whether the terminal device has already logged in to 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 from the electronic device (eg, the first application server in the electronic device). Tokens can be held.

If the user has completed logging in to the first application (ie, authentication of the first application between the electronic device and the user's terminal device has already been performed), the electronic device according to the embodiments provides information about the first application. Information on the user may be provided to the first application based on the member information (200a). An electronic device according to embodiments receives an access token for a first application from a terminal device of a user, and uses the received access token to check member information for the user. The electronic device provides information about the user based on the verified member information (200a). In this case, information about a user according to embodiments may mean information about a user identified by member information about the first application in an electronic device according to embodiments.

If the user is not logged in to the first application (ie, authentication of the first application is not performed between the electronic device and the user's terminal device), the electronic device according to embodiments may allow the user to log in to the first application. It is possible to check (201) whether or not to log in with the login information of the application. Login information is, for example, information that a terminal device of a user receives from a user, and may refer to information for the user to perform an authentication procedure for a corresponding application service. The login information may include, for example, ID information, e-mail information, or password information for performing an authentication procedure for a corresponding application service. An electronic device according to embodiments may request a query to the user's terminal device to check whether the user logs in with the login information of the first application.

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

If the user does not select to log in with the login information of the first application, the electronic device according to embodiments checks whether the user logs in to the first application with the login information of the second application (202). can do. For example, when the user selects to log in to the first application with the login information of the second application, the electronic device provides the user's member information for the second application based on the login information of the second application input from the user. It can be confirmed from the second storage unit.

Meanwhile, when the user selects not to log in to the first application with the login information of the second application, the electronic device proceeds with a membership sign-up procedure for generating member information for the first application in the first storage unit (202a). Alternatively, the first application in a state in which authentication is not completed may be provided. However, when the user proceeds and completes the membership sign-up process for the first application, the electronic device according to embodiments may provide the first application by using member information about the first application newly input by the user, , information on the corresponding user may be provided to the first application (200a).

When the user selects to log in to the first application with 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 in the user's terminal device. You can confirm (203). If the second application is not installed in 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). When the second application is not installed in the user's terminal device, the terminal device according to embodiments may search for and check the second application in the App Store to install the second application.

When the second application is installed in 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 in the user's terminal device, the electronic device according to embodiments may check (204) whether the user is logged in to the second application with login information for the second application. 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. It can be checked through the device.

If the user is not currently logged in to the second application (ie, authentication of the second application between the electronic device and the user's terminal device has not been performed), the electronic device according to embodiments of the present disclosure A login page of the second application for proceeding with 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 search for member information of the second application for the user. The electronic device according to embodiments may perform an integrated login procedure (integrated authentication procedure) for the first application based on the member information of the second application that has been inquired at (204b). The integrated login procedure (integrated authentication procedure) is an authentication procedure for other application(s) based on the results of the legitimately performed authentication procedure when the user has properly performed the authentication procedure based on the authentication procedure for a specific application. refers to the process of performing The integrated authentication procedure is described in detail, for example, in FIGS. 4 and 5 . When an electronic device according to embodiments properly performs an integrated authentication procedure with a user's terminal device, an integrated authentication token may be provided to the user's terminal device, and the terminal device may store the integrated authentication token. The plurality of application(s) related to the terminal device of the user according to embodiments may perform an authentication procedure based on the integrated authentication token according to the 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 the embodiments may check necessary information from the member information of the second application inquired in the process of performing the integrated login procedure for the first application. Among the necessary information, the electronic device according to embodiments may receive information that cannot be identified from the member information for the second application from the user, and search for information from other application(s) other than the first application and the second application. can be obtained by

On the other hand, in all embodiments, customers who have subscribed to the second application through such a procedure can use the login information of the second application to log in to the first application that is not a member, 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, a separate member sign-in procedure is not required in the first application based on the second application subscription information. Also, the first set of information can be shared between the two applications, and the second set of information can be independently managed. For example, the first set of information may include point information, and the second set of information may include delivery address information. However, when logging in to the first application for the first time, some of the information included in the second set may be set based on information entered in the second application, and after initial setting, information included in the second set is separately modified in the first application. or can be added.

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

An electronic device according to embodiments may perform an authentication procedure for a user through an integrated procedure without individual authentication processes for each of a plurality of applications, thereby simplifying a procedure required for a user to log in.

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

Specifically, FIG. 3 illustrates a method of performing an authentication procedure for a first application based on member information for a 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 some or all of steps 200 to 204c of FIG. 2 , for example.

3(A) shows a case where the user executes 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 indicate a case in which login to the first application is not currently performed in step 200 of FIG. 2 .

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

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

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

A terminal device of a user according to embodiments may render a first area 300 - 1 for querying a login method from the user on the page 300 of the first application. The first area 300-1 according to embodiments is a method for checking whether to log in to the first application (300a) by using the login information of the second application in order to log in to the first application. A first interface (300a), a second interface (300b) for determining whether or not to log in to the first application (300b) by directly receiving login information of the second application from the user, and registering as a member of the first application It may include at least one of a third interface for confirming whether to execute (300c) and a fourth interface for confirming whether to perform login with login information for the first application.

3(B) illustrates 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 That is, when the user clicks the first interface 300a in FIG. 3(A), the user's terminal device or electronic device according to the embodiments (when the second application is installed in the user's terminal device) displays a second application. can be executed (eg, step 203 of FIG. 2). Meanwhile, when the user clicks the first interface 300a but the second application is not installed in 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) may 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 or not to attempt to log in with the login information for the second application to log in the first application. A fifth interface 301a for querying may be provided. When the user clicks the fifth interface 301a, the electronic device according to embodiments may perform an authentication procedure for the first application based on login information of the second application (eg, 204b of FIG. 2 ), Information on the user may be provided to the first application based on the login information for the second application (eg, 204c of FIG. 2 ).

The electronic device according to the embodiments may check necessary information from the member information of the second application inquired in the process of performing the integrated login procedure for the first application. Among the necessary information, the electronic device according to embodiments may receive information that cannot be identified from the member information for the second application from the user, and search for information from other application(s) other than the first application and the second application. can be obtained by

Meanwhile, as described above, the user may attempt to log in using log-in information different from that of the second application for log-in of the first application. Also, there may be a case in which 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 the second interface 300b (31), or when the user clicks the first interface 300a, but as a result of the execution of the second application, the user is not logged in in 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.

3(C) illustrates 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 the first interface 300a in FIG. 3(A), the user's terminal device or electronic device according to embodiments (when the second application is installed in the user's terminal device) displays the second application. It can be executed (eg, step 203 in FIG. 2). Meanwhile, when the user clicks the first interface 300a but the second application is not installed in 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) may be performed.

An electronic device according to embodiments may perform an authentication procedure for a user through an integrated procedure without individual authentication processes for each of a plurality of applications, thereby simplifying a procedure required for a user to log in.

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

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

Referring to FIG. 4 , a user according to embodiments may execute a 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 terminal device 400 of the user.

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 refer to login based on an authentication procedure for logging in to the first application with information (login information) about a user of the second application, for example. That is, the user's terminal device may request integrated authentication login for logging in to the first application using the login information of the second application (4b).

In response to receiving an integrated authentication log-in request 4b from the terminal device 400, the electronic device 401 according to the embodiments generates an SSO Token for integrated authentication, so that the user's terminal device 400 ) can be transmitted (4c). The SSO Token may be generated by the first application member information management unit 401a or the 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 (4d) the received integrated authentication token to the second application 400b. The user's terminal device 400 according to embodiments executes the second application 400b and transfers the received integrated authentication token to the second application 400b.

When the user's terminal device 400 or electronic device 401 according to embodiments is not logged in to the second application in the user's terminal device (ie, for the second application in the user's terminal device) If there is no access token), the user may 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 for the second application for the user.

The user's terminal device 400 according to embodiments transmits the user's access token for the second application and the integrated authentication token according to embodiments to the electronic device 401 according to embodiments (4f). Specifically, the user's terminal device 400 transmits 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 checks 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 and the integrated authentication token received from the second application are compared and contrasted. The electronic device 401 (the first application member information management unit 401a or the authentication confirmation unit 401b) according to the embodiments determines whether the corresponding user is a legitimate or valid user of the second application, the second application The user's access token for the second application may be queried (4g) to the member information management unit 401c.

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

Upon receiving the authentication success signal 4h from the electronic device 401, the second application 400b according to embodiments may transmit an authentication success signal to the first application in response to this (4i).

The first application 400a according to embodiments is sent to the electronic device 401 or the first application member information management unit 401a according to embodiments in response to receiving the authentication success signal from the second application (4i). At least one of the aforementioned integrated authentication token and authentication success signal 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 400a to the first application 400a. An access token (authentication token) for the first application may be transmitted (4k) so as to access the application. The first application 400a according to embodiments may perform (4l) login for a user based on the received access token 4k.

An electronic device according to embodiments may perform an authentication procedure for a user through an integrated procedure without individual authentication processes for each of a plurality of applications, thereby simplifying a procedure required for a user to log in.

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

Specifically, FIG. 5 is a flowchart illustrating an example of performing an authentication procedure for a first application based on login information of a second application according to embodiments. 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 an electronic device according to embodiments. The operation shown in FIG. 5 may include, for example, some or all of operations 204, 204b, and 204c of FIG. 2, and may include operations shown in FIGS. 3(A) to 3(C). .

An 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 . An electronic device according to embodiments may receive an access token for a second application different from the first application and the integrated login token from the second application (501). 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 a member verification success signal to the second application (503). The operation of step 503 may include, for example, operation 4h of FIG. 4 . An electronic device according to embodiments may receive an integrated login token from the first application (504). 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 according to embodiments may include, for example, an access token for the second application stored in a storage unit (second application) included in an electronic device according to embodiments. storage unit) may be included.

In the receiving of the integrated login token from the first application according to embodiments, the integrated login token and the member verification success signal may be received, for example.

Meanwhile, when the user's terminal device completes the integrated authentication procedure, the electronic device according to the embodiments provides information about the user (eg, 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 a user used in the second application with the first application based on the integrated authentication token.

For example, it is assumed that 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 this case, in order to select an item that can be recommended to the user in the first application, the electronic device stores order (payment) history of food orders and delivery in the past, 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 meals through the second application, the electronic device refers to this and prioritizes the item(s) for cooking steak food in the user's first application with high priority. The first application may be controlled to be recommended.

For example, when the user sets a delivery location in the first application, if the user has to set the same delivery location in the second application, the user may be burdened. Accordingly, the electronic device may share information indicating a delivery place set in the first application with the second application.

6 illustrates 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 .

An electronic device according to embodiments may share information about a user used in each application to 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 an operation(s) of sharing information about a user used in each application to another application based on the integrated authentication token 602 (601d) may include at least one. The processor 601c and the transceiver 601d may mean, for example, the processor 110 and the transceiver 120 of FIG. 1 .

An electronic device according to embodiments may include separate storage unit(s) 600a to 600b for each service (or each application). Each of the storage units 601a to 601b according to the embodiments shown in FIG. 6 may be understood as a physical storage device or each storage space included in one storage unit, and may be understood as each storage space included in one storage unit. It can also be understood as each logical space area 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 be shared from information stored in one storage unit.

The user's terminal device 600 according to embodiments receives the integrated authentication token 602 from the electronic device 601 by the integrated authentication procedure performed by the first application 600a to the n-th application 600b. and can be stored. 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 is information about the user or the first application 600a from the first storage unit 601a of the electronic device for the first application 600a. ) may receive information for driving. In addition, the first application 600a receives information about a user or information for driving the first application 600a from the m-storage unit 601b of the electronic device for other applications based on the integrated authentication token. can

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

For example, when a first application that operates a platform for ordering food and delivering food to the user's location receives information about the user's delivery address directly from the user, the user's burden may increase. Accordingly, the first application according to embodiments may request information on the delivery address from the electronic device according to embodiments using the integrated authentication token. An electronic device according to embodiments may verify an integrated authentication token in response to a corresponding request, obtain it from another storage unit (eg, a second storage unit, etc.) including information on the user's delivery address, , information on the user's delivery address may 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, it is assumed that the user has modified information about the delivery address through the second application. In this case, if the first application directly receives information about the user's modified delivery address from the user again, a burden may be added to the user. Accordingly, the first application according to embodiments may request an update of information on the delivery address to the electronic device according to embodiments using the integrated authentication token. An electronic device according to embodiments may verify an integrated authentication token in response to a corresponding request, obtain it from another storage unit (eg, a second storage unit, etc.) including information on the user's delivery address, , Information on the modified user's delivery address may be updated or overridden in the first storage unit. An electronic device according to embodiments includes a storage unit used and managed for each application of each service based on an integrated authentication token. By sharing, it is possible to minimize re-entry of unnecessary information in the process of providing various services to the user, thereby reducing user confusion.

In addition, the electronic device according to the embodiments shares a storage unit used and managed for each application of each service based on the integrated authentication token, enabling integrated management of user information for each interlocking service, and user preference Or, since it is based on the purchase history, personalized and differentiated services can be provided to the user.

7 illustrates an example of a method for an electronic device to share 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 an 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 include some or all of the operations shown in FIG. 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 as a storage unit for the first application included in the electronic device. Meanwhile, when 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 the 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 may check whether the integrated authentication token 703 received from the user's terminal device is a legitimate integrated authentication token. When the electronic device determines that the integrated authentication token is legitimate, the electronic device queries a storage unit for an application other than the first application to provide necessary information (eg, member information about the user or information about the user) to the first application. It can be provided as an application.

Similarly, the electronic device may receive the integrated authentication token 703 from the user's terminal device (second application) and confirm whether the integrated authentication token 703 received from the user's terminal device is a legitimate integrated authentication token. there is. When the electronic device determines that the integrated authentication token is legitimate, the electronic device queries the storage unit for an application other than the second application, and transfers information required by the second application (eg, member information about the user or information about the user) to the second application. It can be provided as an application.

For example, it is assumed that 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 items that can be recommended to the user in the first application, the electronic device stores food order and delivery history, food (item items) managed and stored in a storage unit (database) for the second application. ) can be used for search history.

An electronic device according to embodiments may provide a personalized service to a user in a specific application service based on details of purchased, ordered, or searched items. For example, the electronic device according to embodiments may provide the above-described details of purchased, ordered, or searched items to a corresponding application for an application operating a platform for ordering and delivering food to a 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 may inquire order information about items purchased or ordered by a corresponding user through a plurality of application services. For example, the electronic device may check order details or search details for a period from a current time to a specific time, among purchased or ordered items. An electronic device according to embodiments checks detail information of items purchased or ordered by a corresponding user through a plurality of application services or search detail information of items searched through a plurality of application services, and provides details and items of purchased or ordered items. Search history information can be sorted in chronological order. Details of purchased or ordered items may include, for example, delivery location of each item, order or purchase time of each item, and category information on each item.

For example, the electronic device according to embodiments may receive a request for a recommendation item to be recommended to the user from a 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 a corresponding user. After confirming the legitimacy of the integrated authentication token, the electronic device according to embodiments checks details of items purchased or ordered by the corresponding user and search details of items searched through a plurality of application services from a plurality of storage units in the electronic device, and can be extracted.

An electronic device according to embodiments may provide a personalized service to a user by using details of items purchased or ordered by a corresponding user and search details of items searched through a plurality of application services. For example, when the electronic device checks the details of items purchased or ordered by the user and the word 'beef' is included in the name of the item or a number of words included in a list of words similar to 'beef' are included, The first application may be controlled to expose an item related to 'beef' among items stored in the storage unit (first storage unit) for the first application to an advertisement or recommended item area on the main screen of the first application. Alternatively, when the electronic device checks the user's search history and the word 'beef' is included in many items in the name of the item, among the items stored in the storage unit (first storage unit) for the first application, 'beef' and The first application may be controlled to expose a related item to an advertisement or recommendation item area in the main screen of the first application.

For example, if the user has a purchase history of ordering multiple steak meals through the second application, the electronic device refers to this and prioritizes the item(s) for cooking steak food in the user's first application with high priority. The first application may be controlled to be recommended.

An electronic device according to embodiments may share point information indicating a user's points with a plurality of applications. Points may mean cyber money or virtual currency that a user can use to purchase items or order food. The user may acquire points through, for example, the second application. Meanwhile, in order for a user to use points to place an order for items or food, or to receive a service necessary for the user through a plurality of applications, the electronic device according to embodiments provides information about the user's points managed by a second application. need 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. Based on the integrated authentication token 703, the first application may receive point information 700b of a user used in the second application, and may use the 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 user 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. The delivery-related information may include, for example, delivery destination information indicating a delivery location, information indicating a request necessary for delivery, and payment method information indicating a payment method when purchasing an item.

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

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

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

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

The electronic device according to the embodiments shares a storage used and managed for each application of each service based on an integrated authentication token, thereby minimizing unnecessary re-entry of information in the process of providing various services to the user, resulting in user confusion. can reduce

In addition, the electronic device according to the embodiments shares a storage unit used and managed for each application of each service based on the integrated authentication token, enabling integrated management of user information for each interlocking service, and user preference Or, since it is based on the purchase history, personalized and differentiated services can be provided to the user.

On the other hand, preferred embodiments of the present invention have been disclosed in the present specification and drawings, and although specific terms have been used, they are only used in a general sense to easily explain the technical content of the present invention and help understanding of the present invention. It is not intended to limit the scope of the invention. It is obvious to those skilled in the art that other modified examples based on the technical idea of the present invention can be implemented in addition to the embodiments disclosed herein.

An electronic device or terminal according to the above-described embodiments includes a processor, a memory for storing and executing program data, a permanent storage unit 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, and the like. 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, the computer-readable recording medium includes magnetic storage media (e.g., read-only memory (ROM), random-access memory (RAM), floppy disk, hard disk, etc.) and optical reading media (e.g., CD-ROM) ), and DVD (Digital Versatile Disc). A computer-readable recording medium may be distributed among computer systems connected through a network, and computer-readable codes may be stored and executed in a distributed manner. The medium may be readable by a computer, stored in a memory, and executed by a processor.

This embodiment can be presented as functional block structures and various processing steps. These functional blocks may be implemented with any number of hardware or/and software components that perform specific functions. For example, an embodiment is an integrated circuit configuration such as memory, processing, logic, look-up table, etc., which can execute various functions by control of one or more microprocessors or other control devices. can employ them. Similar to components that can be implemented as software programming or software elements, the present embodiments include data structures, processes, routines, or various algorithms implemented as combinations of other programming constructs, such as C, C++, Java ( It can be implemented in a programming or scripting language such as Java), assembler, or the like. Functional aspects may be implemented in an algorithm running on one or more processors. In addition, this embodiment may employ conventional techniques for electronic environment setting, signal processing, and/or data processing. Terms such as "mechanism", "element", "means", and "composition" may be used broadly and are not limited to mechanical and physical components. The term may include a meaning of a series of software routines in association with a processor or the like.

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

On the other hand, preferred embodiments of the present invention have been disclosed in the present specification and drawings, and although specific terms have been used, they are only used in a general sense to easily explain the technical content of the present invention and help understanding of the present invention. It is not intended to limit the scope of the invention. It is obvious to those skilled in the art that other modified examples based on the technical idea of the present invention can be implemented in addition to the embodiments disclosed herein.

Claims (1)

As a member information management method of an electronic device,
checking whether the user terminal is logged in to the first application in response to execution of the first application;
checking member information on a second application corresponding to the user when the user terminal is not logged in to the first application;
performing a login procedure of the first application for the user based on member information of the second application;
checking a search history of the user 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,
How to manage member information.

Images