WO2019208211A1

WO2019208211A1 - Server device

Info

Publication number: WO2019208211A1
Application number: PCT/JP2019/015520
Authority: WO
Inventors: 淳小野寺; 義和中村
Original assignee: 日本電気株式会社
Priority date: 2018-04-27
Filing date: 2019-04-09
Publication date: 2019-10-31
Also published as: JPWO2019208211A1

Abstract

A server device connected to a data provider device and a data requestor device via a network is provided with a database and a providing unit. The database stores information relating to an interface to acquire data from the data provider device. Upon reception of a first request for requesting an acquisition of the data from the data requestor device, the providing unit acquires the data from the data provider device by a second request created on the basis of the information relating to the interface stored in the database, and transmits the data to the data requestor device.

Description

Server device

The present invention relates to an information processing system, a server device, a method thereof, and a program.

An information processing system for utilizing public data such as documents for open innovation has been proposed.

For example, in the information processing system described in Patent Document 1, a data provider device, a data requester device, and a server device are connected to each other through a network. When the server apparatus receives the public data from the data provider apparatus, the server apparatus registers it in the database, and registers information such as the document ID and the document provider ID in the document information table. When the data requester device requests acquisition of data, the server device retrieves the corresponding public data from the database and transmits it to the data requester device.

In the information processing system described in Non-Patent Document 1, a data provider device, a data requester device, and a data catalog site (server device) are connected to each other through a network. The data catalog site registers the meta information of the public data in the data catalog so that the public data provided by a plurality of data provider devices can be searched across the field. The data requester device searches the data catalog to obtain an API (Application Programming Interface) of the data provider device that provides the desired public data. Then, the data requester device acquires the public data from the corresponding data provider device by executing the acquired API.

JP2016-207163

In the information processing system described in Patent Document 1, a server device acquires public data provided from a data provider device in advance and stores it in a database. For this reason, a database having a capacity corresponding to the amount of public data is required, which increases the cost of the server device. In contrast, the information processing system described in Non-Patent Document 1 is a server device because meta information of public data is registered in a data catalog site, and the contents of the data are held by the data provider device. The construction cost of the data catalog site is small. However, in the information processing system described in Non-Patent Document 1, a data requester must individually execute an API of a data provider device that provides public data desired to be acquired. As a result, the load on the data requester increases.

An object of the present invention is to provide a server device that solves the above-described problems.

A server device according to an aspect of the present invention is provided.
A server device connected to a data provider device and a data requester device through a network,
A database for storing interface information for acquiring data from the data provider device;
When a first request for obtaining the data is received from the data requester device, the data is obtained from the data provider device by a second request created based on the interface information stored in the database. And a providing unit that obtains and sends the data to the data requester apparatus.

A method according to another aspect of the present invention includes:
A method executed by a server device connected to a data provider device and a data requester device through a network and having a database for storing interface information for acquiring data from the data provider device,
When a first request for obtaining the data is received from the data requester device, the data is obtained from the data provider device by a second request created based on the interface information stored in the database. Obtain and send to the data requester device.

A computer-readable recording medium according to another aspect of the present invention is
A computer connected to a data provider device and a data requester device through a network and having a database for storing interface information for acquiring data from the data provider device.
When a first request for obtaining the data is received from the data requester device, the data is obtained from the data provider device by a second request created based on the interface information stored in the database. A program for acquiring and sending the data requester device is recorded.

An information processing system according to another embodiment of the present invention includes:
A server apparatus according to an embodiment of the present invention, and a data provider apparatus and a data requester apparatus connected to the server apparatus through a network.

The present invention having the above-described configuration can reduce the load on the data requester and reduce the cost of the server device.

1 is a block diagram of an information processing system according to a first embodiment of the present invention. It is a figure which shows an example of the data catalog which the server apparatus which concerns on the 1st Embodiment of this invention has. It is a flowchart which shows an example of operation | movement of the registration part of the server apparatus which concerns on the 1st Embodiment of this invention. It is a flowchart which shows an example of operation | movement of the search part of the server apparatus which concerns on the 1st Embodiment of this invention. It is a flowchart which shows an example of operation | movement of the provision part of the server apparatus which concerns on the 1st Embodiment of this invention. 5 is a sequence chart illustrating an example of an operation of a server device when a data access API is called from a data requester device in the first embodiment of the present invention. 7 is a sequence chart showing another example of the operation of the server device when the data access API is called from the data requester device in the first embodiment of the present invention. 6 is a sequence chart showing another example of the operation of the server device when the data access API is called from the data requester device in the first embodiment of the present invention. 6 is a sequence chart showing still another example of the operation of the server device when the data access API is called from the data requester device in the first embodiment of the present invention. 1 is a conceptual diagram of a scoring support system to which an information processing system according to a first embodiment of the present invention is applied. 1 is a conceptual diagram of an active learning degree measurement system to which an information processing system according to a first embodiment of the present invention is applied. 1 is a conceptual diagram of a remote lesson support system to which an information processing system according to a first embodiment of the present invention is applied. 1 is a block diagram of an information processing system according to a first embodiment of the present invention.

Next, embodiments of the present invention will be described in detail with reference to the drawings.
[First embodiment]
FIG. 1 is a block diagram of an information processing system according to the first embodiment of the present invention. Referring to FIG. 1, the information processing system according to the first exemplary embodiment of the present invention includes a server device 100, a plurality of data provider devices 140-1 to 140-m, and a plurality of data requester devices 150-1. 150-n and a network 160 that interconnects them.

The data provider devices 140-1 to 140-m are information processing devices such as personal computers and smartphones that are used by a person who holds data such as documents, images, and voices to release the held data to a third party. It is. The format of the data is arbitrary. For example, the data is in JSON format. However, a data format other than the JSON format, for example, XML may be used. Each of the data provider devices 140-1 to 140-m includes at least one API that is an interface for externally operating a function of disclosing data held therein. The specification of the API held by each data provider device 140-1 to 140-m is arbitrary. For example, the API possessed by a certain data provider device has a POST method format. Further, the API held by other data provider devices is in the GET method format. However, the API is not limited to the POST method format and the GET method format, and may be in other formats.

Each data provider device 140-1 to 140-m is configured to return a response including the requested data upon receiving a data acquisition request by the API. Hereinafter, the API included in the data provider devices 140-1 to 140-m is referred to as a data request API. Further, when the individual data provider devices 140-1 to 140-m are not distinguished, the branch numbers are omitted and simply referred to as the data provider device 140.

The data requester devices 150-1 to 150-n are information processing devices such as personal computers and smartphones used by those who request data such as documents, images, and sounds. Each of the data requester apparatuses 150-1 to 150-n has a browser function that transmits an API request and receives a response. Hereinafter, when the individual data requester devices 150-1 to 150-n are not distinguished, the branch number is omitted and simply referred to as the data requester device 150.

The server apparatus 100 is an information processing apparatus such as a personal computer used by a person who provides a service for providing data held by the data provider apparatus 140 to the data requester apparatus 150. The server device 100 includes a communication interface unit 111, an operation input unit 112, a screen display unit 113, a storage unit 120, and an arithmetic processing unit 130.

The communication interface unit 111 includes, for example, a data communication circuit, and performs data communication with various devices such as the data provider device 140 and the data requester device 150 connected via a wired or wireless communication line. It is configured. The operation input unit 112 includes an operation input device such as a keyboard and a mouse, and is configured to detect an operator operation and output the operation to the arithmetic processing unit 130. The screen display unit 113 is configured by a screen display device such as an LCD (Liquid Crystal Display) or a PDP (Plasma Display Panel), and displays various information such as an operation menu on the screen according to instructions from the arithmetic processing unit 130. It is configured.

The storage unit 120 is configured by a storage device such as a hard disk or a memory, and is configured to store processing information and programs 121 necessary for various processes in the arithmetic processing unit 130. The program 121 is a program that realizes various processing units by being read and executed by the arithmetic processing unit 130, and an external device (not shown) or a storage medium via a data input / output function such as the communication interface unit 111. (Not shown) is read in advance and stored in the storage unit 120. The processing information stored in the storage unit 120 includes data access API information 122 and a data catalog 123.

The data access API information 122 is definition information related to an interface used when the data requester device 150 acquires data from the server device 100. When the API defined by the data access API information 122 is called from the data requester device 150, the server device 100 acquires the data requested by the API from the data provider device 140, and a response including the acquired data Is configured to return. The specification of the data access API is arbitrary. For example, the data access API has a POST method format. However, the data access API is not limited to the POST method format, and may be another format such as a GET method format.

The data catalog 123 is a database that stores information related to data published by the data provider device 140. FIG. 2 shows an example of the data catalog 123. The data catalog 123 in this example has a plurality of entries, and each entry includes items such as a resource ID, an API serial number, a data request API, a request header, a request body, a query string, a time constraint condition, and meta information. The

The resource ID is an identification number assigned to one or a plurality of data that can be collectively acquired from the server apparatus 100 by one data access API request. The API sequence number is a serial number assigned to one or more data request APIs for acquiring data identified by the resource ID. The data request API is a URI of the data request API for acquiring all or part of the data identified by the resource ID. The request header is a name of a request parameter necessary for the header of the data request API. The request body is a name of a request parameter necessary for the request body when the data request API method is POST. The query string is the name of a request parameter required when the data request API method is GET. The time constraint condition is a time condition regarding execution of the data request API. The meta information is a data name, a keyword, and the like extracted from the data body.

For example, the entry in the second line in FIG. 2 indicates that the data with resource ID 1 is https: // dataA. com / v1 / aa. This indicates that the data can be acquired from the data provider device 140 by the data request API json. In addition, the data request API needs to set a request parameter named X-AA in the request header and a request parameter named Abody1 in the request body, and the time required to execute the data request API. This means that there is no constraint. Here, the request parameter X-AA is for selecting (extracting) partial data from data acquired by the data request API. For example, when the data acquired by the data request API is demographic data of a certain municipality after the year 2000, X-AA designates a year, for example. In the entry on the second line in FIG. 2, “Name” is described as the data name in the meta information, and a keyword or the like is described although not shown. Note that the number of request parameters set in the request header is not limited to one, and may be plural. For example, two request parameters named X-AA and X-AAA may be set in the request header. Here, the request parameters X-AA and X-AAA are for selecting (extracting) partial data from data acquired by the data request API. For example, when the data acquired by the data request API is demographic data of a certain municipality after the year 2000, X-AA designates a year, for example, and X-AAA designates a month.

In addition, two entries in the third to fourth lines in FIG. 2 indicate that data with a resource ID of 2 is https: // dataB. com / v1 / bb. json data request API and https: // dataC. com / v1 / cc. This indicates that the data can be acquired from the two data provider devices 140 by a total of two data request APIs of the data request API json. In the former data request API, it is necessary to set a request parameter named X-BB in the request header and a request parameter named Bbody1 in the request body, and the time required to execute the data request API This means that there is no such restriction. In the latter data request API, it is necessary to set a request parameter named X-CC in the request header and to set a request parameter named Cbody1 in the request body, and the time required to execute the data request API This means that there is no such restriction.

Further, a time constraint condition of 08: 00 ≦ t ≦ 18: 00 is set in the entry on the fifth line in FIG. This is because data with a resource ID of 3 is stored at https: // dataD. com / v1 / dd. This indicates that when data is acquired from the data provider device 140 by the data request API “json”, the data request API must be executed in a period from 8:00 am to 6:00 pm. The reason why such a time limit is set is that, for example, the data provider device 140 having the data request API has a limitation on the operation time.

Also, a time constraint condition of 2018/05/01/08: 0 ≦ t is set in the entry on the sixth line in FIG. This is because data with a resource ID of 4 is stored in https: // dataE. com / v1 / ee. When obtaining from the data provider device 140 by the data request API “json”, this indicates that the data request API must be executed after 8:00 am on May 1, 2018. The reason why such a time limit is set is, for example, that the data provided by the data request API is disclosed starting from a specific date and time.

In the entry on the seventh line in FIG. 2, a request parameter named X-FF is set in the request header, the item of the request body is NULL, and the name of the request parameter is set in the item of the query string. Ff1 is described. This is because data with a resource ID of 5 is stored at https: // dataF. com / v1 / ff. When obtaining from the data provider device 140 by the data request API json, it is necessary to set the method as GET, set the request parameter named X-FF in the request header, and set the request parameter Ff1 in the query string Represents that.

Referring to FIG. 1 again, the arithmetic processing unit 130 includes a microprocessor such as an MPU and its peripheral circuits, and reads the program 121 from the storage unit 120 and executes it, thereby cooperating the hardware and the program 121. In this way, various processing units are realized. Main processing units realized by the arithmetic processing unit 130 include a registration unit 131, a search unit 132, and a providing unit 133.

The registration unit 131 is configured to maintain and manage the data catalog 123 on the storage unit 120. For example, the registration unit 131 registers new information in the data catalog 123 according to information received from the data provider device 140 and information input from the operation input unit 112, or deletes the registered information. It is configured to update registered information.

The search unit 132 is configured to search the data catalog 123 on the storage unit 120. For example, the search unit 132 searches the meta information of the entry of the data catalog 123 according to the search request including the keyword received from the data requester device 140, and searches all or part of the contents of the entry having the matching keyword as a search result. It is configured to return as.

The providing unit 133 is configured to acquire the data requested from the data requester device 150 from the data provider device 140 and provide it to the request source. For example, when the API defined by the data access API information 122 is called from the data requester device 150, the providing unit 133 creates data based on information such as the URI of the data request API registered in the data catalog 123. Data is acquired from the data provider device 140 by the request API, and is returned to the data requester device 150.

Next, the operation of the server apparatus 100 according to this embodiment will be described.

FIG. 3 is a flowchart showing an example of the operation of the registration unit 131 of the server apparatus 100. Hereinafter, the operation of the registration unit 131 will be described with reference to FIG.

The registration unit 131 determines whether registration information has been received from the data provider device 140 (step S1), and whether an operation for adding, updating, or deleting registration information has been performed on the data catalog 123 in the operation input unit 112. (Step S2) is constantly monitored.

In this embodiment, the data provider device 140 can register in the data catalog 123 by voluntarily transmitting registration information related to data to be disclosed to the server device 100. The registration information for one case transmitted from the data provider device 140 includes data items of data request API, request header, request body, query string, time constraint condition, and meta information shown in FIG. Yes. When the registration unit 131 receives n registration information (n is a positive integer equal to or greater than 1) from the data provider device 140, the registration unit 131 secures n new entries in the data catalog 123 and receives the received n entries. Registration information is registered in each entry (step S3). At this time, the registration unit 131 registers the newly assigned resource ID in the resource ID item of n new entries. Also, a serial number starting from 1 is registered in the API serial number field of n new entries.

Further, when an operator operation for adding n registration information is performed from the operation input unit 112, the registration unit 131 performs the same operation as when n registration information is received from the data provider device 140. Thus, registration information is added to the data catalog 123 (step S4). The registration unit 131 updates the registration information in the data catalog 123 or updates the registration information registered in the data catalog 123 from the operation input unit 112 according to the operation content. Deletion is performed (step S4).

In the operation of the registration unit 131 described above, any data provider device 140 can register registration information in the data catalog 123. However, the registration unit 131 performs authentication to confirm whether or not the data provider device 140 is a person having a legitimate authority, and registers registration information in the data catalog 123 only for the data provider device 140 that has been successfully authenticated. You may comprise so that it can register. Further, the registration unit 131 performs authentication for confirming whether or not the operator has a legitimate authority, and only the operator who has succeeded in authentication can add, update, and delete registration information from the operation input unit 112 to the data catalog 123. It may be.

Also, the registration unit 131 may make an inquiry to the data provider device 140 to promote data registration. For example, when only a part of a plurality of data provider devices 140 related to each other performs registration, the registration unit 131 may make an inquiry to the unregistered data provider device 140 to urge registration. .

FIG. 4 is a flowchart showing an example of the operation of the search unit 132 of the server device 100. Hereinafter, the operation of the search unit 132 will be described with reference to FIG.

The search unit 132 always monitors whether or not a search request has been received from the data requester device 150 (step S11). In the present embodiment, the data requester device 150 can search for keywords included in the meta information of the data catalog 123 as search keywords. When receiving the search request from the data requester device 150, the search unit 132 searches for an entry in the data catalog 123 that includes the search keyword specified in the search request in the meta information (step S12). Next, the search unit 132 returns the search result to the data requester device 150 that is the search request source (step S13). When the search is successful, the search unit 132 returns a search result including all or part of the information registered in the entry of the data catalog 123 that has been successfully searched. The portion may be at least a resource ID, a request header, a request body, and a query string, for example.

In the operation of the search unit 132 described above, any data requester device 150 can search the data catalog 123. However, the search unit 132 performs authentication for confirming whether or not the data requester device 150 has a legitimate authority, and can search the data catalog 123 only for the data requester device 150 that has been successfully authenticated. You may do it.

FIG. 5 is a flowchart showing an example of the operation of the providing unit 133 of the server device 100. Hereinafter, the operation of the providing unit 133 will be described with reference to FIG.

The providing unit 133 monitors whether an acquisition request has been received from the data requester device 150 (step S21). In the present embodiment, the data requester device 150 can request acquisition of data by specifying the resource ID of the data catalog 123 by calling the data access API. When receiving the acquisition request from the data requester device 150, the providing unit 133 acquires the data specified by the resource ID specified in the acquisition request from the data provider device 140 (step S22). Next, the providing unit 133 returns the acquired data as a response to the data access API to the requesting data requester device 150 (step S23).

In the operation of the providing unit 133 described above, an arbitrary data requester device 150 can request acquisition of data. However, the providing unit 133 performs authentication for confirming whether or not the data requester device 150 has a legitimate authority so that only the data requester device 150 that has succeeded in authentication can acquire data. May be.

Subsequently, the detailed operation of the providing unit 133 will be described using an example of catalog data shown in FIG.

FIG. 6 is a sequence chart showing an example of the operation of the server device 100 when the data access API is called from the data requester device 150-1. In the example of FIG. 6, the data requester device 150-1 sets the value 1 as the resource ID in the request header of the data access API, and the request parameter X− required in the request header of the data acquisition API in the request body. The value 10 is set as the value of AA, and the value 3 is set as the request parameter Abody1 required in the request body. When receiving the request by the data access API (step S31), the providing unit 133 of the server apparatus 100 assembles a data acquisition API for acquiring data having a resource ID value of 1 and makes the request (step S32). Referring to the data catalog of FIG. 2, the data request API registered in the entry with the resource ID = 1 is https: // dataA. com / v1 / aa. json, the required request header is X-AA, and the request body is Abody1. Therefore, the providing unit 133 makes a request by assembling a data acquisition API as described in step S32 of FIG.

When receiving the request by the data access API, the request destination data provider apparatus 140-1 returns a response including data specified by the request parameters X-AA = 10 and Abody1 = 3 to the server apparatus 100. In the example of FIG. 6, the status code is 200 (OK), the response header includes the value AA as the status name aa, and the response body includes AAA1 as the value of the item aa1.

When the server apparatus 100 receives the response from the data provider apparatus 140-1, the server apparatus 100 edits a response that matches the specifications of the data access API based on the content of the received response, and returns the response to the data requester apparatus 150-1. (Step S34). In the example of FIG. 6, the status code is 200 (OK), the response header includes the value AA as the status name Acs-Status, and the response body includes AAA1 as the value of the item aa1.

FIG. 7 is a sequence chart showing another operation example of the server apparatus 100 when the data access API is called from the data requester apparatus 150-1. In the example of FIG. 7, the data requester device 150-1 sets a value 2 as the resource ID in the request header of the data access API, and is required in the request header of the data acquisition API of API sequence number 1 in the request body. The value 11 is set as the value of the request parameter X-BB and the value 12 is set as the value of the request parameter X-CC required in the request header of the data acquisition API of the API serial number 2, and the data acquisition of the API serial number 1 is performed. The value 4 is set as the request parameter Bbody1 required in the API request body, and the value 5 is set as the request parameter Cbody1 required in the data acquisition API request buddy of the API serial number 2. When receiving the request by the data access API (step S41), the providing unit 133 of the server apparatus 100 assembles a data acquisition API for acquiring data having a resource ID value of 2 and makes the request (step S42).

Referring to the data catalog of FIG. 2, there are two data request APIs registered in the entry of resource ID = 2, API sequence number 1 and API sequence number 2. For this reason, the providing unit 133 first makes a request by assembling the data request API of API serial number 1 as described in step S42 (step S42). When receiving the request by the data access API of the API serial number 1, the request destination data provider device 140-2 sends a response including data specified by the request parameters X-BB = 11, Bbody1 = 4 to the server device 100. (Step S43). In the example of FIG. 7, the status code is 200 (OK), the response header includes the value BB as the status name bb, and the response body includes BBB1 as the value of the item bb1.

Next, the providing unit 133 makes a request by assembling the data request API of API serial number 2 as described in step S44. When receiving the request by the data access API of the API serial number 2, the request destination data provider apparatus 140-3 sends a response including data specified by the request parameters X-CC = 12, Cbody1 = 5 to the server apparatus 100. (Step S45). In the example of FIG. 7, the status code is 200 (OK), there is no response header, and CCC1 is included as the value of the item cc1 in the response body.

When the server device 100 finishes receiving all API serial number data request API requests and responses, the server device 100 compiles a response that conforms to the specifications of the data access API based on the content of each received response, and requests the data request. Return to the user device 150-1 (step S46). In the example of FIG. 7, the status code is 200 (OK), the response header includes the value BB as the status name Acs-Status, the response body includes BBB1 as the value of the item bb1, and CCC1 as the value of the item cc1. ing. In the above description, the server device 100 receives all responses from the data provider devices 140-2 and 140-3, and then returns the response to the data requester device 150-1. However, the server device 100 may return the response to the data requester device as soon as the response is received from the data provider device. That is, when the server apparatus 100 receives a response from the data provider apparatus 140-2, the server apparatus 100 edits the response conforming to the data access API specification based on the content of the received response, and sends it to the data requester apparatus 150-1. return. Further, when the server apparatus 100 receives a response from the data provider apparatus 140-3, the server apparatus 100 edits a response that matches the specification of the data access API based on the content of the received response, and sends it to the data requester apparatus 150-1. return. In this case, the data requester apparatus 150-1 returns a plurality of responses to one request. Therefore, the server apparatus 100 assigns a response number so that the data requester apparatus 150-1 can identify each of a plurality of responses, or adds an indicator indicating whether each response is the last response. May be.

FIG. 8 is a sequence chart showing still another operation example of the server apparatus 100 when the data access API is called from the data requester apparatus 150-1. In the example of FIG. 8, the data requester device 150-1 sets the value 3 as the resource ID in the request header of the data access API. When the providing unit 133 of the server apparatus 100 receives a request by the data access API (step S51), the providing unit 133 attempts to make a request by assembling a data acquisition API for acquiring data having a resource ID value of 3. Referring to the data catalog 2, a time constraint condition is set for the entry with resource ID = 3. Therefore, the providing unit 133 controls the timing for acquiring data.

Specifically, the providing unit 133 determines whether or not the request can be made immediately based on the current time and the time constraint condition, and whether or not the request can be made later if the request is not immediately available (step S52). In the case of the time constraint condition of 08: 00 ≦ t ≦ 18: 00, the providing unit 133 determines that the request can be made immediately if the current time is the time zone from 8:00 to 18:00. If the current time is after 0:00 and less than 8:00, the providing unit 133 determines that the request can be made after 8:00 on that day. If the current time is after 18:00 and less than 24:00, the providing unit 133 determines that the request can be made after 8:00 on the next day. The providing unit 133 makes a request as soon as possible if the request can be made immediately (step S53). If the requesting unit 133 cannot immediately request, the providing unit 133 suspends the request until a requestable time zone is entered. And if the provision part 133 enters into the time slot | zone which can be requested, it will implement the pending request (step S53). The reception of the response from the request destination data providing apparatus 140-4 (step S54) and the transmission of the response to the data requester apparatus 150-1 (step S55) are performed in the same manner as steps S33 and S34 of FIG. In the above description, the providing unit 133 automatically implemented the pending request. However, the providing unit 133 may make an inquiry to the requesting data requester apparatus 150-1 before executing the pending request. That is, the providing unit 133 may execute the request that has been suspended after confirming with the data requester device 150-1 again.

FIG. 9 is a sequence chart showing still another operation example of the server apparatus 100 when the data access API is called from the data requester apparatus 150-1. In the example of FIG. 9, the data requester device 150-1 sets the value 5 as the resource ID in the request header of the data access API, and the request parameter X− required in the request header of the data acquisition API in the request body. The value 14 is set as the FF value, and the value 5 is set as the request parameter Ff1 required in the query string. When receiving the request by the data access API (step S61), the providing unit 133 of the server apparatus 100 assembles a data acquisition API for acquiring data having a resource ID value of 5 and makes the request (step S62). Referring to the data catalog of FIG. 2, the method of the data request API registered in the entry with resource ID = 5 is GET. Therefore, the providing unit 133 makes a request by assembling a data acquisition API as described in step S62 of FIG. Reception of a response from the request destination data providing apparatus 140-5 (step S63) and transmission of a response to the data requester apparatus 150-1 (step S64) are performed in the same manner as steps S33 and S34 of FIG.

As described above, according to the present embodiment, the following effects can be obtained.

The cost of the server device 100 can be reduced. The reason is that when the data requester device 150 requests acquisition of data, the server device 100 acquires the data from the data provider device 140 that holds the corresponding data and provides the data requester device 150 with the data. This is because a large-capacity database that holds data acquired from the data provider device 140 in advance is not required.

・・・ The load on the data requester can be reduced. The reason is that a person who requests acquisition of data from the data requester apparatus 150 does not need to individually make a request to the data provider apparatus 140 holding the data to be acquired, and the same interface (data This is because a request may be issued through the access API).

Even when the data acquisition API specifications (eg, POST and GET) for acquiring data are different among the plurality of data requester devices 150, the data requester can use the same interface (data A request can be issued through an access API. The reason is that the server apparatus 100 needs the data request API required based on the data acquisition API information of each data provider apparatus 140 registered in the data catalog 123 and the value of the request parameter specified by the data requester. Is to assemble automatically.

The data requester can acquire the data acquired from the plurality of data provider devices 140 all at once by one data access API request. The reason is that the server apparatus 100 creates a plurality of data acquisition APIs based on the contents of a plurality of entries registered in the data catalog 123 corresponding to the resource ID specified by the data requester, and provides a plurality of data This is because a request is sent to the requester device 140, a plurality of responses from the plurality of data provider devices 140 are edited into one response and returned to the data requester.

The data requester can request data acquisition at a convenient time regardless of the time limit for the data to be acquired. The reason is that the server device 100 manages the time limit for acquiring data from the data provider device 140 in the data catalog 123 and controls the timing of acquiring data, that is, the timing of calling the data acquisition API. .

Subsequently, although the application of the present invention is not limited only to the education field, some examples in which the information processing system according to the present embodiment is applied to an elementary and secondary education system will be described.

(1) Scoring support FIG. 10 is a conceptual diagram of a scoring support system. As shown in FIG. 10, the scoring support system uses the information processing system according to the present embodiment in three stages of answer creation, answer input, and scoring support.

In the answer creation stage, the data provider device 140 used by the teacher registers in the data catalog 123 of the server device 100 in order to disclose the answer information of the test.

In the answer input stage, the data provider device 140 used by the person who supports the input of the answer is a server for publishing the answer by handwritten characters, voices, etc. inputted by the student to the test given as a text. Register in the data catalog 123 of the device 100.

In the stage of scoring support, the data requester device 150 used by the scorer acquires answer information from the data provider device 140 used by the teacher via the server device 100. The data requester device 150 obtains answer data for each school and each student from the data provider device 140 of the answer input person via the server device 100. The data provider device 140 used by the scorer performs scoring based on the acquired information, performs various analyses, and registers the data in the data catalog 123 of the server device 100 in order to disclose the processing results. Processing results include written scoring result data (correct / incorrect results, points (partial points), correct / incorrect locations), statistical data of scoring results by student (score transition, proficiency), and counting units (by school, by class, etc.) There are wrong answer analysis data, scoring data by counting units (by school, by class, etc.). Then, the data requester device 150 used by the teacher acquires the processing result from the data provider device 140 used by the grader via the server device 100.

(2) Active Learning Degree Measurement FIG. 11 is a conceptual diagram of an active learning degree measurement system. As shown in FIG. 11, the active learning degree measurement system uses the information processing system according to the present embodiment in three stages of implementation / collection, quantification, and analysis / reflection.

In the implementation / collection stage, the data provider device 140 that monitors the images and sounds of students taking classes in the classroom is registered in the catalog data of the server device 100 in order to publish the acquired images and sound data. To do. Further, the data provider device 140 registers the voice data for each student obtained by analyzing the voice data and images in the catalog data of the server device 100.

In the quantification stage, the data requester device 150 used for quantification acquires voice data for each student from the data provider device 140 via the server device 100, and the degree of liveliness (rising and falling) and emotions. Analyzes changes (joy, anger, sadness, spirit) and converts voice data into text. Further, the data provider device 140 registers in the catalog data of the server device 100 in order to publish the analysis result of vitality, the analysis result of emotion change, and the voice data converted into text.

At the stage of analysis / reflection, the data requester device 150 used by the analyst receives the vitality analysis result, the emotion change analysis result, the voice text, the data provider device 140 used for quantification via the server device 100. Get image data. Further, the data provider device 140 used by the analyst analyzes the above vitality analysis result, emotion change analysis result, voice text, and image data to analyze the singularity information of the speech change and the singularity of the emotion change. Information is detected, authoring data of singular points and images / sounds are created, and registered in the catalog data of the server apparatus 100 in order to make them public. Specifically, time-series discussion content data of group discussions, who, when and what remarks were made, in what state discussions were made, statistical data such as phrases and vocabulary that occurred frequently during discussions Is registered in the catalog data of the server apparatus 100 in order to make it public. Then, the data requester device 150 used by the teacher obtains the analysis result from the data provider device 140 used by the analyst via the server device 100, and creates a chart for each student.

(3) Distance learning support system FIG. 12 is a conceptual diagram of a distance learning support system. As shown in FIG. 12, in the remote lesson support system, the data provider device 140 installed in the classroom registers in the catalog data of the server device 100 in order to publish the moving image data that captures the state of the lesson. The moving image data capturing the state of the lesson can be acquired from the data requester device 150 via the server device 100 and used for various applications. For example, the data requester device 150 analyzes the acquired moving image data, generates student gaze data and facial expression data, and further analyzes the student's concentration based on those data. In addition, the data requester device 150 analyzes the acquired moving image data and generates utterance content (text) data of the student. In addition, the data requester device 150 analyzes the acquired moving image data and generates person identification data based on face authentication.

[Second Embodiment]
Next, a second embodiment of the present invention will be described. FIG. 13 is a block diagram of an information processing system according to the second embodiment of the present invention.

Referring to FIG. 13, the information processing system 200 according to the present embodiment includes a server device 210, a data provider device 220, a data requester device 230, and a network 240 that connects them to each other.

The data provider device 220 is an information processing device used by a person who provides data such as public data. The data provider device 220 can be configured in the same manner as the data provider device 140 of FIG. 1, for example, but is not limited thereto. The data requester device 230 is an information processing device used by a person who requests data such as public data. The data requester device 230 can be configured in the same manner as the data requester device 150 of FIG. 1, for example, but is not limited thereto.

The server device 210 is an information processing device that acquires data requested from the data requester device 230 via the network 240 from the data provider device 220 via the network 240 and provides the data requester device 230 via the network 240. The server device 210 includes a database 211 and a providing unit 212.

The database 211 is configured to store interface information for acquiring data from the data provider device 220. The database 211 can be configured in the same manner as the data catalog 123 of FIG. 1, for example, but is not limited thereto.

Upon receiving the first request for obtaining data from the data requester device 230, the providing unit 212 receives the first request from the data provider device 220 by using the second request created based on the interface information stored in the database 211. Data is acquired and sent to the data requester device 230. The providing unit 212 can be configured, for example, in the same manner as the providing unit 133 in FIG. 1, but is not limited thereto.

The information processing system 200 according to this embodiment configured as described above operates as follows. That is, when data acquisition is performed, the data requester device 230 issues a first request for data acquisition to the server device 210. When receiving the first request, the provision unit 212 of the server device 210 creates a second request based on the interface information stored in the database 211. Next, the providing unit 212 issues the created second request to the data provider device 220. When receiving the second request, the data provider device 220 sends the requested data to the server device 210. The providing unit 212 of the server device 210 acquires data from the data provider device 220 and sends it to the data requester device 230.

According to this embodiment, the cost of the server device can be reduced. The reason is that when the data requester device 230 is requested to acquire data, the server device 210 acquires data from the data provider device 220 that holds the corresponding data and provides the data requester device 230 with the data. This is because a large-capacity database that holds data acquired from the data provider device 220 in advance is not required.

・・・ The load on the data requester can be reduced. The reason is that a person who requests acquisition of data from the data requester device 230 does not need to individually make a request to the data provider device 220 that holds the data to be acquired. Because it is good.

Although the present invention has been described with reference to the above embodiments, the present invention is not limited to the above-described embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

The present invention enjoys the benefit of priority claim based on the patent application of Japanese Patent Application No. 2018-086145 filed on April 27, 2018 in Japan, and is described in the patent application. The contents are all included in this specification.

The present invention can be used in general information processing systems for utilizing public data such as documents for open innovation.

A part or all of the above embodiments can be described as in the following supplementary notes, but is not limited thereto.
[Appendix 1]
A server device connected to a data provider device and a data requester device through a network,
A database for storing interface information for acquiring data from the data provider device;
When a first request for obtaining the data is received from the data requester device, the data is obtained from the data provider device by a second request created based on the interface information stored in the database. And a providing unit that obtains and sends the data to the data requester device.
[Appendix 2]
The server apparatus according to appendix 1, wherein the database stores the interface information and the identification information of the data in association with each other.
[Appendix 3]
The server device according to

attachment

1 or 2, wherein the first request includes identification information of the data.
[Appendix 4]
The server apparatus according to any one of appendices 1 to 3, wherein the interface information includes a request parameter name necessary for the second request.
[Appendix 5]
The server device according to any one of appendices 1 to 4, wherein the providing unit sets a value of a request parameter extracted from the first request in the second request.
[Appendix 6]
The server apparatus according to any one of appendices 1 to 5, wherein the database stores information of a plurality of the interfaces that are different from each other in association with identification information of the same data.
[Appendix 7]
The providing unit according to any one of appendices 1 to 6, wherein the providing unit creates a plurality of second requests based on information of the plurality of interfaces corresponding to identification information of the data extracted from the first request. Server device.
[Appendix 8]
The providing unit includes a plurality of second data requests from a plurality of the data provider devices by a plurality of the second requests created based on information of the plurality of interfaces corresponding to the identification information of the data extracted from the first request. The server device according to any one of appendices 1 to 7, which acquires the data and sends the data to the data requester device.
[Appendix 9]
The providing unit includes a plurality of second data requests from a plurality of the data provider devices by a plurality of the second requests created based on information of the plurality of interfaces corresponding to the identification information of the data extracted from the first request. The server device according to any one of appendices 1 to 8, wherein the server device acquires the data and sends the data to the data requester device in response to the first request.
[Appendix 10]
10. The server device according to any one of appendices 1 to 9, wherein the interface information includes a temporal restriction condition.
[Appendix 11]
The server device according to any one of supplementary notes 1 to 10, wherein the providing unit controls a timing of acquiring the data from the data provider device according to the second request.
[Appendix 12]
The server device according to any one of appendices 1 to 10, wherein the interface is an API.
[Appendix 13]
A method executed by a server device connected to a data provider device and a data requester device through a network and having a database for storing interface information for acquiring data from the data provider device,
When a first request for obtaining the data is received from the data requester device, the data is obtained from the data provider device by a second request created based on the interface information stored in the database. A method of acquiring and sending to the data requester device.
[Appendix 14]
A computer connected to a data provider device and a data requester device through a network and having a database for storing interface information for acquiring data from the data provider device.
When a first request for obtaining the data is received from the data requester device, the data is obtained from the data provider device by a second request created based on the interface information stored in the database. A computer-readable recording medium having recorded thereon a program for performing processing to obtain and send to the data requester apparatus.
[Appendix 15]
13. An information processing system comprising the server device according to any one of appendices 1 to 12, and a data provider device and a data requester device connected to the server device through a network.

DESCRIPTION OF SYMBOLS 100 ... Server apparatus 111 ... Communication interface part 112 ... Operation input part 113 ... Screen display part 120 ... Storage part 121 ... Program 122 ... Data access API information 123 ... Data catalog 130 ... Arithmetic processing part 131 ... Registration part 132 ... Search part 133 ... providing units 140-1 to 140-m ... data provider devices 150-1 to 150-n ... data requester device 200 ... information processing system 210 ... server device 211 ... database 212 ... providing unit 220 ... data provider device 230: Data requester device 240: Network

Claims

A server device connected to a data provider device and a data requester device through a network,
A database for storing interface information for acquiring data from the data provider device;
When a first request for obtaining the data is received from the data requester device, the data is obtained from the data provider device by a second request created based on the interface information stored in the database. And a providing unit that obtains and sends the data to the data requester device.
The server apparatus according to claim 1, wherein the database stores the interface information and the data identification information in association with each other.
The server device according to claim 1, wherein the first request includes identification information of the data.
The server apparatus according to claim 1, wherein the interface information includes a request parameter name necessary for the second request.
The server device according to claim 1, wherein the providing unit sets a value of a request parameter extracted from the first request in the second request.
The server apparatus according to claim 1, wherein the database stores information on a plurality of the interfaces different from each other in association with identification information of the same data.
The said provision part produces the said several 2nd request based on the information of the said some interface corresponding to the identification information of the said data extracted from the said 1st request. Server device.
The providing unit includes a plurality of second data requests from a plurality of the data provider devices by a plurality of the second requests created based on information of the plurality of interfaces corresponding to the identification information of the data extracted from the first request. The server device according to claim 1, wherein the data is acquired and transmitted to the data requester device.
The providing unit includes a plurality of second data requests from a plurality of the data provider devices by a plurality of the second requests created based on information of the plurality of interfaces corresponding to the identification information of the data extracted from the first request. The server device according to claim 1, wherein the server device acquires the data and sends the data to the data requester device according to a response to the first request.
The server device according to claim 1, wherein the interface information includes a temporal restriction condition.
The server device according to any one of claims 1 to 10, wherein the providing unit controls a timing of acquiring the data from the data provider device according to the second request.
The server device according to claim 1, wherein the interface is an API.
A method executed by a server device connected to a data provider device and a data requester device through a network and having a database for storing interface information for acquiring data from the data provider device,
When a first request for obtaining the data is received from the data requester device, the data is obtained from the data provider device by a second request created based on the interface information stored in the database. A method of acquiring and sending to the data requester device.
A computer connected to a data provider device and a data requester device through a network and having a database for storing interface information for acquiring data from the data provider device.
When a first request for obtaining the data is received from the data requester device, the data is obtained from the data provider device by a second request created based on the interface information stored in the database. A computer-readable recording medium having recorded thereon a program for performing processing to obtain and send to the data requester apparatus.
An information processing system comprising the server device according to any one of claims 1 to 12, and a data provider device and a data requester device connected to the server device through a network.