KR20010091207A - System for global management of client data of internet services - Google Patents

Abstract

PURPOSE: A system for integrating and managing client data in Internet services is provided to integrate client data collected from a plurality of different Internet sites. CONSTITUTION: The system is comprised of a plurality of individual sites(100a-100c) and an integrated client data management system(200). Each site has client profile information and log information for its own clients, and transfers these information to the integrated client data management system(200). An integrated client data part(300) in the integrated client data management system(200), comprised of a common part, a differentiating part, a measuring part, a flexible part, and history part, collects and integrates these information from each site.

Description

Customer data integrated management system of Internet service {SYSTEM FOR GLOBAL MANAGEMENT OF CLIENT DATA OF INTERNET SERVICES}

The present invention relates to a method for generating integrated customer data by integrating customer data generated at each site in a network system composed of a plurality of individual internet sites and an integrated management unit for managing the same. When a company wants to conduct joint marketing, it relates to a method for integrating and managing a plurality of different customer data and a structure of the integrated customer data.

Each Internet site has a customer profile that is appropriate for each service and its characteristics. By integrating and supporting these Internet sites in one management system, it is possible to reduce the cost of developing a support solution that can be commonly used in multiple sites, and maximize the profits of the sites by sharing and supplementing information among multiple sites. Do.

When building such an integrated management system, it is important to efficiently integrate and manage various types of information input through each site. This information includes information unique to the functions of each site and information common to the functions of all sites, and the formats vary greatly.

It is therefore an object of the present invention to provide a method for integrating customer data collected from a number of differently-interfaced Internet sites.

It is another object of the present invention to provide a structure of an integrated customer data portion that incorporates customer data from a number of different sites.

It is yet another object of the present invention to provide an integrated management system for integrating and managing customer data from many different sites.

In order to achieve the above object, the present invention provides a method for generating integrated customer data including a cavity, a history, a specialized, a flexible, and a scale.

In addition, the present invention provides a method for integrated management of data unique to each site and data common to all sites in an appropriate format.

1 is a schematic diagram of an integrated site system in accordance with the present invention, comprising a plurality of individual sites and an integrated management system;

2 is a conceptual diagram showing the configuration of integrated customer data according to the present invention;

3 is a diagram illustrating a procedure for creating a cavity in the integrated management system of the present invention.

4 is a diagram for explaining the relationship between a cavity and a history section.

5 is a diagram illustrating a creation procedure of a history unit in the integrated management system of the present invention.

6 is a diagram illustrating a procedure of generating a scale unit in the integrated management system of the present invention.

FIG. 7 is a diagram for explaining characteristics of specialized and flexible portions data. FIG.

8 is a diagram illustrating a process in which customer data input at each site is classified and managed by a common part, a specialty part, and a flexible part.

<Explanation of symbols for the main parts of the drawings>

100: individual site

200: integrated customer data department

210: common part

220: specialization

230: scale unit

240: flexible part

250: history

300: Integrated Customer Data Management System

According to an aspect of the present invention, in the integrated management system that is connected to one or more Internet sites, and manages customer data from each site in an integrated site support system for supporting the functions of the Internet site,

Means for storing a collaborative section containing customer data independent of the functionality of the site and a history section containing data about customer activity at each site;

An integrated data management system is provided that includes means for generating the common portion and the history portion in response to information from the Internet site.

According to another aspect of the present invention, in the integrated management system that is connected to one or more Internet sites, and manages customer data input from each site in the integrated site support system for supporting the functions of the Internet site,

Means for storing a common data portion containing data of the same item for all sites and a specialized data portion containing data of different items for each site;

An integrated data management system is provided that includes means for creating and updating the common data portion and the specialized data portion in response to information from the individual internet site.

As described above, the integrated customer data used in the integrated management system supporting multiple sites can integrate customer information of individual sites in a short time, and can accommodate the customer management type of each site in the future. It is desirable to be designed. In addition, when the database is to be used for information analysis, it should be designed not only to use the information from an integrated perspective, but also to utilize the information independently for each site.

1 is a schematic diagram of an integrated site system in accordance with the present invention, comprising a plurality of individual sites 100a, 100b, 100c and an integrated customer data management system 300. Each site has customer profile and log information of the customer of its own site, and this information is transferred to the integrated customer data management system 300 and integrated as the integrated customer data unit 200 inside the system 300.

2 is a conceptual diagram illustrating a schematic configuration of the integrated customer data unit 200 of the present invention. The integrated customer data portion of the present invention may include five parts, which are the common portion 210 which is not directly related to the characteristics of each Internet site, the specialized portion 220 reflecting the characteristics of each site, each It is a scale unit 230 that numerically expresses the customer's history, etc. in order to grasp the individual personality of each customer in real time, the flexibility unit 240 in consideration of future scalability and the history unit 250 for grasping the detailed history for each customer. . The cavity 210 is associated with the remaining four parts, and the hysteresis 250 is used to generate the scale 230.

3 is a view showing a creation procedure of the joint unit 210 in the integrated customer data management system of the present invention. The common department includes common information necessary for customer management in all Internet services such as personal information, location and contact information. If a customer, defined by (resident number + country), is registered with several Internet services simultaneously, the information corresponding to this joint shall be cross-referenced to maintain the most current and correct information.

As shown in FIG. 4, the joint unit 210 includes an integrated customer information DB 410 including a plurality of unified customer information for managing customer profile information of various sites and a customer profile for each site. , The site customer information DB 420 including a plurality of site customer information. There may be a plurality of site customer information corresponding to one integrated customer information. That is, there may be one integrated customer information and a plurality of site customer information for one integrated customer number uniquely assigned to each user. Integrated customer information should collect information from multiple sites and maintain it as the most appropriate information. For example, integrated customer information is updated based on the most recently input of customer profile information from multiple sites.

Table 1 is an example of data included in the integrated customer information DB.

Certification Information Integrated customer number password Personal information name Social Security Number date of birth Yin and Yang wedding anniversary job Country Channel Information Zip code Address type address Work phone number Home Phone cellphone fax E-mail id Properties Customer Status Customer Type registration date

In the above table, the customer status indicates, for example, whether the customer is currently registered or the customer whose registration has been canceled, and the customer type indicates, for example, whether it is a corporate customer or an individual customer.

Table 2 is an example of information included in the site customer information DB 420. Site customer information is associated with the integrated customer information through an integrated customer number, and includes customer information for each site. The site customer information DB 420 is distinguished from the characteristic part in that it is managed in the same form irrespective of the characteristics of the site, but unlike the integrated customer information DB, it stores separate data for each site.

Integrated Customer Information Link Key Integrated customer number Site properties Site name (number) Site customer status Site registration date Site personal profile Certification Information Personal information Channel Information

The authentication information, the personal information and the channel information of Table 2 indicate information of the same name of the integrated customer information, except that in the integrated customer information, the information is the only information per customer, whereas the authentication, personal and channel information in the site customer information Is information provided by each site, and may vary from site to site. For example, if the phone number is changed between the subscription of one site and the subscription of another site, the telephone number of the site customer information is different.

Referring to Figure 3 will be described the cavity generation process. The customer profile 310 of the individual site 100 is customer profile information collected at each site to be integrated and is composed of authentication information, personal information, channel information, and registration information as described above. Newly modified or generated customer profile information from each site 100 is transmitted to the integrated customer data management unit 200 (L31).

The transmitted customer profile information is first processed by the standard profile mapping unit 330. The standard profile profile mapping unit 330 converts a customer profile of an individual site having a different format into a standard format commonly used in an integrated site. The standard profile profile mapping unit 330 utilizes the standard information of the profile mapping DB 320. The conversion to form will be performed.

The standard profile profile mapping unit 330 is largely divided into four steps. In step 1, identify the site number from which site the customer profile you want to integrate comes from. Step 2 When requesting the profile mapping DB unit 320 to retrieve mapping information for a site corresponding to this site number (L32), the profile mapping DB unit 320 requests a site-specific customer profile layout according to the request. And mapping information with the integrated customer information layout is provided to the standard profile mapping unit 330 (L33). In step 3, a temporary table of a type capable of generating an integrated customer profile is generated using the mapping information. In the fourth step, the conversion is performed by using the conversion information of the profile mapping DB for each site customer profile and then stored in a temporary table. The difference in the layout of each site is, for example, the difference in information expression between sites or items included in the customer profile, for example, one site shows a female member as 1 and integrated data as "F". it means.

The profile mapping DB unit 320 has mapping information for converting customer layouts of different sites into a standard form of an integrated customer DB. Standard integration code that defines the relationship between the source field and the mapping target field for each site (code standardizing items and attributes to systematically express customer information expressed differently for each site). Includes information about the conversion and information about the conversion. As described above, the customer profile of each site to be integrated may be converted into a standard form by referring to the profile mapping DB unit 320.

Customer profile information of the site mapped in the standard form, stored in the date and time table, is transmitted to the existence check unit 340 (L40). Existence check unit 340 is to check whether the site customer profile exists in the integrated customer information DB unit 370.

The integrated customer information DB unit 370 is a database managed by one profile even if one customer is registered in multiple sites. When a new customer profile is to be reflected in this integrated customer database, the customer profile is pre-set by other sites. The type of job depends on whether it is registered. Therefore, the presence check unit 340 has a return value for the presence or absence by searching the integrated customer information database 370 using the customer's social security number and country code.

If the integrated customer information correction unit 350 already exists customer profile information having the same social security number and country code as a result of the existence check unit 340 (that is, the return value is "Yes"), the existing customer profile information This is the part to update to the latest information. When a new customer profile is sent from an individual site, its validity is verified and, if there is no problem, the existing customer profile stored in the integrated customer information database is updated with the latest information. For example, if the phone number entered as the customer information of the individual site is different from the previously stored phone number, and valid data as the phone number, the phone number part of the joint customer information of the joint department is changed to the newly entered phone number.

The integrated customer information input unit 360 is a part which is performed when the customer profile information that owns the same social security number and country code as the result of the existence check unit is not present (that is, the return value is "no"). A function of inputting information into the integrated customer information database 370 is performed.

The integrated customer information DB 370 is a database that is integrated and managed among customer profile information of various sites, and is composed of authentication information, personal information, channel information, registration information, and the like as described above.

The integrated customer number generation / acquisition unit 380 performs a function of assigning a unique integrated customer number to one customer (identified by the resident code and the country code). The integrated customer number is used to link the site customer information with the integrated customer information when registering a new customer in the integrated customer information database or when updating the customer profile information in the site customer information database. In the case of a customer that already exists in the integrated customer information database 370, the stored integrated customer number is imported, and in the case of a customer that does not exist, a new integrated customer number is generated.

The site customer information reflecting unit 390 modifies or inputs the site customer information using the site customer profile inputted to the standard form profile mapping unit 330 and the integrated customer number generated by the integrated customer number generation / acquisition unit 380. do. That is, the standard form profile mapping unit 330 stores the site customer information mapped to the standard form in the site customer information DB 395.

The site customer information DB unit 395 manages a customer profile for each site, and includes one-to-many relationship with the integrated customer information DB based on the integrated customer number as described above.

4 is a view for explaining the relationship between the cavity part and the history part. The history unit is a part for collectively managing a transaction or a log generated at each Internet site, and includes source information for creating a scale unit to be described later.

The log book is not managed by integrated customers, but by each Internet site and by each customer. As shown in FIG. 4, the site customer DB and the history DB of the joint have a one-to-many relationship.

5 is a diagram illustrating a generation process of the history unit in the integrated customer data management system of the present invention.

First, the customer log generated at the individual site is transmitted to the integrated customer data management system 300 (L51). This site's customer log is a log record of the customer's actions in each site. The site's IP address, time of occurrence, URL (Unified Resource Lacator), and content of interest (for example, Service / product information).

The standard type log mapping unit 530 of the customer data management system 300 receives the customer log and converts it into a standard type with reference to the log mapping DB unit 520.

The log mapping DB unit 520 includes mapping information for converting a layout of a log of a customer of each site into a standard form called an integrated customer log, similar to the profile mapping DB unit 320 of FIG. 3. The log mapping information defines the relationship between the source log field (the field of the site log) and the target log field (the field of the standard type log) for each site.

The standard type log mapping unit 530 performs four steps as in the standard type profile mapping unit 320. As a first step, check the site number from which site the customer log you want to consolidate comes from. Step 2 When requesting the log mapping DB unit 520 to retrieve log mapping information for the site corresponding to this site number (L52), the log mapping DB unit 520 according to the request causes the site-specific log layout and the integrated log layout. Search for mapping information with and return to the standard log mapping unit 530 (L53). In step 3, a temporary table of a type capable of generating an integrated log is generated using the log mapping information. In step 4, the conversion is performed using the conversion information of the log mapping DB unit 520 for each site customer log and then stored in a temporary table.

The validity verification unit 540 determines whether the history information from each site is suitable to be input to the history database. Different types of logs from different sites can be unconditionally accommodated in historical DBs, but only appropriately standardized and registered. In order to accommodate a new type of log in the history DB, a mapping method that can be standardized appropriately must be registered in the log mapping DB, and a validation criterion must be registered in the validity lookup DB.

The determination of whether the history DB unit 560 can be input is made by referring to the validity lookup DB 550 including reference information regarding validation of log data. Validation criteria of the validity lookup DB 550 includes, for example, log data transmitted from a registered site, a login location for a registered customer, a login location for a registered service and a product, and the like.

As a result of determination according to the validation criteria of the validity lookup DB unit (L57), log information from each site is reflected in the history DB 560 that stores log information for each customer from each site.

If the result of the validity judgment is inappropriate (L58), the log information and the cause information failed in the verification (that is, the portion of the validation criteria determined to be inappropriate) are stored in the error database.

The error cause analysis unit 580 searches the error DB unit 570 and if the cause of the verification failure can be clearly identified and immediately resolved, the error cause analysis unit 580 sends the modified log information back to the validation unit 540 again. (L59). If not, send the log information to the site that generated the log again (L60) to solve the cause. In this case, when a new verification criteria is generated at the site, this is reflected in the validity lookup DB unit 550 so that log information input afterwards may be stored in the history DB unit 560 without going to the error DB unit 570. .

6 is a diagram illustrating a generation procedure of the scale unit 230 in the integrated customer profile generation system of the present invention. In order to understand the characteristics of an individual, it is necessary to understand all histories and logs of his or her activities on the Internet. However, due to the nature of Internet services that must perform real-time responses to numerous user connections and individual events, it is practically impossible to identify all such activities. At this time, if the customer's history can be summarized numerically, it is possible to efficiently identify the characteristics of the individual. Thus, the scale unit is used to numerically express the individual's history and log.

Looking at the scale generation process in detail, first, during the marketing activities at each site, the marketing requirements, which are the parts that need support in the entire system, are defined (610). Next, a scale development item is selected based on the marketing requirements (620). At this time, information about the response of the customer after contacting the customer using a past scale similar to the scale currently being developed is displayed. Reference is made from 640.

Once the scale development item suitable for the marketing requirement is determined, a predictive modeling function is calculated (630). Predictive modeling function estimation is the process of creating a function for scale development.For example, if you want to measure how often, how recently, and how many purchases you have made as a measure of customer autonomy, purchase frequency, recent purchase date, and purchase volume. Is to create a function with.

After calculating the predictive modeling function, the scale generator 650 requests the scale to be calculated. At this time, the scale generation unit refers to the history DB unit to generate the scale. The calculated scale is stored in the scale DB unit 670. This calculated scale is information that can grasp the propensity of the customer in real time, which is collected and stored by the integrated customer number. The stored information is used for marketing activities. For example, sports equipment can be marketed to people who have a high measure of the tendency to purchase goods for young people. At this time, the customer response to the marketing activity using the scale is reflected in the customer contact response DB unit 640 (L67).

The result of applying the scale to the marketing activity using the customer contact response database is analyzed 660 to determine whether the scale is correct. If necessary, a new scale is developed by changing the scale value stored in the scale DB 670 or by changing the modeling function itself.

7 is a view for explaining the characteristics of the specialized unit and the flexible unit data.

The specialized unit 220 includes items to be managed depending on the characteristics of each site. Unlike the common part, the items of the specialized part may be set differently for each site. The characteristics of the site are largely related to whether the company related to the site is originally an online company or an offline company. The online company is a category, shopping mall, service provider, forward auction, reverse auction, barter, network, event, and information publishing. Types, Internet-oriented, specialized community types, etc. can be classified. Offline companies are classified into the automotive, distribution, telecommunications, manufacturing, finance, baby and leisure industries. This classification system is used as a database to designate which classification belongs to the site registration, and manage the specialized item fields classified according to the characteristics of each site.

The flexibility unit 240 expands in the future, such as adding a new business requirement such as expansion of a business or changing a service, or if a new item is needed as a result of analyzing response information obtained from contact with a customer. It is part of preparing for sex. Like the site-specific section, the flexibility field is dependent on the site to determine the number and characteristics of the items.

8 is a diagram illustrating a process in which customer data input at each site is classified and managed by the common unit 210, the specialty unit 220, and the flexible unit 240. Once customer data is entered from each site, it is first determined in the field (or item) classifier 810 whether it belongs to a common part, a specialty part, or a flexible part in order to be available data in the integrated management system of the present invention. For example, the user's personal information (phone number, age, etc.) belongs to the joint department data, the user's car accident details entered on the car insurance site belong to the specialized department data, and the user suggested the desired function on the site. This belongs to the data of flexibility. First of all, the joint unit generation operation shown in FIG. 3 is performed, and the specialization unit and the flexible unit generation processing operation are performed using the integrated customer number generated therein. The specialization unit and the flexible unit generation processing are similar to the history generation generation processing method (shown in FIG. 5) such as being processed through the standard type mapping unit and the validation unit. However, since the specialized and flexible parts have different characteristics for each site and are difficult to manage collectively, standardization work is performed in the standard type mapping part managed by each site unlike the history part.

The specific embodiments described in the present specification so far are for clarity of the technical content of the present invention, and the scope of the present invention should not be construed in consultation with only such examples, but the present invention. It includes many variations and modifications within the spirit and scope of the following claims.

According to the integrated customer data generation and management method of the present invention, since information collected at a plurality of sites is managed in a standard manner, this information can be easily used for the business activities of the plurality of sites. While data from each site is managed in a standard way for ease of management and use, the structure of the integrated data is designed to fully reflect the characteristics of each site. In addition, it is possible to maximize the activity of integrated data by using a data model that considers not only the business and user situation of the site so far but also future changes.

Claims (10)

In an integrated management system that is connected to one or more Internet sites, and manages customer data from each site within an integrated site support system for supporting the functions of the Internet site, Means for storing a collaborative section containing customer data independent of the functionality of the site and a history section containing data about customer activity at each site; Means for generating the common and the history in response to information from the internet site. The method of claim 1, Means for storing a specialized section containing data that must be managed depending on the characteristics of each site; And means for generating said specialization in response to information from said Internet site. The method of claim 1, Means for storing flexibility, including data about future scalability of each site, Means for generating the flexibility in response to information from the internet site. In an integrated management system that is connected to one or more Internet sites and manages customer data input from each site in an integrated site support system for supporting the functions of the Internet site, Means for storing a common data portion containing data of the same item for all sites and a specialized data portion containing data of different items for each site; Means for creating and updating said common data portion and said specialized data portion in response to information from said individual internet site. The method of claim 4, wherein the common data unit includes a common part including common information necessary for customer management in all Internet services, such as personal information, location and contact information of the individual, The joint part includes an integrated customer information DB unit including a plurality of integrated customer information incorporating customer profile information of various sites and a site customer information DB unit including a plurality of site customer information for managing a customer profile of each site. The integrated customer information corresponds to one integrated customer number uniquely assigned to the user of the Internet service, and a plurality of site customer information correspond to the integrated data management system. In an integrated management system that is connected to one or more Internet sites and manages customer data input from each site in an integrated site support system for supporting the functions of the Internet site, Means for storing common departments containing common information necessary for customer care in all Internet services, including personally identifiable, local and contact information; Means for creating and updating the community in response to information from the internet site, The joint part includes an integrated customer information DB unit including a plurality of integrated customer information incorporating customer profile information of various sites and a site customer information DB unit including a plurality of site customer information for managing a customer profile of each site. The joint creation and updating means A profile mapping DB containing mapping information for converting layouts of customer profiles of different sites into a standard form commonly used in an integrated site support system; A standard profile profile mapping unit for converting a customer profile of a site having a different format into the standard format by using the profile mapping DB information; A presence check unit for checking whether the integrated customer information for the customer of the site customer profile already exists in the integrated customer information DB unit; Integrated customer information correction unit for modifying the existing integrated customer information to the latest information, if the integrated customer information of the customer already exists as a result of performing the existence check unit; Integrated customer information input unit for adding the information contained in the site customer profile to the integrated customer information DB, if the integrated customer information of the customer does not exist as a result of performing the existence check unit Integrated customer data management system including The method of claim 6, The standard form profile mapping unit Means for verifying the site number from which site the customer profile is from, Means for retrieving the mapping information for the site corresponding to this site number from the profile mapping DB; Means for generating a temporary table in a form capable of storing an integrated customer profile using the mapping information; Means for performing conversion by using the conversion information of the mapping DB for each site customer profile and storing it in the temporary table Integrated customer data management system The method of claim 6, The integrated customer information includes an integrated customer number uniquely assigned to each user, The integrated customer data management system imports the stored integrated customer number if there is already integrated customer information as a result of performing the existence check unit, and if the integrated customer information does not exist as a result of performing the existence check unit. By generating the integrated customer number, the integrated customer number generation / acquisition unit to give the integrated customer number, Site customer information reflecting unit for updating and adding site customer information of the site customer information DB using the site customer profile and the integrated customer number Integrated customer data management system further comprising. In an integrated management system that is connected to one or more Internet sites and manages customer data input from each site in an integrated site support system for supporting the functions of the Internet site, A history database section for storing a history section incorporating logs generated at each Internet site, Means for creating and updating said history in response to customer log information from said internet site, The history section generating and updating means Log mapping DB including mapping information for converting the layout of the customer log of each different site to the standard form commonly used in the integrated site support system, A standard log mapping unit for converting a customer log of a site having a different form into the standard form by using information of the log mapping DB; A validity lookup DB unit including verification information for determining whether the customer log information from each site converted into a standard form can be stored in the history database unit; A validating unit for determining whether the customer log information from each site converted into the standard configuration can be stored in the history database unit by using the verification information stored in the validity lookup DB unit; Means for storing the standardized customer log information in the history storage means when the customer log information can be stored in the history storage means as a result of performing the validation unit; An error database unit for storing information on a cause thereof, when the customer log information cannot be stored in the history storing means as a result of performing the validation unit; Error cause analysis unit for determining whether the cause information stored in the error database unit immediately solved Integrated customer data management system including The method of claim 9, The standard log mapping unit, Means for checking the site number from which site the customer log came from Means for retrieving the mapping information for the site corresponding to this site number from the log mapping DB; Means for generating a temporary table in a form capable of storing an integrated customer log using the mapping information; Means for performing a conversion operation for each customer log by using the conversion information of the mapping DB and storing it in the temporary table Integrated customer data management system