JP7512656B2 - Information processing system, information processing device, information processing method, and program - Google Patents

Description

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

In recent years, various services using codes, including two-dimensional codes such as QR Codes (registered trademark), have become widespread. One example of such a service is one in which a terminal device reads a QR code (registered trademark) and then captures image data and stores it in a storage location indicated by the QR code.

In the conventional technology described above, the information included in the QR code indicating the storage destination is pre-determined in a fixed manner for the service. In other words, in the conventional technology, in a service that is accessed via a code such as a QR code, information associated with the service, such as information indicating the storage destination where data is to be saved, is pre-determined by the service provider. For this reason, for example, it is not possible to flexibly set a code such as a QR code according to the usage scenario of the service user in a series of services that can be accessed by generating the code and then reading the generated code.

The present invention has been made in consideration of the above points, and aims to allow at least a portion of the information associated with a service to be flexibly set according to the usage scenario of the service user.

The disclosed technology is an information processing system including an information processing device capable of communicating with a plurality of terminal devices, the information processing system having a first setting unit that sets information indicating a first input item, which is displayed on a first terminal device requesting generation of a code including identification information that specifies a service provided by the information processing device, in association with the service, and a second setting unit that sets information indicating a second input item different from the first input item, which is displayed on a second terminal device that reads the code , in association with the service before generating the code, the first setting unit sets a storage destination and a login method for information sent from the second terminal device, the login methods including a method of logging in by entering account information and a method of allowing login as a guest .

At least a portion of the information associated with the service can be flexibly set according to the usage scenario of the service user.

FIG. 1 illustrates an example of a configuration of an information processing system according to a first embodiment. FIG. 1 is a diagram illustrating a usage scene of an information processing system according to a first embodiment. FIG. 2 illustrates an example of a hardware configuration of a server device. FIG. 2 illustrates an example of a hardware configuration of a terminal device. FIG. 2 is a diagram illustrating an example of a functional configuration of each device of the first embodiment. FIG. 4 illustrates an example of a registration information storage unit according to the first embodiment; FIG. 2 illustrates an example of an application information storage unit according to the first embodiment; FIG. 4 illustrates an example of a user information storage unit according to the first embodiment; FIG. 4 illustrates an example of a submitted information storage unit according to the first embodiment; FIG. 4 illustrates an example of a questionnaire information storage unit according to the first embodiment; FIG. 4 illustrates an example of a submission information storage unit according to the first embodiment; 4 is a diagram illustrating information stored in a storage unit of the teacher terminal according to the first embodiment. FIG. 4 is a diagram illustrating information stored in a memory unit of a student terminal according to the first embodiment. FIG. FIG. 2 is a first sequence diagram illustrating an operation of the information processing system according to the first embodiment. FIG. 11 is a first diagram illustrating a screen transition of the teacher terminal according to the first embodiment. FIG. 11 is a second diagram illustrating a screen transition of the teacher terminal according to the first embodiment. FIG. 11 is a third diagram illustrating a screen transition of the teacher terminal according to the first embodiment. FIG. 2 is a second sequence diagram illustrating the operation of the information processing system of the first embodiment. FIG. 11 is a fourth diagram illustrating a screen transition of the teacher terminal according to the first embodiment. FIG. 11 is a third sequence diagram illustrating the operation of the information processing system according to the first embodiment. 11A to 11C are diagrams illustrating screen transitions on a student terminal according to the first embodiment. FIG. 11 is a diagram illustrating a usage scene of an information processing system according to a second embodiment. FIG. 11 is a diagram illustrating an example of a functional configuration of each device according to a second embodiment. FIG. 13 illustrates an example of a registration information storage unit according to the second embodiment; FIG. 13 illustrates an example of an application information storage unit according to the second embodiment; FIG. 13 illustrates an example of a user information storage unit according to the second embodiment; FIG. 13 illustrates an example of a submitted information storage unit according to the second embodiment; FIG. 13 illustrates an example of a transfer destination information storage unit according to the second embodiment; FIG. 11 is a sequence diagram showing an operation of the information processing system according to the second embodiment. 13A to 13C are diagrams illustrating screen transitions on a student terminal according to the second embodiment.

(First embodiment)
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS First, an embodiment will be described with reference to the drawings. Fig. 1 is a diagram showing an example of the configuration of an information processing system according to a first embodiment.

In the information processing system 100 of this embodiment, the server device 200 and the user environment E are capable of communicating with each other via a wide-area network n such as the Internet. However, the network n may be a network that is accessible within a specified range, such as an intranet.

The user environment E is a system environment in an organization such as a company or an educational institution such as a school that includes one or more terminal devices 300, 400...N.

The terminal devices 300, 400...N are information processing terminals carried or used by each user in the user environment E. For example, a smartphone, a tablet terminal, a PC, or a mobile phone may be used as the terminal devices 300, 400...N.

In addition, the terminal devices 300, 400...N can be connected to the network n without going through a LAN or the like in the user environment E (for example, via a mobile communication network, etc.). However, the terminal devices 300, 400...N may also be connected to a network in the user environment E.

In the information processing system 100 of this embodiment, the server device 200 causes the terminal device 300 to set information associated with a service provided in the user environment E, and the server device 200 stores the set information in association with the service. Then, in response to a request from the terminal device 300, the server device 200 generates a code including identification information that identifies the service associated with the set information, and downloads the code to the terminal device 300. Note that the code may include the set information.

In other words, in this embodiment, before creating a code that includes identification information that identifies a service, information to be associated with the service is set, and when generating the code, the service and the set information are associated.

Specifically, the information associated with the service includes, for example, information indicating the input fields into which values are to be entered when generating the code, and information indicating the input fields to be displayed when the code is read.

The input item for which a value is to be entered when generating a code is, for example, an item for setting the storage destination for data sent from the terminal device that reads the code. In addition, the input item displayed when the code is read is a questionnaire item for entering the user's response, which is displayed on the terminal device that read the code.

In this embodiment, the information associated with the service is set before the code associated with the service is generated. Therefore, according to this embodiment, for example, it is possible to have the terminal device 400, which reads the code generated in response to a request from the terminal device 300, perform an operation based on the set information.

In this embodiment, the code includes, for example, one-dimensional codes such as barcodes and two-dimensional codes such as QR codes.

Below, a usage scenario of the information processing system 100 will be described with reference to FIG. 2. FIG. 2 is a diagram illustrating a usage scenario of the information processing system of the first embodiment.

In FIG. 2, for example, user environment E is an educational institution, terminal device 300 is a terminal device used mainly by teachers, and terminal device 400 is a terminal device used mainly by students.

In the following description, the terminal device 300 may be referred to as the teacher terminal 300, and the terminal device 400 may be referred to as the student terminal 400.

In the example of FIG. 2, the service provided to user environment E from information processing system 100 is described as a service that supports the collection of work submitted by students to teachers. In the following description, the service that supports the collection of work submitted may be referred to as a submission service. Work submitted includes, for example, test answer sheets and responses to questionnaires about classes.

In user environment E, the teacher terminal 300 requests the server device 200 to generate image data of the QR code, and generates image data of the QR code 21. The teacher terminal 300 then prints the image data of the QR code 21 by including it in the handout 20.

At this time, the QR code 21 is generated to include identification information that identifies the submission service. It may also include information that has been set in advance by the teacher terminal 300.

In this embodiment, by generating the QR code 21 in this manner, information previously set in the teacher terminal 300 is associated with the submission service.

Here, the information previously set by the teacher terminal 300 refers to multiple different settings, such as information indicating the storage destination (submission destination) of the submission 20A submitted from the student terminal 400, and input items for a questionnaire that is displayed on the student terminal 400 that reads the QR code 21.

In this embodiment, a questionnaire is information that associates questions with answer items (input items) for inputting answers to the questions. In this embodiment, a questionnaire in which answers have been input to the answer items is called a questionnaire result. In other words, a questionnaire result is information that includes answers to the questions included in the questionnaire.

In this embodiment, based on the identification information that identifies the submission service included in the QR code 21, information indicating the submission destination of the submission 20A that is previously associated with the submission service and a survey to be displayed on the student terminal 400 that reads the QR code 21 are identified, and the submission 20A including the survey results can be collected. Note that the QR code 21 may also include information indicating the submission destination of the submission 20A.

In this embodiment, the submission 20A includes image data of a completed handout, which is a handout 20 distributed by a teacher to a student and on which the student has written his/her answers, captured by the imaging device of the student terminal 400, and the survey results of the survey that are displayed on the student terminal 400 when the QR code 21 printed on the handout 20 is read.

In this way, according to this embodiment, the teacher, who is the user of the submission service, can set the information associated with the submission service according to the usage scenario, such as the teacher's own teaching style. Therefore, according to this embodiment, the teacher does not need to separately conduct a questionnaire for the handout, and by attaching the set QR code 21 to the handout, the handout can be stored in the desired submission destination and the questionnaire with the desired content can be collected as necessary, which can significantly reduce the teacher's work according to the usage scenario.

In addition, according to this embodiment, it is only necessary to include the QR code 21 generated on the teacher terminal 300 in the document data that is the source of the handout 20, and the handout 20 to which the QR code 21 is attached can be easily created.

Furthermore, according to this embodiment, the submission 20A, which includes the results of the answers entered by the students in the handout 20 and the survey results, is stored in a submission destination designated in advance by the teacher. Therefore, according to this embodiment, the students do not need to hand over the handout 20 on which they have written their answers to the teacher, but can complete it themselves. In addition, the teacher can reduce the effort of collecting the handouts that have been completed and returning them to the students after grading, etc.

Below, the hardware configuration of each device of the information processing system 100 of this embodiment will be described with reference to Figures 3 and 4. Figure 3 is a diagram showing an example of the hardware configuration of a server device.

The server device 200 of this embodiment is constructed by a computer, and as shown in FIG. 3, includes a CPU 201, a ROM 202, a RAM 203, a HD 204, a HDD (Hard Disk Drive) controller 205, a display 206, an external device connection I/F (Interface) 208, a network I/F 209, a data bus B1, a keyboard 211, a pointing device 212, a DVD-RW (Digital Versatile Disk Rewritable) drive 214, and a media I/F 216.

Of these, the CPU 201 controls the operation of the entire server device 200. The ROM 202 stores programs used to drive the CPU 201, such as IPL. The RAM 203 is used as a work area for the CPU 201. The HD 204 stores various data such as programs. The HDD controller 205 controls the reading or writing of various data from the HD 204 according to the control of the CPU 201. The display 206 displays various information such as a cursor, menu, window, character, or image. The external device connection I/F 208 is an interface for connecting various external devices. In this case, the external device is, for example, a USB (Universal Serial Bus) memory or a printer. The network I/F 209 is an interface for data communication using the communication network N. The data bus B1 is an address bus or a data bus for electrically connecting each component such as the CPU 201 shown in FIG. 3.

The keyboard 211 is a type of input means equipped with multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 212 is a type of input means for selecting and executing various instructions, selecting a processing target, moving the cursor, etc. The DVD-RW drive 214 controls the reading and writing of various data from the DVD-RW 213, which is an example of a removable recording medium. Note that this is not limited to a DVD-RW, and may be a DVD-R, etc. The media I/F 216 controls the reading and writing (storing) of data from the recording medium 215, such as a flash memory.

The server device 200 in this embodiment may be, for example, a smartphone, a tablet terminal, a PDA (Personal Digital Assistant), a wearable PC, etc.

Next, the hardware configuration of the terminal devices 300, 400, ..., N will be described with reference to FIG. 4. Here, the hardware configuration of the terminal device 300 will be described as an example of the terminal devices 300, 400, ..., N. FIG. 4 is a diagram showing an example of the hardware configuration of a terminal device.

The terminal device 300 of this embodiment includes a CPU 301, a ROM 302, a RAM 303, an EEPROM 304, a CMOS sensor 305, an image sensor I/F 306, an acceleration/orientation sensor 307, a media I/F 309, and a GPS receiver 311.

Of these, CPU 301 is an arithmetic processing device that controls the operation of the entire terminal device 300. ROM 302 stores CPU 301 and programs used to drive CPU 301, such as IPL. RAM 303 is used as a work area for CPU 301. EEPROM 304 reads or writes various data, such as smartphone programs, under the control of CPU 301. ROM 302, RAM 303, and EEPROM 304 are examples of storage devices for terminal device 300.

The CMOS (Complementary Metal Oxide Semiconductor) sensor 305 is a type of built-in imaging means that captures an image of a subject (mainly a self-portrait) under the control of the CPU 301 to obtain image data. Note that instead of a CMOS sensor, an imaging means such as a CCD (Charge Coupled Device) sensor may also be used.

The imaging element I/F 306 is a circuit that controls the operation of the CMOS sensor 305. The acceleration/direction sensor 307 is a variety of sensors, such as an electronic magnetic compass that detects geomagnetism, a gyrocompass, and an acceleration sensor. The media I/F 309 controls the reading and writing (storage) of data from and to a recording medium 308, such as a flash memory. The GPS receiver 311 receives GPS signals from GPS satellites.

The terminal device 300 also includes a long-distance communication circuit 312, an antenna 312a of the long-distance communication circuit 312, a microphone 315, a speaker 316, an audio input/output I/F 317, a display 318, an external device connection I/F (Interface) 319, a short-distance communication circuit 320, an antenna 320a of the short-distance communication circuit 320, and a touch panel 321.

Of these, the long-distance communication circuit 312 is a circuit that communicates with other devices via a communication network. The microphone 315 is a built-in circuit that converts sound into an electrical signal. The speaker 316 is a built-in circuit that converts electrical signals into physical vibrations to produce sounds such as music and voice. The sound input/output I/F 317 is a circuit that processes the input and output of sound signals between the microphone 315 and the speaker 316 under the control of the CPU 301.

The display 318 is a type of display means, such as a liquid crystal or organic EL (Electro Luminescence) display that displays an image of a subject, various icons, etc. The external device connection I/F 319 is an interface for connecting various external devices. The short-range communication circuit 320 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The touch panel 321 is a type of input means that allows a user to operate the terminal device 300 by pressing the display 318. The display 318 is an example of a display unit that the terminal device 300 has.

Next, the functions of each device in the information processing system 100 of this embodiment will be described with reference to FIG. 5. FIG. 5 is a diagram showing an example of the functional configuration of each device in the first embodiment.

The teacher terminal 300 of this embodiment has a control unit 330, a browser unit 340, a storage unit 350, an imaging unit 360, etc. Each of these units is realized by a process in which one or more programs installed in the teacher terminal 300 are executed by the CPU 301. The control unit 330 may be realized, for example, by an operating system, or may be realized by software such as an application. In the following description, an application may be referred to as an app.

The control unit 330 launches the browser unit 340 upon receiving an operation from the user of the teacher terminal 300.

The browser unit 340 is, for example, a general web browser, and executes processes according to HTML (HyperText Markup Language) data and scripts (for example, JavaScript (registered trademark)). The browser unit 340 is activated by reading a code. When the browser unit 340 of this embodiment reads a code, it accesses the server device 200 based on an initial access URL (Uniform Resource Locator) included in the code, and executes an application corresponding to the registration ID included in the code.

The registration ID is identification information that identifies a service and is associated in advance with an application that realizes the service. The registration ID in this embodiment is an example of identification information that identifies a service. Note that if a service is realized by multiple applications, multiple registration IDs may be associated with one service. The initial access URL indicates the URL that should be accessed first when the teacher terminal 300 accesses the server device 200 for the first time.

Specifically, the browser unit 340 accesses an application associated with the registration ID among the applications held by the server device 200 in accordance with a redirect request from the server device 200 in response to access to the initial access URL. The redirect request is a response from the server device 200 in response to access to the initial access URL.

The browser unit 340 obtains data (HTML data, scripts, etc.) indicating a request to execute processing on the teacher terminal 300 from the accessed application.

Upon receiving an image capture command from the control unit 330, the image capture unit 360 controls the image capture device realized by the CMOS sensor 305 and the image sensor I/F 306 to capture an image.

The student terminal 400 of this embodiment has a control unit (operating system unit) 430, a browser unit 440, a memory unit 450, an imaging unit 360, etc. Each of these units is realized by processing that one or more programs installed in the student terminal 400 executes on the CPU of the student terminal 400. The functions of each unit of the student terminal 400 are the same as those of the teacher terminal 300, so explanations will be omitted.

The server device 200 of this embodiment has a communication unit 210, an application determination unit 220, an authentication unit 230, and an application group 240. Each of these units is realized by a process executed by the CPU 201 of one or more programs installed in the server device 200.

The server device 200 also has a registration information storage unit 261, an app information storage unit 262, a user information storage unit 263, a submission information storage unit 264, a survey information storage unit 265, and a submission information storage unit 266. Each of these storage units can be realized, for example, using ROM 202 or a storage device that can be connected to the server device 200 via a network. The details of each storage unit will be described later.

The communication unit 210 transmits the submission output from the student terminal 400 to the specified submission destination. The submission output from the student terminal 400 includes image data captured by an imaging device possessed by the student terminal 400 and the survey results.

The application determination unit 220 corresponds to the initial access URL. In response to an access to the initial access URL, the application determination unit 220 refers to the registration information storage unit 261 to determine the application corresponding to the registration ID assigned to the initial access URL.

When the application determination unit 220 determines the application corresponding to the registration ID, it sends a response including a redirect request including a URL for this application to the source of the access to the initial access URL.

In this embodiment, when an access is made from the teacher terminal 300, the URL of an application included in the app group 240 is determined to be the application corresponding to the registration ID.

The authentication unit 230 compares the account information input from the teacher terminal 300 or the student terminal 400 with the user information stored in the user information storage unit 263, and authenticates the user (account information) based on the comparison result.

The app group 240 is an example of an application that the server device 200 has.

The app group 240 includes input apps and output apps. An input app is, for example, an application that executes processing according to the purpose, and each application transmits HTML data and scripts, etc. for executing processing according to the purpose, to the teacher terminal 300 and the student terminal 400. An output app is, for example, an application that acquires (downloads) image data stored in the submission information storage unit 266 and executes drawing.

The group of apps 240 in this embodiment includes, for example, various applications that realize the services provided by the server device 200. The group of apps 240 in this embodiment includes, for example, a submission setting app 240-1, a survey creation app 240-2, and a submission app 240-3.

The submission setting app 240-1 is an application that allows the teacher terminal 300 to set information associated with the submission service realized by the submission app 240-3.

In other words, the submission setting app 240-1 is an example of a first setting unit that sets a first input item associated with a service in the teacher terminal 300, which is the first terminal device that requested the generation of the code. The value of the first input item indicates the submission destination of the work sent from the student terminal 400 that read the code.

The survey creation app 240-2 is an application that executes a process to assist in the creation of a survey to be displayed on the student terminal 400 that reads the code.

In other words, the survey creation application 240-2 is an example of a second setting unit that sets a second input item that is different from the first input item displayed on the student terminal 400, which is the second terminal device that read the code, and that is associated with the service. The value of the second input item indicates the answer to the survey.

The submission app 240-3 stores the submission sent from the student terminal 400 that read the code in the submission destination set by the teacher terminal 300.

In other words, the submission application 240-3 is an example of a storage control unit that stores information sent from the second terminal device 400 that reads the code in a storage location included in the code.

Next, each memory unit of the server device 200 will be described with reference to Figures 6 to 11.

Figure 6 is a diagram showing an example of a registration information storage unit of the first embodiment. The registration information stored in the registration information storage unit 261 of this embodiment is information that is given in advance before the operation of the information processing system 100 described below is performed.

The registration information storage unit 261 has the following information items: registration ID, input app ID, output app ID, and tenant ID, and the value of the item "registration ID" is stored in association with the values of the other items. Note that, without making a distinction between input app ID and output app ID, the items may be collectively associated under the item "app ID." In addition, below, when "app ID" is simply written, it indicates either the input app ID or the output app ID.

For example, the identification information for identifying the submission service described above includes the registration IDs "Tag_Portal", "AP_Portal", "Tag_SendM101", "AP_SendM102", and "Tag_Survey". Furthermore, the submission service is realized by an app identified by at least the app IDs "AP_Portal", "AP_SendM101", "AP_SendM102", and "AP_Survey", respectively.

The input app ID is identification information for identifying an application that is set as an input app in the service corresponding to the registration ID. The output app ID is identification information for identifying an application that is set as an output app in the service corresponding to the registration ID. In the following description, the identification information for identifying an application is referred to as the app ID.

For example, the registration ID "Tag_Portal" is associated with the input application ID "AP_Portal," but is not associated with an output application ID. Therefore, it can be seen that the service corresponding to the registration ID "Tag_Portal" transmits HTML data and scripts, etc., to the teacher terminal 300 or the student terminal 400 for executing processing according to the purpose.

The input application ID "AP_Portal" indicates the application ID of the application that executes the process of displaying the menu of the portal screen for teachers. In other words, the application indicated by the application ID "AP_Portal" is the submission setting application 240-1.

The registration ID "Tag_SendM101" is associated with the input application ID "AP_SendM101", but is not associated with an output application ID. Therefore, it can be seen that the service corresponding to the registration ID "Tag_SendM101" is sent to the teacher terminal 300 or the student terminal 400, which transmits HTML data and scripts, etc., for executing processing according to the purpose.

The input application ID "AP_SendM101" indicates the application ID of an application that executes the process of storing the submission, including the survey results, in the folder "M101" of the submission destination (storage destination) specified as the submission destination. In other words, the application indicated by the application ID "AP_SendM101" is the submission application 240-3.

Note that the input application ID "AP_SendM102" associated with the registration ID "Tag_SendM102" is the same as the registration ID "Tag_SendM101" and the input application ID "AP_SendM101" except that the submission folder is replaced with "M102".

The registration ID "Tag_Survey" is associated with the input application ID "AP_Survey", but is not associated with an output application ID. Therefore, it can be seen that the service corresponding to the registration ID "Tag_Survey" is sent to the teacher terminal 300 or the student terminal 400, which transmits HTML data and scripts, etc., for executing processing according to the purpose.

The input application ID "AP_Survey" indicates the application ID of an application that supports the creation of a questionnaire on the teacher terminal 300. In other words, the application indicated by the input application ID "AP_Survey" is the questionnaire creation application 240-2.

In the following description, information including the value of the item "Registration ID" and the values of other items in the registration information storage unit 261 is referred to as registration information.

Figure 7 is a diagram illustrating an example of an application information storage unit of the first embodiment. The application information stored in the application information storage unit 262 of this embodiment is information that is provided in advance before the operation of the information processing system 100 described below is performed.

The app information storage unit 262 has information items such as app ID, app type, URL, compatible browser, etc., and the item "app ID" is associated with other items.

The value of the "Application Type" item indicates the type of application identified by the application ID based on its relationship with the document image data. When the value of the "Application Type" item is "In", this indicates that the application indicated by the application ID is an input application. When the value of the "Application Type" item is "Out", this indicates that the application indicated by the application ID is an output application. Note that, as described above, this item may not be present if there is no distinction between input applications and output applications.

The value of the "URL" item is the URL of the application identified by the app ID.

The value of the item "Compatible Browser" indicates the type of browser that runs the application identified by the app ID. In the example of Figure 7, the type of browser is a terminal browser that indicates the browser section of the teacher terminal 300 and the student terminal 400.

In the following description, information including the values of each item in the app information storage unit 262 is referred to as app information.

Figure 8 is a diagram showing an example of a user information storage unit in the first embodiment. The user information stored in the user information storage unit 263 is information that is given in advance before the operation of the information processing system 100 described below is performed.

The user information storage unit 263 has the following information items: tenant ID, user ID, user ID type, name, student ID number, email address, and available apps, and the item "user ID" is associated with other items.

The value of the item "tenant ID" is identification information of the party (tenant) who has signed a contract to use the service provided by the server device 200. For example, user environment E may correspond to one tenant.

The value of the item "User ID" is identification information for identifying the user of the terminal device. Specifically, the value of the item "User ID" is identification information for identifying the teacher who is the user of the teacher terminal 300, and identification information for identifying the student who is the user of the student terminal 400. In this embodiment, a user ID is assigned to each individual teacher and student. The user ID may be an email address, which will be described later.

The value of the item "User ID type" indicates the type of user ID. Specifically, when the value of the item "User ID type" is "Guest", it indicates that the user is a user whose login information including a user ID and password that identifies the user is not registered in the user information storage unit 263. Also, when the value of the item "User ID type" is "Login", it indicates that login information including a user ID and password that identifies the user is registered in the user information storage unit 263, and that the user logs in using the registered login information.

The value of the "Name" item indicates the user's name. The value of the "Student ID" item indicates the user's (student's) student ID number. The value of the "Email address" item indicates the user's email address.

The value of the "Available Applications" item is the application ID of the application that the corresponding user is permitted to use.

In the following description, information including the values of each item in the user information storage unit 263 is referred to as user information.

In the example of Figure 8, it can be seen that the user identified by "guest1" of tenant ID "T001" is permitted to use the application identified by app ID "AP_Send". The application identified by app ID "AP_Send" is an application that realizes part of the submission service.

In the example of Figure 8, it can be seen that the user identified by "tanaka@xxx.com" of tenant ID "T001" is permitted to use applications identified by app IDs "AP_Send," "AP_Survey," and "AP_Portal," which are applications that realize part of the submission service.

Note that the user information in this embodiment does not need to have all of the items shown in FIG. 8 as information items. The user information may also include items other than those shown in FIG. 8.

Figure 9 is a diagram showing an example of the submission information storage unit of the first embodiment. The submission information stored in the submission information storage unit 264 of this embodiment is generated when information indicating the storage destination (submission destination) of the information is input in the teacher terminal 300, and is stored in the submission information storage unit 264.

The submission information storage unit 264 has information items such as tenant ID, user ID, submission destination, submission destination ID, file ID, lecture room, start time, and class time, and the item "user ID" is associated with other items.

The value of the item "User ID" is a user ID that primarily identifies the teacher. The item "Submission destination" is further associated with the items "Lesson" and "Number of lessons". The values of the items "Lesson" and "Number of lessons" are the values of the submission destination classification entered by the teacher terminal 300 set in the introduction setting information, and indicate the lesson name and the number of lessons.

The value of the item "Submission destination ID" is identification information that specifies the storage destination (memory area) where the submission (image data, questionnaire results) sent from the student terminal 400 is stored. Specifically, the value of the item "Submission destination ID" is the folder name or the like in which the submission is stored, and is created using the value of the item "Submission destination".

The value of the item "File ID" is identification information for identifying a questionnaire file that has been registered in advance. The values of the items "Lecture Room", "Start Time", and "Class Duration" are information that identifies the lecture room in which the class will be held, information that indicates the start time of the class, and information that indicates the duration of the class.

In the following description, the submitted information is information in the submitted information storage unit 264 that includes the value of the item "user ID" and the values of other items.

The submission information does not have to include all of the items shown in FIG. 9. Specifically, for example, the items "lecture room," "start time," "class duration," etc., do not have to be included. The submission information may also include items other than those shown in FIG. 9. The data structure of the submission information storage unit 264 may be set arbitrarily by the teacher who sets the submission destination.

In addition, in the submission information storage unit 264 of this embodiment, for example, document data that is the source of the handout before the answer is written may be stored in association with a user ID and a submission destination.

Figure 10 is a diagram illustrating an example of the survey information storage unit of the first embodiment. The survey information stored in the survey information storage unit 265 of this embodiment is created by the teacher terminal 300 and stored in the survey information storage unit 265.

The survey information storage unit 265 has information items such as user ID, file ID, and survey name, with each item corresponding to the other.

In the survey information storage unit 265, the value of the item "User ID" is a user ID that primarily identifies a teacher. The value of the item "File ID" is identification information for identifying a survey file. In this embodiment, in the survey information storage unit 265, information including the value of the item "User ID" and the values of the other items is survey information.

In the example of Figure 10, it can be seen that the teacher identified by the user ID "tanaka@xxx.com" created a survey file with the survey name "Math 1_Comprehension" identified by the file ID "Srv01".

Figure 11 is a diagram showing an example of the submission information storage unit of the first embodiment. The submission information stored in the submission information storage unit 266 of this embodiment is generated when the submission sent from the student terminal 400 is stored in a folder identified by the submission destination ID.

The submission information storage unit 266 has the following information items: submission destination, user ID, file ID, and file type, and the item "user ID" is associated with other items.

The value of the item "User ID" is identification information that primarily identifies a user corresponding to a student. The value of the item "File ID" is identification information for identifying a file sent from the student terminal 400. The value of the item "File type" indicates the type of submission corresponding to the file.

In FIG. 11, for example, it can be seen that an answer file corresponding to the answer sheet identified by file ID "1000" and a file corresponding to the survey results identified by file ID "1001" are stored as submissions by a user (student) identified by user ID "guest1" in a folder identified by the submission destination ID "/math1/01".

Next, with reference to Figures 12 and 13, we will explain the information stored in the memory unit 350 of the teacher terminal 300 and the information stored in the memory unit 450 of the student terminal 400.

Figure 12 is a diagram illustrating information stored in the memory unit of the teacher terminal in the first embodiment. The information stored in the memory unit 350 of the teacher terminal 300 includes, for example, URL, access token, and content as items.

The value of the item "URL" indicates the server device 200. The value of the item "Access token" indicates the registration ID and user ID. The value of the item "Content" includes the name indicated in Name, the student ID number indicated in No, and the email address indicated in email.

In the example of FIG. 12, since the information is stored in the memory unit 350 of the teacher terminal 300, the user ID included in the access token is not a guest user ID type, but a login user ID type, and is a user ID that identifies the teacher.

Figure 13 is a diagram explaining the information stored in the memory unit of the student terminal in the first embodiment. The items of information stored in the memory unit 450 of the student terminal 400 are the same as the items of information stored in the memory unit 350 of the teacher terminal 300.

In the example of Figure 13, the user ID included in the access token is "guest1."

Next, the operation of the information processing system 100 of this embodiment will be described with reference to FIG. 14. FIG. 14 is a first sequence diagram showing the operation of the information processing system of the first embodiment. In FIG. 14, the operation of setting information to be associated with a submission service will be described.

In the information processing system 100, the browser unit 340 of the terminal device 300 receives an access request to the submission setting app 240-1 from the teacher (step S1401) and sends a connection request to the submission setting app 240-1 to the server device 200 (step S1402).

When accessing for the first time, the access token is not held, so the request is made without the access token.

In the server device 200, since the request is from a client without access authority, the submission setting app 240-1 returns a redirect request to the authentication unit 230 to the teacher terminal 300 (step S1403). At this time, the redirect request includes the URL of the authentication unit 230 and "Tag_Portal", which is a registration ID that identifies the service provided by the submission setting app 240-1.

Next, the browser unit 340 receives the redirect request to the authentication unit 230 and sends a connection request to the server device 200 to the authentication unit 230 (step S1404). The authentication unit 230 sends the URL of the login screen for the authentication service (step S1405).

The browser unit 340 then displays the login screen (step S1406). The browser unit 340 then accepts input of account information on the login screen (step S1407) and transmits a login request including the account information to the authentication unit 230 of the server device 200 (step S1408). The account information in this embodiment includes a user ID, a password, and a registration ID ("Tag_Portal") associated with the submission setting application 240-1.

The authentication unit 230 of the server device 200 then refers to the user information storage unit 263 and determines whether the user information storage unit 263 contains a user ID that matches the user ID contained in the account information, and whether the available apps corresponding to this user ID include an application associated with the registration ID.

Specifically, for example, assume that the user ID entered on the teacher terminal 300 is "tanaka@xxx.com".

In this case, it is determined that a user ID matching "tanaka@xxx.com" exists in the user information storage unit 263. In the registration information storage unit 261, the application associated with the registration ID "Tag_Portal" is the submission setting application 240-1 identified by the application ID "AP_Portal" (see Figures 6 and 8).

Therefore, the authentication unit 230 determines whether the available apps corresponding to "tanaka@xxx.com" include the app ID "AP_Portal". In this embodiment, the available apps corresponding to the user ID "tanaka@xxx.com" in the user information storage unit 263 include the app ID "AP_Portal". Therefore, the authentication unit 230 allows this user to use the submission setting app 240-1 identified by the app ID "AP_Portal".

Specifically, the authentication unit 230 creates an access token for accessing the user information of the user ID "tanaka@xxx.com" and returns it to the browser unit 340 (step S1409). The browser unit 340 holds this access token.

Next, the browser unit 340 uses the acquired access token to send a connection request to the server device 200 for the submission setting application 240-1 associated with the registration ID that has been authorized for use (step S1410).

In the server device 200, the submission setting application 240-1 receives the connection request and returns to the teacher terminal 300 the URL of a menu screen for setting information to be associated with the service (step S1411).

The browser unit 340 of the teacher terminal 300 receives this URL and displays a menu screen for setting information to be associated with the service (step S1412).

This menu screen displays a menu screen for setting information to be associated with the submission application 240-3.

More specifically, the menu screen includes "Introduction," "Survey list," and "Submission destination." When "Introduction" is selected on the menu screen, the browser unit 340 transitions to a process of setting input items for inputting values into the teacher terminal 300 when generating code.

In addition, when "Survey List" is selected on the menu screen, the browser unit 340 transitions to a process of creating a survey to be displayed on the student terminal 400 that read the code.

When "Submission Destination" is selected on the menu screen, the browser unit 340 transitions to a process of obtaining a code that associates the service with the set information.

Next, when the browser unit 340 accepts the selection of "Introduction" on the menu screen (step S1413), it sends an introduction request to the submission setting app 240-1 (step S1414). The introduction request includes an access token. In response to the introduction request, the submission setting app 240-1 returns an application that performs the introduction settings to the teacher terminal 300 (step S1415). In the following description, the application that performs the introduction settings is referred to as the introduction setting app.

The browser unit 340 of the teacher terminal 300 receives and executes the introduction setting app, and causes the introduction screen to be displayed by the introduction setting app (step S1416).

Next, when the browser unit 340 accepts the input of the introduction settings, it sets the settings according to the screen transitions of the introduction setting app, and sends the set introduction setting information together with an access token including the user ID to the submission setting app 240-1, thereby associating the user ID with the introduction setting information and registering it in the submission setting app 240-1 (step S1418).

In this embodiment, the information set by the introduction setting app is an input item for which a value is input into the teacher terminal 300 when generating a code to be assigned to a distribution in the submission service. Details of the settings by the introduction setting app will be described later.

Next, when the browser unit 340 of the teacher terminal 300 accepts the selection of "Survey list" on the menu screen (step S1419), it sends a request to the survey creation application 240-2 to display a list of the created surveys (step S1420).

In this embodiment, when "Survey List" is selected in the introduction setting app, the survey creation app 240-2 identified by the app ID "AP_Survey" is accessed, but the method of accessing the survey creation app 240-2 is not limited to this. For example, when a user directly accesses the survey creation app 240-2 without going through the introduction setting app, the survey creation app 240-2 can be identified based on the registration information storage unit 261 shown in FIG. 6 by including the registration ID "Tag_Survey" in the QR code 21.

In response to this request, the survey creation application 240-2 refers to the survey information storage unit 265 and transmits to the terminal device 300 a list of survey names corresponding to the user ID and an application that supports the creation of the survey (step S1421). Note that if there is no survey name associated with the user ID yet, the list of survey names is not transmitted. In the following description, the application that supports the creation of the survey is referred to as the creation assistance application.

The browser unit 340 of the teacher terminal 300 executes the received creation support app and causes the creation support app to display the list of survey names received (step S1422). Note that if there is no survey name corresponding to the user ID in the survey information storage unit 265, the list of survey names is not received, and therefore in step S1422, a blank screen is displayed by the creation support app.

Next, when an operation to add a survey is performed on the browser unit 340 of the teacher terminal 300 (step S1423), the creation assistance app displays a survey creation screen (step S1424).

When the creation of the survey is completed, the browser unit 340 sends a survey registration request to the survey creation application 240-2 (step S1425). This registration request includes the access token, the survey name, and the survey file.

When the survey creation application 240-2 receives the registration request, it associates and stores the user ID, survey name, and file ID of the survey file contained in the access token in the survey information storage unit 265.

Below, the screen transitions of the teacher terminal 300 during the operation shown in FIG. 14 are described with reference to FIG. 15 to FIG. 17.

Figure 15 is a first diagram illustrating screen transitions on the teacher terminal in the first embodiment. Screen 151 shown in Figure 15 is an example of the login screen displayed in step S1406 in Figure 14.

Screen 151 displays an input field 151a for account information (user ID and password) and operation buttons 151b.

When account information is entered in input field 151a and operation button 151b is operated, screen 151 transitions to screen 152.

Screen 152 is an example of the menu screen displayed in step S1412 of FIG. 14. Screen 152 displays operation buttons 152a, 152b, and 152c.

When the operation button 152a is operated on the screen 152, the browser unit 340 transitions the screen 152 to a setting screen using the introduction setting app.

When the operation button 152b is operated on the screen 152, the browser unit 340 transitions the screen 152 to a setting screen for the creation assistance app.

When operation button 152c is operated on screen 152, browser unit 340 transitions screen 152 to a code creation screen.

In this embodiment, the operation buttons 152b and 152c are displayed after the operation button 152a is selected and the introduction settings are performed by the introduction setting app. Therefore, when the introduction settings are not performed, the operation buttons 152b and 152c are not displayed on the screen 152 or are displayed in an unselectable state.

Figure 16 is a second diagram illustrating the screen transitions of the teacher terminal in the first embodiment. Figure 16 shows an example of the screen transitions displayed by the introduction setting app after the operation button 152a is operated on the screen 152.

When operation button 152a is operated, screen 152 transitions to screen 161 in FIG. 16. Screen 161 is an example of the screen displayed in step S1416 in FIG. 14.

Screen 161 displays a display field 161a and operation buttons 161b. Display field 161a displays options for selecting the person who will decide the destination of the submission. Specifically, display field 161a displays three options: "Decide the submission destination in advance," "Decide the submission destination at the time of submission," and "Allow the submission destination to be changed after the code is created."

In the example of Figure 16, we will explain the case where "Decide the submission destination in advance" is selected and operation button 161b is operated.

When operation button 161b is operated, screen 161 transitions to screen 162. Screen 162 displays input field 162a and operation buttons 162b and 162c. The classification of the submission destination is input in input field 162a. In other words, the classification of the submission destination indicates the hierarchy of the folder to which the code is to be submitted, and indicates the items to be input by the teacher terminal 300 when generating the code.

When operation button 162b is operated on screen 162, an input field for a new category is added to input field 162a.

In the example of FIG. 16, two hierarchies, a major category and a medium category, are added. Furthermore, a destination name can be entered in association with each destination category. The entered destination name may be registered as the name of the corresponding folder. The example of FIG. 16 shows that a folder with a category of "Number of Lessons" can be specified below a folder with a category of "Lesson Name". It may also be possible to set a destination category to be displayed by default. For example, if the major category "Lesson Name" and medium category "Number of Lessons" displayed in FIG. 16 are set as the destination categories to be displayed by default, when operation button 161b is operated, the major category "Lesson Name" and medium category "Number of Lessons" will already be displayed.

In addition to adding new submission destination categories, it may also be possible to delete categories that have already been added.

When the submission destination classification is entered in input field 162a and operation button 162c is operated, screen 162 transitions to screen 163.

Screen 163 is a screen for setting the login method when using the submission application 240-3. Screen 163 displays two login methods as options: logging in by entering account information, and allowing login as a guest.

When both the method of logging in by entering account information and the method of allowing login as a guest are selected on screen 163 and operation button 163a is operated, screen 163 transitions to screen 164.

In addition, when only the method of logging in by entering account information is selected on screen 163 and operation button 163a is operated, screen 163 transitions to screen 165, which will be described later.

Screen 164 displays input fields 164a and operation buttons 164b. Input fields 164a receive the designated items of guest information to be entered when logging in as a guest.

The input field 164a includes guest information items such as email address, name, and student ID number. The items specified in the input field 164a are the items to be input from the student terminal 400 as guest information.

In other words, screen 164 sets the items to be input on the terminal device of the user of the submission application 240-3 (the student terminal 400 that read the QR code 21). When operation button 164b is operated on screen 164, screen 164 transitions to screen 165.

Screen 165 displays a selection field 165a for configuring survey usage settings, and operation buttons 165b. Selection field 165a displays two options for selecting whether or not to use the survey.

In the example of FIG. 16, a case will be described where "use" of the survey is selected. When "use" of the survey is selected in the selection field 165a of the screen 165 and the operation button 165b is operated, the screen 165 transitions to the screen 166.

Screen 166 displays a list of the settings configured by the introduction setting app. In the following explanation, the information configured by the introduction setting app may be referred to as introduction setting information. As shown on screen 166 in FIG. 16, the introduction setting information includes information indicating the items to be input by the teacher terminal 300 when generating the code.

In addition, in this embodiment, as described above, the introduction setting information may be associated with the user ID and stored in the server device 200, or the introduction setting information may be held by an introduction setting app.

When operation button 166a is operated on screen 166, screen 166 transitions to screen 152 in FIG. 15. Note that when operation button 152a is selectable on screen 152, if browser unit 340 holds introduction setting information, it may read the introduction setting information and transition screen 152 to screen 166.

Next, referring to FIG. 17, we will explain the screen transition of the teacher terminal 300 when operation button 152b is selected on screen 152 in FIG. 15.

Figure 17 is a third diagram illustrating the screen transition of the teacher terminal in the first embodiment. Figure 16 shows an example of the screen transition displayed by the creation support app after the operation button 152b is operated on the screen 152.

When operation button 152b is operated on screen 152, screen 152 transitions to screen 171. Screen 171 is an example of a screen displayed in step S1422 of FIG. 14. Screen 171 displays operation button 171a and a message indicating that a survey can be added, and indicates that no survey file corresponding to the user ID exists.

When operation button 171a is operated on screen 171, screen 171 transitions to screen 172. Screen 172 is an example of the screen displayed in step S1424 of FIG. 14.

Screen 172 displays an input field 172a for the survey name and an operation button 172b. When the survey name is input on screen 172 and operation button 172b is operated, screen 172 transitions to screen 173.

Screen 173 displays an input field 173a and operation buttons 173b and 173c. The input field 173a is used to input the topic of the survey. Operation button 173b is an operation button for adding a question to which students are to input an answer in the survey. Operation button 173c is an operation button for transitioning to screen 179, which will be described later.

On screen 173, when the topic of the survey is entered in input field 173a and operation button 172b is operated, screen 173 transitions to screen 174.

Screen 174 displays display field 174a. Display field 174a displays options for selecting the input format of the answer to the newly added question. Specifically, display field 174a includes selection button 174b, which sets the answer to a selection format that allows the answer to be selected from options, and selection button 174c, which sets the answer to a description format that allows the answer to be written.

In FIG. 17, a case where the selection button 174b is operated in the display field 174a is described. When the selection button 174b is operated, the screen 174 transitions to the screen 175.

Screen 175 displays input field 175a for inputting questions included in the questionnaire. Screen 175 also displays input field 175b for inputting answer options for the questions.

On screen 175, when a question is entered in input field 175a, answer options are entered in input field 175b, and operation button 175c is operated, screen 175 transitions to screen 176.

Screen 176 shows that "Difficulty" has been entered as a question included in the survey name "Math 1_Comprehension," and that "Easy" and "Difficult" have been entered as answer options for the question.

In addition, when operation button 176a for adding a new question is operated on screen 176, screen 176 transitions to screen 177.

Display field 177a is displayed on screen 177. Display field 177a includes selection button 177b, which sets the answer to the question in a selection format that allows the answerer to select from a selection of options, and selection button 177c, which sets the answer to the question in a description format that allows the answerer to write the answer.

Screen 177 shows the case where selection button 177c is selected in display field 177a. When selection button 177c is operated on screen 177, screen 177 transitions to screen 178.

On screen 178, an input field 178a for inputting a new question to be added is displayed. Also, on screen 178, an answer entry field 178b is displayed in association with input field 178a. Also, on screen 178, an operation button 178c is displayed.

When a question is entered into input field 178a on screen 178 and operation button 178c is operated, screen 178 transitions to screen 179.

Screen 179 displays display field 179a and operation buttons 179b. Display field 179a displays a preview of the questionnaire. In the example of FIG. 17, display field 179a displays a questionnaire with the theme "Questionnaire about classes" that includes question 1, the answer of which is in the form of multiple choice, and question 2, the answer of which is in the form of a written response.

When operation button 179b is operated on screen 179, the survey displayed in display field 179a is registered in survey creation application 240-2 as a survey file with the survey name "Mathematics 1_Comprehension" and the screen transitions to screen 171A.

Specifically, the survey displayed in the display field 179a is output as a survey file in JSON format, for example. This survey file is given the file ID "Srv01" by the survey creation application 240-2, and is stored in the survey information storage unit 265 in association with the survey name and user ID.

On screen 171A, it can be seen that the questionnaire name "Mathematics 1_Comprehension" has been registered as the questionnaire file corresponding to the user ID.

In this embodiment, as described above, before generating the QR code 21 to be read by the student terminal 400, the teacher terminal 300 sets an item to be input as the destination for the submission of the work, and the student terminal 400 sets an item to be input as a questionnaire response different from the item to be input as the destination for the submission of the work.

The item to be entered as the submission destination of the submission is included in the introduction setting information set by the introduction setting app provided to the teacher terminal 300 by the submission setting app 240-1.

The items to be entered as responses to the questionnaire are included in the questionnaire (information in which questions and answer fields for the questions are associated) created by a creation support app provided to the teacher terminal 300 by the questionnaire creation app 240-2.

Next, the operation of generating the QR code 21 will be described with reference to FIG. 18. FIG. 18 is a second sequence diagram showing the operation of the information processing system of the first embodiment.

The processing in steps S1801 and S1802 in FIG. 18 is similar to the processing in steps S1411 and S1412 in FIG. 14.

When "Submission List" is selected on the menu screen displayed in step S1802 on the teacher terminal 300 (step S1803), the browser unit 340 sends a request to obtain a list of lessons corresponding to the user ID to the submission setting application 240-1 (step S1804). At this time, the request to obtain the list of lessons includes an access token including the user ID.

In the server device 200, the submission setting application 240-1 refers to the submission information storage unit 264, acquires a list of classes corresponding to the user ID included in the access token, and returns this to the browser unit 340 (step S1805). The browser unit 340 displays the acquired list of classes (step S1806). Note that if "Submission List" is selected first on the menu screen, the list is not displayed because no submission information corresponding to the user ID is stored.

Next, the browser unit 340 accepts an instruction to start setting up the class to which the submission destination of the work will be associated (step S1807) and displays an input screen for the submission destination classification set in the introductory setting information (step S1808).

The example in FIG. 18 shows a case where the major category of the submission destination category set in the introduction setting information is "Class Name." If the introduction setting information is stored in association with the submission setting app 240-1, in S1805, the introduction setting information associated with the user ID included in the access token together with the class list is received from the submission setting app 240-1, making it possible to identify and display the submission destination category set in the introduction setting information.

Next, when the browser unit 340 accepts input of the submission category (class name) (step S1809), it sends a registration request for the class name to the submission setting application 240-1 (step S1810). At this time, the registration request includes the input class name and access token. Upon receiving the registration request, the submission setting application 240-1 associates the class name with the user ID included in the access token and stores them in the submission information storage unit 264. Next, the browser unit 340 displays a list of the class names registered in the submission information storage unit 264 (step S1811).

The browser unit 340 then accepts the selection of the lesson name (step S1812) and sends a request to the submission setting application 240-1 to obtain a list of intermediate categories (number of lessons), which are the lower-level submission destination categories of the selected lesson name, based on the submission destination category set in the introduction setting information (step S1813). This request includes an access token. If the lower-level submission destination category of the lesson name is not set in the submission destination category setting of the introduction setting information, it is not necessary to request a list of intermediate categories.

The number of lessons is, for example, the number of times a lesson with a certain lesson name has been taught. For example, if the lesson name is "Mathematics 1", the first lesson of Mathematics 1 will be lesson number "1", and the second lesson will be lesson number "2".

Upon receiving the acquisition request, the submission setting application 240-1 refers to the submission information storage unit 264, acquires a list of the number of lessons and questionnaires associated with the user ID and lesson name included in the access token, and returns the list to the browser unit 340 (step S1814). At this time, the submission setting application 240-1 also returns the number of submissions to the browser unit 340.

The submission setting application 240-1 refers to the introduction setting information and the submission information storage unit 264 to identify the file ID of the questionnaire file corresponding to the user ID, the name of the lesson in the submission destination classification, and the introduction setting information in which the questionnaire usage setting is set to "Use," and refers to the questionnaire information storage unit 265 to obtain the file ID and the corresponding questionnaire name.

The browser unit 340 displays a list of the number of lessons and the questionnaire (step S1815). At this time, the browser unit 340 displays the number of submissions in addition to the list of the number of lessons and the questionnaire.

If the number of lessons associated with the user ID and the lesson name has not been set, the list of lesson numbers is not received from the submission setting application 240-1. Next, when the browser unit 340 receives a list of the number of lessons, it receives a request to set the number of lessons to be the submission destination from the list of the number of lessons (step S1816), and sends a request to register the number of lessons as the submission destination setting to the submission setting application 240-1 (step S1817).

This registration request includes an access token. Upon receiving the registration request, the submission setting application 240-1 stores the selected number of lessons in the "Number of lessons" field of the "Submission destination" item in the submission information storage unit 264. In the example of FIG. 18, this process sets the values of the major category (class name) and medium category (number of lessons) set in the introductory setting information as the submission destination classification.

In the example of Figure 18, the value of the lesson name is set to "Mathematics 1" and the value of the number of lessons is set to "1st." Note that the submission classifications such as the lesson name and the number of lessons are merely examples, and the user can set them to other classifications when setting the submission classification in the introductory settings.

If the number of lessons associated with the teacher's desired user ID and lesson name has not been set, in S1816 the teacher can set (add) the number of lessons based on the medium category (number of lessons) of the submission destination category set in the introductory setting information. Furthermore, in S1817, a registration request for the set (added) number of lessons is sent to the submission setting app 240-1, and the set (added) number of lessons is stored in the "Number of lessons" field of the "Submission destination" item in the submission information storage unit 264.

In step S1815, if the number of lessons and the file ID of the questionnaire corresponding to the user ID do not exist in the submitted information storage unit 264, the list of the number of lessons and the questionnaire will not be displayed. The list of the number of lessons and the questionnaire will not be displayed when the system is first introduced and the number of lessons and the questionnaire have not yet been set.

Next, the browser unit 340 accepts the selection of the number of lessons as part of the information indicating the submission destination, which is associated with the identification information for identifying the service included in the QR code 21 (step S1818).

Then, the browser unit 340 sends a request to the submission setting application 240-1 to obtain a list of lesson contents for the specified lesson (step S1819). This request includes the lesson name, which is the submission destination classification, the number of lessons, and an access token that includes the user ID.

Note that the lesson content in this embodiment includes, for example, document data that is the source of the handout stored in the server device 200 in association with the lesson name and the number of lessons, which are the submission destination classifications included in the request to obtain a content list, image data of the QR code to be printed on the handout, and the submission (image data of the handout with completed questions and the survey results). Therefore, the request to obtain the lesson content includes a request to generate the QR code 21. Note that if a handout with the image data of the QR code has not been distributed and the submission has not been collected, the submission will not be received from the server device 200.

In response to the acquisition request, the submission setting application 240-1 generates a QR code 21 to be attached to the distribution material 20, and returns a list of lesson contents including image data showing the QR code 21 to the browser unit 340 (step S1820). Therefore, the submission setting application 240-1 is also an example of a code generation unit that generates the QR code 21. The method by which the submission setting application 240-1 generates the QR code 21 will be described later.

The browser unit 340 displays a list of lesson contents (step S1821).

Here, since the handouts have not yet been distributed, there are no submissions yet. Therefore, the document data that is the source of the handouts 20 and the QR code 21 are displayed as a list of lesson content. Specifically, in step S1821, an operation button for instructing the display of image data of the QR code 21 and a thumbnail image of the document data that is the source of the handouts 20 are displayed.

Next, when QR code 21 is selected from the list of lesson contents, the browser unit 340 determines that a display request for image data representing QR code 21 has been received (step S1822), and displays the image data of QR code 21 (step S1823). At this time, the browser unit 340 saves the image data representing QR code 21.

The submission setting application 240-1 of this embodiment generates a QR code 21 including a registration ID that identifies a submission service that transmits a submission to a destination indicated by the selected lesson name and number of lessons. Specifically, the submission setting application 240-1 calls up a registration ID that is associated with the app ID "AP_Send" indicating an available app associated with the user ID in the user information storage unit 263, and includes this registration ID in the QR code 21. Here, the generation of the QR code 21 will be described. In this embodiment, the registration ID is embedded in the QR code 21. Below, a method of generating the QR code 21 will be described.

Method 1: A method of describing a registration ID as a query parameter This method is applied when the user making a request to generate the QR code 21 has account information (user ID and password) stored in the user information storage unit 263, and a tenant ID is included in the information items of the registration information storage unit 261. This method can also be applied when the user making a request to generate the QR code 21 does not have account information, as long as there are no duplicate tenant IDs.

When method 1 is applied, the format for retrieving the registered ID from the QR code 21 is, for example, "https://daas.com/start.html?tag=Tag_SendM101."

In this case, in the application information storage unit 262, the submission destination information is identified from the URL of the application ID "AP_SendM101" corresponding to the registration ID "Tag_SendM101" (see Figures 6 and 7).

Method 2: A method of describing a registration ID and a tenant ID as query parameters In this method, by including the tenant ID, it becomes possible to use a registration ID that is duplicated between tenants, and the item "tenant ID" is unnecessary in the registration information storage unit 261. When method 2 is applied, the format for calling up a registration ID from the QR code 21 is, for example, "https://daas.com/start.html? Tag_SendM101&tenant=T001".

Method 3: A method of describing the registered ID as a Web API (Application Programming Interface) This method has the same function as method 1, but can shorten the URL. When method 3 is applied, the format for calling up the registered ID from the QR code 21 is, for example, "https://daas.com/Tag_SendM101."

Method 4: A method of describing each registered ID in a static http file This method has the same function as method 1, but can shorten the URL. When method 4 is applied, the format for calling up the registered ID from the QR code 21 is, for example, "https://daas.com/Tag_SendM101.html."

The registration ID and information on the submission destination may be embedded in the QR code 21. This method is described below as Method 5.

Method 5: A method of describing a registration ID, a tenant ID, and a submission destination as query parameters. In this method, since the submission destination is included in the QR code 21, it is not necessary to create a registration ID for each submission destination.

Specifically, for example, if this method is used to create the QR code 21, the registration ID corresponding to the application that executes the process of storing the code in the folder "M101" specified as the submission destination does not require "M101" indicating the destination folder.

Therefore, in this case, the app ID of the application that executes the service to store the submission in the specified destination will be "AP_Send", and as shown in FIG. 7, there is no need to distinguish the app ID for each of the destination folders "M101" and "M102". Also, the registration ID in this case will be "Tag_Send", and as shown in FIG. 6, there is no need to distinguish the registration ID for each of the destination folders "M101" and "M102".

The value of the item "Available Applications" in the user information storage unit 263 shown in FIG. 8 is the application ID "AP_Send" if the QR code 21 includes information indicating the destination folder. The value of the item "Available Applications" is an application ID differentiated for each destination, such as the application ID "AP_SendM101", if the QR code 21 does not include information indicating the destination folder.

When method 5 is applied, the format for retrieving the registered ID from the QR code 21 is, for example, "https://daas.com/start.html? Tag_SendM101&tenat=T001&destinationID="/mathematics1/01".

Below, with reference to Figure 19, we will explain the screen transitions on the teacher terminal 300 during the operation shown in Figure 18.

Figure 19 is a fourth diagram illustrating screen transitions on the teacher terminal of the first embodiment. Screen 191 shown in Figure 19 is a screen to which screen 152 transitions when operation button 152c is selected on screen 152 in Figure 15, and is an example of the screen displayed in step S1806 in Figure 18.

In screen 191, since no submission destination has been set, only operation button 191a for adding a class to be associated with the submission destination is displayed. When operation button 191a is operated in screen 191, screen 191 transitions to screen 192. Screen 192 is an example of the screen displayed in step S1808 in FIG. 18.

Screen 192 displays an input field 192a for inputting the lesson name, and an operation button 192b for instructing the user to register the lesson name. When the lesson name is input into input field 192a and operation button 192b is operated, screen 192 transitions to screen 193. Screen 193 is an example of the screen displayed in step S1811 of FIG. 18.

Screen 193 displays a list of registered lesson names, with operation buttons 193a corresponding to the registered lesson names. When operation button 193a is operated on screen 193, screen 193 transitions to screen 194. Screen 194 is an example of the screen displayed in step S1815 of FIG. 18.

Display field 194a, 194b, and operation button 194c are displayed on screen 194. Display field 194a displays the name of the survey corresponding to the class name. On screen 194, it can be seen that the name of the survey corresponding to the class name "Mathematics 1" is "Mathematics 1_Comprehension." Furthermore, display field 194b displays the number of classes. On screen 194, it can be seen that the class with the name "Mathematics 1" was held for the first and second time.

Screen 194 also displays the number of submissions in association with the number of lessons displayed in display field 194b. The number of submissions indicates the number of file IDs stored in submission information storage unit 266. Screen 194 shows that there were 46 submissions in the first lesson of lesson name "Mathematics 1". Screen 194 also shows that there were no submissions in the second lesson of lesson name "Mathematics 1".

When operation button 194c is operated on screen 194, the number of lessons is added to display field 194b.

When the number of lessons displayed in display field 194b on screen 194 is selected, screen 194 transitions to screen 195. Screen 195 is an example of a screen displayed in step S1821 of FIG. 18.

For the first lesson, there are 46 submissions. Therefore, on screen 195, the document data of the handouts, information indicating the QR code, and the submissions are displayed as a list of lesson content. In the example of screen 195, the document data of the handouts is displayed as a thumbnail image 195c of the document data of the handouts.

In addition, on screen 195, an operation button 195a for instructing the generation of a QR code is displayed as information indicating the QR code, and an operation button 195b for instructing the download of the submission is displayed as the submission.

When the lesson number "Second" is selected on screen 194, no submissions exist, so screen 195 displays operation buttons 195a and thumbnail images 195c of the handouts.

Screen 194 and screen 195 are examples of screens that appear after the submission destination has already been set and submission has been accepted from the student.

When operation button 193a is operated for the first time, screen 193 transitions to screen 194A. Display field 194b' on screen 194A shows that this is the first class with the class name "Mathematics 1" and that there are 0 submissions, indicating that no submissions have been submitted for this class.

In addition, on screen 194, the document data that will be the source of the distribution can be uploaded and associated with the destination classification and registered in the submission setting application 240-1.

When the number of lessons displayed in display field 194b' on screen 194A is selected, screen 194A transitions to screen 195A.

On screen 195A, since there are zero submissions, operation button 195b may be displayed as not selectable. Also, if operation button 195b is operated, a notification may be displayed indicating that there are no submissions to download.

When operation button 195a is operated on screen 195A, screen 195A transitions to screen 196.

When operation button 195a is selected on screen 195, screen 195 transitions to screen 196. Screen 196 is an example of the screen displayed in step S1823 of FIG. 18.

The generated QR code 21 is displayed on screen 196. The QR code 21 includes a URL that displays the questionnaire named "Math 1_Comprehension" and information that specifies the folder "/Math 1/01" that specifies the destination of the work to be submitted. The /Math 1 folder corresponds to the "Class Name" submission destination classification set in the introductory setting information, and the /01 folder corresponds to the "Number of Lessons" submission destination classification set in the introductory setting information.

When the operation button 196b on the screen 196 is operated, the image data of the QR code 21 displayed on the screen 196 is downloaded and added to the document data that is the source of the distribution material.

In this embodiment, the printed matter obtained by printing the document data to which the QR code 21 generated in this manner has been added becomes the distribution item 20. Note that, as described above, the QR code 21 is merely one example of a code, and other types of codes, such as a one-dimensional code, may also be used.

In addition, in this embodiment, when the operation button 195b is operated on the screen 195, the submission group 97 stored in the submission information storage unit 266 is downloaded.

In this way, in this embodiment, when the QR code 21 is generated by the submission setting app 240-1, the teacher terminal 300 is prompted to input the storage destination of the submission.

Next, the operation of the student terminal 400 in the information processing system 100 of this embodiment will be described. FIG. 20 is a third sequence diagram showing the operation of the information processing system of the first embodiment. FIG. 20 shows the operation when a student reads the QR code 21 printed on the handout 20 using the student terminal 400 and uses the submission app 240-3.

In the information processing system 100 of this embodiment, the student terminal 400 receives an instruction from a student to read a QR code (step S2001), and the control unit 430 instructs the imaging unit 460 to capture an image of the QR code, and the imaging unit 460 causes the imaging device to capture the QR code (step S2002). Note that when the student terminal 400 detects that the student terminal 400 has been brought close to the QR code, it may automatically start the imaging device to capture an image of the QR code.

Next, the control unit 430 of the student terminal 400 acquires the registration ID "Tag_SendM101" and the initial access URL (step S2003). Note that if the QR code is generated using method 5 described above, the acquired registration ID will be "Tag_Send".

Next, the control unit 430 of the student terminal 400 starts the browser unit 440 (step S2004). In response to the start-up, the browser unit 440 grants an access token to the application determination unit 220 of the server device 200 corresponding to the initial access URL, and automatically transmits an HTTP request (step S2005).

In addition, the access token in this embodiment includes the registration ID "Tag_QR01" obtained from the QR code and the user ID.

In the server device 200, the application determination unit 220 requests the student terminal 400 to redirect to the login screen in order to authenticate the user (step S2006).

The browser unit 440 of the student terminal 400 receives this redirect request and requests the URL of the login screen from the authentication unit 230 of the server device 200, and obtains the login screen (step S2007).

Next, the browser unit 340 displays a selection screen for selecting either a method of using the information processing system 100 by inputting account information or a method of using the information processing system 100 as a guest (step S2008). Note that here, the browser unit 340 controls the display based on the login method set in the introduction setting information and the guest information input setting.

The browser unit 440 of the student terminal 400 accepts the selection of guest use (step S2009) and displays a screen for inputting student information (step S2010). In this embodiment, student information includes name, student ID number, email address, etc.

The browser unit 440 of the student terminal 400 accepts the input of the student information and sends a guest login request to the authentication unit 230 of the server device 200 (step S2011).

The authentication unit 230 of the server device 200 creates user information with the value of the item "user ID" set to, for example, guest1, creates an access token for accessing this user information, and sends it to the browser unit 440 (step S2012). The access token includes the registration ID, which is an argument of the guest login request. The access token is also stored in the browser unit 440.

Next, the browser unit 440 sends a connection request to the application determination unit 220 together with the access token (step S2013).

The application determination unit 220 sends a redirect request to the submitted application 240-3 that realizes the service associated with the registration ID included in the access token (step S2014).

Specifically, the application determination unit 220 refers to the registration information storage unit 261 to identify the application ID "AP_SendM101" that corresponds to the registration ID "Tag_SendM101". Then, the application determination unit 220 acquires, from the application information storage unit 262, a URL including a submission destination that corresponds to the application ID "AP_SendM101" indicating the submitted application 240-3.

The browser unit 440 receives the redirect request from the application determination unit 220 and sends a request together with the access token to the submitted application 240-3 (step S2015).

Upon receiving the request, the submission application 240-3 sends the URL of the UI screen that displays the survey to the student terminal 400 (step S2016).

Specifically, the submission application 240-3 identifies the submission destination ID (/Mathematics 1/01) from the URL indicating the submission application 240-3, and references the submission information storage unit 266 (Figure 9). Here, if the file ID of the questionnaire is associated with the identified submission destination ID in the submission information storage unit 266, the submission application 240-3 obtains the survey information registered in the settings of Figure 14 that corresponds to the file ID in the survey information storage unit 265 (Figure 10). The submission application 240-3 then transmits that information to the student terminal 400 together with the survey UI.

Note that if the QR code is generated using method 5, the QR code also contains the submission destination ID, and so in step S2015, the browser unit 440 transmits the submission destination ID obtained from the QR code to the submission application 240-3.

The browser unit 440 of the student terminal 400 receives this URL and displays the survey screen for the survey registered in the settings of FIG. 14 (step S2017). The browser unit 440 of the student terminal 400 accepts input of responses to the survey (step S2018).

The browser unit 440 of the student terminal 400 also receives an instruction to capture the image data of the completed handout 20 on which the answer has been written (step S2019), and issues an image capture instruction to the control unit 430 to capture an image of the completed handout 20 (step S2020). Next, in response to the image capture instruction from the control unit 430, the control unit 430 of the student terminal 400 passes the image data of the image captured by the imaging device of the imaging unit 460 to the browser unit 440 (step S2021).

The browser unit 440 of the student terminal 400 transmits the image data as the submission, an access token including the user ID, and the student information to the communication unit 210 of the server device 200 (step S2022). Next, the browser unit 440 of the student terminal 400 transmits the response data indicating the survey results and the access token including the user ID to the communication unit 210 of the server device 200 (step S2023). The image data and the survey results are stored as the submission in association with the user ID included in the access token in the submission destination specified by the QR code 21 (the submission destination category set in FIG. 18).

The URL of the communication unit 210 is the same as the URL associated with the application ID "AP_SendM101" in the application information storage unit 262, and by referencing this URL, the image data and the response data indicating the survey results are associated with the user ID included in the access token and stored in the submission destination.

Next, referring to FIG. 21, the screen transitions on the student terminal 400 during the operation shown in FIG. 20 will be described. FIG. 21 is a diagram illustrating the screen transitions on the student terminal in the first embodiment.

When the QR code 21 printed on the handout 20 is read on the student terminal 400, the screen 221 is displayed.

Screen 221 is an example of a screen displayed in step S2008 of FIG. 20. Screen 221 displays operation button 221a for selecting a method for logging in and using information processing system 100, and operation button 221b for selecting a method for using information processing system 100 as a guest.

When operation button 221b is operated on screen 221, screen 221 transitions to screen 222. Screen 222 is an example of the screen displayed in step S2010 of FIG. 20.

Screen 222 displays an input field 222a and operation buttons 222b. Input field 222a is an input field for inputting student information. When student information is input into input field 222a on screen 222 and operation button 222b is operated, screen 222 transitions to screen 223.

Screen 223 is an example of a screen displayed in step S2017 of FIG. 20. Screen 223 displays a questionnaire 223a with the name "Mathematics 1_Comprehension" and operation buttons 223b for transitioning between screens.

When an answer to questionnaire 223a is selected on screen 223 and operation button 223b is operated, screen 223 transitions to screen 224.

Screen 224 displays an operation area 224a for instructing the user to take an image, and an operation area 224b for instructing the user to view previously submitted submissions. When operation area 224a is operated on screen 224, screen 224 transitions to screen 225.

Screen 225 is a screen for capturing an image. An image of the handout 20 including the QR code 21 is captured on screen 225. When an image of the handout 20 is captured on screen 225, screen 225 transitions to screen 226.

Display field 226a is displayed on screen 226. Display field 226a displays a message indicating that the survey results and image data of completed handout 20 with the answers written on it have been stored as a submission to the destination specified by QR code 21.

In this manner, in this embodiment, the QR code 21 contains information indicating the items to be input into the terminal device 400 that reads the QR code 21. Therefore, according to this embodiment, when the image data of the handout 20 with the answers written therein is submitted, the survey results are also automatically stored in the submission destination.

In this embodiment, the survey results are described as being stored in a storage location indicated by the QR code 21 together with the image data of the handout 20 on which the answers are written, but this is not limited to the above.

In this embodiment, only the survey results may be stored in the storage location indicated by the QR code.

In this case, when the QR code 21 is read by the terminal device 400, the survey is displayed, and when an instruction to send the survey results is received, the survey results are stored in the storage location specified by the QR code 21. Therefore, in this embodiment, the survey results can be stored in the specified storage location simply by having the terminal device 400 read the QR code, reducing the effort required to collect the survey results.

In addition, in the above-described embodiment, an example of application of the information processing system 100 in an educational setting has been described, but the information processing system 100 may also be applied in settings other than educational settings.

This embodiment may be applied to any situation where, for example, a form of collecting questionnaire results and image data is applicable.

Specifically, for example, in a restaurant or the like, a QR code containing the URL of a survey screen and information indicating where the survey results and image data are stored may be displayed inside the store.

In this case, for example, a customer at a restaurant reads a QR code displayed in the store with their own terminal device, answers a questionnaire, and takes a picture of the product that was the subject of the questionnaire; the questionnaire results and image data of the product are then stored in the storage location indicated by the QR code.

In this way, according to this embodiment, image data (which may be document data, etc.) indicating the subject of the survey and the survey results can be stored in a specified storage location.

In the above example, when the operation button 223b is operated, the submission destination (submission destination ID) stored in the submission information storage unit 264 is uniquely identified by the information (URL) further associated with the application ID associated with the registration ID. However, it is also possible to associate multiple submission destinations (submission destination IDs) with an application ID.

In such a case, for example, by transmitting information indicating the submission destination associated with the application ID (information such as the name of the folder corresponding to the submission destination) from the server device 200 to the terminal device 400 after the operation button 223b is operated, it is possible to display information indicating multiple submission destinations and their corresponding folders, etc. on the screen of the terminal device 400.

Furthermore, when a specific submission destination (e.g., a folder icon or name) is selected by the user (student) submitting the submission from information indicating the submission destination, such as a folder, displayed on the screen of the terminal device 400, the terminal device 400 identifies the selected submission destination. The terminal device 400 then transmits information on the selected submission destination (submission destination ID) to the server device 200. By receiving this information, the server device 200 can identify the submission destination ID. Note that which submission destination (folder) the user submitting the submission should select may be determined in advance by a rule, or may be specified by the user receiving the submission by a means of communication, such as verbal communication.

Second Embodiment
A second embodiment will be described below with reference to the drawings. This embodiment differs from the first embodiment in that a QR code is attached to teaching materials such as textbooks in advance. In the following description of the second embodiment, differences from the first embodiment will be described, and components having the same functional configuration as those in the first embodiment will be given the same reference numerals as those used in the description of the first embodiment, and descriptions thereof will be omitted.

Below, a usage scenario of the information processing system of the second embodiment will be described with reference to FIG. 22. FIG. 22 is a diagram illustrating a usage scenario of the information processing system of the second embodiment.

In the example of FIG. 22, teaching materials 20B are used instead of handouts 20 distributed by a teacher to students. Teaching materials 20B are, for example, teaching materials that combine multiple learning materials and study notes, and a QR code 21A is assigned to each of the multiple learning materials in advance. Note that QR code 21A is merely one example of a code, and other types of codes, such as a one-dimensional code, may also be used.

Each learning material included in the multiple learning materials is, for example, a teaching material used in one lesson. Therefore, learning material 20B includes the same number of learning materials as the number of lessons in which learning material 20B is used, and a QR code 21A for each learning material.

In this embodiment, the QR code 21A assigned to each learning material is used to associate information indicating the content entered in the learning material 20B with the submission destination associated with the QR code 21A.

The example in FIG. 22 shows a case where Teacher A and Teacher B each used the learning material "Mathematics 1, Session 3" in learning material 20B in their respective lessons. A QR code 21A is attached to the learning material "Mathematics 1, Session 3" in learning material 20B.

In this case, Teacher A needs to collect from Student 1, as a submission, an image of the completed learning material "Mathematics 1, Session 3" on which Student 1, who took Teacher A's class, has written his or her answers.

Teacher B also needs to collect from Student 2, as a submission, an image of the completed learning material "Mathematics 1, Session 3" on which Student 2, who took Teacher B's class, has written his/her answers.

Therefore, in this embodiment, a QR code 21A including a registration ID for each learning material in the teaching materials 20B is assigned, and a list of teachers who have taught classes using this learning material is displayed on the student terminal 400 that reads this registration ID.

In this embodiment, the student terminal 400 transfers image data showing an image of the completed learning material "Mathematics 1, Session 3" in which the student has written his/her answers to a submission destination corresponding to the teacher selected by each student. Note that in this embodiment, the image data showing an image of the completed learning material "Mathematics 1, Session 3" in which the student has written his/her answers is an example of a submission.

In this embodiment, this process ensures that even if multiple teachers each use the same teaching material 20B in different lessons, the submissions of students who attended the lesson are stored in the submission destination specified by the teacher who taught the lesson.

In this embodiment, it is necessary to generate and assign a QR code 21A to each learning material included in learning material 20B that needs to be submitted. In other words, in this embodiment, it is necessary to generate QR codes 21A in the same number as the number of lessons that will be held using learning material 20B and assign them to learning material 20B in advance. It is also possible that QR codes 21A are not assigned to learning materials that do not need to be submitted.

In this embodiment, the provider of the service using the server device 200A may specify a tenant ID and generate the QR code 21A, or a teacher using the teaching material 20B may generate the QR code 21A.

In addition, in this embodiment, the administrator of the teaching material 20B at the educational institution may generate the QR code 21A, or the creator of the teaching material 20B may generate the QR code 21A.

In addition, in this embodiment, the QR code 21A assigned to the teaching material 20B may be used by multiple teachers (instructors) belonging to the same educational institution. Furthermore, the QR code 21A assigned to the teaching material 20B may be used by teachers (instructors) belonging to all educational institutions (user environments) that own the tenant ID.

Below, the functional configuration of each device in the information processing system 100 of this embodiment will be described with reference to FIG. 23. FIG. 23 is a diagram showing an example of the functional configuration of each device in the second embodiment.

The server device 200A of this embodiment has an application group 240A. The server device 200A of this embodiment also has a registration information storage unit 261A, an application information storage unit 262A, a user information storage unit 263A, a submission information storage unit 264A, and a forwarding destination information storage unit 267.

The app group 240A of this embodiment includes, for example, a submission setting app 240-1, a survey creation app 240-2, a submission app 240-3, and a transfer app 240-4.

The transfer app 240-4 in this embodiment is an application that realizes a service that allows the student to select a destination for the submission sent from the student terminal 400 that read the QR code 21A, and identifies the submission app 240-3 that corresponds to the destination selected on the student terminal 400. The service realized by the transfer app 240-4 may be referred to as a transfer service.

In other words, forwarding application 240-4 is an example of a forwarding unit that selects a storage destination for information transmitted from the second terminal device that read the code, and causes the storage control unit to store the information transmitted from the second terminal device in the selected storage destination.

Next, each memory unit of the server device 200A will be described with reference to Figures 24 to 28.

Figure 24 is a diagram showing an example of a registration information storage unit of the second embodiment. In the registration information storage unit 261A of this embodiment, in addition to the registration information stored in the registration information storage unit 261 of the first embodiment, the registration IDs "Tag_adSendM101" and "Tag_adSendM102" are added.

The registration IDs "Tag_adSendM101" and "Tag_adSendM102" correspond to the input application IDs "AP_adSendM101" and "AP_adSendM102", respectively.

The registration information storage unit 261A also includes the registration IDs "Tag_TransferM101" and "Tag_TransferM102". These registration IDs correspond to the input application IDs "AP_TransferM101" and "AP_TransferM102", respectively.

The transfer service of this embodiment is realized by transfer apps identified by at least the app IDs "AP_TransferM101" and "AP_TransferM102."

In addition, in the registration information storage unit 261A of this embodiment, the registration ID "Tag_TransferM10X" is added in correspondence with each QR code 21A assigned to each learning material (number of lessons) included in the teaching materials 20B.

FIG. 25 is a diagram illustrating an example of an app information storage unit of the second embodiment. In the app information storage unit 262A illustrated in FIG. 25, app information including an app ID associated with the registration ID added in the registration information storage unit 261A is added.

Specifically, app information including, for example, app ID "AP_adSendM101" is added to app information storage unit 262A. The URL of the application identified by this app ID is "https://daas.com/ezSend&destinationID=DID_adM101", and destinationID is identification information for identifying the submission folder in which information is stored by submission application 240-3.

The application information storage unit 262A also stores application information including the application ID "AP_TransferM101". The URL of the application identified by this application ID is "https://daas.com/transfer&TrsID=TrID_M101", and the TrsID is identification information for identifying the destination folder in which the information transferred by the transfer application 240-4 is stored.

Figure 26 is a diagram showing an example of a user information storage unit of the second embodiment. In the user information storage unit 263A of this embodiment shown in Figure 26, a user identified by the user ID "ando@xxx.com" can also use the applications identified by the app IDs "AP_survey" and "AP_Portal."

Figure 27 is a diagram showing an example of a submission information storage unit of the second embodiment. The submission information storage unit 264A of this embodiment shown in Figure 27 has information items such as a submission destination ID, a tenant ID, a user ID, a first hierarchical level (class name), a second hierarchical level (number of classes), a file ID, a lecture room, a start time, and a class duration.

The values of the items "First Level (Class Name)" and "Second Level (Number of Lessons)" are referenced when generating the name of the destination folder that corresponds to the destination ID.

Specifically, the name of the destination folder corresponding to the destination ID is generated as "tenant ID/user ID/first level/second level".

Figure 28 is a diagram illustrating an example of a forwarding destination information storage unit in the second embodiment. The forwarding destination information storage unit 267 shown in Figure 28 has the following information items: forwarding destination ID, registration ID, and user ID.

The value of the item "Destination ID" corresponds to the registration ID embedded in the QR code 21A assigned to each learning material of the learning material 20B. In other words, the value of the item "Destination ID" is identification information that specifies the destination of the content written in the learning material 20B in which the QR code 21A is provided for each learning material (number of lessons) of the learning material 20B.

Next, the operation of the information processing system of this embodiment will be described with reference to FIG. 29. FIG. 29 is a sequence diagram showing the operation of the information processing system of the second embodiment.

In this embodiment, the student terminal 400 receives an instruction from the student to read a QR code (step S2901), and the control unit 430 instructs the imaging unit 460 to capture an image of the QR code, and the imaging unit 460 causes the imaging device to capture the QR code (step S2902).

Next, the control unit 430 of the student terminal 400 obtains the registration ID and the initial access URL (step S2903).

In this embodiment, the QR code to be imaged is QR code 21A attached to teaching material 20B. In the following explanation of FIG. 29, the registration ID "Tag_TransferM101" is obtained from QR code 21A.

The process from step S2904 to step S2912 in FIG. 29 is the same as the process from step S2004 to step S2012 in FIG. 20, except that the registration ID is replaced with "Tag_TransferM101", so a description of it will be omitted.

In step S2912, the access token sent from the authentication unit 230 of the server device 200A to the browser unit 440 includes the registration ID "Tag_TransferM101", which is an argument of the login request as a guest. The access token is also stored in the browser unit 440.

Next, the browser unit 440 transmits a connection request to the application determination unit 220 together with the access token (step S2913). The access token at this time includes the registration ID "Tag_TransferM101".

The application determination unit 220 makes a redirect request to the transfer application 240-4 that realizes the service associated with the registration ID included in the access token (step S2914).

This redirect request includes the registration ID "Tag_TransferM101", the URL of the transfer destination for the app ID "AP_TransferM101" that corresponds to the registration ID "Tag_TransferM101", and the transfer destination ID.

The browser unit 440 receives the redirect request from the application determination unit 220 and sends a request to the transfer application 240-4 indicated by the application ID "AP_TransferM101" (step S2915).

At this time, the request includes the access token and the transfer destination ID "TrID_M101" that indicates the transfer destination corresponding to the application ID "AP_TransferM101."

Upon receiving the request, the transfer application 240-4 refers to the transfer destination information storage unit 267, obtains the registration ID and user ID corresponding to the transfer destination ID "TrID_M101", and transmits the URL of a selection screen containing a list of users (teachers) corresponding to the user IDs to the student terminal 400 (step S2916).

The browser unit 440 receives this URL and displays a teacher selection screen (step S2917). In this case, the user IDs corresponding to the forwarding destination ID "TrID_M101" are "tanaka@xxx.com" and "ando@xxx.com", so a list of names corresponding to these user IDs is displayed as the teacher selection screen.

When the browser unit 440 receives the selection of a teacher on the selection screen (step S2918), it sends the user ID corresponding to the selected teacher and the transfer destination ID together with the access token to the transfer app 240-4 (step S2919).

The transfer application 240-4 receives the user ID and the transfer destination ID, overwrites the access token with the registration ID associated with the user ID in the transfer destination information storage unit 267, and makes a redirect request to the application determination unit 220 (step S2920).

Specifically, for example, if the selected user ID is "tanaka@xxx.com", the registration ID of the access token is overwritten with "Tag_SendM101".

In this embodiment, this process specifies the transfer destination of image data captured by the terminal device 400 to the storage destination indicated by the URL associated with the registration ID "Tag_SendM101".

The browser unit 440 receives the redirect request and sends a connection request to the application determination unit 220 (step S2921).

The processing from step S2921 to step S2931 is similar to the processing from step S2013 to step S2023 in FIG. 20, so the explanation is omitted.

Next, referring to FIG. 30, the screen transitions of the student terminal 400 of this embodiment will be described. FIG. 30 is a diagram illustrating the screen transitions of the student terminal of the second embodiment.

In this embodiment, in step S2910, screen 222 is displayed, student information is entered into input field 222a, and when operation button 222b is operated, screen 222 transitions to screen 227.

Screen 227 is a teacher selection screen that is displayed on the browser unit 440 in step S2917 of FIG. 29.

The screen 227 includes a display field 227a, a selection field 227b, and an operation button 227c. The display field 227a displays the name of the teaching material 20B, etc. The name of the teaching material 20B may be embedded in the QR code 21A, for example.

The selection field 227b displays a list of the names of users indicated by the user IDs associated with the registration IDs contained in the QR code 21A read by the student terminal 400 in the forwarding destination information storage unit 267, as well as a selection button.

In screen 227, selection field 227b displays a list of user names, with either Teacher A (Mr. A) or Teacher B (Mr. B) selectable. In addition to the list of teacher names, screen 227 may also display an input field for directly entering a keyword (passcode or password) common to the student and the teacher in charge. The user names displayed in the list in selection field 227b only need to correspond to the names of users who will receive the submitted work, and the teacher in charge is merely one example.

When a teacher is selected on screen 227 and operation button 227c is operated, screen 227 transitions to screen 223.

In this embodiment, when operation button 223b is operated on screen 223 and teaching material 20B is imaged on screen 225, the survey results and image data of completed teaching material 20B with answers written in are stored as submissions in a transfer destination corresponding to the teacher selected on screen 227.

As described above, according to this embodiment, even if multiple teachers teach lessons using the same teaching materials with the same QR code, the submissions for each lesson can be stored in the submission destination that corresponds to the teacher who taught the lesson.

In the above example, when a user's name (teacher) is selected in the selection field 227b, the submission destination (submission destination ID) stored in the submission information storage unit 264 is uniquely identified by the information (URL) further associated with the application ID associated with the registration ID corresponding to the user. However, it is also possible to associate multiple submission destinations (submission destination IDs) with an application ID.

In such a case, for example, after selecting the user's name (teacher), information indicating the submission destination associated with the app ID (information such as the name of the folder corresponding to the submission destination) can be sent from server device 200A to terminal device 400, thereby displaying information indicating multiple submission destinations and their corresponding folders, etc., on the screen of terminal device 400.

Furthermore, when a specific submission destination (e.g., a folder icon or name) is selected by the user (student) submitting the work from among information indicating the submission destination, such as a folder, displayed on the screen of the terminal device 400, the terminal device 400 identifies the selected submission destination. The terminal device 400 then transmits information about the selected submission destination (submission destination ID) to the server device 200A. By receiving this information, the server device 200A can identify the submission destination ID. Note that the submission destination (folder) that the user submitting the work should select may be determined in advance by a rule, or may be specified by the user receiving the submission by a means of communication, such as verbal communication.

In addition, in the above-described embodiment, the teaching materials are in paper form, but the teaching materials are not limited to paper form. The teaching materials (including answer sheets and handouts) do not necessarily have to be in paper form, but may be distributed as electronic data and displayed on electronic devices owned by each user.

In the above-described embodiment, examples of submissions include items that are primarily used in educational institutions, such as answer sheets and teaching materials, but submissions are not limited to these. Submissions include meeting materials, explanatory materials, handouts, etc.

In addition, in the above-described embodiment, an example was described in which a code such as a QR code is attached to a submission such as a handout or teaching material, but the handout, teaching material, or other submission and the code do not necessarily have to be integrated.

The code may be attached to a medium other than the submitted item. Specifically, for example, a code corresponding to a submitted item such as a handout or teaching material may be displayed as an image on a screen displayed on a display used by a teacher for explanations. In such a case, a student first reads the code displayed as an image, and then takes a picture of the item to be submitted.

In addition, if the code is attached to a medium separate from the submission, the submission itself may be prepared by the submitting user. Specifically, for example, the submission may be image data of a subject photographed by the submitting user (student), or image data of the contents written on a piece of paper prepared by the submitting user (student).

In this way, even if the handouts or teaching materials without codes have already been distributed, or if the handouts or teaching materials themselves are not needed, the submission destination can be flexibly changed depending on the type of lesson. Note that the type of lesson includes not only classes where students gather in a classroom to take the lesson, but also classes where students take the lesson online from a remote location.

In addition, in the above-described embodiment, the party receiving the submission (submission destination) is described as a teacher, and the party submitting the submission (submitter) is described as a student, but the relationship between the submission destination and the submitter is not limited to that between a teacher and a student.

The example in which the relationship between the submission destination and the submitter is that of a teacher and a student is just one example, and the present invention is applicable to any usage scenario in which there is a user who receives some kind of submission and a user who submits it. Specifically, usage scenarios to which the present invention is applicable include, for example, seminars and classes between lecturers and students, and meetings and briefings between presenters and audience members. Also, as mentioned above, it does not matter whether such usage scenarios are held offline or online.

The functions of the embodiments described above can be realized by one or more processing circuits. In this specification, the term "processing circuit" includes a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, and devices such as an ASIC (Application Specific Integrated Circuit), DSP (digital signal processor), FPGA (field programmable gate array), and conventional circuit modules designed to execute each function described above.

Furthermore, the devices described in each embodiment represent only one of multiple computing environments for implementing the embodiments disclosed herein.

In some embodiments, the server apparatus 200 includes multiple computing devices, such as a server cluster, configured to communicate with one another over any type of communications link, including a network, shared memory, and the like, to perform the processes disclosed herein. Similarly, the terminal apparatus may include multiple computing devices configured to communicate with one another. Additionally, the server apparatus and terminal apparatus may be configured to share the disclosed process steps in various combinations.

The present invention has been described above based on each embodiment, but the present invention is not limited to the requirements shown in the above embodiments. These points can be changed without departing from the spirit of the present invention, and can be appropriately determined according to the application form.

REFERENCE SIGNS LIST 100 Information processing system 200, 200A Server device 210 Communication unit 220 Application determination unit 230 Authentication unit 240 Input application group 261 Registration information storage unit 262 Application information storage unit 263 User information storage unit 264 Submission information storage unit 265 Questionnaire information storage unit 266 Submission information storage unit 267 Transfer destination information storage unit 300, 400 Terminal device 330, 430 Control unit 340, 440 Browser unit 350, 450 Storage unit

Patent No. 6098193

Claims (12)

An information processing system including an information processing device capable of communicating with a plurality of terminal devices,
a first setting unit that sets information indicating a first input item, which is displayed on a first terminal device that requests generation of a code including identification information that identifies a service provided by the information processing device, in association with the service;
a second setting unit that sets information indicating a second input item different from the first input item, which is displayed on a second terminal device that reads the code, in association with the service before generating the code ;
the first setting unit sets a storage destination and a login method for information transmitted from the second terminal device,
The login method of the information processing system includes a method of logging in by inputting account information and a method of permitting login as a guest . The information processing system according to claim 1, wherein the value inputted into the first input item indicates a storage destination of the information transmitted from the second terminal device. The information processing system according to claim 1 or 2, wherein the value entered in the second input item is an answer to a question included in a questionnaire displayed when the second terminal device reads the code. The information processing system according to any one of claims 1 to 3, further comprising a code generating unit that, upon receiving a request to generate the code, generates a code including identification information for identifying the service, an input value of the first input item, and information for displaying a survey including the second input item. a storage control unit that stores information transmitted from the second terminal device that reads the code in a storage destination indicated by an input value of the first input item;
The information processing system according to claim 1 , wherein the transmitted information includes a survey result after a value is input in the second input item. The information processing system according to claim 5, further comprising a transfer unit that selects a storage destination for the information transmitted from the second terminal device that reads the code, and causes the storage control unit to store the information transmitted from the second terminal device in the selected storage destination. The information processing system according to claim 5 or 6, wherein the transmitted information includes image data showing an image of the printed matter on which the code is printed, captured by an imaging device included in the second terminal device. 8. The information processing system according to claim 1, wherein the first setting unit sets items of guest information to be input when logging in as a guest. An information processing device capable of communicating with a plurality of terminal devices,
a first setting unit that sets information indicating a first input item, which is displayed on a first terminal device that requests generation of a code including identification information that identifies a service provided by the information processing device, in association with the service;
a second setting unit that sets information indicating a second input item different from the first input item, which is displayed on a second terminal device that reads the code, in association with the service before generating the code ;
the first setting unit sets a storage destination and a login method for information transmitted from the second terminal device,
The login method of the information processing device includes a method of logging in by inputting account information and a method of permitting login as a guest . An information processing method by an information processing device capable of communicating with a plurality of terminal devices, the information processing device comprising:
setting information indicating a first input item, which is displayed on a first terminal device requesting generation of a code including identification information for identifying a service provided by the information processing device , in association with the service by a first setting unit ;
setting information indicating a second input item different from the first input item, which is displayed on a second terminal device that reads the code , in association with the service by a second setting unit before generating the code ;
the first setting unit sets a storage destination and a login method for information transmitted from the second terminal device,
The information processing method , wherein the login method includes a method of logging in by inputting account information and a method of permitting login as a guest . An information processing device capable of communicating with a plurality of terminal devices,
setting information indicating a first input item, which is displayed on a first terminal device requesting generation of a code including identification information for identifying a service provided by the information processing device , in association with the service by a first setting unit ;
executing a process of setting information indicating a second input item different from the first input item, which is displayed on a second terminal device that reads the code , in association with the service by a second setting unit before generating the code ;
the first setting unit sets a storage destination and a login method for information transmitted from the second terminal device,
The log-in method includes a method of logging in by inputting account information and a method of permitting login as a guest . a first terminal that requests generation of a code including identification information that identifies a service provided by an information processing device;
a second terminal for reading the code;
a first setting unit that sets information indicating a first input item, which is displayed on the first terminal that requests the generation of the code, in association with the service based on information received from the first terminal;
a second setting unit that sets information indicating a second input item, which is displayed on the second terminal that reads the code, in association with the service before generating the code based on information received from the first terminal ,
the first setting unit sets a storage destination and a login method for information transmitted from the second terminal,
The login method includes a method of logging in by inputting account information and a method of permitting login as a guest .

Images