JP2023002290A - Server device, message system, terminal device, program, and message providing method - Google Patents

Abstract

To provide a server device, a message system, a terminal device, a program, and a message providing method that enable guardians to communicate with each other without the need to exchange contact addresses.SOLUTION: A server device comprises a storage part and a providing part. The storage part stores, in response to receiving certification information certifying that a user belongs to a first group, the user who is a sender of the certification information as a user of the first group. The storage part can associatively the user and attributes of the user. The providing part can provide message information for the user selected by a selection part for selecting the user corresponding to the attributes among users in the first group.SELECTED DRAWING: Figure 3

Description

The present invention relates to a server device, a message system, a terminal device, a program, and a message providing method.

Parents such as students who go to school etc. need to keep in touch with each other. At this time, it is necessary to exchange contact information such as telephone numbers, e-mail addresses, or IDs (identifiers) of SNS (social networking service). However, exchanging contact information may lead to troubles between parents.

Japanese Patent Application Laid-Open No. 2004-192283

The problem to be solved by the embodiments of the present invention is to provide a server device, a message system, a terminal device, a program, and a message providing method that enable communication between parents without the need to exchange contact information. is.

A server device of an embodiment includes a storage unit and a providing unit. The storage unit stores the user who sent the proof information as a user of the first group based on the reception of the proof information proving that the user belongs to the first group. The storage unit can store the user and the attribute of the user in association with each other. The providing unit enables the message information to be provided to the users selected by the selecting unit that selects users corresponding to the attributes from among the users of the first group.

The present invention allows communication between parents without the need to exchange contact information.

1 is a block diagram showing an example of a message system according to an embodiment and an example of a configuration of main parts of components included in the message system; FIG. 2 is a flowchart showing an example of processing by a processor of the school terminal in FIG. 1; FIG. 2 is a flow chart showing an example of processing by a processor of the message server in FIG. 1; FIG. FIG. 2 is a flow chart showing an example of processing by a processor of the message server in FIG. 1; FIG. FIG. 2 is a flow chart showing an example of processing by a processor of the guardian terminal in FIG. 1; FIG. FIG. 2 is a flow chart showing an example of processing by a processor of the guardian terminal in FIG. 1; FIG. 2 is a flow chart showing an example of processing by the processor of the guardian terminal in FIG. 1 or the processor of the school terminal in FIG. 1; FIG. 2 is a flow chart showing an example of processing by a processor of the guardian terminal in FIG. 1; FIG.

A message system according to an embodiment will be described below with reference to the drawings. In addition, each drawing used for description of the following embodiment may abbreviate|omit a structure for description. Also, the same reference numerals refer to similar elements throughout the drawings and the specification.
FIG. 1 is a block diagram showing an example of a message system 1 according to an embodiment and an example of a main configuration of components included in the message system 1. As shown in FIG. The message system 1 is a system that provides message services to terminals and the like. The message service in this embodiment is sent from the school (kindergarten, nursery school, elementary school, junior high school, high school, university, special support school, vocational school, miscellaneous school, unlicensed school, or various educational training facilities). Or students, etc. (hereinafter collectively referred to as "students") guardians or relatives other than guardians (hereinafter, "guardians or relatives other than guardians" are simply "protected This is a service that allows anonymous messages to be sent to and exchanged between guardians. In addition, no personally identifiable information is required to use the message service. Examples of information that can identify an individual include name, telephone number, e-mail address, credit card number, and personal identification code (information for biometric authentication (DNA sequence, face, iris, fingerprint, palm print, and vein pattern). and behavioral features such as gait), my number, driver's license number, passport number, basic pension number, health insurance card number, etc.). The message system 1 includes, as an example, a message server 100, a school terminal 200, a printer 300 and a parent's terminal 400. FIG. Although FIG. 1 shows one device each of the message server 100, the school terminal 200, the printer 300, and the parent terminal 400, the number of devices is not limited.

A message server 100, a school terminal 200, a printer 300, and a guardian terminal 400 are connected to a network NW. Network NW is a communication network typically including the Internet. The network NW is typically a communication network including a WAN (wide area network). The network NW may be a communication network including a private network such as an intranet. The network NW may be a communication network including a LAN (local area network). Also, the network NW may be a wireless line, a wired line, or a mixture of wireless and wired lines. Also, the network NW may be a communication network including a dedicated line or a public mobile telephone network.

The message server 100 is, for example, a server device for providing message services. The message server 100 includes, as an example, a processor 110 , a ROM (read-only memory) 120 , a RAM (random-access memory) 130 , an auxiliary storage device 140 and a communication I/F (interface) 150 . A bus 160 or the like connects these units.

The processor 110 is a central portion of a computer that performs processing such as calculation and control necessary for the operation of the message server 100, and performs various calculations and processes. The processor 110 includes, for example, a CPU (central processing unit), MPU (micro processing unit), SoC (system on a chip), DSP (digital signal processor), GPU (graphics processing unit), ASIC (application specific integrated circuit), Examples include PLDs (programmable logic devices) and FPGAs (field-programmable gate arrays). Alternatively, processor 110 is a combination of several of these. Also, the processor 110 may be a combination of these with a hardware accelerator or the like. Processor 110 controls each part to implement various functions of message server 100 based on programs such as firmware, system software, and application software stored in ROM 120 or auxiliary storage device 140 . Also, the processor 110 executes processing described below based on the program. Part or all of the program may be incorporated in the circuit of processor 110 .

The ROM 120 and RAM 130 are the main memory devices of the computer with the processor 110 at its core.
The ROM 120 is a non-volatile memory exclusively used for reading data. The ROM 120 stores, for example, firmware among the above programs. The ROM 120 also stores data used when the processor 110 performs various processes.
The RAM 130 is a memory used for reading and writing data. The RAM 130 is used as a work area or the like for storing data temporarily used when the processor 110 performs various processes. RAM 130 is typically volatile memory.

Auxiliary storage device 140 is an auxiliary storage device of a computer centered on processor 110 . The auxiliary storage device 140 is, for example, an EEPROM (electric erasable programmable read-only memory), a HDD (hard disk drive), or a flash memory. The auxiliary storage device 140 stores, for example, system software and application software among the above programs. Further, the auxiliary storage device 140 stores data used by the processor 110 to perform various processes, data generated by the processes performed by the processor 110, various setting values, and the like.

The auxiliary storage device 140 also stores a message database 141 and a school database 142, for example.

The message database 141 is a database that manages and stores messages in the message service.

The school database 142 is a database that manages and stores information about each school that uses the message service.

Communication I/F 150 is an interface for message server 100 to communicate via network NW or the like. The message server 100 communicates with, for example, the school terminal 200 and the guardian terminal 400 via the communication I/F 150 and the network NW.

The bus 160 includes a control bus, an address bus, a data bus, etc., and transmits signals exchanged with each part of the message server 100 .

The school terminal 200 is a device used by school staff to use the message service. The school terminal 200 is, for example, a PC (personal computer), a tablet terminal, a smart phone, or the like. The school terminal 200 contains the processor 210, ROM220, RAM230, the auxiliary storage device 240, communication I/F250, the input device 260, and the display device 270 as an example. A bus 280 or the like connects these units.

The processor 210 is a central portion of a computer that performs processing such as calculation and control necessary for the operation of the school terminal 200, and performs various calculations and processing. Processor 210 is, for example, a CPU, MPU, SoC, DSP, GPU, ASIC, PLD, FPGA, or the like. Alternatively, processor 210 is a combination of several of these. Also, the processor 210 may be a combination of these with a hardware accelerator or the like. Processor 210 controls each part to implement various functions of school terminal 200 based on programs such as firmware, system software, and application software stored in ROM 220 or auxiliary storage device 240 . Also, the processor 210 executes processing described below based on the program. Part or all of the program may be incorporated in the circuit of processor 210 .

The ROM 220 and RAM 230 are the main storage devices of the computer with the processor 210 at its core.
The ROM 220 is a non-volatile memory exclusively used for reading data. The ROM 220 stores, for example, firmware among the above programs. The ROM 220 also stores data used when the processor 210 performs various processes.
The RAM 230 is a memory used for reading and writing data. The RAM 230 is used as a work area for storing data temporarily used when the processor 210 performs various processes. RAM 230 is typically volatile memory.

Auxiliary storage device 240 is an auxiliary storage device of a computer centered on processor 210 . Auxiliary storage device 240 is, for example, EEPROM, HDD, or flash memory. The auxiliary storage device 240 stores, for example, system software and application software among the above programs. Further, the auxiliary storage device 240 stores data used by the processor 210 in performing various processes, data generated by the processes in the processor 210, various setting values, and the like.

Communication I/F 250 is an interface for school terminal 200 to communicate via network NW or the like. The school terminal 200 communicates with the message server 100 and the printer 300 via the communication I/F 250 and the network NW, for example.

The input device 260 receives operations by the operator of the school terminal 200 . The input device 260 is, for example, a keyboard, keypad, touchpad, mouse or controller. Also, the input device 260 may be a device for voice input.

The display device 270 displays a screen for notifying the operator of the school terminal 200 of various information. The display device 270 is, for example, a display such as a liquid crystal display or an organic EL (electro-luminescence) display. A touch panel can also be used as the input device 260 and the display device 270 . That is, a display panel included in the touch panel can be used as the display device 270 , and a touch pad included in the touch panel can be used as the input device 260 .

The bus 280 includes a control bus, an address bus, a data bus, etc., and transmits signals to and from each part of the school terminal 200 .

The printer 300 is a device that prints images and the like. The printer 300 prints images transmitted from the school terminal device 200, for example. A character is a kind of image. The school terminal device 200, for example, instructs the printer 300 to print via the network NW. Alternatively, the school terminal device 200 instructs the printer 300 to print using communication using a USB (universal serial bus) or other communication.

A parent terminal 400 is a device used by a parent or the like to use the message service. Parent terminal 400 is, for example, typically a smart phone or a tablet terminal. Alternatively, parent terminal 400 may be a PC or the like. Parent terminal 400 includes a processor 410 , ROM 420 , RAM 430 , auxiliary storage device 440 , communication I/F 450 , touch panel 460 and camera 470 as an example. A bus 480 or the like connects these units. Parent terminal 400 is an example of a terminal device.

The processor 410 is a central portion of a computer that performs processing such as calculation and control required for the operation of the guardian terminal 400, and performs various calculations and processing. Processor 410 is, for example, a CPU, MPU, SoC, DSP, GPU, ASIC, PLD, or FPGA. Alternatively, processor 410 is a combination of several of these. Also, the processor 410 may be a combination of these with a hardware accelerator or the like. Processor 410 controls each part to realize various functions of guardian terminal 400 based on programs such as firmware, system software, and application software stored in ROM 420 or auxiliary storage device 440 . Also, the processor 410 executes processing described below based on the program. Part or all of the program may be incorporated in the circuit of processor 410 .

The ROM 420 and RAM 430 are the main storage devices of the computer with the processor 410 at its core.
The ROM 420 is a non-volatile memory exclusively used for reading data. The ROM 420 stores, for example, firmware among the above programs. The ROM 420 also stores data used when the processor 410 performs various processes.
The RAM 430 is a memory used for reading and writing data. The RAM 430 is used as a work area or the like for storing data temporarily used when the processor 410 performs various processes. RAM 430 is typically volatile memory.

Auxiliary storage device 440 is an auxiliary storage device of a computer centered on processor 410 . Auxiliary storage device 440 is, for example, EEPROM, HDD, or flash memory. Auxiliary storage device 440 stores, for example, system software and application software among the programs described above. The application software includes application software for using the message service (hereinafter referred to as "message application"). Further, the auxiliary storage device 440 stores data used by the processor 410 to perform various processes, data generated by the processes performed by the processor 410, various setting values, and the like.

Communication I/F 450 is an interface for guardian terminal 400 to communicate via network NW or the like. Guardian terminal 400 communicates with message server 100 or the like via communication I/F 150 and network NW, for example.

The touch panel 460 is, for example, a stack of a display such as a liquid crystal display or an organic EL display and a pointing device for touch input. The display included in touch panel 460 functions as a display device that displays a screen for notifying the operator of parent terminal 400 of various types of information. Further, the touch panel 460 functions as an input device that receives touch operations by the operator.

Camera 470 captures images. The camera 470 also outputs captured image data. A moving image is a kind of image.

The bus 480 includes a control bus, an address bus, a data bus, etc., and transmits signals exchanged with each part of the guardian terminal 400 .

The operation of the message system 1 according to the embodiment will be described below with reference to FIGS. 2 to 8 and the like. It should be noted that the contents of the processing in the following description of the operation are examples, and various processing that can obtain similar results can be used as appropriate. 2 and 7 are flowcharts showing an example of processing by the processor 210 of the school terminal 200. FIG. The processor 210 executes the processes of FIGS. 2 and 7 based on programs stored in the ROM 220, the auxiliary storage device 240, or the like, for example. 3 and 4 are flow charts showing an example of processing by processor 110 of message server 100. FIG. The processor 110 executes the processes of FIGS. 3 and 4 based on programs stored in the ROM 120, the auxiliary storage device 140, or the like, for example. 5 to 8 are flowcharts showing an example of processing by the processor 410 of the guardian terminal 400. FIG. Processor 410 executes the processes of FIGS. 5 to 8 based on a program such as a message application stored in ROM 420 or auxiliary storage device 440, for example. Note that the processing in FIG. 7 is processing common to the school terminal 200 and the guardian terminal 400 .

At step ST11, the processor 210 determines whether or not to request the message server 100 to create a message group. A message group is, for example, a school-based group. In the message service, messages can only be sent and received within the same group. The operator of the school terminal 200 uses the input device 260 or the like to input creation information required to create a message group, for example. Then, the operator operates, for example, a creation button for instructing creation of a message group using the input device 260 or the like. For example, the processor 210 determines to request creation of a message group in response to the creation button being operated while creation information is input. Note that the creation information includes, for example, class information and deletion time information. The class information is information on each class in the school. The class information includes, for example, what year and group each class is in, the number of people in the class, and the like. Also, the deletion time information is information indicating the date and time when the message group is deleted. Note that a default value may be automatically entered as the date and time for deleting the message group. The default value is, for example, the date of admission to school and promotion to the next grade, which is 00:00:00 on April 1, the day after graduation. The deletion time information may indicate the date and time of deletion according to the length of time until deletion. If processor 210 does not determine to request creation of a message group, it determines No in step ST11 and proceeds to step ST12.

In step ST12, processor 210 determines whether or not to request message server 100 to issue an invitation code. The invitation code will be described later. If processor 210 does not request the issuance of an invitation code, it determines No in step ST12 and returns to step ST11. Thus, the processor 210 enters a standby state in which steps ST11 and ST12 are repeated until it determines to request the creation of a message group or to request the issuance of an invitation code.

If the processor 210 determines to request creation of a message group while in the standby state of steps ST11 and ST12, it determines Yes in step ST11 and proceeds to step ST13.

In step ST13, processor 210 generates a creation request. Processor 210 generates a production request to include production information entered by, for example, an operator. The creation request is information requesting the message server 100 to create a message group based on the creation information. After generating the creation request, processor 210 instructs communication I/F 250 to transmit the creation request to message server 100 . Upon receiving this transmission instruction, communication I/F 250 transmits the creation request to message server 100 . The transmitted creation request is received by communication I/F 150 of message server 100 .

On the other hand, in step ST21 of FIG. 3, processor 110 of message server 100 determines whether communication I/F 150 has received a creation request. If the creation request is not received, processor 110 determines No in step ST21 and proceeds to step ST22.

In step ST22, processor 110 determines whether or not a code request has been received by communication I/F 150. FIG. If the code request is not received, processor 110 determines No in step ST22 and proceeds to step ST23.

In step ST23, processor 110 determines whether communication I/F 150 has received a registration request. If the registration request is not received, processor 110 determines No in step ST23 and proceeds to step ST24.

In step ST<b>24 , processor 110 determines whether registration information has been received by communication I/F 150 . If the registration information is not received, processor 110 determines No in step ST24 and proceeds to step ST25 in FIG.

In step ST25, processor 110 determines whether communication I/F 150 has received an attribute change request. If the attribute change request is not received, processor 110 determines No in step ST25 and proceeds to step ST26.

In step ST26, processor 110 determines whether communication I/F 150 has received a message transmission request. If the message transmission request is not received, processor 110 determines No in step ST26 and proceeds to step ST27.

In step ST27, processor 110 determines whether communication I/F 150 has received an inquiry request. If the inquiry request is not received, processor 110 determines No in step ST27 and proceeds to step ST28.

In step ST28, the processor 110 determines whether or not the date and time for deleting the message group has arrived. Processor 110 determines No in step ST28 and returns to step ST21 of FIG. 3 if the deletion date and time of the message group has not yet come. Thus, the processor 110 repeats steps ST21 to ST28 until a creation request, a code request, a registration request, registration information, an attribute change request, a message transmission request, or an inquiry request is received, or until the message group deletion date and time is reached. It will be in a standby state. Code requests, registration requests, registration information, attribute change requests, message transmission requests, and inquiry requests will be described later.

If the processor 110 receives a creation request while it is in the standby state of steps ST21 to ST28, it determines Yes in step ST21 and proceeds to step ST29.
At step ST29, processor 110 creates a message group based on the creation information included in the creation request. For this purpose, processor 110 assigns a group ID to the message group. The processor 110 then stores the creation information in the school database 142 in association with the group ID. A group ID is identification information unique to each message group. Also, the processor 110 assigns a class ID to each class included in the class information. A class ID is identification information unique to each class. For each class, the processor 110 associates the class ID with the class information of the class identified by the class ID and stores them in the school database 142 . The class information includes, for example, information indicating what year and group the class identified by the class ID belongs to, information indicating the number of students in the class, and the like. The processor 110 also associates the group ID with each class ID so that each class is a class within the school identified by the group ID.

In step ST<b>30 , processor 110 instructs communication I/F 150 to transmit the creation notification to school terminal 200 . The creation notification is, for example, information that notifies that a message group has been created. Alternatively, processor 110 may instruct to send a creation failure notification instead of a creation notification if the message group is not created for some reason. The creation failure notification is, for example, information notifying that the message group could not be created. Upon receiving the transmission instruction, the communication I/F 150 transmits a creation notification or a creation failure notification to the school terminal 200 . The transmitted creation notification or creation failure notification is received by the communication I/F 250 of the school terminal 200 . The processor 110 returns to step ST21 after the process of step ST30.

On the other hand, in step ST14 of FIG. 2, the processor 210 of the school terminal 200 waits for the communication I/F 250 to receive a creation notification or a creation failure notification. If the notification of creation has been received, the processor 210 determines Yes in step ST14 and proceeds to step ST15.

At step ST15, the processor 210 generates an image corresponding to the creation result screen based on the creation notification or creation failure notification. Processor 210 then directs display device 270 to display this generated image. Upon receiving the display instruction, the display device 270 displays the creation result screen. After the process of step ST15, the processor 210 returns to step ST11 when, for example, the display of the creation result screen is completed.

The creation result screen is a screen showing the creation result of the message group. The creation result screen when the creation notification is received in step ST14 is, for example, a screen showing that a message group has been created. The creation result screen when the creation failure notification is received in step ST14 is, for example, a screen indicating that the message group was not created.

An invitation code is required for parents to participate in message groups. The invitation code is different for each class, for example. As an example, the homeroom teacher of each class distributes a printout of the invitation code to the students in the class. The invitation code printed on the print is, for example, in the form of a two-dimensional code such as a QR code (registered trademark). A student who receives the print from a homeroom teacher or the like returns home, for example, and hands the print to a guardian. The parent thus obtains the invitation code. However, the method of distributing the invitation code from the school side to the guardian may be another method. In addition, the invitation code that the parent obtains does not have to be in a printed state. For example, a parent may somehow obtain an invitation code in electronic form. Also, the invitation code may be distributed to the guardian in a format other than the two-dimensional code.
In this way, the invitation code can only be obtained by parents of students who belong to the school that created the message group. A group of guardians (guardian group) of students belonging to the school is an example of the first group. Therefore, the invitation code is an example of certification information that proves belonging to the first group.
Also, the invitation code is different for each class. A group of guardians of students belonging to the same class is an example of the second group. Therefore, the invitation code is an example of proof information proving belonging to the second group within the first group.

The school staff or the like operates the school terminal 200 to print the invitation code. For this purpose, the school staff operates the input device 260 or the like to input the invitation information necessary for issuing the invitation code, and then operates an issue button or the like for instructing the issue of the invitation code. The invitation information includes, for example, a class for issuing an invitation code, the number of invitation codes to be printed, and the like.

For example, the processor 210 determines to request the issuance of the invitation code in response to the operation of instructing the issuance of the invitation code, such as the operation of the issue button. If the processor 210 determines to request the issuance of an invitation code while in the standby state of steps ST11 and ST12, it determines Yes in step ST12 and proceeds to step ST16.

In step ST16, processor 210 generates a code request. The code request contains invitation information. A code request is information instructing to send an invitation code for the class specified in the invitation information. After generating the code request, processor 210 instructs communication I/F 250 to transmit the code request to message server 100 . Upon receiving this transmission instruction, communication I/F 250 transmits the code request to message server 100 . The transmitted code request is received by communication I/F 150 of message server 100 .

On the other hand, if the processor 110 of the message server 100 receives a code request while in the waiting state of steps ST21 to ST28, it determines Yes in step ST22 of FIG. 3 and proceeds to step ST31.
In step ST31, processor 110 generates an invitation code for the class specified by the invitation information. Processor 110 then stores the invitation code in school database 142 in association with the class ID of the class. Note that the processor 110 may set an expiration date for the invitation code. The processor 110 sets the deadline by, for example, associating code deadline information indicating the deadline with the generated invitation code and storing it in the school database 142 . The deadline is set in advance by, for example, a manager of the message group or a manager or designer of the message server 100 . Alternatively, the invitation information may contain information indicating the deadline. In this case, processor 110 sets the deadline included in the invitation information. Note that the processor 110 does not need to generate a new invitation code if there is already an invitation code associated with the class ID of the class specified by the invitation information and the invitation code has not expired. . If a new invitation code is not generated, processor 110 uses the invitation code associated with the class ID in place of the invitation code generated in step ST31 in the process of next step ST32.

At step ST<b>32 , processor 110 instructs communication I/F 150 to transmit the invitation code generated at step ST<b>31 to school terminal 200 . Upon receiving this transmission instruction, communication I/F 150 transmits the invitation code to message server 100 . The transmitted invitation code is received by communication I/F 250 of school terminal 200 . The processor 110 returns to step ST21 after the process of step ST32.

On the other hand, processor 210 of school terminal 200 waits for an invitation code to be received by communication I/F 150 in step ST17 of FIG. If the invitation code is received, processor 210 determines Yes in step ST17 and proceeds to step ST18.

At step ST18, processor 210 generates an image for printing. Images for printing include an invitation code encoded in two dimensions, an image showing which class the invitation code is for, an image showing how to use the message service, and an image showing how to obtain the message app. include. Processor 210 two-dimensionally encodes the invitation code received in step ST12 in order to generate a print image. Alternatively, processor 110 of message server 100 may two-dimensionally encode the invitation code. In this case, the invitation code sent by message server 100 in step 32 of FIG. 3 is two-dimensionally coded.

In step ST19, the processor 210 instructs the printer 300 to print the print images generated in step ST18 by the number of prints included in the invitation information. In response to this instruction, the printer 300 prints the corresponding number of images for printing. The processor 210 returns to step ST11 after the process of step ST19.
The staff of the school distributes the prints printed in this way to the students of the same class as the class entered as the invitation information.

A method for a guardian who has obtained an invitation code to join the message group will be described below. The parent who is the operator of the parent terminal 400 causes the camera 470 of the parent terminal 400 to display an invitation code in the form of a two-dimensional code, for example.
At step ST61 in FIG. 5, processor 410 of parent terminal 400 waits for acquisition of an invitation code. The processor 410 acquires the invitation code by reading the invitation code from the two-dimensional code included in the image captured by the camera 470, for example. When processor 410 acquires the invitation code, it determines Yes in step ST61 and proceeds to step ST62.

At step ST62, processor 410 generates a registration request. The registration request includes the invitation code acquired in step ST61. The registration request is, for example, information indicating a desire to register for participation in the message group using the invitation code. The registration request preferably does not contain personally identifiable information, and particularly preferably does not contain the names, phone numbers and e-mail addresses of students and parents. This is to enhance the anonymity of the message service. After generating the registration request, processor 410 instructs communication I/F 450 to transmit the registration request to message server 100 . Upon receiving this transmission instruction, communication I/F 450 transmits the registration request to message server 100 . The transmitted registration request is received by communication I/F 150 of message server 100 .
Note that the registration request including the invitation code is an example of certification information. Processor 410 functions as an example of a transmission unit that transmits an invitation code or a registration request to message server 100 by performing the process of step ST62 in cooperation with communication I/F 450 . Alternatively, processor 410 functions as an example of a transmission unit by controlling communication I/F 450 and performing the process of step ST62.

On the other hand, if processor 110 of message server 100 receives a registration request while it is in the standby state of steps ST21 to ST28, it determines Yes in step ST23 of FIG. 3 and proceeds to step ST33.
In step ST33, processor 110 determines whether or not it is possible to register for participation in the message group using the invitation code included in the registration request. Processor 110 checks to see if the invitation code is stored in school database 142 . If the invitation code is not stored, processor 110 determines that participation registration is not possible. Also, if the invitation code is stored in the school database 142 , the processor 110 checks the expiration information of the invitation code stored in the school database 142 . The processor 110 determines that participation registration is not possible if the time limit has expired as a result of confirmation. When not determining that participation registration is not possible, the processor 110 determines that participation registration is possible. If processor 110 determines that participation registration is not possible, it determines No in step ST33 and proceeds to step ST34.

In step ST34, processor 110 generates a first rejection notice. The first refusal notification is information notifying that registration for participation in the message group is not possible. Also, the first refusal notification includes the reason why participation registration is not possible. For example, if the invite code was not stored in the school database 142, the reason is that the invite code is an invalid code. For example, if the invite code has expired, the reason is that the invite code has expired. After generating the first rejection notice, processor 110 instructs communication I/F 150 to transmit the first rejection notice to guardian terminal 400 . Upon receiving this transmission instruction, communication I/F 150 transmits the first refusal notification to guardian terminal 400 . The transmitted first refusal notification is received by communication I/F 450 of guardian terminal 400 . The processor 110 returns to step ST21 after the process of step ST34.

On the other hand, if the participation registration is possible, the processor 110 determines Yes in step ST33 and proceeds to step ST35.
In step ST35, processor 110 generates a first registration notification. The first registration notification is information notifying that registration for participation in the message group is possible. The first registration notification includes a temporary ID and input request information. The temporary ID is a unique ID for each user who is in the process of registration for participation. The processor 110 also associates the temporary ID with the class ID and stores it in the school database 142 . The class ID is a class ID stored in school database 142 in association with the invitation code included in the registration request received in step ST23. The input request information is information indicating what information is to be input when registering for participation. The information to be entered when registering for participation may be divided into information that must be entered and information that may or may not be entered. Information to be input when registering for participation is determined in advance by, for example, the manager of the message group, or the manager or designer of the message system 1 . After generating the first registration notification, processor 110 instructs communication I/F 150 to transmit the first registration notification to parent terminal 400 . Upon receiving this transmission instruction, communication I/F 150 transmits the first registration notification to guardian terminal 400 . The transmitted first registration notification is received by communication I/F 450 of guardian terminal 400 . The processor 110 returns to step ST21 after the process of step ST35.

On the other hand, in step ST63 of FIG. 5, processor 410 of guardian terminal 400 waits for communication I/F 450 to receive the first rejection notice or the first registration notice. If the first rejection notice or the first registration notice is received, processor 410 determines Yes in step ST63 and proceeds to step ST64.

In step ST64, processor 410 determines whether or not registration for participation in the message group is possible. For example, if the first rejection notice is received in step ST63, processor 410 determines that participation registration is not possible. Then, processor 410 determines that participation registration is possible when the first registration notification is received in step ST63. If the registration for participation in the message group is not possible, processor 410 determines No in step ST64 and proceeds to step ST65.

At step ST65, processor 410 generates an image corresponding to the first refusal screen. Processor 410 then instructs touch panel 460 to display this generated image. In response to the display instruction, touch panel 460 displays the first refusal screen. The first refusal screen includes an image indicating the reason why participation registration is not possible. The reason is the reason included in the first rejection notice. After the process of step ST65, the processor 410 returns to step ST61 when, for example, the display of the first refusal screen is completed.

On the other hand, if registration for participation in the message group is possible, processor 410 determines Yes in step ST64 and proceeds to step ST66.
At step ST66, processor 410 generates an image corresponding to the input screen. Processor 410 then instructs touch panel 460 to display this generated image. In response to the display instruction, touch panel 460 displays an input screen.

The input screen includes, for example, a notification image, an input field, and an input completion button. The notification image is an image indicating that registration for participation in the message group is possible. The input field is an input field for inputting information to be input to register for participation in the message group. What the information is is indicated in the input request information included in the first registration notification. The information to be input for registration of participation in the message group is, for example, the student's attendance number and the parent's sex and age. It should be noted that the parent's gender and age or generation are information used for displaying advertisements, for example. The input completion button is, for example, a button to be operated when information input to the input field is completed.

The guardian operates the touch panel 460 or the like to input information into each input field on the input screen. Then, when the input is completed, the parent operates the touch panel 460 or the like to operate the input completion button.
At step ST67, the processor 410 waits for an operation indicating that the input to the input field is completed. That is, processor 410 waits for a predetermined operation such as operating an input button. If the processor 410 has performed an operation indicating that the entry in the entry field has been completed, the processor 410 determines Yes in step ST67 and proceeds to step ST68.

In step ST68, processor 410 generates registration information. The registration information is information including information necessary for participation registration. The registration information includes, for example, the temporary ID, the information entered in the input field (hereinafter referred to as "input information"), and the terminal ID. The temporary ID is the same as the temporary ID included in the first registration notification received in step ST63. The terminal ID is a unique identification code for each guardian terminal 400 . A terminal ID is, for example, a device token. The registration information preferably does not contain information that can identify an individual, and particularly preferably does not contain the names, telephone numbers and e-mail addresses of students and guardians. This is to enhance the anonymity of the message service. After generating the registration information, processor 410 instructs communication I/F 450 to transmit the registration information to message server 100 . Upon receiving this transmission instruction, communication I/F 450 transmits the registration information to message server 100 . The transmitted registration information is received by communication I/F 150 of message server 100 .

On the other hand, if the processor 110 of the message server 100 receives the registration information during the standby state of steps ST21 to ST28, it determines Yes in step ST24 of FIG. 3 and proceeds to step ST36.
At step ST36, the processor 110 determines whether or not it is possible to register for participation in the message group based on the registration information. The processor 110 identifies, for example, among the class IDs stored in the school database 142, the class ID associated with the temporary ID included in the registration information. Processor 110 then determines whether the attendance number included in the registration information is a registerable attendance number. For example, if the attendance number is larger than the number of people in the class specified by the class ID, the processor 110 determines that the attendance number does not exist and that registration is not possible. In addition, when the number of registered guardian users with the attendance number is equal to or greater than a predetermined number, the processor 110 determines that participation registration is not possible. The predetermined number is determined in advance by, for example, a manager of the message group, or a manager or designer of the message system 1, or the like. The predetermined number is two as an example. In the school database 142, for each attendance number, the user ID of the guardian of the student with that attendance number is associated with each class. For example, the number of user IDs associated with each attendance number is the number of registered guardian users with that attendance number. Processor 110 determines that registration is possible if it does not determine that registration is not possible. If processor 110 determines that registration for participation in the message group is not possible, it determines No in step ST36 and proceeds to step ST37.

In step ST37, processor 110 generates a second rejection notice. The second refusal notification is information notifying that registration for participation in the message group is not possible. Also, the first refusal notification includes the reason why participation registration is not possible. For example, the reason is that the attendance number included in the registration information does not exist. For example, the reason is that the maximum number of guardians that can be registered per attendance number has been reached. After generating the second rejection notice, processor 110 instructs communication I/F 150 to transmit the second rejection notice to parent terminal 400 . In response to this transmission instruction, communication I/F 150 transmits the second rejection notification to guardian terminal 400 . The transmitted second rejection notification is received by communication I/F 450 of guardian terminal 400 .

On the other hand, if the processor 110 determines that it is possible to register for participation in the message group, it determines Yes in step ST36 and proceeds to step ST38.
At step ST38, the processor 110 registers the guardian to participate in the message group based on the registration information received at step ST24. For this purpose, the processor 110 generates a new user ID. The user ID is unique identification information for each user using the message service. Then, the processor 110 associates the class ID and group ID identified in step ST36 with the user ID and stores them in the school database 142. FIG. The processor 110 also associates the user ID with the attendance number included in the registration information and stores them in the school database 142 . The processor 110 also associates the user ID with the input information, the terminal ID, and the attribute information included in the registration information, and stores them in the school database 142 . Also, the processor 110 adds grade and class to the attribute information. The grade and class to be added are, for example, the same as the grade and class included in the class information. The class information is class information associated with the class ID associated with the user ID. Details of the attribute information will be described later. Note that the association between the class ID and the user ID indicates that the user identified by the user ID is the guardian of the student of the class identified by the class ID. Also, the fact that the user ID and the attendance number are associated indicates that the user identified by the user ID is the guardian of the student with the attendance number.

As described above, the processor 110 cooperates with the auxiliary storage device 140 that stores the school database 142 to perform the process of step ST38, thereby storing the user who sent the invitation code as the first group of users. It functions as an example of a part. In addition, the processor 110 cooperates with the auxiliary storage device 140 to add a class to the attribute information, thereby functioning as an example of a storage unit that stores belonging to the second group as a user attribute. .

In step ST39, processor 110 generates a second registration notification. The second registration notification is information notifying that registration for participation in the message group has been completed. Also, the second registration notification includes the user ID generated in step ST38. After generating the second registration notification, processor 110 instructs communication I/F 150 to transmit the second registration notification to parent terminal 400 . Upon receiving this transmission instruction, communication I/F 150 transmits the second registration notification to guardian terminal 400 . The transmitted second registration notification is received by communication I/F 450 of guardian terminal 400 . The processor 110 returns to step ST21 after the process of step ST39.

On the other hand, in step ST69 of FIG. 5, processor 410 of guardian terminal 400 waits for the second registration notification or the second rejection notification to be received by communication I/F 450. FIG. If the second registration notification or the second rejection notification is received, processor 410 determines Yes in step ST69 and proceeds to step ST70.

In step ST70, processor 410 determines whether or not registration for participation in the message group is possible. Processor 410 determines that participation registration is not possible if, for example, the second rejection notice is received in step ST70. Then, if the second registration notice is received in step ST70, processor 410 determines that participation registration is possible. If processor 410 determines that registration for participation in the message group is not possible, it determines No in step ST70 and proceeds to step ST71.

In step ST71, processor 410 generates an image corresponding to the second refusal screen. Processor 410 then instructs touch panel 460 to display this generated image. In response to the display instruction, touch panel 460 displays the second refusal screen. After the process of step ST71, the processor 410 returns to step ST61 when, for example, the display of the second refusal screen is finished.

On the other hand, if processor 410 determines that participation registration to the message group is possible, it determines Yes in step ST71 and proceeds to step ST72.
At step ST72, processor 410 stores the user ID included in the second registration notification in auxiliary storage device 440 or the like.

At step ST73, processor 410 generates an image corresponding to the registration screen. Processor 410 then instructs touch panel 460 to display this generated image. In response to the display instruction, touch panel 460 displays the registration screen.

The registration screen includes, for example, an image indicating that participation registration has been completed. After the process of step ST73, the processor 410 returns to step ST61 when, for example, the display of the registration screen is completed.

How to set attributes for each user will be described below. Each user is associated with attribute information as described above. The attribute information includes attributes indicating features or characteristics of users. Attributes can be divided into, for example, student attributes and guardian attributes. The student attribute indicates, for example, the student's grade, class, club to which the student belongs, committee to which the student belongs, group to which the student belongs, such as group attendance at school. The guardian attribute indicates, for example, a group to which the guardian belongs, such as a PTA officer or volunteer activity. Note that the attribute is not limited to the group to which the student or guardian belongs, and may be any feature or property related to the student or guardian. Note that, of the student attributes, the student's grade and class cannot be changed by the guardian. Also, there may be attributes other than grade and class that cannot be changed by parents. From the viewpoint of improving anonymity, it is preferable that the attribute information does not include information that can identify an individual.

In step ST81 of FIG. 6, the processor 410 of the guardian terminal 400 determines whether or not to start attribute setting. For example, the processor 410 determines to start setting attributes in response to an operation to start setting attributes. If the processor 410 does not determine to start setting attributes, it determines No in step ST81 and repeats the process of step ST81. Then, if the processor 410 determines to start setting attributes, it determines Yes in step ST81 and proceeds to step ST82.

At step ST82, processor 410 generates an image corresponding to the attribute setting screen. Processor 410 then instructs touch panel 460 to display this generated image. In response to the display instruction, touch panel 460 displays the attribute setting screen. The attribute setting screen is a screen for setting attributes.

The attribute setting screen includes, for example, a list of attributes that can be set and an attribute setting button. In addition, for each settable attribute, if there is already an attribute included in the attribute information, the attribute setting screen displays such that it is possible to know whether or not it is in a setting state. The attribute information is attribute information associated with the user ID in the school database 142 . The user ID is the same as the user ID stored in auxiliary storage device 440 or the like in step ST72. Note that the setting state indicates a state included in the attribute information. A state that is not in the set state is called a canceled state. For example, on the attribute setting screen, set attributes are displayed as selected, and canceled attributes are displayed as unselected, so that each attribute can be identified as set or canceled. indicate. Attributes in the selected state and attributes in the unselected state differ in appearance, for example, in color. Note that the processor 410 acquires from the message server 100, for example, a list of settable attributes and information indicating whether each attribute is set or unset. Alternatively, the auxiliary storage device 440 or the like may store a list of settable attributes and information indicating whether each attribute is set or canceled. In this case, the processor 410 may acquire a list of settable attributes and information indicating whether each attribute is set or canceled from the auxiliary storage device 440 or the like. Configurable attributes are set in advance by, for example, a message group administrator. The attribute setting button is, for example, a button that is operated when the attribute change is desired to be reflected.

For example, when there is an attribute to be set, the parent operates the touch panel 460 by tapping the area where the attribute is displayed to set the attribute to the selected state. Further, for example, when the parent wishes to cancel the set attribute, the parent operates touch panel 460 by, for example, tapping the area where the attribute is displayed, thereby deselecting the attribute. change to state. The guardian operates the attribute setting button when the selected state or the unselected state is desired for each attribute.

At step ST83, the processor 410 determines whether or not to reflect the attribute change. The processor 410 does not determine to reflect the attribute change unless the attribute setting button is operated. Then, if the attribute setting button is operated, the processor 410 determines to reflect the attribute change. If the processor 410 does not determine to reflect the attribute change, it determines No in step ST83 and repeats the process of step ST83. On the other hand, if the processor 410 determines to reflect the attribute change, it determines Yes in step ST83 and proceeds to step ST84.

In step ST84, processor 410 generates an attribute change request. The attribute change request is information requesting that attribute information be changed as indicated by the attribute change information. The attribute change request includes a user ID and attribute change information. The user ID is a user ID stored in auxiliary storage device 440 . The attribute change information indicates whether each attribute is set or canceled. The processor 410, for example, indicates that the attributes in the selected state on the attribute setting screen are to be set, and the attributes in the unselected state on the attribute setting screen are to be canceled. Generate change information. After generating the attribute change request, processor 410 instructs communication I/F 450 to transmit the attribute change request to message server 100 . Upon receiving this transmission instruction, the communication I/F 450 transmits the attribute change request to the message server 100 . The transmitted attribute change request is received by communication I/F 150 of message server 100 .

On the other hand, if processor 110 of message server 100 receives an attribute change request while in the waiting state of steps ST21 to ST28, it determines Yes in step ST25 of FIG. 4 and proceeds to step ST40.
At step ST40, the processor 110 changes the attribute information based on the attribute change information included in the attribute change request. The attribute information is attribute information stored in the school database 142 in association with the user ID included in the attribute change request. For example, the processor 110 adds, to the attribute information, an attribute that is indicated to be set in the attribute change information and is not already included in the attribute information. Also, the processor 110 deletes, from the attribute information, an attribute already included in the attribute information among the attributes indicated to be in the canceled state in the attribute change information, for example. Note that the attribute added to the attribute information is included in the attribute information. Attributes deleted from the attribute information are no longer included in the attribute information.

As described above, the processor 110 cooperates with the auxiliary storage device 140 that stores the school database 142, and performs the processing of step ST40, so that the user and the attribute of the user are associated (associated) and stored. serves as an example of

In step ST<b>41 , processor 110 instructs communication I/F 150 to transmit a change notification to guardian terminal 400 . The change notification is, for example, information notifying that the attribute change has been completed. Upon receiving the transmission instruction, communication I/F 150 transmits the change notification to guardian terminal 400 . The transmitted notification of change is received by communication I/F 450 of guardian terminal 400 . The processor 110 returns to step ST21 of FIG. 3 after the process of step ST41.

On the other hand, in step ST85 of FIG. 6, the processor 410 of the guardian terminal 400 is waiting for the change notification to be received by the communication I/F450. If the change notification is received, processor 410 determines Yes in step ST85 and proceeds to step ST86.

In step ST86, processor 410 generates an image corresponding to the change result screen. Processor 410 then instructs touch panel 460 to display this generated image. In response to the display instruction, touch panel 460 displays the change result screen. The change result screen includes, for example, an image indicating that the attribute change has been completed. The processor 410 returns to step ST81 after the process of step ST86.

The following describes creating and sending a message using the message service.
The processing in FIG. 7 is processing common to the school terminal 200 and the guardian terminal 400 . Here, processing of the processor 410 of the guardian terminal 400 will be representatively described. When school terminal 200 executes the processing of FIG. 7, processor 210 performs the processing instead of processor 410. FIG.

In step ST91, processor 410 determines whether or not to start creating a message. Processor 410 determines to start creating a message, for example, in response to operation of a button instructing to start creating a message. If processor 410 does not start creating a message, it determines No in step ST91 and repeats the process of step ST91. Then, if processor 410 starts creating a message, it determines Yes in step ST91 and proceeds to step ST92.

In step ST92, processor 410 generates an image corresponding to the creation screen. Processor 410 then instructs touch panel 460 to display this generated image. In response to the display instruction, touch panel 460 displays the creation screen.

The creation screen is a screen for creating a message. The creation screen includes, for example, a message input field, an attribute setting field, and a send button.
The message entry field is an area for entering a message. It should be noted that the message input field is not limited to a character string, and an image or the like may be input. In addition, the message input field may be able to attach various files.

The attribute setting column is an area for setting the destination of the message. In the attribute setting column, one or more attributes of the other party to whom the message is to be sent are entered. For example, if two attributes, attribute A and attribute B, are entered in the attribute setting field, the message is sent to the user for whom attribute A and attribute B are set. The attribute input method to be input in the attribute setting field is not limited to the AND condition, and may be input using the OR condition or the NOT condition. For example, if (attribute A OR attribute B), the message will be sent to users who have at least one of attribute A or attribute B set. For example, if (attribute A OR attribute B), then the message will be sent to users who have attribute A set and attribute B unset. As described above, the message is sent to the user corresponding to the attribute entered in the attribute setting field among the users participating in the same message group.

The send button is a button that is operated when sending a message.
The operator of the guardian terminal 400, for example, inputs a message and attributes on the creation screen and operates a send button.

At step ST93, processor 410 waits for an operation to send a message. That is, processor 410 waits for a predetermined operation such as operating a send button. If an operation to send a message has been performed, processor 410 determines Yes in step ST93 and proceeds to step ST94.

In step ST94, processor 410 generates a message transmission request. The message transmission request includes message information, destination information and user ID. The message transmission request is information requesting transmission of the message information to the destination indicated by the destination information. The message information is, for example, the content entered in the message entry field on the creation screen. The destination information is, for example, the content entered in the attribute setting column on the creation screen. The user ID in the message transmission request is the user ID stored in auxiliary storage device 440 . After generating the message transmission request, processor 410 instructs communication I/F 450 to transmit the message transmission request to message server 100 . Upon receiving this transmission instruction, communication I/F 450 transmits the message transmission request to message server 100 . The transmitted message transmission request is received by communication I/F 150 of message server 100 .
Processor 410 cooperates with communication I/F 450 to perform the process of step ST94, thereby functioning as an example of a transmission unit that transmits an attribute indicating a destination of message information to message server 100. FIG. Alternatively, processor 410 functions as an example of a transmission section by controlling communication I/F 450 and performing the process of step ST94.

On the other hand, if processor 110 of message server 100 receives a message transmission request in the waiting state of steps ST21 to ST28, it determines Yes in step ST26 of FIG. 4 and proceeds to step ST42.
In step ST<b>42 , processor 110 instructs communication I/F 150 to transmit a success notification to guardian terminal 400 . The success notification is information indicating that the message server 100 has successfully received the message transmission request. Upon receiving this transmission instruction, the communication I/F 150 transmits the success notification to the school terminal 200 . The transmitted notification of success is received by communication I/F 450 of guardian terminal 400 .

On the other hand, in step ST95 of FIG. 7, the processor 410 of the parent terminal 400 waits for the communication I/F 450 to receive the success notification. If the notification of success is received, processor 410 determines Yes in step ST95 and proceeds to step ST96.

In step ST96, processor 410 generates an image corresponding to the success screen. Processor 410 then instructs touch panel 460 to display this generated image. In response to the display instruction, touch panel 460 displays a success screen. The success screen is a screen indicating that the message transmission request has been successfully transmitted. The processor 410 returns to step ST91 after the process of step ST96.

On the other hand, in step ST43 of FIG. 4, the processor 110 of the message server 100 converts the message information included in the message transmission request received in step ST41 into the group ID, the message ID, the user ID included in the message transmission request, and the message transmission request. It is stored in the message database 141 in association with the destination information included in the message transmission request. The group ID is a group ID associated with the user ID included in the message transmission request in the school database 142 . That is, it is the group ID of the group in which the user identified by the user ID participates. A message ID is identification information unique to each piece of message information. Processor 110 generates a message ID and attaches it to the message information.

In step ST44, the processor 110 searches for a user having an attribute corresponding to the destination information among the users participating in the same group as the user who sent the message transmission request. To this end, processor 110 identifies, for example, in school database 142 the group ID associated with the user ID included in the message request. The processor 110 then acquires attribute information associated with each user ID associated with the group ID. Then, the processor 110 identifies attribute information whose attribute setting state and attribute cancellation state match those of the destination information included in the message transmission request. Processor 110 identifies the user ID associated with the matching attribute information. Each user ID specified in this way is the user ID of the user to whom the message information is to be sent. Processor 110 also acquires the terminal ID associated with each user ID identified as a destination. The terminal ID indicates the terminal to which the message information is to be sent.
In this way, the processor 110 selects a user having attributes corresponding to the destination information as a destination by specifying the user ID. Therefore, the processor 110 functions as an example of a selection unit that selects a user corresponding to the attribute by performing the process of step ST44.

In step ST45, processor 110 instructs communication I/F 150 to transmit message notification to each guardian terminal 400 specified by each terminal ID acquired in step ST44. The message notification includes the message information stored in step ST43 and the message ID of the message information. The message notification is information notifying that the message notification has been received. Upon receiving this transmission instruction, the communication I/F 150 transmits the message notification to each guardian terminal 400 . The transmitted message notification is received by the communication I/F 450 of each guardian terminal 400 . The processor 110 returns to step ST21 of FIG. 3 after the process of step ST45.
The processor 110 functions as an example of a provider that enables the provision of messages by performing the process of step ST45.

On the other hand, the processor 410 of the guardian terminal 400 determines whether the message notification was received by communication I/F450 in FIG.8 ST101. If the message notification is not received, processor 410 determines No in step ST101 and proceeds to step ST102.

In step ST102, processor 410 determines whether or not to inquire whether there is an unreceived message. If processor 410 does not determine to inquire whether there is an unreceived message, it determines No in step ST102 and proceeds to step ST103.

In step ST103, processor 410 determines whether or not to display a message. If the message is not displayed, processor 410 determines No in step ST103 and returns to step ST101. Thus, processor 410 enters a standby state in which steps ST101 to ST103 are repeated until a message notification is received, an inquiry is made as to whether there is an unreceived message, or a message is displayed.

If processor 410 receives a message notification while it is in the standby state of steps ST101 to ST103, it determines Yes in step ST101 and proceeds to step ST104. Note that processor 410 functions as an example of a receiving unit that receives message information by cooperating with communication I/F 450 to receive message notification. Alternatively, processor 410 functions as an example of a receiver by controlling communication I/F 450 to receive message notifications.
In step ST104, processor 410 associates the message included in the message notification with the message ID included in the message notification and stores it in auxiliary storage device 440 or the like.

In step ST105, processor 410 notifies the owner of guardian terminal 400 or the like that the message has arrived by push notification or the like. For example, processor 410 notifies that a message has arrived by causing touch panel 460 to display an image indicating that the message has arrived. For example, processor 410 announces the arrival of a message by outputting a sound from a speaker. For example, the processor 410 notifies that a message has arrived by, for example, vibrating a vibrator. Processor 410 returns to step ST101 after the process of step ST105.

For example, if an attribute setting is changed, there is a possibility that the message corresponding to the changed attribute has not been received. Also, if you have newly registered for participation in a message group, there may be messages that you have not received yet. Also, if the parent terminal 400 is in a state where communication is not possible, there may be unreceived messages.
In such a case, if the operator of guardian terminal 400 wants to check whether there is an unreceived message, for example, the operator uses touch panel 460 to perform an operation for instructing to inquire whether there is an unreceived message. conduct.

Processor 410 determines to inquire for unreceived messages, for example, when an operation is performed to instruct to inquire for unreceived messages. If processor 410 determines to inquire whether there is an unreceived message during the standby state of steps ST101 to ST103, it determines Yes in step ST102 and proceeds to step ST106.

In step ST106, processor 410 instructs communication I/F 450 to transmit an inquiry request to message server 100. FIG. The inquiry request is information indicating a request to check whether there is an unreceived message. Also, the inquiry request is information indicating a request to send a message if there is an unreceived message. The inquiry request includes, for example, the user ID stored in auxiliary storage device 440 . Upon receiving this transmission instruction, communication I/F 450 transmits the inquiry request to message server 100 . The transmitted query request is received by communication I/F 150 of message server 100 .

On the other hand, if processor 110 of message server 100 receives an inquiry request in the standby state of steps ST21 to ST28, it determines Yes in step ST27 of FIG. 4 and proceeds to step ST46.
At step ST46, processor 110 checks whether there is unreceived message information for the user identified by the user ID included in the inquiry request. Processor 110 also identifies which message information is unreceived message information. Here, an example of a method of confirming whether or not there is unreceived message information and a method of identifying which message information is unreceived message information will be described. The method of confirming whether there is unreceived message information and the method of identifying which message information is unreceived message information are not limited to those shown below.

Processor 110 acquires attribute information associated with the user ID. Processor 110 also obtains a group ID associated with the user ID. Then, the processor 110 determines that the destination information associated with the group ID in the message information stored in the message database 141 matches the setting state and cancellation state of the acquired attribute information. Find what you want. Processor 110 creates a list of message IDs for each piece of message information found by the search. Processor 110 then transmits the list to the source of the inquiry request.

The processor 410 of the guardian terminal 400 that has received the list checks whether each message ID included in the list matches the message ID associated with the message information stored in the auxiliary storage device. Processor 410 then removes the message IDs that had matches from the list and creates a list of message IDs that did not have matches. Processor 410 sends the list to message server 100 .

The processor 110 determines that there is no unreceived message, for example, if the received list does not contain the message ID. For example, if there is one or more message IDs in the received list, processor 110 determines that there is an unreceived message. Also, the message information specified by the message ID included in the list is the unreceived message information.

In step ST47, processor 110 determines whether or not there is unreceived message information. If processor 110 determines that there is no unreceived message information, it determines No in step ST47 and proceeds to step ST48.

In step ST<b>48 , processor 110 instructs communication I/F 150 to transmit a result notification to guardian terminal 400 . The result notification is information notifying that there is no unreceived message. Upon receiving this transmission instruction, the communication I/F 150 transmits the result notification to the guardian terminal 400 . The transmitted result notification is received by communication I/F 450 of guardian terminal 400 . The processor 110 returns to step ST21 of FIG. 3 after the process of step ST48.

On the other hand, if processor 110 determines that there is unreceived message information, it determines Yes in step ST47 of FIG. 4 and proceeds to step ST49.
In step ST<b>49 , processor 110 instructs communication I/F 150 to transmit an unreceived message notification to guardian terminal 400 . The unreceived message notification is information for notifying that there is unreceived message information. Also, the unreceived message notification includes each message information specified as unreceived by the process of step ST46. The unreceived message notification also includes the message ID of each message information. In response to this transmission instruction, communication I/F 150 transmits the unreceived message notification to guardian terminal 400 . The transmitted unreceived message notification is received by communication I/F 450 of guardian terminal 400 . The processor 110 returns to step ST21 of FIG. 3 after the process of step ST49.
The processor 110 functions as a provider that provides a message by performing the process of step ST49.

On the other hand, in step ST107 of FIG. 8, the processor 410 of the parent terminal 400 waits for the communication I/F 450 to receive a result notification or an unreceived message notification. If the result notification or the unreceived message notification is received, processor 410 determines Yes in step ST107 and proceeds to step ST108.

In step ST108, processor 410 causes touch panel 460 to display an image indicating whether or not there is an unreceived message. When processor 410 receives the result notification, processor 410 causes touch panel 460 to display an image indicating that there is no unreceived message. When processor 410 receives an unreceived message notification, processor 410 causes touch panel 460 to display an image indicating that there is an unreceived message.

In step ST109, processor 410 determines whether or not there is unreceived message information. If there is no unreceived message information, processor 410 determines No in step ST109 and returns to step ST101. On the other hand, if there is unreceived message information, processor 410 determines Yes in step ST109 and proceeds to step ST110.

In step ST110, processor 410 associates each piece of message information included in the unreceived message notification with the message ID and stores it in auxiliary storage device 440. FIG. Processor 410 returns to step ST101 after the process of step ST110.

When the guardian wants to see the contents of the message information received by the guardian terminal 400, the guardian uses the touch panel 460, for example, to perform an operation to specify which message information the guardian wants to see. Then, the guardian performs an operation to instruct display of the contents of the message information. Note that the guardian may specify individual message information or attributes by specifying the content of which message information the guardian wants to see.
Processor 410 determines to display a message, for example, in response to such an operation. If the processor 410 determines to display a message in the standby state of steps ST101 to ST103, it determines Yes in step ST103 and proceeds to step ST111.

In step ST111, processor 410 generates an image corresponding to the message screen. Processor 410 then instructs touch panel 460 to display this generated image. In response to the display instruction, touch panel 460 displays a message screen. Processor 410 returns to step ST101 after the process of step ST111.
The message screen contains the contents of the message information. The message information is, for example, message information designated by a parent's operation. When an individual message is specified in the operation of specifying the contents of which message information to be viewed, the message screen includes the contents of the message information specified in the operation. Also, if an attribute is specified in the operation for specifying the contents of which message information to be viewed, the contents of a plurality of message information with matching attributes are included. The contents of the plurality of message information are arranged, for example, in order of newness of the message information. For example, the contents of the plurality of message information may be arranged like an existing messenger application. Note that the processor 410 generates the message screen by acquiring the contents of the message information from the auxiliary storage device 440, for example.

Also, the processor 410 may determine to automatically display the message after the message notification is received in step ST101. In this case, for example, after the process of step ST105, the processor 410 determines Yes in step ST103 and proceeds to step ST111. Processor 410 then displays a message screen containing the content of the message information included in the message notification received in step ST101.

Alternatively, the processor 410 may determine to automatically display the message after receiving the unreceived message notification in step ST107. In this case, for example, after the process of step ST110, the processor 410 determines Yes in step ST103 and proceeds to step ST111. Processor 410 then displays a message screen containing the content of the message information included in the unreceived message notification received in step ST107.

For each message group, the processor 110 of the message server 100 refers to the deletion time information associated with the group ID of the message group, and confirms that the current date and time is later than the deletion date and time of the message group (predetermined timing). ) are monitored. For example, if the current date and time for any message group is after the deletion date and time of the message group, the processor 110 determines that the deletion date and time of the message group has come.
If the processor 110 of the message server 100 determines that the date and time for deleting the message group has come while in the standby state of steps ST21 to ST28, it determines Yes in step ST28 of FIG. Proceed to ST50.

In step ST50, the processor 110 deletes part or all of the information about the message groups whose deletion date and time are before the current date and time. As an example, the processor 110 includes creation information associated with the group ID of the message group to be deleted, class ID associated with the group ID, class information and each invitation code associated with the class ID, and each invitation code. The associated deadline information, each user ID associated with the group ID, and the attendance number, input information, terminal ID, attribute information, etc. associated with the user ID are deleted from the school database 142 . Also, the processor 110 deletes from the message database 141 each piece of message information associated with the group ID of the message group to be deleted, and the message ID and destination information associated with each piece of message information. Note that the processor 110 may delete only part of the information listed above. In addition, the method of deleting information may be a method of deleting data, a method of not deleting data so that the deleted data can be recognized, or a method of not deleting data, such as a company managing message service A method that prevents access from users other than some users may be used, or another method may be used. Alternatively, processor 110 may take action to prevent each user from sending or receiving messages. The processor 110 returns to step ST21 after the process of step ST50.
By performing the processes of steps ST28 and ST50, the processor 110 functions as an example of a deletion unit that deletes the information about the user so that the message information cannot be provided at a predetermined timing.

According to the message system 1 of the embodiment, upon receiving an invitation code, the message server 100 registers the user who sent the invitation code for participation in the message group. Also, the message server 100 sets attributes for each user.
Participation in the message group does not require any personally identifiable information, as the invitation code is sufficient to participate in the message group. Also, since each user designates the destination of the message by the attribute, the message can be sent to the desired party without specifying the individual. In this way, parents can communicate with each other without exchanging contact information.

Also, according to the message system 1 of the embodiment, it is possible to send a message to each guardian using the school terminal 200 . As an example, if only the class is entered as an attribute to be entered in the attribute setting field, it is possible to make a simultaneous contact with the guardians of the students in the class.

Further, according to the message system 1 of the embodiment, the message server 100 does not transmit the user ID of the sender of the message information when transmitting the message information to the guardian terminal 400 . Therefore, the recipient of the message information does not know who the sender of the message is. Therefore, the transmission of messages by the message system of the embodiment is anonymous.

Further, according to the message system 1 of the embodiment, the message server 100 deletes information of each user when the predetermined date and time has come. As a result, the message system 1 of the embodiment can prevent troubles that occur between parents whose students were in the same class before graduation or promotion after the student graduates or advances to the next grade.

Also, the message system 1 of the embodiment uses a different invitation code for each class. As a result, the message system 1 of the embodiment prevents a class different from the class to which the student actually belongs to be set as an attribute.

The above embodiment can also be modified as follows.
In the above embodiment, the message server 100 changed the attribute information of the user in response to receiving the attribute change request from the guardian terminal 400 . However, the message server 100 may change the user's attribute information in accordance with instructions from the school terminal 200 . For example, the school terminal 200 transmits to the message server 100 information specifying a user whose attribute information is to be changed and information indicating which attribute is to be set and which attribute is to be released. Information identifying the user is, for example, the class and attendance number. A class ID may be used instead of the class. Alternatively, the information specifying the user may be a user ID. The operator of the school terminal 200 operates the input device 260, for example, to input information specifying the user whose attribute information is to be changed, and information indicating which attribute to set and which attribute to cancel. Input to the school terminal 200 . It should be noted that although an instruction from the school terminal 200 can set or cancel an attribute, there may be an attribute that cannot be set or canceled by an instruction from the parent terminal 400 . Also, although the setting state or the cancellation state can be set only by an instruction from the parent terminal 400, there may be an attribute that cannot be set to the setting state or the cancellation state by an instruction from the school terminal 200. FIG.

In the above embodiment, the message server 100 does not transmit the user ID of the sender of the message information when transmitting the message information to the guardian terminal 400 . However, the message server 100 may also transmit the user ID of the sender of the message information when transmitting the message information to the guardian terminal 400 . In this case, the recipient of the message knows the user ID of the sender of the message. This allows the recipient of the message to know which of the multiple received messages was sent by the same user.

Also, when transmitting message information to the guardian terminal 400, the message server 100 may transmit information indicating the class and attendance number of the sender of the message. In this case, the recipient of the message knows the class and attendance number of the sender of the message.

The message group in the above embodiment is explained using the message group for each school as an example. However, the message service of embodiments can also be used by non-school groups. Non-school groups may be, for example, hospitals, companies, or other organizations, communities, or groups of people who have something in common.
Also, the first group in the above embodiment is a group of parents of students. However, instead of students, employees, full-time employees, temporary employees, shareholders, retirees, OBs (old boys), OGs (old girls), local residents, visitors, or their families may be used. Also, a friend, an acquaintance, or some other related person or person may be used instead of the guardian.
Also, the second group in the above embodiment is a class. However, instead of classes, clubs, committees, departments, rooms, or any other group of people within the first group may be used.

In the above embodiment, the invitation code is different for each class. However, the invitation code may be different for each grade other than the class.

In the above embodiment, the information to be entered to register for participation in the message group requires entry of the attendance number of the student and the gender and age of the guardian. However, the information to be input to register for participation in the message group is not limited to these. In addition, even if there is no information to be input to register for participation in the message group, it is acceptable.

In the above-described embodiment, the message server 100 stores the attribute of the user identified by the user ID by associating the attribute information with the user ID. However, the message server 100 may store each user's attributes by other methods.

A part of the processing executed by the message server 100 in the above embodiment may be executed by the school terminal 200 or the parent terminal 400 . The message server 100 may execute part of the processing executed by the school terminal 200 or the parent terminal 400 in the above embodiment.

The processor 110, the processor 210, or the processor 410 may implement part or all of the processing implemented by the program in the above-described embodiments by means of a circuit hardware configuration.

A program that implements the processing of the embodiment is transferred in a state of being stored in a device, for example. However, the device may be transferred without the program stored. Then, the program may be transferred separately and written into the device. Transfer of the program at this time can be realized, for example, by recording it on a removable storage medium or downloading it via a network such as the Internet or LAN.

Although the embodiments of the present invention have been described above, they are shown as examples and are not intended to limit the scope of the present invention. Embodiments of the present invention can be implemented in various ways without departing from the gist of the present invention.

1 message system 100 message server 110, 210, 410 processor 120, 220, 420 ROM
130, 230, 430 RAM
140,240,440 auxiliary storage device 141 message database 142 school database 150,250,450 communication I/F
160,280,480 Bus 200 School terminal 260 Input device 270 Display device 300 Printer 400 Parent terminal 460 Touch panel 470 Camera

Claims (8)

storing the user who sent the proof information as a user of the first group, based on receiving the proof information proving that he/she belongs to the first group, and storing the user and the attribute of the user; a storage unit that can be associated and stored;
a server apparatus comprising: a providing unit capable of providing message information to the user selected by the selecting unit that selects a user corresponding to the attribute from among the users of the first group. 2. The server device according to claim 1, wherein said certification information does not include the name, telephone number and e-mail address of said user. A deletion unit that deletes information about the user stored by the storage unit so that message information cannot be provided to the user selected by the selection unit at a predetermined timing. 3. The server device according to claim 1 or 2. including a terminal device and a server device,
The terminal device
a transmitting unit configured to transmit, to the server apparatus, proof information proving that the user belongs to the first group and an attribute indicating a destination of message information;
a receiving unit that receives message information provided from the server device,
The server device
storing the user who sent the certification information as a user of the first group based on the receipt of the certification information transmitted from the user through the terminal device, and associating the user with the attribute; a memorizable storage unit;
a providing unit configured to provide message information to the users selected by a selection unit that selects users corresponding to the attributes transmitted by the transmission unit from among the users of the first group. By transmitting certification information proving that the user belongs to the first group to the server device, the server device is requested to be stored as a user of the first group, and an attribute indicating a destination of message information is provided. a transmission unit for requesting the server device to be able to provide message information to the user corresponding to the attribute by transmitting to the server device;
A terminal device comprising a reception unit that receives message information provided from the server device. The processor provided in the server device,
storing the user who sent the proof information as a user of the first group, based on receiving the proof information proving that he/she belongs to the first group, and storing the user and the attribute of the user; a storage unit that can be associated and stored;
A program that functions as a providing unit capable of providing message information to the user selected by the selecting unit that selects a user corresponding to the attribute from among the users of the first group. The processor provided in the terminal device,
By transmitting certification information proving that the user belongs to the first group to the server device, the server device is requested to be stored as a user of the first group, and an attribute indicating a destination of message information is provided. a transmission unit for requesting the server device to be able to provide message information to the user corresponding to the attribute by transmitting to the server device;
A program that functions as a receiving unit that receives message information provided from the server device. Sending proof information proving that it belongs to the first group,
storing the user who sent the certification information as a user of the first group based on the receipt of the certification information;
storing the user and attributes of the user in association with each other;
A message providing method, wherein message information can be provided to the user selected by a selection unit that selects a user corresponding to the attribute from among the users of the first group.

Images