Information processing device, method, program
The system enhances childcare facility operations by targeting notifications to specific locations based on child-class affiliations, improving efficiency and allowing workers to concentrate on childcare during pickup times.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2026-01-07
- Publication Date
- 2026-03-17
AI Technical Summary
Existing childcare facility systems require childcare workers to check notifications for children who are not their assigned children, diverting attention from their primary duties during pickup times.
A system that stores child and guardian information, determines notification destinations based on class affiliation, and notifies relevant locations within the facility, allowing for targeted and efficient communication with parents.
Facilitates smoother preparations for child pickup, enabling childcare workers to focus on their duties by reducing unnecessary notifications and improving operational efficiency.
Smart Images

Figure 0007831897000001_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to an information processing apparatus, method, and program.
Background Art
[0002] Childcare is provided in a childcare facility. When the childcare time in the childcare facility is about to end, the guardian of the child visits the childcare facility to pick up the child. In response to this visit, the operator of the childcare facility, such as a childcare worker, makes preparations for the greeting, such as getting ready, and then greets the guardian.
[0003] Patent Document 1 describes a technique that assumes a nursery school and aims to "identify a person corresponding to a visitor (authenticated person) and provide a system or the like that can contribute to the smooth operation of a facility or the like." In Patent Document 1, in order to solve the above problem, as "a system for authenticating that a visitor 70 to a nursery school 1 (facility) is a guardian of a registered child (enrollee)", "guardian information including the characteristic information of the guardian and enrollee information, which is information about a child (enrollee) associated with the guardian, are stored", "the acquired characteristic information of the visitor 70 is compared with the characteristic information included in the guardian information stored in the storage unit", "the visitor 70 is authenticated as a guardian", "based on the enrollee information associated with the authenticated guardian, information about the child (enrollee) is output", and "the output information about the child (enrollee) is notified to the inside of the nursery school 1 (facility)" are described.
Prior Art Documents
Patent Documents
[0004]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0005] When parents pick up their children from daycare, they visit the facility, and the childcare worker assists them in preparing to go home. However, in the case of the technology described in Patent Document 1, the notification method involves notifying the entire facility, which means that the childcare worker in charge of a child is frequently required to check notifications for children who are not their assigned child (children assigned to other childcare workers), which can be time-consuming and make it difficult for them to focus on childcare duties.
[0006] Therefore, there is a need for technology that will make it even easier for children to prepare to go home after being picked up by their parents, and to allow their teachers to focus on their childcare duties. [Means for solving the problem]
[0007] According to one embodiment, a program is provided for operating a computer having one or more computer processors. The memory unit is configured to store information about the names of children using the childcare facility, information about the class to which the children belong at the childcare facility, and information for authenticating the children's guardians in association with each other. Notification means are installed in multiple locations at the childcare facility. The program causes one or more computer processors to perform the following steps: to detect that a child's guardian has come to the childcare facility based on the information for authenticating the guardian; to determine a notification destination related to the child from among multiple notification destinations at the childcare facility, based on the information about the child's class associated with the detected guardian; and to notify the notification means at the determined notification destination of at least one of the visiting guardian's information or the information of the guardian's child. [Effects of the Invention]
[0008] According to this disclosure, it will be possible to make preparations for children to go home after being picked up by their parents go more smoothly, and make it easier for the childcare worker in charge to concentrate on childcare duties. [Brief explanation of the drawing]
[0009] [Figure 1] Figure 1 shows the configuration of System 1. [Figure 2] Figure 2 shows the configuration of server 20. [Figure 3] Figure 3 shows the configuration of terminal 10. [Figure 4] Figure 4 shows the data structure of the child database 211. [Figure 5] Figure 5 shows the data structure of the parent database 212. [Figure 6] Figure 6 shows the data structure of the notification recipient management database 213. [Figure 7] Figure 7 shows the data structure of the childcare schedule database 214. [Figure 8] Figure 8 shows the data structure of the childcare record management database 215. [Figure 9] Figure 9 shows the data structure of the parent visit history database 216. [Figure 10] Figure 10 shows the data structure of the notification history database 217. [Figure 11] Figure 11 shows the process flow for receiving online registration of authentication information from parents / guardians. [Figure 12] Figure 12 shows the process flow for notifying the childcare facility of a parent's visit, with the child's class being notified as the recipient. [Figure 13] Figure 13 shows the process flow for predicting and notifying parents of the time they will be visiting to pick up their children. [Figure 14] Figure 14 shows an example of a screen that notifies a parent or guardian that they have arrived to pick up their child. [Figure 15] Figure 15 shows an example of a screen displaying the child's childcare record to visiting parents. [Figure 16]FIG. 16 is a diagram showing the data structure of the suspicious person detection history database 218. [Figure 17] FIG. 17 is a diagram showing the data structure of the facility safety score database 219. [Figure 18] FIG. 18 is a diagram showing the flow of a process for detecting a suspicious person, sending a notification, and evaluating the safety of a facility. [Figure 19] FIG. 19 is a diagram showing the flow of a process for authenticating that a child has entered a room and sending a notification to a guardian. [Figure 20] FIG. 20 is an example screen showing the result of evaluating the safety presented to a facility manager or a guardian. [Figure 21] FIG. 21 is an example screen for notifying a guardian's terminal that a student has entered a learning facility.
Mode for Carrying Out the Invention
[0010] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all the drawings for describing the embodiments, common components are denoted by the same reference numerals, and repeated descriptions are omitted. Note that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Also, not all the components shown in the embodiments are essential components of the present disclosure. Further, each figure is a schematic diagram and is not necessarily drawn precisely.
[0011] Also, in the following description, the "processor" is one or more processors. At least one processor is typically a microprocessor such as a CPU (Central Processing Unit), but may also be another type of processor such as a GPU (Graphics Processing Unit). At least one processor may be single-core or multi-core.
[0012] Furthermore, at least one processor may be a broad-sense processor, such as a hardware circuit that performs some or all of the processing (e.g., an FPGA (Field-Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit)).
[0013] Furthermore, in the following explanation, we may use expressions such as "xxx table" to describe information that yields an output for a given input. This information can be data with any structure, or it can be a learning model such as a neural network that generates an output for a given input. Therefore, "xxx table" can be referred to as "xxx information."
[0014] Furthermore, in the following explanation, the structure of each table is just an example; one table may be divided into two or more tables, or all or part of two or more tables may be a single table.
[0015] Furthermore, in the following explanation, the subject of the process may sometimes be "program," but since a program is executed by a processor and performs defined processes using the memory and / or interface as appropriate, the subject of the process may also be the processor (or a device such as a controller that has that processor).
[0016] The program may be installed on a device such as a computer, or it may reside on a program distribution server or a computer-readable (e.g., non-temporary) recording medium. Furthermore, in the following description, two or more programs may be implemented as a single program, or one program may be implemented as two or more programs.
[0017] Furthermore, in the following explanation, identification numbers are used as identification information for various objects, but other types of identification information (for example, identifiers including letters or symbols) may also be used.
[0018] Furthermore, in the following explanations, when describing similar elements without distinction, a reference code (or a common code among reference codes) may be used, and when describing similar elements with distinction, the element's identification number (or reference code) may be used.
[0019] Furthermore, in the following explanation, only control lines and information lines deemed necessary for the explanation are shown, and not all control lines and information lines in the product are necessarily shown. All components may be interconnected.
[0020] <Outline of the Embodiment> The embodiments will be described below.
[0021] <1.1 System Configuration Diagram> Figure 1 shows the configuration of System 1.
[0022] The system 1 shown in Figure 1 includes a terminal 10 for users (such as parents) of the childcare facility 30, a terminal 10B for users (such as childcare workers) who operate the childcare facility 30, a server 20, detection means (such as cameras) 31 installed in the childcare facility 30, multiple notification means 32 (in the illustrated example, notification means 32A, notification means 32B, etc., such as signage, tablets, etc., installed in one or more classes to which children belong in the childcare facility 30), a reader (such as an IC card reader) 33, and an artificial intelligence service server 95 (which may also be referred to as the "large-scale language model service server 95"). Each of these devices communicates via the network 80.
[0023] In the illustrated example, one terminal 10 is shown as the terminal used by users of the childcare facility 30, but each user is operating their own terminal.
[0024] In this embodiment, each device (terminal device, server, etc.) can also be considered as an information processing device. That is, the collection of each device can be considered as a single "information processing device," and System 1 may be formed as a collection of multiple devices. The way in which the multiple functions required to realize System 1 according to this embodiment are distributed to one or more hardware can be appropriately determined in view of the processing capacity of each hardware and / or the specifications required for System 1.
[0025] Terminal 10 is a device operated by the user. Terminal 10 can be implemented, for example, as follows: • Handheld mobile devices such as smartphones and tablets • Stationary PCs (Personal Computers), Laptop PCs • Wearable devices worn by the user (watch-type, glasses-type, etc.) Terminal 10 includes a communication interface (IF) 12, an input device 13, an output device 14, memory 15, storage 16, and a processor 19.
[0026] The communication interface 12 is an interface for inputting and outputting signals so that terminal 10 can communicate with an external device.
[0027] The input device 13 is a device for receiving input operations from the user (for example, a touch panel, touchpad, pointing device such as a mouse, keyboard, etc.).
[0028] The output device 14 is a device (such as a display or speaker) for presenting information to the user.
[0029] Memory 15 is for temporarily storing programs and data processed by programs, etc., and is a volatile memory such as DRAM (Dynamic Random Access Memory).
[0030] Storage 16 is for storing data, and can be, for example, flash memory or an HDD (Hard Disk Drive).
[0031] The processor 19 is hardware for executing the instruction set described in the program, and consists of an arithmetic unit, registers, peripheral circuits, etc.
[0032] Server 20 is a system that processes information such as registration of parents who use childcare facilities 30.
[0033] The server 20 includes a communication interface 22, an input / output interface 23, memory 25, storage 26, and a processor 29.
[0034] Communication IF22 is an interface for inputting and outputting signals so that the server 20 can communicate with external devices.
[0035] Input / Output IF23 functions as an interface between an input device for receiving user input operations and an output device for presenting information to the user.
[0036] Memory 25 is for temporarily storing programs and data processed by programs, etc., and is a volatile memory such as DRAM (Dynamic Random Access Memory).
[0037] Storage 26 is for storing data, and can be, for example, flash memory or an HDD (Hard Disk Drive).
[0038] The processor 29 is hardware for executing the instruction set described in the program, and consists of an arithmetic unit, registers, peripheral circuits, etc.
[0039] Childcare facility 30 is a facility that provides childcare to children in one or more classes (for example, classes classified according to age) while managing entry and exit by authenticating visitors at the entrance. The following methods may be used to authenticate visitors at childcare facility 30. A camera (detection means 31) installed at the entrance performs facial recognition of visitors, and if the visitor is pre-registered, the door is unlocked and entry is permitted. • By communicating with the NFC (Near Field Communication) chip on the parent's device to a reader such as an IC card reader (reader 33) installed at the entrance, the door is unlocked and entry is permitted, as it recognizes that a pre-registered parent has arrived. The parent's device 10 accesses a short-range wireless communication access point, such as a Wi-Fi access point, installed at the entrance of the childcare facility 30. The parent's device 10 displays an application or website and accesses the access point while authenticating the parent (user ID, password, etc.) (the application may perform parent authentication in advance), thereby unlocking the door and granting entry. Furthermore, in the case of parents picking up their children from childcare facility 30 by car, a camera installed at the entrance can photograph the vehicle, and if it is a vehicle that has been registered in advance (for example, by reading the license plate and confirming that it is a license plate that has been registered in advance), it can be considered that the parent has arrived. At this time, authentication may be performed based on the result of photographing the vehicle, and once it is determined that it is the parent's vehicle, the door may be unlocked (allowing the vehicle to enter) to allow the vehicle to pass through.
[0040] The childcare facility 30 has a playground and a building with multiple rooms, and each of the multiple rooms is associated with a class in order to provide childcare to children in one or more classes. In each class, notification means 32 such as signage terminals, tablet terminals, and speakers may be installed, or a tablet terminal may be installed (in the illustrated example, an example is shown in which multiple notification means 32 are installed, such as notification means 32A, notification means 32B, etc.). For example, a control terminal with communication functions can be connected to a monitor to make it a signage terminal. The information from these signage and tablets in each class is managed (in the notification destination management database 213 described later). The childcare facility 30 also has common areas such as an entrance, a hall, and a playground, and terminals such as signage, tablets, and speakers may be installed in these common areas as well. The signage terminal is installed in the classroom and has a certain display area so that the information displayed on the signage terminal can be seen from inside the classroom.
[0041] <1.2 Functional Configuration of Server 20> Figure 2 shows the configuration of server 20. As shown in Figure 2, server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.
[0042] The communications unit 201 performs processing to enable the server 20 to communicate with external devices.
[0043] The memory unit 202 stores various databases, including a child database 211, a parent database 212, a notification recipient management database 213, a childcare schedule database 214, a childcare record management database 215, a parent visit history database 216, and a notification history database 217.
[0044] The child database 211 is a database that manages information such as the child's name, the child's guardian, the class the child belongs to at the childcare facility 30, and the childcare worker in charge. Further details will be provided later.
[0045] The parent / guardian database 212 is a database that manages the names of children's guardians, information for guardian authentication, and information about the children of those guardians. Further details will be provided later.
[0046] The notification recipient management database 213 is a database that manages information on who to notify when a child's guardian visits the childcare facility 30 to pick up their child. Further details will be provided later.
[0047] The childcare schedule database 214 is a database that manages information such as time slots and activity locations as part of the childcare schedule at the childcare facility 30. Further details will be provided later.
[0048] The childcare record management database 215 is a database for managing records such as daily logs of childcare provided at childcare facilities 30. Further details will be provided later.
[0049] The Parent Visit History Database 216 is a database that manages the history of visits by parents to the childcare facility 30 to pick up their children. Further details will be provided later.
[0050] The notification history database 217 is a database that manages the history of notifications made by parents to the childcare facility 30 when they visit the facility to pick up their children. Further details will be provided later.
[0051] The control unit 203 is realized when the processor 29 reads a program stored in the memory unit 202 and executes instructions contained in the program. By operating according to the program, the control unit 203 performs the functions indicated by the reception control module 2041, transmission control module 2042, user management module 2043, notification destination management module 2044, schedule management module 2045, childcare record management module 2046, and visitor notification module 2047.
[0052] The receive control module 2041 controls the process by which the server 20 receives signals from external devices according to a communication protocol.
[0053] The transmission control module 2042 controls the process by which the server 20 transmits signals to external devices according to a communication protocol.
[0054] The user management module 2043 is a program module that manages information on various users, such as users who use the childcare facility 30 and users who operate the childcare facility 30, and performs processing to update the child database 211, the parent database 212, etc.
[0055] The notification destination management module 2044 is a program module that manages notification destinations (digital signage, tablets, childcare workers' terminals, etc.) for notifying parents when it is time to pick up their children at the childcare facility 30, and updates the notification destination management database 213.
[0056] The schedule management module 2045 is a program module that receives registration of childcare schedules at the childcare facility 30 and updates the childcare schedule database 214.
[0057] The childcare record management module 2046 is a program module that receives registration of childcare records for children at the childcare facility 30 and updates the childcare record management database 215.
[0058] The visitor notification module 2047 is a program module that, when a parent visits the childcare facility 30 to pick up a child, notifies various devices such as the notification means 32 at the childcare facility 30 and the childcare worker's terminal 10B, and updates the notification history database 217.
[0059] <1.3 Configuration of Terminal 10> Figure 3 shows the configuration of terminal 10.
[0060] As shown in Figure 3, terminal 10 includes multiple antennas (antenna 111, antenna 112), communication units corresponding to each antenna (first communication unit 120, second communication unit 121), an input device 130 (including a touch-sensitive device 131), a display 132, an audio processing unit 140, a microphone 141, a speaker 142, a position information sensor 150, a camera 160, a motion sensor 170, a storage unit 180, and a control unit 190. Terminal 10 also has functions and configurations not specifically shown in Figure 3 (for example, a battery for maintaining power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.). As shown in Figure 3, each block included in terminal 10 is electrically connected by a bus or the like.
[0061] Antenna 111 radiates signals emitted by terminal 10 as radio waves. Antenna 111 also receives radio waves from space and provides the received signals to first communication unit 120.
[0062] Antenna 112 radiates signals emitted by terminal 10 as radio waves. Antenna 112 also receives radio waves from space and provides the received signals to the second communication unit 121.
[0063] The first communication unit 120 performs modulation and demodulation processing, etc., for the terminal 10 to transmit and receive signals via the antenna 111 in order to communicate with other wireless devices. The second communication unit 121 also performs modulation and demodulation processing, etc., for the terminal 10 to transmit and receive signals via the antenna 112 in order to communicate with other wireless devices. The first communication unit 120 and the second communication unit 121 are a communication module that includes a tuner, an RSSI (Received Signal Strength Indicator) calculation circuit, a CRC (Cyclic Redundancy Check) calculation circuit, a high-frequency circuit, etc. The first communication unit 120 and the second communication unit 121 perform modulation and demodulation, frequency conversion, etc., of the wireless signals transmitted and received by the terminal 10, and provide the received signal to the control unit 190.
[0064] The input device 130 has a mechanism for receiving user input operations. Specifically, the input device 130 is configured as a touchscreen and includes a touch-sensitive device 131. The touch-sensitive device 131 receives user input operations of the terminal 10. The touch-sensitive device 131 detects the user's contact position with the touch panel, for example, by using a capacitive touch panel. The touch-sensitive device 131 outputs a signal indicating the user's contact position detected by the touch panel to the control unit 190 as an input operation.
[0065] The display 132 displays data such as images, videos, and text in accordance with the control of the control unit 190. The display 132 is implemented by, for example, an LCD or an organic EL display.
[0066] The audio processing unit 140 modulates and demodulates the audio signal. The audio processing unit 140 modulates the signal received from the microphone 141 and provides the modulated signal to the control unit 190. The audio processing unit 140 also provides the audio signal to the speaker 142. The audio processing unit 140 is implemented, for example, by an audio processing processor. The microphone 141 receives an audio input and provides the audio signal corresponding to that audio input to the audio processing unit 140. The speaker 142 converts the audio signal received from the audio processing unit 140 into sound and outputs the sound to the outside of the terminal 10.
[0067] The location information sensor 150 is a sensor that detects the location of the terminal 10, and is, for example, a GPS (Global Positioning System) module. A GPS module is a receiving device used in a satellite positioning system. In a satellite positioning system, signals are received from at least three or four satellites, and the current location of the terminal 10, which is equipped with a GPS module, is detected based on the received signals.
[0068] Camera 160 is a device that receives light using a photodetector and outputs it as an image. Camera 160 is, for example, a depth camera that can detect the distance from camera 160 to the object being photographed.
[0069] The motion sensor 170 includes an acceleration sensor, an angular velocity sensor, etc., and detects the movement of the terminal 10.
[0070] The storage unit 180 is composed of, for example, flash memory and stores data and programs used by the terminal 10. The various types of information stored in the storage unit 180 will be described later.
[0071] The control unit 190 controls the operation of the terminal 10 by reading the program stored in the memory unit 180 and executing the instructions contained in the program. The control unit 190 is, for example, an application processor. By operating according to the program, the control unit 190 controls the operation reception unit 191, the transmission / reception unit 192, the data processing unit 193, and the notification control unit 1 It functions as both 94 and memory control unit 195.
[0072] The operation reception unit 191 processes input operations from the user to an input device such as a touch-sensitive device 131. Based on the coordinate information of the touch-sensitive device 131 where the user's finger or the like has made contact, the operation reception unit 191 determines the type of operation, such as whether the user's operation is a flick operation, a tap operation, or a drag (swipe) operation.
[0073] The transmitting / receiving unit 192 performs processing to enable the terminal 10 to send and receive data with an external device such as a server 20 in accordance with a communication protocol.
[0074] The data processing unit 193 performs calculations on the data received as input by the terminal 10 according to the program and outputs the calculation results to memory or other locations.
[0075] The notification control unit 194 performs the following processes: displaying the display image on the display 132, outputting sound to the speaker 142, and generating vibrations.
[0076] The memory control unit 195 controls the storage of data to the memory unit 180.
[0077] The various types of information stored by the memory unit 180 will now be explained. In a certain situation, the memory unit 180 stores user information 181.
[0078] User information 181 is information about a user who uses the services provided by server 20.
[0079] <2 Data Structure> Figure 4 shows the data structure of the child database 211. The child database 211 includes the following fields: "Child ID", "Child Name", "Class ID", "Class Name", "Parent ID", "Teacher ID", "Teacher Name", "Date of Birth", "Gender", and "Emergency Contact Information".
[0080] The item "Child ID" is an ID used to uniquely identify a child.
[0081] The field "Child's Name" should be the child's full name.
[0082] The item "Class ID" is an ID that identifies the class to which the child belongs.
[0083] The item "Class Name" is the name of the class to which the child belongs.
[0084] The item "Guardian ID" is an ID used to identify the child's guardian.
[0085] The item "Homeroom Teacher ID" is an ID used to identify the teacher in charge of a child.
[0086] The item "Name of the assigned childcare worker" is the name of the assigned childcare worker.
[0087] The item "Date of Birth" contains information about the child's date of birth.
[0088] The item "Gender" refers to the child's gender.
[0089] The item "Emergency Contact" is a phone number to be contacted in case of an emergency.
[0090] Figure 5 shows the data structure of the parent database 212. The parent database 212 includes the fields "Parent ID", "Parent Name", "Authentication Data", "Related Child ID", "Authentication Code", "Telephone Number", and "Email Address".
[0091] The "Guardian ID" field is an ID used to uniquely identify the guardian.
[0092] The field "Parent / Guardian Name" should be the parent / guardian's full name.
[0093] The item "Authentication Data" is the data used for parental authentication.
[0094] The item "Authentication Data" preferably consists of "Feature Vector" data extracted from the guardian's facial image. During registration and authentication, Server 20 generates multidimensional (e.g., 128-dimensional or 512-dimensional) vector data from the facial image, quantifying the positional relationships of the eyes, nose, and mouth. For authentication and re-identification (Re-ID), the system determines whether the person is the same by calculating the "Euclidean distance" or "cosine similarity" between these vector data. This makes it difficult to reconstruct the original facial image from the numerical data even if the database information is leaked, thus enhancing the level of protection for personal information.
[0095] (1) For example, if the appearance of the guardian, such as the guardian's face, is used for authentication, it may be facial image data used for facial recognition. Also, if an object owned by the guardian, such as a vehicle used to pick up the child, is used for authentication, it may be information about the appearance of the object, such as the vehicle's license plate. Thus, the authentication data used to authenticate the guardian may be information detected by the detection means 31, such as a camera.
[0096] (2) Furthermore, when authentication is performed using identification information embedded in an IC chip or the like on a device owned by a guardian (for example, information stored on a medium readable by the reader 33), such identification information may be authentication information. Thus, the authentication data used to authenticate a guardian may be information obtained through communication between devices by a reader 33 such as an IC card reader.
[0097] (3) Information used to authenticate a guardian may include the guardian's user ID (for example, an email address may be used as the user ID) and password. For example, a wireless communication access point, such as a Wi-Fi access point, may be installed near the entrance of the childcare facility 30, and the guardian's terminal 10 may be able to access the access point even outside the childcare facility 30. The guardian's terminal 10 may access the access point, display a default page in the browser on the terminal 10, or accept a login through the processing of an application running on the terminal 10, and authenticate the guardian by comparing it with the user ID and password provided by the terminal 10.
[0098] The item "Related Child ID" is the ID of the child associated with the guardian. It is the ID of the child the guardian will pick up.
[0099] The item "Authentication Code" is a code issued for identity verification when registering authentication data. For example, it is the identity verification code when registering a parent's facial recognition data. In a device installed inside the childcare facility 30, the data used for parent authentication is not stored. Instead, the server 20, which operates outside the childcare facility 30, issues the authentication code and receives authentication data from the parent, storing the authentication data. This way, the childcare facility 30 itself does not store data for authenticating the parent. When authenticating a parent, the authentication result is obtained from the server 20 by sensing the parent's information (such as the results of the parent's facial image capture as described above).
[0100] The item "Phone Number" is the contact phone number of the parent or guardian.
[0101] The item "Email Address" is the parent's email address.
[0102] Figure 6 shows the data structure of the notification recipient management database 213. The notification recipient management database 213 includes the items "Class ID", "Signage ID", "Tablet Terminal ID", "Childcare Worker Terminal ID", "Notification Recipient Type", and "Notification Method".
[0103] The item "Class ID" is an ID used to identify the class to which a child belongs.
[0104] The item "Signage ID" is an ID that identifies the signage terminal within the facility. In this way, an ID that identifies the signage terminal is maintained in association with an ID that identifies the class, making it possible to identify the signage terminal installed in a class.
[0105] The item "Tablet Device ID" is an ID that identifies a tablet device within a class. In this way, an ID that identifies a tablet device is maintained in association with an ID that identifies the class, making it possible to identify the tablet devices installed in the class.
[0106] The item "Childcare Worker Terminal ID" is the ID of the terminal (such as a smartphone) used by the childcare worker. In this way, an ID is maintained that identifies the terminal used by the childcare worker, associated with the ID that identifies the class, making it possible to identify the terminal of the childcare worker in charge of the class.
[0107] The item "Notification Recipient Type" contains information about the type of recipient (digital signage, tablet, childcare worker's terminal, etc.).
[0108] The item "Notification Method" refers to the method of notification (display, sound, vibration, etc.).
[0109] Figure 7 shows the data structure of the childcare schedule database 214. The childcare schedule database 214 includes the items "Time Slot", "Location ID within the facility", "Location Name within the facility", "Class ID", and "Activity Details".
[0110] The "Time Slot" field contains information about the time slots in which classes and children are active. Although not shown in the diagram, the "Time Slot" field may also store date information. In other words, it may accept registration of schedules for each date and manage them in the childcare schedule database 214.
[0111] The item "Location ID within the facility" is an ID that identifies the location where the activity takes place. This ID may be associated with the item "Class ID" in the notification recipient management database 213.
[0112] The item "Name of location within the facility" is the name of the place where the activity takes place.
[0113] The "Class ID" field is an ID that identifies the active class.
[0114] The item "Activity Details" contains information about the specific activities performed during a given time period.
[0115] Figure 8 shows the data structure of the childcare record management database 215. The childcare record management database 215 includes the fields "Diary ID", "Child ID", "Childcare Worker ID", "Diary Text", "Diary Image", and "Record Date and Time".
[0116] The item "Diary ID" is an ID used to uniquely identify the diary entries recorded by childcare workers.
[0117] The item "Child ID" is an ID used to identify the child being recorded.
[0118] The item "Childcare Worker ID" is an ID used to identify the childcare worker who recorded the daily log.
[0119] The item "Diary Text" refers to the text content of the diary recorded by the childcare worker.
[0120] The item "Logbook Images" refers to image data (such as photographs) attached to the logbook.
[0121] The item "Record Date and Time" is the date and time the log entry was made.
[0122] Figure 9 shows the data structure of the parent visit history database 216. The parent visit history database 216 includes the fields "Visit History ID", "Parent ID", "Visit Date and Time", "Authentication Method", and "Authentication Success Flag".
[0123] The item "Visit History ID" is an ID used to uniquely identify a parent's visit history.
[0124] The "Parent ID" field is an ID used to identify the visiting parent. It may be associated with the "Parent ID" field in Parent Database 212.
[0125] The item "Date and Time of Visit" is the date and time when the parent / guardian visited and successfully completed the authentication process.
[0126] The "Authentication Method" field contains information about the method used to detect and authenticate the visitor's presence (e.g., facial recognition, license plate recognition).
[0127] The "Authentication Success Flag" item is a flag that indicates whether authentication was successful or not.
[0128] Figure 10 shows the data structure of the notification history database 217. The notification history database 217 includes the items "Notification History ID", "Visitor History ID", "Notification Date and Time", "Notification Recipient ID", "Notification Content", and "Notification Result".
[0129] The item "Notification History ID" is an ID used to uniquely identify the execution history of notifications.
[0130] The item "Visit History ID" is the visit history ID of the associated guardian. It may also be associated with the item "Visit History ID" in the Guardian Visit History Database 216.
[0131] The item "Notification Date and Time" indicates the date and time the notification was issued.
[0132] The "Notification Recipient ID" field is the ID of the terminal or signage that received the notification. It may also be associated with the "Signage ID," "Tablet Terminal ID," and "Childcare Worker Terminal ID" fields in the notification recipient management database 213.
[0133] The item "Notification Content" contains information about the specific details announced in the notification.
[0134] The "Notification Result" item indicates the status of the notification result (success, failure, etc.).
[0135] <3 operations> Figure 11 shows the process flow for receiving online registration of authentication information from parents. Note that the following explanation describes an example where parents register their authentication information using a service provided by server 20, rather than the childcare facility performing the registration process. This allows the childcare facility to store the authentication information on server 20 rather than having to retain it themselves. Alternatively, staff at the childcare facility may perform the registration process for parents at the facility.
[0136] In step S1111, terminal 10 accepts an operation from the parent to enter an authentication code provided to the parent by the childcare facility on an operation screen (web page or app) for registering authentication information (e.g., facial image). The authentication code may be issued by server 20. Terminal 10 also accepts an operation to take a picture of or upload authentication information (facial image data necessary for facial recognition, image of the vehicle driven by the parent to pick up the child (license plate, etc.)).
[0137] For example, the server 20 is configured to store facial information for facial recognition of parents as information for authenticating the parents of children in the parent database 212 of the storage unit 202. The user management module 2043 provides the parent's terminal 10 with an operation screen to accept registration of facial images for facial recognition. The user management module 2043 issues an authentication code associated with the childcare facility to the parent who registers the facial image.
[0138] In step S1112, terminal 10 sends the authentication code and authentication information (such as facial image data) entered by the user to server 20.
[0139] In step S1121, the user management module 2043 of server 20 verifies the received authentication code and confirms the legitimacy of the parent.
[0140] In step S1122, if authentication is successful, the user management module 2043 of server 20 stores the authentication information (such as facial image data) in the parent database 212, linked to the parent's identification information (parent ID). The user management module 2043 also updates the child database 211 associated with the parent, establishing the association between the parent and child.
[0141] In this way, the user management module 2043 registers authentication information for the guardians of children using the childcare facility by receiving the issued authentication code from the guardians who register the facial image.
[0142] In step S1123, the server 20 sends a registration completion notification to the parent's terminal 10.
[0143] In step S1113, terminal 10 receives a notification from server 20 and displays a screen indicating that registration is complete.
[0144] Figure 12 shows that when a parent visits the childcare facility, the class in which the child is located is notified to the facility. This diagram shows the process for notifying parents of their visit.
[0145] In step S1221, the visitor notification module 2047 of the server 20 acquires authentication information (such as facial image data) captured by the camera, compares it with the parent database 212, and authenticates the parent.
[0146] Server 20 is configured to store information about the names of children using the childcare facility, information about the class to which the child belongs at the childcare facility, and information for authenticating the child's guardian in association with each other in the child database 211 and guardian database 212 of the storage unit 202. Notification means 32 (notification means 32A, notification means 32B, ... in Figure 1) are installed in multiple locations in the childcare facility 30. The visitor notification module 2047 detects when a child's guardian has come to the childcare facility based on the information for authenticating the guardian.
[0147] (Method for detecting when a parent or guardian has arrived)
[0148] (1) Taking a photograph of the subject to be authenticated using a camera. Here, as a method for detecting when a parent has come to the childcare facility 30, for example, a camera acting as a detection means 31 installed at the entrance of the childcare facility 30 may be used to photograph the parent and perform facial recognition of the parent, or a specific object the parent is carrying (such as the license plate of the vehicle the parent drives to pick up the child) may be photographed to detect the parent's arrival.
[0149] As described above, a camera is installed at the entrance of the childcare facility 30. The visitor notification module 2047 detects when a parent has entered the childcare facility by photographing the parent's face or a specific object the parent is holding with the camera at the entrance of the childcare facility 30 and comparing it with authentication information.
[0150] (2) Parental authentication information registered for unlocking the door Here, as a method for detecting when a parent or guardian has arrived at the childcare facility 30, a means of unlocking the door at the entrance of the childcare facility 30 may be used. For example, the IC chip that the parent possesses is connected to the IC card reader installed on the entrance door.
[0151] (The childcare facility registers the parent's IC chip identification information in advance.) • Wireless communication devices such as Wi-Fi access points and Bluetooth® communication devices will be installed near the entrance door, and communication will be possible even outside the door. Parents will access these wireless communication devices on their devices and authenticate using a user ID, password, etc. Thus, the server 20 is configured to store authentication information for each user of the childcare facility 30 in the parent database 212 of the storage unit 202, which is used to unlock the door when entering the childcare facility 30. A reader 33 that reads the information via short-range wireless communication is installed at the entrance of the childcare facility 30.
[0152] The visitor notification module 2047 causes the reader 33, which is installed at the entrance of the childcare facility 30, to read the identification information of the terminal 10 held by the guardian when the terminal 10 and the reader 33 are within a certain distance of each other. Here, the determination of "within a certain distance" can be made by, for example, the received signal strength indicator (RSSI) of radio waves such as Bluetooth® Low Energy (BLE) transmitted from the terminal 10. The reader 33 (or a cooperating receiver) measures the RSSI of the radio waves from the terminal 10, and when the value reaches a predetermined threshold (e.g., -60 dBm or higher), it is considered that the guardian has approached with the intention of unlocking the door, and the authentication process is started. This prevents false detection of guardians who are simply passing by the facility. Alternatively, the system may detect that a guardian has arrived by comparing the information obtained from the visitor detection result with the authentication information for unlocking the door.
[0153] Furthermore, since radio wave strength is easily affected by environmental factors, the visitor notification module 2047 uses a "moving average filter" or "hysteresis control" to prevent false detections and chattering (frequent switching between detected and undetected states). Specifically, instead of making a determination based solely on the instantaneous RSSI value, it determines a visitor's presence only when the average RSSI value over the past few seconds exceeds a threshold, or when signals exceeding the threshold are received "a specified number of times (e.g., 5 times) or more consecutively within a specified time (e.g., 3 seconds)". In addition, once a visitor's presence has been determined, even if the RSSI value falls below the determination threshold, it is not immediately considered a "departure." A certain holding time is set, or the threshold for canceling the notification is set lower than the threshold for the determination, thereby preventing excessive notifications.
[0154] In step S1222, the visitor notification module 2047 of server 20 obtains the child ID and class ID associated with the guardian upon successful authentication. The visitor notification module 2047 refers to the childcare schedule database 214 and determines the appropriate notification destination (such as the child's classroom signage or the homeroom teacher's terminal) based on the current time and location information within the facility.
[0155] In this way, the visitor notification module 2047, based on the information of the child's class associated with the parent whose visit has been detected, determines the notification destination relevant to the child (for example, the signage in the child's class) from among multiple notification destinations at the childcare facility 30 (for example, installing signage in each class, installing speakers at the entrance of the childcare facility 30, the playground, etc.) to inform the child's parent that they have visited the childcare facility 30.
[0156] The visitor notification module 2047 refers to the parent database 212 and, if there are multiple child IDs associated with the detected parent (in the case of siblings), identifies all of the multiple class IDs to which each child belongs as targets for notification. In this case, the visitor notification module 2047 notifies the notification means 32 of the identified multiple classes using either "multicast" or "sequential transmission". Specifically, it generates a message that displays "the older brother's name" on the signage of the "Sunflower Class" to which the older brother belongs, and simultaneously displays "the younger brother's name" on the signage of the "Dandelion Class" to which the younger brother belongs, allowing the parent to complete contact with all teachers with a single authentication operation.
[0157] In step S1223, the visitor notification module 2047 of server 20 generates a notification. (Example of notification content: "Mr. Yamada T. from Sunflower Class is here to pick you up.")
[0158] (Content to be notified) The visitor notification module 2047 notifies the recipient determined in step S1222 of at least one of the parent's or child's name, along with information about the child's class. (Example of notification content: "Mr. / Ms. ●● from class ●●, your parent / guardian has come to pick you up." Note that server 20 allows various honorifics such as "chan," "kun," and "san" to be set for children.) The child database 211 of the memory unit 202 is configured to store information about the class to which a child belongs, including the name of the class. The visitor notification module 2047 may also generate notification information by referring to the information about the class to which a child belongs, combining at least one of the parent's name or the name of the parent's child with the name of the class to which the child belongs, and then notify the determined recipient of the generated notification information.
[0159] In step S1224, the visitor notification module 2047 of the server 20 sends the notification content to the determined notification destination terminal.
[0160] In this manner, the visitor notification module 2047 notifies the designated notification means (notification means 32) of at least one of the visiting guardian's information or the information of the guardian's child.
[0161] (1) How to determine who will be notified: Notifications will be sent to the class's terminals. In the notification recipient management database 213, the class to which a child belongs is associated with the identification information of the terminal (signage, tablet) placed in that class. The visitor notification module 2047 uses the terminal in the class of the visiting parent's child as the notification recipient.
[0162] More specifically, the notification destination management database 213 of the memory unit 202 is configured to store identification information of output terminals (notification means 32A, 32B, ...) installed in each class of the childcare facility 30. The visitor notification module 2047 determines the notification destination related to the child of the visiting parent by referring to the notification destination management database 213, and from among multiple notification destinations, it determines the output terminal installed in the class to which the child belongs as the notification destination. The visitor notification module 2047 uses different notification methods for the output terminal in the class to which the determined child belongs and for the output terminal in the class to which the child does not belong, thereby notifying at least one of the visiting parent's information or the parent's child's information.
[0163] As a specific difference in notification methods, the visitor notification module 2047 may send a control signal to the notification means 32 (signage, etc.) of the class to which the visiting child belongs, causing a chime sound to ring and highlighting the parent's name and the child's name in the center of the screen (pop-up display, etc.) (highlight mode). On the other hand, to the notification means 32 of other classes to which the child does not belong, a control signal may be sent that is silent and displays only an icon or text in the corner of the screen so as not to disrupt childcare activities (silent mode). This ensures that the visit is recognized only by childcare workers in the relevant classes without interfering with the work of childcare workers in unrelated classes. In this way, by differentiating the notification methods, the content of the information to be notified may be the same for each class, but the visual presentation may differ within each class, for example, by highlighting the size and position of the child's name in the class to which the visiting child belongs, while not doing so in other classes. Alternatively, the notification method may be auditorily different for the class to which the visiting child belongs and for other classes.
[0164] As a specific difference in notification methods, the visitor notification module 2047 sends a control signal including an "Interrupt Flag = True" and a "Volume = High" command to the notification means 32 of the class to which the visiting child belongs (target class). As a result, the signage in the target class displays the parent's name and the child's name as a pop-up in the center of the screen, regardless of the current display content, and a notification sound is played. On the other hand, to the notification means 32 of other classes to which the child does not belong (non-target classes), a control signal including a "Ticker Flag = True" and a "Mute Command (Volume = Mute)" is sent. As a result, in other classes, only text information is displayed scrolling at the bottom of the screen so as not to disrupt childcare activities, and no notification sound is played (or only vibration is activated). In this way, by dynamically changing the control command for each notification destination, optimal notification according to location is achieved even for the same detection event.
[0165] (2) How to determine who will be notified: Notification will be sent to the terminal of the childcare worker in charge of the class. In the notification recipient management database 213, the class to which a child belongs is associated with the identification information (user account, etc.) of the teacher (nursery teacher) in charge of the child's class (smartphone app, etc.). The visitor notification module 2047 uses the teacher's device as the notification recipient.
[0166] More specifically, the notification destination management database 213 of the memory unit 202 is configured to store identification information of terminals held by operators in charge of each class at the childcare facility 30. The visitor notification module 2047 determines the notification destination related to the child of the visiting parent, and from among multiple notification destinations, it selects the terminal of the operator in charge of the class to which the child belongs as the notification destination. The visitor notification module 2047 uses different notification methods for the terminal of the operator in charge of the class to which the selected child belongs and the terminal of the operator who does not have such a terminal, thereby notifying at least one of the information of the visiting parent or the information of the parent's child.
[0167] In notifying terminals 10B (smartphones, etc.) held by operators such as childcare workers, the visitor notification module 2047 uses the OS-provided "Notification Channel" or "Importance Flag" for control. Specifically, it sends a push notification with the "Critical Alert" or "High Priority" attribute to the terminal of the child's assigned caregiver when a visitor arrives. This forces the notification sound and vibration to activate and displays the notification at the forefront of the screen, even if the terminal is set to silent mode (vibration mode). On the other hand, it sends a notification with the "Default" or "Silent" attribute to the terminal of a caregiver who is not assigned to the child, displaying it only in the notification center (history) to avoid interrupting work with sound or vibration.
[0168] (3) Method for determining who to notify: Notification based on the child's position on the schedule. The visitor notification module 2047 matches the child's schedule information (time of day and location) at the childcare facility 30 and notifies the parent or guardian of their scheduled location at the time of their visit (or when their visit is detected).
[0169] The childcare schedule database 214 in the memory unit 202 is configured to store schedule information for each class of children, including information about the locations the children use for each time slot. The visitor notification module 2047 refers to the schedule information from among multiple notification destinations and determines the location the child is using as the notification destination based on the timing when it is detected that a parent has arrived.
[0170] (4) Notification of pick-up time according to the location within the childcare facility 30 Here, depending on the location, it may be possible to differentiate the distribution of information, either by informing all visitors of the parents who have come to the facility, or by informing each class that the parents of the children enrolled in that class have come to visit. For example, depending on the recipient, such as the area near the entrance or hall of childcare facility 30, it may be possible to inform all visitors and children who come to childcare facility 30.
[0171] The visitor notification module 2047 may, when installed in a specific location in the childcare facility 30 (for example, near the entrance or in the playground, in a place other than the classroom where the child is enrolled), notify at least one of the information of the parent whose visit has been detected or the information of the parent's child, regardless of the child's class. On the other hand, when installed in a location other than a specific location, the notification may be made according to the notification destination determined in step S1222.
[0172] (5) Notification of pick-up time according to the time of day Here, the visitor notification module 2047 may either notify all visiting parents or send notifications to each class depending on the time of day. For example, the visitor notification module 2047 may notify all visiting parents during certain time periods. For example, depending on the time of day, there may be irregular pick-up times that differ from the usual pick-up times for children. Also, as time progresses, children waiting to be picked up by their parents may be gathered into one class. If such specific time periods are set and the time falls within those specific time periods, the visitor notification module 2047 may decide to notify multiple recipients of the childcare facility 30 (e.g., all classes), regardless of the recipients determined based on the information of the child's class associated with the detected visitor. The visitor notification module 2047 may, during certain time periods, notify multiple determined recipients of at least one of the detected parent's information or the information of the parent's child, regardless of the child's class. Furthermore, the childcare facility 30 may notify specific recipients of visits (for example, the class in which children waiting to be picked up are gathered as the time gets later) of all visits by parents whose arrival is detected. Also, childcare facilities may have regular childcare hours while also offering extended childcare (childcare provided outside of regular childcare hours). The visit notification module 2047 may, during regular childcare hours, notify parents upon their arrival according to the child's class as described above, but during extended childcare hours, it may decide to notify any class regardless of the child's class (for example, children may be gathered in a designated class (such as a joint childcare room) during extended childcare), or multiple recipients (for example, all classes, each terminal within the childcare facility). The notification recipient management module 2044 controls the dynamic changes to the signage of the notification recipients by referring to the time information and the childcare schedule database 214. For example, suppose that during extended childcare hours after 6 PM, children from multiple classes are gathered in one joint childcare room (e.g., playroom).In this case, even if the visiting parent's child is originally in the "Sunflower Class," the visitor notification module 2047 will notify the child not at the terminal in the "Sunflower Class classroom," but rather at the terminal in the "playroom," which is currently the activity location for the child's class.
[0173] (6) Other: Notifications to parents regarding waiting times upon arrival at the park. When the visitor notification module 2047 detects that a parent has arrived, it notifies the parent of information (such as the teacher's daily report) indicating the child's condition on the day of the visit (or may include the child's condition in the past). For example, a display installed at the location where the parent has arrived may authenticate the parent and then display a daily report, including text and images, about the parent's child.
[0174] The childcare record management database 215 in the memory unit 202 is configured to store log information recording the activities of children at the childcare facility 30. In step S1221, the visitor notification module 2047 detects that a child's guardian has arrived and, by referring to the log information in the childcare record management database 215, presents the guardian with the results of recording the child's activities.
[0175] In step S1211, the notification means 32 receives a notification from the server 20 and notifies the guardian of their visit via screen display or voice guidance.
[0176] In step S1225, the visitor notification module 2047 of the server 20 records information indicating that a parent has visited and information indicating that a notification was made via signage, etc., in the parent visit history database 216 and the notification history database 217.
[0177] Figure 13 shows the process flow for predicting and notifying parents of the time they will be visiting to pick up their children.
[0178] In step S1321, the visitor notification module 2047 of the server 20 obtains information such as the scheduled pick-up time entered in advance by the parent, the facility's schedule (childcare schedule database 214), and weather forecasts.
[0179] The parent visit history database 216 on server 20 is configured to store historical information about the timing when it was detected that a parent had visited the childcare facility 30 in step S1221.
[0180] In step S1322, the visitor notification module 2047 of the server 20 collects data on each parent's past visit times from the parent visit history database 216.
[0181] In step S1323, the visitor notification module 2047 of server 20 obtains the parent's current location information as needed (if the parent has given permission to obtain location information).
[0182] In step S1324, the visitor notification module 2047 of server 20 executes an algorithm to predict the visit time of parents based on the collected data. Specifically, server 20 calculates the average visit time for each day of the week from the past visit history of the target parent. In this case, a weighted average may be used so that more recent data has a greater weight. Furthermore, server 20 applies weather information and traffic information for the day as correction factors. For example, if the weather is "rainy", a predetermined time (e.g., 15 minutes) may be added to the average visit time on sunny days, or if there is traffic congestion information for roads around the childcare facility, a delay prediction time according to the degree of congestion may be added to calculate the predicted visit time. Server 20 may also infer the visit time using a trained model such as a regression model that has been trained using this input data (date and time, weather, traffic conditions) and output data (actual visit time) as training data. As a specific prediction logic, server 20 may calculate the predicted visit time (T_pred) using the following formula.
[0183] T_pred = T_base + α × W + β × D Here, T_base is the average visit time for each day of the week over a recent period (e.g., one month) for the parent in question. W is a weather coefficient, a variable that is '1' if the obtained weather forecast is 'rain' or 'snow', and '0' otherwise. α is a weather delay constant (e.g., 15 minutes). D is a traffic condition coefficient, indicating the level of congestion (0-10) on the route from the parent's workplace to the childcare facility. β is a delay constant due to congestion (e.g., level × 2 minutes). Furthermore, the server 20 may not only perform simple addition but also apply coefficients (individual profile coefficients) tailored to the individual characteristics of each parent, using a machine learning model that has been trained on the parent's past behavioral logs (e.g., "on rainy days, I arrive 20 minutes earlier than average").
[0184] (1) For childcare workers: Predict the time when parents will pick up their children. Prepare in advance for when parents will arrive. The visitor notification module 2047 refers to past history to identify time periods when a parent is likely to visit, and notifies the user of the possibility of a parent's visit as that time period approaches.
[0185] More specifically, the parent visit history database 216 is configured to store historical information about the timing when it was detected in step S1221 that a parent had visited the childcare facility 30.
[0186] The visitor notification module 2047 identifies time periods when parents are most likely to visit, based on information from their visit history. For example, it identifies time periods when parents are most likely to visit by aggregating the distribution of visit times for certain time periods, calculating the median and average visit times, etc. When a time period identified as likely to bring a parent to visit arrives on a day when the child is using the childcare facility 30, the visitor notification module 2047 notifies the child of the possibility of a parent's visit. Here, as explained in Figure 12, the notification may be output to a notification means 32 such as signage installed in the classroom where the child of the parent is enrolled.
[0187] (2) Obtain weather information and predict the pick-up time according to the weather. The visitor notification module 2047 may predict the time when parents will pick up their children based on weather information on the day of pickup and weather information during the time of pickup, and notify the parents of the prediction result via notification means 32, etc. For example, if the weather is expected to worsen, parents may come to pick up their children earlier.
[0188] More specifically, the visitor notification module 2047 obtains weather forecast information for the area where the childcare facility 30 is located on days when the child is using the facility. Based on the content of the obtained weather forecast, the visitor notification module 2047 identifies the time of day when the child's guardian is most likely to visit. For example, if it is raining (rain gear will be needed, and the walking time may be longer than on a sunny day), or if the temperature is different from the average (it is preferable to have warm clothing as the temperature is lower than average), the module may predict that the pick-up will be a certain amount earlier. As will be described later, the visitor notification module 2047 notifies the guardian of the possibility of their visit as the identified time period approaches. Here, if the pick-up time is predicted based on the weather information, the notification may be sent to the guardian's child's class notification means 32, as explained in Figure 12. Additionally, it may be provided that the pick-up time is a prediction based on weather information (for example, a message stating that "the pick-up may be earlier due to bad weather" and the predicted pick-up time).
[0189] (3) Other factors that may affect parents' ability to travel to childcare facility 30 (e.g., traffic congestion) The visitor notification module 2047 may predict the pick-up time based on factors that influence parents' travel to the childcare facility 30, such as road congestion. For example, it may predict that parents will be late if there is traffic congestion on the main road leading to the childcare facility 30.
[0190] In step S1325, the visitor notification module 2047 of the server 20 sends a notification to the terminal of the relevant childcare worker or the class terminal (notification means 32) when the predicted visit time approaches.
[0191] (1) Content of the notification: Displays statistical data on the parent's past visits to the daycare center and a prediction of the pick-up time. The visitor notification module 2047 may also notify the notification device 32 or the like of statistical information on the history of visits by the child's guardian and information on the time periods that have been identified as likely to see a guardian visit.
[0192] (2) Parents will be asked to enter the time they plan to pick up their child. The visitor notification module 2047 of server 20 accepts input from parents regarding the time they plan to pick up their children, and based on this history, it may identify time slots when parents are most likely to visit and notify the parents of the possibility of their visit as that time slot approaches. On days when a child is using the childcare facility 30, the visitor notification module 2047 accepts input from the child's parents regarding the time they plan to visit the childcare facility. When the time of the accepted visit arrives, the visitor notification module 2047 notifies the parents of the possibility of their visit using notification means 32, etc.
[0193] (3) Based on the information of the parent's location, predict the time of pickup and notify the parent when it is time to pick up. The visitor notification module 2047 may acquire the location information of the parent's device and detect when the location information changes, thereby notifying the childcare facility 30 that the parent has started to move to pick up their child. The visitor notification module 2047 may also notify the childcare facility 30 when the parent approaches the facility.
[0194] The visitor notification module 2047 acquires location information of the child's guardian on days when the child is using the childcare facility 30. Based on the acquired location information of the child's guardian and the location information of the childcare facility 30, the visitor notification module 2047 evaluates the likelihood of the child's guardian arriving. For example, the visitor notification module 2047 evaluates whether the guardian has started moving, whether the guardian is approaching the childcare facility 30 (the distance between the guardian's location and the childcare facility 30 is decreasing), and whether the guardian is about to arrive at the childcare facility 30 (the estimated arrival time based on the search results of the travel route from the guardian's location to the childcare facility 30 is within a certain time). Based on the evaluation results of the likelihood of the child's guardian arriving, the visitor notification module 2047 notifies the system of the possibility of the guardian arriving.
[0195] In location-based detection, to prevent false positives, server 20 performs not only intrusion detection into a geofence (virtual boundary) centered on the childcare facility, but also a determination of the 'movement vector'. Specifically, when a parent's terminal 10 enters a designated area (e.g., a radius of 500m), it is determined that there is a 'high probability of arrival' only if its direction of movement is directed towards the childcare facility's coordinates. If the movement vector is moving away from the facility or passing through the facility, it is considered a simple pass-through and notification is withheld. This allows for accurate support in preparing to pick up children without overreacting to parents who are merely passing by the vicinity of the facility.
[0196] In step S1311, the notification means 32 receives a notification from the server 20 and displays the following information on the screen. • Predicted arrival time (Example: "Mr. Yamada T.'s guardian is scheduled to arrive around 17:30.") • Statistical data on past visit times • Supplementary information such as weather and traffic conditions (e.g., bad weather, traffic congestion causing delays). In step S1326, the visitor notification module 2047 of server 20 learns the difference between the actual visit time and the predicted time and updates the data to improve the accuracy of the algorithm.
[0197] <4. Screen Example> Figure 14 shows an example of a screen that notifies a parent or guardian that they have arrived to pick up their child. While the example shown is for a portrait-oriented screen, it may also be displayed on a landscape-oriented screen. In that case, the layout of the displayed items may be changed or the displayed items may be switched between portrait and landscape screens.
[0198] Operation screen 1400 is an operation screen that notifies the parent or guardian that they have come to pick up their child.
[0199] The operation screen 1400 corresponds to each process in Figure 12.
[0200] The notification message area display area 1402 is an area for displaying notification messages that inform parents of their arrival. For example, it is an area for displaying a notification message such as "Ms. ●da ●ko from the Sunflower Class is here to pick up her child." As shown in the diagram, the notification message and the time the notification was made may be displayed together. This makes it easy to recognize when a parent has arrived, and also makes it easy for the operator of the childcare facility 30 (for example, the class teacher) to check the current time displayed on the operation screen 1400 and understand the elapsed time since the parent's arrival.
[0201] Furthermore, when distributing notification messages for each class regarding the pick-up of children belonging to that class, the notification content may include at least one of the child's name or the child's guardian's name, without including the class name. For example, if a notification message is displayed on the signage in the Himawari class classroom, it may notify the child's name without including the class name, such as "This is to pick up Ms. ●da ●ko." The notification message may also display an image of the child (such as a face image) or an image of the child's guardian (such as a face image). Here, the childcare facility may accept settings from guardians regarding whether or not to display the child's face image and the guardian's face image in notifications. For example, if a guardian has set the notification to not display face images, the notification can display at least one of the child's name or the child's guardian's name, but not the guardian's face image. Also, depending on the location where the notification means 32 is installed, the childcare facility may accept settings from guardians or other persons regarding whether or not to display the face images of guardians, etc., when notifying the pick-up message. For example, in a childcare facility, terminals that are not visible to children or parents but are visible only to staff may display the facial image of visiting parents, while terminals in areas where children and parents come and go within each classroom of the childcare facility may not display the facial image of the parents, depending on the parents' settings.
[0202] Furthermore, the signage screen may not display the class name, but instead display at least the name of the child who has been picked up or the name of the child's guardian, while the audio output from the signage and speakers within the childcare facility 30 may include the class name as well. In this way, when the notification means 32 notifies of the child's arrival using multiple output methods such as visual (display on a screen), auditory (audio output), and skin contact (vibration), the notification content may differ for each type. Alternatively, the notification may be made only by auditory means (audio output from speakers), without using visual means, and only by at least the name of the child who has been picked up or the name of the child's guardian.
[0203] This allows for appropriate control over the amount of information displayed on the signage for each class, while also providing voice notifications to indicate which class is being picked up. This provides teachers with information to help them decide whether or not to pay attention to the pick-up notification, potentially leading to smoother operations. For example, by first outputting the class name in the voice notification, followed by at least one of the child's name or the child's parent's name, teachers can quickly decide whether or not to pay attention to the voice notification. If it concerns their own class, they can then easily identify the child being picked up by comparing the voice output with the information displayed on the signage.
[0204] The pickup time prediction area display region 1404 is the area that displays the predicted pickup time for parents. This area displays times based on past history and prediction algorithms.
[0205] The child information area display area 1406 is an area that displays the child's photo and basic information (name, class, age, etc.).
[0206] The notification history area display area 1408 is an area that displays a list of past notifications and visits by other children.
[0207] The important notices area display area 1410 is an area for displaying emergency contacts and messages from important facilities.
[0208] The confirmation button operation unit 1412 is an operating component that receives an operation to record that the childcare worker has confirmed the notification content.
[0209] The detailed display button operation unit 1414 is an operating component that accepts operations to display detailed information and notices about children.
[0210] The filter function specification unit 1416 is an operating member that provides a selection function for narrowing down the notifications to be displayed by class or time period.
[0211] Figure 15 shows an example of a screen displaying the child's childcare record to visiting parents.
[0212] Operation screen 1500 is a screen that displays the child's childcare record to visiting parents.
[0213] The childcare log area display area 1502 is an area for displaying records of the children's activities on the day, photos, and comments from childcare workers. It may display records held in the childcare record management database 215, and may display records for the day or past records. For example, it may display past records related to the record for the day, or if it is a record of physical activity, it may also display past records of physical activity. The server 20 refers to the childcare record management database 215 and identifies past records related to the record on the day of pickup from the records held for children who have been picked up. For example, the server 20 may refer to the childcare record management database 215 for children who have been picked up, identify records related to the day of pickup (or the most recent past record), generate a prompt that includes an instruction to summarize the childcare record, and send the generated prompt to the server 95 of the large-scale language model service, thereby obtaining a summary of the childcare record, including past records, and presenting it to the parents. Furthermore, in the childcare log area display region 1502, the server 20 may accept settings from the child's guardian regarding whether or not to display the child's log. For example, in a terminal used for guardian authentication when picking up a child, the guardian may set the terminal not to display the child's log, as unspecified individuals may be able to view the contents of the terminal. Here, the server 20 may refer to the childcare worker's log for the class to which the child being picked up belongs, summarize its contents, or display an abstracted version that excludes proper nouns such as names of people on the screen. For example, as a prompt given to the server 95 of the large-scale language model service, the server 20 refers to the childcare worker's log for the class to which the guardian's child belongs (childcare record management database 215), obtains information on the guardian's child's log, the log information for each child in the child's class, and the log information for the entire class to which the child belongs, and creates a prompt that includes instructions to summarize the contents, or instructions to summarize while excluding proper nouns such as names of people, while referring to this information.
[0214] Here, as a preprocessing step before generating prompts, server 20 performs a replacement process for proper nouns contained in the log text data. Specifically, server 20 refers to the child database 211 and the childcare worker database (not shown) to identify child names and childcare worker names contained in the log text. Server 20 replaces the identified names with specific tokens (e.g., "{Child A}", "{Childcare Worker B}", etc.) or common pronouns, and then sends them to server 95 of the large-scale language model service.
[0215] This allows for secure generation of summaries and other data without directly transmitting personal information to the external server 95. Server 20 may switch, depending on the parent's settings, whether to display the tokens included in the response obtained from Server 95 as the original name, or to display them in an anonymized state. In this way, when using the external large-scale language model service server 95, Server 20 performs "anonymization processing (masking processing)" before sending a prompt to prevent leakage of personal information. Specifically, Server 20 identifies the "child's name," "parent's name," and "teacher's name" included in the diary text by matching them with the child database 211, etc., and replaces them with unique tokens (e.g., "{Child_A}", "{Teacher_B}"). Server 20 sends a prompt containing the replaced text to Server 95 and receives the generated summary text. Subsequently, Server 20 reverse-replaces the tokens ({Child_A}, etc.) in the received summary text with the original "child's name," etc., to restore it and generate the final display data. This makes it possible to use advanced summarization and text generation functions without providing personal information to external AI services. Server 20 may provide the prompt to the server 95 of the large-scale language model service, receive the processing result, and display it in the childcare log area display area 1502.
[0216] Waiting time guidance area 1504 is an area that displays information about the waiting time until a childcare worker brings the child. For example, it is an area that displays "We will be coming to pick up your child shortly. Please wait a moment."
[0217] Facility Announcements Area 1506 is an area for displaying general announcements from the childcare facility, such as event schedules and notices.
[0218] The survey area display area 1508 is the area where we request surveys and feedback from childcare facilities.
[0219] The Read / Confirm Button Operation Unit 1510 is an operation component that receives input from parents to confirm that they have read the childcare log or notices.
[0220] The contact information input field acquisition unit 1512 is a text box where parents can freely enter messages and comments for childcare workers.
[0221] <Second Embodiment> The first embodiment described a system that primarily operates in childcare facilities, notifying staff upon the arrival of a parent or guardian. The second embodiment describes a system that is also suitable for educational facilities such as cram schools and extracurricular activity classes. In addition to a notification function to parents triggered by student authentication, it describes a function that enhances security around the facility and objectively evaluates and visualizes the safety of the facility.
[0222] In recent years, while small-group and unmanned operations have become more common in educational facilities such as cram schools and after-school activity classes, ensuring the safety of children not only within the facility but also on their routes to and from the facility (safety during commutes) has become a crucial issue. Parents have a need to understand not only when their children enter and leave the facility, but also whether the facility is a "safe environment," and operators are required to objectively demonstrate the security level of their facility and provide parents with peace of mind.
[0223] Therefore, the system according to this embodiment is equipped with a monitoring function that utilizes imaging means such as cameras used for entry and exit management to detect unregistered individuals (suspicious persons, etc.). In particular, in addition to simply detecting unregistered individuals, the system aims to improve detection accuracy by introducing a process that excludes children and their companions (siblings, etc.) from the count of suspicious persons based on physical characteristics and estimated age.
[0224] Furthermore, based on the accumulated detection history, this system calculates evaluation indicators (security score and rank) that show the "safety" of the facility, and visualizes and presents them in a dashboard format. This allows parents to intuitively understand the safety level of the facility.
[0225] Furthermore, when authenticating students' entry and exit, this system refers to the calculated safety assessment of the facility and the recent suspicious person detection status (threat level). If the threat level is determined to be high, in addition to the regular notification, a warning message urging caution in the surrounding area is dynamically added and sent to parents when notifying them of their child's entry and exit.
[0226] Thus, according to this embodiment, it is possible to realize a security platform that not only records entry and exit times but also reduces environmental risks around the facility and provides a high level of peace of mind and safety to both parents and facility operators.
[0227] The specific configuration and processing of this embodiment will be described below with reference to the drawings.
[0228] <Structure> The overall configuration of System 1 according to this embodiment is the same as that shown in Figure 1 in the first embodiment, but each component plays the following role.
[0229] Childcare facility 30 also functions as an educational facility such as a cram school or extracurricular activity class. Alternatively, separate from childcare facility 30, there may be other educational facilities such as cram schools or extracurricular activity classes that students (including children, but also adults) attend. In this case, the detection means 31 (camera, etc.) not only authenticates visitors but also continuously or periodically photographs the area around the facility and transmits the video data to server 20, thereby serving as a surveillance camera for suspicious person detection and security evaluation, as described later.
[0230] Furthermore, the reader 33 (IC reader, etc.) is used not only for unlocking operations by guardians, but also as a device to authenticate the entry and exit of children (school attendance) by reading IC cards or other media carried by the students (children) using the facility.
[0231] The configuration of the server 20 in this embodiment is based on the configuration shown in Figure 2, but with functional extensions.
[0232] In addition to the modules described in the first embodiment, the control unit 203 also includes functions as a "security management module" and a "child attendance management module" (not shown).
[0233] The security management module is a functional unit that detects suspicious individuals, determines whether to exclude them, and calculates a safety score for the facility based on video data and other information acquired from the detection means 31.
[0234] The attendance management module is a functional unit that performs identity verification of children based on their operation of a reader 33, etc., and controls the system to notify the parent / guardian's terminal 10 of the child's entry and exit.
[0235] In addition to the databases shown in the first embodiment, the memory unit 202 also stores the "suspicious person detection history database 218" shown in Figure 16 and the "facility safety score database 219" shown in Figure 17, which will be described later.
[0236] The structure of each database is also configured as follows, in accordance with this embodiment.
[0237] In this embodiment, the child database 211 shown in Figure 4 includes, in addition to the item "Child ID," an item called "Child Authentication Data" (not shown). This item stores information necessary for the child to authenticate themselves, such as the child's facial image data, the identification ID (UID, etc.) of the IC card the child possesses, or QR code (registered trademark) information, all associated with the Child ID.
[0238] In the parent database 212 shown in Figure 5, the items "telephone number" and "email address" are used not only as emergency contacts, but also as recipients to whom the system automatically sends notifications when a child enters or leaves the facility (arrival / departure).
[0239] <Data structure> Figure 16 shows the data structure of the suspicious person detection history database 218.
[0240] The "Detection History ID" field is information used to uniquely identify a suspicious person detection event.
[0241] The "Detection Date and Time" field indicates the date and time (timing) when the event was detected.
[0242] The "Detection Location ID" field identifies the location (area) inside or outside the facility where the event was detected.
[0243] The item "Detection Location Name" is information indicating the name of the location where the event was detected.
[0244] The item "Detection Method ID" is information that identifies the device (camera, etc.) that detected the event.
[0245] The "Event Type" field contains attribute information indicating the type of event detected (e.g., authentication failure, loitering detection, loitering detection).
[0246] The item "Authentication Result" (when the event type is authentication trial) is information indicating the status of authentication by the parent / child authentication system (success, failure, or not applicable).
[0247] The item "Threat Score (Suspiciousness Score)" is information about the evaluation results calculated by the system, such as a score (e.g., 0-100) indicating the likelihood of the person being suspicious or the level of threat. This score serves as the basis for calculating the security assessment.
[0248] The "Judgment Result Status" item is information indicating the status of the system's automatic judgment based on the threat score.
[0249] The item "Estimated Age Group" is attribute information indicating the age group of the detected individual, as estimated by image analysis. This information is used as the basis for exclusion decisions.
[0250] The "Estimated Height" attribute indicates the height (in cm) of the detected subject, as estimated through image analysis. This information is used as the basis for exclusion decisions.
[0251] The item "Detected Behavior Details" contains information that shows the specific behavioral patterns and characteristics that formed the basis for the determination.
[0252] The "Exclusion Determination Flag" item contains information about a flag indicating whether or not the person meets the "conditions for excluding a suspicious person" (e.g., a child, a known person) (e.g., 1 means excluded, 0 means not excluded).
[0253] The "Exclusion Reason Details" field contains information indicating the reason why an item was determined to be excluded (flag=1) (e.g., estimated age is below the threshold).
[0254] The item "Image Data Reference Information" contains information such as paths or links to image files or video files that serve as evidence at the time of detection.
[0255] The item "Operator Notification Status" is information indicating the status (unnotified, notified, notification failed) of whether a notification (alert) has been executed to the facility operator.
[0256] The item "Notification Date and Time" is information indicating the date and time (timing) when the notification to the operator was executed.
[0257] The item "Operator Confirmation Status" is information indicating the situation (unconfirmed, being confirmed, responded, false alarm determined) of the operator's confirmation and response to the notification.
[0258] The item "Responsible Person ID" is information for identifying the operator (nursery teacher, instructor, etc.) who performed the confirmation and response.
[0259] The item "Response Record Memo" is information indicating the details of the response content and remarks recorded by the operator.
[0260] Figure 17 is a diagram showing the data structure of the facility safety score database 219.
[0261] The item "Safety Evaluation ID" is information (such as a management number) for uniquely identifying the calculated safety evaluation record.
[0262] The item "Detected Facility ID" is information for uniquely identifying the facility that was the target for calculating the safety score.
[0263] The item "Aggregation Target Period" is information indicating the range of the period (weekly, monthly, etc.) that was the target of the evaluation.
[0264] The item "Safety Rank" is information on the evaluation result indicating the rank (such as S~D determination) that shows the safety level of the facility step by step based on the calculated score.
[0265] The item "Overall Score" is information on the evaluation result indicating the quantitative evaluation value of safety (e.g., out of 100 points) calculated from the number of suspicious person detections and the response situation.
[0266] The item "Suspicious Person Detection Frequency" indicates the number of times a person was counted as a "suspicious person" after passing the exclusion logic during the aggregation period.
[0267] The "Frequently Occurring Time Period" item indicates the time period in which suspicious individuals were most frequently detected. This information can be used, for example, to alert parents.
[0268] The item "Main Detection Locations" indicates the names of areas and camera locations around the facility where suspicious individuals were frequently detected.
[0269] The "Evaluation Comment" item is information that displays a standardized or generated message based on the rank, intended for display on the dashboard.
[0270] The "Last Updated" field indicates the date and time this evaluation score was calculated and updated.
[0271] <Operation> Figure 18 shows the process flow for detecting suspicious individuals, issuing notifications, and evaluating the safety of the facility.
[0272] In step S1821, the server 20 determines the possibility of a person being a suspicious individual based on information received from the detection means (such as a surveillance camera). Specifically, it performs actions such as calculating a threat score through behavioral analysis, detecting authentication failures, or determining exclusion conditions.
[0273] Here, server 20 determines patterns that are highly likely to be malicious attempts (attacks), rather than isolated authentication failures, as "suspicious authentication failures."
[0274] Specifically, server 20 adds a threat score if authentication fails a predetermined number of times (e.g., 5 times) or more consecutively within a predetermined time period (e.g., 1 minute) by the same terminal or the same person (face image) (suspected brute-force attack), or if video analysis detects actions such as hiding one's face from the camera or holding up a photo or display (suspected impersonation attack) even though the face image is not registered.
[0275] In behavioral analysis, Server 20 uses image analysis to detect a person's skeleton and track their movement trajectory. For example, if the same person stays in a predetermined area around the facility, such as a pre-set "forbidden area" (e.g., near a fence) or within a predetermined distance (e.g., 5 meters) from the facility's boundary line, for a predetermined time (e.g., 3 minutes) or if the same person comes and goes multiple times (e.g., 3 or more times) in a short period of time (e.g., 10 minutes), it is determined to be "loitering" and a threat score is added. Server 20 also detects the direction of a person's gaze and adds a threat score if it detects that the person is staring at the inside of the facility for a certain period of time (e.g., 5 seconds) or if it detects that the person is attempting to climb the outer wall or gate of the facility (determined from the relative positions of their hands and feet).
[0276] Thus, as the logic for determining "wandering" in behavioral analysis, server 20 tracks the movement trajectory of the detected person and determines it as "wandering (suspicious behavior)" if any of the following conditions are met, and adds to the threat score.
[0277] (1) If the same person stays in an area within a specified distance (e.g., 5m) from the outer boundary of the facility for a cumulative total of 3 minutes or more.
[0278] (2) If the same person passes in front of the entrance / exit of the facility three or more times within a specified time (e.g., 10 minutes) without entering or leaving the facility.
[0279] (3) If a specific posture different from normal walking (e.g., crouching, climbing over a fence) is detected by skeletal detection (pose estimation) of a person for a period of 5 seconds or more. Furthermore, the server 20 performs a "re-identification" process to determine whether the person detected is the same person across multiple different detection means 31 (cameras) or at different time periods. Specifically, the server 20 vectorizes and extracts feature quantities such as the color and pattern of clothing, body shape, and belongings from the full-body image of the detected person.
[0280] Server 20 calculates the similarity (cosine similarity, etc.) between the feature vector of a person detected by camera A within the facility and the feature vector of a person detected (or previously detected) by camera B installed in a different location. If the similarity exceeds a predetermined threshold, Server 20 determines them to be the "same person" and analyzes the linked movement trajectories. This allows for accurate detection and evaluation of a series of "wandering behaviors," even if a person leaves the camera's field of view and then reappears, or if they move between multiple monitoring areas.
[0281] In determining exclusion criteria, server 20 estimates the age group of the detected person using AI (deep learning, etc.) from the facial image. It also estimates the person's height using the principle of triangulation based on the camera's installation height or by using a depth sensor (depth camera). Server 20 considers the possibility that the detected person is not a "suspicious person" but a "child" or "person accompanying" who is a person under protection, and makes an exclusion decision. Specifically, server 20 estimates the height of the detected person using the principle of triangulation based on the installation height of the detection means 31 (camera), or using the depth sensor (depth sensor) provided by the detection means 31. Furthermore, server 20 estimates the age group of the detected person using AI (deep learning, etc.) from the facial image or skeletal features during walking. Server 20, if the estimated height is below a predetermined value (e.g., 140 cm) and the estimated age is below a predetermined value (e.g., 12 years old), will consider the person to be a "child" and will either not add to the threat score based on the behavioral detection described above, or will invalidate the calculated threat score.
[0282] In addition to making a determination based on only height and estimated age, the server 20 may perform "whitelist verification". Specifically, the face image of the detected person is compared with the face images registered in the guardian database 212 and the staff database. If it is identified as a registered person (guardian, staff, etc.), it is excluded from the detection targets as a suspicious person. Also, by detecting features such as "schoolbag", "designated daycare bag", and "uniform" through image analysis, even if the estimated height exceeds the threshold, it may be determined that the probability of being a "student / child" is high, and a correction may be made to lower the suspicious person score.
[0283] As a result, for example, for a person with a height of "140 cm or less" and an estimated age of "12 years or less", it is determined that there is a high possibility that they are a "child" rather than a suspicious person, and a process of excluding them from the count of suspicious person detections or significantly subtracting the threat score is performed.
[0284] In step S1822, the server 20 accumulates the determination results (detection date and time, location, threat score, imaging data reference information, etc.) as security history in the "suspicious person detection history database".
[0285] In step S1823, when the threat score exceeds the threshold, the server 20 immediately sends an alert to the operator's terminal in parallel with this process.
[0286] In step S1824, the server 20 aggregates and analyzes the accumulated security history regularly or based on a request (e.g., analysis of detection frequencies by time zone and location).
[0287] Here, the server 20 manages the map data of the facility and its surroundings by dividing it into meshes (grids) of a predetermined size (e.g., 1 m × 1 m).
[0288] The server 20 has previously associated the viewing angles of each camera with the coordinates on the map, and converts the position in the video where a suspicious person is detected into coordinates (mesh ID) on the map.
[0289] Server 20 aggregates the number of detections for each mesh as a heatmap and identifies areas where meshes with a high number of detections exceeding a threshold are concentrated as "main detection locations." Alternatively, it derives location-specific trends by aggregating the number of detections within geofences (virtual boundaries) predefined as "main gate area" and "parking area."
[0290] In step S1825, the server 20 generates evaluation information (security score, statistical report, etc.) that assesses the safety of the facility based on the analysis results.
[0291] For example, when calculating the overall security score, server 20 deducts points from a baseline (e.g., 100 points) based on the number of times a suspicious person is detected. In this process, weights are applied according to the threat score (suspiciousness score) of the detected suspicious person and the importance of the location where the detection occurred (e.g., the main gate or the back entrance).
[0292] Specifically, the following formula can be used.
[0293] Total score = 100 - Σ(Number of detected incidents × Threat score coefficient × Location importance coefficient) + (Number of incidents completed by the operator × Response coefficient (Recovery coefficient)) Here, the "location importance coefficient" is set to a larger value (e.g., 1.5 times) for locations with higher importance, such as "near classroom windows" or "main gate." In addition, if the operator responds quickly to an alert (updating to "responded"), the score is restored by a certain amount, so that the evaluation reflects not only the security situation but also the quality of the facility's management system.
[0294] An example of the formula for calculating the overall security score ($S$) is shown below.
[0295] S = 100 - Σ(E_i × w_i × d_t) + R Here, E_i is the number of detected events. w_i is the weighting coefficient for the threat level.
[0296] A distinctive feature is that server 20 applies a "time decay coefficient (d_t)." This coefficient decreases (approaches 0) as time passes since a detection event occurred. This means that even if a suspicious person was detected in the past, the score will gradually recover if the area has been safe recently, thus accurately reflecting the current security situation.
[0297] This allows for a more accurate evaluation, where the score doesn't simply drop because of a high number of detections, but rather if the operator takes prompt action, the score decline can be mitigated.
[0298] In step S1811, terminal 10 sends a request to server 20 to display safety evaluation information based on an action by the operator or guardian.
[0299] In step S1826, the server 20 sends the generated evaluation information to the terminal 10 upon request.
[0300] In step S1826 (or another learning step), the server 20 updates the judgment algorithm using the operator's verification results (feedback).
[0301] Specifically, server 20 adds image data of events that the operator has determined to be "false alarms (not suspicious)" in the suspicious person detection history database 218 to the training dataset as the correct label (not suspicious person).
[0302] Server 20 periodically (e.g., once a week) retrains (fine-tunes) the suspicious person detection model (AI model) using the accumulated training dataset. This reduces the frequency of incorrectly identifying frequently occurring individuals specific to the facility, such as "delivery workers wearing a particular uniform" or "cleaners at the facility," as suspicious persons, thereby continuously improving the accuracy of the detection.
[0303] In step S1812, terminal 10 displays the evaluation information received from server 20 on its screen (dashboard, report, etc.).
[0304] Figure 19 shows the process flow for authenticating a child's entry into a room and notifying the guardian.
[0305] In step S1911, terminal 10 obtains the child's authentication information (ID, facial image data, etc.) through operation by the child (such as touching an IC card) or automatic detection (such as facial recognition).
[0306] In step S1912, terminal 10 sends the acquired authentication information and information indicating whether it is an arrival (going to the nursery / entering the room) or departure (going out of the nursery / leaving the room) to server 20.
[0307] In step S1921, the server 20 compares the authentication information received from the terminal 10 with the child authentication data registered in the "child database" to authenticate and identify the child.
[0308] In step S1922, if authentication is successful, the server 20 records the event (date, time, and circumstances) of the child's arrival or departure.
[0309] In step S1923, the server 20 retrieves the contact information of the parent associated with the identified child from the "Parent Database".
[0310] In step S1924, the server 20 generates a notification message that includes the child's name, date and time, and situation.
[0311] In step S1925, the server 20 sends the generated notification content to the parent's device based on the acquired contact information. This transmission is performed, for example, by push notification or message sending.
[0312] <Screen example> Figure 20 shows an example of a screen displaying the results of a safety assessment, which is presented to facility managers and guardians.
[0313] The Security Dashboard 2000 is a screen that visualizes facility safety assessment information generated based on the analysis results of suspicious person detection history, with the aim of enabling operators and guardians to understand the security situation.
[0314] The overall security score display area 2002 is an area that displays the overall safety evaluation of the facility (e.g., a score out of 100 points, S / A / B / C rank) calculated based on accumulated history. Changes (improvement / deterioration) from the previous period may also be displayed in this area.
[0315] The detection summary display area 2004 is an area that displays key statistical information such as the total number of suspicious person detections, the number of alerts issued, and the number of cases resolved within the specified period.
[0316] The detection count trend graph display area 2006 is an area that displays the time-series trend of the number of suspicious person detections (e.g., daily trend over the past month) using a line graph or similar method, in order to facilitate understanding of trends.
[0317] The Time-of-Day / Day-of-Week Detection Frequency Graph Display Area 2008 is an area that displays the detection frequency by time of day and day of the week using bar graphs and heat maps, in order to identify the time of day and day of the week when suspicious persons are more likely to be detected.
[0318] Location-Specific Detection Frequency Graph Display Area 2010 is an area that displays the detection frequency for each location in order to identify places inside and outside the facility where suspicious persons are likely to be detected (e.g., entrance, parking lot, back entrance).
[0319] The "Recent Detection Events List" area (2012) displays a list of recent suspicious person detection events, including their history (detection date and time, location, threat score, response status, etc.).
[0320] The Evaluation Comments / Advice Display Area 2014 is an area that displays evaluation comments and recommended actions (e.g., "Recommend strengthening evening patrols") automatically generated by the system based on the analysis results, or observations entered by the operator.
[0321] The display period specification unit 2016 is an operation component that accepts operations to specify and change the target period for the statistical information to be displayed on the dashboard (e.g., "This week," "This month," "Past 3 months," or any date range).
[0322] The target facility selection unit 2018 is an operating component that accepts operations for selecting the facility to be displayed (when the operator manages multiple facilities).
[0323] The filtering condition specification unit 2020 is an operating component that accepts operations to narrow down the list of detection events to be displayed based on specific conditions (e.g., threat score range, response status).
[0324] The detail display button 2022 is provided for each item in the detected event list and is an operating component that accepts an operation to transition to a screen that displays detailed information about the event (imaging data, corresponding records, etc.).
[0325] When displaying image data from when a suspicious person is detected, such as by operating the detailed display button 2022, the server 20 (or terminal 10) may perform image processing for privacy protection.
[0326] Specifically, server 20 detects the facial regions of other people in the image (passersby, other children, etc.) besides the detected target person (the person identified as a suspicious person), automatically masks (blurs) them, and then displays them.
[0327] Furthermore, in cases where the likelihood of identifying a person as suspicious is low (threat score is moderate or lower), the system masks the person's face, making only overall features such as clothing and build visible. This reduces the risk of infringing on portrait rights in the event of a false positive while still providing a warning.
[0328] The Report Output Button 2024 is an operation component that accepts the operation to output (download) the displayed evaluation information in a standard report format (PDF, etc.).
[0329] Figure 21 shows an example of a screen that notifies parents on their devices when a student enters a learning facility.
[0330] The notification header display area 2102 is an area that displays the date and time the notification was received and its title (e.g., "Notification of Room Entry").
[0331] The target student information display area 2104 is an area that displays the facial photograph (registered image or photographed image), name, and grade / class name of the authenticated student.
[0332] The entry / exit status display area 2106 is an area that displays the student's actions ("entered the room," "exited the room") and the exact time of those actions.
[0333] Security warning area 2108 is an area that is only displayed when the threat level around the facility is high. This area is highlighted with a red frame or icon and displays a message such as "Suspicious person detected around the facility."
[0334] Specifically, the server 20 checks whether a detection event exceeding a predetermined threshold (e.g., level 3 or higher) in the suspicious person detection history database 218 has been recorded within a predetermined time period (e.g., within 30 minutes) prior to the time when a child entered or left the room (authentication).
[0335] If the relevant event exists, the server 20 sends a security warning flag to the terminal 10 in addition to the normal entry / exit notification message, and the terminal 10 expands and displays the warning area 2108.
[0336] Furthermore, server 20 monitors the conditions for deactivating the security warning flag once it has been set (safety declaration conditions). Specifically, if a predetermined time (e.g., 1 hour) has elapsed since the last suspicious person detection event and no new detections have occurred during that time, server 20 automatically turns off the warning flag.
[0337] Alternatively, when server 20 receives a "security check complete" operation signal from the operator's terminal, it immediately turns off the warning flag.
[0338] In response to the warning flag being turned off, the server 20 sends a signal to the parent's device 10 instructing it to return to "normal mode" (or display a notification that "security has been confirmed"), and hides the security warning display area 2108 on the screen, or switches it to a display indicating security, such as green.
[0339] While Figures 19 and 21 illustrate the process upon a child's entry into the classroom, the system according to this embodiment also functions similarly to the first embodiment when a parent or guardian arrives to pick up their child (the scenario corresponding to Appendix 1). Specifically, when the detection means 31 installed at the reception area of the cram school detects the arrival of a parent or guardian, the server 20 notifies the instructor's terminal in the classroom where the parent's child (student) is located of the parent's arrival. Furthermore, at this time (corresponding to Appendix 17-19), the server 20 refers to the suspicious person detection history database 218 to check whether a suspicious person has been detected in the vicinity of the facility in the recent past (for example, within the last 30 minutes). If a suspicious person has been detected, the server 20 includes a security warning (corresponding to the security warning display area 2108 in Figure 21) in the notification sent to the classroom, such as "A suspicious person has been detected in the vicinity. Please be careful when handing over students." This further enhances the safety of instructors when handing over students to parents who have come to pick them up.
[0340] The threat details display area 2110 is an area that displays information that forms the basis of the warning (e.g., "Detection location: near the main gate," "Detection time: 10 minutes ago") and a simplified display of the current safety rank of the facility.
[0341] The supplementary message display area 2112 from the facility is an area that displays instructions issued by the facility in conjunction with the warning (e.g., "Please enter the classroom when picking up your child," "We will be implementing group dismissal").
[0342] The confirmation complete button 2114 is an operating component that accepts an action (e.g., pressing the "Confirmed" button) by the guardian to notify the facility that they have reviewed the warning content.
[0343] The detailed confirmation link button 2116 is an operating component that allows users to proceed to the dashboard screen (such as the suspicious person detection map) and check the situation in more detail.
[0344] The pick-up notification button 2118 is an operating component that accepts input from parents who have received a warning, allowing them to immediately reply to the facility with their intention to pick up their child and their estimated arrival time.
[0345] The emergency contact button 2120 is an operating component that accepts operations for making phone calls to the facility and notifying emergency contacts.
[0346] <Variation> In the above description of the embodiment, an example was described in which the server 20 communicates with the server 95 of the large-scale language model service to prompt the large-scale language model and have it execute processing. In this way, the server 20 can prompt a system that performs language processing to perform information processing in accordance with the prompt. Such an information processing system that performs language processing may use an external device (for example, the server 95 of the large-scale language model service), or it may be executed by an information processing system built into the server 20 or terminal 10 (for example, a processor for language processing).
[0347] A network consists of various mobile communication systems, such as the internet, LANs, and wireless base stations. For example, a network includes 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks that can connect to the internet via designated access points (e.g., Wi-Fi®). When connecting wirelessly, communication protocols include, for example, Z-Wave®, ZigBee®, and Bluetooth®. When connecting via a wired connection, the network also includes connections made directly via USB (Universal Serial Bus) cables, etc.
[0348] Furthermore, by distributing all or part of each hardware configuration across multiple computers and connecting them to each other via a network, a computer can be virtually realized. Thus, the concept of a computer includes not only computers housed in a single enclosure or case, but also virtualized computer systems.
[0349] A database, specifically a relational database, is used to manage and link together tabular data sets called masters, which are structurally defined by rows and columns. In a database, tables are called tables, masters are called masters, the columns of tables are called columns, and the rows of tables are called records. In a relational database, relationships can be established and linked between tables and masters.
[0350] Typically, each table and master has a primary key column to uniquely identify records, but setting a primary key column is not mandatory. The control unit can instruct the processor 901 to add, delete, or update records in specific tables and masters stored in the memory unit, according to various programs.
[0351] Furthermore, by storing data, various programs, and various databases in the memory unit, the information processing device and information processing system related to this disclosure can be considered to have been manufactured.
[0352] Furthermore, the databases and masters in this disclosure may include any data structures (lists, dictionaries, associative arrays, objects, etc.) in which information is structurally defined. Data structures also include data that can be considered as data structures by combining data with functions, classes, methods, etc., written in any programming language.
[0353] Furthermore, each of the above-mentioned configurations, functions, processing units, processing means, etc., may be implemented in hardware, either partially or entirely, by designing them as integrated circuits, for example. The present invention can also be implemented by software program code that realizes the functions of the embodiment. In this case, a storage medium on which the program code is recorded is provided to a computer, and the processor of that computer reads the program code stored in the storage medium. In this case, the program code read from the storage medium itself realizes the functions of the embodiment described above, and the program code itself and the storage medium on which it is stored constitute the present invention. Examples of storage media used to supply such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs, optical disks, magneto-optical disks, CD-Rs, magnetic tapes, non-volatile memory cards, ROMs, and the like.
[0354] Furthermore, the program code that implements the functions described in this embodiment can be implemented in a wide range of programming or scripting languages, such as assembler, C / C++, Perl, Shell, PHP, and Java (registered trademark).
[0355] Furthermore, the program code for the software that implements the functions of the embodiment may be distributed via a network and stored in a storage means such as a computer's hard disk or memory, or in a storage medium such as a CD-RW or CD-R, and the computer's processor may read and execute the program code stored in the storage means or storage medium.
[0356] The functions realized by the components described herein may be implemented in a circuit or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), CPUs (a Central Processing Unit), conventional circuits, and / or combinations thereof, programmed to realize the functions described herein. A processor is considered to be a circuit or processing circuitry, including transistors and other circuits. A processor may be a programmed processor that executes a program stored in memory.
[0357] In this specification, circuitry, unit, and means are hardware programmed to perform or execute the functions described herein. Such hardware may be any hardware disclosed herein, or any hardware known to be programmed to perform or execute the functions described herein.
[0358] If the hardware is a processor that is considered to be a type of circuitry, then the circuitry, means, or unit is a combination of hardware and software used to constitute the hardware and / or processor.
[0359] While several embodiments of this disclosure have been described above, these embodiments can be implemented in a variety of other forms, and various omissions, substitutions, and modifications are permitted without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents.
[0360] (Note) The details described in each of the above embodiments are noted below.
[0361] (Note 1) A program for operating a computer having one or more computer processors, wherein the memory unit is configured to store in association information information of the names of children using a childcare facility, information information of the class to which the children belong at the childcare facility, and information for authenticating the guardians of the children, and the childcare facility has multiple notification means installed in multiple locations, and the program causes one or more computer processors to perform the following steps: to detect that a child's guardian has come to the childcare facility based on the information for authenticating the guardian; to determine a notification destination related to the child from among multiple notification destinations at the childcare facility based on the information of the child's class associated with the detected guardian; and to notify the notification means at the determined notification destination of at least one of the information of the visiting guardian or the information of the guardian's child.
[0362] (Note 2) In the notification step, a notification device installed at a specific location in the childcare facility notifies at least one of the parent's information or the parent's child's information detected in the detection step, regardless of the child's class, while a notification device installed at a location other than a specific location notifies according to the notification destination determined in the determination step, as described in Appendix 1 of the program.
[0363] (Note 3) The program described in either Appendix 1 or 2, wherein in the decision-making step, it is decided that during a specific time period, notifications will be sent to multiple recipients at the childcare facility, regardless of the recipients determined based on the class information of the child associated with the detected guardian, and in the notification step, during a specific time period, at least one of the detected guardian's information or the information of the guardian's child will be sent to the multiple determined recipients, regardless of the child's class.
[0364] (Note 4) A program as described in any of Appendix 1 to 3, wherein a camera is installed at the entrance of the childcare facility, and in the detection step, the camera at the entrance captures the face of the parent or a specific object the parent is holding, and this is compared with information used to authenticate the parent to detect that the parent has entered the childcare facility.
[0365] (Note 5) The program, as described in any of Appendix 1 to 4, is configured in the memory unit to store authentication information for each user of the childcare facility to unlock the door upon entry to the facility, a reader is installed at the entrance of the childcare facility to read the information via short-range wireless communication, and in the detection step, when the terminal held by the guardian and the reader installed at the entrance of the childcare facility are within a certain distance of each other, the program detects that a guardian has arrived by comparing the information obtained from reading the terminal with the authentication information for unlocking the door.
[0366] (Note 6) The program, as described in any of Appendix 1 to 5, is configured in its memory unit to store identification information of output terminals installed in each class of the childcare facility, and in the step of determining, it determines the notification destination related to the child of the visiting parent, and from among multiple notification destinations, it determines the output terminal installed in the class to which the child belongs as the notification destination, and in the step of notifying, it uses different notification methods for the output terminal in the class to which the determined child belongs and for the output terminal in the class to which the child does not belong, thereby notifying at least one of the visiting parent's information or the information of the parent's child.
[0367] (Note 7) The program, as described in any of Appendix 1 to 6, is configured in its memory unit to store identification information of terminals held by operators in charge of each class at the childcare facility, and in the decision step, determines the recipient of notifications related to the child of the visiting parent, and from among multiple recipients, selects the terminal of the operator in charge of the class to which the child belongs as the recipient, and in the notification step, uses different notification methods for the terminal of the operator in charge of the selected class to which the child belongs and the terminal of the operator who does not have a designated class, thereby notifying at least one of the visiting parent's information or the information of the parent's child.
[0368] (Note 8) The program, as described in any of Appendix 1 to 7, is configured in the memory unit to store schedule information for each class of children, including information about the places the children use at different times of the day, and in the decision step, it refers to the schedule information from among multiple notification destinations and determines the location the child is using as the notification destination based on the timing at which it is detected that a parent or guardian has arrived.
[0369] (Note 9) The program described in any one of the appendices 6 to 8, wherein the memory unit is configured to store information about the class to which a child belongs, and in the notification step, it generates notification content information by referring to the information about the class to which the child belongs, and by combining at least one of the parent's name or the name of the parent's child with the name of the class to which the child belongs, and then notifies the determined recipient of the generated notification content information.
[0370] (Note 10) The memory unit is configured to store historical information of when a parent has come to the childcare facility in the detection step, and the program causes one or more computer processors to perform the following steps: identify time periods when a parent is likely to come based on the history information of the parent's visits, and notify the child of the possibility of a parent's visit when the time period identified as likely to come arrives on a day when the child is using the childcare facility. This is the program described in any of Appendix 1 to 9.
[0371] (Note 11) The program described in Appendix 10 notifies the child's guardian of both statistical information on the history of visits and information on the time slots that are identified as likely to see a guardian.
[0372] (Note 12) The program is one of the programs described in any of Appendix 1 to 11, which causes one or more computer processors to perform the steps of receiving input from a child's guardian of the child on days when the child is using the childcare facility, and notifying the guardian of the possibility of their arrival as the received scheduled arrival time approaches.
[0373] (Note 13) The program is one of the programs described in any of Appendix 1 to 12, which causes one or more computer processors to perform the following steps: to obtain weather forecast information for the area where the childcare facility is located on days when the child is using the childcare facility; to identify the time of day when the child's guardian is likely to visit, based on the content of the obtained weather forecast; and to notify the guardian of the possibility of visit when the identified time of day arrives.
[0374] (Note 14) The program is one of the programs described in any of Appendix 1 to 13, which causes one or more computer processors to perform the following steps: to obtain location information of the child's guardian on days when the child is using the childcare facility; to evaluate the likelihood of the child's guardian visiting based on the obtained location information of the child's guardian and location information of the childcare facility; and to notify the guardian of the likelihood of the guardian visiting based on the evaluation result of the likelihood of the guardian visiting.
[0375] (Note 15) The memory unit is configured to store log information recording the activities of children in a childcare facility, and the program is one or more computer processors that, in response to detecting the arrival of a child's guardian in a detection step, refer to the log information and perform a step of presenting the results of recording the child's activities to the guardian, as described in any of the appendices 1 to 14.
[0376] (Note 16) The memory unit is configured to store facial information for facial recognition of the guardian as information for authenticating the guardian of a child, and the program causes one or more computer processors to execute the following steps: providing an operation screen to the guardian's terminal for accepting registration of a facial image for facial recognition; issuing an authentication code associated with the childcare facility to the guardian who registers the facial image; and registering information for authenticating the guardian of a child using the childcare facility by accepting input of the issued authentication code from the guardian who registers the facial image, as described in any of the appendices 1 to 15.
[0377] (Note 17) The memory unit is further configured to store information about persons detected from images taken by cameras that photograph a designated area of the facility, and the program causes one or more computer processors to perform the following steps: to detect suspicious persons who are not registered by detecting persons from images taken by cameras and comparing them with information that authenticates guardians; to analyze trends, including the frequency or time of appearance of suspicious persons, based on the detection history of detected suspicious persons; and to calculate and output evaluation indicators that show the safety of the facility based on the analyzed trends, as described in any of the appendices 1 to 16.
[0378] (Note 18) The program described in Appendix 17, which, in the calculation step, determines the physical characteristics or estimated age of the detected suspicious person, and excludes the person from the count of suspicious persons in the calculation of safety evaluation indicators if the person is below a specified age or has specified physical characteristics.
[0379] (Note 19) The program described in Appendix 17 or 18, which, in the output step, visualizes the calculated safety evaluation index along with information on the time or location where the suspicious person was detected, and displays it on the terminal of the facility manager or guardian.
[0380] (Note 20) A method performed by a computer having one or more computer processors, wherein a memory unit is configured to store in association information information of the names of children using a childcare facility, information information of the class to which the children belong at the childcare facility, and information for authenticating the guardians of the children, and the childcare facility has multiple notification means installed in multiple locations, the method performing the steps of: one or more computer processors detecting that a child's guardian has come to the childcare facility based on information for authenticating the guardian; determining a notification destination related to the child from among multiple notification destinations at the childcare facility based on information of the child's class associated with the detected guardian; and notifying the notification means at the determined notification destination of at least one of the information of the visiting guardian or the information of the guardian's child.
[0381] (Note 21) Information processing device, wherein the storage unit is configured to store in association information information of the names of children using the childcare facility, information information of the class to which the children belong at the childcare facility, and information for authenticating the guardians of the children, and the childcare facility has multiple notification means installed in multiple locations, and the control unit of the information processing device performs the following steps: detecting that a child's guardian has come to the childcare facility based on the information for authenticating the guardian; determining a notification destination related to the child from among multiple notification destinations at the childcare facility based on the information of the child's class associated with the detected guardian; and notifying the notification means at the determined notification destination of at least one of the visiting guardian's information or the information of the guardian's child.
[0382] (Note 2-1) A program for operating a computer having one or more computer processors, wherein the memory unit is configured to store information of a person detected from video footage taken by a camera capturing a predetermined area of a facility, and the program causes one or more computer processors to perform the following steps: to detect a person from video footage taken by a camera and determine whether or not the person is a suspicious person based on the person's behavior or attributes; to calculate an evaluation index indicating the safety of the facility based on the detection history of persons determined to be suspicious; and to output the calculated safety evaluation index to the screen of a terminal.
[0383] (Note 2-2) The program described in Appendix (2-1) includes a step in which the height or estimated age of a detected person is identified, and if the identified height or estimated age is below a predetermined threshold, the person is excluded from the determination as a suspicious person or excluded from the count of suspicious persons in the calculation of the evaluation index.
[0384] (Appendix 2-3) A method performed by a computer having one or more computer processors, wherein a memory unit is configured to store information of a person detected from video footage taken by a camera capturing a predetermined area of a facility, the method comprising: one or more computer processors detecting a person from video footage taken by a camera and determining whether or not the person is a suspicious person based on the person's behavior or attributes; calculating an evaluation index indicating the safety of the facility based on the detection history of persons determined to be suspicious; and outputting the calculated safety evaluation index to the screen of a terminal.
[0385] (Appendix 2-4) Information processing device, wherein a storage unit is configured to store information of a person detected from video footage taken by a camera capturing a predetermined area of a facility, and the control unit of the information processing device performs the following steps: one or more computer processors detect a person from video footage taken by a camera and determine whether or not the person is a suspicious person based on the person's behavior or attributes; calculating an evaluation index indicating the safety of the facility based on the detection history of persons determined to be suspicious; and outputting the calculated safety evaluation index to the screen of a terminal.
[0386] (Note 3-1) A program for operating a computer having one or more computer processors, wherein the memory unit is configured to store information for authenticating a child using a facility or a guardian of said child, and information on the history of suspicious person detections in the vicinity of the facility, and the program causes one or more computer processors to perform the following steps: receiving an authentication operation when a child or guardian enters or leaves the facility or visits; referring to the detection history information in response to the authentication operation and determining whether a suspicious person has been detected within a predetermined time from the time the authentication operation was performed; and, if it is determined that a suspicious person has been detected within the predetermined time, including warning information to urge caution in the vicinity of the facility in the notification information indicating entry or exit or visit sent to the notification destination associated with the authentication operation.
[0387] (Appendix 3-2) A method performed by a computer having one or more computer processors, wherein a memory unit is configured to store information for authenticating a child using a facility or a guardian of said child, and information on the history of suspicious person detections in the vicinity of the facility, the method comprising: one or more computer processors receiving an authentication operation associated with a child or guardian entering or leaving the facility or visiting the facility; referring to the detection history information in response to the authentication operation and determining whether a suspicious person has been detected within a predetermined time from the time the authentication operation was performed; and, if it is determined that a suspicious person has been detected within the predetermined time, including warning information to urge caution in the vicinity of the facility in the notification information indicating entry or exit or visit to be sent to the notification destination associated with the authentication operation.
[0388] (Appendix 3-3) Information processing device, wherein the storage unit is configured to store information for authenticating a child using a facility or a guardian of said child, and information on the history of suspicious person detections in the vicinity of the facility, and the control unit of the information processing device performs the following steps: receiving an authentication operation when a child or guardian enters or leaves the facility or visits; referring to the detection history information in response to the authentication operation being performed and determining whether or not a suspicious person has been detected within a predetermined time from the time the authentication operation was performed; and, if it is determined that a suspicious person has been detected within the predetermined time, including warning information to urge caution in the vicinity of the facility in the notification information indicating entry or exit or visit that is sent to the notification destination associated with the authentication operation.
Claims
1. A program for operating a computer having one or more computer processors, The memory unit is configured to store information relating to the names of children using the childcare facility, information about the class to which the child belongs at the childcare facility, and information for authenticating the child's guardian. In the aforementioned childcare facility, notification devices are installed in multiple locations. The program is configured on one or more computer processors. A step of detecting when a child's guardian has come to the childcare facility based on information used to authenticate the guardian, Based on the information of the child's class associated with the detected guardian, the steps include determining the notification recipients relevant to the child from among several notification recipients at the childcare facility when the child's guardian visits the facility, A program that causes a designated notification means to perform the step of notifying at least one of the visiting guardian's information or the information of the guardian's child.
2. In the notification step, the notification means installed at a specific location in the childcare facility shall notify at least one of the parent's information or the parent's child's information detected in the detection step, regardless of the child's class, The program according to claim 1, wherein a notification means installed at a location other than the aforementioned specific location provides notification according to the notification destination determined in the determination step.
3. In the aforementioned decision-making step, it is decided that during a specific time period, the notification will be sent to multiple recipients of the childcare facility, regardless of the recipient determined based on the information of the child's class associated with the detected guardian. The program according to claim 1, wherein in the notification step, during the specific time period, at least one of the detected parent's information or the parent's child's information is reported to the predetermined number of recipients, regardless of the child's class.
4. A camera is installed at the entrance of the aforementioned childcare facility. The program according to claim 1, wherein in the detection step, the program detects that the guardian has come to the childcare facility by photographing the guardian's face or a specific object held by the guardian with the camera at the entrance and comparing it with information that authenticates the guardian.
5. The memory unit is configured to store authentication information for each user of the childcare facility, which is used to unlock the door when entering the childcare facility. At the entrance of the aforementioned childcare facility, a reading device that reads information via short-range wireless communication is installed. The program according to claim 1, wherein in the detection step, when the terminal held by the guardian and the reader installed at the entrance of the childcare facility are within a certain distance of each other, the program detects that a guardian has arrived by comparing the information obtained from the terminal read by the reader with the authentication information for unlocking the door.
6. The memory unit is configured to store identification information of output terminals installed in each class of the childcare facility. In the step of making the determination, the notification destination related to the child of the visiting parent is determined, and from among several notification destinations, the output terminal installed in the class to which the child belongs is selected as the notification destination, and in the step of making the notification, the notification method is changed between the output terminal in the class to which the child belongs and the output terminal installed in the class to which the child does not belong, thereby notifying at least one of the information of the visiting parent or the information of the parent's child. The program according to claim 1.
7. The memory unit is configured to store identification information of terminals held by operators in charge of each class at the childcare facility. In the aforementioned decision-making step, in determining the recipient of notifications related to the child of the visiting parent, among several recipients, the terminal of the operator in charge of the class to which the child belongs is selected as the recipient. The program according to claim 1, wherein in the notification step, different notification methods are used for the terminal of the operator in charge of the class to which the determined child belongs and for the terminal of the operator not in charge, thereby notifying at least one of the visiting parent's information or the information of the parent's child.
8. The memory unit is configured to store information about the schedules of the children in each class, including information about the places the children use for each time slot. The program according to claim 1, wherein in the step of making the determination, the program refers to the schedule information among a plurality of notification destinations and determines the location where the child is using as the notification destination based on the timing at which it is detected that the guardian has arrived.
9. The memory unit is configured to store information about the class to which the child belongs, including the name of the class, and in the notification step, By referring to the information of the class to which the child belongs, information is generated that combines at least one of the parent's name or the parent's child's name with the name of the class to which the child belongs. The program according to any one of claims 6 to 8, which broadcasts the generated information of the broadcast content to a determined recipient.
10. The memory unit is configured to store historical information about the timing when it was detected that a parent had come to the childcare facility during the detection step. The program further provides the following to one or more computer processors: Based on the visit history information of the aforementioned guardian, the steps include identifying the time period when the guardian is most likely to visit, The program according to claim 1, which performs the step of notifying the child's guardian of the possibility of their visit when a time period has arrived in which the child's guardian is likely to visit on a day when the child is using the childcare facility.
11. Claim 1: In the notification step, the notification includes both statistical information on the history of visits by the child's guardian and information on the time period in which the guardian is likely to visit. The program described in section 0.
12. The program further provides the following to one or more computer processors: A step in which the child’s guardian enters the time they plan to visit the childcare facility on a day when the child is using the childcare facility, The program according to claim 1, which performs the step of notifying the guardian of the possibility of their visit when the scheduled time of their visit arrives.
13. The program further provides the following to one or more computer processors: On days when the child is using the aforementioned childcare facility, the weather forecast information for the area where the childcare facility is located is obtained, The steps include identifying the time period when the child's guardian is most likely to visit, based on the content of the weather forecast obtained, The program according to claim 1, which performs the step of notifying the guardian of the possibility of their visit in response to the arrival of a specified time period.
14. The program further provides the following to one or more computer processors: The steps include obtaining information on the location of the child's guardian on the day the child is using the childcare facility, A step of evaluating the likelihood of the child's guardian visiting, based on the acquired location information of the child's guardian and the location information of the childcare facility, Based on the evaluation results regarding the likelihood of the child's guardian visiting, the following steps are taken: notify the guardian of the possibility of their visit; The program according to claim 1.
15. The memory unit is configured to store log information recording the activities of children at the childcare facility. The program further provides the following to one or more computer processors: The program according to claim 1, wherein, in the detection step, it is detected that the child's guardian has come to the visit, and in response, the program is instructed to perform a step of presenting the results of recording the child's activities to the guardian by referring to the log information.
16. The memory unit is configured to store facial information for facial recognition of the guardian as information for authenticating the guardian of the child. The program further provides the following to one or more computer processors: The steps include providing the aforementioned guardian's device with an operation screen for accepting registration of facial images for facial recognition, The steps include issuing an authentication code linked to the aforementioned childcare facility to the parent who registers a facial image, The program according to claim 1, which performs the step of registering information to authenticate the guardian of the child using the childcare facility by receiving input of the issued authentication code from the guardian who registers the facial image.
17. The memory unit is further configured to store information about people detected from images taken by a camera that photographs a predetermined area of the facility. The program further provides the following to one or more computer processors: The steps include detecting a person from the video footage acquired by the aforementioned camera and comparing it with the information used to authenticate the guardian, thereby detecting a suspicious person who is not registered; Based on the detection history of the detected suspicious person, the step of analyzing trends including the frequency or time of appearance of the suspicious person, Based on the analyzed trends, the steps include calculating and outputting evaluation indicators that show the safety of the facility, The program according to claim 1, which causes to execute.
18. In the calculation step described above, The program according to claim 17, which determines the physical characteristics or estimated age of the detected suspicious person, and if the person is below a predetermined age or has predetermined physical characteristics, excludes them from the count of suspicious persons in the calculation of the safety evaluation index.
19. In the output step described above, The program according to claim 17 or 18, which visualizes the calculated safety evaluation index along with information on the time or location in which the suspicious person was detected, and displays it on the terminal of the facility manager or guardian.
20. A method performed by a computer having one or more computer processors, The memory unit is configured to store information relating to the names of children using the childcare facility, information about the class to which the child belongs at the childcare facility, and information for authenticating the child's guardian. In the aforementioned childcare facility, notification devices are installed in multiple locations. The above method involves one or more computer processors, A step of detecting when a child's guardian has come to the childcare facility based on information used to authenticate the guardian, Based on the information of the child's class associated with the detected guardian, the steps include determining the notification recipients relevant to the child from among several notification recipients at the childcare facility when the child's guardian visits the facility, A method comprising the steps of: providing information about the visiting guardian or information about the guardian's child to a designated notification means.
21. An information processing device, The memory unit is configured to store information relating to the names of children using the childcare facility, information about the class to which the child belongs at the childcare facility, and information for authenticating the child's guardian. In the aforementioned childcare facility, notification devices are installed in multiple locations. The control unit of the information processing device, A step of detecting when a child's guardian has come to the childcare facility based on information used to authenticate the guardian, Based on the information of the child's class associated with the detected guardian, the steps include determining the notification recipients relevant to the child from among several notification recipients at the childcare facility when the child's guardian visits the facility, An information processing device that performs the steps of: notifying a designated notification means of the designated recipient of at least one of the information of the visiting guardian or the information of the guardian's child.
Citation Information
Patent Citations
Kindergarten orderly pick-up system based on cloud computing platform and face recognition technology
CN110111456A
Facility visitor authentication system, visitor authentication system, personal authentication system, personal authentication device and notification method thereof
JP2018081449A