KR20100073884A - Method of intermediation and synchronization customer information based on id federation - Google Patents

Abstract

PURPOSE: A method for intermediation and synchronization of customer information based on ID federation are provided to relay additional information of a client permission and policy base through client interaction and synchronize client information between affiliated service sites thereby easily matching the client information to the affiliated service sites. CONSTITUTION: If additional acquisition of a client information is required, a server of service B obtains information providing agreement of a client after displaying of necessary item through performing of client interaction(419,421). If possession information of ID federation system among agreed information does not exist, the ID connecting system searches the client information from affiliated service sites(422,432). If the client information does not exist, the ID connecting system obtains the client information(433,436). The ID connecting system performs synchronization.

Description

Brokerage and synchronization of customer information based on ID linkage {METHOD OF INTERMEDIATION AND SYNCHRONIZATION CUSTOMER INFORMATION BASED ON ID FEDERATION}

The present invention relates to a method of brokering and synchronizing customer information based on ID linkage, and more specifically, after verifying ID mapping information at the time of linkage authentication of a customer and performing automatic authentication with another affiliate service, If additional information is needed, mediating the customer's additional information based on permission and policy through customer interaction and synchronizing the customer information with each other through the affiliate sites, it is possible to easily mediate the customer information between the affiliate sites. And it relates to a method of brokering and synchronizing the customer information based on the ID linkage, which can easily match customer information between affiliate sites.

In the Internet service, a profile registration process including a user's ID and password is pre-registered with a service provider (SP) through a membership registration process. Through this process, the user inputs ID and password through the user terminal to complete authentication from the service provider. Then, the user can use the corresponding service through the user terminal.

Recently, with the increase and development of services through the Internet, securing personal information and ensuring user convenience have become important issues. Therefore, efforts are being made to provide Internet services to users more safely and conveniently through federation ID or user-centered ID management rather than centralized ID management.

As part of this effort, there is an authentication technology that allows a member of a web site to have the same rights as a member of the site without a separate login procedure when the web site is linked to an external site linked to the site. In particular, in such authentication technology, when a user wants to join a specific site (sub site), the member information of the already subscribed site (main site) is transmitted to the sub site. Then, the sub site does not require a separate login procedure to the user, but provides the user with the same authority as a member of the main site. Such authentication technology is a single sign-on (SSO) technology. In other words, the single sign-on technique is intended to facilitate authentication between heterogeneous sites. Single sign-on technology is intended to simplify the registration and login process at the sub site when a user of one site (main site) goes to another site (sub site).

In addition, the "Liberty Alliance group" manages the user ID and password for each service provider (SP), and service providers interoperate with each other to provide a single sign-on service to the user. In addition, when a user wants to log out, a single logout service is provided that logs out the web sites of all service providers that are logged in at once.

On the other hand, looking at the service authentication technology through the conventional association ID, such a conventional technology forms a trust region through the cooperation between service providers. The conventional technology authenticates a user by exchanging each service authentication information according to a standard procedure. With the interchange method, once a user is authenticated to a site in the trusted realm, a single login can be used without having to authenticate again at another site. In addition, when a user logs out at one site, a single logout is possible, which automatically logs out at all other sites.

In order to link user authentication information through such a linkage ID, or to effectively handle and provide a single log-in and a single logout service, the first site login information in a trusted area and the linkage login information through ID linkage must be correlated and managed. .

In addition, research is being conducted on how to use customer information stored in various service sites that manage customer information independently of each other when linking IDs. However, there is a problem that there is a limitation in sharing or transmitting and receiving customer information between other sites due to the protection of the information of the customer.

Therefore, the prior art as described above has a problem that there is a limitation in sharing or transmitting and receiving customer information between other sites due to the aspect of protecting the information of the customer, and to solve such a problem is an object of the present invention.

Therefore, the present invention checks the ID mapping information when the customer's linked authentication and performs automatic authentication with other affiliate services, and when additional login information is required for login to the affiliate site, the customer is added based on permission and policy through customer interaction. By brokering information and synchronizing customer information across affiliate sites, you can easily mediate additional customer information between affiliate sites and easily match customer information between affiliate sites. The purpose is to provide a method of mediating and synchronizing customer information based on ID linkage.

The objects of the present invention are not limited to the above-mentioned objects, and other objects and advantages of the present invention which are not mentioned can be understood by the following description, and will be more clearly understood by the embodiments of the present invention. Also, it will be readily appreciated that the objects and advantages of the present invention may be realized by the means and combinations thereof indicated in the claims.

In order to solve the above problems, after verifying the ID mapping information at the time of the linked authentication of the customer to perform automatic authentication with other affiliated services, when the additional information of the customer is required to log in to the affiliated site, the authorization and It is characterized by mediating customer additional information based on policy and synchronizing customer information between affiliate sites.

More specifically, in the method of mediating and synchronizing customer information based on ID linkage, the method checks whether there is an ID linkage according to an ID linkage request from a user terminal connected to a first service server to a second service server. Linkage setting step of setting an ID linkage; A login step of requesting ID authentication from the second service server to log in the user terminal to the second service server; Acquiring and agreeing customer information for acquiring customer information through customer interaction according to a customer profile request of the second service server and confirming whether there is previously stored customer information; And providing customer information by using the previously stored customer information or receiving customer information from the user terminal and providing the received customer information to the second service server according to the confirmation result.

In addition, the method of the present invention further includes a synchronization processing step of checking and processing the customer information synchronization to the first and second service servers based on a policy based on a corresponding processing instruction if the synchronization conditions are met.

The present invention as described above, after verifying the ID mapping information when the customer's linked authentication to perform the automatic authentication to other third party services, if the additional information of the customer is required when logging into the affiliate site based on the permission and policy through the customer interaction By intermediating additional customer information and synchronizing customer information with each other through affiliate sites, it is possible to easily mediate customer information between affiliate sites and easily match customer information between affiliate sites. It can be effected.

That is, in the first aspect of the present invention, the field type and value of the service-related customer information managed between the services associated with each other at the time of ID linkage authentication is different, in this situation, after the ID linkage authentication between the services, additionally necessary customer information There is an intermediary effect that makes it possible for sites to mutually provide customer information on a policy and permission basis.

Second, the present invention has the effect of maintaining the consistency of information through policy-based customer information synchronization so that customer information does not mutually inconsistency among affiliated sites that independently manage customer information.

BRIEF DESCRIPTION OF THE DRAWINGS The above and other objects, features and advantages of the present invention will become more apparent from the following detailed description of the present invention when taken in conjunction with the accompanying drawings, It can be easily carried out. In addition, in describing the present invention, when it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

In order to solve the above problems, the present invention relates to a method of synchronizing customer information based on ID association that arbitrates and synchronizes customer permission-based and policy-based customer information.

In an environment where IDs between heterogeneous services that independently manage IDs and customer information are automatically linked and authenticated, field types and values of service-related customer information managed between affiliated services are different when ID linkage authentication is performed. In this situation, after interlinking and verifying each other's IDs, mediate customer information on the basis of policy and permission to provide and synchronize additional customer information between affiliate sites. This paper presents a method for synchronizing to match and an ID arbitration management system device implementing the same.

Hereinafter, a method of performing mediation and synchronization based on policy and permission will be described with reference to the accompanying drawings.

1 is a flowchart illustrating an ID linkage environment between general heterogeneous services to which the present invention is applied.

As shown in FIG. 1, the ID association environment between heterogeneous services includes a user terminal 11, a service A server 12, a service B server 13, and an ID association system 14.

The user terminal 11 used by the customer first accesses the service A by requesting a connection to the service A server 12 which independently manages the ID.

The service A server 12 performs local authentication on the user terminal 11 and issues an initial authentication ticket. Here, the service A server 12 makes a request to the authentication server A in its own authentication.

Subsequently, the service A server 12 transmits the initial authentication ticket to the user terminal 11 in the form of a cookie. Then, the customer can use the service A through the user terminal (11).

Then, when the customer who used the service A clicks the link of the service B site existing in the service A site through the user terminal 11, the service A server 12 links to the service B link from the user terminal 11. Is requested (105).

In addition, the service A server 12 requests to perform the automatic authentication through the service link with the initial authentication ticket containing the customer information to the ID linkage system 14 (106).

Subsequently, the ID association system 14 performs association establishment when the customer's initial authentication association request is made (107). The ID linkage system 14 receives an ID of a customer existing at a site to be linked through a customer interaction. And the ID linkage system 14 requests the authentication of the ID entered by the customer in the authentication server of the site. As a result of the authentication request, the ID association system 14 generates ID mapping information in the database when authentication is successful.

In the case of the customer who is not the first request and has already established the association, the ID association system 14 inquires only ID mapping information (108). The ID linkage system 14 requests the authentication server B to the authentication server B of the affiliated site B using the inquired ID mapping information (109).

The authentication request result 109, if the authentication is successful, the ID association system 14 receives a response message for the authentication success from the service B server 13, or receives an authentication failure message if authentication fails (110).

If the authentication is successful, the ID association system 14 issues a federation ticket (111).

The ID association system 14 transmits the association cookie to the user terminal 11 (112). Thus, the ID association system 14 allows the user terminal 11 to access (log in) the service B server 13 (113).

On the other hand, in the case of the user terminal 11 first access to the affiliated service B site, the case where additional customer information necessary for the service B is required according to the determination of the affiliated service B site will be described. In such a case, the user terminal 11 requests the user terminal 11 to share the required profile through the customer interaction, obtains additional customer information with the permission of the customer, and then accesses the service B server 13.

Figure 2 is an embodiment configuration of an ID linkage system for mediating and synchronizing the ID and customer information to which the present invention is applied.

As shown in FIG. 2, the ID association system 14 includes a metadata management unit 201, an association setting unit 202, a multi-domain authentication unit 203, a DB processing unit 204, an ID mapping management unit 205, and the like. The session key check unit 206, the customer interaction unit 207, the profile sharing control unit 208, the policy application management unit 209, and the common DB 210 are included.

The metadata manager 201 registers and manages affiliate site information in a database.

The linkage setting unit 202 performs a function of setting information to be used for linkage to an ID for a customer who initially logs in by linking to an affiliated site for the first time.

In addition, the multi-domain authentication unit 203 searches for an appropriate authentication server when different IDs managed in various affiliate sites are requested, and requests the authentication of the authentication server to receive the response. As a result of the response, the multi-domain authenticator 203 performs a function of controlling the customer connection according to whether the authentication succeeds or fails.

The DB processing unit 204 stores various tables necessary for the ID association system 14 to operate. The DB processing unit 204 stores and manages customer information and setting information in the table. If necessary, the DB processing unit 204 performs a function of inquiring data from the database table, updating data, or inputting data.

In addition, the ID mapping manager 205 maps different IDs that are individually managed in the affiliated site based on key information of a specific customer so that IDs of each site of the customer may be related to each other. ID mapping management unit 205 to identify the unique ID of each site through the ID mapping information at the time of multi-domain authentication to be authenticated with the appropriate ID to the corresponding authentication module. This is to allow automatic login for connection authentication between each service site.

In addition, the session key checker 206 checks whether the session of the customer is valid at the site for which the connection authentication request is currently made, checks the key of the customer, and uses the search key of the ID mapping information.

In addition, the customer interaction unit 207 allows the customer to automatically share additional customer information necessary for accessing the service to automatically log in to the affiliated service site through the linkage authentication through the interaction with the customer or receive the integrated input. That is, the customer interaction unit 207 induces the customer to set the disclosure range so that the service can be automatically shared between the affiliated service sites and the ID linkage system 14, or, if necessary, the user directly the user terminal 11 Or enter your information through a browser and allow mediation.

The profile sharing control unit 208 searches the common database 210 to determine whether the customer information exists in order to mediate the customer information received from the affiliate service site. As a result of the determination, when the customer information does not exist, the profile sharing control unit 208 searches for a site where the necessary information of the customer exists by searching for affiliate service sites. The profile sharing control unit 208 then obtains the customer permission for the retrieved customer information. Then, the profile sharing control unit 208 performs a function of controlling the transmission of the customer information obtained the customer permission to the requested affiliate service site.

And the policy application management unit 209 performs a function of applying the policy base (Policy base) rules, such as increasing the reliability of the corresponding site when the increase in automatic login, such as through the authentication between the other affiliated sites of the customer.

3 is a structural diagram of an embodiment of a database table used in an ID linkage based customer information brokering and synchronization method according to the present invention.

As shown in FIG. 3, the database table includes a customer information table 301, a linked customer information table 302, an affiliate site information table 303, an ID mapping information table 304, a linked authentication table 305, and synchronization. A retry table 306.

The customer information table 301 is a table that stores common information of customers. The customer information table 301 generates and stores a customer unique number in the form of a universally unique ID (UUID) that uniquely identifies a customer as a key. For example, the customer information table 301 may include a customer ID, a customer status, a registration date, a termination date, a change date, a name, a social security number, an alias, an email, a date of birth, a gender, an address, a language code, a phone (home, work, mobile phone). ), Fax, messenger, PR message, public photo, tag, other information and information disclosure setting.

The linked customer information table 302 stores the information generated when the customer first registers the linked. The linked customer information table 302 has an affiliate site number and an affiliate ID as keys. The linked customer information table 302 has a linked registration date and time and a linked termination date and time.

The affiliated site information table 303 has a site number as a key. Affiliate site information table 303 includes the site domain, use status, authentication key, site URL, affiliate mapping URL, unsubscribe sink URL, site information, registration date, login URL, SSO URL, logout URL, mapping URL, and mapping URL. , Fields of customer profile type, confidence level, synchronization immediateity and synchronization threshold are required.

The ID mapping information table 304 has a mapping key and an affiliate member unique key as keys. The ID mapping information table 304 includes affiliated member IDs, affiliated site numbers, affiliated site domains, affiliated states, mapping registration dates, mapping termination dates, and change date and time.

The synchronization retry table 306 is for ensuring the consistency of customer information managed independently of each other when addition, change, and deletion of customer information occurs between the ID linkage device 14 or affiliate service sites. The synchronization retry table 306 is a table that is stored for retrying synchronization when an error occurs while processing the synchronization. The synchronization retry table 306 is used to pass the history table after five attempts of synchronization retry. The synchronization retry table 306 has a synchronization ID as a key. The synchronization retry table 306 has the synchronization registration date, synchronization type, synchronization command, synchronization URL, synchronization port, synchronization protocol, registration date, and synchronization target system as fields.

On the other hand, the policy required when performing the ID linkage device is shown in Table 1 below.

As shown in [Table 1], the policy has a basic structure to execute a processing command when the condition is satisfied by the condition and the action. If the processing instruction is a numerical operation, it is weighted so that the administrator can execute the policy while changing the weight according to the situation.

Synchronization immediateness is calculated to identify affiliated service sites that should be notified immediately by the ID mediation management system when the customer information changes. If the affiliate site wants to synchronize immediately from the start of the affiliate, if synchronization instantiation is set above the threshold, synchronization is automatically triggered when the customer information is changed. Other affiliate sites increase the instantaneous synchronization by 0.1 as the number of new registrations or change registrations increases or the number of association authentications increases. At this time, the weight may be set to α, β, γ, etc. according to the administrator's judgment. Through this process, if synchronization instantiation exceeds the threshold defined separately, synchronization is immediately performed when customer information is changed.

In addition, the policy is defined in case of a synchronization error. When synchronization fails, the operator stores the synchronization information in the 'retry table' and the operator manually synchronizes in case of failure even after retrying as many times as the synchronization retries.

4A to 4C are flowcharts illustrating an embodiment of a method for mediating and synchronizing customer information based on ID association according to the present invention.

'로 연결되어 있으며, 도 4b와 도 4c는 '

', '

'로 연결되어 있다.4A and 4B are

4b and 4c are connected to the

','

'Is connected.

First, the user terminal 11 requests access to the service A server 12 (401). The service A server 12 requests authentication from the dedicated authentication server A (402). Then, it is checked whether the authentication result is successful (403).

If the verification result 403 and the authentication result is failed, the service A server 12 transmits an authentication failure message (404). On the other hand, if the authentication result is successful, the user terminal 11 logs in to the service A server 12 (405). The user terminal 11 then uses the service A (406).

Then, when the customer clicks on a link to the 'service B' while using the service A (407), the user terminal 11 requests the association to the ID association system 14 (408).

In addition, the ID linkage system 14 checks whether linkage has been previously set in the corresponding affiliate site (409).

As a result of the check 409, the ID association system 14 performs association establishment if association is not established. That is, the ID linkage system 14 receives the customer ID of the partner site from the user terminal 11 (410). The ID linkage system 14 completes the authentication of the customer ID in the authentication system of the corresponding affiliate site (411). Subsequently, the ID association system 14 generates ID mapping information using the authentication result (412). Thereafter, the ID linkage system 14 performs the process again from step “409”.

On the other hand, if the verification result 409, the association is established, the ID association system 14 confirms whether the session key of the customer is valid (413). In order to perform multi-domain authentication using the valid session key, the ID association system 14 requests ID authentication from the service B server 13 (414). The ID linkage system 14 checks whether the authentication result of the service B server 13 is successful (415).

If the verification result 415, the authentication result of the service B server 13 fails, the ID association system 14 transmits an authentication failure message (416). On the other hand, if the authentication result of the service B server 13 is successful, the ID association system 14 issues a federated authentication ticket (417). Subsequently, the ID linkage system 14 automatically searches the site number of the service B in the affiliated site information table of the database with a key, and automatically returns the user terminal 11 to the single sign-on URL of the service B returned as a result. Log in (418).

Meanwhile, the server 13 of the service B checks whether additional acquisition of customer information is necessary (419).

As a result of the check 419, if additional acquisition of customer information is unnecessary, the server 13 of the service B allows the customer to use the service B (420). On the other hand, if additional acquisition of customer information is required, the necessary items are displayed to the customer through the customer interaction and the customer's information provision consent is obtained (421).

Thereafter, the server 13 of the service B of the agreed information checks whether there is information held by the ID association system 14 (422).

As a result of the check 422, if there is retention information, the ID linkage system 14 checks the 'authentication key' of the requesting site in the 'partnership site information' table (423). The ID association system 14 then verifies whether the verified site authentication key is valid (424).

As a result of the check 424, if the site authentication key is valid, the ID association system 14 checks the 'public information setting' in the 'customer information table' to check whether the corresponding field is disclosed (425). On the other hand, if the site authentication key is not valid, the ID association system 14 terminates the customer information providing process.

The ID linkage system 14 checks whether the 'public information setting' is consistent with the customer agreement (426).

As a result of the check 426, if the information disclosure setting does not agree with the customer agreement, the ID linkage system 14 performs a resynchronization procedure with the customer (427). Thereafter, the ID association system 14 checks whether the customer agrees (428).

As a result of the check 428, if the customer does not agree, the ID linkage system 14 outputs a login impossible message to the user terminal 11 (429). On the other hand, if the customer agrees, the ID linkage system 14 provides the customer information to the site B (430).

On the other hand, if the check result 426, 'public information setting' is consistent with the customer agreement, the ID association system 14 provides the previously stored customer information to the 'service B' server 13 (431).

On the other hand, if the check result 422, the ID linkage system 14 of the agreed information does not have information, the ID linkage system 14 searches for the customer information on the affiliated service sites (432). The ID linkage system 14 checks whether the customer information exists (433).

If the verification result 433, customer information exists, the ID association system 14 obtains the customer consent (434). The ID linkage system 14 stores the common DB (435).

On the other hand, if the check result 433, customer information does not exist, the ID linkage system 14 displays the value input box on the customer terminal to obtain the information in order to obtain an item requiring the customer input (436). The ID linkage system 14 stores the additional customer input information and the 'public information setting' in the 'customer information table' (437).

ID association system 14 then makes service B available to the customer (438).

On the other hand, when affiliated service sites such as Service B acquire additional customer information from the ID linkage system 14 or directly input through an interaction with the customer, changes in customer information to affiliated service sites that require immediate synchronization or Notification of further deletions should be given. The ID linkage system 14 checks 'sync immediateness' and 'threshold' of the 'partnership site information' table (439). ID association system 14 then checks 440 if the identified 'sync immediateness' exceeds 'threshold'.

As a result of the check 440, if the 'synchronization immediateness' exceeds the 'threshold', the ID association system 14 performs a synchronization process (441). On the other hand, if the 'synchronization immediateness' does not exceed the 'threshold', the ID association system 14 ends the process of performing the synchronization process.

5 is a diagram illustrating an embodiment of a method for synchronizing customer information based on ID association according to the present invention.

In an ID association environment between heterogeneous services, the ID association system 14 for mediating customer information operates in several cases.

That is, the customer may directly log in to the ID linkage system 14 through the user terminal 11 to change and leave the customer information. In this case, the ID association system 14 immediately notifies the synchronization target affiliate sites 501 to 503 of the changed customer information.

For example, when a customer subscribes, withdraws, or changes in the synchronizing target site n 503 immediately, each affiliate service site notifies the ID association system 14 of the related information. Then, the ID linkage system 14 enables notification of customer information change and withdrawal when the immediate synchronization target affiliate sites 1 and 2 (501, 502), which are other affiliated sites other than the corresponding affiliate service site, are immediately synchronized.

FIG. 6 and FIG. 7 are flowcharts illustrating an embodiment of a process for performing synchronization for each individual in a method of mediating and synchronizing customer information based on ID association according to the present invention.

First, when the change and withdrawal of customer information occurs in the ID linkage system 14 (601), the ID linkage system 14 searches the 'partnership site information' table (602). In addition, the ID linkage system 14 extracts a site number whose synchronization immediateness exceeds the synchronization threshold and immediately extracts the synchronization number (603).

Subsequently, the ID linkage system 14 notifies the synchronization information of the customer information to the 'synchronization target site i' (604).

Thereafter, the ID association system 14 checks whether the synchronization information notification is successful (605).

If the confirmation result 605, the synchronization information notification is successful, the ID association system 14 stores the synchronization details in the synchronization history table (606). On the other hand, if notification of the synchronization information fails, the ID association system 14 stores the synchronization details in the 'sync retry' table (607).

After storing the synchronization details 606, the ID association system 14 checks if there are more synchronization target sites (608).

If the confirmation result 608, the synchronization target site is further present, the ID association system 14 performs the process "604" until the synchronization information is notified to all the synchronization target site.

As a result of the check 608, if there is no synchronization target site, the ID association system 14 ends the process.

On the other hand, if customer registration, withdrawal and change occurs in the synchronization target site immediately (609), the ID linkage system 14 reflects the storage of customer subscription information, withdrawal information and change information (610). The ID association system 14 performs the process "602".

Meanwhile, a process of performing synchronization for each object will be described with reference to FIG. 7.

First, when the customer automatically logs in to the affiliated site through the user terminal 11 with customer registration or affiliate authentication, the affiliated site requests sharing of customer information to the ID linkage system 14 (702).

The ID linkage system 14 confirms the 'public information setting' in the customer information table (703). Subsequently, the ID association system 14 checks whether information disclosure is set (704).

If the confirmation result 704, information disclosure is not set, the ID association system 14 requests the customer consent (705). The ID association system 14 then verifies whether the customer agrees (706).

As a result of the check 706, if the customer does not agree, the ID association system 14 requests the customer to directly enter the site (707). The site then checks 708 whether the customer enters directly.

As a result of the verification (708), if the customer enters directly, the site stores the customer information in the affiliate site (710). The site is performed again from the process “610” of FIG. 6. On the other hand, if the customer does not enter it directly, the site notifies the login error (709).

On the other hand, if the confirmation result 704, the information disclosure is set, the ID association system 14 provides the information to the affiliate site (711). The provided customer information is stored in the affiliate site (712).

On the other hand, the method of the present invention as described above can be written in a computer program. And the code and code segments constituting the program can be easily inferred by a computer programmer in the art. In addition, the written program is stored in a computer-readable recording medium (information storage medium), and read and executed by a computer to implement the method of the present invention. The recording medium may include any type of computer readable recording medium.

The present invention described above is capable of various substitutions, modifications, and changes without departing from the technical spirit of the present invention for those skilled in the art to which the present invention pertains. It is not limited by the drawings.

1 is a flowchart illustrating an ID linkage environment between general heterogeneous services to which the present invention is applied;

2 is a configuration diagram of an embodiment of an ID linkage system for mediating and synchronizing ID and customer information to which the present invention is applied;

3 is a structural diagram of an embodiment of a database table used in an ID linkage based customer information brokering and synchronization method according to the present invention;

4A to 4C are flowcharts of an embodiment of a method for mediating and synchronizing customer information based on ID association according to the present invention;

5 is a diagram illustrating an embodiment of a method for synchronizing customer information based on ID association according to the present invention;

FIG. 6 and FIG. 7 are flowcharts illustrating an embodiment of a process for performing synchronization for each individual in a method of mediating and synchronizing customer information based on ID association according to the present invention.

* Explanation of symbols for the main parts of the drawings

13: ID association system 201: metadata management unit

202: association setting unit 203: multi-domain authentication unit

204: DB processing unit 205: ID mapping management unit

206: session key check unit 207: customer interaction unit

208: profile sharing control unit 209: policy application management unit

Claims (8)

In the method of brokering and synchronizing customer information based on ID linkage, An association setting step of establishing an ID association by checking whether there is an ID association according to an ID association request from a user terminal connected to the first service server to the second service server; A login step of requesting ID authentication from the second service server to log in the user terminal to the second service server; Acquiring and agreeing customer information for acquiring customer information through customer interaction according to a customer profile request of the second service server and confirming whether there is previously stored customer information; And According to the check result, using the pre-stored customer information or receiving customer information from the user terminal to provide the customer information to the second service server step ID linkage based customer information brokering and synchronization method comprising a. The method of claim 1, Synchronization processing step of checking and processing the customer information synchronization to the first and second service server based on the policy based on the processing instruction if the synchronization conditions are met. ID linkage based customer information brokering and synchronization method further comprising a. The method of claim 2, The synchronization processing step, Performing a processing instruction for synchronization immediateness according to whether the synchronization immediateness among the synchronization conditions exceeds a synchronization threshold; How to mediate and synchronize customer information based on ID linkage. The method of claim 3, wherein The synchronization processing step, The synchronization condition in which the synchronization immediateity is increased includes a case in which any one of a new registered customer, a changed registered customer, and an associated authentication number increase. How to mediate and synchronize customer information based on ID linkage. The method of claim 4, wherein The synchronization processing step, When the processing instruction is a numerical operation, the synchronization processing based on a policy while changing the weight for the processing instruction How to mediate and synchronize customer information based on ID linkage. 6. The method according to any one of claims 1 to 5, The customer information consent and confirmation step, If the customer profile type of the second service server requires additional acquisition of customer information, acquiring consent for providing customer information through customer interaction is obtained. How to mediate and synchronize customer information based on ID linkage. The method of claim 6, The customer information consent and confirmation step, Confirming the information disclosure setting of the customer information table through the customer interaction and confirming whether the checked information disclosure setting is consistent with the customer agreement or not; How to mediate and synchronize customer information based on ID linkage. The method of claim 7, wherein The customer information providing step, If the information disclosure setting is in agreement with the customer agreement, provide the pre-stored customer information to the second service server, and if the information disclosure setting does not match with the customer agreement, outputting a login impossible message How to mediate and synchronize customer information based on ID linkage.

Images