Method for tokenizing personal information through depersonalization and requesting and authorizing tokenized personal information, and system therefor

Abstract

Provided are: a personal information management method for storing and managing personal information by depersonalizing same, thereby enhancing the security of the personal information; and a system therefor. The personal information management method, according to one embodiment of the present disclosure, may comprise the steps of: acquiring a plurality of pieces of personal information associated with a specific data identifier, wherein the plurality of pieces of personal information are distinguished according to category; acquiring a plurality of pieces of depersonalized information by tokenizing the pieces of personal information or retrieving tokenized pieces of personal information corresponding to the pieces of personal information from respective mapping tables of the categories, wherein the tokenized pieces of personal information are separately stored in the respective mapping tables of the categories; and generating a plurality of data tokens associated with the specific data identifier by processing the plurality of pieces of depersonalized information.

Description

Method and system for tokenization through depersonalization of personal information and requesting and authorizing tokenized personal information.

[0001] The present disclosure relates to a method and system for tokenizing personal information through depersonalization and requesting and authorizing tokenized personal information. More specifically, the present disclosure relates to a personal information management method and system for enhancing the security of personal information by depersonalizing and storing it.

[0002] As the importance of personal information security increases, companies are making efforts to prevent personal information leaks by utilizing various methods, such as physically separating personal information storage from other information storage, encrypting personal information, or tokenizing it.

[0003] Regardless of the method used, the original data of the personal information (e.g., clear text) must be stored somewhere. However, according to conventional technology, multiple pieces of personal information, such as names, phone numbers, and addresses, are stored in a linked manner. In this case, if the storage of the original data is hacked and the original data regarding a specific piece of personal information (e.g., name) becomes accessible, the original data regarding other personal information related to it (e.g., phone numbers, addresses, etc. of a user with that name) also becomes accessible. Therefore, there was a problem in that it was impossible to prevent personal information leakage in the event that the storage of the original data was hacked.

[0004] The technical problem to be solved through some embodiments of the present disclosure is to provide a method for storing and managing personal information in a de-personalized manner and a system to which the method is applied.

[0005] Another technical problem to be solved through some embodiments of the present disclosure is to provide a method and a system to which the method is applied, which generates a data token for personal information using de-personalized information and supports access to the personal information based on the generated data token.

[0006] The technical problems of the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art of the present disclosure from the description below.

[0007] A personal information management method according to one embodiment of the present disclosure for solving the above technical problem may include a step of obtaining a plurality of personal information associated with a specific data identifier, wherein the plurality of personal information are distinguished by category; a step of obtaining a plurality of depersonalized information by tokenizing the personal information or finding tokenized personal information corresponding to the personal information in a category-specific mapping table, wherein the tokenized personal information is separately stored in the category-specific mapping table; and a step of generating a plurality of data tokens associated with the specific data identifier by processing the plurality of depersonalized information.

[0008] In one embodiment, each of the above category-specific mapping tables may be unrelated to each other.

[0009] In one embodiment, the step of obtaining the plurality of de-personalized pieces of information may include a step of handling the tokenized personal information corresponding to the personal information as the de-personalized information if finding the personal information in the category-specific mapping table is successful, and a step of tokenizing the personal information and separately storing the personal information and the tokenized personal information in the category-specific mapping table if finding the personal information in the category-specific mapping table is unsuccessful.

[0010] In one embodiment, the step of generating the plurality of data tokens may include a step of generating the plurality of data tokens such that a first data token, which is a result of processing the first de-personalized information at a first time point, and a second data token, which is a result of processing the first de-personalized information at a second time point, are different from each other. In this case, the step of generating the plurality of data tokens may include a step of generating the plurality of data tokens by adding a random value to each of the plurality of de-personalized information. In addition, the step of generating the plurality of data tokens may further include a step of generating the plurality of data tokens by encrypting the de-personalized information to which the random value has been added.

[0011] In one embodiment, the plurality of data tokens may be stored in association with the specific data identifier.

[0012] In one embodiment, the personal information management method may further include the steps of receiving a request from a personal information consumer to provide a plurality of personal information pieces associated with the specific data identifier, determining whether to approve the request, and providing the plurality of personal information pieces associated with the specific data identifier to the personal information consumer if the request is approved. In this case, the step of determining whether to approve the request may include the steps of determining the validity of a first access token signed by the personal information consumer and a second access token signed by a management entity of the de-personalized information, and approving the request if the signed first access token and the signed second access token are valid. In addition, the signed second access token may be received from the personal information consumer after being signed by the management entity of the de-personalized information.

[0013] A personal information management system according to another embodiment of the present disclosure for solving the above technical problem may include a memory into which a computer program is loaded and a processor for executing the computer program. At this time, the computer program may include instructions for obtaining a plurality of personal information associated with a specific data identifier, wherein the plurality of personal information is distinguished by category, instructions for obtaining a plurality of de-personalized information by tokenizing the personal information or finding tokenized personal information corresponding to the personal information in a category-specific mapping table, wherein the tokenized personal information is separately stored in the category-specific mapping table, and instructions for generating a plurality of data tokens associated with the specific data identifier by processing the plurality of de-personalized information.

[0014] In one embodiment, the instructions for obtaining the plurality of de-personalized pieces of information may include instructions for treating the tokenized personal information corresponding to the personal information as the de-personalized information if finding the personal information in the category-specific mapping table is successful, and instructions for tokenizing the personal information and separately storing the personal information and the tokenized personal information in the category-specific mapping table if finding the personal information in the category-specific mapping table is unsuccessful.

[0015] In one embodiment, the instructions for generating the plurality of data tokens may include instructions for generating the plurality of data tokens such that a first data token, which is a result of processing the first de-personalized information at a first time point, and a second data token, which is a result of processing the first de-personalized information at a second time point, are different from each other.

[0016] In one embodiment, the computer program may further include instructions for receiving a request from a personal information consumer to provide a plurality of pieces of personal information associated with the specific data identifier, instructions for determining whether to approve the request, and instructions for providing the plurality of pieces of personal information associated with the specific data identifier to the personal information consumer if the request is approved. In this case, the instructions for determining whether to approve the request may include instructions for determining the validity of a first access token signed by the personal information consumer and a second access token signed by a management entity of the de-personalized information, and instructions for approving the request if the signed first access token and the signed second access token are valid.

[0017] Figure 1 is a configuration diagram of the entire system according to one embodiment of the present disclosure.

[0018] FIG. 2 is a flowchart of a personal information management method according to one embodiment of the present disclosure.

[0019] FIG. 3 and FIG. 4 are diagrams exemplarily showing a process in which personal information is processed according to one embodiment of the present disclosure.

[0020] FIG. 5 and FIG. 6 are flowcharts illustrating some processes of a personal information management method according to one embodiment of the present disclosure.

[0021] FIG. 7 is a diagram exemplarily showing a process for obtaining personal information according to one embodiment of the present disclosure.

[0022] FIG. 8 is a hardware configuration diagram of a computing system described in some embodiments of the present disclosure.

[0023] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the attached drawings. The advantages and features of the present invention, and methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the attached drawings. However, the technical spirit of the present invention is not limited to the following embodiments, but can be implemented in various different forms. The following embodiments are provided only to complete the technical spirit of the present invention and to fully inform those skilled in the art of the present invention of the scope of the present invention, and the technical spirit of the present invention is defined only by the scope of the claims.

[0024] In describing various embodiments of the present disclosure, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present invention, the detailed description will be omitted.

[0025] Unless otherwise defined, the terms (including technical and scientific terms) used in the following examples may be used with meanings commonly understood by those of ordinary skill in the art to which this disclosure pertains; however, this may vary depending on the intentions of engineers working in the relevant field, precedents, the emergence of new technologies, etc. The terminology used in this disclosure is for the purpose of describing the embodiments and is not intended to limit the scope of this disclosure.

[0026] In the following examples, singular expressions include plural concepts unless the context clearly specifies that they are singular. Furthermore, plural expressions include singular concepts unless the context clearly specifies that they are plural.

[0027] In addition, terms such as first, second, A, B, (a), (b), etc. used in the following embodiments are only used to distinguish certain components from other components, and the nature, order, or sequence of the components are not limited by the terms.

[0028] Hereinafter, various embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0029] Figure 1 is a configuration diagram of the entire system according to one embodiment of the present disclosure.

[0030] Hereinafter, the configuration and operation of the entire system according to one embodiment of the present disclosure will be described with reference to FIG. 1. As illustrated in FIG. 1, the entire system according to the present embodiment may be configured to include a personal information management system (10), and in some embodiments, may further include at least some of a data token management server (20) and a personal information consumer (30).

[0031] Meanwhile, although in FIG. 1, for convenience of explanation, the personal information management system (10) is illustrated as being separate from the data token management server (20) and the personal information consumer (30), it is obvious to those skilled in the art that at least a part of the configuration and / or function of the personal information management system (10) may be implemented within the data token management server (20) and / or the personal information consumer (30). Similarly, at least a part of the configuration and / or function of the data token management server (20) may be implemented within the personal information management system (10) and / or the personal information consumer (30), or at least a part of the configuration and / or function of the personal information consumer (30) may be implemented within the personal information management system (10) and / or the data token management server (20). The personal information management system (10) may also be configured using one or more physical servers included in a server farm based on cloud technology such as a virtual machine.

[0032] The de-personalized personal information manager (100) can acquire multiple pieces of personal information associated with a specific data identifier. The multiple pieces of personal information may be categorized. For example, the multiple pieces of personal information may refer to three pieces of personal information: "Lee Bo-an" in the name category, "Songpa-daero 343" in the address category, and "010-1234-5678" in the phone number category.

[0033] A data identifier can refer to information that identifies the data associated with personal information entered when that information is entered. For example, if a user enters personal information as orderer information when ordering a product through a website or app, the identifier for that order (e.g., "order_id") can serve as this data identifier. In another example, if a user enters personal information as recipient information when ordering a product through a website or app, the identifier for that delivery (e.g., "delivery_id") can serve as this data identifier.

[0034] Additionally, the depersonalized personal information manager (100) can acquire multiple depersonalized pieces of information by tokenizing the personal information or searching for tokenized personal information corresponding to the personal information in a category-specific mapping table. At this time, the tokenized personal information may be stored separately in the category-specific mapping table. Furthermore, the depersonalized personal information manager (100) can generate multiple data tokens associated with specific data identifiers by processing the multiple depersonalized pieces of information. A detailed description of the acquisition of depersonalized information and the generation of data tokens will be provided below.

[0035] The depersonalized information database (11) can store and / or manage a category-specific mapping table that stores personal information and tokenized personal information.

[0036] The request authorization device (12) can receive a request from a personal information consumer (30) to provide personal information associated with a specific data identifier and determine whether to grant authorization. If the request for personal information is approved, the personal information associated with the specific data identifier can be provided to the personal information consumer (30).

[0037] A "personal information consumer" (30) may refer to an entity requesting the provision of personal information associated with a specific data identifier. For example, personal information may be requested when searching for information related to a specific data identifier (e.g., order information, delivery information, etc. containing personal information) or when collecting information for statistical analysis purposes.

[0038] In some embodiments, a web or app running on a user terminal (not shown) may correspond to such a personal information consumer (30). In other embodiments, a front-end server, gateway, client application, etc. connected to the web or app through a session, etc. may correspond to such a personal information consumer (30).

[0039] Meanwhile, the present disclosure mainly describes an embodiment in which a request for provision of personal information by a personal information consumer (30) is transmitted to a personal information management system (10) through a data token management server (20), but in some cases, a personal information consumer (30) may directly request provision of personal information to the personal information management system (10).

[0040] The data token management server (20) can manage a data token database (21) that stores data tokens associated with specific data identifiers. In addition, the data token management server (20) can transmit personal information regarding a specific data identifier input from a personal information consumer (30) to the personal information management system (10), thereby allowing the personal information to be tokenized by the de-personalized personal information manager (100).

[0041] The personal information management system (10), the data token management server (20), and the personal information consumer (30) can communicate with each other via a communication network (not shown). The communication network can be implemented as any type of wired / wireless network, such as a local area network (LAN), a wide area network (WAN), a mobile radio communication network, or Wibro (Wireless Broadband Internet).

[0042] The personal information management system (10) may be configured to include the above-described de-personalized information manager (100), de-personalized information database (11), and request authorizer (12), and each of the de-personalized information manager (100), de-personalized information database (11), and request authorizer (12) may be implemented as an independent computing system, or at least some of the de-personalized information manager (100), de-personalized information database (11), and request authorizer (12) may be implemented together through one computing system.

[0043] The configuration and operation of the entire system according to the present embodiment have been described above. In particular, the operation of the depersonalized information manager (100) will be understood in more detail through the embodiments described below. In other words, the operation of the depersonalized information manager (100) can be supplemented through the embodiments described below.

[0044] Next, a personal information management method according to one embodiment of the present disclosure will be described with reference to FIGS. 2 through 7. The personal information management method according to this embodiment may be performed by one or more computing systems. Furthermore, some operations of the personal information management method according to this embodiment may be performed by a first computing system, while the remaining operations may be performed by a second computing system.

[0045] For example, some operations of the personal information management method according to the present embodiment may be performed by an on-premise physical server, while the remaining operations may be performed by a cloud server. Hereinafter, if the entity performing each operation is omitted, it will be understood that the entity performing the operation is the computing system.

[0046] First, a personal information management method according to this embodiment is outlined with reference to Figure 2. Details of each step may be provided later, as needed. Multiple pieces of personal information associated with a specific data identifier are acquired (S100). As described above, the multiple pieces of personal information may be categorized.

[0047] Next, de-personalized information is obtained by tokenizing the personal information or finding tokenized personal information corresponding to the personal information in a category-specific mapping table (S200). As described above, the tokenized personal information may be stored separately in the category-specific mapping table.

[0048] FIG. 3 is a diagram illustrating a category-specific mapping table according to some embodiments of the present disclosure. A more detailed description will be provided with reference to FIG. 3.

[0049] The category-specific mapping tables (310, 320, and 330) may define correspondences between personal information (312, 322, and 332) and tokenized personal information (311, 321, and 331). For example, in the name category mapping table (310), the personal information "Lee Bo-an" corresponds to "oiiuy87wead," and "oiiuy87wead" corresponds to the tokenized value of "Lee Bo-an," i.e., the tokenized personal information. There is no mathematical relationship between the personal information and its tokenized value, and therefore, personal information cannot be derived from the tokenized personal information without referring to the category-specific mapping table.

[0050] In some embodiments, when obtaining de-personalized information (S200), if personal information (312, 322, and 332) is successfully found in the category-specific mapping table (310, 320, and 330), tokenized personal information (311, 321, and 331) corresponding to the personal information (312, 322, and 332) may be treated (or obtained) as de-personalized information. This may be the case when values ​​corresponding to personal information (312, 322, and 332) are already stored in the category-specific mapping table (310, 320, and 330).

[0051] And, if finding personal information in the category-specific mapping tables (310, 320, and 330) fails, the personal information can be tokenized, and the tokenized result, i.e., the tokenized personal information, can be obtained as de-personalized information. Here, the personal information and the corresponding tokenized personal information can be separately stored in the category-specific mapping tables (310, 320, and 330). In this case, it may be the case that the value corresponding to the personal information is not stored in the category-specific mapping tables (310, 320, and 330), so new data must be separately stored in the category-specific mapping tables (310, 320, and 330).

[0052] For example, assuming that the personal information "Lee Bo-an" is not stored in the mapping table (310) of the name category, the de-personalized personal information manager (100) can tokenize "Lee Bo-an", separately store "Lee Bo-an" and its tokenized value "oiiuy87wead" in the mapping table (310) of the name category, and obtain the tokenized personal information "oiiuy87wead" as de-personalized information.

[0053] Referring to FIG. 3, if a plurality of personal information associated with a specific data identifier is “iBoAn”, “Songpa-daero 343”, and “010-1234-5678”, the plurality of de-personalized information acquired through step S200 according to the above-described embodiment may be “oiiuy87wead”, “09klj3nlajsdf”, and “oiquowienzs”, respectively.

[0054] Meanwhile, storing personal information (312, 322, and 332) and tokenized personal information (311, 321, and 331) separately in category-specific mapping tables (310, 320, and 330) may mean that each of the category-specific mapping tables (310, 320, and 330) is unrelated to each other.

[0055] To be more specific, the data of each of the mapping table (310) of the name category, the mapping table (320) of the phone number category, and the mapping table (330) of the address category may be stored separately without any relation to each other.

[0056] For example, if multiple personal information associated with a specific data identifier are "Lee Bo-an," "Songpa-daero 343," and "010-1234-5678," and each piece of personal information is stored in association (e.g., multiple pieces of personal information are stored in the same table), then by combining these pieces of personal information, it is possible to identify a specific individual named "Lee Bo-an" whose address is "Songpa-daero 343" and whose phone number is "010-1234-5678." However, if personal information and its tokenized values ​​are stored separately in category-specific mapping tables (310, 320, and 330) as in this embodiment, the association between the personal information pieces disappears. Therefore, it is not possible to know that "Lee Bo-an"'s phone number is "010-1234-5678" or that his address is "Songpa-daero 343" by only referencing the category-specific mapping tables (310, 320, and 330).

[0057] This means that when personal information (312, 322, and 332) is stored separately in the category-specific mapping tables (310, 320, and 330), the nature of the personal information, i.e., the property of being able to identify a specific individual on its own or in combination with other information, disappears. By doing so, even if the de-personalized information database (11; or personal information management system (10)) that stores and / or manages the category-specific mapping tables (310, 320, and 330) is hacked, personal information can be prevented from being leaked.

[0058] Referring again to FIG. 2, multiple data tokens associated with specific data identifiers are generated by processing the multiple de-personalized information acquired as described above (S300). The multiple data tokens thus generated can be stored in a data token database (21) in association with the specific data identifiers.

[0059] FIG. 4 is a diagram exemplarily showing data (400) stored in a data token database (21) according to some embodiments of the present disclosure. This will be described in more detail with reference to FIG. 4.

[0060] A plurality of data tokens generated by processing a plurality of de-personalized pieces of information may be stored in association with a data identifier (410). For example, if the plurality of de-personalized pieces of information are "oiiuy87wead", "09klj3nlajsdf", and "oiquowienzs", the plurality of data tokens (420) generated by processing them may be "oiiuy87wead-oiw", "09klj3nlajsdf-oiiu", and "oiquowienzs-928", respectively. In this case, the plurality of data tokens (420) may be stored in association with the data identifier "ixjw3ix89w3".

[0061] In some embodiments, data tokens may be generated such that the first data token, which is the result of processing the first de-personalized information at a first time point, and the second data token, which is the result of processing the first de-personalized information at a second time point, are different from each other. That is, the de-personalized information obtained by processing personal information of a specific value through steps S100 and S200 described above may always have the same value regardless of the time of acquisition, but the data token generated by processing the de-personalized information may differ depending on the time of generation. By doing so, the security of personal information can be enhanced.

[0062] For example, even if the de-personalized information obtained by processing personal information called “iBoAn” through the above-described steps S100 and S200 always has the value “oiiuy87wead” regardless of the time of acquisition, the first data token generated by processing “oiiuy87wead” at the first time point and the second data token generated by processing the same “oiiuy87wead” at the second time point may have different values.

[0063] Referring further to Figure 5, in some embodiments, a data token (420) can be generated by adding a random value to de-personalized information to achieve this result (S310). The random value varies depending on the time of its creation (or addition), and may be, for example, a salt.

[0064] Furthermore, in some embodiments, a data token can be generated by encrypting de-personalized information (420) with a random value added as described above (S320). The encryption method may, for example, follow a symmetric key encryption method, but is not limited thereto, and various methods may be used within the scope that can achieve the purpose of the present disclosure. When following a symmetric key encryption method, the personal information management system (10) and the data token management server (20) may share a key used for encryption / decryption.

[0065] According to the personal information management method described in detail above, in order for a hacker to steal personal information, (i) he must hack the data token management server (20) to find out the data token, (ii) he must also find out the method of generating the data token to derive de-personalized information from the data token, and (iii) he must hack the personal information management system (10) to find out the personal information corresponding to the de-personalized information. In other words, if even one of the conditions (i) to (iii) above is lacking, personal information cannot be leaked, so the security of personal information is greatly enhanced.

[0066] Hereinafter, a process in which a personal information consumer (30) accesses personal information based on a data token generated (S300) according to some embodiments of the present disclosure is described with reference to FIGS. 6 and 7.

[0067] A personal information consumer requests the provision of multiple pieces of personal information associated with a specific data identifier (S400). At this time, the personal information consumer (30), for example, a web / app running on a user terminal, a front-end server, etc., may transmit a specific data identifier (e.g., delivery_id "ixjw3ix89w3" in FIG. 4) and information about a specific user with access to the corresponding personal information to the data token management server (20) (S410). Hereinafter, this information about a specific user is referred to as a user context. The user context can be acquired based on a first access token signed by the personal information consumer (30).

[0068] The data token management server (20) may request a second access token from the personal information management system (10) after verifying access rights to personal information using a specific data identifier and user context (S420). At this time, the data token management server (20) may transmit a specific data identifier (e.g., delivery_id "ixjw3ix89w3" of FIG. 4), a user context, and a plurality of data tokens (e.g., 420 of FIG. 4) associated with the specific data identifier to the personal information management system (10).

[0069] The personal information management system (10) signs the second access token and transmits the signed second access token to the data token management server (20) (S510). At this time, the signed second access token may include a specific data identifier (e.g., delivery_id "ixjw3ix89w3" in FIG. 4), a user context, a plurality of data tokens (e.g., 420 in FIG. 4) associated with the specific data identifier, information regarding the expiration time of the signed second access token, and information regarding the signature by the personal information management system (10). In addition, the data token management server (20) may transmit the signed second access token received in this manner to the personal information consumer (30) (S520).

[0070] A personal information consumer (30) can transmit a first access token signed by the personal information consumer (30) and a second access token signed by the personal information management system (10), which is the management entity of de-personalized information, to the personal information management system (10).

[0071] The personal information management system (10), specifically the request authorization unit (12), can determine the validity of the signed first access token and the signed second access token as described above, and if they are valid, can authorize the request for provision of personal information (S600). In some embodiments, it can further verify whether the user context acquired based on the first access token matches the user context included in the second access token, and if so, can authorize the request for provision of personal information. By doing so, it is possible to check whether the first access token and the second access token have been tampered with.

[0072] And, when the request is authorized as above (S600), the request authorization device (12) can provide a plurality of personal information (e.g., “Lee Bo-an”, “Songpa-daero 343”, “010-1234-5678”) associated with a specific data identifier (e.g., delivery_id “ixjw3ix89w3” in FIG. 4) to the personal information consumer (30). Here, the plurality of personal information provided to the personal information consumer (30) may be clear text or masked data, but is not limited thereto.

[0073] In some embodiments, in order to provide multiple pieces of personal information (e.g., “Lee Bo-an”, “Songpa-daero 343”, “010-1234-5678”) as described above, de-personalized information (e.g., “oiiuy87wead”, “09klj3nlajsdf”, “oiquowienzs”) can be obtained by decrypting multiple data tokens (e.g., 420 in FIG. 4) associated with specific data identifiers (e.g., delivery_id “ixjw3ix89w3” in FIG. 4) included in the second access token or removing random values ​​added to the data tokens (or decrypted data tokens). In addition, by referring to the category-specific mapping table (310, 320 and 330 of FIG. 3), a plurality of pieces of personal information (e.g., “Lee Bo-an”, “Songpa-daero 343”, “010-1234-5678”) corresponding to each of these de-personalized pieces of information can be provided to the personal information consumer (30).

[0074] FIG. 8 is an exemplary hardware configuration diagram illustrating a computing system (1000) according to some embodiments of the present disclosure.

[0075] As illustrated in FIG. 8, the computing system (1000) of FIG. 8 may include one or more processors (1100), a system bus (1600), a communication interface (1200), a memory (1400) for loading a computer program (1500) executed by the processor (1100), and a storage (1300) for storing the computer program (1500). However, only components related to the embodiment of the present disclosure are illustrated in FIG. 8. Therefore, a person skilled in the art to which the present disclosure pertains will appreciate that other general components may be included in addition to the components illustrated in FIG. 8. That is, the computing system (1000) may further include various components in addition to the components illustrated in FIG. 8. Furthermore, in some cases, the computing system (1000) may be configured in a form in which some of the components illustrated in FIG. 8 are omitted. Hereinafter, each component of the computing system (1000) will be described.

[0076] The processor (1100) can control the overall operation of each component of the computing system (1000). The processor (1100) can be configured to include at least one of a Central Processing Unit (CPU), a Micro Processor Unit (MPU), a Micro Controller Unit (MCU), a Graphic Processing Unit (GPU), a Neural Processing Unit (NPU), or any other type of processor well known in the technical field of the present disclosure. In addition, the processor (1100) can perform operations for at least one application or program for executing operations / methods according to various embodiments of the present disclosure. The computing system (1000) can include one or more processors.

[0077] Next, the memory (1400) can store various data, commands, and / or information. The memory (1400) can load a computer program (1500) from the storage (1300) to execute methods / operations according to various embodiments of the present disclosure. The memory (1400) may be implemented as a volatile memory such as RAM, but the technical scope of the present disclosure is not limited thereto.

[0078] Next, the system bus (1600) can provide communication functions between components of the computing system (1000). The system bus (1600) can be implemented as various types of buses, such as an address bus, a data bus, and a control bus.

[0079] Next, the communication interface (1200) can support wired and wireless Internet communication of the computing system (1000). Furthermore, the communication interface (1200) can also support various communication methods other than Internet communication. To this end, the communication interface (1200) can be configured to include a communication module well known in the technical field of the present disclosure.

[0080] Next, the storage (1300) can non-temporarily store one or more computer programs (1500). The storage (1300) can be configured to include non-volatile memory such as flash memory, a hard disk, a removable disk, or any form of computer-readable recording medium well known in the art to which the present disclosure pertains.

[0081] Next, the computer program (1500) may include one or more instructions that cause the processor (1100) to perform operations / methods according to various embodiments of the present disclosure when loaded into the memory (1400). That is, when the computer program (1500) is loaded into the memory (1400), the processor (1100) may execute the one or more instructions, thereby performing the methods / operations according to various embodiments of the present disclosure.

[0082] In some embodiments, the computer program (1500) may include instructions for obtaining a plurality of personal information associated with a particular data identifier, wherein the plurality of personal information is distinguished by category; instructions for obtaining a plurality of de-personalized information by tokenizing the personal information or finding tokenized personal information corresponding to the personal information in a category-specific mapping table, wherein the tokenized personal information is separately stored in the category-specific mapping table; and instructions for generating a plurality of data tokens associated with the particular data identifier by processing the plurality of de-personalized information.

[0083] In one embodiment, the instructions for obtaining the plurality of de-personalized pieces of information may include instructions for treating the tokenized personal information corresponding to the personal information as the de-personalized information if finding the personal information in the category-specific mapping table is successful, and instructions for tokenizing the personal information and separately storing the personal information and the tokenized personal information in the category-specific mapping table if finding the personal information in the category-specific mapping table is unsuccessful.

[0084] In one embodiment, the instructions for generating the plurality of data tokens may include instructions for generating the plurality of data tokens such that a first data token, which is a result of processing the first de-personalized information at a first time point, and a second data token, which is a result of processing the first de-personalized information at a second time point, are different from each other.

[0085] In one embodiment, the computer program (1500) may further include instructions for receiving a request from a personal information consumer for provision of a plurality of pieces of personal information associated with the specific data identifier, instructions for determining whether to approve the request, and instructions for providing the plurality of pieces of personal information associated with the specific data identifier to the personal information consumer if the request is approved. In this case, the instructions for determining whether to approve the request may include instructions for determining the validity of a first access token signed by the personal information consumer and a second access token signed by a management entity of the de-personalized information, and instructions for approving the request if the signed first access token and the signed second access token are valid.

[0086] Meanwhile, in some embodiments, the computing system (1000) illustrated in FIG. 8 may refer to a virtual machine implemented based on cloud technology. For example, the computing system (1000) may be a virtual machine operating on one or more physical servers included in a server farm. In this case, at least some of the processor (1100), memory (1400), and storage (1300) illustrated in FIG. 8 may be virtual hardware, and the communication interface (1200) may also be implemented as a virtualized networking element, such as a virtual switch.

[0087] So far, with reference to FIG. 8, an exemplary computing system (1000) capable of implementing a personal information management system (10) according to some embodiments of the present disclosure has been described.

[0088] Various embodiments of the present disclosure and effects according to the embodiments have been described with reference to FIGS. 1 through 8. The effects according to the technical concept of the present disclosure are not limited to the effects described above, and other effects not mentioned will be clearly understood by those skilled in the art from the above description.

[0089] Furthermore, even though the above embodiments have described multiple components as being combined or operating in combination, the technical concept of the present disclosure is not necessarily limited to these embodiments. That is, within the scope of the technical concept of the present disclosure, all of the components may be selectively combined and operated one or more times.

[0090] The technical concepts of the present disclosure described so far can be implemented as computer-readable code on a computer-readable medium. A computer program recorded on a computer-readable recording medium can be transmitted to another computing system via a network such as the Internet, installed on said other computing system, and thus used on said other computing system.

[0091] Although the operations are depicted in a particular order in the drawings, this should not be construed as requiring that the operations be performed in the particular order depicted, or in any sequential order, or that all depicted operations must be performed to achieve the desired results. In certain situations, multitasking and parallel processing may be advantageous.

[0092] Although various embodiments of the present disclosure have been described with reference to the attached drawings, those skilled in the art will appreciate that the technical concepts of the present disclosure can be implemented in other specific forms without changing the technical concepts or essential features thereof. Therefore, it should be understood that the embodiments described above are exemplary in all respects and not restrictive. The scope of protection of the present disclosure should be interpreted by the claims below, and all technical concepts within a scope equivalent thereto should be interpreted as being included within the scope of the technical concepts defined by the present disclosure.

Claims

1. In a method performed by a computing system, A step of obtaining a plurality of personal information associated with a specific data identifier, wherein the plurality of personal information are distinguished according to categories; A step of obtaining a plurality of depersonalized pieces of information by tokenizing the personal information or finding tokenized personal information corresponding to the personal information in a category-specific mapping table, wherein the tokenized personal information is stored separately in the category-specific mapping table; and A step of generating a plurality of data tokens associated with the specific data identifier by processing the plurality of de-personalized information, How to manage your personal information.

2. In paragraph 1, Each of the above category-specific mapping tables is unrelated to each other. How to manage your personal information.

3. In paragraph 1, The step of obtaining the above multiple de-personalized information is: If the personal information is successfully found in the above category-specific mapping table, a step of treating the tokenized personal information corresponding to the personal information as the de-personalized information; and If finding the personal information in the above category-specific mapping table fails, the step of tokenizing the personal information and separately storing the personal information and the tokenized personal information in the above category-specific mapping table is included. How to manage your personal information.

4. In paragraph 1, The step of generating the above multiple data tokens is: A step of generating the plurality of data tokens such that the first data token, which is a result of processing the first de-personalized information at a first time point, and the second data token, which is a result of processing the first de-personalized information at a second time point, are different from each other, How to manage your personal information.

5. In paragraph 4, The step of generating the above multiple data tokens is: A step of generating the plurality of data tokens by adding a random value to each of the plurality of de-personalized pieces of information, How to manage your personal information.

6. In paragraph 5, The step of generating the above multiple data tokens is: Further comprising a step of generating the plurality of data tokens by encrypting the de-personalized information to which the random value is added. How to manage your personal information.

7. In paragraph 1, The above plurality of data tokens are stored in association with the specific data identifier, How to manage your personal information.

8. In paragraph 1, A step of requesting provision of multiple pieces of personal information associated with the specific data identifier from a personal information consumer; a step of determining whether to approve the above request; and If the request is approved, further comprising the step of providing the personal information consumer with a plurality of pieces of personal information associated with the specific data identifier. How to manage your personal information.

9. In paragraph 8, The step of determining whether to approve the above request is: A step of determining the validity of a first access token signed by the personal information consumer and a second access token signed by the management entity of the de-personalized information; and comprising a step of authorizing the request if the signed first access token and the signed second access token are valid; How to manage your personal information.

10. In paragraph 9, The above signed second access token is received from the personal information consumer after being signed by the management entity of the de-personalized information. How to manage your personal information.

11. Communication interface; Memory into which computer programs are loaded; and Including a processor for executing the above computer program, The above computer program, Instructions for obtaining a plurality of pieces of personal information associated with a specific data identifier, wherein the plurality of pieces of personal information are distinguished by category; Instructions for obtaining a plurality of de-personalized pieces of information by tokenizing the personal information or finding tokenized personal information corresponding to the personal information in a category-specific mapping table, wherein the tokenized personal information is stored separately in the category-specific mapping table; and Including instructions for generating a plurality of data tokens associated with the specific data identifier by processing the plurality of de-personalized information. Personal information management system.

12. In paragraph 11, The instructions for obtaining the above multiple de-personalized information are: Instructions for handling the tokenized personal information corresponding to the personal information as the de-personalized information when the personal information is successfully found in the above category-specific mapping table; and If finding the personal information in the category-specific mapping table fails, instructions for tokenizing the personal information and separately storing the personal information and the tokenized personal information in the category-specific mapping table are included. Personal information management system.

13. In paragraph 11, The instructions for generating the above multiple data tokens are: Including instructions for generating the plurality of data tokens such that the first data token, which is a result of processing the first de-personalized information at the first time point, and the second data token, which is a result of processing the first de-personalized information at the second time point, are different from each other. Personal information management system.

14. In paragraph 11, Instructions requesting the provision of multiple pieces of personal information associated with said specific data identifier from a personal information consumer; Instructions for determining whether to grant the above request; and Further comprising instructions for providing a plurality of pieces of personal information associated with the specific data identifier to the personal information consumer when the request is approved. Personal information management system.

15. In paragraph 14, Instructions that determine whether to grant the above request are: Instructions for determining the validity of a first access token signed by the personal information consumer and a second access token signed by the management entity of the de-personalized information; and Including instructions for authorizing the request if the signed first access token and the signed second access token are valid. Personal information management system.

Images