WO2022107336A1 - 情報処理プログラム、情報処理方法および情報処理装置 - Google Patents

情報処理プログラム、情報処理方法および情報処理装置 Download PDF

Info

Publication number
WO2022107336A1
WO2022107336A1 PCT/JP2020/043490 JP2020043490W WO2022107336A1 WO 2022107336 A1 WO2022107336 A1 WO 2022107336A1 JP 2020043490 W JP2020043490 W JP 2020043490W WO 2022107336 A1 WO2022107336 A1 WO 2022107336A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
management unit
identifier
data management
registered
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2020/043490
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
哲 西間木
誠之 福井
格 中川
出 佐藤
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fujitsu Ltd filed Critical Fujitsu Ltd
Priority to EP20962498.0A priority Critical patent/EP4250211A4/en
Priority to PCT/JP2020/043490 priority patent/WO2022107336A1/ja
Priority to JP2022563545A priority patent/JP7487793B2/ja
Publication of WO2022107336A1 publication Critical patent/WO2022107336A1/ja
Priority to US18/136,489 priority patent/US20230259646A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices

Definitions

  • An embodiment of the present invention relates to an information processing program, an information processing method, and an information processing apparatus.
  • the traffic related to the data synchronization of the blockchain will increase. If the traffic related to the blockchain increases in this way, the transaction performance of the blockchain may deteriorate, and the operation of the traceability system may be delayed.
  • One aspect is to provide information processing programs, information processing methods and information processing devices that can support the comfortable operation of traceability systems.
  • the information processing program causes the computer to execute the process of accepting, the process of registering in the first data management unit, and the process of registering in the second data management unit.
  • the process of accepting accepts trail data to be registered in the traceability system.
  • the identifier corresponding to the received trail data is registered in the first data management unit that is shared and managed between the organizations of the traceability system.
  • the information regarding the received trail data is registered in the second data management unit different from the first data management unit together with the identifier.
  • FIG. 1 is an explanatory diagram illustrating an outline of the traceability system according to the embodiment.
  • FIG. 2 is a block diagram showing a functional configuration example of the server device.
  • FIG. 3 is an explanatory diagram illustrating an outline of trail data registered in the traceability system according to the embodiment.
  • FIG. 4A is a flowchart showing an operation example relating to the setting of the access right.
  • FIG. 4B is a flowchart showing an operation example relating to the setting of the access right.
  • FIG. 5 is a flowchart showing an operation example of the server device.
  • FIG. 6 is an explanatory diagram illustrating an outline of the operation of the traceability system according to the embodiment.
  • FIG. 7A is a flowchart showing an operation example of the server device.
  • FIG. 7B is a flowchart showing an operation example of the server device.
  • FIG. 7C is a flowchart showing an operation example of the server device.
  • FIG. 8A is an explanatory diagram illustrating an outline of the operation of the traceability system according to the embodiment.
  • FIG. 8B is an explanatory diagram illustrating an outline of the operation of the traceability system according to the embodiment.
  • FIG. 9 is an explanatory diagram illustrating an example of a computer configuration.
  • FIG. 1 is an explanatory diagram illustrating an outline of the traceability system according to the embodiment.
  • each organization (organizations A, B, C 7) such as producers, processors, and distributors related to manufacturing supply chains, pharmaceuticals / foods, etc. is connected to a network 2 such as the Internet. It is connected so that it can communicate in both directions via.
  • each organization (organizations A, B, C %) registers historical information such as transaction details and processing details related to the product (manufacturing) as evidence (trail) data.
  • This trail data includes an identifier such as an identification number for identifying the current history information and an identifier such as an identification number indicating the previous history information.
  • the traceability system 1 ensures traceability (traceability) regarding the history of transaction details, processing details, and the like related to the product (manufacturing).
  • server devices 10A, 10B, 10C As an example of an information processing device that manages various information, a PC (Personal Computer) used by a user, and the like.
  • the terminal devices 20A, 20B, 20C The server devices 10A, 10B, 10C ... And the terminal devices 20A, 20B, 20C ...
  • the server device 10 and the terminal device 20 For each organization are referred to as the server device 10 and the terminal device 20 unless otherwise specified.
  • FIG. 2 is a block diagram showing a functional configuration example of the server device 10.
  • the server device 10 includes a communication unit 11, a control unit 12, a shared data management unit 13, an individual company data management unit 14, a content data management unit 15, and a transfer processing unit 16. Have.
  • the communication unit 11 is a processing unit that communicates with other devices (for example, a terminal device 20 or a server device 10 of another organization) via a communication cable or the like under the control of the control unit 12.
  • the communication unit 11 receives registration data to be registered as trail data such as transaction details and processing details related to the product (manufacturing) from the terminal device 20.
  • the registered data includes historical information such as transaction details and processing details, and content data indicating the substance of the transaction or processing (for example, text, moving image, etc.).
  • the communication unit 11 transmits a request to the server device 10 of another organization, receives a reply to the transmitted request, and the like. Further, the communication unit 11 communicates with the server device 10 of another organization regarding data synchronization between the organizations in the shared data management unit 13.
  • the control unit 12 is a processing unit that controls various operations in the server device 10.
  • the control unit 12 can be realized by a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or the like. Further, the control unit 12 can also be realized by hard-wired logic such as ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array).
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • control unit 12 when the control unit 12 receives the trail data to be registered in the traceability system 1 from the terminal device 20 via the communication unit 11, the control unit 12 performs a registration process for registering the received trail data. Further, when the control unit 12 receives the identifier related to the trail data to be acquired from the terminal device 20 via the communication unit 11, the control unit 12 performs a process of acquiring the trail data corresponding to the received identifier and outputting it to the terminal device 20.
  • the shared data management unit 13 is a processing unit that manages the shared data D13 shared between the organizations of the traceability system 1 (organizations A, B, C ...) for the trail data to be registered. Specifically, the shared data management unit 13 is distributed by distributed ledger technology such as blockchain by data synchronization with the server device 10 between participating organizations (organizations A, B, C %) via the communication unit 11. The shared data D13 is shared between participating organizations (organizations A, B, C %) via the ledger.
  • the individual company data management unit 14 is a processing unit that manages the individual company data D14 within the organization (individual company) without sharing the trail data to be registered between the organizations (organizations A, B, C ). ..
  • a known database such as MongoDB or CouchDB can be applied.
  • the content data management unit 15 does not share the trail data to be registered between the organizations (organizations A, B, C ...) like the individual company data management unit 14, but the content data D15 in the organization (individual company). It is a processing unit that manages.
  • a known Web server WebDAV or the like capable of storing / acquiring various media data and text data can be applied.
  • FIG. 3 is an explanatory diagram illustrating an outline of trail data registered in the traceability system 1 according to the embodiment.
  • the traceability system 1 separately registers and manages trail data (history information and contents) to be registered into shared data D13, individual company data D14, and content data D15.
  • the server device 10 registers the shared data D13 shared between the organizations in the shared data management unit 13 for the trail data to be registered, and the individual company data D14 managed in the organization is the individual company data management unit. Register in 14, and register the content data D15 related to the content in the content data management unit 15.
  • the shared data D13 is a history ID (shared data, an identifier of individual company data) corresponding to trail data and a hash (hash value of individual company data D14) which is summary information of contents registered as individual company data D14. And the ID of the previous history.
  • the traceability system 1 based on the history ID included in the shared data D13 and the ID of the previous history, the history of transaction details, processing details, etc. related to the product (manufacturing) can be obtained. Can be tracked. Further, in the traceability system 1, it is possible to verify whether or not the data has been tampered with by comparing the hash included in the shared data D13 with the hash obtained from the individual company data D14.
  • the individual company data D14 has the same history ID (identifier) as that registered in the shared data D13, history information (registration information from the terminal device 20), access information to the content data D15, and a summary of the content data D15. It has a hash (hash value of the content data D15) which is information.
  • the access information to the content data D15 is, for example, information indicating the storage destination of the content data D15 in the content data management unit 15 (URL of the storage destination, etc.).
  • the traceability system 1 can obtain the history information registered as trail data. Further, the traceability system 1 can access the content data D15 registered as trail data. Further, in the traceability system 1, it is possible to verify whether or not the data has been tampered with by comparing the hash included in the individual company data D14 with the hash obtained from the content data D15.
  • the content data D15 includes a content ID (identifier of content data) and data indicating content (registration information from the terminal device 20) such as moving images and texts related to transaction content, processing content, and the like.
  • the transfer processing unit 16 is a processing unit that performs processing related to the transfer of various data under the control of the control unit 12.
  • the transfer processing unit 16 when the transfer processing unit 16 receives an access request for data for which an identifier is specified from the terminal device 20, the transfer processing unit 16 identifies the organization that manages the data based on the identifier. Specifically, when the identifier has a configuration of an organization name + an identification number or the like, the transfer processing unit 16 identifies the organization that manages the data from the organization name included in the identifier. Further, when the identifier does not include the organization name or the like, the transfer processing unit 16 transmits the identifier to the server device 10 of each of the participating organizations (organizations A, B, C ...), And manages the information corresponding to the identifier. Identify the organization by asking if it is the original. Next, the transfer processing unit 16 transfers the access request to the server device 10 of the specified management source organization, and transfers the response corresponding to the access request to the terminal device 20.
  • the transfer processing unit 16 receives an access request for data managed in the organization by the individual company data management unit 14 or the content data management unit 15 from the server device 10 of another organization, the requested data. Is read from the individual company data management unit 14 or the content data management unit 15, and transferred to the requester via the communication unit 11. At this time, the transfer processing unit 16 verifies whether or not there is an access right set for each organization by referring to a preset access control list (ACL), and transfers data to the requester according to the verification result. You may go. For example, if the requesting organization has access rights to the data, the transfer processing unit 16 transfers the data to the requesting source. If there is no access right, the transfer processing unit 16 returns an error to the requester.
  • ACL preset access control list
  • FIG. 4A is a flowchart showing an operation example relating to the setting of the access right. Specifically, FIG. 4A is a flowchart showing an operation example of setting registration of an access control list for the individual company data management unit 14. FIG. 4B is a flowchart showing an operation example of setting registration of the access control list for the content data management unit 15.
  • the communication unit 11 issues an access right setting request specifying an individual company data ID indicating an organization and an access policy indicating the presence or absence of an access right to the organization. Receive from 20 (S10).
  • control unit 12 transmits the request for the access right setting request received by the communication unit 11 to the transfer processing unit 16 (S11).
  • the transfer processing unit 16 registers the access policy for the organization corresponding to the individual company data ID in the access control list based on the access right setting request (S12), and ends the processing.
  • the communication unit 11 issues an access right setting request from the terminal device 20 by designating a content ID indicating the content and an access policy indicating the presence or absence of the access right to the content.
  • control unit 12 transmits the request for the access right setting request received by the communication unit 11 to the transfer processing unit 16 (S21).
  • the transfer processing unit 16 registers the access policy for the content corresponding to the content ID in the access control list (S22) based on the access right setting request, and ends the processing.
  • FIG. 5 is a flowchart showing an operation example of the server device.
  • the communication unit 11 receives the history information and the content data D15 regarding the trail data to be registered from the terminal device 20 (S30). The communication unit 11 passes the received data to the control unit 12.
  • control unit 12 registers the received content data D15 in the content data management unit 15 (S31), and generates a content ID that serves as an identifier (access destination) of the registered content data D15 (S32).
  • the content ID may be, for example, a URL indicating a storage destination of the content data D15 stored in the content data management unit 15.
  • control unit 12 calculates the hash value of the content data D15 (S33), and registers the hash value of the content ID, the history information, and the content data D15 in the individual company data management unit 14 as the individual company data D14 (S34). ..
  • control unit 12 generates a history ID that serves as an identifier for the shared data D13 and the individual company data D14 regarding the trail data to be registered (S35).
  • the control unit 12 includes the generated history ID in the individual company data D14 and registers it in the individual company data management unit 14.
  • control unit 12 searches the individual company data management unit 14 using a part of the history information as a key, and corresponds to the transaction content and the processing content that are the first steps for the transaction content and the processing content in the trail data to be registered. Ask for history information. As a result, the control unit 12 acquires the history ID of the history information in the previous stage (S36).
  • control unit 12 calculates the hash value of the individual company data D14 (S37), and registers the shared data D13 including the history ID, the history ID of the previous stage, and the hash value of the individual company data D14 in the shared data management unit 13. (S38).
  • control unit 12 returns the history ID related to the trail data to be registered to the terminal device 20 via the communication unit 11 (S39), and ends the process.
  • FIG. 6 is an explanatory diagram illustrating an outline of the operation of the traceability system according to the embodiment.
  • the trail data is registered from the terminal device 20A of the organization A to the server device 10A in S30.
  • the server device 10A of the organization A performs a registration process for registering the received trail data (S31 to S38).
  • the shared data D13 including the history ID, the history ID in the previous stage, and the hash value of the individual company data D14 is registered in the shared data management unit 13. Further, the individual company data D14 including the history ID, the content ID, the history information, and the hash value of the content data D15 is registered in the individual company data management unit 14. Further, the content data D15 is registered in the content data management unit 15.
  • the shared data management unit 13 of the server device 10A shares the shared data D13 between the participating organizations via the distributed ledger by data synchronization with the server device 10 between the participating organizations (organizations A, B, C ...) (S40). ).
  • the shared data D13 in the shared data management unit 13 of the server device 10A and the shared data D13 in the shared data management unit 13 of the server device 10B become the same data.
  • FIG. 7A to 7B are flowcharts showing an operation example of the server device 10.
  • FIG. 7A is a flowchart showing an operation example of the server device 10 in the case of acquiring the corresponding shared data D13 using an identifier (history ID) as a key.
  • 7B and 7C are flowcharts showing an operation example of the server device 10 when the corresponding individual company data D14 and the content data D15 are acquired by using the identifier (history ID) as a key.
  • the communication unit 11 receives a shared data request using the history ID as a key from the terminal device 20 (S50). The communication unit 11 passes the received shared data request to the control unit 12.
  • control unit 12 acquires the shared data D13 corresponding to the designated ID from the shared data management unit 13 (S51). Next, the control unit 12 transmits the acquired shared data D13 to the terminal device 20 via the communication unit 11 (S52), and ends the process.
  • the communication unit 11 receives the individual company data request using the history ID as a key from the terminal device 20 (S60). The communication unit 11 passes the received individual company data request to the control unit 12.
  • control unit 12 transfers the request for the individual company data request to the transfer processing unit 16 (S61).
  • transfer processing unit 16 identifies the acquisition destination organization from the history ID included in the individual company data request, and transfers the request to the server device 10 of the specified organization (S62).
  • the transfer processing unit 16 acquisition destination transfer processing unit 16 of the server device 10 that received the request confirms the ACL and verifies the existence of the access right in the requesting organization (S63).
  • the transfer processing unit 16 of the acquisition destination acquires the individual company data D14 corresponding to the history ID included in the individual company data request from the individual company data management unit 14 of the acquisition destination. Return to the requester of the request.
  • the transfer processing unit 16 of the request source transfers the acquired individual company data D14 to the terminal device 20 (S64).
  • the communication unit 11 receives the content data request for which the content ID is specified from the terminal device 20 (S66). The communication unit 11 passes the received content data request to the control unit 12.
  • control unit 12 transfers the content data request request to the transfer processing unit 16 (S67).
  • transfer processing unit 16 identifies the acquisition destination organization from the content ID included in the content data request, and transfers the request to the server device 10 of the specified organization (S68).
  • the content ID is the address information indicating the storage destination of the content
  • the organization indicated by the address information is specified.
  • the transfer processing unit 16 acquisition destination transfer processing unit 16 of the server device 10 that received the request confirms the ACL and verifies the existence of the access right in the requesting organization (S69).
  • the transfer processing unit 16 of the acquisition destination acquires the content data D15 corresponding to the content ID included in the content data request from the content data management unit 15 of the acquisition destination, and requests the request. Return to the original.
  • the transfer processing unit 16 of the request source transfers the acquired content data D15 to the terminal device 20 (S70).
  • FIG. 8A and 8B are explanatory views illustrating an outline of the operation of the traceability system according to the embodiment.
  • the terminal device 20B of the organization B requests the server device 10B for shared data using the history ID as a key.
  • the server device 10B acquires the shared data D13 corresponding to the designated ID from the shared data management unit 13 and returns it to the terminal device 20B (S51, S52).
  • the terminal device 20B makes an individual company data request to the server device 10B using the ID in the shared data D13 as a key (S60).
  • the control unit 12 of the server device 10B transfers the request for the individual company data request to the transfer processing unit 16 (S61).
  • the transfer processing unit 16 identifies the corresponding organization based on the ID included in the individual company data request, and transfers the individual company data request request to the server device 10A of the specified organization A (S62). ..
  • the transfer processing unit 16 of the server device 10A acquires the individual company data D14 based on the ID included in the individual company data request and returns it to the request source server device 10B.
  • the transfer processing unit 16 of the server device 10B transfers the individual company data D14 returned from the server device 10A to the terminal device 20B (S64).
  • the terminal device 20B of the organization B the individual company data D14 registered in the organization A can be confirmed based on the ID.
  • the consistency of the data may be verified by comparing the hash included in the acquired shared data D13 with the hash calculated from the acquired individual company data D14.
  • the transfer processing unit 16 identifies the corresponding organization based on the content ID included in the content data request, and transfers the content data request request to the server device 10A of the specified organization A (S68).
  • the transfer processing unit 16 of the server device 10A acquires the content data D15 based on the ID included in the content data request and returns it to the request source server device 10B.
  • the transfer processing unit 16 of the server device 10B transfers the content data D15 returned from the server device 10A to the terminal device 20B (S70).
  • the terminal device 20B of the organization B can confirm the content data D15 registered in the organization A based on the ID.
  • the consistency of the data may be verified by comparing the hash included in the acquired individual company data D14 with the hash calculated from the acquired content data D15.
  • the server device 10 receives the trail data to be registered in the traceability system 1 from the terminal device 20.
  • the server device 10 registers the identifier corresponding to the received trail data in the shared data management unit 13 that is shared and managed between the organizations of the traceability system 1.
  • the server device 10 registers the information related to the received trail data in the individual company data management unit 14 together with the identifier corresponding to the trail data.
  • the identifier corresponding to the trail data to be registered is registered in the shared data management unit 13, and the information related to the trail data is registered in the individual company data management unit 14 together with the identifier, so that the shared data management is performed. It is possible to prevent an increase in traffic related to data synchronization between organizations in the unit 13. Therefore, in the traceability system 1, there is no possibility that the transaction performance of the shared data management unit 13 is deteriorated, and comfortable operation can be realized.
  • the shared data management unit 13 of the server device 10 shares data between organizations via the distributed ledger between the organizations of the traceability system 1.
  • the identifier corresponding to the trail data can be shared between the organizations via the distributed ledger.
  • the server device 10 registers the summary information of the information regarding the received trail data in the shared data management unit 13 together with the identifier corresponding to the trail data.
  • the traceability system 1 can verify the information related to the trail data registered in the individual company data management unit 14 based on the summary information registered in the shared data management unit 13.
  • the server device 10 registers the received trail data in the content data management unit 15, and manages the information indicating the access destination to the trail data registered in the content data management unit 15 together with the identifier corresponding to the trail data. Register in department 14. As a result, the traceability system 1 can access the trail data registered in the content data management unit 15 based on the information indicating the access destination registered in the individual company data management unit 14.
  • the server device 10 registers the summary information of the trail data registered in the content data management unit 15 in the individual company data management unit 14 together with the identifier corresponding to the trail data.
  • the traceability system 1 can verify the trail data registered in the content data management unit 15 based on the summary information registered in the individual company data management unit 14.
  • the server device 10 receives an identifier related to the trail data to be acquired from the identifiers registered in the shared data management unit 13. Then, the server device 10 identifies an organization that manages trail data corresponding to this identifier based on the received identifier. The server device 10 then requests the identified organization for trail data corresponding to the received identifier. As a result, the traceability system 1 can obtain trail data corresponding to the identifier based on the identifier registered in the shared data management unit 13.
  • the server device 10 when the server device 10 receives the request for the trail data corresponding to the identifier, is the requesting organization the organization to which the access right is granted based on the access right to the data preset for each organization? Verify whether or not. Then, the server device 10 transmits the trail data corresponding to the identifier to the requester based on the verification result. As a result, in the traceability system 1, access to the trail data can be controlled for each organization.
  • the traceability system 1 of the present embodiment access to the trail data can be controlled for each organization, but the traceability system 1 performs finer-grained access control for each user.
  • the control unit 12 of the server device 10 sets the access right for each user in the transfer processing unit 16 in the above-mentioned access right setting. Then, the control unit 12 performs user authentication processing as a preprocessing for receiving a request for trail data corresponding to an identifier from the terminal device 20, and assigns authentication information including user information by user authentication to the transfer processing unit 16. And notify.
  • the transfer processing unit 16 verifies whether or not the requesting user is a user to whom the access right is granted, based on the given authentication information.
  • the verification of the access right by the authentication information may be applied as a unit of attribute information given to the user, for example, role or project affiliation information, so as to enable access control in an organizational unit.
  • each component of each of the illustrated devices does not necessarily have to be physically configured as shown in the figure. That is, the specific form of distribution / integration of each device is not limited to the one shown in the figure, and all or part of them may be functionally or physically distributed / physically in any unit according to various loads and usage conditions. Can be integrated and configured.
  • various processing functions of the communication unit 11, the control unit 12, the shared data management unit 13, the individual company data management unit 14, the content data management unit 15, and the transfer processing unit 16 of the server device 10 are performed by the CPU (or MPU, MCU (or MPU, MCU). You may execute all or any part of it on a microcomputer (micro computer) such as Micro Controller Unit). In addition, various processing functions may be executed in whole or in any part on a program analyzed and executed by a CPU (or a microcomputer such as an MPU or MCU) or on hardware by wired logic. Needless to say, it's good. Further, various processing functions performed by the server device 10 may be executed by a plurality of computers in cooperation by cloud computing.
  • FIG. 9 is an explanatory diagram illustrating an example of a computer configuration.
  • the computer 200 has a CPU 201 that executes various arithmetic processes, an input device 202 that accepts data input, a monitor 203, and a speaker 204. Further, the computer 200 has a medium reading device 205 for reading a program or the like from a storage medium, an interface device 206 for connecting to various devices, and a communication device 207 for communicating with an external device by wire or wirelessly. Further, the computer 200 has a RAM 208 for temporarily storing various information and a hard disk device 209. Further, each part (201 to 209) in the computer 200 is connected to the bus 210.
  • the hard disk device 209 has the functional configurations described in the above embodiment (for example, communication unit 11, control unit 12, shared data management unit 13, individual company data management unit 14, content data management unit 15, and transfer processing unit 16).
  • the program 211 for executing various processes is stored. Further, various data 212 referred to by the program 211 are stored in the hard disk device 209.
  • the input device 202 receives, for example, an input of operation information from an operator.
  • the monitor 203 displays, for example, various screens operated by the operator. For example, a printing device or the like is connected to the interface device 206.
  • the communication device 207 is connected to a communication network such as a LAN (Local Area Network), and exchanges various information with an external device via the communication network.
  • LAN Local Area Network
  • the CPU 201 reads the program 211 stored in the hard disk device 209, expands it into the RAM 208, and executes the program. Various processes related to the unit 14, the content data management unit 15 and the transfer processing unit 16) are performed.
  • the program 211 may not be stored in the hard disk device 209.
  • the computer 200 may read and execute the program 211 stored in the readable storage medium.
  • the storage medium that can be read by the computer 200 is, for example, a CD-ROM, a DVD disk, a portable recording medium such as a USB (Universal Serial Bus) memory, a semiconductor memory such as a flash memory, a hard disk drive, or the like.
  • the program 211 may be stored in a device connected to a public line, the Internet, a LAN, or the like, and the computer 200 may read the program 211 from these and execute the program 211.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Bioethics (AREA)
  • Databases & Information Systems (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Tourism & Hospitality (AREA)
  • Development Economics (AREA)
  • Finance (AREA)
  • Accounting & Taxation (AREA)
  • Human Resources & Organizations (AREA)
  • Primary Health Care (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
PCT/JP2020/043490 2020-11-20 2020-11-20 情報処理プログラム、情報処理方法および情報処理装置 Ceased WO2022107336A1 (ja)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP20962498.0A EP4250211A4 (en) 2020-11-20 2020-11-20 PROGRAM, METHOD AND DEVICE FOR PROCESSING INFORMATION
PCT/JP2020/043490 WO2022107336A1 (ja) 2020-11-20 2020-11-20 情報処理プログラム、情報処理方法および情報処理装置
JP2022563545A JP7487793B2 (ja) 2020-11-20 2020-11-20 情報処理プログラム、情報処理方法および情報処理装置
US18/136,489 US20230259646A1 (en) 2020-11-20 2023-04-19 Storage medium, information processing method, and information processing device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2020/043490 WO2022107336A1 (ja) 2020-11-20 2020-11-20 情報処理プログラム、情報処理方法および情報処理装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/136,489 Continuation US20230259646A1 (en) 2020-11-20 2023-04-19 Storage medium, information processing method, and information processing device

Publications (1)

Publication Number Publication Date
WO2022107336A1 true WO2022107336A1 (ja) 2022-05-27

Family

ID=81708712

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2020/043490 Ceased WO2022107336A1 (ja) 2020-11-20 2020-11-20 情報処理プログラム、情報処理方法および情報処理装置

Country Status (4)

Country Link
US (1) US20230259646A1 (https=)
EP (1) EP4250211A4 (https=)
JP (1) JP7487793B2 (https=)
WO (1) WO2022107336A1 (https=)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2018173692A (ja) * 2017-03-31 2018-11-08 Ｎｅｃソリューションイノベータ株式会社 物品情報管理装置、システム、方法およびプログラム
WO2018225428A1 (ja) * 2017-06-05 2018-12-13 Ｎｅｃソリューションイノベータ株式会社 診療記録管理システム、装置、方法およびプログラム
JP2020046993A (ja) 2018-09-19 2020-03-26 富士通株式会社 情報処理装置、情報処理プログラムおよび情報処理方法
CN111127034A (zh) * 2019-12-02 2020-05-08 北京海益同展信息科技有限公司 商品的追溯方法、装置、客户端及存储介质
JP6762647B1 (ja) * 2019-08-09 2020-09-30 広志 谷本 プログラム、チャレンジ支援システム、チャレンジ支援方法、端末

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7743018B2 (en) * 2006-04-10 2010-06-22 International Business Machines Corporation Transient storage in distributed collaborative computing environments
US9514060B2 (en) * 2008-07-29 2016-12-06 Entropic Communications, Llc Device, system and method of accessing data stored in a memory
US20140244504A1 (en) * 2013-02-27 2014-08-28 Mastercard International Incorporated Methods and systems for processing electronic transactions and managing vehicle costs
US11062368B1 (en) * 2014-03-19 2021-07-13 Google Llc Selecting online content using offline data
EP3459029A1 (en) * 2016-05-20 2019-03-27 Moog Inc. Secure and traceable manufactured parts
EP3564845B1 (en) * 2016-12-28 2025-08-13 Takayuki Nakamura Data usage method, system, and program thereof employing blockchain network (bcn)
CN110832518B (zh) * 2017-04-19 2024-04-19 维萨国际服务协会 使用远程销售点系统进行安全交易的系统、方法和设备
US10944546B2 (en) * 2017-07-07 2021-03-09 Microsoft Technology Licensing, Llc Blockchain object interface
US10693662B2 (en) * 2018-02-22 2020-06-23 Idlogiq Inc. Methods for secure serialization of supply chain product units
US11488176B2 (en) * 2019-01-31 2022-11-01 Salesforce.Com, Inc. Systems, methods, and apparatuses for implementing certificates of authenticity of digital twins transacted onto a blockchain using distributed ledger technology (DLT)
US11972862B2 (en) * 2020-04-29 2024-04-30 Mend Medical, LLC Blockchain-based technologies for tracking product lifecycle

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2018173692A (ja) * 2017-03-31 2018-11-08 Ｎｅｃソリューションイノベータ株式会社 物品情報管理装置、システム、方法およびプログラム
WO2018225428A1 (ja) * 2017-06-05 2018-12-13 Ｎｅｃソリューションイノベータ株式会社 診療記録管理システム、装置、方法およびプログラム
JP2020046993A (ja) 2018-09-19 2020-03-26 富士通株式会社 情報処理装置、情報処理プログラムおよび情報処理方法
JP6762647B1 (ja) * 2019-08-09 2020-09-30 広志 谷本 プログラム、チャレンジ支援システム、チャレンジ支援方法、端末
CN111127034A (zh) * 2019-12-02 2020-05-08 北京海益同展信息科技有限公司 商品的追溯方法、装置、客户端及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4250211A4

Also Published As

Publication number Publication date
EP4250211A1 (en) 2023-09-27
US20230259646A1 (en) 2023-08-17
JPWO2022107336A1 (https=) 2022-05-27
EP4250211A4 (en) 2023-09-27
JP7487793B2 (ja) 2024-05-21

Similar Documents

Publication Publication Date Title
US10637926B2 (en) Methods and apparatuses for providing a data feed for internet of things
KR100950125B1 (ko) 트레이서빌리티 시스템, 트레이서빌리티 방법, 및트레이서빌리티 프로그램을 기록한 컴퓨터로 판독 가능한기록 매체
JP6268282B2 (ja) リクエスト処理方法および装置
US10341367B1 (en) System and method for inquiring IOC information by P2P protocol
JP7154842B2 (ja) クラウドベース文書の許可管理
US12093349B2 (en) Method for distributing certificate of right to use digital content, and computer program stored in medium in order to carry out method
TW201729121A (zh) 雲端服務伺服器及用來管理一雲端服務伺服器之方法
US20160162232A1 (en) Information processing system, information processor, non-transitory computer readable medium, and information processing method
CN112215609A (zh) 基于超级账本的房产用户身份认证方法、装置和电子设备
US10574785B2 (en) Methods and systems of identifying a device using strong component conflict detection
JP4858945B2 (ja) システムにアクセスする方法及びネットワークシステム
JP6733490B2 (ja) 開発支援システム、開発支援装置、応答制御プログラム、応答制御方法および応答制御装置
WO2022107336A1 (ja) 情報処理プログラム、情報処理方法および情報処理装置
WO2022107337A1 (ja) 情報処理プログラム、情報処理方法および情報処理装置
CN117896130B (zh) 一种工业互联网数据访问控制方法、装置、设备及介质
CN111260375B (zh) 一种服务处理方法和装置
JP2023030513A (ja) 通信システム、通信方法及びプログラム
KR102821020B1 (ko) 분산 식별자를 활용한 분산형 파일 시스템 기반의 데이터 거래 방법
CN115268939A (zh) 应用下发方法、装置、计算机设备和存储介质
US20080256608A1 (en) Linking Between Internet Subscription Websites
JP2002007347A (ja) Ｗｅｂコンテンツ配信方法及びシステム及びＷｅｂコンテンツ配信プログラムを格納した記憶媒体
EP4350533A1 (en) Computer-implemented method and system for processing a service with sovereign data
KR102736860B1 (ko) 온라인 쇼핑몰 교육을 위한 콘텐츠 제공 플랫폼 서비스 운영 방법, 장치 및 시스템
John et al. Storage Automation Using the Interplanetary File System and RFID for Authentication
CN120021187A (zh) 基于区块链的数据管理方法、装置及设备、介质、产品

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20962498

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022563545

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020962498

Country of ref document: EP

Effective date: 20230620