WO2020153053A1 - データベース管理サービス提供システム - Google Patents
データベース管理サービス提供システム Download PDFInfo
- Publication number
- WO2020153053A1 WO2020153053A1 PCT/JP2019/049536 JP2019049536W WO2020153053A1 WO 2020153053 A1 WO2020153053 A1 WO 2020153053A1 JP 2019049536 W JP2019049536 W JP 2019049536W WO 2020153053 A1 WO2020153053 A1 WO 2020153053A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- server
- storage area
- servers
- information storage
- query
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24553—Query execution of query operations
- G06F16/24561—Intermediate data storage techniques for performance improvement
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2471—Distributed queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/256—Integrating or interfacing systems involving database management systems in federated or virtual databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
- G06Q10/00—Administration; Management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
Definitions
- the present invention relates to a database management service providing system.
- distributed form technology or block chain technology
- centralized management or centralized management
- the present invention is particularly directed to a service providing system of a database management system for improving agility of information sharing (eg, information bank, information cooperation/association) between partners belonging to a supply chain.
- information sharing eg, information bank, information cooperation/association
- the supply chain will be described as an example. It should be noted that the supply chain can be read as multiple corporate groups that share information.
- Patent Document 1 discloses a mechanism for centrally managing meta information of contents in sharing information (contents such as files) stored in a distributed manner.
- Patent Document 2 discloses a mechanism for preventing duplicate storage of the same file by sharing meta information (file storage location information, etc.) of files stored in one or more distributed file servers by BC technology.
- Patent Document 3 discloses an example of an IT system that realizes a commercial transaction using BC technology.
- the plurality of servers include a first server and a second server.
- Each of the plurality of servers includes a shared information storage area for storing information shared with other servers.
- the plurality of servers operate to match the data in the shared information storage area.
- the first server manages a first local database.
- the second server generates query information for accessing the first local database, and stores the query information in the shared information storage area of the second server.
- the first server acquires the query information from the shared information storage area of the first server, and stores a result for the query information in the shared information storage area of the first server.
- the second server acquires the result from the shared information storage area of the second server.
- the outline of this embodiment is explained.
- the present embodiment describes a technology related to an IT infrastructure and a database management system that realizes information sharing between companies, for example.
- the system and method according to the embodiment is particularly suitable for a distributed database management system that realizes management of a business federation (eg, supply chain) and information sharing between companies belonging to the business federation.
- a business federation eg, supply chain
- the information shared between partners is stored in the database using the DBMS (database management system) program of the server owned by each partner.
- DBMS database management system
- the configuration information and management information required to use/execute each DBMS program are shared among the partners by the BC (block chain) technology.
- the partner can access each local database through the DBMS program in another server by joining the blockchain network (group sharing information by BC technology).
- OSS Open Source Software
- Another example of the method is the distributed method, in which multiple servers that share data hold mutual copies of the shared data.
- the distributed method it is possible to update the data in each server with a low load, but it is difficult to guarantee the data authenticity.
- Blockchain technology is a data sharing technology that adopts the latter distributed method.
- the blockchain technology In order to guarantee the authenticity of the shared data, the blockchain technology not only shares the updated data but also adds the electronic signature of the server or the user who updated the data together with the history of the data before the update. This prevents tampering by a third party and facilitates tampering detection.
- Blockchain technology provides data sharing with a lower load than the centralized method, and can provide the same degree of reliability as the centralized method.
- FIG. 1 illustrates the network configuration of this system.
- the servers 104, 105, 106, 107, 108, 109 held by one or more companies belonging to the supply chain 101 and the end user device 110 are connected to the Internet 102 and communicate via the Internet 102.
- the servers 104, 105, 106, 107, 108, and 109 held by one or more companies belonging to the supply chain 101 are further connected to the block chain network 103 and communicate via them.
- the Internet 102 includes a blockchain network 103.
- Each of the servers 104, 105, 106, 107, 108 and 109 has a Local DB (database) 407. However, in FIG. 1, only the Local DBs of the servers 104, 105, and 109 necessary for explaining the processing are described.
- the server 105 has a Server Application Program 401.
- a plurality of broken lines 118 schematically show the trust relationship between the servers in the blockchain network 103. There is a trust relationship between the servers to which the dashed line 118 connects.
- the blockchain platform (by the BC Service Program 402 in FIG. 2) realizes communication of BC transactions on the blockchain network 103 by a chain of data exchange between servers having a trust relationship shown by a broken line 118.
- the Server Application Program 401 of the server 105 operates from the End User Device 110. , Via the Internet 102.
- the Server Application Program 401 sends a query to the server 104 or 109 via the blockchain network 103 in order to obtain the data necessary for processing from the respective Local DB 407 of the other server 104 or 109. ..
- the Internet 102 includes blockchain networks 103, 203, and servers 104, 105, 109 and end user devices 110 connect to the Internet 102.
- the servers 104, 105, 109 connect to the blockchain network 103. None of the servers shown in FIG. 2 are connected to the blockchain network 203.
- Each of the servers 104, 105, and 109 has a BC Service Program 402, a DBMS Program 403, a Management DB 406, and a Local DB 407. Further, the server 105 has one or more Server Application Programs 401. The server 105 may have a plurality of Server Application Programs corresponding to different Local DBs.
- the end user device 110 has an End User Device Application Program 806.
- the End User Device Application Program 806 instructs the Server Application Program 401 to perform the operation 115 via the Internet 102.
- operation 115 is an access to the specified database.
- BC Service Program 402 is a program module that realizes a blockchain platform. Since this module is generally software published by OSS and uses common functions in the present embodiment, the description of the internal operation will be omitted in the following detailed description. In the present embodiment, common functions such as BC transaction communication and data multiplexing (copying) in multiple servers are mainly used.
- BC transaction is a transaction via a blockchain network.
- data shared between servers is multiplexed. That is, the server operates so that the data stored in the shared information storage area match.
- dedata of the Management DB 406 described later are multiplexed, and the server operates (communicates) so that the Management DB 406 matches.
- the ManagementDB 406 (storage area thereof) is an example of the shared information storage area.
- the DBMS Program 403 is a program module that adds a function for connecting to a block chain network to a program that realizes a general database management system (DBMS).
- DBMS database management system
- the function of query processing provided by the database management system is generally known, and thus detailed description will be omitted.
- a database management system that uses the SQL database language defined by the ISO standard can be used.
- DBMS Program 403 a data storage that does not adopt the SQL database language such as a key/value storage (Key Value Storage), an object storage (Object Storage), and a Web server (Web Server) is realized. You may use the program module which does.
- the ManagementDB 406 is a database or a storage that holds the configuration information and management information necessary for executing the DBMS Program 403.
- the configuration information is information necessary for starting the DBMS Program 403, and the management information is data that the DBMS Program 403 refers to for managing the Local DB 407.
- the data held in the Management DB 406 is multiplexed by the BC Service Program 402 in each Management DB 406 of a plurality of servers.
- the Local DB 407 is a storage that holds a database managed by the DBMS Program 403.
- the End User Device Application Program 806 is a program module for operating the Server Application Program 401 via the Internet 102.
- the internal hardware configuration of the one or more servers will be described with reference to FIG. 3 by taking the server 301 in the figure as an example.
- the server 301 has an MPU 302, a memory 303, a NIC 304 for connecting to the Internet 102, and a data bus 305 for connecting them.
- the MPU 302 is a microprocessor unit and is an example of a processor.
- the memory 303 is a main memory and is an example of a storage device.
- the NIC 304 is a network interface card that connects to the Internet 102.
- the data structure of the Memory 303 of the server 301 will be described with reference to FIG.
- the Memory 303 has a Server Application Program 401, a BC Service Program 402, a DBMS Program 403, a Server Configuration Data 405, a Management DB 406, and a Local DB 407.
- the Server Application Program 401 is a program module that realizes the business application used by the end user.
- BC Service Program 402 is a program module that realizes a blockchain platform.
- the DBMS Program 403 is a program module that realizes a database management system that participates in a blockchain network. The operation of each program module will be described in the following operation flow.
- the Server Configuration Data 405 is a data storage area that holds configuration information and management information unique to the server itself.
- the ManagementDB 406 (management database) is a data storage area that holds the configuration information and management information necessary for executing the DBMS Program 403.
- the management information required to use the DBMS Program 403 generally differs depending on the specifications of the adopted DBMS Program 403, but also includes common information.
- the common configuration information includes the data source name of the Local DB 407 managed by the DBMS Program 403, the database name, the database table name held by the Local DB 407, etc., and the Management DB 406 is held by some or all of them. be able to.
- the common management information includes the existence of a user who can use the DBMS Program 403, user account information that holds user authority, and the like. A part or all of these can be held in the Management DB 406.
- these configuration information and management information are arbitrary information required to use the DBMS Program 403, and the description of the processing of these information inside the DBMS Program 403 is omitted. ..
- the Local DB 407 (local database) is a data storage area that holds a database used by the Server Application Program 401 via the DBMS Program 403. Note that the Management DB 406 and Local DB 407 may be held in an externally connected storage device.
- the internal configuration of the Server Configuration Data 405 will be described with reference to FIG.
- the Server Configuration Data 405 has a Database ID 501, a Data Table "Peer List” 502, and a Data Table "Local Account List” 503.
- the Database ID 501 is a data storage area that holds identification information for distinguishing the Local DB of the own server.
- the server has one Local DB, but a plurality of Local DBs may be held.
- This identifier may be a serial number that does not duplicate in the system, or any information that does not duplicate such as the Internet address of each server.
- the Data Table "Peer List” 502 is a list of servers (nodes) that the local server has a trust relationship 118 with, and a list of other servers with which communication is performed.
- the update information to be shared in the blockchain network is transmitted to all the servers indicated by the Data Table "Peer List” 502. With Peer List 502, peer-to-peer communication with a trust relationship allows all servers in the blockchain network to share information.
- Data Table “Peer List” 502 is a data table having a column “URI” and a column “Peer ID”.
- the column “URI” may be the internet address of another server (a server having the trust relationship 118) with which the BC Service Program 402 of the own server communicates directly.
- the column “Peer ID” is server identification information on the blockchain network. For this server identification information, generally, a public key generated for each server based on the public key cryptosystem adopted by the blockchain platform is used.
- Data Table "Local Account Count” 503 is a list of tables managed by the own server.
- the record of the Data Table “Local Account Count” 503 has a column “Database ID”, a column “Table Name”, a column “BC Account ID”, and a column “Secret Key”.
- the column “Database ID” holds the Database ID of the server that holds the database table of the local database.
- the column “Table Name” holds the name of the database table.
- the column “BC Account ID” holds server identification information (public key) on the blockchain network.
- the column “Secret Key” holds the secret key of the server identification information on the blockchain network.
- the data structure of the ManagementDB 406 will be described with reference to FIG.
- the ManagementDB 406 is information shared between servers on the blockchain network.
- the update of the ManagementDB 406 on any server is reflected on all the servers on the blockchain network.
- Management DB406 (management database) is DB Table "DB Table List” 601, DB Table “Global Account List” 602, data storage area "BCTransactionPayloadforDBInquiry” storage area "BCTransactionTransaction” area 603. It has Payload for DB Inquiry Response "604 (query response storage area).
- DB Table "DB Table List” 601 is information about a database managed by a server on the blockchain network, and is a list of all tables on the blockchain network in this example. This allows a server on the blockchain network to generate query information for any server.
- the DB Table "DB Table List” 601 has a column “Database ID”, a column “Table Name”, and a column "BC Account ID”.
- DB Table "Global Account List” 602 is a list of all end users who connect to the blockchain network.
- the DB Table "Global Account List” 602 has a column "User ID” and a column "BC Account ID”.
- the column “User ID” holds identification information of the end user. This identification information may be a unique character string or a numerical value.
- the column “BC Account ID” is identification information on the blockchain network that is assigned to the end user, and holds a public key like the server identification information.
- the data storage area "BC Transaction Payload for DB Inquiry" 603 holds the query information to be sent to the DBMS Program 403 of another server via the blockchain network.
- the query information is updated when new query information is generated.
- the data storage area "BC Transaction Payload for DB Inquiry” 603 has a data field "Data Kind” 605 (data type information), a data field “DB Inquiry” 606 (query information), and a data field “Response Destination” 607 ( Respond destination) and data field “DB Inquiry ID” 608 (query identification information) are retained.
- the data field "Data Kind" 605 (data type information) holds identification information that identifies the type of data content of BC Transaction Payload.
- the BC transaction of the query holds identification information that means the query.
- the data field “Response Destination” 607 (response destination) holds the return destination of the query execution response of the DBMS Program 403.
- the return destination of this response may be the BC Account ID of the server, the URI (Internet address), or the like.
- the data field “Response Destination” 607 is destination information of the query result.
- the Response Destination 607 is referred to when the DBMS Program 403 directly changes the response to the query transmission source server (without going through the BC Service Program 402).
- the data field "DB Inquiry ID" 608 (query identification information) is identification information for identifying the query, and may be a unique serial number or transaction identification information on the block chain.
- the data storage area "BC Transaction Payload for DB Inquiry Response” 604 (query response storage area) holds response information for the query information sent to another server. For example, in the case of a search result, this response information holds the character strings "the return code, the result "1"".
- the data storage area "BC Transaction Payload for DB Inquiry Response” 604 (query response storage area) includes a data field "Data Kind” 605 (data type), a data field “DB Inquiry Response” 610 (query response information), and data. -Has field "DB Inquiry ID” 611 (query identification information).
- a data field "Data Kind” 605 (data type) holds identification information indicating a query response.
- the data field “DB Inquiry Response” 610 (query response information) holds the response information from the DBMS Program 403 by executing the query.
- the data field "DB Inquiry ID” 611 (query identification information) holds the DB Inquiry ID (value stored in the DB Inquiry ID 608) of the query executed by the DBMS Program 403, and the sender of the query sends the transmission. Be able to identify the query response to the query that the original sent.
- the DB Inquiry IDs 608 and 611 will be described as serial numbers for identifying queries, any identification information that does not overlap may be used, and even if the identification information of a BC transaction managed inside the BC Service Program 402 is used. Good. For example, when transmitting a BC transaction with the command geth provided by the blockchain platform Ethereum, the identification information can be acquired.
- the transmitting side can determine whether or not the response is for the transmitted BC transaction.
- the data structure of Local DB 407 will be described with reference to FIG. 7.
- the Local DB 407 shows an example of a database table used by the Server Application Program as an example for explaining the operation.
- the contents of the Server Application Program depend on the end user and the supply chain, so different database tables may be held accordingly.
- the Local DB 407 has, for example, a DB Table "AAA” 701 and a DB Table “BBB” 702.
- the record of DB Table “AAA” 701 has a column “Column_1” and a column “Column_2”.
- the record of DB Table “BBB” 702 has a column “Column_1” and a column “Column_2”.
- FIG. 8 shows an internal configuration example of the end user device 110.
- the end user device 110 has an MPU 801, a Memory 802, a NIC 803 connected to the Internet, a User IF 804 for inputting operations and information display by the end user, and a data bus 803 connecting them.
- the MPU 801 is a general microprocessor unit and is an example of a processor.
- the Memory 802 is a main memory and is an example of a storage device.
- the Memory 802 includes an End User Device Application Program 806 and a Device Configuration Data 807.
- the End User Device Application Program 806 is a program module for operating the Server Application Program 401.
- the Device Configuration Data 807 holds configuration information and management information unique to the End User Device 110.
- the NIC 803 is a network interface. It's a card.
- the User IF 804 is a module that displays information in line with the operation input of the end user.
- FIG. 9 shows the data storage area of the Memory 806 and the data configuration of the Device Configuration Data 806.
- the Device Configuration Data 806 has a Data Table "Application Accounting List” 901.
- Data Table "Application Accounting List” 901 is a list of Server Application Programs used by end users.
- the record of Data Table "Application Accounting Count List” 901 has a column "Application ID”, a column “BC Account ID”, a column “Secret Key”, and a column “URI”.
- the column “URI” holds the connection destination URL in the Server Application Program used by the user of the End User Device 806.
- the server or end user device can have a computer configuration.
- the processor can operate as various functional units by executing a program stored in the storage device.
- a sentence having a program as a subject can have a processor or a device including the processor as a subject.
- at least a part of the functions of the server and the end user device may be realized by an LSI different from the processor.
- the server and the end user device may be realized by a virtual machine provided by a cloud computing service.
- FIG. 10 shows the main data flow for accessing the data in the database table held by the local database 407 of the server 109 (first server) from the Server Application Program 401 of the server 105 (second server). Showing.
- broken-line rectangles indicating the BC Service Program 402 and the DBMS Program 403 indicate the functions of the programs 402 and 403, respectively.
- the Server Application Program 401 of the server 105 In response to the request from the end user device 110, the Server Application Program 401 of the server 105 generates a query to the local database 407 of the server 109.
- the Application Program 401 writes via the BC Service Program 402 of the server 105 to the BC Transaction Payload for DB Inquiry 603 (query storage area) of the Management DB of the server 105.
- the BC Service Program 402 held by a plurality of servers including the servers 105 and 109 transfers the packet "BC Transaction for DB Inquiry" 1001 based on the trust relationship 118 and updates the server 105's Management DB 406. It is reflected in Management DB406 of. In this example, the update of the storage areas 603 and 604 for the query will be described, but the update to the Management DB 406 in any server is reflected in the Management DB 406 of all the servers on the blockchain network.
- the DBMS Program 403 held by each server determines the contents of the BC Transaction Payload for DB Inquiry 603 (query storage area) held by the Management DB 406 via the BC Service Program 402, acquires the query information, and executes the query. To do.
- the DBMS Program 403 returns the execution response to the query transmission source indicated by the Response Destination 607 via the BC Service Program 402 or directly.
- the DBMS Program 403 decides which method to send back, based on the size of the data to be sent back. For example, when the data size is equal to or smaller than the specified value, the execution response is sent via BC Service Program 402 (blockchain network/protocol) to multiple servers including the query transmission source as a packet 1007 of the blockchain network. Transferred. When the data size is larger than the specified value, the execution response is returned as an out-band packet 1008 on the Internet 102 without being stored in the shared information storage area.
- BC Service Program 402 blockchain network/protocol
- FIG. 11 shows, as an example, a configuration in which the Local DB 407 managed by the DBMS Program 403 of the server 109 is duplicated on another server.
- This configuration example is suitable when the Local DB 407 holds a lot of long data.
- the DBMS Program 403 of the server 109 operates so that the servers 107 and 108 having the block chain network trust relationships 1109 and 1110 have a copy of the Local DB 407.
- the servers 107 and 108 are all the servers described in the Peer List 502 of the server 109.
- the servers 107 and 108 may be a part of the servers in the Peer List 502.
- the server 109 includes the Peer List 502 of the server 109 as an execution result in Payload.
- the server having the copy of Local DB 407 is a part of the server of Peer List 502, the list of the part of the servers is included.
- the Server Application Program 401 that has obtained the query response can operate so as to obtain the query result from another server that has a copy of the Local DB 407 of the server 109 in the Peer List 502 that the query response holds. Since query results can be obtained in parallel from one or more other servers, it is possible to shorten the query result acquisition time, reduce the performance peak due to IT resources, and improve the performance. The details of the operation of each program are explained below.
- FIG. 12 is an example of the operation flow of the Server Application Program 401.
- the Server Application Program 401 first executes the operation block 1201.
- operation block 1201 the database inquiry request from the End User Device 110 is received, and the operation block 1202 is executed.
- the Server Application Program 401 refers to the DB Table List 601 to generate a record that matches the database query and the serial number, and requests the BC Service Program 402 of the own server to send a transaction together with the record.
- the transaction transmission is a request to write information to BC Transaction Payload for DB Inquiry 603 of Management DB 406 of the own server.
- the Server Application Program 401 next executes the operation block 1203.
- the Server Application Program 401 requests the BC Service Program 402 of its own server to receive a transaction from the BC Transaction Payload for DB Inquiry Response 604 of the Management DB 406.
- the transaction reception request is an acquisition request for the content (information) of Payload 604.
- the Server Application Program 401 repeats the transaction reception request and executes the operation block 1204.
- the Server Application Program 401 sends the execution result held by the DB TransactionPayloadforDBInquiryResponse604 to the EndUserDevice110 and ends.
- the database management service can be provided to the End User Device 110.
- FIG. 13 is an example of the operation flow of BC Service Program 402.
- the BC Service Program 402 first executes the operation block 1301.
- the BC Service Program 402 determines whether the received request is a BC transaction transmission. If it is a BC transaction transmission, the BC Service Program 402 executes the operation block 1302. Otherwise, the BC Service Program 402 executes the action block 1304.
- the BC Service Program 402 writes the received data as the Payload of the BC Transaction Payload for DB Inquiry 603 in the Management DB 406 of its own server, and executes the operation block 1303.
- the contents of the change in the ManagementDB 406 of the own server are transmitted to the BC Service Program 402 of all the servers in the Peer List 502, and the processing ends.
- the BC Service Program 402 reflects the change contents of the Management BD 406 received from the BC Service Program 402 of another server in the Management DB 406 of the own server.
- the BC Service Program 402 transfers the changed contents to the BC Service Program 402 of the server in the Peer List 502, and executes the operation block 1305.
- the changed content of the Management BD 406 is propagated to all the servers in the blockchain network via the trust relationship indicated by the Peer List 502.
- the BC Service Program 402 determines whether the received request is a BC transaction reception. If it is a BC transaction reception, the BC Service Program 402 executes the operation block 1306. If not, the BC Service Program 402 ends the flow.
- the BC Service Program 402 responds to the program (call content) of the designated BC Transaction Payload for DB Inquiry Response 604 in the Management DB 406, and ends. Note that the BC Service Program 402 may wait for the specified Payload in the Management DB 406 to be updated.
- FIG. 14 is an operation flow example of the DBMS Program 403.
- the DBMS Program 403 first executes the operation block 1401.
- the operation block 1401 requests the BC Service Program 402 to receive a transaction regarding the BC Transaction Payload for DB Inquiry 603 in the Management DB 406 of its own server.
- the DBMS Program 403 acquires the data type, database inquiry, and serial number from the BC Transaction Payload for DB Inquiry 603. If the data type is not “DBMS”, the DBMS Program 403 requests repeated transaction reception and executes the operation block 1402.
- the DBMS Program 403 refers to the Local Account Count 503 and determines whether the access destination is a table managed by itself. When the table is not a table managed by itself, the DBMS Program 403 requests repeated transaction reception and executes the operation block 1402.
- the DBMS Program 403 executes the above database inquiry to the Local DB 407, obtains the result, and executes operation block 1403.
- the DBMS Program 403 combines the result and the serial number held by the BC Transaction Payload for DB Inquiry 603, and sets the BC Transaction TransmissionPay ancestor4 for the BCTransactionPayloadforDBinquiry4 as the BCTransactionPayloadforDBinquiry4 in the Management DB 406. Request and finish.
- FIG. 15 is an operation flow of the End User Device Application Program 806.
- the End User Device Application Program 806 first executes the operation block 1501.
- the End User Device Application Program 806 sends the database query input via the User IF to, for example, the Server Application Program 401 (accessing to DB(X)) of the server 105, and executes the operation block 1502. ..
- the End User Device Application Program 806 displays the response from the Server Application Program 401 (accessing to DB(X)) of the server 105 via the User IF and ends.
- the server of the company participating in the supply chain can access the database of another server participating in the blockchain network by participating in the blockchain network. This eliminates the need to add a program to the DBMS program to support the server application program, facilitates system construction for participation in the supply chain, and is expected to improve business agility.
- the data held by the local database and the management database may be encrypted or data compressed, and in that case, it is sufficient if there is a means for decrypting the encryption or compression before the data is processed.
- RDBMS relational database management system
- the query information in that case is expressed in the SQL language.
- the Key Value Storage or Object Storage
- the query information may be the one described in REST Application Programming Interface.
- the query information may be expressed in HTML (Hyper Text Markup Language).
- HTML Hyper Text Markup Language
- the query information may be used according to the specifications of the adopted database management system program.
- the access to the database of this embodiment can be applied to a system different from the supply chain.
- the database of another server can be accessed quickly and easily.
- the system may share information for providing the database management service by a technique different from the blockchain technique.
- BC Transaction Payload for DB Inquiry 603 a data format of a process control block adopted to manage and control the process in a general operating system program may be adopted.
- the query is also shared with other Servers via the BC Service Program 402.
- the other server launches a process for executing the query based on the contents of the process control block.
- the "process” described here may be read as “job”, “task”, or “thread”. Further, the "process control block” may be read as an “event control block” used in a general network balancer program.
- FIG. 16 shows a system configuration example of the second embodiment. This system configuration example differs from the system configuration example of the first embodiment in that the Local DB 407 is not managed by the DBMS Program 403, but is managed by the blockchain platform. FIG. 16 shows the main data flow in the system configuration example of this embodiment.
- the server 109 is connected to the two block chain networks 103 and 203.
- the Relay Program 404 operates instead of the DBMS Program 403 in the first embodiment.
- the Relay Program 404 is a program module that mediates BC transactions between different blockchain networks. The functions of the Relay Program 404 are shown in the broken line rectangle indicating the Relay Program 404.
- the server 109 further has a BC Service Program 412 for a BC transaction in the block chain network 203, in addition to the configuration of the first embodiment.
- the server 109 has a Server Configuration dATA 405 and a Management DB 406 for each of the blockchain networks 103 and 203.
- the ManagementDB 406 for the blockchain network 203 is a second shared information storage area.
- the DB Table List 601 is common to the block chain networks 103 and 203, and shows both tables.
- FIG. 17 shows an example of the operation flow of the Relay Program 404.
- the access destination of the query from the blockchain network 103 is the Local DB of the server (third server) included in the blockchain network 203, and is transferred to the blockchain network 203.
- the query response from the blockchain network 203 is transferred to the blockchain network 103.
- the Relay Program 404 first executes the operation block 1701. In operation block 1701, the Relay Program 404 requests the BC Service Program 402 of the blockchain network 103 to receive a transaction regarding the BC Transaction Payload for DB Inquiry 603 in the Management DB 406.
- the Relay Program 404 acquires the data type, the database inquiry, and the serial number from the relevant BC Transaction Payload for DB Inquiry 603. Until the information from the BC Transaction Payload for DB Inquiry 603 is obtained, the Relay Program 404 requests repeated transaction reception and executes the operation block 1702.
- the Relay Program 404 transfers the query held by the BC Transaction Payload for DB Inquiry 603 to another block chain network 203 as a BC transaction, and executes the operation block 1703.
- the Relay Program 404 refers to the DB Table List 601 of the blockchain network 203 and determines that the access destination is the Local DB of the blockchain network 203.
- the Relay Program 404 requests the BC Service Program 412 of the block chain network 203 to send a transaction in order to write the acquired query in the BC Transaction Payload for DB Inquiry 603 of the Management DB 406 for the block chain network 203.
- the BC Service Program 412 sends the update of the Management DB 406 to the server of the Peer List 502 of the blockchain network 203.
- the Relay Program 404 requests the BC Service Program 412 of the blockchain network 203 to receive a BC transaction from the BC Transaction Payload for DB Inquiry Response 604 for the blockchain network 203.
- the Relay Program 404 acquires a response to the above query (result of the above transaction transmission).
- the Relay Program 404 generates a record that combines the result of the above transaction transmission and the serial number held by the BC Transaction Payload for DB Inquiry 603 of the blockchain network 103.
- the Relay Program 404 writes the record to the BC Transaction Payload for DB inquiry Response 604 in the Management DB 406 of the blockchain network 103. Specifically, the Relay Program 404 requests the BC Service Program 402 of the blockchain network 103 to send a transaction for the record. After that, the Relay Program 404 ends.
- the present embodiment shares information with different blockchain networks (other information sharing groups using different blockchain technologies), so that the query information is applied to program module applications that employ different blockchain technologies.
- -It is equipped with a Relay Program that converts to a programming interface (API).
- the server application program can operate without considering the difference, and the server application program can be modified. It is unnecessary, and it is easy to deal with various tasks.
- the present invention is not limited to the above-described embodiments, but includes various modifications.
- the above-described embodiments have been described in detail in order to explain the present invention in an easy-to-understand manner, and are not necessarily limited to those having all the configurations described.
- a part of the configuration of a certain embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of a certain embodiment.
- other configurations can be added/deleted/replaced.
- each of the above-mentioned components, functions, processing units, etc. may be realized in hardware by designing a part or all of them with, for example, an integrated circuit.
- each of the above-described configurations, functions, and the like may be realized by software by a processor interpreting and executing a program that realizes each function.
- Information such as a program, a table, and a file that realizes each function can be placed in a memory, a hard disk, a recording device such as SSD (Solid State Drive), or a recording medium such as an IC card or an SD card.
- the control lines and information lines shown are those that are considered to be necessary for explanation, and not all the control lines and information lines on the product are necessarily shown. In practice, it may be considered that almost all the configurations are connected to each other.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Computational Linguistics (AREA)
- Business, Economics & Management (AREA)
- Software Systems (AREA)
- Marketing (AREA)
- Mathematical Physics (AREA)
- Fuzzy Systems (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- Probability & Statistics with Applications (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Strategic Management (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
データ・フィールド"DB Inquiry ID"608(クエリ識別情報)は、クエリを識別するための識別情報で、重複のない連番や、ブロックチェーン上のトランザクション識別情報でよい。
Claims (8)
- 複数のサーバ及び1以上のデータベースを含む、データベース管理サービス提供システムであって、
前記複数のサーバは、
第1のサーバと、
第2のサーバと、を含み、
前記複数のサーバの各サーバは、他のサーバと共有する情報を格納する共有情報格納領域を含み、
前記複数のサーバは、前記共有情報格納領域のデータを一致させるように動作し、
前記第1のサーバは、第1のローカル・データベースを管理し、
前記第2のサーバは、
前記第1のローカル・データベースへのアクセスのためのクエリ情報を生成し、
前記クエリ情報を、前記第2のサーバの前記共有情報格納領域に格納し、
前記第1のサーバは、
前記第1のサーバの前記共有情報格納領域から前記クエリ情報を取得し、
前記クエリ情報に対する結果を前記第1のサーバの前記共有情報格納領域に格納し、
前記第2のサーバは、前記第2のサーバの前記共有情報格納領域から前記結果を取得する、データベース管理サービス提供システム。 - 請求項1に記載のデータベース管理サービス提供システムであって、
前記共有情報格納領域は、前記複数のサーバが管理する複数のデータベースについての情報を格納している、データベース管理サービス提供システム。 - 請求項1に記載のデータベース管理サービス提供システムであって、
前記複数のサーバの各サーバは、前記複数のサーバにおいて通信を行う他のサーバのリストを保持し、
前記複数のサーバの各サーバは、前記共有情報格納領域における更新を前記リストに示される前記他のサーバに送信する、データベース管理サービス提供システム。 - 請求項1に記載のデータベース管理サービス提供システムであって、
前記第2のサーバは、
エンド・ユーザ・デバイスからの指示に応答して前記クエリ情報を生成し、
前記第2のサーバの前記共有情報格納領域から取得した前記結果を前記エンド・ユーザ・デバイスに送信する、データベース管理サービス提供システム。 - 請求項1に記載のデータベース管理サービス提供システムであって、
前記第1のサーバは、
前記第1のサーバの前記共有情報格納領域から、前記第1のローカル・データベースに対する第2のクエリ情報を取得し、前記第2のクエリ情報は、クエリ結果の送り先情報を含み、
前記第2のクエリ情報の結果を前記第1のサーバの前記共有情報格納領域に格納することなく、前記送り先情報が示すサーバに前記第2のクエリ情報の結果を送信する、データベース管理サービス提供システム。 - 請求項1に記載のデータベース管理サービス提供システムであって、
前記複数のサーバにおける前記第1のサーバと異なる1以上のサーバが、前記第1のローカル・データベースの複製を管理し、
前記第1のサーバは、
前記第1のサーバの前記共有情報格納領域から、前記第1のローカル・データベースに対する第3のクエリ情報を取得し、
前記1以上のサーバの情報を含む前記第3のクエリ情報の結果を、前記第1のサーバの前記共有情報格納領域に格納する、データベース管理サービス提供システム。 - 請求項1に記載のデータベース管理サービス提供システムであって、
前記共有情報格納領域は第1の共有情報格納領域であり、
前記第1のサーバは、
第2のデータベース管理サービス提供システムに含まれ、
第2のデータベース管理サービス提供システムの他のサーバと共有する情報を格納する第2の共有情報格納領域を含み、
前記第1のサーバの前記第1の共有情報格納領域から、前記第2のデータベース管理サービス提供システムに含まれる第3のサーバが管理するローカル・データベースに対する第4のクエリ情報を取得し、
前記第1のサーバの前記第2の共有情報格納領域に前記第4のクエリ情報を格納し、
前記第1のサーバの前記第2の共有情報格納領域から前記第4のクエリ情報に対する結果を取得し、
前記第4のクエリ情報に対する結果を前記第1のサーバの前記第1の共有情報格納領域に格納する、データベース管理サービス提供システム。 - 複数のサーバ及び1以上のデータベースを含むシステムにより実行される方法であって、
前記複数のサーバは、
第1のサーバと、
第2のサーバと、を含み、
前記複数のサーバの各サーバは、他のサーバと共有する情報を格納する共有情報格納領域を含み、
前記複数のサーバは、前記共有情報格納領域のデータを一致させるように動作し、
前記方法は、
前記第1のサーバが、第1のローカル・データベースを管理し、
前記第2のサーバが、前記第1のローカル・データベースへのアクセスのためにクエリ情報を生成し、
前記第2のサーバが、前記クエリ情報を、前記第2のサーバの前記共有情報格納領域に格納し、
前記第1のサーバが、前記第1のサーバの前記共有情報格納領域から前記クエリ情報を取得し、
前記第1のサーバが、前記クエリ情報に対する結果を前記第1のサーバの前記共有情報格納領域に格納し、
前記第2のサーバが、前記第2のサーバの前記共有情報格納領域から前記結果を取得する、方法。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020217015530A KR102598619B1 (ko) | 2019-01-23 | 2019-12-18 | 데이터베이스 관리 서비스 제공 시스템 |
US17/420,075 US11797556B2 (en) | 2019-01-23 | 2019-12-18 | Database management service provision system |
BR112021013970-2A BR112021013970A2 (pt) | 2019-01-23 | 2019-12-18 | Sistema de provisão de serviço de gerenciamento de banco de dados, e, método para ser executado por um sistema incluindo uma pluralidade de servidores e um ou mais bancos de dados |
CN201980080426.3A CN113168405A (zh) | 2019-01-23 | 2019-12-18 | 数据库管理服务提供*** |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2019-009349 | 2019-01-23 | ||
JP2019009349A JP7071938B2 (ja) | 2019-01-23 | 2019-01-23 | データベース管理サービス提供システム |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020153053A1 true WO2020153053A1 (ja) | 2020-07-30 |
Family
ID=71735698
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2019/049536 WO2020153053A1 (ja) | 2019-01-23 | 2019-12-18 | データベース管理サービス提供システム |
Country Status (6)
Country | Link |
---|---|
US (1) | US11797556B2 (ja) |
JP (1) | JP7071938B2 (ja) |
KR (1) | KR102598619B1 (ja) |
CN (1) | CN113168405A (ja) |
BR (1) | BR112021013970A2 (ja) |
WO (1) | WO2020153053A1 (ja) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP7409297B2 (ja) | 2020-12-23 | 2024-01-09 | 株式会社デンソー | 情報管理方法、及び情報管理プログラム |
TW202322137A (zh) * | 2021-10-04 | 2023-06-01 | 日商日本電氣股份有限公司 | 管理方法、管理系統及電子健康紀錄系統 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005275937A (ja) * | 2004-03-25 | 2005-10-06 | Fujitsu Ltd | P2pネットワークシステム |
JP2007219634A (ja) * | 2006-02-14 | 2007-08-30 | Dat Japan Kk | 分散型データベースシステム及びデータベースの分散管理方法 |
JP2011159106A (ja) * | 2010-02-01 | 2011-08-18 | Nippon Telegr & Teleph Corp <Ntt> | データベースシステム |
Family Cites Families (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6044374A (en) | 1997-11-14 | 2000-03-28 | Informatica Corporation | Method and apparatus for sharing metadata between multiple data marts through object references |
KR100436431B1 (ko) | 2001-06-21 | 2004-06-16 | (주)와이즈피어 | 피어투피어 네트워크상에서의 협업적인 정보 교환시스템 |
US8868467B2 (en) * | 2002-10-23 | 2014-10-21 | Oleg Serebrennikov | Method for performing transactional communication using a universal transaction account identifier assigned to a customer |
US7996888B2 (en) * | 2002-01-11 | 2011-08-09 | Nokia Corporation | Virtual identity apparatus and method for using same |
US7010553B2 (en) * | 2002-03-19 | 2006-03-07 | Network Appliance, Inc. | System and method for redirecting access to a remote mirrored snapshot |
JP2005276094A (ja) | 2004-03-26 | 2005-10-06 | Hitachi Ltd | 分散ストレージ装置のファイル管理方法及び分散ストレージシステム並びにプログラム |
US8683566B1 (en) * | 2009-09-08 | 2014-03-25 | Sprint Communications Company L.P. | Secure access and architecture for virtual private sites |
KR101511098B1 (ko) | 2011-10-10 | 2015-04-10 | 네이버 주식회사 | 분산된 컨테이너들을 사용하여 데이터를 관리하는 시스템 및 방법 |
US8904231B2 (en) * | 2012-08-08 | 2014-12-02 | Netapp, Inc. | Synchronous local and cross-site failover in clustered storage systems |
US9268834B2 (en) * | 2012-12-13 | 2016-02-23 | Microsoft Technology Licensing, Llc | Distributed SQL query processing using key-value storage system |
CN104166738A (zh) * | 2014-09-04 | 2014-11-26 | 北京国双科技有限公司 | 数据库查询处理的方法及装置 |
US9870562B2 (en) | 2015-05-21 | 2018-01-16 | Mastercard International Incorporated | Method and system for integration of market exchange and issuer processing for blockchain-based transactions |
GB2561722B (en) * | 2015-10-23 | 2021-10-20 | Kodiak Networks Inc | System and method for content messaging |
US10965649B2 (en) * | 2015-10-30 | 2021-03-30 | Fatpipe, Inc. | Persistent data communication sessions across WAN |
US10430485B2 (en) * | 2016-05-10 | 2019-10-01 | Go Daddy Operating Company, LLC | Verifying character sets in domain name requests |
CN107786621B (zh) * | 2016-08-31 | 2020-10-16 | 阿里巴巴集团控股有限公司 | 一种用户信息管理方法、访问处理方法及装置和*** |
US10225078B2 (en) * | 2017-02-09 | 2019-03-05 | International Business Machines Corporation | Managing a database management system using a blockchain database |
JP2018190227A (ja) | 2017-05-09 | 2018-11-29 | 野田 真一 | ネットワーク分散型重複排除ファイルストレージシステム |
CN107273455B (zh) * | 2017-05-31 | 2020-12-18 | 深圳前海微众银行股份有限公司 | 区块链数据访问方法和装置 |
CN107315786B (zh) * | 2017-06-12 | 2020-12-11 | 腾讯科技(深圳)有限公司 | 业务数据存储方法及装置 |
CN108334595B (zh) * | 2018-01-31 | 2020-08-04 | 泰康保险集团股份有限公司 | 数据共享方法及装置 |
KR101893729B1 (ko) * | 2018-03-28 | 2018-10-04 | 주식회사 마크로젠 | 복수의 블록체인에 기반한 데이터 공유 방법 |
CN108717443B (zh) * | 2018-05-17 | 2020-06-05 | 京东数字科技控股有限公司 | 数据共享方法、区块链***和计算机可读存储介质 |
CN109257412A (zh) * | 2018-08-10 | 2019-01-22 | 中国联合网络通信集团有限公司 | 一种数据共享方法及装置 |
CN109191355B (zh) * | 2018-08-21 | 2022-02-25 | 严治 | 一种基于区块链的创伤数据共享*** |
-
2019
- 2019-01-23 JP JP2019009349A patent/JP7071938B2/ja active Active
- 2019-12-18 KR KR1020217015530A patent/KR102598619B1/ko active IP Right Grant
- 2019-12-18 BR BR112021013970-2A patent/BR112021013970A2/pt unknown
- 2019-12-18 WO PCT/JP2019/049536 patent/WO2020153053A1/ja active Application Filing
- 2019-12-18 US US17/420,075 patent/US11797556B2/en active Active
- 2019-12-18 CN CN201980080426.3A patent/CN113168405A/zh active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005275937A (ja) * | 2004-03-25 | 2005-10-06 | Fujitsu Ltd | P2pネットワークシステム |
JP2007219634A (ja) * | 2006-02-14 | 2007-08-30 | Dat Japan Kk | 分散型データベースシステム及びデータベースの分散管理方法 |
JP2011159106A (ja) * | 2010-02-01 | 2011-08-18 | Nippon Telegr & Teleph Corp <Ntt> | データベースシステム |
Also Published As
Publication number | Publication date |
---|---|
US11797556B2 (en) | 2023-10-24 |
CN113168405A (zh) | 2021-07-23 |
BR112021013970A2 (pt) | 2021-09-21 |
US20220129473A1 (en) | 2022-04-28 |
JP2020119207A (ja) | 2020-08-06 |
KR20210082481A (ko) | 2021-07-05 |
KR102598619B1 (ko) | 2023-11-07 |
JP7071938B2 (ja) | 2022-05-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9727590B2 (en) | Data management and indexing across a distributed database | |
US7437388B1 (en) | Protecting data for distributed applications using cooperative backup agents | |
US9690839B2 (en) | Computer architectures using shared storage | |
US9462056B1 (en) | Policy-based meta-data driven co-location of computation and datasets in the cloud | |
US20070011136A1 (en) | Employing an identifier for an account of one domain in another domain to facilitate access of data on shared storage media | |
US20160292249A1 (en) | Dynamic replica failure detection and healing | |
JP5193056B2 (ja) | 無線装置の最新データを維持するための方法及びシステム | |
JP5360978B2 (ja) | ファイルサーバ、及びファイルサーバにおけるファイル操作通知方法 | |
US20070005604A1 (en) | Supporting replication among a plurality of file operation servers | |
US10440106B2 (en) | Hosted file sync with stateless sync nodes | |
WO2011108695A1 (ja) | 並列データ処理システム、並列データ処理方法及びプログラム | |
JPH04310188A (ja) | 文書/画像ライブラリのためのライブラリサービス方法 | |
JP2005535947A (ja) | 異なるタイプのバックエンド・データ・ストアにアクセスするためのシステムおよび方法 | |
JP2007025785A (ja) | データベース処理方法、システム及びプログラム | |
US20080288498A1 (en) | Network-attached storage devices | |
US8611542B1 (en) | Peer to peer key synchronization | |
US7899998B1 (en) | Conflict avoidance in data store replication | |
WO2020153053A1 (ja) | データベース管理サービス提供システム | |
US7373393B2 (en) | File system | |
JP2004318744A (ja) | 高可用性を提供するデータベース処理方法 | |
JP2004302564A (ja) | ネームサービス提供方法及びその実施装置並びにその処理プログラム | |
JP4222065B2 (ja) | 情報システムにおけるデータアクセス方法および情報システム | |
US11157454B2 (en) | Event-based synchronization in a file sharing environment | |
US7509302B2 (en) | Device, method and program for providing a high-performance storage access environment while issuing a volume access request including an address of a volume to access | |
JP2001318905A (ja) | ディスク共有型分散サーバシステム |
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: 19911179 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 20217015530 Country of ref document: KR Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112021013970 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112021013970 Country of ref document: BR Kind code of ref document: A2 Effective date: 20210715 |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19911179 Country of ref document: EP Kind code of ref document: A1 |