KR102456040B1 - Method for preventing redundant storage of electronic records between distributed recording systems by using object access token - Google Patents

Abstract

Disclosed is a method for preventing duplicate storage of electronic records between distributed record systems using entity access tokens. a record production system of a plurality of institutions producing records objects of each institution; managing, by the records management/correction system of each institution, storage, viewing, and disposal of record objects produced in the records production system of each institution; The records management/correction system of each institution uses the object access token issued by the block chain network system for records management to distribute the produced record object so that it is not stored redundantly in the record storage of each institution and store it in the record storage of the institution. performing a process of storing, performing a process of viewing a record object already stored in the record storage of each institution, or performing a process of discarding a record object already stored in the record storage of each institution constitutes the step. According to the method for preventing duplicate storage of electronic records between distributed record systems using the entity access token described above, the entity access token is used to determine the redundancy of each record entity for each unit of record entity of each institution, and register and utilize it in the blockchain network. By being configured, there is an effect that multiple organizations can smoothly utilize overlapping data and prevent redundant storage.

Description

Method for preventing duplicate storage of electronic records between distributed record systems using object access tokens

The present invention relates to a method for preventing duplicate storage of electronic records between distributed record systems using an entity access token.

Many institutions each own and manage data generated by their own institutions.

Since it is not easy to share databases or to build an integrated database between institutions, smooth data integration is not being achieved.

Countless records, data, and documents are created and poured out every moment, but it is almost impossible for each institution to check whether these data are duplicate data.

Accordingly, there is a need for a method for storing and managing a large number of such data without overlapping with each other, and for using the data in an integrated manner.

Unexamined Patent Publication No. 10-2020-0117718 Laid-Open Patent Publication No. 10-2020-0119112

An object of the present invention is to provide a method for preventing duplicate storage of electronic records between distributed record systems using an entity access token.

According to the object of the present invention described above, there is provided a method for preventing duplicate storage of electronic records between distributed record systems using an entity access token, the method comprising: a record production system of a plurality of institutions producing record objects of each institution; managing, by the records management/correction system of each institution, storage, viewing, and disposal of record objects produced in the records production system of each institution; The records management/correction system of each institution uses the object access token issued by the block chain network system for records management to distribute the produced record object so that it is not stored redundantly in the record storage of each institution and store it in the record storage of the institution. performing a process of storing, performing a process of viewing a record object already stored in the record storage of each institution, or performing a process of discarding a record object already stored in the record storage of each institution can

And the records management/correction system of each institution uses the object access token issued by the block chain network system for records management to distribute the produced record object so that it is not stored redundantly in the record storage of each institution, and the record storage of the institution The step of performing a process of storing to a record storage, performing a process of reading a record object already stored in the record storage of each institution, or performing a process of discarding a record object already stored in the record storage of each institution includes the steps of: / requesting, by the storage object viewing request module of the management correction system, viewing of the storage object pre-stored in the record storage; requesting, by the access token validation module of the record storage, validation of the access token of the archived object requested to be viewed in the archived object reading request module; verifying, by the signature certificate validation module of the record management blockchain network system, the validity of the signature certificate of the access token for which validation is requested in the access token validation request module; when the validity is verified by the signature certificate validation module, the archive object delivery module of the record storage reads the archive object from the object storage module and delivers it to the records management/correction system of the institution; The archived object viewing module of the record management/correction system may be configured to include the step of receiving the archived object from the archived object delivery module and performing the browsing.

And the records management/correction system of each institution uses the object access token issued by the block chain network system for records management to distribute the produced record object so that it is not stored redundantly in the record storage of each institution, and the record storage of the institution The step of performing a process of storing to a record storage, performing a process of reading a record object already stored in the record storage of each institution, or performing a process of discarding a record object already stored in the record storage of each institution includes the steps of: requesting, by the archive object disposal request module of the management/correction system, to discard the archive object pre-stored in the record storage; requesting, by the object reference number confirmation request module of the records management/correction system, to check the number of referenced objects by the records management/correction system of another institution with respect to the archived objects requested to be discarded by the archived object disposal request module; confirming, by the object reference number confirmation module of the record storage, the number of object references by the object reference number confirmation request module; When the number of object references confirmed by the object reference number confirmation module is greater than 1, the step of reducing the number of reference number reduction module of the record management blockchain network system by 1; When the number of object references confirmed by the object reference count confirmation module is greater than 1, the meta-information discard/object maintenance module of the record management/remediation system discards the meta-information of the archived object and maintains the storage of the archived object. to do; When the number of object references confirmed by the object reference count confirmation module is 0, the meta information discard/object deletion request module of the record management/revision system discards the meta information of the corresponding archived object and requests deletion of the corresponding archived object to do; The object deletion module of the record storage may be configured to include deleting the corresponding archived object according to the request of the meta-information discard/object deletion request module.

According to the method for preventing duplicate storage of electronic records between distributed record systems using the entity access token described above, the entity access token is used to determine the redundancy of each record entity for each unit of record entity of each institution, and register and utilize it in the blockchain network. By being configured, there is an effect that multiple organizations can smoothly utilize overlapping data and prevent redundant storage.

1 is a block diagram of a system for preventing duplicate storage of electronic records between distributed recording systems using an individual access token according to an embodiment of the present invention.
2 is a detailed configuration diagram of a system for preventing duplicate storage of electronic records between distributed recording systems using an individual access token according to an embodiment of the present invention.
3 is a flowchart of a method for preventing duplicate storage of electronic records between distributed recording systems using an entity access token according to an embodiment of the present invention.
4 to 6 are detailed flowcharts of a method for preventing duplicate storage of electronic records between distributed recording systems using an individual access token according to an embodiment of the present invention.

Since the present invention can have various changes and can have various embodiments, specific embodiments are illustrated in the drawings and will be described in detail in the detailed content for carrying out the invention. However, this is not intended to limit the present invention to specific embodiments, and should be understood to include all modifications, equivalents and substitutes included in the spirit and scope of the present invention. In describing each figure, like reference numerals have been used for like elements.

Terms such as first, second, A, and B may be used to describe various elements, but the elements should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component. and/or includes a combination of a plurality of related listed items or any of a plurality of related listed items.

When a component is referred to as being “connected” or “connected” to another component, it may be directly connected or connected to the other component, but it is understood that other components may exist in between. it should be On the other hand, when it is said that a certain element is "directly connected" or "directly connected" to another element, it should be understood that the other element does not exist in the middle.

The terms used in the present application are only used to describe specific embodiments, and are not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly dictates otherwise. In the present application, terms such as “comprise” or “have” are intended to designate that a feature, number, step, operation, component, part, or combination thereof described in the specification exists, but one or more other features It is to be understood that this does not preclude the possibility of the presence or addition of numbers, steps, operations, components, parts, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in a commonly used dictionary should be interpreted as having a meaning consistent with the meaning in the context of the related art, and should not be interpreted in an ideal or excessively formal meaning unless explicitly defined in the present application. does not

Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram of a system for preventing duplicate storage of electronic records between distributed record systems using an individual access token according to an embodiment of the present invention, and FIG. 2 is a distributed record using an entity access token according to an embodiment of the present invention. It is a detailed configuration diagram of a system for preventing duplicate storage of electronic records between systems.

1 and 2, a system for preventing duplicate storage of electronic records between distributed records systems using an entity access token according to an embodiment of the present invention includes a record production system 100, a records management/correction system 200, and a record It may be configured to include a storage 300 , a blockchain network system 400 for records management, and an integrated records storage 500 .

Here, the records production system 100 , the records management/correction system 200 , and the records storage 300 are systems each held by various institutions, and may be operated separately in each institution to manage the data of the institution. .

Hereinafter, a detailed configuration will be described.

The multiple institution's record production system 100 may be configured to produce each institution's record object.

Here, the recording object may be composed of one object in a unit of file, or may be composed of recording content that is a bundle of several objects. Here, the criterion for determining the redundancy for preventing redundant storage of records may be an individual unit.

The records management/correction system 200 may be configured to manage the storage, viewing, and disposal of record objects produced in the records production system 100 of each institution.

The records management/correction system 200 of each institution can prevent duplicate storage and manage the records of each institution through the blockchain network system 400 for records management based on the block chain.

The record management/correction system 200 includes an entity unique information extraction module 201, meta information registration module 202, meta information/access talk storage module 203, archive object reading request module 204, archive object viewing module 205, a storage object disposal request module 206, an object reference count confirmation request module 207, a meta-information disposal/object maintenance module 208, and a meta-information disposal/object deletion request module 209. can

The record storage 300 is a record storage provided for each institution, and records objects can be stored, viewed, and discarded by the records management/correction system 200 of the institution.

The record storage 300 may be configured to include an object storage module 301 , an access token validation module 302 , an archive object delivery module 303 , a reference count check module 304 , and an object deletion module 305 . have.

The block chain network system 400 for records management may be configured to interoperate with the records management/correction system 200 of each institution to prevent duplication of entities of each institution, and to manage viewing and disposal.

Specifically, the block chain network system 400 for record management determines whether the record object produced by the record production system 100 for each institution is the same, and prevents duplicated storage in the record storage 300 for each institution. , it may be configured to control the viewing and disposal of record objects pre-stored in the record storage 300 for each institution.

The block chain network system 400 for record management includes the same entity verification module 401, the number of reference initial setting module 402, the entity access token issuance module 403, the reference number increase module 404, and the signature certificate validation module 405 , may be configured to include a reference count reduction module 406 .

The integrated record storage 500 is a configuration that can be additionally provided in the present invention, and is a configuration in which objects stored in the record storage 200 of each institution are integrated and stored without duplication.

The integrated record storage 500 may be additionally provided, or the record storage 200 may be utilized as it is by preventing objects stored in the existing record storage 200 of each institution from overlapping with each other.

Even when the integrated record storage 500 is additionally provided, the original document of each entity may be configured to be stored as it is in the record storage 200 of each institution.

In the following, each process related to recording, viewing, and disposal of an object will be specifically described.

First, the object recording process is described.

The object recording process includes the object unique information extraction module 201 of the records management/correction system 200 , the meta information registration module 202 , the meta information/access talk storage module 203 , and the object storage module of the record storage 300 . 301, the same entity confirmation module 401 of the block chain network system 400 for record management, the reference number initial setting module 402, the entity access token issuance module 403, and the reference number increase module 404 participate can

Hereinafter, a detailed configuration will be described.

The entity unique information extraction module 201 may be configured to extract entity unique information from a recorded entity produced by the record production system 100 .

Here, the entity unique information is a unique information value capable of discriminating a recording entity, that is, an original text file, and may be configured to use a hash value for the entire entity. Although the probability of overlapping hash values is close to zero, in order to remove even a small probability, at least two or more pieces of information such as the size of an object or a hash value for a certain section among the objects may be combined and used.

In addition, when one original document is composed of multiple entities, individual unique information can be extracted for each of the multiple entities.

The same entity identification module 401 may be configured to check whether a corresponding recorded entity is already stored in the record storage 300 of each institution using the entity unique information extracted by the entity unique information extraction module 201 . The same entity checking module 401 may check whether hash values match.

The reference number initial setting module 402 may be configured to initially set the number of references of the corresponding recorded object to 1 when the corresponding recorded object is not already stored as a result of the identification of the same object checking module 401 . Here, multiple institutions may create the same record object, which can be expressed as the number of references.

The entity access token issuance module 403 may be configured to issue an entity access token for a recorded entity in which the number of references is initially set by the reference number initial setting module 402 . The object access token may include path information to access the object.

The meta information registration module 202 generates meta information by using the entity unique information extracted by the entity unique information extraction module 201 when the record object produced by the record production system 100 is the first recorded entity. and may be configured to register.

The meta information/access talk storage module 203 may be configured to store the meta information registered in the meta information registration module 202 and the entity access token issued by the entity access token issuance module 404 .

The object storage module 301 may be configured to store the recorded object produced by the record production system 100 when the recorded object is the first recorded object.

The reference number increase module 404 may be configured to increase the number of references of the corresponding recorded object by one when the corresponding recorded object is already stored as a result of the identification of the same object checking module 401 .

Next, the browsing process of archived records will be described.

The archival record viewing process includes the archival object view request module 204 of the records management/remediation system 200 , the archival object view module 205 , the access token validation module 302 of the record storage 300 , and the archival object delivery The module 303, the signature certificate validation module 405 of the blockchain network system 400 for record management may participate.

Hereinafter, a detailed configuration will be described.

The archive object view request module 204 may be configured to request a view of an archive object pre-stored in the record storage 300 .

The access token validation module 302 may be configured to request validation of the access token of the storage entity requested to be viewed by the archive object view request module 204 .

The signing certificate validation module 405 may be configured to verify the validity of the signing certificate of the access token for which validation is requested in the access token validation request module 302 .

The archived object delivery module 303 reads the corresponding archived object from the object storage module 301 when the validity is verified by the signature certificate validation module 405 and transmits it to the records management/correction system 200 of the institution. can be configured.

The archived object viewing module 205 may be configured to receive the archived object from the archived object delivery module 303 and perform browsing.

Next, a process for discarding archived records will be described.

In the process of disposing of archived records, the archived object disposal request module 206 of the records management/correction system 200, the object reference count check request module 207, the meta-information disposal/object maintenance module 208, and the meta-information disposal/object The deletion request module 209, the reference count confirmation module 304 of the record storage 300, the object deletion module 305, and the reference count reduction module 406 of the record management blockchain network system 400 can participate. .

Hereinafter, a detailed configuration will be described.

The archive object disposal request module 206 may be configured to request the disposal of an archive object pre-stored in the record storage 300 .

The object reference count confirmation request module 207 may be configured to request confirmation of the number of object references by the records management/remediation system 200 of another institution for the archived object requested to be destroyed in the archive object disposal request module 206 . can

The number of references confirmation module 304 may be configured to confirm the number of object references by the object reference number confirmation request module 207 .

The number of references reduction module 406 may be configured to decrease the number of object references by one when the number of object references confirmed by the object reference number confirmation module 304 is greater than one. Decrease the number of references by the institution that requested the decommissioning by one.

The meta-information discard/object maintenance module 208 is configured to discard the meta-information of the corresponding archived object and maintain the storage of the corresponding archived object when the number of object references confirmed by the object reference count confirmation module 304 is greater than 1 can be Even if meta information is discarded, the entity itself may be maintained.

The meta-information discard/object deletion request module 209 is configured to discard the meta-information of the corresponding archived object and request deletion of the corresponding archived object when the number of object references confirmed by the object reference count check module 304 is 0 can be It is safe to delete the archived object itself, as no agency records the number of references to that record object.

The object deletion module 305 may be configured to delete the corresponding archived object according to the request of the meta-information discard/object deletion request module 209 .

3 is a flowchart of a method for preventing duplicate storage of electronic records between distributed recording systems using an entity access token according to an embodiment of the present invention.

Referring to FIG. 3 , the record production system 100 of a plurality of institutions produces a record object of each institution ( S100 ).

Next, the records management/correction system 200 of each institution manages the storage, viewing, and disposal of the record object produced in the record production system 100 of each institution ( S200 ).

Next, the records management/correction system 200 of each institution transfers the produced record object to the record storage 300 of each institution using the object access token issued by the block chain network system 400 for records management. Perform a process of distributing and storing in the record storage 300 of the respective institution so as not to be stored redundantly, or perform a process of reading the record object already stored in the record storage 300 of each institution, or the record storage of each institution A process of discarding the record object already stored in 300 is performed (S300).

4 to 6 are detailed flowcharts of a method for preventing duplicate storage of electronic records between distributed recording systems using an individual access token according to an embodiment of the present invention.

4 shows the recording process of an entity.

Referring to FIG. 4 , the entity unique information extraction module 201 of the records management/correction system 200 extracts entity unique information from the recorded entity produced by the record production system 100 ( S311 ).

Next, the same entity confirmation module 401 of the block chain network system 400 for record management uses the entity unique information extracted from the entity unique information extraction module 201, and the corresponding record object is stored in the record storage 300 of each institution. ) is already stored in (S312).

Next, as a result of the confirmation of the same object confirmation module 401, if the corresponding record object is not already stored, the reference number of the record management block chain network system 400 initial setting module 402 sets the reference number of the record object is initially set to 1 (S313).

Next, the entity access token issuance module 403 of the block chain network system 400 for record management issues an entity access token for the record entity whose reference number is initially set by the reference number initial setting module 402 (S314) ).

Next, when the recorded object produced by the record production system 100 is the first recorded object, the meta information registration module 202 of the records management/correction system 200 performs the object unique information extraction module 201 . Meta information is generated and registered using the extracted entity unique information (S315).

Next, when the record object produced by the record production system 100 is the first record object, the meta information/access talk storage module 203 of the records management/correction system 200 performs the meta information registration module 202 ), the registered meta information and the entity access token issued by the entity access token issuing module 404 are stored (S316).

Next, when the record object produced by the record production system 100 is the first record object, the object storage module 301 of the record storage 300 stores the record object (S317).

Next, as a result of the verification of the same entity confirmation module 401, if the corresponding record object is already stored, the reference increase module 404 of the block chain network system 400 for record management sets the reference number of the record object to 1 increase (S318).

5 shows the viewing process of an entity.

Referring to FIG. 5 , the archived object view request module 204 of the record/management correction system 200 requests to view the archived object pre-stored in the record storage 300 ( S321 ).

Next, the access token validation module 302 of the record storage 300 requests validation of the access token of the archived object requested to be viewed by the archived object view request module 204 ( S322 ).

Next, the signature certificate validation module 405 of the block chain network system 400 for record management verifies the validity of the signature certificate of the access token for which validation is requested in the access token validation request module 302 (S323) ).

Next, when the validity is verified in the signature certificate validation module 405 , the archive object delivery module 303 of the record storage 300 reads the archive object from the object storage module 301 and manages the records of the institution / Transmits to the correction system 200 (S324).

Next, the archived object viewing module 205 of the record management/correction system 200 receives the archived object from the archived object delivery module 303 and browses ( S325 ).

6 shows the disposition process of an entity.

Referring to FIG. 6 , the archived object disposal request module 206 of the records management/correction system 200 requests to discard the archived object pre-stored in the record storage 300 ( S331 ).

Next, the record management/correction system 200 of another institution determines the number of object reference number confirmation request module 207 of the records management/correction system 200 for the archived object requested to be destroyed in the archive object disposal request module 206 . It requests confirmation of the number of object references by (S332).

Next, the object reference number confirmation module 304 of the record storage 300 checks the number of object references by the object reference number confirmation request module 207 (S333).

Next, if the number of object references confirmed by the object reference number confirmation module 304 is greater than 1, the reference number reduction module 406 of the block chain network system 400 for record management reduces the object reference number by 1 make it (S334).

Next, when the number of object references confirmed by the object reference number confirmation module 304 is greater than 1, the meta-information disposal/object maintenance module 208 of the records management/correction system 200 returns the meta-information of the corresponding archived object. Discard and maintain the storage of the storage object (S335).

Next, when the number of object references confirmed by the object reference number confirmation module 304 is 0, the meta information disposal/object deletion request module 209 of the record management/correction system 200 transmits the meta information of the corresponding archived object. Discard and request deletion of the corresponding archived object (S336).

Next, the object deletion module 305 of the record storage 300 deletes the corresponding archived object according to the request of the meta-information discard/object deletion request module 209 (S337).

Although described with reference to the above embodiments, those skilled in the art can understand that various modifications and changes can be made to the present invention without departing from the spirit and scope of the present invention as set forth in the following claims. There will be.

100: records production system 200: records management/correction system
300: history storage
400: Blockchain Network System for Records Management
500: Unified record storage 201: Object unique information extraction module
202: meta information registration module 203: meta information / access torque storage module
204: archive object view request module 205: archive object view module
206: Archive object disposal request module 207: Object reference count check request module
208: Meta-information discard/object maintenance module
209: Meta information disposal/object deletion request module
301: object storage module 302: access token validation module
303: Archive object forwarding module 304: Object reference count check module
305: Delete object module 401: Same object check module
402: Reference number initial setting module 403: Entity access token issuance module
404: increment reference module 405: signature certificate validation module
406: Reference count reduction module

Claims (4)

the multiple institution's record production system 100 producing each institution's record object;
managing, by the records management/correction system 200 of each institution, storage, viewing, and disposal of record objects produced in the records production system 100 of each institution;
The records management/correction system 200 of each institution uses the object access token issued by the block chain network system 400 for records management to duplicate the produced record object in the record storage 300 of each institution. Perform a process of distributing and storing in the record storage 300 of the respective institution, or performing the process of reading the record object already stored in the record storage 300 of each institution, or the record storage 300 of each institution performing a process of destroying recorded objects already stored in
The records management/correction system 200 of each institution uses the object access token issued by the block chain network system 400 for records management to duplicate the produced record object in the record storage 300 of each institution. Perform a process of distributing and storing in the record storage 300 of the respective institution, or performing the process of reading the record object already stored in the record storage 300 of each institution, or the record storage 300 of each institution The steps to perform the process of discarding recorded objects already stored in
extracting, by the entity unique information extraction module 201 of the records management/correction system 200, entity unique information from the recorded entity produced by the record production system 100;
The same entity identification module 401 of the block chain network system 400 for record management uses the entity unique information extracted from the entity unique information extraction module 201, and the corresponding record object is stored in the record storage 300 of each institution Steps to check if it is already stored in
As a result of checking the same object confirmation module 401, if the corresponding record object is not already stored, the reference number initial setting module 402 of the record management block chain network system 400 sets the reference number of the record object initial setting to 1,
issuing, by the entity access token issuance module 403 of the block chain network system 400 for record management, an entity access token for the record entity whose reference number is initially set by the reference number initial setting module 402;
When the recorded object produced by the record production system 100 is the first recorded object, the meta information registration module 202 of the records management/correction system 200 performs the object unique information extraction module 201 Creating and registering meta information using the extracted entity unique information;
When the record object produced by the record production system 100 is the first record object, the meta information/access talk storage module 203 of the records management/correction system 200 performs the meta information registration module 202 . storing the registered meta information and the entity access token issued by the entity access token issuing module 404;
when the record object produced by the record production system 100 is the first record object, the object storage module 301 of the record storage 300 stores the record object;
As a result of the verification of the same entity confirmation module 401, if the corresponding record object is already stored, the reference number increase module 404 of the record management block chain network system 400 increases the reference number of the record object by 1 comprising the steps of
requesting, by the archival object view request module 204 of the record management/correction system 200, to view the archival object pre-stored in the record storage 300;
requesting, by the access token validation module 302 of the record storage 300, validation of the access token of the archived entity requested to be viewed in the archived object view request module 204;
verifying, by the signature certificate validation module 405 of the record management blockchain network system 400, the validity of the signature certificate of the access token for which validation is requested in the access token validation request module 302;
When the validity of the signature certificate validation module 405 is verified, the archived object delivery module 303 of the record storage 300 reads the archived object from the object storage module 301 and manages the records of the corresponding institution. /passing to the calibration system 200;
Entity access token, characterized in that the archived object viewing module (205) of the records management/remediation system (200) is configured to further include the step of receiving the archived object from the archived object delivery module (303) and performing the browsing A method for preventing duplicate storage of electronic records between distributed record systems using
delete delete The method of claim 1,
The records management/correction system 200 of each institution uses the object access token issued by the block chain network system 400 for records management to duplicate the produced record object in the record storage 300 of each institution. Perform a process of distributing and storing in the record storage 300 of the respective institution, or performing the process of reading the record object already stored in the record storage 300 of each institution, or the record storage 300 of each institution The steps to perform the process of discarding recorded objects already stored in
requesting, by the archived object disposal request module (206) of the records management/correction system (200), to discard the archived object pre-stored in the record storage (300);
The object reference number confirmation request module 207 of the records management/correction system 200 sends the records management/correction system 200 of another institution with respect to the archived object requested to be discarded by the archived object disposal request module 206. requesting confirmation of the number of object references by
confirming, by the object reference number confirmation module (304) of the record storage (300), the number of object references by the object reference number confirmation request module (207);
When the number of object references confirmed by the object reference number confirmation module 304 is greater than 1, the reference number reduction module 406 of the record management block chain network system 400 reduces the number of object references by 1. step;
When the number of object references confirmed by the object reference number confirmation module 304 is greater than 1, the meta-information discard/object maintenance module 208 of the record management/correction system 200 stores the meta information of the corresponding archived object. discarding and maintaining storage of the archived object;
When the number of object references confirmed by the object reference number confirmation module 304 is 0, the meta information discard/object deletion request module 209 of the record management/correction system 200 retrieves the meta information of the corresponding archived object. discarding and requesting deletion of the archived object;
The object access token, characterized in that the object deletion module (305) of the record storage (300) is configured to include the step of deleting the corresponding stored object according to the request of the meta-information discard/object deletion request module (209). A method for preventing duplicate storage of electronic records between distributed record systems.

Images