System for providing shareable decentralized identity service and method for providing shareable decentralized identity service using same

Abstract

A system for providing a shareable decentralized identity service, according to one embodiment of the present invention, comprises: an owner terminal configured to receive owner signature information for proving that an owner owns a managed object; a sharer terminal communicatively connected to a service server and configured to receive sharer signature information for proving that a sharer jointly manages the managed object with the owner; a service server communicatively connected to the owner terminal and the sharer terminal, and configured to generate at least one piece of information selected from among managed-object decentralized identifier information for identifying the managed object owned by the owner on the basis of the owner signature information, owner decentralized identifier information of which validity is verified on the basis of the owner signature information, and sharer decentralized identifier information of which validity is verified on the basis of the sharer signature information; and a blockchain network communicatively connected to the service server and configured to record the managed-object decentralized identifier information and at least one piece of decentralized identifier information selected from among the owner decentralized identifier information and the sharer decentralized identifier information.

Description

System for providing a shareable decentralized ID service and method for providing a shareable decentralized ID service using the same

[0001] The present invention relates to a system for providing a shareable decentralized ID service and a method for providing a shareable decentralized ID service using the same. More specifically, the invention relates to a system for providing a shareable decentralized ID service and a method for providing a shareable decentralized ID service using the same, which can clearly provide unique information regarding an object that can be jointly owned, while also more securely maintaining information regarding users who manage said object, such as the owner or co-owner of said object.

[0002] Current identity management systems rely primarily on centralized systems such as governments, corporations, and social media.

[0003] However, through decentralized IDs based on blockchain or other distributed ledger technologies, users can manage and verify their own identities, thereby providing greater privacy and security and enabling them to prove their identity without control by a central authority.

[0004] To use decentralized IDs, the generation of a Decentralized Identifier (DID) capable of uniquely identifying a specific user is required; through this, individuals retain sovereignty over their identity information and can selectively provide only the necessary information.

[0005] Furthermore, DID enhances privacy protection and security, enabling identity verification in various fields without control by central authorities. For instance, it can be used in digital passports, academic credential verification, and medical record management, and the risk of hacking or data leakage is reduced thanks to the decentralized nature of blockchain.

[0006] However, existing DIDs are limited to use as a means of verifying human identity or for identity verification services, and are not being utilized in fields requiring management functions, such as when multiple owners exist or owner information changes after a DID is assigned to a specific entity.

[0007] Furthermore, existing DID-based identity authentication services issued DIDs via a blockchain network only at the time of issuance and subsequently operated off-chain; as they operated without passing through a blockchain network, there are limitations in terms of the blockchain ecosystem and the scalability of DID-based services.

[0008] Meanwhile, as the pet market grows and the need for pet care increases, individual identification is becoming more important as the demand for various businesses rises.

[0009] For example, while some countries implement mandatory animal registration systems, the systems are not being effectively utilized; therefore, there is a need to establish an effective identification system for pets, including animal registration, to expand and manage the pet market.

[0010] In particular, to enhance effectiveness, an identity verification system through private institutions is necessary in addition to trusted agencies such as government agencies; however, if the identity verification system is operated by private institutions, the reliability of the data may become an issue.

[0011] In other words, as the need for pet management elements increases, there is a growing necessity for distributed ID technology that enables joint management and sharing, taking into account the pet care system where multiple guardians exist.

[0012] The present invention aims to solve the aforementioned problems by providing a shareable decentralized ID service provision system and a shareable decentralized ID service provision method using the same, which can clearly provide unique information regarding a jointly owned object that can be managed by multiple users, such as a pet, while more securely maintaining information about users managing the object, such as the owner and co-owners of the object.

[0013] A shareable decentralized ID service providing system according to an embodiment of the present invention comprises: an owner terminal configured to receive owner signature information proving ownership of a managed object; a co-owner terminal configured to receive co-owner signature information proving ownership of a co-owner who jointly manages the managed object with the owner, and connected to communication with the service server; a service server configured to receive at least one selected information among managed object distributed identifier information that distinguishes a managed object owned by the owner based on the owner signature information, owner distributed identifier information whose validity is verified based on the owner signature information, and co-owner distributed identifier information whose validity is verified based on the co-owner signature information; and a blockchain network configured to receive communication with the service server and to record at least one selected distributed identifier information among the managed object distributed identifier information, owner distributed identifier information, and co-owner distributed identifier information.

[0014] More specifically, the managed distributed identifier information comprises: basic managed distributed identifier information including information indicating the owner of the managed object; and modified managed distributed identifier information generated based on the basic managed distributed identifier information, including information indicating that the co-owner has been added or modified as a co-manager of the managed object; wherein the owner terminal is configured to receive co-owner addition request information requesting the addition of the co-owner in order to proceed with joint management of the co-owner and the managed object; and the service server is characterized by generating the modified managed distributed identifier information and providing it to the blockchain network only when the authority of the co-owner has been verified, after receiving the co-owner addition request information from the owner terminal.

[0015] More specifically, the above-mentioned request for adding a co-owner further includes a request for adding a first co-owner, which is a new co-owner who has not been assigned the above-mentioned distributed identifier information from the owner terminal; and the service server receives the request for adding a first co-owner from the owner terminal and provides it to the co-owner terminal, and is characterized by generating a distributed identifier information for a co-owner whose validity is verified based on the co-owner signature information of the first co-owner input through the co-owner terminal.

[0016] More specifically, it further includes information for adding a first co-owner, which is information input through the owner terminal and requests the addition of a first co-owner who is a new co-owner not assigned the shared co-owner distributed identifier information; and the service server receives the first co-owner addition request information from the owner terminal and provides it to the co-owner terminal, and generates shared co-owner distributed identifier information whose validity is verified based on the co-owner signature information of the first co-owner input through the co-owner terminal.

[0017] More specifically, the above-mentioned request for adding a co-owner further includes a second request for adding a co-owner who has been assigned the co-owner distributed identifier information from the owner terminal; and the service server receives the second request for adding a co-owner from the owner terminal and determines whether a co-owner distributed identifier distinguishing the user of the co-owner terminal is registered in the blockchain network, and if a co-owner distributed identifier already registered in the blockchain network exists, verifies the validity of both the owner's signature information and the second co-owner's signature information and records the second management target distributed identifier modification information, in which the second co-owner is added as the joint manager, in the blockchain network.

[0018] More specifically, the owner terminal is configured to receive owner change request information, which is information requesting the transfer of ownership of the managed object to a third co-owner, and the service server, after receiving the owner change request information, analyzes the co-owner distributed identifier information of the third co-owner receiving the ownership transfer to determine whether the current owner's request for ownership transfer is appropriate, and then verifies the validity of both the owner's signature information and the third co-owner's signature information, and records third managed object distributed identifier modification information, which includes the content that the ownership of the managed object has been transferred to the third co-owner, on the blockchain network.

[0019] And, a method for providing a shareable decentralized ID service according to an embodiment of the present invention relates to a method for providing a shareable decentralized ID service based on a system for providing a shareable decentralized ID service comprising an owner terminal, a sharer terminal, a service server, and a blockchain network, comprising: an owner signature information input step of receiving owner signature information proving that the owner is a user of the owner terminal and is the owner of a managed object through the owner terminal; an owner verification step of verifying the validity of the owner signature information provided through the owner terminal at the service server after the owner signature information input step; an owner distributed identifier information generation step of generating a distributed identifier of the owner and recording it in the blockchain network if the owner signature information is verifiable at the service server after the owner verification step; and a managed object distributed identifier basic information generation step of generating a managed object distributed identifier basic information including information indicating the owner of the managed object while distinguishing the managed object owned by the owner and recording it in the blockchain network after the owner distributed identifier information generation step, if the owner signature information is verifiable at the service server. A co-owner addition request step in which, in the service server, information requesting to add a co-owner who jointly manages the managed object with the owner is received through the owner terminal, wherein co-owner addition request information is received; a co-owner signature information input step, after the co-owner addition request step, in which co-owner signature information proving that one is a co-owner is received through the co-owner terminal; and a co-owner verification step, after the co-owner signature information input step, in which the service server verifies the validity of the co-owner signature information provided through the co-owner terminal.and, after the shared member verification step, a step of generating managed distributed identifier modification information, wherein the service server generates managed distributed identifier modification information including information indicating that the shared member has been added or modified to the joint manager of the managed object based on the managed distributed identifier basic information; characterized by including;

[0020] The above-mentioned request for adding a co-owner includes, after the step of generating basic information for the managed distributed identifier, receiving information for adding a first co-owner, which is information for adding a first co-owner who is a new co-owner not assigned to the co-owner distributed identifier information, through the owner terminal; and the above-mentioned request for adding information for modifying the managed distributed identifier includes, after the step of generating basic information for the managed distributed identifier, verifying the validity of the signature information of the co-owner at the service server to generate new information for the co-owner distributed identifier, and then generating information for modifying the first managed distributed identifier indicating that the first co-owner has been added as a joint manager of the managed object, and recording this information on the blockchain network.

[0021] The above-mentioned request for adding a co-owner includes a second request for adding a co-owner, which is information for adding a second co-owner who possesses the co-owner distributed identifier information, provided through the owner terminal after the step of generating basic information for the managed distributed identifier; and the above-mentioned request for adding modified information for the managed distributed identifier is characterized by generating second modified information for the managed distributed identifier, which indicates that the co-owner has been added as a joint manager of the managed object, by verifying the validity of the signature information of both the owner and the co-owner at the service server after the step of generating second modified information for the managed distributed identifier, which is then recorded in the blockchain network.

[0022] The above-mentioned request for adding a co-owner includes, after the step of generating basic information for the managed object distributed identifier, a step of requesting a change of owner, which is information requesting the transfer of ownership of the managed object to a third co-owner through the owner terminal; and the step of generating modified information for the managed object distributed identifier is characterized by, after the step of requesting a change of owner, verifying the validity of both the signature information of the owner and the signature information of the third co-owner at the service server to generate modified information for the third managed object distributed identifier that includes the content of the transfer of ownership of the managed object to the third co-owner, and recording it on the blockchain network.

[0023] A shareable decentralized ID service providing system according to one embodiment of the present invention verifies validity based on signature information of the owner and the sharer and records the information on a blockchain network, thereby enabling secure authentication that is impossible to tamper with, and thereby maintaining the ownership and sharing rights of the managed object transparently and reliably, and simultaneously securing security and efficiency in a decentralized manner.

[0024] In addition, when an owner adds or modifies a co-owner of a managed object, information requesting the addition of a co-owner is entered through the owner's terminal, and the service server generates information modifying the managed object's distributed identifier only after verifying the co-owner's authority and records it on the blockchain network. This ensures that changes to ownership and sharing rights for the managed object are accurately reflected and that only verified information is recorded on the blockchain, thereby significantly improving the transparency and security of management rights.

[0025] In addition, a shareable decentralized ID service providing system according to one embodiment of the present invention is configured such that when information requesting the addition of a first sharer is entered from an owner terminal, the service server transmits it to a sharer terminal, and after verifying its validity based on the signature information of the new sharer, sharesr distributed identifier information is generated. Through this configuration, the verification of identity validity and authorization are processed transparently and securely during the process of adding a new sharer, and by recording this on a blockchain, reliable sharer management is possible without a central authority, thereby allowing the process of adding a new sharer to proceed more reliably and securely.

[0026] In addition, a shareable decentralized ID service providing system according to one embodiment of the present invention can provide the effect of enhancing reliability and security in the process of adding a new sharer by configuring that a request for adding a first sharer is input from an owner terminal, a service server transmits this to a sharer terminal, and then generates a sharer distributed identifier information by verifying its validity based on the sharer's signature information.

[0027] In addition, a shareable decentralized ID service providing system according to one embodiment of the present invention has the effect of making the identity verification process of a sharer added as a co-manager more reliable and secure by a configuration in which the service server checks whether the distributed identifier of the sharer is already registered in a blockchain network, and then verifies the signature information of both the owner and the second sharer to modify the management information.

[0028] In particular, reliability can be enhanced through duplicate verification of already registered co-owners, and security and transparency can be strengthened by verifying the signature information of the owner and the second co-owner together so that joint management authority is granted only with the mutual consent of both parties.

[0029] In addition, a shareable decentralized ID service providing system according to one embodiment of the present invention can provide the effect of improving reliability and transparency in the ownership transfer process by preventing illegal or abnormal ownership transfers through a configuration in which ownership transfer request information is input through an owner terminal, a service server analyzes the distributed identifier information of a third co-owner, and then verifies the signature information of both the owner and the third co-owner to record the ownership transfer, thereby analyzing in advance whether the ownership transfer request is appropriate and ensuring that the ownership transfer is carried out only after verifying the signature information of both parties.

[0030] In addition, the method for providing a shareable decentralized ID service according to one embodiment of the present invention can provide the effect of ensuring that the identity and authority of the owner and co-owner are reliably verified and securely recorded through a process of verifying ownership and management authority based on the signature information of the owner and co-owner, and recording this on a blockchain to transparently maintain the information of the owner and co-owner of the managed object.

[0031] In addition, a method for providing a shareable decentralized ID service according to one embodiment of the present invention can ensure a safe and transparent joint management system in a decentralized manner by verifying whether a new sharer has been properly added through a procedure that verifies the validity of the sharer's signature information after the first sharer addition request information is entered, and by recording this on a blockchain to maintain it in a way that prevents tampering.

[0032] In addition, a method for providing a shareable decentralized ID service according to one embodiment of the present invention is configured such that an owner inputs a request to add a second co-owner who already possesses shared identifier information, and a service server verifies the signature information of both the owner and the co-owner, adds them as joint managers of the managed object, and records this on a blockchain. Through this configuration, joint management authority is granted only after the signature information of both the owner and the co-owner is verified, and transparency and prevention of tampering are guaranteed by recording this information on the blockchain. Through this, a joint management system for the managed object can be maintained safely and reliably through redundant verification.

[0033] In addition, a method for providing a shareable decentralized ID service according to one embodiment of the present invention is configured such that an owner inputs information requesting a transfer of ownership to a third co-owner, and a service server verifies the signature information of both the owner and the third co-owner and records the details of the transfer of ownership on a blockchain. By verifying the signature information of both the owner and the third co-owner to confirm that the transfer of ownership has been legally carried out and recording this on a blockchain, it is possible to prevent forgery and tampering. Through this, the transfer of ownership can be processed safely, and the security and reliability of the change of ownership can be secured in a decentralized manner.

[0034] FIG. 1 is a schematic diagram illustrating the configuration of a shareable decentralized ID service providing system according to one embodiment of the present invention.

[0035] FIG. 2 is a block diagram illustrating a terminal that constitutes a shareable decentralized ID service providing system according to one embodiment of the present invention.

[0036] FIG. 3 is a block diagram illustrating a service server that constitutes a shareable decentralized ID service providing system according to an embodiment of the present invention.

[0037] FIG. 4 is a block diagram illustrating a blockchain network constituting a shareable decentralized ID service providing system according to one embodiment of the present invention.

[0038] FIG. 5 is a flowchart illustrating the process of generating managed distributed identifier information through a shareable decentralized ID service providing system according to an embodiment of the present invention.

[0039] FIG. 6 is a flowchart illustrating the process of sharing between an owner terminal and a first sharer terminal through a shareable decentralized ID service providing system according to an embodiment of the present invention.

[0040] FIG. 7 is a flowchart illustrating the process of sharing between an owner terminal and a second sharer terminal through a shareable decentralized ID service providing system according to an embodiment of the present invention.

[0041] FIG. 8 is a flowchart illustrating the process of sharing between an owner terminal and a third sharer terminal through a shareable decentralized ID service providing system according to an embodiment of the present invention.

[0042] FIG. 9 is a flowchart illustrating the sequence of steps for a method of providing a shareable decentralized ID service according to an embodiment of the present invention.

[0043] The advantages and 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 accompanying drawings.

[0044] However, the present invention is not limited to the embodiments disclosed below but can be implemented in various different forms, and these embodiments are provided merely to ensure that the disclosure of the present invention is complete and to fully inform those skilled in the art of the scope of the invention, and the present invention is defined only by the scope of the claims.

[0045] Furthermore, the terms used in this specification are for describing the embodiments and are not intended to limit the invention.

[0046] In this specification, the singular form includes the plural form unless specifically stated otherwise in the text. As used in this specification, "comprises" and / or "comprising" do not exclude the presence or addition of other components other than those mentioned.

[0047] Unless otherwise defined, all terms used in this specification (including technical and scientific terms) may be used in a meaning that is commonly understood by those skilled in the art to which the present invention belongs.

[0048] FIG. 1 is a schematic diagram illustrating the configuration of a shareable decentralized ID service providing system according to one embodiment of the present invention.

[0049] As illustrated in FIG. 1, a shareable decentralized ID service providing system according to one embodiment of the present invention may include an owner terminal (100), a sharer terminal (200), a service server (300), and a blockchain network (400).

[0050] Here, the owner terminal (100) and the sharer terminal (200) may be provided as terminals (T) including mobile phones, smartphones, laptop computers, digital broadcasting terminals, PDAs (personal digital assistants), PMPs (portable multimedia players), navigation systems, slate PCs, tablet PCs, watch-type terminals, glass-type terminals (smart glasses), HMDs (head-mounted displays), etc.

[0051] First, the owner terminal (100) is configured to receive owner signature information proving that the user is the owner of a managed object that requires separate management.

[0052] In particular, the managed objects managed by the user of the owner terminal (100) may include pets and children who cannot directly operate the terminal to generate a Decentralized Identifier (DID) for the use of a decentralized ID system, as well as inanimate objects.

[0053] Here, the owner terminal (100) may be configured to communicate with the service server (300), and to verify the validity of the owner terminal (100), it is configured to generate and store a unique private key that distinguishes the user of the owner terminal (100) and a public key for verifying the private key.

[0054] In addition, the owner terminal (100) can generate a managed object distributed identifier information that distinguishes a managed object owned by the owner based on the owner signature information, along with owner distributed identifier information whose validity is verified based on owner signature information through the service server (300), and can record this in the blockchain network (400).

[0055] At this time, the owner terminal (100) may be configured to generate a public key and private key pair for issuing the owner distributed identifier and a public key and private key pair for issuing the managed distributed identifier in order to generate the owner distributed identifier information and the managed distributed identifier information.

[0056] Next, the co-owner terminal (200) is connected to the service server (300) for communication, and is configured to receive co-owner signature information proving that the co-owner is jointly managing the managed object with the owner.

[0057] Additionally, the shared terminal (200) may be configured to communicate with the service server (300), and is configured to generate and store a unique private key that distinguishes the user of the shared terminal (200) and a public key for verifying the private key in order to verify the validity of the shared terminal (200).

[0058] At this time, the shared terminal (200) can generate shared distributed identifier information that has been validated based on shared signature information through the service server (300), and can record this on the blockchain network (400).

[0059] At this time, the shared terminal (200) may be configured to generate a public key and a private key pair for issuing the shared distributed identifier in order to generate the shared distributed identifier information.

[0060] More specifically, the shared terminal (200) may include a first shared terminal (210), a second shared terminal (220), and a third shared terminal (230).

[0061] Here, the first shared-user terminal (210) is a shared-user terminal that has not acquired the aforementioned shared-user distributed identifier information at the time when the owner terminal (100) possesses the owner distributed identifier information and the managed distributed identifier information, and the second shared-user terminal (220) and the third shared-user terminal (230) can be defined as shared-user terminals that possess the aforementioned shared-user distributed identifier information at the time described above.

[0062] And, as previously described, the service server (300) is configured to communicate with the owner terminal and the sharer terminal.

[0063] In particular, the service server (300) is configured to generate managed distributed identifier information, owner distributed identifier information, and co-owner distributed identifier information.

[0064] The above-mentioned managed object distributed identifier information is information that distinguishes a managed object owned by the owner based on the above-mentioned owner signature information, and can be encrypted and recorded on the above-mentioned blockchain network.

[0065] Additionally, the service server (300) may include a ledger database, and the service server (300) may be configured to generate the managed distributed identifier information, owner distributed identifier information, and co-owner distributed identifier information and store them in the ledger database.

[0066] In other words, by allowing the managed distributed identifier information, owner distributed identifier information, and co-owner distributed identifier information to be stored separately in the ledger database, it is possible to provide a stable service by performing backups of the aforementioned distributed identifier information.

[0067] In addition, even if a problem occurs in the blockchain network (400) described later, the decentralized ID provision service of the present invention can be continuously provided by utilizing the distributed identifier information stored in the ledger database, thereby maintaining the continuity of information and providing a more reliable service.

[0068] In addition, when the blockchain network is interrupted, distributed identifier information generated or updated after the point of interruption of the blockchain network is stored in the ledger database.

[0069] In particular, when the blockchain network is restarted, the service server (300) may be activated to record distributed identifier information generated or updated after the aforementioned time point in the blockchain network.

[0070] More specifically, the above-mentioned managed distributed identifier information may include basic information on the managed distributed identifier and modification information on the managed distributed identifier.

[0071] Here, the basic information of the managed distributed identifier is information including information indicating the owner of the managed object, and is information initially generated at the service server (300) through the owner terminal (100).

[0072] And, the above-mentioned managed distributed identifier modification information is information indicating that the shared person has been added or modified as a joint manager of the above-mentioned managed object, and can be generated in the service server (300) based on the above-mentioned managed distributed identifier basic information.

[0073] In addition, the above owner distributed identifier information is information whose validity has been verified based on the above owner signature information, and can be encrypted and recorded on the above blockchain network.

[0074] Next, the shared shareholder distributed identifier information is information whose validity has been verified based on the shared shareholder signature information, and can be encrypted and recorded on the blockchain network.

[0075] At this time, the service server (300) is driven to hash at least one of the distributed identifier information selected from the managed distributed identifier information, the owner distributed identifier information, and the co-owner distributed identifier information, and record it on the blockchain network.

[0076]

[0077] Next, the blockchain network (400) is connected to the service server and is configured to record at least one distributed identifier information selected from the managed distributed identifier information, the owner distributed identifier information, and the co-owner distributed identifier information.

[0078] Hereinafter, the operation sequence of a shareable decentralized ID service providing system according to one embodiment of the present invention will be explained in more detail with reference to FIGS. 5 to 7.

[0079]

[0080] Next, with reference to FIG. 2, a terminal constituting a shareable decentralized ID service providing system according to one embodiment of the present invention will be described.

[0081] FIG. 2 is a block diagram illustrating a terminal that constitutes a shareable decentralized ID service providing system according to one embodiment of the present invention.

[0082] As illustrated in FIG. 2, the terminal (T) may include an input unit, a sensing unit, a wireless communication unit, an output unit, a memory unit, an interface unit, a power supply unit, and a control unit.

[0083] However, not all of the components described above are essential components, and the terminal (T) may be implemented with more components than those described above, or with fewer components.

[0084] The above components will be examined in turn below.

[0085] The above input unit may include a camera or video input unit for video signal input, a microphone or audio input unit for audio signal input, and a user input unit (e.g., a touchpad, etc.) for receiving information from a user.

[0086] Voice data or image data collected from the input unit can be analyzed and processed into user control commands.

[0087] The sensing unit may include one or more sensors for sensing at least one of information within the mobile communication terminal, information about the surrounding environment surrounding the mobile communication terminal, and user information.

[0088] For example, the sensing unit may include at least one of a proximity sensor, an illumination sensor, a touch sensor, an acceleration sensor, a magnetic sensor, a gravity sensor (G-sensor), a gyroscope sensor, a motion sensor, an RGB sensor, an infrared sensor (IR sensor), a fingerprint sensor, an ultrasonic sensor, and an optical sensor (e.g., a camera).

[0089] The output unit is intended to generate output related to sight, hearing, or touch, and may include at least one of a display unit, an audio output unit, and a haptic module.

[0090] The display unit can implement a touch screen by forming a layered structure with the touch sensor or by being formed as an integral unit.

[0091] This touch screen functions as a user input unit that provides an input interface between the terminal (T) and the user, and at the same time can provide an output interface between the terminal (T) and the user.

[0092] The interface section serves as a channel for various types of external devices connected to the terminal (T).

[0093] This interface section may include at least one of a wired / wireless headset port, an external charger port, a wired / wireless data port, a memory card port, a port for connecting a device equipped with an identification module, an audio I / O (Input / Output) port, a video I / O (Input / Output) port, and an earphone port.

[0094] In the terminal (T), appropriate control related to the connected external device can be performed in response to the connection of an external device to the interface part.

[0095] In addition, the memory unit stores data that supports various functions of the terminal (T). The memory unit can store multiple application programs (or applications) running on the terminal (T), data for the operation of the terminal (T), and instructions.

[0096] At least some of these applications can be downloaded from an external server via wireless communication.

[0097] Meanwhile, the application program is stored in a memory unit and installed on a terminal (T), and can be driven by a control unit to perform the operation (or function) of the terminal (T).

[0098] In addition to operations related to the above service, the control unit typically controls the overall operation of the terminal (T).

[0099] The control unit can provide or process appropriate information or functions to the user by processing signals, data, information, etc. that are input or output through the components examined above, or by running an application program stored in the memory unit.

[0100] In addition, the control unit can control at least some of the aforementioned components to run an application program stored in the memory unit. Furthermore, the control unit can operate at least two or more of the components included in the terminal (T) in combination with each other to run the service.

[0101] The power supply unit, under the control of the control unit, receives external power and internal power and supplies power to each component included in the terminal (T). This power supply unit includes a battery, and the battery may be a built-in battery or a replaceable battery.

[0102] The wireless communication unit may include one or more components that enable wireless communication between the terminal (T) and the wireless communication system or wireless communication between the terminal (T) and the network where the terminal (T) is located.

[0103] For example, the wireless communication unit may include a mobile communication module, a short-range communication module, and a location information module.

[0104] The above mobile communication module transmits and receives wireless signals with at least one of a base station, an external terminal, and a server on a mobile communication network. Here, the wireless signal may include various forms of data such as voice signals, video call signals, or text / multimedia message transmission and reception.

[0105] The above-mentioned short-range communication module refers to a module for short-range communication. Short-range communication technologies such as Bluetooth, RFID (Radio Frequency Identification), infrared communication (IrDA, Infrared Data Association), UWB (Ultra Wideband), and ZigBee may be used.

[0106] The above location information module is a module for obtaining the location (or current location) of a terminal (T), and representative examples thereof include a GPS (Global Positioning System) module or a WiFi (Wireless Fidelity) module.

[0107] As another example, if the terminal (T) utilizes a Wi-Fi module, the location of the terminal (T) can be obtained based on information from a wireless AP (Wireless Access Point) that transmits or receives wireless signals with the Wi-Fi module.

[0108] If necessary, the location information module may perform any of the other modules of the wireless communication unit to obtain data regarding the location of the terminal (T) as a substitute or additionally.

[0109] That is, the location information module is a module used to obtain the location (or current location) of the terminal (T), and is not limited to a module that directly calculates or obtains the location of the mobile terminal.

[0110]

[0111] Next, the service server will be described in more detail with reference to Fig. 3.

[0112] FIG. 3 is a block diagram illustrating a service server that constitutes a shareable decentralized ID service providing system according to an embodiment of the present invention.

[0113] As illustrated in FIG. 3, the service server (300) includes a wireless communication module configured to communicate wirelessly, a database that receives and stores information input through the aforementioned user terminal, an execution module responsible for running and executing a service application (Application, app) provided and installed on the user terminal from the service server (300), a data analysis module that analyzes recommendation information for the purchased product of the sales product stored in the database, a management module that accumulates and manages the recommendation information, and a control module that controls the aforementioned components.

[0114]

[0115] Next, the blockchain network described above will be explained in more detail with reference to Fig. 4.

[0116] FIG. 4 is a block diagram illustrating a blockchain network constituting a shareable decentralized ID service providing system according to one embodiment of the present invention.

[0117] As illustrated in FIG. 4, the blockchain network (400) may include a DID registry for generating distributed identifiers as described above, and the DID registry may be managed by the operator of the service.

[0118]

[0119] Next, with reference to FIGS. 5 to 7, the operation sequence of a shareable decentralized ID service providing system according to one embodiment of the present invention will be described in more detail.

[0120] FIG. 5 is a flowchart illustrating the process of generating managed distributed identifier information through a shareable decentralized ID service providing system according to an embodiment of the present invention.

[0121] Referring to FIG. 5, first, the generation and storage of a first public key and a first private key that distinguish the owner are carried out through the owner terminal (100). At this time, the generated first public key can be collected by the service server (300).

[0122] Next, when distributed identifier generation request information requesting the generation of distributed identifier information is input through the owner terminal (100), the service server collects this information and generates signature request information requesting an owner signature proving ownership of the managed object, and provides this information to the owner terminal (100).

[0123] Subsequently, the owner terminal (100) generates owner signature information proving ownership of the managed object based on the first private key and provides it to the service server, and the service server (300) that receives the owner signature information determines whether verification is possible by matching it with the first public key provided earlier.

[0124] At this time, if the owner signature information can be verified with the first public key, the service server (300) generates owner distributed identifier information that has been validated based on the owner signature information, hashes it, and records it in the blockchain network (400).

[0125] Subsequently, through the blockchain network (400), record completion information is generated indicating that the recording of the owner distributed identifier information is completed.

[0126] And, the service server (300) can receive the record completion information and, based thereon, generate owner distributed identifier issuance information indicating that the generation of owner distributed identifier information has been completed, and provide it to the owner terminal (100).

[0127] Meanwhile, if the above owner signature information cannot be verified with the above first public key, the received signature information is discarded, and owner distributed identifier issuance failure information is generated to indicate that the generation of the above owner distributed identifier information has failed, and is provided to the above owner terminal (100).

[0128]

[0129] Next, in order to proceed with the generation of managed object distributed identifier information that distinguishes the managed object owned by the owner, the generation and storage of a second public key and a second private key that distinguish the managed object are performed at the owner terminal (100). At this time, the generated second public key can be collected from the service server (300).

[0130] And, through the owner terminal (100), input of information for a managed object, which is information for distinguishing the managed object, can be performed.

[0131] At this time, the information on the managed object may include an element capable of distinguishing the managed object, along with an element indicating the relationship between the managed object and the owner.

[0132] Afterward, the service server (300) receives the information on the managed object, and then analyzes the information on the managed object to define the relationship between the managed object and the owner.

[0133] At this time, the service server (300) may define the relationship based on legally verifiable records, such as purchase history and registration history, of the owner when the managed object is a tradeable object, and may define the relationship based on family relationships when the managed object is a child.

[0134] At this time, it goes without saying that the information serving as the standard for defining the aforementioned relationship can be obtained through a separate external service server.

[0135] Afterwards, the service server (300) requests owner signature information from the owner terminal (100) and receives it, and then matches the owner signature information with the previously received second public key to determine whether verification is possible.

[0136] At this time, if the owner signature information can be verified with the second public key, the service server (300) generates basic information for a managed distributed identifier whose validity is verified based on the owner signature information, and hashes it and records it in the blockchain network (400).

[0137] Subsequently, through the blockchain network (400), record completion information is generated indicating that the recording of the basic information of the managed distributed identifier is completed.

[0138] And, the service server (300) can receive the record completion information and, based thereon, generate owner distributed identifier issuance information indicating that the creation of the basic information of the managed distributed identifier has been completed, and provide it to the owner terminal (100).

[0139] Meanwhile, if the above owner signature information cannot be verified with the above second public key, the received signature information is discarded, and a management target distributed identifier issuance failure information is generated to indicate that the generation of the above management target distributed identifier information has failed, and this information is provided to the above owner terminal (100).

[0140]

[0141] Next, with reference to FIG. 6, the process of sharing between an owner terminal and a first sharer terminal through a shareable decentralized ID service providing system according to an embodiment of the present invention will be described in more detail.

[0142] FIG. 6 is a flowchart illustrating the process of sharing between an owner terminal and a first sharer terminal through a shareable decentralized ID service providing system according to an embodiment of the present invention.

[0143] In the case of the process of sharing between the owner terminal (100) and the first sharer terminal (210), since this step is performed after the managed distributed identifier is generated, the description of the process of generating the managed distributed identifier is omitted.

[0144] First, the first co-owner is defined as a new co-owner who has not been assigned the co-owner distributed identifier information.

[0145] More specifically, the first shared terminal (210) can be defined as a shared terminal that has not acquired the shared distributed identifier information at the time when the owner terminal (100) possesses the owner distributed identifier information and the managed distributed identifier information.

[0146] As illustrated in FIG. 6, in order for the owner and the co-owner to jointly manage the object to be managed through the owner terminal (100), a first co-owner addition request information is input requesting the addition of the co-owner.

[0147] The above information requesting the addition of the first co-owner is information entered through the owner terminal (100), and is information requesting the addition of the first co-owner, a new co-owner who has not been assigned the co-owner distributed identifier information.

[0148] Afterwards, the service server (300) receives the first shared person addition request information from the owner terminal (100) and provides it to the first shared person terminal (210).

[0149] Through the first shareholder terminal (210) that receives the first shareholder addition request information, the generation and storage of a third public key and a third private key that distinguish the shareholder are carried out, and the third public key generated at this time can be collected by the service server (300).

[0150] Next, when information requesting the creation of a distributed identifier, which is information requesting the creation of a distributed identifier of a shareholder, is input at the first shareholder terminal (210), the service server (300) receives this information, defines the relationship between the owner and the first shareholder, and then generates signature request information.

[0151] Here, the signature request information is provided to the owner terminal (100) and the first co-owner terminal (210), respectively.

[0152] At this time, the service server (300) generates shared shareholder distributed identifier information and records it on the blockchain network when the validity of the shared shareholder signature information of the first shared shareholder input through the shared shareholder terminal is verified by the public key, and when the validity of the shared shareholder signature information is not verified, the generation of the shared shareholder distributed identifier information fails.

[0153] And, the service server (300) verifies the owner signature information obtained through the owner terminal (100) and the first co-owner signature information obtained through the first co-owner terminal (210), respectively, and when it is determined that all signature information can be verified with a public key and its validity is verified, it generates the managed distributed identifier modification information and hashes it to the blockchain network and records it.

[0154] In particular, only when the relationship between the above owner and the above first co-owner is proven, the above-described above-described managed object distributed identifier basic information is recorded on the blockchain network to indicate that the above-described managed object modified information has been added as a co-owner who jointly manages the above-described managed object with the above owner.

[0155] That is, as described above, by a configuration in which request information for adding a first co-owner is entered at the owner terminal, the service server transmits it to the first co-owner terminal, and then validates its validity based on the signature information of the first co-owner to generate new co-owner distributed identifier information, the effect of increasing reliability and security during the process of adding a new co-owner can be provided.

[0156]

[0157] Next, with reference to FIG. 7, the process of sharing between an owner terminal and a second sharer terminal will be described in more detail through a shareable decentralized ID service providing system according to one embodiment of the present invention.

[0158] FIG. 7 is a flowchart illustrating the process of sharing between an owner terminal and a second sharer terminal through a shareable decentralized ID service providing system according to an embodiment of the present invention.

[0159] The second shared terminal (220) above can be defined as the terminal of a shared person who possesses the shared person distributed identifier information at the time when the owner terminal (100) possesses the owner distributed identifier information and the managed distributed identifier information.

[0160] As illustrated in FIG. 7, in order for the owner and the co-owner to jointly manage the object to be managed through the owner terminal (100), a second co-owner addition request information is input requesting the addition of the co-owner.

[0161] Here, the second co-owner addition request information is information requesting the addition of a co-owner who has been assigned the co-owner distributed identifier information.

[0162] Afterwards, the service server (300) receives the second co-owner addition request information from the owner terminal (100) and determines whether a shared shareholder distributed identifier distinguishing the user of the second co-owner terminal (220) is registered in the blockchain network (400).

[0163] Afterwards, if there is a shared shareholder distributed identifier already registered in the blockchain network (400), it is determined whether the owner's request to add a shared shareholder is appropriate.

[0164] Next, if the service server (300) determines that the owner's request is a valid request, it generates and transmits signature request information requesting the owner's signature information to the second co-owner terminal (220).

[0165] Afterwards, the service server (300) receives and verifies the second co-owner signature information input through the second co-owner terminal (220).

[0166] In addition, the service server (300) also transmits signature request information requesting the owner's signature information to the owner terminal side, and proceeds with the process of receiving and verifying the owner's signature information input through the owner terminal (100).

[0167] Then, the service server (300) verifies the owner signature information obtained through the owner terminal (100) and the second co-owner signature information obtained through the second co-owner terminal (220), respectively, and when it is determined that all signature information can be verified with a public key and its validity is verified, it generates a second managed distributed identifier modification information with the second co-owner added as the joint manager, hashes it, and records it on a blockchain network.

[0168] That is, by a configuration in which the service server verifies whether the distributed identifier of the co-owner is already registered in the blockchain network, and then verifies the signature information of both the owner and the second co-owner to modify the management information, the identity verification process of the co-owner added as a joint manager is carried out more reliably and securely.

[0169] In particular, reliability can be enhanced through duplicate verification of already registered co-owners, and security and transparency can be strengthened by verifying the signature information of the owner and the second co-owner together so that joint management authority is granted only with the mutual consent of both parties.

[0170]

[0171] Next, with reference to FIG. 8, the process of transferring ownership between an owner terminal and a third sharer terminal through a shareable decentralized ID service providing system according to one embodiment of the present invention will be described in more detail.

[0172] FIG. 8 is a flowchart illustrating the process of transferring ownership between an owner terminal and a third sharer terminal through a shareable decentralized ID service providing system according to an embodiment of the present invention.

[0173] The third shared terminal (230) can be defined as the terminal of a shared person who possesses the shared person distributed identifier information at the time when the owner terminal (100) possesses the owner distributed identifier information and the managed distributed identifier information.

[0174] As illustrated in FIG. 8, owner change request information, which is information requesting the transfer of ownership of the managed object to a third co-owner, is input through the owner terminal (100).

[0175] Here, the above-mentioned owner change request information is information requested to transfer ownership to a co-owner who has been assigned the above-mentioned co-owner distributed identifier information.

[0176] Afterward, the service server (300), after receiving the owner change request information, determines whether a shared shareholder distributed identifier distinguishing the user of the third shared shareholder terminal (230) is registered in the blockchain network (400).

[0177] Next, if there is a shared owner distributed identifier already registered in the blockchain network (400), it is determined whether the current owner's request for a change of owner is appropriate.

[0178] Next, the service server (300) analyzes the shared identifier information of the third co-owner receiving the ownership transfer to determine whether the current owner's request for ownership transfer is appropriate. If it determines that the request for ownership transfer is appropriate, it generates and transmits signature request information requesting the signature information of the third co-owner to the third co-owner terminal (230).

[0179] And, the service server (300) receives and verifies the third co-owner signature information input through the third co-owner terminal (230).

[0180] In addition, the service server (300) also transmits signature request information requesting the owner's signature information to the owner terminal side, and proceeds with the process of receiving and verifying the owner's signature information input through the owner terminal (100).

[0181] Then, the service server (300) verifies the owner signature information obtained through the owner terminal (100) and the third co-owner signature information obtained through the third co-owner terminal (230), respectively, and when it is determined that all signature information can be verified with a public key and its validity is verified, it generates third managed object distributed identifier modification information in which the ownership of the managed object is transferred to the third co-owner, and hashes and records this in a blockchain network.

[0182] That is, through a configuration in which ownership transfer request information is input through the owner terminal (100), and the service server analyzes the shared identifier information of the third co-owner and verifies both the signature information of the owner and the third co-owner to record the ownership transfer, it is possible to prevent illegal or abnormal ownership transfers by analyzing in advance whether the ownership transfer request is appropriate and ensuring that the ownership transfer is carried out only after verifying the signature information of both parties, thereby providing the effect of improving reliability and transparency in the ownership transfer process.

[0183]

[0184] Next, with reference to FIG. 9, a method for providing a shareable decentralized ID service according to an embodiment of the present invention will be described in more detail.

[0185] FIG. 9 is a flowchart illustrating the sequence of steps for a method of providing a shareable decentralized ID service according to an embodiment of the present invention.

[0186] A method for providing a shareable decentralized ID service according to one embodiment of the present invention is carried out based on the shareable decentralized ID service provision system described above.

[0187] In particular, the above-described decentralized ID service providing system includes an owner signature information input step (S100), an owner verification step (S200), an owner distributed identifier information generation step (S300), a managed distributed identifier basic information generation step (S400), a co-owner addition request step (S500), a co-owner signature information input step (S600), a co-owner verification step (S700), and a managed distributed identifier modification information generation step (S800).

[0188] First, the owner signature information input step (S100) is a step performed through the owner terminal, and proceeds to receive owner signature information proving that the user of the owner terminal is the owner of the managed object.

[0189] Next, the owner verification step (S200) is a step performed on the service server after the owner signature information input step.

[0190] More specifically, the above owner verification step (S200) is performed to verify the validity of the owner signature information provided through the owner terminal.

[0191] And, the above-mentioned owner distributed identifier information generation step (S300) is a step performed after the above-mentioned owner verification step (S200), and is performed through the above-mentioned service server.

[0192] In particular, the step of generating the owner distributed identifier information (S300) proceeds to generate the owner's distributed identifier and record it on the blockchain network only when the owner signature information can be verified by the service server.

[0193] Next, the step of generating basic information for the managed distributed identifier (S400) is performed through the service server after the step of generating owner distributed identifier information.

[0194] More specifically, the step of generating basic information for a managed distributed identifier (S400) proceeds to generate basic information for a managed distributed identifier that includes information indicating the owner of the managed object, while distinguishing the managed object owned by the owner, and to record it on the blockchain network when the owner signature information can be verified on the service server.

[0195] Next, the above-mentioned request to add a co-owner step (S500) is a step in which the service server receives information requesting the addition of a co-owner, which is information requesting to add a co-owner who jointly manages the managed object with the owner, through the owner terminal.

[0196] Here, the request to add a co-owner step (S500) may be performed separately according to the type of co-owner, and may include a first request to add a co-owner step, a second request to add a co-owner step, and a request to change the owner step.

[0197] First, the above-mentioned first co-owner addition request step is a step of adding a first co-owner, which is a new co-owner who has not been assigned co-owner distributed identifier information.

[0198] More specifically, the first co-owner addition request step proceeds to receive first co-owner addition request information, which is information for adding a first co-owner who is a new co-owner not assigned the co-owner distributed identifier information, through the owner terminal after the management target distributed identifier basic information generation step (S400).

[0199] And, the step of requesting the addition of the second co-owner is a step of adding a second co-owner who possesses the shared identifier information.

[0200] More specifically, the step of requesting the addition of the second co-owner is carried out such that, after the step of generating basic information on the managed distributed identifier, the information for adding the second co-owner who possesses the shared identifier information is provided through the owner terminal.

[0201] And, the above-mentioned owner change request step is a step in which the current owner requests the transfer of ownership of the above-mentioned managed object from a third co-owner.

[0202] More specifically, the owner change request step proceeds to receive owner change request information, which is information requesting the transfer of ownership of the managed object to a third co-owner, through the owner terminal after the management target distributed identifier basic information generation step.

[0203] At this time, based on the information classified according to the type of co-owner as described above, the managed distributed identifier modification information generated in the subsequent managed distributed identifier modification information generation step (S800) can be generated more clearly by distinguishing it.

[0204]

[0205] Next, the co-owner signature information input step (S600) is a step performed through the co-owner terminal after the co-owner addition request step.

[0206] More specifically, the co-owner signature information input step (S600) is a step in which co-owner signature information proving that one is a co-owner is received.

[0207] Here, the private key assigned to the co-owner can be utilized as the above-mentioned co-owner signature information.

[0208] Next, the co-owner verification step (S700) is performed through the service server after the co-owner signature information input step.

[0209] At this time, the above-mentioned co-owner verification step (S700) proceeds to verify the validity of the co-owner signature information provided through the above-mentioned co-owner terminal.

[0210] To verify the validity of the above-mentioned co-signer signature information, the private key and shared key assigned to the co-signer may be utilized, and the step of generating the managed distributed identifier modification information described below may be carried out only when the validity verification proceeds successfully.

[0211] Next, the step of generating modification information for the managed distributed identifier (S800) is a step performed after the shared entity verification step (S700).

[0212] More specifically, the step of generating modification information for the managed distributed identifier (S800) proceeds to generate modification information for the managed distributed identifier, which is generated based on the basic information of the managed distributed identifier at the service server, hash the information, and record it on a blockchain network.

[0213] More specifically, the step of generating managed distributed identifier modification information (S800) is a step of generating managed distributed identifier modification information that includes information indicating that the shared person has been added or modified as a co-manager of the managed object, hashing the information, and recording it on a blockchain network.

[0214] In particular, the step of generating modified information for the managed distributed identifier is performed to generate different modified information for the managed distributed identifier depending on whether the above-described first request for adding a co-owner, second request for a co-owner, and request for changing an owner step are performed.

[0215] For example, when the above-mentioned first co-owner addition request step is performed, the service server verifies the validity of the co-owner's signature information to generate new co-owner distributed identifier information, and then generates first managed object distributed identifier modification information indicating that the first co-owner has been added as a joint manager of the managed object, and records this information on the blockchain network.

[0216] And, when the above-mentioned second co-owner addition request step is performed, the service server verifies the validity of both the owner and the co-owner's signature information and proceeds to generate second managed object distributed identifier modification information indicating that the co-owner has been added as a joint manager of the managed object, and records it on the blockchain network.

[0217] In addition, when the above-mentioned owner change request step is performed, the service server verifies the validity of both the signature information of the owner and the signature information of the third co-owner, generates third managed object distributed identifier modification information including the content that the ownership of the managed object has been transferred to the third co-owner, and proceeds to record it on the blockchain network.

[0218] As described above, through a configuration in which the service server verifies the signature information of both the owner and co-owner, adds them as joint managers of the managed object, and records this on the blockchain, joint management authority is granted only after the signature information of both the owner and co-owner has been verified. Since this information is recorded on the blockchain, transparency and prevention of tampering are guaranteed. Through this redundant verification, the joint management system for the managed object can be maintained safely and reliably.

[0219]

[0220] Each step of the control algorithm according to the present invention described above may be executed in a different order as needed, and it is obvious that even in the case of an embodiment executed in a different order, it falls within the scope of the present invention.

[0221] Although the present invention has been described above with reference to the embodiments illustrated in the drawings, this is merely for the purpose of explaining the invention, and those skilled in the art will understand that various modifications or equivalent embodiments are possible from the detailed description of the invention.

[0222] Therefore, the true scope of rights of the present invention must be determined by the technical concept of the patent claims.

[0223] A shareable decentralized ID service providing system according to one embodiment of the present invention comprises: an owner terminal configured to receive owner signature information proving ownership of a managed object; a co-owner terminal configured to receive co-owner signature information proving ownership of a co-owner who jointly manages the managed object with the owner, and connected to communication with the service server; a service server configured to receive at least one selected information among managed object distributed identifier information that distinguishes a managed object owned by the owner based on the owner signature information, owner distributed identifier information whose validity is verified based on the owner signature information, and co-owner distributed identifier information whose validity is verified based on the co-owner signature information; and a blockchain network configured to receive communication with the service server and to record at least one selected distributed identifier information among the managed object distributed identifier information, owner distributed identifier information, and co-owner distributed identifier information. This is a form for implementing the invention.

[0224] More specifically, the managed distributed identifier information comprises: basic managed distributed identifier information including information indicating the owner of the managed object; and modified managed distributed identifier information generated based on the basic managed distributed identifier information, including information indicating that the co-owner has been added or modified as a co-manager of the managed object; wherein the owner terminal is configured to receive co-owner addition request information requesting the addition of the co-owner in order to proceed with joint management of the co-owner and the managed object; and the service server, after receiving the co-owner addition request information from the owner terminal, generates the modified managed distributed identifier information and provides it to the blockchain network only when the authority of the co-owner has been verified.

[0225] More specifically, the above-mentioned request for adding a co-owner further includes a first request for adding a co-owner, which is a new co-owner who has not been assigned the above-mentioned distributed identifier information from the owner terminal; and the service server receives the first request for adding a co-owner from the owner terminal and provides it to the co-owner terminal, and generates a co-owner distributed identifier information whose validity is verified based on the co-owner signature information of the first co-owner input through the co-owner terminal, as a form for implementing the invention.

[0226] More specifically, the invention further includes information for requesting the addition of a first co-owner, which is information input through the owner terminal and is a new co-owner who has not been assigned the shared co-owner distributed identifier information; and the service server receives the first co-owner addition request information from the owner terminal and provides it to the co-owner terminal, and generates shared co-owner distributed identifier information whose validity is verified based on the co-owner signature information of the first co-owner input through the co-owner terminal, as a form for implementing the invention.

[0227] More specifically, the above-mentioned request for adding a co-owner further includes a second request for adding a co-owner who has been assigned the co-owner distributed identifier information from the owner terminal; and the service server receives the second request for adding a co-owner from the owner terminal and determines whether a co-owner distributed identifier distinguishing the user of the co-owner terminal is registered in the blockchain network, and if a co-owner distributed identifier already registered in the blockchain network exists, verifies the validity of both the owner's signature information and the second co-owner's signature information, and records the second management target distributed identifier modification information, in which the second co-owner is added as the joint manager, in the blockchain network, as a form for implementing the invention.

[0228] More specifically, the owner terminal is configured to receive owner change request information, which is information requesting the transfer of ownership of the managed object to a third co-owner, and the service server, after receiving the owner change request information, analyzes the co-owner distributed identifier information of the third co-owner receiving the ownership transfer to determine whether the current owner's request for ownership transfer is appropriate, and then verifies the validity of both the owner's signature information and the third co-owner's signature information, and records third managed object distributed identifier modification information, which includes the content that the ownership of the managed object has been transferred to the third co-owner, on the blockchain network, as a form for implementing the invention.

[0229] And, a method for providing a shareable decentralized ID service according to an embodiment of the present invention relates to a method for providing a shareable decentralized ID service based on a system for providing a shareable decentralized ID service comprising an owner terminal, a sharer terminal, a service server, and a blockchain network, comprising: an owner signature information input step of receiving owner signature information proving that the owner is a user of the owner terminal and is the owner of a managed object through the owner terminal; an owner verification step of verifying the validity of the owner signature information provided through the owner terminal at the service server after the owner signature information input step; an owner distributed identifier information generation step of generating a distributed identifier of the owner and recording it in the blockchain network if the owner signature information is verifiable at the service server after the owner verification step; and a managed object distributed identifier basic information generation step of generating a managed object distributed identifier basic information including information indicating the owner of the managed object while distinguishing the managed object owned by the owner and recording it in the blockchain network after the owner distributed identifier information generation step, if the owner signature information is verifiable at the service server. A co-owner addition request step in which, in the service server, information requesting to add a co-owner who jointly manages the managed object with the owner is received through the owner terminal, wherein co-owner addition request information is received; a co-owner signature information input step, after the co-owner addition request step, in which co-owner signature information proving that one is a co-owner is received through the co-owner terminal; and a co-owner verification step, after the co-owner signature information input step, in which the service server verifies the validity of the co-owner signature information provided through the co-owner terminal.The invention is implemented in a form that includes: a step of generating managed distributed identifier modification information, after the shared member verification step, generating managed distributed identifier modification information at the service server based on the managed distributed identifier basic information, the modified information including information indicating that the shared member has been added or modified to the joint manager of the managed object;

[0230] The above-mentioned request for adding a co-owner includes, after the step of generating basic information for the managed distributed identifier, receiving information for adding a first co-owner, which is information for adding a first co-owner who has not been assigned the co-owner distributed identifier information, through the owner terminal; and the step of generating information for modifying the managed distributed identifier includes, after the step of generating basic information for the managed distributed identifier, verifying the validity of the signature information of the co-owner at the service server to generate new information for the co-owner distributed identifier, and then generating information for modifying the first managed distributed identifier indicating that the first co-owner has been added as a joint manager of the managed object, and recording this information on the blockchain network, as a form for implementing the invention.

[0231] The above-mentioned request for adding a co-owner includes a step for requesting the addition of a second co-owner, which is information for adding a second co-owner who possesses the co-owner distributed identifier information, provided through the owner terminal after the step for generating basic information of the managed distributed identifier; and the step for generating modified information of the managed distributed identifier is, after the step for requesting the addition of a second co-owner, in the service server, verifying the validity of both the owner and the co-owner's signature information to generate modified information of the second managed distributed identifier indicating that the co-owner has been added as a joint manager of the managed object, and recording this information on the blockchain network, as a form for implementing the invention.

[0232] The above-mentioned request for adding a co-owner includes, after the step of generating basic information for the managed object distributed identifier, a step of requesting a change of owner, which is information requesting the transfer of ownership of the managed object to a third co-owner through the owner terminal; and the step of generating modified information for the managed object distributed identifier includes, after the step of requesting a change of owner, verifying the validity of both the signature information of the owner and the signature information of the third co-owner at the service server to generate modified information for the third managed object distributed identifier that includes the content of the transfer of ownership of the managed object to the third co-owner, and recording it on the blockchain network, as a form for implementing the invention.

[0233] A shareable decentralized ID service providing system according to one embodiment of the present invention is expected to be widely used in industry in that it verifies validity based on the signature information of the owner and the sharer and records the information on a blockchain network, thereby enabling secure authentication that is impossible to tamper with, and thereby maintaining the ownership and sharing rights of the managed object transparently and reliably, while simultaneously securing security and efficiency in a decentralized manner.

[0234] In addition, when an owner adds or modifies a co-owner of a managed object, information requesting the addition of a co-owner is entered through the owner's terminal, and the service server creates information modifying the managed object's distributed identifier only after verifying the co-owner's authority and records it on the blockchain network. This ensures that changes to ownership and sharing rights for the managed object are accurately reflected and that only verified information is recorded on the blockchain, thereby significantly enhancing the transparency and security of management rights. Therefore, it is expected to be widely used in the industry.

[0235] In addition, the shareable decentralized ID service providing system according to one embodiment of the present invention is expected to be widely used in industry in that, when information requesting the addition of a first sharer is entered from the owner terminal, the service server transmits it to the sharer terminal, and after verifying validity based on the signature information of the new sharer, generates a sharer distributed identifier information, thereby transparently and securely processing the validation of identity and authorization during the process of adding a new sharer, and by recording this on a blockchain, reliable sharer management is possible without a central authority, so the process of adding a new sharer can proceed more reliably and securely.

[0236] In addition, the shareable decentralized ID service providing system according to one embodiment of the present invention is expected to be widely used in industry in that it can provide the effect of enhancing reliability and security in the process of adding a new sharer by configuring that a request for adding a first sharer is input from an owner terminal, a service server transmits this to a sharer terminal, and then generates a sharer distributed identifier information by verifying validity based on the sharer's signature information.

[0237] In addition, a shareable decentralized ID service providing system according to one embodiment of the present invention is expected to be widely used in industry in that the identity verification process of a sharer added as a co-manager is carried out more reliably and securely by a configuration in which the service server checks whether the distributed identifier of the sharer is already registered in a blockchain network, and then verifies the signature information of both the owner and the second sharer to modify the management information.

[0238] In particular, it is expected to be widely used in the industry as it can enhance security and transparency by increasing reliability through duplicate verification of already registered co-owners and verifying the signature information of the owner and the second co-owner together so that joint management authority is granted only with the mutual consent of both parties.

[0239] In addition, a shareable decentralized ID service providing system according to one embodiment of the present invention is expected to be widely used in industry in that it can provide the effect of improving reliability and transparency in the ownership transfer process by preventing illegal or abnormal ownership transfers through a configuration in which ownership transfer request information is input through an owner terminal, a service server analyzes the distributed identifier information of a third co-owner, and then verifies both the signature information of the owner and the third co-owner to record the ownership transfer, thereby analyzing in advance whether the ownership transfer request is appropriate and ensuring that the ownership transfer is carried out only after verifying the signature information of both parties.

[0240] In addition, the method for providing a shareable decentralized ID service according to one embodiment of the present invention is expected to be widely used in industry in that it can provide the effect of ensuring that the identity and authority of the owner and co-owner are reliably verified and securely recorded through a process of verifying ownership and management authority based on the signature information of the owner and co-owner and recording this on a blockchain to transparently maintain the information of the owner and co-owner of the managed object.

[0241] In addition, the method for providing a shareable decentralized ID service according to one embodiment of the present invention is expected to be widely used in industry in that it can ensure a safe and transparent joint management system in a decentralized manner by verifying whether a new sharer has been properly added through a procedure that verifies the validity of the sharer's signature information after the first sharer addition request information is entered, and by recording this on a blockchain to maintain it in a way that prevents tampering.

[0242] In addition, a method for providing a shareable decentralized ID service according to one embodiment of the present invention is configured such that an owner inputs a request to add a second co-owner who already possesses shared identifier information, and a service server verifies the signature information of both the owner and the co-owner, adds them as joint managers of a managed object, and records this on a blockchain. Through this configuration, joint management authority is granted only after the signature information of both the owner and the co-owner is verified, and transparency and prevention of tampering are guaranteed as this information is recorded on the blockchain. It is expected to be widely used in industry as this allows for the safe and reliable maintenance of a joint management system for a managed object through redundant verification.

[0243] In addition, the method for providing a shareable decentralized ID service according to one embodiment of the present invention is expected to be widely used in industry in that, through a configuration in which an owner inputs information requesting a transfer of ownership to a third co-owner, and a service server verifies the signature information of both the owner and the third co-owner and records the details of the transfer of ownership on a blockchain, it is possible to prevent forgery by verifying the signature information of both the owner and the third co-owner to confirm that the transfer of ownership has been legally carried out and recording it on a blockchain, thereby enabling the transfer of ownership to be processed safely and ensuring the security and reliability of the change of ownership in a decentralized manner.

Claims

1. An owner terminal (100) provided to receive owner signature information proving ownership of the object under management; A co-owner terminal (200) provided to receive co-owner signature information proving that the co-owner is jointly managing the above-mentioned managed object with the owner; A service server (300) that is connected to the above owner terminal and the above co-owner terminal and generates at least one selected information among management target distributed identifier information that distinguishes a management target object owned by the owner based on the above owner signature information, owner distributed identifier information whose validity is verified based on the above owner signature information, and co-owner distributed identifier information whose validity is verified based on the above co-owner signature information; and A shareable decentralized ID service providing system characterized by including: a blockchain network (400) configured to communicate with the service server and to record at least one distributed identifier information selected from the managed distributed identifier information, the owner distributed identifier information, and the sharer distributed identifier information.

2. In Paragraph 1, The above-mentioned managed distributed identifier information is, Basic information for a managed distributed identifier including information indicating the owner of the above-mentioned managed object; and Managed distributed identifier modification information generated based on the above managed distributed identifier basic information and including information indicating that the shared person has been added or modified as a joint manager of the above managed object; The above-mentioned owner terminal is, In order to proceed with joint management of the said co-owner and the said managed object, information requesting the addition of said co-owner is provided to be received. The above service server is, A shareable decentralized ID service providing system characterized by receiving information requesting the addition of a shared person from the owner terminal, and then, only when the authority of the shared person is verified, generating information to modify the managed distributed identifier and providing it to the blockchain network.

3. In Paragraph 2, The above information regarding the request to add a co-owner is, Further including first co-owner addition request information requesting the addition of a first co-owner, a new co-owner who has not been assigned the co-owner distributed identifier information from the owner terminal; The above service server is, The above-mentioned request for the addition of the first co-owner is received from the above-mentioned owner terminal and provided to the above-mentioned co-owner terminal, A shareable decentralized ID service providing system characterized by generating sharer distributed identifier information whose validity is verified based on the sharer signature information of the first sharer input through the sharer terminal.

4. In Paragraph 3, It further includes first co-owner addition request information, which is information input through the owner terminal and requests the addition of a first co-owner, a new co-owner who has not been assigned the co-owner distributed identifier information; The above service server is, The above-mentioned request for the addition of the first co-owner is received from the above-mentioned owner terminal and provided to the above-mentioned co-owner terminal, A shareable decentralized ID service providing system characterized by generating sharer distributed identifier information whose validity is verified based on the sharer signature information of the first sharer input through the sharer terminal.

5. In Paragraph 2, The above information regarding the request to add a co-owner is, It further includes second co-owner addition request information requesting the addition of a co-owner who has been assigned the co-owner distributed identifier information from the owner terminal; The above service server is, Receive the second co-owner addition request information from the owner terminal and determine whether a shared shareholder distributed identifier distinguishing the user of the co-owner terminal is registered in the blockchain network, and A shareable decentralized ID service providing system characterized by verifying the validity of both the owner's signature information and the second co-owner's signature information when a shared member distributed identifier already registered in the blockchain network exists, and recording modification information for a second managed distributed identifier in which the second co-owner is added as a joint manager in the blockchain network.

6. In Paragraph 2, The above-mentioned owner terminal is, It is configured to receive owner change request information, which is information requesting the transfer of ownership of the said managed object to a third co-owner, and The above service server is, A shareable decentralized ID service providing system characterized by receiving the above-mentioned owner change request information, analyzing the shared identifier information of the third co-owner receiving the ownership transfer to determine whether the current owner's request for ownership transfer is appropriate, verifying the validity of both the signature information of the owner and the signature information of the third co-owner, and recording third managed object shared identifier modification information, which includes the content that the ownership of the managed object has been transferred to the third co-owner, on the blockchain network.

7. A method for providing a shareable decentralized ID service based on a shareable decentralized ID service providing system comprising an owner terminal, a sharer terminal, a service server, and a blockchain network, wherein Owner signature information input step (S100) of receiving owner signature information proving that the user of the owner terminal is the owner of the managed object through the owner terminal; After the above owner signature information input step, an owner verification step (S200) that verifies the validity of the owner signature information provided through the owner terminal from the service server; After the above owner verification step, if the above owner signature information can be verified on the service server, an owner distributed identifier information generation step (S300) of generating the owner's distributed identifier and recording it on the blockchain network; After the above-mentioned owner distributed identifier information generation step, if the above-mentioned owner signature information is verifiable on the service server, a managed object distributed identifier basic information generation step (S400) is performed to generate managed object distributed identifier basic information including information indicating the owner of the managed object while distinguishing the managed object owned by the owner, and to record this information on the blockchain network; A request for adding a co-owner (S500) receiving, through the owner terminal at the service server, information for requesting to add a co-owner who jointly manages the managed object with the owner; After the above-mentioned request for addition of a co-owner, a co-owner signature information input step (S600) in which co-owner signature information proving that one is a co-owner is received through the co-owner terminal; After the above-mentioned co-owner signature information input step, a co-owner verification step (S700) that verifies the validity of the co-owner signature information provided through the co-owner terminal from the service server; and A method for providing a shareable decentralized ID service, characterized by including: a step (S800) for generating managed distributed identifier modification information, wherein, after the shared person verification step, the service server generates managed distributed identifier modification information including information indicating that the shared person has been added or modified to the joint manager of the managed object based on the managed distributed identifier basic information.

8. In Paragraph 7, The above request step for adding a co-owner is, After the above-mentioned management target distributed identifier basic information generation step (S400), the first co-owner addition request step receives, through the owner terminal, first co-owner addition request information, which is information for adding a first co-owner who is a new co-owner not assigned co-owner distributed identifier information; and The above-mentioned step of generating modification information for managed distributed identifiers is, A method for providing a shareable decentralized ID service, characterized by, after the above-mentioned first co-owner addition request step, verifying the validity of the co-owner's signature information in the service server to generate new co-owner distributed identifier information, and then generating first managed object distributed identifier modification information indicating that the first co-owner has been added as a joint manager of the managed object and recording it in the blockchain network.

9. In Paragraph 7, The above request step for adding a co-owner (S500) is, After the step of generating basic information for the managed distributed identifier, the step of requesting the addition of a second co-owner proceeds to receive information for adding a second co-owner, which is information for adding a second co-owner possessing the shared sharer distributed identifier information, through the owner terminal; The above-mentioned step of generating modification information for managed distributed identifiers is, A method for providing a shareable decentralized ID service, characterized by, after the above-mentioned second co-owner addition request step, verifying the validity of both the owner and the co-owner's signature information in the service server to generate second managed object distributed identifier modification information indicating that the co-owner has been added as a joint manager of the managed object, and recording this information in the blockchain network.

10. In Paragraph 7, The above request step for adding a co-owner (S500) is, After the step of generating basic information for the managed object distributed identifier, the owner change request step proceeds to receive owner change request information, which is information requesting the transfer of ownership of the managed object to a third co-owner, through the owner terminal; and The above-mentioned step of generating modification information for managed distributed identifiers is, A method for providing a shareable decentralized ID service, characterized by, after the above-mentioned owner change request step, verifying the validity of both the signature information of the owner and the signature information of the third co-owner at the service server, generating third managed object distributed identifier modification information including the content that the ownership of the managed object has been transferred to the third co-owner, and recording it on the blockchain network.

Images