Information processing device, information processing method, and program

Abstract

To provide an information processing device, an information processing method, and a program that can reduce the possibility of inconvenient information being viewed on a terminal device.SOLUTION: A user management unit 21 of a server device 2 registers two user terminals 4 so as to associate each of the two user terminals 4 with children and teaching staff members, and synchronize information about the children and the teaching staff members between the two user terminals 4. The user management unit 21 can be set so that the information about at least one of the children and the teaching staff members associated with the two user terminals 4 cannot be viewed on one of the user terminals 4.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to an information processing device, an information processing method, and a program. [Background technology]

[0002] It is common to synchronize information among multiple terminal devices, making it possible to view the same information on each terminal device. As one such technology, Patent Document 1 discloses a system in which two terminal devices owned by two guardians of a child are registered and information about the child is synchronized between those terminal devices. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-123771 Summary of the Invention [Problem to be solved by the invention]

[0004] However, when information is synchronized among a plurality of terminal devices, some of the terminal devices may view information that would be inconvenient if viewed.

[0005] The present invention has been made in view of the above, and has an object to provide an information processing device, an information processing method, and a program that can reduce the possibility of inconvenient information being viewed on a terminal device. [Means for solving the problem]

[0006] According to one aspect of the present invention, there is provided an information processing device comprising a registration unit that registers a plurality of terminal devices so as to associate each of the plurality of terminal devices with at least one association target and synchronize information regarding each association target among the plurality of terminal devices, and the registration unit is capable of setting information regarding at least one of the association targets so that it cannot be viewed on at least one of the plurality of terminal devices.

[0007] According to another aspect of the present invention, there is provided an information processing method executed by a computer, characterized in that the information processing method includes a step of setting information relating to at least one of a plurality of terminal devices that are each associated with at least one associated object and registered so that information relating to each associated object is synchronized so that the information relating to at least one of the associated objects cannot be viewed on the terminal device.

[0008] According to another aspect of the present invention, there is provided a program that causes a computer to execute a step of setting information relating to at least one of a plurality of terminal devices that are each associated with at least one associated object and registered so that information relating to each associated object is synchronized so that the information relating to at least one of the associated objects cannot be viewed on the terminal device. [Effects of the Invention]

[0009] According to the present invention, it is possible to reduce the viewing of inconvenient information on a terminal device. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a block diagram showing a configuration of a communication system according to an embodiment; [Figure 2] 2 is a block diagram showing the configuration of a server device in the communication system shown in FIG. 1. FIG. [Figure 3] FIG. 10 is a diagram showing a guardian table. [Figure 4] FIG. 10 is a diagram showing a terminal table. [Figure 5] FIG. 10 is a diagram showing a children's table. [Figure 6] FIG. 10 is a diagram illustrating a class table. [Figure 7] FIG. 10 is a diagram showing a non-display child table. [Figure 8] 2 is a block diagram showing the configuration of a user terminal in the communication system shown in FIG. 1. FIG. [Figure 9] 1. FIG. 4 is a sequence diagram illustrating an operation for performing a non-display setting in the communication system shown in FIG. [Figure 10] 9 is a sequence diagram for explaining the operation of acquiring viewable child information in the user terminal shown in FIG. 8. FIG. [Figure 11] FIG. 10 is a diagram illustrating an example of a notification list screen. [Figure 12] FIG. 10 is a diagram illustrating another example of the notification list screen. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the same or equivalent parts or components are designated by the same or equivalent reference numerals throughout the drawings, and their description will be omitted or simplified.

[0012] 1, a communication system 1 according to this embodiment includes a server device (corresponding to an information processing device) 2, a school terminal 3, and a plurality of user terminals (corresponding to terminal devices) 4. The school terminal 3 and the user terminals 4 are connectable to the server device 2 via a network 5 such as the Internet.

[0013] The server device 2 manages information transmitted and received between the school terminal 3 and the user terminal 4. The server device 2 is configured by a computer equipped with a CPU, ROM, RAM, a hard disk, etc. The server device 2 may be a cloud server provided on a cloud.

[0014] As shown in FIG. 2, the server device 2 includes a control unit 11, a database unit 12, a program storage unit 13, and an external communication unit .

[0015] The control unit 11 controls the overall operation of the server device 2. The control unit 11 is configured to include a CPU and the like. The control unit 11 includes a user management unit (corresponding to a registration unit) 21, a school newsletter management unit 22, and a contact information management unit 23. Each unit of the control unit 11 is configured by the CPU executing a program stored in the program storage unit 13.

[0016] The user management unit 21 performs a process for user registration to register the user terminal 4 in the server device 2 .

[0017] Specifically, the user management unit 21 issues a guardian ID, a family ID, a terminal ID, and a child ID in response to input operations on the user terminal 4 at the time of user registration.

[0018] Here, the guardian ID is information for uniquely identifying the guardian (parent) of a child or student attending school who owns the user terminal 4. Children or students who attend school will be referred to simply as "children."

[0019] The family ID is information for uniquely identifying the family of the guardian and child. The terminal ID is information for uniquely identifying the user terminal 4. The child ID is information for uniquely identifying the child.

[0020] Then, the user management unit 21 associates the guardian ID, the guardian's nickname, and the family ID, and stores them in a guardian table 31, which will be described later.

[0021] Here, the nickname of the guardian is a name different from the name of the guardian, which is used to display the guardian in an application for viewing school newsletters, etc., used on the user terminal 4. The nickname of the guardian is entered on the user terminal 4 by an input operation during user registration.

[0022] The user management unit 21 also associates the terminal ID with the guardian ID and stores them in a terminal table 32 (described later). The user management unit 21 also associates the child ID with the family ID and stores them in a child table 33 (described later). The user management unit 21 also associates the class ID, child ID, child nickname, and attendance number and stores them in a class table 34 (described later).

[0023] Here, the class ID is information for uniquely identifying a class in a school. The class ID is acquired by the user terminal 4 from a class QR code, which is a QR code (registered trademark) for registration, which will be described later, and is transmitted to the server device 2.

[0024] Furthermore, the child's nickname is a name different from the child's name, and is used to display the child in applications used on the user terminal 4. The attendance number is the attendance number for the class to which the child belongs. The child's nickname and attendance number are entered into the user terminal 4 by input operations during user registration.

[0025] In addition, when registering another user terminal 4 invited from a registered user terminal 4, the user management unit 21 issues a parent ID of the parent who owns the invited user terminal 4 and a terminal ID of the user terminal 4 in response to input operations on the user terminal 4.

[0026] Then, the user management unit 21 stores the parent ID of the parent who is the owner of the invited user terminal 4 and the nickname of the parent in the parent table 31 in association with the home ID to which the parent ID of the parent who is the owner of the inviting user terminal 4 is associated.

[0027] Furthermore, the user management unit 21 stores the terminal ID of the invited user terminal 4 and the guardian ID of the guardian who owns the user terminal 4 in the terminal table 32 in association with each other.

[0028] Here, an invitation from a registered user terminal 4 to another user terminal 4 is performed, for example, after the user terminal 4 of one of the parents of a child has been registered, in order to register the user terminal 4 of the other parent. As will be described later, an invitation from a registered user terminal 4 to another user terminal 4 is performed by having the other user terminal 4 read an invitation QR code displayed by the registered user terminal 4.

[0029] As described above, the parent ID of the parent who is the owner of the inviting user terminal 4 and the parent ID of the parent who is the owner of the invited user terminal 4 are associated with the same family ID and stored in the parent table 31, so that these user terminals 4 are registered in association with each other.

[0030] Furthermore, since the child ID and the household ID are associated in the child table 33, two user terminals 4 associated with each other by a common household ID are each associated with the same child (corresponding to an associated object).

[0031] As a result, two user terminals 4 associated with each other by a common family ID are registered so that information about the child is synchronized between these user terminals 4. The information about the child that is synchronized includes the child's class (class ID), the child's nickname, the child's attendance number, school newsletters (described later), and contact information (described later).

[0032] Furthermore, when user registration is performed to add and associate a new child with an already registered user terminal 4, the user management unit 21 issues a child ID for the new child in response to an input operation on the user terminal 4.

[0033] Then, the user management unit 21 associates the child ID of the new child with the family ID associated with the guardian ID of the guardian who is the owner of the user terminal 4, and stores them in the child table 33.

[0034] Furthermore, the user management unit 21 stores in the class table 34 the class ID of the new child's class, the child ID of the new child, the nickname of the new child, and the attendance number of the class to which the new child belongs, in association with each other.

[0035] Here, the class ID of the new child's class is obtained by the user terminal 4 from the class QR code corresponding to the new child's class and transmitted to the server device 2. In addition, the nickname and attendance number of the new child are input into the user terminal 4 by an input operation during user registration.

[0036] When an operation to add a new child is performed on one of two user terminals 4 that are associated with each other by a common household ID, and the child ID of the new child is associated with the household ID and registered in the child table 33, the new child is also associated with the other user terminal 4 by the common household ID. Information about this new child is also synchronized between the two associated user terminals 4.

[0037] In this embodiment, in addition to classes made up of students, a school also has a faculty class made up of school faculty and staff. The faculty class is set up to distribute business information to faculty and staff.

[0038] Then, the user terminals 4 owned by the teaching staff are registered in the server device 2 in order to view business information and the like.

[0039] When registering a user, the user management unit 21 performs the same process when the user terminal 4 is owned by a teacher or staff member as when the user terminal 4 is owned by a parent or guardian.

[0040] That is, even in this case, the user management unit 21 issues a guardian ID, a family ID, a terminal ID, and a child ID in response to input operations on the user terminal 4 during user registration. In this case, the guardian ID is information for uniquely identifying the faculty member as the owner of the user terminal 4. The family ID is information for uniquely identifying the faculty member's family. The child ID is information for uniquely identifying the faculty member in the faculty class.

[0041] Then, the user management unit 21 associates the guardian ID, the guardian's nickname, and the family ID and stores them in the guardian table 31. The guardian's nickname is the one entered by the teacher or staff member during user registration.

[0042] The user management unit 21 also associates the terminal ID with the guardian ID and stores them in the terminal table 32. The user management unit 21 also associates the child ID with the family ID and stores them in the child table 33. The user management unit 21 also associates the class ID, child ID, child nickname, and attendance number and stores them in the class table 34.

[0043] In this case, the class ID indicates the faculty class, and is obtained by the user terminal 4 from the class QR code for the faculty class and transmitted to the server device 2. The nickname of the child is the one entered by the faculty member during user registration. Also, the attendance number in this case is, for example, the number assigned to the faculty member in the faculty class.

[0044] As described above, the guardian ID and family ID indicating the faculty member who owns the user terminal 4 are associated in the guardian table 31, and the terminal ID and guardian ID are associated in the terminal table 32. Furthermore, the child ID and family ID indicating the faculty member in the faculty class are associated in the child table 33, and the child ID and class ID of the faculty class are associated in the class table 34. Therefore, the user terminal 4 of the faculty member is registered in association with the faculty member in the faculty class.

[0045] If the guardian of a child is also a faculty member of the school, the guardian's user terminal 4 is associated with a faculty member in the faculty class and registered (registered as the faculty member's user terminal 4), and then user registration is performed to add and associate the child. Alternatively, the guardian's user terminal 4 is associated with a child and registered (registered as the guardian's user terminal 4), and then user registration is performed to add and associate the faculty member in the faculty class.

[0046] Therefore, the user terminal 4 of a parent who is also a teacher is registered in association with the child and the teacher who is the parent.

[0047] When two user terminals 4 are registered and associated with each other using a common home ID, and one of these user terminals 4 is registered as a user terminal 4 of a teacher or staff member, each user terminal 4 is associated with the teacher or staff member (corresponding to the associated target) because the child ID indicating the teacher or staff member and the home ID are associated.

[0048] Furthermore, information relating to faculty and staff members is synchronized between these user terminals 4. The information relating to faculty and staff members includes information indicating the faculty and staff member class (class ID), nicknames of students input by faculty and staff members, attendance numbers of students input by faculty and staff members, and school newsletters for faculty and staff members, which will be described later.

[0049] The user management unit 21 can be configured so that information about at least one of the children and teaching staff associated with two user terminals 4 that are registered and associated with each other by a common family ID cannot be viewed on either user terminal 4.

[0050] Specifically, the user management unit 21 associates the child ID with the guardian ID and stores them in the hidden child table 35 described below, thereby making it possible to set information about the child or teaching staff indicated by the child ID so that it cannot be viewed on the user terminal 4 of the guardian (including a guardian who is also a teaching staff member) indicated by the guardian ID.

[0051] The school newsletter management unit 22 manages the school newsletters to be distributed to the user terminal 4. Specifically, the school newsletter management unit 22 performs processes such as storing school newsletter data, which is image data of the school newsletter, in a school newsletter table 36 described later, and transmitting the school newsletter data to the user terminal 4.

[0052] Here, there are school newsletters for parents that are distributed to the parent's user terminal 4, and for teachers that are distributed to the teacher's user terminal 4. Both of these are distributed to the user terminal 4 of a parent who is also a teacher. The school newsletter for teachers is intended to distribute business information, etc.

[0053] The contact information management unit 23 performs processing such as storing contact information in a contact information table 37 (described later). Contact information is information used by the school to contact parents individually.

[0054] The database unit 12 stores a parent table 31, a terminal table 32, a child table 33, a class table 34, a hidden child table 35, a school newsletter table 36, and a contact information table 37. The database unit 12 is composed of a hard disk or the like.

[0055] As shown in Fig. 3, the guardian table 31 is a table that associates guardian IDs, nicknames of guardians, and family IDs. Here, as described above, when a user terminal 4 of a teacher or staff member is registered, the guardian ID corresponding to that user terminal 4 becomes information for uniquely identifying the teacher or staff member who is the owner of the user terminal 4. For this reason, the guardian IDs in the guardian table 31 include those that indicate teachers or staff members who are not guardians of children. Note that the guardian IDs in the guardian table 31 also include those that indicate guardians who are also teachers or staff members of the school.

[0056] As shown in FIG. 4, the terminal table 32 is a table that associates terminal IDs with guardian IDs.

[0057] As shown in Fig. 5, the child table 33 is a table that associates a child ID with a family ID. Here, as described above, when a teacher's user terminal 4 is registered, the child ID becomes information for uniquely identifying the teacher in the teacher class. Therefore, the child ID in the child table 33 includes an ID indicating the teacher in the teacher class.

[0058] As shown in Fig. 6, the class table 34 is a table that associates class IDs, student IDs, student nicknames, and attendance numbers. Here, the class IDs in the class table 34 include those that indicate student classes and those that indicate faculty classes. A student ID associated with a class ID that indicates a faculty class indicates a faculty member.

[0059] As shown in FIG. 7, the hidden child table 35 is a table that associates a child ID with the guardian ID of the guardian who owns the user terminal 4 that cannot view information about the child or teaching staff indicated by the child ID.

[0060] The school newsletter table 36 is a table that stores the above-mentioned school newsletter data in association with distribution target information indicating the class to which the data is to be distributed.

[0061] The contact information table 37 is a table that stores the above-mentioned contact information in association with a child ID.

[0062] The program storage unit 13 stores various programs executed by the CPU of the server device 2. The program storage unit 13 is configured by a hard disk or the like.

[0063] The external communication unit 14 performs communication processing with external devices via the network 5 .

[0064] The school terminal 3 is a terminal device used by school faculty and staff to perform operations related to the distribution of school newsletters, etc. The school terminal 3 is composed of a computer equipped with a CPU, ROM, RAM, hard disk, a display unit consisting of an LCD panel, etc., and an input unit having a keyboard, mouse, etc.

[0065] The user terminal 4 is a terminal device that allows parents of children and teachers to view school newsletters, etc. The user terminal 4 is composed of a smartphone, a tablet terminal, or the like.

[0066] As shown in FIG. 8, the user terminal 4 includes a control unit 41, a program storage unit 42, an application information storage unit 43, an imaging unit 44, a display unit 45, an input unit 46, and an external communication unit 47.

[0067] The control unit 41 controls the overall operation of the user terminal 4. The control unit 41 is configured with a CPU, etc. The control unit 41 performs operations such as display control of school newsletters by causing the CPU to execute a dedicated application program for viewing school newsletters, etc., which is stored in the program storage unit 42.

[0068] The program storage unit 42 stores various programs such as the application programs described above. The program storage unit 42 is configured with a flash memory or the like. The application programs described above can be acquired from any app store server via the network 5, for example.

[0069] The application information storage unit 43 stores the parent ID of the owner of the user terminal 4, the terminal ID of the user terminal 4, and the like.

[0070] The imaging unit 44 is a camera that captures an image of a subject. The imaging unit 44 is used by the user terminal 4 to read a class QR code for user registration and an invitation QR code.

[0071] The display unit 45 displays various screens and information and is configured with a liquid crystal display panel or the like.

[0072] The input unit 46 accepts various input operations by the operator of the user terminal 4. The input unit 46 includes a touch panel (not shown). The touch panel is disposed over the display unit 45. The touch panel detects contact operations by the operator.

[0073] The external communication unit 47 performs communication processing with external devices via the network 5 .

[0074] Next, the operation of the communication system 1 during user registration will be described.

[0075] First, when the class for which a class QR code is to be issued is input on the school terminal 3 and an operation to request the issuance of a class QR code is performed, the school terminal 3 transmits an instruction to issue a class QR code to the server device 2.

[0076] When the user management unit 21 of the server device 2 receives the class QR code issuance instruction, it generates a class QR code with the class ID embedded in it. Then, the user management unit 21 transmits image data of the registration guide including the class QR code to the school terminal 3.

[0077] Next, the school terminal 3 causes a printing device (not shown) to print the registration guidebook for each student in the class onto a printing medium such as paper based on the image data of the registration guidebook. The registration guidebooks are distributed to the homes of each child in the class.

[0078] Here, if the class QR code is for registering the faculty member's user terminal 4 and has a class ID indicating the faculty member class embedded therein, a registration guide is distributed to each faculty member.

[0079] Next, the user terminal 4 reads the class QR code in the registration guide. Specifically, the control unit 41 of the user terminal 4 acquires the class QR code in the image captured by the imaging unit 44. Then, the control unit 41 analyzes the class QR code to acquire the class ID.

[0080] Next, the control unit 41 displays a predetermined input screen on the display unit 45 and accepts input of the guardian's nickname, the child's class attendance number, and the child's nickname. In response, the guardian operates the user terminal 4 to input the above-mentioned information such as the guardian's nickname.

[0081] If the class QR code is for registration on a teacher's user terminal 4, the teacher operates the user terminal 4 to input information such as the guardian's nickname. In this case, the teacher inputs appropriate names as the guardian's nickname and the student's nickname. The teacher also inputs, for example, the number assigned to the teacher in the teacher's class as the attendance number.

[0082] When the above-mentioned information such as the guardian's nickname is input, the control unit 41 transmits to the server device 2 the class ID, the guardian's nickname, the child's attendance number, and the child's nickname.

[0083] When the user management unit 21 of the server device 2 receives information such as the class ID and the parent's nickname, it issues a parent ID, a home ID, a terminal ID, and a child ID.

[0084] Next, the user management unit 21 associates the guardian ID, the guardian's nickname, and the family ID and stores them in the guardian table 31. The user management unit 21 also associates the terminal ID and the guardian ID and stores them in the terminal table 32. The user management unit 21 also associates the child ID and the family ID and stores them in the child table 33. The user management unit 21 also associates the class ID, the child ID, the child's nickname, and the attendance number and stores them in the class table 34.

[0085] Next, the user management unit 21 transmits the guardian ID and the terminal ID to the user terminal 4.

[0086] Next, the control unit 41 of the user terminal 4 stores the guardian ID and terminal ID transmitted from the server device 2 in the application information storage unit 43. This completes the series of operations.

[0087] Next, an operation of registering another user terminal 4 in response to an invitation from a registered user terminal 4 in the communication system 1 will be described.

[0088] Here, the registered user terminal 4 is referred to as user terminal 4A, and another user terminal 4 invited by user terminal 4A is referred to as user terminal 4B. For example, user terminal 4A is the user terminal 4 of one of the child's parents, and user terminal 4B is the user terminal 4 of the other parent.

[0089] First, when an operation to request the issuance of an invitation QR code is performed on the registered user terminal 4A, the control unit 41 of the user terminal 4A transmits an invitation QR code issuance instruction to the server device 2.

[0090] Upon receiving the invitation QR code issuance instruction, the user management unit 21 of the server device 2 issues an invitation code. Then, the user management unit 21 generates an invitation QR code with the invitation code embedded therein.

[0091] Next, the user management unit 21 transmits image data of the invitation QR code to the user terminal 4A.

[0092] When control unit 41 of user terminal 4A receives the image data of the invitation QR code, it causes the invitation QR code to be displayed on display unit 45. Then, the parent or guardian who is the owner of user terminal 4A presents the invitation QR code displayed on user terminal 4A to user terminal 4B.

[0093] Next, user terminal 4B reads the invitation QR code. Specifically, control unit 41 of user terminal 4B acquires the invitation QR code in the image captured by imaging unit 44. Then, control unit 41 of user terminal 4B analyzes the invitation QR code to acquire the invitation code.

[0094] Next, the control unit 41 of the user terminal 4B displays a predetermined input screen on the display unit 45 and accepts input of the guardian's nickname. In response, the guardian who is the owner of the user terminal 4B operates the user terminal 4B to input the guardian's nickname.

[0095] When the parent's nickname is entered, the control unit 41 of the user terminal 4B transmits the invitation code and the parent's nickname to the server device 2.

[0096] Upon receiving the invitation code and the nickname of the guardian, the user management unit 21 of the server device 2 issues a guardian ID of the guardian who is the owner of the user terminal 4B and a terminal ID of the user terminal 4B.

[0097] Next, the user management unit 21 associates the guardian ID of the guardian who owns user terminal 4B and the nickname of the guardian with the home ID to which the guardian ID of the guardian who owns user terminal 4A is associated, and stores the association in the guardian table 31. The user management unit 21 also associates the terminal ID of user terminal 4B with the guardian ID of the guardian who owns user terminal 4B, and stores the association in the terminal table 32.

[0098] Next, the user management unit 21 transmits to the user terminal 4B the guardian ID of the guardian who is the owner of the user terminal 4B and the terminal ID of the user terminal 4B.

[0099] Next, the control unit 41 of the user terminal 4B stores the guardian ID and terminal ID transmitted from the server device 2 in the application information storage unit 43. This completes the series of operations.

[0100] As described above, the parent ID of the parent who owns user terminal 4A and the parent ID of the parent who owns user terminal 4B are associated with the same household ID and stored in parent table 31, thereby registering user terminals 4A and 4B in association with each other.

[0101] Since the child ID and the family ID are associated with each other in the child table 33, the user terminals 4A and 4B associated with each other by a common family ID are associated with the same child.

[0102] As a result, the user terminals 4A and 4B, which are associated with each other by the common household ID, are registered so that information about children is synchronized between the user terminals 4A and 4B.

[0103] Next, the operation at the time of user registration for adding and associating a new student or teacher with a user terminal 4 already registered in the communication system 1 will be described.

[0104] First, the user terminal 4 reads the class QR code corresponding to the new child's class or the QR code of the faculty / staff class to obtain the class ID.

[0105] Next, the control unit 41 of the user terminal 4 displays a predetermined input screen on the display unit 45 and accepts input of the guardian's nickname, the child's class attendance number, and the child's nickname. In response, the guardian operates the user terminal 4 to input the above-mentioned information such as the guardian's nickname.

[0106] Here, when a teacher or staff member is to be additionally associated with an already registered user terminal 4, the teacher or staff member who is also the guardian of the child already associated with the user terminal 4 enters appropriate names as the guardian's nickname and the child's nickname. In addition, the teacher or staff member enters, for example, the number assigned to the teacher or staff member in the teacher's class as the attendance number.

[0107] When the above-mentioned information such as the parent's nickname is entered, the control unit 41 transmits the class ID, the parent's nickname, the child's attendance number, the child's nickname, and the parent ID stored in the application information storage unit 43 to the server device 2.

[0108] When the user management unit 21 of the server device 2 receives information such as the class ID and the parent's nickname, it issues a child ID.

[0109] Here, when a new child is added to and associated with a registered user terminal 4, the child ID issued here is the child ID of the new child. Also, when a teacher is added to and associated with a registered user terminal 4, the child ID issued here indicates the teacher in the teacher class.

[0110] Next, the user management unit 21 associates the child ID of the new child or teacher with the family ID associated with the guardian ID transmitted from the user terminal 4, and stores them in the child table 33. This completes the series of operations.

[0111] Here, when an operation to add a new child or teacher is performed as described above on one of the two user terminals 4 associated with each other by a common family ID, and the child ID of the new child or teacher is associated with the family ID and registered in the child table 33, the new child or teacher will also be associated with the other user terminal 4 by the common family ID. Information about this new child or teacher will also be synchronized between the two user terminals 4 associated with each other.

[0112] Next, the operation of performing non-display setting in the communication system 1 will be described.

[0113] The hidden setting is a setting that prevents information about at least one of the children and teaching staff associated with two user terminals 4 that are associated with each other by a common family ID from being viewed on either user terminal 4.

[0114] Here, an example will be described in which the user terminals 4A and 4B are associated with each other by a common family ID, and information about the associated faculty member is set so that it cannot be viewed by the user terminal 4A.

[0115] Here, the parent who owns user terminal 4A is one of the parents of the child, and the parent who owns user terminal 4B is the other parent. The parent who owns user terminal 4B is also a teacher.

[0116] Since the child ID of at least one child who is the child of these two guardians and the child ID indicating a teacher or staff member are associated with a common family ID in the child table 33, user terminals 4A and 4B are associated with the child and the teacher or staff member.

[0117] 9, the control unit 41 of the user terminal 4B transmits a shared terminal information request to acquire shared terminal information corresponding to the home ID associated with the user terminal 4B to the server device 2. The shared terminal information request transmitted by the user terminal 4B includes the guardian ID of the guardian who is the owner of the user terminal 4B.

[0118] Here, the shared terminal refers to at least one user terminal 4 associated with the common home ID. The shared terminal information is information indicating the user terminal 4 that sent the shared terminal information request and another user terminal 4 that is associated with the common home ID.

[0119] Next, in step S2, the user management unit 21 of the server device 2 that has received the shared terminal information request searches for a shared terminal that corresponds to the home ID associated with the user terminal 4B.

[0120] Specifically, based on the guardian ID of the guardian who owns user terminal 4B, the user management unit 21 refers to the guardian table 31 to obtain the guardian ID and nickname of the guardian who owns user terminal 4A that is associated with the same home ID as the home ID to which user terminal 4B is associated.

[0121] Furthermore, the user management unit 21 refers to the child table 33 and the class table 34 to acquire the child ID and the child's nickname associated with the family ID associated with the user terminals 4A and 4B.

[0122] In this example, multiple child IDs including child IDs that indicate teaching staff, and the nicknames of each child are acquired.

[0123] Next, in step S3, the user management unit 21 transmits the shared terminal information to the user terminal 4B. The shared terminal information includes the guardian ID and nickname of the guardian who owns the user terminal 4A, and the child ID and nickname of the child associated with the family ID associated with the user terminals 4A and 4B.

[0124] Next, in step S4, the control unit 41 of the user terminal 4B that has received the shared terminal information displays a hide instruction screen (not shown) on the display unit 45. The hide instruction screen is a screen for selecting students or teachers who are not allowed to view (display) information on the shared terminal.

[0125] The hide instruction screen displays the nickname of the parent / guardian who owns user terminal 4A as information indicating the owner of the shared terminal. The hide instruction screen also displays a selection field for selecting a child or teacher whose information is to be hidden on user terminal 4A from at least one child and one teacher associated with user terminals 4A and 4B. The children and teachers are displayed by their nicknames in the selection field.

[0126] In this example, a parent who is also a teacher and who owns the user terminal 4B selects "teacher" from the selection field on the non-display instruction screen.

[0127] When an operation to select a faculty member is performed, in step S5, the control unit 41 of the user terminal 4B transmits a hide instruction to the server device 2 to instruct the user terminal 4A to set the information about the faculty member so that it cannot be viewed (displayed). The hide instruction includes the student ID indicating the faculty member.

[0128] Next, in step S6, the user management unit 21 of the server device 2 that has received the hide instruction sets the device to be hidden. Specifically, the user management unit 21 associates the child ID indicating the teaching staff member with the guardian ID of the guardian who is the owner of the user terminal 4A, and stores them in the hidden child table 35.

[0129] For example, assume that "PID1" in the parent table 31 of Fig. 3 and the terminal table 32 of Fig. 4 is the parent ID of the parent who owns the user terminal 4A. Also assume that "PID2" is the parent ID of the parent who is also a teaching staff member and who owns the user terminal 4B. Both "PID1" and "PID2" are associated with "HID1."

[0130] 5, "STID1" and "STID2," both associated with "HID1," are assumed to be the child IDs of children whose parents are the owners of user terminal 4A and user terminal 4B. Also, "STID3," associated with "HID1," is assumed to be the child ID indicating a teacher who is also the guardian and owns user terminal 4B. That is, user terminals 4A and 4B are each associated with two children and a teacher.

[0131] In this case, by storing "STID3" and "PID1" in association with each other in the non-display child table 35 as shown in FIG. 7, it is possible to set up the user terminal 4A so that information about teaching staff cannot be viewed.

[0132] 9, in step S7, the user management unit 21 of the server device 2 transmits a non-display setting end notification to the user terminal 4B to notify that the non-display setting has ended, thereby completing a series of operations.

[0133] Next, the operation of acquiring the viewable child information in the user terminal 4 will be described.

[0134] The viewable child information is information indicating children for whom an application for viewing school newsletters and the like on the user terminal 4 is to display information such as school newsletters.

[0135] 10, when an application is launched or the screen is switched to the home screen of the application on the user terminal 4, in step S12 the control unit 41 transmits a request for viewable child information to acquire viewable child information to the server device 2. The request for viewable child information includes the guardian ID of the guardian who is the owner of the user terminal 4.

[0136] Next, in step S13, the user management unit 21 of the server device 2 that has received the request for viewable child information searches for a child whose information is to be displayed in the user terminal 4 that has sent the request for viewable child information.

[0137] Specifically, the user management unit 21 refers to the guardian table 31 based on the guardian ID of the guardian who owns the user terminal 4 that sent the request for viewable child information, and acquires the family ID associated with that user terminal 4. Then, the user management unit 21 refers to the child table 33 and the class table 34 and acquires the child ID associated with the family ID with which that user terminal 4 is associated.

[0138] Here, the user management unit 21 excludes from the search any child ID associated with the household ID to which the user terminal 4 is associated that is associated in the hidden child table 35 with the guardian ID of the guardian who owns the user terminal 4.

[0139] In other words, even if the child ID is associated with the household ID associated with the user terminal 4 from which the request for viewable child information was sent, the child ID of a child or teacher who is set so that information cannot be viewed on that user terminal 4 will not be included in the viewable child information sent in step S14 described below.

[0140] Next, in step S14, the user management unit 21 transmits the viewable child information including the child ID acquired by the search in step S13 to the user terminal 4 that sent the viewable child information request. This completes the series of operations.

[0141] Using the example of user terminals 4A and 4B used in the explanation of the hide setting operation above, in this example, information about teachers and staff members is set to be unviewable on user terminal 4A. Therefore, when an application is launched or the screen is switched to the home screen on user terminal 4A and a request for viewable child information is sent to server device 2, the viewable child information returned from server device 2 does not include a child ID indicating a teacher or staff member. On the other hand, when an application is launched or the screen is switched to the home screen on user terminal 4B and a request for viewable child information is sent to server device 2, the viewable child information returned from server device 2 includes a child ID indicating a teacher or staff member in addition to a child ID indicating a child.

[0142] On the user terminal 4, the information on the children and teaching staff indicated by the above-mentioned viewable child information can be viewed.

[0143] For example, when a parent or guardian wishes to view a school newsletter on the user terminal 4, the parent or guardian can select the school newsletter to view from a notification list screen 51 shown in FIG.

[0144] Here, the control unit 41 of the user terminal 4 displays tabs 52A to 52C for each child and teacher indicated in the viewable child information on the notification list screen 51. In the example of FIG. 11, the tabs 52A and 52B are for displaying a list of school newsletters for parents of children for each child. The tab 52C is for displaying a list of school newsletters for teachers. The lists of school newsletters for each child and teacher are stored in the application information storage unit 43 of the user terminal 4 based on notifications from the server device 2.

[0145] When an operation to select one of the school newsletters is performed from the notification list screen 51, the control unit 41 requests the school newsletter data of the selected school newsletter from the server device 2. In response, the school newsletter management unit 22 of the server device 2 transmits the requested school newsletter data to the user terminal 4.

[0146] The control unit 41 of the user terminal 4 displays an image of the school newsletter on the display unit 45 based on the school newsletter data transmitted from the server device 2. In this way, the school newsletter can be viewed.

[0147] Even if a child ID is associated with a family ID with which the user terminal 4 is associated, if the child ID is not included in the viewable child information, the tab for the child or faculty member indicated by the child ID will not be displayed on the notification list screen 51. Therefore, the school newsletter for the parent or guardian of the child indicated by the child ID or the school newsletter for the faculty member cannot be viewed on the user terminal 4.

[0148] If the user terminal 4 is set to not allow viewing of information about faculty and staff, the faculty and staff tab will not be displayed on the notification list screen 51, as shown in Figure 12. Therefore, it is not possible to select and view school newsletters for faculty and staff.

[0149] In the example of user terminals 4A and 4B used in the explanation of the operation of the hide setting mentioned above, the notification list screen 51 is displayed as shown in Fig. 11 on user terminal 4B. In contrast, on user terminal 4A, which is set so that information about faculty and staff cannot be viewed, the notification list screen 51 is displayed as shown in Fig. 12, and school newsletters intended for faculty and staff cannot be selected and viewed. This makes it possible to prevent information used by faculty and staff, which should not be viewed by anyone other than faculty and staff, from being viewed on user terminal 4A of a parent who is not a faculty member.

[0150] In the example of user terminals 4A and 4B used in the explanation of the hide setting operation described above, information about teachers and staff was set to be unavailable, but it may also be set to be unavailable for information about children. In a user terminal 4 that is set to be unavailable for information about a certain child, in addition to the school newsletter for the child's parents, the above-mentioned contact information corresponding to the child will also be unavailable for viewing.

[0151] As described above, in the communication system 1, the user management unit 21 of the server device 2 can set two user terminals 4 that are associated with each other and have synchronized information so that information about at least one of the associated students and teaching staff cannot be viewed on either user terminal 4. This reduces the risk of inconvenient information being viewed on the user terminal 4.

[0152] For example, the user management unit 21 can set two user terminals 4 that are associated with each other and have synchronized information so that information about a teacher or staff member associated with the two user terminals 4 cannot be viewed on one (some) of the user terminals 4. This reduces the possibility that business information about teachers or staff members that should not be viewed by anyone other than the teachers or staff members will be viewed on the user terminals 4 of parents other than the teachers or staff members.

[0153] In the above-described embodiment, an example was described in which two user terminals 4 owned by a child's family that are associated with each other can be set so that information about at least one of the associated child and teaching staff cannot be viewed on either user terminal 4.

[0154] However, the user terminal 4 is not limited to those owned by the child's family, and the number of user terminals 4 associated with each other is not limited to two. Furthermore, the association targets of the user terminal 4 are not limited to children and teachers. Furthermore, the number of user terminals 4 that are set to prevent the viewing of information related to the association targets is not limited. It is sufficient that at least one of the terminal devices among a plurality of terminal devices that are each associated with at least one association target and registered so that information related to each association target is synchronized can be set to prevent the viewing of information related to at least one of the association targets.

[0155] 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 created by appropriately combining multiple components disclosed in the above-described embodiments. For example, some components may be omitted from all the components shown in the embodiments.

[0156] [Note] The present application discloses the following inventions.

[0157] (Appendix 1) a registration unit that registers a plurality of terminal devices so as to associate each of the plurality of terminal devices with at least one association object and synchronize information about each association object among the plurality of terminal devices; The information processing device, wherein the registration unit can set information relating to at least one of the association targets so that the information cannot be viewed on at least one of the plurality of terminal devices.

[0158] (Appendix 2) the plurality of terminal devices are owned by the families of students attending the school; The information processing device described in Appendix 1 is characterized in that the registration unit associates the multiple terminal devices with students attending the school and school faculty and staff, registers the multiple terminal devices so as to synchronize information about the students and information about the faculty and staff, and sets the information about the faculty and staff so that it cannot be viewed on some of the terminal devices.

[0159] (Appendix 3) 1. A computer-implemented information processing method, comprising: An information processing method characterized by including a step of setting information relating to at least one of a plurality of terminal devices that are each associated with at least one associated object and registered so that information relating to each associated object is synchronized so that information relating to at least one of the associated objects cannot be viewed on the terminal device.

[0160] (Appendix 4) A program that causes a computer to execute a step of setting information relating to at least one of a plurality of terminal devices that are each associated with at least one associated object and registered so that information relating to each associated object is synchronized so that information relating to at least one of the associated objects cannot be viewed on the terminal device. [Explanation of symbols]

[0161] 1. Communication Systems 2. Server device 3. School terminals 4. User terminal 11 Control section 12 Database Department 13 Program memory section 14 External Communications Department 21 User Management Department 22 School Newsletter Management Department 23 Contact Information Management Department 31 Parent Table 32 Terminal Table 33 Children's Table 34 Class Table 35 Hidden Children Table 36 School News Table 37 Contact Information Table 41 Control Unit 42 Program memory section 43 Application information storage unit 44 Imaging unit 45 Display section 46 Input section 47 External Communications Department 51 Notification list screen 52A~52C Tabs

Claims

1. a registration unit that registers a plurality of terminal devices so as to associate each of the plurality of terminal devices with at least one association object and synchronize information regarding each association object among the plurality of terminal devices; The information processing device, wherein the registration unit can set information relating to at least one of the association targets so that the information cannot be viewed on at least one of the plurality of terminal devices.

2. the plurality of terminal devices are owned by the families of students attending the school; The information processing device described in claim 1, characterized in that the registration unit associates the multiple terminal devices with students attending the school and school faculty and staff, registers the multiple terminal devices so as to synchronize information about students and information about faculty and staff, and sets the information about faculty and staff so that it cannot be viewed on some of the terminal devices.

3. 1. A computer-implemented information processing method, comprising: An information processing method characterized by including a step of setting information relating to at least one of a plurality of terminal devices, each associated with at least one associated object and registered so that information relating to each associated object is synchronized, so that information relating to at least one of the associated objects cannot be viewed on the terminal device.

4. A program that causes a computer to execute a step of setting information relating to at least one of a plurality of terminal devices that are each associated with at least one associated object and registered so that information relating to each associated object is synchronized so that information relating to at least one of the associated objects cannot be viewed on the terminal device.

Images