JP7292318B2 - REGISTRATION DEVICE, REGISTRATION METHOD, AND PROGRAM - Google Patents

Description

The present invention relates to a registration device, a registration method, and a program.

As a system for registering a user, there is a system that scans an image of a code such as a QR code (registered trademark) with a mobile terminal, transmits the information contained in the code from the mobile terminal to a server, and registers the user ( See Patent Document 1).

Japanese Patent Publication No. 2017-503253

As a system for registering users as described above, there is a system that can register terminal devices of other users in association with terminal devices of registered users. In such a system, it is required to eliminate the registration of unauthorized terminal devices that should not be registered in association with registered terminal devices.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a registration device, a registration method, and a program capable of excluding registration of unauthorized terminal devices.

According to one aspect of the present invention, information included in the registration code is obtained from a registration code issuing unit that issues a registration code for user registration, a storage unit, and a terminal device that has acquired the registration code. , and acquires user identification information input to the terminal device, associates information indicating the terminal device, information included in the registration code, and the identification information, and stores the information in the storage unit. a registration unit that registers a device; and an invitation code issuing unit that transmits an invitation code to the registered terminal device in response to a request from the registered terminal device, wherein the registration unit is the registered terminal device. When the invitation code is input from another terminal device that has acquired the invitation code via the device and is different from the registered terminal device, the information indicating the other terminal device is sent to the registration The other terminal device is registered by being stored in the storage unit in association with the information contained in the code and the identification information input at the time of registration of the registered terminal device, and is different from the registered terminal device. When the information included in the registration code and the identification information indicating the same user as the identification information input at the time of registration of the registered terminal device are obtained from another terminal device, the other terminal device There is provided a registration device characterized by providing an error notification to the

According to another aspect of the present invention, the registration code is included in the registration code from a registration code issuing unit that issues a registration code for user registration, a storage unit, and a terminal device that acquires the registration code. information and the identification information of the user input to the terminal device, and associate the information indicating the terminal device with the information included in the registration code and the identification information, and store the information in the storage unit. a registration unit for registering a terminal device, wherein the registration unit inputs information included in the registration code and information included in the registration code from another terminal device different from the registered terminal device at the time of registration of the registered terminal device. when the identification information indicating the same user as the identification information obtained is acquired, the other terminal device is caused to apply for registration to the registered terminal device, and the registered terminal device registers the other terminal device is permitted, the information indicating the other terminal device, the information included in the registration code, and the identification information are associated with each other and stored in the storage unit to register the other terminal device. A registration device is provided.

According to another aspect of the present invention, a step of issuing a registration code for user registration; a step of registering the terminal device by acquiring the identification information of the user that has been received, and storing the information indicating the terminal device, the information included in the registration code, and the identification information in association with each other in a storage unit; a step of transmitting an invitation code to the registered terminal device in response to a request from the already registered terminal device; and the registered terminal device acquiring the invitation code via the registered terminal device. When the invitation code is input from a different terminal device, the information indicating the other terminal device is included in the information included in the registration code and the identification input at the time of registration of the registered terminal device. a step of registering the other terminal device by associating it with information and storing it in the storage unit; When identification information indicating the same user as the identification information input at the time of registration of a terminal device that has already been registered is acquired, an error notification is provided to the other terminal device. be done.

According to another aspect of the present invention, a step of issuing a registration code for user registration; a step of registering the terminal device by acquiring the identification information of the user that has been received, and storing the information indicating the terminal device, the information included in the registration code, and the identification information in association with each other in a storage unit; When the information included in the registration code and the identification information indicating the same user as the identification information input at the time of registration of the registered terminal device are acquired from another terminal device different from the registered terminal device , when the other terminal device is caused to apply for registration to the registered terminal device, and the registered terminal device permits the registration of the other terminal device, the information indicating the other terminal device and the registration and a step of registering the other terminal device by associating information included in a code with the identification information and storing them in the storage unit.

According to another aspect of the present invention, the step of issuing a registration code for user registration to a computer, and the information included in the registration code and the terminal from the terminal device that acquired the registration code, A step of acquiring identification information of a user input to a device, and registering the terminal device by associating information indicating the terminal device, information included in the registration code, and the identification information and storing them in a storage unit. a step of transmitting an invitation code to the registered terminal device in response to a request from the registered terminal device; and the registered terminal device that has acquired the invitation code via the registered terminal device. When the invitation code is input from another terminal device different from the device, information indicating the other terminal device is included in the registration code and entered at the time of registration of the registered terminal device. a step of registering the other terminal device by storing it in the storage unit in association with the identification information, and information included in the registration code from another terminal device different from the registered terminal device; and if identification information indicating the same user as the identification information input at the time of registration of the registered terminal device is acquired, a step of notifying the other terminal device of an error is provided. be done.

According to another aspect of the present invention, the step of issuing a registration code for user registration to a computer, and the information included in the registration code and the terminal from the terminal device that acquired the registration code, A step of acquiring identification information of a user input to a device, and registering the terminal device by associating information indicating the terminal device, information included in the registration code, and the identification information and storing them in a storage unit. Then, from another terminal device different from the registered terminal device, the information included in the registration code and the identification information indicating the same user as the identification information input at the time of registration of the registered terminal device are obtained. in the case where said other terminal device applies for registration to said registered terminal device, and said registered terminal device permits registration of said other terminal device, information indicating said other terminal device; A program is provided for executing a step of registering the other terminal device by associating the information included in the registration code with the identification information and storing them in the storage unit.

According to the present invention, it is possible to eliminate the registration of unauthorized terminal devices.

1 is an explanatory diagram of an outline of a business model realized in an embodiment; FIG. 1 is a block diagram showing the configuration of a point management system according to a first embodiment; FIG. 3 is a block diagram showing the configuration of a server device of the point management system shown in FIG. 2; FIG. It is a figure which shows an advertisement management table. It is a figure which shows an area management table. It is a figure which shows a school management table. FIG. 10 is a diagram showing a class management table; FIG. FIG. 10 is a diagram showing a child management table; FIG. It is a figure which shows a guardian management table. It is a figure which shows an invitation code management table. It is a figure which shows a point management table. It is a figure which shows an article table. 3 is a block diagram showing the configuration of a guardian terminal of the point management system shown in FIG. 2; FIG. FIG. 10 is a sequence diagram for explaining operations at the time of user registration in the point management system of the first embodiment; It is a figure which shows the class QR code column of a registration guide. It is a figure which shows a guardian information screen. It is a figure which shows a child information screen. It is a figure which shows a group setting screen. It is a figure which shows a registration confirmation screen. It is a figure which shows an error screen. FIG. 7 is a sequence diagram for explaining the operation at the time of additional registration of the guardian terminal in the point management system of the first embodiment; It is a figure which shows the QR code screen for an invitation. It is a figure which shows a registration confirmation screen. FIG. 10 is a diagram showing a home screen of an application; FIG. It is a figure which shows an advertisement list screen. FIG. 4 is a sequence diagram for explaining the operation of browsing an advertiser's site in the point management system of the first embodiment; It is a figure which shows the screen which displayed the acquisition point number. It is a figure which shows a point use page. FIG. 4 is a sequence diagram for explaining the operation when points are exchanged for goods in the point management system of the first embodiment; It is a figure which shows a notification list screen. It is a figure which shows a health observation screen. It is a figure which shows an absence/tardy contact screen. It is a figure which shows an individual contact screen. FIG. 11 is a sequence diagram for explaining operations at the time of user registration in the point management system of the second embodiment; FIG. 11 is a sequence diagram for explaining operations at the time of user registration in the point management system of the second embodiment; It is a figure which shows a registered terminal display screen. It is a figure which shows a registration permission screen. It is a figure which shows a registration refusal notification screen.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described with reference to the drawings. In addition, the same or equivalent reference numerals are given to the same or equivalent parts and components throughout each drawing, and the description thereof will be omitted or simplified.

[Overview of business model]
An outline of a business model implemented in an embodiment of the present invention will be described with reference to FIG.

A service provider 1 shown in FIG. 1 is a group or organization that provides services. The service provided by the service provider 1 is a public service in real space, not a service on the Internet. For example, the service provider 1 is a school that provides educational services, a hospital that provides medical services, and the like. The service provider 1 is not limited to public schools, and may be private schools, hospitals, and the like.

The service user 2 is a service user who uses the service provided by the service provider 1 or a related person. Service users are children and students in schools, patients in hospitals, and the like. A related person of the service user is a family member of the service user or the like.

The operation manager 3 is a business operator who operates and manages the entire activity based on this business model. Specifically, the operation manager 3 grants points that can be exchanged for goods to the service provider 1, processes for exchanging points for goods, examines advertisements of advertisers 5 described later, and manages advertising fees. etc.

The sponsor company 4 is a company that delivers to the service provider 1 goods (sponsored goods) that can be exchanged for points. The sponsor company 4 is a company that agrees with the idea of supporting the financial resources of the service provider 1 through this business model.

The advertiser 5 is a company that publishes advertisements in applications used in terminal devices such as smartphones of the service user side 2 . The advertiser 5 pays the advertising fee to the operation manager 3. The advertisement fee is used for the price of the goods of the sponsor company 4 that are exchanged for points.

As shown in FIG. 1, in this business model, an advertisement of an advertiser 5 is posted in an application used in the terminal device of the service user 2 (step S1).

The service user side 2 accesses the advertiser site such as the home page of the advertiser 5 from the advertisement posted in the application and browses the advertiser site (step S2). As a result, the operation manager 3 provides the service provider 1 with points that can be exchanged for goods (step S3).

In order to exchange the points for goods, the service provider 1 requests the operation manager 3 to exchange the points for desired goods (step S4). Upon receiving this request, the operations manager 3 orders the requested goods from the sponsoring company 4 (step S5). Also, the operation manager 3 pays the sponsor company 4 for the goods. The sponsor company 4 delivers the goods to the service provider 1 (step S6).

As described above, according to this business model, when the advertiser's site is viewed on the terminal device of the service user 2, the service provider 1 is given points that can be exchanged for goods. As a result, points can be given to the service provider 1, which is various organizations that provide services, based on the behavior of the service user 2. FIG. By exchanging the points for goods, the financial resources of the service provider 1 can be supported.

[First embodiment]
Next, a first embodiment that implements the business model described above will be described. In the first embodiment, the service provider 1 in FIG. 1 is a school that is an organization that provides educational services.

As shown in FIG. 2, the point management system 11 according to the first embodiment includes a server device (corresponding to a registration device) 12, an operation manager terminal 13, a school terminal 14, a printing device 15, and a guardian terminal. 16. An administrator terminal 13, a school terminal 14, and a guardian terminal (corresponding to a terminal device) 16 can be connected to the server device 12 via a network 17 such as the Internet.

Here, the school terminal 14 and the printing device 15 are provided at the school 200 . The school 200 provided with the school terminal 14 and the printing device 15 may be one or plural. Further, the number of school terminals 14 provided in one school 200 may be one or plural. The school 200 is an elementary school, junior high school, or the like, and may be public or private.

The parent terminal 16 is a terminal device such as a smart phone or a tablet terminal owned by a parent (parent) of a child or student who attends the school 200 . One guardian terminal 16 may be provided for one commuting student, or a plurality of such terminals may be provided. A child or a student who attends school 200 is simply referred to as a "child". A child is a person who uses the educational service provided by the school 200, corresponds to the service user described above, and is included in the service user side 2 in FIG. A child's guardian (parent) corresponds to a person related to the service user and is included in the service user side 2 .

The server device 12 is a server that provides support services including a point giving service in which the operation manager 3 gives the school 200 points that can be exchanged for goods. The support service includes, in addition to the point-giving service, a letter service for distributing and delivering school news, and a communication service for making various contacts between the school and the child's home. The school 200 can contract and use only some of the above three services included in the support service.

In this embodiment, three services included in the support service are described as being managed by one operation manager 3, but some of the three services are managed by another operation manager 3. can be anything. Also, the three services may be managed by different operation managers 3 respectively.

The server device 12 is configured by a computer including a CPU, ROM, RAM, hard disk, and the like. Note that the server device 12 may be a cloud server provided on the cloud.

As shown in FIG. 3 , the server device 12 includes a control section 21 , a database section (corresponding to a storage section) 22 , a program storage section 23 and an external communication section 24 .

The control unit 21 controls the operation of the server device 12 as a whole. The control unit 21 is configured including a CPU and the like. The control unit 21 includes a user management unit 31 , an advertisement management unit 32 , a point management unit 33 , a school news management unit 34 and a contact information management unit 35 . Each unit of the control unit 21 is configured by executing a program stored in the program storage unit 23 by the CPU.

The user management unit 31 performs processing for user registration of the support service described above. The user management unit 31 includes a class code issuing unit (corresponding to a registration code issuing unit) 41 , an invitation code issuing unit 42 , and a user registration unit (corresponding to a registering unit) 43 . Each part of the user management part 31 is configured by executing a registered program stored in the program storage part 23 by the CPU.

Upon receiving the class code issuing instruction from the school 200, the class code issuing unit 41 issues the class code (corresponding to the registration code) of the class at the school 200 instructed in the class code issuing instruction. Also, the class code issuing unit 41 issues (generates) a class QR code in which the class code is embedded. A class code is a code containing a class ID. A class ID is information for uniquely identifying each class in the school 200 .

The invitation code issuing unit 42 issues an invitation code upon receiving an invitation code issuing instruction from the guardian terminal 16 . In addition, the invitation code issuing unit 42 issues (generates) an invitation QR code in which the invitation code is embedded. The invitation code is a code used to associate another parent's terminal 16 with the registered parent's terminal 16 via the parent's terminal 16 registered in the server 12 and register it in the server 12. .

The user registration unit 43 performs processing for user registration. Specifically, the user registration unit 43 issues a parent ID and a terminal ID upon receiving terminal transmission information (to be described later) transmitted from the parent terminal 16 that acquired the class code. Then, the user registration unit 43 associates the parent ID, the terminal ID, the class ID included in the terminal transmission information, and the child ID (corresponding to user identification information) included in the terminal transmission information, which will be described later. It is stored in the guardian management table 56. Information such as guardian nicknames is also stored in the guardian management table 56, as will be described later.

Here, the guardian ID is information for uniquely identifying each guardian. A terminal ID is information for uniquely identifying each parent terminal 16 .

Also, in this embodiment, the child ID is the attendance number in the class to which the child belongs. The attendance number is entered at the parent terminal 16 that has acquired the class code, as will be described later.

In addition, the user registration unit 43 acquires the same class ID and child ID as the class ID and child ID associated with one of the parent terminals 16 (guardian ID) registered in the server device 12 from the terminal transmission information. In this case, an error notification is transmitted to the guardian terminal 16 which is the transmission source of the terminal transmission information.

In addition, the user registration unit 43 acquires the invitation code via the registered guardian terminal 16, and when the invitation code is input from another guardian terminal 16 different from the registered guardian terminal 16 , the terminal ID of the other parent terminal 16 is associated with the same child ID and class ID as the child ID and class ID associated with the terminal ID of the registered parent terminal 16, and stored in the parent management table 56. Memorize.

Specifically, when the user registration unit 43 receives a registration instruction (described later) after receiving invited terminal transmission information (described later) including an invitation code from the guardian terminal 16 that has been invited, the user registration unit 43 registers the guardian ID and the terminal ID. to be issued. Then, the user registration unit 43 adds the same child ID and class ID as the child ID and class ID associated with the terminal ID of the registered parent terminal 16 that has received the issuance of the invitation code from the server device 12, The parent ID and terminal ID of the parent terminal 16 that sent the invitation terminal transmission information are associated with each other and stored in the parent management table 56 . Information such as guardian nicknames is also stored in the guardian management table 56, as will be described later.

As a result, the registered parent terminal 16 and the parent terminal 16 that has acquired (invited) the invitation code from the registered parent terminal 16 are associated by the common child ID and class ID. Registered in the server device 12 . This also synchronizes the child ID and class ID between the registered parent terminal 16 and the invited parent terminal 16 . Information such as the child's nickname is also synchronized, as will be described later.

The advertisement management unit 32 manages the advertisements of the advertiser 5 posted in the dedicated application used on the parent's terminal 16 . Specifically, the advertisement management unit 32 performs distribution of advertisement image data to the parent's terminal 16, and the like.

The point management unit 33 performs processing such as giving points to the school 200 in the point giving service. The point management unit 33 includes a point granting unit 46 and a point exchange unit 47 .

The point granting unit 46 grants points generated when the parent terminal 16 browses the advertiser site to the school 200 attended by the child associated with the parent terminal 16 . Then, the point granting unit 46 associates the granted points with the school ID of the school 200 and stores them in the school management table 53 of the database unit 22, which will be described later.

When the point exchange unit 47 receives a point exchange request for exchanging points for desired goods from the school 200, it performs point exchange processing and ordering processing. The point exchange process is a process of subtracting the points corresponding to the requested goods from the number of points held by the school 200 in the school management table 53 . The ordering process is a process of ordering goods from the sponsor company 4 .

The school news management unit 34 manages school news distributed and distributed in the letter service. Specifically, the school news management unit 34 performs processing for storing school news data, which is image data of school news, in a school news table 60 to be described later, processing for transmitting the school news data to the parent terminal 16, and the like.

The contact information management unit 35 performs processing such as storing contact information in the contact service in a contact information table 61 to be described later.

The database unit 22 includes an advertisement management table 51, a region management table 52, a school management table 53, a class management table 54, a child management table 55, a guardian management table 56, an invitation code management table 57, A point management table 58, an article table 59, a school news table 60, and a contact information table 61 are stored. The database unit 22 is composed of a hard disk or the like.

The advertisement management table 51, as shown in FIG. 4, is a table that associates advertisement IDs, advertisement image data, company IDs, delivery regions, delivery periods, advertiser site information, unit prices per click, and advertisement point information.

The advertisement ID is information for uniquely identifying each advertisement registered in the server device 12 . One advertiser 5 may register multiple types of advertisements.

The advertisement image data is image data of an advertisement image. The advertisement image data includes advertisement image data to be displayed in a banner advertisement area 102 (see FIG. 24) described later, and advertisement image data to be displayed in an advertisement area 104 (see FIG. 25) in an advertisement list screen 103 described later. and are included.

The company ID is information for uniquely identifying the company of the advertiser 5 . The distribution area indicates the area where each advertisement is distributed. The delivery period indicates the delivery period of each advertisement. The advertiser's site information is the URL of an external advertiser's site, such as the home page of the advertiser's 5 company.

The cost per click is the number of points generated by viewing each advertiser's site once. The advertisement point information is information indicating the total number of points generated by viewing each advertisement.

The URL stored in the advertisement management table 51 as the advertiser site information may be the URL of the leaflet image. Furthermore, flyer images may be stored in the server device 12 .

The area management table 52, as shown in FIG. 5, is a table that associates an area with the school ID of each school 200 located in each area.

The school management table 53, as shown in FIG. 6, is a table that associates school IDs, school names, and the number of points possessed.

The class management table 54, as shown in FIG. 7, is a table that associates class IDs, class names, number of children, and school IDs. The number of children is the number of children in each class. A plurality of children belong to each class.

The child management table 55, as shown in FIG. 8, is a table that associates child IDs, child nicknames, class IDs, and distribution groups.

The child's nickname is entered in the parent's terminal 16 when the parent's terminal 16 is registered in the server device 12 . A child's nickname is different from the child's full name. The child's nickname is used, for example, to display the child in the application used on the parent's terminal 16 .

A distribution group is a group that can be selected as a distribution target of school news in the letter service. A distribution group is, for example, a club at a school. The distribution group is selected and input on the parent terminal 16 when the parent terminal 16 is registered in the server device 12 .

As shown in FIG. 9, the guardian management table 56 associates guardian IDs, guardian nicknames, guardian ages, relationships with children, terminal IDs, terminal names, child IDs, class IDs, and invitation codes. It is a table. As for the invitation code, only the code for the guardian terminal 16 to which the invitation code was issued is stored in the guardian management table 56 . The parent's nickname, parent's age, and relationship with the child are entered in the parent's terminal 16 when registering the parent's terminal 16 with the server device 12 . A guardian's nickname is different from the guardian's full name. The parent's nickname is used to display the parent in the application used on the parent's terminal 16, and the like.

The invitation code management table 57, as shown in FIG. 10, is a table that associates invitation codes with guardian IDs.

The point management table 58 is a table in which browsing histories of advertiser sites by the parent terminal 16 are registered. As shown in FIG. 11, the point management table 58 includes the browsing date and time when the advertiser site was browsed by the parent terminal 16, the advertiser site information of the advertiser site, the parent who browsed the advertiser site. The terminal ID of the terminal 16, the child ID associated with the terminal ID, the school ID of the school 200 attended by the child with the child ID, the number of times the parent terminal 16 viewed the advertiser site, and the parent terminal 16 This is a table that associates the number of points acquired by viewing the advertiser site.

The article table 59, as shown in FIG. 12, is a table that associates article names, article image data, and required points.

The item name is the name of an item that can be exchanged for points in the point granting service. The product image data is image data of a photograph of each product. The required number of points is the number of points required to exchange each item for points. The required number of points for each item is set in advance according to the price of each item.

The school news table 60 is a table that stores school news data in the letter service in association with distribution target information indicating distribution targets (classes, groups, etc.) and read information. The already read information is information indicating whether or not the school news has been viewed (unread or already read) on each guardian terminal 16 to be distributed.

The contact information table 61 is a table that stores contact information in the contact service in association with the child ID. The contact information includes health observation information, attendance confirmation information, individual contact information, and reply information to individual contact.

The health observation information is health-related information such as body temperature and health condition of the child, which is communicated from parents to the school 200 . The attendance confirmation information is information related to the child's absence, arriving late, leaving early, etc., which is sent from the guardian to the school 200 . The individual contact information is information for individual contact from the school 200 to the guardian. The individual contact information is, for example, information for notifying a schedule change of an individual interview. Reply information to the individual contact is information that the guardian replies to the individual contact information from the school 200 .

The program storage unit 23 stores various programs executed by the CPU of the server device 12 . The program storage unit 23 is configured by a hard disk or the like.

The external communication unit 24 performs communication processing with an external device via the network 17 .

The operation manager terminal 13 is a terminal device for the operation manager 3 to perform operations related to the support service. The operation manager terminal 13 is configured by a computer having a display section including a CPU, a ROM, a RAM, a hard disk, a liquid crystal display panel, etc., and an input section having a keyboard, a mouse, and the like. A browser for accessing the server device 12 is installed in the operation manager terminal 13 .

The school terminal 14 is a terminal device for the teacher of the school 200 to perform operations related to the support service. The school terminal 14 is composed of a computer similar to the operation manager terminal 13 . A browser for accessing the server device 12 is installed in the school terminal 14 .

The printing device 15 prints a registration guide, etc., which will be described later.

The parent's terminal 16 is a terminal device for the child's parent to perform operations related to the support service. The guardian terminal 16 is composed of a smart phone, a tablet terminal, or the like, as described above.

As shown in FIG. 13, the parent terminal 16 includes a control unit 71, a program storage unit 72, an application information storage unit 73, an imaging unit 74, a display unit 75, an input unit 76, and an external communication unit 77. and

The control unit 71 controls the operation of the guardian terminal 16 as a whole. The control unit 71 is configured including a CPU and the like. The control unit 71 includes a code acquisition unit 81 , a display control unit 82 , an advertisement processing unit 83 , a point processing unit 84 , a school news processing unit 85 and a contact information processing unit 86 . Each unit of the control unit 71 is configured by executing a dedicated application program stored in the program storage unit 72 by the CPU for using the support service.

When the imaging unit 74 is imaging the class QR code, the code acquisition unit 81 acquires the class QR code, analyzes it to acquire the class code, and acquires the class ID from the class code. Further, when the imaging unit 74 captures an image of the invitation QR code, the code acquisition unit 81 acquires the invitation QR code, analyzes it, and acquires the invitation code.

The display control unit 82 controls to display various screens on the display unit 75 .

The advertisement processing unit 83 performs processing such as transmitting an advertiser site information request for requesting advertiser site information to the server device 12 in order to browse the advertiser site.

The point processing unit 84 performs a process of updating the terminal point information in the application information storage unit 73 when the school 200 acquires points by viewing the advertiser site on the parent's terminal 16 .

The school news processing unit 85 performs processing such as transmitting a school news acquisition request for acquiring school news data to the server device 12 .

The contact information processing unit 86 performs processing such as transmitting health observation information, attendance confirmation information, and reply information to individual contact to the server device 12 .

The program storage unit 72 stores various programs such as application programs for using support services. The program storage unit 72 is composed of a flash memory or the like. An application program for using the support service can be obtained from any app store server via the network 17, for example.

The application information storage unit 73 stores the terminal ID of the parent's terminal 16, the child ID of the child associated with the parent's terminal 16, the school ID of the school 200 the child attends, terminal point information, notification list information, and the like. do. The terminal point information is information indicating the acquisition history of points by browsing the advertiser's site on the parent's terminal 16 . Notification list information is information indicating a list of push notifications from the server device 12 . The notification list information includes, for example, the document name of the school news sent together with each push notification received by the parent terminal 16 .

The imaging unit 74 is a camera that images a subject. The imaging unit 74 is used by the guardian terminal 16 to read the class QR code and the invitation QR code.

The display unit 75 displays various screens. The display unit 75 is configured by a liquid crystal display panel or the like.

The input unit 76 receives various input operations by the operator of the guardian terminal 16 . Input unit 76 includes a touch panel (not shown). The touch panel is arranged over the display unit 75 . A touch panel detects a contact operation by an operator.

The external communication unit 77 performs communication processing with an external device via the network 17 .

Next, the operation at the time of user registration in the point management system 11 will be described.

First, at step S11 in FIG. Specifically, when a class for which a class code is to be issued is input and an operation requesting the issuance of a class code is performed, the school terminal 14 transmits a class code issuance instruction to the server device 12 . The class code issuance instruction includes the class name, the number of students in the class, and the school ID of the school 200 that sent the class code issuance instruction.

When the server device 12 receives the class code issuing instruction, the class code issuing unit 41 issues a class code including the class ID in step S12. A class code consists of, for example, a string of numbers. The score issuing unit 431 causes the class management table 54 to store the class ID, class name, number of students in the class, and school ID of the issued class code in association with each other.

Next, in step S13, the class code issuing unit 41 generates a class QR code in which the class code is embedded.

Next, in step S14, the class code issuing unit 41 transmits the image data of the registration guidebook including the class QR code to the school terminal 14 that sent the class code issuing instruction.

Next, in step S15, the school terminal 14 instructs the printing device 15 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.

The registration guide includes a class QR code field 87 shown in FIG. A class QR code 88 is posted in the class QR code column 87 . Also, the class QR code field 87 is provided with an attendance number entry field 89 . In the attendance number entry column 89, the attendance number of each child in the class is entered by handwriting. Further, the class QR code field 87 describes the school name, class name, expiration date of the preset class QR code, and class code.

Returning to FIG. 14, in step S16, the school 200 distributes a registration guide to each child's home. For example, school 200 allows each child to take home an enrollment guide.

Next, in step S17, the guardian terminal 16 reads the class QR code 88 in the class QR code column 87.

Specifically, the code acquisition unit 81 acquires the class QR code 88 in the image captured by the imaging unit 74 displayed on the class QR code reading screen (not shown).

Next, in step S<b>18 , the code acquisition unit 81 analyzes the class QR code 88 and acquires the class code embedded in the class QR code 88 . Then, the code acquisition unit 81 acquires the class ID from the class code. Code acquisition portion 81 causes application information storage portion 73 to store the acquired class ID.

Instead of acquiring the class code by reading the class QR code 88 printed on the registration guide, the URL for registration is sent from the server device 12 to the guardian terminal 16 by e-mail or the like, and the registration A class code may be obtained from a URL.

Next, in step S19, the guardian terminal 16 accepts input of guardian information. Specifically, the display control unit 82 causes the display unit 75 to display a guardian information screen 91 shown in FIG. The guardian who owns the guardian terminal 16 performs an operation of inputting the guardian information on the guardian information screen 91 . Guardian information includes guardian's age, relationship with the child, and guardian's nickname. Code acquisition portion 81 causes application information storage portion 73 to store the input guardian information.

When the guardian information is input, the guardian terminal 16 receives the input of the child information in step S20. Specifically, the display control unit 82 first causes the display unit 75 to display the child information screen 92 shown in FIG. The parent who owns the parent terminal 16 performs an operation of inputting the child's class attendance number and the child's nickname on the child information screen 92 . The child information screen 92 displays the grade and class of the child. The grade and class are determined from the class ID.

When the information input to the child information screen 92 is completed, the group setting screen 93 shown in FIG. An operation is performed on the group setting screen 93 to select a distribution group for school news in the letter service. This completes the input of the child information. The child information includes the child's class attendance number, the child's nickname, and the distribution group. Code acquisition portion 81 stores the input child information in application information storage portion 73 .

After that, a registration confirmation screen 94 shown in FIG. 19 is displayed on the display section 75 . The registration confirmation screen 94 is provided with a completion button 95 for completing user registration.

When the completion button 95 is pressed, the code acquisition unit 81 transmits the terminal transmission information to the server device 12 in step S21 of FIG. The terminal transmission information includes class ID, child ID (attendance number), terminal name of parent terminal 16, parent's age, parent's relationship with child, parent's nickname, child's nickname, and delivery group. included. Here, as the terminal name of the guardian terminal 16, information such as the model name held by the guardian terminal 16 can be used.

When the server device 12 receives the terminal transmission information through the external communication unit 24, the child ID included in the terminal transmission information is obtained. Then, in step S22, the user registration unit 43 determines whether or not there is a registered guardian terminal 16 corresponding to the child indicated by the child ID included in the terminal transmission information. Specifically, the user registration unit 43 refers to the parent management table 56 and refers to the parent terminal 16 (parent/guardian ID) is registered.

When the parent terminal 16 (parent ID) associated with the same class ID and child ID as the class ID and child ID included in the terminal transmission information is registered, the user registration unit 43 It is determined that there is a registered guardian terminal 16 corresponding to the child indicated by the child ID. In other words, the user registration unit 43 registers the same class ID and child ID as the class ID and child ID associated with one of the parent terminals 16 (guardian ID) registered in the server device 12 according to the terminal transmission information. If acquired, it is determined that there is a registered guardian terminal 16 corresponding to the child indicated by the child ID included in the terminal transmission information.

If it is determined that there is a registered parent's terminal 16 (step S22: YES), in step S23, the user registration unit 43 transmits an error notification to the parent's terminal 16 that sent the terminal transmission information.

When the guardian terminal 16 receives the error notification, the display control section 82 causes the display section 75 to display an error screen 96 shown in FIG. 20 in step S24. This completes a series of processes. As shown in FIG. 20, the error screen 96 displays a message notifying of a regular procedure for obtaining an invitation code from the registered guardian terminal 16 and registering it.

Returning to FIG. 14, when it is determined in step S22 that there is no registered parental terminal 16 (step S22: NO), in step S25, the user registration unit 43 registers the parental terminal 16 of the transmission source of the terminal transmission information. Issue parent ID and terminal ID for

Next, in step S26, the user registration unit 43 registers the guardian ID, terminal ID, and information included in the terminal transmission information in the child management table 55 and the guardian management table 56. FIG. Specifically, the user registration unit 43 stores the child ID, the child's nickname, the class ID, and the distribution group in association with each other in the child management table 55 . In addition, the user registration unit 43 associates the guardian ID, guardian's nickname, guardian's age, guardian's relationship with the child, terminal ID, terminal name, child ID, and class ID, and stores them in the guardian management table. 56.

Next, in step S<b>27 , the user registration unit 43 transmits the guardian ID, terminal ID, and school ID to the guardian terminal 16 .

Next, in step S<b>28 , the code acquisition unit 81 of the parent terminal 16 causes the application information storage unit 73 to store the parent ID, terminal ID, and school ID transmitted from the server device 12 . This completes a series of processes.

Next, the operation at the time of additional registration (invitation) of the guardian terminal 16 in the point management system 11 will be described.

Additional registration (invitation) of a parent's terminal 16 is to add and register another parent's terminal 16 corresponding to a child when there is a registered parent's terminal 16 corresponding to the child. The additional registration of the parent terminal 16 is performed, for example, after registering the parent terminal 16 of one of the parents of a certain child, to register the parent terminal 16 of the other parent.

First, in step S31 of FIG. 21, the registered guardian terminal 16A transmits an invitation code issuance instruction to the server device 12. FIG. Specifically, when an invitation code issuance request operation is performed, the code acquisition unit 81 of the guardian terminal 16A transmits an invitation code issuance instruction to the server device 12 . The invitation code issuance instruction includes the guardian ID stored in the guardian terminal 16A.

Here, in FIG. 21, the registered guardian terminal 16 of a certain child's guardian is assumed to be the guardian terminal 16A, and the terminal to be additionally registered (invited) as the guardian terminal 16 of the child's guardian is the guardian terminal 16B. and

When the server device 12 receives the invitation code issuing instruction, the invitation code issuing unit 42 issues an invitation code in step S32. The invitation code issuing unit 42 stores the issued invitation code in the guardian management table 56 and the invitation code management table 57 in association with the guardian ID of the guardian terminal 16A.

Next, in step S33, the invitation code issuing unit 42 generates an invitation QR code in which the invitation code is embedded.

Next, in step S34, the invitation code issuing unit 42 transmits the image data of the invitation QR code to the guardian terminal 16A.

Next, in step S35, the display control unit 82 of the guardian terminal 16A causes the display unit 75 to display the invitation QR code. Specifically, the display control unit 82 displays the invitation QR code 98 on the invitation QR code screen 97 shown in FIG.

Returning to FIG. 21, in step S36, the operator of the parent terminal 16A presents the invitation QR code 98 displayed on the parent terminal 16A to the parent terminal 16B.

Next, in step S37, the parent terminal 16B reads the QR code 98 for invitation.

Specifically, the code acquisition unit 81 of the guardian terminal 16B acquires the invitation QR code 98 in the video imaged by the imaging unit 74 displayed on the invitation QR code reading screen (not shown). do.

Next, in step S<b>38 , the code acquisition unit 81 analyzes the invitation QR code 98 and acquires the invitation code embedded in the invitation QR code 98 .

Next, in step S39, the guardian terminal 16B accepts input of guardian information. The process of step S39 is the same as the process of step S19 in FIG. 14 described above.

Next, in step S<b>40 , the code acquisition unit 81 of the parent terminal 16</b>B transmits the invited terminal transmission information to the server device 12 . The invited terminal transmission information includes an invitation code, the terminal name of the parent terminal 16B, the parent's age, the parent's relationship with the child, and the parent's nickname.

When the server device 12 receives the invited terminal transmission information, the user registration unit 43 transmits a registration content confirmation instruction to the guardian terminal 16B in step S41. The registration content confirmation instruction includes the child's school name, class name, child's nickname, and distribution group indicated by the child ID associated with the terminal ID of the parent terminal 16A.

When the guardian terminal 16B receives the registration content confirmation instruction, the display control unit 82 causes the display unit 75 to display the registration confirmation screen 99 shown in FIG. 23 in step S42. The registration confirmation screen 99 displays the child's school name, class name, nickname, and distribution group indicated by the child ID associated with the parent terminal 16A.

Further, the registration confirmation screen 99 is provided with a completion button 100 for completing the user registration. When the completion button 100 is pressed, the code acquisition unit 81 of the guardian terminal 16B transmits a registration instruction to the server device 12 in step S43 of FIG.

When the server device 12 receives the registration instruction, in step S44, the user registration unit 43 issues a guardian ID and a terminal ID for the guardian terminal 16B.

Next, in step S45, the user registration unit 43 registers the guardian ID corresponding to the guardian terminal 16B, the terminal ID, the terminal name, the age of the guardian, the relationship of the guardian to the child, and the nickname of the guardian. Register in the management table 56. At this time, the user registration unit 43 registers the same child ID and class ID as the child ID and class ID associated with the terminal ID of the parent terminal 16A, and the parent ID, terminal ID, and terminal name corresponding to the parent terminal 16B. , guardian's age, guardian's relationship with the child, and guardian's nickname are associated with each other and stored in the guardian management table 56 .

As a result, the parent terminal 16A and the parent terminal 16B are associated and registered in the server device 12 by the common child ID and class ID. Further, this synchronizes the child ID and the class ID between the parent terminal 16A and the parent terminal 16B. As a result, the child's nickname and distribution group are also synchronized.

Therefore, the parent terminal 16B can be registered without inputting the child information (attendance number, child's nickname, distribution group) input at the time of registration of the parent terminal 16A.

Next, in step S46, the user registration unit 43 transmits the guardian ID, terminal ID, and school ID to the guardian terminal 16B.

Next, in step S<b>47 , the code acquisition unit 81 of the parent terminal 16</b>B causes the application information storage unit 73 to store the parent ID, terminal ID, and school ID transmitted from the server device 12 . This completes a series of processes.

Next, the operation of browsing the advertiser's site for receiving points by the point giving service in the point management system 11 will be described.

FIG. 24 shows the home screen 101 of the application for using the support service on the parent terminal 16. As shown in FIG. A banner advertisement area 102 is provided on the home screen 101 . The banner advertisement area 102 is always provided not only on the home screen 101 but also on the application display screen.

Also, the application on the parent terminal 16 can display an advertisement list screen 103 shown in FIG. The advertisement list screen 103 is a screen for displaying a list of advertisements currently distributed in the area where the school 200 attended by the child associated with the parent terminal 16 is located. An advertisement area 104 is displayed on the advertisement list screen 103 . The advertisement list screen 103 also displays the point acquisition status (whether or not points have been acquired) for each advertisement.

Advertisement images are displayed in the banner advertisement area 102 and the advertisement area 104 based on the advertisement image data distributed by the advertisement management unit 32 of the server device 12 . The advertisement management unit 32 distributes the advertisement ID to the parent terminal 16 together with the advertisement image data of each advertisement. The advertisement image of the banner advertisement area 102 is switched each time the display screen of the application is switched.

In step S51 of FIG. 26, when an operation of pressing the banner advertisement area 102 or one of the advertisement areas 104 is performed as an operation of viewing an advertisement, in step S52, the advertisement processing unit 83 of the parent terminal 16 reads the advertisement. A main site information request is sent to the server device 12 . The advertiser site information request includes the advertisement ID of the advertisement displayed in the pressed banner advertisement area 102 or advertisement area 104 and the terminal ID of the parent's terminal 16 .

When the server device 12 receives the advertiser site information request, in step S53, the advertisement management unit 32 refers to the advertisement management table 51 and the point management table 58 to refer to the parent terminal 16 that transmitted the advertiser site information request. determines whether or not the number of visits to the advertiser site requested by is equal to or greater than the maximum number of points earned.

The maximum number of point acquisition is set in advance as an upper limit of the number of browsing times for which one advertiser's site can acquire points on one parent's terminal 16 . The maximum number of points obtained may be one or more.

If it is determined that the number of views is equal to or greater than the point acquisition upper limit number (step S53: YES), the advertisement management unit 32 transmits the advertiser site information of the requested advertiser site to the parent terminal 16 in step S54. .

When the parent terminal 16 receives the advertiser site information, the display control unit 82 causes the display unit 75 to display the advertiser site based on the advertiser site information in step S55. This completes a series of processes.

In step S53, when the advertisement management unit 32 determines that the number of views is less than the maximum number of points to be acquired (step S53: NO), in step S56, the point granting unit 46 protects the sender of the advertiser site information request. Points are given to the school 200 attended by the child associated with the user terminal 16.例文帳に追加

Specifically, the point granting unit 46 acquires from the advertisement management table 51 the click unit price (number of points) of the advertiser site requested by the advertiser site information request. Next, the point granting unit 46 adds the number of points corresponding to the acquired click unit price to the number of points held corresponding to the school ID of the school 200 to which points are to be granted in the school management table 53 .

In addition, the point granting unit 46 updates the advertisement point information in the advertisement management table 51 of the advertiser site requested by the advertiser site information request to a value obtained by adding the number of points corresponding to the click unit price of the advertiser site. .

Next, in step S57, the point granting unit 46 updates the number of times the requested advertiser site has been viewed by the parent terminal 16, which is the source of the advertiser site information request, and the number of acquired points. Specifically, the point granting unit 46 adds "1" to the number of views, and adds the number of points corresponding to the unit price of click to the number of acquired points.

Next, in step S58, the advertisement management unit 32 transmits to the guardian terminal 16 the advertiser site information of the requested advertiser site and the acquired point information indicating the number of points that can be acquired by browsing the advertiser site this time. .

When the parent terminal 16 receives the advertiser site information and the acquired point information, the display control unit 82 causes the display unit 75 to display the number of acquired points on the pop-up screen 105 as shown in FIG. 27 in step S59. Also, the point processing unit 84 updates the terminal point information in the application information storage unit 73 .

Returning to FIG. 26, in step S60, the display control unit 82 causes the display unit 75 to display the advertiser's site based on the advertiser's site information. This completes a series of processes.

Next, the operation of exchanging the points held by the school 200 for goods in the point management system 11 will be described.

When the school 200 uses the points, the school terminal 14 accesses the point use page in the point giving service provided by the server device 12 through the browser according to the teacher's operation.

As a result, a point use page 111 as shown in FIG. 28 is displayed on the display section of the school terminal 14 . The points use page 111 lists at least some pictures of the items stored in the item table 59 of the server device 12, the names of the items, and the required number of points. From this point use page 111, the teacher of the school 200 can select an item that the teacher wants to exchange points for.

When a desired item is selected and an operation for exchanging points for the item is performed, in step S71 of FIG. Send to device 12 .

Next, in step S72, the point exchange unit 47 of the server device 12 performs point exchange processing upon receiving the point exchange request. Specifically, the point exchange unit 47 subtracts the points corresponding to the requested item from the number of points held by the school 200 that sent the point exchange request in the school management table 53 .

Next, in step S73, the point exchange unit 47 places an order for the requested item with the sponsoring company 4 that provides the requested item. This completes the series of operations.

After the above-described order processing by the point exchange unit 47 is performed, the sponsor company 4 delivers the ordered goods to the school 200 .

Note that the school 200 may contact the operation manager 3 by e-mail, telephone, or the like to designate an item and exchange the points for the item.

In this case, in response to the operation by the staff of the operation manager 3 who has been contacted by the school 200, the operation manager terminal 13 accesses the server device 12 and designates the points of the school 200 instructed to exchange the points for goods. Instruct to perform the process for exchanging for the purchased item.

In response, the point exchange unit 47 subtracts the points corresponding to the designated goods from the number of points possessed by the school 200 instructed to exchange points for goods in the school management table 53 .

Also, the operation manager 3 orders the goods designated by the school 200 from the sponsoring company 4 by e-mail, telephone, or the like. After that, the sponsor company 4 delivers the ordered goods to the school 200 .

Next, the operation of printing and distributing school news in the letter service in the point management system 11 will be described.

First, in response to an operation on the school terminal 14 , the school terminal 14 uploads school news data, which is image data of school news, to the server device 12 .

Next, by operating the school terminal 14, the class, group, etc. to which the school news is to be delivered is specified.

Thereafter, by operating the school terminal 14, instructions for printing and distribution of the school news are given. In response to this, the school terminal 14 transmits the school news data to the printing device 15 and instructs the printing device 15 to print the number of copies for the number of people to be distributed. Further, the school terminal 14 transmits a distribution instruction to the server device 12 to distribute the school news data to the distribution target.

Note that the print instruction and the distribution instruction may be executed by a single operation on the school terminal 14 . For example, the print instruction and the distribution instruction may be executed by one operation of pressing a print/distribution instruction button displayed on the display section of the school terminal 14 .

The printing device 15 instructed to print prints on a print medium such as paper based on the school news data. The printed school news is distributed to the homes of the children included in the distribution target.

The school news management unit 34 of the server device 12 that has received the distribution instruction associates the school news data for which the distribution instruction is given with the distribution target information and the already read information and stores them in the school news table 60 . At this stage, all parent terminals 16 to be distributed are in an unread state.

Next, the school news management unit 34 transmits a push notification to each parent terminal 16 targeted for distribution. At this time, along with the push notification, the name of the document in the school news is also sent. Upon receiving the push notification, the school news processing unit 85 of the parent terminal 16 adds the received push notification to the notification list information of the application information storage unit 73 .

Here, the guardian terminal 16 can display a notification list screen 121 shown in FIG. 30 based on the notification list information in the application information storage unit 73 . On the notification list screen 121, a list of school news notified by push notification is displayed. The school news to be displayed can be selected from the notification list screen 121 . On the notification list screen 121, in association with the document name of each school news, an unread mark 122 indicating that the school news has not been read on the parent terminal 16 displaying the notification list screen 121, or has been read. A read mark 123 indicating that is displayed.

When an operation is performed to select any school news from the notification list screen 121, the school news processing unit 85 transmits a school news acquisition request for requesting school news data of the selected school news to the server device 12. do.

When the server device 12 receives the school news acquisition request, the school news management unit 34 transmits the requested school news data to the parent terminal 16 .

When the parent terminal 16 receives the school news data, the display control unit 82 causes the display unit 75 to display an image of the school news based on the school news data.

When the unread school news is displayed, the school news processing unit 85 transmits a read status notification indicating that the school news has been read on the parent terminal 16 to the server device 12. .

When the server device 12 receives the read status notification, the school news management unit 34 adds the school news data notified by the read status notification in the school news table 60 to the parent terminal 16 of the transmission source of the read status notification. Change the read status of from unread to read.

As described above, in the letter service, printed matter of school news to be distributed to parents is created, and school news data is delivered to the parent terminal 16 . As a result, even if the child forgets to give the printed matter to the parent, the information printed on the printed matter can be transmitted to the parent's terminal 16.例文帳に追加Also, since the parent can recognize that the printed matter has been distributed to the child, the parent can receive the printed matter from the child and obtain information from the printed matter. Therefore, it is possible to reduce the possibility that the information printed on the printed matter is not communicated to the guardian.

Next, the operation when using the contact service in the point management system 11 will be described.

First, a case where a guardian reports health observation information of a child to school 200 will be described.

When the parent reports the health observation information of the child to the school 200, the display unit 75 of the parent terminal 16 displays the health observation screen 131 shown in FIG. On the health observation screen 131, it is possible to input the child's body temperature, health condition, and the like.

When the child's body temperature, health condition, etc. are entered on the health observation screen 131, the contact information processing unit 86 transmits the health observation information including the entered body temperature, health condition, etc. to the server device 12 together with the child's ID.

When server device 12 receives the health observation information and the child ID, contact information management unit 35 stores the health observation information in contact information table 61 in association with the child ID and the date of the day.

Also, the contact information management unit 35 transmits the health observation information to the school terminal 14 together with the child ID. Accordingly, the school 200 is notified of the child's health observation information.

Here, the parent terminal 16 can display the history of reported health observation information. When displaying the history of health observation information, the guardian terminal 16 transmits a health observation history request to the server device 12 . The health observation history request includes the child ID of the child whose history of health observation information is to be displayed on the guardian terminal 16 of the transmission source.

When server device 12 receives the health observation history request, contact information management unit 35 updates the health observation information associated with the child ID included in the health observation history request in contact information table 61 to the sender of the health observation history request. is transmitted to the guardian terminal 16 of . As a result, the history of health observation information can be displayed on the parent terminal 16 .

When there are a plurality of guardian terminals 16 registered in the server device 12 in association with one child ID, contact information management is performed in response to a health observation history request including the child ID from any of the guardian terminals 16. Unit 35 transmits the same health observation information. That is, the contact information management unit 35 synchronizes the health observation information of the child corresponding to the child ID among the plurality of parent terminals 16 registered in the server device 12 in association with one child ID.

Next, a case where a parent contacts the school 200 regarding a child's attendance will be described.

When the parent/guardian contacts the school 200 regarding the child's attendance, the display unit 75 of the parent/guardian terminal 16 displays an absence/tardy contact screen 132 shown in FIG. On the absence/tardiness contact screen 132, it is possible to input the child's absence, arriving late, leaving early, and their period.

When the child's absence, arriving late, leaving early, and their periods, etc. are input on the absence/tardy contact screen 132, the contact information processing unit 86 displays the absence, arriving late, leaving early, and attendance information including those periods. The confirmation information is sent to the server device 12 together with the child ID.

When the server device 12 receives the attendance confirmation information and the child ID, the contact information management unit 35 stores the attendance confirmation information in the contact information table 61 in association with the child ID.

The contact information management unit 35 also transmits the attendance confirmation information to the school terminal 14 together with the child ID. As a result, the school 200 is notified of the child's attendance.

Here, as with the health observation information described above, the history of the attendance confirmation information can also be displayed on the guardian terminal 16 . In addition, like the health observation information described above, the attendance confirmation information is also synchronized among the plurality of parent terminals 16 registered in the server device 12 in association with one child ID.

Next, a case in which the school 200 contacts parents individually will be described.

When the school 200 contacts the parents individually, an input screen for individual contact is displayed on the display unit of the school terminal 14 according to the teacher's operation, and the contents of the contact are entered. Then, the individual communication information including the content of the input communication is transmitted to the server device 12 together with the child ID of the child to be contacted.

When server device 12 receives the individual contact information and the child ID, contact information management unit 35 stores the individual contact information in contact information table 61 in association with the child ID.

Next, the contact information management unit 35 sends a contact notification indicating that the individual contact information has been sent from the school 200 to the parent terminal 16 associated with the child ID sent together with the individual contact information.

On the guardian terminal 16, the presence of the individual contact information for which the contact notification has been received can be confirmed on the individual contact screen 133 shown in FIG. When the individual contact information display area is pressed on the individual contact screen 133, the contact information processing unit 86 transmits to the server device 12 an individual contact information acquisition request for requesting the individual contact information.

When the server device 12 receives the individual contact information acquisition request, the contact information management unit 35 transmits the requested individual contact information to the guardian terminal 16 that is the source of the individual contact information acquisition request.

When the guardian terminal 16 receives the individual contact information, the display control section 82 causes the display section 75 to display the individual contact information. As a result, the parent can confirm the content of the individual communication from the school 200 on the parent terminal 16 .

When replying to the individual contact information, the reply information is transmitted from the guardian terminal 16 to the server device 12, stored in the contact information table 61, and then transmitted to the school terminal 14. FIG.

As described above, in the point management system 11, the class code issuing unit 41 issues a class code including a class ID. The user registration unit 43 associates the terminal ID of the parent terminal 16 from which the class code is acquired, the class ID included in the class code, and the attendance number (child ID) of the child in the class, and manages the parents in the database unit 22. Store in table 56 . As a result, when registering a child in association with the parent terminal 16, there is no need to register personal information such as the child's name and address. Therefore, it is possible to manage the child while protecting the child's privacy.

In addition, in the point management system 11, the attendance number (child ID), which is information that does not include personal information, is registered in the database unit 22 as identification information for identifying the child. can be managed.

Further, in the point management system 11, by using the attendance number (child ID) of the child's class, it is possible to manage the child who attends the school 200 while protecting the privacy of the child.

In addition, since the point management system 11 registers the child's nickname in the database unit 22, the nickname can be used instead of registering the child's name, which is personal information. For example, the child's nickname can be used for displaying the child in the application.

In addition, in the point management system 11, the user registration unit 43 allows the child ID and Synchronize class IDs. Therefore, the other parent terminal 16 can be registered without inputting the child information that was input when the registered parent terminal 16 was registered, thereby simplifying the registration operation.

In addition, in the point management system 11, health observation information and attendance confirmation information are synchronized among a plurality of parent terminals 16 registered in association with one child ID. Therefore, health observation information and attendance confirmation information can be shared among a plurality of parent terminals 16 registered in association with one child ID.

In addition, in the point management system 11, the user registration unit 43 acquires an invitation code from another parent terminal 16 different from the registered parent terminal 16, which has acquired an invitation code via the registered parent terminal 16. When the code is input, the terminal ID of the other parent terminal 16 is associated with the same child ID and class ID as the child ID and class ID associated with the terminal ID of the registered parent terminal 16. It is stored in the guardian management table 56 of the database unit 22 . In addition, the user registration unit 43 transmits the class ID and child ID that are the same as the class ID and child ID associated with one of the parent terminals 16 (guardian ID) registered in the server device 12 to other terminal transmission information. If it is obtained from the guardian terminal 16, an error notification is sent to the other guardian terminal 16. FIG.

As a result, when the authorized parental terminal 16 (the terminal of the child's guardian) has been registered, the non-authorized parental terminal 16 (the terminal of the person who is not the child's guardian) acquires and registers the class code. When trying to do so, it is possible to prevent the registration of the unauthorized guardian terminal 16.例文帳に追加In addition, when the non-authorized parental terminal 16 is registered, an error is notified when the authorized parental terminal 16 acquires the class code and tries to register, so that the child's parent is not authorized to It can be noticed that the guardian terminal 16 of the parent is registered. As a result, it becomes possible to exclude the registration of unauthorized guardian terminals 16 .

[Second embodiment]
Next, a description will be given of a second embodiment in which the operation at the time of user registration in the above-described first embodiment is changed.

In the second embodiment, first, in step S81 of FIG. 34, the guardian terminal 16 reads the class QR code 88 in the class QR code column 87 of the registration guide, as in step S17 of FIG. 14 described above.

After that, the processing of steps S82 to S86 is the same as the processing of steps S18 to S22 in FIG.

If it is determined in step S86 that there is a registered parental terminal 16 (step S86: YES), in step S87 the user registration unit 43 notifies the parental terminal 16 of the transmission source of the terminal transmission information that the terminal has been registered. to send.

Here, in FIG. 34, the guardian terminal 16C is the registered guardian terminal 16. FIG.

The registered terminal notification corresponds to the terminal name associated with the terminal ID of the registered guardian terminal 16C, the guardian's nickname, the age of the guardian, the relationship with the child, the child's ID, the class ID, and the relevant class ID. It contains the class name etc. to be used.

When the guardian terminal 16 receives the registered terminal notification, the display control unit 82 causes the display unit 75 to display the registered terminal display screen 141 shown in FIG. 36 in step S88.

The registered terminal display screen 141 displays the child ID (attendance number) associated with the registered parent terminal 16C, the class name of the child indicated by the child ID, the terminal name of the parent terminal 16C, and the like. In addition, on the registered terminal display screen 141, an application button 142 for selecting to apply for registration to the registered guardian terminal 16C and a cancel button 143 for selecting not to apply for registration are displayed. be done.

Next, in step S89, the code acquisition unit 81 of the guardian terminal 16 determines whether application for registration has been selected. If the application button 142 is pressed on the registered terminal display screen 141, the code acquisition unit 81 determines that application for registration has been selected, and if the cancel button 143 is pressed, does not apply for registration. is selected.

If the code acquisition unit 81 determines that the user has selected not to apply for registration (step S89: NO), the series of processes ends.

If it is determined that application for registration has been selected (step S89: YES), in step S90, the code acquisition unit 81 transmits a registration application notification to the registered guardian terminal 16C. The registration application notification includes the class ID obtained in step S82, the parent's nickname input in step S83, and the attendance number (child ID) input in step S84.

When the guardian terminal 16C receives the registration application notification, the display control unit 82 causes the display unit 75 to display the registration permission screen 146 shown in FIG. 37 in step S91.

The registration permission screen 146 displays a message notifying that there is a parent terminal 16 to be registered in association with the same child ID as the child ID with which the parent terminal 16C is associated. Further, the registration permission screen 146 displays a rejection button 147 for selecting rejection of registration and a permission button 148 for selecting permission of registration.

Next, in step S92, the code acquisition unit 81 of the guardian terminal 16C determines whether or not permitting registration has been selected. Here, code acquisition unit 81 determines that permission to register has been selected when permission button 148 is pressed on registration permission screen 146, and can refuse registration when refusal button 147 is pressed. judged to be selected.

If it is determined that permitting registration has been selected (step S92: YES), code acquisition unit 81 transmits a registration permitting notification to server device 12 in step S93.

When the server device 12 receives the registration permission notification, the process proceeds to step S94. The processing of steps S94 to S97 is the same as the processing of steps S25 to S28 in FIG. 14 described above.

In step S86, when the user registration unit 43 determines that there is a registered guardian terminal 16 (step S86: NO), the process proceeds to step S94.

If it is determined in step S92 that rejection of registration has been selected (step S92: NO), code acquisition section 81 transmits a registration rejection notification to server device 12 in step S98 of FIG.

When the server device 12 receives the registration refusal notification, the user registration unit 43 transmits the registration refusal notification to the guardian terminal 16 in step S99.

When the guardian terminal 16 receives the registration rejection notification, the display control unit 82 causes the display unit 75 to display the registration rejection notification screen 151 shown in FIG. 38 in step S100. This completes a series of processes.

As described above, in the second embodiment, the user registration unit 43 receives the class ID associated with the registered parent terminal 16 and the When the same class ID and child ID as the child ID are obtained, the other parent terminal 16 is caused to apply for registration to the registered parent terminal 16, and the registered parent terminal 16 requests the registration of the other parent terminal 16. If the registration is permitted, the terminal ID, class ID, and child ID of the other parent terminal 16 are associated and stored in the parent management table 56 .

As a result, the registered guardian terminal 16 can refuse to register the unauthorized guardian terminal 16, so that the registration of the unauthorized guardian terminal 16 can be excluded.

[Other embodiments]
As noted above, the present invention has been described through first and second embodiments, but the discussion and drawings forming part of this disclosure should not be understood to limit the present invention. Various alternative embodiments, implementations and operational techniques will become apparent to those skilled in the art from this disclosure.

In the first and second embodiments described above, the case where the service provider 1 is a school has been described. However, not limited to these, the service provider 1 is, for example, a hospital that provides medical services, a nursing facility that provides nursing care services, a nursery school, a kindergarten, a company, a department within a company, a public fire department, a mutual aid organization such as a fire brigade , a public health center, etc. Schools as the service provider 1 include elementary schools, junior high schools, high schools, universities, and the like. The present invention can be applied even when the service provider 1 is various organizations that provide services.

In the first and second embodiments described above, the service provider 1 is a school and the service user 2 is a parent. It may be a student who attends school, a graduate, or their family.

If the service provider 1 is a nursery school or kindergarten, the service users 2 may be kindergarten children or their guardians, graduates or their guardians, and their families. If the service provider 1 is a hospital, the service users 2 may be patients, their caregivers, caregivers, people who have completed treatment, and their families. If the service provider 1 is a company or a department within the company, the service users 2 may include employees, full-time employees, temporary employees, shareholders, retirees, OBs, their families, and the like. If the service provider 1 is a community-based local government such as a public fire station, a public health center, or a mutual aid organization such as a fire brigade, the service users 2 are local residents, visitors, or their families. may

In the first embodiment described above, when registering another parent terminal 16 to be registered in association with the registered parent terminal 16, the child ID, class ID, etc. are synchronized between these parent terminals 16. However, the present invention is not limited to this, as long as it synchronizes predetermined registration information.

In the above-described first and second embodiments, as identification information for identifying a child, the attendance number (child ID) of the child's school class was registered, but this is not limiting and does not include the user's personal information. It may be anything as long as identification information is registered.

In the first and second embodiments described above, health observation information and attendance confirmation information are synchronized between a plurality of parent terminals 16 registered in association with one child ID. It is sufficient if it synchronizes the information of

In the first and second embodiments described above, a class QR code is used to notify information for user registration, but other types of code such as bar codes may be used. The same applies to the invitation QR code.

In the first and second embodiments described above, the terminal ID is issued by the server device 12, but the terminal ID may be generated by the parent terminal 16, or the unique identification originally held by the parent terminal 16 may be generated. Information may be used as a terminal ID.

Thus, the present invention naturally includes various embodiments and the like not described here. Therefore, the technical scope of the present invention is defined only by the matters specifying the invention according to the valid scope of claims based on the above description.

[Appendix]
This application discloses the following inventions.

(Appendix 1)
a registration code issuing unit that issues a registration code for user registration;
a storage unit;
Information included in the registration code and user identification information input to the terminal device are acquired from the terminal device that acquired the registration code, and information indicating the terminal device and information included in the registration code are acquired. a registration unit that registers the terminal device by associating information with the identification information and storing the information in the storage unit;
an invitation code issuing unit that transmits an invitation code to the registered terminal device in response to a request from the registered terminal device;
The registration unit
Information indicating the other terminal device when the invitation code is input from another terminal device different from the registered terminal device that has acquired the invitation code via the registered terminal device is stored in the storage unit in association with the information included in the registration code and the identification information entered at the time of registration of the registered terminal device, thereby registering the other terminal device;
Acquired information included in the registration code and identification information indicating the same user as the identification information input at the time of registration of the registered terminal device from another terminal device different from the registered terminal device a registration device that notifies the other terminal device of an error in the event of a failure.

(Appendix 2)
a registration code issuing unit that issues a registration code for user registration;
a storage unit;
Information included in the registration code and user identification information input to the terminal device are acquired from the terminal device that acquired the registration code, and information indicating the terminal device and information included in the registration code are acquired. a registration unit that registers the terminal device by associating information with the identification information and storing the information in the storage unit;
The registration unit receives from a terminal device different from the registered terminal device information contained in the registration code and an identification indicating the same user as the identification information input at the time of registration of the registered terminal device. When the information is acquired, the other terminal device is caused to apply for registration to the registered terminal device, and when the registered terminal device permits registration of the other terminal device, the other terminal device a registration device that registers the other terminal device by associating information indicating the identification, information included in the registration code, and the identification information with each other and storing the identification information in the storage unit.

(Appendix 3)
issuing a registration code for user registration;
Information included in the registration code and user identification information input to the terminal device are acquired from the terminal device that acquired the registration code, and information indicating the terminal device and information included in the registration code are acquired. a step of registering the terminal device by associating the information with the identification information and storing the information in a storage unit;
sending an invitation code to the registered terminal device in response to a request from the registered terminal device;
Information indicating the other terminal device when the invitation code is input from another terminal device different from the registered terminal device that has acquired the invitation code via the registered terminal device is stored in the storage unit in association with the information included in the registration code and the identification information input at the time of registration of the registered terminal device, thereby registering the other terminal device;
Acquired information included in the registration code and identification information indicating the same user as the identification information input at the time of registration of the registered terminal device from another terminal device different from the registered terminal device and a step of notifying the other terminal device of the error in the case of the registration method.

(Appendix 4)
issuing a registration code for user registration;
Information included in the registration code and user identification information input to the terminal device are acquired from the terminal device that acquired the registration code, and information indicating the terminal device and information included in the registration code are acquired. a step of registering the terminal device by associating the information with the identification information and storing the information in a storage unit;
When the information included in the registration code and the identification information indicating the same user as the identification information entered at the time of registration of the registered terminal device are obtained from another terminal device that is different from the registered terminal device. and when the other terminal device is caused to apply for registration to the registered terminal device, and the registered terminal device permits registration of the other terminal device, information indicating the other terminal device and the registration and a step of registering the other terminal device by associating information contained in a user code with the identification information and storing the identification information in the storage unit.

(Appendix 5)
to the computer,
issuing a registration code for user registration;
Information included in the registration code and user identification information input to the terminal device are acquired from the terminal device that acquired the registration code, and information indicating the terminal device and information included in the registration code are acquired. a step of registering the terminal device by associating the information with the identification information and storing the information in a storage unit;
sending an invitation code to the registered terminal device in response to a request from the registered terminal device;
Information indicating the other terminal device when the invitation code is input from another terminal device different from the registered terminal device that has acquired the invitation code via the registered terminal device is stored in the storage unit in association with the information included in the registration code and the identification information input at the time of registration of the registered terminal device, thereby registering the other terminal device;
Acquired information included in the registration code and identification information indicating the same user as the identification information input at the time of registration of the registered terminal device from another terminal device different from the registered terminal device In this case, a program for executing a step of notifying the other terminal device of the error;

(Appendix 6)
to the computer,
issuing a registration code for user registration;
Information included in the registration code and user identification information input to the terminal device are acquired from the terminal device that acquired the registration code, and information indicating the terminal device and information included in the registration code are acquired. a step of registering the terminal device by associating the information with the identification information and storing the information in a storage unit;
When the information included in the registration code and the identification information indicating the same user as the identification information entered at the time of registration of the registered terminal device are obtained from another terminal device that is different from the registered terminal device. and when the other terminal device is caused to apply for registration to the registered terminal device, and the registered terminal device permits registration of the other terminal device, information indicating the other terminal device and the registration and a step of registering the other terminal device by associating the information included in the application code with the identification information and storing the identification information in the storage unit.

1 Service Provider 2 Service User Side 3 Operation Manager 4 Sponsoring Company 5 Advertiser 11 Point Management System 12 Server Device 13 Operation Manager Terminal 14 School Terminal 15 Printer 16 Parent Terminal 21 Control Section 22 Database Section 23 Program Storage Section 24 external communication unit 31 user management unit
32 advertisement management unit 33 point management unit 34 school news management unit 35 contact information management unit 41 class code issuing unit 42 invitation code issuing unit 43 user registration unit 46 point giving unit 47 point exchange unit 51 advertisement management table 52 area management table 53 School management table 54 Class management table 55 Child management table 56 Parent management table 57 Invitation code management table 58 Point management table 59 Goods table 60 School news table 61 Contact information table 71 Control unit 72 Program storage unit 73 Application information storage unit 74 Imaging unit 75 Display unit 76 Input unit 77 External communication unit 81 Code acquisition unit 82 Display control unit 83 Advertisement processing unit 84 Point processing unit 85 School news processing unit 86 Contact information processing unit 87 Class QR code field 88 Class QR code 89 Attendance number Entry field 98 Invitation QR code 102 Banner advertising area 104 Advertising area

Claims (6)

a registration code issuing unit that issues a registration code for user registration;
a storage unit;
Information included in the registration code and user identification information input to the terminal device are acquired from the terminal device that acquired the registration code, and information indicating the terminal device and information included in the registration code are acquired. a registration unit that registers the terminal device by associating information with the identification information and storing the information in the storage unit;
an invitation code issuing unit that transmits an invitation code to the registered terminal device in response to a request from the registered terminal device;
The registration unit
Information indicating the other terminal device when the invitation code is input from another terminal device different from the registered terminal device that has acquired the invitation code via the registered terminal device is stored in the storage unit in association with the information included in the registration code and the identification information input at the time of registration of the registered terminal device, thereby registering the other terminal device;
Acquired information included in the registration code and identification information indicating the same user as the identification information input at the time of registration of the registered terminal device from another terminal device different from the registered terminal device a registration device that notifies the other terminal device of an error in the event of a failure. a registration code issuing unit that issues a registration code for user registration;
a storage unit;
Information included in the registration code and user identification information input to the terminal device are acquired from the terminal device that acquired the registration code, and information indicating the terminal device and information included in the registration code are acquired. a registration unit that registers the terminal device by associating information with the identification information and storing the information in the storage unit;
The registration unit receives from a terminal device different from the registered terminal device information contained in the registration code and an identification indicating the same user as the identification information input at the time of registration of the registered terminal device. When the information is acquired, the other terminal device is caused to apply for registration to the registered terminal device, and when the registered terminal device permits registration of the other terminal device, the other terminal device a registration device that registers the other terminal device by associating information indicating the identification, information included in the registration code, and the identification information with each other and storing the identification information in the storage unit. issuing a registration code for user registration;
Information included in the registration code and user identification information input to the terminal device are acquired from the terminal device that acquired the registration code, and information indicating the terminal device and information included in the registration code are acquired. a step of registering the terminal device by associating the information with the identification information and storing the information in a storage unit;
sending an invitation code to the registered terminal device in response to a request from the registered terminal device;
Information indicating the other terminal device when the invitation code is input from another terminal device different from the registered terminal device that has acquired the invitation code via the registered terminal device is stored in the storage unit in association with the information included in the registration code and the identification information input at the time of registration of the registered terminal device, thereby registering the other terminal device;
Acquired information included in the registration code and identification information indicating the same user as the identification information input at the time of registration of the registered terminal device from another terminal device different from the registered terminal device and a step of notifying the other terminal device of the error in the case of the registration method. issuing a registration code for user registration;
Information included in the registration code and user identification information input to the terminal device are acquired from the terminal device that acquired the registration code, and information indicating the terminal device and information included in the registration code are acquired. a step of registering the terminal device by associating the information with the identification information and storing the information in a storage unit;
When the information included in the registration code and the identification information indicating the same user as the identification information entered at the time of registration of the registered terminal device are obtained from another terminal device that is different from the registered terminal device. and when the other terminal device is caused to apply for registration to the registered terminal device, and the registered terminal device permits registration of the other terminal device, information indicating the other terminal device and the registration and a step of registering the other terminal device by associating information contained in a user code with the identification information and storing the identification information in the storage unit. to the computer,
issuing a registration code for user registration;
Information included in the registration code and user identification information input to the terminal device are acquired from the terminal device that acquired the registration code, and information indicating the terminal device and information included in the registration code are acquired. a step of registering the terminal device by associating the information with the identification information and storing the information in a storage unit;
sending an invitation code to the registered terminal device in response to a request from the registered terminal device;
Information indicating the other terminal device when the invitation code is input from another terminal device different from the registered terminal device that has acquired the invitation code via the registered terminal device is stored in the storage unit in association with the information included in the registration code and the identification information input at the time of registration of the registered terminal device, thereby registering the other terminal device;
Acquired information included in the registration code and identification information indicating the same user as the identification information input at the time of registration of the registered terminal device from another terminal device different from the registered terminal device In this case, a program for executing a step of notifying the other terminal device of the error; to the computer,
issuing a registration code for user registration;
Information included in the registration code and user identification information input to the terminal device are acquired from the terminal device that acquired the registration code, and information indicating the terminal device and information included in the registration code are acquired. a step of registering the terminal device by associating the information with the identification information and storing the information in a storage unit;
When the information included in the registration code and the identification information indicating the same user as the identification information entered at the time of registration of the registered terminal device are obtained from another terminal device that is different from the registered terminal device. and when the other terminal device is caused to apply for registration to the registered terminal device, and the registered terminal device permits registration of the other terminal device, information indicating the other terminal device and the registration and a step of registering the other terminal device by associating the information included in the application code with the identification information and storing the identification information in the storage unit.

Images