Message transmission system and method

Abstract

To provide a message transmission system and method for easily confirming and managing a message transmitted from each server for providing different services to a user.SOLUTION: This system is provided with a first server 20 for transmitting a message to an application to be used by a user and a second server 30 for providing a service different from that of the first server 20 to the user, and the first server 20 receives the message and a destination transmitted from the second server 30, and transmits the message to the application based on the destination.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a messaging system and method for sending messages to an application from servers that provide different services. [Background technology]

[0002] 2. Description of the Related Art Conventionally, a system has been proposed in which messages are sent and received between users of a given service via a server that provides the service.

[0003] For example, a system has been proposed in which messages are sent and received between a school's terminal device and a parent's terminal device via a server that provides a school communication service for communicating between the school and the parent. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2006-202307 Summary of the Invention [Problem to be solved by the invention]

[0005] In addition to the school contact service mentioned above, other school-related services that parents use include school fee collection services, etc. Parents install applications for these different services on their own terminal devices and receive the services.

[0006] However, for example, if a school sends a message to a parent using each service, the parent will receive the message separately using the application for each service on their terminal device. Even though the messages are from the same school-related service, the parent must launch a separate application to check each message, which is extremely time-consuming and makes message management complicated.

[0007] In addition, Patent Document 1 proposes a system that sends a message to a user when information is registered in a database, indicating that the information has been registered, but does not propose anything regarding receiving messages from servers that provide different services such as those described above.

[0008] In view of the above circumstances, the present invention aims to provide a message sending system and method that allows users to easily check and manage messages sent to them from each server that provides different services. [Means for solving the problem]

[0009] The message sending system of the present invention comprises a first server that sends a message to an application used by a user, and a second server that provides the user with a service different from that of the first server, and the first server receives the message and destination sent from the second server, and sends the message to the application based on the destination. [Effects of the Invention]

[0010] According to the message sending system of the present invention, messages sent to a user from a first server and a second server that provide different services can be aggregated by an application of the service on the first server, allowing the user to easily check and manage messages from the different services. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram showing a schematic configuration of a message management system using an embodiment of the message transmission system of the present invention. [Figure 2] FIG. 1 shows an example of a guardian table, a message table, and a message destination table. [Figure 3] FIG. 10 is a diagram showing an example of an ID linkage table. [Figure 4] Flowchart for explaining the registration process for guardians (guardian IDs) in the school communication service application [Figure 5] Flowchart for explaining the collaboration process between the school communication service application and the school collection service application [Figure 6] FIG. 10 is a diagram showing an example of an association contract table. [Figure 7] A flowchart for explaining a transmission process when a message is sent from a school-oriented fee collection service application on a school terminal device to a parent terminal device. DETAILED DESCRIPTION OF THE INVENTION

[0012] A message management system using an embodiment of a message transmission system of the present invention will be described in detail below with reference to the drawings. Fig. 1 is a block diagram showing a schematic configuration of a message management system 1 of this embodiment.

[0013] As shown in FIG. 1, the message control system 1 of this embodiment includes a school terminal device 10, a first server 20, a second server 30, and a parent terminal device 40.

[0014] The school terminal device 10 and the first server 20 and the second server 30, the parent terminal device 40 and the first server 20 and the second server 30, and the first server 20 and the second server 30 are connected via communication lines. The communication lines may be internet lines or telephone lines. The communication lines may be wired or wireless.

[0015] First, the general operation of the message control system 1 of this embodiment will be described.

[0016] The message management system 1 of this embodiment is a system that manages messages from a school communication service provided by a first server 20 and messages from a school collection service provided by a second server 30, and aggregates and manages messages from these two different services.

[0017] The school terminal device 10 and the parent terminal device 40 each have two applications: a school communication service application (hereinafter referred to as the school communication application) and a school fee collection service application (hereinafter referred to as the school fee collection application).

[0018] The school communication application is an application used as a means of communication between the school and parents, and allows the school to contact parents and parents to contact the school about attendance, etc. The school collection application is an application for a service related to schools, similar to the school communication service, but is an application used by the school to collect fees from parents.

[0019] The first server 20 is linked to a school communication application, and the second server 30 is linked to a school fee collection application.

[0020] When a message is sent from the school terminal device 10 to the parent terminal device 40 using the school communication service, the school communication application is launched, the device logs in to the first server 20, and the message is sent to the school communication application of the parent terminal device 40 via the first server 20.

[0021] On the other hand, when a message is sent from the school terminal device 10 to the parent terminal device 40 using the school fee collection service, the school fee collection application is launched and the user logs in to the second server 30. The school terminal device 10 then sends the message and its destination to the second server 30, and the second server 30 then sends the received message and destination to the first server 20. The first server 20 then sends a message to the school communication application of the parent terminal device 40 based on the received message and destination.

[0022] That is, messages sent from the school terminal device 10 are aggregated in the first server 20 for both the school communication service and the school collection service, and are sent from the first server 20 to the school communication application of the parent terminal device 40.

[0023] The above is a rough processing flow of the message control system 1 of this embodiment. Although only one school terminal device 10 is shown in Fig. 1, in reality, at least as many as the number of schools are provided. Also, although only one parent terminal device 40 is shown, in reality, at least as many as the number of students are provided.

[0024] Next, each device constituting the message control system 1 of this embodiment will be described in detail.

[0025] The school terminal device 10 is used by school staff such as teachers, and may be, for example, a desktop computer or a notebook computer, but is not limited to these, and may also be a mobile terminal such as a tablet terminal.

[0026] The school terminal device 10 comprises a control unit 11, a memory unit 12, and a display unit 13. The control unit 11 controls the entire school terminal device 10. In particular, the control unit 11 creates and manages messages sent from the school to the parents of students, and manages reply messages sent from the parents to the school.

[0027] As described above, a school communication application and a school fee collection application are installed in the storage unit 12. When the school communication application or the school fee collection application is started by the CPU (Central Processing Unit) of the control unit 11, a message to parents is created and sent in the school terminal device 10. Note that instead of using an application installed in the storage unit 12 as in this embodiment, an application provided via a web browser may be used.

[0028] The display unit 13 displays a user interface screen of the school communication application, a user interface screen of the school fee collection application, and the like.

[0029] The school terminal device 10 includes, as hardware, a CPU, semiconductor memories such as a ROM (Read Only Memory) and a RAM (Random Access Memory), storage such as a hard disk, and a communication I / F (Interface).

[0030] As described above, the first server 20 is a server that works in conjunction with the school communication application, and includes a control unit 21 and a storage unit 22. The control unit 21 accepts messages sent from the school communication application of the school terminal device 10 and transmits the messages to the parent terminal device 40, and also accepts reply messages sent from the parent terminal device 40 and transmits the reply messages to the school communication application of the school terminal device 10.

[0031] The storage unit 22 includes a guardian table, a message table, and a message destination table.

[0032] As shown in FIG. 2A, the guardian table associates guardian IDs with the terminal identification information used by the guardian of each guardian ID. A guardian ID is identification information that is automatically generated for each guardian by the control unit 21. A guardian ID is simply composed of text such as numbers and letters, and does not include personal information unique to the guardian, such as an email address, telephone number, name, or address. The terminal identification information is identification information unique to the guardian terminal device 40 used by the guardian of each guardian ID.

[0033] As shown in FIG. 2B, the message table is a table that associates a message ID for identifying each message sent from the school terminal device 10 with the message title, message content, and the date and time of sending.

[0034] The message destination table is a table that associates a message ID with a parent ID to which the message of that message ID is to be sent.

[0035] A message for the parent or guardian is created in the school communication application of the school terminal device 10, and the message and the parent ID of the message recipient are sent from the school terminal device 10 to the first server 20. The control unit 21 of the first server 20 updates the message table shown in Fig. 2B and the message destination table shown in Fig. 2C based on the received message and parent ID.

[0036] Then, the control unit 21 refers to the parent table shown in FIG. 2A, identifies the terminal identification information corresponding to the parent ID, and transmits a message to the school communication application of the parent terminal device 40 having the identified terminal identification information.

[0037] The first server 20 includes, as hardware, a CPU, semiconductor memories such as ROM and RAM, storage such as a hard disk, and a communication I / F.

[0038] As described above, the second server 30 is a server that works in conjunction with the school fee collection application, and includes a control unit 31 and a storage unit 32. The control unit 31 accepts a message sent from the school fee collection application of the school terminal device 10, and sends the message to the school communication application of the parent / guardian terminal device 40 via the first server 20, and also accepts a reply message sent from the parent / guardian terminal device 40, and sends the reply message to the school fee collection application of the school terminal device 10.

[0039] The storage unit 32 has an ID federation table that associates the email address of each guardian with the above-mentioned guardian ID of each guardian. Fig. 3 is a diagram showing an example of the ID federation table. The email addresses of guardians in the ID federation table are set and input by each guardian in the school collection application, and are the guardian's identification information (user ID) in the school collection application. In this embodiment, the guardian ID in the school communication application corresponds to the first identification information of the present invention, and the guardian's email address (user ID) in the school collection application corresponds to the second identification information of the present invention.

[0040] A message for the guardian is created in the school fee collection application of the school terminal device 10, and the message and the email address to which the message is to be sent are transmitted from the school terminal device 10 to the second server 30. The control unit 31 of the second server 30 refers to the ID linkage table shown in FIG. 3 based on the received email address, and acquires the guardian ID corresponding to the received email address (user ID). The control unit 31 then transmits the received message and the acquired guardian ID to the first server 20.

[0041] The control unit 21 of the first server 20 updates the message table shown in FIG. 2B and the message destination table shown in FIG. 2C based on the message sent from the second server 30 and the guardian ID.

[0042] Then, the control unit 21 refers to the parent table shown in FIG. 2A, identifies the terminal identification information corresponding to the parent ID, and transmits a message to the school communication application of the parent terminal device 40 having the identified terminal identification information.

[0043] The second server 30 includes, as hardware, a CPU, semiconductor memories such as ROM and RAM, storage such as a hard disk, and a communication I / F.

[0044] The parent terminal device 40 is used by parents of students at the school, and may be a mobile terminal such as a smartphone or tablet terminal, but is not limited to these and may also be a desktop computer or a laptop computer.

[0045] The parent terminal device 40 includes a control unit 41, a storage unit 42, a display unit 43, and a reading unit 44.

[0046] The control unit 41 controls the entire parent / guardian terminal device 40. In particular, the control unit 41 causes the display unit 43 to display messages sent from the school communication application of the school terminal device 10 and received via the first server 20, and messages sent from the school fee collection application of the school terminal device 10 and received via the second server 30 and the first server 20.

[0047] In addition, the control unit 41 accepts reply messages set and input by parents in the school communication application and sends them to the school terminal device 10 via the first server 20, and also accepts reply messages set and input by parents in the school collection application and sends them to the school terminal device 10 via the second server 30.

[0048] A school communication application and a school fee collection application are installed in the storage unit 42. When the school communication application or the school fee collection application is started by the CPU of the control unit 41, a reply message to the school is created and sent in the parent terminal device 40. Note that instead of using an application installed in the storage unit 42 as in this embodiment, an application provided via a web browser may be used.

[0049] The display unit 43 displays a user interface screen of the school communication application, a user interface screen of the school fee collection application, and the like.

[0050] The reading unit 44 has a camera or the like and optically reads printed matter.

[0051] The parent terminal device 40 includes, as hardware, a CPU, semiconductor memories such as ROM and RAM, storage such as a hard disk, and a communication I / F.

[0052] Next, a description will be given of the processing of the message control system 1 of this embodiment. First, the guardian (guardian ID) registration processing in the school communication application will be described with reference to the flowchart shown in FIG.

[0053] First, a school communication application is launched on the school terminal device 10 (S10), and in response to an instruction from a school staff member or the like, a registration QR code (registered trademark) issuance instruction is transmitted from the school terminal device 10 to the first server 20 (S12). The first server 20 generates a registration QR code in response to the received registration QR code issuance instruction (S14), and transmits image data including the registration QR code to the school terminal device 10 (S16).

[0054] Next, at the school, the image data received by the school terminal device 10 is printed using a printing device (not shown) such as a printer (S18), and the printed matter is sent to the parents.

[0055] Then, the parent reads the registration QR code printed on the printed matter using the reading unit 44 of the parent terminal device 40 (S20). Next, the read data and the terminal identification information of the parent terminal device 40 are sent to the first server 20 (S22).

[0056] When the first server 20 receives the read data of the registration QR code, it automatically generates a new guardian ID (S24), associates the guardian ID with the terminal identification information, and registers it in the guardian table shown in FIG. 2A (S26).

[0057] This concludes the description of the guardian (guardian ID) registration process in the school communication application.

[0058] Next, the process of linking the school communication application and the school fee collection application will be described with reference to the flowchart shown in FIG.

[0059] First, based on the contract information exchanged in advance, an interlocking contract table indicating whether or not to perform interlocking processing between the school liaison application and the school collection application is set in the first server 20 (S30). Fig. 6 is a diagram showing an example of the interlocking contract table. Information on whether or not to perform interlocking processing for each school is set in the interlocking contract table. Specifically, if the valid flag shown in Fig. 6 is "TRUE", the interlocking processing described below is performed, and if it is "FALSE", the interlocking processing is not performed.

[0060] Then, when the school communication application is started in the parent terminal device 40 (S32), the parent terminal device 40 transmits a school ID to the first server 20 (S34). The school ID is identification information unique to each school, and is set in advance in the school communication application of the parent terminal device 40.

[0061] When the first server 20 receives the school ID, it checks the valid flag in the linked contract table shown in Fig. 6 and determines whether or not to perform linked processing (S36). If the valid flag is "TRUE", the first server 20 transmits link processing instruction information to the parent terminal device 40 (S38).

[0062] When the parent terminal device 40 receives the instruction information for the linking process, it performs the linking process (S40). Specifically, the parent terminal device 40 displays a screen asking whether or not to approve the linking process, and if the parent approves the linking process, the parent selects (tap) the icon of the school collection application. In response to the tapping of the icon of the school collection service, the parent terminal device 40 transmits the parent ID of the school communication application and the user ID of the school collection application to the second server 30 (S42).

[0063] The user ID of the school fee collection application is identification information for each user of the application, specifically, the user's email address. The user ID is set and input by the parent / guardian on the parent / guardian terminal device 40. If a user ID has already been registered on the parent / guardian terminal device 40, that user ID is transmitted; if it has not been registered, the parent / guardian sets and inputs it at the timing of the linking process.

[0064] When the second server 30 receives the parent ID and the user ID transmitted from the parent terminal device 40, it associates them and newly registers them in the ID linking table shown in FIG. 3 (S44).

[0065] This concludes the description of the collaboration process between the school communication application and the school fee collection application.

[0066] Next, a transmission process when a message is transmitted from the school fee collection application of the school terminal device 10 to the parent terminal device 40 will be described with reference to the flowchart shown in FIG.

[0067] First, a school collection application is launched on the school terminal device 10 (S50), a message is created in the application, a user ID to which the message is addressed is specified, and the message content and user ID are sent to the second server 30 (S52).

[0068] When the second server 30 receives the message content and the user ID, it refers to the ID linkage table shown in FIG. 3 and identifies the guardian ID corresponding to the received user ID (S54).

[0069] Then, the second server 30 transmits the identified guardian ID, the message content, and a message transmission request to the first server 20 (S56).

[0070] When the first server 20 receives the guardian ID and the message content sent from the second server 30, it updates the message table shown in Fig. 2B and the message destination table shown in Fig. 2C, and refers to the guardian table shown in Fig. 2A to identify the terminal identification information corresponding to the received guardian ID (S58). Then, based on the identified terminal identification information, the first server 20 sends a message to the guardian terminal device 40 (S60), which is received by the school communication application of the guardian terminal device 40 (S62), and is viewed by the guardian.

[0071] According to the message management system 1 of the above embodiment, messages sent to parents from the first server 20 and the second server 30, which provide different services, can be aggregated by the school communication application of the first server 20, allowing parents to easily check and manage messages from the different services.

[0072] Furthermore, according to the message management system 1 of the above embodiment, the first server 20 automatically generates a parent ID, and the second server 30 refers to the ID linking table shown in Figure 3 and sends the parent ID to the first server 20 as the message destination. Therefore, messages from the school collection application can be sent to parents using the parent ID without providing personal information of parents or students to the second server 30, thereby preventing the leakage of personal information of parents and students.

[0073] Furthermore, according to the message management system 1 of the above embodiment, the second server 30 links the parent ID of the school communication application with the user ID of the school collection application and registers them in the ID linking table only when the school communication application and the school collection application are linked together, so that messages can be aggregated in the school communication application only if the parent wishes.

[0074] In addition, if the above-mentioned school communication application and school collection application are not linked, the message sent from the school collection application of the school terminal device 10 is sent to the school collection application by the second server 30 based on the user ID (email address).

[0075] Furthermore, in the above embodiment, the first server 20 provides a school contact service and the second server 30 provides a school-oriented fee collection service, but the services provided by the first server 20 and the second server 30 are not limited to these services and may be other services. Furthermore, in the above embodiment, the services are school-related, but the first server 20 and the second server 30 may provide services other than those related to schools. In other words, the services provided by the first server 20 and the second server 30 and the senders and receivers of messages in the present invention are not limited to the examples in the above embodiment.

[0076] Furthermore, the present invention is not limited to the above-described embodiments, and the components can be modified and embodied in practice without departing from the spirit of the invention. Furthermore, various inventions can be formed by appropriately combining multiple components disclosed in the above-described embodiments. For example, all of the components shown in the embodiments can be appropriately combined. Naturally, various modifications and applications are possible within the scope of the invention.

[0077] The present invention further discloses the following supplementary notes.

[0078] (Appendix 1) The message sending system of the present invention comprises a first server that sends a message to an application used by a user, and a second server that provides the user with a service different from that of the first server, and the first server receives the message and destination sent from the second server, and sends the message to the application based on the destination.

[0079] (Appendix 2) In the message sending system described in Appendix 1, the first server can automatically generate and store the user's first identification information and send a message to an application based on the first identification information, and the second server can associate the second identification information entered by the user with the first identification information and store them, and send the first identification information to the first server as the destination.

[0080] (Appendix 3) In the message sending system described in Appendix 2, the second server can link and store the first identification information and the second identification information based on collaboration information between the services provided to the user by the first server and the services provided to the user by the second server.

[0081] (Appendix 4) The message sending method of the present invention sends a message from a first server to an application used by a user and provides the user with a service different from that of the first server from a second server, in which the first server receives the message and destination sent from the second server and sends the message to the application based on the destination. [Explanation of symbols]

[0082] 1. Message Management System 10 School terminal equipment 11 Control section 12 Storage section 13 Display section 20 First Server 21 Control section 22 Memory section 30 Second Server 31 Control Unit 32 Storage section 40 Parental terminal device 41 Control Unit 42 Storage section 43 Display section 44 Reading unit

Claims

1. a first server that sends messages to an application used by a user; a second server that provides a service different from that of the first server to the user; A message transmission system in which the first server receives a message and a destination sent from the second server, and transmits the message to the application based on the destination.

2. the first server automatically generates and stores first identification information of the user, and sends a message to the application based on the first identification information; The message sending system of claim 1, wherein the second server associates and stores the second identification information set and input by the user with the first identification information, and sends the first identification information to the first server as the destination.

3. The message sending system of claim 2, wherein the second server links and stores the first identification information and the second identification information based on collaboration information between the services provided by the first server to the user and the services provided by the second server to the user.

4. Sending a message from the first server to an application used by the user; A message transmission method for providing a service different from that of the first server from a second server to the user, comprising: A message sending method in which the first server receives a message and a destination sent from the second server, and sends the message to the application based on the destination.

Images