KR20010044385A - Personal information transfer system and method using computer network, and computer-readable media recorded the method - Google Patents

Abstract

The present invention discloses a system in which synchronization of personal information is performed in real time under the Internet environment, and personal information can be exchanged without changing the website's own system. Such a system may include a client-side message having a client-side message analyzer for generating a message utilizing a command and data according to a requested operation to be performed with a server, or analyzing the received message and classifying the received message and the command into data. A client having an execution unit and a client-side network management unit for transmitting a message through the network; Server-side network management unit for transmitting information through the network, server-side message analysis unit and command to analyze the work to be performed with the client, collect and perform the necessary information, and provide the result of the message message. Server side message execution unit having a processing unit, a data manager 325 for managing a form designated by a site administrator for interlocking information transmitted through a network and a DB installed on a server, and a type of DB installed on a server DB linking unit is provided to perform DB work according to the form designated by the site administrator.

Description

Personal information exchange system using a network, a method of exchanging information using the system, and a computer-readable recording medium on which the method is recorded. {Personal information transfer system and method using computer network, and computer-readable media recorded the method}

The present invention relates to a method of exchanging information in an internet environment.

Information using the Internet in an Internet environment For example, a cookie provided by an internet browser to exchange a set of information individually managed by a user, in particular, personal information of a user (hereinafter referred to as "personal information"). ) Or a separate program for accessing the server when the personal information is stored on a separately prepared server and the stored information is needed. For example, Microsoft's Passport is used.

The method of storing information on the user PC 110 and providing the stored information using cookies provided by the Internet browser is not encrypted when storing the information on the user PC 110 or exchanging personal information in the Internet environment. Therefore, there is a weak security problem, and also because the domain where the cookie is set, that is, the domain can be used only on the same website, personal information cannot be shared on websites with different domains.

In the method of exchanging personal information using Microsoft's Passport, a general purpose is excluded in order to manage personal information exclusively. That is, since personal information is stored only in a server prepared separately, that is, a server provided by Microsoft, and Microsoft manages exclusively, the user cannot directly manage stored personal information using the user PC 110 or the like. In addition, in order to manage personal information of members, the website administrator must develop, purchase, and install a separate information acquisition program developed using a separate passport API (Application Programming Interface) provided by Microsoft. In addition to sharing information that Microsoft provides on its website, personal information management programs, such as member information management that are built individually on the website, are meaningless.

According to the method of managing and providing such personal information, each member's personal information is fixed to a certain value in the membership of the website, but it is inconvenient to record each item of personal information every time the user joins each website. There is this.

In addition, even when logging in to each website, every time you log in to each website, such as membership registration, you need to write down the items required for login, such as ID, Password, etc. individually. Moreover, for the websites that are subscribed, the user must remember all the IDs and passwords of the respective websites, so the more websites that are subscribed to, the more difficult the management of their IDs and passwords is. do.

In addition, each website has its own membership information management system, but does not have any standardized membership information management system that is common to all websites. There are also many difficulties in managing and modifying "member information". In other words, when the user's e-mail address is changed or the phone number is changed, the user must access each of the registered websites and modify the member information. This makes the Internet user uncomfortable and results in the member information of the Internet user being left unmodified. This result can cause a great loss on the website side where the information of Internet users is particularly important.

The present invention has been made in order to solve such a problem, a system for performing synchronization on personal information in real time and exchanging personal information without changing its system on a website, an information exchange method using the system, and Its purpose is to provide a computer readable recording medium having recorded thereon the method.

1 schematically illustrates a system configuration for implementing a PITP service according to the present invention,

2 is a block diagram of a basic member information database of the PDS server according to the present invention;

FIG. 3 is a functional diagram illustrating in more detail a client / server system for performing a PITP service in the system shown in FIG.

4 is a flowchart illustrating a process of setting an environment of a PSS or PDS server by a web site administrator.

5 is a flowchart illustrating a P-client installation process according to PITP membership.

6 and 7 illustrate a process of storing personal information by the P-client. FIG. 6 is a flowchart illustrating a process of storing personal information in a local storage using an input / output system of a user PC. This is a flowchart showing the process of storing personal information in a separate PDS server other than the local repository.

FIG. 8 illustrates a process in which a P-client requests and obtains personal information stored in a PDS server.

8A is a flowchart illustrating a process of sending a message requesting personal information to a PDS server by a P-client.

8B and 8C are flowcharts illustrating a process in which a PDS server receives and analyzes a corresponding message from a P-client, and transmits the stored personal information to the P-client.

8d is a flowchart illustrating a process of receiving personal information transmitted from a PDS server.

FIG. 9 illustrates the entire process of providing the PSS server with personal information required by the P-client in the PSS server.

FIG. 9A is a flowchart illustrating a process of requesting a PDS server to inform a PDS server of a location where personal information is stored.

FIG. 9B is a flowchart illustrating a process in which the PDS server informs the P-client of a personal information storage location in response to a request for location information of the P-client.

9C and 9H are flowcharts illustrating a process in which a P-client retrieves the personal information stored in the local storage and sends the personal information to the PSS server when the personal information is stored in the local storage.

9D to 9H illustrate a process of providing personal information required by the P-client to the PSS server when personal information is stored in the PDS server.

FIG. 9D is a flowchart illustrating a process in which a P-client sends a message requesting personal information to a PDS server.

9E and 9F are flowcharts illustrating a process in which a PDS server receives and analyzes a corresponding message from a P-client and transmits stored personal information to the P-client.

FIG. 9G is a flowchart illustrating a process in which a P-client receives personal information transmitted from a PDS server.

FIG. 9H is a flowchart illustrating a process in which a P-client receives a message for transmission sent from a PDS server.

10 is a flowchart illustrating a process of logging in to a predetermined website.

11 illustrates information input by users through an input screen of a web browser.

12 shows a data structure managed by the data manager 325,

FIG. 13A illustrates a process of generating a message for transmitting information using the P-client message analyzer as an example, FIG. 13B illustrates a message before encoding in the process of FIG. 13, and FIG. 13C illustrates an encoded message. One,

14A illustrates a process of generating an encrypted message in an encryption module, FIG. 14B illustrates a process of generating a decrypted message in an encryption module, and FIG. 14C illustrates an example of an encrypted message.

15A illustrates a network process of actually transmitting a message, and FIG. 15B illustrates a message generated to transmit an encrypted message on a network.

16 illustrates a process of checking condition integrity in a P-client,

17 illustrates a process of managing a data form in the PSS server, and

18 illustrates a DB management process of the PSS server, that is, a management process of the database itself.

In order to achieve the above object, an information exchange system according to an embodiment of the present invention may generate a message utilizing commands and data or analyze a received message according to a requested operation to be performed with a server. A client having a client side message executing unit having a client side message analyzing unit for separating command and data, and a client having a client side network managing unit for transmitting a message through the network; Server-side network management unit for transmitting information through the network, and server-side message analysis unit and command to analyze the work to be performed with the client, collect and perform the necessary information, and to provide the result of the message message Server-side message execution unit with processing unit, data manager for managing form designated by site administrator to link information transmitted through network with DB installed on server, site administrator regardless of DB type installed on server It includes a server with DB linkage to perform DB work according to the format specified by.

Furthermore, the server-side message execution unit manages a PITP utility for encoding or decoding a message, a result value management unit for storing a result value of a job performed by the command processor, and a result code of a job performed by the command processor. It further comprises a result code management unit for the client, it is preferable that the client encodes or decodes the message in the client-side message analyzer.

The client may further include a command manager for analyzing a meaning of the command transmitted from the client-side message analyzer and providing a command for performing a task transmitted from the client-side message analyzer, and from the client-side message analyzer. And a data confirmation unit for managing the transferred data, and a data confirmation unit for confirming whether the data transmitted from the data management unit meets the condition value transmitted from the data management unit.

The client may include a client-side encryption module for encrypting or decrypting a message, and the server may include a server-side encryption module for encrypting or decrypting a message.

The client-side encryption module and the server-side encryption module may encrypt the encoded message.

The server-side network manager includes a socket server for accepting a network connection of the client, and a socket thread for transmitting and receiving data while maintaining a connection with the client.

The server may further include an administrator program for changing setting information related to server setting by a site administrator, and an environment setting management unit for applying the setting information to message transmission and reception.

Here, the setting information may include information related to the DB type and network connection, and the server may further include a condition generating unit for determining the integrity of the data.

The client includes a web browser interworking unit for sending predetermined parameters to the client-side message analyzing unit in response to a web browser call command.

In this case, the client preferably includes a data transmission unit for storing the message in the storage location or reading from the storage location and analyzing the message and providing information on the storage location.

The storage location may be a local storage, the server may be at least two, and the storage location may be a DB of at least one server.

According to another aspect of the present invention, an information exchange method includes a client / server including a storage location where personal information is stored, a client for providing personal information, and a server for requesting necessary personal information. A system, comprising: requesting personal information needed by a client storing personal information in the storage location; Receiving personal information required from a client extracting personal information from a storage location through a network; And reprocessing the personal information provided through the network in accordance with the form used in the DB.

The reprocessing may include reading form information used in a DB, changing personal information received from the client according to the form information, and processing the changed personal information by directly interworking with a DB of the corresponding work. It includes; performing.

Furthermore, the client collects commands and data corresponding to the requested operation and provides a message, analyzes personal information transmitted from the client, divides the command into data and performs the operation corresponding to the analyzed command. It may include a step.

In addition, the method may further include decoding the encoded message transmitted from the client, and the client may include decrypting the encrypted message.

The information providing step may include accepting a network connection of the client; Creating a thread to maintain a connection with the client and to send and receive data. Here, the thread creation step includes applying information related to a network connection.

The reprocessing step may include applying information regarding a data form, and the operation of interworking with the DB may be a login or the operation of interworking with the DB.

In one embodiment according to another aspect of the present invention, in a client / server system including a storage location for storing personal information, a client for providing personal information, and a server for requesting the necessary personal information Means for requesting personal information needed by a client storing personal information at the storage location; Means for receiving the personal information required from the client which has extracted the personal information from the storage location through the network; Means for reprocessing the personal information provided through the network in accordance with the form used in the DB; provided by a computer-readable recording medium recording a program for executing.

In addition, the means for reprocessing the information, the means for reading the form information used in the DB and to change the personal information received from the client in accordance with the form information, and the changed personal information directly linked to the DB during the operation Means for performing a task to process; may further include a program that can be executed.

In addition, the client collects a command and data corresponding to the requested operation and provides a message, analyzes personal information transmitted from the client, classifies the command and data, and performs a task corresponding to the analyzed command. A program for executing the means may be included, and a program for executing the means for decoding the encoded message sent from the client or the means for decrypting the encrypted message sent from the client may be included.

The information providing means may include a means for accepting a network connection of the client and a means for generating a thread for maintaining a connection with the client and transmitting and receiving data, so that a program may be executed. In addition, the thread generating means may include a means for applying information related to a network connection, and the reprocessing means may include a program capable of executing a means for applying information regarding a data format.

In one embodiment according to another aspect of the present invention, in order to perform a DB operation according to a specified form irrespective of the type of DB, including a name area and a content area that can be input, output and search, the name The area and the content area provide a computer-readable recording medium having recorded form data, which can be input, output and stored in pairs with each other.

In the following embodiments of the information exchange method according to the present invention, a network user registers to a predetermined website, a member himself or herself can manage his / her member information stored on the website, and logs in. With reference to the accompanying drawings will be described how to automatically provide the personal information required in the case.

First, in order to perform services such as management of personal information and automatic membership, automatic login, automatic update of personal information, etc., the present invention uses a separate protocol different from the conventional one, and for convenience of the following description, Personal Information Transfer Protocol).

In addition, PITP is a PITP site server program (hereinafter referred to simply as "PSS") installed on a server side related to an Internet service such as a general web service, and a user PC of a general individual who wants a web service. PITP client program (hereinafter referred to simply as "P-client") as a user program to be installed in the PC), and a PITP data server program (PITP Data Server program) that performs membership registration and authentication in conjunction with the PITP client program. (Hereinafter, simply referred to as "PDS") are used, and they operate in conjunction with an existing Internet system as described below.

In addition, PITP according to the present invention operates based on TCP / IP, and is a transfer protocol related to the transmission of personal information corresponding to an application layer of Level 7 in the OSI 7 hierarchy, and is basically a separate database. Do not use However, four DB tables are required to store and manage personal information in the user PC 110 or in a separate server (see PDS server (see 130 in FIG. 1)).

Hereinafter, the overall system configuration for implementing the PITP service according to the present invention, and the detailed configuration and embodiments of the information exchange method will be described.

1 schematically illustrates an overall system configuration for implementing a PITP service according to the present invention.

Referring to FIG. 1, as an embodiment for implementing a PITP service according to the present invention, an information exchange system includes a web browser 111 and data for requesting a service from a P-client 310 to a web server through the Internet. A user PC 110 including a storage device 113 for storing data and an input / output device 112 for data input, a PSS 320, a general web server 121, and a DB server for storing and managing general information. Server comprising a 122 (hereinafter referred to as "PSS server"), and a server including a DB server 132 and a general web server 131 for storing and managing the PDS (330) and personal information (Hereinafter referred to as "PDS server") is connected via the Internet 140.

The general web server is a server system installed to perform a web service through the Internet on a website, and refers to a server that existed before using a PITP service. Here, the web server is described as an example of a web service among the Internet services, and the present invention is not limited thereto.

In addition, the DB server 122 of the PSS server 120 refers to a database server installed by the website itself, DB server that manages the information according to the website-specific self-defined format before using the PITP service By means of the PSS 320 is installed, the interworking process is performed as described below to achieve the PITP service according to the present invention.

In addition, when the DB server 132 of the PDS server 130 does not store and manage personal information in the user PC 110 as described below, the personal information is stored in the PDS server 130 and is to be managed. In this case, as described above, four DB tables are required for the DB, which will be described with reference to FIG. 2. In addition, a file structure corresponding to the four DB tables is also required when personal information is to be stored and managed in the user PC 110.

2 illustrates a basic member information database configuration diagram of the PDS server 130 according to the present invention.

Referring to FIG. 2, the database includes four tables, Pds_site, Pds_data, member, and Pds_real_data tables.

The Pds_site table 210 stores information of websites (ie, websites of the web server of the PSS server 120) in which the requested personal information is actually stored.

In the event that the user's personal information is changed in the future when the user is registered as a member by joining various websites, the member information should be automatically changed by PITP. 310 should be aware of the fact that you are a member of the website. Therefore, when each website is registered, information about the website is stored in the PDS server 130 when personal information is transmitted via PITP, and the Pds_site table 210 is stored in the website itself. DB table that stores information about

The Pds_site table 210 has a Siteindex field 211, a Name field 212, a Siteip field 213, and a Siteport field 214. Here, the siteindex field 211 is used as a number for distinguishing a website and is defined as a non-overlapping primary key, the name field 212 stores a website name, and the siteip field 213 contains an ip of a website. The address is stored and connected to PITP based on this address. The Siteport field 214 stores the port address of the PSS server 120 installed in the website.

The member table 220 is for storing the personal information of a user by distinguishing the user, and has a Member_index field 221, an Id field 222, and a Password field 223.

The member_index field 221 stores an index number for distinguishing a user and is defined as a non-overlapping primary key. An Id field 222 stores an Id of a user, and a password field 223 stores a user's password. Stored.

The Pds_data table 230 is a table in which information about websites is stored when the user's personal information is transmitted to and stored in various websites. In fact, only the list of sites is stored. . The Pds_data table 230 includes a Pds_data_index field 231 storing a serial number defined as a primary key, a Siteindex field 232 connected to a website stored at Pds_site 230, and a user stored in a member table. It has a member_index field 233 in which a serial number is stored, and an Autoupdate field 234 which stores whether or not to automatically update changed information in this site when personal information is changed. In the Autoupdate field, for example, when set to True, the changed personal information is automatically updated.

Pds_real_data table 240 is a table that stores the same personal information stored in each website, and has a Pds_data_index field 241, a fieldnum field 242, a name field 243 and a value field 244. In the Pds_data_index field 241, a member_index field and a siteindex field are combined to store a value for distinguishing information about a specific site of a specific user, and the fieldnum field 242 is used to store various items of information in a website. A field distinguished by a serial number. The name field 243 stores a personal information item name, and the value field 244 stores a value corresponding to the personal information item.

Next, the types and attributes of all information input for processing personal information in PITP are as follows.

In PITP, the entire information used to send and receive personal information can be divided into 9 types of data types and data types such as basic, other, required, and additional.

Here, the basic data are data defined by selecting the common data that are currently used in the Internet a lot and commonly used in PITP, and generally may include a member ID or a password. Other data may not be defined by default in PITP and may be classified as special data required at each website or in special circumstances. Mandatory data is necessary data in a situation where information such as membership is required, for example, information of a nature that must be input, such as a member ID required for membership, may belong to this. In addition, additional data is data that is not necessarily required in a situation where information such as membership registration is required, for example, information that is not necessarily entered, such as a job or a mobile phone number required for membership.

These data types always apply two or more data types together in the actual use process. An example of such a situation is shown below.

ID Resident registration number Certification status License number Basic data O O X X Other data X X O O Required data O X O X Additional data X O X O

As can be seen from the table above, the basic data and other data classifications have a fundamental relationship such as whether PITP is designated as basic data. The distinction between essential data and supplementary data, however, depends entirely on the need for information, regardless of PITP, whether the data is essential at the site or in a particular situation.

In terms of data attributes, all information managed by PITP has its own attributes, such as level and name, that PITP assigns to the information. Information managed in PITP is to be distinguished from other information, and the data attributes in PITP that can be used are as follows.

Levels are used to specify the importance of the data and use integers greater than or equal to one.

Name is used to store the name of the data and has the name of the data used within the PITP compliant program. Basic data can be used anywhere.

Show Name is the name that will be shown to the user. For example, if the name of the external output of the password is a password, the user will see the information as a password.

Type specifies the type of the value the data has. The uppercase letter of 1 byte is used, and the types of types that can be used are as follows.

S:

String type.

I:

Integer type.

B:

Boolean type.

Value:

The actual value of the data itself.

Update:

Specifies whether the data can be modified. In actual implementations, the numbers are represented using the numbers 0 or 1.

Blank:

Specifies whether the data is required data or additional data. In actual implementations, the status is represented by the numbers 0 or 1.

Script:

For the data, "ID can only be 4-8 characters," such as the condition required for the existence of data in the form of a separate script specified by PITP.

Login:

Specifies whether the data is required for login. In actual implementations, the numbers are represented using the numbers 0 or 1.

Next, the script structure is as follows.

Scripts, which are part of data attributes, are used to describe requirements for specific information. The overall configuration allows the judgment of many cases based on regular expression method, but the overall efficiency is excluded except routines that may be overly complicated or slow in consideration of the properties of PITP based on real time. To increase.

An example of the syntax of the script used in PITP (PITP Regular Expression Syntax) D is as follows:

[xyz]

Any character in parentheses is satisfied. \ And-have special meanings.

[^ xyz]

Satisfies any character not included in parentheses. \ And-are used for special meanings.

"xxx"

Refers to a specific string. \ Is not used in any special sense.

{x, y}

X represents constant repetition, x represents the minimum value to be repeated, and y represents the maximum value to be repeated.

*

No or one or more repetitions. Same as {0,}.

+

Represent one or more iterations. It means the same as {1,}.

?

No or one repetition. Same as {0,1}.

()

Group certain patterns into one unit.

\

A special meaning is associated with the following character. If it is followed by a lowercase letter, it represents an escape character.

-

A range is shown within [].

^

The first word in [] is used to mean "out of range."

Introducing the actual script examples composed using the above script syntax as follows.

[a-zA-Z] {1,3}

Represents a word of 1 to 3 letters of the alphabet.

[a-z] {4,}

Lowercase letters represent words of 4 letters or more.

[A-Z] {, 5}

A capital letter of 5 characters or less is shown.

[0-9] {8}

Represents eight letters.

([\ 128- \ 255] [\ 128- \ 255]) {4}

Represents four Korean characters.

\ 65,

Represents a value with an ASCII number of 65.

\ *

It represents an asterisk, not an iteration.

[0-9]

number

-? [0-9] +

Negative numbers have negative signs

-{0,1} [0-9] {1,}

English lowercase letters

[a-z]

English capital letters

[A-Z]

ID between 4-8 characters in English case

[a-zA-Z] {4,8}

The first letter is uppercase English and the rest is 3-8 letters of English upper and lowercase letters and numbers.

[0-9] {6}-[1-4] [0-9] {6}

Resident registration number

And the following is an example of the context configuration of the script used in PITP.

〈Exps〉 :: = 〈exps〉 〈exp〉

| 〈Exp〉

〈Exp〉 :: = (〈exp〉 | 〈exp〉)

| 〈Exp〉?

| 〈Exp〉 *

| 〈Exp〉 +

| 〈Exp〉 {〈digits〉}

| 〈Exp〉 {〈digits〉,}

| 〈Exp〉 {, 〈digits〉} | 〈Exp〉 {〈digits〉, 〈digits〉}

| (<Exp>)

| 〈Str〉

| "〈Rstr〉”

〈Rstr〉 :: = 〈rstr〉 〈rchar〉

| 〈Rchar〉

〈Lchar〉 :: = 〈char〉

| [〈Range〉]

| [^ 〈Range〉]

〈Range〉 :: = 〈range〉 〈rchar〉

| 〈Range〉 〈char〉-〈char〉

| 〈Rchar〉

| 〈Char〉-〈char〉

〈Char〉 :: = 〈rchar〉

| 〈Escchar〉

〈Rchar〉 :: = 〈alpha〉

| Digit

Digits: = digits digits

| Digit

〈Escchar〉 :: = \ b

| \ f

| \ n

| \ r

| \ t

| \ <Alpha>

| \ <Digits>

<Alpha> :: = | a | b | c | ... x | y | z | A | B | C | ... | X | Y | Z

<Digit> :: = 0 | 1 | ... | 9

Next, a set of data that can be commonly used by selecting common data that is currently used on the Internet, such as a member ID or a password, has been described as basic data in PITP. Examples of information designated as such basic data based on the Name property are as follows.

Name Explanation ID ID Password password Name name RRNumber Resident registration number Gender gender Age age Birthday birthday Address address Email e-mail Telephone Phone number Cellular Cell Phone Number Job job Marriage Marital Status Zipcode Zip code Income Monthly income Workshop Work Name Scholarship Education

For example, using the data structure of PITP described so far, for example, the information requested at the time of registration at iUmall (http://www.iumall.co.kr) website is modified as follows to fit the data structure of PITP.

Name / Show Name Data type Level / Type Update / Blank / Login Script Name / member name Basic data / required data 1 / S 0/0/0 4 characters or less ID / Member ID Basic data / required data 1 / S 0/0/1 Up to 8 alphanumeric characters Password / Password Basic data / required data 1 / S 1/0/1 None Email / E-mail Address Basic data / required data 1 / S 1/1/0 None RRNumber / resident registration number Basic data / required data 1 / S 0/0/0 None Zipcode / Postal Code Basic data / required data 1 / S 1/0/0 "xxx-xxx" form compliance Address / address Basic data / required data 1 / S 1/0/0 None Job Basic data / additional data 1 / S 1/1/0 None Workshop / workplace name Basic data / additional data 1 / S 1/1/0 None Telephone / Phone Number Basic data / additional data 1 / S 1/1/0 None Cellular / Cell Phone Basic data / additional data 1 / S 1/1/0 None Scholarship Basic data / additional data 1 / S 1/1/0 None Income / monthly income Basic data / additional data 1 / S 1/1/0 None Marriage / Marriage Basic data / additional data 1 / S 1/1/0 None

Since the PITP service has a very high demand for security that information should be thoroughly encrypted by transmitting information at the time of information transmission, it is preferable to encrypt the information for this purpose. Therefore, PSS encryption module 322 or P-client encryption described later The encryption to be used in module 314 is described first.

In general, the principle of an encryption algorithm is to disclose the encryption and decryption algorithms and to hide the encryption and decryption keys. This encryption method uses a secret key method such as DES, IDEA, RC2, RC4, RC5, AES, Blowfish, and an algorithm using elliptic curve principle (ECC: Elliptic Curve Cryptosystem) and RSA (Rivest-Shamir-Adleman) algorithm. Key method There are other secret key and public key method. For example, PITP encryption can be performed by using public key method using RSA algorithm.

In addition, in relation to encoding decoding and information transmission, which will be described later, basic rules for instructions and execution results thereof will be exemplified.

Basically, the delimiter uses "|" as a delimiter, and when the special characters such as "|" and "%" appear in the data, ASCII code is converted to 2 hexadecimal digits (| →% 7c ,% →% 25) In addition, the command (COMMAND) uses three bytes to unify the uppercase three letters (for example, DDC | Data ...). The result for the command uses four bytes. To unify with four letters (for example, 1010 | Data ....)

Each definition is made according to these basic command rules, and the execution result thereof is as follows. In the table, FN (Field Name) means the name of the item to be used, and FV (: Field Value) means the value of the item to be used.

COMMAND Explanation RESULT DDC Data Duplicate Check Checks specific fields in the north or south, can be used to check IDs. DUPLICATE 1050NOT_DUPLICATE 1051 DLR Data deLete Request Deletes the value of a specific field. DELETE_OK 8080 DELETE_FAIL 8081 DDR Data Definition Request Requests the contents of the data defined. DDR_OK 3010 DDR_ERROR 3011 ReturnCode┃Count┃Level┃Name┃SName┃Type┃Update┃Blank┃Script┃LoginR┃Level2 .... Return the total number of items as the second argument From the third argument, Level, Name, Pass information of SName, Type, Update, Blank, Script, LoginR continuously. DUR Modify Data Update Request information DUR┃FN┃FV ... UPDATE_OK 1060UPDATE_NOT_LOGIN 1061UPDATE_NOT_PDS 1062UPDATE_NOT_EXIST 1063UPDATE_NOT_UPDATABLE 1064UPDATE_FAIL 1065 DLR Load Data Load Reuest information DLR LOAD_OK 1070LOAD_NOT_LOGIN 1071LOAD_NOT_PSS 1072LOAD_NOT_EXIST 1073LOAD_FAIL 1074ReturnCode┃Field┃Value┃Field┃Value .... From the second argument, there are two arguments. Passing. DSR Data Save Save request information.DSR┃FN┃FV ... SAVE_OK 1080 SAVE_NOT_LOGIN 1081 SAVE_NOT_PDS 1082 SAVE_FAIL 1083 ULI User Log In Log in to the appropriate website: ULI┃FN┃FV ... LOGIN_OK 1010 ID_NOT_ESIST 1011 PASSWPRD_INCORRECT 1012 ALREAD_LOGIN 1013 ULO User Log Out Log out the site FN IDULO┃FN ... LOGOUT_OK 1020 NOT_LOGIN 1021 LOGOUT_ID_INCORRECT 1022 URI Register as a User Regist In URI┃FN┃FV ... REGISTER_IN_OK 1030REGISTER_IN_ID_EXIST 1031 REGISTER_IN_FAIL 1032 URO User Regiwt Out Member withdrawal.URO┃FN┃FV ... REGISTER_OUT_OK 1040 REGISTER_OUT_NOT_LOGIN 1041REGISTER_OUT_ID_INCORRECT 1042REGISTER_OUT_FAIL 1043

Next, the P-client, PSS, and PDS shown in FIG. 1 will be described in more detail with reference to FIG. 3.

FIG. 3 illustrates in more detail a functional configuration diagram of a client / server relationship between a P-client and a PSS server of a user PC.

Referring to FIG. 3, the P-client 310 installed in the user PC 110 may include a web browser interworking unit 311, a P-client message execution unit 313, a P-client encryption module 314, and data. It has a transmitter 315 and a P-client network manager 316.

The web browser interworker, when the web browser invokes the P-client 310, understands the instructions from the web browser and passes the appropriate parameters, e.g., to the P-client 310. As will be described later, when the P-client 310 is installed in the user PC 110, a PITP connection menu is generated in a menu, pop-up menu, toolbar, or toolband of a web browser. The web browser checks the current web page and mouse movement event message state and sends appropriate parameters to the P-client message analyzer 313a of the P-client message execution unit 313.

The P-client message execution unit 313 includes a message analyzer 313a, a command manager 313c, a data manager 313b, and a condition checker 313d, analyzes information provided from the outside, and requests It is responsible for generating the necessary messages according to the task, encoding them, and passing the result to the encryption module. It accepts the information input by the user from the web browser linkage unit 311 to determine the type of the requested task, and selects the required command to generate the required message. When data is to be provided, the integrity is checked in consideration of the conditions of the data (see FIG. 16), and then the data is connected to the message to form a single unified message. The generated message is finally converted into an encoded message through an encoding process for special characters, and the encoded message is provided to the encryption module. When a message is received from the outside, the message transmitted from the encryption module is provided. The received message is again analyzed into commands and data, and the data is divided into information and conditional. And it processes the necessary work according to the type of command.

Here, the P-client message analyzer 313a (Main manager) is a module that manages and processes all processes of the P-client 310 of PITP, and calls each module and controls the flow according to the situation. Since every command consists of actual commands and data, which is defined by the communication protocol with the server, the P-client message analyzer 313a receives the command and sends it to the command manager 313c to find out the command. It checks the flow for each instruction and controls each module according to the situation.

The command control unit 313c (Command Control) is a function that processes all commands transmitted / received with the server. In addition, the result code (Result Code) information for the command is stored, and delivers the information about each code to the P-client message analysis unit (313a). All commands and rules are the same as the PSS message execution unit 323 of the PSS server 120. The data is received from the server, separated into data and result values, and forwarded to the message analysis unit. Synthesize necessary commands to create commands to send to the server

Data control unit 313b (Data Control) is a module for managing data, and data used in PITP includes Level, Name, Show Name, Type, Value, It has properties of Update, Blank, Script, and Login. Here, Type is divided into String, Integer, Select, Check, and MultiLine. Such information is transmitted through a command from the server side. The message analyzer separates data and commands through the command manager 313c, and parses the data in the data manager 313b to generate and manage data having respective attributes and types.

Each data has its own input condition, which is defined grammatically by the data parser 313d (Script Parser), and the condition checker uses the value of each data. It checks whether the data is suitable for a script and passes the result to the P-client message analyzer 313a.

The P-client encryption module 314 (En / Decrypt Module) encrypts the data provided by the P-client message analyzer 313a in a public key manner, and provides the result to the data transmitter 315. give. In addition, the encrypted message provided by the data transmitter 315 is decrypted, and the result is transmitted to the message analyzer.

The data transfer unit 315 stores and retrieves data in a file or transmits / receives data to a server through the P-client network manager. The command generated by the message analyzer is encrypted through the encryption module, and then comes to the data transmitter 315. The data transmitter 315 sends data to the file input / output system 112 according to the method specified by the message analyzer. Or send data to the network management unit. In addition, it serves to send the data received through the network management unit to the encryption module and to read the data through the file input and output system 112 and transmit it to the message analysis unit through the encryption module.

In the PITP service, the network connection is the P-client attempting to connect the network to the server. At this time, the P-client network attempts a network connection with the server through a preset port through the connection with the data transmission unit 315. After the connection is made, when the transmission and reception of data are completed and all network operations are completed. Keep the connection up.

The file input / output system 112 (File I / O) of the user computer inputs / outputs data from a file designated by the data transfer unit 315.

Next, the PSS 320 includes a PSS network management unit 321, a PSS encryption module 322, a PSS message execution unit 323, a DB interworking unit 324, a data manager 325, an environment setting management unit 326, It has a condition generator 327 and an administrator program 328.

The PSS network manager 321 (Network Connection) is provided with a socket server 321a (Socket Server: 321a) and a socket thread (Socket Thread: 321b), and accepts a connection request from the outside and exchanges information. That is, when information is transmitted from the outside, the transmission header and the transmission tail are removed to extract an encrypted data portion, and the result is provided to the encryption module. In addition, when encrypted data is provided from the encryption module, the transmission header and the transmission tail are attached to generate a transmission message, and the result is transmitted to the transmission partner, that is, the P-client 310 (FIGS. 15A and 15B). Reference)

Here, the socket server 321a accepts a network connection of the P-client 310. The socket server 321a waits for a connection to a port set in the configuration manager 326 (Server Config), and accepts the connection if there is a connection. Since it operates as a multi-thread, it creates one thread and passes the connection of the P-client 310 to the socket thread, and then waits for another connection.

In addition, a socket thread 321b is created and executed by one thread for one connection of the P-client 310. The connection of the P-client 310 is accepted by the socket server 321a, and then the thread is executed. By generating and passing the connection, the data is actually transmitted and received while maintaining the connection with the P-client 310. The received data is transmitted to the command parser and transmitted the result. When the connection with the P-client 310 is terminated, execution of the thread is stopped and destroyed.

The PSS message executing unit (Command Control) 323 includes a PSS message analyzing unit 323a, a command processing unit 323b, a PITP utility 323c, a result value managing unit 323d, and a result code managing unit 323e. It analyzes the messages provided by the client, generates and encodes the necessary messages according to the requested operation, and passes the result to the encryption module. In other words, it receives the message transmitted from the password and the module, analyzes the command and data, performs the necessary work according to the type of command by interworking with the DB, collects the result and sends it as a new message. When a job is required for the job, the job is performed using the DB interlocking unit 324.

The PSS message execution unit 323a (Command Parser) is a function that processes all commands received from the P-client 310. The delimiters, encoding, and decoding are processed in the PITP utility. Each data information about the decoded and separated delimiters is transferred to the command processor 323b after being reconstructed into a list.

The PITP utility 323c processes encoding and decoding necessary for PITP. That is, when a plurality of data is transmitted, it is necessary to define a separator bar (Separator Bar: '┃' in the embodiment of PITP) that can distinguish each factor, so that encoding and decoding should be performed. That is, by the encoding, the '┃' character corresponding to the delimiter in the actual data is converted into another character. In other words, the% character is displayed first to indicate that it is encoded, and ASCII codes of the character are converted to hexadecimal and displayed after the character. There are 256 ASCII codes, which can be represented with exactly two digits when expressed in hexadecimal. In other words, the ASCII code of '┃' character is 124 and if it is represented in hexadecimal, it becomes '7c', so when '┃' character is encoded, it becomes '% 7c'. Since the encoding is indicated by the '%' symbol, encoding for the '%' character is required in addition to the '┃' character. The '%' character is ASCII code 37, so if you convert it to hexadecimal, it becomes '25', so the '%' character in the data is encoded as '% 25'.

In case of decoding, it is separated into tokens based on '|'. If there is a '%' character among the characters in each token, the two characters after it are judged as hexadecimal and converted to decimal to find the character corresponding to the ASCII code.

The command processing unit 323b (Process) performs the corresponding operations based on the first three letters corresponding to the command among the received data. If additional factors are needed, they are used appropriately, and the work results are transferred to the result management unit and stored. Before you do anything, check two things first. The first is to determine if the requested operation is feasible on this server. For example, personal information can be retrieved from a server installed in each site, but subscription to the entire site cannot be performed. The second checks whether you are logged in. Some operations can be done without logging in, and others are not. For example, changing personal information is possible only after login.

The result value management unit 323d (Result) stores the results of the operation in the command processing unit 323b and reconstructs them in a form suitable for transmission. The result value to be transmitted has a code value indicating a result status first, and these values are stored in a result code manager 323e (Return Code). If additional factors are needed, they are reconfigured into a transportable form to conform to the protocol of PITP. The concatenation of multiple arguments based on delimiters and the encoding of the actual data itself are handled by the PITP utility 323c.

The result code management unit 323e (Return Code) stores a code value for the processing result, and the code value is divided into two types, a success and failure.

Since the DBS 324 (DB Module) operates regardless of the type of DB, the DB interworking unit 324 operates in relation to the DB and functions to handle the differences between the DBs in the middle. Since server is generally Java based, it is based on Java DataBase Connectivity (JDBC). JDBC can generate connectivity regardless of DB type, but JDBC driver Due to the difference, it is not completely independent of the type of DB. Therefore, these differences are in charge of the DB interlocking unit 324, and thus, other than the DB interlocking unit 324, the operation is completely independent of the DB.

The data manager includes a data field (325a), a data list (325b), and a data body (DATA body: 325c), and manages the form of information stored in the DB. The site administrator of the web server receives the contents set using the data body 325c (Administrator Tool) and generates a form of data according to the received contents. The generated form is provided at the request of the DB interlocking unit 324, and the DB interlocking unit 324 manages the connection of the DB according to the provided form.

The data field 325a is a part for defining a user's personal information item, and in order to define a personal information item, a name, a displayed name, a data type, whether update is possible, a space is available, and a linked DB table (Table) ), Whether it is used as a key, whether it is required at login, information steps, scripts, and actual data items are required.

The data list 325b is a portion where the data fields 325a are collected. One data field 325a is generated for each item of personal information, and among these pieces of information, the data list 325b connects the same information level. The data list 325b is gathered step by step to form a data body 325c.

In the data body 325c, user personal information is stored, and information items of the user are divided into levels, and information of various items is stored in each level. One data list 325b is generated for each information step, and the data body 325c is such that the data list 325b is collected and the entire user information is stored.

The data body 325c (Admin Tool) is a program (Tool) that can change setting information of the PSS server 120 or the PDS server 130. The administrator may change the setting information of the PSS server 120 using such a program. The setting information of the PSS server 120 or the PDS server 130 includes the server name, the type of server (whether it is a data server or a server installed in an individual site), a port number to accept a connection, a DB type, and a connection. Various related items are included.

The configuration manager 326 (Server Config) processes functions related to the setting of the PSS server 120 or the PDS server 130. The server settings store the server name, server type (full data server or server installed at the individual site), the port number to accept the connection, the type of database, and various items related to the connection. The information of the configuration manager 326 may be set through the data body 325c (Admin Tool), and applied when the socket thread 321b is generated based on the stored information.

In addition, the user PC 110 may be networked through the PSS server 120 and the PDS server 130, which is a separate server, through the Internet, and the PITP service may be used, such as a PDS server installed in the PDS server 130 ( 130, the components of the program are the same as the components of the PSS 320 and the functions thereof will be omitted in order to avoid duplication of description, and in the following description of the components of the PDS server 130 of the PSS 320 The same code | symbol as a structure shall have the same function.

The method of installing the P-client 310, PSS 320, and PDS 330 as described above may be separately purchased for each user PC 110, PSS server 120, or PDS server 130, respectively. In some cases, the P-client 310 may implement an automatic installation by placing an ActiveX control on a web page, or may be implemented using accessories provided by Explorer, which is a Microsoft web browser.

The following is an example of implementing automatic installation by placing ActiveX Control on a web page. In other words, if you place ActiveX on a web page, a window will appear asking if you want to install ActiveX automatically if a lower version of ActiveX is installed or the ActiveX is not installed. Click "Yes" to install the ActiveX. If you bundle the inf file containing the installation program of the P-client 310 and the command line to execute the program in the cab file, the installation program is automatically executed while installing the ActiveX, and the P-client 310 is automatically You can install it.

As a method of using the accessories provided by the explorer, there may be a method using a toolbar button, an explorer bar, or a toolband.

Additional buttons can be placed on the Toolbar, such as Back, Forward, Stop, etc., with the icon, for example, the Messenger button on the far right of the Toolbar. These buttons appear when you install msn messenger, and are buttons that run Windows applications. This button can be used to launch other Explorer Bars or launch applications like the messenger button.

In addition, the Explorer Bar means a bar that can additionally contain a desired menu. The bar can be a Vertical Bar or a Horizontal Bar according to its location. The Explorer Bar is an ATL / COM object that creates and registers a dll file. Create In the part of registering the dll file, the value is entered in the registry. When it is registered normally, the menu is created under the search window, and the vertical bar above and the horizontal bar below can be created based on the center branch line.

Toolband means the band added in the upper toolbar. Toolband can be created by registering dll file by making dll file with ATL / COM like explorer bar.

According to this configuration, the P-client 310 is installed on the user PC 110, and enables the management and automatic membership of personal information through PITP, automatic login, automatic update of personal information, etc. In conjunction with the Internet web browser 111, such as Internet Explorer (Internet Explorer) or Netscape (Netscape), it automatically executes when a member registration or login occurs in various websites, and enables the corresponding operation. In addition, the P-client 310 basically stores and manages the user's personal information. Based on this, the P-client 310 registers and logs in to the website where the PSS 320 is installed, or inputs or confirms personal information. Automatically do the work for you when needed. In addition, when the personal information is modified or changed in the P-client 310, the information of the registered web sites is also updated, so that the member information stored in each PSS server 120 can be automatically managed.

And, if the PSS 320 is installed, the existing DB is data mapping (Mapping) is made to be compatible with the DB of the P-client 310 or other PSS server 120 or PDS server 130. That is, the fact that items such as member name, password, and address of the member information are the same fields as Name, Password, and Address defined in PITP, and thus the user PC 110 and data of P client are defined. Communication is possible, so data can be shared with other sites, and data sharing is possible, such as automatic membership registration, automatic login, and automatic update of personal information. Since the PSS server 120 can take the form of being mounted as a module (MODULE) to the existing system without changing the existing system in order to provide maximum convenience to the existing website, the PSS ( 320) can be installed. In addition, even before the PSS 320 is installed, users who have already registered as members of the website transmit the personal information of the user according to the PITP standard. Therefore, even if the user has already subscribed to the website, if the P-client 310 is installed on the user PC 110, the member information can be received and the website can be used as it is to use the information.

The PDS server 130 is used to enable the PITP service using a separate server in addition to using the PITP service using the P-client 310, and in this case, the members of the members who use the user PC 110. It handles subscription, user authentication, and information management functions of the PSS servers 120. To this end, the PDS server 130 provides personal information defined in PITP, and the user forms a database of personal information based on the personal information. The personal information stored in the PDS server 130 is stored in each PSS server ( It is used to register or log in to 120). In addition, when the PSS 320 is installed in the server system of each website, the PDS server 130 is the basic information such as the site name, URL, IP, Port of the website and the installed PSS 320 Since the index is stored, the P-client 310 can manage site-specific information of users based on the site information and the index.

Such a configuration and function will be described in more detail with reference to FIGS. 4 to 18 attached to the method for providing personal information according to the present invention.

In order to use the PITP service, a P-client 310 and a PSS server 120 are required. First, an environment of the PSS server 120 must be set by a web site administrator.

4 is a flowchart illustrating a process of setting an environment of a PSS (or PDS) server by a website administrator of the server in order to configure the server as described above.

Referring to FIG. 4, in step 401, the website manager accesses the data body 325c of the PSS server 120 using the web browser 111 or a predetermined application program to determine and input a desired setting value.

In step 402, the data bodies 325c are classified according to their types, and the results are analyzed.

In step 403, the process proceeds to step 404 if it relates to the network setting depending on whether the setting is for network setting or to step 406 if it relates to a data manager 325 other than the network.

In step 404, the input information is transferred to the configuration manager 326.

In step 405, the environment setting manager 326 stores a setting value received from the data body 325c and applies the setting value to the socket thread 321b to generate a thread and use it for data transmission and reception as described below.

In step 406, in the case of setting values other than information on network setting, that is, information on the structure of the data manager 325, the condition generating unit 327 generates a condition.

In step 407, the condition generated in the condition generator 327 is transferred to the data manager 325, and in step 408, a data field, a data list 325b, and a data body 325c are generated together with the transferred condition. .

In order to use the PITP service, the user must install the P-client 310 in the user PC 110.

5 is a flowchart illustrating a P-client 310 installation process according to PITP membership.

Referring to FIG. 5, in step 501, a user selects PITP membership.

In step 502, the PIT installation guide program determines whether or not the P-client 310 is installed in the user PC 110, and terminates if it is already installed, and moves to step 503 if it is not installed. .

In step 503, the PITP installation guide program terminates if the user does not want to install depending on whether or not to install the P-client 310, and moves to step 504 if the user wants to install it.

In step 504, the PITP installation guide program executes the PITP installation program to install the P-client 310 program on the user PC 110 and moves to step 505.

In step 505, the PITP installer provides an input screen for the user to enter personal information and proceeds to step 506.

In step 506, the PITP installation program determines whether the user inputs the personal information is complete, and waits if the user does not finish, and moves to step 507 when the personal information input is finished.

In step 507, the user specifies a storage location of personal information.

In step 508, the PITP installation program determines whether or not to store in the user PC 110, go to step 509 if the storage is stored in the user PC 110, otherwise, go to step 510.

In step 509, the P-client 310 encrypts and stores the personal information in the form of a file in the user PC 110 and terminates the installation.

In step 510, the P-client 310 accesses the PDS server 130 and transmits personal information.

In step 511, the P-client 310 determines whether the transmission of the personal information to the PDS server 130 is completed and waits if the transmission of the personal information is not completed, and if the personal information transmission is completed, the P-client ( The installation of 310 is terminated.

6 and 7 illustrate the process of storing personal information by the P-client 310 in more detail. The user PC 110 personal file system using the input / output system of the user PC 110 (hereinafter referred to as “local storage”). ")) Or the processes stored in a separate PDS server 130 are shown.

Or less, the local repository is private to the user

First, FIG. 6 is a flowchart illustrating a process of storing personal information in a local storage using an input / output system of a user PC. In this case, the local storage means a file system in a user's personal PC.

Referring to FIG. 6, in step 601, the P-client message analyzer 313a starts a personal information transmission task.

In step 602, the command manager 313c provides a personal information storage command and moves to step 603.

In step 603, the P-client message analyzer 313a generates a message, encodes the message, and moves to step 604. FIG.

In step 604, the P-client encryption module 314 encrypts and encrypts the message and forwards the encrypted message to the data transmitter 315. FIG.

In step 605, the data transmission unit 315 determines whether to store the personal information in the user PC 110 as a local storage, and if it is stored in the user PC 110, the data transmission unit 315 moves to step 606, and the user PC 110. If not, go to step 607.

In operation 606, the data transmitter 315 stores the message in the form of a file in the user PC 110 using the file input / output system 112 of the user PC 110.

In step 607, the data transmitter 315 designates the network information of the party to be transmitted, forwards the encrypted message to the P-client network manager 316, and moves to step 608.

In step 608, the P-client network manager 316 converts the encrypted message into a message for transmission and transmits it to the PDS server 130.

In step 609, the network manager determines whether the message transmission is completed, waits if it is not completed, and ends storing personal information when the message transmission is completed.

Next, FIG. 7 is a flowchart illustrating a process of storing personal information in a separate PDS server 130 other than the local storage. In this process, the personal information is sent from the P-client 310 to the PDS server 130, and the PDS server 130 receives the message and then finds that it is a personal information storage command and stores the information in the DB. .

Referring to FIG. 7, in step 701, the socket server 321a waits for a connection from the outside.

In step 702, the socket server 321a determines whether a connection has occurred, and moves to step 701 if no connection has occurred, and moves to step 703 if a connection has occurred.

In step 703, the socket server 321a accepts a connection from the outside, and passes control to a connection from the outside to the socket thread 321b.

In step 704, the socket thread 321b receives the message for transmission, extracts the encrypted message and passes the result to the PDS encryption module 322.

In step 705, the PDS encryption module 322 decrypts the encrypted message and passes the message to the PDS message analyzer 323a.

In step 706, the PDS message analyzer 323a decodes the message using the PDS PITP utility and analyzes the command and data from the message.

In step 707, the command processor 323b receives the analyzed command and data and analyzes what kind of work to perform.

In step 708, the command processing unit 323b moves to step 709 if the analyzed command is an information storage command, and ends otherwise.

In step 709, the data manager 325 provides a data form to the DB interlocking unit 324, and the DB interlocking unit 324 stores the corresponding data in the DB.

In step 710, the command processing unit 323b stores the processing result in the result value managing unit 323d and ends.

Next, the user must load the personal information required for using the PITP service to the user PC (110). In the case where personal information for PITP service is stored in the local storage of the user PC 110, the necessary personal information is read directly from the file input / output system 112 of the user PC 110, and the PDS server 130 ), The P-client 310 needs to obtain and obtain the personal information required by the P-client 310.

8 is a flowchart illustrating a process in which the P-client 310 requests and obtains personal information stored in the PDS server 130. In this case, the P-client 310 sends a message requesting personal information to the PDS server 130, and the PDS server 130 reads the personal information from the DB by analyzing the message and makes a message to the P-client. Provided to 310.

First, FIG. 8A illustrates a process of sending a message requesting personal information to the PDS server 130 by the P-client 310 as a flowchart.

Referring to FIG. 8A, in step 801, the P-client message analyzer 313a starts a request for personal information.

In step 802, the command manager 313c provides an information request command.

In step 803, the P-client message analyzer 313a generates and encodes the message.

In step 804, the P-client encryption module 314 encrypts the message and passes the encrypted message to the data transmitter 315.

In step 805, the data transmission unit 315 designates network information in a transmission state, and transmits an encrypted message to the P-client network management unit 316.

In step 806, the P-client network manager 316 converts the encrypted message into a message for transmission and transmits it to the PDS server 130.

8B and 8C are flowcharts illustrating a process in which the PDS server 130 receives and analyzes a corresponding message from the P-client 310 and transmits the stored personal information to the P-client 310. will be.

8B and 8C, in the PDS server 130, the socket server 321a waits until there is a connection from the outside, especially the P-client 310 (steps 808 and 809).

At step 810, socket server 321a accepts the connection, if any, from P-client 310 and passes network management to socket thread 321b.

In step 811, the socket thread 321b receives the message for transmission, extracts the encrypted message, and passes the result to the PDS encryption module 322.

In step 812, the PDS encryption module 322 decrypts the encrypted message and passes the message to the PDS message analyzer 323a.

In step 813, the PDS message analyzer 323a decodes the message using the PITP utility 323c and analyzes the command and data in the message.

In step 814, the command processor 323b receives the analyzed command and data and analyzes what kind of work to perform.

In step 815, if it is determined that the analysis result information request command is moved to step 816.

In step 816, the data manager 325 provides a data form, and the DB interlocking unit 324 retrieves the requested data and stores the result in the result value managing unit 323d.

In step 817, the PDS message analyzer generates a result message and encodes the message using the PITP utility.

In step 818, the PDS encryption module encrypts the message and forwards the encrypted message to the socket thread 321b.

In steps 819 and 820, the socket thread 321b converts the encrypted message into a message for transmission and transmits the message to the P-client 310 to terminate the process in the PDS server 130.

8D illustrates a flowchart of receiving personal information transmitted from the PDS server 130.

Referring to FIG. 8D, the P-client 310 is waiting for personal information to be transmitted from the PDS server 130 (steps 821 and 822).

In step 823, when personal information is transmitted from the PDS server 130, the P-client network manager 316 receives the message for transmission and passes it to the data transmitter 315.

In step 824, the data transmitter 315 extracts the encrypted message from the message for transmission and passes the result to the P-client encryption module 314.

In step 825, the P-client encryption module 314 decrypts the encrypted message, and passes the decrypted message to the P-client message analyzer 313a.

In step 826, the P-client message analyzer 313a decodes the message and analyzes the command and data.

In step 827, the data manager 313b analyzes the value of each data and passes the script to the data checker 313d.

In step 828, the data checking unit 313d analyzes the condition of the transferred script and ends the information request process in the P-client 310.

Looking at the process of providing the personal information required by the PS client 120 to the PSS server 120, the P-client 310 first, the P-client 310 to inform the location where the personal information is stored The PDS server 130 requests the PDS server 130 to inform the P-client 310 of where the personal information is located. Next, the P-client 310 analyzes the location information and retrieves the personal information from the local repository or the PDS server 130 and provides it to the PSS server 120.

9A to 9F show the whole process in a flowchart.

First, FIG. 9A illustrates a process of requesting the PDS server 130 to inform the PDS server 130 of a location where personal information is stored. Referring to FIG. 9A, in step 901, the web browser linkage unit is performed. Analyze the type of event that has occurred.

In step 902, if it is determined that the request is a personal information, step 903 is reached;

In step 903, the P-client message analyzing unit 313a starts a personal information location checking operation.

In step 904, the command manager 313c provides a location seal command.

In step 905, the P-client message analyzer 313a generates and encodes the message.

In step 906, the P-client encryption module 314 encrypts the message and forwards the encrypted message to the data transmitter 315.

In step 907, the data transmission unit 315 designates the network information of the transmission state, and delivers the encrypted message to the P-client network management unit 316.

In step 908, the P-client network manager 316 converts the encrypted message into a message for transmission and transmits the message to the PDS server 130. In step 909, the P-client network manager 316 waits until transmission of the message for transmission is completed.

Next, FIG. 9B is a flowchart illustrating a process in which the PDS server 130 notifies the P-client 310 of the location of storing personal information in response to the location information request of the P-client 310, and FIG. 9B. For reference, in steps 910 and 911, the P-client 310 waits until the location information is transmitted from the PDS server 130.

In step 912, when the P-client network manager 316 receives the message for the location information, the P-client network manager 316 transfers the message to the data transmitter 315.

In step 913, the data transmitter 315 extracts the encrypted message from the transmitted message and passes the result to the P-client encryption module 314.

In step 914, P-client encryption module 314 decrypts the encrypted message and passes the message to P-client message analyzer 313a.

In step 915, the P-client message analyzer 313a analyzes the command and data by decoding the message.

In step 916, the command manager 313c analyzes the result code manager 323e, and in step 917, determines whether to use the local storage, and moves to step 920 (see FIG. 9C) when using the local storage, If the local store is not used, the process moves to step 930 (see FIG. 9D).

Next, FIGS. 9C and 9H illustrate a process of providing personal information required by the P-client 310 to the PSS server 120 when personal information is stored in a local repository. 9C, in operation 920, the data transmitter 315 reads personal information stored in the form of a file in the user PC 110 using the file input / output system.

In step 921, the P-client encryption module 314 decrypts the personal information and passes it to the P-client message analyzer 313a.

In step 922, the P-client message analyzer 313a starts providing the personal information.

In step 923, the command manager 313c provides an information providing instruction, and in step 924, the condition confirming unit confirms whether the condition of the personal information read from the storage location and the information requested from the outside match. That is, in order to provide externally requested personal information, the personal information of the storage location is read, and then the read personal information is checked whether the form matches the requested personal information.

In step 924, the condition goes to step 927 if the conditions do not match, and if step matches, step 926.

In step 926, if the condition is matched, the corresponding data is included in the transmission data and the process moves to step 928. Here, the data confirmed to match the condition is transmitted to the requesting party.

In step 927, if the conditions do not match, the process moves to step 928 without including the corresponding data in the transmission data.

In step 928, it is analyzed whether there is data remaining to evaluate the condition, and if so, the flow goes to step 925, and if not, the flow goes to step 960.

9D to 9H illustrate a process of providing the personal information stored in the PDS server 130 to the PSS server 120 by the P-client 310 in a flowchart.

FIG. 9D is a flowchart illustrating a process in which the P-client 310 sends a message requesting personal information to the PDS server 130. Referring to FIG. 9D, in operation 930, the P-client message is analyzed. The unit 313a starts a request for personal information to the PDS server 130.

In step 931, the command manager 313c provides an information request command, and in step 932, the P-client message analyzer 313a generates and encodes a message.

In step 933, the P-client encryption module 314 encrypts the message and transmits the encrypted message to the data transmitter 315.

In step 934, the data transmission unit 315 designates the network information of the party to be transmitted and delivers the encrypted message to the network manager.

In step 935, the P-client network manager 316 converts the encrypted message into a message for transmission, and transmits it to the PDS server 130.

9E and 9F illustrate a process in which the PDS server 130 receives and analyzes the corresponding message from the P-client 310 and transmits the stored personal information to the P-client 310 as a flowchart.

9E and 9F, in the PDS server 130, the socket server 321a is waiting for the connection of the external, in particular, the P-client 310 (steps 940 and 941).

In step 942, the socket server 321a accepts the connection, if any, from the P-client 310 and hands over network management to the socket thread 321b.

In step 943, the socket thread 321b receives the message for transmission, extracts the encrypted message, and passes the result to the PDS encryption module 322.

In step 944, the PDS encryption module decrypts the encrypted message and passes the message to the PDS message analyzer 323a.

In step 945, the PDS message analyzer 323a decodes the message using the PITP utility 323c and analyzes the command and data in the message.

In step 946, the command processor 323b receives the analyzed command and data and analyzes what kind of work to perform.

In step 947, if it is determined that the analysis result information request command is reached, step 948 is reached.

In step 948, the data manager 325 provides a data form, and the DB interlocking unit 324 retrieves the requested data and stores the result in the result value managing unit 323d.

In step 949, the PDS message analyzer generates a result message and encodes the message using the PITP utility.

In step 950, the PDS encryption module encrypts the message and delivers the encrypted message to the socket thread 321b.

In steps 951 and 952, the socket thread 321b converts the encrypted message into a message for transmission and transmits it to the P-client 310.

FIG. 9G illustrates a process in which the P-client 310 receives a transmission message transmitted from the PDS server 130. Referring to FIG. 9G, in operation 960, the P-client 310 may use a PDS server ( Wait for information to be sent from 130).

In step 961, if there is a transmission from the PDS server 130, in step 962, the P-client network manager 316 receives the message for transmission and passes it to the data transmitter 315.

In step 963, the data transmitter 315 extracts the encrypted message from the message for transmission and passes the result to the P-client encryption module 314.

In step 964, the P-client encryption module 314 decrypts the encrypted message and passes the message to the P-client message analyzer 313a.

In step 965, the P-client message analyzer 313a decodes the message and analyzes the command and data.

In step 966, the data manager 313b analyzes the value of each data and passes the script to the data checker 313d.

In step 967, the data checking unit 313d analyzes the condition of the transferred script.

In step 968, the P-client message analyzer 313a starts a personal information providing task.

In step 969, the command managing unit 313c provides an information providing instruction. In step 970, the data checking unit 313d checks whether the conditions of the information to be provided and the information to be provided match, and in step 971, the condition. Analyze whether this matches.

If the conditions do not match, the process proceeds to not include the data in the transmission data in step 972, and the process proceeds to step 974. If the conditions do not match, the partner who requested the information in step 933 has confirmed that the conditions match. The data is included in the transmission data to be sent to step 974.

In step 974, it is analyzed whether there is data left to evaluate the condition, and if the condition remains, the process moves to step 971, and if the condition remains, the process goes to step 974.

In step 975, the P-client message analyzer 313a generates and encodes the message.

In step 976, the P-client encryption module 314 encrypts the message, and transmits the encrypted message to the data transmission unit 315.

In step 997, the data transmitter 315 designates the network information of the party to be transmitted and transmits the encrypted message to the P-client network manager 316.

In step 978, the P-client network manager 316 converts the encrypted message into a message for transmission and transmits it to the PSS server 120.

In step 979, wait until the transfer is complete and terminate when the transfer is complete.

According to this process, after the personal information stored in the local storage of the user PC 110 or the PDS server 130 is provided from the P-client 310 to the PSS server 120, the PSS server 120 is provided Personal information is automatically saved in DB. The storage process of the PSS server 120, the process of storing personal information to the PDS server 130, that is described with reference to Figure 7, that is to transmit the personal information from the P-client 310 to the PDS server 130 This is the same as the storing process, and a description thereof will be omitted to avoid duplication.

FIG. 10 is a flowchart illustrating a process of logging in to a predetermined website. Referring to FIG. 10, in step 1010, a user selects a PITP member subscription at a predetermined website.

In step 1011, if the PSS 320 program is installed on the website, the process goes to step 1012, and if the PSS 320 program is not installed, the process goes to step 1020.

In step 1012, it is determined whether the P-client 310 is installed in the user PC 110, and if the P-client 310 is installed, the process moves to step 1013, and the P-client 310 is not installed. If no, go to step 1020.

In step 1013, it is determined whether the member has already subscribed to the website, and if it is a new member, the process moves to step 1014, and if the member is an existing member, the procedure goes to step 1015.

In step 1014, the automatic member registration process is performed according to the process as described with reference to FIG.

In step 1015, it is determined whether the website is registered with the P-client 310, and if it is already registered, the process moves to step 1017, and if not, the information of the website is stored in the P-client 310 ( Step 1016), the process moves to step 1017.

In step 1017, the automatic login process is performed according to the procedure described with reference to FIG. 9, and then the login process is terminated.

In step 1020, since the PITP is not available, the website outputs a manual login screen, waits for input of the login information (step 1021), and when the login information is input, the website performs a login process. End the login process.

Next, various forms of data generated or existing in each process described in the above flowchart will be described.

FIG. 11 illustrates information input by users through an input screen of the web browser 111.

The information shown in FIG. 11 corresponds to the first information input by the user through the input screen of the web browser 111 and may exist as personal information of the member between the web browser 111 and the web browser linking unit 311. Data that exists.

12 shows a data structure managed by the data manager 325 portion.

In order to store and manage personal information in the PDS or PSS server 120, a data form must first be registered in the data manager of the PDS or PSS server 120. FIG. 12 illustrates this data form. Referring to FIG. 12, the 'name' item of the information shown in FIG. 11 is composed of one data list 325b using this data field 325a. In addition, when data lists 325b applied to all items such as 'ID' and 'password' are collected, one data body 325c is configured. According to this data format, data is stored and managed in the PSS or PDS server 130.

FIG. 13A illustrates a process of generating a message for transmitting information using the P-client message analyzer 313a as an example, FIG. 13B illustrates a message before encoding in the process of FIG. 13, and FIG. 13C is an encoding. Shows the message.

Referring to FIG. 13A, in order to exchange information, the P-client message analyzer 313a generates a message so that the message can be exchanged with each other.

If there is a message generation request, the P-client message analysis unit 313a first analyzes the type of the requested operation (step 1301).

In this way, an instruction suitable for the type of job is acquired from the P-client instruction management unit 313c (step 1302), and an item name and item value of data to be transferred from the data management unit 313b are obtained (step 1303).

Then, the data to be delivered is classified and separated by a '┃' separator (step 1304), and a message to be transmitted is generated by combining the command and the data (step 1305).

Referring to FIG. 13B, a format and an example of a message generated in step 1305 of FIG. 13 are illustrated. In this case, there are two types of messages using a command 1311 and a return code 1312. Both of them are shown in the drawing. It is used when requested, and the format using the return code indicates that it was used to complete the task and report the result.

Referring to FIG. 13A, when a special symbol such as a delimiter '┃' is present among the messages generated in step 1305, the corresponding data is encoded (step 1306). If there is no special symbol, encoding is performed. It is not the same as the message generated in step 1305.

Referring to FIG. 13C, a format and an example of a message encoded in step 1306 of FIG. 13 are illustrated.

FIG. 14A illustrates a process of generating an encrypted message in an encryption module, FIG. 14B illustrates a process of generating a decrypted message in an encryption module, and FIG. 14C illustrates an example of an encrypted message. Here, encryption will be described with respect to the public key method.

Referring to FIG. 14A, when a message to be encrypted (or an encoded message) is provided to an encryption module, the public key is transmitted to a transmission partner (ie, a PSS or a PDS server) between the public key and the private key, and the public key is transmitted. To encrypt the encoded message.

Referring to FIG. 14B, when a message encrypted with a public key is provided to an encryption module, the message encrypted with the generated private key is decrypted.

Referring to FIG. 14C, a message before and after being encrypted is illustrated. Here, the message before encryption corresponds to the decryption message, and the message after encryption corresponds to the encrypted message.

15A illustrates a network process of actually transmitting a message, and FIG. 15B illustrates a message generated for transmitting an encrypted message on a network.

Referring to FIG. 15A, when the data transmitter 315 provides the network manager with location information of data to be transmitted (that is, an encrypted message) and a transmission partner (PSS or PDS server), the network manager may transmit a header and a transmission header. Create a message for transmission by applying the information to the data to be transmitted. Then, it attempts to connect with the transmission partner and transmits a message for transmission to the transmission partner. When the transmission message is transmitted from the transmission partner, the transmission header and the additional information are removed from the transmission message, and then the data transmitted to the data transmission unit 315 is provided.

Referring to FIG. 15B, a message generated for transmitting an encrypted message on an actual network is illustrated. Here, a header for transmission and a tail for transmission are applied, and the message is provided to an external transmission partner by the network manager.

16 illustrates a process of checking condition integrity in the P-client 310.

Referring to FIG. 16, when the data manager 313b passes the item value and condition information of data to the data checker 313d, the data checker 313d analyzes the condition information and a grammatical error exists in the condition information. Do an error check. After the error check on the condition information is completed, the data checking unit 313d checks whether the item value corresponds to the content specified in the condition information, derives the result, and displays the result of the condition analysis on the data item value. By passing to 313b), it is possible to confirm whether the data item quotient matches the condition to be considered in providing the data. Here, the condition integrity process corresponds to a process of checking which data meets a predetermined condition. In this case, the condition is provided in the form of the script as described above. For example, 'AAA' meets the condition '[AZ] +', but '111' does not satisfy the condition [AZ] + '. This verification can be said to be performed.

17 illustrates a process of managing a data form in the PSS server 120 in more detail.

Referring to FIG. 17, when the web site administrator delivers configuration information to the data body 325c using an input device, the data body 325c is a type of information input into two types of network configuration and database connection configuration. The data form information is generated by extracting the data form setting information from the database environment setting information, and obtaining the condition information provided by the condition generating unit 327, and the data body 325c includes the data name and the item. By passing the value and condition information to the data manager 325, the DB interlocking unit 324 performs the interworking operation with the DB according to a form designated by the administrator so that the website can utilize the database as desired. That is, the DB interworking unit 324 always processes the work in conjunction with the data manager 325, the data manager 325 is a form that expresses the relationship between the actual DB and the data used in the PSS (320). It can be said to manage.

18 shows a DB management process of the PSS server 120, that is, a management process of the database itself.

Referring to FIG. 18, when the command processing unit 323b extracts a job to be processed by interworking with the DB, and transfers the extracted DB interlocking tasks and DB interworking task information to the DB interlocking unit 324, the DB interlocking unit ( 324 first generates a general query for working with the DB, obtains data form information to be considered when interworking with the DB from the data manager 325, and converts the generated universal query into an execution query suitable for an actual DB. . The DB interworking unit 324 delivers the query for execution to the DB, executes the query, and changes the execution result of the query to a general-purpose result form. In addition, the DB interlocking unit 324 transmits the execution result according to the DB interlocking operation to the result value managing unit 323d.

According to the information exchange system and method according to the present invention as described above, it is possible to make the user to database their own information and directly manage the information based on the separately defined basic personal information, and also to register this information when registering Based on this, the information required by the site is automatically entered to enable convenient and simple membership registration.

In addition, not only the user's personal information, but also the member information subscribed to each website can be stored and managed as a database in accordance with the regulations proposed by PITP, so that the login can be automatically proceeded based on this. This prevents the inconvenience caused by logging in and the accident of forgetting the information of each site.

Moreover, PITP can manage the user's information and the member information subscribed to each site by database, so when the user modifies the user's information, the information stored in each site can be automatically updated.

Furthermore, based on the encryption method suggested by PITP, when transmitting / receiving personal information, it is completely encrypted and transmitted / received. Therefore, the user can manage and input the information without worrying that his information is maliciously leaked.

Therefore, the Internet user can automatically provide the necessary personal information, such as when a user registers or logs in to a predetermined website, and can directly manage his / her member information stored in the website. .

Claims (30)

A client-side message execution unit having a client-side message analysis unit for generating a message utilizing a command and data according to a requested operation to be performed with a server, or analyzing a received message and classifying the received command and data; A client having a client-side network manager for transmitting a message through the network; A server side network management unit for transmitting information through a network; A server-side message execution unit including a server-side message analyzer and a command processor to analyze the work to be performed with the client, collect and perform necessary information, and then provide the message as a result; A data manager for managing a form designated by a site administrator in order to link information transmitted through a network with a DB installed on a server; An information exchange client / server system including a server having a DB linking unit for performing DB operations according to a form designated by a site administrator regardless of the type of DB installed on the server. The method of claim 1, The server side message execution unit, A PITP utility for encoding or decoding a message, a result value management unit for storing a result value of the operation performed by the command processing unit, and a result code management unit for managing result code of the operation performed by the command processing unit , And said client encodes or decodes the message in a client-side message analyzer. The method of claim 2, The client, A command manager for analyzing a meaning of a command transmitted from the client-side message analyzer and providing a command for performing a task transferred from the client-side message analyzer; A data manager for managing data transmitted from the client-side message analyzer; And a data confirmation unit for confirming whether the data transmitted from the data management unit meets the condition value transmitted from the data management unit. The method of claim 3, wherein The client further includes a client-side encryption module for encrypting or decrypting the message, The server further comprises a server-side encryption module for encrypting or decrypting the message. The method of claim 4, wherein The client-side encryption module and the server-side encryption module encrypt an encoded message. The method of claim 4, wherein The server side network management unit, And a socket server for receiving a network connection of the client, and a socket thread for transmitting and receiving data while maintaining a connection with the client. The method of claim 6, The server further includes an administrator program for changing setting information related to server setting by a site administrator, and an environment setting management unit for applying the setting information to message transmission and reception. According to claim 7, The setting information includes information related to the DB type and network connection. The method of claim 8, The server further comprises a condition generating unit for determining the integrity of the data. The method of claim 9, And the client further comprises a web browser interworking unit for sending predetermined parameters to the client-side message analyzing unit in response to a web browser call command. The method according to claim 3 or 4, And the client further comprises a data transmission section for storing the message in or reading from the storage location and providing information about the storage location. The method of claim 11, And the storage location is a local repository. The method of claim 11, And at least two servers, and the storage location is at least one DB of the servers. A client / server system comprising a storage location where personal information is stored, a client providing personal information, and a server for requesting necessary personal information. Requesting personal information required by a client storing personal information in the storage location; And Receiving personal information required from a client extracting personal information from a storage location through a network; Information exchange method comprising the step of reprocessing the personal information provided through the network in accordance with the form used in the DB The method of claim 14, The reprocessing step, Reading the form information used in the DB and changing the personal information received from the client according to the form information, and performing the process of directly interworking with the DB of the changed personal information; Information exchange method characterized in that. The method of claim 15, The client collects the command and data corresponding to the requested operation, provides a message, analyzes the personal information transmitted from the client, classifies the command into data, and performs the operation corresponding to the analyzed command. Information exchange method comprising a. The method of claim 16, Decoding the encoded message sent from the client. The method of claim 17, And decrypting the encrypted message in the client. The method of claim 18, The information providing step, Accepting a network connection of the client; Creating a thread to maintain a connection with the client and to send and receive data. The method of claim 19, The thread creation step includes applying information related to a network connection, The reprocessing step includes the step of applying information about the data format. The method of claim 20, Information processing method, characterized in that the processing in connection with the DB is a member subscription. The method of claim 21, Information processing method characterized in that the operation of processing with the DB is a login. A client / server system comprising a storage location where personal information is stored, a client providing personal information, and a server for requesting necessary personal information. Means for requesting personal information needed by a client storing personal information at the storage location; Means for receiving the personal information required from the client which has extracted the personal information from the storage location through the network; And means for reprocessing personal information provided through a network in a form used in a DB. The method of claim 23, wherein Means for reprocessing the information; Means for reading the form information used in the DB and changing the personal information received from the client according to the form information, and means for performing the operation of directly processing the changed personal information with the DB during the operation. Computer-readable recording media that record programs that can be executed, including. The method of claim 24, The client collects the command and data corresponding to the requested operation and provides a message, and analyzes the personal information transmitted from the client to divide the command and data, and means for performing the operation corresponding to the analyzed command A computer-readable recording medium that records a program that can be executed by including more. The method of claim 25, And a computer-readable recording medium having recorded thereon a program for executing the means for decoding the encoded message sent from the client. The method of claim 26, And a computer-readable recording medium having recorded thereon a program for executing means for decrypting an encrypted message sent from the client. The method of claim 27, The information providing means, And means for accepting the client's network connection, and means for creating a thread for maintaining a connection with the client and for transmitting and receiving data. The method of claim 28, The thread creation means comprises means for applying information relating to a network connection, And said reprocessing means comprises means for applying information relating to a data format. Regardless of the type of DB, to perform DB operation according to the specified form, It includes a name area and a content area where you can input, output, and search. And the name area and the content area are paired with each other to be input, output, and stored.