Information processor, information processing method, and program

Abstract

To provide an information processor, an information processing method and a program that can reduce errors when registering terminal devices while reducing user effort.SOLUTION: A user registration section 23 of a server device 2 registers a plurality of parental terminals 5 of a predetermined upper limit number or less by associating them with each other. The user registration section 23 can deregister the respective parental terminals 5.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] In order to synchronize information among multiple terminal devices that use the same application, the multiple terminal devices are associated with each other and registered in a system. As one such technique, Patent Document 1 discloses a system in which two terminal devices owned by two guardians of a child are associated with each other and registered, and information is synchronized between the 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] In some systems, there is a limit to the number of terminal devices that can be registered in association with each other.

[0005] In such a case, for example, if an application is uninstalled on a registered terminal device due to an incorrect operation, and then reinstalled and re-registered, it may be treated as a different terminal device, resulting in a registration error as the above-mentioned upper limit is exceeded.

[0006] Also, for example, if the model change is not performed according to the normal procedure due to a malfunction of the registered terminal device, when an attempt is made to register the terminal device after the model change, a registration error may occur as the number of registered devices exceeds the above-mentioned upper limit.

[0007] For example, it is possible to avoid the above-mentioned registration error by re-registering each terminal device as a new terminal device, but this requires a great deal of effort from the user.

[0008] The present invention has been made in view of the above, and has as its object to provide an information processing device, an information processing method, and a program that can reduce registration errors of terminal devices while minimizing the work required of users. [Means for solving the problem]

[0009] According to one aspect of the present invention, an information processing device is provided which includes a registration unit that registers multiple terminal devices up to a predetermined upper limit number in association with each other, and which is characterized in that the registration unit is capable of deregistering each of the terminal devices.

[0010] According to another aspect of the present invention, there is provided an information processing method executed by a computer, characterized in that it includes a step of deregistering at least one of a plurality of terminal devices that are associated with each other and registered, the number of which is up to a predetermined upper limit.

[0011] According to another aspect of the present invention, a program is provided that causes a computer to execute a step of deregistering at least one of a plurality of terminal devices that are associated with each other and registered, the number of which is equal to or less than a predetermined upper limit. [Effects of the Invention]

[0012] According to the present invention, it is possible to reduce registration errors of terminal devices while minimizing the work required of users. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a block diagram showing a configuration of an information processing system according to an embodiment; [Figure 2] 2 is a block diagram showing a configuration of a server device of the information processing system shown in FIG. 1. FIG. [Figure 3]FIG. 10 is a diagram showing a school table. [Figure 4] FIG. 10 is a diagram showing a guardian table. [Figure 5] FIG. 10 is a diagram showing a terminal table. [Figure 6] FIG. 10 is a diagram showing a children's table. [Figure 7] FIG. 10 is a diagram illustrating a class table. [Figure 8] 2 is a block diagram showing the configuration of a parent terminal of the information processing system shown in FIG. 1. FIG. [Figure 9] 1. FIG. 4 is a sequence diagram for explaining an operation at the time of user registration in the information processing system shown in FIG. [Figure 10] FIG. 10 is a diagram showing the class QR code section of the registration guide. [Figure 11] FIG. 10 is a diagram showing a parental information screen. [Figure 12] FIG. 10 is a diagram showing a child information screen. [Figure 13] 1. FIG. 4 is a sequence diagram illustrating an operation when a parent terminal is additionally registered in the information processing system shown in FIG. [Figure 14] FIG. 10 is a diagram showing an invitation QR code screen. [Figure 15] 1. FIG. 4 is a sequence diagram for explaining the operation of canceling the registration of a parent terminal in the information processing system shown in FIG. [Figure 16] FIG. 10 is a diagram showing a deregistration screen. DETAILED DESCRIPTION OF THE INVENTION

[0014] 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.

[0015] 1, an information processing system 1 according to this embodiment includes a server device (corresponding to an information processing device) 2, a school terminal 3, a printing device 4, and a parent terminal (corresponding to a terminal device) 5. The school terminal 3 and the parent terminal 5 are connectable to the server device 2 via a network 6 such as the Internet.

[0016] Here, the school terminal 3 and the printing device 4 are installed in a school 7. There may be one or more schools 7 equipped with the school terminal 3 and the printing device 4. Furthermore, there may be one or more school terminals 3 installed in one school 7. The school 7 may be an elementary school, a junior high school, or the like, and may be public or private.

[0017] Furthermore, the guardian terminal 5 is a smartphone, tablet terminal, etc. owned by the guardian (parent) of a child or student who commutes to school 7. There may be one or more guardian terminals 5 for each student. Children or students who commute to school 7 will be referred to simply as "children."

[0018] The server device 2 is a server that provides support services including a points-granting service that grants points to the school 7 that can be exchanged for goods in response to viewing advertisements on the parent / guardian terminal 5. In addition to the points-granting service, the support services also include a letter service that distributes and delivers school newsletters, and a communication service that carries out various communications between the school 7 and the children's homes. The school 7 can sign up for and use only some of the above-mentioned three services included in the support services.

[0019] The server device 2 is configured by a computer including a CPU, a ROM, a RAM, a hard disk, etc. The server device 2 may be a cloud server provided on a cloud.

[0020] 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 .

[0021] Here, since the information processing system 1 of this embodiment is characterized by the user registration of the support service described above, in FIG. 2, illustration and description of the configuration other than the configuration related to user registration will be omitted.

[0022] 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 class code issuing unit 21, an invitation code issuing unit 22, and a user registration unit (corresponding to a registration unit) 23. Each unit of the control unit 11 is configured by the CPU executing a program stored in the program storage unit 13.

[0023] When the class code issuing unit 21 receives a class code issuance instruction from the school 7, it issues a class code for the class at the school 7 instructed in the class code issuance instruction. The class code issuing unit 21 also issues (generates) a class QR code, which is a QR code (registered trademark) with the class code embedded in it. The class code is a code that includes a class ID. The class code is, for example, made up of a numeric string. The class ID is information for uniquely identifying each class at the school 7.

[0024] When the invitation code issuing unit 22 receives an invitation code issuing instruction from the parent / guardian terminal 5, it issues an invitation code. The invitation code issuing unit 22 also issues (generates) an invitation QR code with the invitation code embedded in it. The invitation code is a code used to associate another parent / guardian terminal 5 with the registered parent / guardian terminal 5 and register it in the server device 2 via a parent / guardian terminal 5 that has already been registered in the server device 2. The invitation code is, for example, made up of a numeric string.

[0025] The user registration unit 23 performs user registration processing to register a parent / guardian terminal 5 that uses the above-mentioned support service in the server device 2. Specifically, when the user registration unit 23 receives the terminal transmission information (described below) transmitted from the parent / guardian terminal 5 that has acquired the class code, it issues a parent / guardian ID, a home ID, a terminal ID, and a child ID. Here, the parent / guardian ID is information for uniquely identifying the parent / guardian. The home ID is information for uniquely identifying the parent / guardian and the home of the child. The terminal ID is information for uniquely identifying the parent / guardian terminal 5. The child ID is information for uniquely identifying the child.

[0026] Then, the user registration unit 23 associates the guardian ID with the home ID and stores them in the guardian table 32. Note that, as will be described later, information such as the nickname of the guardian is also stored in the guardian table 32.

[0027] Furthermore, the user registration unit 23 associates the terminal ID with the guardian ID and stores them in the terminal table 33, which will be described later. Note that the terminal information and deletion flag are also stored in the terminal table 33, as will be described later.

[0028] The user registration unit 23 also associates the child ID with the family ID and stores them in a child table 34, which will be described later. The user registration unit 23 also associates the class ID included in the terminal transmission information with the child ID and stores them in a class table 35, which will be described later. The child's nickname and attendance number are also stored in the class table 35, which will be described later.

[0029] In addition, when an invitation code is input from another parent terminal 5 that has obtained the invitation code through a registered parent terminal 5, the user registration unit 23 registers the other parent terminal 5 in association with the registered parent terminal 5.

[0030] Specifically, when the user registration unit 23 receives the invited terminal transmission information described below, which includes an invitation code, from a parent terminal 5 that has obtained the invitation code from a registered parent terminal 5 (that has been invited), and if the condition for the maximum number of shared terminals described below is met, the user registration unit 23 issues a parent ID for the parent who owns the invited parent terminal 5 and a terminal ID for the invited parent terminal 5.

[0031] Then, the user registration unit 23 stores the parent ID of the parent who owns the invited parent terminal 5 in the parent table 32 in association with the home ID to which the parent ID of the parent who owns the invited registered parent terminal 5 is associated. Note that, as will be described later, the nickname of the parent who owns the invited parent terminal 5 is also stored in the parent table 32.

[0032] Furthermore, the user registration unit 23 associates the terminal ID of the invited parent / guardian terminal 5 with the parent / guardian ID of the parent who owns the parent / guardian terminal 5, and stores them in the terminal table 33. As will be described later, the terminal information and deletion flag of the invited parent / guardian terminal 5 are also stored in the terminal table 33.

[0033] As a result, the registered parent / guardian terminal 5 and the parent / guardian terminal 5 invited by the registered parent / guardian terminal 5 are associated with each other using the common family ID and registered in the server device 2. As a result, information about the child (corresponding to the association target) associated with these parent / guardian terminals 5 is synchronized between the registered parent / guardian terminal 5 that invited and the invited parent / guardian terminal 5. The information about the child that is synchronized includes the child's class (class ID), the child's nickname, the child's attendance number, the school newsletter in the letter service described above, contact information in the contact service, etc.

[0034] Here, in the information processing system 1, the number of shared terminals, which are parent / guardian terminals 5 associated with each other and registered using a common home ID, is set to a predetermined upper limit of at least 2. That is, the user registration unit 23 can associate multiple parent / guardian terminals 5 with each other and register them in the server device 2 up to the upper limit.

[0035] The user registration unit 23 can also cancel the registration of each registered parent terminal 5. Specifically, the user registration unit 23 cancels the registration of the parent terminal 5 by changing a deletion flag (described later) associated with the terminal ID of the parent terminal 5 instructed by a deregistration instruction (described later) from "FALSE" to "TRUE."

[0036] The database unit 12 stores a school table 31, a guardian table 32, a terminal table 33, a student table 34, and a class table 35. The database unit 12 is configured with a hard disk or the like.

[0037] As shown in FIG. 3, the school table 31 is a table that associates school IDs with school names.

[0038] As shown in FIG. 4, the guardian table 32 is a table that associates guardian IDs, nicknames of guardians, ages of guardians, relationships with children, and family IDs.

[0039] Here, the guardian's nickname, guardian's age, and relationship to the child are entered in the guardian terminal 5 when the guardian terminal 5 is registered in the server device 2. The guardian's nickname is used to display the guardian in an application for using the support service on the guardian terminal 5. The guardian's nickname is different from the guardian's name.

[0040] As shown in FIG. 5, the terminal table 33 is a table that associates terminal IDs, guardian IDs, terminal information, and deletion flags.

[0041] Here, the terminal information is obtained from the parent terminal 5 when registering the parent terminal 5 with the server device 2. As the terminal information, information such as the model name held by the parent terminal 5 can be used.

[0042] The deletion flag indicates whether or not the parent terminal 5 has been deregistered from the server device 2. "TRUE" indicates that the registration has been deregistered, and "FALSE" indicates that the registration has not been deregistered (is registered). When the parent terminal 5 is registered with the server device 2, the deletion flag is set to "FALSE." The deletion flag associated with the parent ID of the parent who owns the parent terminal 5 that has been instructed to be deregistered by a deregistration instruction, which will be described later, is changed to "TRUE."

[0043] As shown in FIG. 6, the child table 34 is a table that associates child IDs with household IDs.

[0044] As shown in FIG. 7, the class table 35 is a table that associates class IDs, student IDs, student nicknames, and attendance numbers.

[0045] Here, the child's nickname and attendance number are entered into the parent / guardian terminal 5 when registering the parent / guardian terminal 5 with the server device 2. The child's nickname is used to display the child in an application for using support services on the parent / guardian terminal 5. The child's nickname is different from the child's name. The attendance number is the attendance number for the class to which the child belongs.

[0046] 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.

[0047] The external communication unit 14 performs communication processing with external devices via the network 6 .

[0048] The school terminal 3 is a terminal device used by teachers at the school 7 to perform operations related to the support service. 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.

[0049] The printing device 4 prints the registration guidebook and the like, which will be described later.

[0050] The parent terminal 5 is a terminal device that allows a parent of a child to perform operations related to the support service. As described above, the parent terminal 5 is a smartphone, a tablet terminal, or the like.

[0051] As shown in FIG. 8, the parent terminal 5 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.

[0052] The control unit 41 controls the overall operation of the parent / guardian terminal 5. The control unit 41 is configured to include a CPU, etc. The control unit 41 performs processing related to the support service by causing the CPU to execute a dedicated application program for using the support service, which is stored in the program storage unit 42.

[0053] The program storage unit 42 stores various programs such as application programs for using the support service. The program storage unit 42 is configured with a flash memory or the like. The application programs for using the support service can be obtained from any app store server via the network 6 and installed on the parent / guardian terminal 5, for example.

[0054] The application information storage unit 43 stores the parent ID of the parent who owns the parent terminal 5, the terminal ID of the parent terminal 5, the school ID of the school 7 attended by a child in the home of the parent who owns the parent terminal 5, the class ID of the class to which the child belongs, etc.

[0055] The imaging unit 44 is a camera that captures an image of a subject. The imaging unit 44 is used by the parent terminal 5 to read the class QR code and the invitation QR code.

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

[0057] The input unit 46 accepts various input operations by the operator of the parent / guardian terminal 5. 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.

[0058] The external communication unit 47 performs communication processing with external devices via the network 6 .

[0059] Next, the operation of the information processing system 1 during user registration will be described.

[0060] 9, the school terminal 3 of the school 7 transmits a class code issuance instruction to the server device 2. Specifically, when the class for which a class code is to be issued is input and an operation to request the issuance of the class code is performed, the school terminal 3 transmits the class code issuance instruction to the server device 2. The class code issuance instruction includes the class name, the number of students in the class, and the school ID of the school 7 that transmitted the class code issuance instruction.

[0061] When the server device 2 receives the class code issuance instruction, in step S2, the class code issuing unit 21 issues a class code including a class ID.

[0062] Next, in step S3, the class code issuing unit 21 generates a class QR code in which the class code is embedded.

[0063] Next, in step S4, the class code issuing unit 21 transmits image data of the registration guide including the class QR code to the school terminal 3 that sent the class code issuance instruction.

[0064] Next, in step S5, the school terminal 3 instructs the printing device 4 to print registration guides for the number of children in the class on a printing medium such as paper based on the image data of the registration guides. As a result, the printing device 4 prints the registration guides.

[0065] Here, the registration guide includes a class QR code field 51 shown in FIG. 10. Class QR code field 51 includes class QR code 52. Class QR code field 51 also includes an attendance number entry field 53. The attendance number of each student in the class is entered by hand in attendance number entry field 53. Class QR code field 51 also includes the school name, class name, the preset expiration date of the class QR code, and the class code.

[0066] 9, in step S6, the school 7 distributes a registration guide to the home of each child. For example, the school 7 has each child take the registration guide home.

[0067] Next, in step S7, the parent terminal 5 reads the class QR code 52 in the class QR code field 51. Specifically, the control unit 41 of the parent terminal 5 acquires the class QR code 52 in the video captured by the imaging unit 44.

[0068] Next, in step S8, the control unit 41 analyzes the class QR code 52 and acquires the class code embedded in the class QR code 52. The control unit 41 then acquires a class ID from the class code. The control unit 41 stores the acquired class ID in the application information storage unit 43.

[0069] Next, in step S9, the parent / guardian terminal 5 accepts input of parent / guardian information. Specifically, the control unit 41 causes the display unit 45 to display a parent / guardian information screen 56 shown in FIG. 11. The parent who owns the parent / guardian terminal 5 performs an operation to input parent / guardian information on the parent / guardian information screen 56. The parent / guardian information includes the parent's age, relationship to the child, and nickname. The control unit 41 stores the input parent / guardian information in the application information storage unit 43.

[0070] Returning to FIG. 9 , in step S10, the parent / guardian terminal 5 accepts input of child information. Specifically, the control unit 41 causes the display unit 45 to display a child information screen 57 shown in FIG. 12. The parent / guardian who owns the parent / guardian terminal 5 performs an operation to input child information into the child information screen 57. The child information includes the child's attendance number in his / her class and the child's nickname. The control unit 41 stores the input child information in the application information storage unit 43.

[0071] 9, in step S11, the control unit 41 of the parent / guardian terminal 5 transmits terminal transmission information to the server device 2. The terminal transmission information includes the class ID, terminal information, the parent / guardian's generation, the parent / guardian's relationship to the child, the parent / guardian's nickname, the child's nickname, and the attendance number.

[0072] When the server device 2 receives the terminal transmission information, in step S12, the user registration unit 23 issues a parent ID and a family ID of the parent who owns the parent terminal 5 that is the source of the terminal transmission information. The user registration unit 23 also issues a terminal ID of the parent terminal 5 that is the source of the terminal transmission information. The user registration unit 23 also issues a child ID of the child whose attendance number and nickname are included in the terminal transmission information.

[0073] Next, in step S13, the user registration unit 23 registers the guardian ID, home ID, terminal ID, child ID, and information included in the terminal transmission information in the guardian table 32, terminal table 33, child table 34, and class table 35.

[0074] Specifically, the user registration unit 23 associates the guardian ID, the guardian's nickname, the guardian's generation, the guardian's relationship to the child, and the family ID, and stores them in the guardian table 32. The user registration unit 23 also associates the terminal ID, the guardian ID, terminal information, and a deletion flag, and stores them in the terminal table 32. Here, the user registration unit 23 sets the deletion flag to "FALSE."

[0075] The user registration unit 23 also associates the child ID with the family ID and stores them in the child table 34. The user registration unit 23 also associates the class ID, child ID, child nickname, and attendance number and stores them in the class table 35.

[0076] Next, in step S14, the user registration unit 23 transmits the parent ID, the terminal ID, and the school ID to the parent terminal 5.

[0077] Next, in step S15, the control unit 41 of the parent terminal 5 stores the parent ID, terminal ID, and school ID transmitted from the server device 2 in the application information storage unit 43. This completes the series of processes.

[0078] Next, the operation of the information processing system 1 at the time of additional registration (invitation) of the parent terminal 5 will be described.

[0079] Additional registration (invitation) of a parent / guardian terminal 5 is performed when there is already a registered parent / guardian terminal 5 for a child, and another parent / guardian terminal 5 corresponding to that child is registered. Additional registration of a parent / guardian terminal 5 is performed, for example, after the parent / guardian terminal 5 of one of the parents of a child has been registered, in order to register the parent / guardian terminal 5 of the other parent.

[0080] 13, the registered parent / guardian terminal 5A transmits an invitation code issuance instruction to the server device 2. Specifically, when an operation to request the issuance of an invitation code is performed, the control unit 41 of the parent / guardian terminal 5A transmits the invitation code issuance instruction to the server device 2. The invitation code issuance instruction includes the parent / guardian ID of the parent / guardian who owns the parent / guardian terminal 5A.

[0081] 13, the registered parent / guardian terminal 5 of a certain child's parent is referred to as parent / guardian terminal 5A, and the parent / guardian terminal 5 that is additionally registered (invited) as the parent / guardian terminal 5 of the child is referred to as parent / guardian terminal 5B. In other words, the owners of parent / guardian terminals 5A and 5B are the parents of the same child.

[0082] When the server device 2 receives the invitation code issuance instruction, in step S22, the invitation code issuing unit 22 issues an invitation code.

[0083] Next, in step S23, the invitation code issuing unit 22 generates an invitation QR code in which the invitation code is embedded.

[0084] Next, in step S24, the invitation code issuing unit 22 transmits image data of the invitation QR code to the parent terminal 5A.

[0085] Next, in step S25, the control unit 41 of the parent / guardian terminal 5A causes the invitation QR code to be displayed on the display unit 45. Specifically, the control unit 41 causes the invitation QR code 59 to be displayed on the invitation QR code screen 58 shown in FIG.

[0086] Returning to FIG. 13, in step S26, the parent who owns the parent terminal 5A submits the invitation QR code 59 displayed on the parent terminal 5A to the parent terminal 5B.

[0087] Next, in step S27, the parent terminal 5B reads the invitation QR code 59. Specifically, the control unit 41 of the parent terminal 5B acquires the invitation QR code 59 in the image captured by the imaging unit 44.

[0088] Next, in step S28, control unit 41 analyzes invitation QR code 59 and obtains the invitation code embedded in invitation QR code 59.

[0089] Next, in step S29, the parent terminal 5B accepts input of parent information. The process of step S29 is the same as the process of step S9 in FIG.

[0090] Next, in step S30, the control unit 41 transmits invited terminal transmission information to the server device 2. The invited terminal transmission information includes an invitation code, terminal information of the parent / guardian terminal 5B, the age of the parent / guardian who owns the parent / guardian terminal 5B, the parent / guardian's relationship to the child, and the parent / guardian's nickname.

[0091] When the server device 2 receives the invited terminal transmission information, in step S31, the user registration unit 23 determines whether the number of shared terminals registered and associated with each other by the home ID to which the guardian terminal 5A is associated is less than a predetermined upper limit number.

[0092] Here, the user registration unit 23 determines that the number of shared terminals is less than the upper limit if the number of parent IDs associated with the home ID to which the parent terminal 5A is associated in the parent table 32 and whose associated deletion flag in the terminal table 33 is "FALSE" is less than the upper limit.

[0093] If it is determined that the number of shared terminals has reached the upper limit (step S31: NO), in step S32, the user registration unit 23 transmits an error notification to the parent terminal 5B.

[0094] When parent terminal 5B receives the error notification, in step S33, control unit 41 causes display unit 45 to display an error screen (not shown) for notifying that a registration error (shared terminal upper limit error) has occurred, which indicates that registration is not possible because the upper limit on the number of shared terminals has been reached. This ends the series of processes.

[0095] If it is determined in step S31 that the number of shared terminals is less than the upper limit (step S31: YES), in step S34, the user registration unit 23 issues a parent ID of the parent who owns the parent terminal 5B and a terminal ID of the parent terminal 5B.

[0096] Next, in step S35, the user registration unit 23 registers the guardian ID, terminal ID, terminal information, guardian's age, guardian's relationship to the child, and guardian's nickname corresponding to the guardian terminal 5B in the guardian table 32 and terminal table 33.

[0097] Specifically, the user registration unit 23 stores in the parent table 32 the parent ID, age group, relationship to the child, and nickname of the parent who owns the parent terminal 5B, in association with the same home ID as the home ID associated with the parent ID of the parent who owns the parent terminal 5A.

[0098] Furthermore, the user registration unit 23 associates the guardian ID of the guardian who owns the guardian terminal 5B, the terminal ID and terminal information of the guardian terminal 5B, and a deletion flag and stores them in the terminal table 33. Here, the user registration unit 23 sets the deletion flag to "FALSE."

[0099] As a result, the parent terminals 5A and 5B are associated with each other by the common family ID and registered in the server device 2. As a result, the child ID, class ID, child attendance number, and nickname are synchronized between the parent terminals 5A and 5B. Therefore, the parent terminal 5B can be registered without inputting the child information (child attendance number and nickname) that was input when registering the parent terminal 5A. In addition, information such as the school newsletter in the letter service and contact information in the contact service described above is also synchronized between the parent terminals 5A and 5B.

[0100] Next, in step S36, the user registration unit 23 transmits the parent ID, the terminal ID, and the school ID to the parent terminal 5B.

[0101] Next, in step S37, the control unit 41 of the parent terminal 5B stores the parent ID, terminal ID, and school ID transmitted from the server device 2 in the application information storage unit 43. This completes the series of processes.

[0102] Next, an operation for canceling the registration of the parent terminal 5 in the information processing system 1 will be described.

[0103] The operation of deregistering a parent terminal 5 may be performed to deregister the parent terminal 5, for example, when an application for using a support service is uninstalled due to an operation error or the like on a parent terminal 5 included in multiple parent terminals 5 (shared terminals) associated with each other by a common family ID, and then the application is reinstalled and the parent terminal 5 is re-registered in association with another parent terminal 5 that was associated with it before the uninstallation. This is to prevent the upper limit on the number of shared terminals from being exceeded when re-registering the parent terminal 5 on which the application has been reinstalled.

[0104] Furthermore, for example, if a parent terminal 5 included in multiple parent terminals 5 (shared terminals) associated with each other by a common family ID malfunctions, the parent who owns that parent terminal 5 may change to a new parent terminal 5 without following the normal procedure, install an application on it, and register the new parent terminal 5 in association with another parent terminal 5 that was associated with the parent terminal 5 before the change, and the registration of the parent terminal 5 before the change may be cancelled. This is to prevent the upper limit on the number of shared terminals from being exceeded when registering the new parent terminal 5.

[0105] Here, we will explain an example in which the registration of parent terminal 5B, one of parent terminals 5A and 5B that are associated with each other, is canceled. It is assumed that there are no other parent terminals 5 associated with the common family ID to which parent terminals 5A and 5B are associated. It is assumed that parent terminal 5B has uninstalled and reinstalled an application, and is now attempting to re-register it in association with parent terminal 5A.

[0106] The parent who owns the parent terminal 5B reinstalls the application on the parent terminal 5B and then verbally or otherwise requests the parent who owns the parent terminal 5A to cancel the registration of the parent terminal 5B.

[0107] When the parent who owns the parent terminal 5A that has received the request performs a predetermined operation, in step S41 of Fig. 15, the control unit 41 of the parent terminal 5A transmits a shared terminal information request to the server device 2 to acquire shared terminal information corresponding to the home ID with which the parent terminal 5A is associated. The shared terminal information request transmitted by the parent terminal 5A includes the parent ID of the parent who owns the parent terminal 5A.

[0108] Here, the shared terminal information is information indicating another shared terminal that is associated with the parent terminal 5 (parent terminal 5A in this example) that sent the shared terminal information request and the parent terminal 5 (parent terminal 5B in this example) that is a common household ID.

[0109] When the server device 2 receives the shared terminal information request, in step S42, the user registration unit 23 searches for a shared terminal corresponding to the home ID associated with the parent terminal 5A.

[0110] Specifically, based on the parent ID of the parent who owns the parent terminal 5A, the user registration unit 23 refers to the parent table 32 and the terminal table 33 to obtain the nickname of the parent who owns the parent terminal 5B that is associated with the same home ID as the home ID to which the parent terminal 5A is associated, and the terminal information of the parent terminal 5B.

[0111] Next, in step S43, the user registration unit 23 transmits the shared terminal information to the parent terminal 5A. The shared terminal information includes the parent ID of the parent who owns the parent terminal 5B, the nickname of the parent, and the terminal information of the parent terminal 5B.

[0112] When the parent terminal 5A receives the shared terminal information, in step S44, the control unit 41 causes the display unit 45 to display a deregistration screen 60 shown in FIG.

[0113] The deregistration screen 60 displays the nickname of the parent who owns the parent terminal 5B, the terminal information of the parent terminal 5B, and a deregistration button 61 for issuing an instruction to deregister the parent terminal 5B.

[0114] 15, when the deregistration button 61 is pressed, in step S45, the control unit 41 of the parent terminal 5A transmits a deregistration instruction to the server device 2. The deregistration instruction includes the parent ID of the parent who owns the parent terminal 5B.

[0115] When the server device 2 receives the deregistration instruction, in step S46, the user registration unit 23 deregisters the parent terminal 5B. Specifically, the user registration unit 23 changes the deletion flag associated with the parent ID of the parent who owns the parent terminal 5B in the terminal table 33 from "FALSE" to "TRUE."

[0116] Next, in step S47, the user registration unit 23 transmits a deregistration notification to the parent terminal 5A to notify that the deregistration of the parent terminal 5B has been completed, thereby completing the series of processes.

[0117] By canceling the registration of a parent terminal 5 as described above, even if the number of shared terminals including the parent terminal 5 reached the upper limit before the registration was canceled, the number of shared terminals will be less than the upper limit after the registration is canceled.

[0118] Here, it is assumed that the deregistered parent terminal 5 is one in which an application has been uninstalled and then reinstalled, and that the parent terminal 5 is re-registered in association with another parent terminal 5 that was associated with the parent terminal 5 before the uninstallation. In this case, the re-registration is performed by the other parent terminal 5 that was associated with the deregistered parent terminal 5 before the uninstallation inviting the deregistered parent terminal 5.

[0119] The operation of another parent terminal 5 inviting and registering a deregistered parent terminal 5 is the same as the operation described in the flowchart of Fig. 13. In this case, due to the deregistration of the parent terminal 5 on which the application has been reinstalled, the number of shared terminals falls below the upper limit, as described above. Therefore, a shared terminal upper limit error, in which it is determined in step S31 of Fig. 13 that the number of shared terminals has reached the upper limit (step S31: NO), does not occur, and the parent terminal 5 on which the application has been reinstalled is re-registered.

[0120] For example, in the example of the parent terminals 5A and 5B used in the description of the operation of deregistering the parent terminal 5 described above, the parent terminal 5A invites the deregistered parent terminal 5B, thereby re-registering the parent terminal 5B. Specifically, the parent terminal 5B is re-registered in the server device 2 by the operation described in the flowchart of FIG.

[0121] Furthermore, the parent terminal 5 whose registration has been cancelled is the parent terminal 5 before the model change when the model is changed to a new parent terminal 5 without following the normal model change procedure. The new parent terminal 5 after the model change is then registered in association with the other parent terminal 5 that was associated with the parent terminal 5 before the model change. In this case, the other parent terminal 5 that was associated with the parent terminal 5 before the model change invites the parent terminal 5 after the model change, thereby registering the parent terminal 5 after the model change.

[0122] The operation of another parent terminal 5 inviting and registering a parent terminal 5 after changing the model is the same as the operation described in the flowchart of Fig. 13. In this case, too, a shared terminal upper limit error does not occur, and the parent terminal 5 after changing the model is registered.

[0123] Unlike the present embodiment, it is assumed that it is not possible to cancel the registration of a parent terminal 5 registered in the server device 2. In this case, the procedure for re-registering a parent terminal 5 that has had an application uninstalled and then reinstalled, in association with another parent terminal 5 that was associated before the uninstallation, while avoiding a shared terminal upper limit error, is as follows.

[0124] Here, it is assumed that of the parent terminals 5A and 5B associated with each other, parent terminal 5A uninstalls and then reinstalls an application, contrary to the example used in the explanation of the operation of deregistering the parent terminal 5. It is assumed that parent terminals 5A and 5B are associated with each other, but there are no other parent terminals 5 associated with the common household ID.

[0125] First, the parent who owns the parent terminal 5A verbally or otherwise requests the school 7 to cancel the registration of the child associated with the parent terminal 5A.

[0126] The school terminal 3 of the school 7 that has received the request transmits a child deregistration instruction to the server device 2 in response to an operation by a teacher or the like. The child deregistration instruction includes the child ID of the child whose registration has been requested to be deregistered.

[0127] The user registration unit 23 of the server device 2 that has received the child deregistration instruction cancels the registration of the child specified by the child deregistration instruction. Specifically, the user registration unit 23 deletes from the class table 35 the child ID of the child specified by the child deregistration instruction, the class ID associated with the child ID, the child's nickname, and the attendance number.

[0128] After this, the parent terminal 5A is registered through the same operations as those described in the flowchart of Figure 9. The parent ID, home ID, and terminal ID issued at this time are different from those issued when the parent terminal 5A was registered before the application was uninstalled. As a result, the parent terminal 5A is registered as a new parent terminal 5.

[0129] Next, the parent terminal 5A invites the parent terminal 5B, whereby the parent terminal 5B is registered in association with the parent terminal 5A.

[0130] At this time, the parent terminal 5B uninstalls and then reinstalls the application in response to an operation by the parent who owns the parent terminal 5B.

[0131] After this, by the operation described in the flowchart of Fig. 13 above, the parent terminal 5B is associated with the parent terminal 5A and registered in the server device 2. The parent ID and terminal ID issued at this time are different from those issued when the parent terminal 5B was registered before the application was uninstalled. As a result, the parent terminal 5B is registered as a new parent terminal 5. At this time, since there is no other parent terminal 5 registered in association with the parent terminal 5A, a shared terminal upper limit error does not occur.

[0132] In this way, by re-registering the parent terminals 5A and 5B as new parent terminals 5, it is possible to avoid a shared terminal upper limit error and re-register the parent terminal 5A in association with the parent terminal 5B that was associated with it before the uninstallation.

[0133] In this case, however, the parent / guardian terminal 5A must start over by scanning the class QR code in the registration guide, and the parent / guardian terminal 5B must uninstall and reinstall the application, which requires a lot of work for the parent / guardian (user) who owns each of the parent / guardian terminals 5A and 5B.

[0134] In contrast to this, in this embodiment, as described above, the registration of a parent terminal 5 that has uninstalled and then reinstalled an application is cancelled. This allows another parent terminal 5 to invite the parent terminal 5 whose registration has been cancelled and register it while avoiding a shared terminal upper limit error, thereby reducing the effort required of the parent (user).

[0135] Unlike this embodiment, in the case where it is not possible to cancel the registration of a parent terminal 5 registered on the server device 2, the procedure for registering a parent terminal 5 after a model change that has been performed without following the normal procedure, in association with other parent terminals 5 with which the parent terminal 5 before the model change was associated, while avoiding a shared terminal limit error, is the same as the procedure for re-registering a parent terminal 5 after an application has been uninstalled and then reinstalled, in association with other parent terminals 5 with which it was associated before the uninstallation, as described above.

[0136] As described above, in the information processing system 1, the user registration unit 23 of the server device 2 can cancel the registration of each registered parent / guardian terminal 5. This makes it possible to re-register a parent / guardian terminal 5 that has uninstalled and then reinstalled an application in association with another parent / guardian terminal 5 that was associated with the parent / guardian terminal 5 before the uninstallation, while reducing the amount of work required by the parent (user). Similarly, it makes it possible to re-register a parent / guardian terminal 5 that has been changed without following the correct procedure in association with another parent / guardian terminal 5 that was associated with the parent / guardian terminal 5 before the change, while reducing the amount of work required by the parent / guardian. Therefore, it is possible to reduce registration errors for parent / guardian terminals 5, while reducing the amount of work required by the parent / guardian.

[0137] Furthermore, the user registration unit 23 of the server device 2 cancels the registration of other parent / guardian terminals 5 in response to an instruction from the parent / guardian terminal 5. For example, in the example used in the explanation of the operation of canceling the registration of a parent / guardian terminal 5 described above, the user registration unit 23 cancels the registration of parent / guardian terminal 5B in response to an instruction to cancel the registration from parent / guardian terminal 5A. This makes it possible to easily cancel the registration of a parent / guardian terminal 5 in response to an instruction from another parent / guardian terminal 5 synchronized with the parent / guardian terminal 5.

[0138] It is also possible for the user registration unit 23 to be able to delete the registration of the parent / guardian terminal 5 in response to an instruction from a device other than the parent / guardian terminal 5, such as the school terminal 3.

[0139] In the example used to explain the operation of canceling the registration of a parent terminal 5 described above, the registration of one parent terminal 5B was canceled. However, for example, when three or more parent terminals 5 are associated with each other, it is also possible to cancel the registration of multiple other parent terminals 5 by issuing a cancellation instruction from one parent terminal 5.

[0140] In the above-described embodiment, an example has been described in which multiple parent terminals 5 (terminal devices) owned by a child's family are associated with each other and with the child, and information related to the child is synchronized. However, the multiple terminal devices that are associated with each other are not limited to those owned by the family. Furthermore, the objects that the terminal devices are associated with are not limited to children, and the information related to the objects that are synchronized among the multiple terminal devices is not limited to information related to children.

[0141] 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.

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

[0143] (Appendix 1) a registration unit that registers a plurality of terminal devices, the number of which is equal to or less than a predetermined upper limit, in association with each other; The information processing device, wherein the registration unit is capable of deregistering each of the terminal devices.

[0144] (Appendix 2) The registration unit registering the 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; 2. The information processing device according to claim 1, wherein the information processing device cancels the registration of another of the terminal devices in response to an instruction from the terminal device.

[0145] (Appendix 3) 1. A computer-implemented information processing method, comprising: 1. An information processing apparatus comprising: a step of canceling registration of at least one of a plurality of terminal devices registered in association with each other, the number of which is equal to or less than a predetermined upper limit.

[0146] (Appendix 4) A program causing a computer to execute a step of deregistering at least one of a plurality of terminal devices that are associated with each other and registered, the number of which is equal to or less than a predetermined upper limit. [Explanation of symbols]

[0147] 1. Information Processing Systems 2. Server device 3. School terminals 4 Printing device 5. Parental Device 11 Control section 12 Database Department 13 Program memory section 14 External Communications Department 21 Class Code Issuance Department 22 Invitation Code Issuance Department 23 User Registration Section 31 School Table 32 Parent Table 33 Terminal Table 34 Children's Table 35 Class 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 Class QR Code Column 52 Class QR Code 53 Attendance number entry field 56 Parent information screen 57 Child Information Screen 58 Invitation QR code screen 59 Invitation QR Code 60 Unsubscription screen 61 Unsubscribe button

Claims

1. a registration unit that registers a plurality of terminal devices, the number of which is equal to or less than a predetermined upper limit, in association with each other; The information processing device, wherein the registration unit is capable of deregistering each of the terminal devices.

2. The registration unit registering the 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; 2. The information processing apparatus according to claim 1, wherein the information processing apparatus cancels the registration of another of the terminal devices in response to an instruction from the terminal device.

3. 1. A computer-implemented information processing method, comprising:

1. An information processing apparatus comprising: a step of canceling registration of at least one of a plurality of terminal devices registered in association with each other, the number of which is equal to or less than a predetermined upper limit.

4. A program causing a computer to execute a step of deregistering at least one of a plurality of terminal devices that are associated with each other and registered, the number of which is equal to or less than a predetermined upper limit.

Images