Method and device for generating relational id based on distributed identifiers

Abstract

To provide a relational ID generation method and a relational ID generation device, by which a relationship between pre-registered users is proved using distributed identifiers.SOLUTION: A relational ID generation method includes: a step of a service provider to receive a membership request including relational user membership request statement information from a terminal of a first user; a step of verifying a relationship between the first user and a second user; a step of generating a relational ID including relationship information between the first user and the second user; and a step of the first user to request, via the service provider, the second user for task execution using the relational ID, and the second user to receive the request of the task execution based on the relational ID.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a technology for generating a relational user ID that can prove a relationship among pre-registered users using a Decentralized Identifier (DID).

[0002] Furthermore, the present invention relates to a technology in which a related person (family member) intervenes to safely support procedures such as membership registration, password reset, and service operation support for users (the elderly) with a low digital power level using a relational user ID.

Background Art

[0003] The development of digital technology and the COVID-19 pandemic have accelerated the digitalization of daily life, and it has become clear that the elderly with a low digital power level rather feel inconvenience. According to the "2022 Digital Information Gap Report" released by the South Korean government, the group with the lowest digital power level is the elderly, which continues to decline from the 20s (127.2%) to over 70s (55.6%), and the digital information level of those over 70s is more than twice lower than that of the 20s. Also, according to an analysis of the digital device usage power level for those aged 65 and above in Gyeonggi-do, the usage power of character sending and receiving (81.1%) is the highest, and there are many difficulties in using services such as finance (14.4%) and shopping (9.4%) that require user membership registration and login procedures.

[0004] User membership registration and login procedures refer to the act of registering and proving oneself to the system. Login procedures are very diverse, ranging from the basic ID / password method to social login and biometric authentication methods, and the terms and authentication procedures used are also different. It is inevitable that it is difficult for the elderly with a low digital power level to handle such user registration and login procedures.

[0005] Therefore, it is frequent that mainly family members and acquaintances around assist in the membership and user login procedures for using online services in a face-to-face manner, and privacy issues such as the exposure and theft of personal information occur during this process. Also, when the user's login information is initialized due to device changes or device updates, etc., the user cannot use the online service and may experience psychological problems such as stress of having to receive help from people around again and a decrease in self-esteem during that process.

[0006] The present invention provides a relational user ID generation method and utilization strategy that can prove the relationship between pre-registered users using a decentralized identifier.

Prior Art Documents

Patent Documents

[0007]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0008] An object of the present invention is to generate a relational user ID that can prove the relationship between pre-registered users using a decentralized identifier.

[0009] Also, an object of the present invention is to provide a service that supports the digital operations of users with a low digital power level.

Means for Solving the Problems

[0010] To achieve the above object, a relational ID generation method based on a distributed identifier according to an embodiment of the present invention includes the steps of receiving an invitation to join including relational user invitation text information from a terminal of a first user, verifying the relationship between the first user and the second user, and generating a relational ID including relationship information between the first user and the second user. The first user requests to perform a task using the relational ID, and the second user can receive a task execution request based on the relational ID.

[0011] At this time, the relational user invitation text information can be received by the terminal of the first user from the terminal of the second user.

[0012] At this time, the relational user invitation text information can include the name, gender, date of birth, telecommunications carrier, telephone number, and domestic and foreign personal information of the first user.

[0013] At this time, the step of generating the relational ID can include the steps of authenticating the first user, requesting the terminal of the second user to generate the relational ID of the first user using the public key information of the first user, receiving the personal key signature value of the second user's distributed identifier document and the relational ID of the first user from the terminal of the second user, and storing the generated relational ID document of the first user in the distributed identifier document storage.

[0014] At this time, the controller and capability invocation attribute values of the relational ID document of the first user can correspond to the distributed identifier of the second user.

[0015] At this time, the step of generating the relational ID can further include the step of verifying whether the second user has generated the relational ID of the first user using the public key of the second user's distributed identifier document.

[0016] At this time, the step of generating the relational ID may further include the step of transmitting a membership completion notification message to the terminal of the first user and the terminal of the second user respectively.

[0017] At this time, the method may further include the step of storing the identity information of the first user and the related person information of the second user. The identity information of the first user includes the name, gender, date of birth, communication carrier, phone number and domestic / foreign nationality information of the first user. The related person information of the second user may include the name, phone number of the second user and the relationship information with the first user.

[0018] At this time, if the method receives a business execution request from the terminal of the first user, it can compare the related person information corresponding to the business execution request with the controller information in the relational ID document of the first user.

[0019] At this time, the relational ID document can correspond to a Decentralized Identifier Document.

[0020] In addition, a relational ID generation device based on a decentralized identifier according to an embodiment of the present invention for achieving the above object includes one or more processors and an execution memory for storing at least one or more programs executed by the one or more processors. The at least one or more programs include instructions for receiving a membership request including relational user membership request document information from the terminal of the first user, verifying the relationship between the first user and the second user, and generating a relational ID including the relationship information between the first user and the second user. The first user requests business execution using the relational ID, and the second user can receive a business execution request based on the relational ID.

[0021] At this time, the relational user membership request document information can be received by the terminal of the first user from the terminal of the second user.

[0022] At this time, the relational user membership invitation text information may include the name, gender, date of birth, communication carrier, phone number, and domestic / foreign personal information of the first user.

[0023] At this time, the step of generating the relational ID may include the step of authenticating the first user, the step of requesting the generation of the first user's relational ID on the second user's terminal using the public key information of the first user, the step of receiving the personal key signature value of the second user's decentralized identifier document and the first user's relational ID from the second user's terminal, and the step of storing the generated relational ID document of the first user in the decentralized identifier document storage.

[0024] At this time, the controller and capability invocation attribute values of the relational ID document of the first user may correspond to the decentralized identifier of the second user.

[0025] At this time, the step of generating the relational ID may further include the step of verifying whether the second user has generated the first user's relational ID using the public key of the second user's decentralized identifier document.

[0026] At this time, the step of generating the relational ID may further include the step of transmitting a membership completion notice message to the first user's terminal and the second user's terminal respectively.

[0027] At this time, the program further includes an instruction word for storing the identity information of the first user and the related person information of the second user. The identity information of the first user includes the name, gender, date of birth, communication carrier, phone number, and domestic / foreign personal information of the first user. The related person information of the second user may include the name, phone number of the second user, and the relationship information with the first user.

[0028] At this time, if the program receives a business execution request from the terminal of the first user, it can compare the relevant person information corresponding to the business execution request with the controller information in the relational ID document of the first user.

[0029] At this time, the relational ID document can correspond to a Decentralized Identifier Document.

Advantages of the Invention

[0030] According to the present invention, a relational user ID for proving a relationship between pre-registered users using a decentralized identifier can be generated.

[0031] In addition, the present invention can provide a service for assisting the digital business of users with a low digital power level.

Brief Description of the Drawings

[0032]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Modes for Carrying Out the Invention

[0033] The advantages, features of the present invention, and the methods for achieving them will become clear by referring to the embodiments described in detail below together with the attached drawings. However, the present invention is not limited to the embodiments disclosed below, and can be realized in various different forms. The present embodiments are merely provided to make the disclosure of the present invention complete and to fully inform those with ordinary knowledge in the technical field to which the present invention pertains of the scope of the invention. The present invention is defined only by the scope of the claims. The same reference numerals refer to the same components throughout the specification.

[0034] For example, although terms such as "first" or "second" are used to describe various components, such components are not limited by such terms. Such terms are merely used to distinguish one component from another. Therefore, the first component referred to below may be the second component within the technical idea of the present invention.

[0035] The terms used in this specification are for the purpose of explaining the embodiments and are not intended to limit the present invention. In this specification, the singular form includes the plural form unless otherwise specifically stated in the text. The term "comprises" or "comprising" used in the specification includes the meaning that the recited component or step does not exclude the existence or addition of one or more other components or steps.

[0036] As used herein, terms such as "A or B", "at least one of A and B", "at least one of A or B", "A, B or C", "at least one of A, B and C", and "at least one of A, B, or C" can each include any one of the items listed together with the corresponding term, or all possible combinations thereof.

[0037] Unless otherwise defined, all terms used herein are construed to have a meaning commonly understood by those of ordinary skill in the technical field to which the present invention pertains. Also, terms defined in commonly used dictionaries are not ideally or overly construed unless specifically defined otherwise.

[0038] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. When describing with reference to the drawings, the same or corresponding components are denoted by the same reference numerals, and duplicate descriptions thereof are omitted.

[0039] FIG. 1 is a flowchart showing a relational ID generation method based on a distributed identifier according to an embodiment of the present invention.

[0040] The relational ID generation method based on a distributed identifier according to an embodiment of the present invention is performed by a relational ID generation device based on a distributed identifier such as a computing device or a service provider server.

[0041] Referring to FIG. 1, the relational ID generation method based on a distributed identifier according to an embodiment of the present invention includes a step S110 of receiving an invitation to join including relational user invitation text information from a terminal of a first user, a step S120 of verifying the relationship between the first user and the second user, and a step S130 of generating a relational ID including relationship information between the first user and the second user. The first user requests to perform a task using the relational ID, and the second user can receive a task execution request based on the relational ID.

[0042] At this time, the relational user membership invitation text information can be received by the terminal of the first user from the terminal of the second user.

[0043] At this time, the relational user membership invitation text information can include the name, gender, date of birth, communication carrier, telephone number, and domestic and foreign personal information of the first user.

[0044] At this time, step S130 of generating the relational ID can include the step of performing identity authentication on the first user, the step of requesting the terminal of the second user to generate the relational ID of the first user using the public key information of the first user, the step of receiving the personal key signature value of the second user's decentralized identifier document and the relational ID of the first user from the terminal of the second user, and the step of storing the generated relational ID document of the first user in the decentralized identifier document storage.

[0045] At this time, the controller and capability invocation attribute values of the relational ID document of the first user can correspond to the decentralized identifier of the second user.

[0046] At this time, step S130 of generating the relational ID can further include the step of verifying whether the second user has generated the relational ID of the first user using the public key of the second user's decentralized identifier document.

[0047] At this time, step S130 of generating the relational ID can further include the step of transmitting a membership completion notice message to the terminal of the first user and the terminal of the second user respectively.

[0048] At this time, the method further includes the step of storing the identity information of the first user and the related person information of the second user, where the identity information of the first user includes the name, gender, date of birth, communication carrier, phone number, and domestic and foreign personal information of the first user, and the related person information of the second user can include the name, phone number, and relationship information with the first user.

[0049] At this time, if the method receives a service execution request from the terminal of the first user, it can compare the related person information corresponding to the service execution request with the controller information in the relational ID document of the first user.

[0050] At this time, the relational ID document can correspond to a Decentralized Identifier Document.

[0051] FIG. 2 is a diagram conceptually showing the relational ID generation process according to an embodiment of the present invention.

[0052] Referring to FIG. 2, the relational ID generation according to an embodiment of the present invention is performed in a decentralized identifier document storage, the terminal of the first user (elderly person), the service provider, and the terminal of the second user (related person). Hereinafter, each element in which the relational ID generation according to an embodiment of the present invention is performed will be described in detail.

[0053] The first user (elderly person) is a user with a low digital power level, and can refer to a user who receives support from a related person accepted by the user for complex procedures such as online enrollment, password reset, and service business processing. For example, the first user can correspond to the parent of the second user. Although shown as the first user in FIG. 2, the configuration can correspond to the terminal of the first user such as a computing device.

[0054] The second user (related person) is a user with a high digital power level, and can represent a user who assists procedures such as online membership, password reset, and service business processing for users with a low digital power level. For example, the second user can correspond to the child of the first user. Although shown as the second user in FIG. 2, the configuration can correspond to the terminal of the second user such as a computing device.

[0055] The service provider can register and verify a relationship-based user ID based on a decentralized identifier, and provide services so that users with a low digital power level can receive assistance for safe and convenient user membership, password reset, and service business processing procedures with the help of related persons accepted by the user. For example, the service provider can correspond to a mobile communication operator, etc. Similarly, although shown as the service provider in FIG. 2, the configuration can correspond to the server of the service provider, etc.

[0056] The decentralized identifier storage can represent a storage that stores and manages a Decentralized Identifier Document for service users in a decentralized ledger system (e.g., blockchain) that can be operated together with the service provider or other service providers.

[0057] FIG. 3 is an example of the decentralized identifier document of the first user.

[0058] FIG. 4 is an example of the decentralized identifier document of the second user.

[0059] Referring to FIGS. 3 and 4, the decentralized identifier documents (DID Documents) of the first user and the second user for generating the relationship-based user ID can be confirmed. The data shown in FIGS. 3 and 4 is an example for explaining the present invention, and the scope of the present invention is not limited thereto, and the data can be changed depending on the configuration of the system.

[0060] Hereinafter, with reference to FIGS. 5 to 9, each step of the method for generating and utilizing a relational ID based on a decentralized identifier according to an embodiment of the present invention will be described in detail.

[0061] FIG. 5 is a flowchart showing the user enrollment step of the second user in the relational ID generation method according to an embodiment of the present invention.

[0062] Referring to FIG. 5, the second user 300 (terminal) installs the service App provided by the service provider 200 for enrollment (S201). Next, the second user 300 selects the user enrollment menu of the service App (S202). At this time, the service App can generate a public key pair for generating a decentralized identifier.

[0063] At this time, the service App can use a secure element (SE) for secure public key pair generation and management. Also, a user authentication function using the user's biometric information can be registered for secure user access management of the secure element device and the service App.

[0064] At this time, the service App generates a decentralized identifier for the second user 300 using the securely generated public key information. At this time, the service App can generate a decentralized identifier document for the decentralized identifier for the second user 300 as shown in FIG. 4.

[0065] The service App can generate a user enrollment request document for user enrollment (S203). At this time, the service App can generate a user enrollment request document including the generated decentralized identifier document of the second user 300.

[0066] At this time, in order for the Service App to prove to the Service Provider 200 that the Second User 300 is the owner of the decentralized identifier document to be registered, the Service App can generate a request message that includes the value (Proof) signed with the private key paired with the public key used when generating the decentralized identifier.

[0067] The Service App transmits a user enrollment request to the Service Provider 200 (S204). At this time, the user enrollment request message can be transmitted to the Service Provider 200 together. The Service Provider 200 can confirm the user enrollment request message and request the Second User 300 to confirm their identity by mobile phone (S205).

[0068] The Second User 300 can use the Service App to confirm their identity by mobile phone (S206). The Service App can transmit the result of the identity confirmation by mobile phone to the Service Provider 200 (S207). The Service Provider 200 verifies the result of the identity confirmation by mobile phone of the Second User 300 and the decentralized identifier document of the Second User 300 (S208).

[0069] At this time, in order to verify the decentralized identifier document of the Second User 300, the Service Provider 200 can verify the signature value (Proof) included in the user enrollment request message with the public key confirmed through the decentralized identifier document of the Second User 300.

[0070] The Service Provider 200 can register the decentralized identifier document of the Second User 300 in the decentralized identifier storage (S209). The Service Provider 200 can store and manage the user identity information of the Second User 300 (S210).

[0071] At this time, the user ID of the Second User 300 is the decentralized identifier generated by the Second User 300. At this time, the user identity information includes the user's name, phone number, date of birth, gender, nationality (domestic or foreign), communication carrier information, CI information, etc. that can be confirmed by identity confirmation by mobile phone.

[0072] The service provider 200 transmits the user enrollment result to the second user 300 (S211). The second user 300 confirms the result of the user enrollment process (S212).

[0073] FIGS. 6 and 7 are flowcharts showing the relational ID generation steps in a relational ID generation method according to an embodiment of the present invention.

[0074] Referring to FIGS. 6 and 7, for generating a relational ID, the second user 300 can execute the service App (S301). The second user 300 can select the relational user enrollment request menu of the service App (S302). The second user 300 can create a relational user enrollment request form via the service App (S303).

[0075] At this time, the second user 300 creates the identity information of the related person. The identity information of the related person in the relational user enrollment request form means a user with a low digital power level. At this time, the identity information of the related person must include the name, gender, date of birth, communication carrier, phone number, and the classification of domestic or foreigner of the user who must be input for personal confirmation on the mobile phone so that a user with a low digital power level can easily proceed with the personal confirmation procedure on the mobile phone.

[0076] At this time, the second user 300 inputs the related person relationship information. The related person relationship information is information that expresses the relationship with the related person based on the self. For example, types such as child, younger brother (sister), parent, etc. are included.

[0077] At this time, the second user 300 also includes the relationship verification information that the service provider 200 can verify the relationship between the second user 300 and the related person. For example, a digital file obtained by scanning a family relationship certificate in the form of a digital certificate or a family relationship certificate in the form of an official document is included in the relationship verification information.

[0078] The service App generates a relational user invitation text (S304). At this time, the invitation text includes a Deep Link that enables the relevant person to easily confirm the text. A Deep Link is a type of URL link that, when clicked by a user, can execute a specific App or move to a specific screen within a specific App. With this function, a user with low digital capabilities can simply click on the relational user invitation text received via SMS or messenger message, and not only immediately move to the relational user registration screen without performing another procedure for user registration, but also can immediately prepare to enter the user's identity information so that the identity verification procedure on the mobile phone can be easily performed. If the App is not installed, the Deep Link function can guide the user to the official App store site where the app can be installed, enabling the user to be easily induced to install the service App.

[0079] At this time, the second user 300 includes the identity information of the inviter. The inviter's identity information includes the inviter's decentralized identifier, name, phone number, relationship information between the second user 300 and the relevant person, etc.

[0080] At this time, the service App can generate the invitation text to include the value (Proof) signed with the private key paired with the public key used when generating the decentralized identifier in order to prove to the service provider 200 that the second user 300 is the owner of their own decentralized identifier.

[0081] At this time, the inviter's identity information can be utilized for the purpose of enabling the first user 100 who received the relational user invitation to confirm the identity of the inviter.

[0082] At this time, the service App encrypts the relational user invitation text with the message encryption key provided by the service App. At this time, the message encryption key is generated each time the service provider is requested to generate a disposable encryption key and managed in a session, and the message encryption key session information can be provided in the response.

[0083] At this time, the invitation text is composed of a Deep link, the inviter's identity information, message encryption key session information, and an encrypted relational user membership invitation summary form.

[0084] The second user 300 can select a means to transmit the relational user membership invitation text to the relevant person (S305). At this time, the transmission means includes text messages, messenger services, e-mails, etc.

[0085] The service App can transmit the relational user membership invitation text to the relevant person by the transmission means selected by the second user 300 (S306). The first user 100 can confirm whether the processing for the relational user membership invitation is possible (S307). At this time, the first user 100 can click on the relational user membership invitation text received in the message format.

[0086] At this time, the terminal of the first user 100 checks whether the service App is installed on the terminal of the first user 100 through the Deep Link function, and if not, it can move to the official App store site where the service App can be installed. At this time, if the service App is installed on the terminal of the first user 100, it moves to the screen for processing the relational user membership.

[0087] The first user 100 checks and accepts the content of the relational user membership invitation text via the service App (S308). At this time, the content of the invitation text that the first user 100 can check may be the inviter's identity information. At this time, the first user 100 can check whether the inviter is an inviter trusted by the person himself / herself and can accept the invitation.

[0088] The service App requests the service provider 200 for relational user membership (S309). At this time, the service App can transmit the received relational user membership invitation text together.

[0089] The service provider 200 checks the relational user membership invitation letter (S310). At this time, the service provider 200 checks the message encryption key session information included in the invitation letter, queries the message encryption key managed in the session, decrypts the relational user membership invitation format using the queried message encryption key, and checks the content of the relational user membership invitation format.

[0090] At this time, the service provider 200 checks the decentralized identifier of the second user 300 from the identity information of the requester, and queries the decentralized identifier document of the second user 300 through the decentralized identifier document storage 400.

[0091] At this time, the service provider 200 checks the public key information from the decentralized identifier document of the second user 300, and verifies the signature value (Proof) of the relational user membership invitation format.

[0092] The service provider 200 verifies the relationship between the related party and the requester (S311). At this time, the relationship between the two can be verified based on the relationship information and the relationship certification information confirmed through the relational user membership invitation format.

[0093] At this time, it is also possible for the counselor of the service provider 200 to directly confirm through wired consultation and record the confirmation content.

[0094] The service provider 200 requests the first user 100 to confirm their identity by mobile phone (S312). At this time, in order to enable a user with a low digital power level to easily proceed with the identity confirmation procedure by mobile phone, the identity information that must be input for identity confirmation by mobile phone can be transmitted.

[0095] At this time, the identity information is the identity information of the related party confirmed through the relational user membership format, and includes the user's name, gender, date of birth, communication carrier, phone number, and the classification of domestic or foreigner.

[0096] The first user 100 performs an identity verification procedure on the mobile phone (S313). At this time, the service App automatically configures a screen for identity verification on the mobile phone using the received identity information. The first user 100 can check whether their identity information is correct and request an authentication number. At this time, the service App can request the first user 100 to check whether their identity information is correct through voice guidance or the like.

[0097] At this time, the service App automatically identifies the authentication number received via text message and automatically enters the authentication number into the identity verification screen on the mobile phone. The first user 100 can easily perform identity verification on the mobile phone using the automatically entered authentication number.

[0098] If the identity verification on the mobile phone is successfully completed, the service App can transmit the result to the service provider 200 (S314). The service provider 200 can check the identity verification result on the mobile phone (S315). At this time, the information that can be verified by the identity verification on the mobile phone includes the user's name, phone number, date of birth, gender, nationality (domestic or foreign), communication carrier information, CI information, etc.

[0099] The service provider 200 requests the first user 100 to generate a public key (S316). At this time, the service provider 200 can generate and transmit an arbitrary random number for public key verification. The first user 100 generates a public key (S317). At this time, the service App can generate a public key pair for distributed identifier generation.

[0100] At this time, the service App can use a secure element (SE) for secure public key pair generation and management. Also, for secure user access management of the secure element device and the service App, a user authentication function using the user's biometric information can be registered.

[0101] The service App can transmit the generated public key information to the service provider 200 (S318). At this time, a value (Proof) obtained by signing an arbitrary random number transmitted by the service provider 200 with the private key can be generated and transmitted so that the service provider 200 can verify whether it has the private key corresponding to the public key.

[0102] The service provider 200 verifies the received public key information (S319). At this time, the service provider 200 can check whether an arbitrary random number value generated in the request step matches the signed random number value for public key verification.

[0103] The service provider 200 can request the second user 300 to generate a relational user ID for the first user 100 (S320). At this time, the service provider 200 can transmit the public key information generated by the first user 100 to the second user 300. At this time, the service provider 200 can transmit the identity information of the first user 100 to the second user 300. At this time, the identity information can include the name, phone number, and relationship information of the first user 100.

[0104] The second user 300 checks the relational user ID generation request message (S321). At this time, the second user 300 checks the name, phone number, and relationship information of the first user 100, who is the owner of the relational user ID to be generated, and checks whether it is the same as the identity information for which it requested relational user membership, and can accept it.

[0105] The service App of the second user 300 generates a relational user ID for the first user 100 (S322). At this time, the service App can generate a decentralized identifier for the first user 100 using the public key information of the first user 100 and generate a decentralized identifier document for the first user 100 as shown in FIG. 3.

[0106] At this time, when the service App generates the decentralized identifier document for the first user 100, it sets the controller and the capabilityInvocation attribute value to the decentralized identifier of the second user 300. The controller attribute of the decentralized identifier document can be meant to be an entity that has the ability (capability) to change the decentralized identifier document. That is, using the controller and the capabilityInvocation attributes of the decentralized identifier document, the second user 300, who is a related party, can manage the decentralized identifier document, which is the authentication information of the first user 100 with a low digital power level, instead.

[0107] The service App of the second user 300 can transmit the generated relational user ID information of the first user 100 to the service provider 200 (S323). At this time, in order for the service provider 200 to verify that the second user 300 has generated the decentralized identifier document for the first user 100, a signature value (Proof) obtained by signing the response message with the private key paired with the decentralized identifier of the second user 300 can be generated and transmitted.

[0108] The service provider 200 verifies the generated relational user ID information (S324). At this time, the service provider 200 can verify the signature value (Proof) with the public key confirmed from the decentralized identifier document of the second user 300 in order to verify whether the second user 300 has generated the decentralized identifier document for the first user 100.

[0109] At this time, the service provider 200 can confirm whether the hash value of the public key generated by the first user 100 is the same as the hash value of the public key described in the decentralized identifier document of the first user 100 in order to confirm whether the generated decentralized identifier document of the first user 100 is generated based on the public key information generated by the first user 100.

[0110] The service provider 200 can register the decentralized identification document for the first user 100 in the decentralized identification document storage 400 (S325). The service provider 200 can store and manage the user identity information for the first user 100 (S326).

[0111] At this time, the service provider 200 can check whether the identity information of the first user is pre-stored. If the identity information is pre-stored, this is determined as a password reset procedure, the existing user identity information is deleted, and the newly generated relational user ID information is stored and managed. The determination of whether there is a password reset procedure can also be confirmed and determined from the procedure of confirming the relational user membership invitation letter (S310).

[0112] At this time, the user ID of the first user 100 can be set to the decentralized identifier generated by the second user 300. At this time, the user identity information includes the user's name, phone number, date of birth, gender, nationality (domestic or foreign), communication carrier information, CI information, etc. that can be confirmed by self-verification on the mobile phone.

[0113] The service provider 200 stores and manages the related person information for the first user 100 (S327). At this time, the related person information may be the identity information for the second user 300. At this time, the identity information stores and manages the name, phone number, decentralized identifier, relationship information, etc. of the second user 300.

[0114] The service provider 200 can store and manage the related person information for the second user 300 (S328). At this time, the related person information can correspond to the identity information for the first user 100. At this time, the identity information stores and manages the name, phone number, decentralized identifier, relationship information, etc. of the first user 100.

[0115] The service provider 200 can transmit a guidance message regarding the completion of relational user registration to the second user 300 (S329). At this time, the service provider 200 can transmit the related person information regarding the second user 300. At this time, the service provider 200 can transmit the relational user registration request and the completion date and time information. The second user 300 confirms the content of the relational user registration completion guidance (S329-1).

[0116] The service provider 200 can respond to the first user 100 with the result of relational user registration (S330). At this time, the service provider 200 can transmit the related person information regarding the first user 100. At this time, the service provider 200 can also transmit the relational user registration request and the completion date and time information. The first user 100 confirms the content of the relational user registration result (S330-1).

[0117] FIG. 8 is a flowchart showing the user authentication steps based on the relational ID according to an embodiment of the present invention.

[0118] Referring to FIG. 8, for user authentication, the first user 100 executes the service App (S401). The first user 100 can select the login menu of the service App (S402). The service App can request service login from the service provider 200 (S403). The service provider 200 can request user authentication information from the first user 100 (S404). At this time, the service provider 200 can generate and transmit an arbitrary random number for user authentication.

[0119] The service App of the first user 100 can generate user authentication information (S405). At this time, the service App can query the decentralized identifier of the first user 100. At this time, the service App can perform biometric authentication of the user in order to use the personal key corresponding to the decentralized identifier.

[0120] At this time, the service App can generate a value (Proof) obtained by signing any received random number with the private key. At this time, the user authentication information is composed of the distributed identifier of the first user 100, any received random number value, and its signature value.

[0121] The service App of the first user 100 transmits the generated user authentication information to the service provider 200 (S406). The service provider 200 can verify the user authentication information (S407). At this time, the service provider 200 can confirm the distributed identifier of the first user 100. At this time, the service provider 200 can confirm whether the distributed identifier of the first user 100 is registered in the user identity information DB.

[0122] At this time, the service provider 200 can query the distributed identifier document for the first user 100 from the distributed identifier document storage 400. At this time, the service provider 200 can verify the signature value (Proof) with the public key confirmed from the distributed identifier document of the first user 100. At this time, the service provider 200 can confirm whether the random number value generated in the user authentication information request step is the same as the random number value signed with the private key.

[0123] The service provider 200 can transmit the user authentication information verification result to the first user 100 in the service login response (S408). The service App of the first user 100 can confirm the service login response result (S409).

[0124] FIG. 9 is a flowchart showing the business support steps based on the relational ID according to an embodiment of the present invention.

[0125] Referring to FIG. 9, for the business support request, the first user 100 can log in to the service using the service App (S501). At this time, the service provider 200 may be in a state of confirming the distributed identifier for the first user 100. The first user 100 can select the related person support service menu of the service App (S502). At this time, the first user 100 can select the related person for whom support is requested. At this time, the first user 100 can select the purpose for which support is requested. At this time, the first user 100 can create the content of the support request in text.

[0126] The service App of the first user 100 requests the related person support service from the service provider 200 (S503). At this time, the service App can transmit the support request content selected or input by the first user 100. The service provider 200 can query the related person information requested by the first user 100 (S504). At this time, the service provider 200 can query the related person information preset using the distributed identifier of the first user 100.

[0127] The service provider can request related person support from the registered related persons (S505). At this time, the service provider can transmit the user identity information for requesting related person support and the support request content. The second user 300 can confirm the related person support request content (S506). At this time, the second user can confirm the identity of the user who requested the related person support and the support request content, and can accept the availability of support. At this time, the second user can modify or add the support request content.

[0128] The service App of the second user can transmit a response to the availability of related person support to the service provider (S507). At this time, the service App can generate a request message to include the value (Proof) signed with the private key paired with the public key used when generating the distributed identifier to prove to the service provider 200 that the second user 300 is a related person of the first user 100 in the related person support response message.

[0129] The service provider can check and process the content of the support for the relevant parties (S508). At this time, the service provider 200 can query the decentralized identifier document for the second user 300 from the decentralized identifier document storage 400. At this time, the service provider 200 can verify the signature value (Proof) with the public key confirmed from the decentralized identifier document of the second user 300. At this time, the service provider can receive the confirmation of the requester for the support content again by means such as wired. At this time, the service provider can receive the confirmation of the relevant parties for the support content again by means such as wired. At this time, the service provider can process the business for the finally confirmed support content.

[0130] The service provider can inform the relevant parties of the result of the relevant party support process (S509). At this time, the service provider can transmit the service business processing result, the service request, and the completion date and time. The second user can confirm the result of the relevant party support process (S509-1).

[0131] The service provider responds to the requester with the result of the relevant party support service (S510). At this time, the service provider can transmit the service business processing result, the service request, and the completion date and time. The first user can confirm the result of the relevant party support service (S510-1).

[0132] FIG. 10 is a diagram showing the configuration of a computer system according to an embodiment.

[0133] The relational ID generation device based on the decentralized identifier according to the embodiment can be realized in a computer system 1000 such as a computer-readable recording medium.

[0134] The computer system 1000 can include one or more processors 1010, a memory 1030, a user interface input device 1040, a user interface output device 1050, and a storage 1060 that communicate with each other via a bus 1020. Further, the computer system 1000 can further include a network interface 1070 connected to a network 1080. The processor 1010 may be a semiconductor device that executes a program or processing instruction stored in the central processing unit or the memory 1030 or the storage 1060. The memory 1030 and the storage 1060 may be storage media including at least one or more of a volatile medium, a non-volatile medium, a separable medium, a non-separable medium, a communication medium, or an information transmission medium. For example, the memory 1030 can include a ROM 1031 and a RAM 1032.

[0135] The relational ID generation device based on a distributed identifier according to an embodiment of the present invention includes one or more processors 1010 and an execution memory 1030 that stores at least one or more programs executed by the one or more processors 1010. The at least one or more programs include instructions for receiving an invitation to join including relational user invitation text information from a terminal of a first user, verifying the relationship between the first user and the second user, and generating a relational ID including relationship information between the first user and the second user. The first user requests the performance of a task using the relational ID, and the second user can receive a task performance request based on the relational ID.

[0136] At this time, the relational user invitation text information can be received by the terminal of the first user from the terminal of the second user.

[0137] At this time, the relational user invitation text information can include the name, gender, date of birth, telecommunications carrier, telephone number, and domestic / foreign personal information of the first user.

[0138] At this time, the step of generating the relational ID may include the step of authenticating the first user, the step of requesting the generation of the relational ID of the first user to the terminal of the second user using the public key information of the first user, the step of receiving the personal key signature value of the second user's decentralized identifier document and the relational ID of the first user from the terminal of the second user, and the step of storing the generated relational ID document of the first user in the decentralized identifier document storage.

[0139] At this time, the controller and capability invocation attribute values of the relational ID document of the first user can correspond to the decentralized identifier of the second user.

[0140] At this time, the step of generating the relational ID may further include the step of verifying whether the second user has generated the relational ID of the first user using the public key of the second user's decentralized identifier document.

[0141] At this time, the step of generating the relational ID may further include the step of transmitting a membership completion notice message to the terminal of the first user and the terminal of the second user respectively.

[0142] At this time, the program further includes an instruction word for storing the identity information of the first user and the related person information of the second user. The identity information of the first user includes the name, gender, date of birth, communication carrier, phone number and domestic / foreign personal information of the first user. The related person information of the second user may include the name, phone number of the second user and the relationship information with the first user.

[0143] At this time, if the program receives a service execution request from the terminal of the first user, it can compare the related person information corresponding to the service execution request with the controller information in the relational ID document of the first user.

[0144] At this time, the relational ID document can correspond to a Decentralized Identifier Document.

[0145] The specific implementations described in the present invention are examples and do not limit the scope of the present invention in any way. For the sake of brevity of the specification, descriptions of conventional electronic configurations, control systems, software, and other functional aspects of the system may be omitted. Also, the connections or connecting members of the lines between the components shown in the drawings are shown by way of example of functional connections and / or physical or circuit connections, and in actual devices, they may be replaceable or shown as additional diverse functional connections, physical connections, or circuit connections. Also, components that are not necessarily required for the application of the present invention are not mentioned specifically, such as "essential" or "importantly".

[0146] Therefore, the idea of the present invention should not be defined only by the above-described embodiments, and not only the scope of the claims described below, but also all scopes equivalent or equivalently changed therefrom belong to the scope of the idea of the present invention.

Explanation of Reference Numerals

[0147] 1000: Computer system, 1010: Processor 1020: Bus, 1030: Memory 1031: ROM, 1032: RAM 1040: User interface input device 1050: User interface output device 1060: Storage, 1070: Network interface 1080: Network

Claims

1. 1. A method for supporting registration of a relational ID based on a distributed identifier, comprising: receiving a membership request including relational user membership request information from a terminal of a first user; verifying a relationship between the first user and a second user; generating a relationship ID including relationship information between the first user and the second user; Including, The first user requests a task to be performed using the relationship ID; The second user receives a task execution request based on the relationship type ID. A method for generating a relational ID based on a distributed identifier.

2. The relationship-type user membership request message information is received by the first user's terminal from the second user's terminal. The method for generating a relational ID based on a distributed identifier according to claim 1.

3. The relationship-type user membership request information includes the first user's name, gender, date of birth, telecommunications carrier, phone number, and domestic / foreign information. The method for generating a relational ID based on a distributed identifier according to claim 2.

4. The step of generating a relation type ID includes: performing identity authentication for the first user; requesting a terminal of the second user to generate a relationship ID of the first user using public key information of the first user; receiving a private key signature value of a second user distributed identifier document and a relationship type ID of a first user from a terminal of the second user; storing the generated relational identity document of the first user in a distributed identifier document storage; The method for generating a relational ID based on a distributed identifier according to claim 1, further comprising:

5. The Controller and Capability invocation attribute values ​​of the first user's relational ID document correspond to the second user's distributed identifier; The method for generating a relational ID based on a distributed identifier according to claim 4.

6. The step of generating a relation type ID includes: and verifying whether the second user generated the relational ID of the first user using a public key of the second user distributed identifier document. The method for generating a relational ID based on a distributed identifier according to claim 4.

7. The step of generating a relation type ID includes: and further comprising transmitting a membership completion notification message to the first user terminal and the second user terminal, respectively. The method for generating a relational ID based on a distributed identifier according to claim 4.

8. The method comprises: storing identity information of the first user and relationship information of the second user; The identity information of the first user includes the name, gender, date of birth, telecommunications carrier, telephone number, and domestic / foreigner information of the first user; The second user's related party information includes the second user's name, phone number, and related party information to the first user. The method for generating a relational ID based on a distributed identifier according to claim 1.

9. The method comprises: When a task execution request is received from the terminal of the first user, related party information corresponding to the task execution request is compared with controller information in a relational ID document of the first user; The method for generating a relational ID based on a distributed identifier according to claim 5.

10. The relational ID document corresponds to a decentralized ID document. The method for generating a relational ID based on a distributed identifier according to claim 4.

11. one or more processors; an execution memory for storing at least one program to be executed by said one or more processors; Including, The at least one program is receiving a membership request including relational user membership request information from a terminal of a first user; verifying a relationship between the first user and a second user; generating a relationship ID including relationship information between the first user and the second user; Including a command to perform The first user requests a task to be performed using the relationship ID; The second user receives a task execution request based on the relationship type ID. A relational ID generation device based on a distributed identifier.

12. The relationship-type user membership request message information is received by the first user's terminal from the second user's terminal. The apparatus for generating a relational ID based on a distributed identifier according to claim 11.

13. The relationship-type user membership request information includes the first user's name, gender, date of birth, telecommunications carrier, phone number, and domestic / foreign information. The apparatus for generating a relational ID based on a distributed identifier according to claim 12.

14. The step of generating a relation type ID includes: performing identity authentication for the first user; requesting a terminal of the second user to generate a relationship ID of the first user using public key information of the first user; receiving a private key signature value of a second user distributed identifier document and a relationship type ID of a first user from a terminal of the second user; storing the generated relational identity document of the first user in a distributed identifier document storage; The apparatus for generating a relational ID based on a distributed identifier according to claim 11, further comprising:

15. The Controller and Capability invocation attribute values ​​of the first user's relational ID document correspond to the second user's distributed identifier; The apparatus for generating a relational ID based on a distributed identifier according to claim 14.

16. The step of generating a relation type ID includes: and verifying whether the second user generated the relational ID of the first user using a public key of the second user distributed identifier document. The apparatus for generating a relational ID based on a distributed identifier according to claim 14.

17. The step of generating a relation type ID includes: and further comprising transmitting a membership completion notification message to the first user terminal and the second user terminal, respectively. The apparatus for generating a relational ID based on a distributed identifier according to claim 14.

18. The program is The method further includes the step of storing identity information of the first user and related party information of the second user, The identity information of the first user includes the name, gender, date of birth, telecommunications carrier, telephone number, and domestic / foreigner information of the first user; The second user's related party information includes the second user's name, phone number, and related party information to the first user. The apparatus for generating a relational ID based on a distributed identifier according to claim 11.

19. The program is When a task execution request is received from the terminal of the first user, related party information corresponding to the task execution request is compared with controller information in a relational ID document of the first user; The apparatus for generating a relational ID based on a distributed identifier according to claim 15.

20. The relational ID document corresponds to a decentralized ID document. The apparatus for generating a relational ID based on a distributed identifier according to claim 14.

Images